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

Abstract

In a wireless communication system according to one example of the present invention, a method for a terminal (UE) to receive a signal includes receiving a setting related to network energy saving (NES) from a network, and monitoring downlink control information (DCI) based on a discontinuous reception (DRX) cycle in an RRC (radio resource control) idle / inactive state, and a time interval during which the setting related to NES is applied in the RRC idle / inactive state is determined based on an integer multiple of the DRX cycle.

Description

[Technical Field]

[0001] The present invention relates to a wireless communication system, and more particularly to a method and apparatus for transmitting and receiving a wireless signal. [Background technology]

[0002] Wireless communication systems have been widely deployed to provide various communication services such as voice and data. Generally, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention [Problem to be solved by the invention]

[0003] SUMMARY OF THE INVENTION The present invention provides a method and apparatus for efficiently transmitting and receiving radio signals.

[0004] Other technical problems can be derived from the embodiments disclosed in the detailed description. [Means for solving the problem]

[0005] In a wireless communication system according to an aspect of the present invention, a method for a terminal (UE) receiving a signal includes receiving a network energy saving (NES) configuration from a network, and monitoring downlink control information (DCI) based on a discontinuous reception (DRX) cycle in an RRC (radio resource control) idle / inactive state. A time period during which the NES configuration is applied in the RRC idle / inactive state is determined based on an integer multiple of the DRX cycle.

[0006] The length of the time period in which the NES setting is applied is an integer multiple of the length of the DRX cycle.

[0007] The DCI is a DCI for paging, and the DRX cycle is a period during which the terminal monitors paging occasions (POs).

[0008] The size of the integer multiple of the DRX cycle is determined based on signaling from the network.

[0009] The start of the time period during which the NES-related settings are applied is determined based on the paging occasion (PO) monitored by the terminal.

[0010] The time interval to which the NES setting is applied is set based on a discontinuous pattern in the time domain.

[0011] The DCI includes information on operations related to the NES that the UE performs in an RRC idle / inactive state. The UE receives a paging early indication (PEI) for early indication of whether information on the operations related to the NES is included in the DCI.

[0012] The terminal receives a paging early indication (PEI) for early indication of whether to monitor the DCI. The PEI includes information on the NES operation that the terminal performs in the RRC idle / inactive state.

[0013] In another aspect of the present invention, there is provided a computer-readable recording medium having a program recorded thereon for performing the above-described signal receiving method.

[0014] In another aspect of the present invention, there is provided a terminal that performs the above-described signal receiving method.

[0015] In yet another aspect of the present invention, there is provided a device for controlling a terminal that performs the above-described signal receiving method.

[0016] In accordance with another aspect of the present invention, a method for transmitting a signal by a base station in a wireless communication system includes transmitting a network energy saving (NES)-related configuration and transmitting downlink control information (DCI) to a terminal in an RRC (radio resource control) idle / inactive state based on a discontinuous reception (DRX) cycle, and a time period during which the NES-related configuration is applied to the terminal in the RRC idle / inactive state is determined based on an integer multiple of the DRX cycle.

[0017] In another aspect of the present invention, there is provided a base station that performs the above-described signal transmission method. [Effects of the Invention]

[0018] According to an embodiment of the present invention, signals can be transmitted and received more accurately and efficiently in a wireless communication system.

[0019] Other technical advantages can be derived from the embodiments disclosed in the detailed description. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a diagram illustrating physical channels used in a 3GPP (registered trademark) system, which is an example of a wireless communication system, and a general signal transmission method using these channels. [Figure 2] FIG. 1 is a diagram illustrating the structure of a radio frame. [Figure 3] FIG. 1 illustrates a resource grid of slots. [Figure 4] FIG. 10 is a diagram illustrating an example of mapping physical channels within a slot. [Figure 5] FIG. 1 is a diagram illustrating a transmission and reception process of a PDCCH (Physical Downlink Control Channel). [Figure 6] 1 is a diagram illustrating a PDSCH reception and ACK / NACK transmission process. [Figure 7] FIG. 1 illustrates a PUSCH transmission process. [Figure 8] FIG. 10 is a diagram for explaining operations related to DRX. [Figure 9] FIG. 10 is a diagram for explaining operations related to DRX. [Figure 10] FIG. 10 is a diagram for explaining operations related to DRX. [Figure 11] FIG. 1 is a diagram for explaining a WUS. [Figure 12] A diagram to explain the operation of a terminal regarding NES in an RRC idle / inactive state. [Figure 13] 1 is a diagram illustrating signal transmission and reception in a network system according to an embodiment of the present invention. [Figure 14] FIG. 2 is a diagram illustrating signal reception by a terminal according to an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram illustrating signal transmission from a base station according to an embodiment of the present invention. [Figure 16] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 17] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 18] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. [Figure 19] 1 is a diagram illustrating a communication system 1 and wireless devices applicable to the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0021] The following technologies can be used for various wireless access systems, such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, LTE-A (Advanced) is an evolved version of 3GPP LTE, and 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0022] As more communication devices require larger communication capacities, there is an emerging need for improved mobile broadband communication compared to existing RATs (Radio Access Technologies). Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime, anywhere, is one of the important issues to consider in next-generation communications. Furthermore, communication system designs that take into account reliability- and latency-sensitive services / terminals are being discussed. Thus, the introduction of next-generation RATs that take into account eMBB (enhanced Mobile Broadband Communication), massive MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed. In one embodiment of the present invention, for convenience, the relevant technologies are referred to as NR (New radio or New RAT).

[0023] For clarity of explanation, the description will be focused on 3GPP NR, but the technical idea of the present invention is not limited thereto.

[0024] For background, terms, definitions, abbreviations, etc. relevant to this invention, the following documents may be referenced (Incorporated by Reference):

[0025] 3GPP LTE

[0026] - 38.211: Physical channels and modulation

[0027] - 38.212: Multiplexing and channel coding

[0028] - 38.213: Physical layer procedures for control

[0029] - 38.214: Physical layer procedures for data

[0030] - 38.215: Physical layer measurements

[0031] - 38.300: NR and NG-RAN Overall Description

[0032] - 38.304: User Equipment (UE) procedures in idle mode and in RRC Inactive state

[0033] - 38.321Medium Access Control (MAC) protocol specification

[0034] - 38.331: Radio Resource Control (RRC) protocol specification

[0035] - 37.213: Introduction of channel access procedures to unlicensed spectrum for NR-based access

[0036] - 36.355: LTE Positioning Protocol

[0037] - 37.355: LTE Positioning Protocol

[0038] Terms and Abbreviations

[0039] - 5GC: 5G Core Network

[0040] - 5GS: 5G System

[0041] - AP: Access Point

[0042] - CID: Cell ID

[0043] - E-CID: Enhanced Cell ID

[0044] - PRS: Positioning Reference Signal

[0045] - RRM: Radio Resource Management

[0046] - TP: Transmission Point

[0047] - TRP: Transmission and Reception Point

[0048] - UE: User Equipment

[0049] - SSB: Synchronization Signal Block

[0050] - SFN: System Frame Number

[0051] - SS: Search Space

[0052] - CSS: Common Search Space

[0053] - USS: UE-specific Search Space

[0054] - PDCCH: Physical Downlink Control Channel

[0055] - PDSCH: Physical Downlink Shared Channel;

[0056] - PUCCH: Physical Uplink Control Channel;

[0057] - PUSCH: Physical Uplink Shared Channel;

[0058] - DCI: Downlink Control Information

[0059] - UCI: Uplink Control Information

[0060] - SI: System Information

[0061] - SIB: System Information Block

[0062] - MIB: Master Information Block

[0063] - RRC: Radio Resource Control

[0064] - DRX: Discontinuous Reception

[0065] - RNTI: Radio Network Temporary Identifier

[0066] - CSI: Channel state information

[0067] - PCell: Primary Cell

[0068] - SCell: Secondary Cell

[0069] - PSCell: Primary SCG(Secondary Cell Group) Cell

[0070] - CA: Carrier Aggregation

[0071] - WUS: Wake up Signal

[0072] - PO: Paging Occasion

[0073] - PEI: Paging Early Indication

[0074] - PEI-O: PEI Occasion

[0075] - NES: Network Energy Saving

[0076] - RO: RACH Occasion

[0077] - RAR: Random Access Response

[0078] -SDT: Small Data Transmission

[0079] In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information from the base station via an uplink (UL). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information exchanged.

[0080] FIG. 1 is a diagram illustrating physical channels used in a 3GPP NR system and a typical signal transmission method using these channels.

[0081] A terminal that is powered on from a power-off state or newly enters a cell performs an initial cell search, such as establishing synchronization with a base station, in step S101. To this end, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The terminal establishes synchronization with the base station based on the PSS / SSS and obtains information such as a cell identity. The terminal also obtains broadcast information within the cell based on the PBCH. In addition, the terminal can receive a downlink reference signal (DL RS) during the initial cell search to check the status of the downlink channel.

[0082] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information from the physical downlink control channel in step S102 to obtain more specific system information.

[0083] Thereafter, the terminal performs a random access procedure, such as steps S103 to S106, to complete connection to the base station. To this end, the terminal transmits a preamble over a physical random access channel (PRACH) (S103) and receives a response message for the preamble over a physical downlink control channel (PRACH) and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, the terminal performs a contention resolution procedure, such as transmitting a further physical random access channel (S105) and receiving a physical downlink control channel (PRACH) and a corresponding physical downlink shared channel (S106).

[0084] After performing this procedure, the terminal then receives a physical downlink control channel / physical downlink shared channel (S107) and transmits a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) as a general uplink / downlink signal transmission procedure (S108). The control information transmitted by the terminal to the base station is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted via PUCCH, but when control information and traffic data need to be transmitted simultaneously, it is transmitted via PUSCH. In addition, UCI can be transmitted aperiodically via PUSCH at the request / instruction of the network.

[0085] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. A radio frame has a length of 10 ms and is divided into two 5 ms half-frames (HF). Each half-frame is divided into five 1 ms subframes (SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 symbols. When an extended CP is used, each slot contains 12 symbols.

[0086] Table 1 illustrates that when a general CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS.

[0087] [Table 1]

[0088] *N slot symb :Number of symbols in the slot

[0089] *N frame,u slot : Number of slots in the frame

[0090] *N subframe,u slot : Number of slots in a subframe

[0091] Table 2 illustrates how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS when an extended CP is used.

[0092] [Table 2]

[0093] The frame structure is illustrative only, and the number of subframes, slots, and symbols in a frame can vary.

[0094] In an NR system, OFDM numerology (e.g., SCS) can be configured to be different among multiple cells merged into one terminal. Accordingly, the (absolute time) duration of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) consisting of the same number of symbols can be configured to be different among the merged cells. Here, the symbols include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

