Disaster roaming for PLMN

By receiving disaster roaming parameters and reason code judgments, the service interruption problem caused by PLMN stop operation in disaster situations is solved, and service attempts are avoided in areas that do not support disaster roaming, and re-registering when overwriting recovery is completed, ensuring disaster Continuity of roaming services.

CN118923169APending Publication Date: 2024-11-08APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030091.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-29
Filing Date
2023-03-27
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In disaster situations, when the public land mobile network (PLMN) stops operation, it is difficult for user equipment (UE) to achieve disaster roaming, resulting in service interruption, and the existing technology lacks effective solutions.

Method used

User equipment (UE) receives disaster roaming parameters contained in broadcast information, sends a registration request to the disabled PLMN, and receives a reason code to determine whether disaster roaming is allowed in the current tracking area, store tracking area identifiers, and prevents further registration when not allowed. Try and try again after leaving the tracking area.

Benefits of technology

Effectively avoid service attempts in tracking areas that do not support disaster roaming, save bandwidth, and re-try registration when the UE moves to the coverage area, ensuring the recovery of services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923169A_ABST
    Figure CN118923169A_ABST
Patent Text Reader

Abstract

A user equipment (UE) is configured to receive broadcast information from a cell of a public land mobile network (PLMN), the broadcast information including a parameter indicating support of disaster roaming, where the PLMN is a disabled PLMN (FPLMN) of the UE; attempting to register with the FPLMN by transmitting a registration request to the PLMN, the registration request including the PLMN ID of the determined PLMN in the disaster; receiving a message including a cause code indicating that the disaster roaming for the FPLMN is not allowed in a current tracking area (TA) of the cell for the determined PLMN in disaster; storing a tracking area identifier (TAI) of the cell; and preventing a further registration attempt with the FPLMN for the determined PLMN in disaster when the UE is in the current TA.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Priority / Incorporated by Reference

[0002] This application claims priority to U.S. Provisional Application No. 63 / 325,138, filed on March 29, 2022, entitled “Disaster Roaming for PLMN,” the entire contents of which are incorporated herein by reference. Background Art

[0003] A user equipment (UE) may establish a connection with at least one of a plurality of different networks or network types. Different networks or network types may provide different network services to the UE. For example, a base station of a network may provide the UE with access to a public land mobile network (PLMN) (e.g., a PLMN operating a 5G new radio (NR) radio access network (RAN)).

[0004] In some scenarios, the RAN of a PLMN stops operating, for example, due to a disaster situation. In these scenarios, another PLMN, typically a Forbidden PLMN (FPLMN) for the UE, can enable disaster roaming for the UE. The FPLMN can provide normal services to subscribers that are normally served by the PLMN in the disaster. Summary of the invention

[0005] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. The operations include: receiving broadcast information from a cell of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming, wherein the PLMN is a forbidden PLMN (FPLMN) for the UE; attempting to register with the FPLMN by sending a registration request to the FPLMN, the registration request including a PLMN ID of a determined PLMN in disaster; receiving a message including a reason code indicating that disaster roaming for the FPLMN is not allowed in a current tracking area (TA) of the cell for the determined PLMN in disaster; storing a tracking area identifier (TAI) of the cell; and preventing further registration attempts for the determined PLMN in disaster to the FPLMN while the UE is in the current TA.

[0006] Other exemplary embodiments relate to a user equipment (UE) having: a transceiver configured to communicate with one or more networks; and a processor communicatively coupled to the transceiver and configured to perform operations. The operations include: receiving broadcast information from a cell of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming, wherein the PLMN is a forbidden PLMN (FPLMN) of the UE; attempting to register with the FPLMN by sending a registration request to the PLMN, the registration request including a PLMN ID of a determined PLMN in disaster; receiving a message including a reason code indicating that disaster roaming for the FPLMN is not allowed in a current tracking area (TA) of the cell for the determined PLMN in disaster; storing a tracking area identifier (TAI) of the cell; and preventing further registration attempts for the determined PLMN in disaster to the FPLMN when the UE is in the current TA.

[0007] Additional exemplary embodiments relate to a processor of a base station configured to perform operations. The operations include: transmitting broadcast information of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming; receiving a registration request from a user equipment (UE), the registration request including a PLMN ID of a determined PLMN in a disaster, wherein the PLMN is a forbidden PLMN (FPLMN) for the UE; determining that the determined PLMN in a disaster does not provide network coverage in a current tracking area (TA); and transmitting a message including a reason code indicating that the FPLMN does not allow the disaster roaming for the determined PLMN in a disaster in the current TA. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0009] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0010] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0011] Figure 4a A table illustrating an exemplary network deployment for a UE in which one or more PLMNs cease to operate in the current UE geographic area, such as in a disaster situation, is shown according to various exemplary embodiments.

[0012] Figure 4bFIG. 4 shows an example of a PLMN providing disaster roaming according to various exemplary embodiments, in which a PLMN providing disaster roaming broadcasts only disaster-related indications and does not broadcast a list of PLMNs in a disaster. Figure 4a An exemplary diagram of UE and network operations performed in the scenario described in .

[0013] Figure 4c FIG. 1 shows an example of a method for providing disaster roaming in a TA when a PLMN providing disaster roaming in the TA broadcasts a disaster related indication and an accompanying list of PLMNs in a disaster in the TA according to various exemplary embodiments. Figure 4a An exemplary diagram of UE and network operations performed in the scenario described in .

