Method and apparatus for extended discontinuous reception in wireless communication system

Abstract

The present disclosure relates to a 5th-Generation (5G) or 6th-Generation (6G) communication system supporting higher data rates. Specifically, the present disclosure provides a method for extended discontinuous reception (eDRX). In accordance with an aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system includes identifying, for a radio resource control (RRC) inactive state, a first extended discontinuous reception (eDRX) period associated with a core network (CN) entity and a second eDRX period associated with a radio access network (RAN) node; and monitoring the paging opportunity in the RRC inactive state according to the DRX cycle.

Description

TECHNICAL FIELD

[0001] The disclosure relates generally to the field of communications, and more particularly, to a user equipment (UE), a base station (BS) and methods thereof for extended discontinuous reception (eDRX) in a wireless communication system. BACKGROUND

[0002] The fifth generation (5G) mobile communication technologies define broad frequency bands so that high transmission rates and new services are possible, and are implemented not only in the frequency bands (sub-6 GHz) such as 3.5 GHz, but also in the extremely high frequency bands (mmWave) such as 28 GHz and 39 GHz, and the 6th generation (6G) mobile communication technologies (referred to as beyond 5G systems) have been discussed, which will be implemented in terahertz (THz) bands (28 GHz to 143 GHz, 43 GHz to 71 GHz, 71 GHz to 114 GHz, and 114 GHz to 300 GHz) to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies.

[0003] Since the development of 5G mobile communication technologies, standardization for reducing radio-wave path loss and increasing radio-wave transmission distances in mmWave bands through beamforming and multiple input multiple output (MIMO), operating multiple subcarrier spaces to effectively use mmWave resources and dynamic operation of time slot formats, initial access techniques for supporting multi-beam transmission and wide bands, definition and operation of bandwidth parts (BWPs), new channel coding methods such as low-density parity check (LDPC) codes for large amounts of data transmission and polar codes for highly reliable transmission of control information, layer 2 (L2) pre-processing, and network slicing for providing a dedicated network dedicated to a specific service, has been in progress.

[0004] In light of services to be supported by 5G mobile communication technologies, discussions about improvement and performance enhancement of initial 5G mobile communication technologies have been underway, and there has been standardization for physical layers, such as vehicle-to-everything (V2X) for assisting driving determination of autonomous vehicles based on information about positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, new radio unlicensed (NR-U) aiming to conform to various regulation-related requirements of system operations in unlicensed bands, NR UE power saving, non-terrestrial networks (NTN) for providing coverage in areas where communication with ground networks is unavailable as UE-satellite direct communication, and positioning.

[0005] Air interface architecture / protocol regarding technologies are being standardized, such as Industrial Internet of Things (IIoT) for support of new services through interworking and convergence with other industries, Integrated Access and Backhaul (IAB) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access (two-step RACH of NR) for simplifying a random access procedure. Standardization is underway regarding a 5G baseline architecture (e.g., service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and a system architecture / service for receiving services based on UE position, Mobile Edge Computing (MEC).

[0006] With the commercialization of 5G mobile communication systems, connected devices, which have increased exponentially, will be connected to communication networks, and accordingly, enhanced functionality and performance of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research into the following is planned: extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Such development of 5G mobile communication systems will serve as a basis for not only developing new waveforms for providing coverage of terahertz bands for 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, lenses and antennas based on metamaterials for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS), but also developing Full-Duplex technology for improving frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a level of complexity exceeding the limit of UE operation capability by utilizing super-high-performance communication and computing resources.

[0008] Wireless communication systems are developing toward broadband wireless communication systems to provide high-speed and high-quality packet data services using communication standards such as 3GPP's High Speed Packet Access (HSPA), LTE (Long Term Evolution) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-advanced (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.16e, and typical voice-based services.

[0009] An LTE system employs an Orthogonal Frequency Division Multiplexing (OFDM) scheme in a downlink (DL) and a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme in an uplink (UL), which indicates a radio link through which a UE (or a mobile station (MS)) transmits data or a control signal to a BS (BS or eNodeB), and the DL indicates a radio link through which the BS transmits data or a control signal to the UE. The above-described multiple access scheme separates data or control information of individual users by allocating and operating time-frequency resources for transmitting data or control information for each user to avoid overlapping each other, i.e., establishing orthogonality.

[0010] Since a 5G communication system, which is a communication system after LTE, must freely reflect various requirements of users and service providers, there is a need to support services satisfying various requirements including eMBB, mMTC, and URLLC. SUMMARY

[0011] SOLUTION TO PROBLEM

[0012] The present disclosure is directed to resolving at least the above problems and / or disadvantages and to providing at least the below-described advantages.

[0013] Accordingly, an aspect of the present disclosure is to provide an apparatus and method capable of efficiently providing services in a mobile communication system.

[0014] According to aspects of the disclosure, a method performed by a user equipment (UE) in a wireless communication system includes identifying, for a radio resource control (RRC) inactive state, a first extended discontinuous reception (eDRX) cycle associated with a core network (CN) entity and a second eDRX cycle associated with a radio access network (RAN) node; and monitoring a paging occasion in the RRC inactive state according to a DRX cycle, wherein, in a case that the first eDRX cycle is longer than 1024 radio frames and the second eDRX cycle is longer than 1024 radio frames: the DRX cycle is determined by a shortest value among a first UE-specific value configured by upper layer, a second UE-specific value configured by RRC, and a default DRX value broadcasted in system information during an overlapping period of a first paging time window associated with the CN entity and a second paging time window associated with the RAN node; the DRX cycle is determined by a shortest value among the first UE-specific value configured by upper layer and the default DRX value broadcasted in system information during a period included in the first paging time window associated with the CN entity and outside of the second paging time window associated with the RAN node; and the DRX cycle is determined by the second UE-specific value configured by RRC during a period included in the second paging time window associated with the RAN node and outside of the first paging time window associated with the CN entity.

[0015] The disclosed embodiments can effectively provide services in a mobile communication system. BRIEF DESCRIPTION OF DRAWINGS

[0016] The foregoing and other aspects, features, and advantages of certain embodiments of the present disclosure will be more apparent from the following description, as taken in conjunction with the accompanying drawings, in which:

[0017] Figure 1 A next-generation mobile communication system according to an embodiment is illustrated;

[0018] Figure 2 Switching of a radio connection state in a next-generation mobile communication system according to an embodiment is illustrated;

[0019] Figure 3 Operation of a BS (or network) broadcasting a paging occasion (PO) and a paging message according to an embodiment is illustrated;

[0020] Figure 4 A core network (CN) paging reception procedure of a UE in an idle mode according to an embodiment is illustrated;

[0021] Figure 5 A random access network (RAN) paging reception procedure of a UE in an inactive mode according to an embodiment is illustrated;

[0022] Figure 6A process for a UE to determine a paging monitoring cycle is shown according to an embodiment;

[0023] Figure 7 A paging procedure using eDRX in LTE is shown according to an embodiment;

[0024] Figure 8 A UE device is shown according to an embodiment; and

[0025] Figure 9 A BS device is shown according to an embodiment. DETAILED DESCRIPTION

[0026] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of embodiments of the present disclosure. Therefore, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Descriptions of well-known functions and structures are omitted to make the disclosure more concise.

[0027] Similarly, in the drawings, some elements can be exaggerated, omitted, or schematically illustrated and the size of each element does not completely reflect the actual size. Identical or corresponding elements are provided with the same or corresponding reference numerals.

[0028] The following embodiments are provided only to more completely explain the present disclosure as fully as possible, and to further convey the scope of the present disclosure to those skilled in the art. In the present document, identical or similar reference numerals indicate identical or similar elements.

[0029] As used herein, a unit refers to a software element or a hardware element that performs a predetermined function, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). However, the unit is not always applied to software or hardware, and can be constructed as a storage medium that stores one or more processors. Therefore, the unit includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, sub-routines, program code segments, drivers, firmware, microcode, circuits, data, database, data structures, tables, arrays, and parameters. Elements and functions provided by the unit can be combined into fewer elements or units, or divided into more elements or units. The elements and units can be implemented as one or more central processing units (CPUs) within a reproduction device or a secure multimedia card.

[0030] In the following description, for convenience, terms for identifying access nodes and for referring to network entities, messages, interfaces between network entities, various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited by the terms used below, and other terms referring to the subject matter having equivalent technical meanings can be used.

[0031] For convenience of description, terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard will be used. However, the disclosure is not limited by the terms and names, and can be similarly applied to systems conforming to other standards. With respect to the BS, for convenience of description, the term eNB can be used interchangeably with the term gNB. The term terminal can refer to a mobile phone, a Node B (NB)-IoT device, a sensor, and various wireless communication devices.

[0032] Here, the BS allocates resources to the terminal, and can be at least one of a gNode B, an eNode B, an NB, a wireless access unit, a BS controller, and a node on a network. The terminal can 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. The BS and the terminal are not limited to these examples.

[0033] The disclosure can be applied to 3GPP NR and intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail businesses, security and safety-related services, etc.) based on 5G communication and IoT-related technologies.

[0034] In this document, LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems will be described by way of example, but the disclosure can also be applied to other communication systems having a similar technical background or channel type as the embodiments of the disclosure. Based on the determination of those skilled in the art, the embodiments of the disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of the disclosure.

[0035] Figure 1 A next-generation mobile communication system according to an embodiment is shown.

[0036] Reference Figure 1 A radio access network of a radio communication system (hereinafter, a next-generation mobile communication system, NR, or 5G) can include a next-generation BS (gNB: NR Node b) 110 and an NR core network. The NR CN can include, but is not limited to, an access management function (AMF) 105. A user terminal (NR UE: New Radio User Equipment) 115 can access an external network via the gNB 110 and the AMF 105.

[0037] In Figure 1In the middle, the gNB 110 can correspond to an evolved Node B (eNB) of a legacy LTE system. The gNB 110 can be connected to the NR UE 115 through a radio channel 120 and can provide improved services compared to the legacy Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, the gNB 110 can serve as a device that collects state information such as a buffer state of a UE, an available transmission power state, and a channel state and performs scheduling as needed. One gNB 110 can control multiple cells. To achieve ultra-high-speed data transfer beyond the current LTE, the next-generation mobile communication system can provide a wider bandwidth than the existing maximum bandwidth, can adopt orthogonal frequency division multiplexing (OFDM) as a radio access technology, and can additionally use a beamforming technique.

