WO2021206322A1 - Scheme for processing congestion control exception for operation of multi-usim terminal moving between usims - Google Patents

Abstract

Provided are a method for processing congestion control exception for an operation of a multi-universal subscriber identification module (USIM) terminal moving between USIMs, and a device for implementing same. The multi-USIM terminal performs registration in a first network and a second network, receives information related to a back-off timer for congestion control from an access and mobility management function (AMF) in the first network, and operates the back-off timer. When determined to depart from the first network, the multi-USIM terminal transmits, to the AMF in the first network, a non-access stratum (NAS) message including information indicating a departure from the first network during operation of the back-off timer.

Description

Congestion control exception handling method for movement between USIMs of multi-USIM terminals

This specification relates to a congestion control exception handling method for a movement operation between USIMs of a multi-universal subscriber identification module (USIM) terminal.

3rd generation partnership project (3GPP) long-term evolution (LTE) is a technology for enabling high-speed packet communication. Many methods have been proposed to reduce costs for users and operators, which are LTE goals, improve service quality, expand coverage, and increase system capacity. 3GPP LTE requires lower cost per bit, improved service availability, flexible use of frequency bands, simple structure, open interface, and proper power consumption of terminals as high-level requirements.

Work has begun to develop requirements and specifications for a new radio (NR) system in the International Telecommunication Union (ITU) and 3GPP. 3GPP identifies the technical components needed to successfully standardize NR in a timely manner that satisfies both urgent market needs and the longer-term requirements set forth by the ITU radio communication sector (ITU-R) international mobile telecommunications (IMT)-2020 process. and should be developed Furthermore, NR should be able to use any spectral band up to at least 100 GHz that could be used for wireless communication even in the distant future.

NR targets a single technology framework that covers all deployment scenarios, usage scenarios and requirements, including enhanced mobile broadband (eMBB), massive machine type-communications (mMTC), ultra-reliable and low latency communications (URLLC), and more. do. NR must be forward compatible in nature.

Multi-SIM (subscriber identification module) devices allow one device to use multiple services over multiple networks. To date, multi-SIM devices have been supported without specific support within the 3GPP specification. The 3GPP specification will officially support multi-SIM devices starting with Rel-17. Support for multi-SIM devices in Rel-17 aims to enable improved performance and user experience for multi-SIM devices.

A multi-SIM device may leave one network and join another network, and it may be necessary to inform the currently connected network of this fact. However, in a situation in which congestion control is applied, it may not be possible to notify this fact itself, so we intend to solve this problem.

In one aspect, a method performed by a wireless device operating in a wireless communication system is provided. The method includes performing registration with a first network and a second network, receiving information related to a backoff timer for congestion control from an access and mobility management function (AMF) in the first network, and the backoff timer including the step of operating If the wireless device decides to leave the first network, the method sends a non-access stratum (NAS) message including information indicating to leave the first network while the backoff timer is running to the first and sending to the AMF in the network.

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

The present specification may have various effects.

For example, even in a NAS level congestion control situation, the multi-USIM device may transmit a NAS MM message including a departure instruction to a currently connected system.

For example, a system to which multi-USIM devices are currently connected can effectively utilize resources allocated to the multi-USIM devices in other places without wasting it.

Effects that can be obtained through specific examples of the present specification are not limited to the effects listed above. For example, various technical effects that a person having ordinary skill in the related art can understand or derive from this specification may exist. Accordingly, the specific effects of the present specification are not limited to those explicitly described herein, and may include various effects that can be understood or derived from the technical characteristics of the present specification.

1 shows an example of a communication system to which an implementation of the present specification is applied.

2 shows an example of a wireless device to which the implementation of the present specification is applied.

3 shows an example of a wireless device to which the implementation of the present specification is applied.

4 shows an example of a UE to which the implementation of the present specification is applied.

5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.

6 shows an example of a method performed by a wireless device to which the implementation of the present specification is applied.

7 shows an example of a procedure for leaving a network to which an implementation of the present specification is applied.

The following technique, apparatus and system can be applied to various wireless multiple access systems. Examples of 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 system, a single SC-FDMA (single) system. It includes a carrier frequency division multiple access) system, and a multicarrier frequency division multiple access (MC-FDMA) system. CDMA may be implemented over a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented through a 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 implemented through a wireless 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 part of the 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 uses OFDMA in downlink (DL) and SC-FDMA in uplink (UL). Evolution of 3GPP LTE includes LTE-A (advanced), LTE-A Pro, and/or 5G NR (new radio).

For convenience of description, implementations of the present specification are mainly described in the context of a 3GPP-based wireless communication system. However, the technical characteristics of the present specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to the 3GPP-based wireless communication system, but aspects of the present specification that are not limited to the 3GPP-based wireless communication system may be applied to other mobile communication systems.

For terms and techniques not specifically described among terms and techniques used in this specification, reference may be made to a wireless communication standard document issued before this specification.

In this specification, "A or B (A or B)" may mean "only A", "only B", or "both A and B". In other words, “A or B (A or B)” in the present specification may be interpreted as “A and/or B (A and/or B)”. For example, "A, B or C(A, B or C)" herein means "only A", "only B", "only C", or "any and any combination of A, B and C ( any combination of A, B and C)".