[0014] Figure 5a A table 500 illustrating an exemplary network deployment for a UE in which one or more PLMNs cease to operate in the current UE geographic area, such as in a disaster situation, is shown in accordance with various exemplary embodiments.

[0015] Figure 5b FIG. 4 shows an example of a PLMN providing disaster roaming according to various exemplary embodiments, in which a PLMN providing disaster roaming broadcasts only disaster-related indications and does not broadcast a list of PLMNs in a disaster. Figure 5a An exemplary diagram of UE and network operations performed in the scenario described in .

[0016] Figure 5c FIG. 1 shows an example of a method for providing disaster roaming in a TA when a PLMN providing disaster roaming in the TA broadcasts a disaster related indication and an accompanying list of PLMNs in a disaster in the TA according to various exemplary embodiments. Figure 5a An exemplary diagram of UE and network operations performed in the scenario described in .

[0017] Figure 6 An exemplary method for PLMN selection in a disaster roaming scenario is shown according to various exemplary embodiments described herein. DETAILED DESCRIPTION

[0018] The exemplary embodiments may be further understood with reference to the following description and the associated drawings, in which similar elements have the same reference numerals. The exemplary embodiments are described with reference to user equipment (UE). However, the reference to UE is provided for illustrative purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component. The exemplary embodiments are also described with reference to a 5G new radio (NR) network. However, the reference to the 5G NR network is provided for illustrative purposes only. The exemplary embodiments may be utilized with any network that can establish a connection with a UE and exchange information and data with the UE.

[0019] Exemplary embodiments are described with reference to a public land mobile network (PLMN) for providing disaster roaming services and a system, apparatus, and method for user equipment (UE) attempting to access these disaster roaming services. Specifically, the embodiments described herein relate to operations for rejecting a disaster roaming registration request of a UE using a new cause code, the new cause code indicating that when a second PLMN indicated as a PLMN in a disaster (or a PLMN that ceased operation) in the registration request does not provide network coverage in the current tracking area (TA) of the UE, disaster roaming is not allowed within the TA. In addition, the UE can use the new cause code to avoid further attempts to access disaster roaming services of a PLMN in which the UE indicated the same second PLMN as the PLMN in the disaster in the registration request when it was located. When the UE exits the current TA, the UE can attempt to register with the PLMN again by indicating the same second PLMN as the PLMN in the disaster in the registration request.

[0020] Hereinafter, the term "disaster situation" may refer to a scenario where a PLMN that normally provides normal service in an area is currently out of operation (OoO). The type of event that causes such an OoO "disaster situation" may vary, and any reference to a "disaster situation" herein is not limited to any particular type of outage, but more generally refers to the inability of a network / PLMN to provide services to a UE that the network / PLMN normally could provide such services to.

[0021] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0022] UE 110 may be configured to communicate with one or more networks. In the example of network arrangement 100, the network with which UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution RAN, traditional cellular network, WLAN, etc.), and UE 110 may also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110 may establish a connection with 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NR RAN 120.

[0023] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator (e.g., Verizon, AT&T, T-Mobile, etc.). The 5G NR RAN 120 may, for example, include a cell or base station (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base station, microcell base station, small cell base station, femtocell base station, etc.) configured to send and receive communication traffic from a UE equipped with an appropriate cellular chipset. The gNB 120A may include one or more communication interfaces to exchange data and / or information with the UE 110, a corresponding RAN, a cellular core network 130, the Internet 140, etc.

[0024] UE 110 may connect to 5G NR-RAN 120 via gNB 120A. Those skilled in the art will appreciate that any relevant procedures may be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 may be associated with a particular cellular provider, where UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 may transmit corresponding credential information in order to associate with 5G NR-RAN 120. More specifically, UE 110 may be associated with a particular cell (e.g., gNB 120A). However, as described above, reference to 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0025] In addition to the 5G NR RAN 120, the network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0026] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110 with respect to the network arrangement 100 of FIG. UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, and the like.

[0027] Processor 205 may be configured to execute multiple engines of UE 110. For example, these engines may include a disaster roaming engine 235, which is configured to perform operations including determining an allowed PLMN of the UE that is currently in a disaster, and attempting to register with a forbidden PLMN (FPLMN) that provides disaster roaming services using the allowed PLMN as a "determined PLMN". UE 110 may receive a rejection of the registration attempt, the rejection including a new cause value indicating that "disaster roaming is not allowed for a determined PLMN with a disaster condition in this tracking area", which will be described in further detail below. Upon receiving the new cause value, disaster roaming engine 235 may store the tracking area identifier (TAI) of the cell in a list, which will be described in more detail below.

[0028] The above-described engine as an application (e.g., program) executed by the processor 205 is merely exemplary. The functionality associated with the engine may also be represented as an independent combined component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as an application or an independent application. In addition, in some UEs, the functionality described for the processor 205 is split between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0029] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables a user to perform input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN (not shown in the figure), traditional RAN (not shown in the figure), WLAN (not shown in the figure), etc. Therefore, the transceiver 225 can operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0030] Figure 3 An exemplary base station, e.g., gNB 120A, is shown in accordance with various exemplary embodiments. gNB 120A may represent any access node through which UE 110 may establish a connection and manage network operations.

[0031] The gNB 120A may include a processor 305, a memory arrangement 310, an input / output (I / O) device 315, a transceiver 320, and other components 325. The other components 325 may include, for example, a battery, a data acquisition device, ports for electrically connecting the base station to other electronic devices, and the like.

