METHOD AND SYSTEM TO DETERMINE WAIT TIME FOR DISASTER SERVICE REGISTRATION

Abstract

Embodiments herein disclose methods for handling operation of a UE during a disaster situation by the UE. The method includes initiating a wait timer upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service. Further, the method includes determining whether at least one of: a MS is registered via a non-3GPP access or 3GPP access to another allowable PLMN, the FPLMN has stopped broadcasting a disaster related indication, and the FPLMN has stopped broadcasting the PLMN with the disaster condition. Further, the method includes stopping the wait timer and performing a PLMN selection procedure based on the determination. The provided method optimizes the operations in disaster situations.

Claims

1. A method for handling operation of a user equipment (UE) during a disaster situation, the method comprising: initiating, by the UE, a wait timer upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service; determining, by the UE, a condition based on that at least one of: whether a mobile station (MS) is registered, via a non-3.sup.rd generation partnership project (3GPP) access or a 3GPP access, to an allowable PLMN, the FPLMN has stopped broadcasting a disaster related indication, or the FPLMN has stopped broadcasting the allowable PLMN with a disaster condition; and stopping, by the UE, the wait timer and performing a PLMN selection procedure based on the determined condition.

2. The method of claim 1, wherein the wait timer is a timer started with a generated random number within a disaster roaming wait range configured by a home public land mobile network (HPLMN).

3. A method for handling an operation of a user equipment (UE) during a disaster situation, the method comprising: detecting, by the UE, that an emergency service is initiated; and stopping, by the UE, a wait timer based on a detection that the emergency service is initiated, wherein the wait timer is initiated upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service.

4. The method of claim 3, wherein the wait timer is a timer started with a generated random number within a disaster roaming wait range configured by a home public land mobile network (HPLMN).

5. A user equipment (UE), the UE comprising: a processor; memory; and a controller coupled with the processor and the memory, the controller configured to: initiate a wait timer upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service, determine a condition based on that at least one of: whether a mobile station (MS) is registered, via a non-3.sup.rd generation partnership project (3GPP) access or a 3GPP access, to an allowable PLMN, the FPLMN has stopped broadcasting a disaster related indication, or the FPLMN has stopped broadcasting the allowable PLMN with a disaster condition, and stop the wait timer and perform a PLMN selection procedure based on the determined condition.

6. The UE of claim 5, wherein the wait timer is a timer started with a generated random number within a disaster roaming wait range configured by a home public land mobile network (HPLMN).

7. A user equipment (UE), the UE comprising: a processor; memory; and a controller coupled with the processor and the memory, the controller configured to: detect that an emergency service is initiated, and stop a wait timer based on a detection that the emergency service is initiated, wherein the wait timer is initiated upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service.

8. The UE of claim 7, wherein the wait timer is a timer started with a generated random number within a disaster roaming wait range configured by a home public land mobile network (HPLMN).

Description

BRIEF DESCRIPTION OF FIGURES

[0021] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0022] FIG. 1 illustrates a scenario of handling operation of a UE during a disaster situation according to prior arts;

[0023] FIG. 2 illustrates a scenario, wherein the time taken for a UE to select the PLMN is random according to embodiments as disclosed herein;

[0024] FIG. 3 illustrates various hardware components of the UE for handling operation of the UE during the disaster situation based on a wait timer according to embodiments as disclosed herein; and

[0025] FIG. 4 and FIG. 5 are flowcharts illustrating methods for handling operation of a UE during the disaster situation based on a wait timer according to embodiments as disclosed herein.

DETAILED DESCRIPTION

[0026] FIGS. 1 through 5, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0027] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0028] Embodiments herein use the terms “PLMN search” and “PLMN selection” interchangeably herein.