As used herein, a slash (/) or a comma (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 this specification, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, in this specification, the expression "at least one of A or B" or "at least one of A and/or B" means "A and at least one of A and B”.

Also, as used herein, "at least one of A, B and C" means "only A", "only B", "only C", or "A, B and C" any combination of A, B and C". Also, "at least one of A, B or C" or "at least one of A, B and/or C" means can mean “at least one of A, B and C”.

In addition, parentheses used herein may mean "for example". Specifically, when displayed as “control information (PDCCH)”, “PDCCH” may be proposed as an example of “control information”. In other words, "control information" in the present specification is not limited to "PDCCH", and "PDCCH" may be proposed as an example of "control information". In addition, even when displayed as “control information (ie, PDCCH)”, “PDCCH” may be proposed as an example of “control information”.

In this specification, technical features that are individually described within one drawing may be implemented individually or simultaneously.

Although not limited thereto, the various descriptions, functions, procedures, suggestions, methods, and/or operation flowcharts disclosed herein may be applied to various fields requiring wireless communication and/or connection (eg, 5G) between devices.

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

1 shows an example of a communication system to which an implementation of the present specification is applied.

The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of the present specification can be applied to other 5G usage scenarios not shown in FIG. 1 .

The three main requirements categories for 5G are (1) enhanced mobile broadband (eMBB) category, (2) massive machine type communication (mMTC) category, and (3) ultra-reliable, low-latency communication. (URLLC; ultra-reliable and low latency communications) category.

Referring to FIG. 1 , a communication system 1 includes wireless devices 100a to 100f , a base station (BS) 200 , and a network 300 . 1 illustrates a 5G network as an example of a network of the communication system 1, the implementation of the present specification is not limited to the 5G system, and may be applied to future communication systems beyond the 5G system.

Base station 200 and network 300 may be implemented as wireless devices, and certain wireless devices may act as base station/network nodes in relation to other wireless devices.

The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (eg, 5G NR or LTE), and may also be referred to as a communication/wireless/5G device. The wireless devices 100a to 100f are not limited thereto, and include, but are not limited to, the robot 100a, the vehicles 100b-1 and 100b-2, the extended reality (XR) device 100c, the portable device 100d, and home appliances. It may include a product 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400 . For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication. Vehicles may include unmanned aerial vehicles (UAVs) (eg drones). XR devices may include AR/VR/mixed reality (MR) devices, and may include head-mounted devices (HMDs) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, and the like. mounted device) or HUD (head-up display). Portable devices may include smartphones, smart pads, wearable devices (eg, smart watches or smart glasses), and computers (eg, laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

In this specification, the wireless devices 100a to 100f may be referred to as user equipment (UE). The UE is, for example, a mobile phone, a smartphone, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, an autonomous driving function. Vehicles with, connected cars, UAVs, AI modules, robots, AR devices, VR devices, MR devices, holographic devices, public safety devices, MTC devices, IoT devices, medical devices, fintech devices (or financial devices), security devices , weather/environmental devices, 5G service related devices, or 4th industrial revolution related devices.

For example, the UAV may be an aircraft that does not have a person on board and is navigated by a radio control signal.

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

For example, the public safety device may include an image relay device or an image device that can be worn on a user's body.

For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart light bulbs, door locks, or various sensors.

For example, a medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating, or preventing a disease. For example, a medical device may be a device used to diagnose, treat, alleviate, or correct an injury or injury. For example, a medical device may be a device used for the purpose of examining, replacing, or modifying structure or function. For example, the medical device may be a device used for pregnancy control purposes. For example, a medical device may include a device for treatment, a device for driving, an (ex vivo) diagnostic device, a hearing aid, or a device for a procedure.

For example, a security device may be a device installed to prevent possible danger and maintain safety. For example, the security device may be a camera, closed circuit television (CCTV), recorder, or black box.

For example, the fintech device may be a device capable of providing financial services such as mobile payment. For example, a fintech device may include a payment device or a POS system.

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

The wireless devices 100a to 100f may be connected to the network 300 through the base station 200 . 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 through the network 300 . The network 300 may be configured using a 3G network, a 4G (eg, LTE) network, a 5G (eg, NR) network, and a 5G or later network. The wireless devices 100a to 100f may communicate with each other through the base station 200/network 300, but communicate directly without going through the base station 200/network 300 (eg, sidelink communication). You may. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (eg, vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication). Also, the IoT device (eg, a sensor) may communicate directly with another IoT device (eg, a sensor) or other wireless devices 100a to 100f.

Wireless communication/ connections 150a , 150b , 150c may be established between the wireless devices 100a - 100f and/or between the wireless devices 100a - 100f and the base station 200 and/or between the base station 200 . Here, the wireless communication/connection includes uplink/downlink communication 150a, sidelink communication 150b (or device-to-device (D2D) communication), and inter-base station communication 150c (eg, relay, integrated IAB (IAB)). access and backhaul), etc.), and may be established through various RATs (eg, 5G NR). The wireless devices 100a to 100f and the base station 200 may transmit/receive wireless signals to each other through the wireless communication/ connections 150a, 150b, and 150c. For example, the wireless communication/ connection 150a , 150b , 150c may transmit/receive signals through various physical channels. To this end, based on the various proposals of the present specification, various configuration information setting processes for transmission/reception of radio signals, various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), and at least a part of a resource allocation process and the like may be performed.

AI refers to a field that studies artificial intelligence or methodologies that can create it, and machine learning (machine learning) refers to a field that defines various problems dealt with in the field of artificial intelligence and studies methodologies to solve them. . Machine learning is also defined as an algorithm that improves the performance of a certain task through constant experience.

A robot can mean a machine that automatically handles or operates a task given by its own capabilities. In particular, a robot having a function of recognizing an environment and performing an operation by self-judgment may be referred to as an intelligent robot. Robots can be classified into industrial, medical, home, military, etc. depending on the purpose or field of use. The robot may be provided with a driving unit including an actuator or a motor to perform various physical operations such as moving the robot joints. In addition, the movable robot includes a wheel, a brake, a propeller, and the like in the driving unit, and can travel on the ground or fly in the air through the driving unit.

Autonomous driving refers to a technology that drives by itself, and an autonomous driving vehicle refers to a vehicle that runs without or with minimal manipulation of a user. For example, autonomous driving includes technology that maintains a driving lane, technology that automatically adjusts speed such as adaptive cruise control, technology that automatically drives along a predetermined route, and technology that automatically sets a route when a destination is set. Technology, etc. may all be included. The vehicle includes a vehicle having only an internal combustion engine, a hybrid vehicle having both an internal combustion engine and an electric motor, and an electric vehicle having only an electric motor, and may include not only automobiles, but also trains, motorcycles, and the like. Autonomous vehicles can be viewed as robots with autonomous driving capabilities.

Expanded reality refers to VR, AR, and MR. VR technology provides only CG images of objects or backgrounds in the real world, AR technology provides virtual CG images on top of the images of real objects, and MR technology provides CG by mixing and combining virtual objects with the real world. it's technology MR technology is similar to AR technology in that it shows both real and virtual objects. However, there is a difference in that in AR technology, a virtual object is used in a form that complements a real object, whereas in MR technology, a virtual object and a real object are used with equal characteristics.

NR supports multiple numerology or subcarrier spacing (SCS) to support various 5G services. For example, when SCS is 15kHz, it supports wide area in traditional cellular band, and when SCS is 30kHz/60kHz, dense-urban, lower latency and wider area are supported. It supports a wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome the phase noise.

The NR frequency band may be defined as two types of frequency ranges (FR1, FR2). The numerical value of the frequency range is subject to change. For example, the frequency ranges of the two types (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range", FR2 may mean "above 6GHz range", and may be referred to as millimeter wave (mmW). have.

Frequency range definition	frequency range	Subcarrier Spacing
FR1	450MHz - 6000MHz	15, 30, 60 kHz
FR2	24250MHz - 52600MHz	60, 120, 240 kHz

As mentioned above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a 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 higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) included in FR1 may include an unlicensed band. The unlicensed band can be used for a variety of purposes, for example, for communication for vehicles (eg, autonomous driving).

Frequency range definition	frequency range	Subcarrier Spacing
FR1	410MHz - 7125MHz	15, 30, 60 kHz
FR2	24250MHz - 52600MHz	60, 120, 240 kHz

Here, the wireless communication technology implemented in the wireless device of the present specification may include narrowband IoT (NB-IoT, narrowband IoT) for low-power communication as well as LTE, NR, and 6G. For example, the NB-IoT technology may be an example of a low power wide area network (LPWAN) technology, and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is not limited to the above-described name. . Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as enhanced MTC (eMTC). For example, LTE-M technology is 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE MTC , and/or 7) may be implemented in at least one of various standards such as LTE M, and is not limited to the above-described name. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may include at least one of ZigBee, Bluetooth, and/or LPWAN in consideration of low-power communication, and limited to the above-mentioned names it is not For example, the ZigBee technology may create personal area networks (PAN) related to small/low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

2 shows an example of a wireless device to which the implementation of the present specification is applied.

Referring to FIG. 2 , the first wireless device 100 and the second wireless device 200 may transmit/receive radio signals to/from an external device through various RATs (eg, LTE and NR).

