METHOD FOR CONTROLLING CONGESTION CAUSED BY DISASTER ROAMING USER, AND DEVICE SUPPORTING SAME

Information

  • Patent Application
  • 20230254733
  • Publication Number
    20230254733
  • Date Filed
    July 09, 2021
    2 years ago
  • Date Published
    August 10, 2023
    9 months ago
Abstract
Provided is a method for controlling congestion caused by a disaster roaming user and a device supporting same. When a disaster occurs in a first public land mobile network (PLMN) that provides a service in a specific area, a user equipment (UE) performs registration with a second PLMN that provides a service in the specific area, and receives a message from a network in the second PLMN. The message includes: (i) information indicating that the UE is subject to congestion control in the second PLMN on the basis of the application of a disaster condition in the first PLMN; and (ii) timer information related to the congestion control. The UE operates a timer on the basis of the timer information, and performs PLMN selection with respect to a PLMN other than the second PLMN while the timer is running.
Description
TECHNICAL FIELD

The present disclosure relates to a method for controlling a congestion situation caused by a disaster roaming user and an apparatus supporting the same.


BACKGROUND

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3GPP LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement.


Work has started in international telecommunication union (ITU) and 3GPP to develop requirements and specifications for new radio (NR) systems. 3GPP has to identify and develop the technology components needed for successfully standardizing the new RAT timely satisfying both the urgent market needs, and the more long-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. Further, the NR should be able to use any spectrum band ranging at least up to 100 GHz that may be made available for wireless communications even in a more distant future.


The NR targets a single technical framework addressing all usage scenarios, requirements and deployment scenarios including enhanced mobile broadband (eMBB), massive machine-type-communications (mMTC), ultra-reliable and low latency communications (URLLC), etc. The NR shall be inherently forward compatible.


Mobile communication service is becoming an indispensable service in daily life, and communication operators are making various attempts to prevent service interruption. For example, a communication operator may install multiple wired networks in a core network section (e.g., multiple wired networks between core network nodes), and even if a problem occurs in one wired network, communication services may be continuously provided using another wired network. Alternatively, a communication operator may install a plurality of core network nodes, such as AMF, so that even if a problem occurs in one core network node, other core network nodes perform backup to prevent communication services from being disconnected.


However, in the event of a disaster such as fire or earthquake, the above countermeasures may not be helpful. For example, in the event of a fire, all communication networks connected to the outside from one node of the wireless network may be lost. In addition, in a virtualized cloud environment, a plurality of core network nodes is likely to be installed in one data center located in the same region. Therefore, if a fire or an earthquake occurs in an area where a data center is located, there is a high possibility that functions of all core network nodes will be lost no matter how many core network nodes are installed.


SUMMARY

When a communication service is not possible through a network of a specific operator due to a disaster, a method of minimizing service interruption by temporarily roaming a subscriber of the operator to a network of another operator in the vicinity is being discussed. In this case, a congestion situation may occur because users temporarily flock to a disaster roaming operator accommodating subscribers from a disaster-occurring operator, and a solution to this problem may be required.


In an aspect, a method performed by a user equipment (UE) operating in a wireless communication system is provided. The method comprises, detecting that a disaster condition applies to a first Public Land Mobile Network (PLMN) providing services in a specific area, performing registration with a second PLMN providing services in the specific area, receiving a message from a network in the second PLMN. The message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control. The method comprises, operating a timer based on the timer information, and performing PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.


In another aspect, an apparatus for implementing the above method is provided.


The present disclosure can have various advantageous effects.


For example, in a 5G system, a disaster roaming PLMN providing roaming service due to a disaster can anticipate a congestion situation due to disaster inbound roamers.


For example, when congestion occurs in the disaster roaming PLMN due to disaster inbound roamers, congestion control can be performed to reduce an impact on a communication service of the disaster roaming PLMN.


For example, the disaster inbound roamers can be successfully moved to another disaster roaming PLMN, thereby enhancing the user experience.


Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.



FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.



FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.



FIG. 4 shows an example of UE to which implementations of the present disclosure is applied.



FIG. 5 shows an example of 5G system architecture to which implementations of the present disclosure is applied.



FIG. 6 shows a concept of MINT to which implementations of the present disclosure is applied.



FIG. 7 shows an example of a method performed by a UE to which implementations of the present disclosure is applied.



FIG. 8 shows an example of a method performed by a RAN node of a second PLMN to which implementations of the present disclosure is applied.





DETAILED DESCRIPTION

The following techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access (SC-FDMA) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be embodied through radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be embodied through radio technology such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be embodied through radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or evolved UTRA (E-UTRA). UTRA is a part of a universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G new radio (NR).


For convenience of description, implementations of the present disclosure are mainly described in regards to a 3GPP based wireless communication system. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP based wireless communication system, aspects of the present disclosure that are not limited to 3GPP based wireless communication system are applicable to other mobile communication systems.


For terms and technologies which are not specifically described among the terms of and technologies employed in the present disclosure, the wireless communication standard documents published before the present disclosure may be referenced.


In the present disclosure, “A or B” may mean “only A”, “only B”, or “both A and B”. In other words, “A or B” in the present disclosure may be interpreted as “A and/or B”. For example, “A, B or C” in the present disclosure may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”.


In the present disclosure, slash (/) or comma (,) may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B or C”.


In the present disclosure, “at least one of A and B” may mean “only A”, “only B” or “both A and B”. In addition, the expression “at least one of A or B” or “at least one of A and/or B” in the present disclosure may be interpreted as same as “at least one of A and B”.


In addition, in the present disclosure, “at least one of A, B and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. In addition, “at least one of A, B or C” or “at least one of A, B and/or C” may mean “at least one of A, B and C”.


Also, parentheses used in the present disclosure may mean “for example”. In detail, when it is shown as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, “control information” in the present disclosure is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of “control information”. In addition, even when shown as “control information (i.e., PDCCH)”, “PDCCH” may be proposed as an example of “control information”.


Technical features that are separately described in one drawing in the present disclosure may be implemented separately or simultaneously.


Although not limited thereto, various descriptions, functions, procedures, suggestions, methods and/or operational flowcharts of the present disclosure disclosed herein can be applied to various fields requiring wireless communication and/or connection (e.g., 5G) between devices.


Hereinafter, the present disclosure will be described in more detail with reference to drawings. The same reference numerals in the following drawings and/or descriptions may refer to the same and/or corresponding hardware blocks, software blocks, and/or functional blocks unless otherwise indicated.



FIG. 1 shows an example of a communication system to which implementations of the present disclosure is applied.


The 5G usage scenarios shown in FIG. 1 are only exemplary, and the technical features of the present disclosure can be applied to other 5G usage scenarios which are not shown in FIG. 1.


Three main requirement categories for 5G include (1) a category of enhanced mobile broadband (eMBB), (2) a category of massive machine type communication (mMTC), and (3) a category of ultra-reliable and low latency communications (URLLC).


Referring to FIG. 1, the communication system 1 includes wireless devices 100a to 100f, base stations (BSs) 200, and a network 300. Although FIG. 1 illustrates a 5G network as an example of the network of the communication system 1, the implementations of the present disclosure are not limited to the 5G system, and can be applied to the future communication system beyond the 5G system.


The BSs 200 and the network 300 may be implemented as wireless devices and a specific wireless device may operate as a BS/network node with respect to other wireless devices.


The wireless devices 100a to 100f represent devices performing communication using radio access technology (RAT) (e.g., 5G new RAT (NR)) or LTE) and may be referred to as communication/radio/5G devices. The wireless devices 100a to 100f may include, without being limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an AR/VR/Mixed Reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter.


In the present disclosure, the wireless devices 100a to 100f may be called user equipments (UEs). A UE may include, for example, a cellular phone, a smartphone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, an ultrabook, a vehicle, a vehicle having an autonomous traveling function, a connected car, an UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a FinTech device (or a financial device), a security device, a weather/environment device, a device related to a 5G service, or a device related to a fourth industrial revolution field.


The UAV may be, for example, an aircraft aviated by a wireless control signal without a human being onboard.


The VR device may include, for example, a device for implementing an object or a background of the virtual world. The AR device may include, for example, a device implemented by connecting an object or a background of the virtual world to an object or a background of the real world. The MR device may include, for example, a device implemented by merging an object or a background of the virtual world into an object or a background of the real world. The hologram device may include, for example, a device for implementing a stereoscopic image of 360 degrees by recording and reproducing stereoscopic information, using an interference phenomenon of light generated when two laser lights called holography meet.