[0095] FIG. 3 illustrates a resource grid of a slot. A slot includes multiple symbols in the time domain. For example, in the case of a general CP, one slot includes 14 symbols, while in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP is defined as multiple consecutive physical RBs (PRBs) in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier includes up to N BWPs (e.g., 5 BWPs). Data communication is performed using activated BWPs, and only one BWP can be activated for one UE. Each element in the resource grid is called a resource element (RE), and one complex symbol can be mapped to it.

[0096] FIG. 4 illustrates an example of physical channel mapping within a slot. In an NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel are all included within one slot. For example, the first N symbols in a slot are used to transmit a DL control channel (e.g., PDCCH) (hereinafter referred to as the DL control region), and the last M symbols in the slot are used to transmit a UL control channel (e.g., PUCCH) (hereinafter referred to as the UL control region). N and M are each an integer greater than or equal to 0. A resource region between the DL control region and the UL control region (hereinafter referred to as the data region) is used to transmit DL data (e.g., PDSCH) or UL data (e.g., PUSCH). The GP provides a time gap when the base station and the UE switch from transmission mode to reception mode or from reception mode to transmission mode. Some symbols at the time of DL to UL transition within a subframe can be set as the GP.

[0097] The PDCCH carries Downlink Control Information (DCI). For example, the PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the Paging Channel (PCH), system information on the DL-SCH, resource allocation information for higher layer control messages such as random access responses transmitted on the PDSCH, transmit power control commands, and activation / deactivation of Configured Scheduling (CS). The DCI includes a cyclic redundancy check (CRC), which is masked / scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) depending on the owner or use of the PDCCH. For example, if the PDCCH is for a specific terminal, the CRC is masked with a terminal identifier (e.g., Cell-RNTI, C-RNTI). If the PDCCH is related to paging, the CRC is masked with a Paging-RNTI (P-RNTI). If the PDCCH is related to system information (e.g., System Information Block, SIB), the CRC is masked to a System Information RNTI (SI-RNTI). If the PDCCH is related to a random access response, the CRC is masked to a Random Access RNTI (RA-RNTI).

[0098] FIG. 5 is a diagram illustrating a PDCCH transmission / reception process.

[0099] Referring to FIG. 5, a base station transmits a CORESET (Control Resource Set) configuration to a terminal (S502). A CORESET is defined by a set of REGs (Resource Element Groups) having a predetermined pneumatic system (e.g., SCS, CP length, etc.). A REG is defined by one OFDM symbol and one (P)RB. Multiple CORESETs for one terminal may overlap in the time / frequency domain. A CORESET is configured by system information (e.g., Master Information Block, MIB) or higher layer (e.g., Radio Resource Control, RRC, layer) signaling. For example, configuration information for a predetermined common CORESET (e.g., CORESET#0) is transmitted by an MIB. For example, a PDSCH carrying SIB1 (system information block 1) is scheduled by a specific PDCCH, and CORESET#0 is for transmitting the specific PDCCH. Furthermore, configuration information regarding CORESET#N (e.g., N>0) is transmitted by RRC signaling (e.g., cell-common RRC signaling or UE-specific RRC signaling, etc.). As an example, UE-specific RRC signaling carrying CORESET configuration information includes, but is not limited to, various signaling such as an RRC setup message, an RRC reconfiguration message, and / or BWP configuration information. Specifically, the CORESET configuration includes the following information / fields:

[0100] - controlResourceSetId: Indicates the ID of the CORESET.

[0101] - frequencyDomainResources: Indicates the frequency domain resources of CORESET. It is indicated by a bitmap, and each bit corresponds to an RB group (= 6 (consecutive) RBs). For example, the MSB (Most Significant Bit) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit whose bit value is 1 is assigned to the frequency domain resources of CORESET.

[0102] - duration: indicates the time domain resource of CORESET. It indicates the number of consecutive OFDM symbols that make up CORESET. duration has a value of 1 to 3.

[0103] - cce-REG-MappingType: Indicates the mapping type between CCE (Control Channel Element) and REG. Interleaved and non-interleaved types are supported.

[0104] - interleaverSize: Indicates the interleaver size.

[0105] - pdcch-DMRS-ScramblingID: Indicates the value used for PDCCH DMRS initialization. If pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0106] - precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0107] - reg-BundleSize: Indicates the REG bundle size.

[0108] - tci-PresentInDCI: Indicates whether the TCI (Transmission Configuration Index) field is included in the DL-related DCI.

[0109] - tci-StatesPDCCH-ToAddList: Indicates a subset of the TCI states defined in the PDCCH-Configuration. The TCI states are used to provide the Quasi-Co-Location (QCL) relationship between DL RSs and PDCCH DMRS ports within the RS set (TCI-State).

[0110] The base station also transmits a PDCCH SS (Search Space) configuration to the terminal (S504). The PDCCH SS configuration is transmitted by higher layer signaling (e.g., RRC signaling). For example, RRC signaling includes various signaling such as, but not limited to, an RRC setup message, an RRC reconfiguration message, and / or BWP configuration information. For convenience of explanation, FIG. 5 shows the CORESET configuration and the PDCCH SS configuration being signaled separately, but the present invention is not limited thereto. For example, the CORESET configuration and the PDCCH SS configuration may be transmitted by one message (e.g., one RRC signaling) or may be transmitted by different messages.

[0111] The PDCCH SS configuration includes information about the configuration of the PDCCH SS set. The PDCCH SS set is defined by a set of PDCCH candidates that the terminal monitors (e.g., performs blind detection). One or more SS sets are configured for the terminal. Each SS set is either a USS set or a CSS set. For convenience, the PDCCH SS set will be simply referred to as "SS" or "PDCCH SS" below.

[0112] The PDCCH SS set includes PDCCH candidates. PDCCH candidates indicate the CCEs that the terminal monitors for PDCCH reception / detection. Here, monitoring includes blind decoding (BD) of the PDCCH candidates. One PDCCH (candidate) consists of 1, 2, 4, 8, or 16 CCEs depending on the aggregation level (AL). One CCE consists of 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one COREST configuration. One SS is defined based on one SS configuration, and the SS configuration includes the following information / fields:

[0113] - searchSpaceId: Indicates the ID of the SS.

[0114] - controlResourceSetId: Indicates the CORESET associated with the SS.

[0115] - monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring periodicity period (slot unit) and the PDCCH monitoring period offset (slot unit).

[0116] - monitoringSymbolsWithinSlot: Indicates the first OFDM symbol for PDCCH monitoring within a slot where PDCCH monitoring is configured. It is indicated by a bitmap, and each bit corresponds to each OFDM symbol within the slot. The MSB of the bitmap corresponds to the first OFDM symbol within the slot. The OFDM symbol corresponding to a bit with a bit value of 1 corresponds to the first symbol of CORESET within the slot.

[0117] -nrofCandidates: Indicates the number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5, 6, 8) for each AL={1, 2, 4, 8, 16}.

[0118] -searchSpaceType: Indicates CSS (Common Search Space) or USS (UE-specific search space), and indicates the DCI format used for the corresponding SS type.

[0119] Next, the base station generates a PDCCH and transmits it to the terminal (S506), and the terminal monitors PDCCH candidates in one or more SSs to receive / detect the PDCCH (S508). An opportunity (e.g., time / frequency resource) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities are configured within a slot.

[0120] Table 3 illustrates the characteristics of each SS type.

[0121] [Table 3]

[0122] Table 4 illustrates DCI formats transmitted via the PDCCH.

[0123] [Table 4]

[0124] DCI format 0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format 0_1 is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI formats 0_0 / 0_1 are referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 are referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to convey dynamic slot format information (e.g., dynamic SFI) to a UE, and DCI format 2_1 is used to convey downlink pre-emption information to a UE. DCI format 2_0 and / or DCI format 2_1 are transmitted to terminals in a corresponding group via a group common PDCCH, which is a PDCCH transmitted to terminals defined in one group.

[0125] DCI format 0_0 and DCI format 1_0 are called fallback DCI formats, and DCI format 0_1 and DCI format 1_1 are called non-fallback DCI formats. The fallback DCI format maintains the same DCI size / field configuration regardless of the terminal settings. On the other hand, the non-fallback DCI format has different DCI size / field configuration depending on the terminal settings.

[0126] The mapping type from CCE to REG is set to either a non-interleaved CCE-REG mapping type or an interleaved CCE-REG mapping type.

[0127] - Non-interleaved CCE-REG mapping type (or localized mapping type) (Figure 5): Six REGs for a given CCE constitute one REG bundle, and all REGs for a given CCE are contiguous. One REG bundle corresponds to one CCE.

[0128] - Interleaved CCE-REG mapping type (or distributed mapping type): 2, 3, or 6 REGs for a given CCE constitute one REG bundle, and the REG bundles are interleaved within a CORESET. A REG bundle within a CORESET consisting of 1 to 2 OFDM symbols consists of 2 or 6 REGs, and a REG bundle within a CORESET consisting of 3 OFDM symbols consists of 3 or 6 REGs. The size of the REG bundle is set for each CORESET.

[0129] Figure 6 illustrates a PDSCH reception and ACK / NACK transmission process. Referring to Figure 6, a UE detects a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and indicates a DL allocation-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 include the following information:

[0130] - Frequency domain resource assignment: Indicates the RB set assigned to the PDSCH.

[0131] - Time domain resource assignment: Indicates K0 (e.g., slot offset), the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index) and the length of the PDSCH (e.g., number of OFDM symbols).

[0132] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

[0133] - HARQ process number (4 bits): Indicates the HARQ process ID (Identity) for data (e.g., PDSCH, TB).

[0134] - PUCCH resource indicator (PRI): Indicates the PUCCH resource used for UCI transmission among multiple PUCCH resources in a PUCCH resource set.

[0135] Thereafter, the UE receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and then transmits UCI via the PUCCH in slot #(n1+K1) after finishing receiving the PDSCH in slot #n1 (where n+K0≦n1). Here, the UCI includes a HARQ-ACK response to the PDSCH. For convenience, in FIG. 6, it is assumed that the SCS for the PDSCH and the SCS for the PUCCH are the same and that slot #n1 = slot #n+K0, but the present invention is not limited to this. If the SCSs are different, K1 is indicated / interpreted based on the SCS of the PUCCH.