In FIG. 2, {first wireless device 100 and second wireless device 200} are {wireless devices 100a to 100f and base station 200} in FIG. 1, {wireless device 100a to 100f ) and wireless devices 100a to 100f} and/or {base station 200 and base station 200}.

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 .

Processing chip 101 may include at least one processor, such as processor 102 , and at least one memory, such as memory 104 . In FIG. 2 , the memory 104 is exemplarily shown to be included in the processing chip 101 . Additionally and/or alternatively, the memory 104 may be located external to the processing chip 101 .

The processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 102 may process the information in the memory 104 to generate first information/signal, and transmit a wireless signal including the first information/signal through the transceiver 106 . The processor 102 may receive a wireless signal including the second information/signal through the transceiver 106 , and store information obtained by processing the second information/signal in the memory 104 .

Memory 104 may be operatively coupled to processor 102 . Memory 104 may store various types of information and/or instructions. Memory 104 may store software code 105 that, when executed by processor 102 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. 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 flow diagrams disclosed herein. For example, software code 105 may control processor 102 to perform one or more protocols. For example, software code 105 may control processor 102 to perform one or more air interface protocol layers.

Here, the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR). The transceiver 106 may be coupled to the processor 102 to transmit and/or receive wireless signals via one or more antennas 108 . Each transceiver 106 may include a transmitter and/or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In this specification, 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 .

Processing chip 201 may include at least one processor, such as processor 202 , and at least one memory, such as memory 204 . In FIG. 2 , the memory 204 is exemplarily shown to be included in the processing chip 201 . Additionally and/or alternatively, the memory 204 may be located external to the processing chip 201 .

The processor 202 may control the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information/signal, and transmit a wireless signal including the third information/signal through the transceiver 206 . The processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 , and store information obtained by processing the fourth information/signal in the memory 204 .

Memory 204 may be operatively coupled to processor 202 . Memory 204 may store various types of information and/or instructions. The memory 204 may store software code 205 that, when executed by the processor 202 , implements instructions that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. 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 flow diagrams disclosed herein. For example, software code 205 may control processor 202 to perform one or more protocols. For example, software code 205 may control processor 202 to perform one or more air interface protocol layers.

Here, the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a RAT (eg, LTE or NR). The transceiver 206 may be coupled to the processor 202 to transmit and/or receive wireless signals via one or more antennas 208 . Each transceiver 206 may include a transmitter and/or a receiver. The transceiver 206 may be used interchangeably with the RF unit. In this specification, 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 in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors 102 , 202 . For example, the one or more processors 102 and 202 may include one or more layers (eg, a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, A functional layer such as a radio resource control (RRC) layer and a service data adaptation protocol (SDAP) layer) may be implemented. The one or more processors 102, 202 generate one or more protocol data units (PDUs) and/or one or more service data units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. can do. One or more processors 102 , 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. The one or more processors 102, 202 may configure a signal including a PDU, SDU, message, control information, data or information (eg, a baseband signal) and provide it to one or more transceivers (106, 206). One or more processors 102 , 202 may receive signals (eg, baseband signals) from one or more transceivers 106 , 206 , and may be described, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein. PDU, SDU, message, control information, data or information may be acquired according to

One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, and/or microcomputers. One or more processors 102 , 202 may be implemented by hardware, firmware, software, and/or a combination thereof. For 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), and/or one or more field programmable gates (FPGAs) arrays) may be included in one or more processors 102 , 202 . The descriptions, functions, procedures, suggestions, methods, and/or flow diagrams disclosed herein may be implemented using firmware and/or software, and the firmware and/or software may be implemented to include modules, procedures, functions. . Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flow diagrams disclosed herein may be included in one or more processors 102 , 202 , or stored in one or more memories 104 , 204 . It may be driven by the above processors 102 and 202 . The descriptions, functions, procedures, proposals, methods, and/or flow diagrams disclosed herein may be implemented using firmware or software in the form of code, instructions, and/or sets of instructions.

One or more memories 104 , 204 may be coupled with one or more processors 102 , 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and/or instructions. One or more memories 104, 204 may include read-only memory (ROM), random access memory (RAM), erasable programmable ROM (EPROM), flash memory, hard drives, registers, cache memory, computer readable storage media and/or these may be composed of a combination of One or more memories 104 , 204 may be located inside and/or external to one or more processors 102 , 202 . In addition, one or more memories 104 , 204 may be coupled to one or more processors 102 , 202 through various technologies, such as wired or wireless connections.

One or more transceivers 106, 206 may transmit user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein to one or more other devices. . The one or more transceivers 106, 206 may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein, from one or more other devices. have. For example, one or more transceivers 106 , 206 may be coupled to one or more processors 102 , 202 and may transmit and receive wireless signals. For example, one or more processors 102 , 202 may control one or more transceivers 106 , 206 to transmit user data, control information, wireless signals, etc. to one or more other devices. In addition, one or more processors 102 , 202 may control one or more transceivers 106 , 206 to receive user data, control information, radio signals, etc. from one or more other devices.

One or more transceivers 106 , 206 may be coupled to one or more antennas 108 , 208 . One or more transceivers 106, 206 may be connected via one or more antennas 108, 208 to user data, control information, radio signals/channels referred to in the descriptions, functions, procedures, proposals, methods, and/or flow charts disclosed herein. It may be set to transmit and receive, etc. Herein, the one or more antennas 108 and 208 may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).

The one or more transceivers 106, 206 are configured to process the received user data, control information, radio signals/channels, etc. using the one or more processors 102, 202, such as received user data, control information, radio signals/channels, and the like. etc. can be converted from an RF band signal to a baseband signal. One or more transceivers 106 and 206 may convert user data, control information, radio signals/channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106 , 206 may include (analog) oscillators and/or filters. For example, one or more transceivers 106, 206 up-convert OFDM baseband signals to OFDM signals via (analog) oscillators and/or filters under the control of one or more processors 102, 202; , an up-converted OFDM signal may be transmitted at a carrier frequency. One or more transceivers 106, 206 receive the OFDM signal at the carrier frequency and down-convert the OFDM signal to an OFDM baseband signal through an (analog) oscillator and/or filter under the control of one or more processors 102, 202. can be down-converted.

In the implementation of the present specification, the UE may operate as a transmitting device in an uplink (UL) and a receiving device in a downlink (DL). In the implementation of the present specification, the base station may operate as a receiving device in the UL and a transmitting device in the DL. Hereinafter, for technical convenience, it is mainly assumed that the first wireless device 100 operates as a UE and the second wireless device 200 operates as a base station. For example, a processor 102 coupled to, mounted on, or shipped with the first wireless device 100 may perform UE operations in accordance with implementations of the present disclosure or may configure the transceiver 106 to perform UE operations in accordance with implementations of the present disclosure. can be configured to control. A processor 202 coupled to, mounted on, or shipped to the second wireless device 200 is configured to perform a base station operation according to an implementation of the present specification or to control the transceiver 206 to perform a base station operation according to an implementation of the present specification. can be

In this specification, a base station may be referred to as a Node B (Node B), an eNode B (eNB), or a gNB.

3 shows an example of a wireless device to which the implementation of the present specification is applied.