The public safety device may include, for example, an image relay device or an image device that is wearable on the body of a user.


The MTC device and the IoT device may be, for example, devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include smartmeters, vending machines, thermometers, smartbulbs, door locks, or various sensors.


The medical device may be, for example, a device used for the purpose of diagnosing, treating, relieving, curing, or preventing disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, relieving, or correcting injury or impairment. For example, the medical device may be a device used for the purpose of inspecting, replacing, or modifying a structure or a function. For example, the medical device may be a device used for the purpose of adjusting pregnancy. For example, the medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for procedure.


The security device may be, for example, a device installed to prevent a danger that may arise and to maintain safety. For example, the security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.


The FinTech device may be, for example, a device capable of providing a financial service such as mobile payment. For example, the FinTech device may include a payment device or a point of sales (POS) system.


The weather/environment device may include, for example, a device for monitoring or predicting a weather/environment.


The wireless devices 100a to 100f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100a to 100f and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a beyond-5G network. Although the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs 200/network 300. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.


Wireless communication/connections 150a, 150b and 150c may be established between the wireless devices 100a to 100f and/or between wireless device 100a to 100f and BS 200 and/or between BSs 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. The wireless devices 100a to 100f and the BSs 200/the wireless devices 100a to 100f may transmit/receive radio signals to/from each other through the wireless communication/connections 150a, 150b and 150c. For example, the wireless communication/connections 150a, 150b and 150c may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/de-mapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.


AI refers to the field of studying artificial intelligence or the methodology that can create it, and machine learning refers to the field of defining various problems addressed in the field of AI and the field of methodology to solve them. Machine learning is also defined as an algorithm that increases the performance of a task through steady experience on a task.


Robot means a machine that automatically processes or operates a given task by its own ability. In particular, robots with the ability to recognize the environment and make self-determination to perform actions can be called intelligent robots. Robots can be classified as industrial, medical, home, military, etc., depending on the purpose or area of use. The robot can perform a variety of physical operations, such as moving the robot joints with actuators or motors. The movable robot also includes wheels, brakes, propellers, etc., on the drive, allowing it to drive on the ground or fly in the air.


Autonomous driving means a technology that drives on its own, and autonomous vehicles mean vehicles that drive without user's control or with minimal user's control. For example, autonomous driving may include maintaining lanes in motion, automatically adjusting speed such as adaptive cruise control, automatic driving along a set route, and automatically setting a route when a destination is set. The vehicle covers vehicles equipped with internal combustion engines, hybrid vehicles equipped with internal combustion engines and electric motors, and electric vehicles equipped with electric motors, and may include trains, motorcycles, etc., as well as cars. Autonomous vehicles can be seen as robots with autonomous driving functions.


Extended reality is collectively referred to as VR, AR, and MR. VR technology provides objects and backgrounds of real world only through computer graphic (CG) images. AR technology provides a virtual CG image on top of a real object image. MR technology is a CG technology that combines and combines virtual objects into the real world. MR technology is similar to AR technology in that they show real and virtual objects together. However, there is a difference in that in AR technology, virtual objects are used as complementary forms to real objects, while in MR technology, virtual objects and real objects are used as equal personalities.


NR supports multiples numerologies (and/or multiple subcarrier spacings (SCS)) to support various 5G services. For example, if SCS is 15 kHz, wide area can be supported in traditional cellular bands, and if SCS is 30 kHz/60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. If SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.


The NR frequency band may be defined as two types of frequency range, i.e., FR1 and FR2. The numerical value of the frequency range may be changed. For example, the frequency ranges of the two types (FR1 and FR2) may be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 may mean “sub 6 GHz range”, FR2 may mean “above 6 GHz range,” and may be referred to as millimeter wave (mmW).











TABLE 1





Frequency Range
Corresponding
Subcarrier


designation
frequency range
Spacing







FR1
 450 MHz-6000 MHz
 15, 30, 60 kHz


FR2
24250 MHz-52600 MHz
60, 120, 240 kHz









As mentioned above, the numerical value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or more included in FR1 may include an unlicensed band. Unlicensed bands may be used for a variety of purposes, for example for communication for vehicles (e.g., autonomous driving).











TABLE 2





Frequency Range
Corresponding
Subcarrier


designation
frequency range
Spacing







FR1
 410 MHz-7125 MHz
 15, 30, 60 kHz


FR2
24250 MHz-52600 MHz
60, 120, 240 kHz









Here, the radio communication technologies implemented in the wireless devices in the present disclosure may include narrowband internet-of-things (NB-IoT) technology for low-power communication as well as LTE, NR and 6G. For example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology, may be implemented in specifications such as LTE Cat NB1 and/or LTE Cat NB2, and may not be limited to the above-mentioned names. Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and be called by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented in at least one of the various specifications, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M, and may not be limited to the above-mentioned names.


Additionally and/or alternatively, the radio communication technologies implemented in the wireless devices in the present disclosure may include at least one of ZigBee, Bluetooth, and/or LPWAN which take into account low-power communication, and may not be limited to the above-mentioned names. For example, ZigBee technology may generate personal area networks (PANs) associated with small/low-power digital communication based on various specifications such as IEEE 802.15.4 and may be called various names.



FIG. 2 shows an example of wireless devices to which implementations of the present disclosure is applied.


Referring to FIG. 2, a first wireless device 100 and a second wireless device 200 may transmit/receive radio signals to/from an external device through a variety of RATs (e.g., LTE and NR).


In FIG. 2, {the first wireless device 100 and the second wireless device 200} may correspond to at least one of {the wireless device 100a to 100f and the BS 200}, {the wireless device 100a to 100f and the wireless device 100a to 100f} and/or {the BS 200 and the BS 200} of FIG. 1.


The first wireless device 100 may include at least one transceiver, such as a transceiver 106, at least one processing chip, such as a processing chip 101, and/or one or more antennas 108.


The processing chip 101 may include at least one processor, such a processor 102, and at least one memory, such as a memory 104. It is exemplarily shown in FIG. 2 that the memory 104 is included in the processing chip 101. Additional and/or alternatively, the memory 104 may be placed outside of the processing chip 101.


The processor 102 may control the memory 104 and/or the transceiver 106 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 102 may process information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory 104.


The memory 104 may be operably connectable to the processor 102. The memory 104 may store various types of information and/or instructions. The memory 104 may store a software code 105 which implements instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may implement instructions that, when executed by the processor 102, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 105 may control the processor 102 to perform one or more protocols. For example, the software code 105 may control the processor 102 to perform one or more layers of the radio interface protocol.


Herein, the processor 102 and the memory 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver 106 may include a transmitter and/or a receiver. The transceiver 106 may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the first wireless device 100 may represent a communication modem/circuit/chip.


The second wireless device 200 may include at least one transceiver, such as a transceiver 206, at least one processing chip, such as a processing chip 201, and/or one or more antennas 208.


The processing chip 201 may include at least one processor, such a processor 202, and at least one memory, such as a memory 204. It is exemplarily shown in FIG. 2 that the memory 204 is included in the processing chip 201. Additional and/or alternatively, the memory 204 may be placed outside of the processing chip 201.


The processor 202 may control the memory 204 and/or the transceiver 206 and may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts described in the present disclosure. For example, the processor 202 may process information within the memory 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver 206. The processor 202 may receive radio signals including fourth information/signals through the transceiver 106 and then store information obtained by processing the fourth information/signals in the memory 204.


The memory 204 may be operably connectable to the processor 202. The memory 204 may store various types of information and/or instructions. The memory 204 may store a software code 205 which implements instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may implement instructions that, when executed by the processor 202, perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. For example, the software code 205 may control the processor 202 to perform one or more protocols. For example, the software code 205 may control the processor 202 to perform one or more layers of the radio interface protocol.


Herein, the processor 202 and the memory 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver 206 may include a transmitter and/or a receiver. The transceiver 206 may be interchangeably used with RF unit. In the present disclosure, the second wireless device 200 may represent a communication modem/circuit/chip.


Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, radio resource control (RRC) layer, and service data adaptation protocol (SDAP) layer). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data unit (SDUs) according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure.