[0136] If the PDSCH is configured to transmit a maximum of one TB, the HARQ-ACK response consists of 1 bit. If the PDSCH is configured to transmit a maximum of two TBs, the HARQ-ACK response consists of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the transmission time of the HARQ-ACK for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted in slot #(n+K1) includes the HARQ-ACK responses for multiple PDSCHs.

[0137] Whether or not a UE performs spatial bundling for HARQ-ACK responses is configured for each cell group (e.g., RRC / higher layer signaling). For example, spatial bundling is configured individually for each HARQ-ACK response transmitted via a PUCCH and / or a HARQ-ACK response transmitted via a PUSCH.

[0138] Spatial bundling is supported when the maximum number of TBs (or codewords) that can be received at one time (or scheduled by 1 DCI) in a corresponding serving cell is two (or more than two) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). On the other hand, for 2-TB transmission, more than four layers are used, and for 1-TB transmission, up to four layers are used. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling is performed on serving cells in the corresponding cell group that can schedule more than four layers. A UE that wishes to transmit a HARQ-ACK response via spatial bundling in a corresponding serving cell can generate a HARQ-ACK response by performing a bit-wise logical AND operation on A / N bits for multiple TBs.

[0139] For example, assuming that a terminal receives DCI scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, a terminal performing spatial bundling can generate a single A / N bit by logically ANDing the first A / N bit for the first TB and the second A / N bit for the second TB. As a result, if both the first TB and the second TB are ACK, the terminal reports an ACK bit value to the base station, and if both TBs are NACK, the terminal reports a NACK bit value to the base station.

[0140] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by logically ANDing the A / N bit for the 1-TB with a bit value of 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.

[0141] A base station / UE has multiple parallel DL HARQ processes for DL transmission. Multiple parallel HARQ processes enable continuous DL transmission while waiting for HARQ feedback for successful or unsuccessful reception of previous DL transmission. Each HARQ process is associated with a HARQ buffer in the Medium Access Control (MAC) layer. Each DL HARQ process manages state variables related to the number of transmissions of MAC Physical Data Blocks (PDUs) in the buffer, HARQ feedback for MAC PDUs in the buffer, the current redundancy version, etc. Each HARQ process is distinguished by a HARQ process ID.

[0142] 7 illustrates a PUSCH transmission process. Referring to FIG. 7, a UE detects a PDCCH in slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0 and 0_1). DCI formats 0_0 and 0_1 include the following information:

[0143] - Frequency domain resource assignment: Indicates the RB set assigned to the PUSCH.

[0144] - Time domain resource assignment: Indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH within the slot. The starting symbol and length are indicated by the SLIV (Start and Length Indicator Value), or are indicated separately.

[0145] Thereafter, the terminal transmits a PUSCH in slot #(n+K2) according to the scheduling information of slot #n, where the PUSCH includes a UL-SCH TB.

[0146] Paging

[0147] The network (i) approaches UEs in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states using paging messages, and (ii) notifies UEs in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states of system information changes and ETWS / CMAS (Earthquake and Tsunami Warning System / Commercial Mobile Alert System) instructions using short messages. Both paging messages and short messages are transmitted based on the P-RNTI-based PDCCH, but paging messages are transmitted on the Paging Control Channel (PCCH), which is a logical channel, while short messages are transmitted directly via the PDCCH, which is a physical channel. Since the PCCH, which is a logical channel, is mapped to the PDSCH, which is a physical channel, it can be understood that paging messages are scheduled based on the P-RNTI-based PDCCH.

[0148] While in RRC_IDLE, the UE monitors the paging channel for CN (core network)-initiated paging. In RRC_INACTIVE, the UE also monitors the paging channel for RAN (radio access network)-initiated paging. The UE does not need to continuously monitor the paging channel. Paging DRX defines that a UE in RRC_IDLE or RRC_INACTIVE monitors the paging channel only during one PO (Paging Occasion) per DRX cycle. The paging DRX period is configured by the network as follows:

[0149] 1) In the case of CN-initiated paging, the basic period is broadcast by the system information.

[0150] 2) In the case of CN-initiated paging, the UE-specific periodicity is set by NAS signaling.

[0151] 3) For RAN-initiated paging, a UE-specific periodicity is set by RRC signaling.

[0152] Since the UE's POs for CN-initiated and RAN-initiated paging are both based on the same UE ID, the two POs overlap. The number of POs in a DRX cycle is configured by the system information, and the network allocates UEs to POs based on their IDs.

[0153] When in RRC_CONNECTED, the UE monitors the paging channel in each PO signaled in the system information for SI change indication and PWS notification. In the case of Bandwidth Adaptation (BA), a UE in RRC_CONNECTED monitors only the paging channel of an active BWP with a configured common search space.

[0154] In the case of shared spectrum channel access, an additional PDCCH monitoring period is configured in the UE's PO to monitor paging. However, if the UE detects a P-RNTI-based PDCCH transmission in its PO, the UE does not need to monitor the next PDCCH monitoring period in the PO.

[0155] To reduce power consumption, the UE uses Discontinuous Reception (DRX) in the RRC_IDLE and RRC_INACTIVE states. The UE monitors one Paging Occasion (PO) per DRX cycle. A PO is a set of PDCCH monitoring intervals and consists of multiple time slots (e.g., subframes or OFDM symbols) in which paging DCI is transmitted. A Paging Frame (PF) is one radio frame and includes one or more POs or the start of a PO.

[0156] In multi-beam operation, the UE assumes that the same paging message and the same short message are repeated in all transmit beams. The paging message is the same for both RAN-initiated and CN-initiated paging.

[0157] When the UE receives the RAN-initiated paging, it initiates the RRC Connection Resume procedure. If the UE receives the CN-initiated paging in the RRC_INACTIVE state, it transitions to RRC_IDLE and notifies the NAS.

[0158] The PF and PO for paging are determined as follows:

[0159] - Determining SFN for PF:

[0160] (SFN+PF offset ) mod T=(T div N)*(UE_ID mod N)

[0161] - Determining the index (i_s) that indicates the index of the PO:

[0162] i_s=floor(UE_ID / N) mod Ns

[0163] The following parameters are used in the calculation of PF and i_s:

[0164] T: UE DRX period (T is determined by the shortest value among the UE-specific DRX value (if configured by RRC and / or higher layers) and the basic DRX value broadcast in the system information. In the RRC_IDLE state, if a UE-specific DRX is not configured by higher layers, the basic value is applied.)

[0165] - N:T total number of paging frames

[0166] - Ns: Number of POs in PF

[0167] -PF offset :Offset used for PF determination

[0168] - UE_ID:5G-S-TMSI mode 1024

[0169] DRX (Discontinuous Reception)

[0170] (1) RRC_CONNECTED DRX

[0171] FIG. 8 is a diagram for explaining the DRX operation of the terminal.

[0172] A terminal can perform DRX operation while executing the above-described / proposed procedures and / or methods. A terminal configured for DRX can reduce power consumption by discontinuously receiving DL signals. DRX is performed in the RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. DRX in the RRC_IDLE state and RRC_INACTIVE state is used to discontinuously receive paging signals. DRX performed in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0173] Referring to FIG. 8, a DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval during which On Duration is periodically repeated. On Duration indicates a time period during which the UE monitors to receive the PDCCH. When DRX is configured, the UE monitors the PDCCH during On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates an inactivity timer and remains awake. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration expires. Therefore, when DRX is configured, PDCCH monitoring / reception is performed discontinuously in the time domain when performing the above-described / proposed procedures and / or methods. For example, when DRX is configured, in the present invention, PDCCH reception opportunities (e.g., slots having a PDCCH search space) are configured discontinuously according to the DRX configuration. On the other hand, if DRX is not configured, when the above-described / proposed procedures and / or methods are performed, PDCCH monitoring / reception is performed continuously in the time domain. For example, if DRX is not configured, in the present invention, PDCCH reception opportunities (e.g., slots having PDCCH search spaces) are configured continuously. On the other hand, PDCCH monitoring may be restricted in the time interval configured as the measurement gap, regardless of whether DRX is configured.

[0174] Table 5 shows the process of the UE related to DRX (RRC_CONNECTED state). Referring to Table 5, DRX configuration information is received via higher layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by a DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously when performing the procedures and / or methods described / proposed in the present invention.

[0175] [Table 5]

[0176] Here, MAC-CellGroupConfig includes configuration information required to set MAC (Medium Access Control) parameters for a cell group. MAC-CellGroupConfig may also include configuration information related to DRX. For example, MAC-CellGroupConfig includes the following information in the definition of DRX: - Value of drx-OnDurationTimer: defines the length of the start interval of the DRX cycle

[0177] - Value of drx-InactivityTimer: defines the length of the time interval in which the UE is in an awake state after a PDCCH opportunity in which a PDCCH indicating initial UL or DL data is detected.

[0178] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between the reception of a DL initial transmission and the reception of a DL retransmission.

[0179] - Value of drx-HARQ-RTT-TimerDL: Defines the maximum time interval between the reception of a grant for an UL initial transmission and the reception of a grant for an UL retransmission.

[0180] - drx-LongCycleStartOffset: defines the length and start of a DRX cycle

[0181] - drx-ShortCycle(optional): defines the time length of a short DRX cycle

[0182] Here, if any one of the drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is operating, the terminal performs PDCCH monitoring at every PDCCH opportunity while maintaining an active state.

[0183] RRC_IDLE DRX

[0184] In the RRC_IDLE state and the RRC_INACTIVE state, DRX is used to discontinuously receive paging signals. For convenience, DRX performed in the RRC_IDLE (or RRC_INACTIVE) state is referred to as RRC_IDLE DRX.

[0185] Therefore, when DRX is configured, PDCCH monitoring / reception can be performed discontinuously in the time domain when performing the procedures and / or methods described / proposed above.

[0186] FIG. 9 illustrates a DRX cycle for paging.

[0187] Referring to Figure 9, DRX is configured for discontinuous reception of paging signals. A terminal can receive DRX configuration information from a base station via higher layer (e.g., RRC) signaling. The DRX configuration information includes configuration information for a DRX cycle, a DRX offset, and a DRX timer. The terminal alternates between an On duration and a Sleep duration according to the DRX cycle. The terminal operates in a wakeup mode during the On duration and in a sleep mode during the Sleep duration.