[0032] The processor 305 may be configured to execute multiple engines of the gNB 120A. For example, the processor 305 of the gNB 120A may execute a disaster roaming engine 330, which may cause the gNB 120A to perform operations including: broadcasting information indicating support for disaster roaming services; receiving a registration attempt from a UE, the registration attempt indicating a "determined PLMN in disaster"; and rejecting the registration attempt using a new cause value indicating "disaster roaming is not allowed for a determined PLMN with a disaster condition in the tracking area", which will be described in further detail below.

[0033] However, reference to processor 305 is merely exemplary. The functionality associated with the engine may also be represented as a separate integrated component of the gNB 120A, or may be a modular component coupled to the gNB 120A, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. In addition, in some base stations, the functionality described for processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of a base station.

[0034] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the gNB 120A. The I / O device 315 may be a hardware component or port that enables a user to interact with the gNB 120A. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies). Thus, the transceiver 320 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0035] A public land mobile network (PLMN) refers to a wireless service provided by a network operator to subscribers in a specific geographic area. The above network arrangement 100 may represent a network arrangement deployed by an operator of a specific public land mobile network (PLMN). In some scenarios, multiple PLMNs may operate within the same network arrangement 100 and share components, such as base stations. A PLMN may be connected to other PLMNs for providing services including roaming, messaging, data, etc. These other PLMNs may belong to the same operator or different operators. The exemplary embodiments described herein may relate to any number of network arrangements deployed by any number of PLMNs, as will be described in more detail below.

[0036] Each PLMN is identified by a PLMN ID that includes a combination of a mobile country code (MCC) and a mobile network code (MNC), where each such combination is globally unique. The subscriber's home PLMN (HPLMN) is stored on the subscriber's SIM card. In addition, one or more visited PLMNs (VPLMNs) may be maintained by the UE and stored on the SIM. When the UE attempts to access a PLMN that is not an HPLMN and the attempt is successful, the accessed PLMN may be stored as a VPLMN. In other scenarios, the VPLMN may be stored at the UE in different ways. A disabled PLMN (FPLMN) refers to a PLMN to which the UE cannot normally connect. The FPLMN list is maintained by the UE and stored on the SIM. When the UE attempts to access a PLMN (e.g., transmits an attach request) and the network rejects the request using the reason code "PLMN not allowed", a new PLMN entry is added to the FPLMN list.

[0037] When the UE detects a system information broadcast from the network, including, for example, a PLMN ID including a Mobile Country Code (MCC) and a Mobile Network Code (MNC), the UE may attempt to access a Public Land Mobile Network (PLMN), for example, to register with the network. The UE may then initiate registration by transmitting a Registration Request to the PLMN, which may be accepted by the PLMN, or rejected, with the rejection being associated with a reason code. The PLMN may reject a registration attempt from the UE when the UE is located in a geographical location where the network is not allowed to provide service due to regulatory or legal restrictions. A reason code may be included in a Registration Rejection when the PLMN is not allowed to provide any service to the UE. A Registration Rejection may be in response to an Initial Registration Request or a Mobility Registration Request.

[0038] As described above, the UE may establish a connection to the corresponding RAN of one or more PLMNs. In some scenarios, the RAN of the PLMN stops operating, for example, due to a disaster situation. In these scenarios, another PLMN, which is typically a disabled PLMN (FPLMN) of the UE, may enable disaster roaming for the UE. The FPLMN may provide normal services to subscribers who are normally served by the PLMN in the disaster. It is the responsibility of the operator of the FPLMN to determine whether disaster roaming services can be provided to the UE. For example, the FPLMN may check whether a disaster roaming agreement (DRA) exists between the FPLMN and the HPLMN of the UE, and additionally check whether a DRA exists between the FPLMN and the PLMN indicated in the registration request (e.g., a "determined PLMN with a disaster situation"), as will be described in more detail below.

[0039] In order to attempt to register disaster roaming, the UE determines the highest priority PLMN with which the UE will register normally and which is in a disaster, and indicates the PLMN as a "determined PLMN with disaster condition" when requesting registration for disaster roaming. The PLMN indicated as a "determined PLMN with disaster condition" may be referred to as a "determined PLMN" in the following description. The UE may determine one or more "determined PLMNs" based on information stored at the UE (e.g., a database of PLMNs to which the UE can attach).

[0040] A PLMN providing disaster roaming services may indicate support for disaster roaming in various ways. In a first example, the PLMN may broadcast in any NG-RAN cell a "list of one or more PLMNs with disaster conditions for which disaster roaming is available to the PLMN". In a second example, the PLMN may broadcast a "disaster-related indication" without an explicit list of PLMNs in disaster for which disaster roaming is provided. This information may be broadcast by the PLMN via a system information block (SIB). In some exemplary embodiments, the disaster-related indication may comprise a single bit.

[0041] Referring to the second example, it is not specified whether the UE determines the "determined PLMN with disaster conditions". In the first option, the UE may determine the "determined PLMN with disaster conditions" based on information stored locally on the UE about which PLMNs are deployed in a country, for example, by selecting the PLMN from a database in which the UE has stored the operator names of all known PLMN IDs. In the second option, the UE does not make a determination and therefore does not indicate the "determined PLMN with disaster conditions".