[0038] The NR gNB 110 can employ an adaptive modulation and coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to a channel state of the UE. The AMF 105 can perform functions such as mobility support, bearer configuration, and QoS configuration, is responsible for various control functions as well as a mobility management function of the UE, and can be connected to multiple BSs. In addition, the next-generation mobile communication system can interwork with the existing LTE system, and the AMF 105 can be connected to a mobility management entity (MME) 125 via a network interface. The MME 125 can be connected to the eNB 130, which is a legacy BS. A UE supporting LTE-NR dual connectivity can transmit / receive data while maintaining connection with both the gNB 110 and the eNB 130.

[0039] Figure 2 A handover of a wireless connection state in a next-generation mobile communication system according to an embodiment is illustrated.

[0040] Herein, the UE can have three radio resource control (RRC) wireless connection states in the next-generation mobile communication system. A connected mode (RRC_CONNECTED) 205 can indicate that the UE is in a wireless connection state capable of transmitting and receiving data. An idle mode (RRC_IDLE) 230 can indicate that the UE is in a wireless connection state of monitoring whether a page is transmitted to the UE. The connected mode 205 and the idle mode 230 are wireless connection states that can also be applied to the LTE system, and details thereof can be the same as those of the LTE system. An inactive mode (RRC_INACTIVE) 215, as well as the connected mode 205 and the idle mode 230, can be newly applied to the next-generation mobile communication system. The RRC_INACTIVE 215 state can correspond to an inactive wireless connection state, an inactive mode, a deactivated mode, etc.

[0041] In the inactive mode 215 wireless connected state, the UE context can be maintained in the BS and the UE, and radio access network (RAN) based paging can be supported. Characteristics of the inactive mode 215 wireless connected state are as follows.

[0042] Cell reselection mobility,

[0043] A CN-NR RAN connection (both C / U-planes) has been established for the UE,

[0044] The UE AS context is stored in at least one gNB and the UE,

[0045] Paging is initiated by the NR RAN (i.e., RAN paging),

[0046] The RAN-based notification area is managed by the NR RAN, and

[0047] The NR RAN knows the RAN-based notification area to which the UE belongs.

[0048] A UE in the inactive mode 215 can switch to the connected mode 205 or the idle mode 230 through specific procedures.

[0049] In step 210, the UE can switch from the inactive mode 215 to the connected mode 205 according to a resume procedure, and from the connected mode 205 to the inactive mode 215 through a release procedure including suspend configuration information. In step 210, one or more RRC messages can be transmitted and received between the UE and the BS, and step 210 can include one or more detailed steps.

[0050] In step 220, the UE can switch from the inactive mode 215 to the idle mode 230 through the release procedure 220 after the resume procedure.

[0051] In step 225, switching between the connected mode 205 and the idle mode 230 can be performed according to conventional LTE techniques, such as establishment or release procedures.

[0052] Figure 3 An operation in which a BS (or network) broadcasts a PO and a paging message according to an embodiment is illustrated.

[0053] A NR-based 5G or next generation radio access network (NG-RAN) can include NG-RAN nodes, and the NG-RAN nodes can correspond to gNBs. A gNB can provide NR user plane (UP) and control plane (CP) protocol terminations towards a UE. In addition, a gNB is connected by means of an NG interface for a 5G core (5GC), and more specifically, connected to an AMF by an NG control (NG-C) interface and to a UPF by an NG user (NG-U) interface.

[0054] In addition, in a 5G (e.g., NR) wireless communication system, a UE can use DRX to reduce power consumption in an RRC_IDLE or RRC_INACTIVE mode. In an RRC_IDLE or RRC_INACTIVE state, the UE can only periodically (e.g., in each DRX cycle) monitor a physical downlink control channel (PDCCH) for a short period of time, rather than continuously monitoring the PDCCH, to receive a PO, a system information (SI) update notification, or an emergency notification.

[0055] Reference Figure 3 The paging message 310 can be transmitted through a physical downlink shared channel (PDSCH). If there is a paging message 310 in the PDSCH, a PDCCH can be shown as a paging radio network temporary identifier (P-RNTI). The P-RNTI can be common to all UEs. A UE identity, such as a system architecture evolution (SAE) temporary mobile subscription identifier (S-TMSI) of a UE in an RRC_IDLE state or an inactive radio network temporary identifier (I-RNTI) of a UE in an RRC_INACTIVE state, can be included in the paging message 310 to indicate paging for a specific UE.

[0056] The paging message 310 can include multiple UE identities for paging multiple UEs. The paging message 310 can be broadcast on a data channel (e.g., PDSCH) (e.g., PDCCH masked with P-RNTI). SI update and emergency notification are included in downlink control information (DCI), and the PDCCH carrying the DCI can be indicated as P-RNTI. In RRC_IDLE or RRC_INACTIVE mode, a UE can monitor one PO 305 per DRX cycle. In RRC_IDLE or RRC_INACTIVE mode, a UE can monitor a PO in an initial DL bandwidth part (DL BWP). In RRC connected state, a UE can monitor one or more POs to receive SI update notification and emergency notification. A UE can monitor all POs in a paging DRX cycle and at least one PO in an SI modification period. In RRC_IDLE or RRC_INACTIVE mode, a UE can monitor a PO in an active DL BWP. A PO is a set of S PDCCH monitoring occasions for paging, where S can indicate the number of synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) transmitted in a cell. A UE can first determine a paging frame (PF) and then determine a PO of the determined PF. One PF can be a radio frame of 10 ms. The PF and PO can be determined as follows, but the present disclosure is not limited thereto.

[0057] - The PF of a UE is a radio frame with a system frame number (SFN) that satisfies the expression (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N).

[0058] An index (i_s) indicating the index of a PO is determined by i_s = floor(UE_ID / N) mod Ns.

[0059] T is a DRX cycle of a UE.

[0060] In RRC_INACTIVE state, T is determined by the shortest of the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by non-access stratum (NAS), and the default DRX value broadcast in SI.

[0061] In RRC_IDLE state, T is determined by the shortest of the UE-specific DRX value configured by NAS and the default DRX value broadcast in SI. If the UE-specific DRX is not configured by upper layers (i.e., NAS), the default value is applied.

[0062] N is the number of total paging frames in T.

[0063] Ns is the number of POs per PF.

[0064] PF_offset is the offset for PF determination.

[0065] UE_ID is 5G-S-TMSI mod 1024.

[0066] The parameters Ns, nAndPagingFrameOffset and the length of the default DRX cycle are signaled in SIB1. The values of N and PF_offset are derived from the parameter nAndPagingFrameOffset defined in TS 38.331. If the UE does not have a 5G-S-TMSI, for example, when the UE has not registered onto the network, the UE will use UE_ID = 0 as the default identity in the above PF and i_s formulas.

[0067] The PDCCH monitoring occasions for paging are determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB.

[0068] If the search space identity (SearchSpaceId) = 0 is configured for the pagingSearchSpace, the PDCCH monitoring timing for paging is the same as for remaining SI (RMSI) (see definition in clause 13 in TS 38.213). If SearchSpaceId = 0 is configured for pagingSearchSpace, Ns can be 1 or 2. If Ns = 1, there is only a single PO in the PF starting from the first PDCCH monitoring time for paging. If Ns = 2, the PO is present in either the first half frame (i_s = 0) or the second half frame (i_s = 1) of the PF.

[0069] If non-zero SearchSpaceId is configured for paging search space, UE can monitor the (i_s+1)th PO. The PDCCH monitoring occasions for paging are determined based on the paging search space configuration (paging-searchspace) signaled by gNB. In case the PDCCH monitoring for paging does not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon), the numbering can be sequential starting from 0, i.e., starting from the first PDCCH monitoring occasion for paging in a PF. gNB can signal the parameter firstPDCCH-MonitoringOcasionOfPO corresponding to each PO of a PF. If firstPDCCH-MonitoringOcasionOfPO is signaled, the (i_s+1)th PO is a set of S consecutive PDCCH monitoring occasions for paging starting from the PDCCH monitoring occasion number indicated by firstPDCCH-MonitoringOcasionOfPO. That is, the (i_s+1)th value of the firstPDCCH-MonitoringOcasionOfPO parameter or the (i_s+1)th PO can be a set of S consecutive PDCCH monitoring occasions for paging starting from the (i_s*S)th PDCCH monitoring occasion for paging. S can be the number of actual transmitted SSBs determined according to the parameter ssb-PositionsInBurst signaled in SystemInformationBlock1 received from gNB. The parameter first-PDCCH-MonitoringOcasionOfPO is signaled in SIB1 for paging in initial DL BWP. When paging from a DL BWP other than initial DL BWP, the parameter first-PDCCH-MonitoringOcasionOfPO is signaled in the corresponding BWP configuration.

[0070] A PDCCH indicated as P-RNTI can transmit information according to DCI format 1_0. The following information can indicate information transmitted with DCI format 1_0 using cyclic redundancy check (CRC) scrambled with P-RNTI.

[0071] According to Table 1 below, Short Message Indicator - 2 bits.

[0072] According to Table 2 below, Short Message - 8 bits. This bit field is reserved if only scheduling information for paging is carried.

[0073] Frequency domain resource allocation - Bit. This bit field is reserved if only short message is carried.

[0074] Size of CORESET 0.

[0075] Time domain resource allocation - 4 bits as defined in Technical Specification (TS) 38.214 standard. This bit field is reserved if only short message is carried.

[0076] VRB to PRB mapping - 1 bit according to TS 38.212 standard. This bit field is reserved if only short message is carried.

[0077] Modulation and coding scheme - 5 bits as defined in TS 38.214 standard, using Table 5.1.3.1-1. This bit field is reserved if only short message is carried.

[0078] Transport block (TB) scaling - 2 bits as defined in TS 38.214 standard. This bit field is reserved if only short message is carried.

[0079] Reserved bits - 6 bits.

[0080] The following Table 1 can indicate the short message indicator.

[0081] [Table 1]

[0082]

[0083] The following Table 2 defines the short message. Bit 1 can be the most significant bit (MSB).

[0084] [Table 2]

[0085]

[0086] The UE can detect a PDCCH transmission from the gNB to monitor the PO (305) and identify the short message indicator by which it determines whether there is a paging message. If the UE determines there is a paging message by the short message indicator, it can receive the PDSCH (e.g., the paging message) (310).

[0087] The paging message format is shown in Table 3 below.

[0088] [Table 3]

[0089]

[0090] One paging message includes a list with PagingRecord as an entry, and each entry can include ue-Identity to indicate the UE to be paged. If the UE finds the same PagingRecord as its own UE identity (e.g., S-TMSI or I-RNTI) from the list, the UE can start the operation of switching to the RRC connected mode.