[0029] The embodiments herein achieve methods for handling operation of a UE during a disaster situation. The method includes initiating, by the UE, a wait timer upon selecting a forbidden public land mobile network (FPLMN) to receive a disaster roaming service. Further, the method includes determining, by the UE, that at least one of: a MS is registered via a non-3GPP access or a 3GPP access to another allowable PLMN, the FPLMN has stopped broadcasting a disaster related indication, and the FPLMN has stopped broadcasting the PLMN with the disaster condition. Further, the method includes stopping, by the UE, the wait timer and performing a PLMN selection procedure based on the determination.

[0030] The method can be used for determining the wait time for the UE to look for another PLMN (other than the PLMN to which the UE was registered) in the area (where the UE is located) and attempt to register on the PLMN to obtain service, on the disaster condition occurring. The provided method optimizes the operations in disaster situations without signalling overload.

[0031] Referring now to the drawings, and more particularly to FIG. 2 to FIG. 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0032] FIG. 2 illustrates a scenario (S200), wherein the time taken for a UE to select the PLMN is random according to embodiments as disclosed herein.

[0033] In an embodiment, the methods and systems can be used for enabling PLMN A to determine a disaster PLMN for a UE (assuming PLMN A is providing disaster inbound roaming services for multiple disaster PLMN's), when the UE identifies that a disaster situation has occurred, or disaster condition applies for a PLMN (PLMN D1) and the UE initiates registration on a PLMN A for disaster roaming services.

[0034] When the UE identifies that a disaster situation has occurred or disaster condition applies for a PLMN (PLMN D1), and the list of PLMNs to be used while in a disaster condition includes PLMN A, then the UE can register on PLMN A and get disaster roaming services on the PLMN A. If the PLMN A is providing disaster roaming services for multiple PLMN (PLMN D1, D2, D3), then it may be necessary for the AMF to know which is the disaster PLMN corresponding to the UE in order to apply differential disaster roaming services for different UE's.

[0035] The UE determines whether the disaster situation has been revoked or removed based on one or more of the following example triggers (this should be just taken as an example events):

[0036] a) Broadcast bit of serving PLMN-A (the cell of PLMN-A on which the UE is currently camping) does not indicate support for disaster inbound roaming services, or does not indicate support for disaster inbound roaming services for the selected PLMN-D—or—PLMN-A has stopped broadcasting PLMN-D;

[0037] b) The UE finds a non-3GPP access signal or the 3GPP access signal. The UE is able get into connected mode over a PLMN. Optionally, this PLMN is not part of forbidden PLMN list or the PLMN is a HPLMN or the PLMN is an EHPLMN. Optionally, this step is true if the registration procedure is successful over a non-3GPP access or 3GPP access. Optionally, this step is true if the UE is able to find the PLMN over the non-3GPP access of the current serving country (determined over 3GPP access) or when the UE gets into connected mode over non-3GPP access;

[0038] c) if none of the PLMNs configured in the UE are known to provide disaster inbound roaming service are available in a given area; and

[0039] d) If the UE finds the PLMN which is available, allowable and not part of forbidden PLMN list stored in the UE. This PLMN can be available either on 3GPP access or non-3GPP access.

[0040] “Priority order based on 23.122” is defined as below (as in 4.4.3.1.1 Automatic Network Selection Mode Procedure).

[0041] The UE/MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in the following order:

[0042] 1) RPLMN:

[0043] i) Either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present),

[0044] ii) Each PLMN/access technology combination in the “user controlled PLMN selector with access technology” data file in the SIM (in priority order) (UPLMN list),

[0045] iii) Each PLMN/access technology combination in the “operator controlled PLMN selector with access technology” data file in the SIM (in priority order) or stored in the ME (in priority order) (OPLMN list),

[0046] iv) Other PLMN/access technology combinations with received high quality signal in random order. Please note that high quality signal is defined in the appropriate AS specification,

[0047] v) Other PLMN/access technology combinations in order of decreasing signal quality, and

[0048] VI) FPLMN list PLMNs.

[0049] Priority order based on 23.122 except RPLMN is defined as below.

[0050] a) Follow the same order “priority order based on 23.122,” but skip RPLMN.

