KR20210098845A - METHODS FOR PERFORMING COMMUNICATION USING MULTIPLE USIMs AND APPARATUSES THEREOF - Google Patents

Abstract

The present disclosure proposes a method and apparatus for performing communication by user equipment (UE) with multiple USIMs that are in operation at the same time. In one aspect, the present disclosure provides a method for UE to perform communication using multiple USIMs, which includes the steps of: determining one or more networks in a connected state to be cancelled, in a state of being concurrently registered in one or more networks associated with a plurality of USIMs; transmitting assistance information for instructing cancellation, to a base station or a core network control plane entity; and monitoring a paging message based on the assistance information.

Description

A method for performing communication using a plurality of SIMs and an apparatus therefor

The present disclosure proposes a method and apparatus for performing communication by a UE with multiple USIMs that are in operation at the same time.

A user using a communication terminal may use two or more USIMs in one terminal. Two or more SIMs can be configured to use networks operated by different operators. Alternatively, two or more SIMs may be configured to use different services operated by one operator.

In addition, according to various communication environments and terminal characteristics, data may be simultaneously transmitted/received using two or more SIMs, or data may be transmitted/received sequentially.

As such, a plurality of SIMs may be configured and used in a single terminal for various purposes.

However, when two or more SIMs are used, the paging error of the terminal may overlap or the state of the terminal may be set differently for each SIM. In addition, when data transmission/reception using two or more SIMs overlaps or when a specific event occurs at an overlapping time, data service through one or more networks may be limited. In addition, when two or more SIMs each change their RRC connection state differently, a specific procedure for an operation for handling this is required.

As such, when a plurality of SIMs are used in a single terminal, there is a possibility that a problem may occur in that a smooth service cannot be provided due to various overlapping situations and state changes.

An object of the present disclosure is to provide a method and an apparatus for providing a communication service without service interruption even when two or more SIMs are configured in a terminal.

In one aspect, the present disclosure provides a method for a terminal to perform communication using a plurality of USIMs, wherein, in a state of concurrent registration in one or more networks associated with a plurality of SIMs, one or more of a connected state There is provided a method comprising the steps of determining release for the network, transmitting help information for instructing release to a base station or a core network control plane entity, and monitoring a paging message based on the help information.

In another aspect, the present disclosure provides a method for a base station to communicate with a terminal using a plurality of USIMs, disconnection transmitted from a terminal simultaneously registered in one or more networks associated with a plurality of SIMs It provides a method comprising the steps of receiving help information for instructing from a core network control plane entity and controlling transmission of a paging message to the terminal based on the help information.

In another aspect, the present disclosure provides a terminal for performing communication using a plurality of SIMs (USIMs), wherein, in a state of concurrent registration in one or more networks associated with a plurality of SIMs, one or more of a connected state It provides a terminal device comprising a control unit for determining release of the network and a transmitter for transmitting help information for instructing release to a base station or a core network control plane entity, wherein the controller monitors a paging message based on the help information.

In another aspect, the present disclosure provides a base station for communicating with a terminal using a plurality of USIMs, disconnecting a connection transmitted from a terminal simultaneously registered in one or more networks associated with a plurality of SIMs. There is provided a base station apparatus including a receiver for receiving help information for instructing from a core network control plane entity, and a controller for controlling transmission of a paging message to a terminal based on the help information.

The present disclosure provides an effect of providing a communication service without service interruption even when two or more SIMs are configured in the terminal.

1 is a diagram schematically illustrating a structure of an NR wireless communication system to which this embodiment can be applied.
2 is a diagram for explaining a frame structure in an NR system to which this embodiment can be applied.
3 is a diagram for explaining a resource grid supported by a radio access technology to which this embodiment can be applied.
4 is a diagram for explaining a bandwidth part supported by a radio access technology to which the present embodiment can be applied.
5 is a diagram exemplarily illustrating a synchronization signal block in a radio access technology to which the present embodiment can be applied.
6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.
7 is a diagram for explaining CORESET.
8 is a diagram illustrating an example in which different subcarrier spacings are arranged at the symbol level.
9 is a diagram for explaining a time domain structure in a next-generation wireless communication system to which this embodiment can be applied.
10 is a flowchart illustrating an operation of a terminal according to an embodiment.
11 is a flowchart illustrating an operation of a base station according to an embodiment.
12 is a diagram showing the configuration of a terminal according to an embodiment.
13 is a diagram showing the configuration of a base station according to an embodiment.

Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. In adding reference numerals to components of each drawing, the same components may have the same reference numerals as much as possible even though they are indicated in different drawings. In addition, in describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present technical idea, the detailed description thereof may be omitted. When "includes", "has", "consisting of", etc. mentioned in this specification are used, other parts may be added unless "only" is used. When a component is expressed in a singular, it may include a case in which the plural is included unless otherwise explicitly stated.

In addition, in describing the components of the present disclosure, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only for distinguishing the elements from other elements, and the essence, order, order, or number of the elements are not limited by the terms.

In the description of the positional relationship of the components, when two or more components are described as being "connected", "coupled" or "connected", the two or more components are directly "connected", "coupled" or "connected" ", but it will be understood that two or more components and other components may be further "interposed" and "connected," "coupled," or "connected." Here, other components may be included in one or more of two or more components that are “connected”, “coupled” or “connected” to each other.

In the description of the temporal flow relation related to the components, the operation method, the manufacturing method, etc., for example, a temporal precedence relationship such as "after", "after", "after", "before", etc. Or, when a flow precedence relationship is described, it may include a case where it is not continuous unless "immediately" or "directly" is used.

On the other hand, when numerical values or corresponding information (eg, level, etc.) for a component are mentioned, even if there is no explicit description, the numerical value or the corresponding information is based on various factors (eg, process factors, internal or external shock, Noise, etc.) may be interpreted as including an error range that may occur.

A wireless communication system in the present specification refers to a system for providing various communication services such as voice and data packets using radio resources, and may include a terminal, a base station, or a core network.

The present embodiments disclosed below may be applied to a wireless communication system using various wireless access technologies. For example, the present embodiments are CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access) Alternatively, it may be applied to various various radio access technologies such as non-orthogonal multiple access (NOMA). In addition, the wireless access technology may mean not only a specific access technology, but also a communication technology for each generation established by various communication consultation organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented with a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced datarates for GSM evolution (EDGE). OFDMA may be implemented with a wireless technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and evolved UTRA (E-UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with a system based on IEEE 802.16e. 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) that uses evolved-UMTSterrestrial radio access (E-UTRA), and employs OFDMA in the downlink and SC- in the uplink. FDMA is employed. As such, the present embodiments may be applied to currently disclosed or commercialized radio access technologies, or may be applied to radio access technologies currently under development or to be developed in the future.

On the other hand, the terminal in the present specification is a comprehensive concept meaning a device including a wireless communication module for performing communication with a base station in a wireless communication system, WCDMA, LTE, NR, HSPA and IMT-2020 (5G or New Radio), etc. It should be interpreted as a concept including all of UE (User Equipment), MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), wireless device, and the like in GSM. In addition, the terminal may be a user portable device, such as a smart phone, depending on the type of use, and in the V2X communication system may mean a vehicle, a device including a wireless communication module in the vehicle, and the like. In addition, in the case of a machine type communication (Machine Type Communication) system, it may mean an MTC terminal, an M2M terminal, a URLLC terminal, etc. equipped with a communication module to perform machine type communication.

A base station or cell in the present specification refers to an end that communicates with a terminal in terms of a network, a Node-B (Node-B), an evolved Node-B (eNB), gNode-B (gNB), a Low Power Node (LPN), Sector, site, various types of antennas, base transceiver system (BTS), access point, point (eg, transmission point, reception point, transmission/reception point), relay node (Relay Node) ), mega cell, macro cell, micro cell, pico cell, femto cell, RRH (Remote Radio Head), RU (Radio Unit), and small cell (small cell), etc. In addition, the cell may mean including a BWP (Bandwidth Part) in the frequency domain. For example, the serving cell may mean the Activation BWP of the UE.

In the various cells listed above, since there is a base station controlling one or more cells, the base station can be interpreted in two ways. 1) in relation to the radio area, it may be the device itself providing a mega cell, a macro cell, a micro cell, a pico cell, a femto cell, or a small cell, or 2) may indicate the radio area itself. In 1), the devices providing a predetermined radio area are controlled by the same entity, or all devices interacting to form a radio area cooperatively are directed to the base station. A point, a transmission/reception point, a transmission point, a reception point, etc. become an embodiment of a base station according to a configuration method of a wireless area. In 2), the radio area itself in which the signal is received or transmitted from the point of view of the user terminal or the neighboring base station may be indicated to the base station.

In the present specification, a cell is a component carrier having a coverage of a signal transmitted from a transmission/reception point or a coverage of a signal transmitted from a transmission/reception point, and the transmission/reception point itself. can

Uplink (Uplink, UL, or uplink) refers to a method of transmitting and receiving data by the terminal to and from the base station, and downlink (Downlink, DL, or downlink) refers to a method of transmitting and receiving data to and from the terminal by the base station do. A downlink may mean a communication or communication path from a multi-transmission/reception point to a terminal, and an uplink may mean a communication or communication path from the terminal to a multi-transmission/reception point. In this case, in the downlink, the transmitter may be a part of multiple transmission/reception points, and the receiver may be a part of the terminal. Also, in the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of the multi-transmission/reception point.

The uplink and downlink transmit and receive control information through a control channel such as a Physical Downlink Control CHannel (PDCCH), a Physical Uplink Control CHannel (PUCCH), etc., and a Physical Downlink Shared CHannel (PDSCH), a Physical Uplink Shared CHannel (PUSCH), etc Data is transmitted and received by configuring the same data channel. Hereinafter, a situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH and PDSCH may be expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH and PDSCH'. do.

For clarity of explanation, the present technical idea will be mainly described below for a 3GPP LTE/LTE-A/NR (New RAT) communication system, but the present technical features are not limited to the corresponding communication system.

In 3GPP, after research on 4G (4th-Generation) communication technology, 5G (5th-Generation) communication technology is developed to meet the requirements of ITU-R's next-generation wireless access technology. Specifically, 3GPP develops LTE-A pro, which improves LTE-Advanced technology according to the requirements of ITU-R as a 5G communication technology, and a new NR communication technology separate from 4G communication technology. LTE-A pro and NR both refer to 5G communication technology. Hereinafter, 5G communication technology will be described focusing on NR unless a specific communication technology is specified.

In the NR operation scenario, various operation scenarios were defined by adding consideration of satellites, automobiles, and new verticals to the existing 4G LTE scenarios. It is deployed in a range and supports the mMTC (Massive Machine Communication) scenario that requires a low data rate and asynchronous connection, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and supports high-speed mobility. .

To satisfy this scenario, NR discloses a wireless communication system to which a new waveform and frame structure technology, low latency technology, mmWave support technology, and forward compatible technology are applied. In particular, in the NR system, various technical changes are presented in terms of flexibility in order to provide forward compatibility. The main technical features of NR will be described with reference to the drawings below.

<Normal NR system>

1 is a diagram schematically illustrating a structure of an NR system to which this embodiment can be applied.

1, the NR system is divided into a 5G Core Network (5GC) and an NR-RAN part, and the NG-RAN controls the user plane (SDAP/PDCP/RLC/MAC/PHY) and UE (User Equipment) It consists of gNBs and ng-eNBs that provide planar (RRC) protocol termination. The gNB interconnects or gNBs and ng-eNBs are interconnected via an Xn interface. gNB and ng-eNB are each connected to 5GC through the NG interface. 5GC may be configured to include an Access and Mobility Management Function (AMF) in charge of a control plane such as terminal access and mobility control functions, and a User Plane Function (UPF) in charge of a control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

gNB means a base station that provides NR user plane and control plane protocol termination to a terminal, and ng-eNB means a base station that provides E-UTRA user plane and control plane protocol termination to a terminal. The base station described in this specification should be understood as encompassing gNB and ng-eNB, and may be used as a meaning to refer to gNB or ng-eNB separately if necessary.

<NR Waveform, Pneumologic and Frame Structure>

In NR, a CP-OFDM waveform using a cyclic prefix is used for downlink transmission, and CP-OFDM or DFT-s-OFDM is used for uplink transmission. OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output), and has advantages of using a low-complexity receiver with high frequency efficiency.

Meanwhile, in NR, since the requirements for data rate, delay rate, coverage, etc. are different for each of the three scenarios described above, it is necessary to efficiently satisfy the requirements for each scenario through the frequency band constituting an arbitrary NR system. . To this end, a technique for efficiently multiplexing a plurality of different numerology-based radio resources has been proposed.

Specifically, the NR transmission numerology is determined based on sub-carrier spacing and cyclic prefix (CP), and the μ value is used as an exponential value of 2 based on 15 kHz as shown in Table 1 below. is changed to

μ subcarrier spacing Cyclic prefix Supported for data Supported for synch 0 15 Normal Yes Yes One 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes

As shown in Table 1 above, the NR pneumatology can be divided into five types according to the subcarrier spacing. This is different from the fact that the subcarrier interval of LTE, one of the 4G communication technologies, is fixed at 15 kHz. Specifically, subcarrier intervals used for data transmission in NR are 15, 30, 60, and 120 kHz, and subcarrier intervals used for synchronization signal transmission are 15, 30, 120, 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier interval. On the other hand, as for the frame structure in NR, a frame having a length of 10 ms is defined, which is composed of 10 subframes having the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame includes 5 subframes. In the case of a 15 kHz subcarrier interval, one subframe consists of one slot, and each slot consists of 14 OFDM symbols.

2 is a diagram for explaining a frame structure in an NR system to which this embodiment can be applied.

Referring to FIG. 2 , a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length in the time domain of the slot may vary according to the subcarrier interval. For example, in the case of a numerology having a 15 kHz subcarrier interval, the slot is 1 ms long and is composed of the same length as the subframe. On the other hand, in the case of numerology having a 30 kHz subcarrier interval, a slot consists of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, the subframe and the frame are defined to have a fixed time length, and the slot is defined by the number of symbols, so that the time length may vary according to the subcarrier interval.