[0042] Some exemplary embodiments relate to a first option in which the UE determines and indicates a "determined PLMN" when attempting to register with an FPLMN providing disaster roaming (DR). If a first PLMN (e.g., PLMN 1) does not provide network coverage in all areas of a country and the UE is at a location outside the coverage area of ​​PLMN 1, subscribers who would normally be served by that PLMN 1 (e.g., locations within the coverage area of ​​PLMN 1) should not receive services via a disabled PLMN providing disaster roaming (e.g., FPLMN 1), regardless of whether PLMN 1 is in a disaster. This means that if a subscriber or visitor of PLMN 1 attempts to register for disaster roaming on an FPLMN 1 providing disaster roaming via the above first option in a geographic area where PLMN 1 does not provide network coverage (because other PLMNs in the area are in a disaster), the FPLMN 1 providing disaster roaming should reject the registration request.

[0043] According to the currently agreed concept, disaster roaming services will be provided to subscribers only if FPLMN 1 has a Disaster Roaming Agreement (DRA) with the subscriber's Home PLMN (HPLMN) and FPLMN 1 has a DRA with a "determined PLMN with disaster conditions" (i.e., with PLMN 1). If the UE is located in the country of the HPLMN, the "determined PLMN with disaster conditions" may be the HPLMN.

[0044] Currently, rejection reasons are only defined for the following scenarios: 1) the FPLMN providing disaster roaming does not have any disaster roaming agreement (DRA) with the subscriber's home PLMN (HPLMN) (reason: "PLMN not allowed"), and 2) the PLMN 2 providing disaster roaming does not have any DRA with a "determined PLMN with disaster conditions" different from the HPLMN (reason: "disaster roaming for determined PLMN with disaster conditions is not allowed"). The reason code "PLMN not allowed" may be referred to as "reason 1" herein, and the reason code "disaster roaming for determined PLMN with disaster conditions is not allowed" may be referred to as "reason 2" herein. These reasons may have different numbers according to various specifications, and "reason 1" and "reason 2" are for illustrative purposes only.

[0045] For the first case, when the UE receives a registration reject message with the cause "PLMN not allowed" (cause 1), the UE will not retry to register disaster roaming of the same FPLMN (e.g., FPLMN 1). For the second case, when the UE receives a registration reject message with the cause "disaster roaming for a determined PLMN with a disaster condition is not allowed" (cause 2), the UE will not use PLMN 1 as the "determined PLMN" to retry to register disaster roaming of the same FPLMN (e.g., FPLMN 1). However, the UE may use a different PLMN (e.g., PLMN 2) as the "determined PLMN" to attempt to register disaster roaming of the same FPLMN (e.g., FPLMN 1). In both cases, the UE may use PLMN 1 or a different PLMN (e.g., PLMN 2) as the "determined PLMN" to attempt to register disaster roaming of a different FPLMN (e.g., FPLMN 2).

[0046] However, as discussed above, there is a third case where the request for disaster roaming registration is rejected because the "determined PLMN with disaster condition" determined by the UE and signaled to the FPLMN (e.g., FPLMN 1) does not have network coverage in the current geographic area. There is currently no suitable rejection reason for this third case. For this case, if the UE moves to a geographic area where PLMN1 normally has network coverage, the UE should not be prevented from attempting to register disaster roaming for the same FPLMN (e.g., FPLMN 1) using PLMN 1 as the "determined PLMN".

[0047] According to various exemplary embodiments described herein, a disaster roaming framework is described in which a new cause is used to indicate that disaster roaming to a "determined PLMN in disaster" is not supported in the current tracking area (TA). The new cause may be referred to herein as "disaster roaming for a determined PLMN with disaster conditions is not allowed in this tracking area" and may also be referred to as "cause 3". However, those skilled in the art will determine that the new cause may be expressed in any appropriate manner to convey the above concepts and may include any cause number.