[0188] In the wake-up mode, the UE can monitor a PO to receive a paging message. A PO refers to a time resource / duration (e.g., subframe, slot) in which the UE expects to receive a paging message. PO monitoring includes monitoring a PDCCH (or MPDCCH, NPDCCH) scrambled with a P-RNTI (hereinafter referred to as a paging PDCCH) in the PO. A paging message is included in the paging PDCCH or a PDSCH scheduled by the paging PDCCH. One or more POs are included in a paging frame (PF), which is periodically configured based on the UE_ID. Here, the PF corresponds to one radio frame, and the UE_ID is determined based on the IMSI (International Mobile Subscriber Identity) of the UE. If DRX is configured, the UE monitors only one PO per DRX cycle. When the terminal receives a paging message instructing a change of its ID and / or system information in the PO, the terminal may perform a RACH procedure to initialize (or re-establish) a connection with the base station or may receive (or acquire) new system information from the base station. Therefore, when performing the procedures and / or methods described / proposed above, PO monitoring is performed discontinuously in the time domain to perform a RACH to connect with the base station or to receive (or acquire) new system information from the base station.

[0189] FIG. 10 illustrates an extended DRX (eDRX) cycle.

[0190] According to the DRX cycle configuration, the maximum cycle duration may be limited to 2.56 seconds. However, in the case of a terminal that transmits and receives data intermittently, such as an MTC terminal or an NB-IoT terminal, unnecessary power consumption may occur during the DRX cycle. To further reduce the power consumption of the terminal, a method for significantly extending the DRX cycle based on a power saving mode (PSM) and a paging time window or paging transmission window (PTW) has been introduced. The extended DRX cycle is simply referred to as an eDRX cycle. Specifically, paging hyper-frames (PH) are periodically configured based on the UE_ID, and a PTW is defined within the PH. The terminal performs a DRX cycle during the PTW duration, switches to a wake-up mode in its own PO, and can monitor paging signals. One or more DRX cycles (e.g., wake-up mode and sleep mode) shown in FIG. 9 may be included within the PTW duration. The number of DRX cycles within the PTW duration may be configured by the base station via a higher layer (e.g., RRC) signal.

[0191] WUS(Wake-up signal) / PEI(Paging Early Indication)

[0192] LTE Rel-15 NB-IoT and MTC introduce a wake-up signal (WUS) for UE power saving. The WUS is a signal that indicates in advance whether an actual paging transmission exists in the search space for paging purposes at a specific location. When a base station intends to transmit a paging message to a paging occasion (PO) at a specific location, it transmits the WUS to a WUS transmission location associated with the PO. The UE monitors the WUS transmission location associated with the PO at a specific location. If it detects a WUS at the WUS transmission location, it can expect a paging message to be transmitted at the corresponding PO. If it does not detect a WUS at the WUS transmission location, it can perform operations such as not expecting a paging message at the corresponding PO, thereby achieving power saving benefits. LTE Rel-16 NB-IoT and MTC introduce a UE-group WUS to improve the power saving benefits of the Rel-15 WUS. The UE-group WUS has the advantage of reducing unnecessary UE wake-ups by using a WUS transmission location and sequence determined based on the UE's UE-group ID.

[0193] FIG. 11 is a diagram illustrating a WUS in an LTE system. Referring to FIG. 11, in MTC and NB-IoT, a WUS is used to reduce power consumption associated with paging monitoring. The WUS is a physical layer signal that indicates whether a terminal monitors a paging signal (e.g., an MPDCCH / NPDCCH scrambled with a P-RNTI) according to a cell configuration. In a terminal not configured with eDRX (i.e., configured with only DRX), the WUS is associated with one PO (N=1). Conversely, in a terminal configured with eDRX, the WUS is associated with one or more POs (N≧1). If a WUS is detected, the terminal monitors the next N POs associated with the WUS. Conversely, if a WUS is not detected, the terminal maintains sleep mode by omitting PO monitoring until monitoring the next WUS. The terminal receives configuration information for the WUS from the base station and monitors the WUS based on the WUS configuration information. The configuration information for the WUS includes, for example, the maximum WUS duration, the number of consecutive POs associated with the WUS, gap information, etc. The maximum WUS duration indicates the maximum time duration for WUS transmission and is expressed as a ratio to the maximum number of repetitions (e.g., Rmax) associated with the PDCCH (e.g., MPDCCH, NPDCCH). Although a terminal can expect repeated WUS transmissions within the maximum WUS duration, the actual number of WUS transmissions may be less than the maximum number of WUS transmissions within the maximum WUS duration. For example, the number of WUS repetitions is smaller for terminals in good coverage. The resources / opportunities for transmitting WUS within the maximum WUS duration are referred to as WUS resources. A WUS resource is defined by multiple consecutive OFDM symbols and multiple consecutive subcarriers. A WUS resource is defined by multiple consecutive OFDM symbols and multiple consecutive subcarriers within a subframe or slot. For example, a WUS resource is defined by 14 consecutive OFDM symbols and 12 consecutive subcarriers. A device that detects a WUS will not monitor the WUS until the first PO associated with the WUS.If no WUS is detected within the maximum WUS interval, the terminal does not monitor the paging signal in the PO associated with the WUS (or remains in sleep mode).

[0194] In a communication system such as NR, whether a UE should monitor or provide paging DCI in a PO is indicated by a PEI (e.g., a sequence- or DCI-based Paging Early Indication). If the UE successfully detects the PEI, it monitors the paging DCI (and / or the PDSCH carrying the corresponding paging message). If the PEI is not detected, the UE skips monitoring the paging DCI in the PO.

[0195] L1 signaling based Network Energy Saving for idle / inactive UE

[0196] Energy conservation in base stations is an important consideration in wireless communication systems, including 3GPP, because it contributes to building environmentally friendly networks by reducing carbon emissions and reducing carrier operational expenditures (OPEX). In particular, the introduction of 5G communications requires higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Recent studies have shown that base station energy costs could reach as much as 20% of total OPEX. Due to this growing interest in base station energy conservation, research into network energy savings (NES) is being discussed in 3GPP NR release 18.

[0197] Specifically, how to achieve more efficient operation dynamically and / or semi-statically and finer granularity adaptation of transmissions and / or receptions in one or more of network energy saving techniques in time, frequency, spatial, and power domains is discussed, along with potential assistance / feedback from the terminal and potential terminal assistance information.

[0198] In such a situation, the operation of the base station to improve the efficiency of the NES of the base station is defined, and the operation of the terminal taking this into consideration is defined.

[0199] One method for supporting the NES operation is to stop all or part of the signals or channels provided by the base station for a predetermined period. A method in which the base station stops operations related to the uplink reception of the terminal for a predetermined period is also considered. When the base station performs such an NES operation, the terminal needs to accurately understand the transmission and reception assumptions of the received signals and channels. This is necessary to prevent malfunctions that may occur when the terminal assumes a signal / channel that is not transmitted, and to prevent unnecessary power consumption that may occur when the terminal repeats invalid operations.

[0200] In 3GPP NR, a terminal in an RRC idle or inactive state receives information such as paging from a base station and transmits and receives various types of signals and channels to transition to an RRC connected state as necessary. As described above, when a base station performs / supports an NES operation, a terminal in an idle / inactive state needs to recognize the NES operation of the base station and perform an appropriate operation accordingly. In this regard, unlike a terminal in a connected state, the types of signals / channels that a terminal in an idle / inactive state can acquire may be limited, and the setting / instruction information that can be instructed may also be restricted. In addition, since a base station and a terminal in an idle / inactive state do not maintain a connection with each other, in most cases it is difficult to determine the state of a terminal in an idle / inactive state, and feedback from the terminal regarding the transmission and reception of information provided by the base station cannot be expected. Therefore, a method for supporting an NES operation for a terminal in an idle / inactive state needs to be distinguished from a method for supporting an NES operation for a terminal in a connected state.

[0201] In consideration of the above-mentioned problems, we propose a method in which an idle / inactive terminal receives necessary configuration information from a base station performing NES operation and performs related operations. The proposed method has the effect of preventing malfunctions and unnecessary power consumption by allowing the terminal to recognize when the base station stops transmitting specific signals and channels for a predetermined period.

[0202] For convenience, the description will be based on the characteristics and structure of the NR system and NES, but the proposed method can be applied to all wireless communication transmission and reception structures and services without being limited thereto. One or more of the proposed methods may be applied in combination, or may be applied independently without being combined. Terms, symbols, procedures, etc. may be replaced with other terms, symbols, procedures, etc.

[0203] In one embodiment, a method is proposed in which a base station uses L1 signaling that can be received by an idle / inactive terminal to instruct (or provide information to) the terminal on actions related to NES, and the terminal performs actions based on this.

[0204] The information / settings related to the NES referred to in this specification are, for example, information for informing a terminal that a base station temporarily activates / deactivates transmission / reception operations of signals and channels for the purpose of energy saving of the base station, and for the terminal to use this information to expect reception of signals and channels transmitted by the base station or to support an operation of transmitting signals and channels to the base station. A specific example of the information / settings related to the NES includes information such as a cell DRX / DRX pattern, and also includes activation / deactivation and individual detailed operations according to the type of signal and channel, or independently or separately for UL and DL.

[0205] For example, L1 signaling that can be received by a terminal in an idle / inactive state is a PDCCH that transmits DCI format 2_7 (hereinafter referred to as PEI DCI) scrambled with P-RNTI and / or a PDCCH that transmits DCI format 1_0 (hereinafter referred to as paging DCI) scrambled with P-RNTI. Hereinafter, L1 signaling is used to mean signaling that a terminal in an idle / inactive state expects to receive, and is used as a concept that includes a PDCCH that transmits PEI DCI and paging DCI.

[0206] [Proposal 1] NES support by PEI or Paging DCI

[0207] Proposal 1 proposes a method of using PEI DCI or paging DCI as L1 signaling to provide or obtain instructions and configuration information for NES operation.

[0208] Option 1-1. Providing information on NES operation by PEI

[0209] When the PEI DCI is used to provide NES information to an idle / inactive UE, the PEI DCI includes a DCI field (hereinafter referred to as the NES field) containing NES information. To this end, the base station provides configuration information regarding the NES field using a higher layer signal (e.g., an SIB), which the UE can receive. When the NES field is configured on the PEI DCI, at least one of the following options 1-1-x is used as an example of a UE's NES information acquisition procedure based on the NES field.