[0091] Depending on which entity initiates the paging, the paging can be classified into two types. CN initiated paging or CN paging indicates that the CN or AMF or MME initiates the paging, and RAN initiated paging or RAN paging indicates that the RAN (BS, gNB or eNB) initiates the paging.

[0092] The UE in idle mode can monitor the paging channel to receive the CN paging. The UE in inactive mode monitors the paging channel to receive the RAN paging as well as the CN paging. The UE does not need to monitor the paging channel continuously. The UE can be required to monitor the paging channel only once during the PO in the DRX cycle defined in TS 38.304. The paging DRX cycle can be configured by the network.

[0093] 1) For CN paging, the default periodicity (or default CN paging periodicity or default paging periodicity) can be broadcasted through SI.

[0094] 2) For CN paging, the UE specific periodicity (or UE specific CN paging periodicity) can be configured through NAS signaling.

[0095] 3) For RAN paging, the UE specific periodicity (or UE specific RAN paging periodicity or RAN paging periodicity) can be configured through RRC signaling.

[0096] The UE can use the lowest value among the applicable (i.e., configured) DRX periodicities depending on the RRC mode as the paging monitoring periodicity. That is, the UE in idle mode can use the lower value among the default CN paging periodicity and the UE specific CN paging periodicity (if configured). The UE in inactive mode can use the lowest value among the default CN paging periodicity, the UE specific CN paging periodicity (if configured), and the RAN paging periodicity (if configured).

[0097] Figure 4 A CN paging reception procedure of a UE in idle mode (RRC_Idle) according to an embodiment is illustrated.

[0098] Reference Figure 4, a UE in idle mode can monitor the paging channel for every predefined DRX cycle during the PO 405 to save energy. That is, the UE can enter sleep mode between POs. The UE can scan for PDCCH with CRC scrambled with P-RNTI for every PO. If the UPF receives DL data destined for the UE, the UPF can initiate a paging procedure to the AMF through a session management function (SMF). In step 410, the AMF can manage the location information of the UE in units of registered tracking areas and broadcast a NG application protocol (NGAP) paging message to all gNBs within the registered tracking area to which the UE belongs. In step 415, the gNBs that have received the NGAP paging message transmit PDCCH (with CRC scrambled with P-RNTI) according to the PO of the UE. In step 420, the UE scanning the PDCCH can detect the transmission of the PDCCH from the gNB and receive an RRC paging message. In step 425, if the UE finds the same PagingRecord as its own UE identity (e.g., S-TMSI or I-RNTI) in the RRC paging message, the UE can perform random access to establish an RRC connection.

[0099] Figure 5 A RAN paging reception procedure of a UE in an inactive mode (RRC_Inactive) according to an embodiment is illustrated.

[0100] Referring to Figure 5 , a UE in inactive mode can monitor the paging channel for every predefined DRX cycle during the PO 505 to save energy. That is, the UE can enter sleep mode between POs. The UE can scan for PDCCH with CRC scrambled with P-RNTI for every PO. In step 510, if the UPF receives DL data destined for the UE, the UE can send the received data to a serving BS (gNB). The serving BS can store or manage the location record of the UE in units of a RAN notification area (RNA). Accordingly, in FIG. 515, the serving BS can deliver an Xn application protocol (XnAP) RAN paging message to all gNBs in the RNA to which the UE belongs. In step 520, the gNBs that have received the XnAP RAN paging message transmit PDCCH (with CRC scrambled with P-RNTI) according to the PO of the UE. In step 525, the UE scanning the PDCCH can detect the transmission of the PDCCH from the gNB and receive an RRC paging message. In step 530, if the UE finds the same PagingRecord as its own UE identity (e.g., S-TMSI or I-RNTI) in the RRC paging message, the UE can perform random access to establish an RRC reconnection.

[0101] Figure 6 A procedure for a UE to determine a paging monitoring cycle is shown, in accordance with an embodiment.

[0102] Reference Figure 6 In step 605, the UE can receive system information blocks (SIBs). In step 610, the UE can select one cell based on one or more received SI fragments and camp on the selected cell. In step 615, the UE can establish an RRC connection setup with the camped cell.

[0103] In step 617, the UE can report UE capability. For example, the UE can report to the BS whether the UE supports eDRX (e.g., RRC_INACTIVE eDRX).

[0104] In step 620, the UE that has switched to RRC connected mode can receive eDRX configuration (e.g., eDRX configuration for CN paging or RRC_IDLE mode) from the CN in a negotiation process using NAS signaling (e.g., attach request / accept or tracking area update request / accept messages) with the CN (MME or AMF). The eDRX configuration can include eDRX cycle (e.g., T eDRX or T eDRX_IDLE ). The eDRX configuration can include paging time window (PTW) length information (e.g., length of PTW or PTW_IDLE).

[0105] In step 625, the UE’s RRC connected configuration can be released and the UE can switch the RRC mode to idle mode (RRC_IDLE) or inactive mode (RRC_INACTIVE). When the BS switches the UE to inactive mode, the RRC release message can include eDRX configuration information (e.g., eDRX configuration information for RAN paging or RRC_INACTIVE mode). The eDRX setting can include eDRX cycle (e.g., T eDRX_INACTIVE ).

[0106] The eDRX configuration can include PTW length information (e.g., length of PTW_INACTIVE).

[0107] In step 630, the UE in inactive or idle mode can move through several cells and perform cell selection and cell reselection.

[0108] In step 635, the UE can receive SIBs of the camped cell or BS. From this, the UE can receive whether the cell or BS allows or supports eDRX (e.g., eDRX-Allowed, eDRX-AllowedIdle, or eDRX-AllowedInactive).

[0109] In step 640, the UE can use the received eDRX configuration information, DRX configuration information, SIB indicator, etc. to calculate the paging monitoring period in inactive or idle mode and monitor the paging.

[0110] Figure 7 A paging procedure using eDRX in LTE is shown in accordance with an embodiment.

[0111] If extended DRX (eDRX) in LTE is configured to a UE in idle mode, the following can be applied. The present disclosure is not limited to the following embodiments.

[0112] In idle mode, the DRX cycle can be extended to 10.24s or longer, and up to 2621.44s (43.69 minutes).

[0113] - A Hyper slot frame number (Hyper-SFN, H-SFN, or HSFN) 705 is broadcast from the cell, and the HSFN can be increased once per period of SFN values. Reference Figure 7 If the first HSFN is n, the next HSFN can be n+1, and the next HSFN can be n+2, such that the HSFN is increased in this way (710). In LTE, as time passes, the SFN value is increased from 0 to 1023 (10 ms per radio frame), and the SFN returns to 0 after reaching 1023, and the HSFN value can be increased by 1. As a result, in 715, the length of one HSFN is equal to the length of 1024 SFNs, and can also be equal to 10240 ms (= 10.24s).

[0114] A Paging hyperframe (PH) can indicate the H-SFN in which the UE starts monitoring the paging DRX during the PTW used in ECM-IDLE mode. The PH can be determined by a formula known to the MME / AMF, UE, and BS, and can be determined from the eDRX cycle and the UE identity.

[0115] During the PTW, the UE can monitor the paging 1) during the PTW or 2) until a paging message including the UE’s NAS identity is received (whichever occurs first). The start offset of the PTW is uniformly distributed within the PH, and can be defined according to the 3GPP TS standard.

[0116] The MME / AMF can use the formulas defined in the 3GPP TS standard to determine the start times of PH and PTW. Furthermore, the MME / AMF can send an S1 paging request just before the start of PTW or during PTW to avoid the process of storing paging messages in the BS.

[0117] When a UE uses eDRX, it may not meet the requirements of Earthquake and Tsunami Warning System (ETWS), Commercial Mobile Alert Service (CMAS), and Public Warning System (PWS). For Extended Access Block (EAB), if the UE using eDRX supports SIB14, SIB14 can be obtained before the RRC connection is established.

[0118] When the eDRX period is longer than the SI modification period, the UE can check whether the stored SI is valid before the RRC connection is established. For UEs configured with an eDRX period longer than the SI modification period, a paging message including systemInfoModification-eDRX can be used to notify of the SI change.

[0119] In LTE, the UE can be configured by NAS to include eDRX cycles (T eDRX eDRX. A UE can only operate using eDRX if it is configured with eDRX by the NAS and if the serving cell indicates its support for eDRX via the SI. If T is configured in the UE... eDRX =512 radio frames, then PO can be monitored at T=512 according to conventional DRX operation (clause 7.1 in TS 36.304). In other cases, a UE configured with eDRX can monitor PO: 1) during periodic PTW according to conventional DRX operation (e.g., clause 7.1 in TS 36.304), or 2) until a paging message including the UE's NAS identifier is received (whichever occurs first).

[0120] PTW 720 is UE-specific and can be determined by 1) PH 725, 2) the PTW start point (PTW_start) 730 within PH 725, and 3) the PTW end point (PTW_end) 735. These three PTW determining factors are shown in Table 4 below. PTW_end 735 can also indicate the SFN outside PH 725, which includes PTW_start 730, which depends on the configuration length of PTW_start 730 and PTW 720.

[0121] [Table 4]

[0122]

[0123]

[0124] In LTE, the configuration of a UE with eDRX depends on the UE's RRC state and whether the UE is inside or outside the PTW, depending on the T eDRX The configuration (e.g., 620) and whether the cell where the user is camped supports eDRX (e.g., 635) are monitored for PO in the period indicated in the description below. (rf = radio frame, UE-specific period = UE-specific CN paging period, default period = default CN paging period)

[0125] 1. A UE in RRC_IDLE state can depend on the following three cases (Case 1) IDLE,LTE Case 2 IDLE,LTE and situation 3 IDLE,LTE To determine the paging monitoring cycle (T) DRX_IDLE,LTE ).

[0126] Note that the min instruction is a function that outputs the minimum value among the input values ​​configured for the UE.

[0127] Case 1 IDLE,LTE When T eDRX When not configured or the cell does not allow eDRX

[0128] =>T DRX_IDLE,LTE =min(UE-specific paging period, default paging period)

[0129] Case 2 IDLE,LTE When T eDRX =512rf (=5.12 seconds) is configured and eDRX is enabled in the camped cell.

[0130] =>T DRX_IDLE,LTE =T eDRX =5.12 seconds

[0131] Case 3 IDLE,LTE When T eDRX When ≠512rf (=5.12 seconds) is configured and eDRX is enabled in the camped cell.