On the other hand, NR defines a basic unit of scheduling as a slot, and also introduces a mini-slot (or a sub-slot or a non-slot based schedule) to reduce transmission delay in a radio section. When a wide subcarrier interval is used, the length of one slot is shortened in inverse proportion, so that transmission delay in a radio section can be reduced. The mini-slot (or sub-slot) is for efficient support of the URLLC scenario and can be scheduled in units of 2, 4, or 7 symbols.

Also, unlike LTE, NR defines uplink and downlink resource allocation at a symbol level within one slot. In order to reduce HARQ delay, a slot structure capable of transmitting HARQ ACK/NACK directly within a transmission slot is defined, and this slot structure is named as a self-contained structure and will be described.

NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15. In addition, a common frame structure constituting an FDD or TDD frame is supported through a combination of various slots. For example, a slot structure in which all symbols of a slot are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink symbols and uplink symbols are combined are supported. In addition, NR supports that data transmission is scheduled to be distributed in one or more slots. Accordingly, the base station may inform the terminal whether the slot is a downlink slot, an uplink slot, or a flexible slot using a slot format indicator (SFI). The base station may indicate the slot format by indicating the index of the table configured through UE-specific RRC signaling using SFI, and may indicate dynamically through Downlink Control Information (DCI) or statically or through RRC. It can also be ordered quasi-statically.

<NR Physical Resources>

In relation to a physical resource in NR, an antenna port, a resource grid, a resource element, a resource block, a bandwidth part, etc. are considered do.

An antenna port is defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. When the large-scale property of a channel carrying a symbol on one antenna port can be inferred from a channel carrying a symbol on another antenna port, the two antenna ports are QC/QCL (quasi co-located or QC/QCL) quasi co-location). Here, the wide range characteristic includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

3 is a diagram for explaining a resource grid supported by a radio access technology to which this embodiment can be applied.

Referring to FIG. 3 , in the resource grid, since NR supports a plurality of numerologies on the same carrier, a resource grid may exist according to each numerology. In addition, the resource grid may exist according to an antenna port, a subcarrier interval, and a transmission direction.

A resource block consists of 12 subcarriers, and is defined only in the frequency domain. In addition, a resource element is composed of one OFDM symbol and one subcarrier. Accordingly, as in FIG. 3 , the size of one resource block may vary according to the subcarrier interval. In addition, NR defines "Point A" serving as a common reference point for a resource block grid, a common resource block, a virtual resource block, and the like.

4 is a diagram for explaining a bandwidth part supported by a radio access technology to which the present embodiment can be applied.

In NR, unlike LTE in which the carrier bandwidth is fixed at 20Mhz, the maximum carrier bandwidth is set from 50Mhz to 400Mhz for each subcarrier interval. Therefore, it is not assumed that all terminals use all of these carrier bandwidths. Accordingly, in NR, as shown in FIG. 4 , a bandwidth part (BWP) may be designated within the carrier bandwidth and used by the terminal. In addition, the bandwidth part is associated with one numerology and is composed of a subset of continuous common resource blocks, and may be dynamically activated according to time. A maximum of four bandwidth parts are configured in the terminal, respectively, in uplink and downlink, and data is transmitted/received using the activated bandwidth part at a given time.

In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, to prevent unnecessary frequency re-tunning between downlink and uplink operations For this purpose, the downlink and uplink bandwidth parts are set in pairs to share a center frequency.

<NR Initial Connection>

In NR, the terminal accesses the base station and performs a cell search and random access procedure in order to perform communication.

Cell search is a procedure in which the UE synchronizes the cell of the corresponding base station using a synchronization signal block (SSB) transmitted by the base station, obtains a physical layer cell ID, and obtains system information.

5 is a diagram exemplarily illustrating a synchronization signal block in a radio access technology to which the present embodiment can be applied.

Referring to FIG. 5, the SSB consists of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) occupying 1 symbol and 127 subcarriers, respectively, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

The UE receives the SSB by monitoring the SSB in the time and frequency domains.

SSB can be transmitted up to 64 times in 5ms. A plurality of SSBs are transmitted using different transmission beams within 5 ms, and the UE performs detection on the assumption that SSBs are transmitted every 20 ms when viewed based on one specific beam used for transmission. The number of beams that can be used for SSB transmission within 5 ms time may increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted in 3 GHz or less, and SSB can be transmitted using up to 8 different beams in a frequency band of 3 to 6 GHz and up to 64 different beams in a frequency band of 6 GHz or more.

Two SSBs are included in one slot, and the start symbol and the number of repetitions within the slot are determined according to the subcarrier interval as follows.

On the other hand, the SSB is not transmitted at the center frequency of the carrier bandwidth, unlike the SS of the conventional LTE. That is, the SSB may be transmitted in a place other than the center of the system band, and a plurality of SSBs may be transmitted in the frequency domain when wideband operation is supported. Accordingly, the UE monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB. The carrier raster and synchronization raster, which are the center frequency location information of the channel for initial access, are newly defined in NR, and the synchronization raster has a wider frequency interval than the carrier raster, so that the terminal can support fast SSB search. can

The UE may acquire the MIB through the PBCH of the SSB. MIB (Master Information Block) includes minimum information for the terminal to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH includes information on the position of the first DM-RS symbol in the time domain, information for the UE to monitor SIB1 (eg, SIB1 neurology information, information related to SIB1 CORESET, search space information, PDCCH related parameter information, etc.), offset information between the common resource block and the SSB (the position of the absolute SSB in the carrier is transmitted through SIB1), and the like. Here, the SIB1 neurology information is equally applied to some messages used in the random access procedure for accessing the base station after the UE completes the cell search procedure. For example, the neurology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

The aforementioned RMSI may mean System Information Block 1 (SIB1), and SIB1 is periodically broadcast (eg, 160 ms) in the cell. SIB1 includes information necessary for the UE to perform an initial random access procedure, and is periodically transmitted through the PDSCH. In order for the UE to receive SIB1, it must receive neurology information used for SIB1 transmission and CORESET (Control Resource Set) information used for scheduling SIB1 through the PBCH. The UE checks scheduling information for SIB1 by using SI-RNTI in CORESET, and acquires SIB1 on PDSCH according to the scheduling information. SIBs other than SIB1 may be transmitted periodically or may be transmitted according to the request of the terminal.

6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.

Referring to FIG. 6 , upon completion of cell search, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted through the PRACH. Specifically, the random access preamble is transmitted to the base station through a PRACH consisting of continuous radio resources in a specific slot that is periodically repeated. In general, when a UE initially accesses a cell, a contention-based random access procedure is performed, and when performing random access for beam failure recovery (BFR), a contention-free random access procedure is performed.

The terminal receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), a UL grant (uplink radio resource), a temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and a Time Alignment Command (TAC). Since one random access response may include random access response information for one or more terminals, the random access preamble identifier may be included to inform which terminal the included UL Grant, temporary C-RNTI, and TAC are valid. The random access preamble identifier may be an identifier for the random access preamble received by the base station. The TAC may be included as information for the UE to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, that is, RA-RNTI (Random Access - Radio Network Temporary Identifier).

Upon receiving the valid random access response, the terminal processes information included in the random access response and performs scheduled transmission to the base station. For example, the UE applies the TAC and stores the temporary C-RNTI. In addition, data stored in the buffer of the terminal or newly generated data is transmitted to the base station by using the UL grant. In this case, information for identifying the terminal should be included.

Finally, the terminal receives a downlink message for contention resolution.

<NR CORESET>

The downlink control channel in NR is transmitted in a control resource set (CORESET) having a length of 1 to 3 symbols, and transmits up/down scheduling information, slot format index (SFI), transmit power control (TPC) information, etc. .

In this way, NR introduced the concept of CORESET in order to secure the flexibility of the system. CORESET (Control Resource Set) means a time-frequency resource for a downlink control signal. The UE may decode the control channel candidates by using one or more search spaces in the CORESET time-frequency resource. Quasi CoLocation (QCL) assumptions for each CORESET are set, and this is used for the purpose of notifying the characteristics of the analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay, which are characteristics assumed by the conventional QCL.

7 is a diagram for explaining CORESET.

Referring to FIG. 7 , CORESET may exist in various forms within a carrier bandwidth within one slot, and CORESET may consist of up to three OFDM symbols in the time domain. In addition, CORESET is defined as a multiple of 6 resource blocks up to the carrier bandwidth in the frequency domain.

The first CORESET is indicated through the MIB as part of the initial bandwidth part configuration to receive additional configuration information and system information from the network. After establishing a connection with the base station, the terminal may receive and configure one or more pieces of CORESET information through RRC signaling.

In this specification, frequencies, frames, subframes, resources, resource blocks, regions, bands, subbands, control channels, data channels, synchronization signals, various reference signals, various signals or various messages related to NR (New Radio) can be interpreted in various meanings used in the past or present or used in the future.

New Radio (NR)

NR, a next-generation wireless communication technology that is being standardized in 3GPP, provides an improved data rate compared to LTE and is a radio access technology that can satisfy various QoS requirements required for each segmented and detailed usage scenario. . In particular, enhancement Mobile BroadBand (eMBB), massive MTC (mMTC), and Ultra Reliable and Low Latency Communications (URLLC) have been defined as representative usage scenarios of NR. As a method for satisfying the requirements for each scenario, a frame structure that is flexible compared to LTE is provided. The NR frame structure supports a multiple subcarrier-based frame structure. The basic subcarrier spacing (SubCarrier Spacing, SCS) becomes 15 kHz, and a total of 5 types of SCS are supported at 15 kHz*2^n.

8 is a diagram illustrating an example in which different subcarrier spacings are arranged at the symbol level.

Referring to FIG. 8 , it can be seen that the length of the time axis of the slot varies according to numerology. That is, it can be seen that the shorter the slot length, the larger the SCS. In addition, the number of OFDM symbols constituting a slot in NR, y value, is fixed to have a value of y=14 regardless of the SCS value in the case of normal CP. Accordingly, an arbitrary slot consists of 14 symbols. In addition, all symbols may be used for DL transmission, or all symbols may be used for UL transmission, or may be used in the form of DL portion + (gap) + UL portion according to the transmission direction of the slot. there is.

In addition, in any numerology (or SCS), a mini-slot composed of fewer symbols than the aforementioned slot is defined. A short time-domain scheduling interval for mini-slot-based uplink/downlink data transmission/reception may be configured, or a long time-domain scheduling interval for uplink/downlink data transmission/reception through slot aggregation may be configured. there is. In particular, in the case of transmitting and receiving latency-sensitive data such as URLLC, it is difficult to satisfy the latency requirement if 1ms (14 symbols)-based slot-based scheduling defined in a numerology-based frame structure with a small SCS value such as 15kHz is performed. can Accordingly, scheduling that can satisfy the requirements of URLLC can be performed based on defining a mini-slot composed of fewer OFDM symbols than a slot composed of 14 symbols.

9 is a diagram for explaining a time domain structure in a next-generation wireless communication system to which this embodiment can be applied.

Referring to FIG. 9 , NR supports the following structure on the time axis. The difference from the existing LTE is that in NR, the basic scheduling unit is changed to the aforementioned slot. In addition, a slot is composed of 14 OFDM symbols as shown in FIG. 9 regardless of subcarrier spacing. On the other hand, a non-slot structure (mini-slot structure) composed of 2, 4, and 7 OFDM symbols, which is a smaller scheduling unit, is supported. The non-slot structure may be utilized as a scheduling unit for the URLLC service.

■ Radio frame: Fixed 10ms regardless of numerology.

■ Subframe: Fixed to 1ms in the time domain (Fixed 1ms as a reference for time duration). Unlike LTE, it is not used as a scheduling unit for data and control signals.

■ Slot: Used mainly for eMBB scenarios (Mainly for eMBB). Include 14 OFDM symbols.

■ Non-slot (i.e. mini-slot): Mainly used for URLLC scenarios, but not limited thereto (Mainly for URLLC, but not limited to URLLC only). Include 2, 4, or 7 OFDM symbols.

■ One TTI duration: A Time duration for data/control channel transmission. A number of OFDM symbols per a slot/non-slot in the time main

NR Paging procedure

In the paging technique, the network attempts to receive an RRC IDLE or RRC INACTIVE terminal, or notifies an RRC IDLE, RRC INACTIVE or RRC CONNECTED terminal of a system information change and an Earthquake and Tsunami Warning System/Commercial Mobiel Alert System (ETWS/CMAS) instruction. used for For example, the RRC IDLE terminal monitors a paging channel for core network initiated (CN-initiated) paging, and the RRC INACTIVE terminal monitors a paging channel for RAN-initiated paging. Paging DRX is defined to reduce power consumption of RRC IDLE or RRC INACTIVE UE. The paging DRX cycle may be configured by the network as follows.

- The default cycle for core network initiated paging is broadcast through system information (For CN-initiated paging, a default cycle is broadcast in system information).

- A UE specific cycle for core network initiated paging may be configured through NAS signaling (For CN-initiated paging, a UE specific cycle can be configured via NAS signaling).

- A UE-specific cycle for RAN-initiated paging may be configured through RRC signaling (For RAN-initiated paging, a UE-specific cycle can be configured via RRC signaling)

The UE uses the shortest DRX cycle among applicable cycles (The UE uses the shortest of the DRX cycles applicable). For example, the RRC IDLE terminal uses the shortest cycle among the default cycle for the core network initiated paging and the terminal specific cycle. Similarly, the RRC INACTIVE UE uses the shortest cycle among the above two cycles for core network initiated paging and one cycle for RAN initiated paging.

On the other hand, the UE monitors one paging occurrence (PO: Paging Occasion) per DRX cycle. The PO may consist of a plurality of timeslots in which the paging DCI is transmitted as a PDCCH monitoring attack set. A PF (paging frame) is one radio frame and may include one or a plurality of PO(s) or a start point of POs. (A PO is a set of PDCCH monitoring occasions and can consist of multiple time slots (eg subframe or OFDM symbol) where paging DCI can be sent. One Paging Frame (PF) is one Radio Frame and may contain one or multiple PO(s) ) or starting point of a PO.)

