Method and device for transmitting and receiving wireless signals in wireless communication system

Abstract

Disclosed are a method performed by a UE and a device therefor in a wireless communication system according to various embodiments. Disclosed are a device and a method therefor, the device: receiving configuration information for configuring at least one resource related to a system information block1 (SIB1) request; transmitting a first signal for requesting SIB1 transmission for a first cell in the at least one resource; receiving a response signal to the first signal; and monitoring an SIB1 for the first cell.

Description

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

[0001] This specification relates to a wireless communication system, and more specifically, to a method and device for transmitting and receiving wireless signals.

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). Examples of multiple access systems include 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).

[0003] As more and more communication devices demand ever-increasing communication traffic, the need for next-generation 5G systems, which offer enhanced wireless broadband communication capabilities over existing LTE systems, is growing. This next-generation 5G system, known as NewRAT, differentiates communication scenarios into Enhanced Mobile Broadband (eMBB), Ultra-reliability and low-latency communication (URLLC), and Massive Machine-Type Communications (mMTC).

[0004] Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate; URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability (e.g., V2X, Emergency Service, and Remote Control); and mMTC is a next-generation mobile communication scenario with characteristics such as Low Cost, Low Energy, Short Packet, and Massive Connectivity (e.g., IoT).

[0005] The technical problem to be achieved by the present invention is to provide a more accurate and efficient signal transmission and reception method and a device therefor.

[0006] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0007] A method by a UE (User Equipment) according to one aspect includes the steps of: receiving configuration information for setting at least one resource related to a SIB1 (System Information Block1) request; transmitting a first signal requesting SIB1 transmission to a first cell from the at least one resource; receiving a response signal to the first signal; and monitoring SIB1 for the first cell; wherein the monitoring of SIB1 can be performed based on a reception time of the response signal and a specific time.

[0008] Alternatively, the monitoring of the SIB1 is characterized in that it is performed based on the passage of a predetermined time from the time of receiving the response signal.

[0009] Alternatively, the at least one resource is at least one RO (Random Access Occasion), and the first signal is a PRACH (Physical Random Access Channel) transmitted based on the at least one RO.

[0010] Alternatively, the response signal is characterized in that it is a Random Access Response (RAR) that responds to the reception of the PRACH.

[0011] Alternatively, the setting information is characterized in that it is acquired through a SSB (Synchronization signal block) received from a second cell different from the first cell.

[0012] Alternatively, the first cell is a non-anchor cell, the second cell is an anchor cell, the first signal is transmitted to the first cell rather than the second cell, and the response signal and the SIB1 are received from the first cell.

[0013] Alternatively, the monitoring of the SIB1 is characterized in that it is performed only in a beam direction corresponding to the beam direction used for transmitting the first signal.

[0014] Alternatively, the first cell is characterized in that it is a SIB1-less cell that transmits the SIB1 only when the first signal is received.

[0015] Alternatively, the setting information further includes list information for at least one cell that requires a request for transmission of the SIB1, and the first cell is characterized in that it is a cell having the highest reception strength of a downlink signal among the at least one cell.

[0016] Alternatively, the setting information is characterized in that it further includes mapping information between an index for the at least one cell and the at least one resource.

[0017] A storage medium storing programs for performing the above-described method by the UE according to another aspect may be provided.

[0018] A UE may be provided that performs the above-described method according to another aspect.

[0019] A processing device may be provided for controlling a UE to perform the above-described method according to another aspect.

[0020] A method performed by a base station according to another aspect may include the steps of: receiving a first signal requesting transmission of System Information Block 1 (SIB1) from a UE (User Equipment) in at least one resource related to a SIB1 request; transmitting a response signal to the first signal; and transmitting the SIB1 based on a transmission time point and a specific time of the response signal.

[0021] According to various embodiments, signals can be transmitted or received more accurately and efficiently in a wireless communication system.

[0022] Alternatively, power usage of the network and / or terminals in a wireless communication system can be more efficiently controlled.

[0023] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0024] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0025] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0026] Figure 2 illustrates the structure of a radio frame.

[0027] Figure 3 illustrates a resource grid of slots.

[0028] Figure 4 illustrates an example of physical channels being mapped within a slot.

[0029] FIG. 5 and FIG. 6 are diagrams for explaining Idle Mode DRX (Discontinuous Reception) operation.

[0030] FIGS. 7 to 9 are diagrams for explaining DRX operation in RRC (Radio Resource Control) connected mode.

[0031] Figure 10 is a diagram for explaining a method of monitoring DCI format 2_6.

[0032] FIG. 11 is a diagram for explaining a method for performing communication based on cell DRX / DTX between a base station and a terminal.

[0033] Figure 12 is a diagram for explaining transmission of On-demand SIB1.

[0034] Figure 13 is a drawing for explaining a method of performing On-demand SIB1.

[0035] Figure 14 is a diagram for explaining a method for a terminal to receive SIB1 from a cell that operates on-demand SIB1.

[0036] FIG. 15 is a diagram for explaining a method for transmitting a requested SIB1 from a cell operating on-demand SIB1.

[0037] Figures 16 to 19 illustrate a communication system (1) and a wireless device applicable to the present invention.

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

[0039] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing RAT (Radio Access Technology) is emerging. Furthermore, massive MTC (Machine Type Communications), which connects multiple devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communication. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced Mobile BroadBand Communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. In one embodiment of the present invention, for convenience, the corresponding technology is referred to as NR (New Radio or New RAT).

[0040] The term 'base station' used in this specification may be replaced with terms such as fixed station, Node B, gNode B (gNB), Access Point (AP), cell, or transmission and reception point (TRP). The term 'relay node' may be replaced with terms such as Relay Node (RN) or Relay Station. In addition, the term 'terminal' may be replaced with terms such as User Equipment (UE), Mobile Station (MS), Mobile Subscriber Station (MSS), or Subscriber Station (SS).

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

[0042] The following documents may be referenced for background information, definitions of terms, abbreviations, etc. related to the present invention (Incorporated by Reference).

[0043] - 38.211: Physical channels and modulation

[0044] - 38.212: Multiplexing and channel coding

[0045] - 38.213: Physical layer procedures for control

[0046] - 38.214: Physical layer procedures for data

[0047] - 38.215: Physical layer measurements

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

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

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

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

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

[0053] - 36.355: LTE Positioning Protocol

[0054] - 37.355: LTE Positioning Protocol

[0055] 용어 및 약어

[0056] - 5GC: 5G Core Network

[0057] - 5GS: 5G System

[0058] - NES: network energy saving

[0059] - ES: energy saving

[0060] - SSB: synchronization signal / PBCH block

[0061] - FR: frequency range

[0062] - CC: component carrier

[0063] - NCGI : NR Cell Global Identifier

[0064] - SI: system information

[0065] - PCell: primary cell

[0066] - SCell: secondary cell

[0067] - PDCCH: Physical Downlink Control CHannel

[0068] - PDSCH: Physical Downlink Shared CHannel

[0069] - PUSCH: Physical Uplink Shared CHannel

[0070] - CSI: Channel state information

[0071] - RRM: Radio resource management

[0072] - SCS: Sub-carrier spacing

[0073] - RLM: Radio link monitoring

[0074] - DCI: Downlink Control Information

[0075] - CAP: Channel Access Procedure

[0076] - Ucell: Unlicensed cell

[0077] - TBS: Transport Block Size

[0078] - TDRA: Time Domain Resource Allocation

[0079] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of the entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.)

[0080] - BWP: BandWidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0081] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0082] - REG: Resource element group

[0083] - SFI: Slot Format Indicator (An indicator indicating the symbol level DL / UL direction within a specific slot(s), transmitted through the group common PDCCH.)

[0084] - COT: Channel occupancy time

[0085] - SPS: Semi-persistent scheduling

[0086] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or antenna port(s) of the corresponding RS). In the NR system, four QCL types are defined as follows. 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter} For any DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y) ) can be set as a reference to

[0087] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0088] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0089] - TRP: Transmission and Reception Point

[0090] In a wireless communication system, a terminal receives information from a base station via the downlink (DL) and transmits it to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0091] Figure 1 is a drawing for explaining physical channels used in a 3GPP NR system and a general signal transmission method using them.

[0092] When a terminal is powered on again from a powered-off state or enters a new cell, it performs an initial cell search operation, such as synchronizing with the 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 synchronizes with the base station based on the PSS / SSS and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

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

[0094] Thereafter, the terminal may perform a random access procedure such as steps S103 to S106 to complete connection to the base station. To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S103) and receive a response message to the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, a contention resolution procedure such as transmission of an additional physical random access channel (S105) and reception of a physical downlink control channel and a corresponding physical downlink shared channel (S106) may be performed.

[0095] The terminal that has performed the procedure as described above can then perform the general uplink / downlink signal transmission procedure, such as receiving a physical downlink control channel / physical downlink shared channel (S107) and transmitting a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). The control information that the terminal transmits 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 through PUCCH, but can be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, UCI can be transmitted aperiodically via PUSCH upon request / instruction from the network.

[0096] Figure 2 illustrates the structure of a radio frame. In NR, uplink and downlink transmissions are organized into frames. Each radio frame is 10 ms long and is divided into two 5 ms half-frames (HF). Each half-frame is divided into five 1 ms sub-frames (SF). A sub-frame is divided into one or more slots, and the number of slots within a sub-frame depends on the subcarrier spacing (SCS). Each slot contains 12 or 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 OFDM symbols.

[0097] Table 1 illustrates that when CP is normally used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0098] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

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

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

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

[0102] Table 2 illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

[0103] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0104] The structure of the frame is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be varied.

[0105] In an NR system, OFDM numerology (e.g., SCS) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbol).

[0106] Figure 3 illustrates a resource grid of a slot. A slot includes multiple symbols in the time domain. For example, in the case of a regular CP, one slot includes 14 symbols, but 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 Bandwidth Part (BWP) is defined as multiple consecutive Physical RBs (PRBs) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0107] Figure 4 illustrates an example of mapping physical channels 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 can all be included within a single slot. For example, the first N symbols within a slot can be used to transmit a DL control channel (e.g., PDCCH) (hereinafter, DL control region), and the last M symbols within a slot can be used to transmit a UL control channel (e.g., PUCCH) (hereinafter, UL control region). N and M are each integers greater than or equal to 0. The resource region (hereinafter, data region) between the DL control region and the UL control region can be used to transmit DL data (e.g., PDSCH) or UL data (e.g., PUSCH). GP provides a time gap when a base station and a terminal switch from a transmission mode to a reception mode or from a reception mode to a transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0108] 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 upper layer control messages such as random access responses transmitted on the PDSCH, transmission power control commands, activation / deactivation of Configured Scheduling (CS), etc. 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 usage 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 for paging, the CRC is masked with the Paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., a System Information Block, SIB), the CRC is masked with the System Information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the Random Access-RNTI (RA-RNTI).