The wireless device may be implemented in various forms according to usage examples/services (refer to FIG. 1 ).

Referring to FIG. 3 , the wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 2 , and may be configured by various components, devices/parts and/or modules. For example, each wireless device 100 , 200 may include a communication device 110 , a control device 120 , a memory device 130 , and an additional component 140 . The communication device 110 may include communication circuitry 112 and a transceiver 114 . For example, communication circuitry 112 may include one or more processors 102 , 202 of FIG. 2 and/or one or more memories 104 , 204 of FIG. 2 . For example, transceiver 114 may include one or more transceivers 106 , 206 of FIG. 2 and/or one or more antennas 108 , 208 of FIG. 2 . The control device 120 is electrically connected to the communication device 110 , the memory device 130 , and the additional component 140 , and controls the overall operation of each wireless device 100 , 200 . For example, the control device 120 may control the electrical/mechanical operation of each of the wireless devices 100 and 200 based on the program/code/command/information stored in the memory device 130 . The control device 120 transmits the information stored in the memory device 130 to the outside (eg, other communication devices) through the communication device 110 through the wireless/wired interface, or the communication device ( 110), information received from the outside (eg, other communication devices) may be stored in the memory device 130 .

The additional component 140 may be variously configured according to the type of the wireless device 100 or 200 . For example, the additional component 140 may include at least one of a power unit/battery, an input/output (I/O) device (eg, an audio I/O port, a video I/O port), a drive unit, and a computing device. can The wireless devices 100 and 200 include, but are not limited to, a robot (100a in FIG. 1 ), a vehicle ( 100b-1 and 100b-2 in FIG. 1 ), an XR device ( 100c in FIG. 1 ), and a portable device ( FIG. 1 ). 100d), home appliances (100e in FIG. 1), IoT devices (100f in FIG. 1), digital broadcast terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices , a climate/environmental device, an AI server/device (400 in FIG. 1 ), a base station (200 in FIG. 1 ), and a network node may be implemented. The wireless devices 100 and 200 may be used in a moving or fixed location according to usage examples/services.

In FIG. 3 , all of the various components, devices/parts and/or modules of the wireless devices 100 and 200 may be connected to each other via a wired interface, or at least some of them may be wirelessly connected via the communication device 110 . For example, in each of the wireless devices 100 and 200 , the control device 120 and the communication device 110 are connected by wire, and the control device 120 and the first device (eg, 130 and 140 ) are communication devices. It may be connected wirelessly through 110 . Each component, device/portion and/or module within the wireless device 100, 200 may further include one or more elements. For example, the control device 120 may be configured by one or more processor sets. For example, the control device 120 may be configured by a set of a communication control processor, an application processor (AP), an electronic control unit (ECU), a graphic processing device, and a memory control processor. As another example, the memory device 130 may be configured by RAM, DRAM, ROM, flash memory, volatile memory, non-volatile memory, and/or a combination thereof.

4 shows an example of a UE to which the implementation of the present specification is applied.

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

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

The processor 102 may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. The processor 102 may be configured to control one or more other components of the UE 100 to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. A layer of air interface protocol may be implemented in the processor 102 . Processor 102 may include an ASIC, other chipset, logic circuitry, 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), and a modem (modulator and demodulator). Examples of processor 102 SNAPDRAGON ^TM series made from Qualcomm® processor, EXYNOS ^TM series made from Samsung® processor, A series of processors made from Apple®, HELIO ^TM series processor made in MediaTek®, ATOM ^TM series processors made from Intel® or in the corresponding next-generation processor.