In the multi-beam operation, the UE assumes that the same paging message and the same short message are repeated in all transmitted beams. And, accordingly, beam selection for receiving the paging message and the short message depends on the implementation of the terminal. The paging message is the same for radio network initiated paging and core network initiated paging. When the radio network initiation paging is received, the terminal initiates the RRC resumption procedure. If the UE receives the core network initiation paging in the RRC inactive state, it moves to the RRC idle and notifies the NAS (Non Access Stratum). (In multi-beam operations, the UE assumes that the same paging message and the same Short Message are repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the paging message and Short Message is up to UE The paging message is same for both RAN initiated paging and CN initiated paging. The UE initiates RRC Connection Resume procedure upon receiving RAN initiated paging. If the UE receives a CN initiated paging in RRC_INACTIVE state, the UE moves to RRC_IDLE and informs NAS .)

PF and PO are determined by the following formula.

The system frame number (SFN) for the PF is determined by the following equation.

(SFN + PF_offset) mod T = (T div N)*(UE_ID mod N)

In addition, Index (i_s) indicating the index of the paging error PO is determined by the following equation.

i_s = floor (UE_ID/N) mod Ns

If the 'paging-SearchSpace' and 'firstPDCCH-MonitoringOccasionOfPO' parameters are configured, the PDCCH monitoring attack for paging is determined according to the corresponding parameters.

When SearchSpaceId = 0 is configured for pagingSearchSpace , the PDCCH monitoring opportunity for paging is the same as in the case of the RMSI defined in clause 13 of TS 38.213 (When SearchSpaceId = 0 is configured for pagingSearchSpace , the PDCCH monitoring occasions for paging are same as for RMSI as defined in clause 13 in TS 38.213).

If SearchSpaceId = 0 is configured for pagingSearchSpace, then Ns is 1 or 2. In the case of Ns = 1, there is only one PO starting in the first PDCCH monitoring situation for paging in the PF. (When SearchSpaceId = 0 is configured for pagingSearchSpace , Ns is either 1 or 2. For Ns = 1, there is only one PO which starts from the first PDCCH monitoring occasion for paging in the PF. For Ns = 2, PO is either in the first half frame (i_s = 0) or the second half frame (i_s = 1) of the PF.)

If a non-zero SearchSpaceId is set in pagingSearchSpace, the UE monitors the (i_s + 1)-th PO. PO is a set of 'S' continuous PDCCH monitoring cases, and 'S' is the number of actually transmitted SSBs determined according to ssb-PositionsInBurst of SIB1. The K-th PDCCH monitoring opportunity for paging in the PO corresponds to the K-th transmitted SSB. PDCCH monitoring opportunities for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from 0, starting from the first PDCCH monitoring opportunity for paging in PF. When there is firstPDCCH-MonitoringOccasionOfPO, the starting PDCCH monitoring opportunity number of the (i_s+1)-th PO is the (i_s+1)-th value of the firstPDCCH-MonitoringOccasionOfPO parameter. (When SearchSpaceId other than 0 is configured for pagingSearchSpace, the UE monitors the (i_s + 1) ^th PO. A PO is a set of 'S' consecutive PDCCH monitoring occasions where 'S' is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1. The K th PDCCH monitoring occasion for paging in the PO corresponds to the K th transmitted SSB. The PDCCH monitoring occasions for paging which do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from zero starting from the first PDCCH monitoring occasion for paging in the PF. When firstPDCCH-MonitoringOccasionOfPO is present, the starting PDCCH monitoring occasion number of (i_s + 1) th PO is the ( i_s + 1) ^th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s * S.)

■ A PO associated with a PF may start in the PF or after the PF.

■ The PDCCH monitoring situation for the PO may span several radio frames. (The PDCCH monitoring occasions for a PO can span multiple radio frames. When SearchSpaceId other than 0 is configured for paging-SearchSpace the PDCCH monitoring occasions for a PO can span multiple periods of the paging search space.)

The following parameters are used in the calculation of PF and i_s above.

T: DRX cycle of the terminal. (T is determined by the shortest of the UE specific DRX value(s), if configured by RRC and/or upper layers, and a default DRX value broadcast in system information. In RRC_IDLE state, if UE specific DRX is not configured by upper layers, the default value is applied).

N: number of total paging frames in T

Ns: number of paging occasions for a PF

PF_offset: offset used for PF determination

UE_ID: 5G-S-TMSI mod 1024

The parameters Ns, nAndPagingFrameOffset and the length of the basic DRX cycle are signaled in SIB1. The values of N and PF_offset may be derived from the nAndPagingFrameOffset parameter defined in TS 38.331. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled through SIB1 for paging in the initial DL BWP. In the case of paging in a DL BWP other than the initial DL BWP, the first-PDCCH-MonitoringOccasionOfPO parameter is signaled through the associated BWP configuration. (Parameters Ns , nAndPagingFrameOffset , and the length of default DRX Cycle are signaled in SIB1 . The values of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in TS 38.331 [3]. The parameter first-PDCCH-MonitoringOccasionOfPO is signalled in SIB1 for paging in initial DL BWP. For paging in a DL BWP other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.)

If the UE does not have 5G-S-TMSI, for example, if the UE has not yet registered with the network, the UE shall use the default ID UE_ID = 0 in the above PF and i_s formula (If the UE has no 5G- S-TMSI, for instance when the UE has not yet registered onto the network, the UE shall use as default identity UE_ID = 0 in the PF and i_s formulas above).

5G-S-TMSI is a bit string with a length of 48 bits as defined in TS 23.501. 5G-S-TMSI is interpreted as a binary number in which the leftmost bit represents the most significant bit in the above formula (5G-S-TMSI is a 48 bit long bit string as defined in TS 23.501. 5G-S-TMSI shall in the formulae above be interpreted as a binary number where the left most bit represents the most significant bit).

Multi USIM terminal

A user may have a plurality of subscriptions to one terminal. For example, a user may have one personal subscription and one corporate subscription for one terminal. Alternatively, the user may have two personal subscriptions to one terminal.

Meanwhile, one SIM may be associated with the terminal for each subscription. For convenience of description, a terminal having one or more SIMs is denoted as a plurality of SIM terminals. This is for convenience of description and includes a dual SIM terminal having two subscriptions, and may be used instead of any term. Also, for convenience of description, hereinafter, a terminal may mean a plurality of SIM terminals.

Currently, there is no standard specification for supporting multiple SIM terminals. Accordingly, it is necessary for a terminal registered in one or more networks to receive paging from one or more networks. However, there may be cases in which paging errors of the terminal overlap or the terminal cannot receive paging through another network while transmitting and receiving data in an active state (eg, RRC connected) through one network. Accordingly, while the terminal transmits and receives data in an active state (eg, RRC connected) through one network, an important mobile terminated service may not be provided through another network. In addition, if multiple SIM terminals are simultaneously transmitted and received in connection with each SIM, the service may be interrupted because it cannot process them. In particular, when a handover occurs in connection with one SIM according to the movement of a terminal, performance may be deteriorated due to service interruption.

The present disclosure devised to solve this problem is to provide a method and apparatus capable of preventing the occurrence of a service problem when a plurality of SIMs are configured in a terminal.

As an example, the present disclosure proposes a method and apparatus for providing an incoming service by effectively receiving paging through a network associated with another SIM by a plurality of SIM terminals that transmit and receive data in an active state through a network associated with one SIM. want to As another example, the present disclosure intends to propose a method and apparatus for reducing service interruption when a collision occurs in transmission and reception by associated SIMs or when a terminal moves. As another example, the present disclosure intends to propose a method and apparatus capable of providing a switching operation between different SIMs.

For convenience of description, hereinafter, the radio access technology will be described based on NR. However, this is only for convenience of description and may be applied in LTE or any other radio access technology. On the other hand, although the present disclosure is mainly described as being applied to a licensed band, it can be equally applied to any radio access technology using an unlicensed band. In the present specification, well-known information or technology is omitted for convenience of description, and each embodiment may include information elements and procedures specified in TS 38.331, a 3GPP NR RRC standard. Even if the definition of the information element or the content of the related procedure is not included in this specification, the content specified in the standard is used in connection with this embodiment, and the content is also included in the present disclosure.

The SIM in this embodiment may be a physical SIM or an embedded-SIM (eSIM). A plurality of SIMs associated with the terminal may belong to the same operator or may belong to different operators.

First, a scenario to which the present disclosure can be applied will be described. Hereinafter, for convenience of explanation, a scenario will be described based on a plurality of SIM terminals having two subscriptions. This is only for convenience of description, and the present embodiment may be applied to any scenario including a terminal using two or more multiple SIMs.

A multi-SIM terminal may represent a UE with multiple USIMs that are in operation at the same time. A user may have a subscription linked to two LTE wireless networks operated by different operators through one terminal. A user may have a subscription linked to two LTE wireless networks operated by one operator through one terminal. A user may have a subscription linked to two NR radio networks operated by different operators through one terminal. A user may have a subscription associated with two NR radio networks operated by one operator through one terminal. A user may have a subscription associated with each of the LTE wireless network and the NR wireless network operated by different operators through one terminal. A user may have a subscription associated with each of the LTE wireless network and the NR wireless network operated by one operator through one terminal. Two wireless networks linked to multiple SIM terminals may be linked to different core networks, respectively. The core network may be 5GS or EPS. A user may have a subscription linked to two core networks operated by different operators through one terminal. When different operators linked to multiple SIMs use one wireless network by sharing/slicing/roaming, multiple SIM terminals can receive services through two different core networks connected to one wireless network. In this case, the shared/sliced/roamed wireless network may be LTE or NR.

Each network associated with each SIM may process to independently perform a registration procedure from SIMs of a plurality of SIM terminals. The terminal may be connected to each core network based on 5GS for both SIMs. In this case, the wireless network may generally assume NR application. However, NR or LTE may be used, respectively. Both SIMs in one UE may be connected to each EPS-based core network. At this time, the wireless network assumes NR application, but NR or LTE may be used, respectively. In one terminal, one SIM may be linked to the EPS-based core network and the other SIM may be linked to the 5GS-based core network. If two SIMs are connected to a single shared/sliced/roaming wireless network, the wireless network assumes NR application, but LTE can be used.

For example, the plurality of SIM terminals may be terminals capable of dual reception/dual transmission (Dual Rx/Dual Tx UEs). In this case, the terminal can transmit and receive data simultaneously through each network associated with two SIMs through two receivers and two transmitters. As another example, the multiple SIM terminals may be dual reception/single transmission terminals (Dual Rx/Single Tx UEs). Alternatively, the multiple SIM terminals may be single reception/single transmission terminals (Single Rx/Single Tx UEs). When a multi-SIM terminal has only one transmitter, data cannot be simultaneously transmitted through a network associated with each SIM. Alternatively, when multiple SIM terminals have only one receiver, data cannot be simultaneously received through a network associated with each SIM.