[0109] For PDCCH reception, the UE may monitor (e.g., perform blind decoding) a set of PDCCH candidates in a CORESET. The PDCCH candidates represent the CCE(s) that the UE monitors for PDCCH reception / detection. PDCCH monitoring may be performed in one or more CORESETs on an active DL BWP on each activated cell in which PDCCH monitoring is configured. The set of PDCCH candidates that the UE monitors is defined as a PDCCH Search Space (SS) set. The SS set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

[0110] Table 3 illustrates the PDCCH search space.

[0111] Search SpaceTypeRNTIUse CaseType0-PDCCHCommonSI-RNTI on a primary cellBroadcast of System InformationType0A-PDCCHCommonSI-RNTI on a primary cellBroadcast of System InformationType1-PDCCHCommonRA-RNTI or TC-RNTI on a primary cellMsg2, Msg4 in RACHType2-PDCCHCommonP-RNTI on a primary cellPagingSystem Information change notificationType3-PDCCHCommonINT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI or CS-RNTIGroup signalingUE SpecificC-RNTI, MCS-C-RNTI or CS-RNTIUE signaling (eg, PDSCH / PUSCH)

[0112] SS sets can be configured via system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Each DL BWP of a serving cell can have up to S (e.g., 10) SS sets configured. For example, the following parameters / information can be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration can be associated with one or more SS sets.

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

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

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

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

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

[0118] - searchSpaceType: Indicates whether the SS type is CSS or USS.

[0119] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0120] Based on the CORESET / SS set configuration, a UE can monitor PDCCH candidates in one or more SS sets within a slot. An opportunity (e.g., time / frequency resources) for monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities can be configured within a slot.

[0121] PUCCH formatLength in OFDM symbolsNumber of bitsUsageEtc01 - 2≤2HARQ, SRSequence selection14 - 14≤2HARQ, [SR]Sequence modulation21 - 2>2HARQ, CSI, [SR]CP-OFDM34 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(no UE multiplexing)44 - 14>2HARQ, CSI, [SR]DFT-s-OFDM(Pre DFT OCC)

[0122] 1) PUCCH Format 0 (PF0)

[0123] - Supported UCI payload sizes: up to K bits (e.g., K = 2)

[0124] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0125] - Transmission structure: Consists of only UCI signals without DM-RS, and transmits the UCI status by selecting and transmitting one of multiple sequences.

[0126] 2) PUCCH Format 1 (PF1)

[0127] - Supported UCI payload sizes: up to K bits (e.g., K = 2)

[0128] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0129] Transmission Structure: DM-RS and UCI are configured in TDM format on different OFDM symbols, with UCI multiplying a specific sequence with modulation (e.g., QPSK) symbols. Cyclic Shift (CS) / Orthogonal Cover Code (OCC) is applied to both UCI and DM-RS to support CDM between multiple PUCCH resources (following PUCCH Format 1) (within the same RB).

[0130] 3) PUCCH Format 2 (PF2)

[0131] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0132] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0133] - Transmission structure: DMRS and UCI are configured / mapped in FDM form within the same symbol, and are transmitted by applying only IFFT without DFT to the encoded UCI bits.

[0134] 4) PUCCH Format 3 (PF3)

[0135] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0136] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0137] Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format, and transmitted by applying DFT to the corrupted UCI bits. OCC is applied to UCI at the DFT front end, and CS (or IFDM mapping) is applied to DMRS to support multiplexing to multiple terminals.

[0138] 5) PUCCH Format 4 (PF4)

[0139] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0140] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0141] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format, and a structure that transmits without multiplexing between terminals by applying DFT to the encoded UCI bits.

[0142] DRX (Discontinuous Reception) Operation

[0143] The UE uses Discontinuous Reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. When DRX is configured, the UE performs DRX operations according to DRX configuration information.

[0144] A UE operating based on DRX repeatedly turns ON / OFF its reception operation. For example, when DRX is configured, the UE attempts to receive / detect PDCCH (e.g., monitor PDCCH) only during a predetermined time interval (e.g., ON), and does not attempt PDCCH reception during the remaining time (e.g., OFF / Sleep).

[0145] At this time, the time that the terminal must attempt to receive the PDCCH is called On-duration, and On-duration is defined once per DRX cycle. The UE can receive DRX configuration information from a base station (e.g., gNB) through RRC signaling and perform DRX operation by receiving (Long) DRX command MAC CE.

[0146] Meanwhile, DRX configuration information can be included in MAC-CellGroupConfig. IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group including DRX.

[0147] DRX (Discontinuous Reception) refers to an operation mode in which a UE (User Equipment) discontinuously receives / monitors a downlink channel to reduce battery consumption. In other words, a UE configured for DRX can reduce power consumption by discontinuously receiving downlink signals. DRX operation is performed in a DRX cycle, where On Duration represents a time interval that is periodically repeated. DRX includes On Duration and Sleep Duration (or Opportunity for DRX). On Duration represents the time interval during which the UE monitors the PDCCH to receive the PDCCH. DRX can be performed in the RRC (Radio Resource Control)_IDLE State (or mode), RRC_INACTIVE State (or mode), or RRC_CONNECTED State (or mode). In the RRC_IDLE State and RRC_INACTIVE State, DRX is used to discontinuously receive a paging signal.

[0148] - RRC_Idle State: A state in which a wireless connection (RRC connection) is not established between the base station and the terminal.

[0149] - RRC Inactive State: A wireless connection (RRC connection) is established between the base station and the terminal, but the wireless connection is inactive.

[0150] - RRC_Connected state: A wireless connection (RRC connection) is established between the base station and the terminal.

[0151] DRX is basically divided into Idle mode DRX, Connected DRX (C-DRX), and Extended DRX. DRX applied in the RRC IDLE state is called IDLE mode DRX, and DRX applied in the RRC CONNECTED state is called Connected mode DRX (C-DRX).

[0152] eDRX (Extended / enhanced DRX) is a mechanism that can extend the cycle of IDLE mode DRX and C-DRX. Whether eDRX is allowed in IDLE mode DRX can be set based on system information (e.g., SIB1).

[0153] SIB1 may include an eDRX-Allowed parameter. The eDRX-Allowed parameter is a parameter indicating whether IDLE mode extended DRX is allowed.

[0154] (1) IDLE mode DRX

[0155] In IDLE mode, the UE may use DRX to reduce power consumption. A paging opportunity (PO) may be a time interval (e.g., a slot or a subframe) during which a Paging-Radio Network Temporary Identifier (P-RNTI)-based Physical Downlink Control Channel (PDCCH) may be transmitted. The P-RNTI-based PDCCH may address / schedule paging messages. For P-RNTI-based PDCCH transmissions, the PO may indicate the starting subframe for PDCCH repetition.

[0156] A paging frame (PF) is a radio frame that may contain one or more paging opportunities. When DRX is used, the UE may be configured to monitor only one PO per DRX cycle. The PF and / or PO may be determined based on DRX parameters provided via network signaling (e.g., system information).

[0157] Hereinafter, 'PDCCH' may refer to MPDCCH, NPDCCH, and / or general PDCCH. Hereinafter, 'UE' may refer to MTC UE, BL (Bandwidth Reduced Low Complexity) / CE (Coverage Enhanced) UE, NB-IoT UE, RedCap (RedCap) UE, general UE, and / or IAB-MT (Mobile Termination).

[0158] FIG. 5 is a flowchart illustrating an example of a method for performing IDLE mode DRX operation.

[0159] The UE receives IDLE mode DRX configuration information from the base station through upper layer signaling (e.g., system information) (S110).

[0160] Additionally, the UE determines a Paging Frame (PF) and a Paging Occasion (PO) for monitoring the PDCCH in the paging DRX cycle based on the IDLE mode DRX configuration information (S120). In this case, the DRX cycle includes an On Duration and a Sleep Duration (or an Opportunity for DRX).

[0161] Additionally, the UE monitors the PDCCH in the PO of the determined PF (S130). Meanwhile, the UE monitors only one time interval (PO) per paging DRX cycle. For example, the time interval may be a slot or a subframe.

[0162] Additionally, if the UE receives a PDCCH (more precisely, a CRC of the PDCCH) scrambled by the P-RNTI during the On Duration (i.e., if paging is detected), the UE can transition to connected mode and transmit and receive data with the base station.

[0163] Figure 6 is a diagram showing an example of IDLE mode DRX operation.

[0164] Referring to Fig. 6, when there is traffic (data) directed to a UE in the RRC_Idle state (hereinafter referred to as 'Idle state'), paging occurs toward the UE.

[0165] Therefore, the UE wakes up every (paging) DRX cycle and monitors the PDCCH.

[0166] If paging is present, the UE transitions to the Connected state and receives data. Otherwise, the UE may enter sleep mode again.

[0167] (2) Connected mode DRX (C-DRX)

[0168] C-DRX is DRX applied in RRC Connected State. The DRX cycle of C-DRX can be configured as a short DRX cycle and / or a long DRX cycle. The short DRX cycle is optional.

[0169] When C-DRX is configured, the UE performs PDCCH monitoring during the On Duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates (or runs) the Inactive Timer and remains in the Awake State. On the other hand, if no PDCCH is successfully detected during PDCCH monitoring, the UE enters the Sleep State after the On Duration ends.

[0170] When C-DRX is configured, PDCCH reception Occasions (e.g., slots having PDCCH search spaces / candidates) may be configured discontinuously based on the C-DRX configuration. On the other hand, when C-DRX is not configured, PDCCH reception Occasions (e.g., slots having PDCCH search spaces / candidates) may be configured continuously according to the PDCCH search space configuration. Meanwhile, PDCCH monitoring may be limited to a time interval set as a Measurement Gap regardless of the C-DRX configuration.

[0171] Figure 7 is a flowchart illustrating an example of a method for performing a C-DRX operation.

[0172] The UE receives RRC signaling (e.g., MAC-MainConfig IE) containing DRX configuration information from the base station (S310). The DRX configuration information may include the following information.