[0210] (Option 1-1-A) NES field containing a 1-bit indication

[0211] A 1-bit NES field may be configured in the PEI DCI. In this case, the 1-bit information is used to indicate whether or not there is information about the NES in the paging DCI provided after the PEI DCI. For example, if a 1-bit in the PEI DCI indicates 0, the NES information may not be included in the paging DCI. If a 1-bit in the PEI DCI indicates 0, the UE may not need to perform PO monitoring to acquire information about the NES. If a 1-bit in the PEI DCI indicates 1, the UE may monitor the PO, expecting that information about the NES will be provided by the paging DCI. The above-described exemplary 1-bit state representation is merely an example for explanation, and may be defined conversely. The above-described 1-bit information may be an independent field set for the NES, or may be a field used by the base station to indicate to the UE that a paging DCI without scheduling a paging message is to be transmitted. The proposed method is advantageous in terms of payload overhead of the PEI DCI because it can indicate to the UE whether or not it is necessary to acquire information about the NES by adding only one bit to the PEI DCI.

[0212] (Option 1-1-B) Providing information using a multi-bit NES field

[0213] The PEI DCI can be configured with an NES field consisting of multiple bits. In this case, the UE can obtain operations and related information related to the NES that can be performed in an idle / inactive state through the NES field on the PEI DCI. In this case, when the UE obtains information about the NES through the NES field on the PEI DCI, the UE can be configured not to perform PO monitoring to obtain information about the NES, regardless of whether an NES operation is specified. In addition, even if information about the NES cannot be obtained through the NES field, the UE can be configured not to monitor the PO to obtain information about the NES. In the case of a UE that monitors the PEI, the proposed method is advantageous in terms of power saving of the UE because it can obtain information about the NES through the PEI, eliminating unnecessary PO monitoring.

[0214] (Option 1-1-C) Providing partial information using a multi-bit NES field

[0215] The PEI DCI may have an NES field consisting of multiple bits, and the NES field may include part of the information about the NES. In this case, the UE may obtain part of the information related to the NES that can be performed in an idle / inactive state through the NES field on the PEI DCI, and may be configured to monitor the PO to obtain the remaining part as needed. The paging DCI on the PO may provide information about the NES, including information not provided in the PEI DCI. As a specific example, the following detailed method may be considered.

[0216] In one detailed method, when one of multiple NES operation candidates is selected and an NES operation is performed, the NES field on the PEI DCI may be limited to select only some of the candidates, and the remaining candidates or all of the candidates may be selectable in the paging DCI. This is an advantageous method for saving the payload overhead of the PEI DCI by not providing an NES operation that is not frequently used in the PEI DCI.

[0217] As another detailed method, when the types of information on the NES are subdivided, only some of the types may be provided in the NES field on the PEI DCI, and the remaining types or all of the types may be provided in the paging DCI. This means that useful (or required) information on the NES varies depending on the services or capabilities supported by the UE, and if there is information on the NES that is essential, has relatively high priority, or is commonly used regardless of capabilities or services, such information may be provided by the PEI DCI, and the UE may obtain the remaining information by the paging DCI as needed, thereby saving the payload overhead of the PEI DCI.

[0218] As a specific method, if the terminal acquires information about the NES through the PEI DCI and is instructed by the acquired information that no operation related to the NES is to be performed, the terminal may be configured not to perform PO monitoring only to acquire information about the NES. On the other hand, if the terminal acquires information about the NES through the PEI DCI and is instructed by the acquired information that an operation related to the NES is to be performed, the terminal may be configured to select PO monitoring as necessary.

[0219] The method of providing information about the NES using the PEI DCI has an advantageous effect in terms of power saving for terminals with PEI capabilities, since the terminal monitoring the PEI can set / instruct NES operation without generating a separate transmission / reception operation to transmit and receive information.

[0220] Option 1-2. Providing information related to NES operation via paging DCI

[0221] When a paging DCI is used to provide NES information for an idle / inactive UE, the paging DCI may include a DCI field (hereinafter referred to as the NES field) containing NES information. To this end, the base station provides configuration information regarding the NES field using a higher layer signal (e.g., an SIB), and the UE may receive this information. The NES field is configured on the paging DCI, and the UE's NES information acquisition procedure based on this can select and use one of the following options 1-2-x.

[0222] (Option 1-2-A) Configure the NES information field on the shot message field

[0223] A method of providing information about the NES using a short message field on the paging DCI is used. The proposed method is used when the short message indicator field indicates a state of '10' (i.e., only a short message exists in the DCI) or a state of '11' (i.e., scheduling information for both paging and short messages exists in the DCI). In this case, the terminal can obtain information about the NES operation from a bit on the short message field defined by the standard and indicated via higher layer signaling.

[0224] If the proposed method indicates that the shot message indicator field is in the "01" state (i.e., only paging scheduling information is present in the DCI), the entire shot message field can be used to provide and obtain information related to NES operation.

[0225] (Option 1-2-B) Configure the NES information field using bits other than the shot message field and the shot message indicator field.

[0226] A method of providing information about the NES by utilizing a bit other than the shot message field or the shot message indicator field on the paging DCI is used. The proposed method is used when the shot message indicator field indicates a state of '01' (i.e., only paging scheduling information exists in the DCI) or a state of '11' (i.e., scheduling information for both paging and shot messages exists in the DCI). As a specific method, a reserved bit that is not used in the paging DCI field is used, and the base station can obtain information about the NES operation from the bit indicated through higher layer signaling.

[0227] If the proposed method is used when the shot message indicator field indicates the "10" state (i.e., only a shot message exists in the DCI), the method of providing information related to the NES can be determined differently from when the shot message indicator field indicates other states, by changing the position and number of bits used. For example, all bits except the shot message field and the shot message indicator field can be used to provide and obtain information related to the NES operation.

[0228] (Option 1-2-C) Providing information about the NES using the shot message indicator "00"

[0229] When the shot message indicator field on the paging DCI indicates '00', a method of providing information about the NES by utilizing all or some of the other paging DCI bits except for the shot message indicator field is used. This is intended to provide information about the NES by utilizing more bits without affecting legacy terminals, considering that, based on the current Rel-17 NR standard, the state in which the shot message indicator field is '00' is defined as reserved and is not utilized when this state is indicated.

[0230] As in Proposal 2, the method of providing information regarding NES using paging DCI can set / instruct NES operation regardless of the terminal's capabilities without generating a separate transmission / reception operation for the terminal to send and receive information, thereby achieving advantageous effects in terms of versatility and terminal power saving.

[0231] [Proposal 2] Determining the section where NES mode is applied

[0232] Proposal 2 proposes a method for determining and applying an interval in which the NES mode is applied (hereinafter referred to as the NES mode interval) when the NES mode is applied using L1 signaling. Here, the NES mode refers to a state in which the base station and the terminal perform transmission and reception of signals and channels that can be expected in an idle / inactive state based on information about the NES.

[0233] The proposed method for determining the NES mode interval may be defined so as to be commonly applied to all signals and channels that can be controlled in NES mode when the terminal is in an idle / inactive state, or may be defined so that individual settings are applied to each signal and channel.

[0234] The specific method of Proposal 2 can use one or a combination of two or more of the following methods.

[0235] Determining NES mode interval based on paging DRX cycle size

[0236] A method is used in which a time interval in which the NES mode is applied (NES mode interval) is determined based on the size of a paging DRX cycle. Specifically, the length of the NES mode interval is set to a multiple of the paging DRX cycle. The paging DRX cycle refers to a period in which the UE monitors a PO in an idle / inactive state. Specifically, the paging DRX cycle may be a cell-common paging DRX cycle set by the SIB. Even if a UE-specific paging DRX cycle is set for the UE, the cell-common paging DRX cycle may be used instead of the UE-specific paging DRX cycle. This is to set the same NES mode interval for UEs expecting the NES mode from the same base station. For example, referring to FIG. 12, a DRX cycle is periodically repeated, and the UE can monitor a PO during the On-duration of the DRX cycle. The UE can monitor paging DCI via a PDCCH whose CRC is scrambled with P-RNTI for a PO related to itself (e.g., calculated by a UE ID-based module) among the POs on the On-duration. The time period during which the UE performs NES-related operations in the RRC idle / inactive state corresponds to the length of N DRX cycles. As will be described later, the start of the time period during which the UE performs NES-related operations is determined based on a specific PO (e.g., a PO associated with the UE).

[0237] The magnitude of the multiple used to determine the length of the NES mode period is determined by the base station and is provided to the terminal via a higher layer signal (e.g., SIB). In addition, the start position of the NES mode period is determined based on the PO (or PEI-O) that the terminal can expect to monitor based on its own UE ID. As an example, if the length of the NES mode period is set to N paging DRX cycles, the terminal determines the length of the N paging DRX cycles as the NES mode period based on the PO (or PEI-O) in which the NES mode operation is instructed, or based on the PO associated with the PEI-O in which the NES mode operation is instructed (i.e., the PO in which whether to monitor is instructed by the PEI of the corresponding position), and performs the set / instructed operation.

[0238] As a specific method for determining the start position of the NES mode period by applying the proposed method, a method can be considered in which the terminal determines the start point of the NES mode period by selecting a PO (or PEI-O) of another terminal (or its own) that satisfies a predetermined condition, rather than the position of a PO (or PEI-O) selectable by its own UE ID. In this case, the predetermined condition is determined as the position of a PO that is periodically selected according to a predetermined rule from among multiple POs operated from the base station's perspective. This provides an advantageous effect in that the base station can provide a common NES mode period to all terminals.

[0239] The proposed method sets the NES mode interval based on the positions of the PO and PEI-O and the paging DRX cycle, so that parameters related to paging can be reused, which is advantageous in terms of signaling overhead and can provide a favorable structure for NES operations related to PEI and paging.

[0240] Determining NES mode intervals based on SFN index