Hereinafter, a multi-SIM terminal is basically assumed to be a single reception/single transmission terminal (Single Rx/Single Tx UEs) or a dual reception/single transmission terminal (Dual Rx/Single Tx UEs). If the corresponding terminal is transmitting and receiving data while connected to a network associated with one SIM, it is difficult to establish a connection to two networks at the same time and transmit and receive data even if a paging message is received from a network associated with another SIM. If the terminal disconnects the connection of a base station associated with one SIM (referred to as base station A for convenience of explanation) that is already transmitting and receiving data in a connected state internally (locally), and another base station associated with another SIM (in the description of If data is transmitted and received by establishing a connection with base station B for convenience, base station A may unnecessarily waste radio resources to continue data transmission and reception. In addition, in order to release the connection with the base station B and resume the connection to the base station A again, the signaling burden may increase because initial access signaling with the core network must be performed again.

A plurality of SIM terminals may transmit/receive data by performing a network registration procedure/RRC connection setup procedure in connection with each SIM, or may receive paging to transmit/receive data. In addition, tracking area update (TAU) or RNAU (RAN-based notification area updates) may be performed periodically. When all SIMs owned by the multiple SIM terminal are in the RRC inactive/idle state, data transmission/reception may be triggered simultaneously in connection with each SIM. In a multi-SIM terminal, when one SIM is in RRC inactive/idle state and the other SIM is in RRC connected state, data transmission/reception may be triggered simultaneously in connection with each SIM. When a multi-SIM terminal collides in transmission/reception by the associated SIMs, the following methods can be used individually or arbitrarily combined/combined.

10 is a flowchart illustrating an operation of a terminal according to an embodiment.

Referring to FIG. 10 , a terminal performing communication using a plurality of USIMs releases one or more networks in a connected state while concurrently registering in one or more networks associated with the plurality of SIMs. may be performed (S1000).

For example, a terminal performing communication using a plurality of USIMs may be concurrently registered with one or more networks associated with the plurality of SIMs. The terminal may decide to release one or more networks associated with a plurality of SIMs according to arbitrary conditions. For example, the terminal may disconnect the network associated with any one SIM according to a user input signal. Alternatively, the terminal may decide to release the network associated with a specific SIM according to priority or whether a preset condition is satisfied.

The terminal may perform a step of transmitting help information for instructing release to the base station or the core network control plane entity (S1010).

For example, the help information may be transmitted by being included in a NAS transport message or a NAS deregistration message. In addition, the help information may include information for limiting or allowing the transmission of the paging message to the terminal for a predetermined period of time preset by the base station or the core network control plane entity.

For example, information for limiting or allowing paging message transmission includes information for instructing that only voice data be paged, information for instructing limiting paging, radio bearer information for limiting or allowing paging, logical channel identification information (LCID) , a flow identification number, QoS Flow ID (QFI) information, and may include at least one of PDU session identification information.

On the other hand, before the terminal decides to release, it may receive indication information indicating whether the transmission of help information is permitted from the base station or the core network control plane entity (ex, AMF). The terminal can transmit the help information only when the transmission of the help information is permitted by the indication information.

The terminal may perform the step of monitoring the paging message based on the help information (S1020).

For example, when the transmission of the paging message is restricted based on the help information, the UE may monitor the paging message in consideration of the restriction. Alternatively, when the transmission of the paging message is allowed based on the help information, the terminal may monitor the paging message in consideration of the corresponding matter.

Alternatively, the terminal may monitor a paging message in a specific paging error or paging frame determined based on the help information.

Meanwhile, the terminal may not accept the reception of the paging message even if the paging message is confirmed as a result of monitoring the paging message. If the terminal does not accept the reception of the paging message, the terminal may transmit non-acceptance indication information for the paging message to the base station or the core network control plane entity.

Whether the terminal accepts the reception of the paging message may be classified according to the cause of the paging. For example, the paging message may include paging cause information. The terminal may determine whether to accept the reception of the paging message based on the paging cause information.

For example, the paging cause information may include information indicating voice data. For example, if the paging cause information indicates voice data, the terminal may receive the paging message, otherwise it may not accept the reception.

In addition to this, the terminal may perform individual embodiments for the paging operation, service interruption reduction operation, and transmission/reception collision operation described below in any combination. A specific, specific embodiment for each terminal operation will be described in more detail below.

11 is a flowchart illustrating an operation of a base station according to an embodiment.

Referring to FIG. 11 , a base station communicating with a terminal using a plurality of USIMs helps instruct disconnection transmitted from terminals concurrently registered in one or more networks associated with the plurality of SIMs. The step of receiving information from the core network control plane entity may be performed (S1100).

For example, a terminal performing communication using a plurality of USIMs may be concurrently registered with one or more networks associated with the plurality of SIMs. The terminal may decide to release one or more networks associated with a plurality of SIMs according to arbitrary conditions. For example, the terminal may disconnect the network associated with any one SIM according to a user input signal. Alternatively, the terminal may decide to release the network associated with a specific SIM according to priority or whether a preset condition is satisfied.

The terminal may transmit help information for instructing release to the base station or the core network control plane entity. When the terminal transmits help information to the core network control plane entity, the base station may receive the help information from the core network control plane entity. For example, the help information may receive the help information through an interface (eg, N2 interface) between the base station and the core network control plane entity.

For example, the help information may be included in a NAS transport message or a NAS deregistration message and received as a core network control plane entity. In addition, the help information may include information for limiting or allowing the transmission of the paging message to the terminal for a predetermined period of time preset by the base station or the core network control plane entity.

For example, information for limiting or allowing paging message transmission includes information for instructing that only voice data be paged, information for instructing limiting paging, radio bearer information for limiting or allowing paging, logical channel identification information (LCID) , a flow identification number, QoS Flow ID (QFI) information, and may include at least one of PDU session identification information.

On the other hand, before the terminal decides to release, the base station or the core network control plane entity (ex, AMF) may transmit indication information indicating whether the terminal's help information transmission is allowed. The terminal can transmit the help information only when the transmission of the help information is permitted by the indication information.

The base station may perform a step of controlling transmission of a paging message to the terminal based on the help information (S1110).

The base station may determine whether to transmit the paging message to the terminal based on the help information. When the transmission of the paging message is restricted by the help information, the base station controls the transmission of the paging message in consideration of the restriction. Alternatively, the base station may control the paging message to be transmitted in a specific paging error or paging frame determined based on the assistance information.

When the transmission of the paging message is restricted based on the help information, the UE may monitor the paging message in consideration of the restriction. Alternatively, when the transmission of the paging message is allowed based on the help information, the terminal may monitor the paging message in consideration of the corresponding matter. Alternatively, the terminal may monitor a paging message in a specific paging error or paging frame determined based on the help information.

Meanwhile, the terminal may not accept the reception of the paging message even if the paging message is confirmed as a result of monitoring the paging message. If the terminal does not accept the reception of the paging message, the terminal may transmit non-acceptance indication information for the paging message to the base station or the core network control plane entity. The base station may receive non-acceptance indication information.

Whether the terminal accepts the reception of the paging message may be classified according to the cause of the paging. For example, the paging message may include paging cause information. The terminal may determine whether to accept the reception of the paging message based on the paging cause information. To this end, the base station may transmit the paging message including the paging cause information.

For example, the paging cause information may include information indicating voice data. For example, if the paging cause information indicates voice data, the terminal may receive the paging message, otherwise it may not accept the reception.

Hereinafter, the above-described terminal and base station operations will be described in more detail. Each embodiment described below may be performed by a terminal and a base station or a core network entity in any combination.

First, an embodiment of a paging operation of a terminal using a plurality of SIMs will be described.

An embodiment in which the UE requests 5G-S-TMSI reassignment for paging collision avoidance

A plurality of SIM terminals may independently perform a registration procedure for each network associated with each SIM. Each core network associated with each SIM of the plurality of SIM terminals may be connected to different wireless networks (base stations). Alternatively, each core network associated with each SIM of a plurality of SIM terminals may be connected to the same wireless network (base station).

First, a case in which each core network associated with each SIM configured in a plurality of SIM terminals is connected to different wireless networks (base stations) will be described. A plurality of SIM terminals may transition to an idle state in a network associated with each SIM. The terminal may calculate a paging error (PO) by receiving configuration information for paging reception from each network (e.g. wireless network and/or core network). For this purpose, the above-described PF and PO formulas of NR may be used. For LTE wireless networks, the PF and PO formulas specified in 3GPPP TS 36.304 can be used. The two radio networks may be out of synchronization, and may have different system frame numbers (SFNs) at a specific time. Also, the two radio networks may use different subcarrier spacings to have different scheduling units for radio resources. Accordingly, the UE may have overlapping POs at any specific point in time.

When each core network associated with each SIM configured in a plurality of SIM terminals is connected to the same wireless network (base station), the terminal receives configuration information for paging reception from the corresponding wireless network and/or each core network and receives the PO can be calculated. Although it is one wireless network, a case in which POs overlap at any specific time may occur. For example, the terminal identifier assigned to each network that calculates PF/PO is the same, or the value (5G-S-TMSI mod 1024 or terminal identifier index value) obtained by performing a modular operation on each terminal identifier is the same or (5G-S-TMSI mod 1024) may be the same case as the value (UE_ID mod N) that is modularly calculated by N (number of total paging frames in T).

When the terminal recognizes this problem, it can transmit signaling for solving the problem to the network.

For example, the terminal may request allocation of a new terminal identifier (5G-S-TMSI or 5G-GUTI) to the core network control plane entity (e.g. AMF). 5G-S-TMSI is a temporary terminal identifier provided by the 5G core (5GC, e.g. AMF) and represents a terminal identifier that uniquely identifies a terminal in the tracking area. 5G-S-TMSI has a 48-bit value. 5G-S-TMSI consists of 10-bit AMF Set ID, 6-bit AMF Pointer, and 32-bit 5G-TMSI. 5G-GUTI (5G globally unique temporary identity) is another temporary terminal identifier provided by 5G core (5GC, eg AMF). 5G-S-TMSI is a shortened form of the 5G-GUTI. GUTI). 5G-GUTI consists of GUAMI (Globally Unique AMF ID) and 5G-S-TMSI. Therefore, the UE requesting a new 5G-GUTI allocation may be the same as requesting a new 5G-S-TMSI.

As an example, the UE may request allocation of a new UE identifier (e.g. 5G-S-TMSI or 5G-GUTI) to the AMF through a REGISTRATION REQUEST message. The terminal may include indication information for this in the registration request message. As another example, the terminal may request allocation of a new terminal identifier (e.g. 5G-S-TMSI or 5G-GUTI) to AMF through an arbitrary uplink NAS message. The terminal may include indication information for this in the uplink NAS message. As another example, the terminal may request allocation of a new terminal identifier (e.g. 5G-S-TMSI or 5G-GUTI) to the base station through an arbitrary uplink RRC message (e.g. terminal assistance information message). The base station may transmit to the AMF including the allocation request on the N2 interface message between the base station and the AMF. The terminal may include indication information for this in an arbitrary message.

Meanwhile, the AMF may allocate a new terminal identifier upon receiving a registration request from the terminal. In addition, the AMF may transmit the newly allocated terminal identifier in a REGISTRATION ACCEPT message. This may be true even if it is not for periodic registration update. For reference, in the prior art, a new terminal identifier could be allocated only for periodic registration update. Alternatively, the AMF may allocate a new terminal identifier through a generic UE configuration update procedure and transmit it to the terminal.

An embodiment of transmitting help information for supporting paging reception to a base station through RRC signaling

The 5G-S-TMSI reassignment method has a possibility of avoiding collision when all terminals with 5G core network (5GS)-based subscription are in RRC idle or RRC inactive mode, but there are limitations to complete collision avoidance. there may be In addition, when a plurality of SIM terminals transmit/receive data in an active state (eg, RRC connected) through a network associated with one SIM, it may be unable to receive paging through another network. In addition, in the case of a terminal having a subscription based on an LTE wireless network and/or an LTE core network (EPS), it may be difficult to apply the reassignment method. In the LTE wireless network and/or the LTE core network (EPS), the PF/PO calculation formula uses the IMSI as the terminal identifier. IMSI is a value allocated according to subscription, and it is difficult to reassign. Also, for security reasons, in general, transmission over a wireless section may not be desirable.

Accordingly, an embodiment different from the 5G-S-TMSI reallocation method may be applied.

For example, a plurality of SIM terminals may perform signaling to a network to support paging reception from a network associated with each subscription. If the UE recognizes that the POs overlap at any specific point in time, the UE may signal to the network to solve this problem. Alternatively, when the terminal transmits and receives data in an active state (or connected state) on a network associated with one subscription, signaling is performed to the network to support paging reception in an idle or inactive state on a network associated with another subscription. can

For example, the terminal may transmit help information for supporting paging reception to the base station through an arbitrary uplink RRC message. The help information may include one or more of the following information.

- Terminal identifier index value: means an information element used by the base station to calculate a paging frame. This value can be 10 bits. For example, it may be 5G-S-TMSI mod 1024 and/or IMSI mod 1024. For example, when each core network associated with each SIM configured in a plurality of SIM terminals is connected to a different wireless network (base station), wireless network 1 ( The terminal identifier index value associated with the SIM2 may be transmitted to the base station 1). For another example, when each core network associated with each SIM configured in a plurality of SIM terminals is connected to the same wireless network (base station), the terminal is connected to the core network 1 associated with the SIM 1 through a wireless network. It is possible to transmit the terminal identifier index value associated with the SIM 2 to the wireless network (base station).

- UE specific DRX (UE specific DRX) information: UE specific DRX cycle information determined by the AMF by the request of the UE through NAS signaling (e.g. Initial Registration and Mobility Registration procedure). In this information, the UE may also transmit UE-specific DRX associated with a SIM other than the connected SIM.

- RAN paging cycle (ran-PagingCycle) information: For the RRC inactive state terminal, the terminal-specific DRX cycle allocated by the base station is used for radio network initiation paging. In this information, the UE may also transmit UE-specific DRX associated with a SIM other than the connected SIM.

- Periodic registration update timer (Periodic Registration Update Timer) information: the terminal starts periodic registration update when the periodic registration update timer (ex, T3612) expires (When a UE is not registered for emergency services, and timer T3512 expires, the periodic registration update procedure shall be started.). When the terminal performs the periodic registration update procedure, the AMF may allocate a new terminal identifier. Accordingly, the base station may need the corresponding information to estimate a time period during which a paging collision may occur. In this information, the terminal may also transmit a parameter value associated with a SIM other than the connected SIM.

- Periodic RNA update timer (Periodic RAN Notification Area Update Timer) information: The UE starts periodic RNA update when the periodic RNA update timer (ex, T380) expires. The base station may need the corresponding information to estimate the occurrence of a paging collision according to the RNA update. In this information, the terminal may also transmit a parameter value associated with a SIM other than the connected SIM.

- MICO (Mobile Initiated Connection Only) mode indication information: If the AMF enables the mode (MICO mode) that supports only the mobile initiated connection for the terminal, the terminal may deliver indication information indicating that it is in the MICO mode. In this information, the terminal may also transmit a parameter value associated with a SIM other than the connected SIM.

- Timing difference information between two wireless networks (base stations): For example, when each core network associated with each SIM configured in a plurality of SIM terminals is connected to a different wireless network (base station), the terminal In the state of being connected to wireless network 1 linked to SIM 1, wireless network 1 (or cell/serving cell/PCell/any serving cell selected by the terminal linked to base station 1) and SIM to wireless network 1 (base station 1) It is possible to transmit timing difference related information between wireless network 2 (or cell selected by a terminal associated with the corresponding base station 2) associated with 2 . For convenience of explanation, camp-on-cell/serving cell/PCell of wireless network 1 linked to SIM 1 is denoted as PCell1, and camp-on-cell/serving cell/PCell of wireless network 2 linked to SIM 2 is denoted as PCell2. This is for convenience of description and may be denoted by any name. The timing difference information between the two radio networks (base stations) is the SFN difference (SFN offset) between PCell1 and PCell2, PCell1 and PCell2 frame boundary offset, PCell1 and PCell2 subframe boundary offset (frame boundary offset) ) and an offset (frame boundary offset) between the first slot of the PCell1 frame and the first slot of the PCell2 frame. In addition, the timing difference information between the two radio networks (base stations) may include a cell identifier (e.g. Physical Cell identity or CGI or Servcellindex or Scellindex) of PCell1.

- Default paging cycle (defaultPagingCycle) information: information used to obtain the DRX cycle (T) of the terminal, indicating a value transmitted through system information from a base station linked to a SIM other than the connected SIM.

- nAndPagingFrameOffset information: Indicates the number of total paging frames (N) in the DRX cycle (T) of the terminal and paging frame offset (PF_offset) information used for determining the paging frame.

- ns: the number of paging occasions for one paging frame (number of paging occasions for a PF) information.

- firstPDCCH-MonitoringOccasionOfPO information: information for indicating the first PDCCH monitoring occurrence for paging for each PO of the PF.

- nB: A value transmitted through system information when a base station linked to a SIM other than the connected SIM is an LTE base station, and is parameter information used to induce a paging frame and a paging error.