[0173] - on-duration: The period (duration) during which the UE waits to receive a PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE stays awake and starts the drx-inactivity timer.

[0174] - onDurationTimer: The period (Duration) at which the DRX Cycle starts; for example, it can mean the time period that should be continuously monitored from the start of the DRX cycle, and can be expressed in ms.

[0175] - drx-InactivityTimer: Duration after the PDCCH Occasion corresponding to the PDCCH indicating a new UL or DL ​​transmission for the MAC entity; for example, it may be a time period in milliseconds after the UE decodes a PDCCH with scheduling information. That is, the duration during which the UE waits to successfully decode another PDCCH after the last PDCCH decoded. If no other PDCCH is detected within this period, the UE transitions to Sleep mode.

[0176] The UE restarts the drx-inactivity timer after successful decoding of the PDCCH for initial transmission only, not for retransmission.

[0177] - drx-RetransmissionTimer: For DL, the maximum duration until a DL retransmission is received; For UL, the maximum duration until an acknowledgment for a UL retransmission is received. For example, for UL, it is the number of slots for the BWP (Bandwidth part) in which the TB (Transport Block) to be retransmitted is transmitted, and for DL, it is the number of slots for the BWP (Bandwidth part) in which the TB (Transport Block) to be retransmitted is received.

[0178] - longDRX-Cycle: On Duration occurrence cycle (Period)

[0179] - drxStartOffset: Subframe number where the DRX cycle starts

[0180] - drxShortCycleTimer: The period (Duration) during which the UE must follow the short DRX cycle;

[0181] - shortDRX-Cycle: DRX Cycle that runs for the number of drxShortCycleTimer when Drx-InactivityTimer ends

[0182] - drx-SlotOffset: Delay before drx-onDurationTimer starts; can be expressed in ms, or in multiples of 1 / 32ms.

[0183] - Active Time: The total period (Duration) that the UE monitors the PDCCH, including (a) the “On-duration” of the DRX cycle, (b) the time that the UE performs continuous reception while the drx-inactivity timer has not expired, and (c) the time that the UE performs continuous reception while waiting for a retransmission opportunity.

[0184] More specifically, when the DRX Cycle is configured, the Active Time for the serving cell of the DRX group includes the following times:

[0185] - (a) drx-onDurationTimer or (b) drx-InactivityTimer configured for the DRX group. or

[0186] - (c) drx-RetransmissionTimerDL or drx-RetransmissionTimerUL for all serving cells in the DRX group. or

[0187] - (d) ra-ContentionResolutionTimer or msgB-ResponseWindow. or

[0188] - (e) a pending section in which a Scheduling Request is transmitted via PUCCH, or

[0189] - (f) If a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is not received after successfully receiving a Random Access Response (RAR) for a random access preamble not selected by the MAC entity during contention-based random access.

[0190] Additionally, when DRX 'ON' is set through the DRX command of MAC CE (command element) (S320), the UE monitors the PDCCH during the ON Duration of the DRX cycle based on the DRX setting (S330).

[0191] Figure 8 is a diagram showing an example of C-DRX operation.

[0192] Referring to FIG. 8, when the UE receives scheduling information (e.g., DL Assignment or UL Grant) in the RRC_Connected State (hereinafter referred to as Connected State), the UE executes the DRX Inactivity Timer and the RRC Inactivity Timer.

[0193] DRX mode starts after the DRX Inactivity Timer expires. The UE wakes up from the DRX Cycle and monitors the PDCCH for a predetermined period of time (on duration timer).

[0194] In this case, when Short DRX is set, when the UE starts DRX mode, the UE first starts a Short DRX Cycle, and after the Short DRX Cycle ends, the UE starts a Long DRX Cycle. At this time, the Long DRX Cycle is a multiple of the Short DRX Cycle. That is, the UE wakes up more frequently in the Short DRX Cycle. After the RRC Inactivity Timer expires, the UE transitions to the Idle state and performs Idle mode DRX operation.

[0195] Figure 9 illustrates a DRX Cycle. The C-DRX operation was introduced to save power for the UE. If the UE does not receive a PDCCH within the on-duration defined for each DRX cycle, it enters sleep mode and does not perform transmission / reception until the next DRX cycle.

[0196] On the other hand, if the UE receives a PDCCH in On-duration, the Active time may be maintained (or increased) based on the operation of the inactivity timer, retransmission timer, etc. If no additional data is received within the Active time, the UE may perform a sleep operation until the next DRX operation.

[0197] In NR, a wake up signal (WUS) is introduced to obtain additional power saving gains from the existing C-DRX operation. The WUS may be used to indicate whether the UE should perform PDCCH monitoring during the on-duration of each DRX cycle (or multiple DRX cycles). If the UE does not detect a WUS in a designated or indicated WUS occasion, the UE may remain in sleep mode without performing PDCCH monitoring for one or more DRX cycles associated with the WUS.

[0198] (3) Wake Up Signal (DCI Format 2_6)

[0199] Figure 10 is a diagram for explaining a method of monitoring DCI format 2_6.

[0200] In the power saving technology of the Rel-16 NR system, when a DRX operation is performed, whether or not each DRX cycle wakes up can be notified to the terminal through DCI format 2_6.

[0201] Referring to Figure 10, the monitoring occasion for DCI format 2_6 can be determined by the ps-Offset indicated by the network and the Time Gap reported by the terminal. The Time Gap reported by the terminal can be interpreted as a preparation period required for operations after the terminal wakes up.

[0202] Referring to FIG. 10, the network can instruct the terminal to configure a search space (SS) set capable of monitoring DCI format 2_6. The SS set configuration can instruct the terminal to monitor DCI format 2_6 through consecutive slots of a duration length at intervals of a monitoring periodicity.

[0203] In the DRX configuration, the monitoring window for monitoring DCI format 2_6 is determined by the start point of the DRX cycle (e.g., the point where the on-duration timer starts) and the ps-Offset configured by the network. In addition, PDCCH monitoring may not be required in the Time Gap section reported by the UE. Finally, the SS Set monitoring occasion where the UE performs actual monitoring can be determined as the first Full Duration (i.e., Actual Monitoring Occasions in FIG. 10) within the monitoring window.

[0204] By detecting DCI format 2_6 in the monitoring window set based on ps-Offset, the base station can instruct the terminal whether to wake up or not in the next DRX cycle.

[0205] NES (network energy saving)

[0206] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing the operational expenditure (OPEX) of telecommunications operators. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached up to 20% of total OPEX. This heightened interest in base station energy conservation has led to the approval of a new study item, "Study on Network Energy Savings," in certain scenarios (e.g., 3GPP NR Release 18).

[0207] Specifically, in order to improve the energy saving capability of the base station from the perspective of transmission and reception, the following enhancement techniques are being considered.

[0208] - A method for more fine-tuning transmission and / or reception dynamically and / or semi-statically in one or more of the network energy-saving techniques in the time, frequency, space and power domains, and for achieving more efficient operation through potential UE assistance / feedback and potential UE assistance information.

[0209] The base station identifies the NES solution(s) to be applied. The NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. The NES solution(s) to be applied may be adaptively selected or predefined based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.). The base station that identified the NES solution(s) performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal. Thereafter, the base station performs operations for the NES. At this time, the base station may perform the operations for the NES based on the previously performed signaling. That is, based on the system information, configuration information, and control information transmitted through signaling, the base station can turn on / off transmission and reception of a specific signal, turn on / off elements in the spatial domain, or adjust resources for transmission and reception of a measurement signal.

[0210] Examples of possible NES solutions include:

[0211] - Intra-system energy saving solution: A RAN node can request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or can perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0212] - Inter-system energy saving solution: NG-RAN nodes that own capacity booster cells can autonomously transition those cells to an inactive state.

[0213] - SSB-less SCell solution: If SSB or SMTC (SSB-based RRM measurement timing configuration) configuration is not provided for the SCell, the UE can obtain timing reference and AGC source from another serving cell. In FR1 or FR2, the base station can configure intra-band CA or inter-band CA including the SCell without SSB transmission, in which case the SSB / SIB transmission can be triggered by the WUS (wake up signal) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station can stay in the sleep state for a longer time.

[0214] - Cell DTX / DRX solution: In order to reduce the downlink transmission / uplink reception activity time of the base station, a periodic cell DTX / DRX pattern (e.g., active and inactive periods) can be commonly set for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern can be set and activated separately, and up to two cell DTX / DRX patterns can be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for SPS opportunities or monitoring PDCCH can be stopped during the cell DTX inactivity period. When cell DRX is set and activated, at least one of transmission on CG resources or SR transmission can be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 group common signaling.

[0215] -- Parameters such as active duration and cycle can be configured for cell DTX / DRX. Active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and cycle specifies the periodic repetition of the active duration and inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle are common. If the base station recognizes an emergency call or a public safety-related service (e.g., MPS or MCS), the network can release or deactivate the cell DTX / DRX configuration so as not to affect the service. In addition, at least some overlap is required between the active duration of the connected mode DRX of the UE and the active duration of the cell DTX / DRX. For example, the connected mode DRX cycle of the UE may be a multiple of the cell DTX / DRX cycle, or vice versa.

[0216] - Conditional handover (CHO) solution: A CHO procedure performed in a way that the execution of the handover is determined by the UE is used while the NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE can use an NES-specific CHO event to initiate CHO for a candidate cell, and the reception of a DCI that activates the CHO condition(s) set by the NES event indication can be applied as an additional triggering condition for this.

[0217] - Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmit power adaptation, the UE may be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, the CSI configuration, measurement, and / or reporting behavior may be affected.

[0218] FIG. 11 is a diagram for explaining a method for performing communication based on cell DRX / DTX between a base station and a terminal.

[0219] To enable base stations to operate in sleep mode for relatively long periods of time without frequent wake-ups, base station DTX / DRX has been proposed for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission under low system load conditions by configuring cell DTX and setting the on-duration of C-DRX of terminals within the active period of the cell DTX.

[0220] Referring to FIG. 11, the base station transmits system information to the terminal (S111), and the terminal checks information related to cell DTX / DRX. For example, the system information may include MIB (master information block), SIB1 (System information block1), etc. In relation to the NES technology, as shown in Table 5 below, the MIB may include information related to cell barring (e.g., cellBarred), and the SIB1 may include information related to the cell barring status (e.g., cellBarredNES). Specifically, when cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. Conversely, when cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell barring status. If cellBarred of MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX can treat the cell as barred and perform cell reselection to another cell. On the other hand, if cellBarred of MIB is set to barred and cellBarredNES is included in SIB1, the terminal supporting NES cell DTX / DRX can determine that the cell is not barred.