[0241] A method using an SFN index is used to set the NES mode period. Specifically, the start point of the NES mode period is determined by the base station and calculated using an offset and period provided via a higher layer signal (e.g., SIB). The length of the NES mode period is determined by the base station and a value provided via a higher layer signal (e.g., SIB). In this case, the length may be set using a transmission / reception unit in the time domain (e.g., frame, subframe, slot, and symbol) or a time unit such as ms. Alternatively, the length of the NES mode period may be determined by applying a multiple based on a unit length used for other purposes, such as a paging DRX cycle. Specifically, the start point of the NES mode period may be set to be the SFN index of a position adjacent to the L1 signaling instructing the UE to perform the NES operation (e.g., the closest position among the previous positions or the closest position that will appear next), among SFN indices selectable based on the offset and period provided by the base station. As an example, after a terminal is instructed to perform an NES operation via L1 signaling, if the SFN index that meets the condition for the start position of the NES mode section is #n frame, and the length of the NES mode section that the terminal acquires via an upper layer signal is N frames, the terminal assumes the range from #n frame to #n+N-1 frame as the NES mode section and performs the associated NES operation.

[0242] As a specific example, a method may be considered in which a modification period boundary and the length of a modification period are used as criteria for determining an NES mode period. Here, the modification period boundary and the modification period are concepts used to determine a criterion / unit period for SIB update, and are defined as described in the 3GPP TS 38.331 standard. In this case, the UE may assume that the NES mode period starts from the first modification period boundary that appears after the NES operation is indicated through L1 signaling. The length of the NES mode period applied at this time may be determined to operate at a length that is a multiple of the modification period indicated by the base station through higher layer signaling. This provides an opportunity for a UE with NES capability to switch NES operation through a simplified procedure by dynamic indication through L1 signaling, and also provides an advantageous structure for a UE without NES capability to obtain an effect similar to that of an NES mode period through an SIB update procedure.

[0243] The proposed method has the advantage of providing a structure of an NES mode interval suitable for providing a common NES mode interval to all terminals to which an NES mode interval is instructed from the same base station, and also has the advantage of providing flexibility to the base station in that the base station can select the start position and length of the required NES mode interval with relatively low constraints.

[0244] Apply the pattern of the NES mode section

[0245] A structure is used in which the NES mode intervals indicated through L1 signaling occur in a discontinuous pattern. For example, the pattern has a structure in which NES mode intervals and non-NES mode intervals intersect. In this case, the non-NES mode interval may refer to an interval in which the configured / instructed NES operation is not performed, or may refer to an interval in which relaxed NES operation (e.g., some NES operations are deactivated and other NES operations are maintained) is performed. In this case, the pattern may be predetermined by a standard or may be configured by the base station and provided to the terminal via higher layer signaling (e.g., SIB). For example, the pattern includes information on the structure in which the NES mode intervals and non-NES mode intervals are arranged and the length of each interval. In addition, a structure is used in which the base station determines the length of the interval in which the pattern is maintained, and the terminal receives this length via higher layer signaling (e.g., SIB).

[0246] The proposed method has the advantage that if periodic activation / deactivation of the NES mode section is required to smoothly support the transmission and reception operations of the terminal, or if a structure that periodically provides a relaxed NES mode section is required, this can be supported without incurring any additional signaling overhead beyond the initial L1 signaling indication.

[0247] [Proposal 3] Signals / Channels to which NES mode operation applies

[0248] Proposal 3 proposes transmission / reception operations for signals and channels that can be assumed and performed by a UE in an idle / inactive state when the NES mode is applied using L1 signaling. In the NES mode period, the UE is specified to perform NES operations for signals and channels for PEI, paging, SSB, SIB, random access, measurement, positioning, SDT, etc., for which transmission / reception and related operations can be performed in the idle / inactive state. One of the NES operations that can be performed is that the signals and channels are specified to not expect or perform transmission / reception assumptions and related operations while the NES mode period is maintained. Another NES operation is that the signals and channels are specified to perform transmission / reception assumptions and related operations only at a predetermined period or position while the NES mode period is maintained (e.g., at a position that occurs relatively intermittently compared to a non-NES mode period).

[0249] Proposal 3 includes NES operations that are applied in a distinctive manner, taking into consideration the characteristics of each signal and channel and the conditions required for related operations. The distinctive NES operations can be considered in the following detailed manner for each signal and channel.

[0250] PEI and / or Paging

[0251] The UE can monitor the PEI-O and PO to receive PEI and paging information. In the NES mode section, it is advantageous for the base station not to transmit PEI or paging in terms of energy conservation. In consideration of this, the UE can be configured not to monitor the PEI and paging in the section to which the NES mode section is applied. For example, if the NES operation is indicated by L1 signaling, the UE can be configured not to expect (not to receive) PDCCH monitoring operation for receiving PEI and paging at the positions of the PEI-O and PO included in the NES mode section.

[0252] The proposed method is a method of specifying that the UE does not expect to acquire information for a specific purpose through the PEI or PO. As an example, the UE is specified to expect that paging message scheduling will not be performed in the NES mode section. In this case, the UE may be allowed to monitor the PEI-O or PO as needed (or according to the configuration), but may not expect paging message scheduling and therefore may not perform any related operations. As an example of the related operation, buffering for PDSCH decoding may be considered, which may provide an advantageous effect in preventing UE power consumption caused by buffering the PDSCH while the UE is decoding the PDCCH. As another example of the specific purpose, the UE is specified to expect that short message information such as a SIB change indication and / or an ETWS / CMAS notification will not be provided in the NES mode section. On the other hand, if allowed (or required), the UE may be allowed to acquire information related to the NES through the PEI and paging in a limited manner. This is intended to allow monitoring of PEI and paging so that the base station can more dynamically control NES operation when information about the NES is provided by PEI or paging, and to prevent malfunction of the terminal due to possible PEI and paging PDCCH missing.

[0253] As proposed above, all or part of the specific purpose information that is specified as not expected can be set to be temporarily allowed if certain conditions are met within the NES mode period. As an example, the information is provided by the base station at the PEI-O or PO position that is periodically allowed within the NES mode period, and set to be expected by the UE. This is to prevent a situation in which the transmission and reception of latency-sensitive information such as a paging message or ETS / CMAS notification is significantly delayed when the length of the NES mode period is long, and can also be used to provide information regarding a change in SIB before the UE ends the NES mode period.

[0254] SSB

[0255] In the NES mode section, it is advantageous for the base station not to transmit SSBs in terms of energy conservation. Taking this into consideration, the base station can be configured not to transmit SSBs in the NES mode section, and the terminal can be configured not to perform operations related to SSB reception.

[0256] Meanwhile, since a terminal performs RRM measurements on a cell in an idle / inactive state and receives SSBs for purposes such as setting a beam index for transmission and reception of other signals / channels, AGC, and time / frequency tracking, whether to assume transmission and reception of SSBs is important for terminal operation. In consideration of this, the base station may be configured to transmit periodic SSBs that are advantageous from the perspective of energy saving in the NES mode section. A specific method for setting / instructing and transmitting the periodic SSBs that are advantageous from the perspective of energy saving can be selected and used from one of the following options 3-1-x.

[0257] (Option 3-1-A) Skipping SSB Instructions

[0258] In the proposed method, the terminal can assume basic SSB transmission and reception at the SSB position set in the SIB. To achieve further energy saving effects, the base station can provide the terminal with indication information for SSB skipping to be applied in the NES mode section. In this case, the terminal determines not to assume transmission and reception for some of the SSB transmission positions set in the SIB based on the indication information. For example, the SSB skipping indication information is provided in the form of a pattern indicated by a bitmap structure and / or in the form of indication information for a skipping region that occurs periodically.

[0259] (Option 3-1-B) Conditional SSB Transmission

[0260] In the proposed method, the UE can assume basic SSB transmission and reception at the SSB position set within the NES mode section. In addition to the basic SSB transmission and reception position, if certain conditions are met, the base station can determine whether to perform temporary SSB transmission, and the UE can be configured to expect SSB reception based on this assumption. To this end, the base station can determine whether or not temporary SSB is supported and its structure, and provide this configuration information to the UE via an upper layer signal (e.g., SIB), and the UE can expect and perform related operations upon receiving this.

[0261] In this case, the predetermined condition includes activation of temporary SSB transmission by another signal or channel. For example, the UE receives activation information of temporary SSB transmission by a PEI DCI or a paging DCI, and thereby checks whether a temporary SSB has occurred.

[0262] Alternatively, the predetermined condition may be defined such that, if the terminal can expect / assume transmission / reception of a specific signal or channel, it expects transmission / reception of a temporary SSB at a position determined based on the transmission position of the signal or channel. As an example, the specific signal or channel that the terminal can expect / assume may include the position of a PEI-O or PO that the terminal is allowed to monitor within the NES mode section, or may include the monitoring position of a PDCCH and a PDSCH for transmission / reception of an SIB. As another example, when the terminal performs a RACH, the position of the RO may be used as a reference position, and when the terminal transmits a PRACH, it may be defined such that it expects transmission / reception of a temporary SSB based on the position of an RAR window associated therewith.

[0263] Although the proposed method is described based on the transmission and reception of temporary SSBs, those skilled in the art will understand that similar gains can be achieved when applying the concept of the proposed method to other types of reference signals available to the terminal (e.g., CSI / RS or TRS).

[0264] (Option 3-1-C) Additional SSB Instructions

[0265] In the proposed method, the UE can assume basic SSB transmission and reception at the SSB position set within the NES mode section. In addition to the basic SSB transmission and reception positions, the base station can be configured to transmit additional SSBs at positions outside the NES mode section, and the UE can be configured to expect SSB reception based on this assumption. In this case, the additional SSBs can be configured to have a periodically occurring structure, with their application determined based on whether the NES mode section is applied, without a separate enabling / disabling procedure. To this end, the base station can determine the periodic position and structure of the additional SSBs and provide corresponding configuration information to the UE via an upper layer signal (e.g., SIB), and the UE can expect to perform related operations upon receiving this information.

[0266] The proposed method provides the effect of NES (network energy saving) by setting the position of the SSB transmitted in the NES mode section to the period of the basic SSB transmission and transmitting additional SSBs at other positions. At the same time, for terminals without NES capability, the same SSB period is always assumed regardless of whether the NES mode section is in place, providing a structure that is advantageous for stable operation of general terminals.

[0267] Although the proposed method is described based on the transmission and reception of additional SSBs, those skilled in the art will understand that similar gains can be achieved when applying the concept of the proposed method to other types of reference signals available to the terminal (e.g., CSI / RS or TRS).

[0268] SIB

[0269] In the NES mode section, it is advantageous for the base station not to transmit SIBs in terms of energy conservation. Taking this into consideration, the base station can be configured not to transmit SIBs in the NES mode section, and the terminal can be configured not to perform operations related to SSB reception.

