Enhancements for minimizing service interruptions

By selecting the second PLMN with the Disaster Roaming Agreement and manually registering in a disaster situation, the UE achieves continuity and rapid recovery of services, solving the problem of service interruption in a disaster situation, and improving the reliability and efficiency of disaster roaming services .

CN119096567APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202380030205.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-30
Filing Date
2023-03-22
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In disaster situations, it is difficult for user equipment (UE) to effectively access disaster roaming services, and the prior art cannot effectively mitigate service interruptions and failures, especially when PLMNs cannot provide services.

Method used

The UE manages service connections by selecting a second PLMN with a disaster roaming agreement, or even the PLMN in the prohibited list, and manually selecting and registering in a disaster situation, using a disaster roaming wait timer and a recovery wait timer. Ensure continuity and rapid recovery of services.

Benefits of technology

The service continuity and rapid recovery of UE in disaster situations are achieved, the signaling load on the PLMN is reduced, the reliability and efficiency of disaster roaming services are improved, and the communication services of users are not interrupted.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096567A_ABST
    Figure CN119096567A_ABST
Patent Text Reader

Abstract

A user equipment (UE) is configured to identify a disaster condition applied to a first public land mobile network (PLMN); selecting a second PLMN for a disaster roaming service, where one or more tracking areas (TAs) of the second PLMN are locally stored in a barring list at the UE, and where the second PLMN and the first PLMN have a roaming agreement for a disaster roaming service; and registering a disaster roaming service in the one or more TAs of the second PLMN from the barring list with the second PLMN.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] User equipment (UE) can connect to a network that supports Minimization of Service Interruption (MINT). MINT provides a framework that enables UEs of a given public land mobile network (PLMN) to obtain disaster roaming services from another PLMN during a disaster situation. This provides UEs with an opportunity to mitigate service interruptions and failures in the event of a disaster. Summary of the invention

[0002] Some exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: selecting a first public land mobile network (PLMN) for a disaster roaming service; and initiating a disaster roaming wait timer, wherein when the disaster roaming wait timer is running, the UE does not initiate a normal registration with the first PLMN.

[0003] Other exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: identifying a disaster condition that applies to a first public land mobile network (PLMN); selecting a second PLMN for disaster roaming services, wherein one or more tracking areas (TAs) of the second PLMN are in a prohibited list stored locally at the UE, and wherein the second PLMN and the first PLMN have a roaming agreement for disaster roaming services; and registering the disaster roaming services in the one or more TAs of the second PLMN from the prohibited list with the second PLMN.

[0004] Other exemplary embodiments relate to a method performed by a user equipment (UE). The method includes: selecting a public land mobile network (PLMN) for registration in a disaster situation, wherein the selection is manually performed at the UE; initiating a registration process with the PLMN, wherein the PLMN is in a prohibited PLMN list; receiving a type of rejection reason for the registration process, wherein the registration process is for normal service; and autonomously initiating a registration process for a disaster roaming service based on the type of rejection reason. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0008] Figure 4Methods for accessing and recovering from disaster roaming services according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0009] The exemplary embodiments may be further understood with reference to the following description and the associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments relate to minimizing service interruption (MINT). As will be described in more detail below, the exemplary embodiments introduce enhancements to accessing and recovering from disaster roaming services.

[0010] The exemplary embodiments are described with reference to user equipment (UE). However, reference to UE is provided for illustration 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, UE described herein is used to represent any electronic component.

[0011] The exemplary embodiments are also described with reference to a fifth generation (5G) network that supports MINT. In general, MINT refers to a framework that enables a UE to obtain disaster roaming services from a public land mobile network (PLMN) during a disaster situation. For example, a PLMN may not be able to provide services in the event of a disaster (e.g., a natural disaster, fire, explosion, traffic accident, etc.), and MINT may enable a UE of a given PLMN to obtain connectivity services (e.g., voice calls, mobile data services, etc.) from another PLMN when the disaster situation applies. Therefore, the UE may have the opportunity to mitigate service interruptions and failures in the event of a disaster. Throughout this specification, a UE that is unable to obtain services from a PLMN that is normally served by the PLMN due to service failures during a disaster situation but is able to register with other PLMNs may be referred to as a "disaster inbound roamer."

[0012] A disaster condition may be initiated and terminated by a government or any other appropriate entity. A disaster condition may apply to a specific geographic area for a specific duration. Throughout this specification, a disaster condition may be characterized as applying to a UE, a specific geographic area, and / or a PLMN. In order to distinguish between different types of PLMNs, reference is made to a PLMN with a disaster condition and a PLMN without a disaster condition. The term "PLMN with a disaster condition" identifies a PLMN to which a disaster condition applies, and the term "PLMN without a disaster condition" identifies a PLMN that is not subject to a disaster condition. A PLMN without a disaster condition may provide disaster roaming services to a UE (e.g., a disaster inbound roamer) of the PLMN with a disaster condition. However, a PLMN without a disaster condition is not required to provide disaster roaming services.

[0013] As described above, when a disaster condition applies, the UE may have the opportunity to mitigate service interruptions and failures. As an example, the UE may not have coverage of its home PLMN (HPLMN) and obtain information that the disaster condition applies to the HPLMN. The UE may then register with another PLMN that provides disaster roaming services in the area where the disaster condition applies. When the disaster condition ends and no longer applies to the HPLMN, the currently occupied PLMN may stop providing disaster roaming services. The UE may then perform network reselection / re-registration to return to its HPLMN. This example is provided for illustrative purposes only. The exemplary embodiment does not require the HPLMN to be subject to a disaster condition and may be used with any appropriate type of PLMN with a disaster condition.