The memory 104 is operatively coupled to the processor 102 and stores various information for operating the processor 102 . Memory 104 may include ROM, RAM, flash memory, memory cards, storage media, and/or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (eg, procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams disclosed herein. have. Modules may be stored in memory 104 and executed by processor 102 . The memory 104 may be implemented within the processor 102 or external to the processor 102 , in which case it may be communicatively coupled with the processor 102 through various methods known in the art.

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

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

The display 114 outputs the result processed by the processor 102 . Keypad 116 receives input for use by processor 102 . The keypad 116 may be displayed on the display 114 .

The SIM card 118 is an integrated circuit for securely storing an international mobile subscriber identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone or computer. You can also store contact information on many SIM cards.

The speaker 120 outputs sound related results processed by the processor 102 . Microphone 122 receives sound related input for use by processor 102 .

5 shows an example of a 5G system architecture to which the implementation of the present specification is applied.

The 5G system (5GS; 5G system) structure consists of the following network functions (NFs).

- AUSF (Authentication Server Function)

- AMF (Access and Mobility Management Function)

- DN (Data Network), e.g. operator services, Internet access or third-party services

- USDF (Unstructured Data Storage Function)

- NEF (Network Exposure Function)

- I-NEF (Intermediate NEF)

- NRF (Network Repository Function)

- NSSF (Network Slice Selection Function)

- PCF (Policy Control Function)

- SMF (Session Management Function)

- UDM (Unified Data Management)

- UDR (Unified Data Repository)

- UPF (User Plane Function)

- UCMF (UE radio Capability Management Function)

- AF (Application Function)

- UE (User Equipment)

- (R)AN ((Radio) Access Network)

- 5G-EIR (5G-Equipment Identity Register)

- NWDAF (Network Data Analytics Function)

-CHF (Charging Function)

In addition, the following network functions may be considered.

- N3IWF (Non-3GPP InterWorking Function)

- TNGF (Trusted Non-3GPP Gateway Function)

- W-AGF (Wireline Access Gateway Function)

5 shows the 5G system structure of a non-roaming case using a reference point representation that shows how various network functions interact with each other.

In FIG. 5 , UDSF, NEF and NRF are not described for the sake of clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF and NRF as needed.

For clarity, the connection between UDRs and other NFs (eg PCFs) is not shown in FIG. 5 . For clarity, the connection between NWDAF and other NFs (eg PCF) is not shown in FIG. 5 .

The 5G system architecture includes the following reference points.

- N1: the reference point between the UE and the AMF.

- N2: the reference point between (R)AN and AMF.

- N3: Reference point between (R)AN and UPF.

- N4: reference point between SMF and UPF.

- N6: the reference point between the UPF and the data network.

- N9: reference point between two UPFs.

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

- N5: Reference point between PCF and AF.

- N7: reference point between SMF and PCF.

- N8: Reference point between UDM and AMF.

- N10: reference point between UDM and SMF.

- N11: reference point between AMF and SMF.

- N12: reference point between AMF and AUSF.

- N13: reference point between UDM and AUSF.

- N14: the reference point between the two AMFs.

- N15: Reference point between PCF and AMF in case of non-roaming scenario, and reference point between PCF and AMF of visited network in case of roaming scenario.

- N16: reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

- N22: reference point between AMF and NSSF.

In some cases, it may be necessary to connect two NFs to each other to service the UE.

Discussion is underway to formally support support for multiple universal subscriber identification module (USIM) devices in 3GPP. The multi-USIM may be referred to as a MUSIM. In order to support multiple USIM devices, the following needs to be discussed.

- Mechanism for handling MT (mobile terminated) service directed to USIM A while the UE is actively communicating with USIM B

- A mechanism to allow coordinated leaving and resumption of an in-progress connection in the 3GPP system associated with USIM A: the UE temporarily leaves the 3GPP system associated with USIM B, and is associated with USIM A in a network-controlled manner You can go back to the 3GPP system. At this time, it is necessary to discuss how the network handles the occurrence of MT data or MT control plane activity in a suspended connection.

- Mechanism to enable paging reception on multi-USIM devices

- Handling of service priority: That is, it needs to be discussed whether the operation of the UE receiving the paging information is determined by the USIM configuration, user preference, or both.

A discussion for supporting a multi-USIM device may be limited to a multi-SIM device having a single Rx (reception)/single Tx (transmission) and dual Rx/single Tx.

A discussion for supporting a multi-USIM device may be common to 5GS and an evolved packet system (EPS). That is, a problem to be solved for supporting a multi-USIM device may be common to 5GS and EPS. Accordingly, the discussion for supporting multi-USIM devices can be applied to both 5GS and EPS. However, the solution in 5GS and the solution in EPS need not be the same.

The discussion for supporting a multi-USIM device may be applied when the same mobile network operator (MNO) or different MNOs have a plurality of USIMs.

The discussion for supporting multi-USIM devices can be applied to DR mode (single USIM) interworking between 5GS and EPS.

As described above, coordinated departure of multi-USIM devices needs to be discussed in order to support multi-USIM devices. Reference may be made to S5.3, S6.4 and S6.5 of 3GPP TR 23.761 V0.3.0. The coordinated departure of the multi-USIM device may be referred to as a key issue 3 for supporting the multi-USIM device.

It is assumed that multiple USIM devices are associated with multiple USIMs and are registered at the same time. While actively communicating with a system associated with one USIM (i.e., the current system), a multi-USIM device may determine that it needs to perform some action (eg, responding to a paging, performing a mobility update) on a system associated with another USIM. .

Currently, if there is no procedure for notifying the network, the multi-USIM device may automatically leave or release the RRC connection with the current system. This is likely to be interpreted by the current system as a case of error, likely to skew statistics in the current system, and misguide algorithms that rely on it. In addition, if the UE cannot receive downlink data or process paging in the current system while the multi-USIM device leaves the current system, resources may be wasted. Therefore, the following needs to be discussed.

- A method of preventing a multi-USIM device from wasting network resources while leaving the current 3GPP system through coordination with the network

- How the network handles MT data or MT control plane activity while multi-USIM devices are leaving

For coordinated departure of multi-USIM devices, two solutions can be proposed. Each solution may be called solution #4 and solution #5.

(1) Solution #4: NAS-triggered RRC disconnection

NAS-triggered RRC disconnection may be proposed to avoid wasting network resources and ensure synchronization between the UE and the network. The release of these resources may be guaranteed by the synchronized local resource release at the UE and the network side triggered by the transmission/reception of a UE NAS message having a specific indicator.

This solution can be applied to both EPS and 5GS.

This solution provides a mechanism for the UE to instruct the network in the NAS that the UE is switching from the current system to another system, and thus the resources for this UE should be released. An indicator for this may be provided by the UE in a UL NAS TRANSPORT message (5GS) / UPLINK GENERIC NAS TRANSPORT message (EPS).

- After transmitting the indicator, the UE locally releases the RRC connection and transitions to the RRC_IDLE state and the CM_IDLE/ECM_IDLE state.

- Upon receiving the indicator from the UE, the AMF (5GC) or MME (EPC) triggers the AN release procedure (5GS) or the S1 release procedure (EPS) with a specific cause value, to the RAN N2 UE release context command message (5GS) or S1-AP: S1 UE Context Release Command Message (EPS) is sent.

- Upon receiving the specific cause value, the RAN triggers the release of the local RRC connection, and informs the AMF (5GC) or the MME (EPC).

- AMF (5GC) or MME (EPC) proceeds with the remaining steps of the AN release procedure (5GS) or the S1 release procedure (EPS).

The above mechanism ensures that a handshake between the UE and the network is not required, thus minimizing the time required for the UE to switch to another system from the moment the UE leaves the current system.

(2) Solution #5: Exit and Resume Solution

This solution aims to cover the following use cases where the UE leaves the system for various periods of time.

- The UE sends/receives short message service (SMS) in the target system, or to perform periodic registration/tracking area update0 (TAU), or to identify the caller of an incoming call, for example 100-500ms In case of departure for a short period of

- when the UE leaves the target system to make a call, eg for a long period of several minutes

One design principle of this solution is to minimize the signaling required for coordinated exits, including exits and returns, and to minimize disruption of service on the source system.

This solution can be applied to both EPS and 5GS.

For single-receiver multi-USIM devices, if USIM1 is registered with the 3GPP system (eg PLMN 1) and it decides to establish a connection to USIM2 in the 3GPP system (eg PLMN 2), a short stay in PLMN 2 ( eg: MT service page response) or long-term; In contrast, UE (USIM1) notifies PLMN1 that UE (USIM1) is leaving, and PLMN1 may stop a specific DL service for UE (USIM1).

The USIM of the UE/multi-USIM device may initially be separately registered with each PLMN.

The exit procedure may be initiated at the NAS level or the AS level. The UE (USIM) may provide MUSIM release assistance information (RAI) to the network to help the MT service delivery of the network.

When UE/USIM2 terminates service in PLMN 2 or receives a notification (eg paging or NAS level notification) indicating that there is a higher priority MT service in PLMN 1, the UE sends to UE/USIM 1 in PLMN 1 service can be resumed.

The service resumption procedure may also be performed at the NAS level or the AS level. This may be a normal existing resume procedure (eg NAS service request or RRC resume).

The impact on each entity according to this solution is as follows.

1) SMF:

- After receiving the MT data processing information based on the release support information from the UE as an N11 message, the PDU session processing method is determined

- Initiated MT data processing guidelines to UPF

- Initiate general MT data processing guidelines for return instruction reception and UPF

2) UPF:

- Block DL data transmission at the request of MF

3) AMF:

- Receive release support information from UE via NAS or RAN via N2 message

- Provides NAS response to UE

- Provides MT data processing information to SMF based on release support information from UE

4) NG-RAN:

- Supports UE-initiated RRC departure procedure with release support information

- Provides release support information to AMF

- Transmits an RRC response message to the UE

5) UE:

- Supports NAS exit procedure with release support information

- Supports the RRC departure process with release support information

- Support NAS resume procedure

- Support RRC resume procedure

NAS level congestion control will be described. Refer to S5.19.7.2 of 3GPP TS 23.501 V16.3.0.

NAS level congestion control is to prevent the UE from transmitting NAS signaling first while a mobility management back-off timer (hereinafter, simply referred to as a back-off timer) is operating in a network congestion situation. The value of the backoff timer may be differently allocated by the core network for each UE.

More specifically, in a general overload condition, the AMF may reject the NAS message from the UE using 5G-AN. If the NAS request is rejected, the AMF may send the value of the backoff timer to the UE. While the backoff timer is running, the UE cannot initiate any NAS requests except for deregistration procedures, procedures not affected by congestion control (eg high priority access, emergency services) and mobile termination services. can't After this procedure, the backoff timer continues to run. While the backoff timer is running, if the UE is already in the CM-CONNECTED state, a mobility registration update may be performed. If the UE receives a paging request or NAS notification message from the AMF while the backoff timer is running, the UE stops the backoff timer and service request procedure or mobility through 3GPP connection and/or non-3GPP connection Start the registration update process. On a non-3GPP connection, if the UE is in the CM-IDLE state when the backoff timer is stopped, the UE initiates a service request procedure that is triggered to the UE as soon as it is switched back to the CM-CONNECTED state.

