KR20220136766A - Method and apparatus for transmitting and receiving a signal in a wireless communication system - Google Patents

Abstract

The present invention relates to a method and apparatus for transmitting and receiving signals in a wireless communication system. A method of operating a terminal supporting a plurality of Universal Subscriber Identity Modules (USIMs) in a wireless communication system according to the present invention may comprise the steps of: receiving system information from a base station based on a first USIM among the plurality of USIMs; receiving a paging message from the base station based on the first USIM among the plurality of USIMs; determining whether a paging cause value is included in the paging message; and performing an operation by the first USIM or the second USIM among the plurality of USIMs, based on a result of the determination. The present invention is to provide an apparatus and method capable of effectively providing a service in a mobile communication system.

Description

Method and apparatus for transmitting and receiving signals in a wireless communication system

The present disclosure relates to a method and apparatus for transmitting and receiving a signal in a wireless communication system.

Efforts are being made to develop an improved ^5th generation ( ^5G ) communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G (4th generation) communication system. For this reason, the 5G communication system or the pre-5G communication system is called a system after the 4G network (Beyond 4G Network) communication system or the LTE system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the very high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, the advanced coding modulation (ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

As various services can be provided according to the development of the wireless communication system as described above, a method for smoothly providing these services is required.

Based on the above discussion, the present disclosure provides an apparatus and method for effectively providing a service in a mobile communication system.

According to an embodiment of the present disclosure, in a method of operating a terminal supporting a plurality of Universal Subscriber Identity Modules (USIMs) in a wireless communication system, based on a first USIM among the plurality of USIMs, system information is received from a base station. step, receiving a paging message from the base station based on the first USIM among the plurality of USIMs, determining whether a paging cause value is included in the paging message, and the determination based on a result of , performing an operation by the first USIM or the second USIM among the plurality of USIMs.

The disclosed embodiment provides an apparatus and method for effectively providing a service in a mobile communication system.

1A is a diagram illustrating a structure of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure.
1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present disclosure.
1C is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
FIG. 1E is a view showing a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) releases an RRC connection mode (RRC_CONNECTED) from a base station associated with one USIM, and releases another USIM, according to an embodiment of the present disclosure; FIG. It is a diagram showing a method of performing an operation related to .
FIG. 1f illustrates operations of a terminal and a base station when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a base station associated with one USIM, according to an embodiment of the present disclosure; It is a flow chart.
FIG. 1G illustrates operations of a terminal and a base station when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a network associated with one USIM, according to an embodiment of the present disclosure; It is a flow chart.
1H is a flowchart illustrating the operation of a terminal when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a network associated with one USIM, according to an embodiment of the present disclosure; .
1I is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present disclosure.
1J is a block diagram illustrating the configuration of an NR base station according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, in the description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

Advantages and features of the present disclosure, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only the present embodiments allow the disclosure of the present disclosure to be complete, and common knowledge in the technical field to which the present disclosure belongs It is provided to fully inform the possessor of the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible for the instructions stored in the flowchart block(s) to produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in the blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~ unit' performs certain roles do. However, '-part' is not limited to software or hardware. '~unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Thus, as an example, '~' denotes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, in an embodiment, '~ part' may include one or more processors.

In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

A term for identifying an access node used in the following description, a term referring to a network entity (network entity), a term referring to messages, a term referring to an interface between network objects, and various identification information Reference terms and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

In the following description, a physical channel and a signal may be used interchangeably with data or a control signal. For example, a physical downlink shared channel (PDSCH) is a term referring to a physical channel through which data is transmitted, but the PDSCH may also be used to refer to data. That is, in the present disclosure, an expression 'transmitting a physical channel' may be interpreted equivalently to an expression 'transmitting data or a signal through a physical channel'.

Hereinafter, in the present disclosure, higher signaling refers to a signal transmission method in which a base station is transmitted to a terminal using a downlink data channel of a physical layer, or from a terminal to a base station using an uplink data channel of a physical layer. Upper signaling may be understood as radio resource control (RRC) signaling or media access control (MAC) control element (CE).

For convenience of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project NR (New Radio) (3GPP) or 3rd Generation Partnership Project Long Term Evolution (LTE) standard. However, the present disclosure is not limited by the terms and names, and may be equally applied to systems conforming to other standards. In the present disclosure, gNB may be used interchangeably with eNB for convenience of description. That is, a base station described as an eNB may represent a gNB. Also, the term terminal may refer to mobile phones, MTC devices, NB-IoT devices, sensors, as well as other wireless communication devices.

Hereinafter, the base station, as a subject performing resource allocation of the terminal, is at least one of gNode B (gNB), eNode B (eNB), Node B, BS (Base Station), radio access unit, base station controller, or a node on the network. can The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Of course, it is not limited to the above example.

Also, in the present disclosure, the controller may be designated as a processor.

Also, in the present disclosure, a layer (layer device) may be referred to as a layer or an entity.

The present disclosure describes a method and apparatus for discriminating a paging cause in a next-generation mobile communication system.

1A is a diagram illustrating a structure of an LTE system according to an embodiment of the present disclosure.

Referring to Figure 1a, as shown, the radio access network of the LTE system is a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20) and It may be composed of MME (1a-25, Mobility Management Entity) and S-GW (1a-30, Serving-Gateway). User equipment (hereinafter referred to as UE or terminal) 1a-35 may access an external network through ENBs 1a-05 to 1a-20 and S-GW 1a-30.

In FIG. 1A , ENBs 1a-05 to 1a-20 may correspond to existing Node Bs of the UMTS system. The ENB is connected to the UEs 1a-35 through a radio channel and can perform a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) through the Internet protocol, are serviced through a shared channel, so status information such as buffer status, available transmission power status, and channel status of UEs A device for scheduling is required, and the ENBs 1a-05 to 1a-20 can be in charge of this. One ENB can usually control multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system may use, for example, Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a radio access technology in a 20 MHz bandwidth. In addition, an Adaptive Modulation & Coding (AMC) scheme that determines a modulation scheme and a channel coding rate according to the channel state of the terminal may be applied. The S-GW 1a-30 is a device that provides a data bearer, and may create or remove a data bearer under the control of the MME 1a-25. The MME is a device in charge of various control functions as well as a mobility management function for the UE, and can be connected to a plurality of base stations.

