Methods and systems for manual mode search following a disaster condition

Abstract

ABSTRACT Methods and systems for Manual Mode Search following a Disaster Condition Embodiments herein disclose methods and systems for providing services efficiently in a wireless communication network, following a disaster condition. A method disclosed herein involves determining by a UE when there is a disaster condition. During Manual PLMN selection, the user or the upper layers shall select a PLMN that is offering disaster roaming services, and may also select the registration type on the selected PLMN. The UE shall trigger selection for the selected PLMN and perform a registration procedure on the selected PLMN using the selected registration type. FIG. 3

Description

TECHNICAL FIELD

[001] Embodiments disclosed herein relate to wireless communicationnetworks, and more particularly to managing services in a wireless communicationnetwork, following a disaster condition.BACKGROUND

[002] There are requirements that can help in avoiding service interruptionsthat may arise when a disaster condition (for example, a fire or an earthquake),occurs on a given Public Land Mobile Network (PLMN), and for which the UserEquipment (UEs) may be redirected to another PLMN in a manner that keeps theservice interruption to a minimum. A mobile network may fail to provide service inthe event of a disaster. These requirements can provide the fifth generation system(5GS) with the capability to mitigate the interruption of service. The UEs mayobtain service in the event of a disaster, if there are PLMN operators prepared tooffer service to the UEs. The minimization of service interruption may beconstrained to a particular time and place.

[003] The PLMN that is impacted by a disaster condition is also referred toas "PLMN D" herein. The PLMN that is not affected by the disaster condition andis providing disaster roaming service on behalf of PLMN D is also referred to asavailable PLMN or "PLMN A" herein.

[004] When a disaster happens, the network may become unresponsive, dueto which the user can go for manual PLMN selection or Manual Network SelectionMode Procedure. When the disaster condition is detected for the PLMN D, the usermay be denied service, so the user may trigger a manual PLMN selection or ManualNetwork Selection Mode Procedure.

[005] The terms "Manual PLMN Selection" and "Manual NetworkSelection Mode Procedure" have been used interchangeably to refer to a manualselection of a PLMN.

[006] There can be several PLMNs present in the area the UE is located in,so when these PLMNs are presented to the user, they may be categorized in mannerssuch as "preferred PLMN," "forbidden PLMN" etc. The UE may provide anindication to the user or the upper layers on the type (category) of PLMNs and theupper layers can act on how they can be presented to the user.

[007] The PLMNs that support disaster roaming services may only consistof forbidden PLMNs, and if there are only forbidden PLMNs in the area, all thePLMNs will be displayed as forbidden PLMNs to the user which can be misleadingand thereby prevent the user from selecting any of those forbidden PLMNs to obtaindisaster roaming services.

[008] Once all the PLMN(s) are listed to the user, the user can select anyPLMN from the list and trigger registration on the selected PLMN.

[009] However, as illustrated in FIG. 1, it is not clear whether upon selectinga PLMN, by the user or the upper layers, which may be a forbidden PLMN thatmay or may not support Disaster Roaming, if the UE will trigger normal registrationor registration for disaster inbound roaming services for the selected PLMN.Moreover, there is no option provided to the user if he wants to trigger normalregistration or registration for disaster inbound roaming services. The user mayneed the flexibility for selecting either type of registration as there may be differentcharges and services based on the type of registration that may be performed.

[0010] When the UE is registered on PLMN A to receive disaster inboundroaming services on behalf of PLMN D, then during manual PLMN selection, if theUE determines that the disaster condition has ended on PLMN D (through anybroadcast information or any access stratum (AS) / non access stratum (NAS)Signalling message or via non-3GPP access), it is not clear how the UE shouldproceed after making such a determination.OBJECTS

[0011] The principal object of the embodiments herein is to disclosemethods and systems for connecting a UE to a PLMN during Manual PLMNselection.

[0012] Another object of the embodiments disclosed herein is to disclosemethods and systems for connecting a UE to a PLMN upon selection of theregistration type by the UE.SUMMARY