[0270] In the proposed method, a method of applying different operations in the NES mode section depending on the type of information provided by the SIB may be considered. As a specific method, the base station may be configured to support periodic SIB transmission for some SIBs regardless of the presence or absence of the NES mode section. For example, SIB1 corresponds to this, and / or SIBs providing information about the NES are included. In this case, the periodicity applied to the periodic SIB transmission may be configured to be different between the NES mode section and the non-NES mode section. The base station may provide corresponding configuration information via higher layer signaling, and the UE may receive this and perform related operations. In another proposed specific method, whether periodic SIB transmission is supported for some SIBs other than the above may be determined depending on the presence or absence of the NES mode section. As an example, if a periodic SIB transmission structure is set for a specific SIB-X, transmission and reception between the base station and the terminal taking this into consideration can be allowed only in non-NES mode sections, and in NES mode sections, the periodic SIB transmission structure is not assumed, and only transmission and reception of the on-demand SIB transmission structure can be expected.

[0271] And / or, the proposed method uses a method in which the SIB transmission time is determined according to the SSB transmission pattern in the NES mode section. In this case, the SIB transmission / reception assumption method used in the non-NES mode section and the SIB transmission / reception assumption method used in the NES mode section are different from each other, and this may be a method depending on the SSB transmission period or pattern. As an example, the section in which SIB transmission / reception is allowed in the NES mode section may be determined by setting a window for SIB transmission / reception based on SSB transmission / reception sections that occur periodically (or according to a pattern) in the NES mode section, and the terminal may assume SIB reception only within the corresponding section.

[0272] Random Access

[0273] In terms of energy conservation, it is advantageous for the base station not to perform a random access (hereinafter referred to as RA) procedure in the NES mode section. In consideration of this, the base station may be configured not to support the RA procedure in the NES mode section, and the terminal may be configured not to perform transmission / reception operations related to RA.

[0274] Meanwhile, it is preferable that the RA procedure be allowed even in the NES mode section, considering the case where an operation or information that the terminal wishes to request from the base station occurs, or where data to be transmitted occurs. In consideration of this, a method of restrictively allowing RA-related procedures in the NES mode section can be considered. For example, the generation period of ROs and RARs that the terminal can assume to use in the NES mode section can be set to be relatively long, and / or the number of ROs and corresponding RARs that can be used can be set to be relatively reduced based on a predetermined time point determined as the period.

[0275] And / or, in the proposed method, a method is used in which the allowable time point of RO is determined according to the SSB transmission pattern in the NES mode section. In this case, the configuration method of RO used in the non-NES mode section and the configuration method of RO used in the NES mode section are different from each other, and may be a method depending on the SSB transmission period or pattern. As an example, the time period in which PRACH transmission and reception using RO in the NES mode section is allowed may be determined by setting a window for RACH based on SSB transmission and reception periods that occur periodically (or according to a pattern) in the NES mode section, and the UE may assume the availability of RACH operation using RO only within that period.

[0276] measurement request

[0277] A UE needs to periodically perform intra-cell / inter-cell RRM measurements in an idle / inactive state. To do this, the UE needs to periodically receive SSBs and perform measurements on them. Meanwhile, for a base station capable of NES operation, the SSB transmission period may change depending on whether or not the base station operates in NES mode. In consideration of this, this specification proposes a method in which the UE issues different measurement requirements depending on whether or not the base station supports or applies the NES mode. A specific method can be selected from one of the following options 3-2-x.

[0278] (Option 3-2-A) Setting measurement requests taking into account SSB transmission patterns

[0279] The UE can perform intra / inter-cell measurement operations taking into account the SSB transmission pattern determined depending on the presence or absence of the NES mode section. For example, if the measurement period required in the non-NES mode section is shorter than the SSB period used in the NES mode section, the UE is configured to perform measurements based on the SSB period of the NES mode section. This is to prevent unnecessary switching of the camped-on cell by adjusting the RRM measurement period based on the SSB that the UE can measure.

[0280] Alternatively, if the measurement period required in the non-NES mode section is longer than the SSB period used in the NES mode section, the UE may be configured to maintain the same measurement period regardless of whether the NES mode section is applied. This allows the UE to perform RRM measurement at a normal period when RRM measurement is possible, and can provide an advantageous effect in quickly finding a camped-on cell suitable for transmission and reception.

[0281] (Option 3-2-A) Setting measurement requests taking paging cycles into account

[0282] The UE can perform intra / inter-cell measurement operations taking into account the paging DRX cycle determined depending on whether or not there is an NES mode section. For example, if the paging DRX cycle required in the non-NES mode section is different from the paging DRX cycle used in the NES mode section, the UE determines to perform measurement based on the period of the paging DRX cycle of each section. This is expected to enable the base station to provide SSB in accordance with the period of PO and PEI-O to support smooth paging and PEI operations even in the NES mode section, and is also a suitable method for aligning the UE's PEI / paging monitoring operation with the RRM measurement operation to prevent unnecessary power consumption.

[0283] TRS availability indication

[0284] The 3GPP Rel-17 NR standard introduces a procedure for setting and transmitting / receiving a TRS that an idle / inactive UE can expect to receive, in consideration of power saving. From the perspective of a base station, not transmitting this TRS in the NES mode section is advantageous in terms of energy saving. Meanwhile, considering that the TRS is used for time / frequency resynchronization and tracking of an idle / inactive UE, the UE needs to clearly understand how the TRS can assume transmission / reception in the NES mode section. Furthermore, when PDCCH / PDSCH transmission / reception occurs in the NES mode section, TRS transmission / reception is advantageous for an idle / inactive UE. In consideration of this, this specification proposes a TRS setting method and structure that allows a UE to assume transmission / reception in the NES mode section.

[0285] As a specific method, if an NES mode period starts within a TRS available period (i.e., a period designated so that an idle / inactive UE can assume transmission and reception of the promised TRS) designated in a non-NES mode period, the UE can be set so that the designated TRS available period cannot be assumed any more from the boundary where the NES mode period starts. This is advantageous considering that when the base station starts the NES mode, assuming that PDCCH and PDSCH do not occur or occur with a low probability, the efficiency of the base station's TRS transmission energy relative to the UE's power saving effect is significantly reduced.

[0286] As another specific method, a method is considered in which a TRS transmission pattern in an NES mode period is applied differently from the TRS transmission method in a non-NES mode period. As an example, in a non-NES mode period, the transmission / reception structure of the TRS available period for an idle / inactive UE designed in Rel-17 NR may be assumed, while a new TRS available period may be set and used in an NES mode period. In this case, the method for activating the new TRS available period may be defined similarly to the TRS activation method for an idle / inactive UE defined in the conventional Rel-17 NR. When activated, it is expected that the TRS available period will occur in a discontinuous structure only if predetermined conditions are met. As a specific example, the new TRS available period is defined in the form of a specific window determined based on the PEI-O or PO of the UE. The proposed method allows the base station to control whether to send or receive TRS via L1 signaling, thereby ensuring flexibility in the base station's TRS control, while at the same time ensuring limited TRS transmission and reception in sections where the terminal primarily requires TRS, thereby improving the energy-saving effects of the base station and the terminal.

[0287] 13 is a diagram for explaining signal transmission and reception in a network system according to an embodiment. For understanding of FIG. 13, the explanations of Proposals 1 to 3 above can be referred to.

[0288] Referring to FIG. 13, the UE receives NES-related configuration from the network (1005). The NES-related configuration includes configuration information for UE operation required when NES is performed. The NES-related configuration is received via higher layer signaling. For example, the NES-related configuration is information for informing the UE that the base station temporarily activates / deactivates transmission / reception operations of signals and channels for energy saving of the base station, and for the UE to use this information to expect reception of signals and channels transmitted by the base station or to support an operation of transmitting signals and channels to the base station. Specific examples of the NES-related configuration include information such as a cell DRX / DRX pattern, and also include activation / deactivation and individual detailed operations according to the types of signals and channels, or independent or separated for each of UL and DL. For example, the NES-related configuration includes information on the configuration of the NES field included in L1 signaling (e.g., DCI). For example, as shown in Figure 12, a time period during which an operation related to the NES is performed corresponds to N DRX cycles (N is a positive integer), and the value of N is included in the configuration related to the NES received through higher layer signaling. The higher layer signaling for the configuration related to the NES includes, but is not limited to, an SIB or dedicated RRC signaling for the UE in a connected state.

[0289] The UE monitors a PEI (paging early indication) (1015) and receives a PEI from the network (1010). On the other hand, if a PEI is not configured, steps 1010 and 1015 related to the PEI can be omitted. The PEI is used to early indicate whether the UE monitors paging DCI in the PO. For example, the PEI includes information on NES-related operations that the UE performs in an RRC idle / inactive state. The PEI can also early indicate whether information on NES-related operations is included in the paging DCI.

[0290] The UE monitors the paging DCI in the PO on the DRX on duration 1025 and receives the paging DCI 1020. For example, the paging DCI includes information on an operation related to the NES that the UE performs in the RRC idle / inactive state.

[0291] FIG. 14 is a diagram illustrating signal reception by a terminal according to an embodiment.

[0292] Referring to Figure 14, the terminal receives a network energy saving (NES) setting from the network (A05). The NES setting is, for example, information that notifies the terminal that the base station temporarily activates / deactivates transmission / reception of signals and channels for energy saving of the base station, and is used by the terminal to expect reception of signals and channels transmitted by the base station or to support transmission of signals and channels to the base station. Specific examples of the NES setting include information such as a cell DRX / DRX pattern, and also include activation / deactivation and individual detailed operations according to the type of signal and channel, or independent or divided for each of UL and DL.

[0293] The terminal monitors downlink control information (DCI) based on a discontinuous reception (DRX) cycle in an RRC (radio resource control) idle / inactive state (A10).

[0294] The time period during which the NES-related settings are applied in the RRC idle / inactive state is determined based on an integer multiple of the DRX cycle.

[0295] The length of the time period in which the NES setting is applied is an integer multiple of the length of the DRX cycle.

[0296] The DCI is a DCI for paging, and the DRX cycle is a period during which the terminal monitors paging occasions (POs).

[0297] The size of the integer multiple of the DRX cycle is determined based on signaling from the network.

[0298] The start of the time period during which the NES-related settings are applied is determined based on the paging occasion (PO) monitored by the terminal.