1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present disclosure.

Referring to FIG. 1b, the radio protocol of the LTE system is PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), MAC (Medium Access) in the UE and ENB, respectively. Control 1b-15, 1b-30). Packet Data Convergence Protocol (PDCP) (1b-05, 1b-40) may be in charge of operations such as IP header compression/restore. The main functions of PDCP are summarized below.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

- Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

- Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

The radio link control (hereinafter referred to as RLC) 1b-10 and 1b-35 may perform ARQ operation by reconfiguring a PDCP packet data unit (PDU) to an appropriate size. The main functions of RLC are summarized below.

- Data transfer function (Transfer of upper layer PDUs)

- ARQ function (Error Correction through ARQ (only for AM data transfer))

- Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)

- Re-segmentation of RLC data PDUs (only for AM data transfer)

- Reordering of RLC data PDUs (only for UM and AM data transfer)

- Duplicate detection (only for UM and AM data transfer)

- Protocol error detection (only for AM data transfer)

- RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))

- RLC re-establishment function (RLC re-establishment)

The MACs 1b-15 and 1b-30 are connected to several RLC layer devices configured in one terminal, and may perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized below.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels)

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The physical layer (1b-20, 1b-25) channel-codes and modulates upper layer data, converts it into an OFDM symbol and transmits it over a radio channel, or demodulates and channel-decodes an OFDM symbol received through the radio channel and transmits it to an upper layer action can be made.

1C is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

1c, as shown, the radio access network of the next-generation mobile communication system (hereinafter referred to as NR or 5g) is a next-generation base station (New Radio Node B, hereinafter, NR gNB or NR base station) 1c-10 and NR CN 1c -05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) 1c-15 may access an external network through NR gNB 1c-10 and NR CN 1c-05.

In FIG. 1c , the NR gNB 1c-10 may correspond to an Evolved Node B (eNB) of the existing LTE system. The NR gNB (1c-10) is connected to the NR UE (1c-15) through a radio channel and can provide a service superior to that of the existing Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs is required. (1c-10) may be in charge. One NR gNB 1c-10 can typically control multiple cells. In order to implement ultra-high-speed data transmission compared to current LTE, it can have more than the existing maximum bandwidth, and additionally beamforming technology can be grafted by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a radio access technology. . In addition, an adaptive modulation & coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the terminal may be applied. The NR CN (1c-05) may perform functions such as mobility support, bearer setup, QoS setup, and the like. The NR CN (1c-05) is a device in charge of various control functions as well as a mobility management function for the terminal, and may be connected to a plurality of base stations. In addition, the next-generation mobile communication system may be linked with the existing LTE system, and the NR CN (1c-05) may be connected to the MME (1c-25) through a network interface. The MME (1c-25) may be connected to the existing base station eNB (1c-30).

1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system to which the present disclosure can be applied. .

Referring to FIG. 1d, the radio protocol of the next-generation mobile communication system is NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), and NR RLC (1d-10) in the terminal and the NR base station, respectively. , 1d-35), and NR MAC (1d-15, 1d-30).

The main functions of the NR SDAPs 1d-01 and 1d-45 may include some of the following functions.

transfer of user plane data

Mapping between a QoS flow and a DRB for both DL and UL for uplink and downlink

Marking QoS flow ID in both DL and UL packets for uplink and downlink

A function of mapping a relective QoS flow to a data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For the SDAP layer device, the UE can receive the RRC message to determine whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel, and the SDAP header When is set, the terminal uses the NAS QoS reflection setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflection setting 1-bit indicator (AS reflective QoS) of the SDAP header to determine the uplink and downlink QoS flows and mapping information for the data bearer. can be instructed to update or reset The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority and scheduling information to support a smooth service.

The main function of the NR PDCP (1d-05, 1d-40) may include some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

In the above, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP sequence number (SN), and a function of delivering data to a higher layer in the reordered order may include, or may include a function of directly delivering without considering the order, may include a function of reordering the order to record the lost PDCP PDUs, and report the status of the lost PDCP PDUs It may include a function for the transmitting side, and may include a function for requesting retransmission for lost PDCP PDUs.

The main function of the NR RLC (1d-10, 1d-35) may include some of the following functions.

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment function (RLC re-establishment)

In the above, the in-sequence delivery function of the NR RLC device refers to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and one RLC SDU is originally divided into several RLC SDUs and received If it is, it may include a function of reassembling it and delivering it, and may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or PDCP SN (sequence number), and rearranging the order May include a function of recording the lost RLC PDUs, may include a function of reporting a status on the lost RLC PDUs to the transmitting side, and may include a function of requesting retransmission for the lost RLC PDUs. and, when there is a lost RLC SDU, it may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to the upper layer, or even if there is a lost RLC SDU, if a predetermined timer has expired It may include a function of sequentially delivering all RLC SDUs received before the start of RLC to the upper layer, or if a predetermined timer expires even if there are lost RLC SDUs, all RLC SDUs received so far are sequentially transferred to the upper layer. It may include a function to transmit. In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the sequence number and sequence number) and delivered to the PDCP device out of sequence (out-of sequence delivery). Segments stored in the buffer or to be received later are received, reconstructed into one complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed by the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order, and one RLC SDU originally has several RLCs. When received after being divided into SDUs, it may include a function of reassembling and delivering it, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs, arranging the order, and recording the lost RLC PDUs. can

The NR MACs 1d-15 and 1d-30 may be connected to several NR RLC layer devices configured in one terminal, and the main function of the NR MAC may include some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The NR PHY layer (1d-20, 1d-25) channel-codes and modulates upper layer data, makes an OFDM symbol and transmits it to a radio channel, or demodulates and channel-decodes an OFDM symbol received through a radio channel to an upper layer. You can perform a forwarding action.

FIG. 1E is a view showing a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) releases an RRC connection mode (RRC_CONNECTED) from a base station associated with one USIM, and releases another USIM, according to an embodiment of the present disclosure; FIG. It is a diagram showing a method of performing an operation related to .