[0132] => Within PTW, T DRX_IDLE,LTE =min(UE-specific paging period, default paging period)

[0133] => Outside of PTW, the UE may not monitor paging.

[0134] 2. A UE in RRC_INACTIVE state can depend on the following three cases (Case 1) INACTIVE,LTE Case 2 INACTIVE,LTE and situation 3 INACTIVE,LTE To determine the paging monitoring cycle (T) DRX_INACTIVE,LTE ).

[0135] Case 1 INACTIVE,LTE ) When T eDRX is not configured or the camping cell does not allow eDRX

[0136] => T DRX_INACTIVE,LTE = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0137] - Case 2 INACTIVE,LTE ) When T eDRX = 512rf (= 5.12 seconds) is configured and the camping cell allows eDRX

[0138] => T DRX_INACTIVE,LTE = min (T eDRX (= 5.12 seconds), RAN paging cycle)

[0139] Case 3 INACTIVE,LTE ) When T eDRX ≠ 512rf (= 5.12 seconds) and the camping cell allows eDRX

[0140] => Within PTW, T DRX_INACTIVE,LTE = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0141] => Outside PTW, T DRX_INACTIVE,LTE = RAN paging cycle

[0142] The above determination of the paging monitoring period (paging monitoring period and DRX cycle) in LTE can be summarized as shown in Table 5 and Table 6 below.

[0143] [Table 5]

[0144] - UE in RRC_IDLE mode

[0145]

[0146] [Table 6]

[0147] - UE in RRC_INACTIVE mode

[0148]

[0149] In NR Release (Rel) 17, unlike the eDRX configuration in LTE, the legacy T eDRX can be classified into an eDRX cycle for a UE in RRC_IDLE (= T eDRX_IDLE ) and an eDRX cycle for a UE in RRC_INACTIVE (= T eDRX_INACTIVE ). Since TeDRX_IDLE may be configured by the CN, so it can also be denoted as T eDRX_CN . Since T eDRX_INACTIVE may be configured by the RAN (BS), it can also be denoted as T eDRX_RAN . Also, in Rel-17 NR, the period (DRX cycle) in which a UE in RRC_IDLE and RRC_INACTIVE monitors paging can depend on the configuration of T eDRX_IDLE and T eDRX_INACTIVE and on whether the camping cell supports eDRX (eDRX-AllowedIdle or eDRX-AllowedInactive) (e.g., 635) and is determined as follows.

[0150] 1. A UE in RRC_IDLE can determine the paging monitoring period (T DRX_IDLE,NR ) according to the following three cases (Case 1 IDLE,NR , Case 2 IDLE,NR , and Case 3 IDLE,NR ).

[0151] Note that min indicates a function that outputs the minimum value only for values configured for the UE among the input values.

[0152] Case 1 IDLE,NR ) when T eDRX_IDLE is not configured

[0153] => T DRX_IDLE,NR = min (UE specific paging cycle, default paging cycle)

[0154] Case 2 IDLE,NR ) when T eDRX_IDLE ≤ 10.24 seconds is configured

[0155] => If eDRX-AllowedIdle is configured, T DRX_IDLE,NR = T eDRX_IDLE

[0156] => If eDRX-AllowedIdle is not configured, T DRX_IDLE,NR = min (UE specific paging cycle, default paging cycle)

[0157] Case 3 IDLE,NR ) when T eDRX_IDLE > 10.24 seconds is configured

[0158] => If eDRX-AllowedIdle is configured,

[0159] => Within PTW_IDLE, T DRX_IDLE,NR = min (UE specific paging cycle, default paging cycle)

[0160] => Outside of PTW_IDLE, the UE can not monitor paging.

[0161] Note that in Rel 17, only when T eDRX_IDLE > 10.24 seconds is PTW_IDLE defined and every T eDRX_IDLE occurs.

[0162] 2. A UE in RRC_INACTIVE can determine the paging monitoring period (T INACTIVE,NR ) depending on the following five cases (Case 1 INACTIVE,NR , Case 2 INACTIVE,NR , Case 3 INACTIVE,NR , Case 4 INACTIVE,NR , and Case 5 DRX_INACTIVE,NR ).

[0163] Case 1 INACTIVE,NR ) when T eDRX_IDLE is not configured and T eDRX_INACTIVE is also not configured

[0164] => T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0165] Case 2 INACTIVE,NR ) when T eDRX_IDLE ≤ 10.24 seconds is configured and T eDRX_INACTIVE is not configured

[0166] => If eDRX-AllowedIdle is configured, T DRX_INACTIVE,NR = min (T eDRX_IDLE , RAN paging cycle)

[0167] => If eDRX-AllowedIdle is not configured, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0168] Case 3 INACTIVE,NR ) when T eDRX_IDLE ≤ 10.24 seconds is configured and T eDRX_INACTIVE ≤ 10.24 seconds is configured

[0169] => If eDRX-AllowedIdle is configured and eDRX-AllowedInactive is configured, T DRX_INACTIVE,NR = min (T eDRX_IDLE , T eDRX_INACTIVE )

[0170] => If eDRX-AllowedIdle is configured and eDRX-AllowedInactive is not configured, T DRX_INACTIVE,NR = min (T eDRX_IDLE , RAN paging cycle)

[0171] => If eDRX-AllowedIdle is not configured and eDRX-AllowedInactive is not configured, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0172] Case 4 INACTIVE,NR ) when T eDRX_IDLE > 10.24 seconds is configured and T eDRX_INACTIVE is not configured

[0173] => If eDRX-AllowedIdle is configured,

[0174] => Within a PTW, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0175] => Outside a PTW, T DRX_INACTIVE,NR = RAN paging cycle

[0176] => If eDRX-AllowedIdle is not configured,

[0177] => T DRX_INACTIVE，NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0178] Case 5 INACTIVE，NR ) when T eDRX_IDLE > 10.24 seconds is configured and T eDRX_INACTIVE ≤ 10.24 seconds is configured

[0179] => If eDRX-AllowedIdle is configured and eDRX-AllowedInactive is configured,

[0180] => Within a PTW, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, T eDRX_INACTIVE )

[0181] => Outside a PTW, T DRX_INACTIVE,NR = T eDRX_INACTIVE

[0182] => If eDRX-AllowedIdle is configured and eDRX-AllowedInactive is not configured,

[0183] => Within PTW, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0184] => Outside PTW, T DRX_INACTIVE,NR = RAN paging cycle

[0185] => If eDRX-AllowedIdle is not configured and eDRX-AllowedInactive is not configured, T DRX_INACTIVE,NR = min (UE specific paging cycle, default paging cycle, RAN paging cycle)

[0186] T eDRX_INACTIVE > 10.24 seconds to reduce UE’s energy consumption in inactive mode. In this case, a PTW (e.g., PTW_INACTIVE) separate from PTW_IDLE can be defined. PTW_IDLE information (e.g., PTW_IDLE length) is a value configured by CN or AMF, and the UE can monitor CN paging in min (UE specific paging cycle, default paging cycle) period within PTW_IDLE, and can not monitor CN paging outside PTW_IDLE. Similarly, PTW_INACTIVE information (e.g., PTW_INACTIVE length) can be a value configured by RAN or BS, and the UE can monitor RAN paging in RAN paging cycle within PTW_INACTIVE, and can not monitor RAN paging outside PTW_INACTIVE.

[0187] When T eDRX_INACTIVE > 10.24 seconds, an indicator that BS supports or allows eDRX operation in idle mode can be defined in SIB (e.g., 635) (e.g., eDRX-AllowedIdle). For example, the BS can indicate whether eDRX in idle mode is supported or allowed by including or omitting eDRX-AllowedIdle in the SIB. eDRX_INACTIVE ≤ 10.24 seconds, and by including or omitting eDRX-AllowedInactive-long in the SIB whether eDRX in inactive mode is supported or allowed in a period of T eDRX_INACTIVE > 10.24 seconds.

[0188] In this document, if T eDRX_INACTIVE > 10.24 seconds (e.g., Rel-18 NR), the paging monitoring periodicity of a UE in inactive mode can depend on SIB indicators (e.g., eDRX-AllowedIdle, eDRX-AllowedInactive, and eDRX-AllowedInactive-long) and T eDRX_IDLE / T eDRX_INACTIVE are configured differently.

[0189] In case 1-1, when a UE

[0190] 1) is configured by the CN or AMF with T eDRX_IDLE > 10.24 seconds (620),

[0191] 2) is configured by the BS with T eDRX_INACTIVE > 10.24 seconds (625), and

[0192] 3) where the cell in which the UE resides while in inactive mode includes / includes / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) (635), respectively,

[0193] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds and is allowed to perform operations in the corresponding cell according to it, the UE can perform idle mode eDRX operations at T eDRX_IDLE > 10.24 seconds. The UE can only monitor for CN paging in the period of min (default paging cycle, UE-specific paging cycle) for the configured value within PTW_IDLE and can not monitor for CN paging outside of PTW_IDLE. Also, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds and is allowed to perform operations in the corresponding cell according to it, the UE can perform inactive mode eDRX operations at T eDRX_INACTIVE > 10.24 seconds. The UE can only monitor for RAN paging in the RAN paging cycle for the configured value within PTW_INACTIVE and can not monitor for RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring periodicity 640 of a UE in inactive mode can be as follows (for the configured value only).

[0194] 1) within PTW_IDLE and within PTW_INACTIVE,

[0195] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0196] 2) within PTW_IDLE and outside PTW_INACTIVE,

[0197] min (default paging cycle, UE specific paging cycle)

[0198] 3) outside PTW_IDLE and within PTW_INACTIVE,

[0199] RAN paging cycle

[0200] 4) outside PTW_IDLE and outside PTW_INACTIVE,

[0201] The UE can not perform paging monitoring.

[0202] In case 1-2, when the UE

[0203] 1) is configured with T eDRX_IDLE > 10.24 seconds by the CN or AMF,

[0204] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and

[0205] 3) where the cell in which the UE resides when in inactive mode includes / excludes / excludes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively,

[0206] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds and is allowed to perform operation according thereto in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE > 10.24 seconds. The UE can monitor CN paging in min (default paging cycle, UE specific paging cycle) for the configured value only within PTW_IDLE and can not monitor CN paging outside PTW_IDLE. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds but is not allowed to perform operation according thereto in the corresponding cell, the UE can not perform inactive mode eDRX operation at T eDRX_INACTIVE > 10.24 seconds. The UE can always (regardless of the portion according to PTW_INACTIVE) monitor RAN paging in RAN paging cycle. Thus, the paging monitoring period 640 of the UE in inactive mode can be as follows (for the configured value only).