[0221] - SIB1SIB1messageSIB1-v1740-IEs ::= SEQUENCE {si-SchedulingInfo-v1740 SI-SchedulingInfo-v1740 OPTIONAL, -- Need RnonCriticalExtensionSIB1-v1800-IEsOPTIONAL}SIB1-v1800-IEs ::= SEQUENCE {cellBarredNES-r18 ENUMERATED {notBarred} OPTIONAL, -- Need RnonCriticalExtension SEQUENCE {} OPTIONAL}SIB1field descriptionscellBarredNESThe presence of this field indicates that the cell is allowed for UEs supporting NES cell DTX / DRX.

[0222] The terminal has the capability to support NES cell DTX / DRX, and it is assumed that cellBarred of MIB is set to notBarred, or cellBarred of MIB is set to barred and cellBarredNES is included in SIB1. Accordingly, the terminal performs a random access procedure to access the base station (S112), and can perform communication thereafter. At this time, the base station performs a cell DTX / DRX operation and transmits configuration information related to the cell DTX / DRX operation to the terminal (S113). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). Additionally, the configuration information may further include information for receiving and interpreting cell DRX / DRX related control information (e.g. DCI related information) (see TS 38.331CellDTXDRX-Config).

[0223] Thereafter, the base station transmits control information related to cell DTX / DRX to the terminal (S115). The control information related to cell DTX / DRX may include DCI having a designated format (e.g., format 2_9). If an operation for a serving cell according to at least one of the cell DTX operation and the cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config), the terminal may check a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring a PDCCH conveying control information of a designated format during an active time through a higher layer parameter (e.g., SearchSpace), and may obtain a location of information about the serving cell within the control information through a higher layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal may obtain control information based on the identified set of search spaces and location.

[0224] Control information related to cell DTX / DRX may be used to indicate activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is configured as a SUL (supplementary uplink) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.

[0225] The DCI format 2_9 related to this can be defined as shown in Table 6 below.

[0226] - DCI Format 2_9DCI format 2_9 is used for activating or de-activating the cell DTX and / or DRX configuration of one or multiple serving cells for one or more UEs, and / or for providing NES-mode indication of the primary cell for one or more UEs.The following information is transmitted by means of the DCI format 2_9 with CRC scrambled by cellDTRX:- block number 1, block number 2,..., block numberNwhere the starting position of a block associated with a serving cell is determined by the parameterpositionInDCI-cellDTRXprovided by higher layers for the UE.If the UE is configuredto monitor DCI 2_9 with CRC scrambled by cellDTRX-RNTI, one or more blocks are configured for the UE by higher layers, with the following fields defined for each block:- Cell DTX / DRX indication - number of bits determined by the following:- If higher layer parametercellDTXDRX-L1activationis configured- 2 bits as defined in Clause 11.5 of [5, TS38.213] ifcellDTXDRXconfigTypeis configured todtxdrxfor the associated serving cell of the block, with the MSB corresponding to cell DTX configuration and the LSB corresponding to cell DRX configuration;- 1 bit as defined in Clause 11.5 of [5, TS38.213]ifcellDTXDRXconfigTypeis configured to eitherdtxordrxfor the associated serving cell of the block;- 0 bit otherwise.- NES-mode indication - 1 bit indicating NES-specific CHO execution condition as defined in Clause 11.5 of [5, TS38.213], if the higher layer parameternesEventis configured and the associated serving cell of the block is primary cell; 0 bit otherwise.The size of DCI format 2_9 is indicated by the higher layer parametersizeDCI-2-9.

[0227] Thereafter, the terminal and the base station can perform communication based on the cell DTX / DRX. Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor the signal from the base station. During the DTX-OFF, the base station enters a sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON can completely cover the DRX-ON of the terminal. Furthermore, the base station can align the transmission of Xn / NG and the transmission of Uu for the purpose of NES. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform a dormancy-like behavior of sparsely transmitting or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal may sparsely receive or not receive a downlink signal / channel depending on the settings of the base station. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH.

[0228] Enhancements of network energy savings for NR

[0229] A work item (WI) titled “Enhancements of network energy savings for NR” has been additionally approved for a given scenario (3GPP NR release 19). Specifically, the following enhancement techniques are being considered for the given scenario, as shown in Table 7.

[0230] Objective of SI or Core part WI or Testing part WIThe objectives of the work item are the following:1. Specify procedures and signaling method(s) to supporton-demand SSBSCell operation for UEs in connected mode configured with CA, for both intra- / inter-band CA. [RAN1 / 2 / 3 / 4]- Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling)- Note1: On-demand SSB transmission can be used by UE for at least SCell time / frequency synchronization, L1 / L3 measurements and SCell activation, and is supported for FR1 and FR2 in non-shared spectrum.2. Study procedures and signaling method(s) to supporton-demand SIB1for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]- Triggering method by uplink wake-up-signal using an existing signal / channel.- Wake-up-signal configuration provisioning to UE* Note: No modification of SSB will be discussed under this objective- Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.- Checkpoint for normative work in RAN#1053. Specifyadaptation of common signal / channel transmissions. [RAN1 / 2 / 3 / 4]- Adaptation of SSB in time domain, e.g. adapting periodicity- Adaptation of PRACH in time domain- Study adaptation of PRACH in spatial domain, e.g. non-uniform PRACH resources per SSB, and specify if found beneficial--This study is to be done in 2Q'2024 only- Adaptation of paging occasions including confining the paging occasions in the time domain* Note: there shall be no paging latency increase- Note: there shall be no negative impact to legacy UEs, unless significant benefits are shown4. Specify the corresponding core requirements, for the above features [RAN4].

[0231] (1) On-demand SSB

[0232] A method to reduce energy consumption by having a base station transmit SSB on a specific cell through an on-demand SSB process and not transmit SSB on that cell when an on-demand SSB process is not available can be discussed. In the existing NR system, SSB must be transmitted periodically and always for purposes such as time / frequency synchronization or RRM (Radio Resource Management), making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SSB transmission until the on-demand SSB process is involved and then performing SSB transmission. The on-demand SSB process can be triggered using one of the following methods:

[0233] 1) The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS in the NR system).

[0234] 2) Requesting SSB transmission from base station (or TRP) #1 to base station (or TRP) #2 through an interface between base stations (e.g., Xn interface in NR system) or backhaul signaling.

[0235] 3) Signaling whether SSB transmission is possible for the corresponding Scell ​​through Scell ​​activation / deactivation signaling.

[0236] Considering coexistence with existing NR terminals, etc., the given scenario (3GPP NR release 19) is limited to on-demand SSB operation for connected mode terminals and SCells, but in future releases or next generation communication systems, on-demand SSB operation (for SSB transmission on PCell) considering inactive or idle mode terminals or initially connected terminals may be defined. In addition, CA (carrier aggregation) including the SCell can be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process can be utilized for at least functionality such as time / frequency synchronization, L1 / L3 measurement, and SCell activation.

[0237] (2) On-demand SIB1 transmission

[0238] Figure 12 is a diagram for explaining transmission of On-demand SIB1.

[0239] In the existing NR system, SIB1, which contains system information, random access information, etc. for initial connection or idle mode terminals to access the cell, had to be provided periodically, so it was difficult to reduce energy consumption even when the base station had no data to receive or send. Considering this, a method was introduced in which the base station does not perform SIB1 transmission and only performs SIB1 transmission when an on-demand SIB1 process is involved, thereby reducing base station energy consumption. The on-demand SIB1 process can be triggered by the base station transmitting an uplink signal / channel (e.g., PRACH in the NR system). In this regard, the following scenarios can be considered.

[0240] (1) Scenario 1

[0241] Referring to Fig. 12 (a), the terminal may receive an SSB (and / or another downlink signal / channel) from cell#1 and recognize that SIB1 is not transmitted on the cell#1. In this case, the terminal may transmit a signal requesting SIB1 (hereinafter, for convenience of explanation, the signal is defined as a WUS, wake-up signal) based on information provided in the SSB (and / or another downlink signal / channel) and / or predetermined information, thereby triggering transmission of SIB1 related to the cell#1. The base station or cell#1 that receives the WUS may transmit a specific DL signal / channel on cell#1 in response to the WUS, and may transmit SIB1 on cell#1 (or without transmitting the corresponding DL signal / channel).

[0242] (2) Scenario 2

[0243] Referring to FIG. 12 (b), the terminal may receive an SSB (and / or another downlink signal / channel such as SIB1) from cell#1, recognize that SIB1 is not transmitted on cell#2, and attempt camp-on via cell#2. In this case, the terminal may transmit a signal (e.g., WUS) requesting SIB1 related to cell#2 on cell#1 based on information provided in the received SSB (and / or another downlink signal / channel such as SIB1) and / or predetermined information, thereby triggering transmission of SIB1 for cell#2. The base station receiving the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response to the WUS, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0244] (3) Scenario 3

[0245] Referring to Fig. 12 (c), the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from cell#1, recognize that SIB1 is not transmitted on cell#2, and attempt camp-on via cell#2. The terminal may trigger transmission of SIB1 for cell#2 by transmitting a WUS, which is a signal requesting SIB1, on cell#2 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station may transmit a specific DL signal / channel on cell#2 in response to the WUS, and may transmit SIB1 for cell#2 on cell#2 (or without transmitting the corresponding DL signal / channel).

[0246] In this way, a method for reducing the energy consumption of the base station / cell by reducing the transmission frequency of common signals / channels such as SSB, PRACH, and paging by the base station can be discussed. As described above, completely turning off the transmission of SSB can significantly reduce the energy consumption of the base station. However, if there is no SSB, which performs functions such as time / frequency synchronization or RRM measurement from the perspective of the terminal, stable operation may not be guaranteed for cells that do not transmit SSB. Considering this, it may be more appropriate to save the energy of the base station / cell by changing the transmission pattern of SSB according to the situation rather than completely turning off the transmission of SSB. Here, the transmission pattern of SSB may be related to the transmission period, the period for each SSB candidate index, the SSB candidate index(es) transmitted within one transmission period, the transmission power, etc.