The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software and the firmware or software may be adapted to include the modules, procedures, or functions. Firmware or software adapted to perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure may be implemented using firmware or software in the form of code, commands, and/or a set of commands.


The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by read-only memories (ROMs), random access memories (RAMS), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.


The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices.


The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure, through the one or more antennas 108 and 208. In the present disclosure, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).


The one or more transceivers 106 and 206 may convert received user data, control information, radio signals/channels, etc., from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters. For example, the one or more transceivers 106 and 206 can up-convert OFDM baseband signals to OFDM signals by their (analog) oscillators and/or filters under the control of the one or more processors 102 and 202 and transmit the up-converted OFDM signals at the carrier frequency. The one or more transceivers 106 and 206 may receive OFDM signals at a carrier frequency and down-convert the OFDM signals into OFDM baseband signals by their (analog) oscillators and/or filters under the control of the one or more processors 102 and 202.


In the implementations of the present disclosure, a UE may operate as a transmitting device in uplink (UL) and as a receiving device in downlink (DL). In the implementations of the present disclosure, a BS may operate as a receiving device in UL and as a transmitting device in DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE, and the second wireless device 200 acts as the BS. For example, the processor(s) 102 connected to, mounted on or launched in the first wireless device 100 may be adapted to perform the UE behavior according to an implementation of the present disclosure or control the transceiver(s) 106 to perform the UE behavior according to an implementation of the present disclosure. The processor(s) 202 connected to, mounted on or launched in the second wireless device 200 may be adapted to perform the BS behavior according to an implementation of the present disclosure or control the transceiver(s) 206 to perform the BS behavior according to an implementation of the present disclosure.


In the present disclosure, a BS is also referred to as a node B (NB), an eNode B (eNB), or a gNB.



FIG. 3 shows an example of a wireless device to which implementations of the present disclosure is applied.


The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 1).


Referring to FIG. 3, wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit 110 may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 of FIG. 2 and/or the one or more memories 104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 of FIG. 2 and/or the one or more antennas 108 and 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140 and controls overall operation of each of the wireless devices 100 and 200. For example, the control unit 120 may control an electric/mechanical operation of each of the wireless devices 100 and 200 based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.


The additional components 140 may be variously configured according to types of the wireless devices 100 and 200. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit (e.g., audio I/O port, video I/O port), a driving unit, and a computing unit. The wireless devices 100 and 200 may be implemented in the form of, without being limited to, the robot (100a of FIG. 1), the vehicles (100b-1 and 100b-2 of FIG. 1), the XR device (100c of FIG. 1), the hand-held device (100d of FIG. 1), the home appliance (100e of FIG. 1), the IoT device (100f of FIG. 1), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 1), the BSs (200 of FIG. 1), a network node, etc. The wireless devices 100 and 200 may be used in a mobile or fixed place according to a use-example/service.


In FIG. 3, the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by a RAM, a dynamic RAM (DRAM), a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.



FIG. 4 shows an example of UE to which implementations of the present disclosure is applied.


Referring to FIG. 4, a UE 100 may correspond to the first wireless device 100 of FIG. 2 and/or the wireless device 100 or 200 of FIG. 3.


A UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 110, a battery 112, a display 114, a keypad 116, a subscriber identification module (SIM) card 118, a speaker 120, and a microphone 122.


The processor 102 may be adapted to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include ASIC, other chipset, logic circuit and/or data processing device. The processor 102 may be an application processor. The processor 102 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a modem (modulator and demodulator). An example of the processor 102 may be found in SNAPDRAGON™ series of processors made by Qualcomm®, EXYNOS™ series of processors made by Samsung®, A series of processors made by Apple®, HELIO™ series of processors made by MediaTek®, ATOM™ series of processors made by Intel® or a corresponding next generation processor.


The memory 104 is operatively coupled with the processor 102 and stores a variety of information to operate the processor 102. The memory 104 may include ROM, RAM, flash memory, memory card, storage medium and/or other storage device. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in the present disclosure. The modules can be stored in the memory 104 and executed by the processor 102. The memory 104 can be implemented within the processor 102 or external to the processor 102 in which case those can be communicatively coupled to the processor 102 via various means as is known in the art.


The transceiver 106 is operatively coupled with the processor 102, and transmits and/or receives a radio signal. The transceiver 106 includes a transmitter and a receiver. The transceiver 106 may include baseband circuitry to process radio frequency signals. The transceiver 106 controls the one or more antennas 108 to transmit and/or receive a radio signal.


The power management module 110 manages power for the processor 102 and/or the transceiver 106. The battery 112 supplies power to the power management module 110.


The display 114 outputs results processed by the processor 102. The keypad 116 receives inputs to be used by the processor 102. The keypad 116 may be shown on the display 114.


The SIM card 118 is an integrated circuit that is intended to securely store the international mobile subscriber identity (IMSI) number and its related key, which are used to identify and authenticate subscribers on mobile telephony devices (such as mobile phones and computers). It is also possible to store contact information on many SIM cards.


The speaker 120 outputs sound-related results processed by the processor 102. The microphone 122 receives sound-related inputs to be used by the processor 102.



FIG. 5 shows an example of 5G system architecture to which implementations of the present disclosure is applied.


The 5G system (5GS) architecture consists of the following network functions (NF).

    • Authentication Server Function (AUSF)
    • Access and Mobility Management Function (AMF)
    • Data Network (DN), e.g., operator services, Internet access or 3rd party services
    • Unstructured Data Storage Function (UDSF)
    • Network Exposure Function (NEF)
    • Intermediate NEF (I-NEF)
    • Network Repository Function (NRF)
    • Network Slice Selection Function (NSSF)
    • Policy Control Function (PCF)
    • Session Management Function (SMF)
    • Unified Data Management (UDM)
    • Unified Data Repository (UDR)
    • User Plane Function (UPF)
    • UE radio Capability Management Function (UCMF)
    • Application Function (AF)
    • User Equipment (UE)
    • (Radio) Access Network ((R)AN)
    • 5G-Equipment Identity Register (5G-EIR)
    • Network Data Analytics Function (NWDAF)
    • CHarging Function (CHF)


Furthermore, the following network functions may be considered.

    • Non-3GPP InterWorking Function (N3IWF)
    • Trusted Non-3GPP Gateway Function (TNGF)
    • Wireline Access Gateway Function (W-AGF)



FIG. 5 depicts the 5G system architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other.


In FIG. 5, for the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary.


For clarity, the UDR and its connections with other NFs, e.g., PCF, are not depicted in FIG. 5. For clarity, the NWDAF and its connections with other NFs, e.g., PCF, are not depicted in FIG. 5.


The 5G system architecture contains the following reference points:

    • N1: Reference point between the UE and the AMF.
    • N2: Reference point between the (R)AN and the AMF.
    • N3: Reference point between the (R)AN and the UPF.
    • N4: Reference point between the SMF and the UPF.
    • N6: Reference point between the UPF and a Data Network.
    • N9: Reference point between two UPFs.


The following reference points show the interactions that exist between the NF services in the NFs.

    • N5: Reference point between the PCF and an AF.
    • N7: Reference point between the SMF and the PCF.
    • N8: Reference point between the UDM and the AMF.
    • N10: Reference point between the UDM and the SMF.
    • N11: Reference point between the AMF and the SMF.
    • N12: Reference point between the AMF and the AUSF.
    • N13: Reference point between the UDM and the AUSF.
    • N14: Reference point between two AMFs.
    • N15: Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario.
    • N16: Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network).
    • N22: Reference point between the AMF and the NSSF.


In some cases, a couple of NFs may need to be associated with each other to serve a UE.


The 5G system proposes several methods for controlling network congestion when it occurs, one of which is NAS level Mobility Management (MM) congestion control. According to the NAS level MM congestion control, the UE applies a back-off mechanism for a specific time, and accordingly, additional signaling may not be performed at the MM level.


Specifically, the AMF may detect 5GMM signaling congestion and perform general NAS level MM congestion control. Under the 5GMM signaling congestion conditions, the AMF may reject 5GMM signaling requests from UEs. The AMF should not reject the following request:


a) requests for emergency services;


b) requests for emergency services fallback;


c) requests from UEs configured for high priority access in selected PLMN; and


d) DEREGISTRATION REQUEST message.