[0013] Accordingly, the embodiments herein provide methods and systemsfor providing services efficiently in a wireless communication network, followinga disaster condition. A first method disclosed herein involves determining by theUE that there is a disaster condition. The disaster condition can be present in asource PLMN. The method further involves displaying, by the UE, to the user orindicating, by the UE, to the upper layers, at least one of the following:a. a list of available PLMN(s) in an area that the UE is located in; andb. the registration types supported by the available PLMN(s).

[0014] The method further involves selecting, by the user or the upperlayers, at least one of the following:a. at least one PLMN from the available PLMN(s); andb. at least one registration type supported by the selected at least onePLMN.

[0015] The method further involves triggering, by the UE, to choose theselected at least one PLMN. The method further involves triggering, by the UE, toperform a registration procedure using the at least one registration type supportedby the at least one PLMN, upon selection of the at least one registration type by atleast one of: the user or the upper layers; and the UE. The registration typessupported by the selected at least one PLMN can include normal registration anddisaster roaming registration. The method further involves including, by the UE, ina registration request message a 5GS registration type value set to the registrationtype selected. If the registration types supported by the available PLMN(s) are notdisplayed to the user or the upper layers, or if the user or the upper layers do notselect the at least one registration type supported by the selected at least one PLMN,then the registration type selected by the UE may indicate normal registrationprocedure.

[0016] A system disclosed herein comprises of at least one source PLMN,at least one target PLMN, and at least one UE. The at least one source PLMN issusceptible to becoming inoperative due to a disaster condition on it. The at leastone target PLMN, which is chosen by the UE based on user or the upper layersselection, provides disaster roaming services. The at least one UE may beconfigured to perform at least one of the following:a. determine that there is a disaster condition on the at least one sourcePLMN;b. display to the user or indicate to the upper layers at least one of: alist of at least one available PLMN(s); and the registration typessupported by the available PLMN(s);c. choose the at least one target PLMN, wherein the at least one targetPLMN is among the available PLMN(s) and is selected by the useror the upper layers;d. choose at least one registration type that is supported by the at leastone target PLMN, upon a selection of the at least one registrationtype by at least one of: the user or the upper layers; and the UE;e. trigger a registration procedure using the selected at least oneregistration type; andf. include in a registration request message a 5GS registration typevalue to the selected registration type.

[0017] These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with the followingdescription and the accompanying drawings. It should be understood, however, thatthe following descriptions, while indicating at least one embodiment and numerousspecific details thereof, are given by way of illustration and not of limitation. Manychanges and modifications may be made within the scope of the embodimentsherein without departing from the spirit thereof, and the embodiments hereininclude all such modifications.BRIEF DESCRIPTION OF FIGURES

[0018] The embodiments disclosed herein are illustrated in theaccompanying drawings, throughout which like reference letters indicatecorresponding parts in the various figures. The embodiments herein will be betterunderstood from the following description with reference to the drawings, in which:

[0019] FIG. 1 depicts an example user interface (UI) for performing manualPLMN selection, according to prior arts;

[0020] FIG. 2 depicts an example user interface (UI) for performing manualselection of PLMN and registration type, according to embodiments as disclosedherein;

[0021] FIG. 3 depicts a method for connecting a UE to a PLMN duringManual PLMN selection, according to embodiments as disclosed herein; and

[0022] FIG. 4 depicts a system for facilitating manual selection of PLMNand registration type, according to embodiments as disclosed herein.DETAILED DESCRIPTION

[0023] The embodiments herein and the various features and advantageousdetails thereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings and detailed in thefollowing description. Descriptions of well-known components and processingtechniques are omitted so as to not unnecessarily obscure the embodiments herein.The examples used herein are intended merely to facilitate an understanding ofways in which the embodiments herein can be practiced and to further enable thoseof skill in the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