[0247] Alternatively, in the case of contention-based random access with respect to PRACH resources, the base station may not know when the terminal will transmit the PRACH. Therefore, the base station must always attempt to receive / monitor the configured PRACH resources, which may increase the energy consumption of the base station. Considering this, a method for controlling the amount of PRACH resources needs to be considered to save the energy of the base station. Here, controlling the amount of PRACH resources may be done by controlling the period of the PRACH resources, controlling the amount of resources by pre-configuring PRACH resource sets #1 and #2 and indicating whether to activate at least one of them, or providing the corresponding RACH (or PRACH) resource amount uniformly or non-uniformly for each SSB index.

[0248] Alternatively, in the case of paging, previously, paging frames (PFs) and / or paging occasions (POs) were distributed along the time axis within a DRX cycle (or paging cycle), and the terminal attempted to receive paging at a specific PF / PO derived from a formula based on its ID. From the base station's perspective, if paging was to be transmitted to multiple terminals simultaneously, the paging had to be transmitted frequently by waking up. As a method for reducing the base station energy consumption caused by this, a method of arranging PFs and / or POs for paging reception as close to the time axis as possible or arranging different frequency axis resources within the same time may be considered.

[0249] As higher data rates are demanded, base stations must be equipped with more antennas and provide services across wider bandwidths and frequency bands. Recent studies have shown that base station energy costs can account for up to 20% of total operational expenditures (OPEX). To build eco-friendly networks by reducing carbon emissions and lowering operating expenses (OPEX) for telecommunications operators, energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP.

[0250] Due to this increased interest in base station energy savings, a new study item called “study on network energy savings” was approved for a given scenario (3GPP NR release 18), and the technologies specified in the subsequent work items included SSB-less SCell operation for inter-band CA of FR1 and co-located cells, improvements to the Cell DTX / DRX mechanism including alignment of Cell DTX / DRX and UE DRX in RRC_CONNECTED mode, and inter-node information exchange of Cell DTX / DRX. Additionally, it includes spatial and power domain techniques to enable efficient adaptation of spatial elements, efficient adaptation of power offset values ​​between PDSCH and CSI-RS, mechanisms to prevent camping of legacy UEs in cells where NES techniques are adopted for a given scenario (Rel-18), improvements to CHO procedures, inter-node beam activation and improvements to limit paging in a limited area, and corresponding RRM / RF core requirements.

[0251] Meanwhile, since there are other technologies that have been identified as useful through studies but are not yet specified in 3GPP Rel-18, 3GPP Rel-19 WI aims to adopt additional technologies that can achieve network energy saving benefits related to beneficial technologies that have not been adopted in 3GPP Rel-18 (e.g., on-demand SSB and on-demand SIB1 transmission, adaptation of common signal / channel transmission, etc.).

[0252] Hereinafter, a method for an idle / inactive terminal in a cell operating on-demand SIB1 to request SIB1 transmission to a cell / base station via a wake-up signal (WUS) is described. Specifically, the transmission conditions of the WUS, the WUS transmission and WUS transmission / reception procedures, and the WUS transmission failure handling and retransmission procedures are described in detail. In addition, an anchor cell can be defined as Cell A, and a non-anchor cell can be defined as an NES cell.

[0253] On-demand SIB1 procedure for energy saving

[0254] Figure 13 is a drawing for explaining a method of performing On-demand SIB1.

[0255] From the perspective of a base station operating multiple frequency bands, even when the number of terminals served is small or the traffic load is relatively low, the amount of energy consumed by the base station through periodic transmission of SSB and / or system information (e.g., SIB1) can be quite large.

[0256] For example, referring to FIG. 13, a base station operating three frequency bands may periodically transmit (legacy) SSB and / or SIB1 only in some frequency bands (e.g., F1). The base station may transmit a simplified (or modified) S-SSB (simplified SSB) in another frequency band (e.g., F2) or may not transmit SSB and / or SIB1 in another frequency band (e.g., F3). In this way, the base station may save energy by not transmitting SIB1 on F2 and / or F3. Meanwhile, the frequency bands described above may refer to bands, carriers, serving cells, or BWPs.

[0257] The terminal can move from F1 to F2 or F3 and perform the on-demand SIB1 procedure. Thereafter, the terminal can receive SSB and / or SIB1 for the F2 or F3 frequency band, perform a RACH procedure, and enter the RRC connected mode to transmit and receive DL and / or UL data through F2 or F3. In the following, for the convenience of explanation, the frequency band where S-SSB can be transmitted, such as F2, the frequency band where SSB cannot be transmitted, such as F3, and / or the frequency band where SIB1 is transmitted through the on-demand SIB1 procedure is defined as the F2 frequency band, but the proposal described below can of course be applied to frequency bands such as F3.

[0258] In addition, for the convenience of explanation below, a frequency band that provides information about another frequency band through SSB and / or SIB1, such as F1 illustrated in FIG. 13, is defined as an anchor cell, and another frequency band for which cell information is provided through SSB and / or SIB1 of the anchor cell is defined as a non-anchor cell (e.g., F2 or F3). Here, the information about the other frequency band through SSB and / or SIB1 may include whether SIB1 is currently being periodically transmitted in the other frequency band (or whether the cell is based on an on-demand SIB1 procedure), transmission time pattern information of SIB1 on the other frequency band if SIB1 is periodically transmitted, and / or configuration information about UE WUS resources for the on-demand SIB1 procedure if SIB1 is not periodically transmitted. And / or, the UE may assume that there is an association and / or QCL (Quasi Co Location) relationship between the anchor cell and the non-anchor cell.

[0259] 1. Method #1: Conditions for triggering WUS transmission when the terminal has set up WUS resources for on-demand SIB1.

[0260] The terminal may compare the reception quality (e.g., RSRP, RSRQ, etc.) of the DL signal / channel (e.g., SSB) of the anchor cell and its associated non-anchor cells to select a cell with better quality and attempt to connect. At this time, if there is more than one non-anchor cell, the terminal may select a cell with better reception quality among the non-anchor cells, or may randomly select one of the cells with a quality level or higher. Alternatively, the terminal may preferentially select a cell (or non-anchor cell) with the (lowest) index or the (highest) index based on the list and index of non-anchor cells provided through the SSB / SIB1 of the anchor cell, or may select a cell (or non-anchor cell) with the highest priority according to the priorities among the established non-anchor cells. Here, the terminal's selection of a specific cell may be premised on the assumption that the SSB transmitted by the cell is higher than a threshold value established / defined in advance.

[0261] Since SIB1 is not periodically transmitted from the cell, terminals in a cell (or non-anchor cell) operating on-demand SIB1 can notify the base station (or non-anchor cell) of the need for SIB1 transmission through a pre-configured WUS resource when reception of SIB1 is required. For example, if the cell (or non-anchor cell) to which the terminal initially attempted to connect is a cell operating on-demand SIB1 (e.g., a SIB-less cell), SIB1 may not be transmitted. In this case, the terminal can request SIB1 transmission to the cell (or non-anchor cell) by transmitting a WUS (from a WUS resource preset to request SIB1 transmission) to the cell (or non-anchor cell), and can perform a full-fledged initial access procedure for the cell (or non-anchor cell) by transmitting a PRACH based on a PRACH configuration included in SIB1 received from the cell (or non-anchor cell).

[0262] Additionally, idle / inactive terminals can be notified of SI (system information) modifications via paging messages. Here, SI modifications may mean that SI may change at the next modification period boundary. Accordingly, if SI modifications (e.g., modifications of SI for a specific non-anchor cell or cell 1) are indicated via paging / paging messages, the terminals can perform an SI acquisition procedure to obtain SI for the cell 1 (or non-anchor cell) by transmitting a WUS.

[0263] Meanwhile, if an anchor cell and at least one non-anchor cell associated with the anchor cell are configured for a terminal, the terminal may be instructed (e.g., PDCCH-order) to perform initial access (via a specific non-anchor cell) via a paging / paging message. If the cell (or cell) to which the initial access is instructed is a cell operating on-demand SIB1 (e.g., a SIB-less cell) and does not transmit SIB1, the terminal may transmit a WUS to the cell to request SIB1 transmission. The terminal may receive SIB1 from the cell and perform a full-fledged initial access procedure for the cell based on the PRACH configuration for accessing the cell included in the SIB1.

[0264] Alternatively, the terminal may receive cell indexes, frequency locations (e.g., ARFCN (Absolute Radio Frequency Channel Number)), UL WUS configuration for requesting SIB1, etc. of a plurality of non-anchor cells (NES cells) operating on-demand SIB1 for energy saving from an anchor cell (Cell A). The terminal may select a cell (hereinafter, NES cell) based on at least one of the following two methods.

[0265] - Method 1) Selecting an NES cell operating on-demand SIB1 (or OD-SIB1) explicitly indicated through the UL WUS settings provided by the anchor cell (or cell A), or,

[0266] - Method 2) A method of selecting a NES cell based on the measured reception quality of a DL signal (e.g., SSB) transmitted by the NES cell.

[0267] For example, in the case of method 1), the terminal may receive list information of multiple (candidate) NES cells from the anchor cell (or cell A). In this case, the terminal may determine a specific NES cell in the list or a subset of candidate NES cells through a modular operation or grouping based on the terminal ID. When the subset of candidate NES cells is determined, the terminal may select one NES cell from the subset based on a method / condition defined in advance in a standard document (e.g., a 3GPP TS document) or a setting / instruction (e.g., a cell with the highest index or the lowest index), or the terminal may randomly select one NES cell among the NES cells in the subset. In this case, the subset may also include the same list information (or NES cell candidate list information) set by the base station (or the anchor cell). For example, even if a base station configures five NES cell candidates or provides list information for five NES cells, it can be configured to actually select only three NES cells for each terminal.

[0268] Meanwhile, the measured reception quality / reception strength for the DL signal (e.g., SSB) of the NES cell selected / determined by the terminal through the above-described "Method 1") may be below a predefined threshold (or a threshold set by the base station). In this case, even if the terminal is explicitly instructed to select the NES cell through "Method 1"), the terminal may exceptionally (irrespective of the instruction) apply "Method 2") to select any NES cell having a reception quality of the DL signal (e.g., SSB) above the threshold. Alternatively, the terminal may continue to camp on Cell A without accessing the selected NES cell. Alternatively, it is also possible to randomly select one NES cell among at least one NES cell that satisfies the condition of "Method 2") among the (candidate) NES cells included in the candidate list for the NES cell set by the base station. Alternatively, if none of the (candidate) NES cells in the candidate list satisfies the condition of “Method 2), the terminal may continue to camp on Cell A without performing selection of the NES cell.