A Multi-USIM capable UE 1e-01 according to an embodiment of the present disclosure may refer to a terminal supporting two or more USIMs. In the present disclosure, for convenience of description, a Dual-USIM terminal supporting two USIMs is considered. However, the present disclosure is not limited to dual-USIM terminals, and may also be applied to terminals supporting two or more USIMs. A dual-USIM terminal can transmit only to a base station associated with one USIM at a given time (of course, it can also transmit to a base station associated with each USIM at the same time). On the other hand, a dual-USIM terminal has a feature of being able to receive from a base station associated with one USIM at a given time or from a base station associated with each USIM at the same time.

Referring to FIG. 1E , a multi-USIM terminal 1e-01 may mean a terminal supporting a plurality of USIMs in one device. As an example, the multi-USIM terminal may mean a USIM 1 terminal (USIM1 UE) 1e-02 when operating in USIM 1, and a USIM 2 terminal (USIM2 UE) 1e-03 when operating in USIM 2 have. The base station may recognize the Multi-USIM terminal as one terminal per USIM terminal without recognizing it as one terminal. For example, base station 1 (NW (network) 1) (1e-04) recognizes the USIM 1 terminal 1e-02 as one terminal, and the base station 2 (NW 2) (1e-05) recognizes the USIM 2 terminal ( 1e-03) can be recognized as one terminal. Hereinafter, for convenience of description, in the embodiments of the present disclosure, when a Multi-USIM terminal communicates using USIM 1, the Multi-USIM terminal may be referred to as a USIM 1 terminal, and the Multi-USIM terminal uses USIM 2 When communicating using the Multi-USIM terminal, it may be referred to as a USIM 2 terminal. That is, the Multi-USIM terminal may be a USIM 1 terminal or a USIM 2 terminal depending on which USIM among USIM 1 and USIM 2 is used.

In step 1e-10, the USIM 1 terminal 1e-02 may be in the RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the base station 1 1e-04. In the RRC connected mode, the USIM 1 terminal 1e-02 may transmit and receive data with the base station 1 1e-04.

In step 1e-11, the USIM 2 terminal 1e-03 does not establish an RRC connection with the base station 2 1e-05, and may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).

In step 1e-15, the USIM 1 terminal 1e-02 may transmit a terminal capability information message (UECapabilityInformation) to the base station 1 1e-04. The terminal capability information message may include an indicator or an information element indicating that the USIM 1 terminal 1e-02 supports Multi-USIM. Or, in the terminal capability information message, the USIM 2 terminal (1e-03) establishes / resumes the RRC connection with the base station 2 (1e-05) to transmit and receive data for a long time or for an unpredictable time, the USIM 1 terminal (1e-02) indicates that the base station 1 (1e-04) wants to release the RRC connected mode (preference to leave RRC_CONNECTED) indicator or information necessary to leave the RRC connected mode (eg, preferred RRC state) Terminal capability information may be stored.

Hereinafter, for convenience of description in the embodiments of the present disclosure, the USIM 2 terminal 1e-03 transits to the base station 2 1e-05 and the RRC connected mode (RRC_CONNECTED) to transmit and receive data, the USIM 1 terminal 1e -02) and the base station 1 (1e-04) and the procedure for escaping from the RRC connected mode may be referred to as LTS (Long-time switching). That is, the USIM 1 terminal capability information included in the terminal capability information message may mean supporting the LTS. Of course, whether the LTS is supported is whether the USIM 1 terminal 1e-02 can operate by switching to another USIM terminal while maintaining the RRC connection mode with the base station 1 1e-04 for the Multi-USIM operation. It can also be applied in common with For example, the terminal capability information message may include capability information of the USIM 1 terminal, and in this case, the capability information of the USIM 1 terminal may include information related to the LTS support of the USIM 1 terminal. In addition, the capability information of the USIM 1 terminal is whether the USIM 1 terminal 1e-02 can operate by switching to another USIM terminal while maintaining the RRC connection mode with the base station 1 1e-04 for the multi-USIM operation. It may include information indicating whether or not According to an embodiment, the capability information of the USIM 1 terminal is information related to the LTS support of the USIM 1 terminal and the USIM 1 terminal 1e-02 and the base station 1 1e-04 RRC connection mode for multi-USIM operation. It may include all information indicating whether it can operate by switching to another USIM terminal while maintaining it.

In step 1e-20, the base station 1 (1e-04) provides the USIM 1 terminal 1e-02 through a predetermined RRC message or NAS (Non-Access Stratum) message LTS (Long-time switching) configuration information can be set. For example, the predetermined RRC message may mean an RRCReconfiguration message containing otherConfig. The long-time switching configuration information may include at least one of the following.

- An indicator or information element indicating whether the USIM 1 terminal (1e-02) may perform the LTS procedure to the base station 1 (1e-04)

- A new timer value driven by the USIM 1 terminal (1e-02) to transition to the RRC idle mode without a response from the base station. Base station 1 (1e-04) may set the timer value to a value smaller than or equal to or smaller than the conventional dataInactivityTimer. The USIM 1 terminal 1e-02, which has driven the new timer with the timer value, receives a predetermined response message (RRCRelease, RRCReconfiguration, MobilityFromNRCommand, MAC CE, DCI) from the base station 1 (1e-04) until the new timer expires. If not, the USIM 1 terminal 1e-02 may transition to the RRC idle mode when the timer expires. The base station 1 (1e-04) may also drive the timer when receiving a message transmitted by the USIM 1 terminal (1e-02) to get out of the RRC connected mode. The reason that the base station 1 (1e-04) drives the timer when receiving the message transmitted by the USIM 1 terminal 1e-02 to get out of the RRC connected mode is the base station 1 (1e-04) and the USIM 1 terminal 1e -02) because it can resolve the RRC state mismatch. In the present disclosure, the timer may be referred to as Txxx. That is, the timer Txxx may mean a new timer driven by the USIM 1 terminal 1e-02 to transition to the RRC idle mode without a response from the base station as described above.

- The USIM 1 terminal 1e-02 transmits that a predetermined RRC message, NAS message, or MAC CE is transmitted to get out of the RRC connected mode, but it is canceled and the USIM 1 terminal 1e-02 wants to maintain the RRC connected mode. indicator of whether

