WO2024031238A1

WO2024031238A1 - Methods for managing forbidden public land mobile network (plmn), and terminal devices

Info

Publication number: WO2024031238A1
Application number: PCT/CN2022/110844
Authority: WO
Inventors: 黄少武; 杨皓睿
Original assignee: 哲库科技(北京)有限公司
Priority date: 2022-08-08
Filing date: 2022-08-08
Publication date: 2024-02-15

Abstract

Methods for managing a forbidden public land mobile network (PLMN), and terminal devices. A method comprises: when a first PLMN is added to a forbidden PLMN list, starting a first timer, wherein the forbidden PLMN list and first timer related information are stored in a same storage unit.

Description

Methods and terminal equipment for managing prohibited public land mobile networks PLMN

Technical field

The embodiments of the present application relate to the field of communications, and specifically relate to a method and terminal equipment for managing a prohibited public land mobile network PLMN.

Background technique

In some scenarios, the terminal device can manage to ban the Public Land Mobile Network (PLMN) based on timer T3245. For example, when terminal 1 receives rejection reason #11 or #35 for PLMN A issued by the network device, When , write PLMN A to the prohibited PLMN list in the Subscriber Identity Module (SIM) card, and start T3245, and the running status of T3245 is stored in UE1.

However, there is currently room for further optimization of the management methods for banning PLMNs.

Contents of the invention

This application provides a method and terminal equipment for managing a prohibited public land mobile network PLMN.

A first aspect provides a method for managing a prohibited PLMN in a public land mobile network, including: when a first PLMN is added to a prohibited PLMN list, a first terminal starts a first timer; wherein the prohibited PLMN list and The first timer related information is stored in the same storage unit.

In a second aspect, a method for managing prohibited PLMNs in a public land mobile network is provided, including: when a second event occurs, a second terminal obtains a prohibited PLMN list and first timer related information, and the prohibited PLMN list and The first timer related information is stored in the same storage unit; the target PLMN is managed according to the first timer related information.

In a third aspect, a method for managing a prohibited public land mobile network PLMN is provided, including: starting a first timer when the SIM card of the subscriber identity module of the second terminal is changed; and when the first timer expires In this case, delete the target PLMN in the prohibited PLMN list.

A fourth aspect provides a terminal device for executing the method in the above first aspect or its respective implementations.

Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its respective implementations.

A fifth aspect provides a terminal device for executing the method in the above second aspect or its respective implementations.

Specifically, the terminal device includes a functional module for executing the method in the above second aspect or its respective implementations.

A sixth aspect provides a terminal device for executing the method in the above third aspect or its respective implementations.

Specifically, the terminal device includes a functional module for executing the method in the above third aspect or its respective implementations.

In a seventh aspect, a terminal device is provided, including a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the method in the above first aspect or its implementations.

In an eighth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, and execute the method in the above second aspect or its respective implementations.

In a ninth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, and execute the method in the above third aspect or its respective implementations.

In a tenth aspect, a chip is provided for implementing any one of the above-mentioned first to third aspects or the method in each implementation manner thereof. Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that the device installed with the device executes any one of the above-mentioned first to third aspects or implementations thereof. method.

An eleventh aspect provides a computer-readable storage medium for storing a computer program, the computer program causing a computer to execute any one of the above-mentioned first to third aspects or the method in each implementation thereof.

In a twelfth aspect, a computer program product is provided, including computer program instructions, which cause a computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner thereof.

A thirteenth aspect provides a computer program that, when run on a computer, causes the computer to execute any one of the above-mentioned first to third aspects or the method in each implementation thereof.

Description of drawings

Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

Figure 2 is a schematic flow chart of a method of managing a PLMN in the related art.

Figure 3 is a schematic flow chart of a method of managing a PLMN in the related art.

Figure 4 is a schematic diagram of a method for managing prohibited PLMNs provided by an embodiment of the present application.

Figure 5 is a schematic diagram of another method for managing prohibited PLMNs provided by an embodiment of the present application.

Figure 6 is a schematic diagram of yet another method for managing prohibited PLMNs provided by an embodiment of the present application.

Figure 7 is a schematic flow chart of a method for managing prohibited PLMNs according to an embodiment of the present application.

Figure 8 is a schematic flow chart of another method for managing prohibited PLMNs according to an embodiment of the present application.

Figure 9 is a processing flow chart of the terminal device when the second event occurs according to an embodiment of the present application.

Figure 10 is a processing flow chart of the terminal device when receiving rejection reason #11 or #35 according to an embodiment of the present application.

Figure 11 is a processing flow chart of the terminal device when removing the card according to an embodiment of the present application.

Figure 12 is a processing flow chart of the terminal device when shutting down according to an embodiment of the present application.

Figure 13 is a processing flow chart of the terminal device when the timer times out according to an embodiment of the present application.

Figure 14 is a schematic flow chart of yet another method for managing prohibited PLMNs according to an embodiment of the present application.

Figure 15 is a processing flow chart of the terminal device when the second event occurs according to yet another embodiment of the present application.

Figure 16 is a processing flow chart of the terminal device when receiving rejection reason #11 or #35 according to yet another embodiment of the present application.

Figure 17 is a processing flow chart of the terminal device when the timer times out according to another embodiment of the present application.

Figure 18 is a schematic flowchart of yet another method for managing prohibited PLMNs according to an embodiment of the present application.

Figure 19 is a processing flow chart of the terminal device when the second event occurs according to yet another embodiment of the present application.

Figure 20 is a processing flow chart of the terminal device when the second event occurs according to yet another embodiment of the present application.

Figure 21 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

Figure 22 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

Figure 23 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

Figure 24 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Figure 25 is a schematic block diagram of a chip provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Regarding the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), wireless fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) deployment scenario. Internet scene.

Optionally, the communication system in the embodiment of the present application can be applied to the unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or the communication system in the embodiment of the present application can also be applied to the licensed spectrum, where, Licensed spectrum can also be considered as unshared spectrum.

The embodiments of this application describe various embodiments in combination with network equipment and terminal equipment. The terminal equipment may also be called user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

The terminal device can be a station (STATION, STA) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital assistant. (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or in the future Terminal equipment in the evolved Public Land Mobile Network (PLMN) network, etc.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).

In the embodiment of this application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal. Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of this application, the network device may be a device used to communicate with mobile devices. The network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA. , or it can be a base station (NodeB, NB) in WCDMA, or an evolutionary base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network network equipment (gNB) or network equipment in the future evolved PLMN network or network equipment in the NTN network, etc.

As an example and not a limitation, in the embodiment of the present application, the network device may have mobile characteristics, for example, the network device may be a mobile device. Optionally, the network device can be a satellite or balloon station. For example, the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc. Optionally, the network device may also be a base station installed on land, water, etc.

In this embodiment of the present application, network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell can be a network equipment ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). The small cell here can include: urban cell (Metro cell), micro cell (Micro cell), pico cell ( Pico cell), femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in Figure 1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (also referred to as a communication terminal or terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area.

Figure 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that in the embodiments of this application, devices with communication functions in the network/system may be called communication devices. Taking the communication system 100 shown in Figure 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be described again here. ; The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the description of the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.

In the embodiment of this application, "predefinition" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). This application is specific to its The implementation method is not limited. For example, predefined can refer to what is defined in the protocol.

In the embodiment of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.

In order to facilitate understanding of the technical solutions of the embodiments of this application, the management method of Forbidden PLMN (FPLMN) related to this application will be described.

In some scenarios, the terminal device may manage to ban the PLMN based on timer T3245. For example, in the case where the terminal device is configured to allow the use of T3245 to manage the ban on PLMN, the terminal device may manage to ban the PLMN based on T3245. Among them, the terminal device is configured to allow the use of T3245 to manage and prohibit the PLMN, which can refer to the timer T3245 operation value in the terminal device's Subscriber Identity Module (Subscriber Identity Module, SIM) card or Global Subscriber Identity Module (Universal Subscriber Identity Module, USIM) card ( Timer T3245Behaviour value) is set to 1. Alternatively, it can also refer to the Timer T3245Behaviour value in the non-volatile memory (Non-Volatile Memory, NVM) of the terminal device being set to 1.

In some scenarios, when the terminal device initiates registration with PLMN A, but the network device issues rejection reason #11 or #35, the terminal device can write PLMN A into the prohibited PLMN list in the SIM card of the terminal device and enable it. T3245, further manages the prohibited PLMN list based on T3245.

Combining Figure 2 and Figure 3, the T3245-based management solution for prohibiting PLMN in related technologies will be described.

As shown in Figure 2, when the SIM card is inserted into UE1, UE1 initiates registration with PLMN A, but receives rejection reason #11 or #35 issued by the network device. In this case, UE1 writes PLMN A into the SIM. Disable the PLMN list and start T3245, which runs in UE1. For example, the file EF_FPLMN of the SIM card in Figure 2 is a file that records prohibited PLMNs. Writing PLMN A to the prohibited PLMN list in the SIM can be understood as writing PLMN A to the file EF_FPLMN of the SIM card.

Afterwards, the SIM card was pulled out from UE1 and inserted into UE2. When UE2 turned on and camped in the cell of PLMN A again, UE2 could not initiate registration in the cell of PLMN A because PLMN A belonged to the prohibited PLMN list. Moreover, since UE2 does not know that T3245 has been activated in UE1, it cannot unban PLMN A through T3245. PLMN A will permanently remain in the banned PLMN list in SIM. Unless manual network selection and registration is successful, UE1 cannot Registration is initiated on the cell of PLMN A.

In addition, in the above example, even if the SIM card has always existed in UE1, when the T3245 timer times out, UE1 will delete PLMN A from the prohibited PLMN list, and will also delete other PLMNs in the prohibited PLMN list, so there are This may cause errors in the management of prohibited PLMNs. For example, as shown in Figure 3, when the SIM card is issued, PLMN PLMN list and start T3245. When T3245 times out, all PLMNs in the PLMN list will be prohibited from being cleared.