- Paging collision indication information: If multiple SIM terminals enter the RRC idle or RRC inactive state on networks associated with two subscriptions, the terminal may estimate whether a paging collision will occur. When a paging collision is expected, the terminal may transmit indication information for this to the base station. The corresponding information may transmit one or more of the paging collision period, the next paging collision expected time, the remaining time until the next paging collision, and the expected duration/duration of the paging collision. The base station may request information from the terminal to receive the paging collision indication information, or transmit and receive indication information allowing information transmission.

Meanwhile, the terminal may transmit one or more pieces of assistance information for supporting the above-described paging reception to the base station through the terminal assistance information RRC message. Alternatively, the terminal may transmit one or more pieces of information among the assistance information for supporting the above-described paging reception to the base station through an RRC Setup Complete message. Alternatively, the terminal may transmit one or more pieces of information among the help information for supporting the above-described paging reception to the base station through a measurement reporting (MeasurementReport) message.

The base station may receive the assistance information from the terminal by requesting the corresponding information to the terminal in order to receive the above-described assistance information or by transmitting indication information allowing the transmission of the corresponding information. As an example, one bit of indication information may be explicitly transmitted to system information and received. As another example, when arbitrary information related to system information is included, the terminal may transmit the information and receive it. As another example, it is possible to request to transmit the corresponding information through an arbitrary downlink RRC message, and to receive the corresponding information from the terminal.

The base station may transfer the received information to the AMF.

An embodiment of transmitting help information for supporting paging reception to a base station through NAS signaling

The terminal may be assigned a new terminal temporary identifier (5G-S-TMSI) in the network initial registration process. Alternatively, the terminal may be allocated a new terminal temporary identifier (5G-S-TMSI) in the periodic registration update process. Therefore, it may be desirable to deliver the help information for supporting the above-described paging reception when the terminal performs the initial registration procedure. Alternatively, it may be preferable to deliver help information for supporting paging reception when the terminal performs periodic update. Alternatively, some of the above-described information may be transmitted by the UE to the base station through RRC signaling. Some of the above-mentioned information may be transmitted by the UE to the core network entity (e.g. AMF) through NAS signaling. And the corresponding core network entity can deliver it to the base station.

For example, the terminal may transmit one or more pieces of information among the help information for supporting the above-described paging reception to the AMF through a NAS transport procedure. As another example, the terminal may transmit one or more pieces of information among the help information for supporting the above-described paging reception to the AMF through the registration procedure. As another example, the terminal may transmit one or more pieces of help information for supporting the above-described paging reception to the AMF through a service request procedure.

As another example, the AMF may receive the corresponding information from the terminal by requesting the corresponding information to the terminal in order to receive the corresponding information or transmitting indication information for allowing the corresponding information transmission. Alternatively, the terminal capable of the corresponding function may be configured to include the corresponding information. Capability information for this may be defined and configured in the terminal. For example, indication information for indicating a terminal capable of supporting multiple SIMs may be defined and configured. And/or in the case of a single reception/single transmission terminal (Single Rx/Single Tx UEs) or a dual reception/single transmission terminal (Dual Rx/Single Tx UEs) terminal, the information may be included and transmitted. Alternatively, when the authority is authenticated by the core network entity (e.g. UDM, HSS) through the core network signaling, the AMF may receive it and transmit it to the base station.

Meanwhile, when the base station receives help information for supporting paging reception through the above-described methods, the base station may use the information to enable the terminal to receive paging from a network associated with each subscription. For example, when a multi-SIM terminal is connected to a wireless network associated with one SIM, the base station may not schedule radio resources at a time when paging reception is expected from a network associated with another SIM. As another example, when a multi-SIM terminal is connected to a wireless network associated with one SIM, the base station may indicate to the terminal information about a time gap (GAP) in which paging reception is expected from a network associated with another SIM. . The corresponding gap information may be a value obtained by converting the PO of a wireless network linked to a SIM other than the SIM linked to the connected state base station into an error within the system frame number corresponding to the PCell of the connected state base station and the corresponding system frame number. For example, the corresponding frame SFN may be a value obtained by subtracting (or adding or subtracting) the SFN difference (SFN offset) between the two wireless networks from the value that is modularly calculated with the above-described DRX cycle (T) of the UE.

That is, (SFN + PF_offset - SFN difference) mod T = (T div N) * (UE_ID mod N) or SFN + PF_offset + SFN difference) mod T = (T div N) * (UE_ID mod N) may be . Here, the PF_offset, T, N, and UE_ID parameters are values used to calculate a paging frame of a wireless network associated with a SIM other than the SIM associated with the connected state base station, and may be a value received by the base station from the terminal. PO may also be a value obtained by subtracting (or adding or subtracting) the frame boundary offset from the existing PO. When the corresponding information is indicated, the terminal may not perform one or more operations among arbitrary active state operations. For example, the UE may perform any active state operation SRS transmission, CSI reporting, PDCCH monitoring, PUCCH transmission, serving cell measurement, intra frequency measurement, inter-frequency, inter for a serving cell (PCell or SCell) associated with a connected state base station. -You may not perform all or one or more of the RAT frequency measurements. Alternatively, the terminal may perform paging reception for a PCell of a wireless network associated with a SIM other than the SIM associated with the connected state base station. For this, the gap information may include cell identification information of the corresponding cell.

The help information, etc., transmitted by the terminal to the base station or the core network entity described above may be included in the help information transmitted by the terminal described in FIGS. 10 and 11 to the base station or the core network entity. Alternatively, the above-described transmission/reception information between the terminal and the base station may be performed through separate signaling. Hereinafter, an embodiment of an operation for reducing service interruption of a terminal according to a different embodiment from a paging message will be described in more detail.

Examples of processing by delaying / pending RNAU or TAU

When the terminal is in RRC inactive or RRC idle state in each network associated with multiple SIMs, according to the movement of the terminal or according to a periodic timer configured by the base station or the core network entity (eg AMF), RNAU (RAN-based) notification area updates) or tracking area update (TAU) may be initiated/generated.

- When the AS linked to the two SIMs are both RRC idle and/or RRC inactive

For example, when multiple SIM terminals are in RRC inactive state in a network associated with one SIM and in RRC idle state in networks associated with another SIM, the terminal moves or a periodic timer (eg RRC inactive state) In case of T380 timer, in case of RRC idle state, RAN-based notification area updates (RNAU) or tracking area update (TAU) may occur according to Periodic Registration Update Timer (T3612)). If the NAS or AS in the terminal linked to the two SIMs detects a collision, the terminal can handle it by adjusting it. For example, processing may be performed with priority according to the configuration information indicated by the base station or the core network entity (e.g. AMF). Alternatively, the terminal may process with priority according to information pre-configured according to user preference information or the like.

If the SIM subscription linked to the RRC inactive state takes precedence, the corresponding RNA update may be processed first. The UE may set the TAU update to the pending state in the RRC idle state associated with another SIM. For example, when the UE initiates the RRC establishment/setup procedure, a related variable (e.g. pendingTAupdate) may be defined and the corresponding variable may be set to true. After the RNA update is finished, the UE may enter the RRC inactive (or RRC idle) state in the network associated with the SIM. In this case, the terminal may set the corresponding variable to false. The UE may notify this from the AS to the NAS. The corresponding AS and NAS are mapped to a base station (base station_A)/AMF (AMF_A) linked to one SIM (SIM_A), and AS_A, NAS_A, and a base station (base station) linked to another SIM (SIM_B) AS_B and NAS_B configured in _B)/AMF (AMF_B) may be configured and operated independently. Alternatively, one AS and one NAS may be configured, and two entities may be configured within each AS and NAS to operate independently.

The UE may initiate TAU update. For this purpose, any AS procedure (eg RRC procedure, RRC connection setup request message transmission, RRC connection resume request message transmission, RNAU, paging message reception) or any NAS procedure between AS_A and AS_B or between NAS_A and NAS_B (eg registration request message) , service request message, control plane service request message, NAS transport message transmission, TAU, paging message reception) operation may be indicated when it occurs.

For example, the UE may initiate transmission of an RRC resume request message for RNA update in RRC inactive state in connection with one SIM (SIM_A). The corresponding AS (AS_A) directs this to the AS (AS_B) linked to the other SIM (SIM_B). A higher layer may request establishment of an RRC connection for TA update in the RRC idle state associated with another SIM. If the UE initiates transmission of the RRC resume request message for RNA update in connection with SIM_A, it sets the TAU update to pending state in connection with SIM_B. After the RNA update in connection with the SIM_A is terminated, the UE may enter the RRC inactive (or RRC idle) state in the network associated with the SIM. The corresponding AS (AS_A) directs this to the AS (AS_B) linked to the other SIM. Alternatively, the corresponding AS (AS_A) directs it to the NAS (NAS_A), the NAS_A directs it to the NAS_B linked to another SIM, and the NAS_B directs it to the AS (AS_B). The UE may set the corresponding variable to false in AS_B. The UE may notify this from the AS to the NAS. As described above, the AS and NAS may be configured and operated independently of AS_A, AS_B, NAS_A, and NAS_B, or may be configured with one AS and one NAS and may operate independently within each AS and NAS. The UE may initiate TAU update.

If the SIM subscription associated with the RRC idle state has priority, the UE may preferentially process the corresponding TA update. The UE may set the RNA update to the pending state in the RRC inactive state linked to another SIM. For example, when the UE initiates the RRC resume procedure, a related variable (e.g. pendingRNAupdate or a new variable) may be defined and the corresponding variable may be set to true. After the TA update is finished, the UE may change to an RRC inactive (or RRC idle) state in a network associated with the corresponding SIM. The terminal may set the corresponding variable to false. The UE may notify this from the AS to the NAS. As described above, the AS and NAS may be configured and operated independently of AS_A, AS_B, NAS_A, and NAS_B, or may be configured with one AS and one NAS and may operate independently within each AS and NAS. The terminal may initiate an RNAU update. To this end, similar to the above, the UE performs any AS procedure between AS_A and AS_B or between NAS_A and NAS_B (eg RRC procedure, RRC connection setup request message transmission, RRC connection resume request message transmission, RNAU, paging message reception) or any This may be indicated when a NAS procedure (eg registration request message, service request message, control plane service request message, NAS transport message transmission, TAU, paging message reception) operation occurs. The instruction procedure between AS (AS_A) and AS (AS_B) may use the above.

- When the AS linked to one SIM is RRC connected, the AS linked to the other SIM is in RRC idle/RRC inactive status

A plurality of SIM terminals may be in an RRC connected state in a network associated with one SIM (SIM_A), and may be in an RRC inactive or RRC idle state in a network associated with another SIM (SIM_B). In this case, depending on the movement of the terminal or a periodic timer (eg, T380 timer in RRC inactive state, Periodic Registration Update Timer (T3612) in RRC idle state), RNAU (RAN-based notification area updates) or TAU (tracking area) update) can be initiated/generated.

The UE may set the RNA update to the pending state in the RRC inactive state in the network associated with the other SIM (SIM_B). For example, the UE may define a related variable (e.g. pendingRNAupdate or a new variable) and set the corresponding variable to true. When the RRC resume request procedure for RNA update in connection with SIM_B is started, the UE sets the RNA update in connection with SIM_B to a pending state at any point in time related to the procedure. For example, an arbitrary time point is a time when RRC connection resumption is triggered by a response to NG-RAN paging, an integrated access control procedure execution time, a time when RRC connection resumption is triggered by an upper layer, and transmission of an RRC resumption request message starts It may be any one of the previous, connection state entry/transition reception time from AS_A, and the end time of the gap configured for AS_B operation from AS_A. The gap is further described below.

The UE may go from the RRC connected state to the RRC inactive or RRC idle state for the SIM (SIM_A) in the previously RRC connected state. AS_A may indicate this to AS_B. The terminal may set the corresponding variable to false. The UE may notify this from the AS to the NAS. As described above, the AS and NAS may be configured and operated independently of AS_A, AS_B, NAS_A, and NAS_B, or may be configured with one AS and one NAS and may operate independently within each AS and NAS. The terminal may initiate an RNAU update. The UE may initiate the RRC restart procedure by setting the cause of resumption to RNA update. This can be applied when the SIM subscription associated with the RRC connection state takes precedence or the corresponding configuration does not exist. Alternatively, when the gap configured for AS_B operation starts from AS_A, the UE may set the corresponding variable to false. The UE may notify this from the AS to the NAS. The UE may initiate the RRC restart procedure by setting the cause of resumption to RNA update. The instruction procedure between AS (AS_A) and AS (AS_B) may use the above.

The UE may set the TA update to the pending state in the RRC idle state in the network associated with the other SIM (SIM_B). For example, when initiating the RRC establishment/setup procedure, the UE may define related variables (e.g. pendingTAupdate, pendingsetup) and set the corresponding variables to true. The UE may enter the RRC inactive or RRC idle state in the RRC connected state for the SIM (SIM_A) in the previously RRC connected state. The corresponding AS (AS_A) directs this to the AS (AS_B) linked to the other SIM. The terminal may set the corresponding variable to false. The UE may notify this from the AS to the NAS. The UE may initiate TAU update. This may be applied to a case in which the SIM subscription associated with the RRC connection state takes precedence. Alternatively, it may be applied when the corresponding configuration does not exist.

The UE may set the RNA/TA update to the pending state in the RRC inactive/RRC idle state in a network associated with another SIM. For example, until the gap/period/duration/cycle indicated by the base station is started/started/repeated (or from that point until a certain offset time, e.g., until the offset time indicated by the base station) RNA/TA update can be penned. For convenience of description, this is referred to as a gap below.