- A prohibit timer value to prevent LTS procedure start from being performed again for a certain period of time after LTS procedure start. The USIM 1 terminal 1e-02, which has driven the new prohibit timer with the prohibit timer value, cannot start the LTS procedure again until the new timer expires. However, although the USIM 1 terminal 1e-02 has transmitted a predetermined RRC message, NAS message, or MAC CE to get out of the RRC connected mode, the USIM 1 terminal 1e-02 wants to cancel it and maintain the RRC connected mode. If an indicator of whether this can be transmitted is set, the LTS procedure may be started again even if the prohibit timer is running. The prohibit timer value may be set to a value smaller than or equal to or smaller than a new timer value driven to transition to the RRC idle mode without a response from the base station. The reason why the prohibit timer value is set to a value smaller than or equal to or smaller than a new timer value driven to transition to the RRC idle mode without a response from the base station is that when the terminal does not receive a response from the base station, the LTS procedure can be restarted. In the present disclosure, the timer may be referred to as Tyyy. That is, the timer Tyyy may mean a prohibit timer for preventing the LTS procedure from being performed again for a predetermined period of time after the LTS procedure is started.

In step 1e-25, based on the steps described with reference to FIG. 1f to be described later, the USIM 2 terminal 1e-03 is the USIM 1 terminal 1e-02 for a specific short-time switching (STS)-gap period. The RRC connection with the base station 1 (1e-04) is released, and accordingly, the USIM 2 terminal (1e-03) establishes or resumes the RRC connection with the base station 2 (1e-05) to determine that data should be transmitted and received. . For example, in step 1e-25, the USIM 2 terminal (1e-03) monitors the paging channel transmitted by the base station 2 (1e-05) for a specific STS-gap period to receive a paging (CN paging or RAN paging) message. can And the paging message includes a USIM 2 terminal identifier (ue-Identity) that can identify the USIM 2 terminal (1e-03) and / or (and / or) a reason value for sending a paging message (cause value) For example, since there is a paging cause indicating voice), the USIM 2 terminal 1e-03 may determine whether to transmit/receive data in response to the paging message transmitted by the base station 2 1e-05.

In step 1e-30, the USIM 2 terminal 1e-03 releases the RRC connection between the USIM 1 terminal 1e-02 and the base station 1 1e-04 to the USIM 1 terminal 1e-02, and the USIM 2 terminal (1e-03) may provide an indicator or information element that it wants to transmit and receive data by establishing or resuming an RRC connection with the base station 2 (1e-05). For example, the USIM 2 terminal 1e-03 gives the USIM 1 terminal 1e-02 an indication of preference to perform a long-time switching procedure (LTS). information can be transmitted.

In step 1e-35, the USIM 1 terminal (1e-02) for the USIM 2 terminal (1e-03) with the base station 1 (1e-04) and a predetermined RRC message containing information to release the RRC connection mode or NAS The message may be transmitted to base station 1 (1e-04). The predetermined RRC message may mean a UEAssistanceInformation or a new RRC message, and the predetermined NAS message may mean a Registration Request or a Service Request message or a ULInformationTransfer. The information of wanting to release the RRC connected mode may include at least one of an indicator of wanting to leave the RRC connected mode, a preferred RRC state (RRC_IDLE or RRC_INACTIVE or preference to RRC_CONNECTED), and paging restriction information. The information to release the RRC connection mode may be transmitted by being included in only the predetermined RRC message, or may be transmitted by being included in only the predetermined NAS message, and the predetermined NAS message may be stored in the predetermined RRC message It may be transmitted by

Of course, in step 1e-35, the USIM 1 terminal 1e-02 may transmit the MAC CE to the base station 1 1e-04. The MAC CE may mean a MAC CE that wants to leave the RRC connected mode or may mean a MAC CE indicating a preferred RRC state. According to an embodiment, the MAC CE may mean a MAC CE message.

In step 1e-31, the USIM 1 terminal 1e-02 sets a new timer Txxx as a new timer value driven to transition to the RRC idle mode without a response from the base station 1 1e-04, which was described above in step 1e-20. After (re)operation, in step 1e-35, the USIM 1 terminal 1e-02 may transmit the predetermined RRC message, the NAS message, or the MAC CE to the base station 1 1e-04.

Alternatively, the USIM 1 terminal 1e-02 successfully transmits the predetermined RRC message, NAS message, or MAC CE (when an RRC layer receives an acknowledgment that the message has been successfully received from the RLC or PDCP or MAC layer) When done, a new timer Txxx may be driven.

In step 1e-31, the USIM 1 terminal 1e-02 may drive the above-described new timer Tyyy. Although steps 1e-31 have been described after steps 1e-35, steps 1e-31 may be performed before steps 1e-35.

In step 1e-40, the USIM 1 terminal 1e-02 may receive an RRC connection release message (RRCRelease) from the base station 1 (1e-04).

The present disclosure may propose an embodiment in which the USIM 1 terminal 1e-02 stops the new timer Txxx driven in steps 1e-31 upon receiving the RRC connection release message. For example, in step 1e-41, the USIM 1 terminal 1e-02 may stop the new timer Txxx.

The reason why the USIM 1 terminal 1e-02 stops the new timer Txxx is, if the new timer Txxx expires because the new timer Txxx is not stopped, the USIM 1 terminal 1e- 02) is because it may be necessary to perform the action (UE actions upon going to RRC_IDLE, section 5.3.11 in TS 38.331) unnecessarily to RRC_IDLE again. Additionally, when the USIM 1 terminal 1e-02 needs to transition to the RRC idle mode according to the RRC connection release message, the USIM 1 terminal 1e-02 in step 1e-41 receives the LTS (Long) set in step 1e-20. -time switching) configuration information can also be turned off.

In step 1e-43, the USIM 1 terminal 1e-02 may transition to the RRC deactivation mode when the RRC connection release message received in step 1e-40 includes the reservation configuration information (suspendConfig), and 1e- If the RRC connection release message received in step 40 does not include reservation configuration information (suspendConfig), it may transition to the RRC idle mode.

In step 1e-45, the USIM 2 terminal 1e-03 performs an RRC connection establishment or RRC connection resume procedure with the base station 2 1e-05 to transition to the RRC connected mode. Data can be sent and received.

FIG. 1f illustrates operations of a terminal and a base station when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a base station associated with one USIM, according to an embodiment of the present disclosure; It is a flow chart.

