Patent Application
20240341006
This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2023-0044864, filed on Apr. 5, 2023, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference in its entirety.
The disclosure relates generally to the field of communication, and more particularly, to a user equipment (UE), a base station (BS), and methods thereof for extended discontinuous reception (eDRX) in wireless communication systems.
Fifth generation (5G) mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in sub 6 gigahertz (GHz) bands such as 3.5 GHz, but also in above 6 GHz bands referred to as millimeter wave (mmWave) including 28 GHz and 39 GHz. In addition, it has been considered to implement sixth generation (6G0 mobile communication technologies (referred to as beyond 5G systems) in terahertz (THz) bands, such as 95 GHz to 3 THz bands, to achieve transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
Since the outset of the development of 5G mobile communication technologies, to support services and to satisfy performance requirements in connection with enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine-type communications (mMTC), there has been ongoing standardization regarding beamforming and massive multiple input multiple output (MIMO) for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, operating multiple subcarrier spacings for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of bandwidth part (BWP), new channel coding methods such as a low density parity check (LDPC) code for large amounts of data transmission and a polar code for highly reliable transmission of control information, layer 2 (L2) pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
Discussions ensue regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as vehicle-to-everything (V2X) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, new radio unlicensed (NR-U) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
There is also ongoing standardization in air interface architecture/protocol regarding technologies such as industrial Internet of things (IIoT) for supporting 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 for simplifying random access procedures (2-step RACH for NR). There is also ongoing standardization in system architecture/service 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 mobile edge computing (MEC) for receiving services based on UE positions.
As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR) and the like, 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
Such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as full dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS), but also full-duplex technology for increasing 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 levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE (long-term evolution) or evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-A), LTE-Pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), institute of electrical and electronics engineers (IEEE) 802.16e, and typical voice-based services.
An LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and employs 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 control signals to a BS (BS or eNode B), and the DL indicates a radio link through which the BS transmits data or control signals to the UE. The above multiple access scheme separates data or control information of respective users by allocating and operating time-frequency resources for transmitting the data or control information for each user so as to avoid overlapping each other, that is, to establish orthogonality.
Since a 5G communication system, which is a communication system subsequent to LTE, must freely reflect various requirements of users and service providers, services satisfying various requirements including eMBB, mMTC, and URLLC, need to be supported.
The disclosure has been made to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below.
Accordingly, an aspect of the disclosure is to provide an apparatus and method capable of effectively providing services in a mobile communication system.
In accordance with an aspect 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 case that the first eDRX cycle is longer than 1024 radio frames and the second eDRX cycle is longer than 1024 radio frames: during an overlapped 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 a first UE specific value configured by an upper layer, a second UE specific value configured by an RRC, and a default DRX value broadcasted in system information; during a period included in the first paging time window associated with the CN entity and being outside of the 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 the upper layer and the default DRX value broadcasted in the system information; and during a period included in the second paging time window associated with the RAN node and being outside of the first paging time window associated with the CN entity, the DRX cycle is determined by the second UE specific value configured by the RRC.
The disclosed embodiment is able to effectively provide services in a mobile communication system.
The foregoing and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description with reference to the accompanying drawings, in which:
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of embodiments of the present disclosure. Accordingly, 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 constructions may be omitted for the sake of clarity and conciseness.
Similarly, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated and the size of each element does not completely reflect the actual size. The same or corresponding elements are provided with the same or corresponding reference numerals.
The following embodiments are provided only to completely explain the disclosure and inform those skilled in the art of the scope of the disclosure. Herein, the same or like reference signs indicate the same or like elements.
As used herein, a unit refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the unit does not always apply to software or hardware and may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the unit includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the unit may be either combined into fewer elements, or a unit, or divided more elements, or a unit. The elements and units or may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card.
In the following description, terms for identifying access nodes and for referring to network entities, messages, interfaces between network entities, various identification information, and the like are illustratively used for the sake of convenience. Therefore, the disclosure is not limited by the terms as used below, and other terms referring to subjects having equivalent technical meanings may be used.
Terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standards will be used for the sake of descriptive convenience. However, the disclosure is not limited by these terms and names, and may be similarly applied to systems that conform other standards. As to a BS, the term eNB may be interchangeably used with the term gNB for the sake of descriptive convenience. The term terminal may refer to mobile phones, node B (NB)-IoT devices, sensors, and various wireless communication devices.
Herein, a BS allocates resources to terminals, and may 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. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. The BS and the terminal are not limited to these examples.
The disclosure may be applied to 3GPP NR and to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety-related services, etc.) based on 5G communication and IoT-related technology.
Herein, LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems will be described by way of example, but the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types to the embodiments of the disclosure. Based on determinations by those skilled in the art, the embodiments of the disclosure may also be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure.
Referring to
In
The NR gNB 110 may employ an adaptive modulation & coding (AMC) scheme for determining a modulation scheme and a channel coding rate according to a channel state of a UE. The AMF 105 may perform functions such as mobility support, bearer configuration, and QoS configuration, is responsible for various control functions as well as a mobility management function for a UE, and may be connected to multiple BSs. In addition, the next-generation mobile communication system may interwork with the existing LTE system, and the AMF 105 may be connected to a mobility management entity (MME) 125 via a network interface. The MME 125 may be connected to an eNB 130 that is an existing BS. A UE supporting LTE-NR dual connectivity may transmit/receive data while maintaining connections to both the gNB 110 and the eNB 130.
Herein, a UE may have three radio resource control (RRC) wireless connection states in a next-generation mobile communication system. A connection mode (RRC_CONNECTED) 205 may indicate that the UE is in a wireless connection state capable of transmitting and receiving data. A idle mode (RRC_IDLE) 230 may indicate that the UE is in a wireless connection state of monitoring whether paging is transmitted to the UE. The connection mode 205 and the idle mode 230 are wireless connection states that may also be applied to the LTE system, and the details thereof may be the same as those of the LTE system. An inactive mode (RRC_INACTIVE) 215 may be newly applied, as well as the connection mode 205 and the idle mode 230, to the next-generation mobile communication system. The RRC_INACTIVE 215 state may correspond to an inactive wireless connection state, an inactive mode, a deactivated mode, or the like.
In the inactive mode 215 wireless connection state, the UE context may be maintained in the BS and the UE, and radio access network (RAN)-based paging may be supported. The characteristics of the inactive mode 215 wireless connection state are as follows.
The UE in the inactive mode 215 may switch to the connection mode 205 or the idle mode 230 through a specific procedure.
In step 210, the UE may switch from the inactive mode 215 to the connection mode 205 according to a resume process, and switch from the connection mode 205 to the inactive mode 215 through a release procedure including suspend setting information. One or more RRC messages may be transmitted and received between the UE and the BS in step 210, and step 210 may include one or more detailed steps.
In step 220, the UE may switch from the inactive mode 215 to the idle mode 230 through the release procedure 220 after the resume procedure.
In step 225, switching between the connection mode 205 and the idle mode 230 may be performed according to conventional LTE technology, such as an establishment or release procedure.
A 5G or next-generation radio access network (NG-RAN) based on NR may include NG-RAN nodes, and the NG-RAN node may correspond to a gNB. The gNB may provide NR user plane (UP) and control plane (CP) protocol termination to the UE. In addition, gNBs are connected through an NG interface for the 5G core (5GC), and more specifically, are connected to an AMF by an NG-control (NG-C) interface and to a UP function (UPF) by an NG-user (NG-U) interface.
Additionally, in a 5G, e.g., NR, wireless communication system, the UE may use DRX to reduce power consumption in the RRC_IDLE or RRC_INACTIVE mode. In an RRC_IDLE or RRC_INACTIVE state, the UE may monitor the physical downlink control channel (PDCCH) periodically (e.g., in every DRX cycle) only for a short period of time, instead of consistently monitor the PDCCH, to receive a PO, a system information (SI) update notification, or an emergency notification.
Referring to
The paging message 310 may include multiple UE identities for paging multiple UEs. The paging message 310 may be broadcast over a data channel (e.g., PDSCH) (for example, the PDCCH is masked with the P-RNTI). SI updates and emergency notifications are included in downlink control information (DCI), and the PDCCH carrying the DCI may be indicated as a P-RNTI. In the RRC_IDLE or RRC_INACTIVE mode, the UE may monitor one PO 305 every DRX cycle. In the RRC_IDLE or RRC_INACTIVE mode, the UE may monitor the PO in the initial DL bandwidth part (DL BWP). In the RRC connected state, the UE may monitor one or more POs to receive SI update notifications and emergency notifications. The UE may monitor all POs in the paging DRX cycle and monitor at least one PO in the SI modification period. In the RRC_IDLE or RRC_INACTIVE mode, the UE may monitor the PO in the active DL BWP. The PO is a set of S PDCCH monitoring occasions for paging, where S may indicate the number of synchronization signal and physical broadcast channel (PBCH) blocks (SSBs) transmitted in the cell. The UE may first determine a paging frame (PF) and then determine a PO for the determined PF. One PF may be a radio frame of 10 ms. The PF and PO may be determined as follows, but the disclosure is not limited thereto.
Index (i_s), indicating the index of the PO, is determined by i_s=floor (UE_ID/N) mod Ns.
T is the DRX cycle of the UE.
In the RRC_INACTIVE state, T is determined by the shortest of the UE specific DRX value configured by RRC, UE specific DRX value configured by a non-access stratum (NAS), and a default DRX value broadcast in SI.
In the RRC_IDLE state, T is determined by the shortest of UE specific DRX value configured by NAS and a 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.
Parameters Ns, nAndPagingFrameOffset, and the length of default DRX Cycle are signaled in SIB1. The values of N and PF_offset are derived from the parameter nAndPagingFrameOffset as defined in TS 38.331. If the UE has no 5G-S-TMSI, for instance when the UE has not yet registered onto the network, the UE shall use as default identity UE_ID=0 in the PF and i_s formulas above.
The PDCCH monitoring occasions for paging are determined based on paging search space configuration (paging-SearchSpace) signaled by the gNB.
If SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring timing for paging is the same as for remaining SI (RMSI) (see the definition in clause 13 in TS 38.213). If SearchSpaceId=0 is configured for pagingSearchSpace, Ns may be 1 or 2. If Ns=1, there is only a single PO starting from the first PDCCH monitoring time for paging in the PF. If Ns=2, the PO exists in the first half frame (i_s=0) or the second half frame (i_s=1) of the PF.
If a non-zero SearchSpaceId is configured for pagingSearchSpace, the UE may monitor the (i_s+1)th PO. The PDCCH monitoring time for paging is determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. In the case of PDCCH monitoring for paging that does not overlap the UL symbol (determined according to tdd-UL-DL-ConfigurationCommon), the numbering may be sequential from 0, i.e., from the first PDCCH monitoring time for paging in the PF. The gNB may signal the parameter firstPDCCH-MonitoringOccasionOfPO for each PO corresponding to the PF. If firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PO is a set of S consecutive PDCCH monitoring times for paging, starting from the PDCCH monitoring time number indicated by firstPDCCH-MonitoringOccasionOfPO. That is, the (i_s+1)th value of firstPDCCH-MonitoringOccasionOfPO parameter or the (i_s+1)th PO may be a set of S consecutive PDCCH monitoring times for paging, starting from the (i_s*S)th PDCCH monitoring time for paging. S may be the number of actually transmitted SSBs determined according to the parameter ssb-PositionsInBurst signaled in SystemInformationBlock1 received from the gNB. The parameter of first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. When paging from a DL BWP other than the initial DL BWP, the parameter of first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.
The PDCCH indicated as a P-RNTI may transmit information according to DCI format 1_0. The information below may indicate information transmitted in DCI format 1_0 using a cyclic redundancy check (CRC) scrambled with a P-RNTI.
Short messages indicator-2 bits according to Table 1 below.
Short messages-8 bits according to Table 2 below. If only the scheduling information for paging is carried, this bit field is reserved.
Time domain resource assignment—4 bits as defined in the technical specification (TS) 38.214 standard. If only the short message is carried, this bit field is reserved.
VRB-to-PRB mapping—1 bit according to the TS 38.212 standard. If only the short message is carried, this bit field is reserved.
Modulation and coding scheme—5 bits as defined in the TS 38.214 standard, using Table 5.1.3.1-1. If only the short message is carried, this bit field is reserved.
Transport block (TB) scaling—2 bits as defined in the TS 38.214 standard. If only the short message is carried, this bit field is reserved.
Reserved bits—6 bits
Table 1 below may indicate the short message indicators.
Table 2 below defines short messages. Bit 1 may be the most significant bit (MSB).
The UE may detect PDCCH transmission from the gNB to monitor the PO (305) and identify a short message indicator therethrough, thereby determining whether there is a paging message. If the UE determines that there is a paging message through the short message indicator, it may receive a PDSCH (e.g., paging message) (310).
The paging message format is as shown in Table 3 below.
One paging message includes a list with a PagingRecord as an entry, and each entry may include ue-Identity to indicate the UE subject to paging. If the UE finds a PagingRecord that is identical to its own UE identity (e.g., S-TMSI or I-RNTI) from the list, the UE may start an operation of switching to the RRC connection mode.
Paging may be classified into two types depending on which entity initiates paging. CN-initiated paging or CN paging indicates that the CN or the AMF or MME initiates paging, and RAN-initiated paging or RAN paging indicates that the RAN (BS, gNB, or eNB) initiates paging.
The UE in the idle mode may monitor a paging channel to receive CN paging. The UE in the inactive mode monitors the paging channel to receive RAN paging, as well as CN paging. The UEs do not need to continuously monitor the paging channel. The UEs may be required to monitor the paging channel only during the PO once in the DRX cycle defined in TS 38.304. The paging DRX cycle may be configured by the network.
The UE may use the lowest value among the applicable (i.e., configured) DRX cycles depending on the RRC mode as the paging monitoring cycle. That is, the UE in the idle mode may use the lower value of the default CN paging cycle and the UE-specific CN paging cycle (if configured). The UE in the inactive mode may use the lowest value among the default CN paging cycle, the UE-specific CN paging cycle (if configured), and the RAN paging cycle (if configured).
Referring to
Referring to
Referring to
In step 617, the UE may report UE capability. For example, the UE may report to the BS whether the UE supports eDRX (e.g., RRC_INACTIVE eDRX).
In step 620, the UE having switched to the RRC connection mode may receive an eDRX configuration (e.g., the eDRX configuration for CN paging or RRC_IDLE mode) from the CN in the negotiation procedure using NAS signaling (e.g., Attach request/accept or a tracking area update request/accept message) with the CN (MME or AMF). The eDRX configuration may include an eDRX cycle (e.g., TeDRX or TeDRX_IDLE). The eDRX configuration may include paging time window (PTW) length information (e.g., the length of PTW or PTW_IDLE).
In step 625, the UE's RRC connection configuration may be released, and the UE may switch the RRC mode to the idle mode (RRC_IDLE) or inactive mode (RRC_INACTIVE). When the BS switches the UE to the inactive mode, the RRC release message may include eDRX configuration information (e.g., eDRX configuration information for RAN paging or RRC_INACTIVE mode). The eDRX setting may include an eDRX cycle (e.g., TeDRX_INACTIVE).
An eDRX configuration may include PTW length information (e.g., the length of PTW_INACTIVE).
In step 630, the UE in the inactive or idle mode may move through several cells and perform cell selection and cell reselection.
In step 635, the UE may receive an SIB of the camped cell or BS. Through this, the UE may receive whether the cell or BS allows or supports eDRX (e.g., eDRX-Allowed, eDRX-AllowedIdle, or eDRX-AllowedInactive).
In step 640, the UE may calculate a paging monitoring cycle in the inactive or idle mode using the received eDRX configuration information, DRX configuration information, SIB indicator, or the like and monitor paging.
If extended DRX (eDRX) is configured to the UE in the idle mode in LTE, the following may be applied. The disclosure is not limited to the below examples.
In the idle mode, the DRX cycle may be extended to 10.24 s or more, and up to 2621.44 s (43.69 minutes).
Paging hyperframe (PH) may indicate the H-SFN in which the UE starts monitoring paging DRX during the PTW used in the ECM-IDLE mode. The PH may be determined by a formula known to the MME/AMF, UE, and BS, and may be determined as a function of eDRX cycle and UE identity.
During the PTW, the UE may monitor paging 1) during the PTW or 2) until receiving a paging message including the NAS identity of the UE (whichever occurs first). The start offset of the PTW is uniformly distributed within the PH and may be defined according to the 3GPP TS standard.
The MME/AMF may determine the start time of PH and PTW using the formula defined in the 3GPP TS standard. In addition, the MME/AMF may send an S1 paging request just before the start of the PTW or during the PTW to avoid the procedure of storing the paging message in the BS.
When the UE uses eDRX, the requirements of the earthquake and tsunami warning system (ETWS), commercial mobile alert service (CMAS), and public warning system (PWS) may not be satisfied. For extended access barring (EAB), if the UE using eDRX supports SIB14, SIB14 may be acquired before RRC connection establishment.
When the eDRX cycle is longer than the SI modification period, the UE may check whether the stored SI is valid before RRC connection establishment. For the UE configured with an eDRX cycle longer than the SI modification period, a paging message including systemInfoModification-eDRX may be used to notify SI changes.
In LTE, the UE may be configured with eDRX including an eDRX cycle (TeDRX) by the NAS. The UE may operate with eDRX only when the UE is configured with eDRX by the NAS and when the serving cell indicates that it supports eDRX through SI. If TeDRX=512 radio frames are configured in the UE, the PO may be monitored at T=512 according to the legacy DRX operation (clause 7.1 in TS 36.304). In other cases, the UE configured with eDRX may monitor the PO; 1) according to the legacy DRX operation (e.g. clause 7.1 in TS 36.304) during the periodic PTW or 2) until the reception of a paging message including the NAS identity of the UE (whichever occurs first).
The PTW 720 is UE-specific, and may be determined by 1) the PH 725, 2) the PTW start point (PTW_start) 730 within the PH 725, and 3) the PTW end point (PTW_end) 735. The three PTW determinants described above may be determined as shown below in Table 4. The PTW_end 735 may also indicate the SFN outside the PH 725, which includes the PTW_start 730 depending on the PTW_start 730 and the configured length of the PTW 720.
In LTE, the UE configured with eDRX may monitor the PO in the cycle indicated in the description below depending on the UE's RRC state and whether the UE is inside or outside the PTW, depending on the TeDRX configuration (e.g., 620), and whether the camped cell supports eDRX (e.g., 635). (rf=radio frame, UE specific cycle=UE specific CN paging cycle, Default cycle=Default CN paging cycle)
It is noted that min indicates a function that outputs the minimum value only for the values configured for the UE from among input values.
The above determination of the paging monitoring cycles (paging monitoring cycle and DRX cycle) in LTE may be summarized as shown in Table 5 and Table 6 below.
In NR Release (Rel) 17, unlike the eDRX configuration in LTE, the conventional TeDRX may be classified into an eDRX cycle for UE in the RRC_IDLE (=TeDRX_IDLE) and an eDRX cycle for UE in the RRC_INACTIVE (=TeDRX_INACTIVE). Since TeDRX_IDLE may be configured by the CN, it may also be expressed as TeDRX_CN. Since TeDRX_INACTIVE may be configured by the RAN (BS), it may also be expressed as TeDRX_RAN. In addition, in Release 17 NR, the cycle (DRX cycle) in which the UE in the RRC_IDLE and RRC_INACTIVE monitors paging may be determined depending on the configuration of TeDRX_IDLE and TeDRX_INACTIVE and depending on whether the camped cell supports eDRX (eDRX-AllowedIdle or eDRX-AllowedInactive) (e.g., 635) as follows.
It is noted that min indicates a function that outputs the minimum value only for the values configured for the UE from among input values.
It is noted that in Rel 17, PTW_IDLE is defined only when TeDRX_IDLE>10.24 seconds and occurs every TeDRX_IDLE.
TeDRX_INACTIVE>10.24 seconds may be supported/defined to reduce energy consumption of the UE in the inactive mode. In this case, a PTW separate from PTW_IDLE may be defined (e.g., PTW_INACTIVE). PTW_IDLE information (e.g., PTW_IDLE length) is a value configured by the CN or AMF, and the UE may monitor CN paging in the cycle of min (UE specific paging cycle, Default paging cycle) inside PTW_IDLE and may not monitor CN paging outside PTW_IDLE. Similarly, PTW_INACTIVE information (e.g., PTW_INACTIVE length) may be a value configured by the RAN or BS, and the UE may monitor RAN paging in the RAN paging cycle inside PTW_INACTIVE and may not monitor RAN paging outside PTW_INACTIVE.
An indicator with which the BS supports or allows eDRX operation when TeDRX_INACTIVE>10.24 seconds may be defined in the SIB (e.g., 635) (e.g., eDRX-AllowedInactive-long). For example, the BS may indicate whether to support or allow eDRX in the idle mode by including or omitting eDRX-AllowedIdle in or from the SIB, indicate whether to support or allow eDRX in the inactive mode in the cycle of TeDRX_INACTIVE≤10.24 seconds by including or omitting eDRX-AllowedInactive in or from the SIB, and indicate whether to support or allow eDRX in the inactive mode in the cycle of TeDRX_INACTIVE>10.24 seconds by including or omitting eDRX-AllowedInactive-long in or from the SIB.
Herein, if TeDRX_INACTIVE>10.24 seconds is supported (e.g., Release 18 NR), the paging monitoring cycle of the UE in the inactive mode may be determined differently depending on the SIB indicators (e.g., eDRX-AllowedIdle, eDRX-AllowedInactive, and eDRX-AllowedInactive-long), as well as TeDRX_IDLE/TeDRX_INACTIVE configurations.
In Case 1-1, when the UE
The UE may not perform paging monitoring.
In Case 1-2, when the UE
In Case 1-3, when the UE
Option 1) The UE may always (regardless of the section according to PTW_INACTIVE) monitor RAN paging in the RAN paging cycle.
Option 2) Option 2 is based on the assumption that the UE may be configured with both TeDRX_INACTIVE>10.24 seconds (e.g., ran-ExtendedPagingCycle in the RRCRelease message) and TeDRX_INACTIVE≤10.24 seconds (e.g., ran-ExtendedPagingCycle-long in the RRCRelease message) by the BS.
If the UE is configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤ 10.24 seconds, the UE is unable to use TeDRX_INACTIVE>10.24 seconds in the corresponding cell but may reduce energy consumption for RAN paging monitoring using TeDRX_INACTIVE≤10.24 seconds separately configured, instead of using a RAN paging cycle.
If the UE is not configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤ 10.24 seconds, the UE may monitor RAN paging in the RAN paging cycle.
Option 3) Although the UE is unable to use TeDRX_INACTIVE>10.24 seconds configured in the corresponding cell, since the cell allows TeDRX_INACTIVE≤10.24 seconds, the UE may monitor RAN paging in the cycle of 10.24 seconds. That is, 10.24 seconds, which is the greatest value in the range of TeDRX_INACTIVE≤10.24 seconds allowed to reduce energy consumption as much as possible, may be used.
Therefore, the paging monitoring cycle 640 of the UE in the inactive mode may be as follows (only for configured values).
When Option 1
If TeDRX_INACTIVE≤10.24 seconds is configured,
If TeDRX_INACTIVE≤10.24 seconds is not configured,
In Case 1-4, when the UE
The UE may not perform paging monitoring.
In Case 1-5, when the UE
In Case 1-6, when the UE
The UE may not perform paging monitoring.
In Case 1-7, when the UE
In Case 2-1, when the UE
In Case 2-2, when the UE
In Case 2-3, when the UE
Option 1) The UE may always (regardless of the section according to PTW_INACTIVE) monitor RAN paging in the RAN paging cycle.
Option 2) Option 2 is based on the assumption that the UE may be configured with both TeDRX_INACTIVE>10.24 seconds (e.g., ran-ExtendedPagingCycle in the RRCRelease message) and TeDRX_INACTIVE≤10.24 seconds (e.g., ran-ExtendedPagingCycle-long in the RRCRelease message) by the BS.
If the UE is configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤10.24 seconds, the UE is unable to use TeDRX_INACTIVE>10.24 seconds in the corresponding cell but may reduce energy consumption for RAN paging monitoring using TeDRX_INACTIVE≤10.24 seconds separately configured, instead of using RAN paging cycle.
If the UE is not configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤ 10.24 seconds, the UE may monitor RAN paging in the RAN paging cycle.
Option 3) Although the UE is unable to use TeDRX_INACTIVE>10.24 seconds configured in the cell, since the cell allows TeDRX_INACTIVE≤10.24 seconds, the UE may monitor RAN paging in the cycle of 10.24 seconds. That is, 10.24 seconds, which is the greatest value in the range of TeDRX_INACTIVE≤10.24 seconds allowed to reduce energy consumption as much as possible, may be used.
Therefore, the paging monitoring cycle 640 of the UE in the inactive mode may be as follows (only for configured values).
In Case 2-4, when the UE
TeDRX_INACTIVE>10.24 seconds. The UE may monitor RAN paging in the RAN paging cycle inside PTW_INACTIVE only for configured values, and may not monitor RAN paging outside PTW_INACTIVE. Therefore, the paging monitoring cycle 640 of the UE in the inactive mode may be as follows (only for configured values).
In Case 2-5, when the UE
In Case 2-6, when the UE
In Case 2-7, when the UE
In Case 3-1, when the UE
In Case 3-2, when the UE
In Case 3-3, when the UE
In Option 1, the UE may always (regardless of the section according to PTW_INACTIVE) monitor RAN paging in the RAN paging cycle.
Option 2 is based on the assumption that the UE may be configured with both TeDRX_INACTIVE>10.24 seconds (e.g., ran-ExtendedPagingCycle in the RRCRelease message) and TeDRX_INACTIVE≤10.24 seconds (e.g., ran-ExtendedPagingCycle-long in the RRCRelease message) by the BS.
If the UE is configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤10.24 seconds (625), the UE is unable to use TeDRX_INACTIVE>10.24 seconds in the corresponding cell but may reduce energy consumption for RAN paging monitoring using TeDRX_INACTIVE≤10.24 seconds separately configured, instead of using RAN paging cycle.
If the UE is not configured with both TeDRX_INACTIVE>10.24 seconds and TeDRX_INACTIVE≤ 10.24 seconds (625), the UE may monitor RAN paging in the RAN paging cycle.
In Option 3, although the UE is unable to use TeDRX_INACTIVE>10.24 seconds configured in the cell, since the cell allows TeDRX_INACTIVE≤10.24 seconds, the UE may monitor RAN paging in the cycle of 10.24 seconds. That is, 10.24 seconds, which is the greatest value in the range of TeDRX_INACTIVE≤10.24 seconds allowed to reduce energy consumption as much as possible, may be used.
Therefore, the paging monitoring cycle of the UE in the inactive mode may be as follows (only for configured values).
If TeDRX_INACTIVE≤10.24 seconds is configured,
If TeDRX_INACTIVE≤10.24 seconds is not configured,
In Case 3-4, when the UE
In Case 3-5, when the UE
In Case 3-6, when the UE
In Case 3-7, when the UE
Referring to
The RF processor 810 may 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 may up-convert a baseband signal provided from the baseband processor 820 to an RF band signal, thereby transmitting the same through an antenna, and down-convert an RF band signal received through the antenna to a baseband signal.
For example, the RF processor 810 may 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), and the like, but is not limited to such examples. The UE may have a plurality of antennas and a plurality of RF chains. The RF processor 810 may perform beamforming. To perform beamforming, the RF processor 810 may adjust the phases and magnitudes of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor 810 may perform MIMO, and may receive multiple layers when performing the MIMO operation.
The baseband processor 820 may perform a function of conversion 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 may encode and modulate transmission bit strings, thereby generating complex symbols. Upon receiving data, the baseband processor 820 may demodulate and decode a baseband signal provided from the RF processor 810, thereby recovering reception bit strings.
For example, when an orthogonal frequency division multiplexing (OFDM) scheme is applied, when transmitting data, the baseband processor 820 may generate complex symbols by encoding and modulating transmission bit strings, map the complex symbols with subcarriers, and then configure OFDM symbols through an inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 820 may divide the baseband signal provided from the RF processor 810 into OFDM symbol units, restore the signals mapped with the subcarriers through a fast Fourier transform (FFT) operation, and then restore reception bit strings through demodulation and decoding.
The baseband processor 820 and the RF processor 810 may transmit and receive signals as described above. Accordingly, the baseband processor 820 and the RF processor 810 may 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 may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processor 820 and the RF processor 810 may include different communication modules for processing signals in different frequency bands. For example, the different wireless access technologies may include a wireless local area network (LAN), a cellular network (e.g., LTE), and the like. In addition, the different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz or NRhz) band and an mmWave (e.g., 60 GHz) band. The UE may transmit and receive signals to and from the BS using the baseband processor 820 and the RF processor 810, and the signals may include control information and data.
The storage unit 830 may store data such as basic programs, application programs, and configuration information for the operation of the UE. For example, the storage unit 830 may store data information such as basic programs, application programs, and configuration information for the operation of the UE, may provide stored data in response to a request from the controller 840, and may store a program to perform the above-described method for eDRX.
The storage unit 830 may be configured as storage media such as read only memory (ROM), random access memory (RAM), hard disks, compact disc (CD)-ROM, and digital versatile disc (DVD), or a combination of the storage media. In addition, the storage unit 830 may be configured as a plurality of memories.
The controller 840 controls the overall operation of the UE. For example, the controller 840 may transmit and receive signals through the baseband processor 820 and the RF processor 810.
In addition, the controller 840 may record and read data in and from the storage unit 830. To this end, the controller 840 may include at least one processor. For example, the controller 840 may include a communication processor (CP) for controlling communication and an application processor (AP) for controlling upper layers such as application programs. In addition, The controller 840 may include a multi-connection processor 842 for performing a process for operation in a multi-connection mode. In addition, at least one element of the UE may be implemented as one chip.
The BS shown in
As shown in
The RF processor 910 may up-convert a baseband signal provided from the baseband processor 920 to an RF band signal, thereby transmitting the same through an antenna, and down-convert an RF band signal received through the antenna to a baseband signal.
The RF processor 910 may 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), and the like. The RF processor 910 may have a plurality of antennas and a plurality of RF chains. The RF processor 910 may perform beamforming. To perform beamforming, the RF processor 910 may adjust the phases and magnitudes of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processor 910 may transmit one or more layers to perform a DL MIMO operation.
The baseband processor 920 may perform a function of conversion 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 920 may encode and modulate transmission bit strings, thereby generating complex symbols. Upon receiving data, the baseband processor 920 may demodulate and decode a baseband signal provided from the RF processor 910, thereby recovering reception bit strings. For example, when an OFDM scheme is applied, when transmitting data, the baseband processor 920 may generate complex symbols by encoding and modulating transmission bit strings, map the complex symbols with subcarriers, and then configure OFDM symbols through an IFFT operation and CP insertion. When receiving data, the baseband processor 920 may divide the baseband signal provided from the RF processor 910 into OFDM symbol units, restore the signals mapped with the subcarriers through an FFT operation, and then restore reception bit strings through demodulation and decoding. The baseband processor 920 and the RF processor 910 may transmit and receive signals as described above. Accordingly, the baseband processor 920 and the RF processor 910 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The BS may transmit and receive signals to and from the UE using the baseband processor 920 and the RF processor 910, and the signals may include control information and data.
The backhaul communication unit 930 provides an interface for performing communication with other nodes in the network. For example, the backhaul communication unit 930 may convert a bit string, transmitted from the primary BS to another node, such as a secondary BS, a CN, etc., into a physical signal, and convert physical signals received from other nodes into bit strings.
The storage unit 940 may store data such as basic programs, application programs, and configuration information for the operation of the primary BS. For example, the storage unit 940 may store information about bearers assigned to the connected UE, measurement results reported from the connected UE, etc. The storage unit 940 may store information that serves as a criterion for determining whether to provide or suspend multiple connections to the UE. In addition, the storage unit 940 may provide stored data in response to a request from the controller 950. The storage unit 940 may be configured as storage media such as ROM, RAM, hard disks, CD-ROMs, and DVDs, or a combination of the storage media. In addition, the storage unit 940 may be configured as a plurality of memories. The storage unit 940 may store a program to perform the above-described method for eDRX.
The controller 950 controls the overall operation of the primary BS. For example, the controller 950 may transmit and receive signals through the baseband processor 920 and the RF processor 910 or through the backhaul communication unit 930. In addition, the controller 950 may record and read data in and from the storage unit 940. To this end, the controller 950 may include at least one processor. In addition, The controller 950 may include a multi-connection processor 952 for performing a process for operation in a multi-connection mode.
Methods disclosed in the claims and/or methods according to the embodiments described in the specification of the disclosure may be implemented by hardware, software, or a combination of hardware and software.
When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device. The at least one program may include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure.
The programs (software modules or software) may be stored in non-volatile memories including a random access memory and a flash memory, a ROM, an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), DVDs, or other type optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. A plurality of such memories may be included in the electronic device.
In addition, the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, LAN, wide LAN (WLAN), and storage area network (SAN) or a combination thereof. Such a storage device may access the electronic device via an external port. A separate storage device on the communication network may access a portable electronic device.
It is understood that each block 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 may 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 instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may 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 that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
While the disclosure has been illustrated and described with reference to various embodiments of the present disclosure, those skilled in the art will understand that various changes can be made in form and detail without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2023-0044864 | Apr 2023 | KR | national |