[0207] 1) Within PTW_IDLE

[0208] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0209] 2) Outside PTW_IDLE,

[0210] RAN paging cycle

[0211] In case 1-3, when the UE

[0212] 1) is configured with T eDRX_IDLE > 10.24 seconds by the CN or AMF,

[0213] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and

[0214] 3) where the cell in which the UE resides while in inactive mode includes / includes / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0215] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds and is allowed to perform operation according to it in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE > 10.24 seconds. The UE can monitor CN paging in min (default paging cycle, UE specific paging cycle) cycles for the configured value only within PTW_IDLE and can not monitor CN paging outside PTW_IDLE. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds but is not allowed to perform operation according to it in the corresponding cell, the UE can not perform inactive mode eDRX operation at T eDRX_INACTIVE > 10.24 seconds. The UE can monitor RAN paging in the cycle according to one of the following options.

[0216] Option 1) The UE can always (regardless of the part according to PTW_INACTIVE) monitor RAN paging in the RAN paging cycle.

[0217] Option 2) Option 2 is based on the assumption that the UE can be configured with T eDRX_INACTIVE > 10.24 seconds (e.g., ran-ExtendedPagingCycle in RRCRelease message) and T eDRX_INACTIVE≤ 10.24 seconds (e.g., ran-ExtendedPagingCycle-long in RRCRelease message).

[0218] If the UE is configured with T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE ≤ 10.24 seconds, the UE cannot use T eDRX_INACTIVE > 10.24 seconds in the corresponding cell, but can use a separately configured T eDRX_INACTIVE ≤ 10.24 seconds instead of using the RAN paging cycle to reduce energy consumption for RAN paging monitoring.

[0219] If the UE is not configured with T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE ≤ 10.24 seconds, the UE can monitor RAN paging in the RAN paging cycle.

[0220] Option 3) Although the UE cannot use T eDRX_INACTIVE > 10.24 seconds configured in the corresponding cell, the UE can monitor RAN paging with a period of 10.24 seconds since the cell allows T eDRX_INACTIVE ≤ 10.24 seconds. That is, 10.24 seconds, which is the maximum value in the range of T eDRX_INACTIVE ≤ 10.24 seconds that allows the energy consumption to be reduced as much as possible, can be used.

[0221] Therefore, the paging monitoring period 640 of the UE in the inactive mode can be as follows (only for configured values).

[0222] When Option 1

[0223] 1) Within PTW_IDLE

[0224] min (default paging cycle, UE-specific paging cycle, RAN paging cycle)

[0225] 2) Outside PTW_IDLE,

[0226] RAN paging cycle

[0227] When Option 2 is used

[0228] If T eDRX_INACTIVE ≤ 10.24 seconds is configured,

[0229] 1) Within PTW_IDLE

[0230] min (default paging cycle, UE-specific paging cycle, T eDRX_INACTIVE (≤ 10.24 seconds))

[0231] 2) Outside of PTW_IDLE,

[0232] T eDRX_INACTIVE (≤ 10.24 seconds)

[0233] If T eDRX_INACTIVE ≤ 10.24 seconds is not configured,

[0234] 1) Within PTW_IDLE

[0235] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0236] 2) Outside of PTW_IDLE,

[0237] RAN paging cycle

[0238] When Option 3 is used

[0239] 1) Within PTW_IDLE

[0240] min (default paging cycle, UE specific paging cycle, 10.24 seconds)

[0241] 2) Outside of PTW_IDLE,

[0242] 10.24 seconds

[0243] In cases 1-4, when the UE

[0244] 1) is configured by the CN or AMF with T eDRX_IDLE > 10.24 seconds, and

[0245] 2) is configured by the BS with T eDRX_INACTIVE > 10.24 seconds, and

[0246] 3) where the cell in which the UE resides while in inactive mode includes / does not include / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively (635),

[0247] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds and is allowed to perform operations according to it in the corresponding cell, the UE can perform idle mode eDRX operations at T eDRX_IDLE > 10.24 seconds. The UE can only monitor for CN paging in the period of min (default paging cycle, UE specific paging cycle) for the configured value within PTW_IDLE and can not monitor for CN paging outside of PTW_IDLE. Furthermore, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE> 10.24 seconds is configured with inactive mode eDRX and is allowed to perform operation according to it in the corresponding cell, so the UE can perform paging monitoring in T eDRX_INACTIVE > 10.24 seconds. The UE can monitor RAN paging only for the configured value in the RAN paging cycle within PTW_INACTIVE and can not monitor RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period for the UE in inactive mode can be as follows (only for the configured value).

[0248] 1) within PTW_IDLE and within PTW_INACTIVE,

[0249] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0250] 2) within PTW_IDLE and outside of PTW_INACTIVE,

[0251] min (default paging cycle, UE specific paging cycle)

[0252] 3) outside of PTW_IDLE and within PTW_INACTIVE,

[0253] RAN paging cycle

[0254] 4) outside of PTW_IDLE and outside of PTW_INACTIVE,

[0255] The UE can not perform paging monitoring.

[0256] In cases 1-5, when the UE

[0257] 1) is configured with T eDRX_IDLE > 10.24 seconds by the CN or AMF, and

[0258] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and

[0259] 3) where the cell in which the UE resides when in inactive mode does not include / does not include / does not include the three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively (635),

[0260] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds, but is not allowed to perform operation according to it in the corresponding cell, so the UE can perform paging monitoring in T eDRX_IDLE> 10.24 seconds does not perform the idle mode eDRX operation. That is, the UE can always (regardless of the part according to PTW_IDLE) monitor the CN paging in the period of min (default paging cycle, UE specific paging cycle). Also, since the UE according to T eDRX_INACTIVE > 10.24 seconds is configured with the inactive mode eDRX but is not allowed to perform the operation according thereto in the corresponding cell, the UE can not be able to monitor the RAN paging in T eDRX_INACTIVE > 10.24 seconds performs the inactive mode eDRX operation. In other words, the UE can always monitor the RAN paging in the RAN paging cycle regardless of the part according to PTW_INACTIVE. Thus, the paging monitoring period of the UE in the inactive mode can be as follows (only for the configured value).

[0261] - min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0262] In case 1-6, when the UE

[0263] 1) is configured with T eDRX_IDLE > 10.24 seconds by the CN or AMF,

[0264] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and

[0265] 3) where the cell in which the UE resides when in the inactive mode includes / two SIB indicators (eDRX-AllowedIdle and eDRX-AllowedInactive-long), respectively,

[0266] Since the UE according to T eDRX_IDLE > 10.24 seconds is configured with the idle mode eDRX and is allowed to perform the operation according thereto in the corresponding cell, the UE can perform the idle mode eDRX operation at T eDRX_IDLE > 10.24 seconds. The UE can monitor the CN paging within PTW_IDLE in the period of min (default paging cycle, UE specific paging cycle) only for the configured value, and can not monitor the CN paging outside PTW_IDLE. Also, since the UE according to T eDRX_INACTIVE > 10.24 seconds is configured with the inactive mode eDRX and is allowed to perform the operation according thereto in the corresponding cell, the UE can perform the inactive mode eDRX operation at T eDRX_INACTIVE> 10.24 seconds. The UE can monitor RAN paging only for configured values in RAN paging cycle within PTW_INACTIVE and can not monitor RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period for the UE in inactive mode can be as follows (only for configured values).

[0267] 1) within PTW_IDLE and within PTW_INACTIVE,

[0268] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0269] 2) within PTW_IDLE and outside of PTW_INACTIVE,

[0270] min (default paging cycle, UE specific paging cycle)

[0271] 3) outside of PTW_IDLE and within PTW_INACTIVE,

[0272] RAN paging cycle

[0273] 4) outside of PTW_IDLE and outside of PTW_INACTIVE;

[0274] The UE can not perform paging monitoring.

[0275] In cases 1-7, when the UE

[0276] 1) is configured with T eDRX_IDLE > 10.24 seconds by the CN or AMF,

[0277] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and

[0278] 3) where the cell in which the UE resides when in inactive mode includes / excludes two SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive-long) respectively,

[0279] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE > 10.24 seconds and is allowed to perform operation according to it in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE > 10.24 seconds. The UE can monitor CN paging only for configured values in min (default paging cycle, UE specific paging cycle) period within PTW_IDLE and can not monitor CN paging outside of PTW_IDLE. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE> 10.24 seconds is configured with inactive mode eDRX but is not allowed to perform operation according to it in the corresponding cell, thus the UE can not be able to monitor RAN paging in T eDRX_INACTIVE > 10.24 seconds performs inactive mode eDRX operation. In other words, regardless of the part according to PTW_INACTIVE, the UE can always monitor RAN paging in RAN paging cycle. Thus, the paging monitoring period 640 of the UE in inactive mode can be as follows (only for configured values).

[0280] 1) within PTW_IDLE

[0281] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0282] 2) outside PTW_IDLE,

[0283] RAN paging cycle

[0284] In case 2-1, when the UE

[0285] 1) is configured with T eDRX_IDLE ≤ 10.24 seconds by CN or AMF,

[0286] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by BS, and

[0287] 3) where the cell in which the UE resides when in inactive mode includes / includes / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0288] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operation according to it in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE ≤ 10.24 seconds. In other words, regardless of the part according to PTW_IDLE, the UE can always monitor CN paging in T eDRX_IDLE cycle only for configured values. In addition, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds and is allowed to perform operation according to it in the corresponding cell, the UE can perform inactive mode eDRX operation at T eDRX_INACTIVE> 10.24 seconds. That is, the UE can monitor RAN paging only for the configured value in the RAN paging cycle within PTW_INACTIVE and can not monitor RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period of the UE in the inactive mode can be as follows (only for the configured value).

[0289] 1) within PTW_INACTIVE,

[0290] min(T eDRX_IDLE , RAN paging cycle)

[0291] 2) outside of PTW_INACTIVE,

[0292] T eDRX_IDLE

[0293] In case 2-2, when the UE

[0294] 1) is configured by the CN or AMF with T eDRX_IDLE ≤ 10.24 seconds,

[0295] 2) is configured by the BS with T eDRX_INACTIVE > 10.24 seconds, and