A Multi-USIM capable UE 1f-01 according to an embodiment of the present disclosure may refer to a UE supporting two or more USIMs. In the present disclosure, for convenience of description, a Dual-USIM terminal supporting two USIMs is considered. However, the present disclosure is not limited to dual-USIM terminals, and may also be applied to terminals supporting two or more USIMs. A dual-USIM terminal can transmit only to a base station associated with one USIM at a given time (of course, it can also transmit to a base station associated with each USIM at the same time). On the other hand, a dual-USIM terminal has a feature of being able to receive from a base station associated with one USIM at a given time or from a base station associated with each USIM at the same time.

Referring to FIG. 1f , a multi-USIM terminal 1f-01 may mean a terminal supporting a plurality of USIMs in one device. For example, the multi-USIM terminal may mean a USIM 1 terminal (USIM1 UE) (1f-02) when operating in USIM 1, and a USIM 2 terminal (USIM2 UE) (1f-03) when operating in USIM 2 have. The base station may recognize the Multi-USIM terminal as one terminal per USIM terminal without recognizing it as one terminal. For example, base station 1 (NW 1) (1f-04) recognizes USIM 1 terminal 1f-02 as one terminal, and base station 2 (NW 2) (1f-05) recognizes USIM 2 terminal 1f-03 ) can be recognized as one terminal. Hereinafter, for convenience of explanation, in the embodiments of the present disclosure, when a Multi-USIM terminal communicates using USIM 1, the Multi-USIM terminal may be referred to as a USIM 1 terminal, and the Multi-USIM terminal uses USIM 2 In the case of communicating with each other, the Multi-USIM terminal may be referred to as a USIM 2 terminal. That is, the Multi-USIM terminal may be a USIM 1 terminal or a USIM 2 terminal depending on which USIM among USIM 1 and USIM 2 is used.

In step 1f-10, the USIM 2 terminal 1f-03 may be in the RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the base station 2 1f-05. In the RRC connected mode, the USIM 2 terminal 1f-03 may transmit and receive data with the base station 2 1f-05. In the present disclosure, the base station 2 may mean an NR base station, an LTE base station, or AMF or MME.

In step 1f-11, the USIM 1 terminal 1f-02 does not establish and resume an RRC connection with the base station 1 1f-04, so it may be in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE). In the present disclosure, the base station 1 (1f-04) may mean an NR base station, an LTE base station, or AMF or MME.

In step 1f-15, the USIM 1 terminal 1f-02 may acquire system information broadcast by the base station 1 1f-04. For example, the system information may mean system information block 1 (SIB1). The present disclosure may propose an embodiment in which an indicator supporting a busy indication procedure is included in the system information.

In step 1f-20, the USIM 1 terminal 1f-02 may receive a CN paging or RAN paging message from the base station 1 1f-04. A paging message according to an embodiment of the present disclosure may include a paging cause value for sending paging for each paging record. As an example, the paging cause may include at least one of the following.

> Voice: A value indicating the reason for sending a paging message for Voice over LTE (VoLTE) or Voice over NR (VoNR).

> Others: A value indicating the reason for sending a paging message for a non-voice service

In step 1f-20, the USIM 1 terminal 1f-02 may confirm that the received paging message has the identifier (ue-Identity -> PagingUE-Identity) of the USIM 1 terminal 1f-02. Also, the USIM 1 terminal 1f-02 may determine whether there is a paging cause value in the identifier of the USIM 1 terminal 1f-02. If the paging cause is included, the USIM 1 terminal 1f-02 may transmit the paging cause to a higher layer device of the USIM 1 terminal 1f-02. The reason for delivering the paging cause to the higher layer device is whether the multi-USIM terminal 1f-01 prioritizes the service of the USIM 2 terminal 1f-03 that is currently in progress, or whether the USIM 1 terminal 1f -02) to determine whether to prioritize the paging message.

In step 1f-25, the multi-USIM terminal (1f-01) wants to continue to maintain the service of the USIM 2 terminal (1f-03) that is currently in progress, so the USIM 1 terminal (1f-02) is a busy indication procedure (busy indication) procedure) can be triggered.

In step 1f-30, the USIM 1 terminal 1f-02 may transmit an RRC connection establishment request message (RRCSetupRequest) or an RRC connection resumption request message (RRCResumeRequest or RRCResumeRequest1) to the base station 1 (1f-04). In the message (eg, RRC connection establishment request message (RRCSetupRequest) or RRC connection resumption request message (RRCResumeRequest or RRCResumeRequest1)), although the paging message was properly received from the base station 1 (1f-04), the USIM 2 terminal (1f-03) A 'busy indication' indicating a new reason value (establishmentCause or resumeCause) for indicating that a response to a paging message cannot be performed in order to continue an ongoing service may be included.

In step 1f-35, the base station 1 (1f-04) may transmit an RRC connection release message (RRCRelease) or an RRC connection establishment message (RRCSetup) or an RRC connection resume message (RRCResume) to the USIM 1 terminal 1f-02. .

In step 1f-40, when the USIM 1 terminal 1f-02 receives the RRC connection establishment message or RRC connection resume message in step 1f-35, in response to this, the RRC connection establishment complete message (RRCSetupComplete) or RRC connection resumes A completion message (RRCResumeComplete) may be transmitted. In the message (eg, RRC connection setup complete message (RRCSetupComplete) or RRC connection resumption completion message (RRCResumeComplete)), the paging message was properly received from the base station 1 (1f-04), but the USIM 2 terminal (1f-03) proceeds and Busy indication information indicating that it cannot respond to a paging message in order to continue with the service may be accommodated. According to one embodiment, although the paging message has been properly received from the base station 1 (1f-04), the USIM 2 terminal 1f-03 indicates that it cannot respond to the paging message in order to continue the ongoing service. The busy indication information may be directly stored in the RRC connection establishment completion message (RRCSetupComplete) or the RRC connection resumption completion message (RRCResumeComplete), or included in the dedicated NAS message including the RRC connection establishment completion message (RRCSetupComplete) or the RRC connection resume completion message. may be

In step 1f-45, the base station 1 (1f-04) may transmit an RRC connection release message (RRCRelease) to the USIM 1 terminal (1f-02).

FIG. 1G illustrates operations of a terminal and a base station when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a network associated with one USIM, according to an embodiment of the present disclosure; It is a flow chart.