[0048] If the network of an FPLMN (e.g., FPLMN 1) infers that disaster roaming is not allowed in the current tracking area (TA) for the "determined PLMN" (if, for example, FPLMN 1 has a DRA with the "determined PLMN" and with the UE's HPLMN, but the "determined PLMN" does not provide network coverage in that TA), the network of the FPLMN will reject the registration request for disaster roaming with a new rejection cause "Disaster roaming for the determined PLMN with disaster conditions is not allowed in this tracking area" (cause 3). If the UE is located in the country of the HPLMN, the "determined PLMN with disaster conditions" may be the HPLMN.

[0049] In some exemplary embodiments, when receiving the registration rejection reason (reason 3), the UE stores the tracking area identity (TAI) of the cell in which the reason is received in association with the PLMN ID of the FPLMN that is the source of receiving reason 3 in the "Forbidden TAI for disaster roaming for PLMN determined to have disaster condition" list. If the (TAI, FPLMNID) entry is included in the list, the UE will not retry registration within the TA and disaster roaming for the FPLMN using the same "determined PLMN". In some embodiments, the PLMN ID of the FPLMN that is the source of receiving reason 3 may be included in the TAI.

[0050] After receiving a rejection from the first FPLMN (e.g., FPLMN 1), the UE may start a new attempt to make a PLMN selection. If the detected cell of the alternative PLMN is in the TA of the PLMN, and the TA is stored in the "Forbidden TAI for disaster roaming for PLMNs with determined disaster conditions" list, the UE may not attempt to select the PLMN. The list may be erased, for example, all entries may be removed periodically or on certain events (such as UE shutdown or USIM removal).

[0051] If there are other PLMNs providing disaster roaming for which the UE has not yet attempted to register for disaster roaming, the UE may attempt to register for disaster roaming using one of these PLMNs.

[0052] In some embodiments, the UE may store the TAI of the cell where the new rejection cause (reason 3) is received together with the PLMN ID of the "determined PLMN with disaster condition" in the "Forbidden TAI for disaster roaming for a determined PLMN with disaster condition" list. If the (TAI, determined PLMN ID) entry is included in the list, the UE may not retry disaster roaming registered within the tracking area and using the same "determined PLMN with disaster condition". However, if the UE can determine a different "determined PLMN with disaster condition" based on information stored locally on the UE, it may retry disaster roaming registered within the tracking area and using a new "determined PLMN with disaster condition". Similar to the above, the list may be erased, for example, all entries may be removed periodically or upon certain events (such as shutdown of the UE or removal of the USIM).

[0053] Hereinafter, two example network deployments for UE will be described with respect to the above-mentioned disaster roaming framework to further illustrate the disaster roaming operations performed by the UE and the PLMN providing disaster roaming services (in these implementations, it is the FPLMN of the UE).

[0054] Figure 4a A table 400 illustrating an exemplary network deployment for a user equipment (UE) 405 according to a first example is shown, wherein one or more PLMNs cease to operate in the current UE geographic location, such as in a disaster situation. In the table 400, six PLMNs are shown, such as a first PLMN (PLMN-A) 410, a second PLMN (PLMN-B) 415, a third PLMN (PLMN-C) 420, a fourth PLMN (PLMN-X) 425, a fifth PLMN (PLMN-Y) 430, and a sixth PLMN (PLMN-Z) 435. In this example, none of the six PLMNs 410-435 is a HPLMN of the UE 405.

[0055] The status of the PLMNs 410-435 relative to the UE 405 and the geographic location where the UE 405 is located is considered both before and after a disaster situation occurs. Before the disaster scenario, PLMN-A 410 is available in the UE geographic location (e.g., has network coverage) and is the FPLMN of the UE; PLMN-B 415 is not available in the UE geographic location (e.g., has no network coverage) and is an allowed PLMN of the UE; PLMN-C 420 is available in the UE geographic location and is an allowed PLMN of the UE; PLMN-X 425 is available in the UE geographic location and is the FPLMN of the UE 405, and no Disaster Roaming Agreement (DRA) exists with PLMN-B 415 or PLMN-C 420; PLMN-Y is available in the UE geographic location and is the FPLMN of the UE 405, and a DRA exists with both PLMN-B 415 and PLMN-C 420 and additionally with the HPLMN of the UE 405; PLMN-Z is available in the UE geographic location and is the FPLMN of the UE 405, and no DRA exists with the HPLMN of the UE 405.

[0056] After a certain disaster scenario, PLMN-A 410 is in a disaster condition in the UE geographic location; PLMN-B 415 remains unavailable (e.g., no network coverage) in the UE geographic location; PLMN-C 420 is in a disaster condition in the UE geographic location; and PLMN-X 425, PLMN-Y 430, and PLMN-Z 435 are available and provide disaster roaming. As described above, disaster roaming is provided to the UE by the PLMN only when a DRA exists with the UE's allowed PLMNs and with the UE's HPLMN.

[0057] Considering the aforementioned disaster scenario, UE 405, PLMN-X 425, PLMN-Y 430, and PLMN-Z 435 may perform communications according to the following examples described with respect to the disaster roaming framework discussed above.

[0058] Figure 4b It is shown that when the PLMN providing disaster roaming only broadcasts disaster-related indications and does not broadcast a list of PLMNs in disaster, Figure 4a An exemplary diagram 450 of UE and network operations performed in the scenario described in FIG. As described above, the disaster-related indication may include, for example, a single bit in a SIB broadcast by the network.

[0059] At 452, the UE receives a disaster roaming indication from one or more of PLMN-X 425, PLMN-Y 430, or PLMN-Z 435. In various examples, the UE may have lost service from an allowed PLMN (e.g., PLMN-C 420), or has recently powered on and performed an initial cell selection. As described above, the PLMN selection procedure includes a series of steps, including decoding an SI broadcast carrying a disaster roaming indication from a cell of the PLMN.

[0060] In 454, the UE determines that the highest priority PLMN with which the UE would normally register is in a disaster, i.e., the "determined PLMN in disaster". This determination is performed based on information stored locally at the UE. In diagram 450, both PLMN-B and PLMN-C are respectively considered "determined PLMNs", and corresponding operations are described with respect to corresponding scenarios in which the UE attempts to register with PLMN-X, PLMN-Y, or PLMN-Z using PLMN-B or PLMN-C as the determined PLMN. Those skilled in the art will appreciate that these operations may be performed continuously or independently depending on the specific scenario encountered by the UE.

[0061] In the first scenario, the UE attempts to register with PLMN-X using PLMN B or PLMN C as the determined PLMN in 456. In either case, PLMN-X rejects the registration request in 458 using cause 2 above, i.e., "disaster roaming is not allowed for a determined PLMN with a disaster condition". This cause is selected because there is no DRA between PLMN-X and either PLMN-B or PLMN-C.

[0062] In the second scenario, the UE attempts to register with PLMN-Z using PLMN B or PLMN C as the determined PLMN in 460. In either case, PLMN-Z rejects the registration request using cause 1 above, i.e., "PLMN not allowed", in 462. This cause is selected because there is no DRA between PLMN-Z and the UE's HPLMN.

[0063] In the third scenario, in 464, the UE attempts to register with PLMN-Y using PLMN B as the determined PLMN. In 466, PLMN-Y rejects the registration request using the new cause 3 described above, i.e., "Disaster roaming for a determined PLMN with a disaster condition is not allowed in this tracking area." This cause is selected because there is a DRA between PLMN Y and the UE's HPLMN and the determined PLMN, but the determined PLMN does not provide network coverage in the cell's TA. As described above, after receiving this new rejection cause, if the UE moves to a different tracking area, the UE may attempt to register with PLMN-Y.

[0064] In the fourth scenario, the UE attempts to register with PLMN Y using PLMN C as the determined PLMN in 468. In 470, the UE successfully registers disaster roaming with PLMN Y because DRA is established with PLMN C and HPLMN, and PLMN-C has network coverage in the current TA.

[0065] Figure 4c FIG. 4 shows that when a PLMN providing disaster roaming in a TA broadcasts a disaster related indication and an accompanying list of PLMNs in a disaster in the TA, Figure 4a An exemplary diagram 480 of UE and network operations performed in the scenario described in FIG. As described above, the disaster-related indication may include a single bit, and the PLMN list may include a PLMN ID.

[0066] In 482, the UE receives a disaster roaming indication and a companion list of PLMNs in disaster from one or more of the PLMNs 425-435. Similar to 452 above, during the PLMN selection procedure, the UE may decode an SI broadcast carrying a disaster roaming indication and a companion list of PLMNs in disaster. In this example, PLMN X lists PLMN-A in the companion list, and PLMN Y and PLMN Z list PLMN-A and PLMN-C in the companion list. PLMN B is not listed because it has no network coverage in the TA. PLMN-C is not listed by PLMN-X because there is no DRA for PLMN-X and PLMN-C.

[0067] In 484, the UE determines that the highest priority PLMN filtered by the list provided in the broadcast message, with which the UE would normally register, is in a disaster, i.e., the "determined PLMN in disaster". In diagram 480, only PLMN-C is considered as the "determined PLMN", and corresponding operations are described with respect to corresponding scenarios in which the UE attempts to register with PLMN-Y or PLMN-Z using PLMN-C as the determined PLMN. Because PLMN B is not included in the list, the UE does not attempt to use PLMN B as the "determined PLMN".

[0068] In the first scenario, the UE does not attempt to register with PLMN-X using PLMN A as the determined PLMN because PLMN A is a forbidden PLMN in 486. The UE also does not attempt to register with PLMN-X using PLMN-C because the PLMN-ID of PLMN-C is not broadcast by PLMN-X.

[0069] In the second scenario, the UE attempts to register with PLMN-Z using PLMN C as the determined PLMN in 490. In 492, PLMN-Z rejects the registration request with cause 1.

[0070] In the third scenario, the UE attempts to register with PLMN-Y using PLMN C as the determined PLMN in 494. The UE successfully registers disaster roaming with PLMN Y in 496. A DRA is established with PLMN C and the HPLMN, and PLMN-C has network coverage in the current TA.

[0071] Figure 5a A table 500 illustrating an exemplary network deployment for a user equipment (UE) 505 according to a second example is shown, wherein one or more PLMNs cease to operate in the current UE geographic location, such as in a disaster situation. In table 500, five PLMNs are shown, such as a first PLMN (PLMN-A) 510, a second PLMN (PLMN-B) 515, a third PLMN (PLMN-C) 520, a fourth PLMN (PLMN-X) 525, and a fifth PLMN (PLMN-Y) 530. In this example, none of the five PLMNs 510-530 is the HPLMN of the UE 505.

[0072] The status of the PLMNs 510-530 relative to the UE 505 and the geographic location in which the UE 505 is located is considered both before and after a disaster condition occurs. Before the disaster scenario, PLMN-A 510 is available in the UE geographic location (e.g., has network coverage) and is the FPLMN for the UE; PLMN-B 515 is not available in the UE geographic location (e.g., has no network coverage) and is an allowed PLMN for the UE; PLMN-C 520 was previously deployed in the country and is no longer deployed in the country; PLMN-X 525 is available in the UE geographic location and is the FPLMN for the UE 505, and no disaster roaming agreement (DRA) exists with PLMN-B 515 or PLMN-C 520; and PLMN-Y 530 is available in the UE geographic location and is the FPLMN for the UE 505, and a DRA exists with both PLMN-B 515 and PLMN-C 520 and additionally with the HPLMN for the UE 505.

[0073] After a certain disaster scenario, PLMN-A 510 is in a disaster condition in the UE geographic location; PLMN-B 515 remains unavailable (e.g., no network coverage) in the UE geographic location; PLMN-C 520 is still no longer deployed in the country; and PLMN-X 525 and PLMN-Y 530 are available and provide disaster roaming. As described above, disaster roaming is provided to the UE by the PLMN only when a DRA exists with the UE's allowed PLMNs and with the UE's HPLMN.

[0074] Considering the aforementioned disaster scenario, UE 505, PLMN-X 525, and PLMN-Y 530 may perform communications according to the following examples described with respect to the disaster roaming framework discussed above.

[0075] Figure 5b It is shown that when the PLMN providing disaster roaming only broadcasts disaster-related indications and does not broadcast a list of PLMNs in disaster, Figure 5a 550 is an exemplary diagram of UE and network operations performed in the scenario described in FIG.

[0076] At 552, the UE receives a disaster roaming indication from one or more of PLMN-X 525 and PLMN-Y 530. In various examples, the UE may have lost service from an allowed PLMN, or has recently powered on and performed an initial cell selection. As described above, the PLMN selection procedure includes a series of steps, including decoding an SI broadcast carrying a disaster roaming indication from a cell of the PLMN.

[0077] In 554, the UE determines that the highest priority PLMN with which the UE would normally register is in a disaster, i.e., the "determined PLMN in disaster". This determination is performed based on information stored locally at the UE. In diagram 550, both PLMN-B and PLMN-C are respectively considered "determined PLMNs", and corresponding operations are described with respect to corresponding scenarios in which the UE attempts to register with PLMN-X or PLMN-Y using PLMN-B or PLMN-C as the determined PLMN. Those skilled in the art will appreciate that these operations may be performed continuously or independently depending on the specific scenario encountered by the UE.

[0078] In the first scenario, the UE attempts to register with PLMN-X using PLMN B or PLMN C as the determined PLMN in 556. In either case, PLMN-X rejects the registration request in 558 using cause 2 above, i.e., "disaster roaming is not allowed for a determined PLMN with a disaster condition". This cause is selected because there is no DRA between PLMN-X and either PLMN-B or PLMN-C.

[0079] In the second scenario, the UE attempts to register with PLMN-Y using PLMN B as the determined PLMN in 560. In 562, PLMN-Y rejects the registration request using cause 3 above, i.e., "Disaster roaming for a determined PLMN with a disaster condition is not allowed in this tracking area." This cause is selected because there is a DRA between PLMN Y and the UE's HPLMN and the determined PLMN, but the determined PLMN does not provide network coverage in the cell's TA.

[0080] In the third scenario, the UE attempts to register with PLMN-Y using PLMN B as the determined PLMN in 564. PLMN-Y rejects the registration request using cause 2 above, i.e., "disaster roaming is not allowed for PLMNs determined to have disaster conditions," in 566. This cause is selected because PLMN C is no longer deployed in the country.

[0081] Figure 5c FIG. 4 shows that when a PLMN providing disaster roaming in a TA broadcasts a disaster related indication and an accompanying list of PLMNs in a disaster in the TA, Figure 5a An exemplary diagram 580 of UE and network operations performed in the scenario described in . As described above, the disaster-related indication may include a single bit, and the PLMN list may include a PLMN ID.

[0082] In 582, the UE receives a disaster roaming indication and a companion list of PLMNs in disaster from one or more of PLMN X or PLMN Y. Similar to 552 above, during the PLMN selection procedure, the UE may decode the SI broadcast carrying the disaster roaming indication and the companion list of PLMNs in disaster. In this example, PLMN X and PLMN Y list PLMN-A in the companion list. PLMN B is not listed because it has no network coverage in the TA, and PLMN C is not listed because it is no longer deployed in the country.

[0083] In 584, the UE determines that the highest priority PLMN filtered by the list provided in the broadcast message with which the UE would normally register is in disaster, i.e., the "determined PLMN in disaster". In diagram 580, no PLMN is determined as the "determined PLMN". PLMN A is the FPLMN of the UE, and only PLMN A is included in the broadcast list.

[0084] In 586, the UE does not attempt to register for disaster roaming on PLMN X or PLMN Y because the only PLMN in the disaster is PLMN A (the UE's FPLMN).

[0085] Embodiments of the present invention provide various UE and network advantages. The UE will gain knowledge about the TA in which the "determined PLMN" cannot be used and avoid attempting to register with the "determined PLMN" in the same TA, but will not avoid attempting to register with the same FPLMN using the same "determined PLMN" when the UE changes to a different TA. Operators that provide disaster roaming can use a single "disaster-related indication" to indicate disaster roaming support without broadcasting an explicit list of PLMNs that are in a disaster, thereby saving valuable bandwidth on SI broadcasts. An FPLMN that rejects registration requests in a specific TA can provide disaster roaming services to the UE when the UE enters a TA in which the "determined PLMN that is in a disaster" has network coverage (in a non-disaster situation), and can generate revenue based on the disaster services provided.

[0086] Figure 6 An exemplary method 600 for PLMN selection in a disaster roaming scenario is shown in accordance with various exemplary embodiments described herein.

[0087] In 605, a user equipment (UE) receives broadcast information from a cell of a public land mobile network (PLMN) (e.g., a disabled PLMN (FPLMN)), the broadcast information including at least a PLMN identifier (ID) and a disaster roaming (DR) indication. In this example, the UE does not receive any associated PLMN ID list in a disaster. In other words, the PLMN only broadcasts parameters indicating support for disaster roaming in the SI broadcast. As described above, in other embodiments, the PLMN may also broadcast an associated PLMN ID list in a disaster, which may simplify the UE's PLMN selection process. However, this embodiment is not considered in exemplary method 600.

[0088] In 610, the UE attempts to register with the FPLMN providing disaster roaming service by sending a registration request including the PLMN ID of the "determined PLMN in disaster" to the FPLMN. The registration request may be an initial registration request, or may be a mobility registration request. The UE determines the "determined PLMN in disaster" based on information stored locally on the UE. For example, the information may include a database in which the UE has stored the operator names of all known PLMN IDs. In some embodiments, the UE may determine more than one "determined PLMN" from the database. The "determined PLMN" may be the UE's HPLMN or the UE's VPLMN. In some embodiments, in the registration request, the UE may additionally include its HPLMN ID so that the FPLMN can determine whether a disaster roaming agreement (DRA) exists between the FPLMN and the UE HPLMN. In some embodiments, the HPLMN ID may be included as part of a subscriber hidden identity (SUCI).

[0089] In 615, the UE receives a message from the cell of the FPLMN, the message including a cause code indicating that "disaster roaming for the determined PLMN with disaster conditions is not allowed in the tracking area" (e.g., the above-mentioned new cause 3). The message may be a registration reject message. As described above, when the FPLMN determines that there is a DRA between the FPLMN and both the "determined PLMN" and the HPLMN of the UE, but the "determined PLMN" does not provide network coverage in the current TA of the UE (i.e., the TA of the cell of the FPLMN), the registration reject message is used.

[0090] In 620, the UE stores at least the tracking area identifier (TAI) of the cell that is the source of receiving cause 3. The UE stores the TAI in a list, which may include other parameters. In a first embodiment, the TAI is stored in a first list and is associated with the FPLMN that is the source of receiving the registration rejection. In a second embodiment, the TAI is stored in a second list and is associated with the "determined PLMN" included by the UE in the registration request. As described above, these lists may be erased periodically or when certain events (e.g., UE shutdown or USIM removal) occur.

[0091] In 625, if the UE remains in the same tracking area, the UE avoids retrying to register for disaster roaming using the same "determined PLMN". In 630, the UE may attempt to register with the same FPLMN or with another FPLMN that provides disaster roaming using a different "determined PLMN". Steps 610-625 may be performed again using a different "determined PLMN". This process may continue until all "determined PLMNs" have been tried.

[0092] In 635, if the UE leaves the tracking area, the UE may attempt to register with the same FPLMN using the same "determined PLMN" as originally used in step 610. As described above in 615, the "determined PLMN" does not provide network coverage in the UE's original TA, but the "determined PLMN" may provide network coverage in the new TA (and is in a disaster situation). In this scenario, the FPLMN will accept the registration request and provide disaster roaming services to the UE.

[0093] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0094] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0095] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0096] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to perform operations comprising: receiving broadcast information from a cell of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming, wherein the PLMN is a forbidden PLMN (FPLMN) of the UE; attempting to register with the FPLMN by sending a registration request to the PLMN, the registration request including a PLMN ID of the determined PLMN in disaster; receiving a message including a cause code indicating that disaster roaming for the FPLMN is not allowed in a current tracking area (TA) of the cell for the determined PLMN in disaster; storing a tracking area identifier (TAI) of the cell; as well as Further registration attempts to the FPLMN for the determined PLMN in disaster are prevented while the UE is in the current TA.