When general NAS level congestion control is active, the AMF may include a value for the mobility management back-off timer T3346 in the reject messages. The UE starts the timer T3346 with the value received in the 5GMM reject messages. To avoid that large numbers of UEs simultaneously initiate deferred requests, the AMF should select the value for the timer T3346 for the rejected UEs so that timeouts are not synchronized.


If the UE is registered in the same PLMN over the 3GPP access and non-3GPP access, and the UE receives the timer T3346 from the AMF, the timer T3346 applies to both 3GPP access and non-3GPP access.


If the timer T3346 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then the timer T3346 is kept running until it expires or it is stopped.


If the UE is switched off when the timer T3346 is running, the UE behaves as follows when the UE is switched on and the USIM in the UE remains the same. When assumed that t1 is the time remaining for T3346 timeout at switch off and t is the time elapsed between switch off and switch on, if t1 is greater than t, then the timer is restarted with the value t1−t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE restarts the timer with the value t1.


If the UE enters a new PLMN while timer T3346 is running, and the new PLMN is not equivalent to the PLMN where the UE started timer T3346, the UE stops timer T3346 when initiating 5GMM procedures in the new PLMN.


After a change in registration area, if the timer T3346 is running and 5GS update status is 5U1 UPDATED, then the UE sets the 5GS update status to 5U2 NOT UPDATED and enters state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE.


If timer T3346 is running or is deactivated, and the UE is a UE configured for high priority access in selected PLMN, or the UE needs to initiate signaling for emergency services or emergency services fallback, then the UE is allowed to initiate 5GMM procedures.


Hereinafter, minimization of service interruption (MINT) will be described. S3.1 and S6.31 of 3GPP TS 22.261 V17.2.0 (2021-03) may be referred.


The most efficient way to prevent interruption of communication services in the event of a disaster is to use roaming. That is, if communication service cannot be received from the communication operator to which the user subscribed due to a disaster, interruption of communication service can be prevented by roaming to another nearby communication operator's network to receive communication service. More specifically, each communication operator may actively install a wireless network and a core network in an area (e.g., one country) for which it is licensed. Different communication operators may construct networks in different ways and/or install core network nodes in different buildings, so even if a disaster occurs, it may not affect all communication operators equally. That is, a problem that occurs in one communication operator may not be equally likely to occur in another communication operator.


In 3GPP Rel-17, a MINT is being discussed in which, in the event of a disaster, a UE receiving a communication service from a communication operator affected by the disaster roams to a network of another communication operator so that the communication service can be continuously received.



FIG. 6 shows a concept of MINT to which implementations of the present disclosure is applied.


Referring to FIG. 6, when a disaster occurs, the roaming operator can accommodate subscribers of the disaster operator by broadcasting the PLMN identifier of the disaster operator. In addition, in order to accommodate subscribers of the disaster operator in case of a disaster, the PLMN identifier of the disaster operator is registered in the core network of the roaming operator, the wireless network broadcasts the corresponding PLMN identifier in the SIB message, and traffic can be mutually transmitted through the core network between operators.


In order to enable the third party to accommodate its roaming subscribers in the event of a communication disaster of its own and/or to accommodate third-party subscribers in the event of a third-party communication disaster, each operator may build a core network node (e.g., MME, S-GW, P-GW) for disaster roaming.


In normal times, the corresponding system should be ready to accept roaming calls through preliminary network interworking between operators, and may accommodate roaming calls between operators by taking follow-up measures according to occurrence criteria when a communication disaster occurs. Pre- and post-measures may follow consultations between operators.


In FIG. 6, it is shown as an example that MINT is applied in an Evolved Packet System (EPS), but MINT may also be applied in a 5G system.


Regarding MINT, the following terms may be defined.

    • Disaster Condition: This is the condition that a government decides when to initiate and terminate (e.g., a natural disaster). When this condition applies, users may have the opportunity to mitigate service interruptions and failures.
    • Disaster Inbound Roamer: A user that (a) cannot get service from the PLMN it would normally be served by, due to failure of service during a Disaster Condition, and (b) is able to register with other PLMNs.
    • Disaster Roaming: This is the special roaming policy that applies during a Disaster


Condition.


Regarding MINT, the following requirements may be considered.


A mobile network may fail to provide service in the event of a disaster (e.g., a fire.) The 5GS may provide functionality to mitigate interruption of service. If there are PLMN operators prepared to offer service, UEs may obtain service from the corresponding PLMN in the event of a disaster. MINT is constrained to a particular time and place. To reduce the impact to the 5G system of supporting Disaster Roaming, the potential congestion resulting from an influx or outflux of Disaster Inbound Roamers is taken into account.


Subject to regulatory requirements or operator's policy, 3GPP system may be able to enable a UE of a given PLMN to obtain connectivity service (e.g., voice call, mobile data service) from another PLMN for the area where a Disaster Condition applies.


The 3GPP system may enable UEs to obtain information that a Disaster Condition applies to a particular PLMN or PLMNs.


If a UE has no coverage of its Home PLMN (HPLMN), then obtains information that a Disaster Condition applies to the UE's HPLMN, the UE may register with a PLMN offering Disaster Roaming service.


The 3GPP system may support means for a PLMN operator to be aware of the area where Disaster Condition applies.


The 3GPP system may be able to support provision of service to Disaster Inbound Roamer only within the specific region where Disaster Condition applies.


The 3GPP system may be able to provide efficient means for a network to inform Disaster Inbound roamers that a Disaster Condition is no longer applicable.


Subject to regulatory requirements or operator's policy, the 3GPP system may support a PLMN operator to be made aware of the failure or recovery of other PLMN(s) in the same country when the Disaster Condition is applies, or when the Disaster Condition is not applicable.


The 3GPP system may be able to provide means to enable a UE to access PLMNs in a forbidden PLMN list if a Disaster condition applies and no other PLMN is available except for PLMNs in the forbidden PLMN list.


The 3GPP system may provide means to enable that a Disaster Condition applies to UEs of a specific PLMN.


The 3GPP system may be able to provide a resource efficient means for a PLMN to indicate to potential Disaster Inbound Roamers whether they can access the PLMN or not.


Disaster Inbound Roamers may perform network reselection when a Disaster Condition has ended.


The 3GPP system may minimize congestion caused by Disaster Roaming.


3GPP system may be able to collect charging information for a Disaster Inbound Roamer with information about the applied disaster condition.


Regarding access control for a UE that satisfies the Disaster Condition, access identity number 4 may be applied. The configuration may be valid for PLMNs that indicate to potential Disaster Inbound Roamers that the UEs can access the PLMN.


Regarding the MINT, network selection may be performed as follows.


At switch on, when in coverage of the last registered PLMN as stored in the SIM/USIM, the UE attaches to that network.


As an option, in automatic selection mode, when no Equivalent HPLMN (EHPLMN) list is present, the UE may select the HPLMN. When the EHPLMN list is present, the UE may select the highest priority EHPLMN among the available EHPLMNs. The operator may able to control the UE behavior by USIM configuration.


As an option, if the UE is in manual network selection mode at switch-on

    • if the last registered PLMN is unavailable and no equivalent PLMN is available, and
    • and the UE finds it is in coverage of either the HPLMN or an EHPLMN


then the UE may register on the corresponding HPLMN or EHPLMN. The UE remains in manual network selection mode.


If the UE returns to coverage of the PLMN on which it is already registered (as indicated by the registered PLMN stored in the SIM/USIM), the UE may perform a location update to a new location area if necessary. As an alternative option to this, if the UE is in automatic network selection mode and it finds coverage of the HPLMN or any EHPLMN, the UE may register on the HPLMN (if the EHPLMN list is not present) or the highest priority EHPLMN of the available EHPLMNs (if the EHPLMN list is present) and not return to the last registered PLMN. If the EHPLMN list is present and not empty, it may be used. The operator may be able to control by USIM configuration whether a UE that supports this option shall follow this alternative behavior.


The default behavior for a UE is to select the last registered PLMN.


If there is no registered PLMN stored in the SIM/USIM, or if this PLMN is unavailable and no equivalent PLMN is available, or the attempted registration fails, the UE may follow one of the following procedures for network selection.


A) Automatic Network Selection Mode


The UE may select and attempt registration on other PLMNs, if available and allowable, if the location area is not in the list of “forbidden LAs for roaming” and the tracking area is not in the list of “forbidden TAs for roaming”, in the following order.