A Multi-USIM capable UE 1g-01 according to an embodiment of the present disclosure may refer to a terminal supporting two or more USIMs. In the present disclosure, for convenience of description, a Dual-USIM terminal supporting two USIMs is considered. However, the present disclosure is not limited to dual-USIM terminals, and may also be applied to terminals supporting two or more USIMs. A dual-USIM terminal can transmit only to a base station associated with one USIM at a given time (of course, it can also transmit to a base station associated with each USIM at the same time). On the other hand, a dual-USIM terminal has a feature of being able to receive from a base station associated with one USIM at a given time or from a base station associated with each USIM at the same time.

Referring to FIG. 1G , a multi-USIM terminal 1g-01 may mean a terminal supporting a plurality of USIMs in one device. For example, the multi-USIM terminal may mean a USIM 1 terminal (USIM1 UE) (1g-02) when operating in USIM 1, and a USIM 2 terminal (USIM2 UE) (1g-03) when operating in USIM 2 have. The base station may recognize the Multi-USIM terminal as one terminal per USIM terminal without recognizing it as one terminal. For example, base station 1 (eNB/gNB) (1g-04) recognizes USIM 1 terminal (1g-02) as one terminal, and base station 2 (eNB/gNB) (1g-06) recognizes USIM 2 terminal (1g) -03) can be recognized as one terminal. Hereinafter, for convenience of description, in the embodiments of the present disclosure, when a Multi-USIM terminal communicates using USIM 1, the Multi-USIM terminal may be referred to as a USIM 1 terminal, and the Multi-USIM terminal uses USIM 2 In the case of communication using the Multi-USIM terminal, the multi-USIM terminal may be referred to as a USIM 2 terminal. That is, the Multi-USIM terminal may be a USIM 1 terminal or a USIM 2 terminal depending on which USIM among USIM 1 and USIM 2 is used.

In step 1g-09, the USIM 2 terminal 1g-03 does not establish or resume the RRC connection with the base station 2 1g-06, so it may be in the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE).

In step 1g-10, the USIM 1 terminal 1g-02 may be in the RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the base station 1 (1g-04). In the RRC connected mode, the USIM 1 terminal 1g-02 may transmit and receive data with the base station 1 1g-04.

In step 1g-15, the USIM 1 terminal (1g-02) to the base station 1 (1g-04) or the core network (MME / AMF) (1g-05), the terminal capability information message (UECapabilityInformation) or RRC message (RRCSetupComplete, RRCResumeComplete) or by transmitting a NAS message (eg, TAU Request, Registration Request, Service Request, etc.), USIM 1 terminal (1g-02) is a terminal that supports Multi-USIM , may transmit terminal capability information indicating that the paging cause value is supported, or may request that the paging cause value be accommodated in the paging message.

In step 1g-20, the base station 1 (1g-04) may transmit an RRC connection release message (RRCRelease) to the USIM 1 terminal (1g-02). The USIM 1 terminal 1g-02 may apply the received RRC connection release message. If inactivation configuration information (suspendConfig in NR; rrc-InactiveConfig in LTE) is included in the RRC connection release message, the USIM 1 terminal 1g-02 may transition to the RRC inactive mode in steps 1g-21. When the deactivation configuration information is not included in the RRC connection release message, the USIM 1 terminal 1g-02 may transition to the RRC idle mode.

In step 1g-25, the base station 1 (1g-04) may broadcast system information. For example, the system information may mean SIB1. The present disclosure proposes an embodiment in which an indicator supporting a paging cause is included in the system information. Specifically, at least one or a plurality of the following methods may be applied according to the operation of the base station.

> Method 1: Include in cellAccessRelatedInfo an indicator that the cell broadcasting the system information supports a paging cause

>> Supports paging cause in cell information in all PLMN-IdentityInfo (plmn-IdentityList, trackingAreaCode, ranac, cellIdentity) included in PLMN-IdentityInfoList, and all NPN-IdentityInfo included in NPN-IdentityInfoList Meaning that the paging cause is supported in the cell information in (npn-IdentityList, trackingAreaCode, ranac, cellIdentity)

> Method 2: An indicator that supports paging cause in a cell broadcasting the system information is applied to PLMN-IdentityInfoList

>> Meaning that the paging cause is supported in the cell information in all PLMN-IdentityInfo (plmn-IdentityList, trackingAreaCode, ranac, cellIdentity) included in PLMN-IdentityInfoList.

> Method 3: Include in PLMN-IdentityInfo an indicator that the cell broadcasting the system information supports paging cause

>> Meaning to support paging cause for each cell information in each PLMN-IdentityInfo (plmn-IdentityList, trackingAreaCode, ranac, cellIdentity)

> Method 4: An indicator that supports paging cause in a cell broadcasting the system information is applied to NPN-IdentityInfoList

>> Meaning that paging cause is supported in cell information in all NPN-IdentityInfo (npn-IdentityList, trackingAreaCode, ranac, cellIdentity) included in NPN-IdentityInfoList

> Method 5: Include in NPN-IdentityInfo an indicator that the cell broadcasting the system information supports paging cause

>> Meaning to support paging cause for each cell information in each NPN-IdentityInfo (npn-IdentityList, trackingAreaCode, ranac, cellIdentity)

Alternatively, the present disclosure proposes an embodiment in which an indicator supporting a busy indication procedure is included in the system information.

In step 1g-30, the USIM 2 terminal 1g-03 may be in the RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the base station 2 (eNB/gNB) 1g-06. In the RRC connected mode, the USIM 2 terminal 1g-03 may transmit and receive data with the base station 2 1g-06.