[0014] Disaster roaming generally refers to the Third Generation Partnership Project (3GPP) roaming policy applied during a disaster condition. MINT provides a framework to facilitate disaster roaming, which may include operations on the UE side and / or the network side that may not be allowed when a disaster condition does not exist. As an example, according to some aspects of disaster roaming, the UE attempts to access a PLMN in a prohibited PLMN list during a disaster condition. In this specification, MINT and its related terms (such as but not limited to "disaster condition", "disaster roaming", "PLMN with disaster condition", "PLMN without disaster condition" and "disaster inbound roamer") are used in the manner as they are defined in various 3GPP specifications and may be modified according to the exemplary embodiments described herein.

[0015] In one aspect, exemplary embodiments relate to accessing and maintaining disaster roaming services during disaster conditions. As will be described in more detail below, exemplary embodiments introduce the following enhancements: obtaining disaster roaming services on a prohibited tracking area (TA), handling MINTs that are not supported by lower-order radio access technologies (RATs), handling abnormal rejection reasons for disaster roaming, manual PLMN selection on a PLMN that provides disaster roaming services, handling back-off timers during disaster conditions, handling emergency sessions when disaster roaming is registered, and selecting a mobility substate when one of the disaster roaming or disaster recovery wait timers is running.

[0016] In another aspect, exemplary embodiments relate to recovery from disaster roaming services when a disaster situation ends. As will be described in more detail below, exemplary embodiments introduce enhancements for reducing the signaling load on an allowed PLMN when a UE returns from a disaster situation, enabling fast registration on an allowed PLMN when a UE returns from a PLMN providing disaster roaming services, and handling changes in broadcast information indicating relief of a disaster situation when UE 110 has an active session.

[0017] 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 purposes of illustration, only an example with a single UE 110 is provided.

[0018] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 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 (LTE) RAN, traditional cellular networks, wireless local area networks (WLAN), etc.), and UE 110 may also communicate with the network via a wired connection. With respect 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.

[0019] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0020] Those skilled in the art will appreciate that any relevant process may be performed for UE 110 to connect to 5G NR RAN 120. For example, as discussed 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 base station (e.g., gNB 120A).

[0021] 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 may refer to an interconnected set of components that manage the operation and traffic of a cellular network. It may include an evolved packet core (EPC) and / or a 5G core (5GC). The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 may generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 may 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 may 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.

[0022] 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.

[0023] Processor 205 may be configured to execute multiple engines of UE 110. For example, the engines may include MINT engine 235. The MINT engine may perform various operations related to MINT, such as, but not limited to, identifying a disaster condition and attempting to register for disaster roaming services with a PLMN.

[0024] The engine 235 described above is provided as an application (e.g., program) executed by the processor 205 for illustrative purposes only. The functions associated with the engine 235 may also be represented as independent combined components of the UE 110, or may be modular components coupled to the UE 110, for example, integrated circuits with or without firmware. For example, the integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing signals and other information. The engine may also be embodied as an application or an independent application. In addition, in some UEs, the functions described for the processor 205 are 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.

[0025] 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 multiple different frequencies or channels (e.g., a set of continuous frequencies).

[0026] Figure 3 An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent a gNB 120A or any other access node that a UE 110 may use to establish a connection and manage network operations.

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

[0028] Processor 305 may be configured to execute multiple engines of base station 300. For example, these engines may include MINT engine 330. MINT engine 330 may perform various operations related to MINT. These operations may include, but are not limited to: transmitting an indication of a disaster condition; performing registration for disaster roaming services to a UE; and transmitting an indication that the disaster condition has ended.

[0029] The engine 330 described above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functions associated with the engine 330 may also be represented as a separate combined component of the base station 300, or may be a modular component coupled to the base station 300, 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. In addition, in some base stations, the functions described for the processor 305 are 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 the base station.

[0030] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the network arrangement 100. 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., a radio component) to enable data exchange with various networks and UEs.

[0031] Figure 4 A method 400 for accessing and recovering from a disaster roaming service is shown according to various exemplary embodiments. Figure 1 The network layout 100 and Figure 2 The method 400 is described with reference to the UE 110 of FIG.

[0032] The method 400 describes a scenario in which a UE 110 accesses a disaster roaming service during a disaster situation and recovers from the disaster roaming when the disaster situation ends. The method 400 is described from the perspective of the UE 110. However, the method 400 includes enhancements on the UE 110 side and the network side.

[0033] The example scenarios described below are provided to demonstrate how the various exemplary enhancements introduced herein can be used for MINT. However, the exemplary enhancements are not limited to this example. These exemplary enhancements can be used independently of each other, in conjunction with other currently implemented MINT mechanisms, in conjunction with future implementations of MINT mechanisms, or independently of other MINT mechanisms.

[0034] In 405, UE 110 receives an indication that a disaster condition applies to one or more PLMNs. As described above, a government or any other suitable entity may initiate a disaster condition. Once initiated, base stations of PLMNs with the disaster condition and / or base stations of PLMNs without the disaster condition may broadcast information indicating that the disaster condition applies to one or more PLMNs. The disaster condition may apply to the HPLMN of UE 110 or any other type of PLMN that UE 110 is allowed to access. The disaster condition information may be included in a system information block (SIB) or any other suitable type of message.

[0035] From the perspective of UE 110, the disaster condition information may indicate that a specific PLMN may not be able to provide services to UE 110 in the area where the disaster condition applies, and that a PLMN providing a disaster roaming service may be able to provide services to UE 110 in the area where the disaster condition applies. Then, UE 110 may search for the PLMN to receive the service. However, it is not necessary to receive the disaster condition information to trigger UE 110 to search for the PLMN providing the disaster roaming service.