[0024] Embodiments herein disclose methods and systems for providingservices efficiently in a wireless communication network, following a disastercondition, wherein the UE shall trigger normal registration or registration fordisaster inbound roaming services (also referred to herein as "disaster roamingregistration") for the target PLMN that is selected by the user or the upper layersduring a Manual Network Selection Mode procedure.

[0025] When the user triggers a Manual PLMN Selection, the UE maycheck for all the available PLMN(s) in the area that the UE is located in. If the UEdoes not find any allowable PLMN(s) and finds only forbidden PLMN(s), the UEcan determine (for example, by any broadcast information), if any of the forbiddenPLMN(s) supports disaster inbound roaming services for the UE. The UE can sendan indication to the upper layers with the PLMN ID(s) for all such PLMN(s) thatsupport disaster inbound roaming services for the UE.

[0026] Optionally, the UE can additionally send an indication to the upperlayers with the PLMN ID(s) of the PLMN A that support disaster roaming serviceson behalf of PLMN D.

[0027] During Manual PLMN Selection, possibilities of informationprovided to the user or the upper layers from any of the NAS or AS layers are listedbelow:i) The user can be notified with a list of PLMN-As which support disaster inboundroaming;ii) The user can be notified with a list of PLMN-As which do not support disasterinbound roaming; i.e., they are only forbidden PLMNs and UE determines that theydo not support the disaster inbound roaming service for any of the PLMN-Ds oroptionally they do support disaster inbound roaming service, but the PLMN-D forwhich they are supporting disaster inbound roaming service is part of a forbiddenPLMN list in the UE;iii) The user can be notified with a list of PLMN-Ds, which are the PLMNsimpacted by the disaster condition; andiv) The user can be notified with a list including each PLMN-A that is providingdisaster roaming service on behalf of each PLMN-D.

[0028] In some embodiments, upon selection, by a user, of a PLMN offeringdisaster roaming services (PLMN-A) in the above list, the UE may also provide theuser with an option to select at least one registration type to be performed on theuser-selected PLMN (PLMN-A). Examples of the at least one registration type canbe normal registration or disaster roaming registration. Following the user selectionof the PLMN and the registration type, the UE may trigger the selection of the userselectedPLMN and perform a registration procedure using the user-selectedregistration type. In other embodiments, the upper layers may perform the selectionof the PLMN offering disaster roaming services and the registration type, in whichcase the UE triggers the selection of the PLMN selected by the upper layers andperforms a registration procedure on the selected PLMN using the registration typeselected by the upper layers.

[0029] In the embodiments where upon selection of PLMN A, the user isprovided with the option to select a registration type on the selected PLMN A, theUE will perform a registration procedure using the selected registration type.

[0030] If the registration type is disaster roaming registration, then the UEmay perform the registration procedure using disaster roaming registration. The UEmay also include in a registration request message a 5GS registration type value setto the disaster roaming registration, to indicate that disaster roaming registrationwas performed. Examples of types of disaster roaming registration include"Disaster Roaming Initial Registration" and "Disaster Roaming MobilityRegistration Update."

[0031] If the registration type is normal registration, then the UE mayperform a registration procedure using normal registration on the PLMN-A.Examples of normal registration can include initial registration, mobilityregistration updating, periodic registration updating, emergency registration, andstand-alone non-public network (SNPN) onboarding registration. The UE mayinclude in the registration request message the 5GS registration type value to thenormal registration to indicate that normal registration was performed.

[0032] In some embodiments, upon selection of the PLMN A by the user orthe upper layers, there may not be an option provided / displayed to the user orindicated to the upper layers to select the registration type on the selected PLMNA. Optionally, the user or the upper layers may not select any registration type whileselecting the PLMN A. When there is no option for selecting a registration type orif the user or the upper layers have not selected any registration type for the selectedPLMN A, the UE may select a registration type similar to normal registration andthe UE may perform a registration procedure using normal registration on thePLMN-A. Examples of normal registration can include initial registration, mobilityregistration updating, periodic registration updating, emergency registration, andstand-alone non-public network (SNPN) onboarding registration. The UE mayinclude in the registration request message the 5GS registration type value to thenormal registration to indicate that normal registration was performed.