In order for the UE to report a PS (packet-swithed) data off state change in the PDU session modification request, the UE operates as follows while the backoff timer operates.

- If the UE is in the CM-IDLE state and has not moved out of the registration area, the UE may send a service request message with an indication that the message is excluded from NAS level congestion control. When the UE is in CM-IDLE state and out of the registration area, the UE may send a mobility registration update request message with a follow-on request and an indication that the message is excluded from NAS level congestion control.

- When the UE is in the CM-CONNECTED state, the UE transmits a PDU session modification request message through a UL NAS delivery message along with an indication that the PS data off state change and the corresponding message are excluded from NAS level congestion control.

When NAS level congestion control is activated in AMF, if the UE indicates that the NAS MM message is excluded from NAS level congestion control, AMF does not reject the NAS MM message, indicating that the NAS SM message is excluded from NAS level congestion control Sends the NAS SM message along with the instruction to the corresponding SMF. SMF verifies that NAS SM messages are not subject to congestion control. Otherwise, the SMF rejects the message. For example, the SMF may reject the received PDU session modification if it is not a data off status report.

Backoff timer does not affect cell/RAT/connection type/PLMN change. Changing the cell/RAT/TA/connection type does not stop the backoff timer. The backoff timer does not trigger PLMN reselection. When accessing a new PLMN other than the equivalent PLMN, the backoff timer is stopped.

To prevent a large number of UEs from initiating delayed requests (nearly) simultaneously, the AMF chooses the value of the backoff timer so that the delayed requests are out of sync.

When the UE needs to report a 5GSM Core Network Capability change or Always-on PDU Session Requested indication when the backoff timer is running, the UE determines that the backoff timer has expired. Delay the relevant MM signaling until the time of the backoff timer expires and then start.

For a UE with a reserved communication pattern, the AMF may consider the UE's communication pattern when selecting the backoff timer value, thereby ensuring that the UE does not miss the reserved communication window.

AMF shall not reject the registration request message for mobility registration update performed when the UE is already in the CM-CONNECTED state.

The AMF may reject the service request message and UL NAS transmission according to the backoff timer when the UE is already in the CM-CONNECTED state. If the UE receives a DL NAS transmission message from AMF while the backoff timer is running, the UE stops the backoff timer.

In case of movement in the CM-IDLE state, the AMF may reject the registration request message for mobility registration update by including the value of the backoff timer in the registration rejection message.

When a UE registered in the same PLMN for 3GPP and non-3GPP connections receives the value of the backoff timer from the AMF, the backoff timer (and each start and stop of the backoff timer) is applied to both 3GPP and non-3GPP connections. The same applies. When a UE registered in a different PLMN for 3GPP connection and non-3GPP connection receives a value of the backoff timer from the AMF, the backoff timer is applied only to the PLMN that provided the value of the corresponding backoff timer to the UE.

When the AMF rejects the registration request message or service request according to the backoff timer having a value greater than the sum of the UE's periodic registration update timer and the implicit deregistration timer, the AMF The registration update timer and/or the implicit deregistration timer should be adjusted so that the AMF does not implicitly deregister the UE while the backoff timer is running. This is to minimize signaling after the backoff timer expires.