[0269] 2. Method #2: WUS transmission and reception procedure of terminals in a (NES) cell operating on-demand SIB1

[0270] In order for a terminal to request transmission of SIB1 via WUS for a cell (or NES cell) operating On-demand SIB1, a WUS resource must first be configured. Meanwhile, an anchor cell and at least one non-anchor cell (or at least one NES cell) associated with the anchor cell may be configured for the terminal, and a WUS resource may be configured for requesting transmission of SIB1 for a specific cell among the at least one non-anchor cell. In this case, it is necessary to indicate / configure which specific non-anchor cell among the multiple non-anchor cells configured for the terminal is the WUS resource for. In this regard, the terminal may configure / receive a list of non-anchor cells associated with the anchor cell from the anchor cell (or the specific non-anchor cell) through an SSB / MIB / SIB, etc., in order to select the first cell (or non-anchor cell). At this time, the list of non-anchor cells may include information on the indexes of non-anchor cells, and may also provide information on a mapping setting regarding which index of a non-anchor cell a WUS resource configured to request transmission of SIB1 is associated with. The terminal may transmit a WUS to a specific non-anchor cell corresponding to the WUS resource and receive SIB1 from a specific non-anchor cell based on the information on the mapping setting. For example, the terminal may receive list information including index information of NES cells (or NES cells operating On-demand SIB1) from a base station or an anchor cell, and may specify / identify an NES cell or a specific NES cell having an index mapped / corresponding to the WUS resource based on the index information, or may be instructed of an index corresponding to the WUS resource.

[0271] Meanwhile, when the terminal transmits the WUS to the specific non-anchor cell (e.g., an NES cell having an index mapped to WUS resources), the terminal may receive a response as to whether the WUS was properly delivered to the base station or the specific non-anchor cell. Here, the response of the base station may be in the form of a Random Access Response (RAR) or may be transmitted via a separate PDCCH. When an ACK for the WUS is transmitted in the form of a RAR, the terminal may consider the WUS transmission to be successful only when it receives a response to the WUS it transmitted within a pre-configured window. When an ACK for the WUS is transmitted via a separate PDCCH, the terminal may be configured in advance with a CORESET / SS (search space) set / RNTI, etc. for receiving the PDCCH. In this case, after transmitting the WUS, the terminal may perform PDCCH monitoring on a pre-arranged time / frequency resource, and may receive a PDCCH that explicitly includes ACK information for the WUS, or may consider that the ACK for the WUS has been implicitly transmitted through reception of a DL / UL scheduling PDCCH. In addition, when multiple cells are configured for the terminal (e.g., an anchor cell and multiple non-anchor cells associated therewith), a cell to which a response to the WUS is to be transmitted may be configured in advance. The cell that transmits the response to the WUS may be the same cell as the cell to which the terminal transmitted the WUS, or may be a different cell.