[0033] In some embodiments, when the user is displayed or the upper layersare indicated the list of available PLMN by the UE, and if the user or the upperlayers select a PLMN that is not offering disaster roaming services, the UE maythen perform a normal registration on the selected PLMN.

[0034] In some embodiments, when the UE is registered on PLMN A fordisaster inbound roaming services for PLMN D in Manual PLMN Selection mode,the UE may trigger a Higher Priority PLMN search. Optionally, the UE may triggerthe Higher Priority PLMN search with a different or modified search timer, whereinthis search may include searching for the PLMN-D. In another embodiment, theHigher Priority PLMN search may not include searching for the PLMN-D for whichthe UE is registered on the PLMN-A for disaster roaming services.

[0035] During the Higher Priority PLMN search or through any broadcastinformation or through any Access Stratum (AS) / Non-Access Stratum (NAS)signaling or via non-3GPP access, if the UE determines that the disaster conditionon the PLMN-D is no longer applicable, due to which the UE was registered onPLMN-A, or if the UE determines that another PLMN is available to providenormal service to the UE, then the UE may perform at least one of the following:a. Indicate to the upper layers and / or the user that the disaster conditionon PLMN-D is no longer applicable, and may also indicate to theupper layers and / or user to trigger a Manual Network SelectionMode Procedure or Automatic PLMN selection or AutomaticNetwork Selection Mode Procedure again.b. Indicate the PLMN ID of the PLMN-D due to which the UE wasregistered on PLMN-A that was offering disaster roaming services,or the PLMN ID of any other available PLMN that is offering normalservice to the UE, as available or allowable for registration.

[0036] In another embodiment, the UE may trigger a PLMN search, and theUE shall check for all the available PLMNs in that area. The UE may send theupdated PLMN list for all the available PLMNs to the upper layers and / or the user.

[0037] In another embodiment, if the user had selected PLMN-D, but dueto the disaster condition on PLMN-D had selected PLMN-A which was providingdisaster roaming services on behalf of PLMN-D, the UE may select and register onthe PLMN-D once the disaster condition on the PLMN-D is no longer applicableeven though UE is in manual mode and the user had selected the PLMN-A.

[0038] Referring now to the drawings, and more particularly to FIGs. 2through 4, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown embodiments.

[0039] FIG. 2 depicts an example user interface (UI) for performing manualselection of PLMN and registration type, according to embodiments as disclosedherein. When the user decides to perform a Manual PLMN selection, a list ofavailable PLMNs may be displayed to the user. In FIG. 2, the user interface (UI)depicts the available PLMN as "Operator 1," "Operator 2," "Operator 3," "Operator4," and "Operator 5." The UI may also indicate which of the available PLMNsbelong to a forbidden PLMN list. The UI may also indicate to the user whatregistration type may be selected on any of the available PLMNs. While FIG. 2illustrates that the possible registration types include normal registration anddisaster roaming registration, it is to be construed as non-limiting as the availablePLMNs may allow selection for additional registration types.

[0040] FIG. 3 depicts a method 300 for connecting a UE to a PLMN duringManual PLMN selection, according to embodiments as disclosed herein.

[0041] At step 302, the UE may determine that there is a disaster condition.The disaster condition may be on a source PLMN, which may be the UE's HPLMNor a VPLMN or any allowable PLMN of the UE and not part of the ForbiddenPLMN list of the UE.

[0042] At step 304, the UE may display to the user or indicate to the upperlayers a list of the available PLMN(s) in an area that the UE is located in. The UEmay additionally display to the user or indicate to the upper layers, one or moreregistration types supported by the one or more available PLMNs.

[0043] At step 306, the user or the upper layers may select at least onePLMN among the available PLMN(s). The user or the upper layers may also selectat least one registration type that is supported by the selected at least one PLMN.