In step 1g-35, the USIM 1 terminal 1g-02 may receive a paging message transmitted from the base station 1 1g-04. The paging message may be CN paging initiated from the core network 1g-05 or RAN paging directly initiated by the base station 1 1g-04. The paging message may include a terminal identifier (PagingUE-Identity) for identifying the USIM 1 terminal 1g-02. If the paging message includes a terminal identifier for identifying the USIM 1 terminal 1g-02, but does not include a paging cause value, the paging cause is included in the system information received in step 1g-25. ) is broadcast, the USIM 1 terminal 1g-02 may determine that the page is being paged due to a non-voice service rather than a voice service. If the paging message includes a terminal identifier for identifying the USIM 1 terminal 1g-02, but does not include a paging cause value, the paging cause is included in the system information received in step 1g-25. ) is not broadcast, the USIM 1 terminal 1g-02 determines that it is paging due to a specific service (any service) from the core network 1g-05 that does not support the paging cause can do. For reference, selected PLMN (Public Land Mobile Network)/equivalent PLMN lists/registered PLMN or selected SNPN (Standalone Non-Public Network)/registered SNPN of the USIM 1 terminal 1g-02 supports paging cause. When the indicator is included in the system information received in step 1g-25, that is, when the indicator supporting the above-described paging reason is broadcast through the system information in step 1g-25, the USIM 1 terminal 1g-02 may determine that the base station 1 (1g-04) supports the paging reason.

1H is a flowchart illustrating the operation of a terminal when a terminal (Multi-USIM UE) supporting a plurality of USIMs (Universal Subscriber Identity Module) receives a paging message from a network associated with one USIM, according to an embodiment of the present disclosure; .

Referring to FIG. 1h, in step 1h-05, the USIM 1 UE (USIM 1 UE) does not establish and resume an RRC connection with the base station, so it may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).

In step 1h-10, the USIM 2 UE (USIM 2 UE) may be in the RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the base station. In the RRC connected mode, the USIM 2 terminal may transmit/receive data to and from the base station.

In step 1h-15, the USIM 1 terminal may acquire system information broadcast by the base station. For example, the system information may mean SIB1.

In step 1h-20, the USIM 1 terminal may receive the paging message transmitted by the base station. In the paging record list (PagingRecordList) accommodated in the paging message, the PagingUE-Identity indicating the USIM 1 terminal may be included in the PagingRecord. For example, the paging record list (PagingRecordList) may include PagingRecord, and PagingRecord may include PagingUE-Identity.

In step 1h-25, the USIM 1 terminal may determine whether a paging cause value is also included in the PagingRecord including the PagingUE-Identity indicating the USIM 1 terminal in step 1h-20.

In step 1h-30, when the USIM 1 terminal includes a paging cause called 'voice' in the PagingRecord including the PagingUE-Identity indicating the USIM 1 terminal in step 1h-25, the USIM 1 according to the above-described embodiment Terminal 2 may perform a long-time switching (LTS) procedure. Of course, a voice service may not be performed in the USIM 2 terminal. In addition, the USIM 1 terminal may be provided with a voice service by performing a general RRC connection establishment and resumption process.

In step 1h-30, the USIM 1 terminal includes a paging cause called 'others' in the PagingRecord including the PagingUE-Identity that refers to the USIM 1 terminal in step 1h-25. busy indication procedure). That is, to determine that the priority of the service in progress in the USIM 2 terminal is high or to continue to receive the service in progress in the USIM 2 terminal, the USIM 1 terminal may perform a busy indication procedure. 'Others' may mean a non-voice service. Alternatively, according to the above-described embodiment, the USIM 2 terminal performs a long-time switching (LTS) procedure and the USIM 1 terminal performs a general RRC connection establishment and resumption process to provide a non-voice service. can be provided This is to determine that the priority of the service in progress in the USIM 2 terminal is low or to receive the service from the paging message received by the USIM 1 terminal without continuing to receive the ongoing service in the USIM 2 terminal. Whether the USIM 1 terminal performs a busy indication procedure or whether the USIM 2 terminal performs a long-time switching (LTS) procedure depends on the priority of the service in progress in the USIM 2 terminal. can be judged based on

In step 1h-40, when the USIM 1 terminal does not include the paging cause in the PagingRecord including the PagingUE-Identity that refers to the USIM 1 terminal in step 1h-25, the system information received in step 1h-15 It can be determined whether an indicator supporting the paging cause is included in the selected PLMN/equivalent PLMN lists/registered PLMN of the USIM 1 UE or in the cell mapped to the selected SNPN/registered SNPN.

In step 1h-45, the USIM 1 terminal in the system information received in step 1h-40, the selected PLMN/equivalent PLMN lists/registered PLMN of the USIM 1 terminal, or the selected SNPN/registered SNPN in the cell mapped to the paging reason (paging cause), if it includes an indicator supporting the busy indication procedure (busy indication procedure) can be performed. That is, to determine that the priority of the service in progress in the USIM 2 terminal is high, or to continue to receive the service in progress in the USIM 2 terminal, the USIM 1 terminal may perform a busy indication procedure. . Alternatively, according to the above-described embodiment, the USIM 2 terminal may perform a long-time switching (LTS) procedure, and the USIM 1 terminal may perform a general RRC connection establishment and resumption process to receive a service due to a paging message. . This is to determine that the priority of the service in progress in the USIM 2 terminal is low or to receive the service from the paging message received by the USIM 1 terminal without continuing to receive the ongoing service in the USIM 2 terminal. Whether the USIM 1 terminal performs a busy indication procedure or whether the USIM 2 terminal performs a long-time switching (LTS) procedure depends on the priority of the service in progress in the USIM 2 terminal. can be judged based on

In step 1h-50, the USIM 1 terminal, in the selected PLMN/equivalent PLMN lists/registered PLMN of the USIM 1 terminal or the selected SNPN/registered SNPN in the system information received in step 1h-40, in the cell mapped to the selected SNPN/registered SNPN, the paging reason (paging If the indicator supporting cause) is not included, no action may be performed. That is, the USIM 1 terminal may not make any response to the paging message. Alternatively, according to the above-described embodiment, the USIM 2 terminal may perform a long-time switching (LTS) procedure and the USIM 1 terminal may perform a general RRC connection establishment and resumption process to receive a service due to a paging message.

1I is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present disclosure.

Referring to FIG. 1I, the terminal may include a radio frequency (RF) processing unit 1i-10, a baseband processing unit 1i-20, a storage unit 1i-30, and a control unit 1i-40. can

According to an embodiment, the RF processing unit 1i-10 may perform a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 1i-10 up-converts the baseband signal provided from the baseband processing unit 1i-20 into an RF band signal, transmits it through an antenna, and receives the RF band signal through the antenna. can be down-converted to a baseband signal. For example, the RF processing unit 1i-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), and the like. can In the figure, only one antenna is shown, but the terminal may include a plurality of antennas. Also, the RF processing unit 1i-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1i-10 may perform beamforming. For the beamforming, the RF processing unit 1i-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit 1i-10 may perform MIMO, and may receive multiple layers when performing MIMO operation.