[0051] The network can optionally put restrictions on the time when the UE can initiate the registration procedure upon arriving in the PLMN without a disaster condition; The timer is hereafter called as wait time. The UE starts this timer when the UE is notified about disaster condition; i.e., the UE determines that disaster condition has occurred or the UE can start the moment that the UE gets into limited service or after camping (or selecting) on the PLMN-A. When the timer is running if the UE determines the disaster situation has been revoked (the conditions how the UE determines is discussed in this embodiment) the UE may stop the wait timer. The UE may not attempt and register on the PLMN providing disaster inbound roaming service (e.g., PLMN-A). The UE may perform PLMN selection procedure based on any of the priority mechanisms defined in this embodiment, if non-forbidden PLMN is available the UE may register on the same otherwise the UE may remain camped on limited service state.

[0052] In yet another embodiment, while the wait timer is running, the UE may not do the PLMN search and select another PLMN on the 3GPP access.

[0053] When the UE moves to a no service/limited service state, the UE may immediately start the random timer along with the PLMN search irrespective of whether the PLMN search is due to disaster situation or not. The UE may not wait until the UE determines that a disaster condition has happened in order to start the random timer. When the UE loses service or enters limited service, then the UE can start the random timer (as depicted in FIG. 2).

[0054] There can be 3 cases arising and the handling of UE is mentioned in detail for the 3 cases as below:

[0055] b) Case 1: If the random timer expires before the PLMN search is completed, the UE may restart the random timer again;

[0056] c) Case 2: The PLMN search has been completed and RPLMN/preferred PLMN's are not found and the random timer is still running, the UE may not trigger a normal PLMN search again for the normal service, when the random timer is running and the available PLMN list shows that there are no RPLMN/preferred PLMN's in the same region. The UE may wait for the random timer to expire, upon which the UE may trigger the registration on any PLMN which is providing disaster roaming services and is in the UE's forbidden PLMN list; and [0057] d) Case 3: The PLMN search has been completed and RPLMN/Preferred PLMN's are found and the random timer is still running, the random timer is aborted or stopped, as the PLMN search is not due to a disaster situation and the UE can try to immediately acquire service on RPLMN/preferred PLMN's.

[0058] The network can optionally put restrictions on the time when the UE can initiate the registration procedure upon arriving in the PLMN without a disaster condition (also called as PLMN-A). This is also referred to as random timer or wait timer herein.

[0059] The network can optionally put restrictions on the time when the UE can initiate the registration procedure upon arriving back into the PLMN with a disaster condition (also called as PLMN-D). This is also referred to as random timer or wait timer herein.

[0060] While this random timer/wait timer is running, if the UE determines that there is a PLMN which can provide normal service to the UE over the 3GPP access or non-3GPP access, then the UE may stop this timer and attempt to register on the respective PLMN which is providing normal service to the UE.

[0061] When the wait timer expires, the UE may first determine if the UE still needs to use the disaster inbound roaming service; i.e., the UE is not yet registered over non-3GPP access or 3GPP access or the UE is not able to find the non-3GPP access service. The UE is not able to find any PLMN which can provide normal service to the UE; i.e., only forbidden PLMNs are available in the area and one or more of those forbidden PLMNs indicate that the forbidden PLMNs support for disaster inbound roaming service in the broadcast information. Then, the UE may trigger registration for disaster inbound roaming service.

[0062] While the wait timer is running, if the UE determines that the disaster situation has been revoked or removed as discussed in this embodiment, the UE may stop the wait timer. The UE may not initiate registration for disaster inbound roaming service. The UE may perform PLMN selection to acquire normal service as discussed in this embodiment.

[0063] While the wait timer is running, if the UE searches for the PLMN and finds the higher priority PLMN-A, but for the same selected PLMN-D:

[0064] e) The wait timer is stopped and execute the wait timer expiry actions;

[0065] f) The existing wait timer continues to run;

[0066] g) The wait timer is stopped and restarted with an initial value;