i) An EHPLMN if the EHPLMN list is present or the HPLMN (derived from the IMSI) if the EHPLMN list is not present, for preferred access technologies in the order specified. In the case that there are multiple EHPLMNs present then the highest priority EHPLMN is selected.


ii) each entry in the “User Controlled PLMN Selector with Access Technology” data field in the SIM/USIM (in priority order).


iii) each entry in the “Operator Controlled PLMN Selector with Access Technology” data field in the SIM/USIM (in priority order).


iv) other PLMN/access technology combinations with sufficient received signal quality in random order.


v) all other PLMN/access technology combinations in order of decreasing signal quality.


It may be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service.


In the case of a UE operating in UE operation mode A or B, an allowable PLMN is one which is not in the Forbidden PLMN data field in the SIM/USIM. This data field may be extended in the Mobile Equipment (ME) memory. In the case of a UE operating in UE operation mode C, an allowable PLMN is one which is not in the Forbidden PLMN data field in the SIM/USIM or in the list of forbidden PLMNs for GPRS service in the ME. When there is no available PLMN except for PLMNs in the Forbidden PLMN data field in the SIM/USIM, and the available PLMNs indicate that Disaster Condition applies, this PLMN may be considered allowable for registration to the UE while the Disaster Condition is applicable.


If successful registration is achieved, the UE may indicate the selected PLMN.


If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE may obtain user consent for restricted local operator services and the UE may use a list of preferred PLMNs for restricted local operator services stored in the ME. If none of the preferred PLMNs for restricted local operator services is available, the UE may select any available PLMN offering restricted local operator services. If one of these PLMNs for restricted local operator service is chosen, the UE may indicate the choice. If none are selected, the UE may wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.


If registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services has been found, the UE may indicate “no service” to the user, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure. When registration cannot be achieved, different (discontinuous) PLMN search schemes may be used in order to minimize the access time while maintaining battery life, e.g. by prioritizing the search in favor of Broadcast Control Channel (BCCH) carriers which have a high probability of belonging to an available and allowable PLMN.


B) Manual Network Selection Mode


The UE may indicate PLMNs, including Forbidden PLMNs, which are available. If there are none, this may also be indicated. The HPLMN of the user may provide on the USIM additional information about the available PLMNs, if this is provided then the UE may indicate that information to the user. This information, provided as free text may include the followings.

    • Preferred partner,
    • roaming agreement status,
    • supported services


Furthermore, the UE may indicate whether the available PLMNs are present on one of the PLMN selector lists (e.g., EHPLMN, User Controlled, Operator Controlled or Forbidden) as well as not being present on any of the lists.


For the purpose of presenting the names of the available PLMNs to the user, the ME may use the USIM defined names if available or other PLMN naming rules in priority order (Country/PLMN indication).


Any available PLMNs is presented in the following order.


i) HPLMN (if the EHPLMN list is not present); or if one or more of the EHPLMNs are available, then based on an optional data field on the USIM, either the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field is not present, then only the highest priority available EHPLMN is presented.


ii) PLMNs contained in the “User Controlled PLMN Selector” data field in the SIMIUSIM (in priority order)


iii) PLMNs contained in the “Operator Controlled PLMN Selector” data field in the SIM/USIM (in priority order)


iv) other PLMN/access technology combinations with sufficient received signal level in random order


v) all other PLMN/access technology combinations in order of decreasing signal strength.


If a PLMN does not support voice services, then this is indicated to the user.


The user may select the desired PLMN and the UE attempts registration on this PLMN (This may take place at any time during the presentation of PLMNs).


If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE may obtain user consent for restricted local operator services and offer the user to select one of these networks. If one of these networks is selected, the UE may indicate the selected PLMN, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.


If the registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services is selected, the UE may indicate “No Service”. The user may then select and attempt to register on another or the same PLMN following the above procedure. The UE shall not attempt to register on a PLMN which has not been selected by the user.


Once the UE has registered on a PLMN selected by the user, the UE does not automatically register on a different PLMN unless:


i) The new PLMN is declared as an equivalent PLMN by the registered PLMN; or,


ii) The user selects automatic mode.


If a PLMN is selected but the UE cannot register on it because registration is rejected with the cause “PLMN not allowed”, the UE may add the PLMN to the Forbidden PLMN list. The UE shall not re-attempt to register on that network unless the same PLMN is selected again by the user.


If a PLMN is selected but the UE cannot register for Packet Switched (PS) services on it because registration is rejected with the cause “GPRS services not allowed in this PLMN”, the UE shall not re-attempt to register for Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or UTRAN PS or GSM EDGE Radio Access Network (GERAN) PS on that network. The PLMN is added to the list “Forbidden PLMN's for GPRS services”. The UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network unless the same PLMN is selected again by the user. The reception of the cause “GPRS services not allowed in this PLMN”, does not affect the CS service.


If a PLMN is selected but the UE cannot register on it for other reasons, the UE may, upon detection of a new LA (not in a forbidden LA list) of the selected PLMN, attempt to register on the PLMN.


If the UE is registered on a PLMN but loses coverage, different (discontinuous) carrier search schemes may be used to minimize the time to find a new valid BCCH carrier and maintain battery life, e.g. by prioritizing the search in favor of BCCH carriers of the registered PLMN.


When a registration attempt by the UE is rejected by a network with an indication of “permanent” PLMN restriction, the PLMN identity may be written to a list of Forbidden PLMNs stored in a data field in the SIM/USIM.


If a successful registration is achieved on a PLMN in the Forbidden PLMN list, the corresponding PLMN may be deleted from the list. However, if successful registration is achieved on a PLMN in the Forbidden PLMN list while Disaster Condition applies, the PLMN may not be deleted from Forbidden PLMN list.


When in automatic mode, the UE may indicate any PLMNs which will not be selected due to their presence in the Forbidden PLMN list.


If a UE receives an equivalent PLMN list containing a PLMN which is included in the Forbidden PLMN list, this PLMN may be removed from the equivalent PLMN list before this is stored by the UE.


When a disaster occurs (i.e., disaster conditions apply) in the HPLMN and the UE recognizes it, the UE may roam to another Visited PLMN (VPLMN) within the corresponding area. The VPLMN should be allowed in advance to be used for disaster roaming. If there are a plurality of disaster roaming PLMNs in the area, the UE may select one of them to receive service in a disaster situation.


However, from the point of view of the disaster roaming PLMN, if disaster roaming service is allowed for users of the disaster-occurring PLMN due to the occurrence of a disaster in a specific area, the number of disaster inbound roamers in the specific area may rapidly increase. Even if there are a plurality of disaster roaming PLMNs in the specific area, due to signal strength in the specific area or frequency band characteristics of the disaster-occurring PLMN, users of the disaster-occurring PLMN may preferentially flow into any one disaster roaming PLMN. In this case, the service quality of the network may be degraded due to the rapid increase in the number of users in the disaster roaming PLMN, and the service quality or user experience of the original subscribers of the disaster roaming PLMN that were normally serviced by the disaster roaming PLMN may be deteriorated.


Hereinafter, according to implementations of the present disclosure, when a disaster occurs in the communication network to which the UE is connected and the communication service cannot be provided from the communication network, and the disaster roaming service is provided through the disaster roaming communication network, a method for solving or minimizing a service quality degradation problem of a disaster roaming communication network due to an inflow of disaster inbound roamers is described.


Hereinafter, UE and terminal may be used interchangeably. Various implementations and/or embodiments of the present disclosure to be described below may be applied to various services, such as eMBB, V2X communication, public safety, IoT, etc. In addition, various implementations and/or embodiments of the present disclosure to be described below may be applied to various types of terminals, e.g., smart phones, vehicles, IoT terminals, robots, etc.


Various implementations and/or embodiments of the present disclosure to be described below may be individually performed, or two or more may be combined to be performed in a complex manner. In addition, combinations of one or more actions/configurations/steps of various implementations and/or embodiments of the present disclosure described below may be performed.