[0044] At step 308, the UE may be triggered to the choose the selected atleast one PLMN.

[0045] At step 310, the UE may be triggered to perform a registrationprocedure using the at least one registration type supported by the selected at leastone PLMN, upon selection of the at least one registration type by the user or theupper layers. In some embodiments, if the registration types are not indicated ordisplayed to the user or the upper layers or if the user or the upper layers do notselect the at least one registration type, the UE may select the at least oneregistration type. The UE-selected at least one registration type may indicate anormal registration procedure.

[0046] The various actions in method 300 may be performed in the orderpresented, in a different order or simultaneously. Further, in some embodiments,some actions listed in FIG. 3 may be omitted.

[0047] FIG. 4 depicts a system for facilitating manual selection of PLMNand registration type, according to embodiments as disclosed herein.

[0048] The system may comprise a UE comprising a memory and aprocessor. The memory may store one or more instructions that when executed bythe processor, result in the performance of the actions by the UE as previouslydescribed herein. The UE may display to the user (through the UE's UI) or the upperlayers a list of PLMNs that the UE may be configured with. This list may includethe source PLMN (an example of which is UE's HPLMN or a VPLMN) and thetarget PLMN. The target PLMN can be the PLMN selected by the user or the upperlayers, wherein the target PLMN may offer disaster roaming services to the UEwhen the source PLMN is impacted by a disaster condition. In other embodiments,the list of PLMNs may also include all the available PLMN(s) in an area that theUE is located in. The list of PLMNs may also include the PLMNs accepting disasterroaming services, not accepting disaster roaming services, and any forbiddenPLMNs. The UE may also display to the user (through the UE's UI) or the upperlayers the registration types supported by the list of the PLMNs (a few examples ofwhich are Normal Registration and Disaster Roaming Registration).

[0049] Through the UI of the UE, the user may be able to provide inputs tothe UE. One example of an input that can be provided to the UE can be selection ofa PLMN during Manual Network Selection Mode. Another example of an input canbe the selection of a registration type to be performed on the selected PLMN.

[0050] The embodiments disclosed herein may refer to "PLMN A" and"target PLMN" interchangeably to refer to the selected PLMN that supports disasterroaming services. The embodiments disclosed herein may refer to "PLMN D" and"source PLMN" interchangeably to refer to the PLMN that is impacted by thedisaster condition.

[0051] The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, by applyingcurrent knowledge, readily modify and / or adapt for various applications suchspecific embodiments without departing from the generic concept, and, therefore,such adaptations and modifications should and are intended to be comprehendedwithin the meaning and range of equivalents of the disclosed embodiments. It is tobe understood that the phraseology or terminology employed herein is for thepurpose of description and not of limitation. Therefore, while the embodimentsherein have been described in terms of at least one embodiment, those skilled in theart will recognize that the embodiments herein can be practiced with modificationwithin the spirit and scope of the embodiments as described herein.

Claims

1. A method for connecting a User Equipment (UE) to at least one Public Land Mobile Network (PLMN), comprising: determining, by the UE, that there is a disaster condition; displaying, by the UE, to a user, at least one of the following: a list of one or more available PLMNs in an area that the UE is located in; and one or more registration types supported by the one or more available PLMNs; selecting, by the user, at least one of the following: at least one PLMN among the one or more available PLMNs; and at least one registration type supported by the selected at least one PLMN; and triggering, by the UE, a registration procedure using the at least one registration type supported by the selected at least one PLMN.

2. The method of claim 1, wherein the one or more registration types include at least one of: normal registration; and disaster roaming registration.

3. The method of claim 1, wherein the list of one or more available PLMNs include at least one of the following: at least one PLMN that supports disaster roaming services; at least one PLMN that does not support disaster roaming services; at least one PLMN affected by the disaster; and at least one PLMN providing disaster roaming services for each PLMN affected by a disaster condition.

4. The method of claim 2, wherein the normal registration comprises including, by the UE, a fifth generation system (5GS) registration type value set to at least one of the following in a registration request message: initial registration; mobility registration updating; periodic registration updating; emergency registration; and stand-alone non-public network (SNPN) onboarding registration.

5. The method of claim 2, wherein the disaster roaming registration comprises including, by the UE, a 5GS registration type value set to at least one of the following in a registration request message: Disaster Roaming Initial Registration; and Disaster Roaming Mobility registration updating.

6. The method of claim 1, wherein the UE includes a 5GS registration type value set to at least one of the following in a registration request message: initial registration; mobility registration updating; periodic registration updating; emergency registration; and stand-alone non-public network (SNPN) onboarding registration, upon either of the following occurring: the one or more registration types supported by the one or more available PLMNs are not displayed to the user; or the user does not select the at least one registration type supported by the selected at least one PLMN.

7. A method for connecting a User Equipment (UE) to at least one Public Land Mobile Network (PLMN), comprising: determining, by the UE, that there is a disaster condition; indicating, by the UE, to one or more upper layers, at least one of the following: a list of one or more available PLMNs in an area that the UE is located in; and one or more registration types supported by the one or more available PLMNs; selecting, by the one or more upper layers, at least one of the following: at least one PLMN among the one or more available PLMNs; and at least one registration type supported by the selected at least one PLMN; and triggering, by the UE, a registration procedure using the at least one registration type supported by the selected at least one PLMN by the one or more upper layers.

8. The method of claim 7, wherein the UE includes a 5GS registration type value set to at least one of the following in a registration request message: initial registration; mobility registration updating; periodic registration updating; emergency registration; and stand-alone non-public network (SNPN) onboarding registration, upon either of the following occurring: the one or more registration types supported by the one or more available PLMNs are not indicated to the one or more upper layers; or the one or more upper layers do not select the at least one registration type supported by the selected at least one PLMN.

9. A system, comprising: at least one source Public Land Mobile Network (PLMN), wherein the at least one source PLMN is susceptible to becoming inoperative due to a disaster condition on it; at least one target PLMN, wherein the at least one target PLMN provides disaster roaming services; and at least one User Equipment (UE) that is configured to perform at least one of the following: determine that there is a disaster condition on the at least one source PLMN; display to a user or indicate to one or more upper layers at least one of the following: a list of at least one available PLMN; and one or more registration types supported by the at least one available PLMN; choose the at least one target PLMN, wherein the at least one target PLMN is among the at least one available PLMN and is selected by the user or the one or more upper layers; choose at least one registration type supported by the at least one target PLMN, upon a selection of the at least one registration type by at least one of the following; the user or the one or more upper layers; and the UE; trigger a registration procedure using the selected at least one registration type; and include in a registration request message a fifth generation system (5GS) registration type value set to the selected registration type.

10. The system of claim 9, wherein the selected at least one registration type includes at least one of the following: normal registration; and disaster roaming registration.

11. The system of claim 10, wherein the normal registration comprises including, by the UE, in the registration request message the 5GS registration type value set to at least one of the following: initial registration; mobility registration updating; periodic registration updating; emergency registration; and stand-alone non-public network (SNPN) onboarding registration.

12. The system of claim 10, wherein the disaster roaming registration comprises including, by the UE, in the registration request message the 5GS registration type value set to at least one of the following: Disaster Roaming Initial Registration; and Disaster Roaming Mobility registration updating.

13. The system of claim 9, wherein the UE includes the 5GS registration type value set to at least one of the following in the registration request message: initial registration; mobility registration updating; periodic registration updating; emergency registration; and stand-alone non-public network (SNPN) onboarding registration, upon either of the following occurring: the one or more registration types supported by the at least one available PLMN are not displayed to the user or indicated to the one or more upper layers; or the user or the one or more upper layers do not select the at least one registration type supported by the at least one target PLMN.