As described above, in order to support coordinated departure of multi-USIM devices, both solutions (ie, solutions #4 and #5) cause the UE to send a NAS MM message to the network so that the UE leaves the current network. (and/or moving to another network). This allows the current network to recognize that the UE is leaving the current network (and/or moving to another network), and accordingly does not stop data transmission to the UE or perform unnecessary actions (eg paging), etc. Operations for efficiently using network resources may be performed.

However, NAS MM messages announcing that the UE is leaving the current network (and/or moving to another network) may be subject to NAS level congestion control. That is, a UE configured for NAS level congestion control may not be able to transmit a NAS MM message informing that the UE is leaving the current network (and/or moving to another network) while the backoff timer is running. If the UE fails to inform that it is leaving the current network (and/or moving to another network) due to NAS level congestion control, the network does not know that the UE has moved to another network and takes additional actions to find the UE (e.g.: retransmission, paging, etc.). Accordingly, network resources may be wasted.

According to the implementation of the present specification, a message transmitted by a multi-USIM device to terminate a connection with a system with which it is currently connected is transmitted exceptionally even in a NAS level congestion control situation (ie, while the backoff timer is operating) make it possible For this, a specific request type, service type, or indicator may be utilized.

According to the implementation of the present specification, two or more USIMs (eg, USIM1, USIM2) may be mounted in a UE, and each USIM may be registered in a different network. The different networks are different in the case of different PLMNs (e.g., PLMN1, PLMN2) on the same system (i.e., 5GS or EPS), in the case of the same PLMN on different systems (i.e., 5GS and another EPS), All cases of the same PLMN on the same system may be included. For example, the first network registered by the UE may be PLMN1, and the second network registered by the UE may be PLMN2. USIM1 may be connected to PLMN1, and the UE terminates this current connection and attempts to perform a specific operation (eg, paging response, mobility registration update, etc.) by connecting with PLMN2 through USIM2. On the other hand, NAS level congestion control is applied to PLMN1, so a general NAS MM message transmitted by the UE may be rejected by the AMF. If USIM1 and USIM2 correspond to the same system and are USIMs belonging to the same PLMN, registration can be performed independently as if they were different PLMNs.

According to the implementation of the present specification, even in a NAS level congestion control situation in PLMN1, a multi-USIM device may perform a procedure for terminating a connection with a currently connected system and notify the currently connected system. Terminating the connection with the currently connected system means leaving the system/network registered using USIM1 (ie PLMN1) and/or registering using USIM2 on the system/network registered using USIM1 (ie PLMN1). It may mean moving to the existing system/network (ie, PLMN2).

The following drawings were created to explain a specific example of the present specification. Since the names of specific devices described in the drawings or the names of specific signals/messages/fields are presented by way of example, the technical features of the present specification are not limited to the specific names used in the following drawings.

6 shows an example of a method performed by a wireless device to which the implementation of the present specification is applied.

In step S600, the wireless device performs registration with the first network and the second network.

In step S610, the wireless device communicates with the first network among the first network and the second network.

In step S620, the wireless device receives information related to a backoff timer for congestion control from the AMF in the first network.

In step S630, the wireless device operates the back-off timer.

In step S640, the wireless device decides to leave the first network.

In step S650, while the back-off timer is running, the wireless device transmits a NAS message including information indicating to leave the first network to the AMF in the first network.

In some implementations, the information indicating leaving the first network may correspond to a request type and/or a service type in the NAS message. Alternatively, the information indicating to leave the first network is a newly defined indicator in the NAS message, and the request type and/or service type in the NAS message may be set to "elevated siganlling" and/or "signalling". .

In some implementations, the NAS message may include release help information for MT data processing of the PDU session.

In some implementations, the backoff timer may continue to operate even after sending the NAS message.

In some implementations, in response to the NAS message, a NAS accept message may be received from an AMF in the first network. The NAS accept message may include at least one of an indicator allowing the wireless device to leave the first network and/or a value of the backoff timer.

In some implementations, after leaving the first network, it can communicate with the second network. The communication with the second network may include a paging response and/or a mobility registration update.

In some implementations, the wireless device may be a multi-USIM device having multiple USIMs. The registration to the first network may be associated with a first USIM of the plurality of USIMs, and the registration to the second network may be associated with a second USIM of the plurality of USIMs. Also, the first network may be associated with a first PLMN, and the second network may be associated with a second PLMN. Also, the first network and the second network may correspond to different systems among 5G system EPS or may correspond to the same system.

In some implementations, the wireless device may communicate with at least one of a mobile device, a network, and/or an autonomous vehicle other than the wireless device.

In addition, the method described in terms of the wireless device in FIG. 6 is configured to 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 . can be performed by

More specifically, a wireless device includes one or more transceivers, one or more processors, and one or more memories operably coupled with the one or more processors. The one or more memories store instructions to cause a next operation to be performed by the one or more processors.

The operation includes performing registration with the first network and the second network.

The operation includes performing communication with the first network of the first network and the second network.

The operation includes receiving information related to a backoff timer for congestion control from an AMF in the first network.

The operation includes operating the backoff timer.

The operation includes determining to leave the first network.

The operation includes transmitting a NAS message including information indicating to leave the first network to the AMF in the first network while the backoff timer is running.

In some implementations, the information indicating leaving the first network may correspond to a request type and/or a service type in the NAS message. Alternatively, the information indicating to leave the first network is a newly defined indicator in the NAS message, and the request type and/or service type in the NAS message may be set to "elevated siganlling" and/or "signalling". .

In some implementations, the NAS message may include release help information for MT data processing of the PDU session.

In some implementations, the backoff timer may continue to operate even after sending the NAS message.

In some implementations, in response to the NAS message, a NAS accept message may be received from an AMF in the first network. The NAS accept message may include at least one of an indicator allowing the wireless device to leave the first network and/or a value of the backoff timer.

In some implementations, after leaving the first network, it can communicate with the second network. The communication with the second network may include a paging response and/or a mobility registration update.

In some implementations, the wireless device may be a multi-USIM device having multiple USIMs. The registration to the first network may be associated with a first USIM of the plurality of USIMs, and the registration to the second network may be associated with a second USIM of the plurality of USIMs. Also, the first network may be associated with a first PLMN, and the second network may be associated with a second PLMN. Also, the first network and the second network may correspond to different systems among 5G system EPS or may correspond to the same system.

In addition, the method described from the perspective of the wireless device in FIG. 6 is control of the processor 102 included in the first wireless device 100 shown in FIG. 2 , and communication included in the wireless device 100 shown in FIG. 3 . It may be performed by the control of the device 110 and/or the control device 120 and/or the control of the processor 102 included in the UE 100 illustrated in FIG. 4 .

More specifically, an apparatus operating in a wireless communication system includes one or more processors and one or more memories operably coupled with the one or more processors. the one or more processors perform registration with a first network and a second network, obtain information related to a backoff timer for congestion control, operate the backoff timer, determine to leave the first network, , while the backoff timer is running, generating a NAS message including information instructing to leave the first network.

Further, the method described in terms of the wireless device in FIG. 6 may be performed by the 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 specification may be implemented directly in hardware, in software executed by a processor, or a combination of the two. For example, in wireless communication, a method performed by a wireless device may be implemented in hardware, software, firmware, or a combination thereof. For example, the software may reside in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or other storage medium.

Some examples of a storage medium may be coupled to the processor such that the processor can read information from the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and storage medium may be in the ASIC. In another example, the processor and the storage medium may exist as separate components.

Computer-readable media may include tangible, non-transitory computer-readable storage media.

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

Further, the methods described herein may be realized, at least in part, by computer readable communication media that carry or communicate code in the form of instructions or data structures and which a computer can access, read and/or execute.

According to some implementations herein, a non-transitory computer-readable medium (CRM) stores a plurality of instructions.

More specifically, CRM stores instructions that cause actions to be performed by one or more processors. The operation is to perform registration with a first network and a second network, obtain information related to a backoff timer for congestion control, run the backoff timer, decide to leave the first network, and and generating a NAS message including information indicating to leave the first network while the off timer is running.

7 shows an example of a procedure for leaving a network to which an implementation of the present specification is applied.

(1) Step S700: UE performs registration with PLMN1 using USIM1. The UE may transmit an indicator (eg, a MUSIM support indicator) indicating that the UE supports multi-USIM in the registration request message. PLMN1 may determine whether to approve the MUSIM function of the UE in consideration of subscription information, operator configuration, and the like. When the MUSIM function of the corresponding UE is approved, an indicator (eg, MUSIM supporter) indicating that the MUSIM function of the corresponding UE is approved may be included in the registration accept message transmitted to the UE.

(2) Step S702: The UE uses USIM2 to register with PLMN2 in the same manner as in step S700.

Even if PLMN2 does not support the MUSIM function and only PLMN1 supports the MUSIM function, the same procedure may be performed as follows.

(3) Step S704: The UE receives NAS level congestion control from PLMN1. For example, when the UE transmits a service request, the AMF of PLMN1 (ie, AMF1) may transmit the value of the backoff timer while rejecting the service request. The UE cannot transmit general NAS signaling except for emergency services while the backoff timer is running.

(4) step S706: while the backoff timer is running, the UE performs a specific operation (eg, paging response, mobility registration update, MO service, etc.) with PLMN2, MM NAS including a leave indication Sends the message to PLMN1 (eg AMF1) with which it is currently connected.

That is, since the NAS level congestion control is applied, the backoff timer may be in operation, and the MM NAS message including the leave instruction may be transmitted as an exception while ignoring the backoff timer. Even after transmitting the MM NAS message including the leave indication, the backoff timer may continue to operate.

The departure indication may be interpreted as a message/information used by the UE to inform leaving the corresponding network/system/PLMN or a message/information used by the UE to inform that the UE moves/moves to another network/system/PLMN.

The MM NAS message may be a service request message, a UL NAS delivery message, or a newly defined NAS message. The request type and/or service type of the MM NAS message (eg, a service type information element (IE) in the case of a service request message) may be set as a request type and/or a service type indicating a departure indication. For example, a request type and/or a service type indicating a departure indication may be “MUSIM release request”. The MM NAS message may include release help information to help process MT data of the PDU session.

AMF1 may not reject the corresponding MM NAS message when the MM NAS message transmitted by the UE includes a leave indication even if the UE is in a congestion control situation. For example, when a "MUSIM release request" is detected by checking the service type of the service request, the corresponding service request may not be rejected. Not rejecting the MM NAS message may be interpreted as not applying congestion control.

Alternatively, while the backoff timer is operating, the UE may additionally include information requesting to allow an exception to the congestion control operation while transmitting the MM NAS message. For example, the request type and/or service type may be set to the conventional "elevated signaling", and a departure indication may be additionally transmitted. In this case, the AMF may not apply congestion control to a message in which the request type and/or service type is set to "elevated signaling". As information requesting that an exception be allowed for congestion control operation, conventional "elevated signaling" may be used, or newly defined information (eg, "message was exempted from congestion control", etc.) may be used.

Alternatively, the request type and/or service type may be set to "signaling", and a departure instruction may be additionally transmitted. In this case, the AMF may not apply congestion control exceptionally to a signaling type NAS message including a departure indication.

(4) Step S708: AMF1 sends an N2 message to RAN1.

The N2 message may include a NAS acceptance message (eg, service acceptance) to be transmitted to the UE. AMF1 may transmit an indicator meaning allowing the UE to leave PLMN1 together with the NAS accept message. AMF1 may transmit the NAS accept message including the value of the backoff timer. This is to apply congestion control to the UE since AMF1 is still in a congestion control situation. In addition, the N2 message may include a release indicator (release indicator).

(5) Step S710: When the N2 message includes a release indicator, the RAN1 transmits an RRC release message to the UE to release the RRC connection with the UE. When the AMF also transmits the NAS accept message to be transmitted to the UE, the RAN1 may perform RRC connection release after transmitting the NAS accept message to the terminal before performing RRC connection release. Alternatively, the RRC release message may include a NAS accept message. If the NAS accept message includes the value of the backoff timer, the UE starts the backoff timer.

(6) Step S712: AMF invokes Nsmf_PDUSession_UpdateSMContext request toward SMF1 to deactivate an activated PDU session for the UE that has transmitted the MUSIM release request. The N11 message for the Nsmf_PDUSession_UpdateSMContext request may include a PDU session ID, a cause, an operation type, release help information, and the like. The cause may be "MUSIM release request", and the operation type may be set to "UP deactivate". The cause may be a separate IE instead of "request MUSIM release". Alternatively, based on the N11 message including the release assistance information, it may implicitly indicate that the UE has transmitted the MUSIM release request.

(7) Step S714: SMF1 and UPF1 perform N4 session modification. That is, SMF1 and UPF1 may release the N3 tunnel of the PDU session by exchanging an N4 session modification request/response.

SMF1 may determine how to process MT data in the future by considering the release assistance information, subscriber information, operator configuration, etc. received in step S712. For example, SMF1 may instruct UPF1 to discard or buffer MT data.

(8) Step S716: In response to step S712, the SMF1 transmits an N11 message corresponding to the Nsmf_PDUSession_UpdateSMContext response to the AMF1.

(9) Step S718: When the RRC connection between USIM1 and PLMN1 is released, the UE may perform an operation for receiving a service from PLMN2 through USIM2. For example, when a paging or NAS notification is received, or an MO service is executed, a service request procedure may be performed. Alternatively, a mobility registration update procedure may be performed for mobility update.

The present specification may have various effects.

For example, even in a NAS level congestion control situation, the multi-USIM device may transmit a NAS MM message including a departure instruction to a currently connected system.

For example, a system to which multi-USIM devices are currently connected can effectively utilize resources allocated to the multi-USIM devices in other places without wasting it.

Effects that can be obtained through specific examples of the present specification are not limited to the effects listed above. For example, various technical effects that a person having ordinary skill in the related art can understand or derive from this specification may exist. Accordingly, the specific effects of the present specification are not limited to those explicitly described herein, and may include various effects that can be understood or derived from the technical characteristics of the present specification.

The claims described herein may be combined in various ways. For example, the technical features of the method claims of the present specification may be combined and implemented as an apparatus, and the technical features of the apparatus claims of the present specification may be combined and implemented as a method. In addition, the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined to be implemented as an apparatus, and the technical features of the method claim of the present specification and the technical features of the apparatus claim may be combined and implemented as a method. Other implementations are within the scope of the following claims.

Claims (16)

1. A method performed by a wireless device operating in a wireless communication system, comprising:

   performing registration with the first network and the second network;

   performing communication with the first network among the first network and the second network;

   receiving information related to a backoff timer for congestion control from an access and mobility management function (AMF) in the first network;

   operating the back-off timer;

   determining to leave the first network;

   while the backoff timer is running, transmitting a non-access stratum (NAS) message including information indicating to leave the first network to the AMF in the first network.
2. The method of claim 1,

   The information indicating leaving the first network corresponds to a request type and/or a service type in the NAS message.
3. The method of claim 1,

   The information indicating to leave the first network is an indicator newly defined in the NAS message,

   A method characterized in that the request type and/or service type in the NAS message is set to "elevated signaling" and/or "signalling".
4. The method of claim 1,

   The method of claim 1, wherein the NAS message includes release assistance information for processing mobile terminating (MT) data of a protocol data unit (PDU) session.
5. The method of claim 1,

   The method, characterized in that even after transmitting the NAS message, the backoff timer continues to operate.
6. The method of claim 1,

   In response to the NAS message, the method further comprising: receiving a NAS accept message from the AMF in the first network.
7. 7. The method of claim 6,

   The NAS accept message includes at least one of an indicator allowing the wireless device to leave the first network and/or a value of the backoff timer.
8. The method of claim 1,

   after leaving the first network, further comprising communicating with the second network;

   The method of claim 1, wherein the communication with the second network includes a paging response and/or a mobility registration update.
9. The method of claim 1,

   The method of claim 1, wherein the wireless device is a multi-USIM device having a plurality of universal subscriber identification modules (USIMs).
10. 10. The method of claim 9,

    The registration with the first network is associated with a first USIM among the plurality of USIMs;

    and the registration with the second network is associated with a second USIM of the plurality of USIMs.
11. The method of claim 1,

    The first network is associated with a first public land mobile network (PLMN),

    The second network is associated with a second PLMN.
12. The method of claim 1,

    The first network and the second network correspond to different systems of a 5G system or an evolved packet system (EPS), or correspond to the same system.
13. The method of claim 1,

    wherein the wireless device communicates with at least one of a mobile device, a network and/or an autonomous vehicle other than the wireless device.
14. A wireless device operating in a wireless communication system, comprising:

    one or more transceivers;

    one or more processors; and

    one or more memories operably coupled with the one or more processors;

    The one or more memories,

    performing registration with the first network and the second network;

    performing communication with the first network among the first network and the second network;

    receiving information related to a backoff timer for congestion control from an access and mobility management function (AMF) in the first network;

    operating the back-off timer based on;

    determining to leave the first network;

    while the backoff timer is running, transmitting a non-access stratum (NAS) message including information indicating to leave the first network to the AMF in the first network;

    and storing instructions for causing an operation comprising: to be performed by the one or more processors.
15. A device operating in a wireless communication system, comprising:

    one or more processors; and

    one or more memories operably coupled with the one or more processors;

    The one or more processors,

    performing registration with the first network and the second network;

    obtaining information related to a backoff timer for congestion control;

    operating the back-off timer;

    determining to leave the first network;

    and generating, while the backoff timer is running, a non-access stratum (NAS) message comprising information indicating to leave the first network.
16. A computer readable medium (CRM) storing instructions to cause an operation to be performed by one or more processors, the operation comprising:

    performing registration with the first network and the second network;

    obtaining information related to a backoff timer for congestion control;

    operating the back-off timer;

    determining to leave the first network;

    and generating a non-access stratum (NAS) message including information indicating to leave the first network while the backoff timer is running.

Images