[0067] h) If the new wait timer (T2) of PLMN-A is greater than the running wait timer (T1), then the UE can set the new wait timer value to T2−T1; and

[0068] i) If the new wait timer (T2) of PLMN-A is less than the running wait timer (T1), then the UE can set the new wait timer value zero; i.e., the UE can stop the wait timer and execute the wait timer expiry actions.

[0069] While the wait timer is running, if the UE searches for the PLMN and finds the higher priority PLMN-A, but for the different PLMN-D:

[0070] j) The wait timer is stopped and execute the wait timer expiry actions;

[0071] k) The existing wait timer continues to run;

[0072] l) The wait timer is stopped and restarted with an initial value;

[0073] m) If the new wait timer (T2) of PLMN-D is greater than the running wait timer (T1), then the UE can set the new wait timer value to T2−T1; and

[0074] n) If the new wait timer (T2) of PLMN-D is less than the running wait timer (T1), then the UE can set the new wait timer value zero; i.e., the UE can stop the wait timer and execute the wait timer expiry actions.

[0075] While the wait timer is running, the UE may not be allowed to perform the PLMN search or the PLMN selection procedure. Optionally, to avoid this, the wait timer value may be less that current set timer values of background search timer for e.g., the higher priority PLMN search timer value is 2 minutes.

[0076] When the wait timer is running, the UE may stop the timer and initiate registration procedure (for example emergency registration) if emergency call or emergency PDU session establishment is pending or higher priority service is pending.

[0077] In an embodiment, “a UE may not start the wait timer” can be interpreted to set the value of the wait timer to zero seconds. The wait timer value may be set to zero seconds, irrespective of the value signalled by network or pre-configured in the UE for one or more of following situations:

[0078] a) If the emergency call was ongoing or emergency call (emergency PDU session) is established;

[0079] b) If the UE is registered on non-3GPP access and losses the service, i.e., the UE goes to IDLE mode over non-3GPP access this can make the UE to search for service over 3GPP access, the UE may determine that disaster condition has occurred. In this case, the UE may not start the wait timer, because the attempt is already randomized; i.e., when disaster occurs, the UE has not made an attempt to register on PLMN-A at the same time along with other UEs and this attempt on PLMN-A is already randomized;

[0080] c) If the UE is already registered on PLMN-A, e.g., PLMN-A1 and the UE selects some other PLMN-A, for e.g., PLMN-A2 for e.g., due to higher priority PLMN-A2 or higher priority PLMN-D is available or PLMN-A1 cell is not available; and

[0081] d) If the UE is already registered on PLMN-A for e.g., due to emergency services and now, the UE again initiates initial registration procedure for normal service or the UE executes, the UE initiated deregistration procedure or network initiated de registration procedure followed by the initial registration procedure.

[0082] If the UE is registered over non-3GPP access and is in connected mode and the UE determines that a disaster condition has occurred on 3GPP access, the UE may start the wait timer. The UE may optionally select and camp on PLMN-A. If on non-3GPP access and the UE goes to IDLE mode, the UE does not find any allowable PLMNs on 3GPP access; i.e., the UE finds only PLMNs, which are available in a Forbidden PLMN (FPLMN) list, then the UE may attempt registration on selected PLMN-A after the running wait timer expires. If the wait timer had already expired, the UE can initiate the registration for disaster inbound roaming service on PLMN-A immediately.

[0083] FIG. 3 illustrates various hardware components of the UE (100) for handling operation of the UE (100) during the disaster situation based on the wait timer, according to embodiments as disclosed herein. The UE (100) can be, for example, but not limited to a laptop, a desktop computer, a notebook, a device-to-device (D2D) device, a vehicle to everything (V2X) device, a smartphone, a foldable phone, a smart TV, a tablet, an immersive device, and an internet of things (IoT) device.