According to implementations of the present disclosure, when a user of a disaster-occurring PLMN (hereinafter referred to as a first PLMN) moves to a disaster roaming PLMN (hereinafter referred to as a second PLMN) and a congestion situation occurs in the second PLMN, the second PLMN may check the PLMN ID of the Globally Unique Temporary Identifier (GUTI) and/or Subscription Permanent Identifier (SUPI) of the UE in response to the UE's MM request, and confirm that the corresponding UE is the UE of the first PLMN. That is, the second PLMN may distinguish between a UE provided with the disaster roaming service and a UE not provided with the disaster roaming service (i.e., a UE originally provided with the service in the second PLMN).


According to implementations of the present disclosure, the second PLMN may apply a congestion control mechanism while rejecting an MM request to a UE introduced from the first PLMN. Congestion control for the UE introduced from the first PLMN may be implemented with a new cause value and timer information. Alternatively, congestion control for the UE introduced from the first PLMN may be implemented with an existing cause value (e.g., cause value #22), timer information, and an indicator. Alternatively, congestion control for the UE introduced from the first PLMN may be implemented with an existing cause value (e.g., cause value #22) and timer information. In addition, the second PLMN may provide the UE with information indicating that the UE needs to move to a new disaster roaming PLMN (e.g., a third PLMN) and information about the third PLMN. Upon receiving this, the UE operates a back-off timer for the second PLMN according to the timer information, and cannot make an additional request for Mobile Originating (MO) signaling to the second PLMN while the back-off timer is running. In addition, when the congestion control is due to disaster roaming, the UE may perform PLMN selection, and the second PLMN may be excluded from the PLMN selection target. If there is a new selectable disaster roaming PLMN, the UE may select a third PLMN. If there is no new selectable disaster roaming PLMN, the UE may remain in the second PLMN, but cannot request additional MO signaling until the back-off timer expires (however, the request for emergency service and/or Mobile Terminated (MT) is possible).


According to implementations of the present disclosure, the second PLMN may apply a congestion control mechanism for a UE introduced from the first PLMN through a network-initiated deregistration request rather than rejection of the UE's MM request. Upon receiving this, the UE deregisters from the second PLMN, operates a back-off timer for the second PLMN, and cannot make an additional request for MO signaling to the second PLMN while the back-off timer is running. In addition, when the congestion control is due to disaster roaming, the UE may perform PLMN selection, and the second PLMN may be excluded from the PLMN selection target. If there is a new selectable disaster roaming PLMN, the UE may select a third PLMN.


According to implementation of the present disclosure, when the UE moves to and registers with the third PLMN according to PLMN selection, the UE may manage the second PLMN as a separate list. For example, the UE may store the second PLMN in a “temporarily forbidden PLMN” list. Accordingly, the UE cannot select the second PLMN when selecting a PLMN in the future.


The following drawings are created to explain specific embodiments of the present disclosure. The names of the specific devices or the names of the specific signals/messages/fields shown in the drawings are provided by way of example, and thus the technical features of the present disclosure are not limited to the specific names used in the following drawings.



FIG. 7 shows an example of a method performed by a UE to which implementations of the present disclosure is applied.


In step S700, the method comprises detecting that a disaster condition applies to a first PLMN providing services in a specific area.


In step S710, the method comprises performing registration with a second PLMN providing services in the specific area.


In step S720, the method comprises receiving a message from a network in the second PLMN. The message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control.


In some implementations, the information informing that the UE is subject to congestion control in the second PLMN may be a new cause value. Alternatively, the information informing that the UE is subject to congestion control in the second PLMN may be a combination of an existing cause value and a new indicator.


In some implementations, the message may include information about at least one PLMN (e.g., third PLMN) among the PLMNs.


In some implementations, the message may be a 5G MM reject message that is a response to a 5G MM request of the UE. Alternatively, the message may be a request message for network-initiated deregistration.


In some implementations, the timer information may be for the second PLMN.


In some implementations, that the UE is subject to congestion control in the second PLMN may be determined based on a PLMN ID included in a GUTI and/or SUPI of the UE.


In step S730, the method comprises operating a timer based on the timer information.


In step S740, the method comprises performing PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.


In some implementations, the UE may be in communication with at least one of a mobile device, a network, and/or autonomous vehicles other than the UE.


Furthermore, the method in perspective of the UE described above in FIG. 7 may be performed by the first wireless device 100 shown in FIG. 2, the wireless device 100 shown in FIG. 3, and/or the UE 100 shown in FIG. 4.


More specifically, the UE comprises at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor. The at least one memory stores instructions to cause the at least one processor to perform operations below.


The UE detects that a disaster condition applies to a first PLMN providing services in a specific area.


The UE performs registration with a second PLMN providing services in the specific area.


The UE receives, via the at least one transceiver, a message from a network in the second PLMN. The message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control.


In some implementations, the information informing that the UE is subject to congestion control in the second PLMN may be a new cause value. Alternatively, the information informing that the UE is subject to congestion control in the second PLMN may be a combination of an existing cause value and a new indicator.


In some implementations, the message may include information about at least one PLMN (e.g., third PLMN) among the PLMNs.


In some implementations, the message may be a 5G MM reject message that is a response to a 5G MM request of the UE. Alternatively, the message may be a request message for network-initiated deregistration.


In some implementations, the timer information may be for the second PLMN.


In some implementations, that the UE is subject to congestion control in the second PLMN may be determined based on a PLMN ID included in a GUTI and/or SUPI of the UE.


The UE operates a timer based on the timer information.


The UE performs PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.


Furthermore, the method in perspective of the UE described above in FIG. 7 may be performed by control of the processor 102 included in the first wireless device 100 shown in FIG. 2, by control of the communication unit 110 and/or the control unit 120 included in the wireless device 100 shown in FIG. 3, and/or by control of the processor 102 included in the UE 100 shown in FIG. 4.


More specifically, a processing apparatus operating in a wireless communication system comprises at least one processor, and at least one memory operably connectable to the at least one processor. The at least one processor is adapted to perform operations comprising: detecting that a disaster condition applies to a first PLMN providing services in a specific area, performing registration with a second PLMN providing services in the specific area, obtaining a message in the second PLMN, wherein the message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control, operating a timer based on the timer information, and performing PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.


Furthermore, the method in perspective of the UE described above in FIG. 7 may be performed by a software code 105 stored in the memory 104 included in the first wireless device 100 shown in FIG. 2.


The technical features of the present disclosure may be embodied directly in hardware, in a software executed by a processor, or in a combination of the two. For example, a method performed by a wireless device in a wireless communication may be implemented in hardware, software, firmware, or any combination thereof. For example, a software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other storage medium.


Some example of storage medium may be coupled to the processor such that the processor can read information from the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. For other example, the processor and the storage medium may reside as discrete components.


The computer-readable medium may include a tangible and non-transitory computer-readable storage medium.


For example, non-transitory computer-readable media may include RAM such as synchronous dynamic random access memory (SDRAM), ROM, non-volatile random access memory (NVRAM), EEPROM, flash memory, magnetic or optical data storage media, or any other medium that can be used to store instructions or data structures. Non-transitory computer-readable media may also include combinations of the above.


In addition, the method described herein may be realized at least in part by a computer-readable communication medium that carries or communicates code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer.


According to some implementations of the present disclosure, a non-transitory computer-readable medium (CRM) has stored thereon a plurality of instructions.


More specifically, CRM stores instructions to cause at least one processor to perform operations. The operations comprise: detecting that a disaster condition applies to a first PLMN providing services in a specific area, performing registration with a second PLMN providing services in the specific area, obtaining a message in the second PLMN, wherein the message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control, operating a timer based on the timer information, and performing PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.



FIG. 8 shows an example of a method performed by a RAN node of a second PLMN to which implementations of the present disclosure is applied.


In step S800, the method comprises receiving a registration request message from a UE.


In step S810, the method comprises transmitting a message to the UE.


The message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of a disaster condition in a first PLMN, and (ii) timer information related to the congestion control.


In some implementations, the information informing that the UE is subject to congestion control in the second PLMN may be a new cause value. Alternatively, the information informing that the UE is subject to congestion control in the second PLMN may be a combination of an existing cause value and a new indicator.


In some implementations, the message may include information about at least one PLMN (e.g., third PLMN) among the PLMNs.


In some implementations, the message may be a 5G MM reject message that is a response to a 5G MM request of the UE. Alternatively, the message may be a request message for network-initiated deregistration.


In some implementations, the timer information may be for the second PLMN.


In some implementations, that the UE is subject to congestion control in the second PLMN may be determined based on a PLMN ID included in a GUTI and/or SUPI of the UE.


Furthermore, the method in perspective of the RAN node described above in FIG. 8 may be performed by the second wireless device 200 shown in FIG. 2 and/or the wireless device 200 shown in FIG. 3.


More specifically, the RAN node comprises at least one transceiver, at least one processor, and at least one memory operably connectable to the at least one processor. The at least one memory stores instructions to cause the at least one processor to perform operations below.


The RAN node receives, via the at least one transceiver, a registration request message from a UE.


The RAN node transmits, via the at least one transceiver, a message to the UE.


The message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of a disaster condition in a first PLMN, and (ii) timer information related to the congestion control.


In some implementations, the information informing that the UE is subject to congestion control in the second PLMN may be a new cause value. Alternatively, the information informing that the UE is subject to congestion control in the second PLMN may be a combination of an existing cause value and a new indicator.


In some implementations, the message may include information about at least one PLMN (e.g., third PLMN) among the PLMNs.


In some implementations, the message may be a 5G MM reject message that is a response to a 5G MM request of the UE. Alternatively, the message may be a request message for network-initiated deregistration.


In some implementations, the timer information may be for the second PLMN.


In some implementations, that the UE is subject to congestion control in the second PLMN may be determined based on a PLMN ID included in a GUTI and/or SUPI of the UE.


Hereinafter, various implementations of the present disclosure are described in detail.


1. First Implementation


While a UE is receiving a communication service from the HPLMN (hereinafter referred to as a first PLMN), a disaster occurs in the HPLMN (i.e., a disaster condition applies), and thus it may be impossible to receive the communication service from the HPLMN. Accordingly, the UE may attempt disaster roaming to a neighboring VPLMN according to operator policies or national regulations. If the selected disaster roaming PLMN (hereinafter referred to as the second PLMN) accepts the registration request of the UE, the UE may register with the disaster roaming PLMN and may receive the disaster roaming service.


After a disaster occurs in a specific area and disaster roaming is applied in the specific area, a large number of UEs in the first PLMN may move to and register with the second PLMN within a short time. As a result, the second PLMN may predict whether congestion will occur in the network. In addition, when congestion is predicted to occur, application of congestion control may be determined.


The second PLMN may predict whether congestion will occur in the network based on various factors. For example, the second PLMN may predict whether congestion will occur in the network based on the number of users, the number of signaling requests, or the amount of traffic in a user plane in the specific area. In particular, the second PLMN may predict whether congestion will occur in the network based on the number of disaster inbound roamers introduced from the first PLMN due to disaster roaming.


Upon predicting that congestion will occur in the network based on various factors, the second PLMN may determine application of congestion control. In particular, when it is determined that congestion will occur due to disaster inbound roamers introduced from the first PLMN, the second PLMN may determine application of disaster roaming congestion control different from conventional congestion control.


The second PLMN may check the PLMN ID included in the GUTI (e.g., 5G-GUTI) and/or SUPI of the UE that sent the 5G MM request. If the corresponding PLMN ID is the same as that of the first PLMN, the second PLMN may know that the corresponding UE is a disaster inbound roamer that accesses/registers to receive disaster roaming service from the second PLMN due to the occurrence of a disaster in the first PLMN. Alternatively, the second PLMN may know that the corresponding UE is a disaster inbound roamer through a separate indicator (e.g., registration type). Accordingly, the second PLMN may determine application of disaster roaming congestion control to the corresponding UE. If the corresponding PLMN ID is not the ID of the first PLMN but the ID of the second PLMN (i.e., the corresponding UE is a subscriber of the second PLMN) and/or the ID of another PLMN (i.e., normal roaming, not disaster roaming), the second PLMN may determine application of general congestion control and/or suspend application of congestion control to the corresponding UE.


2. Second Implementation


According to the first implementation of the present disclosure described above, when the second PLMN predicts that congestion will occur in the network, determines that the corresponding congestion will occur due to disaster inbound roamers introduced from the first PLMN and determines to apply the disaster roaming congestion control, the second PLMN may perform disaster roaming congestion control as follows.


The second PLMN may respond with a reject message to the UE's 5G MM request (e.g., registration request, service request, etc.). In this case, the reject message may include information for disaster roaming congestion control in one of the following ways.


1) 5G MM Cause Value #xx (“Congestion for Disaster Roamer”)+T3346 Value