2. The processor of claim 1 , wherein the operations further comprise: When the UE has moved to a new TA, the registration with the FPLMN is attempted using the determined PLMN in disaster.

3. The processor of claim 1, wherein the TAI is stored in a list and associated with the FPLMN.

4. The processor of claim 1, wherein the TAI is stored in a list and associated with the determined PLMN in disaster.

5. The processor of claim 1, wherein the UE determines the determined PLMN in disaster based on information stored locally on the UE.

6. The processor of claim 1, wherein the determined PLMN in disaster is a Home PLMN (HPLMN) of the UE only if the UE is located in a country of the HPLMN.

7. A user equipment (UE), the user equipment (UE) comprising: a transceiver configured to communicate with one or more networks; and a processor communicatively coupled to the transceiver and configured to perform operations including: receiving broadcast information from a cell of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming, wherein the PLMN is a forbidden PLMN (FPLMN) of the UE; attempting to register with the FPLMN by sending a registration request to the PLMN, the registration request including a PLMN ID of the determined PLMN in disaster; receiving a message including a cause code indicating that disaster roaming for the FPLMN is not allowed in a current tracking area (TA) of the cell for the determined PLMN in disaster; storing a tracking area identifier (TAI) of the cell; as well as Further registration attempts to the FPLMN for the determined PLMN in disaster are prevented while the UE is in the current TA.