Therefore, there is still room for further optimization in how to manage prohibited PLMNs.

In view of this, embodiments of the present application provide a method for managing prohibited PLMNs by storing the prohibited PLMN list and timer-related information for managing the prohibited PLMN list in the same storage unit. In this way, for a terminal device, , either obtain the prohibited PLMN list and timer-related information at the same time, or obtain neither, which is helpful to avoid obtaining only one of the prohibited PLMN list and timer-related information, resulting in the inability to manage the prohibited PLMN list and thus affecting users. A matter of experience.

Embodiments of the present application also provide a method for associating prohibited PLMNs. When the terminal device has a prohibited PLMN list in the SIM card and the prohibited PLMN is not empty, it can start a timer and manage the prohibited PLMN list through the timer. This is helpful to avoid the problem of changing the SIM card while the timer is running, causing the banned PLMN to permanently remain in the banned PLMN list.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of this application include at least part of the following contents.

Figure 4 is a schematic flowchart of a method 200 for managing a prohibited public land mobile network PLMN according to an embodiment of the present application. The method 200 can be applied to the first terminal, which can be the terminal device 120 in the communication system shown in Figure 1. For specific implementation, refer to the relevant description of the embodiment shown in Figure 1. For the sake of brevity, details will not be described here.

In the method 200, the first terminal may store the prohibited PLMN list and timer related information for managing PLMNs in the prohibited PLMN list in the same storage unit. For example, they are all stored in the storage unit of the first terminal, or they are all stored in the storage unit of the SIM card of the first terminal. In this way, the first terminal either obtains the prohibited PLMN list and timer related information at the same time, or cannot obtain both, which is beneficial to realizing effective management of prohibited PLMNs.

It should be understood that the embodiments of this application do not limit the conditions for determining whether a PLMN is banned or added to the banned PLMN list and the conditions for starting the timer. For example, it may be that when rejection reason #11 or #35 issued by the network device is received, The PLMN is added to the prohibited PLMN list and the timer is started, or the first terminal can independently determine to add the PLMN to the prohibited PLMN list and start the timer according to the application scenario, or the PLMN can be added to the prohibited PLMN based on other conditions introduced in the standard evolution. PLMN list and start timer, this application does not limit this.

The following is only an example of adding a PLMN to the prohibited PLMN list and starting the timer when receiving the rejection reason #11 or #35 issued by the network device. It should be noted that other methods of adding a PLMN to the prohibited PLMN list The judgment conditions and the conditions for starting the timer are also applicable to the technical solutions provided by the embodiments of this application.

In this embodiment of the present application, the first terminal is a terminal that is allowed to use timer management to disable PLMN. In some embodiments, the first terminal is configured to allow barring the PLMN using timer management.

In some embodiments, the first terminal is configured to allow the use of timer management to ban the PLMN, which may include:

The Timer T3245Behaviour value in the configuration file of the SIM card of the first terminal (such as EF_FPLMN) is configured as 1, or,

The Timer T3245Behaviour value in the configuration file of the storage unit of the first terminal is configured as 1.

As shown in Figure 4, the method 200 includes at least part of the following content:

S210: When the first PLMN is added to the prohibited PLMN list, start the first timer.

In the embodiment of the present application, the first PLMN may be any PLMN that meets the judgment conditions of being banned or added to the banned PLMN list, and the embodiment of the present application does not place any restrictions on this.

S220: When the first event occurs, store the first timer related information.

In some embodiments, the prohibited PLMN list and the first timer related information are stored in the same storage unit.

In some embodiments, the same storage unit is a storage unit in the first terminal or a storage unit in the SIM of the first terminal.

In some embodiments, the storage unit in the first terminal may be a volatile memory (Volatile Memory, VM) or a non-volatile memory (Non-Volatile Memory, NVM) in the first terminal.

In some embodiments, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM). ), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.

In some embodiments, the volatile memory may be a random access memory (Random Access Memory, RAM), a local database, or other storage units that are cleared upon shutdown.

In some embodiments, the first timer related information includes at least one of the following:

The remaining duration information of the first timer, the total duration information of the first timer, the start time information of the first timer, the time information when the first event occurs, and the running status information of the first timer when the first event occurs.

The remaining duration information of the first timer here can be understood as the remaining duration information of the first timer when the first event occurs.

It should be noted that the first timer related information can be recorded in real time after the first timer is started, or can also be recorded under specific conditions. Different types of related information can have different recording nodes. This application does not The recording node of the first timer-related information is not limited.

It should also be noted that each information in the first timer related information may be recorded at the same time node, or may be recorded at different time nodes, which is not limited in this application. For example, the start time information of the first timer may be recorded when the first timer starts, and the remaining duration information of the first timer may be recorded when the SIM card of the first terminal fails.

It should be understood that the timer in the embodiment of this application may be called a T3245 timer, an extended T3245 timer, a PLMN prohibition timer, or may be a timer defined as other types, which is not limited in this application.

In some embodiments, the first timer is used to trigger the unblocking of the target PLMN in the PLMN list in case of timeout, or in other words, the first timer is used to determine the unblocking time of the target PLMN in the prohibited PLMN list.

For example, when the first timer times out, the target PLMN is deleted from the banned PLMN list, that is, when the first timer times out, the target PLMN is unbanned.

It should be understood that in the embodiment of the present application, the timeout of the first timer can also be expressed as: the first timer expires and the first timer becomes invalid. That is to say, the first terminal may delete the target PLMN from the prohibited PLMN list based on the timeout (or expiration, or invalidation) of the first timer.

In some embodiments, the target PLMN only includes the first PLMN. Then, when the first timer times out, only the first PLMN is unbanned, or in other words, only the first PLMN is deleted from the banned PLMN list.

In this case, timer-based management can achieve accurate prohibition of PLMN, which is beneficial to improving the intelligence and user experience of terminal equipment.

In other embodiments, the target PLMN includes all PLMNs in the prohibited PLMN list. Then, when the first timer times out, all PLMNs in the prohibited PLMN list are unbanned, or in other words, all PLMNs in the prohibited PLMN list are deleted. In this case, timer-based management of all prohibited PLMNs can be implemented, which is beneficial to reducing the implementation complexity of the terminal.

In still other embodiments, the target PLMN includes a plurality of PLMNs in the prohibited PLMN list. Then, when the first timer times out, the multiple PLMNs in the prohibited PLMN list are unbanned, or in other words, the multiple PLMNs in the prohibited PLMN list are deleted. In this case, the management of prohibited PLMN groups can be implemented based on timers. On the one hand, it can improve the intelligence and user experience of the terminal equipment, and on the other hand, it can help reduce the implementation complexity of the terminal.

In some embodiments, the first event may include any event that causes the SIM card of the first terminal to fail (referred to as a failure event), or may also include an event that triggers the start of the first timer, a start event of the first timer, etc. , this application does not limit this.

For example, the SIM card failure event of the first terminal may include at least one of the following events:

The first terminal is powered off, the SIM card of the first terminal is pulled out, and the SIM card of the first terminal is powered off (or in other words, the SIM card of the first terminal is deactivated).

In some embodiments, powering off the SIM card of the first terminal may include disabling the SIM card of the first terminal, for example, the user manually sets the SIM card to be disabled.

For example, the first event may include at least one of the following events:

The first terminal is powered off, the SIM card of the first terminal is pulled out, the SIM card of the first terminal is powered off, and the first PLMN is disabled (for example, rejection reason #11 or #35 for the first PLMN is received from the network device), The first timer starts.

In some embodiments, when a SIM card failure event occurs, the first terminal may store the first timer related information in the storage unit of the first terminal. In this way, when the SIM card is revalidated, the first terminal can use the stored first timer related information to continue to manage the target PLMN in the prohibited PLMN list. Or, when the SIM card is pulled out and inserted into another terminal, since the prohibited PLMN list and timer related information are stored in the storage unit of the first terminal, there will be no situation where other terminals cannot request a certain PLMN in the prohibited PLMN list. PLMN initiated registration issue.

Optionally, when a SIM card failure event occurs, the first terminal may store the remaining duration information of the first timer, the total duration information of the first timer, the start time information of the first timer, and the SIM card failure event. At least one of time information of the event and running status information of the first timer.

For example, when the first terminal is shut down, during the shutdown process, the first terminal can store the remaining duration information of the first timer, the total duration information of the first timer, the start time information of the first timer and the occurrence of the shutdown event. At least one of the time information.

Optionally, the occurrence time information of the shutdown event may refer to any time during the shutdown process, or may also refer to any time information before stopping writing data to the storage unit of the first terminal or SIM during the shutdown process.

For another example, when the SIM card of the first terminal is pulled out, after the SIM card is pulled out, the first terminal can store the time information when the SIM card of the first terminal is pulled out, and the remaining time information of the first timer, At least one of the total duration information of the first timer and the start time information of the first timer.

For another example, after the SIM card of the first terminal is powered off, the first terminal may store the time information of the SIM card of the first terminal being powered off, the remaining duration information of the first timer, the total duration information of the first timer and the first timer. At least one of the start time information of a timer.

Optionally, when a SIM card failure event occurs and the first timer is in a running state when the SIM card failure event occurs, the first terminal may store the first timer related information in the storage unit of the first terminal. Alternatively, if the first timer has expired when the SIM card failure event occurs, the first terminal may not store the first timer related information.

Optionally, when the first PLMN is prohibited or the first timer is turned on, the first terminal may store the total duration information of the first timer, the start time information of the first timer and the occurrence of the first PLMN being prohibited event. at least one of the time information.

For example, when the first terminal receives a rejection message from the network device for the first PLMN (for example, carrying rejection reason 11# or 35#), it determines that the first PLMN is prohibited (or in other words, the first PLMN is regarded as a prohibited PLMN), Further, the first PLMN is added to the prohibited PLMN list and the first timer is started. In this case, the first terminal can store time information when the first PLMN is prohibited event occurs (for example, time information when the rejection message is received, or , at least one of time information added by the first PLMN to the prohibited PLMN list), start time information of the first timer, and total duration information of the first timer.

In some embodiments, when the first PLMN is disabled or the first timer is enabled, the first terminal may store the first timer related information in the storage unit of the SIM card of the first terminal. In this way, when the SIM card is inserted into other terminals, other terminals can use the first timer-related information stored in the SIM card to continue to manage the target PLMN in the banned PLMN list, which is helpful to avoid the problem of the PLMN being unable to unban due to the loss of timer-related information. .

In some scenarios, a second event may occur on the first terminal. The second event may refer to any event that may trigger the behavior of reading the SIM. In other words, the second event may be a SIM card validation event, such as the first terminal turning on. The SIM card is inserted into the first terminal, or the SIM card of the first terminal is powered on (or in other words, the SIM card of the first terminal is enabled), etc. This application does not limit this.

In some embodiments, powering on the SIM card of the first terminal may include re-enabling the SIM card of the first terminal if it is disabled, for example, the user manually sets and enables the SIM card.

In some embodiments, when the second event occurs on the first terminal, the first terminal can determine whether the SIM card has changed, that is, whether to change the card. Since different SIM cards correspond to different permissions, in the case of changing the card In this case, it can be considered that the prohibited PLMN list and first timer related information stored on the first terminal are not applicable to the changed SIM card, or, if the card is not changed, it can be considered that the prohibited PLMN list stored on the first terminal is not applicable to the changed SIM card. Information related to the first timer can continue to be used.

In some embodiments of the present application, the prohibited PLMN list and first timer related information are stored in the storage unit of the first terminal, and the method 200 further includes:

If the SIM card of the first terminal is changed, delete the prohibited PLMN list and first timer related information in the first terminal; or

When the SIM card of the first terminal is not changed, the target PLMN in the prohibited PLMN list is managed according to the first timer related information.

In some embodiments, managing the target PLMN in the prohibited PLMN list according to the first timer related information may include:

According to the first timer related information, it is determined whether to delete (or in other words, whether to unban) the target PLMN in the banned PLMN list, and/or, determine the time to delete the target PLMN in the banned PLMN list, that is, the time to unban the target PLMN.

Determine whether the first timer has timed out based on the information related to the first timer;

Depending on whether the first timer times out, it is determined whether to delete the target PLMN in the prohibited PLMN list.

For example, in the event that the first timer times out, the target PLMN in the prohibited PLMN list is deleted.

For another example, if the first timer does not time out, the second timer is started, and if the second timer times out, the target PLMN in the prohibited PLMN list is deleted. That is to say, the first terminal may delete the target PLMN from the prohibited PLMN list based on the timeout (or expiration, or invalidation) of the second timer.

In some embodiments, the first timer related information includes the running status information of the first timer when the first event occurs. If the first timer is still running when the first event occurs, in this case, the first terminal The time information in the timer-related information determines whether the first timer times out.

The following describes how to set the duration of the second timer and how to determine whether the first timer times out with reference to specific examples.

Method 1: The duration of the second timer is set to the difference between the remaining duration of the first timer and the first duration, and the first duration is the duration between the occurrence time of the first event and the occurrence time of the second event, or, The first duration is the duration between the occurrence time of the first event and the current time.

Optionally, the first event here may be a SIM card invalidation event, and the second event may be a SIM card validation event.

In some embodiments, when a SIM card failure event occurs, the first terminal may store the remaining duration information of the first timer. When the SIM card is revalidated and the first duration has elapsed, the remaining duration of the first timer and the The difference in duration can be understood as the actual remaining duration of the first timer. After the SIM card is re-validated, continue to manage the target PLMN based on the actual remaining time of the first timer. On the one hand, it ensures that the first terminal continues to be unable to initiate registration with the target PLMN during the period when the target PLMN is prohibited. On the other hand, it ensures that the first terminal After this time period, a terminal can initiate registration with the target PLMN without affecting the differentiated management strategies of network equipment for different users.

In some scenarios, the first event is the shutdown of the first terminal, and the second event is the startup of the first terminal, then the first duration may be the duration from the shutdown time of the first terminal to the startup time of the first terminal.

Optionally, the shutdown time of the first terminal may refer to any time during the shutdown process of the first terminal, or may also refer to the time during the shutdown process before the first terminal stops writing data to the storage unit of the first terminal or the SIM card. Any time.

Optionally, the power-on time of the first terminal may refer to any time during the power-on process of the first terminal, or may also refer to after the first terminal is able to read the data of the storage unit of the first terminal or the SIM card during the power-on process. Any time, or any time after the first terminal is able to write data to the storage unit of the first terminal or SIM card.

In other scenarios, the first event is that the SIM card of the first terminal is pulled out, and the second event is that the SIM card is inserted into the first terminal, then the first duration may be the time when the SIM card of the first terminal is pulled out. The time elapsed since the SIM card was inserted into the first terminal.

In some embodiments, the current time may refer to the system time when the first terminal calculates the duration of the second timer.

Method 2: The duration of the second timer is set to the difference between the total duration of the first timer and the second duration, where the second duration is the interval from the start time of the first timer to the second time, and the second time It is the current time or the occurrence time of the second event.

In some embodiments, when the first PLMN is disabled or the first timer is started, the first terminal may store the start time information of the first timer. When the second event occurs and the second duration has elapsed, then The difference between the total duration of the first timer and the second duration can be understood as the actual remaining duration of the first timer. After the second event occurs, continue to manage the target PLMN based on the actual remaining duration of the first timer. On the one hand, it ensures that the first terminal continues to be unable to initiate registration with the target PLMN during the time period when the target PLMN is prohibited. On the other hand, it ensures that the first terminal After this time period, a terminal can initiate registration with the target PLMN without affecting the differentiated management strategies of network equipment for different users.

It should be understood that in this embodiment of the present application, the total duration information of the first timer may be stored in the storage unit of the first terminal, or the total duration of the first timer may not be stored in the storage unit of the first terminal. When providing information, the total duration information of the first timer may be selected by the first terminal, or may be a predefined value, or a default value.

In some embodiments, the total duration of the first timer may also be determined based on the managed target PLMN. For example, timers used to manage different PLMNs may be set to different total durations, enabling precise timer durations to be achieved. Adjustment.

In some embodiments, the first terminal may determine whether the first timer has timed out based on the time elapsed from the occurrence of the first event to the occurrence of the second event (ie, the first time length) and the remaining time length of the first timer. Whether the actual remaining time of the device is greater than zero.

For example, if the remaining time of the first timer is less than or equal to the first time (that is, the actual remaining time of the first timer is less than or equal to 0), it is determined that the first timer has timed out.

For another example, if the remaining time of the first timer is greater than the first time (that is, the actual remaining time of the first timer is greater than 0), it is determined that the first timer has not timed out.

In other embodiments, the first terminal may determine whether the first timer times out based on the start time of the first timer and the second time (ie, the current time or the occurrence time of the second event).

For example, if the interval between the start time of the first timer and the second time is greater than or equal to the total duration of the first timer, it is determined that the first timer has timed out.

For another example, if the interval between the start time of the first timer and the second time is less than the total duration of the first timer, it is determined that the first timer has not timed out.

To sum up, in the embodiment of the present application, the first terminal can store the prohibited PLMN list and the timer-related information used to manage the PLMNs in the prohibited PLMN list in the same storage unit, and both are stored in the storage unit of the first terminal. , or, are stored in the storage unit of the SIM card of the first terminal, which is beneficial to avoid the problem that the SIM card is replaced during the running of the timer, resulting in the prohibited PLMN permanently remaining in the prohibited PLMN list.

The method for managing a prohibited public land mobile network PLMN according to an embodiment of the present application is described in detail above with reference to Figure 4 from the perspective of the first terminal. Hereinafter, another implementation of the present application is described in detail from the perspective of the second terminal with reference to Figure 5 Examples of methods for managing prohibited public land mobile networks, PLMN.

Figure 5 is a schematic flowchart of a method 300 for managing a prohibited public land mobile network PLMN according to another embodiment of the present application. The method 300 is applied to the second terminal, which may be the terminal device 120 in the communication system shown in Figure 1. For specific implementation, please refer to the relevant description of the embodiment shown in Figure 1. For the sake of brevity, details will not be described here.

In the method 300, the second terminal may obtain the prohibited PLMN list and timer related information for managing PLMNs in the prohibited PLMN list from the same storage unit, and further manage the prohibited PLMN list based on the timer related information.

As shown in Figure 5, the method 300 includes at least part of the following content:

S310. When the second event occurs, obtain the prohibited PLMN list and the first timer related information, where the prohibited PLMN list and the first timer related information are stored in the same storage unit;

S320: Manage the first PLMN in the prohibited PLMN list according to the first timer related information.

In some embodiments, the prohibited PLMN list and the first timer related information are stored in the SIM card of the second terminal. That is, the same storage unit may be a storage unit in the SIM card of the second terminal. For example, when the first event occurs, the first terminal stores the prohibited PLMN list and the first timer related information in the SIM card. After the SIM is inserted into the second terminal, the second terminal can read it from the SIM card. Disable PLMN list and first timer related information. For another example, when the first event occurs, the second terminal stores the prohibited PLMN list and the first timer related information in the SIM card, and when the second event occurs, the second terminal can read it from the SIM card. Get the prohibited PLMN list and first timer related information.

In some embodiments, the prohibited PLMN list and the first timer related information are stored in the storage unit of the second terminal. That is, the same storage unit may be the storage unit of the second terminal. For example, when the second terminal is powered off (when the first event occurs), the prohibited PLMN list and first timer related information are stored in the storage unit of the second terminal, and when the second terminal is powered on (when the second event occurs) In this case), the prohibited PLMN list and first timer related information can be read from the storage unit.

In some embodiments, S320 includes:

The target PLMN in the prohibited PLMN list is managed according to the first timer related information, where the target PLMN includes the first PLMN.

It should be understood that in the embodiment of the present application, the timeout of the first timer can also be expressed as: the first timer expires and the first timer becomes invalid.

In some embodiments, the second event may refer to any event that may trigger the behavior of reading the SIM, or the second event may be a SIM card validation event, such as the second terminal is powered on, the SIM card is inserted into the second terminal, or , the SIM card of the second terminal is powered on (or in other words, the SIM card of the second terminal is enabled), etc. This application does not limit this.

In some embodiments, powering on the SIM card of the second terminal may include re-enabling the SIM card of the second terminal if it is disabled, for example, the user manually sets the SIM card to be enabled.

In this embodiment of the present application, the second terminal is a terminal that is allowed to use timer management to disable PLMN. In some embodiments, the second terminal is configured to allow the use of timer management to ban the PLMN, which may include:

The Timer T3245Behaviour value in the configuration file (such as EF_FPLMN) in the SIM card of the second terminal is configured as 1, or,

The Timer T3245Behaviour value in the configuration file in the storage unit of the second terminal is configured as 1.

The start time information of the first timer, the total duration information of the first timer, the time when the first PLMN is banned (for example, the time information of rejection reason 11# or 35# is received, or the time when the first PLMN is added to the banned PLMN list information) time information.

For example, when the first terminal (or the second terminal) receives a rejection message for the first PLMN from the network device (for example, carrying the rejection reason 11# or 35#), it is determined that the first PLMN is prohibited (or in other words, the first PLMN regarded as a prohibited PLMN), further, add the first PLMN to the prohibited PLMN list, and start the first timer. In this case, the first terminal (or the second terminal) can store the event that the first PLMN is prohibited. At least one of time information (for example, time information when the rejection message is received, or time information when the first PLMN is added to the prohibited PLMN list), start time information of the first timer, and total duration information of the first timer.

In some embodiments of this application, the S320 may include:

For another example, if the first timer does not time out, the second timer is started, and if the second timer times out, the target PLMN in the prohibited PLMN list is deleted.

In some embodiments, the second terminal may determine whether the first timer times out based on the total duration of the first timer and a third duration, where the third duration is the start time of the first timer and a third time (such as the current time or the occurrence time of the second event). The current time here may be the system time when the second terminal calculates whether the first timer times out.

In some scenarios, the second event is that the second terminal is powered on. The booting time of the second terminal can refer to any time during the booting process of the second terminal, or it can also refer to the time when the second terminal can read the second terminal during the booting process. Any time after the data is stored in the storage unit of the terminal or the SIM card, or any time after the first terminal is able to write data to the storage unit of the first terminal or the SIM card.

For example, if the total duration of the first timer is less than or equal to the third duration, determine that the first timer has timed out; or

For another example, if the total duration of the first timer is greater than the third duration, it is determined that the first timer has not timed out.

In some embodiments, the duration of the second timer is set to a difference between the total duration of the first timer and the third duration.

It should be understood that in this embodiment of the present application, the total duration information of the first timer may be stored in the SIM of the second terminal, or when the total duration information of the first timer is not stored in the SIM of the second terminal. , the total duration information of the first timer can be selected by the second terminal, or a predefined value, or a default value.

In summary, in some embodiments of the present application, the second terminal can obtain the prohibited PLMN list and timer related information for managing the PLMNs in the prohibited PLMN list from the SIM card, and further manage the prohibited PLMN list based on the timer related information. In this way, even if the SIM card is replaced while the timer is running, the terminal into which the SIM card is inserted can continue to manage the banned PLMN list based on the timer-related information, thereby avoiding the replacement of the SIM card during the timer running, resulting in the permanent retention of the banned PLMN. On the issue of banned PLMN list.

Figure 6 is a schematic flowchart of a method 400 for managing a prohibited public land mobile network PLMN according to yet another embodiment of the present application. The method 400 can be applied to the second terminal, which can be the terminal device 120 in the communication system shown in Figure 1. For specific implementation, please refer to the relevant description of the embodiment shown in Figure 1. For the sake of simplicity, details will not be described here.

As shown in Figure 6, the method 400 includes at least part of the following content:

S410: When the SIM card of the second terminal is changed, start the first timer.

In some embodiments, the first timer is used to trigger the unblocking of the target PLMN in the prohibited PLMN list in case of timeout, or in other words, the first timer is used to determine the unblocking time of the target PLMN in the prohibited PLMN list, or in other words, the first timer is used to trigger the unblocking of the target PLMN in the prohibited PLMN list. The second terminal may delete the target PLMN from the prohibited PLMN list based on the timeout (or expiration, or invalidation) of the first timer.

In some embodiments, the second terminal may start the first timer when the SIM card of the second terminal is changed and the SIM card of the second terminal includes a prohibited PLMN list, and the prohibited PLMN list includes at least one PLMN. It can be understood that the SIM card of the second terminal may be a changed SIM card of the second terminal.

In some embodiments, the target PLMN includes only one PLMN. Then, when the first timer times out, only the PLMN is unbanned, or in other words, only the PLMN is deleted from the banned PLMN list. In this case, timer-based management can achieve accurate prohibition of PLMN, which is beneficial to improving the intelligence and user experience of terminal equipment.

In some embodiments, the target PLMN includes all PLMNs in the prohibited PLMN list. Then, when the first timer times out, all PLMNs in the prohibited PLMN list are unbanned, or in other words, all PLMNs in the prohibited PLMN list are deleted. In this case, timer-based management of all prohibited PLMNs can be implemented, which is beneficial to reducing the implementation complexity of the terminal.

In some embodiments, the target PLMN includes a plurality of PLMNs in the prohibited PLMN list. Then, when the first timer times out, the multiple PLMNs in the prohibited PLMN list are unbanned, or in other words, the multiple PLMNs in the prohibited PLMN list are deleted. In this case, the management of prohibited PLMN groups can be implemented based on timers. On the one hand, it can improve the intelligence and user experience of the terminal equipment, and on the other hand, it can help reduce the implementation complexity of the terminal. In this case, the management of prohibited PLMN groups can be implemented based on timers. On the one hand, it can improve the intelligence and user experience of the terminal equipment, and on the other hand, it can help reduce the implementation complexity of the terminal.

In some embodiments, the second terminal is configured to allow barring the PLMN using timer management.

In some embodiments, the second terminal is configured to allow the use of timer management to ban the PLMN, which may include:

In some embodiments, changes to the SIM card of the second terminal may include but are not limited to the following situations:

The second terminal changes from not inserting the SIM card to inserting the SIM card;

The SIM card of the second terminal is changed from SIM card 1 to SIM card 2;

The SIM card of the second terminal is changed from being powered off to being powered on, or in other words, the SIM card is changed from being disabled to being enabled.

In some embodiments, before the SIM card of the second terminal is changed, the method 400 further includes:

A second event occurs on the second terminal. In other words, the change of the SIM card of the second terminal may be triggered by the second event.

In some embodiments, the second event may refer to any event that may trigger the behavior of reading the SIM card. In other words, the second event may be a SIM card validation event, such as the second terminal is powered on and the SIM card is inserted into the second terminal. Alternatively, the SIM card of the second terminal is powered on (or in other words, the SIM card of the first terminal is enabled), etc. This application does not limit this.

In some embodiments, the total duration of the first timer may be selected by the second terminal, or a predefined value, or a default value, or determined according to the managed PLMN, for example, used to manage the timing of different PLMNs. The timer can be set to different total durations, enabling fine adjustment of the timer duration.

In some embodiments, the first timer related information is stored in a storage unit of the second terminal, for example, stored in an NVM or VM in the second terminal.

In some embodiments of this application, S410 includes:

When the subscriber identity module SIM card of the second terminal is changed, and the prohibited PLMN list in the SIM card of the second terminal includes at least one PLMN, the first timer is started.

Therefore, in the method 400, when the SIM card is changed, the second terminal can determine whether the prohibited PLMN list in the SIM card is empty. If it is not empty, the first timer is started. According to The first timer manages the target PLMN in the prohibited PLMN list, for example, when the first timer times out, the target PLMN in the prohibited PLMN list is deleted.

In some specific implementations, when a first event (for example, a SIM card failure event) occurs, the first terminal may not store timer-related information in the SIM card. Furthermore, when a second event occurs on the first terminal, For example, if the SIM card of the first terminal is inserted into the second terminal, that is, the SIM card of the second terminal is changed, the second terminal cannot obtain the timer related information from the SIM card. In this case, the second terminal can The first timer is started when the banned PLMN list in the SIM card is not empty. After the first timer times out, the target PLMN in the banned PLMN list is unbanned, so that the second terminal can target the target PLMN in the banned PLMN list. Initiating registration will help improve user experience.

The following describes the execution flow of the method for managing prohibited PLMNs according to the embodiments of the present application with reference to specific embodiments.

It should be noted that the following embodiments take one timer to manage one PLMN as an example. In other embodiments, one timer can also be used to manage multiple PLMNs, or all PLMNs. The management methods are similar and will not be described again here. .

Example 1:

In Embodiment 1, the terminal device can store the prohibited PLMN list and timer related information through NVM.

A schematic flow chart of a method for managing prohibited PLMNs based on Embodiment 1 is described with reference to FIG. 7 .

Among them, the SIM card of UE1 may include a prohibited PLMN list, and the prohibited PLMN list includes PLMN X.

S1001, UE1 receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S1002, UE1 regards PLMN A as a prohibited PLMN, stores PLMN A in the prohibited PLMN list in the NVM of UE1, and starts timer A (recorded as T_A).

S1003, UE1 receives a rejection message sent by the network device in PLMN B, carrying rejection reason #11 or #35, indicating that PLMN B is prohibited.

S1004, UE1 regards PLMN B as a prohibited PLMN, stores PLMN B in the prohibited PLMN list in the NVM of UE1, and starts timer B (recorded as T_B).

S1005: When the first event occurs, for example, when the SIM card is pulled out or powered off, the remaining duration information of timer A and the remaining duration information of timer B are saved in the NVM of UE1.

Optionally, if timer A and timer B are still in the running state when the first event occurs, save the remaining duration information of timer A and the remaining duration information of timer B, otherwise, delete timer A Related information and timer B related information.

Optionally, in this case, UEl may also store the occurrence time information of the first event. Further, when a second event occurs (for example, UE1 is powered off, or a SIM card is inserted into UE1), UE1 is triggered to read the card and determine whether the SIM card of UE1 has changed, that is, whether to change the card. If the card is not changed, In this case, UE1 can continue to use the banned PLMN list and timer related information stored in the NVM to manage the banned PLMN. Or, in the case of changing the card, UE1 can clear the PLMN and timer related information in the prohibited PLMN list.

S1006. A second event occurs. For example, the SIM card of UE1 is pulled out from UE1 and inserted into UE2.

S1007. After UE2 is powered on, it selects the cell to camp in PLMN A. Since PLMN A does not belong to the prohibited PLMN list, it can initiate registration with PLMN A.

Specifically, since PLMN A and PLMN B only exist in the prohibited PLMN list of UE1's NVM, after UE1's SIM card is inserted into UE2, UE2 cannot learn that PLMN A and PLMN B are prohibited PLMNs. Therefore, registration can be initiated with PLMN A and PLMN B.

S1008, UE2 initiates the registration process to PLMN A.

Example 2:

In this Embodiment 2, the terminal device may store the prohibited PLMN list and timer related information through a volatile memory (such as a local database).

With reference to FIG. 8 , a schematic flow chart of a method for managing prohibited PLMNs based on Embodiment 2 is described.

S2001, UE1 receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S2002, UE1 regards PLMN A as a prohibited PLMN, stores PLMN A in the prohibited PLMN list in the local database of UE1, and starts timer A (recorded as T_A).

S2003, UE1 receives a rejection message sent by the network device in PLMN B, carrying rejection reason #11 or #35, indicating that PLMN B is prohibited.

S2004, UE1 regards PLMN B as a prohibited PLMN, stores PLMN B in the prohibited PLMN list in the local database of UE1, and starts timer B (recorded as T_B).

S2005: When the SIM card is pulled out, the remaining duration information of timer A and the remaining duration information of timer B are saved in UE1. Optionally, in this case, the time information when the SIM card is pulled out can also be recorded.

Optionally, if timer A and timer B are still running when the SIM card is pulled out, save the remaining duration information of timer A and the remaining duration information of timer B, otherwise, delete the timer. A related information and timer B related information.

Further, when a SIM card is inserted into UE1, UE1 is triggered to read the card and determine whether the SIM card of UE1 has changed, that is, whether the card has been changed. Then, without changing the card, UE1 can continue to use the data stored in the NVM. Banned PLMN list and timer related information management ban PLMN. Or, in the case of changing the card, UE1 can clear the PLMN and timer related information in the prohibited PLMN list.

Optionally, when UE1 is powered off, clear the PLMN and timer related information in the prohibited PLMN list stored in the local database.

S2006, a second event occurs. For example, the SIM card of UE1 is pulled out from UE1 and inserted into UE2.

S2007, after UE2 is powered on, it selects the cell to camp in PLMN A. Since PLMN A does not belong to the prohibited PLMN list, it can initiate registration with PLMN A.

Specifically, since PLMN A and PLMN B only exist in the prohibited PLMN list of UE1's local database, after UE1's SIM card is inserted into UE2, UE2 cannot learn that PLMN A and PLMN B are prohibited PLMNs. Therefore, registration can be initiated with PLMN A and PLMN B.

S2008, UE2 initiates the registration process to PLMN A.

Below, the behavior of the UE side when a second event (such as power on or SIM card insertion) occurs in Embodiment 1 or 2 will be described with reference to FIG. 9 .

As shown in Figure 9, at least some of the following steps may be included:

S1101: When the second event occurs, the UE determines whether to replace the SIM card.

For example, determine whether to replace the SIM card based on whether the International Mobile Subscriber Identity (IMSI) or Subscription Permanent Identifier (SUPI) in the UE's storage unit is consistent with the IMSI or SUPI of the current SIM card. . If the MSI or SUPI in the UE's storage unit is consistent with the IMSI or SUPI of the current SIM card, it is determined that the SIM card has not been replaced. Alternatively, if the MSI or SUPI in the UE's storage unit is inconsistent with the IMSI or SUPI of the current SIM card, it is determined that the SIM card has been replaced. SIM card.

If the SIM card is replaced, S1102 is executed. If the SIM card is not replaced, S1103 is executed.

S1102. The UE clears all PLMN and timer related information in the prohibited PLMN list in the storage unit.

Assuming that the prohibited PLMN list in the storage unit includes information related to PLMN A and its corresponding timer (i.e. T_A), and information related to PLMN B and its corresponding timer (i.e. T_B), then in the case of changing the card, the UE clears PLMN A and its corresponding timer (i.e. T_A) related information, PLMN B and its corresponding timer (i.e. T_B) related information.

Optionally, the timer-related information here may include the remaining duration information of the timer, the running status information of the timer, the occurrence time information of the first event, etc.

S1103. Manage the prohibited PLMN list according to the timer-related information in the storage unit of the UE.

For example, manage PLMN A based on T_A related information, and manage PLMN B based on T_B related information.

S1104: Determine whether the timer has timed out based on timer related information.

For example, if the timer related information includes the running status information of the timer when the first event occurs, and if the timer is running when the first event occurs, it is further determined based on the time information in the timer related information whether the timer has timed out.

Optionally, the UE may determine whether the timer has timed out based on the remaining duration of the timer and the first duration. For specific determination methods, refer to the relevant description in method 200.

S1105. If the timer has not expired, determine the actual remaining duration of the timer.

For example, when timer T_A has not expired, the actual remaining duration of timer T_A is determined as the difference between the saved remaining duration of T_A and the first duration.

S1106: Start timer T_A’, and set the duration of timer T_A’ to the actual remaining duration of timer T_A. That is, the difference between the remaining duration of T_A saved and the first duration.

Further, based on the timer T_A', PLMN A is managed, for example, after the timer T_A' times out, PLMN A is deleted from the prohibited PLMN list.

Below, the behavior of the UE side when receiving the rejection reason #11 or #35 in Embodiment 1 or 2 will be described with reference to FIG. 10 .

As shown in Figure 10, at least some of the following steps may be included:

S1201. The UE receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S1202: The UE determines whether it is configured to allow the use of timers to manage the PLMN.

For example, if the Timer T3245Behaviour value in the configuration file in the UE's SIM card is configured as 1, or if the Timer T3245Behaviour value in the configuration file in the UE's storage unit is configured as 1, it is determined that the UE is configured to allow the use of timing The server manages the PLMN.

Further, if the UE is configured to allow the use of a timer to manage the PLMN, perform S1203; otherwise, perform S1204.

S1203. Store PLMN A into the prohibited PLMN list in the UE's storage unit (such as NVM or local database), and start the timer T_A.

S1204. Store PLMN A in the SIM card of the UE and record the current time information, such as the current system time.

Below, the behavior of the UE side when the SIM card is pulled out in Embodiment 1 or 2 will be described with reference to FIG. 11 .

As shown in Figure 11, at least some of the following steps may be included:

S1301, determine the running status of the timer.

When the timer is in the running state, execute S1302; otherwise, end the process.

S1302: Store the timer's running status and remaining duration information in the UE's storage unit (such as NVM or local database).

For example, if the timer T_X of PLMN Of course, the running status information of the timer does not need to be stored. The timer that stores the remaining duration information is considered to be a timer in the running status.

That is, the storage unit of the UE may include a prohibited PLMN list, and the prohibited PLMN list may include PLMN X. The storage unit of the UE may also include remaining duration information of T_X, or may also include operating status information of T_X.

Below, the behavior of the UE side in the case of shutdown in Embodiment 1 or 2 will be described with reference to FIG. 12 .

As shown in Figure 12, at least some of the following steps may be included:

S1401, determine the running status of the timer.

When the timer is in the running state, execute S1402; otherwise, end the process.

S1402: Store the running status and remaining duration information of the timer in the NVM of the UE.

For example, if the timer T_X of PLMN X is in the running state when shutting down, the remaining duration information and running status information of T_X can be stored in the NVM of the UE. Of course, the running status information of the timer does not need to be stored. The timer that stores the remaining duration information is considered to be a timer in the running status.

That is, the NVM of the UE may include a prohibited PLMN list, and the prohibited PLMN list may include PLMN X. The NVM of the UE may also include remaining duration information of T_X, or may also include operating status information of T_X.

Below, the behavior of the UE side when the timer times out in Embodiment 1 or 2 will be described with reference to FIG. 13 .

As shown in Figure 13, at least some of the following steps may be included:

S1301, determine whether the timer times out. For the specific determination method, refer to the method of determining whether the first timer has timed out in method 200. For the sake of simplicity, details will not be described here.

S1302: When the timer times out, delete the PLMN managed by the timer from the prohibited PLMN list.

For example, the prohibited PLMN list of the UE's storage unit includes PLMN X and timer (T_X) related information corresponding to PLMN X. When T_X times out, delete PLMN X in the prohibited PLMN list.

Further, the network is searched again according to the updated prohibited PLMN list, or the registered PLMN is reselected.

Therefore, in the embodiment of the present application, when receiving rejection reason #11 or #35, the UE can add the prohibited PLMN to the prohibited PLMN list, and store the prohibited PLMN list and timer related information in the storage unit of the first terminal. information, so that whenever the UE is turned on or a SIM card is inserted, the UE can manage the banned PLMN list based on the stored timer-related information, which helps prevent SIM replacement during the timer running, causing the added PLMN to be permanently retained in the banned PLMN list. question.

Example 3:

In this Embodiment 3, the terminal device can store the prohibited PLMN list and timer related information through the SIM card.

A schematic flow chart of a method for managing prohibited PLMNs based on Embodiment 3 is described with reference to FIG. 14 .

S3001, UE1 receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S3002, UE1 regards PLMN A as a prohibited PLMN, stores PLMN A in the prohibited PLMN list in the SIM of UE1, starts timer A (recorded as T_A), and records the start time information of timer A in the SIM card.

S3003, UE1 receives a rejection message sent by the network device in PLMN B, carrying rejection reason #11 or #35, indicating that PLMN B is prohibited.

S3004, UE1 regards PLMN B as a prohibited PLMN, stores PLMN B in the prohibited PLMN list in the NVM of UE1, starts timer B (recorded as T_B), and records the start time information of timer B in the SIM card.

S3005, the first event occurs, such as the SIM card being pulled out or the phone being powered off.

In this case, UE1 may not operate the prohibited PLMN list and timer related information in the SIM card.

S3006. The second event occurs. For example, the SIM card of UE1 is pulled out from UE1 and inserted into UE2.

S3007: UE2 obtains the prohibited PLMN list and timer-related information in the SIM card, and manages the PLMN list based on the timer-related information. For specific management methods, refer to the relevant descriptions in method 300.

S3008, if UE2 reselects to camp in the cell of PLMN A, but PLMN A belongs to the prohibited PLMN list, it cannot initiate registration with the cell of PLMN A.

S3009, when the timer T_A corresponding to PLMN A times out, delete PLMN A and the corresponding T_A related information in the prohibited PLMN list of the SIM card.

S3010, since PLMN A does not belong to the prohibited PLMN list, UE2 can initiate registration with PLMN A.

Hereinafter, in conjunction with FIG. 15 , the behavior of the UE side will be described in Embodiment 3 when the second event (such as powering on or inserting a SIM card) occurs.

As shown in Figure 15, at least some of the following steps may be included:

S3101, read SIM card files, such as EF_NASCONFIG.

S3102: Determine whether the UE is configured to allow the use of timers to manage the PLMN. For the specific determination method, refer to the relevant descriptions of the foregoing embodiments. If yes, execute S3103; otherwise, end the process.

S3103: Obtain the prohibited PLMN list and timer related information in the SIM card.

It is assumed that the prohibited PLMN list in the storage unit includes information related to PLMN A and its corresponding timer (i.e., T_A), and information related to PLMN B and its corresponding timer (i.e., T_B).

Optionally, the timer-related information here may include timer start time information. Optionally, the total duration information of the timer may also be included.

S3104: Determine whether the timer has timed out based on timer related information. For the specific determination method, refer to the relevant descriptions in method 200 or method 300. If it does not time out, execute S3105; otherwise, end the process.

S3105. Determine the actual remaining duration of the timer. For example, determine the difference between the total duration of the timer and the second duration as the actual remaining duration of the timer, where the second duration is from the start time of the timer to the current time or the second duration. The length of time between events.

S3106: Start the timer and set the timer duration to the actual remaining duration of the timer.

For example, if timer T_A has not expired, timer T_A’ is started. If timer T_A’ times out, PLMN A in the prohibited PLMN list is deleted.

Below, the behavior of the UE side when receiving rejection reason #11 or #35 in Embodiment 3 will be described with reference to FIG. 16 .

As shown in Figure 16, at least some of the following steps may be included:

S3201. The UE receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S3202: The UE determines whether it is configured to allow the use of timers to manage the PLMN.

Further, if the UE is configured to allow the use of a timer to manage the PLMN, perform S3203; otherwise, perform S3204.

S3203. Write PLMN A into the prohibited PLMN list of the SIM card of the UE, start the timer T_A, and record the current time information (such as the current system time) or the start time information of the timer T_A in the SIM card.

S3204: Store PLMN A into the prohibited PLMN list in the SIM card, and record the current time information (such as the current system time).

Below, the behavior of the UE side when the timer times out in Embodiment 3 will be described with reference to FIG. 17 .

As shown in Figure 17, at least some of the following steps may be included:

S3301, determine whether the timer times out. For the specific determination method, refer to the relevant implementation of determining whether the first timer times out in method 200. For the sake of simplicity, details will not be described here.

S3302: When the timer times out, delete the PLMN managed by the timer from the prohibited PLMN list.

For example, the prohibited PLMN list of the UE's SIM card includes PLMN A and the timer (T_A) related information corresponding to PLMN A. When T_A times out, delete PLMN A in the prohibited PLMN list.

Therefore, in the embodiment of this application, when receiving rejection reason #11 or #35, the UE can add the prohibited PLMN to the prohibited PLMN list, and store the prohibited PLMN list and timer related information in the SIM of the first terminal. , in this way, when the SIM card is inserted into other UEs, other UEs can also manage the banned PLMN list based on the timer-related information stored in the SIM card, which is helpful to prevent the replacement of SIMs during the timer running, resulting in the added PLMN permanently remaining in the banned PLMN list. The problem.

Example 4:

In this Embodiment 4, the terminal device may store the prohibited PLMN list through the SIM.

With reference to Figure 18, a schematic flow chart of a method for managing prohibited PLMNs based on Embodiment 4 is described.

S4001, UE1 receives a rejection message sent by the network device in PLMN A, carrying rejection reason #11 or #35, indicating that PLMN A is prohibited.

S4002, UE1 regards PLMN A as a prohibited PLMN, stores PLMN A in the prohibited PLMN list in the SIM of UE1, starts timer T3245, and records timer T3245 related information in the storage unit of UE1.

S4003, UE1 receives a rejection message sent by the network device in PLMN B, carrying rejection reason #11 or #35, indicating that PLMN B is prohibited.

S4004, UE1 regards PLMN B as a prohibited PLMN, stores PLMN B in the prohibited PLMN list in the SIM card of UE1, starts timer T3245, and records timer T3245 related information in the storage unit of UE1.

S4005, the first event occurs, such as the SIM card being pulled out or the phone being powered off.

S4006. The second event occurs. For example, the SIM card of UE1 is pulled out from UE1 and inserted into UE2.

S4007: UE2 obtains the prohibited PLMN list in the SIM card and determines to start timer T3245 based on the prohibited PLMN list.

For example, when the prohibited PLMN list is not empty, timer T3245 is started.

S4008, if UE2 reselects to camp in the cell of PLMN A, but PLMN A belongs to the prohibited PLMN list, it cannot initiate registration with the cell of PLMN A.

S4009, when T3245 times out, delete all PLMNs in the prohibited PLMN list in the SIM.

S4010, since PLMN A does not belong to the prohibited PLMN list, UE2 can initiate registration with PLMN A.

Therefore, in the embodiment of this application, when the SIM card of the UE is changed, the UE starts a timer according to the prohibited PLMN list stored in the SIM card. When the timer times out, all PLMNs in the prohibited PLMN list are deleted. , which is helpful to prevent the problem of replacing the SIM during the timer running, causing the added PLMN to permanently remain in the banned PLMN list.

In Embodiment 4, when receiving rejection reason #11 or #35, the behavior of the UE is consistent with the behavior of the UE when receiving rejection reason #11 or #35 in Embodiment 3. The difference is: The timer-related information in Embodiment 3 is stored in the SIM of the UE, and the timer-related information in Embodiment 4 is stored in the storage unit of the UE. For specific implementation, refer to the relevant description in Figure 16. For the sake of brevity, details will not be repeated here.

In Embodiment 4, when the timer times out, the behavior of the UE side in Embodiment 4 is consistent with the behavior of the UE side in Embodiment 3. For specific implementation, refer to the relevant description in Figure 17. For simplicity, here No longer.

It should be understood that in the embodiments of the present application, Embodiments 1 to 4 can be implemented individually or in combination, and this application is not limited thereto.

For example, in Embodiment 4, the prohibited PLMN list and timer related information may be stored in the SIM card of the UE, for example, the information may be stored based on the method in Embodiment 3.

For another example, in Embodiment 4, a prohibited PLMN list may be stored in the SIM card of the UE, and the prohibited PLMN list and timer related information may also be stored in the storage unit of the UE. For example, it may be based on the information in Embodiment 1 or Embodiment 2. stored in a way.

The following describes the behavior of the UE side in Embodiment 4 when the second event (such as powering on or inserting a SIM card) occurs with reference to Figures 19 and 20 .

As shown in Figure 19, at least some of the following steps may be included:

S4101, read SIM card files, such as EF_NASCONFIG.

Optionally, S4101 may be executed when the SIM card of the UE is changed.

S4102: Determine whether the UE is configured to allow the use of a timer to manage the PLMN. For the specific determination method, refer to the relevant descriptions of the foregoing embodiments.

S4103: Obtain the prohibited PLMN list in the SIM card.

Assume that the prohibited PLMN list in the storage unit includes PLMN A and PLMN B.

S4104: Determine the start timer according to the prohibited PLMN list.

After the timer expires, PLMN A and PLMN B in the prohibited PLMN list are deleted.

As shown in Figure 20, at least some of the following steps may be included:

S4101: The UE determines whether to change the SIM card.

For the specific determination method, refer to the relevant descriptions of the foregoing embodiments, which will not be described again here.

Optionally, before S4101, a second event occurs.

Optionally, before the second event occurs, a prohibited PLMN list is stored in the SIM card of the UE, and timer related information is stored in a storage unit of the UE. Optionally, timer related information may also be stored in the SIM card of the UE, and a prohibited PLMN list may also be stored in the storage unit of the UE.

When the SIM card is replaced, S4211 to S4215 are executed. When the SIM card is not replaced, S4202 to S4205 are executed.

S4202: Determine whether the timer has timed out according to the timer-related information in the storage unit of the UE. For the specific determination method, refer to the relevant descriptions of the foregoing embodiments, which will not be described again here.

S4203: Determine the actual remaining duration of the timer. For the specific determination method, refer to Method 1 or Method 2 in the aforementioned embodiment.

S4204: Start the timer, and manage the PLMNs in the prohibited PLMN list based on the started timer.

S4211. Clear the timer related information stored in the storage unit of the UE. Optionally, in the case where the prohibited PLMN list is stored in the storage unit, the prohibited PLMN list is also cleared.

S4212, read the card file of the replaced SIM card.

S4213. Determine whether the UE is configured to use a timer to manage the PLMN. If so, execute 4214, otherwise, end the process.

S4214: Determine whether the prohibited PLMN list in the SIM is empty. If not, execute S4215, otherwise, end the process.

S4215: Start a timer, and the timer's duration is set to the default duration, or a predefined duration, or the set duration is determined based on the prohibition of PPLMN. The PLMNs in the prohibited PLMN list are managed based on this timer.

That is, in Embodiment 4, when the prohibited PLMN list is not empty, the UE starts a timer to manage the PLMNs in the prohibited PLMN list, which is helpful to avoid changing the SIM card during the running of the timer, resulting in prohibited The issue of PLMN permanently remaining on the banned PLMN list.

The method embodiments of the present application are described in detail above with reference to Figures 4 to 20. The device embodiments of the present application are described in detail below with reference to Figures 21 to 25. It should be understood that the device embodiments and the method embodiments correspond to each other, and are similar to The description may refer to the method embodiments.

Figure 21 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application. As shown in Figure 21, the terminal device 500 includes:

The processing unit 510 is configured to start the first timer when the first PLMN is added to the prohibited PLMN list; and

When the first event occurs, store the first timer related information;

Wherein, the prohibited PLMN list and the first timer related information are stored in the same storage unit.

In some embodiments, the processing unit 510 is also used to:

When the first timer times out, delete the target PLMN in the prohibited PLMN list.

In some embodiments, the target PLMN only includes the first PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes multiple PLMNs in the prohibited PLMN list.

In some embodiments, the same storage unit is a storage unit in the terminal device or a storage unit in a SIM card of the user identification module of the terminal device.

In some embodiments, the first event includes at least one of the following:

The terminal device is shut down;

The SIM card of the terminal device is pulled out;

The SIM card of the terminal device is powered off;

The first PLMN is disabled.

The remaining duration information of the first timer;

The total duration information of the first timer;

The start time information of the first timer;

Time information when the first event occurs;

Running status information of the first timer when the first event occurs.

In some embodiments, the first event includes failure of the SIM card of the terminal device, and the processing unit 510 is further configured to:

When the SIM card of the terminal device fails, the remaining duration information of the first timer and/or the first time information is stored in the storage unit of the terminal device, and the first time information is used to indicate The time when the SIM card of the terminal device expires.

In some embodiments, the first event package indicates that the first PLMN is disabled, and the processing unit 510 is further configured to:

When the first PLMN is disabled, the start time information and/or the total duration information of the first timer are stored in the SIM card of the terminal device.

In some embodiments, the prohibited PLMN list and the first timer related information are stored in the storage unit of the terminal device, and the processing unit 510 is also used to:

When the second event occurs and the SIM card of the terminal device is changed, delete the prohibited PLMN list and the first timer related information in the terminal device; or

When the second event occurs and the SIM card of the terminal device is not changed, the target PLMN in the prohibited PLMN list is managed according to the first timer related information.

In some embodiments, the second event includes at least one of the following:

The terminal device is powered on, a SIM card is inserted into the terminal device, and the SIM card in the terminal device is powered on.

In some embodiments, the processing unit 510 is also used to:

Determine whether the first timer has timed out according to the first timer related information; if the first timer times out, delete the target PLMN in the prohibited PLMN list; or

If the first timer does not time out, start the second timer. If the second timer times out, delete the target PLMN in the prohibited PLMN list.

In some embodiments, the duration of the second timer is set to the difference between the remaining duration of the first timer and the first duration, and the first duration is from the occurrence time of the first event to the The duration between the occurrence time of the second event, or the first duration is the duration between the occurrence time of the first event and the current time.

In some embodiments, the processing unit 510 is also used to:

If the remaining duration of the first timer is less than or equal to the first duration, determine that the first timer has timed out; or

If the remaining time of the first timer is greater than the first time length, it is determined that the first timer has not timed out.

In some embodiments, the duration of the second timer is set to the difference between the total duration of the first timer and a second duration, where the second duration is the start time of the first timer. The length of the interval to the second time, which is the current time or the occurrence time of the second event.

In some embodiments, the processing unit 510 is also used to:

When the interval between the start time of the first timer and the second time is greater than or equal to the total duration of the first timer, it is determined that the first timer has timed out; or

When the interval length from the start time of the first timer to the second time is less than the total time length of the first timer, it is determined that the first timer has not timed out.

In some embodiments, the terminal device is configured to allow the use of timer management to ban the PLMN.

Optionally, in some embodiments, the above-mentioned processing unit may be one or more processors.

It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the first terminal in the method embodiment of the present application, and the above and other operations and/or functions of each unit in the terminal device 500 are respectively intended to implement FIG. 4 to FIG. The corresponding process of the first terminal or UE1 in the method embodiment shown in 20 will not be described again for the sake of simplicity.

Figure 22 shows a schematic block diagram of a terminal device 600 according to an embodiment of the present application. As shown in Figure 22, the terminal device 600 includes:

The processing unit 610 is configured to obtain the prohibited PLMN list and the first timer related information when the second event occurs, wherein the prohibited PLMN list and the first timer related information are stored in the same storage unit;

The first PLMN in the prohibited PLMN list is managed according to the first timer related information.

In some embodiments, the processing unit 610 is also used to:

According to the first timer related information, a target PLMN in the prohibited PLMN column list is managed, where the target PLMN includes the first PLMN. In some embodiments, the target PLMN includes only one PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes multiple PLMNs in the prohibited PLMN list.

In some embodiments, the same storage unit is a storage unit in the SIM card of the subscriber identification module.

The start time information of the first timer, and the total duration information of the first timer.

In some embodiments, the processing unit 610 is also used to:

Determine whether the first timer has timed out according to the first timer related information;

If the first timer times out, delete the at least one PLMN in the prohibited PLMN list; or

If the first timer does not time out, a second timer is started. If the second timer times out, the at least one PLMN in the prohibited PLMN list is deleted.

In some embodiments, the duration of the second timer is set to the difference between the total duration of the first timer and a third duration. The third duration is from the start time of the first timer to The length of time between the third time, where the third time is the current time or the occurrence time of the second event.

In some embodiments, determining whether the first timer has timed out based on the first timer related information includes:

When the total duration of the first timer is less than or equal to the third duration, determine that the first timer has timed out; or

When the total duration of the first timer is greater than the third duration, it is determined that the first timer has not timed out.

In some embodiments, the second terminal is configured to allow the use of a timer corresponding to the PLMN.

In some embodiments, the second event includes at least one of the following:

The second terminal is powered on;

Insert a SIM card into the second terminal;

The SIM card of the second terminal is powered on.

Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The above-mentioned processing unit may be one or more processors.

It should be understood that the terminal device 600 according to the embodiment of the present application may correspond to the second terminal in the method embodiment of the present application, and the above and other operations and/or functions of the various units in the terminal device 600 are respectively to implement Figures 4 to 4 The corresponding process of the second terminal or UE2 in the method embodiment shown in 20 will not be described again for the sake of simplicity.

Figure 23 shows a schematic block diagram of a terminal device 700 according to an embodiment of the present application. As shown in Figure 23, the terminal device 700 includes:

The processing unit 710 is configured to start the first timer when the SIM card of the subscriber identification module of the terminal device is changed;

When the first timer times out, the target PLMN in the prohibited PLMN list is deleted.

In some embodiments, the target PLMN includes only one PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes multiple PLMNs in the prohibited PLMN list

In some embodiments, before the SIM card of the terminal device is changed, the processing unit 710 is also used to:

A second event occurs on the terminal device, where the second event includes at least one of the following:

The terminal device is powered on, a SIM card is inserted into the terminal device, and the SIM card of the terminal device is powered on.

In some embodiments, the first timer related information is stored in a storage unit of the terminal device.

In some embodiments, the processing unit 710 is also used to:

When the SIM card of the subscriber identification module of the terminal device is changed, and the prohibited PLMN list in the SIM card of the terminal device includes at least one PLMN, the first timer is started.

It should be understood that the terminal device 700 according to the embodiment of the present application may correspond to the second terminal in the method embodiment of the present application, and the above and other operations and/or functions of the various units in the terminal device 700 are respectively to implement Figures 4 to 4. The corresponding process of the second terminal or UE2 in the method embodiment shown in 20 will not be described again for the sake of simplicity.

Figure 24 is a schematic structural diagram of a communication device 800 provided by an embodiment of the present application. The communication device 800 shown in Figure 24 includes a processor 810. The processor 810 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in Figure 24, the communication device 800 may further include a memory 820. The processor 810 can call and run the computer program from the memory 820 to implement the method in the embodiment of the present application.

The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

Optionally, as shown in Figure 24, the communication device 800 may also include a transceiver 830. The processor 810 may control the transceiver 830 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.

Among them, the transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

Optionally, the communication device 800 may specifically be the first terminal or the second terminal in the embodiment of the present application, and the communication device 800 may implement the corresponding functions implemented by the first terminal or the second terminal in the various methods of the embodiment of the present application. The process, for the sake of brevity, will not be repeated here.

Optionally, the communication device 800 can be a mobile terminal/terminal device according to the embodiment of the present application, and the communication device 800 can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For the sake of simplicity, , which will not be described in detail here.

Figure 25 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 900 shown in Figure 25 includes a processor 910. The processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in Figure 25, the chip 900 may also include a memory 920. The processor 910 can call and run the computer program from the memory 920 to implement the method in the embodiment of the present application.

The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

Optionally, the chip 900 may also include an input interface 930. The processor 910 can control the input interface 930 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the chip 900 may also include an output interface 940. The processor 910 can control the output interface 940 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

Optionally, the chip can be applied to the first terminal or the second terminal in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first terminal or the second terminal in the various methods of the embodiment of the present application, in order to It’s concise and I won’t go into details here.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiment of the present application. For the sake of simplicity, here No longer.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip and has signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available processors. Programmed logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step and logical block diagram disclosed in the embodiment of this application can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the above memory is an exemplary but not restrictive description. For example, the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the first terminal or the second terminal in the embodiment of the present application, and the computer program causes the computer to perform the various methods in the embodiment of the present application by the first terminal or the second terminal. The corresponding process of implementation will not be repeated here for the sake of brevity.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiment of the present application. , for the sake of brevity, will not be repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the first terminal or the second terminal in the embodiment of the present application, and the computer program instructions cause the computer to execute the various methods implemented by the first terminal or the second terminal in the embodiment of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, no further details will be given here.

An embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the first terminal or the second terminal in the embodiment of the present application. When the computer program is run on the computer, it causes the computer to perform the various methods in the embodiment of the present application by the first terminal or the second terminal. The corresponding process implemented by the second terminal will not be repeated here for the sake of simplicity.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the various methods implemented by the mobile terminal/terminal device in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

A method for managing a prohibited public land mobile network PLMN, which is characterized in that it is applied to a first terminal and includes:

When the first PLMN is added to the prohibited PLMN list, start the first timer;

When the first event occurs, store the first timer related information;

Wherein, the prohibited PLMN list and the first timer related information are stored in the same storage unit.
The method of claim 1, further comprising:

When the first timer times out, delete the target PLMN in the prohibited PLMN list, where the target PLMN includes the first PLMN.
The method according to claim 2, characterized in that:

The target PLMN only includes the first PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes multiple PLMNs in the prohibited PLMN list.
The method according to any one of claims 1 to 3, characterized in that the same storage unit is a storage unit in the first terminal or a storage unit in a user identification module SIM card of the first terminal. .
The method according to any one of claims 1-4, characterized in that the first event includes at least one of the following:

The first terminal is shut down;

The SIM card of the first terminal is pulled out;

The SIM card of the first terminal is powered off;

The first PLMN is disabled.
The method according to any one of claims 1-5, characterized in that the first timer related information includes at least one of the following:

The remaining duration information of the first timer;

The total duration information of the first timer;

The start time information of the first timer;

Time information when the first event occurs;

Running status information of the first timer when the first event occurs.
The method according to any one of claims 1 to 6, characterized in that the first event includes a SIM card failure of the first terminal, and when the first event occurs, the first event is stored. Certain timer related information, including:

When the SIM card of the first terminal fails, the remaining duration information of the first timer and/or the first time information is stored in the storage unit of the first terminal, and the first time information is At the time indicating the expiration of the SIM card of the first terminal.
The method according to any one of claims 1 to 6, characterized in that the first event packet and the first PLMN are prohibited, and in the case of the first event, the first timing is stored. Device-related information, including:

When the first PLMN is disabled, the start time information and/or the total duration information of the first timer are stored in the SIM card of the first terminal.
The method according to any one of claims 1 to 7, characterized in that the prohibited PLMN list and the first timer related information are stored in a storage unit of the first terminal, and the method further includes :

When the second event occurs and the SIM card of the first terminal is changed, delete the prohibited PLMN list and the first timer related information in the first terminal; or

When the second event occurs and the SIM card of the first terminal is not changed, the target PLMN in the prohibited PLMN list is managed according to the first timer related information.
The method of claim 9, wherein the second event includes at least one of the following:

The first terminal is powered on, a SIM card is inserted into the first terminal, and the SIM card in the first terminal is powered on.
The method according to claim 9 or 10, characterized in that, managing the target PLMN in the prohibited PLMN list according to the first timer related information includes:

Determine whether the first timer has timed out according to the first timer related information; if the first timer times out, delete the target PLMN in the prohibited PLMN list; or

If the first timer has not expired, a second timer is started. If the second timer has expired, the target PLMN in the prohibited PLMN list is deleted.
The method according to claim 11, characterized in that the duration of the second timer is set to the difference between the remaining duration of the first timer and the first duration, and the first duration is the first duration. The duration between the occurrence time of the event and the occurrence time of the second event, or the first duration is the duration between the occurrence time of the first event and the current time.
The method of claim 12, wherein determining whether the first timer has timed out based on the first timer related information includes:

If the remaining duration of the first timer is less than or equal to the first duration, determine that the first timer has timed out; or

If the remaining time of the first timer is greater than the first time length, it is determined that the first timer has not timed out.
The method according to claim 11, characterized in that the duration of the second timer is set to the difference between the total duration of the first timer and the second duration, wherein the second duration is the The duration of the interval from the start time of the first timer to the second time, and the second time is the current time or the occurrence time of the second event.
The method of claim 14, wherein determining whether the first timer has timed out based on the first timer related information includes:

When the interval between the start time of the first timer and the second time is greater than or equal to the total duration of the first timer, it is determined that the first timer has timed out; or

When the interval length from the start time of the first timer to the second time is less than the total time length of the first timer, it is determined that the first timer has not timed out.
The method according to any one of claims 1-15, characterized in that the first terminal is configured to allow the use of timer management to ban the PLMN.
A method for managing a prohibited public land mobile network PLMN, which is characterized in that it is applied to a second terminal and includes:

When the second event occurs, obtain the prohibited PLMN list and the first timer related information, wherein the prohibited PLMN list and the first timer related information are stored in the same storage unit;

The first PLMN in the prohibited PLMN list is managed according to the first timer related information.
The method according to claim 17, wherein managing the first PLMN in the prohibited PLMN column list according to the first timer related information includes:

manage the target PLMN in the prohibited PLMN column list according to the first timer related information, wherein,

The target PLMN only includes the first PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes a plurality of PLMNs in the prohibited PLMN list, where the plurality of PLMNs include the first PLMN.
The method according to claim 17 or 18, characterized in that,

The same storage unit is a storage unit in the SIM card of the user identification module of the second terminal.
The method according to any one of claims 17-19, characterized in that the first timer related information includes at least one of the following:

The start time information of the first timer, and the total duration information of the first timer.
The method according to any one of claims 18 to 20, characterized in that, managing the target PLMN in the prohibited PLMN list according to the first timer related information includes:

Determine whether the first timer has timed out according to the first timer related information;

If the first timer times out, delete the target PLMN in the prohibited PLMN list; or

If the first timer does not time out, the second timer is started. If the second timer times out, the target PLMN in the prohibited PLMN list is deleted.
The method according to claim 21, characterized in that the duration of the second timer is set to the difference between the total duration of the first timer and a third duration, and the third duration is the difference between the total duration of the first timer and the third duration. The length of time between the start time of a certain timer and the third time, where the third time is the current time or the occurrence time of the second event.
The method of claim 22, wherein determining whether the first timer has timed out based on the first timer related information includes:

When the total duration of the first timer is less than or equal to the third duration, determine that the first timer has timed out; or

When the total duration of the first timer is greater than the third duration, it is determined that the first timer has not timed out.
The method according to any one of claims 17-23, characterized in that the second terminal is configured to allow the use of a timer corresponding to the PLMN.
The method according to any one of claims 17-24, wherein the second event includes at least one of the following:

The second terminal is powered on;

Insert a SIM card into the second terminal;

The SIM card of the second terminal is powered on.
A method for managing a prohibited public land mobile network PLMN, which is characterized in that it is applied to a second terminal and includes:

When the SIM card of the subscriber identification module of the second terminal is changed, start the first timer;

When the first timer times out, the target PLMN in the prohibited PLMN list is deleted.
The method according to claim 26, characterized in that:

The target PLMN includes only one PLMN; or

The target PLMN includes all PLMNs in the prohibited PLMN list; or

The target PLMN includes multiple PLMNs in the prohibited PLMN list.
The method according to claim 26 or 27, characterized in that, before the SIM card of the second terminal is changed, the method further includes:

A second event occurs on the second terminal, where the second event includes at least one of the following:

The second terminal is powered on, the SIM card is inserted into the second terminal, and the SIM card of the second terminal is powered on.
The method according to any one of claims 26 to 28, characterized in that the first timer related information is stored in a storage unit of the second terminal.
The method according to any one of claims 26-29, characterized in that, when the user identification module SIM card of the second terminal is changed, starting the first timer includes:

When the subscriber identity module SIM card of the second terminal is changed, and the prohibited PLMN list in the SIM card of the second terminal includes at least one PLMN, the first timer is started.
The method according to any one of claims 27-30, characterized in that the second terminal is configured to allow the use of timer management to ban the PLMN.
A terminal device, characterized by including:

A processing unit configured to start the first timer when the first PLMN is added to the prohibited PLMN list; and to store the first timer related information when the first event occurs;

Wherein, the prohibited PLMN list and the first timer related information are stored in the same storage unit.
A terminal device, characterized by including:

A processing unit configured to obtain a prohibited PLMN list and first timer related information when a second event occurs, where the prohibited PLMN list and first timer related information are stored in the same storage unit;

The first PLMN in the prohibited PLMN list is managed according to the first timer related information.
A terminal device, characterized by including:

A processing unit configured to start the first timer when the SIM card of the second terminal is changed; and

When the first timer times out, the target PLMN in the prohibited PLMN list is deleted.
A terminal device, characterized in that it includes: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of claims 1 to 16. The method of any one of claims 17 to 25, or the method of any one of claims 26 to 31.
A chip, characterized in that it includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 16, or as The method of any one of claims 17 to 25, or the method of any one of claims 26 to 31.
A computer-readable storage medium, characterized in that it is used to store a computer program, the computer program causes the computer to perform the method as described in any one of claims 1 to 16, or as any one of claims 17 to 25 The method described in claim 26, or the method described in any one of claims 26 to 31.
A computer program product, characterized by comprising computer program instructions, the computer program instructions causing the computer to perform the method as described in any one of claims 1 to 16, or as described in any one of claims 17 to 25 The method, or the method according to any one of claims 26 to 31.
A computer program, characterized in that the computer program causes the computer to perform the method according to any one of claims 1 to 16, or the method according to any one of claims 17 to 25, or the method according to any one of claims 17 to 25. The method of any one of claims 26 to 31.