[0272] A terminal may need to receive an instruction on whether the base station actually transmits SIB1, separately from the base station's response (ACK) to the WUS transmitted by the terminal. For example, since the base station cannot always immediately transmit SIB1 simply by transmitting the WUS of the terminal, the base station may instruct the terminal with scheduling information indicating that it will actually transmit SIB1. Such information on whether the base station actually transmits SIB1 (or scheduling information for the base station's SIB1 transmission) may be transmitted through a separate PDCCH configured in advance for the terminal, or msg2 (or msg4, msg B). Alternatively, information on whether the base station actually transmits SIB1 (or scheduling information for the base station's SIB1 transmission) may also be indicated through the SIB1 (or SIBx) of the anchor cell, paging, or the MIB of a non-anchor cell. The information (or indication thereof) on whether the base station actually transmits SIB1 may include scheduling information (e.g., time / frequency information) when the actual SIB1 will be transmitted, or may simply include information indicating the actual transmission of SIB1. If the information on whether the base station actually transmits SIB1 only includes information indicating the actual transmission of SIB1, the reception of SIB1 may be performed at a time / frequency resource that has been agreed upon / configured in advance. For example, the terminal may expect that SIB1 will be received / transmitted a specific time (T symbol / slot) after the time at which it has been instructed in advance that SIB1 will actually be transmitted. Alternatively, one of a plurality of candidate time points may be directly indicated in advance. Alternatively, similar to TRS, a specific time interval during which SIB1 can be transmitted may be configured in advance, and the terminal may attempt to receive SIB1 within the specific time interval.Meanwhile, even if the base station receives a WUS requesting transmission of SIB1 from the terminal, if it is difficult to transmit SIB1 immediately or if SIB1 was scheduled to be transmitted soon, the base station may instruct the terminal to defer SIB1 transmission at the next cycle / opportunity (e.g., next SI modification period boundary), or instruct the terminal that SIB1 reception is valid from a specific opportunity (occasion). For example, the base station may instruct the terminal that transmission of SIB1 requested by the WUS is delayed / postponed until the next SI modification period, not the current SI modification period, or may instruct the terminal that reception of valid SIB1 is possible from the next SI modification period.

[0273] Alternatively, the terminal may transmit PRACH as a WUS for requesting SIB1. For example, when the WUS resource is set as a PRACH resource, the terminal may transmit a signal requesting transmission of the SIB1 using the PRACH. The terminal may receive a RAR (or a separate PDCCH format (e.g., group-common PDCCH)) for the RAPID transmitted by the terminal (or an ACK for the WUS) as a response to the WUS. In this case, even if an ACK is received through the RAR for the RAPID (Random Access preamble ID) transmitted by another terminal, the terminal may regard it as having received an ACK for the transmission (or reception) of the WUS. In this case, the terminal may attempt to receive SIB1 (from a non-anchor cell corresponding to the WUS) or may move to another non-anchor cell to attempt to receive SIB1. This is because, even if it is a response to a WUS transmitted by another terminal (e.g., RAR, MsgB), if the base station transmits SIB1, the terminal may receive SIB1 according to the response. For example, when a terminal transmits a WUS using PRACH, the terminal can receive / monitor the SIB1 by judging not only its own RAPID but also a response (RAR) to another terminal's RAPID as an ACK in response to the transmission of the WUS.

[0274] In addition, as described above, the cell to receive the WUS and the cell to transmit the ACK / response to the WUS may be the same or different. If the cell to receive the WUS and the cell to transmit the ACK to the WUS are different, the terminal may be configured in advance for each of the cell to receive the WUS and the cell to transmit the ACK / response. In addition, the cell to which the base station transmits SIB1 in response to the WUS may also be the same as or different from the cell to receive the WUS (or the cell to transmit the ACK / response). Accordingly, the terminal may also be configured in advance for the cell to receive the on-demand SIB1. In this case, the terminal may be configured only for the cell to receive the WUS, and may not be configured for the cell to transmit the ACK / response to the WUS and the cell to transmit the SIB1. In this case, the terminal may be considered / defined to receive the ACK / response and SIB1 from the same cell as the cell to receive the WUS. In other words, the terminal may consider / define the cell that will receive the terminal's WUS, the cell that will transmit the ACK / response to the WUS, and the cell that will transmit SIB1 as all the same. For example, as in scenario 3 described with reference to FIG. 12, the terminal may transmit a WUS to a specific cell that requests transmission of SIB1, and receive a response to the WUS and SIB1 from the specific cell.

[0275] Alternatively, if no cell is configured to receive the WUS (e.g., if there is no separate configuration for the cell to receive the WUS, the cell to transmit the ACK for the WUS, or the cell to transmit the SIB1), the terminal may consider / define the cell that performed the initial access as the cell to receive the WUS by default.

[0276] Meanwhile, it is necessary to prevent an increase in signaling overhead and / or a communication error between the terminal and the base station due to the terminal transmitting a WUS again before receiving an ACK / response after transmitting the WUS. To this end, a Prohibit timer may be additionally set to prevent the terminal that transmitted the WUS from transmitting an additional WUS for a specific period of time. A terminal that transmits a WUS requesting on-demand SIB1 on a specific cell (e.g., a specific SIB-less cell) at a specific point in time may activate a prohibit timer from the specific point in time (e.g., the point in time of transmitting the WUS), and repeated transmission / retransmission of the WUS requesting on-demand SIB1 for the specific cell (e.g., the specific SIB-less cell) may not be permitted until the prohibit timer expires. When the above prohibit timer expires, the terminal may transmit a WUS to re-request on-demand SIB1 for the specific cell (e.g., a specific SIB-less cell). Meanwhile, the value of the above prohibit timer may be a value defined in advance or set / instructed by the base station.

[0277] 3. Method #3: Failure Determination / Processing and Retransmission Method after WUS Transmission for On-Demand SIB1 of Terminal

[0278] After the terminal transmits a WUS for receiving SIB1, if it does not receive a response to the WUS within a specific time period, it should consider the transmission of the WUS as a failure and attempt to retransmit the WUS. Accordingly, a specific time (timer / duration) for determining whether the transmission of the WUS has failed may be set in advance, and the terminal may determine that the transmission of the WUS has failed if it does not receive an ACK / response to the transmission of the WUS before the expiration of the set timer or before the end of the time period. At this time, as described above, the cell on which the terminal is currently camped and the cell on which the WUS is received may be different. Accordingly, the criteria for transmission failure (e.g., timer / duration value) may be set differently depending on whether the terminal transmits the WUS signal to an anchor cell or a non-anchor cell, and the operation of the terminal after determining that the transmission of the WUS has failed may also be defined / set differently separately. For example, if a terminal transmits a WUS from a non-anchor cell and the transmission fails, the terminal may move to an anchor cell and perform a retry of the WUS transmission, or may be configured to perform a reselection operation of the anchor cell if the WUS transmission fails in the moved anchor cell as well. In addition, if a dedicated RO (RACH Occasion) / RAPID is configured as a transmission resource of the WUS for the terminal, the operation of the terminal after a transmission failure of the WUS may be separately defined / configured depending on whether the WUS actually transmitted by the terminal used the dedicated RO / RAPID.For example, if a WUS is transmitted (to a non-anchor cell) without using dedicated RO / RAPID and fails, the terminal may be configured to attempt retransmission (to the non-anchor cell) using dedicated RO / RAPID, and if a WUS is transmitted (to a non-anchor cell) using dedicated RO / RAPID and fails, the terminal may be configured to move to an anchor cell and (re)transmit the WUS (to the anchor cell).

[0279] 4. Method #4: How to receive SIB1 from the terminal after successful WUS transmission

[0280] After transmitting a WUS for a SIB1 request, the terminal may receive SIB1 by receiving an ACK / response to the transmission of the WUS, based on a prior configuration or base station instruction. For example, if the terminal receives a response (e.g., RAR) to the transmission of the WUS, the terminal may receive SIB1 after a predetermined time from the time of receiving the response, or may receive SIB1 at a time or frequency resource specified based on a response (e.g., DCI, MAC-CE) containing information about resources scheduled for the SIB1.

[0281] The terminal may attempt to receive SIB1, expecting that SIB1 will be transmitted through a specific cell after a pre-configured / promised time (e.g., T ms / slot) from the time of receiving the base station's ACK / response for transmission of WUS (e.g., transmission of PRACH and / or PUSCH) or GC (group-common)-DCI (or MAC-CE, RAR) indicating scheduling for SIB1. Alternatively, the terminal may attempt to receive SIB1, expecting that SIB1 will be transmitted through a specific cell during a certain time window from the time of receiving the response / scheduling or at a pre-configured PDCCH monitoring occasion. In addition, information on the cell where SIB1 will be scheduled, scheduling information and / or time (e.g., an index of one of pre-configured time candidate indices) may be directly indicated in the base station's ACK / response or GC-DCI (or MAC-CE).

[0282] At this time, the terminal may be configured with multiple CORESETs having different beam directions for each non-anchor cell in advance. In this case, the actual scheduling of SIB1 may allow the terminal to receive SIB1 PDCCH / PDSCH only in the beam direction corresponding to the non-anchor cell where the terminal will receive SIB1. More specifically, multiple CORESETs, for example, 10 MOs (monitoring occasions) may be configured for the terminal according to the index of the non-anchor cell, and non-anchor cell #1 may be configured to monitor MOs mapped to different beam directions from 1 to 5, and cell #2 may be configured to monitor MOs mapped to different beam directions from 6 to 10 (e.g., mapped in a beam index first, cell index second manner). For example, the terminal may be configured with 10 MOs (monitoring occasions) mapped to MOs 1 to 5 for non-anchor cell l#1 and MOs 6 to 10 for non-anchor cell l#2, or may receive configuration information for the 10 MOs. Here, the MOs may be mapped to different beam directions.

[0283] Alternatively, CORESET / SS / RNTI (Control Resource Set / Search Space / Radio Network Temporary Identifier) ​​may be configured for each non-anchor cell or non-anchor cell group. In this case, the UE can receive SIB1 through the CORESET / SS / RNTI corresponding to the non-anchor cell or non-anchor cell group to be received. Alternatively, the UE may configure / be instructed to configure / be instructed to configure CORESET / SS for receiving SIB1 transmitted from a non-anchor cell through an ACK / response to the SIB1 or WUS transmission of the anchor cell.

[0284] Meanwhile, as described above, the configuration information of the CORESET#0 / SS set for OD-SIB1 reception in the NES cell (or non-anchor cell) may be provided through an explicit base station response (e.g., RAR) to the WUS (or UL WUS). In this case, the information of the CORESET / SS set for RAR reception in the NES cell may be configured from Cell A (or the anchor cell). The terminal may use the information of the CORESET / SS set configured from Cell A as is for OD-SIB1 reception, or may configure information of a new CORESET / SS set with the RAR. Alternatively, the terminal may be configured / instructed in advance as to whether to use the information of the CORESET / SS set configured from Cell A as is. In the absence of a separate setting / instruction for this, the terminal may interpret that the setting information of the CORESET / SS set set from Cell A is reused for OD-SIB1 reception (e.g., reception of SIB1 from the NES Cell).

[0285] Alternatively, when the UE receives configurations (e.g., WUS configuration) for OD-SIB1 (on-demand SIB1) reception from the NES cell (or non-anchor cell) from Cell A (anchor cell), the UE may be configured with multiple CORESET / SS (search space) sets (e.g., searchSpaceZero for OD-SIB1) for OD-SIB1 PDCCH reception. The NES cell may transmit msg2 / msgB (random access response) to the UE as a response that the UL WUS for OD-SIB1 request has been received. In this case, the NES cell may directly indicate one of the multiple candidate CORESET / SS sets configured from Cell A. The terminal may attempt to receive OD-SIB1 PDCCH within a time window that is pre-configured / instructed through the CORESET / SS set indicated through msg2 / msgB PDCCH / PDSCH.

[0286] Alternatively, the terminal may be configured with multiple CORESET / SS sets (e.g., searchSpaceZero for OD-SIB1) for OD-SIB1 PDCCH reception through the SSB (e.g., MIB included in the SSB) of the NES cell (or non-anchor cell), and may be directly instructed to select one of the multiple candidate CORESET / SS sets through a response to the UL WUS (e.g., RAR), and may attempt to receive OD-SIB1 PDCCH within a pre-configured / instructed time window. In this case, if the SSB of the NES cell is transmitted in sync raster, the SSB may be transmitted as NCD (Non-Cell Defining)-SSB, but if it is not transmitted in sync raster (not on sync raster), the SSB may be transmitted as CD (Cell Defining)-SSB. For example, the configuration of a CORESET / SS set for OD-SIB1 may be given via a CD SSB (not transmitted in a sync raster) of a NES cell. Instead of receiving the configuration information of SIB1 PDCCH via RAR, the configuration information of SIB1 PDCCH may be provided via the SSB of the NES cell. In this case, the CORESET / SS set configuration for OD-SIB1 may be given via a CD-SSB transmitted in a sync raster separately defined for a terminal capable of receiving OD-SIB1. Additionally, one of multiple CORSET / SS set candidates configured via the WUS configuration of Cell A (or anchor cell) may be indicated via an SSB (e.g., MIB) transmitted on the NES cell.

[0287] Meanwhile, SIB1 of a non-anchor cell (or NES cell) may be multiplexed with SIBx of an anchor cell and transmitted together. In this case, SIBx may refer to SIBs that can be transmitted from the anchor cell (or cell A). For example, if SIB1 of a non-anchor cell is configured to be multiplexed with SIB2 of an anchor cell and transmitted, the UE may obtain SIB1 information of the non-anchor cell by receiving SIB2 of the anchor cell. For example, the anchor cell may schedule SIB1 of the non-anchor cell(s) with NEW-SI-RNTI (System Information - Radio Network Temporary Identifier). If SIB1s for multiple non-anchor cells are muxed, the anchor cell may distinguish which NES cell (or non-anchor cell) the SIB1 is for by using PCI (NR Physical Cell ID), global cell index, NR-ARFCN (Absolute Radio Frequency channel number), or a pre-indexed value. For example, if the SIB1 of an anchor cell and a non-anchor cell are multiplexed, the terminal can monitor the DCI scrambled with the existing SI-RNTI when attempting to receive the SIB1 for the non-anchor cell. Also, if the NEW-SI-RNTI (for a specific non-anchor cell) is set, the terminal can monitor the DCI scrambled with the NEW-SI-RNTI rather than the existing SI-RNTI when attempting to receive the SIB1 for the non-anchor cell.

[0288] When a terminal transmits a WUS for a SIB1 request in a specific beam direction, the terminal may be configured to perform SIB reception, paging monitoring, and / or random access only in a direction corresponding to the beam direction of the transmitted WUS (e.g., in the same beam direction). For example, when a terminal transmits a WUS that is a PRACH in a direction corresponding to SSB index #1 among SSBs transmitted from an anchor cell and / or a non-anchor cell whose RSRP is greater than a specific threshold, the terminal may perform SIB reception, paging monitoring, and / or random access only in the beam direction corresponding to SSB index #1.

[0289] Specifically, when a terminal moves to another cell after transmitting a WUS and receives SIB1, the terminal may need to change the frequency due to reasons such as the frequency gap between cells. Therefore, considering the RF tuning time of the terminal, the timeline of SIB1 reception (e.g., when the cell receiving the WUS and the cell transmitting the corresponding SIB1 are different) may be set to be relatively (relaxed) longer than when SIB1 corresponding to the transmission of WUS is received within the same cell. In addition, the number of SIB1 transmissions and / or time intervals corresponding to the WUS may be set differently (considering SFN mismatch, etc.) depending on the type of WUS transmitted by the terminal (pre-arranged / configured UL signal / channel, or RO / RAPID).

[0290] In this way, when the base station operates in an on-demand manner, omitting SIB1, which is transmitted periodically for energy conservation, and transmitting it only when requested by the terminal, the conditions for triggering a WUS requesting SIB1 from the terminal's perspective and a method for receiving an ACK / response to the transmitted WUS are proposed. This proposed method can obtain energy conservation benefits while appropriately transmitting SIB1 when the terminal needs SIB1 for reasons such as cell access, by setting up a failure determination after transmitting a WUS, a retransmission method, and a method for receiving the requested SIB1.

[0291] Figure 14 is a diagram for explaining a method for a terminal to receive SIB1 from a cell that operates on-demand SIB1.

[0292] The terminal UE may be an NES UE that supports operations related to the NES of the base station as described above. For example, the UE may distinguish among multiple base stations an NES cell / base station that performs operations related to the NES, and may periodically request transmission of SIB1 and / or SSB to cells / base stations (NES base stations) that have not transmitted SIB1 and / or SSB to save energy of the base station.

[0293] Specifically, referring to FIG. 14, the UE may receive configuration information for at least one resource for requesting transmission of SIB1 (S141). As described above, the UE may receive an SSB of a base station / secondary cell (or an anchor cell), obtain list information of the non-anchor cells that do not periodically transmit SIB1 through the SSB, and obtain the configuration information, which is information on at least one resource (e.g., a WUS resource) for requesting transmission of SIB1 to the non-anchor cells. For example, the UE may obtain / configure configuration information for at least one resource for requesting transmission of SIB1 to a non-anchor cell through the SSB of the anchor cell. Alternatively, as described above, the at least one resource may be at least one RO (Random Access channel Occasion) for PRACH transmission. For example, the configuration information may configure at least one RO on which PRACH is transmitted as a resource for requesting transmission of SIB1.

[0294] Alternatively, the configuration information may include information on the indices of non-anchor cells related to the list information, and may further include a mapping configuration between the indices and the at least one resource. In this case, the UE may specify at least one resource mapped to the index of the first cell among the resources configured for the transmission request of SIB1 through the configuration information.

[0295] Next, the UE may transmit a first signal requesting SIB1 transmission to a first cell (e.g., a non-anchor cell performing the on-demand SIB1 procedure) from the at least one resource (S143). For example, the UE may select one cell, the first cell, based on the signal strength of SSB (e.g., the reception strength of SSB received from each of the at least one non-anchor cell) from among the at least one non-anchor cell based on the list information ('Method 2' described above), or may receive an indication of one cell, the first cell, from an anchor cell / base station ('Method 1' described above). In this case, the UE may transmit a first signal requesting transmission of the SIB1 to the first cell for camp-on to the first cell. Alternatively, as described above, the at least one resource may be configured for at least one RO. In this case, the first signal may be a PRACH or a PRACH preamble. For example, the UE can request transmission of SIB1 from the base station (non-anchor cell) by transmitting a PRACH in at least one RO, which is a resource set to request transmission of SIB1.

[0296] Next, the UE may receive a response signal to the first signal (S145). For example, the UE may transmit a PRACH preamble for a specific RAPID on the at least one resource, and may receive an RAR (or MSG2, MSG4, MSGB) as a response signal containing information about the specific RAPID. For example, the UE may determine / determine that an ACK has been received as a response signal to the first signal when an RAR containing information about the specific RAPID is received.

[0297] Next, the UE may monitor SIB1 for the first cell based on reception of the response signal (S147). For example, the UE may monitor SIB1 for the first cell after a specific time has elapsed from the time of reception of the response signal (or the end time of the window associated with the RAR). For example, the UE may expect that the SIB1 will be received from the first cell after a specific time has elapsed from the time of reception of the response signal. Here, the specific time may be a time set in advance based on the time required for processing, such as decoding, of the RAR of the UE. Alternatively, as described in Method #4, the UE may be configured with multiple CORESETs having different beam directions for each non-anchor cell. In this case, the UE may monitor the SIB1 based on at least one CORESET corresponding to the first cell among the multiple CORESETs. Alternatively, the UE may be configured with a CORESET, SS, or RNTI for monitoring the SIB1 from the response signal. Alternatively, the UE may monitor SIB1 of the first cell using only beams in a beam direction corresponding to the beam direction used for transmitting the first signal.

[0298] FIG. 15 is a diagram for explaining a method for transmitting a requested SIB1 from a first cell operating on-demand SIB1.

[0299] The first cell may be a cell / base station that performs on-demand SIB1 operation, transmitting SIB1 only when requested by a UE, without transmitting periodic SIB1 as described above.

[0300] Referring to FIG. 15, a first cell may receive a first signal requesting transmission of SIB1 from a UE via at least one resource (S151). As described above, the at least one resource for requesting transmission of SIB1 may be configured for the UE via an SSB of a second cell, which is an anchor cell of the first cell. Alternatively, the at least one resource may be configured for at least one RO. In this case, the first signal may include a PRACH or a PRACH preamble for a specific RAPID. For example, the first cell may receive a PRACH requesting transmission of SIB1 from at least one RO.

[0301] Next, the first cell may transmit a response signal to the first signal (S153). For example, the first cell may identify a specific RAPID based on a PRACH preamble received from at least one resource, and transmit an RAR (or MSG2, MSG4, MSGB) as a response signal including the specific RAPID.

[0302] Next, the first cell can transmit the requested SIB1 based on the transmission of the response signal (S155). For example, the first cell can transmit the SIB1 after a specific time has elapsed from the transmission time of the response signal (or the end time of the window related to the RAR). For example, the first cell may not transmit the SIB1 before the specific time has elapsed from the transmission time of the response signal, and may transmit the SIB1 only after the specific time has elapsed. Here, the specific time may be a time set in advance based on the time required for processing, such as decoding of the RAR of the UE. Alternatively, as described in Method #4, the first cell can transmit the SIB1 in at least one CORESET set corresponding to itself among a plurality of CORESETs. Alternatively, the first cell can set a CORESET, SS, or RNTI for monitoring the SIB1 to the UE through the response signal. Alternatively, the first cell may transmit the SIB1 using a beam having a beam direction corresponding to the beam direction used to receive the first signal.

[0303] In this way, the proposed invention can effectively request SIB1 through the existing signaling method without defining a new signaling by clearly defining the SIB1 on-demand procedure based on PRACH and RAR. Alternatively, the proposed invention can effectively obtain the energy saving benefit of the cell based on NES while guaranteeing the maximum cell access opportunity of the terminal through the SIB1 on-demand procedure. Alternatively, the proposed invention can support the transmission of SIB1 at an appropriate timing through the SIB1 on-demand procedure even for cells that do not periodically transmit SIB1 for energy saving based on NES, thereby minimizing the access delay to the said cell as much as possible.

[0304] Examples of communication systems to which the invention applies

[0305] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0306] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0307] Figure 16 illustrates a communication system applied to the present invention.