The reject message may include a new 5G MM cause value #xx that is not the conventional 5G MM cause value and a value for back-off timer T3346. The new 5G MM cause value #xx may indicate that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming.


2) 5G MM Cause Value #22 (“Congestion”)+New Indicator+T3346 Value


The reject message may include a cause value #22, which is a 5G MM cause value used in a conventional congestion situation, a value for back-off timer T3346, and an additional new indicator. The new indicator may indicate that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming. Alternatively, the new indicator may indicate a congestion situation due to disaster roaming. The new indicator may be implemented in the form of a 1-bit flag and/or implemented with a plurality of bits.


3) 5G MM Cause Value #22 (“Congestion”)+T3346 Value


The reject message may include a cause value #22, which is a 5G MM cause value used in a conventional congestion situation, and a value for back-off timer T3346. However, the UE may recognize that it is subject to disaster roaming rather than normal roaming. As a result, the UE may judge/act as same as a case that the UE receives a cause value and/or an indicator indicating that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming described in 1) and/or 2).


Additionally, the reject message may include information recommending that the UE moves to another PLMN. This may include a recommendation to move to another PLMN (hereinafter referred to as a third PLMN) and receive disaster roaming service since the service for the disaster inbound roamers is limited due to the network congestion of the second PLMN. The information recommending moving to another PLMN may be implemented in the form of a 1-bit flag. Alternatively, the information recommending moving to another PLMN may explicitly include a PLMN ID of which moving is recommended. If the disaster roaming service is implemented under national roaming (i.e., moving/roaming to another third PLMN within the same country), the PLMN ID may omit Mobile Country Codes (MCC) and include only Mobile Network Codes (MNC).


Upon receiving the reject message including the information for disaster roaming congestion control, the UE may operate as follows. The UE may initiate T3346 for the second PLMN using the received T3346 value. The UE cannot send additional MM requests to the second PLMN until T3346 expires/suspends, and may only send exceptional requests (e.g., requests for emergency services and/or high priority access, etc.).


In addition, when recognizing that the current congestion control is for a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming, the UE may perform PLMN selection. In this case, PLMN selection may be performed except for the first PLMN and the second PLMN. If the reject message includes information recommending moving to another PLMN, PLMN selection may be performed based on the corresponding information. For example, if the information recommending moving to another PLMN includes the PLMN ID of the third PLMN, the third PLMN may be considered with high priority in PLMN selection.


Depending on the result of PLMN selection, the UE may operate as follows.


1) If there is Other PLMN Selectable within the Current Area


When there exists a PLMN (e.g., a third PLMN) to which it is recommended to move or another PLMN to which the UE can access (e.g., a PLMN that is not in the forbidden PLMN list and satisfies radio section physical characteristics such as frequency band), the UE may select a corresponding PLMN and perform registration. When registration is successfully completed in the corresponding PLMN, the UE may continue to receive disaster roaming service from the corresponding PLMN. In this case, the back-off timer T3346 operating for the second PLMN may not be interrupted and may continue to operate.


2) If there is No Other PLMN Selectable within the Current Area


If there is no other selectable PLMN other than the second PLMN within the current area, the UE may maintain a registration state with the second PLMN. While T3346 is operating for the second PLMN, an additional MM request cannot be transmitted to the second PLMN. However, a response to the MT request and/or a request for emergency service may be performed.


In addition, if the reject message does not include information recommending moving to another PLMN, similarly, a registration state with the second PLMN may be maintained and a back-off mechanism may be performed without selecting another PLMN.


3. Third Implementation


According to the first implementation of the present disclosure described above, when the second PLMN predicts that congestion will occur in the network, determines that the corresponding congestion will occur due to disaster inbound roamers introduced from the first PLMN and determines to apply the disaster roaming congestion control, the second PLMN may perform disaster roaming congestion control as follows.


The second PLMN may initiate a network-initiated deregistration procedure before receiving the 5G MM request from the UE. The second PLMN may transmit a deregistration request message to the UE. In this case, the deregistration request message may include information for disaster roaming congestion control in one of the following ways.