[0036] In 410, UE 110 selects a PLMN that provides disaster roaming services. UE 110 may then attempt to register with the selected PLMN to receive services. For example, UE 110 may have no services or limited services. UE 110 may then be triggered to search for PLMNs. Therefore, UE 110 may tune its transceiver 225 to various frequencies to search for information broadcast by base stations of the PLMNs. UE 110 may receive an indication of a disaster condition during the search (e.g., 405), or may receive an indication of a disaster condition before the PLMN search. As will be described in more detail below, UE 110 may receive various different types of information from one or more PLMNs, which may be used to select a PLMN for pre-occupation. In this example, the selected PLMN provides disaster roaming services, however, UE 110 is not required to select a PLMN that provides disaster roaming services.

[0037] Before a disaster situation occurs, the network may provide information that may be used during disaster roaming to UE 110. For example, the HPLMN of UE 110 may provide an indication of whether disaster roaming is enabled in UE 110, the HPLMN and / or VPLMN may provide a PLMN list including zero or more PLMN IDs to be used in a disaster situation, the HPLMN and / or VPLMN may provide a disaster roaming waiting range consisting of a minimum waiting time and a maximum waiting time, and the HPLMN and / or VPLMN may provide a disaster recovery waiting range consisting of a minimum waiting time and a maximum waiting time. In addition, UE 110 may be pre-configured with some or all of the above reference information.

[0038] During the search for the PLMN selected in 410, UE 110 may also receive an indication from the PLMN indicating whether the disaster traveler is allowed to access the PLMN. The indication may be broadcast in a SIB or any other suitable type of message.

[0039] In some examples, when disaster conditions apply, UE 110 may select a PLMN stored in a prohibited PLMN list. Those skilled in the art will appreciate that the prohibited PLMN list is stored locally at UE 110 (e.g., SIM, memory arrangement 210, a combination thereof, etc.) and includes zero or more PLMN IDs. Typically, UE 110 does not attempt to register with a PLMN in the prohibited PLMN list. However, if disaster conditions apply, disaster roaming enables UE 110 to access a PLMN in the prohibited PLMN list.