8. The UE according to claim 7, wherein the operations further comprise: When the UE has moved to a new TA, the registration with the FPLMN is attempted using the determined PLMN in disaster.

9. The UE of claim 7, wherein the TAI is stored in a list and associated with the FPLMN.

10. The UE of claim 7, wherein the TAI is stored in a list and associated with the determined PLMN in disaster.

11. The UE of claim 7, wherein the UE determines the determined PLMN in disaster based on information stored locally on the UE.

12. The UE of claim 7, wherein the determined PLMN in disaster is a Home PLMN (HPLMN) of the UE only if the UE is located in a country of the HPLMN of the HPLMN.

13. A processor of a base station, the processor being configured to perform operations comprising: transmitting broadcast information of a public land mobile network (PLMN), the broadcast information including a parameter indicating support for disaster roaming; receiving a registration request from a user equipment (UE), the registration request including a PLMN ID of a determined PLMN in a disaster, wherein the PLMN is a forbidden PLMN (FPLMN) for the UE; Determining that the determined PLMN in disaster does not provide network coverage in a current tracking area (TA); as well as A message is transmitted including a cause code indicating that the FPLMN does not allow the disaster roaming for the determined PLMN in disaster in the current TA.

14. The processor of claim 13, wherein the operations further comprise: A determination is made as to whether a first Disaster Roaming Agreement (DRA) exists between the FPLMN and the determined PLMN.

15. The processor of claim 14, wherein the operations further comprise: It is determined whether a second DRA exists between the FPLMN and a home PLMN (HPLMN) of the UE.

16. The processor of claim 15, wherein the cause code indicating that the FPLMN does not allow the disaster roaming in the current TA is used only when the first DRA and the second DRA exist.

17. The processor of claim 13, wherein the determined PLMN in disaster is a Home PLMN (HPLMN) of the UE only if the UE is located in a country of the HPLMN.