For example, when a multi-SIM terminal is in a connection state with a wireless network associated with one SIM (SIM_A), the base station (base station_A) is connected to another SIM (SIM_B) from a network (network_B) associated with it. Radio resource scheduling may not be performed for the expected time/period/duration of paging reception. As another example, when a multi-SIM terminal is in a connection state with a wireless network associated with one SIM (SIM_A), the base station (base station_A) is connected to another SIM (SIM_B) from a network (network_B) A (periodic) TAU or RNAU may not perform radio resource scheduling for an expected time/period/duration. As another example, when a multi-SIM terminal is in a connection state with a wireless network associated with one SIM (SIM_A), the base station (base station_A) connects the terminal to a network (network_B) associated with another SIM (SIM_B) ) and gap/pattern/period (eg start offset/frame/slot/subframe/time point, duration /duration/length, repetition period, timing advance, and one or more of the timing difference between the two wireless networks), and in the gap/pattern/period, radio resource scheduling may not be performed in connection with the SIM.

As another example, when a multi-SIM terminal is in a connection state with a wireless network associated with one SIM, the base station may indicate to the terminal a time gap (GAP) in which paging reception is expected from a network associated with another SIM. The corresponding time gap information may be a value obtained by converting the PO of the wireless network linked to a SIM other than the SIM linked to the connected state base station into an error within the system frame number corresponding to the PCell of the connected state base station and the corresponding system frame number. . For example, the corresponding frame SFN may be a value obtained by subtracting (or adding or subtracting) the SFN difference (SFN offset) between the two wireless networks from the value that is modularly calculated with the above-described DRX cycle (T) of the UE. That is, the value according to (SFN + PF_offset - SFN difference) mod T = (T div N)*(UE_ID mod N) or SFN + PF_offset + SFN difference) mod T = (T div N)*(UE_ID mod N) is can be

Here, the PF_offset, T, N, and UE_ID parameters are values used to calculate a paging frame of a wireless network associated with a SIM other than the SIM associated with the connected state base station, and may be a value received by the base station from the terminal. PO may also be a value obtained by subtracting (or adding or subtracting) the frame boundary offset from the existing PO. When the corresponding information is indicated, the terminal may not perform one or more operations among arbitrary active state operations. For example, the UE may perform any active state operation SRS transmission, CSI reporting, PDCCH monitoring, PUCCH transmission, serving cell measurement, intra frequency measurement, inter-frequency, inter for a serving cell (PCell or SCell) associated with a connected state base station. -You may not perform all or one or more of the RAT frequency measurements. Alternatively, the information may perform paging reception for the PCell of the wireless network associated with the SIM (SIM_B) other than the SIM (SIM_A) associated with the connection state base station. Alternatively, the terminal may perform RNAU or TAU. To this end, the gap information may include cell identification information of the corresponding cell. For another example, the gap may be indicated as a multiple of DRX cycles. As another example, the gap may be indicated by information including a start time (e.g. slot) and a required time. For another example, the corresponding gap may be indicated by converting an estimated time required to perform RANU or TAU in units of slots/subframes/frames.

The UE may go from the RRC connected state to the RRC inactive or RRC idle state for the SIM (SIM_A) in the previously RRC connected state. The corresponding AS (AS_A) directs this to the AS (AS_B) linked to the other SIM. The terminal may set the corresponding variable to false.

Alternatively, the UE may pending the RNA/TA update for the SIM_A from the start of the next gap in the RRC connection state (or from the point in time until a certain offset time, for example, until the offset time indicated by the base station). For example, you can set that variable to false. Alternatively, the terminal may set the corresponding variable to true when the duration/duration/length of the corresponding gap ends. The UE may indicate this to a higher layer. The UE may initiate a NAS or RRC procedure for RNA/TA update.

The above-described gap information and information transmitted by the terminal to the base station or the core network entity may be included in the help information described with reference to FIGS. 10 and 11 . Alternatively, the above-described transmission/reception information between the terminal and the base station may be performed through separate signaling.

An embodiment of processing by delaying / pending RNAU or TAU in the handover process

A plurality of SIM terminals may be in an RRC connected state in a network associated with one SIM (SIM_A), and may be in RRC inactive or RRC idle state in a network associated with another SIM (SIM_B). In this case, when the handover procedure is performed in the corresponding SIM (SIM_A) according to the movement of the terminal, RAN-based notification area updates (RNAU) or tracking area (TAU) in a network associated with another SIM (SIM_B) update) can be initiated/generated. Alternatively, when the handover procedure is performed in the corresponding SIM (SIM_A), the above-described gap configured by the base station may occur or enter into an operation where paging reception is expected in the network associated with the other SIM (SIM_B). there is. If the terminal performs an arbitrary operation (eg tuning/measurement/monitoring/connection setup/registration/TAU/RNAU/uplink transmission) in connection with another SIM while handover is executed in connection with one SIM, it It may cause service interruption in the over process.

Accordingly, the base station configures a specific condition and, under the condition, either enters an omission where paging reception is expected in the network linked to another SIM (SIM_B), or ignores the gap configured by the base station and performs only the operation in the serving network. can be instructed to do so. For example, when the UE receives an RRC reconfiguration message including information necessary to access the target cell (Reconfiguration with Sync), the UE synchronizes with the target cell and transmits the RRC reconfiguration complete message to the target base station by transmitting the RRC hand Until the UE synchronises to the target cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to target gNB, the RNAU or TAU can be pending with the network associated with another SIM. The terminal may set the corresponding variable to a pending state (e.g. true). Alternatively, the UE may ignore the gap indicated by the base station or stop/suspend/stop or not start the procedure associated with another SIM expected for the corresponding gap. After transmitting the RRC reconfiguration complete message to the target base station, the terminal may set the corresponding variable to false. The UE may indicate this to a higher layer. Thereafter, the UE may initiate a NAS or RRC procedure for updating an RNA/TA linked to another SIM. Alternatively, the terminal may receive paging associated with another SIM.

An embodiment of defining terminal capability information for supporting multiple SIM functions regardless of band combination

A network (ex. AMF) or a base station may receive corresponding terminal capability parameter information from a terminal in order to apply the above-described multi-SIM function or a function for an arbitrary multi-SIM to a multi-SIM terminal in the present disclosure. For example, the corresponding parameter may be defined for each functional unit. As another example, the corresponding parameter may include information (e.g. MRDC Single UL transmission) for indicating that the UE does not support uplink simultaneous UL transmissions.

The multiple SIM function may be applied to a terminal supporting the dual connectivity function. For example, an AMF or a base station is a terminal having MRDC terminal capability (eg MRDC-Parameters singleUL-Transmission) applied to a DC (Dual connectivity) or MRDC (Multi RAT Dual Connectivity) capable terminal (or transmitting the information The multi-SIM function described above for the terminal) or a function for an arbitrary multi-SIM may be applied.

As another example, the multiple SIM function should be applicable to a terminal that does not support the dual connectivity function. For this purpose, the multiple SIM function even for a terminal that does not have MRDC terminal capability (eg MRDC-Parameters) applied to a DC (Dual connectivity) or MRDC (Multi RAT Dual Connectivity) capable terminal (or a terminal that does not transmit the corresponding information) If it has a terminal capability that supports , the corresponding function can be applied. In this case, the network or the base station may include information for indicating whether a terminal supporting a plurality of SIM functions performs uplink simultaneous UL transmissions and/or downlink simultaneous DL reception. The corresponding information does not need to be defined for each band combination, unlike the terminal capability information included in the MRDC-parameter. That is, corresponding information may be defined for any band or any band combination. For example, it may include a single TX parameter indicating whether simultaneous uplink transmission (simultaneous UL transmissions) is possible and a single RX parameter indicating whether or not simultaneous downlink reception (simultaneous DL reception) is possible. Each corresponding parameter may consist of 1 bit.

As another example, even in the case of a terminal capable of the aforementioned multiple SIM function or a function for any multiple SIM, if the terminal is set to operate a single SIM, the base station or the network needs to recognize this. . For example, the user can disable one of the two SIMs by changing the settings. If the base station or network associated with another SIM that is not disabled may configure information corresponding to the terminal in order to support the terminal's paging reception from the base station or network associated with the disabled SIM. In this case, the terminal may not receive scheduling for a certain period of time for paging reception from the base station or network associated with the disabled SIM according to the configuration unnecessarily. To prevent this, the terminal may notify the base station or the AMF that the multi-SIM function is disabled through an arbitrary uplink signaling message. In case of notifying the base station through the RRC message, the base station may notify this to the AMF, and in the case of notifying the AMF through the NAS message, the AMF may inform the base station. The message transmitted by the terminal to the base station or the AMF may be any one of the uplink messages mentioned in the above-described embodiments.

The message transmitted by the terminal to the base station or the AMF includes information for identifying the SIM, an index for distinguishing the SIM, and cell information (e,g, cell identifier) connected to the SIM and camped on/selected/reselected by the terminal. , PCI), network information (eg PLMN ID, PLMN ID List, Tracking area code), and frequency of the corresponding cell (eg dl-CarrierFreq). The base station or the AMF may instruct the terminal to release the multiple SIM-related configuration. For example, a corresponding radio resource configuration may be modified/released through an RRC reconfiguration message or the like.

When multiple SIM terminals switch SIMs as in the present embodiments, the base station associated with the connected state SIM to support fast switching may indicate to the terminal information helpful for cell selection/cell reselection associated with other SIMs. there is. For example, if the RRC connection associated with the connected state SIM is disconnected and the RRC connection associated with the inactive/idle state SIM is set up, the base station associated with the connected state SIM selects/selects the cell associated with the other SIM to support fast switching. Information useful for cell reselection may be indicated to the terminal. The message transmitted by the terminal to the base station or the AMF includes information for identifying the SIM, an index for distinguishing the SIM, and cell information (e,g, cell identifier) connected to the SIM and camped on/selected/reselected by the terminal. , PCI), network information (eg PLMN ID, PLMN ID List, Tracking area code), and frequency of the corresponding cell (eg dl-CarrierFreq). The UE may perform cell selection/cell reselection using the received information.

For example, the UE may consider the cell/frequency as the highest priority cell/frequency according to the received information. As another example, when the corresponding information is received, the terminal may ignore all priorities provided in the system information. As another example, the UE may (preferentially) perform cell reselection among cells included in the corresponding cell/cell list.

On the other hand, when the service is terminated in the network associated with another SIM, the terminal can resume the connection to the base station in the previous connection state using the existing RRC procedure (e.g. RRC connection resumption procedure). For example, the terminal receives an RRC connection release message from a base station associated with another SIM. The UE receives the RRC connection release message and performs an operation to go to RRC idle. The UE receives the RRC connection release message and completes the state transition to the RRC idle state. Alternatively, the UE receives the RRC connection release message and enters RRC inactive. Alternatively, after the UE instructs a suspend request to the corresponding network or base station, and after a certain period of time (after expiration of a timer set at a predefined time or an indicated time) has elapsed, the existing RRC procedure (eg RRC connection resumption procedure) is used to transfer Connection can be resumed to the base station in the connected state.

As an example, the UE transmits a suspend instruction and the UE may enter the RRC inactive state immediately (or after the indicated time or autonomously). For example, the UE may transition to the RRC inactive state without performing the RRC release procedure including the suspend configuration information from the base station. As another example, the terminal may not expect to receive a response RRC message to the suspend indication request RRC message from the base station. The UE successfully transmits the RRC message through HARQ ACK reception for the MAC PDU including the RRC message from the MAC entity or the ACK (via the status report) for the RLC PDU including the RLC AM entity from the RLC AM entity. it can be confirmed that If confirmed, the UE may enter the RRC inactive state immediately (or after the indicated time or autonomously). If the UE fails to confirm successful transmission of the RRC message, the UE may perform retransmission (e.g. HARQ retransmission, RLC retransmission, or RRC retransmission in case of RLC failure) for the RRC message. Alternatively, when an RLC failure occurs, the transition to the RRC idle mode may be performed without performing an RRC connection reestablishment procedure. Alternatively, if the suspend configuration information is configured in the terminal, it may be made to transition to the RRC inactive mode.

Information transmitted by the terminal to the base station or the core network entity in each of the above-described embodiments may be included in the help information described with reference to FIGS. 10 and 11 . Alternatively, the above-described transmission/reception information between the terminal and the base station may be performed through separate signaling.

Hereinafter, an embodiment for preventing data transmission/reception collision when a plurality of SIM terminals are linked to a plurality of SIMs to transmit and receive data will be described in detail.

An embodiment of defining a switching condition and requesting to suspend/suspend/release the connection to the base station when the corresponding condition is satisfied

The terminal may instruct/request to suspend/suspend/release the wireless connection with the base station A, which is already transmitting and receiving data in a connected state. For convenience of explanation, this is marked as a suspend request. This is for convenience of description and may be replaced with any similar name. In order to support fast network switching or to prevent abnormal operation of the terminal, it is preferable that a condition triggering transmission of a suspend request to the base station is clearly defined. The condition may be pre-configured in the terminal or may be configured in the terminal by being instructed by the base station.

- Configure information and/or prohibit timers to allow request transmission

The base station may configure the terminal with configuration information for instructing the terminal to allow transmission of the suspend request. The terminal may transmit the suspend request to the base station only when information allowing transmission of the suspend request is configured. Corresponding information may be indicated to the terminal through system information to enable cell-specific indication. Alternatively, the corresponding information may be indicated to the UE through an RRC-only message (e.g. RRC reconfiguration message).

Through this, when the terminal is in the connected state, the terminal can transmit a suspend request to the base station. For example, the base station may set (setup/release) information allowing to send the suspend request information in the Other Configuration information element (otherconfig) included in the RRC reconfiguration message. The suspend request information may indicate information for instructing/requesting the UE to be suspended in an RRC inactive state. Alternatively, the suspend request information may indicate information for instructing/requesting that the terminal is disconnected in the RRC idle state. The suspend request information may indicate information for informing that the terminal will soon transition to the RRC inactive/RRC idle state in connection with the corresponding SIM. The suspend request information may include a suspend request prohibit timer for prohibiting the terminal from continuously transmitting the corresponding information. When the terminal is configured to provide the suspend request information, when setting the contents of an uplink message (eg UE assistance message) including the suspend request information or when transmitting the message to the base station, the suspend request received from the base station is prohibited Starts or restarts the timer set by the timer value. If the terminal experiences a radio link failure, etc. and initiates a connection reconfiguration procedure, the timer is set to the corresponding suspend request prohibit timer value and stops the started or restarted timer.