[0040] In some areas, PLMNs may have localized roaming agreements. In this arrangement, instead of using a rejection cause indicating that the PLMN is not allowed (e.g., cause #11) to reject subscribers from other PLMNs, a more localized rejection cause indicating that the subscriber is not allowed in the TA may be utilized. For example, a rejection cause indicating that the TA is not allowed (e.g., cause #12), roaming is not allowed in the TA (e.g., cause #13), and there are no suitable cells in the TA (e.g., cause #15) may be used to reject the subscriber. If the UE 110 receives one of these types of rejection causes, the UE 110 may enter the corresponding TA into a forbidden TA list stored locally at the UE 110 (e.g., SIM, memory arrangement 210, a combination thereof, etc.) to avoid subsequent registration attempts on these TAs. UE 110 may have a single prohibited TA list for all TAs associated with a TA-related rejection cause (e.g., rejection cause #12, 13, 15, etc.), a different prohibited TA list for each rejection cause associated with a TA (e.g., rejection cause #12, 13, 15, etc.), or any other appropriate type of arrangement of one or more prohibited TA lists (e.g., "5GS prohibited tracking area for roaming", "prohibited tracking area for regional service provision", or any other prohibited list corresponding to a rejection cause associated with a TA). When a more localized rejection cause is utilized, the corresponding PLMN may not be stored in the prohibited PLMN list, but one or more TAs of the PLMN may be stored in the prohibited TA list. Under normal circumstances, when a disaster situation applies, even when the corresponding PLMN is providing disaster roaming services, UE 110 may not consider cells of PLMNs having TAs in the prohibited TA list when registering for disaster roaming services, because UE 110 may be configured to only consider the prohibited PLMN list when selecting a PLMN during a disaster situation.

[0041] The exemplary embodiments introduce enhancements that allow the UE 110 to consider the forbidden TA list when selecting a PLMN. In some embodiments, when no suitable cells are available for normal registration, the UE 110 can select an acceptable cell of a PLMN that is not in the forbidden PLMN list but has a TA in the forbidden TA list. Thus, when selecting a PLMN for disaster roaming service, the UE 110 can select a PLMN with a TA stored in the forbidden TA list. In addition, the UE 110 can ignore and / or delete the TA in the forbidden TA list and / or the forbidden TA for the roaming list associated with the PLMN on which the disaster roaming registration is being initiated.

[0042] In 415, UE 110 performs registration for disaster roaming services with the selected PLMN. For example, UE 110 may send a registration request message to the network indicating an initial registration for disaster roaming services. In another example, UE 110 may send a registration request message to the network indicating a mobility registration for disaster roaming services. Once successfully completed, UE 110 may be considered registered for disaster roaming services.

[0043] In this example, registration for disaster roaming services is successful. However, there may be scenarios where registration for disaster roaming services is unsuccessful. According to some aspects, exemplary embodiments introduce enhancements for handling abnormal rejection causes for disaster roaming. When UE 110 attempts to perform disaster registration on a PLMN and UE 110 receives a rejection cause that causes UE 110 to be triggered to add a PLMN or a TA of the PLMN to a prohibited list, UE 110 may attempt to determine whether the PLMN is providing disaster roaming services. For example, UE 110 may search for system information indicating a disaster condition. If, when attempting to register for disaster roaming services, UE 110 identifies one or more conditions indicating that the PLMN provides disaster roaming services after receiving the rejection cause from the PLMN, UE 110 may consider this to be an abnormal situation and handle the rejection cause as an abnormal rejection cause. Then, UE 110 may perform operations associated with receiving an abnormal rejection reason, such as, but not limited to, increasing a registration attempt counter, setting a 5GS update (5U) state to 5U2 not updated, moving to a related substate associated with the abnormal situation, and starting a timer T3511. Upon expiration of timer T3511, UE 110 may retry registration on the PLMN.

[0044] In another embodiment, UE 110 may block the cell after receiving a PLAIN rejection message with a rejection cause, which triggers UE 110 to add the TA and / or PLMN to one of the prohibited PLMN or TA lists. Those skilled in the art will appreciate that a PLAIN message may refer to a message received without security protection (e.g., non-integrity protection). Therefore, in order to handle the rejection cause when attempting to register for disaster roaming services, UE 110 may block the cell from being considered by UE 110 as a disaster roaming service. However, UE 110 may still consider other cells of the same TA or PLMN that can provide disaster roaming services. In another embodiment, in order to handle the rejection cause when attempting to register for disaster roaming services, UE 110 may add the PLMN and / or TA to the corresponding prohibited list, and may also mark the PLMN and / or TA as unavailable for disaster roaming services. UE 110 may then not select a PLMN and / or TA for a disaster roaming registration attempt until a predetermined event occurs. The predetermined event may include, but is not limited to, power off, SIM removal, end of disaster situation, periodically based on a list validity timer, or until UE 110 moves back to an allowed PLMN. After the predetermined event, UE 110 may remove from the forbidden list entries that have been marked as being added due to receiving a rejection message when attempting disaster roaming service.

[0045] As described above, a disaster roaming waiting range consisting of a minimum waiting time and a maximum waiting time may be provided to UE 110. In some examples, UE 110 may generate a random number within the disaster roaming waiting range and start a timer using the generated random number. While the timer is running, UE 110 may not initiate registration on the selected PLMN. When the timer expires, UE 110 may perform a registration procedure using a 5G system (5GS) registration type value set to disaster roaming registration. Doing so may alleviate congestion or tension on the PLMN that accepts disaster inbound roamers.

[0046] According to some aspects, exemplary embodiments introduce enhancements to manual PLMN selection on PLMNs that provide disaster roaming services. A user can manually initiate a search and select a PLMN to request access to services. When a PLMN is selected for manual registration and conditions associated with disaster registration are met, UE 110 can attempt disaster registration on the manually selected PLMN. This provides the network with the flexibility to evaluate UE 110 as both a normal inbound roamer and a disaster inbound roamer. If UE 110 attempting disaster roaming registration is allowed to access the services of the PLMN as a normal inbound roamer, the network can indicate to UE 110 that the network has accepted the registration as a normal registration rather than as a disaster registration. If UE 110 attempts to register normally on a manually selected PLMN and receives a registration rejection message with cause #11, 12, 14 or 15, and if the cell of the selected PLMN passes the criteria for disaster roaming registration attempts, UE 110 can autonomously attempt disaster registration on the selected PLMN without user intervention. Assuming that the PLMN is an allowed PLMN, there may also be a scenario where UE 110 attempts a normal registration. However, on the network side, UE 110 subscription information indicates that UE 110 does not have access to normal services on the selected PLMN, but has access to disaster roaming services on the selected PLMN during the disaster situation. In this type of scenario, the network can indicate in the registration acceptance that the registration of UE 110 has been accepted as not a normal registration but a disaster registration, and the network can additionally indicate the PLMN for which disaster roaming is being provided.

[0047] In addition, the exemplary embodiment introduces an enhancement for handling the T3346 timer during a disaster situation. When UE 110 registers or attempts to register for disaster roaming services and receives a rejection reason #22 for congestion, UE 110 can start a backoff timer T3346. The backoff timer limits the PLMN selection on the UE 110 side, and it can be expected that UE 110 will only camp on the same PLMN and move to a different PLMN based on reselection or loss of coverage. However, this behavior may be detrimental to disaster roaming. The exemplary embodiment introduces an enhancement in which if T3346 is running when UE 110 registers or attempts to register for disaster roaming, and if later UE 110 determines that disaster roaming is no longer applicable based on changes in broadcast information in 5G NG RAN, UE 110 can stop T3346 and take actions related to mitigating disaster roaming by attempting to search for and select a PLMN that was previously in a disaster situation. Additionally, while T3346 is running, UE 110 may choose to periodically attempt to search for the availability of allowed PLMNs without a disaster condition, and may choose to attempt to register on a PLMN found during the search.

[0048] The exemplary embodiment introduces enhancements for handling emergency services when disaster roaming is registered. When UE 110 is registered for disaster roaming services, the availability of other RATs may be limited. However, in order to establish and / or maintain an emergency protocol data unit (PDU) session, UE 110 may need to be able to access other RATs to provide continuity of the emergency session. The exemplary embodiment introduces enhancements so that when disaster roaming services are registered, if an emergency PDU session is established, the lower layers such as the access layer components in UE 110 can be notified that reselection to all RATs in the selected PLMN is allowed. In the case where the upper layers of UE 110 indicate that the reselection restrictions have been cleared, the notification to the lower layers of UE 110 can be explicit, or can be implicitly derived by the access layer based on existing indications of emergency session activity. In addition, to ensure that UE 110 obtains access to normal services on 5GS, UE 110 may preferentially stay on a 5GS cell that supports disaster roaming and reselect to the 5GS cell. When no such cells are available, UE 110 may consider reselecting to EUTRAN (or any other RAT) over the selected PLMN.

[0049] At 420, UE 110 receives an indication that the disaster condition has ended. As described above, the government or any other appropriate entity may terminate the disaster condition. Upon termination, the base station of the PLMN providing disaster roaming services to UE 110 may indicate via the currently camped PLMN that the disaster condition no longer applies and that the disaster roaming services are no longer available. This indication may be provided via a deregistration, a SIB, a lack of system information indicating the disaster condition, or any other appropriate type of indication.

[0050] In 425, UE 110 selects a PLMN. UE 110 may select a PLMN that was previously in a disaster situation, however, UE 110 is not required to select the PLMN. In 430, UE 110 registers with the selected PLMN. For example, when the disaster situation has ended, UE 110 may initiate a registration process to receive network services. Thus, UE 110 may tune its transceiver to various frequencies to search for PLMNs. The selected PLMN may be the same PLMN that previously experienced the disaster situation, or any other suitable PLMN that UE 110 is allowed to access.

[0051] The exemplary embodiment introduces enhancements for handling changes in broadcast information indicating relief of a disaster situation when UE 110 has an active session. For example, a scenario may occur where UE 110 is in an active session when a disaster situation ends. Under normal circumstances, UE 110 may abruptly drop the ongoing session, which may result in a poor user experience.

[0052] In some embodiments, if UE 110 has an active session with a persistent bearer, and if a change in cell broadcast information is identified indicating that the disaster condition has ended, UE 110 may wait until the session is released and the persistent bearer is deactivated before returning to the PLMN that was previously in the disaster condition or any other allowed PLMN.

[0053] The duration for which a session with a persistent bearer is allowed to continue may be equal to the maximum value of the disaster recovery wait time. When UE 110 detects a change in disaster roaming conditions during an active non-emergency persistent bearer session, UE 110 may start a timer having a value equal to the maximum value of the disaster recovery wait range. If the session ends before the timer expires, UE 110 may initiate a PLMN search and attempt to camp on and register with the PLMN that was previously in the disaster situation. If the timer expires and the non-emergency persistent bearer session has not ended, UE 110 may terminate the ongoing session and attempt to search for and select the PLMN that was previously in the disaster situation. On the network side, the PLMN that provides disaster roaming may also allow the persistent bearer session to continue after the disaster situation is alleviated for the duration of the maximum value of the disaster recovery wait range.

[0054] After the disaster situation has ended, a large number of UEs can be expected to return to the PLMN that was previously in the disaster situation. This may cause the PLMN that was previously in the disaster situation to experience a high signaling load, which may have a negative impact on network performance. In one method, a disaster recovery waiting range consisting of a minimum waiting time and a maximum waiting time can be provided to UE 110. In some examples, UE 110 can generate a random number within the disaster recovery waiting range and start a timer using the generated random number. When the timer is running, UE 110 may not initiate registration on the selected PLMN. When the timer expires, UE 110 can perform a registration process to the selected PLMN. Therefore, UE can stagger registration signaling on the PLMN that was previously in the disaster situation. This can be to alleviate congestion or tension on the PLMN caused by UE returning to the PLMN after the disaster situation ends.

[0055] It has been identified that in the event that the UE 110 returns to a PLMN that was previously in a disaster situation, the UE 110 may initiate a mobility registration update procedure. However, it is unlikely that the PLMN will be able to retrieve the UE 110 context from the PLMN that previously provided disaster roaming services. The network may provide a rejection reason for the registration attempt. The UE 110 may then attempt to register with the PLMN via an initial registration with a subscription concealed identifier (SUCI). In other scenarios, the PLMN may initiate an identification procedure for the SUCI of the UE 110 and then proceed with the registration. Therefore, the use of the mobility registration update procedure has been identified as causing unnecessary signaling load when the UE returns from a disaster situation to an allowed PLMN.

[0056] The exemplary embodiment introduces a technique in which a UE 110 returning to a PLMN previously in a disaster situation, after registering for disaster roaming services with another PLMN, initiates an initial registration with a SUCI. Those skilled in the art will appreciate that a SUCI is a privacy-preserving identifier that includes a hidden subscription permanent identifier (SUPI). Thus, the SUCI may be generated based on the SUPI and a public key provided by the HPLMN. Utilizing an initial registration with the SUCI may reduce signaling load as it may allow avoidance of signaling that may be caused by a failed mobility registration update procedure as well as avoidance of signaling associated with an identification procedure for the SUCI.

[0057] There may be a scenario where the UE 110 moves from a PLLMN providing disaster roaming services to an allowed PLMN via a trigger on the UE 110 side. This is in contrast to a network that moves the UE away from the PLMN providing disaster roaming services when the disaster condition ends (e.g., triggering a deregistration, indicating that the disaster condition has ended, etc.). To provide some examples of UE 110 side triggers, the UE 110 may find an allowed PLMN during a PLMN search triggered as part of the expiration of a PLMN search timer, or when attempting service recovery after losing coverage of a PLMN providing disaster roaming services. When a trigger on the UE 110 side causes the UE 110 to return from a PLMN providing disaster roaming services to an allowed PLMN, no signaling overload is expected. Therefore, the UE 110 may skip utilizing the disaster recovery wait timer. Instead, the UE 110 may attempt normal registration of the allowed PLMN at any point after finding the PLMN during a PLMN search that may occur after the UE 110 side trigger condition occurs. However, the exemplary embodiments are not limited to the above example trigger conditions, if UE 110 returns from the PLMN providing disaster roaming service to the allowed PLMN, and if the return is not due to network-initiated deregistration, or if the return is not due to removal of broadcast information related to disaster roaming, then UE 110 will not start the disaster recovery waiting timer and can immediately attempt to register on the allowed PLMN. This can ensure that the service of UE 110 is restored faster in these types of scenarios.

[0058] The exemplary embodiment introduces enhancements related to which 5GMM sub-state to select when one of the disaster roaming or disaster recovery waiting timers is running. When either of these timers is running, it may not be expected that the UE 110 will attempt any registration on the selected PLMN. In this scenario, it would be beneficial for the UE 110 to select the correct 5GMM sub-state that reflects the correct UE 110 state and seamlessly allows / disallows activity on the UE 110 side. In one example, the UE 110 may select the sub-state "5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION" or "5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE" depending on whether the UE 110 is in the DEREGISTERED state or the REGISTERED state and whether either the disaster roaming waiting timer or the disaster recovery waiting timer is active. If there is a request from an upper layer to establish an emergency session or initiate an IMS Multimedia Telephony Service (MMTel), UE 110 may stop the disaster roaming wait timer or the disaster recovery wait timer and immediately attempt to register on the camped PLMN.

[0059] According to some aspects, the exemplary embodiments introduce enhancements for handling of MINT that is not supported by the lower RAT. MINT is supported in 5GS, but not in Evolved Packet System (EPS) / Evolved UMTS Terrestrial Radio Access Network (EUTRAN) (e.g., LTE). MINT signaling between certain network nodes may provide EUTRAN as a restricted RAT to ensure that when disaster roaming is registered in 5GS, UE 110 is not redirected or switched to EUTRAN by the network. However, it is recognized that scenarios may occur in which a UE registered for a disaster condition attempts to reselect to EUTRAN of the same PLMN to receive specific services. The exemplary embodiments introduce enhancements to avoid these types of scenarios.

[0060] In some embodiments, a UE 110 registered or registered for disaster roaming services in 5GS can disable EUTRA capabilities and indicate the EUTRA capabilities to the network. This can ensure that when camped on a PLMN providing disaster roaming services, neither the network nor the UE 110 attempts to move from the 5G RAT to the LTE RAT. In another embodiment, a UE 110 attempting to register or having registered for disaster roaming services can treat EUTRAN as a RAT that is not available for normal services on the PLMN providing disaster roaming services. Therefore, when on a PLMN providing disaster roaming services, the UE 110 can ignore triggers that will cause the UE 110 to select EUTRAN. For example, when voice services are not available in 5G NR, the UE 110 can be triggered to select the EUTRAN of the registered PLMN. When on a PLMN providing disaster roaming services, the UE 110 can ignore the trigger and remain connected to the 5G NR RAN of the PLMN providing disaster roaming services. In another example, in a normal scenario, UE 110 may reach a maximum number of registration attempt failures due to connectivity issues. UE 110 may then disable 5G NR on the selected PLMN and attempt to find services on a different RAT of the same PLMN. According to some exemplary embodiments, if UE 110 reaches a maximum number of registration attempt failures on a 5G NR PLMN while attempting to register for disaster roaming services, UE 110 may ignore or omit operations related to searching for services on EUTRAN or any other RAT of the same PLMN.

[0061] In some embodiments, a UE 110 registered for disaster roaming services may indicate to lower layers, such as an NR radio power control (NRRRC) component, that EUTRAN is a restricted RAT and that the UE 110 is not expected to reselect to that RAT when registered for disaster roaming services.

[0062] In other embodiments, a UE 110 registered for disaster roaming may indicate to lower layers that the current registration is for disaster roaming and the lower layers may reselect to cells of the current PLMN (or equivalent PLMN (EPLMN)) only if they also broadcast indications related to disaster roaming and if the same PLMN that the UE 110 already considers to be in a disaster situation is part of the broadcast information or if the UE 110 can implicitly infer based on the broadcast information that the cell supports disaster inbound roaming for the PLMN that the UE 110 already considers to be in a disaster. For example, consider a scenario where PLMN-1 is in a disaster situation and PLMN-2 is providing disaster roaming services to subscribers of PLMN-1. UE 110 is subsequently accepted by PLMN-2 as a disaster inbound roamer of PLMN-2. UE 110 may then move to idle mode. In idle mode, UE 110 identifies multiple cells of PLMN-2. Some of the cells may broadcast indications related to disasters, while some of the cells do not broadcast indications related to disasters. This may be a means for the network to keep disaster inbound roamers only within certain cells. In this type of scenario, even if all of the multiple cells belong to PLMN-2, UE 110 may reselect to only a subset of the multiple cells that are part of PLMN-2 and broadcast disaster information.

[0063] Example

[0064] In a first embodiment, a processor of a user equipment (UE) is configured to perform operations including: identifying a disaster condition applying to a first public land mobile network (PLMN); selecting a second PLMN for disaster roaming services, wherein one or more tracking areas (TAs) of the second PLMN are in a prohibited list locally stored at the UE, and wherein the second PLMN and the first PLMN have a roaming agreement for disaster roaming services; and registering the disaster roaming services in the one or more TAs of the second PLMN from the prohibited list with the second PLMN.

[0065] In a second embodiment, the processor according to the first embodiment, wherein the forbidden list is one of a forbidden TA list, a forbidden TA list for roaming, or a forbidden TA list for regional offering service.

[0066] In a third embodiment, the processor according to the second embodiment, wherein the second PLMN is not in a forbidden PLMN list stored locally at the UE.

[0067] In a fourth embodiment, according to the processor of the first embodiment, the operations further include removing the one or more TAs of the second PLMN from the forbidden list in response to registering disaster roaming service with the second PLMN.

[0068] In a fifth embodiment, according to the processor of the first embodiment, the operation further comprises: receiving an indication that the second PLMN is providing disaster roaming service, wherein the UE is configured to, in response to the indication, regard the TA of the second PLMN that is part of the prohibited list as available for disaster roaming service.

[0069] In a sixth embodiment, a processor of a user equipment (UE) is configured to perform operations including: registering for disaster roaming services with a first public land mobile network (PLMN); identifying that the disaster condition no longer applies to a second PLMN; and in response to identifying that the disaster condition no longer applies to the second PLMN, initiating an initial registration process with the second PLMN using a subscription concealment identifier (SUCI).

[0070] In a seventh embodiment, a processor of a user equipment (UE) is configured to perform operations including: receiving a disaster recovery wait timer range including a minimum wait time and a maximum wait time; registering for disaster roaming services with a first public land mobile network (PLMN); selecting a second PLMN for normal registration; and registering with the second PLMN, wherein based on the type of triggering condition for initiating a search for the second PLMN, the UE does not use the disaster wait timer before registering with the second PLMN.

[0071] In an eighth embodiment, the processor according to the seventh embodiment, wherein the trigger condition to initiate the search for the second PLMN is one of expiration of a PLMN search timer or loss of coverage of the first PLMN providing disaster roaming service.

[0072] In a ninth embodiment, a processor of a user equipment (UE) is configured to perform operations including: registering for a disaster roaming service with a first public land mobile network (PLMN), wherein the disaster roaming service is provided by a fifth generation (5G) radio access technology (RAT) of the first PLMN connected to a fifth generation core (5GC); and determining that a long term evolution (LTE) RAT connected to an evolved packet core (EPC) is unavailable on the first PLMN providing the disaster roaming service.

[0073] In a tenth embodiment, according to the processor of the ninth embodiment, the operation further includes: disabling LTE capability at the UE when registering a disaster roaming service of a fifth generation system (5GS) with the first PLMN.

[0074] In an eleventh embodiment, according to the processor of the ninth embodiment, the operation also includes: receiving an indication that a trigger condition has occurred for the UE to select the LTE RAT connected to the EPC; and ignoring the trigger condition, wherein ignoring the trigger condition includes declaring a selection failure of the LTE RAT connected to the EPC.

[0075] In a twelfth embodiment, according to the processor of the ninth embodiment, the operation also includes indicating to a lower layer that the LTE RAT is a restricted RAT and that the UE does not reselect the LTE RAT when registering for a disaster roaming service of a fifth generation system (5GS).

[0076] In a thirteenth embodiment, a processor of a user equipment (UE) is configured to perform operations including: identifying a disaster condition applicable to a first public land mobile network (PLMN); transmitting a registration request for disaster roaming service to a second PLMN, wherein the second PLMN is an unallowed PLMN; and receiving a registration rejection reason from the second PLMN.

[0077] In a fourteenth embodiment, according to the processor of the thirteenth embodiment, the operation also includes: after receiving the rejection reason, determining that the second PLMN is providing disaster roaming service; initiating a timer in response to the rejection reason; and when the timer expires, attempting to re-register on the second PLMN.

[0078] In a fifteenth embodiment, the processor according to the fourteenth embodiment, wherein the timer is a T3511 timer.

[0079] In a sixteenth embodiment, according to the processor of the fourteenth embodiment, the operation also includes: increasing a registration attempt counter in response to the rejection cause; updating a fifth generation system (5GS) update (5U) status in response to the rejection cause; and updating a mobility sub-state of the UE in response to the rejection cause.

[0080] In a seventeenth embodiment, according to the processor of the thirteenth embodiment, the operation further comprises: adding the second PLMN or one of the tracking areas (TAs) of the second PLMN to a prohibited list; and prohibiting the cell that transmitted the registration rejection reason to the UE.

[0081] In an eighteenth embodiment, according to the processor of the thirteenth embodiment, the operation also includes: adding the second PLMN or one of the tracking areas (TAs) of the second PLMN to a prohibited list; and storing an indication that the second PLMN or one of the TAs of the second PLMN is not available for disaster roaming.

[0082] In a nineteenth embodiment, a processor of a user equipment (UE) is configured to perform operations including: selecting a public land mobile network (PLMN) for registration in a disaster situation, wherein the selection is manually performed at the UE; and initiating a registration process with the PLMN, wherein the PLMN is in a prohibited PLMN list.

[0083] In a twentieth embodiment, the processor of the nineteenth embodiment, wherein the registration process is for disaster roaming services.

[0084] In a twenty-first embodiment, according to the processor of the nineteenth embodiment, the operation also includes: receiving a type of rejection reason for the registration process, wherein the registration process is used for normal service; and autonomously initiating a registration process for a disaster roaming service based on the type of rejection reason.

[0085] In a twenty-second embodiment, the processor according to the twenty-first embodiment, wherein the type of reject reason is one of reject reason #11, reject reason #12, reject reason #13, or reject reason #15.

[0086] In a twenty-third embodiment, a processor of a user equipment (UE) is configured to perform operations including: initiating registration for disaster roaming services to a first public land mobile network (PLMN); receiving a rejection reason indicating congestion; initiating a backoff timer in response to the rejection reason; while the backoff timer is running, identifying that the disaster condition no longer applies to a second PLMN based on a change in broadcast information; and initiating registration with the second PLMN before the backoff timer expires.

[0087] In a twenty-fourth embodiment, the processor according to the twenty-third embodiment, wherein the backoff timer is a T3346 timer.

[0088] In a twenty-fifth embodiment, the processor of the twenty-third embodiment, wherein the UE is configured to periodically search for an allowable PLMN that is not in a disaster condition while the back-off timer is running.

[0089] In a twenty-sixth embodiment, a processor of a user equipment (UE) is configured to perform operations including: registering with a public land mobile network (PLMN) to obtain disaster roaming services; establishing an emergency protocol data unit session (PDU) session; and indicating to a lower layer of the UE that reselection to all radio access technologies (RATs) in the PLMN is allowed.

[0090] In a twenty-seventh embodiment, a processor of a user equipment (UE) is configured to perform operations including: identifying a disaster condition that applies to a first public land mobile network (PLMN); registering for disaster roaming services with a second PLMN; establishing a session with a persistent bearer via a cell of the second PLMN; and while the session with the persistent bearer is active, identifying that the disaster condition no longer applies to the first PLMN based on changes in broadcast information.

[0091] In a twenty-eighth embodiment, the processor according to the twenty-seventh embodiment, wherein the UE waits until the session is released and in response to identifying that the disaster situation no longer applies to the first PLMN, deactivates the persistent bearer to attempt to return to the first PLMN.

[0092] In a twenty-ninth embodiment, according to the processor of the twenty-seventh embodiment, the operation also includes initiating a timer in response to identifying that the disaster condition no longer applies to the first PLMN, wherein the timer is set to a value equal to a maximum recovery wait time, when the session ends before the expiration of the timer, the UE initiates registration with the first PLMN, and when the timer expires before the session is active, the UE terminates the session and initiates registration with the first PLMN.

[0093] In a thirtieth embodiment, a processor of a user equipment (UE) is configured to perform operations including: selecting a public land mobile network (PLMN) for disaster roaming service; initiating a disaster roaming waiting timer; and when the disaster roaming waiting timer is running and the UE is deregistered, selecting a fifth generation mobility management (5GMM) substate of 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION.

[0094] In a thirty-first embodiment, according to the processor of the thirtieth embodiment, the operation also includes: when the disaster roaming waiting timer is running, receiving a request to establish an emergency session or initiate an IMS multimedia telephone service (MMTel); and in response to the request, stopping the disaster roaming waiting timer and immediately attempting to register on the PLMN.

[0095] In a thirty-second embodiment, a processor of a user equipment (UE) is configured to perform operations including: selecting a public land mobile network (PLMN) for registration that was previously in a disaster state; initiating a disaster recovery waiting timer; and when the disaster recovery waiting timer is running and the UE is registered, selecting a fifth generation mobility management (5GMM) substate of 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE.

[0096] In a thirty-third embodiment, according to the processor of the thirty-second embodiment, the operation also includes: when the disaster recovery waiting timer is running, receiving a request to establish an emergency session or initiate an IMS multimedia telephone service (MMTel); and in response to the request, stopping the disaster recovery waiting timer and immediately attempting to register on the PLMN.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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 method performed by a user equipment UE, the method comprising: selecting a first public land mobile network PLMN for the disaster roaming service; as well as Initiate a disaster roaming waiting timer, wherein when the disaster roaming waiting timer is running, the UE does not initiate a normal registration with the first PLMN.

2. The method according to claim 1, further comprising: When the disaster roaming waiting timer is running, receiving a request to establish an emergency protocol data unit (PDU) session with the first PLMN; Initiating an emergency registration to the first PLMN when the disaster roaming waiting timer is running; as well as When the emergency registration to the first PLMN is successful, the emergency PDU session is established with the first PLMN.

3. The method of claim 2, wherein when the emergency registration is initiated, the disaster roaming wait timer is stopped.

4. The method of claim 2, wherein the disaster roaming wait timer continues to run when the emergency registration is initiated.

5. The method according to claim 2, further comprising: When the disaster roaming wait timer expires, a regular registration to the first PLMN is initiated.

6. The method according to claim 2, further comprising: When the disaster roaming waiting timer expires, wait to initiate a regular registration with the first PLMN until the emergency PDU session is released.

7. The method according to claim 1, further comprising: When the disaster roaming waiting timer is running and the UE is deregistered, the fifth generation mobility management 5GMM substate of 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION is selected.

8. The method according to claim 1, further comprising: Selecting a second PLMN for registration that was previously in a disaster situation; as well as A disaster recovery waiting timer is initiated, wherein when the disaster recovery waiting timer is running, the UE does not initiate normal registration with the second PLMN.

9. The method according to claim 8, further comprising: When the disaster recovery waiting timer is running, receiving a request to establish an emergency protocol data unit (PDU) session with the second PLMN; Initiating an emergency registration to the second PLMN when the disaster roaming waiting timer is running; as well as When the emergency registration with the second PLMN is successful, the emergency PDU session with the second PLMN is established.

10. The method of claim 9, wherein when the emergency registration is initiated, the disaster recovery wait timer is stopped.

11. The method of claim 9, wherein the disaster recovery wait timer continues to run when the emergency registration is initiated.

12. The method according to claim 9, further comprising: When the disaster recovery wait timer expires, a regular registration to the second PLMN is initiated.

13. The method according to claim 9, further comprising: When the disaster recovery waiting timer expires, wait to initiate a regular registration with the second PLMN until the emergency PDU session is released.

14. The method according to claim 8, further comprising: When the disaster recovery waiting timer is running and the UE is registered, the fifth generation mobility management 5GMM substate of 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE is selected.

15. A method performed by a user equipment UE, the method comprising: identifying a disaster condition applicable to a first public land mobile network PLMN; selecting a second PLMN for disaster roaming service, wherein one or more tracking areas TA of the second PLMN are locally stored in a forbidden list at the UE, and wherein the second PLMN and the first PLMN have a roaming agreement for disaster roaming service; as well as Register with the second PLMN for disaster roaming service in the one or more TAs of the second PLMN from the forbidden list.

16. The method of claim 15, wherein the forbidden list is one of a forbidden TA list, a forbidden TA list for roaming, or a forbidden TA list for regional service provision.

17. The method of claim 16, wherein the second PLMN is not in a forbidden PLMN list stored locally at the UE.

18. The method according to claim 15, the operation further comprising: In response to registering with the second PLMN for disaster roaming service, removing the one or more TAs of the second PLMN from the forbidden list.

19. The method of claim 15, further comprising: receiving an indication that the second PLMN is providing disaster roaming service, wherein the UE is configured to, in response to the indication, consider a TA of the second PLMN that is part of the forbidden list as available for disaster roaming service.

20. A method performed by a user equipment UE, the method comprising: selecting a public land mobile network PLMN for registration in a disaster situation, wherein the selecting is performed manually at the UE; Initiating a registration procedure with the PLMN, wherein the PLMN is in a forbidden PLMN list; receiving a type of rejection reason for the registration process, wherein the registration process is for a normal service; and A registration process for the disaster roaming service is autonomously initiated based on the type of rejection reason.

Citation Information

Cited By

  • Communication method and device, storage medium and equipment

    CN122179768A