[0084] In an embodiment, the UE (100) includes a processor (110), a communicator (120), a memory (130), and a controller (140). The processor (110) is coupled with the communicator (120), the memory (130), and the disaster condition handling controller (140). In an embodiment, the controller (140) initiates the wait timer upon selecting the FPLMN (300) to receive the disaster roaming service. Further, the controller (140) determines that at least one of: the MS is registered via a non-3GPP access or a 3GPP access to another allowable PLMN, the FPLMN (300) has stopped broadcasting the disaster related indication, and the FPLMN (300) has stopped broadcasting the PLMN with the disaster condition. Based on the determination, the controller (140) stops the wait timer and performs the PLMN selection procedure

[0085] In another embodiment, the controller (140) detects that an emergency service is initiated and stop the wait timer based on the detection. The wait timer is initiated upon selecting the FPLMN (300) to receive disaster roaming service.

[0086] The controller (140) is physically implemented by analog or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by firmware.

[0087] Further, the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes. The communicator (120) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (130) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” may not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache).

[0088] Further, at least one of the pluralities of modules/controller may be implemented through the AI model using a data driven controller (not shown). The data driven controller can be a ML model based controller and AI model based controller. A function associated with the AI model may be performed through the non-volatile memory, the volatile memory, and the processor (110). The processor (110) may include one or a plurality of processors. At this time, one or a plurality of processors may be a general purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).

[0089] The one or a plurality of processors control the processing of the input data in accordance with a predefined operating rule or AI model stored in the non-volatile memory and the volatile memory. The predefined operating rule or artificial intelligence model is provided through training or learning.

[0090] Here, being provided through learning means that a predefined operating rule or AI model of a desired characteristic is made by applying a learning algorithm to a plurality of learning data. The learning may be performed in a device itself in which AI according to an embodiment is performed, and/o may be implemented through a separate server/system.

[0091] The AI model may comprise of a plurality of neural network layers. Each layer has a plurality of weight values, and performs a layer operation through calculation of a previous layer and an operation of a plurality of weights. Examples of neural networks include, but are not limited to, convolutional neural network (CNN), deep neural network (DNN), recurrent neural network (RNN), restricted Boltzmann Machine (RBM), deep belief network (DBN), bidirectional recurrent deep neural network (BRDNN), generative adversarial networks (GAN), and deep Q-networks.

[0092] The learning algorithm is a method for training a predetermined target device (for example, a robot) using a plurality of learning data to cause, allow, or control the target device to make a determination or prediction. Examples of learning algorithms include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.

[0093] Although FIG. 3 illustrates various hardware components of the UE (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the electronic device UE (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the present disclosure. One or more components can be combined together to perform same or substantially similar function in the UE (100).

[0094] FIG. 4 and FIG. 5 are flow charts (400 and 500) illustrating methods for handling operation of the UE (100) during the disaster situation based on the wait timer according to embodiments as disclosed herein.

[0095] As shown in the FIG. 4, the operations (402-406) are performed by the controller (140). At 402, the method includes initiating the wait timer upon selecting the FPLMN (300) to receive the disaster roaming service. At 404, the method includes determining that at least one of: the MS is registered via the non-3GPP access or the 3GPP access to another allowable PLMN, the FPLMN (300) has stopped broadcasting the disaster related indication, and the FPLMN (300) has stopped broadcasting the PLMN with the disaster condition. At 406, the method includes stopping the wait timer and performing the PLMN selection procedure based on the determination.

[0096] As shown in the FIG. 5, the operations (502 and 504) are performed by the controller (140). At 502, the method includes detecting that the emergency service is initiated. At 504, the method includes stopping the wait timer based on the detection. The wait timer is initiated upon selecting a FPLMN (300) to receive disaster roaming service.

[0097] The provided method is implemented in a wireless communication network (e.g., 4G network, 5G network, 6G network, an open radio access network (ORAN) network or the like). The provided method optimizes the operations in disaster situations.

[0098] The various actions, acts, blocks, steps, or the like in the flow charts (400 and 500) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the present disclosure.

[0099] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.

[0100] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

[0101] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.