According to an embodiment, the baseband processing unit 1i-20 may perform a conversion function between a baseband signal and a bit stream according to a physical layer standard of a system. For example, when transmitting data, the baseband processing unit 1i-20 may generate complex symbols by encoding and modulating a transmitted bit stream. Also, when receiving data, the baseband processing unit 1i-20 may restore a received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1i-10. For example, in the case of orthogonal frequency division multiplexing (OFDM), when transmitting data, the baseband processing unit 1i-20 encodes and modulates a transmission bit stream to generate complex symbols, and convert the complex symbols to subcarriers. After mapping to , OFDM symbols may be configured through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. Also, upon data reception, the baseband processing unit 1i-20 divides the baseband signal provided from the RF processing unit 1i-10 into OFDM symbol units, and maps them to subcarriers through fast Fourier transform (FFT). After restoring the received signals, the received bit stream can be restored through demodulation and decoding.

According to an embodiment, the baseband processing unit 1i-20 and the RF processing unit 1i-10 may transmit and receive signals as described above. Accordingly, the baseband processing unit 1i-20 and the RF processing unit 1i-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit 1i-20 and the RF processing unit 1i-10 may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processing unit 1i-20 and the RF processing unit 1i-10 may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (eg, IEEE 802.11), a cellular network (eg, LTE), and the like. In addition, the different frequency bands may include a super high frequency (SHF) (eg, 2.NRHz, NRhz) band and a millimeter wave (eg, 60GHz) band.

According to an embodiment, the storage unit 1i-30 may store data such as a basic program, an application program, and setting information for the operation of the terminal. In particular, the storage unit 1i-30 may store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit 1i-30 may provide stored data according to the request of the control unit 1i-40. According to an embodiment, the storage unit 1i-30 may store a program for performing an operation of discriminating a paging reason in the wireless communication system according to the above-described embodiments of the present disclosure.

According to an embodiment, the controller 1i-40 may control overall operations of the terminal. For example, in the wireless communication system according to an embodiment of the present disclosure, it is possible to control the components of the terminal to perform a method of distinguishing a paging reason. For example, the control unit 1i-40 may transmit/receive signals through the baseband processing unit 1i-20 and the RF processing unit 1i-10. Also, the control unit 1i-40 may write data to and read data from the storage unit 1i-30. To this end, the controller 1i-40 may include at least one processor. For example, the controller 1i-40 may include a communication processor (CP) that controls for communication and an application processor (AP) that controls an upper layer such as an application program. According to an embodiment of the present disclosure, the controller 1i-40 may also include a multi-connection processing unit 1i-42 that performs processing for operating in a multi-connection mode.

1J is a block diagram illustrating the configuration of an NR base station according to an embodiment of the present disclosure.

Referring to FIG. 1J , the base station may include an RF processing unit 1j-10, a baseband processing unit 1j-20, a communication unit 1j-30, a storage unit 1j-40, and a control unit 1j-50. can

According to an embodiment, the RF processing unit 1j-10 may perform a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processor 1j-10 up-converts the baseband signal provided from the baseband processor 1j-20 into an RF band signal, transmits it through an antenna, and receives the RF band signal through the antenna. can be down-converted to a baseband signal. For example, the RF processing unit 1j-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. In the figure, only one antenna is shown, but the base station may have a plurality of antennas. Also, the RF processing unit 1j-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1j-10 may perform beamforming. For the beamforming, the RF processor 1j-10 may adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit 1j-10 may perform a downlink MIMO operation by transmitting one or more layers.

According to an embodiment, the baseband processing unit 1j-20 may perform a function of converting a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when transmitting data, the baseband processing unit 1j-20 may generate complex symbols by encoding and modulating a transmitted bit stream. Also, when receiving data, the baseband processing unit 1j-20 may restore the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1j-10. For example, in the OFDM scheme, when transmitting data, the baseband processing unit 1j-20 generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then IFFT OFDM symbols can be configured through operation and CP insertion. In addition, upon data reception, the baseband processing unit 1j-20 divides the baseband signal provided from the RF processing unit 1j-10 into OFDM symbol units, and restores signals mapped to subcarriers through FFT operation. After that, the received bit stream can be restored through demodulation and decoding. The baseband processing unit 1j-20 and the RF processing unit 1j-10 may transmit and receive signals as described above. Accordingly, the baseband processing unit 1j-20 and the RF processing unit 1j-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

According to an embodiment, the communication unit 1j-30 may provide an interface for performing communication with other nodes in the network. That is, the communication unit 1j-30 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc. into a physical signal, and converts the physical signal received from the other node into a bit string. can be converted to According to an embodiment, the communication unit 1j-30 may include a backhaul communication unit.

According to an embodiment, the storage unit 1j-40 may store data such as a basic program, an application program, and setting information for the operation of the main base station. In particular, the storage unit 1j-40 may store information on a bearer assigned to an accessed terminal, a measurement result reported from the accessed terminal, and the like. In addition, the storage unit 1j-40 may store information serving as a criterion for determining whether to provide or stop multiple connections to the terminal. In addition, the storage unit 1j-40 may provide stored data according to the request of the control unit 1j-50.

According to an embodiment, the controller 1j-50 may control overall operations of the base station. For example, in a wireless communication system according to an embodiment of the present disclosure, it is possible to control components of a base station to perform a method of distinguishing a paging reason. For example, the control unit 1j-50 may transmit/receive a signal through the baseband processing unit 1j-20 and the RF processing unit 1j-10 or through the communication unit 1j-30. In addition, the control unit 1j-50 may write and read data in the storage unit 1j-40. To this end, the control unit 1j-50 may include at least one processor.

Claims (1)

In the operating method of a terminal supporting a plurality of USIM (Universal Subscriber Identity Module) in a wireless communication system,
receiving system information from a base station based on a first USIM among the plurality of USIMs;
receiving a paging message from the base station based on the first USIM among the plurality of USIMs;
determining whether a paging cause value is included in the paging message; and
performing an operation by the first USIM or the second USIM among the plurality of USIMs based on a result of the determination;
How to include.

Images