1) 5G MM Cause Value #xx (“Congestion for Disaster Roamer”)+T3346 Value


The deregistration request message may include a new 5G MM cause value #xx that is not the conventional 5G MM cause value and a value for back-off timer T3346. The new 5G MM cause value #xx may indicate that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming.


2) 5G MM Cause Value #22 (“Congestion”)+New Indicator+T3346 Value


The deregistration request message may include a cause value #22, which is a 5G MM cause value used in a conventional congestion situation, a value for back-off timer T3346, and an additional new indicator. The new indicator may indicate that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming. Alternatively, the new indicator may indicate a congestion situation due to disaster roaming. The new indicator may be implemented in the form of a 1-bit flag and/or implemented with a plurality of bits.


3) 5G MM Cause Value #22 (“Congestion”)+T3346 Value


The deregistration request message may include a cause value #22, which is a 5G MM cause value used in a conventional congestion situation, and a value for back-off timer T3346. However, the UE may recognize that it is subject to disaster roaming rather than normal roaming. As a result, the UE may judge/act as same as a case that the UE receives a cause value and/or an indicator indicating that the current congestion control targets a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming described in 1) and/or 2).


Additionally, the deregistration request message may include information recommending that the UE moves to another PLMN. This may include a recommendation to move to another PLMN (hereinafter referred to as a third PLMN) and receive disaster roaming service since the service for the disaster inbound roamers is limited due to the network congestion of the second PLMN. The information recommending moving to another PLMN may be implemented in the form of a 1-bit flag. Alternatively, the information recommending moving to another PLMN may explicitly include a PLMN ID of which moving is recommended. If the disaster roaming service is implemented under national roaming (i.e., moving/roaming to another third PLMN within the same country), the PLMN ID may omit MCC and include only MNC.


Upon receiving the deregistration request message including the information for disaster roaming congestion control, the UE may operate as follows. The UE may initiate T3346 for the second PLMN using the received T3346 value. The UE cannot send additional MM requests to the second PLMN until T3346 expires/suspends, and may only send exceptional requests (e.g., requests for emergency services and/or high priority access, etc.).


In addition, when recognizing that the current congestion control is for a subscriber of the first PLMN who has flowed into the second PLMN through disaster roaming, the UE may perform PLMN selection. In this case, PLMN selection may be performed except for the first PLMN and the second PLMN. If the deregistration request message includes information recommending moving to another PLMN, PLMN selection may be performed based on the corresponding information. For example, if the information recommending moving to another PLMN includes the PLMN ID of the third PLMN, the third PLMN may be considered with high priority in PLMN selection.


Depending on the result of PLMN selection, the UE may operate as follows.


1) If there is Other PLMN Selectable within the Current Area


When there exists a PLMN (e.g., a third PLMN) to which it is recommended to move or another PLMN to which the UE can access (e.g., a PLMN that is not in the forbidden PLMN list and satisfies radio section physical characteristics such as frequency band), the UE may select a corresponding PLMN and perform registration. When registration is successfully completed in the corresponding PLMN, the UE may continue to receive disaster roaming service from the corresponding PLMN. In this case, the back-off timer T3346 operating for the second PLMN may not be interrupted and may continue to operate.


2) If there is No Other PLMN Selectable within the Current Area


If there is no other selectable PLMN except for the second PLMN within the current area, the UE becomes unable to receive service. This is because a new registration request cannot be transmitted because the back-off timer is running for the second PLMN. In this case, the UE may periodically perform PLMN selection in the deregistration state and/or attempt registration for emergency access.


4. Fourth Implementation


If movement to another PLMN is recommended and successfully registered with the corresponding PLMN (e.g., the third PLMN) by the second implementation and/or third implementation of the present disclosure described above, the UE may manage the second PLMN as a separate list. For example, the UE may store the second PLMN in a temporarily forbidden PLMN list. The temporarily forbidden PLMN list may include PLMNs in which congestion occurs due to disaster roaming. A PLMN included in the temporarily forbidden PLMN list is deleted from the temporarily forbidden PLMN list after a certain amount of time (e.g., the same time as T3346) has elapsed since it was registered, and if necessary, the UE may retry the registration request for the corresponding PLMN.


The present disclosure can have various advantageous effects.


For example, in a 5G system, a disaster roaming PLMN providing roaming service due to a disaster can anticipate a congestion situation due to disaster inbound roamers.


For example, when congestion occurs in the disaster roaming PLMN due to disaster inbound roamers, congestion control can be performed to reduce an impact on a communication service of the disaster roaming PLMN.


For example, the disaster inbound roamers can be successfully moved to another disaster roaming PLMN, thereby enhancing the user experience.


Advantageous effects which can be obtained through specific embodiments of the present disclosure are not limited to the advantageous effects listed above. For example, there may be a variety of technical effects that a person having ordinary skill in the related art can understand and/or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described herein, but may include various effects that may be understood or derived from the technical features of the present disclosure.


Claims in the present disclosure can be combined in a various way. For instance, technical features in method claims of the present disclosure can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. Other implementations are within the scope of the following claims.

Claims
  • 1. A method performed by a user equipment (UE) adapted to operate in a wireless communication system, the method comprising: detecting that a disaster condition applies to a first Public Land Mobile Network (PLMN) providing services in a specific area;performing registration with a second PLMN providing services in the specific area;receiving a message from a network in the second PLMN, wherein the message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control;operating a timer based on the timer information; andperforming PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.
  • 2. The method of claim 1, wherein the information informing that the UE is subject to congestion control in the second PLMN is a new cause value.
  • 3. The method of claim 1, wherein the information informing that the UE is subject to congestion control in the second PLMN is a combination of an existing cause value and a new indicator.
  • 4. The method of claim 1, wherein the message includes information about at least one PLMN among the PLMNs.
  • 5. The method of claim 1, wherein the message is a 5G MM reject message that is a response to a 5G Mobility Management (MM) request of the UE.
  • 6. The method of claim 1, wherein the message is a request message for network-initiated deregistration.
  • 7. The method of claim 1, wherein the timer information is for the second PLMN.
  • 8. The method of claim 1, wherein that the UE is subject to congestion control in the second PLMN is determined based on a PLMN ID included in a Globally Unique Temporary Identifier (GUTI) and/or Subscription Permanent Identifier (SUPI) of the UE.
  • 9. The method of claim 1, wherein the UE is in communication with at least one of a mobile device, a network, and/or autonomous vehicles other than the UE.
  • 10. A User Equipment (UE) adapted to operate in a wireless communication system, the UE comprising: at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:detecting that a disaster condition applies to a first Public Land Mobile Network (PLMN) providing services in a specific area;performing registration with a second PLMN providing services in the specific area;receiving, via the at least one transceiver, a message from a network in the second PLMN, wherein the message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of the disaster condition in the first PLMN, and (ii) timer information related to the congestion control;operating a timer based on the timer information; andperforming PLMN selection with respect to PLMNs other than the second PLMN while the timer is running.
  • 11. The UE of claim 10, wherein the information informing that the UE is subject to congestion control in the second PLMN is a new cause value and/or a combination of an existing cause value and a new indicator.
  • 12. The UE of claim 10, wherein the message includes information about at least one PLMN among the PLMNs.
  • 13. The UE of claim 10, wherein the message is a 5G MM reject message that is a response to a 5G Mobility Management (MM) request of the UE and/or a request message for network-initiated deregistration.
  • 14. The UE of claim 10, wherein the timer information is for the second PLMN.
  • 15-17. (canceled)
  • 18. A Radio Access Network (RAN) node of a second Public Land Mobile Network (PLMN) adapted to operate in a wireless communication system, the RAN node comprising: at least one transceiver;at least one processor; andat least one memory operably connectable to the at least one processor and storing instructions that, based on being executed by the at least one processor, perform operations comprising:receiving, via the at least one transceiver, a registration request message from a User Equipment (UE); andtransmitting, via the at least one transceiver, a message to the UE,wherein the message includes (i) information informing that the UE is subject to congestion control in the second PLMN based on application of a disaster condition in a first PLMN, and (ii) timer information related to the congestion control.
Priority Claims (1)
Number Date Country Kind
10-2020-0086262 Jul 2020 KR national
PCT Information
Filing Document Filing Date Country Kind
PCT/KR2021/008768 7/9/2021 WO