[0296] 3) where the cell in which the UE camps while in the inactive mode includes / does not include / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0297] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operation according thereto in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE ≤ 10.24 seconds. In other words, regardless of the portion according to PTW_IDLE, the UE can always monitor CN paging only for the configured value in the T eDRX_IDLE period. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds but is not allowed to perform operation according thereto in the corresponding cell, the UE can not perform inactive mode eDRX operation at T eDRX_INACTIVE > 10.24 seconds. In other words, regardless of the portion according to PTW_INACTIVE, the UE can always monitor RAN paging in the RAN paging cycle. Thus, the paging monitoring period of the UE in the inactive mode can be as follows (only for the configured value).

[0298] min(T eDRX_IDLE , RAN paging cycle)

[0299] In case 2-3, when the UE

[0300] 1) is configured with T eDRX_IDLE ≤ 10.24 seconds by the CN or AMF,

[0301] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and,

[0302] 3) where the cell in which the UE resides while in inactive mode includes / includes / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0303] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operations according thereto in the corresponding cell, the UE can perform idle mode eDRX operations at T eDRX_IDLE ≤ 10.24 seconds. In other words, regardless of the portion according to PTW_IDLE, the UE can always monitor the CN paging only for the configured value in T eDRX_IDLE period. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds, but is not allowed to perform operations according thereto in the corresponding cell, the UE can not perform inactive mode eDRX operations at T eDRX_INACTIVE > 10.24 seconds. The UE can monitor the RAN paging in the period according to one of the following options.

[0304] Option 1) The UE can always (regardless of the portion according to PTW_INACTIVE) monitor the RAN paging in the RAN paging cycle.

[0305] Option 2) Option 2 is based on the assumption that the UE can be configured with T eDRX_INACTIVE > 10.24 seconds (e.g., ran-ExtendedPagingCycle in the RRCRelease message) and T eDRX_INACTIVE ≤ 10.24 seconds (e.g., ran-ExtendedPagingCycle-long in the RRCRelease message) by the BS.

[0306] If the UE is configured with T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE≤ 10.24 seconds, then the UE cannot use T eDRX_INACTIVE > 10.24 seconds, but can use a separately configured T eDRX_INACTIVE ≤ 10.24 seconds instead of using the RAN paging cycle to reduce energy consumption of RAN paging monitoring.

[0307] If the UE is not configured with T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE ≤ 10.24 seconds, then the UE can monitor RAN paging in the RAN paging cycle.

[0308] Option 3) Although the UE cannot use T eDRX_INACTIVE > 10.24 seconds configured in the cell, since the cell allows T eDRX_INACTIVE ≤ 10.24 seconds, the UE can monitor RAN paging with a period of 10.24 seconds. That is, 10.24 seconds can be used, which is the maximum value within the range of T eDRX_INACTIVE ≤ 10.24 seconds that allows energy consumption to be reduced as much as possible.

[0309] Therefore, the paging monitoring period 640 of the UE in the inactive mode can be as follows (only for configured values).

[0310] - When Option 1 is used

[0311] min(T eDRX_IDLE , RAN paging cycle)

[0312] When Option 2 is used

[0313] If T eDRX_INACTIVE ≤ 10.24 seconds is configured,

[0314] min(T eDRX_IDLE , T eDRX_INACTIVE (≤ 10.24 seconds))

[0315] If T eDRX_INACTIVE ≤ 10.24 seconds is not configured,

[0316] min(T eDRX_IDLE , RAN paging cycle)

[0317] When Option 3 is used

[0318] min(T eDRX_IDLE , 10.24 seconds)

[0319] In case 2-4, when the UE

[0320] 1) is configured by the CN or AMF with T eDRX_IDLE ≤ 10.24 seconds,

[0321] 2) configured with T eDRX_INACTIVE > 10.24 seconds, and

[0322] 3) where the cell in which the UE resides when in inactive mode includes / excludes / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0323] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operations according thereto in the corresponding cell, the UE can perform idle mode eDRX operations at T eDRX_IDLE ≤ 10.24 seconds. In other words, regardless of the portion according to PTW_IDLE, the UE can always monitor for CN paging only for the configured value at T eDRX_IDLE periods. Further, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds and is allowed to perform operations according thereto in the corresponding cell, the UE can perform inactive mode eDRX operations at T eDRX_INACTIVE > 10.24 seconds. The UE can monitor for RAN paging only for the configured value in RAN paging periods within PTW_INACTIVE and can not monitor for RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period 640 for a UE in inactive mode can be as follows (only for the configured value).

[0324] 1) within PTW_INACTIVE,

[0325] min(T eDRX_IDLE , RAN paging period)

[0326] 2) outside of PTW_INACTIVE,

[0327] T eDRX_IDLE

[0328] In case 2-5, when the UE

[0329] 1) is configured with T eDRX_IDLE ≤ 10.24 seconds by the CN or AMF,

[0330] 2) is configured with T eDRX_INACTIVE > 10.24 seconds by the BS, and,

[0331] 3) where the cell in which the UE camps when in inactive mode does not include / include / include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0332] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds but is not allowed to perform operations according thereto in the corresponding cell, the UE can not perform idle mode eDRX operations at T eDRX_IDLE ≤ 10.24 seconds. That is, regardless of the portion according to PTW_IDLE, the UE can always monitor CN paging with a period of min (default paging cycle, UE-specific paging cycle). Furthermore, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds but is not allowed to perform operations according thereto in the corresponding cell, the UE can not perform inactive mode eDRX operations at T eDRX_INACTIVE > 10.24 seconds. In other words, regardless of the portion according to PTW_INACTIVE, the UE can always monitor RAN paging in the RAN paging cycle. Thus, the paging monitoring period of the UE in the inactive mode can be as follows (only for configured values).

[0333] min (default paging cycle, UE-specific paging cycle, RAN paging cycle)

[0334] In case 2-6, when the UE

[0335] 1) is configured by the CN or AMF to have T eDRX_IDLE ≤ 10.24 seconds,

[0336] 2) is configured by the BS to have T eDRX_INACTIVE > 10.24 seconds, and,

[0337] 3) where the cell in which the UE camps when in inactive mode includes / includes two SIB indicators (eDRX-AllowedIdle and eDRX-AllowedInactive-long), respectively,

[0338] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operations according thereto in the corresponding cell, the UE can perform idle mode eDRX operations at T eDRX_IDLE ≤ 10.24 seconds. In other words, regardless of the portion according to PTW_IDLE, the UE can always perform idle mode eDRX operations at T eDRX_IDLECN paging in the period. In addition, since the UE is configured with idle mode eDRX according to T eDRX_INACTIVE > 10.24 seconds and is allowed to perform operation according thereto in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_INACTIVE > 10.24 seconds. In other words, regardless of the part according to PTW_IDLE, the UE can always monitor CN paging only for the configured value in T eDRX_IDLE

[0339] 1) within PTW_IDLE,

[0340] min(T eDRX_IDLE , RAN paging period)

[0341] 2) outside PTW_IDLE,

[0342] T eDRX_IDLE

[0343] In case 2-7, when the UE

[0344] 1) is configured with T eDRX_INACTIVE ≤ 10.24 seconds by the CN or AMF,

[0345] 2) is configured with T eDRX_IDLE > 10.24 seconds by the BS, and,

[0346] 3) where the cell in which the UE camps when in idle mode includes / does not include two SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive-long) respectively,

[0347] Since the UE is configured with idle mode eDRX according to T eDRX_IDLE ≤ 10.24 seconds and is allowed to perform operation according thereto in the corresponding cell, the UE can perform idle mode eDRX operation at T eDRX_IDLE period. However, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds, but is not allowed to perform operation according thereto in the corresponding cell, the UE can not be able to perform inactive mode eDRX operation at T eDRX_INACTIVE ​> 10.24 seconds. In other words, regardless of the part according to PTW_INACTIVE, the UE can always monitor RAN paging in the RAN paging cycle. Thus, the paging monitoring period of the UE in the inactive mode can be as follows (only for configured values).

[0348] min(T eDRX_IDLE , RAN paging cycle)

[0349] In case 3-1, when the UE

[0350] 1) is not configured with T eDRX_IDLE ,

[0351] 2) is configured with T eDRX_INACTIVE > 10.24 seconds, and

[0352] 3) where the cell in which the UE camps while in the inactive mode includes / includes / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0353] Since the UE is not configured with T eDRX_IDLE , the UE can always monitor CN paging with a period of min (default paging cycle, UE specific paging cycle) regardless of the part according to PTW_IDLE. Also, since the UE is configured with T eDRX_INACTIVE > 10.24 seconds, the UE can perform the inactive mode eDRX operation with T eDRX_INACTIVE > 10.24 seconds. The UE can monitor RAN paging in the RAN paging cycle within PTW_INACTIVE only for configured values, and can not monitor RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period 640 of the UE in the inactive mode can be as follows (only for configured values).

[0354] 1) within PTW_INACTIVE,

[0355] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0356] 2) outside of PTW_INACTIVE,

[0357] min (default paging cycle, UE specific paging cycle)

[0358] In case 3-2, when the UE

[0359] 1) not configured with T eDRX_IDLE ,

[0360] 2) configured with T eDRX_INACTIVE > 10.24 seconds, and

[0361] 3) where the cell camped by the UE when in inactive mode includes / includes / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively,

[0362] Since the UE is not configured with T eDRX_IDLE , it can always (regardless of the part according to PTW_IDLE) monitor CN paging in the period of min (default paging cycle, UE-specific paging cycle). However, since the UE is configured with T eDRX_INACTIVE > 10.24 seconds according to the part of PTW_INACTIVE, but is not allowed to perform operations according to it in the corresponding cell, the UE can not be able to perform inactive mode eDRX operations in T eDRX_INACTIVE > 10.24 seconds. In other words, regardless of the part according to PTW_INACTIVE, the UE can always monitor RAN paging in the RAN paging cycle. Therefore, the paging monitoring period of the UE in inactive mode can be as follows (only for configured values).

[0363] min (default paging cycle, UE-specific paging cycle, RAN paging cycle)

[0364] In case 3-3, when the UE

[0365] 1) not configured with T eDRX_IDLE ,

[0366] 2) configured with T eDRX_INACTIVE > 10.24 seconds, and

[0367] 3) where the cell camped by the UE when in inactive mode includes / includes / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively,

[0368] Since the UE is not configured with T eDRX_IDLE , regardless of the part according to PTW_IDLE, the UE can always monitor CN paging in the period of min (default paging cycle, UE-specific paging cycle). However, since the UE is configured with T eDRX_INACTIVE> 10.24 seconds is configured with an inactive mode eDRX but is not allowed to perform operation according to it in the corresponding cell, so the UE can not be able to monitor RAN paging in T eDRX_INACTIVE > 10.24 seconds. The UE can monitor RAN paging in this period according to one of the following options.