- Request transmission when receiving paging reception from NAS or AS linked to another SIM

When the terminal (successfully) receives the paging message for the terminal from the network (or base station B) associated with the SIM other than the connected state SIM, the terminal may transmit a suspend request to the base station A associated with the connected state SIM. From the viewpoint of one terminal, the communication module associated with each SIM may be configured independently. For example, the application layer, NAS, and AS linked to each SIM may be independently implemented and operated. For convenience of description, these are denoted as application layer A, application layer B, NAS_A, NAS_B, AS_A, and AS_B.

For example, the AS_B of the terminal receiving the paging message from the base station B may directly deliver it to AS_A. As another example, the AS_B of the terminal receiving the paging message from the base station B may deliver it to the upper layer_B (e.g. NAS_B and/or the application layer B) and the upper layer_B to the upper layer_A. As another example, when AS_A of the terminal receives information indicating that it has (successfully) received the paging message from the base station B for the corresponding terminal from AS_B, it may transmit a suspend request to the base station A associated with the connected state SIM. As another example, when AS_A of the terminal receives information indicating that it has (successfully) received the paging message from the base station B for the corresponding terminal from the upper layer_A, it transmits a suspend request to the base station A associated with the connection state SIM. can do.

- Send request considering preference information first

When the related user preference information is pre-configured/set, the terminal may transmit a suspend instruction to the base station A associated with the connected state SIM. The determination of whether to continue to maintain an on-going service in connection with the connected state SIM or to operate to receive a new incoming service in connection with another SIM may be determined by a terminal user input signal. Alternatively, user preference information (or default configuration information) related thereto may be pre-configured in the terminal or may be configured by being directed to the terminal by the base station.

As an example, the user preference information may be implemented so that the user can directly set it in the terminal. The information is displayed on the preference/priority of the SIM (eg priority of SIM A > priority of SIM B), and preference/priority of SIM (eg priority of PLMN A > priority of PLMN B) in the network connected to the SIM (eg PLMN). priority), whether to allow receiving or sending data from other networks while connected to a network associated with one SIM (eg, at least one of voice, SMS, multimedia, and data), while connected to a network associated with one SIM It may include information on one or more of a service category (eg, one or more of voice, SMS, multimedia, and data) that is allowed to receive paging or send data from another network.

As another example, when attempting to establish a connection to a base station B due to a SIM preferred by the user preference information, a network associated with the preferred SIM, or a preferred service, the terminal sends a suspend instruction to the base station A associated with the SIM can be transmitted

- Send request when paging indicates a specific service

When the terminal receives a paging indicating one of MMTEL voice, MMTEL video, and SMS for the terminal from a network (or base station B) associated with a SIM other than the connected state SIM, to the base station A associated with the connected state SIM A suspend request may be sent.

For example, the base station may include, as a new information element in the paging message, information indicating that the service that triggered the corresponding paging is any one of MMTEL voice, MMTEL video, or SMS. As another example, the base station may include information indicating that the service that triggered the corresponding paging is any one of MMTEL voice, MMTEL video, or SMS as a new information element in the paging record information element in the paging message. As another example, the base station receives a paging message indicating that the service triggering the corresponding paging is any one of MMTEL voice, MMTEL video, or SMS, and the terminal initiates a service request procedure. Accordingly, the RRC connection setup message (RRC Setup) received from the base station in response to the RRC connection setup request message (RRC Setup Request) or any downlink RRC message (eg RRC connection reconfiguration message) generated thereafter triggers the corresponding paging It may include information indicating that one service is one of MMTEL voice, MMTEL video, or SMS. As another example, in order to receive a paging message indicating that the service that triggered the corresponding paging is any one of MMTEL voice, MMTEL video, or SMS, and the terminal initiates a service request procedure, the base station performs random access to the terminal MSG2 Alternatively, when performing two-step random access, the MSGB may include information indicating that the service that triggered the paging is one of MMTEL voice, MMTEL video, and SMS. A base station for indicating this may generate and indicate a MAC CE. The corresponding MAC CE may include an information field for identifying the corresponding service. Alternatively, the service may be identified using the LCID. Alternatively, the corresponding service may be classified and indicated by including the MAC PDU classified in the MSGB. As another example, the base station may configure a plurality of SIM terminals to perform paging to the terminal only when paging is indicated by one of MMTEL voice, MMTEL video, or SMS service. The corresponding information may be set by receiving the subscription information of the terminal or the corresponding information from the terminal.

Perform signaling with the corresponding network/base station according to the switching decision

A plurality of SIM terminals may perform registration in association with each SIM. For example, the terminal may perform a registration procedure in a corresponding network in connection with one SIM. In addition, the terminal may perform a registration procedure in the network associated with the SIM in connection with another SIM in the idle state or inactive state with the network associated with the SIM. Multiple SIM terminals communicate in an active state (eg, RRC connected state) through a system associated with one SIM, and perform other activities (eg, RRC idle or RRC inactive state) in a system associated with another SIM. Paging reception, or connection setup according to this, or tracking area update or RNAU according to terminal movement: RAN-based notification area update, or connection setup by mobile outgoing data generation in RRC idle or RRC inactive state, etc.) may have to

According to the above-described embodiments, the terminal may determine whether to continue to maintain an on-going service in connection with the connected state SIM or to operate to receive a new incoming service in connection with another SIM.

- If you decide to keep the linked SIM connection (decided not to switch)

If it is decided not to switch, the terminal may continue to maintain an on-going service in connection with the connected state SIM.

When the terminal receives a paging in connection with another SIM, it may instruct the corresponding base station/AMF to reject the paging reception. For example, the terminal may indicate rejection of the corresponding paging message through one of any uplink NAS messages (e.g. registration request message, service request message, control plane service request message, NAS transport message). The AMF may send an acceptance message or a confirmation message for this to the terminal. Alternatively, the AMF may not send an acceptance message or a confirmation message. For another example, the UE may initiate a de-registration procedure. The terminal may instruct the corresponding base station/AMF to reject the paging reception through the DEREGISTRATION REQUEST message initiated by the terminal.

The AMF may transmit it to the base station. Indicative information for this may be included in the downlink message through the interface between the base station and the AMF.

For another example, the UE may indicate rejection of the corresponding paging message through one of arbitrary uplink RRC messages (e.g. RRC setup request message, UL Information transfer message, and UE assistance message). Information for indicating this may be included in the corresponding message. Alternatively, the UE may generate and instruct the MAC CE to indicate this. Alternatively, the UE may indicate this by designating and using a specific LCID. For another example, the UE may instruct rejection of the corresponding paging message through a FailureInformation RRC message. Information for indicating this may be included in the corresponding message. Alternatively, the UE may generate and instruct the MAC CE to indicate this. Alternatively, the UE may indicate this by designating and using a specific LCID.

When the base station receives an indication from the terminal, it may transmit it to the AMF. For example, the base station may include indication information for this in an uplink message through an interface between the base station and the AMF.

Meanwhile, in the above-described embodiments, each corresponding message/indication information may include indication information for recommending/limiting the next paging attempt. For example, it may include information for indicating that a paging attempt is recommended/permitted for the corresponding terminal. For example, service/radio bearer/LCID/Flow/QFI/PDU session information for which a paging attempt is recommended for the corresponding terminal may be included. To this end, the paging attempt may include one or more information of service type (voice)/radio bearer identification information/LCID/Flow identification information/QFI/PDU session identification information recommended/allowed for a paging attempt for the corresponding terminal. The network receiving the corresponding indication information may attempt paging when paging is started by the corresponding service (voice)/radio bearer/LCID/Flow/QFI/PDU session for the corresponding terminal. As another example, it may include indication information for limiting that paging is not performed for the corresponding terminal. The network receiving the corresponding indication information may not attempt paging with respect to the corresponding terminal in any case. Alternatively, the network receiving the corresponding indication information may not attempt paging for the corresponding terminal in any case except for an emergency service. For another example, the indication information for limiting that the terminal is not performing paging may include a timer for limiting that paging is not performed. For convenience of explanation, this is denoted as a back-off timer. This is only for convenience of description, and may be replaced with any name such as recommendation/expectation/prediction/next paging timer/duration/cycle/period/time/DRX number. The base station or AMF starts a timer set to the received parameter value. The base station or the AMF may not perform the paging attempt/retry while the corresponding timer is operating. .

When a terminal in RRC idle or RRC inactive state in connection with a SIM other than the connected SIM wants to perform a connection setup procedure by updating the tracking area, RNAU, or mobile outgoing data generation according to the movement of the terminal, the terminal performs the procedure can be suspended/suspended/unset/ignored/pending. Indicative information for this may be received from the base station associated with the connected state SIM and configured in the terminal. Alternatively, the indication information may be included and transmitted when instructing a transition to an RRC idle or RRC inactive state from a base station associated with another SIM through an RRC release message. In addition, the indication information may include a timer/duration/period/period/time for suspending/suspending/releasing/ignoring/pending the corresponding procedure. .

- In case of determining the linked SIM switching

If switching is determined, the UE may instruct/request to suspend/suspend/release the corresponding connection/PDU session to the base station/AMF associated with the connection state SIM.

When the terminal receives a paging in connection with another SIM, the terminal suspends the corresponding connection/PDU session to the base station/AMF associated with the connected state SIM in order to receive the corresponding paging and/or to perform the subsequent RRC connection setup procedure/service request procedure. You can instruct/request to /suspend/release.

For example, the terminal suspends/suspends/releases the corresponding connection/PDU session through any one of uplink NAS messages (eg registration request message, service request message, control plane service request message, NAS transport message). can be instructed/requested. The AMF may send an acceptance message or a confirmation message for this to the terminal. Alternatively, the AMF may not send an acceptance message or a confirmation message. For another example, the UE may initiate a de-registration procedure. The terminal may instruct the corresponding base station/AMF to suspend/suspend/release the corresponding connection/PDU session through the DEREGISTRATION REQUEST message initiated by the terminal.

The AMF may transmit it to the base station. Indicative information for this may be included in the downlink message through the interface between the base station and the AMF.

For another example, the UE may instruct suspend/suspend/release of the corresponding connection/PDU session through one of any uplink RRC messages (eg RRC setup request message, UL Information transfer message, UE assistance message). there is. Information (e.g. cause) for indicating this may be included in the corresponding message. Alternatively, the UE may generate and transmit a MAC CE to indicate this. Alternatively, the UE may indicate this by designating a specific LCID. For another example, the UE may instruct suspend/suspend/release of the corresponding connection/PDU session through a FailureInformation RRC message. Information for indicating this may be included in the corresponding message. Alternatively, the UE may generate and transmit a MAC CE to indicate this. Alternatively, the UE may indicate this by designating and using a specific LCID.

The base station may transmit it to the AMF. Indicative information for this may be included in the uplink message through the interface between the base station and the AMF.

In the above-described embodiments, each corresponding message/indication information may include indication information for recommending/limiting the next paging attempt by the corresponding base station. For example, it may include information for indicating that a paging attempt is recommended/permitted for the corresponding terminal. For example, service/radio bearer/LCID/Flow/QFI/PDU session information for which a paging attempt is recommended/allowed for the corresponding UE may be included. To this end, it may include one or more information of service type (voice)/radio bearer identification information/LCID/flow identification information/QFI/PDU session identification information recommended for a paging attempt for the corresponding terminal. The network receiving the corresponding indication information may attempt paging when paging is started by the corresponding service (voice)/radio bearer/LCID/Flow/QFI/PDU session for the corresponding terminal. As another example, it may include indication information for limiting that paging is not performed for the corresponding terminal. The network receiving the corresponding indication information may not attempt paging with respect to the corresponding terminal in any case. Alternatively, the network receiving the corresponding indication information may not attempt paging for the corresponding terminal in any case except for an emergency service. For another example, the indication information for limiting that the terminal is not performing paging may include a timer for limiting that paging is not performed. For convenience of explanation, this is denoted as a back-off timer. This is only for convenience of description, and may be replaced with any name such as recommendation/expectation/prediction/next paging timer/duration/cycle/period/time/number of DRX. The base station or AMF starts a timer set to the received parameter value. It may be set not to perform a paging attempt/retry while the corresponding timer is operating.

The terminal may transmit help information that can help in radio resource/network management, such as recommendation/permission/restriction on paging attempts of the base station/AMF. For example, the help information may include information for indicating that a service that will trigger a corresponding request is any one of MMTEL voice, MMTEL video, and SMS. For another example, the help information may include one or more of radio bearer identification information/LCID/Flow identification information/QFI/PDU session identification information to recommend/allow/limit paging attempts. For another example, the terminal may transmit information for instructing transmission of a suspend request by paging from a base station associated with another SIM. For another example, the terminal may transmit expected/expected suspend time/period/duration information. For another example, the terminal may transmit time/period/duration information for limiting the (maximum) suspend time.

The terminal may transmit the corresponding information to the base station through arbitrary signaling. For example, the signaling may be an RRC message. As another example, the signaling may be transmitted to the base station through the MAC CE.

Procedure processing instruction following the paging procedure after suspend

Upon receiving the suspend request information from the terminal, the base station may suspend/suspend/release the RRC connection. The base station may release the RRC connection or suspend the RRC connection through the RRC connection release procedure. The base station may transmit information for instructing the terminal operation during or after the suspend process through the corresponding message. For example, after the UE transitions to the RRC inactive state for the base station associated with the corresponding SIM, the terminal may resume the suspended/suspended procedure (or subsequent operation) for the base station associated with the other SIM. The corresponding procedure (subsequent operation) can be one of the following operations.

- Resume instruction from AS_A to AS_B

- Resume instruction from AS_A to upper layer (NAS_A)

- When a paging message is received, the terminal identifier and access type are forwarded to the upper layers (forward the ue-Identity and accessType (if present) to the upper layers;)

- Initiation of RRC connection resumption procedure (or sending RRC connection resumption request message)

- Initiate RRC connection setup procedure (or send RRC connection setup request message)

- NAS procedure (e.g. service request procedure) initiation (or NAS message transmission or NAS message delivery to the lower layer)