[0308] Referring to FIG. 16, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

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

[0310] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0311] Examples of wireless devices to which the present invention is applied

[0312] Figure 17 illustrates a wireless device applicable to the present invention.

[0313] Referring to FIG. 17, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 16.

[0314] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0315] Specifically, the first wireless device or terminal (100) may include a processor (102) and a memory (104) connected to a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 11 to 15.

[0316] The processor (102) controls the transceiver (106) to receive configuration information for setting at least one resource related to a SIB1 (System Information Block1) request, transmit a first signal requesting SIB1 transmission to a first cell from the at least one resource, receive a response signal to the first signal, and monitor the SIB1 for the first cell. Here, the monitoring of the SIB1 can be performed based on a reception point of the response signal and a specific time.

[0317] Alternatively, a processing device may be configured that includes a processor (102) controlling a terminal and a memory (104). In this case, at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the terminal to: receive configuration information for setting at least one resource related to a SIB1 (System Information Block 1) request, transmit a first signal requesting SIB1 transmission to a first cell in the at least one resource, receive a response signal to the first signal, and monitor the SIB1 for the first cell. Here, the monitoring of the SIB1 may be performed based on a reception time of the response signal and a specific time.

[0318] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0319] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver or RF transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 11 to 15.

[0320] The processor (202) controls the transceiver (206) to receive a first signal requesting SIB1 transmission from at least one resource related to a SIB1 (System Information Block1) request from a UE (User Equipment), transmit a response signal to the first signal, and transmit the SIB1 based on the transmission time of the response signal and a specific time.

[0321] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, 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, SDAP). 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, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0322] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, 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) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, 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 forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as 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 internally and / or externally 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 technologies, such as wired or wireless connections.

[0324] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected 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. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0325] Examples of wireless devices to which the present invention is applied

[0326] Figure 18 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 16).

[0327] Referring to FIG. 18, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 17 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 18. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 17. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0328] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 16, 100a), a vehicle (Fig. 16, 100b-1, 100b-2), an XR device (Fig. 16, 100c), a portable device (Fig. 16, 100d), a home appliance (Fig. 16, 100e), an IoT device (Fig. 16, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 16, 400), a base station (Fig. 16, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0329] In FIG. 18, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0330] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0331] Figure 19 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

[0332] Referring to FIG. 19, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 18, respectively.

[0333] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward 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) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0334] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0335] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0336] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0337] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0338] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0339] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0340] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0341] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. In the method using UE (User Equipment), A step of receiving configuration information for setting at least one resource related to a SIB1 (System Information Block1) request; A step of transmitting a first signal requesting SIB1 transmission to a first cell from at least one resource; A step of receiving a response signal to the first signal; and A step of monitoring SIB1 for the first cell; A method in which the monitoring of the above SIB1 is performed based on the reception time of the response signal and a specific time.

2. In paragraph 1, A method characterized in that the monitoring of the SIB1 is performed based on the passage of a predetermined time from the time of receiving the response signal.

3. In paragraph 1, wherein at least one of the above resources is at least one RO (Random Access channel Occasion), A method, characterized in that the first signal is a PRACH (Physical Random Access Channel) transmitted based on the at least one RO.

4. In paragraph 3, A method, characterized in that the response signal is a RAR (Random Access Response) that responds to reception of the PRACH.

5. In paragraph 1, The above setting information is obtained through a SSB (Synchronization signal block) received from a second cell different from the first cell, The first cell is a non-anchor cell, and the second cell is an anchor cell, A method characterized in that the first signal is transmitted to the first cell, not the second cell, and the response signal and the SIB1 are received from the first cell.

6. In paragraph 1, A method characterized in that the monitoring of the above SIB1 is performed only in a beam direction corresponding to the beam direction used for transmission of the first signal.

7. In paragraph 1, A method, characterized in that the first cell is a SIB1-less cell that transmits the SIB1 only when the first signal is received.

8. In paragraph 1, The above configuration information further includes list information for at least one cell that requires a request for transmission of the SIB1, A method, characterized in that the first cell is a cell having the highest reception strength of a downlink signal among the at least one cell.

9. In paragraph 8, A method, characterized in that the above setting information further includes mapping information between an index for the at least one cell and the at least one resource.

10. A computer-readable recording medium recording a program for performing the method described in paragraph 1.

11. In UE (User Equipment), RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to receive configuration information for setting at least one resource related to a SIB1 (System Information Block1) request, transmits a first signal requesting SIB1 transmission for a first cell from the at least one resource, receives a response signal for the first signal, and monitors SIB1 for the first cell. The monitoring of the above SIB1 is performed based on the reception time of the response signal and a specific time, UE.

12. In paragraph 11, A UE characterized in that the monitoring of the SIB1 is performed based on the passage of a predetermined time from the time of receiving the response signal.

13. In a processing device that controls UE (User Equipment), at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said UE: Receive configuration information for setting at least one resource related to a SIB1 (System Information Block1) request, transmit a first signal requesting SIB1 transmission to a first cell from the at least one resource, receive a response signal to the first signal, and monitor SIB1 for the first cell. A processing device in which monitoring of the above SIB1 is performed based on the reception time of the response signal and a specific time.

14. In the method by the base station, A step of receiving a first signal requesting SIB1 transmission from at least one resource related to a SIB1 (System Information Block1) request from a UE (User Equipment); a step of transmitting a response signal to the first signal; and A method comprising: a step of transmitting the SIB1 based on the transmission time of the response signal and a specific time; 15. At the base station, RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, A base station, wherein the processor controls the RF transceiver to receive a first signal requesting SIB1 (System Information Block1) transmission from at least one resource related to a SIB1 request from a UE (User Equipment), transmit a response signal to the first signal, and transmit the SIB1 based on a transmission time point of the response signal and a specific time.

Images