[0369] In Option 1, the UE can always (regardless of the part according to PTW_INACTIVE) monitor RAN paging in the RAN paging cycle.

[0370] Option 2 is based on the assumption that the UE can be configured by the BS with T eDRX_INACTIVE > 10.24 seconds (e.g., ran-ExtendedPagingCycle in RRCRelease message) and T eDRX_INACTIVE ≤ 10.24 seconds (e.g., ran-ExtendedPagingCycle-long in RRCRelease message).

[0371] If the UE is configured with both T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE ≤ 10.24 seconds (625), the UE cannot use T eDRX_INACTIVE > 10.24 seconds in the corresponding cell, but can use a separately configured T eDRX_INACTIVE ≤ 10.24 seconds instead of using the RAN paging cycle to reduce energy consumption for RAN paging monitoring.

[0372] If the UE is not configured with T eDRX_INACTIVE > 10.24 seconds and T eDRX_INACTIVE ≤ 10.24 seconds (625), the UE can monitor RAN paging in the RAN paging cycle.

[0373] In Option 3, although the UE cannot use T eDRX_INACTIVE > 10.24 seconds configured in the cell, since the cell allows T eDRX_INACTIVE ≤ 10.24 seconds, the UE can monitor RAN paging with a period of 10.24 seconds. That is, 10.24 seconds can be used, which is the maximum value within the range of T eDRX_INACTIVE ≤ 10.24 seconds that allows energy consumption to be reduced as much as possible.

[0374] Therefore, the paging monitoring period of the UE in the inactive mode can be as follows (only for configured values).

[0375] - When Option 1 is used

[0376] min (default paging cycle, UE-specific paging cycle, RAN paging cycle)

[0377] - When Option 2 is used

[0378] If T eDRX_INACTIVE ≤ 10.24 seconds is configured,

[0379] min (default paging cycle, UE specific paging cycle, T eDRX_INACTIVE (≤ 10.24 seconds))

[0380] If T eDRX_INACTIVE ≤ 10.24 seconds is not configured,

[0381] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0382] - When Option 3 is used

[0383] min (default paging cycle, UE specific paging cycle, 10.24 seconds)

[0384] In case 3-4, when the UE

[0385] 1) is not configured by the CN or AMF with T eDRX_IDLE ,

[0386] 2) is configured by the BS with T eDRX_INACTIVE > 10.24 seconds, and

[0387] 3) where the cell in which the UE resides when in inactive mode includes / does not include / includes three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long) respectively,

[0388] Since the UE is not configured with T eDRX_IDLE , it can always (regardless of the part according to PTW_IDLE) monitor the CN paging in the cycle of min (default paging cycle, UE specific paging cycle). Furthermore, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds and is allowed to perform operations according thereto in the corresponding cell, the UE can perform inactive mode eDRX operations according to T eDRX_INACTIVE > 10.24 seconds. The UE can monitor RAN paging only for the configured values in the RAN paging cycle within PTW_INACTIVE and can not monitor RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring period 640 of the UE in inactive mode can be as follows (only for the configured values).

[0389] 1) Within PTW_INACTIVE,

[0390] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0391] 2) Outside of PTW_INACTIVE,

[0392] min (default paging cycle, UE specific paging cycle)

[0393] In case 3-5, when the UE

[0394] 1) Not configured with T eDRX_IDLE by the CN or AMF,

[0395] 2) Configured with T eDRX_INACTIVE > 10.24 seconds, and

[0396] 3) Where the cell in which the UE resides in inactive mode does not include / does not include / does not include three SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive / eDRX-AllowedInactive-long), respectively,

[0397] Since the UE is not configured with T eDRX_IDLE , it can always (regardless of the part according to PTW_IDLE) monitor CN paging in the cycle of min (default paging cycle, UE specific paging cycle). Furthermore, since the UE is configured with inactive mode eDRX according to T eDRX_INACTIVE > 10.24 seconds, but is not allowed to perform operations according to it in the corresponding cell, the UE can not be able to perform inactive mode eDRX operations according to T eDRX_INACTIVE > 10.24 seconds. In other words, regardless of the part according to PTW_INACTIVE, the UE can always monitor RAN paging in the RAN paging cycle. Therefore, the paging monitoring cycle of the UE in inactive mode can be as follows (only for configured values).

[0398] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0399] In case 3-6, when the UE

[0400] 1) Not configured with T eDRX_IDLE by the CN or AMF,

[0401] 2) Configured with T eDRX_INACTIVE > 10.24 seconds, and

[0402] 3) where the cell in which the UE resides when in inactive mode includes / excludes two SIB indicators (eDRX-AllowedIdle and eDRX-AllowedInactive-long) respectively,

[0403] Since the UE is not configured with T eDRX_IDLE , the UE can always monitor for CN paging with a periodicity of min (default paging cycle, UE specific paging cycle) regardless of the part according to PTW_IDLE. Furthermore, since the UE is configured with T eDRX_INACTIVE > 10.24 seconds according to which it is allowed to perform operations in the corresponding cell, the UE can perform inactive mode eDRX operations in T eDRX_INACTIVE > 10.24 seconds. The UE can monitor for RAN paging only for the configured values in the RAN paging cycle within PTW_INACTIVE and can not monitor for RAN paging outside of PTW_INACTIVE. Thus, the paging monitoring periodicity for a UE in inactive mode can be as follows (only for configured values).

[0404] 1) within PTW_INACTIVE,

[0405] min (default paging cycle, UE specific paging cycle, RAN paging cycle)

[0406] 2) outside of PTW_INACTIVE,

[0407] min (default paging cycle, UE specific paging cycle)

[0408] In case 3-7, when the UE

[0409] 1) is not configured by the CN or AMF with T eDRX_IDLE ,

[0410] 2) is configured by the BS with T eDRX_INACTIVE > 10.24 seconds, and

[0411] 3) where the cell in which the UE resides when in inactive mode includes / excludes two SIB indicators (eDRX-AllowedIdle / eDRX-AllowedInactive-long) respectively,

[0412] Since the UE is not configured with T eDRX_IDLE , the UE can always monitor for CN paging with a periodicity of min (default paging cycle, UE specific paging cycle) regardless of the part according to PTW_IDLE. However, since the UE is configured with T eDRX_INACTIVE> 10.24 seconds is configured with an inactive mode eDRX but is not allowed to perform operations according to it in the corresponding cell, so the UE can not be able to monitor the RAN paging in T eDRX_INACTIVE > 10.24 seconds performs an inactive mode eDRX operation. In other words, regardless of the part according to PTW_INACTIVE, the UE can always monitor the RAN paging in the RAN paging cycle. Therefore, the paging monitoring period 640 of the UE in the inactive mode can be as follows (only for configured values).

[0413] - min (default paging cycle, UE-specific paging cycle, RAN paging cycle)

[0414] Figure 8 A UE device according to an embodiment is illustrated.

[0415] Reference Figure 8 , the UE can include a radio frequency (RF) processor 810, a baseband processor 820, a storage unit 830, and a controller 840. The configuration of the UE is not limited to the example shown in Figure 8 and can include less or more configurations than the configuration shown in Figure 8 .

[0416] The RF processor 810 can perform a function of transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of a signal. That is, the RF processor 810 can up-convert a baseband signal provided from the baseband processor 820 to an RF band signal, thereby transmitting the RF band signal through an antenna, and down-convert an RF band signal received through the antenna to a baseband signal.

[0417] For example, the RF processor 810 can include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc., but is not limited to such examples. The UE can have a plurality of antennas and a plurality of RF chains. The RF processor 810 can perform beamforming. To perform beamforming, the RF processor 810 can adjust the phase and amplitude of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor 810 can perform MIMO, and can receive a plurality of layers when performing the MIMO operation.

[0418] The baseband processor 820 can perform a conversion function between a baseband signal and a bit string according to the physical layer specification of the system. For example, in the case of data transmission, the baseband processor 820 can encode and modulate a transmission bit string, thereby generating a complex symbol. Upon receiving data, the baseband processor 820 can demodulate and decode a baseband signal provided from the RF processor 810, thereby recovering a reception bit string.

[0419] For example, when an orthogonal frequency division multiplexing (OFDM) scheme is applied, the baseband processor 820 can generate a complex symbol by encoding and modulating a transmission bit string, map the complex symbol to a subcarrier, and then configure an OFDM symbol through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion when transmitting data. Also, when receiving data, the baseband processor 820 can divide a baseband signal provided from the RF processor 810 into an OFDM symbol unit, restore a signal mapped to a subcarrier through a fast Fourier transform (FFT) operation, and then restore a reception bit string through demodulation and decoding.

[0420] The baseband processor 820 and the RF processor 810 can transmit and receive signals as described above. Accordingly, the baseband processor 820 and the RF processor 810 can be referred to as a "transmitter", a "receiver", a "transceiver", or a "communication unit". At least one of the baseband processor 820 and the RF processor 810 can include a plurality of communication modules to support a plurality of different wireless access technologies. Also, at least one of the baseband processor 820 and the RF processor 810 can include different communication modules for processing signals in different frequency bands. For example, the different wireless access technologies can include a wireless local area network (LAN), a cellular network (e.g., LTE), etc. Also, the different frequency bands can include a super high frequency (SHF) (e.g., 2.NRHz or NRHz) band and a mmWave (e.g., 60GHz) band. The UE can transmit and receive signals to and from the BS using the baseband processor 820 and the RF processor 810, and the signals can include control information and data.

[0421] The storage unit 830 can store data such as a basic program, an application program, and configuration information for the operation of the UE. For example, the storage unit 830 can store data information such as a basic program, an application program, and configuration information for the operation of the UE, can provide the stored data in response to a request from the controller 840, and can store a program for executing the above-described method for eDRX.

[0422] The storage unit 830 can be configured as a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disk (CD)-ROM, and a digital versatile disk (DVD), or a combination of storage media. Also, the storage unit 830 can be configured as a plurality of memories.

[0423] The controller 840 controls the overall operation of the UE. For example, the controller 840 can transmit and receive signals through the baseband processor 820 and the RF processor 810.