- Send RRC connection resume completion message

- Send RRC connection setup complete message

- Transmission of arbitrary uplink signaling to the corresponding base station

For example, if the terminal receiving the RRC release message from the base station receives the RRC release message with the suspend configuration in response to the RRC resume request message, a timer starts when the RRC resume request message is transmitted If it is, stop the timer.

The UE replaces the parameters (eg. KgNB, KRRCint, C-RNTI, cellIdentity, physical cell identity) in the UE inactive AS context with the received value.

The UE suspends all SRB(s) and DRB(s) except for SRB0.

The UE instructs PDCP suspend to the lower layers of all DRBs.

The UE notifies the suspension of the RRC connection to the upper layer.

The UE enters the RRC inactive state and performs cell selection.

The terminal instructs the resumption to the AS linked to the other SIM.

Identifier/index information for identifying AS/RRC associated with each SIM may be defined in the RRC information element. Through this, the base station and the terminal can distinguish them.

The transmission/reception information for the data transmission/reception collision avoidance embodiment described above may be included in the help information information described with reference to FIGS. 10 and 11 , or may be transmitted/received through additional additional signaling.

According to the operation described above, a terminal having a plurality of SIMs can perform a smooth paging operation, and can prevent service interruption and transmission/reception data collision. Hereinafter, a terminal and a base station apparatus capable of performing all or any combination of the above-described embodiments will be described.

12 is a diagram showing the configuration of a terminal according to an embodiment.

Referring to FIG. 12 , a terminal 1200 performing communication using a plurality of USIMs is concurrently registered with one or more networks associated with the plurality of SIMs, and one or more networks in a connected state It includes a control unit 1210 that determines the release of , and a transmitter 1220 that transmits help information for instructing release to a base station or a core network control plane entity.

The controller 1210 monitors the paging message based on the help information.

For example, a terminal performing communication using a plurality of USIMs may be concurrently registered with one or more networks associated with the plurality of SIMs. The controller 1210 may determine release of one or more networks associated with a plurality of SIMs according to arbitrary conditions. For example, the controller 1210 may disconnect the network associated with any one SIM according to a user input signal. Alternatively, the controller 1210 may determine to release a network associated with a specific SIM according to a priority or whether a preset condition is satisfied.

Help information may be transmitted by being included in a NAS transport message or a NAS deregistration message. In addition, the help information may include information for limiting or allowing the transmission of the paging message to the terminal for a predetermined period of time preset by the base station or the core network control plane entity.

For example, information for limiting or allowing paging message transmission includes information for instructing that only voice data be paged, information for instructing limiting paging, radio bearer information for limiting or allowing paging, logical channel identification information (LCID) , a flow identification number, QoS Flow ID (QFI) information, and may include at least one of PDU session identification information.

Meanwhile, the receiving unit 1230 may receive indication information indicating whether the transmission of help information is permitted from the base station or the core network control plane entity (eg, AMF) before the control unit 1210 determines release. Only when the transmission of the help information is permitted by the indication information, the controller 1210 may transmit the help information.

When the transmission of the paging message is restricted based on the help information, the controller 1210 may monitor the paging message in consideration of the restriction. Alternatively, when the transmission of the paging message is permitted based on the help information, the controller 1210 may monitor the paging message in consideration of the corresponding matter.

Alternatively, the controller 1210 may monitor a paging message in a specific paging error or paging frame determined based on the help information.

Meanwhile, the controller 1210 may not accept the paging message reception even if the paging message is checked as a result of monitoring the paging message. If the controller 1210 does not accept the reception of the paging message, the transmitter 1220 may transmit non-acceptance indication information for the paging message to the base station or the core network control plane entity.

Whether the controller 1210 accepts the reception of the paging message may be classified according to the cause of the paging. For example, the paging message may include paging cause information. The controller 1210 may determine whether to accept the reception of the paging message based on the paging cause information.

For example, the paging cause information may include information indicating voice data. For example, when the paging cause information indicates voice data, the controller 1210 may receive the paging message, otherwise, the controller 1210 may not accept the reception.

In addition to this, the controller 1210 controls the overall operation of the terminal 1200 necessary for a plurality of SIM terminals to perform a paging operation, service interruption reduction, and transmission/reception collision prevention operation required for performing the above-described embodiments.

In addition, the transmitter 1220 and the receiver 1230 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments with the base station or the core network entity.

13 is a diagram showing the configuration of a base station according to an embodiment.

Referring to FIG. 13 , a base station 1300 performing communication with a terminal using a plurality of USIMs instructs disconnection transmitted from terminals concurrently registered in one or more networks associated with the plurality of SIMs. It may include a receiving unit 1330 for receiving help information for this from the core network control plane entity, and a controller 1310 for controlling transmission of a paging message to the terminal based on the help information.

A terminal performing communication using a plurality of USIMs may be concurrently registered with one or more networks associated with the plurality of SIMs. The terminal may decide to release one or more networks associated with a plurality of SIMs according to arbitrary conditions. For example, the terminal may disconnect the network associated with any one SIM according to a user input signal. Alternatively, the terminal may decide to release the network associated with a specific SIM according to priority or whether a preset condition is satisfied.

The terminal may transmit help information for instructing release to the base station or the core network control plane entity. When the terminal transmits the help information to the core network control plane entity, the receiver 1330 may receive the help information from the core network control plane entity. For example, the help information may receive the help information through an interface (eg, N2 interface) between the base station and the core network control plane entity.

For example, the help information may be included in a NAS transport message or a NAS deregistration message and received as a core network control plane entity. In addition, the help information may include information for limiting or allowing the transmission of the paging message to the terminal for a predetermined period of time preset by the base station or the core network control plane entity.

For example, information for limiting or allowing paging message transmission includes information for instructing that only voice data be paged, information for instructing limiting paging, radio bearer information for limiting or allowing paging, logical channel identification information (LCID) , a flow identification number, QoS Flow ID (QFI) information, and may include at least one of PDU session identification information.

On the other hand, before the terminal decides to release, the base station or the core network control plane entity (ex, AMF) may transmit indication information indicating whether the terminal's help information transmission is allowed. The terminal can transmit the help information only when the transmission of the help information is permitted by the indication information.

The controller 1310 may determine whether to transmit the paging message to the terminal based on the help information. When the transmission of the paging message is restricted by the help information, the controller 1310 controls the transmission of the paging message in consideration of the restriction. Alternatively, the controller 1310 may control the paging message to be transmitted in a specific paging error or paging frame determined based on the help information.

When the transmission of the paging message is restricted based on the help information, the UE may monitor the paging message in consideration of the restriction. Alternatively, when the transmission of the paging message is allowed based on the help information, the terminal may monitor the paging message in consideration of the corresponding matter. Alternatively, the terminal may monitor a paging message in a specific paging error or paging frame determined based on the help information.

Meanwhile, the terminal may not accept the reception of the paging message even if the paging message is confirmed as a result of monitoring the paging message. If the terminal does not accept the reception of the paging message, the terminal may transmit non-acceptance indication information for the paging message to the base station or the core network control plane entity. The receiver 1330 may receive non-acceptance indication information.

Whether the terminal accepts the reception of the paging message may be classified according to the cause of the paging. For example, the paging message may include paging cause information. The terminal may determine whether to accept the reception of the paging message based on the paging cause information. To this end, the transmitter 1320 may include the paging cause information in the paging message and transmit it.

For example, the paging cause information may include information indicating voice data. For example, if the paging cause information indicates voice data, the terminal may receive the paging message, otherwise it may not accept the reception.

In addition to this, the controller 1310 controls the overall operation of the base station 1300 necessary for a plurality of SIM terminals to perform a paging operation, a service interruption reduction, and an operation for preventing transmission/reception collision.

In addition, the transmitter 1320 and the receiver 1330 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments with the terminal or the core network entity.

The above-described embodiments may be supported by standard documents disclosed in at least one of IEEE 802, 3GPP and 3GPP2, which are wireless access systems. That is, steps, configurations, and parts not described in order to clearly reveal the technical idea of the present embodiments may be supported by the above-described standard documents. In addition, all terms disclosed in this specification can be explained by the standard documents disclosed above.

The above-described embodiments may be implemented through various means. For example, the present embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of implementation by hardware, the method according to the present embodiments may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), FPGAs (Field Programmable Gate Arrays), may be implemented by a processor, a controller, a microcontroller or a microprocessor.

In the case of implementation by firmware or software, the method according to the present embodiments may be implemented in the form of an apparatus, procedure, or function that performs the functions or operations described above. The software code may be stored in the memory unit and driven by the processor. The memory unit may be located inside or outside the processor, and may transmit and receive data to and from the processor by various known means.

Also, as described above, terms such as "system", "processor", "controller", "component", "module", "interface", "model", or "unit" generally refer to computer-related entities hardware, hardware and software. may mean a combination of, software, or running software. For example, the aforementioned components may be, but are not limited to, a process run by a processor, a processor, a controller, a controlling processor, an object, a thread of execution, a program, and/or a computer. For example, both an application running on a controller or processor and a controller or processor can be a component. One or more components may reside within a process and/or thread of execution, and the components may be located on one device (eg, a system, computing device, etc.) or distributed across two or more devices.

The above description is merely illustrative of the technical spirit of the present disclosure, and various modifications and variations will be possible without departing from the essential characteristics of the present disclosure by those skilled in the art to which the present disclosure pertains. In addition, the present embodiments are not intended to limit the technical spirit of the present disclosure, but rather to explain, so the scope of the present technical spirit is not limited by these embodiments. The protection scope of the present disclosure should be construed by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present disclosure.

Claims (22)

In a method for a terminal to communicate using a plurality of USIMs,
in a state of concurrent registration in one or more networks associated with a plurality of SIMs, determining release of the one or more networks in a connected state;
transmitting help information for instructing the release to a base station or a core network control plane entity; and
and monitoring a paging message based on the help information. The method of claim 1,
Prior to the step of determining the release,
The method further comprising the step of receiving indication information indicating whether to allow the transmission of the help information from the base station or the core network control plane entity. The method of claim 1,
The help information is
How it is transmitted as part of a NAS transport message or a NAS deregistration message. The method of claim 1,
The help information is
The method of including information for restricting or allowing the transmission of the paging message to the terminal for a predetermined period of time by the base station or the core network control plane entity. 5. The method of claim 4
The information for restricting or allowing the transmission of the paging message,
Information for indicating that only voice data is to be paged, information for indicating paging restriction, radio bearer information for restricting or allowing paging, logical channel identification information (LCID), flow identification number, QoS Flow ID (QFI) information and PDU A method comprising at least one of session identification information. The method of claim 1,
The step of monitoring the paging message comprises:
When the reception of the paging message is not accepted, the non-acceptance indication information for the paging message is transmitted to the base station or the core network control plane entity. The method of claim 1,
The paging message is
A method including paging cause information, wherein the paging cause information includes information indicating voice data. In a method for a base station to communicate with a terminal using a plurality of USIMs,
receiving, from a core network control plane entity, help information for instructing disconnection transmitted from terminals simultaneously registered in one or more networks associated with a plurality of SIMs; and
and controlling transmission of a paging message to the terminal based on the help information. 9. The method of claim 8,
Prior to the receiving step,
The method further comprising the step of transmitting indication information indicating whether to allow the transmission of the help information to the terminal. 9. The method of claim 8,
The help information is
The method of including information for restricting or allowing the transmission of the paging message to the terminal for a predetermined period of time by the base station or the core network control plane entity. 11. The method of claim 10
The information for restricting or allowing the transmission of the paging message,
Information for indicating that only voice data is to be paged, information for indicating paging restriction, radio bearer information for restricting or allowing paging, logical channel identification information (LCID), flow identification number, QoS Flow ID (QFI) information and PDU A method comprising at least one of session identification information. In a terminal performing communication using a plurality of USIMs,
a control unit configured to determine release of the one or more networks in a connected state in a state of concurrent registration in one or more networks linked to a plurality of SIMs; and
A transmitter for transmitting help information for instructing the release to a base station or a core network control plane entity,
The control unit is
A terminal for monitoring a paging message based on the help information. 13. The method of claim 12,
The terminal further comprising a receiver for receiving indication information indicating whether to allow the transmission of the help information from the base station or the core network control plane entity. 13. The method of claim 12,
The help information is
A terminal transmitted by being included in a NAS transport message or a NAS deregistration message. 13. The method of claim 12,
The help information is
A terminal comprising information for restricting or allowing the transmission of the paging message to the terminal for a predetermined period of time preset by the base station or the core network control plane entity. 16. The method of claim 15
The information for restricting or allowing the transmission of the paging message,
Information for indicating that only voice data is to be paged, information for indicating paging restriction, radio bearer information for restricting or allowing paging, logical channel identification information (LCID), flow identification number, QoS Flow ID (QFI) information and PDU A terminal including at least one piece of session identification information. 13. The method of claim 12,
The transmitter is
When the control unit does not accept the reception of the paging message as a result of monitoring the paging message, the terminal further transmits non-acceptance indication information for the paging message to the base station or the core network control plane entity. 13. The method of claim 12,
The paging message is
A terminal including paging cause information, wherein the paging cause information includes information indicating voice data. In a base station for communicating with a terminal using a plurality of USIMs,
a receiver for receiving, from a core network control plane entity, help information for instructing disconnection transmitted from terminals simultaneously registered in one or more networks linked to a plurality of SIMs; and
A base station comprising a control unit for controlling transmission of a paging message to the terminal based on the help information. 20. The method of claim 19,
The base station further comprising a transmitter for transmitting indication information indicating whether to allow the transmission of the help information to the terminal. 20. The method of claim 19,
The help information is
The base station or the core network control plane entity includes information for restricting or permitting transmission of the paging message to the terminal for a preset period of time. 22. The method of claim 21
The information for restricting or allowing the transmission of the paging message,
Information for indicating that only voice data is to be paged, information for indicating paging restriction, radio bearer information for restricting or allowing paging, logical channel identification information (LCID), flow identification number, QoS Flow ID (QFI) information and PDU A base station including at least one piece of session identification information.

Images