[0299] The time interval to which the NES setting is applied is set based on a discontinuous pattern in the time domain.

[0300] The DCI includes information on operations related to the NES that the UE performs in an RRC idle / inactive state. The UE receives a paging early indication (PEI) for early indication of whether information on operations related to the NES is included in the DCI.

[0301] The terminal receives a paging early indication (PEI) for early indication of whether to monitor the DCI. The PEI includes information on the NES operation that the terminal performs in the RRC idle / inactive state.

[0302] FIG. 15 is a diagram illustrating signal transmission from a base station according to an embodiment.

[0303] Referring to Figure 15, the base station transmits a setting related to network energy saving (NES) (B05). The NES setting, for example, is information for informing the terminal that the base station will temporarily activate / deactivate transmission / reception operations of signals and channels in order to save energy at the base station, and for the terminal to use this information to expect reception of signals and channels transmitted by the base station or to support an operation of transmitting signals and channels to the base station. A specific example of the NES setting includes information such as a cell DRX / DRX pattern, and also includes activation / deactivation and individual detailed operations according to the type of signal and channel, or independent or divided for each of UL and DL.

[0304] The base station transmits downlink control information (DCI) to a terminal in an RRC (radio resource control) idle / inactive state based on a discontinuous reception (DRX) cycle (B10).

[0305] The time period during which the NES-related configuration is applied to the UE in the RRC idle / inactive state is determined based on an integer multiple of the DRX cycle.

[0306] The length of the time period in which the NES setting is applied is an integer multiple of the length of the DRX cycle.

[0307] The DCI is a DCI for paging, and the DRX cycle is a period during which the terminal monitors paging occasions (POs).

[0308] The base station signals the size of an integer multiple of the DRX cycle to the terminal.

[0309] The start of the time period during which the NES-related settings are applied to the terminal is determined based on the paging occasion (PO) monitored by the terminal.

[0310] The time interval to which the NES setting is applied is set based on a discontinuous pattern in the time domain.

[0311] The DCI includes information on NES-related operations that the UE performs in an RRC idle / inactive state. The base station transmits a paging early indication (PEI) to the UE to indicate whether the DCI includes information on the NES-related operations.

[0312] The base station transmits a paging early indication (PEI) to the terminal to instruct whether to monitor the DCI early. The PEI includes information on the NES operation to be performed by the terminal in the RRC idle / inactive state.

[0313] FIG. 16 illustrates a communication system 1 to which the present invention is applied.

[0314] Referring to FIG. 16, a communication system 1 applicable to the present invention includes wireless devices, base stations, and a network. Here, the wireless devices refer to devices that communicate using wireless connection technologies (e.g., 5G NR, LTE), and are also referred to as communication / wireless / 5G devices. The wireless devices include, but are not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an XR (eXtended Reality) device 100c, a handheld device 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI server / device 400. For example, the vehicles include vehicles equipped with wireless communication capabilities, autonomous vehicles, vehicles capable of vehicle-to-vehicle communication, and the like. Here, the vehicles include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices include Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Mobile devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0315] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. The wireless devices 100a to 100f are equipped with AI (Artificial Intelligence) technology, and are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). IoT devices (e.g., sensors) can also communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0316] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f and the base stations 200, and between the base stations 200. Here, the wireless communication / connections are performed using various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication), and communication between base stations 150c (e.g., relay, Integrated Access Backhaul (IAB)) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and the base stations, and the base stations, can transmit / receive wireless signals to / from each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, according to various proposals of the present invention, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed.

[0317] FIG. 17 illustrates a wireless device to which the present invention can be applied.

[0318] 17, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

[0319] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 102 processes information in the memory 104 to generate first information / signals and then transmits a wireless signal including the first information / signals via the transceiver 106. The processor 102 also receives a wireless signal including second information / signals via the transceiver 106 and then stores information obtained from signal processing of the second information / signals in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In one embodiment of the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0320] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In one embodiment of the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0321] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. The one or more processors 102, 202 generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed herein and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and derive the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein.

[0322] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. For example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein may be included in the one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts disclosed in this specification may be embodied using firmware or software in the form of code, instructions and / or sets of instructions.

[0323] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0324] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or flowcharts herein to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or flowcharts herein from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and are configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein via the one or more antennas 108, 208. In this specification, one or more antennas may refer to multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing by one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102, 202, from baseband signals to RF band signals. For this purpose, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.

[0325] 18 shows another example of a wireless device to which the present invention is applied. The wireless device may be implemented in various forms depending on the use case / service (see FIG. 16).

[0326] 18, wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 17 and are composed of various elements, components, units / sections, and / or modules. For example, the wireless devices 100 and 200 include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102 and 202 and / or one or more memories 104 and 204 in FIG. 17. For example, the transceiver 114 includes one or more transceivers 106 and 206 and / or one or more antennas 108 and 208 in FIG. 17. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. The control unit 120 also transmits the information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from an external device (e.g., another communication device) via the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0327] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Wireless devices may be embodied in the form of, but are not limited to, a robot ( FIG. 17, 100a ), a vehicle ( FIG. 17, 100b-1, 100b-2 ), an XR device ( FIG. 17, 100c ), a mobile device ( FIG. 17, 100d ), a home appliance ( FIG. 17, 100e ), an IoT device ( FIG. 17, 100f ), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or financial device), a security device, a climate / environment device, an AI server / device ( FIG. 17, 400 ), a base station ( FIG. 17, 200 ), a network node, etc. Wireless devices may be mobile or fixed depending on the use case / service.

[0328] In FIG. 18, the various elements, components, units / sections and / or modules within the wireless devices 100, 200 are all connected to each other by wired interfaces, or at least some are connected wirelessly by a communication section 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (e.g., 130, 140) are connected wirelessly via the communication unit 110. Furthermore, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 is configured with a RAM (Random Access Memory), a DRAM (Dynamic RAM), a ROM (Read Only Memory), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0329] 19 is a diagram illustrating a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be embodied as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, etc.

[0330] 19, a vehicle or autonomous vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 is configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 17, respectively.

[0331] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to move on the ground. The driving unit 140a includes an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d implements technology for maintaining a lane while driving, technology for automatically adjusting speed such as adaptive cruise control, technology for automatically driving along a predetermined route, technology for automatically setting a route and driving when a destination is set, etc.

[0332] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a driving plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., adjusting speed / direction) so that the vehicle or autonomous vehicle 100 moves along the autonomous driving route according to the driving plan. The communication unit 110 non-periodically obtains the latest traffic information data from an external server during autonomous driving and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server can predict traffic information data using AI technology based on information collected from the vehicle or autonomous vehicle and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0333] The above-described embodiments are combinations of the elements and features of the present invention in a predetermined form. Each element or feature should be considered optional unless otherwise explicitly stated. Each element or feature may be implemented without being combined with other elements or features. It is also possible to combine some elements and / or features to form an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some elements or features of any embodiment may be included in other embodiments, or may be replaced with corresponding elements or features of other embodiments. It is obvious that claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as new claims by amendment after filing.

[0334] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the characteristics of the present invention. Therefore, the above detailed description should not be construed as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0335] The present invention can be used in a terminal, a base station or other equipment of a wireless mobile communication system.

Claims

1. A method performed by UE (user equipment), Receiving configuration information from the network, including information about time intervals related to random access, and This includes receiving DCI (downlink control information) related to paging, Based on the reception of the DCI, the time interval begins with the first frame, The first frame relates to the boundary of a specific SI (system information) change period, and the specific SI change period is determined based on the timing of the DCI reception.

2. The DCI is received based on a DRX (discontinuous reception) cycle in an idle / inactive state of RRC (radio resource control), The method according to claim 1, wherein the length of the time interval is an integer multiple of the length of the DRX cycle.

3. The method according to claim 1, wherein, based on the fact that a PRACH (physical random access channel) opportunity falls within the time interval, the PRACH opportunity is available for PRACH transmission.

4. The method according to claim 1, wherein the configuration information is received from the network via higher-level signaling.

5. The method according to claim 1, wherein the information relating to the time interval includes the length of the time interval.

6. The method according to claim 1, wherein the DCI's CRC (cyclic redundancy check) is scrambled by a P-RNTI (paging-radio network temporary identifier).

7. The method according to claim 1, wherein the setting information relates to network energy saving.

8. The method according to claim 3, wherein the availability of the PRACH opportunity within the time interval is determined based on the DCI.

9. The method according to claim 1, wherein the specific SI change period is the SI change period among the periodic SI change periods that is closest to the reception timing of the DCI.

10. A non-temporary computer-readable recording medium storing a program for performing the method described in claim 1.

11. Memory configured to store instruction words, and A processor configured to perform an operation by executing the aforementioned instruction, The aforementioned operation is, Receiving configuration information from the network, including information about time intervals related to random access, and This includes receiving DCI (downlink control information) related to paging, Based on the reception of the DCI, the time interval begins with the first frame, The first frame relates to the boundary of a specific SI (system information) change period, and the specific SI change period is determined based on the timing of the DCI reception in the device.

12. The system further comprises a transceiver that transmits or receives wireless signals under the control of the aforementioned processor, The device according to claim 11, wherein the device is a UE (user equipment) that operates in a wireless communication system.

13. The device according to claim 11, wherein the device is an ASIC (application-specific integrated circuit) or a digital signal processing device configured to control UE (user equipment) operating in a wireless communication system.

14. A method performed by a BS (base station), Send configuration information including information about time intervals related to random access, and This includes transmitting DCI (downlink control information) related to paging, Based on the transmission of the DCI, the time interval begins with the first frame, The first frame relates to the boundary of a specific SI (system information) change period, and the specific SI change period is determined based on the transmission timing of the DCI.

15. The method according to claim 14, wherein, based on the fact that a PRACH (physical random access channel) opportunity falls within the time interval, the PRACH opportunity is available for PRACH reception.

16. The method according to claim 14, wherein the setting information is transmitted via higher-level signaling.

17. The method according to claim 14, wherein the information relating to the time interval includes the length of the time interval.

18. The method according to claim 14, wherein the DCI's CRC (cyclic redundancy check) is scrambled by a P-RNTI (paging-radio network temporary identifier).

19. The method of claim 15, wherein the availability of the PRACH opportunity within the time interval is indicated by the DCI.

20. The method according to claim 14, wherein the specific SI change period is the SI change period among the periodic SI change periods that is closest to the transmission timing of the DCI.

Images