[0424] Furthermore, the controller 840 can record data in and read data from the storage unit 830. For this purpose, the controller 840 may include at least one processor. For example, the controller 840 may include a communication processor (CP) for controlling communications and an application processor (AP) for controlling upper-layer applications such as applications. Additionally, the controller 840 may include a multi-connection processor 842 for executing procedures for operation in multi-connection mode. Furthermore, at least one component of the UE may be implemented as a single chip.

[0425] Figure 9 A BS device according to an embodiment is shown.

[0426] Figure 9 The BS shown can be included in the network described above.

[0427] like Figure 9 As shown, the BS may include an RF processor 910, a baseband processor 920, a backhaul communication unit 930, a storage unit 940, and a controller 950. The configuration of the BS is not limited to... Figure 9 The example shown can include more than Figure 9 The configuration shown has fewer or more options. The RF processor 910 can perform functions such as transmitting and receiving signals over a wireless channel, including frequency band switching and signal amplification.

[0428] The RF processor 910 can upconvert the baseband signal provided by the baseband processor 920 into an RF band signal, thereby transmitting the RF band signal through the antenna, and downconvert the RF band signal received through the antenna into a baseband signal.

[0429] RF processor 910 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), analog-to-digital converters (ADCs), etc. RF processor 910 may have multiple antennas and multiple RF chains. RF processor 910 can perform beamforming. To perform beamforming, RF processor 910 can adjust the phase and amplitude of signals transmitted and received through multiple antennas or antenna elements. Additionally, RF processor 910 can transmit one or more layers to perform DL MIMO operation.

[0430] The baseband processor 920 can perform a conversion function between a baseband signal and a bit string according to a physical layer specification of a system. For example, in the case of data transmission, the baseband processor 920 can encode and modulate a transmission bit string, thereby generating complex symbols. Upon receiving data, the baseband processor 920 can demodulate and decode a baseband signal provided from the RF processor 910, thereby recovering a reception bit string. For example, when an OFDM scheme is applied, when data is transmitted, the baseband processor 920 can generate complex symbols by encoding and modulating a transmission bit string, map the complex symbols to subcarriers, and then configure OFDM symbols through an IFFT operation and CP insertion. When data is received, the baseband processor 920 can divide a baseband signal provided from the RF processor 910 into OFDM symbol units, recover signals mapped with subcarriers through an FFT operation, and then recover a reception bit string through demodulation and decoding. The baseband processor 920 and the RF processor 910 can transmit and receive signals as described above. Accordingly, the baseband processor 920 and the RF processor 910 can be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The BS can transmit and receive signals to and from the UE using the baseband processor 920 and the RF processor 910, and the signals can include control information and data.

[0431] The backhaul communication unit 930 provides an interface for performing communication with other nodes in a network. For example, the backhaul communication unit 930 can convert a bit string transmitted from a master BS to another node such as a secondary BS, a CN, etc., into a physical signal, and convert a physical signal received from other nodes into a bit string.

[0432] The storage unit 940 can store data such as a basic program, an application program, and configuration information for operation of the master BS. For example, the storage unit 940 can store information about a bearer allocated to a connected UE, a measurement result reported from a connected UE, etc. The storage unit 940 can store information used as a criterion for determining whether to provide or suspend multiple connections to a UE. Further, the storage unit 940 can provide stored data in response to a request from the controller 950. The storage unit 940 can be configured as a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media. Further, the storage unit 940 can be configured as a plurality of memories. The storage unit 940 can store a program for performing the above-described method for eDRX.

[0433] The controller 950 controls overall operations of the master BS. For example, the controller 950 can transmit and receive signals through the baseband processor 920 and the RF processor 910 or through the backhaul communication unit 930. Also, the controller 950 can record and read data in and from the storage unit 940. To this end, the controller 950 can include at least one processor. Also, the controller 950 can include a multi-connectivity processor 952 for performing a procedure for operating in a multi-connectivity mode.

[0434] The method disclosed in the claims and / or the method according to the embodiments described in the specification of the disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0435] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) can be provided. The one or more programs stored in the computer-readable storage medium can be configured to be executed by one or more processors within the electronic device. At least one program can include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure.

[0436] The programs (software modules or software) can be stored in non-volatile memory including random access memory and flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), a magnetic disc storage device, an optical disc-ROM (CD-ROM), a DVD, or other types of optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them can form a memory in which the program is stored. A plurality of such memories can be included in the electronic device.

[0437] In addition, the programs can be stored in an attachable storage device that can access the electronic device through a communication network such as the Internet, an intranet, a LAN, a wide LAN (WLAN), and a storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. A separate storage device on the communication network can access the portable electronic device.

[0438] It should be understood that each of the blocks of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer- usable or computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0439] Each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be represented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks.

[0440] While the present disclosure has been illustrated and described with reference to various embodiments thereof, it will be understood that various changes in form and details can be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; and The controller, coupled to the transceiver, is configured as follows: For Radio Resource Control (RRC) inactivity, identify the first extended discontinuous reception (eDRX) cycle associated with the core network (CN) entity and the second eDRX cycle associated with the radio access network (RAN) node, and Based on the DRX cycle, paging timing is monitored during RRC inactivity. Specifically, in the case where both the first eDRX period and the second eDRX period are longer than 1024 radio frames: During the overlapping period of the first paging time window associated with the CN entity and the second paging time window associated with the RAN node, the DRX period is determined by the shortest value among the first UE-specific value configured by the upper layer, the second UE-specific value configured by the RRC, and the default DRX value broadcast in the system information. During the period included in the first paging time window associated with the CN entity and outside the second paging time window associated with the RAN node, the DRX period is determined by the shortest value between the first UE-specific value configured by the upper layer and the default DRX value broadcast in the system information; as well as During the period included in the second paging time window associated with the RAN node and outside the first paging time window associated with the CN entity, the DRX period is determined by a second UE-specific value configured by the RRC.

2. The UE according to claim 1, wherein, The controller is also configured as follows: Receive a System Information Block (SIB) from the RAN node, which includes at least one of a first indicator, a second indicator, and a third indicator. The first indicator indicates that eDRX for CN paging is permitted in the cell. The second indicator indicates that eDRX of 10.24 seconds or less is permitted in the cell for RAN paging, and The third indicator indicates that eDRX longer than 10.24 seconds for RAN paging is permitted in the cell.

3. The UE according to claim 2, in, In the case where the first eDRX period is longer than 1024 radio frames, the first indicator is received, but the second and third indicators are not received: During the time period included in the first paging time window associated with the CN entity, the DRX period is determined by the shortest value among the first UE-specific value configured by the upper layer, the second UE-specific value configured by the RRC, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by a second UE-specific value configured by the RRC.

4. The UE according to claim 2, in, In the case where the first eDRX period is longer than 1024 radio frames, the first and second indicators are received, but the third indicator is not received: During the time period included in the first paging time window associated with the CN entity, the DRX cycle is determined by the shortest value among the first UE-specific value configured by the upper layer, the value of the second eDRX cycle, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by the value of the second eDRX cycle.

5. The UE according to claim 2, in, When the first eDRX period is longer than 1024 radio frames and the second eDRX period is equal to or shorter than 1024 radio frames: During the time period included in the first paging time window associated with the CN entity, the DRX cycle is determined by the shortest value among the first UE-specific value configured by the upper layer, the value of the second eDRX cycle, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by the value of the second eDRX cycle.

6. The UE according to claim 1, wherein, The controller also includes: Receive first information from the Access and Mobility Management Function (AMF) entity for the first eDRX cycle configured for idle mode, and The first information includes information about the first paging time window.

7. The UE according to claim 1, wherein, The controller also includes: Receive second information from the base station for the second eDRX cycle configured for inactive mode. The second information includes information about the second paging time window.

8. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: For Radio Resource Control (RRC) inactivity, identify the first extended discontinuous reception (eDRX) cycle associated with the core network (CN) entity and the second eDRX cycle associated with the radio access network (RAN) node; and Based on the DRX cycle, paging timing is monitored during RRC inactivity. Specifically, in the case where both the first eDRX period and the second eDRX period are longer than 1024 radio frames: During the overlapping period of the first paging time window associated with the CN entity and the second paging time window associated with the RAN node, the DRX period is determined by the shortest value among the first UE-specific value configured by the upper layer, the second UE-specific value configured by the RRC, and the default DRX value broadcast in the system information. During the period included in the first paging time window associated with the CN entity and outside the second paging time window associated with the RAN node, the DRX period is determined by the shortest of the first UE-specific value configured at the upper layer and the default DRX value broadcast in the system information; and During the period included in the second paging time window associated with the RAN node and outside the first paging time window associated with the CN entity, the DRX period is determined by a second UE-specific value configured by the RRC.

9. The method according to claim 8, further comprising: Receive a System Information Block (SIB) from the RAN node, which includes at least one of a first indicator, a second indicator, and a third indicator. The first indicator indicates that eDRX for CN paging is permitted in the cell. The second indicator indicates that eDRX of 10.24 seconds or less is permitted in the cell for RAN paging, and The third indicator indicates that eDRX longer than 10.24 seconds for RAN paging is permitted in the cell.

10. The method according to claim 9, in, In the case where the first eDRX period is longer than 1024 radio frames, the first indicator is received, but the second and third indicators are not received: During the time period included in the first paging time window associated with the CN entity, the DRX period is determined by the shortest value among the first UE-specific value configured by the upper layer, the second UE-specific value configured by the RRC, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by a second UE-specific value configured by the RRC.

11. The method according to claim 9, in, In the case where the first eDRX period is longer than 1024 radio frames, the first and second indicators are received, but the third indicator is not received: During the time period included in the first paging time window associated with the CN entity, the DRX cycle is determined by the shortest value among the first UE-specific value configured by the upper layer, the value of the second eDRX cycle, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by the value of the second eDRX cycle.

12. The method according to claim 9, in, When the first eDRX period is longer than 1024 radio frames and the second eDRX period is equal to or shorter than 1024 radio frames: During the time period included in the first paging time window associated with the CN entity, the DRX cycle is determined by the shortest value among the first UE-specific value configured by the upper layer, the value of the second eDRX cycle, and the default DRX value broadcast in the system information; as well as During periods outside the first paging time window associated with the CN entity, the DRX cycle is determined by the value of the second eDRX cycle.

13. The method of claim 8, further comprising: Receive first information from the Access and Mobility Management Function (AMF) entity for the first eDRX cycle configured for idle mode, and The first information includes information about the first paging time window.

14. The method according to claim 13, Receive second information from the base station for the second eDRX cycle configured for inactive mode. in, The second piece of information includes information about the second paging time window.

Images