Method and device for transmitting or receiving on-demand system information in wireless communication system

Abstract

Provided is a method for communication by a base station providing a network energy saving (NES) cell in a wireless communication system. The method comprises the steps of: receiving a wake-up signal (WUS) for the NES cell; on the basis of receiving the WUS, transmitting an on-demand system information block 1 (SIB1) through the NES cell; and transmitting information indicating whether the on-demand SIB1 is transmitted through the NES cell.

Description

Method and apparatus for transmitting or receiving on-demand system information in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and apparatus for energy saving in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] With the recent development of 5G / 6G communication systems that take the environment into account, there is a growing need for methods to reduce energy consumption or save energy in communication systems (e.g., terminals, base stations, networks, etc.).

[0009] Embodiments of the present disclosure may provide a method and apparatus for reducing energy consumption of a communication system.

[0010] Embodiments of the present disclosure may provide a method and apparatus for operating a network energy saving (NES) cell to reduce energy consumption of a base station.

[0011] Embodiments of the present disclosure may provide a method and apparatus for providing information indicating whether an NES cell transmits an on-demand SIB1 to reduce energy consumption of a terminal.

[0012] According to one embodiment, a method for communication by a base station providing a network energy saving (NES) cell in a wireless communication system is provided. The method may include the steps of: receiving a wake-up signal (WUS) for the NES cell; transmitting an on-demand system information block (SIB1) through the NES cell based on receiving the WUS; and transmitting information indicating whether the on-demand SIB1 is transmitted through the NES cell.

[0013] Information indicating whether the above-mentioned on-demand SIB1 is transmitted can be transmitted via the master information block (MIB).

[0014] The cellBarred information and spare information within the above MIB may indicate whether the on-demand SIB1 is transmitted.

[0015] Information indicating whether the above-mentioned on-demand SIB1 is transmitted can be transmitted via a master information block (MIB) or a combination of the MIB and a physical broadcast channel (PBCH).

[0016] The sub-SubcarrierOffset of the above MIB or the combination of the sub-SubcarrierOffset and 1 bit in the above PBCH represents the value of k_SSB, and the k_SSB having a predetermined value indicates that the on-demand SIB1 is being transmitted, and the k_SSB having a value other than the predetermined value indicates that the on-demand SIB1 is not being transmitted.

[0017] Information indicating whether the above-mentioned on-demand SIB1 is transmitted can be transmitted via L1 (layer 1) signaling.

[0018] When the short message indicator in DCI (downlink control information) format 1_0 is set to "00" or "01", the short message field indicates whether the on-demand SIB1 is transmitted; when the short message indicator is set to "10", at least one of the frequency domain resource assignment field, the time domain resource assignment field, the VRB-to-PRB (virtual resource block-to-physical resource block) mapping field, the MCS (modulation and coding scheme) field, and the TB (transport block) scaling field indicates whether the on-demand SIB1 is transmitted; and when the short message indicator is set to "11", at least one bit of the TRS (tracking reference signal) availability or a reserved bit may indicate whether the on-demand SIB1 is transmitted.

[0019] The above-mentioned on-demand SIB1 can be transmitted for a predetermined period or a predetermined number of times.

[0020] The above method may further include the step of stopping the transmission of the on-demand SIB1; the step of switching from NES mode to normal mode after stopping the transmission of the on-demand SIB1; and the step of periodically transmitting the SIB1 in the normal mode.

[0021] Information indicating whether the above-mentioned on-demand SIB1 is transmitted may indicate that the above-mentioned on-demand SIB1 is not transmitted, thereby indicating that the above-mentioned periodic SIB1 is transmitted.

[0022] A base station providing a network energy saving (NES) cell in a wireless communication system may be provided. The base station may include a transceiver; and at least one processor. The at least one processor may be configured to receive a wake-up signal (WUS) for the NES cell; transmit an on-demand system information block 1 (SIB1) through the NES cell based on receiving the WUS; and transmit information indicating whether the on-demand SIB1 is transmitted through the NES cell.

[0023] FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource domain in a wireless communication system according to one embodiment of the present disclosure.

[0024] FIG. 2 illustrates a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.

[0025] FIG. 3 illustrates an example of a time domain mapping structure of a synchronization signal and a beam sweeping operation according to one embodiment of the present disclosure.

[0026] FIG. 4 illustrates a synchronization signal block considered in a wireless communication system according to one embodiment of the present disclosure.

[0027] FIG. 5 illustrates various transmission cases of a synchronization signal block in a frequency band below 6 GHz considered in a wireless communication system according to one embodiment of the present disclosure.

[0028] FIG. 6 illustrates transmission cases of a synchronization signal block in a frequency band of 6 GHz or higher considered in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 7 illustrates transmission cases of a synchronization signal block according to a subcarrier interval within 5ms in a wireless communication system according to one embodiment of the present disclosure.

[0030] FIG. 8 illustrates an example explaining DMRS (demodulation reference signal) patterns (type 1 and type 2) used for communication between a base station and a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 9 illustrates an example of channel estimation using DMRS received from a single PUSCH (physical uplink shared channel) in the time band of a wireless communication system according to one embodiment of the present disclosure.

[0032] FIG. 10 illustrates a method for resetting SSB transmission through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 11 illustrates a method for resetting BWP (bandwidth part) and BW (bandwidth) through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0034] FIG. 12 illustrates a method for resetting a discontinuous reception (DRX) through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0035] FIG. 13 illustrates an example explaining a DTx (discontinuous transmission) method for base station energy saving according to one embodiment of the present disclosure.

[0036] FIG. 14 illustrates an example explaining the operation of a base station according to a gNB wake-up signal according to one embodiment of the present disclosure.

[0037] FIG. 15 illustrates an antenna adaptation method for a base station for energy saving of a wireless communication system according to one embodiment of the present disclosure.

[0038] FIG. 16 is a diagram illustrating an example of an On-demand SIB1 operation considering multiple cells of a base station and a terminal according to an embodiment of the present disclosure.

[0039] FIG. 17 is a diagram illustrating an example of an On-demand SIB1 operation considering a single cell of a base station and a terminal according to an embodiment of the present disclosure.

[0040] FIG. 18 is a drawing illustrating an example of a downstream channel for scheduling an On-demand SIB1 according to one embodiment of the present disclosure.

[0041] FIG. 19 is a drawing illustrating another example of a downstream channel for scheduling an On-demand SIB1 according to one embodiment of the present disclosure.

[0042] FIG. 20 is a flowchart of terminal operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.

[0043] FIG. 21 is a flowchart of base station operations applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.

[0044] FIG. 22 is a block diagram of a terminal according to one embodiment of the present disclosure.

[0045] FIG. 23 is a block diagram of a base station according to one embodiment of the present disclosure.

[0046] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0047] In describing the embodiments of the present disclosure below, technical details that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure are omitted. This is intended to convey the essence of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0048] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0049] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments described below but may be implemented in various different forms. These embodiments are provided merely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the technical concept to which the present disclosure pertains, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the present specification.

[0050] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station.

[0051] In addition, while LTE or LTE-A systems may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0052] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0053] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0054] As used in this disclosure, the term “part” refers to a software or hardware component, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the “part” performs certain roles. However, the “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and '~parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiment, the '~part' may include one or more processors.

[0055] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each specific embodiment, and may also be utilized as a combination of all or part of one or more embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope of the present disclosure without significantly departing from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0056] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as 3GPP’s HSPA (high speed packet access), LTE (long term evolution or E-UTRA (evolved universal terrestrial radio access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2’s HRPD (high rate packet data), UMB (ultra mobile broadband), and IEEE’s 802.17e communication standards.

[0057] In the LTE system, a representative example of a broadband wireless communication system, the downlink (DL) employs the orthogonal frequency division multiplexing (OFDM) method, and the uplink (UL) employs the single carrier frequency division multiple access (SC-FDMA) method. The uplink refers to a wireless link through which a terminal (hereinafter referred to as user equipment (UE) or terminal) (or mobile station (MS)) transmits data or control signals to a base station (eNode B (eNB) or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal (UE). Furthermore, the aforementioned multiple access method typically ensures that the time-frequency resources to be used to transmit data or control information for each user do not overlap, that is, that orthogonality is established, thereby allowing the data or control information of each user to be distinguished.

[0058] 5G communication systems, which are communication systems following LTE, must support services that simultaneously satisfy various requirements so as to freely reflect the diverse needs of users and service providers. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra reliability low latency communication (URLC).

[0059] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing the peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, improvements in various transmission and reception technologies, including enhanced multi-input multi-output (MIMO) transmission technology, may be required. Additionally, while LTE systems transmit signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission speeds required by the 5G communication system by using a frequency bandwidth wider than 20 MHz in frequency bands of 3 to 6 GHz or above 6 GHz.

[0060] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for the connection of a large number of terminals within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT provides communication functions by attaching various sensors and diverse devices, a large number of terminals (e.g., 1,000,000 terminals / km²) are required within a cell. 2 It must be able to support mMTC. In addition, terminals supporting mMTC require wider coverage compared to other services provided by the 5G communication system, as they are likely to be located in dead zones where cells cannot cover, such as building basements, due to the nature of the service. Terminals supporting mMTC must be low-cost devices, and because it is difficult to frequently replace the device's battery, they require a very long battery life of 10 to 16 years.

[0061] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, or emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For example, services supporting URLLC must satisfy air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements must be satisfied. Therefore, for services supporting URLLC, 5G systems must provide a transmit time interval (TTI) smaller than other services, and at the same time, allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0062] Three services of a 5G communication system (hereinafter interchangeable with 5G systems), namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. To satisfy the different requirements of each service, different transmission and reception techniques and transmission and reception parameters may be used between the services.

[0063] The frame structure of a 5G system will be described in more detail below with reference to the drawings. For convenience of explanation, the wireless communication system to which the present disclosure applies will be described below using the configuration of a 5G system as an example; however, the embodiments of the present disclosure may be applied in the same or similar manner to systems of 5G or higher or other communication systems to which the present disclosure is applicable.

[0064] FIG. 1 illustrates the basic structure of the time-frequency domain, which is a wireless resource domain in a wireless communication system according to one embodiment of the present disclosure.

[0065] In FIG. 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM (orthogonal frequency division multiplexing) symbol (or DFT-s-OFDM (discrete Fourier transform spread OFDM) symbol) (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain, the number of subcarriers per resource block (RB) is indicated. (For example, 12) consecutive REs can constitute a single resource block (RB, 104). Additionally, representing the number of symbols per subframe according to the set value μ for subcarrier spacing in the time domain. A number of consecutive OFDM symbols can form a subframe (110).

[0066] FIG. 2 illustrates a slot structure considered in a wireless communication system according to one embodiment of the present disclosure.

[0067] FIG. 2 illustrates an example of a slot structure comprising a frame (200), a subframe (201), and slots (202, 203). One frame (200) may be defined as 10 ms. One subframe (201) may be defined as 1 ms, and thus one frame (200) may consist of a total of 10 subframes (201). One slot (202, 203) may be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( ))=14). One subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per one subframe (201) may vary depending on μ (204 or 205), which is a setting value for the subcarrier space (SCS).

[0068] The slot structure for cases where the subcarrier spacing setting value is μ=0 (204) and μ=1 (205) is illustrated. When μ=0 (204), one subframe (201) may be composed of one slot (202), and when μ=1 (205), one subframe (201) may be composed of two slots (e.g., including slot (203)). That is, depending on the setting value μ for the subcarrier spacing, the number of slots per subframe ( )) may vary, and accordingly, the number of slots per frame ( ) may vary. For example, depending on the setting μ for each subcarrier interval. and It can be defined by the following [Table 1].

[0069] μ 014101114202214404314808414160165143203261464064

[0070] In a 5G wireless communication system, a synchronization signal block (SSB, which may be used interchangeably with SS block or SS / PBCH block) may be transmitted for the initial connection of a terminal, and the synchronization signal block may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). In the initial access phase where the terminal connects to the system, the terminal can first obtain downlink time and frequency domain synchronization from the synchronization signal through a cell search and obtain a cell ID. The synchronization signal may include the PSS and SSS. Then, the terminal can receive a PBCH transmitting a master information block (MIB) from the base station to obtain system information related to transmission and reception, such as system bandwidth or related control information, and basic parameter values. Based on this information, the terminal [transmits] to the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH). The system information block (SIB) can be obtained by performing decoding. Subsequently, the terminal can exchange identification information with the base station through a random access step and establish initial network access by undergoing registration and authentication steps. Additionally, the terminal can obtain cell-common transmission and reception control information by receiving the system information block (SIB) transmitted by the base station.The above cell common transmission and reception control information may include random access control information, paging control information, and common control information for various physical channels.

[0071] The synchronization signal serves as a reference for cell search, and subcarrier spacing can be applied for each frequency band to suit channel environments such as phase noise. In the case of data channels or control channels, as described above, subcarrier spacing may be applied differently depending on the service type to support various services.

[0072] FIG. 3 illustrates an example of a time domain mapping structure of a synchronization signal and a beam sweeping operation according to one embodiment of the present disclosure.

[0073] For the purpose of explanation, the following components may be defined.

[0074] - PSS: Provides some cell ID information as a reference signal for DL ​​time / frequency synchronization.

[0075] - SSS: Serves as a reference for DL ​​time / frequency synchronization and provides the cell ID and some other information. Additionally, it can serve as a reference signal for PBCH demodulation.

[0076] - PBCH: Provides MIB, which is essential system information required for transmitting and receiving data channels and control channels of the terminal. The essential system information may include search space-related control information representing wireless resource mapping information of the control channel, scheduling control information for a separate data channel that transmits system information, and information such as SFN (system frame number), which is a frame-unit index that serves as a timing reference.

[0077] - SS / PBCH Block (Synchronization Signal / PBCH Block or SSB): An SS / PBCH block consists of N OFDM symbols and is formed by a combination of PSS, SSS, PBCH, etc. In systems where beam sweeping technology is applied, the SS / PBCH block is the minimum unit to which beam sweeping is applied. In a 5G system, N can be 4. A base station can transmit up to L SS / PBCH blocks, and the L SS / PBCH blocks are mapped within a half frame (0.5ms). The L SS / PBCH blocks are repeated periodically in units of a predetermined period P. The base station can notify the terminal of the period P through signaling. If there is no separate signaling for the period P, the terminal applies a pre-agreed default value.

[0078] Referring to FIG. 3, beam sweeping can be applied in units of SS / PBCH blocks over time. In the case of Terminal 1 (305), at time t1 (301), it receives an SS / PBCH block using a beam radiated in the direction of #d0 (303) by beamforming applied to SS / PBCH block #0. Then, at time t2 (302), Terminal 2 (306) receives an SS / PBCH block using a beam radiated in the direction of #d4 (304) by beamforming applied to SS / PBCH block #4. The terminal can obtain an optimal synchronization signal through a beam radiated from the base station in the direction where the terminal is located. For example, it may be difficult for Terminal 1 (305) to obtain time / frequency synchronization and essential system information from an SS / PBCH block through a beam radiated in the direction of #d4 (304), which is far from the location of Terminal 1 (305).

[0079] In addition to the initial connection procedure, the terminal may also receive SS / PBCH blocks to determine whether the radio link quality of the current cell is maintained above a certain level. Furthermore, during the handover procedure in which the terminal moves the connection from the current cell to an adjacent cell, the terminal may receive SS / PBCH blocks of the adjacent cell to determine the radio link quality of the adjacent cell and to obtain time / frequency synchronization with the adjacent cell.

[0080] Below, the cell initial connection operation procedure of a 5G wireless communication system will be explained in more detail with reference to the drawings.

[0081] Synchronization signals serve as reference signals for cell search and can be transmitted with subcarrier spacing applied to suit the channel environment (e.g., phase noise) for each frequency band. 5G base stations can transmit multiple synchronization signal blocks depending on the number of analog beams to be operated. For example, PSS and SSS can be mapped and transmitted across 12 RBs, while PBCH can be mapped and transmitted across 24 RBs. The structure of synchronization signal and PBCH transmission in a 5G communication system is described below.

[0082] FIG. 4 illustrates a synchronization signal block considered in a wireless communication system according to one embodiment of the present disclosure.

[0083] Referring to FIG. 4, the synchronization signal block (SS block, SSB) (400) may include PSS (401), SSS (403), and PBCH (402).

[0084] The synchronization signal block (400) can be mapped to four OFDM symbols (404) in the time axis. The PSS (401) and SSS (403) can be transmitted at 12 RB (405) in the frequency axis and at the first and third OFDM symbols in the time axis, respectively. In a 5G system, for example, a total of 1008 different cell IDs can be defined. Depending on the physical cell ID (PCI) of the cell, the PSS (401) can have three different values, and the SSS (403) can have 336 different values. The terminal can obtain one of the 1008 cell IDs (336 x 3 = 1008) as a combination through detection of the PSS (401) and SSS (403). This can be expressed by the following [Equation 1].

[0085]

[0086] Here can be estimated from SSS(403) and can have a value between 0 and 335. can be estimated from PSS (401) and can have a value between 0 and 2. The terminal class The cell ID is a combination of The value can be estimated.

[0087] PBCH (402) can be transmitted from a resource containing 6 RBs (407, 408) on each side excluding 12 RBs (405), with 24 RBs (406) in the frequency axis and SSS (403) in the 2nd to 4th OFDM symbols of the SS block in the time axis being transmitted. PBCH (402) may include a PBCH payload and a PBCH DMRS, and various system information called MIB may be transmitted in the PBCH payload. For example, the MIB may include information such as that in [Table 2] below.

[0088] MIB ::= SEQUENCE {systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffset INTEGER (0..15),dmrs-TypeA-Position ENUMERATED {pos2, pos3},pdcch-ConfigSIB1 PDCCH-ConfigSIB1,cellBarred ENUMERATED {barred, notBarred},intraFreqReselection ENUMERATED {allowed, notAllowed},spare BIT STRING (SIZE (1))}

[0089] - Synchronization signal block information: The frequency domain offset of the synchronization signal block can be indicated through the 4-bit ssb-SubcarrierOffset within the MIB. The index of the synchronization signal block containing the PBCH can be obtained indirectly through PBCH DMRS and decoding of the PBCH. In one embodiment, in a frequency band below 6 GHz, 3 bits obtained through decoding of the PBCH DMRS indicate the synchronization signal block index, and in a frequency band above 6 GHz, a total of 6 bits, including 3 bits obtained through decoding of the PBCH DMRS and 3 bits included in the PBCH payload obtained from PBCH decoding, can indicate the synchronization signal block index containing the PBCH.

[0090] - PDCCH (physical downlink control channel) configuration information: The subcarrier spacing of the common downlink control channel can be indicated via a 1-bit (subCarrierSpacingCommon) within the MIB, and the time-frequency resource configuration information of the CORESET (control resource set) and search space (SS) of Identifier (ID) 0 can be indicated via an 8-bit (pdcch-ConfigSIB1). The CORESET of Identifier 0 can be referred to as controlResourceSetZero, and the search space of Identifier 0 can be referred to as searchspaceZero. In this disclosure, for convenience, the CORESET of Identifier 0 will be referred to as CORESET#0 or control space#0, and the search space of Identifier 0 will be referred to as search space#0. During the initial connection of the cell, the terminal can receive frequency resources indicating the number of RBs of CORESET#0, which includes the common search space set of Type0-PDCCH CSS set, and time resources indicating the number of OFDM symbols, etc., from the pdcch-ConfigSIB1.

[0091] - SFN (system frame number): Within the MIB, 6 bits (systemFrameNumber) can be used to indicate part of the SFN. The 4 bits of the SFN's LSB (Least Significant Bit) are included in the PBCH payload, and the terminal can obtain them indirectly through PBCH decoding.

[0092] - Timing information within a radio frame: With the synchronization signal block index described above and the 1-bit (half frame) obtained through PBCH decoding included in the PBCH payload, the terminal can indirectly check whether the synchronization signal block was transmitted in the first or second half frame of the radio frame.

[0093] Since the transmission bandwidth (12 RB (405)) of PSS (401) and SSS (403) and the transmission bandwidth (24 RB (406)) of PBCH (402) are different, in the first OFDM symbol where PSS (401) is transmitted within the transmission bandwidth of PBCH (402), there are 6 RBs (407, 408) on both sides excluding the 12 RB in the middle where PSS (401) is transmitted, and the area may be used to transmit other signals or be empty.

[0094] - Cell connection permission information: A 1-bit (cellBarred) within the MIB may indicate whether camping to a cell is permitted. Additionally, if camping to the cell with the best reception quality is prohibited (barred), a 1-bit (intraFreqReselection) within the MIB may indicate whether cell reselection to an intra-frequency cell is permitted.

[0095] Synchronization signal blocks can be transmitted using the same analog beam. For example, PSS (401), SSS (403), and PBCH (402) can all be transmitted on the same beam. Since analog beams have the characteristic that they cannot be applied differently in the frequency axis, the same analog beam can be applied to all frequency axis RBs within a specific OFDM symbol to which a specific analog beam is applied. For example, four OFDM symbols in which PSS (401), SSS (403), and PBCH (402) are transmitted can all be transmitted on the same analog beam.

[0096] FIG. 5 illustrates various transmission cases of a synchronization signal block in a frequency band below 6 GHz considered in a wireless communication system according to one embodiment of the present disclosure.

[0097] Referring to FIG. 5, in a 5G communication system, in a frequency band of 6 GHz or lower (or FR1 (frequency range 1), e.g., 410 MHz-7125 MHz), a subcarrier spacing (SCS) of 15 kHz (520) and a subcarrier spacing (SCS) of 30 kHz (530, 540) may be used for the transmission of a synchronization signal block. In the 15 kHz subcarrier spacing (520), there is one transmission case for the synchronization signal block (e.g., Case #1 (501)), and in the 30 kHz subcarrier spacing (530, 540), there may be two transmission cases for the synchronization signal block (e.g., Case #2 (502) and Case #3 (503)).

[0098] In case #1 (501) at a subcarrier interval of 15 kHz (520) in FIG. 5, up to two synchronization signal blocks can be transmitted within a time of 1 ms (504) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols). In an example of FIG. 5, synchronization signal block #0 (507) and synchronization signal block #1 (508) are shown. For example, synchronization signal block #0 (507) can be mapped to four consecutive symbols starting from the 3rd OFDM symbol, and synchronization signal block #1 (508) can be mapped to four consecutive symbols starting from the 9th OFDM symbol.

[0099] Different analog beams may be applied to synchronization signal block #0 (507) and synchronization signal block #1 (508). Also, the same beam may be applied to all 3rd to 6th OFDM symbols mapped to synchronization signal block #0 (507), and the same beam may be applied to all 9th ​​to 12th OFDM symbols mapped to synchronization signal block #1 (508). For the 7th, 8th, 13th, and 14th OFDM symbols that are not mapped to synchronization signal blocks, the analog beam to be used may be freely determined at the discretion of the base station.

[0100] In case #2 (502) at a subcarrier interval of 30 kHz (530) in FIG. 5, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (505) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, up to four synchronization signal blocks can be transmitted within a time of 1 ms (or corresponding to the length of two slots if one slot consists of 14 OFDM symbols). In one example of FIG. 5, a case is illustrated in which synchronization signal block #0 (509), synchronization signal block #1 (510), synchronization signal block #2 (511), and synchronization signal block #3 (512) are transmitted within a time of 1 ms (i.e., two slots). Synchronization signal block #0 (509) and synchronization signal block #1 (510) can be mapped starting from the 5th OFDM symbol and 9th OFDM symbol of the first slot, respectively, and synchronization signal block #2 (511) and synchronization signal block #3 (512) can be mapped starting from the 3rd OFDM symbol and 7th OFDM symbol of the second slot, respectively.

[0101] Different analog beams may be applied to each of the synchronization signal block #0 (509), synchronization signal block #1 (510), synchronization signal block #2 (511), and synchronization signal block #3 (512). Additionally, the same analog beam may be applied to each of the 5th to 8th OFDM symbols in the first slot where synchronization signal block #0 (509) is transmitted, the 9th to 12th OFDM symbols in the first slot where synchronization signal block #1 (510) is transmitted, the 3rd to 6th symbols in the second slot where synchronization signal block #2 (511) is transmitted, and the 7th to 10th symbols in the second slot where synchronization signal block #3 (512) is transmitted. For OFDM symbols where the synchronization signal block is not mapped, the analog beam to be used may be freely determined at the discretion of the base station.

[0102] In case #3 (503) at a subcarrier interval of 30 kHz (540) in FIG. 5, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (506) (or corresponding to the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, up to four synchronization signal blocks can be transmitted within a time of 1 ms (or corresponding to the length of two slots if one slot consists of 14 OFDM symbols). In one example of FIG. 5, synchronization signal block #0 (513), synchronization signal block #1 (514), synchronization signal block #2 (515), and synchronization signal block #3 (516) are shown being transmitted within a time of 1 ms (i.e., two slots). Synchronization signal block #0 (513) and synchronization signal block #1 (514) can be mapped starting from the 3rd OFDM symbol and 9th OFDM symbol of the first slot, respectively, and synchronization signal block #2 (515) and synchronization signal block #3 (516) can be mapped starting from the 3rd OFDM symbol and 9th OFDM symbol of the second slot, respectively.

[0103] Different analog beams may be used for each of the synchronization signal block #0 (513), synchronization signal block #1 (514), synchronization signal block #2 (515), and synchronization signal block #3 (516). As described in the examples above, the same analog beam may be used for all four OFDM symbols in which each synchronization signal block is transmitted, and for OFDM symbols in which the synchronization signal block is not mapped, the choice of which beam to use may be freely determined by the base station.

[0104] FIG. 6 illustrates transmission cases of a synchronization signal block in a frequency band of 6 GHz or higher considered in a wireless communication system according to one embodiment of the present disclosure.

[0105] Referring to FIG. 6, in a wireless communication system, in a frequency band of 6 GHz or higher (or FR2, e.g., 24250 MHz-52000 MHz), a subcarrier spacing of 120 kHz (630), as in the example of Case #4 (610), and a subcarrier spacing of 240 kHz (640), as in the example of Case #5 (620), can be used for the transmission of synchronization signal blocks.

[0106] In case #4 (610) of a subcarrier interval of 120 kHz (630), up to four synchronization signal blocks can be transmitted within a time of 0.25 ms (601) (or, if one slot consists of 14 OFDM symbols, the length of two slots). In an example of FIG. 6, a case is illustrated in which synchronization signal block #0 (603), synchronization signal block #1 (604), synchronization signal block #2 (605), and synchronization signal block #3 (606) are transmitted within 0.25 ms (i.e., two slots). Synchronization signal block #0 (603) and synchronization signal block #1 (604) can each be mapped to four consecutive symbols starting from the 5th OFDM symbol of the first slot and to four consecutive symbols starting from the 9th OFDM symbol, and synchronization signal block #2 (605) and synchronization signal block #3 (606) can each be mapped to four consecutive symbols starting from the 3rd OFDM symbol of the second slot and to four consecutive symbols starting from the 7th OFDM symbol.

[0107] As described in the above embodiment, different analog beams may be used for each of the synchronization signal block #0 (603), synchronization signal block #1 (604), synchronization signal block #2 (605), and synchronization signal block #3 (606). In addition, the same analog beam may be used for all four OFDM symbols transmitted by each synchronization signal block, and for OFDM symbols that are not mapped to the synchronization signal block, the choice of which beam to use may be freely determined by the base station.

[0108] In case #5 (620) at a subcarrier interval of 240 kHz (640), up to 8 synchronization signal blocks can be transmitted within a time of 0.25 ms (602) (or corresponding to a length of 4 slots if 1 slot consists of 14 OFDM symbols). In an example of FIG. 6, a case is illustrated in which synchronization signal block #0 (607), synchronization signal block #1 (608), synchronization signal block #2 (609), synchronization signal block #3 (610), synchronization signal block #4 (611), synchronization signal block #5 (612), synchronization signal block #6 (613), and synchronization signal block #7 (614) are transmitted within 0.25 ms (i.e., 4 slots).

[0109] Synchronization signal block #0 (607) and synchronization signal block #1 (608) can each be mapped to four consecutive symbols starting from the 9th OFDM symbol of the first slot and to four consecutive symbols starting from the 13th OFDM symbol, and synchronization signal block #2 (609) and synchronization signal block #3 (610) can each be mapped to four consecutive symbols starting from the 3rd OFDM symbol of the second slot and to four consecutive symbols starting from the 7th OFDM symbol, and synchronization signal block #4 (611), synchronization signal block #5 (612), and synchronization signal block #6 (613) can each be mapped to four consecutive symbols starting from the 5th OFDM symbol of the third slot, to four consecutive symbols starting from the 9th OFDM symbol and to four consecutive symbols starting from the 13th OFDM symbol, and synchronization signal block #7 (614) can be mapped to the 3rd OFDM symbol of the fourth slot It can be mapped to four consecutive symbols starting from the symbol.

[0110] As described in the above embodiment, different analog beams may be used for each of the synchronization signal block #0 (607), synchronization signal block #1 (608), synchronization signal block #2 (609), synchronization signal block #3 (610), synchronization signal block #4 (611), synchronization signal block #5 (612), synchronization signal block #6 (613), and synchronization signal block #7 (614). In addition, the same analog beam may be used for all four OFDM symbols transmitted by each synchronization signal block, and for OFDM symbols that are not mapped to the synchronization signal block, the choice of which beam to use may be freely determined by the base station.

[0111] FIG. 7 illustrates transmission cases of a synchronization signal block according to a subcarrier interval within 5ms in a wireless communication system according to one embodiment of the present disclosure.

[0112] Referring to FIG. 7, in a 5G communication system, a synchronization signal block can be transmitted periodically in units of, for example, a time interval (710) of 5 ms (corresponding to 5 subframes or half frames).

[0113] In the frequency band below 3 GHz, up to 4 synchronization signal blocks can be transmitted within a time of 5 ms (710). In the frequency band between 3 GHz and 6 GHz, up to 8 synchronization signal blocks can be transmitted. In the frequency band above 6 GHz, up to 64 synchronization signal blocks can be transmitted. As described above, subcarrier spacings of 15 kHz and 30 kHz can be used in frequencies below 6 GHz.

[0114] In the example of FIG. 7, in case #1 (501) with a subcarrier interval of 15 kHz consisting of one slot of FIG. 5, a synchronization signal block can be mapped to the first and second slots in the frequency band below 3 GHz, allowing up to 4 (721) to be transmitted, and in the frequency band above 3 GHz and below 6 GHz, a synchronization signal block can be mapped to the first, second, third, and fourth slots, allowing up to 8 (722) to be transmitted. In case #2 (502) or case #3 (503) with a subcarrier interval of 30 kHz consisting of two slots of FIG. 5, a synchronization signal block can be mapped starting from the first slot in the frequency band below 3 GHz, allowing up to 4 (731, 741) to be transmitted, and in the frequency band above 3 GHz and below 6 GHz, a synchronization signal block can be mapped starting from the first and third slots, allowing up to 8 (732, 742) to be transmitted.

[0115] Subcarrier spacing of 120 kHz and 240 kHz can be used at frequencies above 6 GHz. In the example of FIG. 7, in case #4 (610) at a subcarrier spacing of 120 kHz consisting of two slots of FIG. 6, synchronization signal blocks in the frequency band above 6 GHz can be mapped starting from the 1st, 3rd, 5th, 7th, 11th, 13th, 15th, 17th, 21st, 23rd, 25th, 27th, 31st, 33rd, 35th, and 37th slots, so that up to 64 (751) can be transmitted. In the example of FIG. 7, in case #5 (620) at a subcarrier interval of 240 kHz consisting of 4 slots of FIG. 6, synchronization signal blocks in the over 6 GHz frequency band can be mapped starting from the 1st, 5th, 9th, 13th, 21st, 25th, 29th, and 33rd slots, so that up to 64 (761) can be transmitted.

[0116] The terminal can obtain SIB1 or SIBx (all SIBs excluding SIB1) after performing decoding of PDCCH and PDSCH based on system information contained in the received MIB. SIB1 may include at least one of uplink cell bandwidth-related information, random access parameters, paging parameters, or parameters related to uplink power control.

[0117] Generally, a terminal can establish a wireless link with a network through a random access procedure based on network synchronization and system information acquired during the cell's cell search process. Random access may utilize contention-based or contention-free methods. When a terminal performs cell selection and re-selection during the initial connection phase of a cell, a contention-based random access method may be used, for example, to transition from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access may be used to reset uplink synchronization when downlink data arrives, in the case of a handover, or for location measurement. Table 3 below illustrates the conditions (events) under which the random access procedure is triggered in a 5G system.

[0118] - Initial access from RRC_IDLE;- RRC Connection Re-establishment procedure;- DL or UL data arrival during RRC_CONNECTED when UL synchronization status is "non-synchronised";- UL data arrival during RRC_CONNECTED when there are no PUCCH resources for SR available;- SR failure;- Request by RRC upon synchronous reconfiguration (eg handover);- RRC Connection Resume procedure from RRC_INACTIVE;- To establish time alignment for a secondary TAG;- Request for Other SI;- Beam failure recovery;- Consistent UL LBT failure on SpCell.

[0119] Next, we will explain in detail the Bandwidth Part (BWP) settings in a 5G communication system. In a 5G communication system, the base station can set one or more Bandwidth Parts for the terminal, and for each Bandwidth Part, it can set the information included in [Table 4] below.

[0120] BWP ::= SEQUENCE {bwp-Id BWP-Id,locationAndBandwidth INTEGER (1..65536),subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},cyclicPrefix ENUMERATED { extended}}

[0121] In Table 4, bwp-Id represents the bandwidth portion identifier, locationAndBandwidth represents the bandwidth portion location, subcarrierSpacing represents the subcarrier spacing, and cyclicPrefix represents the cyclic prefix. In addition to the above configuration information, various parameters related to the bandwidth portion may be configured for the terminal. The above information may be transmitted from the base station to the terminal via higher-layer signaling, such as RRC signaling. Among the configured one or more bandwidth portions, at least one bandwidth portion may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via DCI (downlink control information). Prior to an RRC connection, the terminal may receive an Initial BWP for initial connection from the base station via MIB or SIB1 (System Information Block 1).

[0122] To explain specifically regarding the settings for Control Area #0, Search Area #0, and the initial bandwidth portion, the terminal can receive setting information for Control Area #0 and Search Area #0, through the MIB during the initial connection phase, to which a PDCCH can be transmitted for receiving remaining system information (RMSI or SIB 1) required for initial connection. The Control Area and Search Area configured by the MIB can each be considered as Identity (ID) 0. The base station can notify the terminal of setting information, such as frequency allocation information, time allocation information, and numerology, for Control Area #0 through the MIB. Additionally, the base station can notify the terminal of setting information regarding the monitoring period and occasion for Control Area #0, i.e., setting information for Search Area #0, through the MIB.

[0123] In the method for setting the initial bandwidth portion described above, terminals prior to RRC connection (Connected) can receive configuration information regarding the initial bandwidth portion through the MIB during the initial connection phase. More specifically, the terminal can receive a control area (CORESET) from the PBCH MIB for a downlink control channel through which a DCI for scheduling SIBs can be transmitted. The bandwidth of the control area set by the MIB can be considered as the initial bandwidth portion, and through the configured initial bandwidth portion, the terminal can receive the PDSCH through which SIBs are transmitted. In addition to receiving SIBs, the initial bandwidth portion may also be utilized for other system information (OSI), paging, and random access.

[0124] The following describes a method for setting measurement times for RRM (radio resource management) based on synchronization signal blocks (SS block or SSB) of a 5G wireless communication system.

[0125] The terminal receives the MeasObjectNR of MeasObjectToAddModList as a setting for SSB-based intra / inter-frequency measurements and CSI-RS (channel state information-reference signal)-based intra / inter-frequency measurements through upper layer signaling. For example, MeasObjectNR can be configured as shown in [Table 5] below.

[0126] MeasObjectNR ::= SEQUENCE {ssbFreqeuncy ARFCN-ValueNROPTIONAL --Cond SSBorAssociatedSSBssbSubCarrierSpacing SubcarrierSpacingOPTIONAL, -- Cond SSBorAssociatedSSBsmtc1 SSB-MTCOPTIONAL, -- Cond SSBorAssociatedSSBsmtc2 SSB-MTC2OPTIONAL, --Cond IntraFreqConnectedrefFreqCSI-RS ARFCN-ValueNROPTIONAL, -- Cond CSI-RSreferenceSignalConfig ReferenceSignalConfig,absThreshSS-BlocksConsolidation ThresholdNROPTIONAL, -- Need RabsThreshCSI-RS-Consolidataion ThresholdNROPTIONAL, -- Need RnrofSS-BlocksToAverage INTEGER (2 ... maxNrofSS-BlocksToAverage)OPTIONAL, --Need RnrofCSI-RS-ResourcesToAverage INTEGER (2 ... maxNrofCSI-RS-ResourcesToAverage)OPTIONAL, -- Need RquantityConfigIndex INTEGER (1 ... maxNrofQuantityConfig),offsetMO Q-OffsetRangeList,cellsToRemoveList PCI-ListOPTIONAL, -- Need NcellsToaddModList CellsToaddModListOPTIONAL, -- Need NblackCellsToRemoveList PCI-RangeIndexListOPTIONAL, -- Need NblackCellsToAddModList SEQUENCE (SIZE (1 ..maxNRofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NwhiteCellsToRemoveList PCI-RangeIndexListOPTIONAL, -- Need NwhiteCellsToAddModList SEQUENCE (SIZE (1 .. maxNRofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N...,[[freqBandIndicatorNR FreqBandIndicatorNROPTIONAL, -- Need RmeasCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL, -- Need R]],[[smtc3list-r16 SSB-MTC3List-r16OPTIONAL, -- Need Rrmtc-Config-16 SetupRelease {RMTC-Config-r16}OPTIONAL, -- Need Mt312-r16 SetupRelease { T312-r16}OPTIONAL, -- Need M]]}.

[0127] The terms in [Table 5] may perform the following functions, but are not limited thereto.

[0128] -ssbFrequency: You can set the frequency of the synchronization signal associated with MeasObjectNR.

[0129] -ssbSubcarrierSpacing: Sets the subcarrier spacing of the SSB. FR1 can only be applied to 15 kHz or 30 kHz, and FR2 to 120 kHz or 240 kHz.

[0130] -smtc1: Represents the SS / PBCH block measurement timing configuration. It allows you to set the primary measurement timing configuration and configure the timing offset and duration for the SSB.

[0131] You can configure the secondary measurement timing configuration for the SSB associated with the MeasObjectNR having the PCI listed in -smtc2:pci-List.

[0132] In addition to this, it can be configured through other higher-level signaling, for example, SMTC can be configured to the terminal through reconfigurationWithSync for intra-frequency, inter-frequency, and inter-RAT cell reselection, or for changing NR PSCell (primary secondary cell) and NR PCell (primary cell), and SMTC can also be configured to the terminal through SCellConfig for adding NR SCell (secondary cell).

[0133] The terminal can set the first SS / PBCH block measurement timing configuration (SMTC) according to periodicityAndOffset (providing Periodicity and Offset) through smtc1 configured via upper layer signaling for SSB measurement. In one embodiment, the first subframe of each SMTC occasion can be started in a subframe of a system frame number (SFN) and SpCell (special cell) satisfying the conditions of [Table 6] below.

[0134] SFN modT= (FLOOR (Offset / 10));if thePeriodicityis larger thansf5:subframe =Offsetmod 10;else:subframe =Offsetor (Offset+5);withT= CEIL(Periodicity / 10).

[0135] If smtc2 is configured, for the cells indicated by the pci-List value of smtc2 within the same MeasObjectNR, the terminal may configure additional SMTCs according to the periodicity of the configured smtc2 and the offset and duration of smtc1. In addition, the terminal may configure smtc and measure SSBs through smtc3list for smtc2-LP (with long periodicity) and IAB-MT (integrated access and backhaul - mobile termination) for the same frequency (e.g., a frequency for intra-frequency cell reselection) or different frequencies (e.g., frequencies for inter-frequency cell reselection). In one embodiment, the terminal may not consider SSBs transmitted in subframes other than the SMTC occasion for SSB-based RRM measurement at the configured ssbFrequency. The base station may use various multiple TRP (transmit / receive point or transmission / reception point) operation modes depending on the serving cell configuration and PCI configuration. Among them, when two TRPs located at a physically separated distance have different PCIs, there may be two ways to operate the two TRPs.[Operation Method 1]

[0136] Two TRPs with different PCIs can be operated in a 2-serving cell configuration.

[0137] The base station can configure channels and signals transmitted from different TRPs to be included within different serving cell configurations through [Operation Method 1]. That is, each TRP has an independent serving cell configuration, and the frequency band values ​​FrequencyInfoDL indicated by DownlinkConfigCommon within each serving cell configuration may indicate at least some overlapping bands. Since the above multiple TRPs operate based on multiple ServCellIndexes (e.g., ServCellIndex #1 and ServCellIndex #2), it is possible for each TRP to use a separate PCI. That is, the base station can allocate one PCI per ServCellIndex.

[0138] In this case, when multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs have different PCIs (e.g., PCI #1 and PCI #2), and the base station can map the PCI corresponding to each TRP by appropriately selecting the value of ServCellIndex indicated by the cell parameter in QCL (quasi co location)-Info and designate the SSB transmitted from either TRP 1 or TRP 2 as the source reference RS of the QCL configuration information. However, since this configuration applies a single serving cell configuration that can be used for the terminal's carrier aggregation (CA) to multiple TRPs, there is a problem of limiting the degree of freedom of the CA configuration or increasing the signaling burden.

[0139] [Operation Method 2]

[0140] Two TRPs with different PCIs can be operated in a single serving cell configuration.

[0141] The base station can configure channels and signals transmitted from different TRPs through a single serving cell configuration via [Operation Method 2]. Since the terminal operates based on a single ServCellIndex (e.g., ServCellIndex #1), it is impossible for it to recognize the PCI assigned to the second TRP (e.g., PCI #2). [Operation Method 2] may have greater freedom in CA configuration compared to the aforementioned [Operation Method 1], but if multiple SSBs are transmitted from TRP 1 and TRP 2, the SSBs will have different PCIs (e.g., PCI #1 and PCI #2), and the base station may be unable to map the PCI of the second TRP (e.g., PCI #2) through the ServCellIndex indicated by the cell parameter in QCL-Info. The base station may only be able to designate the SSB transmitted from TRP 1 as the source reference RS of the QCL configuration information, and it may be impossible to designate the SSB transmitted from TRP 2.

[0142] As described above, [Operation Method 1] can perform multi-TRP operation for two TRPs with different PCIs through additional serving cell settings without additional specification support, but [Operation Method 2] can operate based on the following additional terminal capability reports and base station configuration information.

[0143] Regarding terminal capability reporting for [Operation Method 2]

[0144] - The terminal can report to the base station via terminal capability that configuration for the serving cell's PCI and other additional PCIs is possible through upper-layer signaling from the base station. Such terminal capability may include two independent numbers, X1 and X2, or each X1 and X2 may be reported as an independent terminal capability.

[0145] - X1 represents the maximum number of additional PCIs that can be configured for the terminal, and the PCI may differ from the PCI of the serving cell; in this case, it refers to a situation where the time domain position and periodicity of the SSB corresponding to the additional PCI are the same as those of the serving cell's SSB.

[0146] - X2 represents the maximum number of additional PCIs that can be configured for the terminal, and in this case, the PCI may differ from the PCI of the serving cell. In this case, the time domain position and periodicity of the SSB corresponding to the additional PCI may differ from the SSB corresponding to the PCI reported as X1.

[0147] - By definition, PCIs corresponding to the values ​​reported as X1 and X2 cannot be set simultaneously.

[0148] - The values ​​reported as X1 and X2 through the terminal capability report can each have one integer value from 0 to 7.

[0149] - The values ​​reported as X1 and X2 may differ from the values ​​reported in FR1 and FR2.

[0150] Regarding upper layer signaling settings for [Operation Method 2]

[0151] - Based on the terminal capability report described above, the terminal may receive an upper layer signaling, SSB-MTCAdditionalPCI-r17, from the base station, and the upper layer signaling may include at least a plurality of additional PCIs having values ​​different from the serving cell, an SSB transmission power corresponding to each additional PCI, and an ssb-PositionInBurst corresponding to each additional PCI, and the maximum number of additional PCIs that can be set may be 7.

[0152] - As an assumption regarding the SSB corresponding to an additional PCI of a different value from the serving cell, the terminal may be assumed to have the same center frequency, subcarrier spacing, and subframe number offset as the SSB of the serving cell.

[0153] - The terminal may assume that the reference RS (e.g., SSB or CSI-RS) corresponding to the PCI of the serving cell is always connected to an active TCI state, and in the case of additionally configured PCIs having values ​​different from the serving cell, when there is one or more PCIs, it may assume that only one of those PCIs is connected to an active TCI state.

[0154] - If a terminal is configured with two different coresetPoolIndexes, and a reference RS corresponding to a serving cell PCI is connected to one or more active TCI states, and a reference RS corresponding to an additionally configured PCI having a different value from the serving cell is connected to one or more active TCI states, the terminal can expect that the active TCI state(s) connected to the serving cell PCI are connected to one of the two coresetPoolIndexes, and the active TCI state(s) connected to the additionally configured PCI having a different value from the serving cell are connected to the other coresetPoolIndex.

[0155] The terminal capability reporting and upper layer signaling of the base station for the above-described [Operation Method 2] can set an additional PCI with a value different from the PCI of the serving cell. If the above setting does not exist, the SSB corresponding to the additional PCI with a value different from the PCI of the serving cell, which cannot be designated as a source reference RS, can be used to designate it as the source reference RS of the QCL setting information. Furthermore, unlike the SSB that can be set for use in purposes such as RRM, mobility, or handover, such as the setting information for the SSB that can be set within the upper layer signaling smtc1 and smtc2, it can be used to serve as a QCL source RS to support multiple TRP operations having different PCIs.

[0156] Next, we will explain in detail the demodulation reference signal (DMRS), which is one of the reference signals in the 5G system.

[0157] A DMRS may consist of multiple DMRS ports, and each port maintains orthogonality using CDM (code division multiplexing) or FDM (frequency division multiplexing) to prevent interference with one another. However, the term DMRS may be expressed using other terms depending on the user's intent and the purpose of use of the reference signal. The term DMRS is provided merely as a specific example to facilitate the explanation of the technical content of this disclosure and to aid in understanding the disclosure, and is not intended to limit the scope of this disclosure. In other words, it is obvious to those skilled in the art that the technical concept of this disclosure can be implemented with any reference signal.

[0158] FIG. 8 illustrates an example explaining DMRS patterns (type 1 and type 2) used for communication between a base station and a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0159] Two DMRS patterns can be supported in 5G systems.

[0160] Referring to FIG. 8, DMRS type 1 (801, 802) is illustrated, specifically 1 symbol pattern (801) and 2 symbol pattern (802). DMRS type 1 (801, 802) is a DMRS pattern with a comb 2 structure and can be composed of two CDM groups (CDM group 0, CDM group 1), and different CDM groups can be FDM.

[0161] In 1 symbol pattern (801), frequency-phase CDM is applied to the same CDM group to distinguish two DMRS ports, thus allowing a total of four orthogonal DMRS ports to be configured. 1 symbol pattern (801) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated by the illustrated number + 1000). In 2 symbol pattern (802), time / frequency-phase CDM is applied to the same CDM group to distinguish four DMRS ports, thus allowing a total of eight orthogonal DMRS ports to be configured. 2 symbol pattern (802) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated by the illustrated number + 1000).

[0162] Referring to FIG. 8, DMRS type 2 (803, 804) is illustrated, and as a DMRS pattern structure in which FD-OCC (frequency domain orthogonal cover codes) is applied to frequency-adjacent subcarriers, it can be composed of three CDM groups (CDM group 0, CDM group 1, CDM group 2), and different CDM groups can be FDM.

[0163] In 1 symbol pattern (803), frequency-phase CDM is applied to the same CDM group to distinguish two DMRS ports, thus allowing a total of six orthogonal DMRS ports to be configured. 1 symbol pattern (803) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated as the illustrated number + 1000). In 2 symbol pattern (704), time / frequency-phase CDM is applied to the same CDM group to distinguish four DMRS ports, thus allowing a total of twelve orthogonal DMRS ports to be configured. 2 symbol pattern (804) may include DMRS port IDs mapped to each CDM group (DMRS port IDs for the downlink may be indicated as the illustrated number + 1000).

[0164] As described above, in an NR system, two different DMRS patterns (e.g., DMRS type 1 (801, 802) or DMRS type 2 (803, 804)) can be configured, and each DMRS pattern can be configured to be either a one-symbol pattern (801, 803) or an adjacent two-symbol pattern (802, 804). Additionally, in an NR system, not only are DMRS port numbers scheduled, but the number of CDM groups scheduled together for PDSCH rate matching can also be configured and signaled. Furthermore, in the case of CP-OFDM (cyclic prefix based orthogonal frequency division multiplex), both of the two DMRS patterns described above may be supported in DL and UL, while in the case of DFT-S-OFDM (discrete Fourier transform spread OFDM), only DMRS type 1 (801, 802) among the DMRS patterns described above may be supported in UL.

[0165] Additionally, support may be provided to configure additional DMRS. Front-loaded DMRS refers to the first DMRS transmitted and received at the earliest symbol in the time domain among the DMRS, and additional DMRS refers to the DMRS transmitted and received at a symbol later than the front-loaded DMRS in the time domain. In an NR system, the number of additional DMRS can be configured from a minimum of 0 to a maximum of 3. Additionally, when additional DMRS is configured, the same pattern as the front-loaded DMRS may be assumed. In one embodiment, regarding the front-loaded DMRS, if information is provided on whether the aforementioned DMRS pattern type is type 1 or type 2, whether the DMRS pattern is a one-symbol pattern or an adjacent two-symbol pattern, and information on the number of DMRS ports and CDM groups used, then when additional DMRS is configured, it may be assumed that the additional DMRS has the same DMRS information as the front-loaded DMRS.

[0166] In one embodiment, the aforementioned downlink DMRS setting can be set through RRC signaling as shown in [Table 7] below.

[0167] DMRS-DownlinkConfig ::= SEQUENCE {dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need SmaxLength ENUMERATED {len2} OPTIONAL, -- Need SscramblingID0 INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1 INTEGER (0..65535) OPTIONAL, -- Need SphaseTrackingRS SetupRelease {PTRS-DownlinkConfig} OPTIONAL, -- Need M...}

[0168] Here, dmrs-Type can set the DMRS type, dmrs-AdditionalPosition can set additional DMRS OFDM symbols, maxLength can set a 1-symbol DMRS pattern or a 2-symbol DMRS pattern, scramblingID0 and scramblingID1 can set scrambling IDs, and phaseTrackingRS can set the PTRS (phase tracking reference signal). In addition, the aforementioned uplink DMRS settings can be configured through RRC signaling as shown in [Table 8] below.

[0169] DMRS-UplinkConfig ::= SEQUENCE {dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need RphaseTrackingRS SetupRelease { PTRS-UplinkConfig} OPTIONAL, -- Need MmaxLength ENUMERATED {len2} OPTIONAL, -- Need StransformPrecodingDisabled SEQUENCE {scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S...} OPTIONAL, -- Need RtransformPrecodingEnabled SEQUENCE {nPUSCH-Identity INTEGER (0..1007) OPTIONAL, -- Need SsequenceGroupHopping ENUMERATED {disabled} OPTIONAL, -- Need SsequenceHopping ENUMERATED {enabled} OPTIONAL, -- Need S...} OPTIONAL, -- Need R...}

[0170] Here, dmrs-Type can set the DMRS type, dmrs-AdditionalPosition (additional DMRS OFDM symbols) can be set, phaseTrackingRS can set PTRS, and maxLength can set a 1-symbol DMRS pattern or a 2-symbol DMRS pattern. scramblingID0 and scramblingID1 can set scrambling IDs0, nPUSCH-Identity can set a cell ID for DFT-s-OFDM, sequenceGroupHopping can disable sequence group hopping, and sequenceHopping can enable sequence hopping. FIG. 9 illustrates an example of channel estimation using DMRS received from a single PUSCH in the time band of a wireless communication system according to an embodiment of the present disclosure. Referring to FIG. 9, in performing channel estimation for data decoding using DMRS, in the frequency band, channel estimation can be performed within a PRG (precoding resource block group), which is the corresponding bundling unit, by using PRB (physical resource blocks) bundling linked to the system band. In addition, in the time unit, the channel can be estimated by assuming that only DMRS received from a single PUSCH has the same precoding.

[0171] The following describes the time domain resource allocation (TDRA) method for data channels in a 5G communication system. A base station can set a time domain resource allocation information table for downlink data channels (PDSCH) and uplink data channels (PUSCH) for the terminal using upper layer signaling (e.g., RRC signaling).

[0172] The base station may set up a table for PDSCH consisting of a maximum of maxNrofDL-Allocations = 17 entries, and for PUSCH, a table consisting of a maximum of maxNrofUL-Allocations = 17 entries. Time domain resource allocation information may include, for example, PDCCH-to-PDSCH slot timing (corresponding to a slot-unit time interval between the time when PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as K0) or PDCCH-to-PUSCH slot timing (corresponding to a slot-unit time interval between the time when PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the starting symbol for which PDSCH or PUSCH is scheduled within the slot, and at least one of the mapping type of PDSCH or PUSCH.

[0173] In one embodiment, time domain resource allocation information for PDSCH can be set to the terminal through RRC signaling as shown in [Table 9] below.

[0174] PDSCH-TimeDomainResourceAllocationListinformation elementPDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocationPDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0 INTEGER(0..32) OPTIONAL, -- Need SmappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127)repetitionNumber ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, -- Cond Formats1-0and1-1}

[0175] Here, k0 represents the PDCCH-to-PDSCH timing (i.e., the slot offset between the DCI and the scheduled PDSCH) in slot units, mappingType represents the PDSCH mapping type, startSymbolAndLength represents the starting symbol and length of the PDSCH, and repetitionNumber represents the number of PDSCH transmission occasions according to the slot-based repetition method. In one embodiment, time domain resource allocation information for PUSCH can be set to the terminal through RRC signaling as shown in [Table 10] below.

[0176] PUSCH-TimeDomainResourceAllocationinformation elementPUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocationPUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2 INTEGER(0..32) OPTIONAL, -- Need SmappingType ENUMERATED {typeA, typeB},startSymbolAndLength INTEGER (0..127)}PUSCH-Allocation-r16 ::= SEQUENCE {mappingType-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbolAndLength-r16 INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbol-r16 INTEGER (0..13) OPTIONAL, -- Cond RepTypeBlength-r16 INTEGER (1..14) OPTIONAL, -- Cond RepTypeBnumberOfRepetitions-r16 ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02...}

[0177] Here, k2 represents the PDCCH-to-PUSCH timing (i.e., the slot offset between the DCI and the scheduled PUSCH) in slot units, mappingType represents the PUSCH mapping type, startSymbolAndLength or StartSymbol and length represents the starting symbol and length of the PUSCH, and numberOfRepetitions may represent the number of repetitions applied to the PUSCH transmission. The base station may indicate at least one entry in the table for time domain resource allocation information to the terminal via L1 signaling (e.g., downlink control information (DCI)) (e.g., by indicating the 'time domain resource allocation' field within the DCI). The terminal may obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station. The transmission of the uplink data channel (PUSCH) in a 5G system is described below. PUSCH transfers may be dynamically scheduled by a UL grant within the DCI (e.g., referred to as DG (dynamic grant)-PUSCH) or by a configured grant Type 1 or configured grant Type 2 (e.g., referred to as CG (configured grant)-PUSCH). Dynamic scheduling for PUSCH transfers may be indicated, for example, by DCI format 0_0 or 0_1.

[0178] A PUSCH transmission of a Configured grant Type 1 can be configured semi-statically by receiving a configuredGrantConfig containing the rrc-ConfiguredUplinkGrant of [Table 11] via upper-layer signaling, without receiving a UL grant within the DCI. A PUSCH transmission of a Configured grant Type 2 can be scheduled semi-persistently by a UL grant within the DCI after receiving a configuredGrantConfig that does not contain the rrc-ConfiguredUplinkGrant of [Table 11] via upper-layer signaling.

[0179] In one embodiment, when a PUSCH transmission is scheduled by a configured grant, the parameters applied to the PUSCH transmission may be set through the upper-layer signaling configuredGrantConfig of [Table 11], excluding specific parameters provided by the upper-layer signaling pusch-Config of [Table 11] (e.g., dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, or scaling of UCI-OnPUSCH). For example, if a terminal is provided with a transformPrecoder within the upper-layer signaling configuredGrantConfig of [Table 11], the terminal may apply tp-pi2BPSK within the pusch-Config of [Table 12] to the PUSCH transmission operated by the configured grant.

[0180] ConfiguredGrantConfigConfiguredGrantConfig ::= SEQUENCE {frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S,cg-DMRS-Configuration DMRS-UplinkConfig,mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},rbg-Size ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUse ENUMERATED {n0, n1},p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-Processes INTEGER(1..17),repK ENUMERATED {n1, n2, n4, n8},repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need Rperiodicity ENUMERATED {sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym17x14, sym20x14,sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym170x14, sym256x14, sym320x14, sym512x14,sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym17x12, sym20x12, sym32x12,sym40x12, sym64x12, sym80x12, sym128x12, sym170x12, sym256x12, sym320x12, sym512x12, sym640x12,sym1280x12, sym2560x12},configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrant SEQUENCE {timeDomainOffset INTEGER (0..5119),timeDomainAllocation INTEGER (0..16),frequencyDomainAllocation BIT STRING (SIZE(18)),antennaPort INTEGER (0..31),dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayers INTEGER (0..63),srs-ResourceIndicator INTEGER (0..16) OPTIONAL, -- Need RmcsAndTBS INTEGER (0..31),frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),...} OPTIONAL, -- Need R...}.

[0181] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission may be the same as the antenna port for SRS (sounding reference signal) transmission. PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config within the upper signaling [Table 12] is 'codebook' or 'nonCodebook'. As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can be semi-statically configured by a configured grant. If a terminal is instructed to schedule PUSCH transmission via DCI format 0_0, the terminal can perform beam configuration for PUSCH transmission using a pucch-spatialRelationInfoID corresponding to a terminal-specific (UE-specific, dedicated) PUCCH resource having the lowest ID within the active uplink subband (BWP) in the serving cell. In one embodiment, PUSCH transmission may be performed based on a single antenna port. In a BWP where a PUCCH resource containing pucch-spatialRelationInfo is not configured, the terminal may not expect scheduling for PUSCH transmission via DCI format 0_0. If the terminal has not configured txConfig within pusch-Config of [Table 12], the terminal may not expect scheduling via DCI format 0_1.

[0182] PUSCH-ConfigPUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need StxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need Sdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig} OPTIONAL, -- Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need SfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need MresourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList} OPTIONAL, -- Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8} OPTIONAL, -- Need Smcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}OPTIONAL, -- Cond codebookBasedmaxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, -- Need Suci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S...}.

[0183] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and can operate semi-statically via a configured grant. When Codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the terminal can determine a precoder for PUSCH transmission based on the SRS resource indicator (SRI), TPMI (transmission precoding matrix indicator), and the transmission rank (number of PUSCH transmission layers). According to one embodiment of the present disclosure, the SRI may be provided via a field SRS resource indicator within the DCI or configured via the srs-ResourceIndicator, which is a higher-level signaling. During codebook-based PUSCH transmission, the terminal may be configured with at least one SRS resource, and, for example, up to two. When a terminal receives an SRI through a DCI, the SRS resource indicated by the SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. Additionally, the TPMI and transmission rank may be provided through the fields precoding information and number of layers within the DCI, or set through the higher-level signaling precodingAndNumberOfLayers. The TPMI may be used to indicate the precoder applied to the PUSCH transmission.A precoder to be used for PUSCH transmission may be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config. In codebook-based PUSCH transmission, the terminal may determine the codebook subset based on TPMI and the codebookSubset in the upper signaling pusch-Config. In one embodiment, the codebookSubset in the upper signaling pusch-Config may be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the terminal to the base station.

[0184] If the terminal reports 'partialAndNonCoherent' as a UE capability, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the terminal reports 'nonCoherent' as a UE capability, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports within the parent signaling SRS-ResourceSet points to two SRS antenna ports, the terminal may not expect the value of the parent signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0185] A terminal can receive one SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource within that SRS resource set can be indicated via SRI. If multiple SRS resources are configured within the SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'codebook', the terminal can expect that the value of nrofSRS-Ports within the upper signaling SRS-Resource will be set to the same value for all SRS resources.

[0186] A terminal transmits one or more SRS resources included in an SRS resource set in which the value of usage is set to 'codebook' according to upper signaling to a base station, and the base station may select one of the SRS resources transmitted by the terminal and instruct the terminal to perform PUSCH transmission using the transmit beam information of the corresponding SRS resource. In one embodiment, in codebook-based PUSCH transmission, an SRI is used as information to select the index of one SRS resource and may be included in a DCI. Additionally, the base station may include information in the DCI that instructs the terminal to use for PUSCH transmission, such as the TPMI and rank, and transmit it. The terminal may perform PUSCH transmission by using the SRS resource instructed by the SRI, applying a precoder instructed by the instructed TPMI and rank based on the transmit beam of the corresponding SRS resource.

[0187] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, or can operate semi-statically via a configured grant. If at least one SRS resource is configured within an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive a non-codebook-based PUSCH transmission scheduled via DCI format 0_1.

[0188] For an SRS resource set in which the value of usage within the upper signaling SRS-ResourceSet is set to 'nonCodebook', the terminal can receive an NZP (non-zero power) CSI-RS resource associated with one SRS resource set. The terminal can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource associated with the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource associated with the SRS resource set and the first symbol of the aperiodic SRS transmission at the terminal is less than a specific number of symbols (e.g., 42 symbols), the terminal may not expect the information for the precoder for SRS transmission to be updated.

[0189] If the value of resourceType within the upper signaling SRS-ResourceSet is set to 'aperiodic', the NZP CSI-RS associated with said SRS-ResourceSet may be indicated by the SRS request field within DCI format 0_1 ​​or 1_1. In one embodiment, if the NZP CSI-RS resource associated with the SRS-ResourceSet is an aperiodic NZP CSI resource and the value of the SRS request field within DCI format 0_1 ​​or 1_1 is not '00', it may indicate the existence of the NZP CSI-RS associated with the SRS-ResourceSet. The said DCI may not indicate cross-carrier or cross-BWP scheduling. If the value of the SRS request indicates the existence of the NZP CSI-RS, said NZP CSI-RS may be located in the slot where the PDCCH containing the SRS request field was transmitted. The TCI states set on the scheduled subcarrier may not be set to QCL-TypeD.

[0190] If a periodic or semi-continuous SRS resource set is configured, the NZP CSI-RS associated with said SRS resource set may be indicated through the associated CSI-RS within the parent signaling SRS-ResourceSet. For non-codebook-based transmission, the terminal may not expect the parent signaling spatialRelationInfo for the SRS resource and the associated CSI-RS within the parent signaling SRS-ResourceSet to be configured together.

[0191] When a terminal is configured with multiple SRS resources, it can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In one embodiment, the SRI may be indicated via a field SRS resource indicator within the DCI or configured via the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the terminal receives the SRI via the DCI, the SRS resource indicated by the SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted prior to the PDCCH containing the SRI. The terminal may use one or multiple SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within a single SRS resource set and the maximum number of SRS resources may be determined by the UE capability reported by the terminal to the base station. SRS resources transmitted simultaneously by the terminal may occupy the same RB. The terminal may configure one SRS port for each SRS resource. Only one SRS resource set can be configured with the value of usage in the upper signaling SRS-ResourceSet set set to 'nonCodebook', and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0192] The base station transmits one NZP CSI-RS associated with an SRS resource set to the terminal, and the terminal can calculate a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the results measured upon receiving the NZP CSI-RS. When the terminal transmits one or more SRS resources within an SRS resource set where usage is set to 'nonCodebook' to the base station, it applies the calculated precoder, and the base station can select one or more SRS resources from among the received one or more SRS resources. In non-codebook-based PUSCH transmission, the SRI may represent an index capable of expressing a combination of one or more SRS resources, and the SRI may be included within the DCI. The number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the terminal can transmit the PUSCH by applying the precoder applied for SRS resource transmission to each layer.

[0193] The following describes the repetitive transmission of the uplink data channel (PUSCH) and the single TB transmission method through multiple slots in a 5G system. A 5G system can support two types of repetitive transmission methods for the uplink data channel (e.g., PUSCH repetitive transmission type A, PUSCH repetitive transmission type B) and TBoMS (TB processing over multi-slot PUSCH), which transmits a single TB across multiple slots using multiple PUSCHs. Additionally, the terminal can receive a setting for either PUSCH repetitive transmission type A or B through upper-layer signaling. Furthermore, the terminal can transmit TBoMS by receiving 'numberOfSlotsTBoMS' through a resource allocation table.

[0194] PUSCH Repeated Transmission Type A

[0195] - As described above, within a single slot, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method, and the base station can transmit the number of repeated transmissions to the terminal via upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). To determine the TBS, the number of slots N set by numberOfSlotsTBoMS is 1.

[0196] - Based on the number of repeated transmissions received from the base station, the terminal may repeatedly transmit an uplink data channel in consecutive slots that has the same starting symbol and length as the uplink data channel set above. In one embodiment, in a slot set as downlink by the base station to the terminal, or if at least one of the symbols within the slot for repeated uplink data channel transmission set by the terminal is set as downlink, the terminal may omit the transmission of the uplink data channel in that slot. For example, the terminal may not transmit the uplink data channel within the number of repeated uplink data channel transmissions. On the other hand, a terminal supporting Rel-17 repeated uplink data transmission determines that a slot capable of repeated uplink data transmission is a "available slot," and the number of transmissions for repeated uplink data channel transmissions can be counted for the slot determined as an "available slot." If repeated uplink data channel transmission determined as an "available slot" is omitted, repeated transmission can be performed through a slot that is available for transmission after postponement. Using the following [Table 13], a redundancy version can be applied according to the redundancy version pattern set for each nth PUSCH transmission occasion.

[0197] PUSCH Repeated Transmission Type B

[0198] - As described above, within a single slot, the start symbol and length of the uplink data channel are determined by the time domain resource allocation method, and the base station can transmit the number of repetitions to the terminal via upper signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). In one embodiment, the number of slots N set as numberOfSlotsTBoMS to determine the TBS is 1.

[0199] - First, based on the starting symbol and length of the uplink data channel set above, the nominal repetition of the uplink data channel can be determined as follows. Here, nominal repetition may refer to the symbol resources set by the base station for repeated PUSCH transmission, and the terminal can determine the resources available for uplink use from the set nominal repetition. In this case, the slot where the nth nominal repetition starts is The symbol given by and where nominal repetition starts in the above start slot is It can be given by. The slot where the nth nominal repetition ends is The symbol given by and where the nominal repetition ends in the last slot above is It can be given by, where n=0, ...,numberofrepetitions-1, S represents the starting symbol of the configured uplink data channel, and L represents the symbol length of the configured uplink data channel. indicates the slot where the PUSCH transmission starts. can represent the number of symbols per slot.

[0200] - The terminal can determine an invalid symbol for PUSCH repeat transmission type B. A symbol configured for the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated can be determined as an invalid symbol for PUSCH repeat transmission type B. Additionally, an invalid symbol can be set based on an upper layer parameter (e.g., InvalidSymbolPattern). As an example, the upper layer parameter (e.g., InvalidSymbolPattern) can set an invalid symbol by providing a symbol-level bitmap spanning one or two slots. In one embodiment, a value marked as 1 in the bitmap may represent an invalid symbol. Additionally, the period and pattern of the bitmap can be set through an upper layer parameter (e.g., periododicityAndPattern). If an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the terminal may apply the invalid symbol pattern, and if it indicates 0, it may not apply the invalid symbol pattern. Alternatively, if an upper layer parameter (e.g., InvalidSymbolPattern) is set and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not set, the terminal may apply the invalid symbol pattern.

[0201] - After an invalid symbol is determined in each nominal repetition, the terminal may consider the symbols excluding the determined invalid symbol as valid symbols. If one or more valid symbols are included in each nominal repetition, the nominal repetition may include one or more actual repetitions. Here, each actual repetition may refer to a symbol actually used for PUSCH repeat transmission among the symbols set in the above-determined nominal repetition, and may include a continuous set of valid symbols that can be used for PUSCH repeat transmission type B within a single slot. Except when the symbol length L of the configured uplink data channel is 1, the terminal may omit the transmission of the actual repetition if an actual repetition having one symbol is set as valid. Using [Table 13] below, a redundancy version may be applied according to the redundancy version pattern configured for each n-th actual repetition.

[0202] TB processing over multiple slots (TBoMS)

[0203] - As described above, the start symbol and length of the uplink data channel are determined by a time domain resource allocation method within a single slot, and the base station can transmit the number of repeated transmissions to the terminal via upper layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI). In one embodiment, TBS can be determined using a value of N greater than or equal to 1, which is the number of slots set by numberOfSlotsTBoMS.

[0204] - Based on the number of slots and the number of repeated transmissions for determining the TBS received from the base station, the terminal may transmit an uplink data channel in consecutive slots that has the same starting symbol and length as the uplink data channel set above. In one embodiment, in a slot set as a downlink by the base station to the terminal, or if at least one of the symbols within the slot for repeated transmission of the uplink data channel set by the terminal is set as a downlink, the terminal may omit the transmission of the uplink data channel in that slot. For example, it may be included in the number of repeated transmissions of the uplink data channel but may not be transmitted.

[0205] On the other hand, a terminal supporting Rel-17 uplink data repeat transmission determines that a slot capable of uplink data repeat transmission is an available slot, and the number of transmissions for the slot determined to be an available slot can be counted during uplink data channel repeat transmission. If the uplink data channel repeat transmission determined to be an available slot is omitted, it can be repeated through a slot that is available for transmission after postponement. In one embodiment, using [Table 13] below, a redundancy version may be applied according to the redundancy version pattern set for each nth PUSCH transmission occasion.

[0206] indicated by the DCI scheduling the PUSCH to be applied ton th transmission occasion (repetition Type A) or TB processing over multiple slots) orn thactual repetition (repetition Type B)((n-(n mod N)) / N)mod 4 = 0((n-(n mod N)) / N)mod 4 = 0((n-(n mod N)) / N)mod 4 = 0((n-(n mod N)) / N)mod 4 = 000231223103310211023

[0207] The following describes a method for determining an uplink available slot for a single or multiple PUSCH transmission in a 5G system. According to one embodiment of the present disclosure, when a terminal is configured to enable AvailableSlotCounting, the terminal can determine an available slot for Type A PUSCH repeated transmission and TBoMS PUSCH transmission based on the tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and TDRA (time domain resource allocation) information field values. That is, if at least one symbol configured as TDRA for PUSCH in a slot for PUSCH transmission overlaps with at least one symbol for a purpose other than uplink transmission, the slot may be determined as an unavailable slot.

[0208] The following describes a method to reduce SSB density through dynamic signaling for base station energy saving in 5G systems.

[0209] FIG. 10 illustrates a method for resetting SSB transmission through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0210] Referring to FIG. 10, the terminal can receive ssb-PositionsInBurst = '11110000' (1002) from the base station via upper layer signaling (SIB1 or ServingCellConfigCommon). At a subcarrier interval of 30 kHz, up to two synchronization signal blocks can be transmitted within a time of 0.5 ms (or the length of one slot if one slot consists of 14 OFDM symbols), and accordingly, the terminal can receive four synchronization signal blocks (SSB) within a time of 1 ms (or the length of two slots if one slot consists of 14 OFDM symbols). At this time, the base station can reset the SSB transmission setting information by broadcasting the bitmap '1010xxxx' (1004) through the Group / Cell common DCI (1003) having the nwes-RNTI (network energy saving-radio network temporary identifier) ​​(or es-RNTI) to reduce the density of SSB transmission for energy saving. At this time, the transmission of SS block #1 (1005) and SS block #3 (1006) can be canceled based on the bitmap (1004) set by the Group / Cell common DCI. FIG. 10 illustrates a method (1001) for resetting SSB transmission through the bitmap-based group / Cell common DCI.

[0211] Additionally, the base station can reset the SSB-periodicity set via upper-layer signaling through the Group / Cell common DCI. Furthermore, by additionally setting Timer information to indicate the application time of the Group / Cell common DCI, the base station can transmit SSBs using the SSB transmission information reset via the Group / Cell common DCI during the set timer. After the timer ends, the base station can operate using the SSB transmission information set via the existing upper-layer signaling. This allows the setting to be switched from normal mode to energy-saving mode via the timer, thereby resetting the SSB configuration information. Alternatively, the base station can set the application time and duration of the SSB configuration information reset via the Group / Cell common DCI to the terminal using Offset and Duration information. In this case, the terminal may not monitor SSBs for the Duration period, starting from the moment the Group / Cell common DCI is received and the moment the Offset is applied.

[0212] The following describes BWP or BW adaptation methods through dynamic signaling for base station energy saving in 5G systems.

[0213] FIG. 11 illustrates a method for resetting BWP and BW through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0214] Referring to FIG. 11, the terminal can operate as an activated BWP or BW through upper layer signaling and L1 signaling from the base station (1101). For example, a fixed power PSD B It can operate via a full 100MHz bandwidth. In this case, the base station uses an equal power PSD for energy saving. BWith this, the BW and BWP can be adjusted to enable a narrower BW of 40 MHz for the terminal (1102). At this time, the adjustment operation of the BW or BWP for energy saving of the base station can be set to match the BWP and BW settings specifically set for the UE through the Group common DCI and Cell specific DCI (1103). For example, UE#0 and UE#1 may have different BWP configurations and locations. At this time, the BW and BWP of all terminals can be set to one identically to save energy by reducing the BW used by the base station. At this time, the BWP or BW in the operation for energy saving can be set to one or more, and this can be used to set the BWP per UE Group.

[0215] In describing the present disclosure, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0216] - MIB (master information block)

[0217] - SIB (system information block) or SIB

[0218] - RRC (radio resource control)

[0219] - MAC (medium access control) CE (control element)

[0220] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.

[0221] - PDCCH (physical downlink control channel)

[0222] - DCI (downlink control information)

[0223] - Terminal-specific (UE-specific) DCI

[0224] - Group common DCI

[0225] - Common DCI

[0226] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

[0227] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)

[0228] - PUCCH (physical uplink control channel)

[0229] - UCI (uplink control information)

[0230] In the following disclosure, the examples are described through a plurality of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0231] The following describes a method for DRX alignment through dynamic signaling to save base station energy in a 5G system.

[0232] FIG. 12 illustrates a method for resetting DRX through dynamic signaling of a wireless communication system according to one embodiment of the present disclosure.

[0233] Referring to FIG. 12, the base station can set the DRX specifically for the UE through upper layer signaling. For example, different drx-LongCycle (1202) or drx-ShortCycle, drx-onDurationTimer (1203), and drx-InactivityTimer (1204) can be set for each terminal. Subsequently, for energy saving, the base station can set the UE-specific DRX settings specifically for the UE group or cell through L1 signaling (1201). Through this, the base station can obtain the same effect for energy saving as the terminal saves power through the DRX.

[0234] The following illustrates an example describing Discontinuous transmission (DTx, DTX) operations to reduce energy consumption of base stations in a 5G system.

[0235] FIG. 13 is a diagram illustrating a DTx method for base station energy saving according to one embodiment of the present disclosure.

[0236] Referring to FIG. 13, the base station can set DTx for energy saving through upper layer signaling (e.g., new system information block (SIB) for DTx or RRC signaling) and L1 signaling (e.g., DCI). At this time, the base station may set a dtx-onDurationTimer (1305) for transmitting a reference signal for measuring, beam management, and path loss, etc., for scheduling a DL SCH (shared channel) for DTx operation, a dtx-InactivityTimer (1306) for receiving a PDSCH after receiving a PDCCH for scheduling a DL SCH, a dtx-offset (1304) for setting an offset between the synchronization signal (SS) (1303) for synchronization before the dtx-onDurationTimer and the dtx-onDurationTimer after the SS setting information, and a dtx-(Long)Cycle (1302) for the DTx to operate periodically based on the setting information. At this time, the dtx-cycle (1302) may be set to multiple long cycles and short cycles. During the operation of DTx, the base station considers the transmitter to be off (or inactive) and therefore may not transmit DL CCH (control channel), SCH, and DL RS. That is, during the operation of DTx, the base station may transmit downlink (e.g., PDCCH, PDSCH, RS, etc.) only during SS (1303), dtx-onDurationTimer (1305), and dtx-InactivityTimer (1306).At this time, additional information for the set SS, such as the SS-gapbetweenBurst (the gap between SS bursts in the time domain) or the number of SS bursts, can be additionally set.

[0237] The following describes a method for activating a base station via a gNB wake-up signal (WUS) during the base station's inactive mode to reduce energy consumption in a 5G system.

[0238] FIG. 14 illustrates an example explaining the operation of a base station according to a gNB WUS according to one embodiment of the present disclosure.

[0239] Referring to FIG. 14, the base station may keep the transmitter in an Off (or inactive) state during the base station's inactive state (or sleep mode) for energy saving. Subsequently, the base station may receive a gNB WUS (1402) from the terminal to activate the base station's sleep mode. Subsequently, when the base station receives a WUS from the terminal via the Rx terminal, it may change the Tx terminal to an On (or active) state (1403). Subsequently, the base station may perform downlink transmission to the terminal. At this time, the base station may perform synchronization after Tx is turned on and perform Control and Data transmission. In addition, various uplink signals, such as PRACH (physical random access channel), scheduling request (SR) PUCCH, PUCCH including Ack, etc., may be considered as gNB WUS. Through the above method, the base station can save energy, and at the same time, the terminal can improve latency.

[0240] At this time, the base station may set a WUS occasion for receiving the gNB WUS and a Sync RS for synchronization before the terminal transmits the gNB WUS. At this time, as the Sync RS, an SSB, TRS (tracking reference signal), Light SSB (PSS+SSS), consecutive SSBs, or new RS (continuous PSS + SSS) may be considered, and as the WUS, a PRACH, PUCCH with SR, or a sequence-based signal may be considered. The Sync RS (1404) for the terminal to activate the base station's energy saving disable mode and the WUS occasion for receiving the WUS may be transmitted repeatedly with WUS-RS periodicity (1405). In the case of FIG. 14, one embodiment is described with an example of a 1-to-1 mapping between the Sync RS and the WUS occasion, but the present disclosure is not limited thereto. For example, Sync and WUS occasion can be mapped N-to-1, 1-to-N, or N-to-M.

[0241] The following describes a method for dynamically turning on / off the Spatial domain elements (i.e., Antenna, power amplifier (PA), or TxRUs (transceiver units or transmission radio units)) of a base station to save base station energy in a 5G system.

[0242] FIG. 15 is a diagram illustrating an antenna adaptation method for a base station for energy saving of a wireless communication system according to one embodiment of the present disclosure.

[0243] Referring to FIG. 15, the base station can adjust the Tx antenna port per RU (radio unit) for network energy savings (NWES) (1501). For example, since the base station's PA (power amplifier) ​​accounts for most of the base station's energy consumption, the base station can turn off the Tx antenna to save energy. At this time, the base station may refer to / use the terminal's RSRP (reference signal received power), CQI (channel quality indicator), and RSRQ (reference signal received quality) to determine whether the Tx antenna can be turned off. The base station can transmit Tx by adjusting the number of activated Tx antennas per UE group or per UE. At this time, the base station can set information including one or more of beam information or reference signal information (e.g., one or more of CSI resource, CSI resource set, or CSI report) based on antenna on / off to the terminal through upper layer signaling (e.g., RRC signaling) or DCI signaling. In addition, the base station can set different antenna information for each BWP and reset the antenna information in response to changes in the BWP. Furthermore, the base station can receive CSI feedback from the terminal to determine the feasibility of spatial domain (SD) adaptation. The base station can determine SD adaptation (based on the CSI feedback). The base station can receive multiple feedback from the terminal through antenna structure hypotheses of various antenna patterns for SD adaptation.

[0244] More specifically, the base station may apply multiple types of SD adaptation (e.g., two types) for energy saving (1502). For example, the multiple types may include Type 1 SD adaptation (1503) and Type 2 SD adaptation (1504).

[0245] When Type 1 SD adaptation (1503) is applied, the base station can adapt the number of antenna ports while maintaining the number of physical antenna elements per antenna port (i.e., logical port). At this time, the RF characteristics (e.g., tx power, beam) per port can be the same. Therefore, the terminal can combine the CSI-RS of the same port during CSI measurements (e.g., L1-RSRP (layer 1-RSRP), L3-RSRP (layer 3-RSRP), etc.).

[0246] In another way, when Type 2 SD adaptation (1504) is applied, the base station can turn on / off physical antenna elements per port with the same number of antenna ports (i.e., logical ports) (1504). In this case, the RF characteristics per port may differ. During CSI measurement, the terminal can distinguish the CSI-RS of the same port and perform measurements for each. The base station can save energy through one or more of a plurality of types of SD adaptation methods, including the two types of SD adaptation methods mentioned above.

[0247] The following describes a method for configuring an On-demand SSB and SIB1 for applying an On-demand SSB and SIB for energy saving in a base station in a 5G system. In this disclosure, the term "on-demand operation" may include an On-demand SSB and an On-demand SIB (e.g., an On-demand SIB1). Furthermore, while the following description focuses on an On-demand SIB1, it is understood that this disclosure can also be applied to an On-demand SSB and other SIBs (On-demand SIBs). Unless otherwise specifically stated, a SIB1 request described below may be transmitted via or by a WUS that can be transmitted by a terminal capable of receiving an On-demand SIB1, and such a WUS may be considered a WUS that is received by a base station capable of transmitting the On-demand SIB1, and in which case the base station can understand that the terminal is requesting the SIB1.

[0248] FIG. 16 is a diagram illustrating an example of an On-demand SIB1 operation considering multiple cells of a base station and a terminal according to an embodiment of the present disclosure.

[0249] A base station may apply / configure / operate multiple cells with different functions for on-demand SIB1 operation considering multiple cells. For example, the base station(s) may apply / configure / operate two cells with different functions for on-demand SIB1 operation considering multiple cells.

[0250] For example, first, the base station periodically transmits additional information (e.g., wake-up-signal (WUS) configuration, additional SIB information of surrounding cells, etc.) through an anchor (or reference, adjacent, neighbor) cell (or from the anchor cell) for the on-demand SIB1 operation of surrounding cells, and may provide the terminal with information about cells that do not transmit SIB1 during the on-demand SIB1 operation (cells where SIB1 is not transmitted, cells where SIB1 transmission is not performed). Cells that do not transmit SIB1 during the on-demand SIB1 operation may be on-demand SIB1 cells or may include on-demand SIB1 cells.

[0251] Secondly, the base station can apply, configure, and operate on-demand SIB1 cells. An on-demand SIB1 cell is a cell that selectively transmits SIB1 for energy saving. For example, whether an on-demand SIB1 cell transmits SIB1 depends on the terminal's request (i.e., on-demand); the on-demand SIB1 cell does not transmit SIB1 if there is no request from the terminal, but transmits SIB1 if the terminal requests it. An on-demand SIB1 cell always transmits SSB (i.e., regardless of the terminal's request) and can monitor the WUS depending on the configuration. Whether the base station is monitoring the WUS can be notified to the terminal via the Anchor cell through upper-layer signaling. The base station may not receive the WUS from the terminal (directly) from the on-demand SIB1 cell. In this case, the base station can receive a SIB1 request from a terminal through an Anchor cell and forward it to an on-demand SIB1 cell via backhaul signaling. On-demand SIB1 operation can be performed using the two cells mentioned above. At this time, the Anchor cell can support one or multiple on-demand SIB1 cells and can have a larger coverage than the on-demand SIB1 cell.

[0252] Anchor cells and on-demand SIB1 cells can be provided by the same base station. Anchor cells and on-demand SIB1 cells may also be provided by different base stations.

[0253] Referring to FIG. 16, the base station can perform an on-demand SIB1 operation for energy saving. More specifically, referring to section (A) (1600), base station(s) can perform on-demand SIB1 operations using multiple cells (anchor cell (Cell A) and on-demand SIB1 cell (Cell B, NES cell). In this case, the base station can transmit the SSB and SIB1 of the corresponding cell to the UE via the anchor cell (Cell A), and additionally transmit a WUS configuration (resource settings for WUS transmission and power control information) for requesting the SIB1 of the on-demand SIB1 cell, and some of the information included in the SIB1 of the on-demand SIB1 cell (e.g., Access-related information, e.g., AccessCellInfo or Barring information). Alternatively, the base station can transmit the SSB from the on-demand SIB1 cell (Cell B) and monitor the WUS according to the WUS configuration. In this case, the terminal measures the SSB from Cell A and Cell B, and when packet processing is required, from Cell B You can decide whether to request SIB1.

[0254] One or a combination of the following methods may be applied as a method for the terminal to distinguish between an anchor cell and an on-demand SIB1 cell.

[0255] [Method 1]

[0256] The terminal can determine the anchor cell or on-demand SIB1 cell through the SSB's PSS, SSS, and / or PCI (physical cell identity). More specifically, PCI It can be determined as follows.

[0257] From the above class The scope is illustrative and in this disclosure class The range of possible values ​​is not limited to this. It can be 0,...,1007, but this is also an example. The range of possible values ​​is not limited to this.

[0258] The terminal is the PSS Cell IDs and / or Cell group ID of the SSS If is set to a specific value that is pre-set or determined, the cell can be identified as an anchor cell or an on-demand SIB1 cell. For example, At least some of the possible values ​​and / or At least some of the possible values ​​can be set / determined to indicate that it is an anchor cell. and / or, for example, At least some of the possible values ​​and / or At least some of the possible values ​​can be set / determined to indicate that it is an on-demand SIB1 cell.

[0259] The terminal can determine that the cell is an anchor cell or an on-demand SIB1 cell if the PCI determined through PSS and SSS is set to a specific value that is pre-configured or determined. For example, At least some of the possible values ​​can be set / determined to indicate that it is an anchor cell. For example, At least some of the possible values ​​can be set / determined to indicate that it is an on-demand SIB1 cell.

[0260] [Method 2]

[0261] The terminal can determine the cell as an anchor cell or an on-demand SIB1 cell through the information of the MIB via the PBCH of the SSB. More specifically, the terminal can determine the anchor cell or an on-demand SIB1 cell using at least some of the information of the MIB exemplified in [Table 14] below.

[0262] MIB ::= SEQUENCE {systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffset INTEGER (0..15),dmrs-TypeA-Position ENUMERATED {pos2, pos3},pdcch-ConfigSIB1 PDCCH-ConfigSIB1,cellBarred ENUMERATED {barred, notBarred},intraFreqReselection ENUMERATED {allowed, notAllowed},spare BIT STRING (SIZE (1))}

[0263] For example, the above spare information may be used. If the above spare information is set to '0', the cell corresponding to the MIB may be determined as an anchor cell, and if the above spare information is set to '1', the cell corresponding to the MIB may be determined as an on-demand SIB1 cell. Conversely, if the above spare information is set to '1', the cell corresponding to the MIB may be determined as an anchor cell, and if the above spare information is set to '0', the cell corresponding to the MIB may be determined as an on-demand SIB1 cell. The ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 information of the above MIB may be used. In this case, the ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 information of the above MIB may be interpreted and used differently from the conventional method. And / or, for example, a specific MSB (most significant bit) or LSB (least significant bit) may indicate whether it is an on-demand SIB1 cell.

[0264] For example, the MSB or LSB of ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 may indicate whether the cell corresponding to the MIB is an on-demand SIB1 cell. ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 are examples, and other information elements (IEs) within other MIBs may be used. For example, the MSB or LSB of an IE within a specific MIB may indicate whether the cell corresponding to the MIB is an on-demand SIB1 cell. For example, if the MSB or LSB has a predefined / set value, the cell corresponding to the MIB may be determined to be an on-demand SIB1 cell.

[0265] A combination of the above cellBarred information and spare information may be used. If the cellBarred information is barred and the spare information is set to '1', the cell corresponding to the MIB may be determined as the on-demand SIB1 cell. If the cellBarred information is notBarred and the spare information is set to '1', the cell corresponding to the MIB may be determined as the anchor cell.

[0266] [Method 3]

[0267] The terminal can determine whether a cell is an on-demand SIB1 cell based on whether SIB1 is transmitted from the cell during a specific period. That is, whether a specific cell is an on-demand SIB1 cell can be determined based on whether SIB1 is received from a specific cell during a specific period.

[0268] More specifically, the terminal may be configured with a window for monitoring SIB1 in advance. If SIB1 is not received during that period, the terminal may determine at least one cell corresponding to that SIB1 as an on-demand SIB1 cell. For example, if a PDSCH for SIB1 is not received during that period, the terminal may determine at least one cell corresponding to that SIB1 as an on-demand SIB1 cell.

[0269] The terminal may determine an on-demand SIB1 cell through the number of searchspace monitorings (e.g., the number of times the terminal has performed monitoring for the corresponding searchspace (within the window)) for receiving a PDCCH (e.g., a PDCCH addressed by SI-RNTI (system information radio network temporary identifier)) for SIB1 scheduling (i.e., containing scheduling information for SIB1). For example, if the number of searchspace monitorings is above or exceeds a preset / predefined threshold, the cell may be determined to be an on-demand SIB1 cell.

[0270] In this case, the measurement taken by the terminal from the cell's SSB must satisfy the requirements for RRM (radio resource management) measurement. This may be a requirement for accessing the cell. That is, if a specific cell satisfies the requirements but SIB1 is not received from that specific cell, that specific cell may be determined to be an on-demand SIB1 cell. For example, if the RSRP (reference signal received power) and / or RSRQ (reference signal received quality) measured from the cell's SSB satisfy the RRM requirements but SIB1 is not received from that specific cell, that specific cell may be determined to be an on-demand SIB1 cell.

[0271] Through at least one of the above methods, the terminal can determine whether the cell is an on-demand SIB1 cell or an anchor cell.

[0272] In the subsequent section (B) (1602), the terminal receives configuration information for WUS transmission and information for accessing the corresponding on-demand SIB1 cell through upper layer signaling (e.g., RRC or SIB1 or SIB for NES (network energy saving)) or L1 signaling (MSG4 (message 4) or PUSCH / PUCCH) through the anchor cell, and can request SIB1 to access the on-demand SIB1 cell.

[0273] In this case, to determine the connection to the on-demand SIB1 cell rather than the anchor cell, the terminal may decide to access the on-demand SIB1 cell instead of the anchor cell if the difference between the RSRP or RSRQ measured via the SSB through the anchor cell and the on-demand SIB1 cell, respectively, is higher than a specific threshold. For example, if the difference between the RSRP or RSRQ measured from the on-demand SIB1 cell's SSB and the RSRP or RSRQ measured from the anchor cell's SSB is greater than or exceeds a predefined / set threshold, the terminal may decide to connect to the on-demand SIB1 cell. Additionally, the terminal may report the measured results to the anchor cell or request a handover to instruct a request for the on-demand SIB1 cell through the anchor cell. When the anchor cell receives a measurement result from the terminal and / or receives a handover request from the anchor cell to the on-demand SIB1 cell, the anchor cell may instruct the on-demand SIB1 cell to make an on-demand SIB1 request. The anchor cell may instruct the on-demand SIB1 cell regarding the measurement result from the terminal and / or whether an on-demand SIB1 request is made via backhaul signaling.

[0274] If it is identified that access to the anchor cell is impossible based on the cellBarred information in the anchor cell's MIB, the terminal may decide to access the on-demand SIB1 cell.

[0275] In the subsequent section (B) (1602), the terminal can transmit the WUS to the anchor cell or the on-demand SIB1 cell according to the WUS configuration information. For example, the WUS can be transmitted via PUCCH, PRACH, or PUSCH.

[0276] The terminal can transmit the WUS once, or repeatedly in the subsequent section (C) (1603). After transmitting the WUS, the terminal can monitor the PDCCH for SIB1 scheduling from the on-demand SIB1 cell. In the previous section (B) (1602), when the terminal identifies the on-demand SIB1 cell, the terminal may not monitor the PDCCH related to SIB1 (of the on-demand SIB1 cell) until the WUS is transmitted. At this time, the base station may transmit SIB1 without monitoring the WUS after receiving the WUS. That is, after receiving the WUS, the base station may stop monitoring the WUS and transmit the SIB1 of the on-demand SIB1 cell.

[0277] Through at least some of the above methods, the base station and the terminal can perform on-demand SIB1 operations considering multiple cells.

[0278] FIG. 17 is a diagram illustrating an example of an On-demand SIB1 operation considering a single cell of a base station and a terminal according to an embodiment of the present disclosure.

[0279] Referring to FIG. 17, a base station can perform on-demand SIB1 operations considering a single cell. Referring to section (A) (1701), the cell can periodically transmit SSBs and selectively transmit PDCCH for SIB1 and PDSCH for SIB1. For example, whether the cell transmits SIB1 depends on a request from a terminal. The cell does not transmit SIB1 if there is no request from the terminal, but transmits SIB1 if the terminal requests it. Additionally, the cell can monitor the WUS to receive an on-demand request for SIB1. At this time, the terminal can receive SSBs through the cell and then determine whether to perform on-demand SIB1 operations using one or more of the following methods. That is, it can determine whether the cell is an on-demand SIB1 cell (or NES cell) that supports on-demand SIB1 by one or more of the following methods.

[0280] [Method 1]

[0281] The terminal can determine the on-demand SIB1 cell through the SSB's PSS, SSS, or PCI. More specifically, PCI It can be determined as follows.

[0282]

[0283] From the above class The scope is illustrative and in this disclosure class The range of possible values ​​is not limited to this. It can be 0,...,1007, but this is also an example. The range of possible values ​​is not limited to this.

[0284] The terminal is the PSS Cell IDs and / or Cell group ID of the SSS If is set to a specific value that is pre-set or determined, the cell can be identified as an on-demand SIB1 cell. For example, At least some of the possible values ​​and / or At least some of the possible values ​​can be set / determined to indicate that it is an on-demand SIB1 cell.

[0285] The terminal may determine the corresponding cell as an on-demand SIB1 cell if the PCI determined through PSS and SSS is set to a specific value that is pre-configured or determined. For example, At least some of the possible values ​​can be set / determined to indicate that it is an on-demand SIB1 cell.

[0286] [Method 2]

[0287] The terminal can determine the corresponding cell as an on-demand SIB1 cell through the information of the MIB via the PBCH of the SSB. More specifically, the terminal can determine the on-demand SIB1 cell using at least some of the information of the MIB exemplified in [Table 15] below.

[0288] MIB ::= SEQUENCE {systemFrameNumber BIT STRING (SIZE (6)),subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffset INTEGER (0..15),dmrs-TypeA-Position ENUMERATED {pos2, pos3},pdcch-ConfigSIB1 PDCCH-ConfigSIB1,cellBarred ENUMERATED {barred, notBarred},intraFreqReselection ENUMERATED {allowed, notAllowed},spare BIT STRING (SIZE (1))}

[0289] For example, the above spare information may be used to determine whether the cell is an on-demand SIB1 cell. If the above spare information is set to '0', the on-demand SIB1 operation for the cell corresponding to the MIB is determined to be disabled, and if it is set to '1', the cell corresponding to the MIB may be determined to be an on-demand SIB1 cell. Conversely, if the above spare information is set to '1', the on-demand SIB1 operation for the cell corresponding to the MIB may be determined to be disabled, and if the above spare information is set to '0', the cell corresponding to the MIB may be determined to be an on-demand SIB1 cell. The ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 information of the above MIB may also be used to determine whether the cell is an on-demand SIB1 cell. In this case, the ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 information of the above MIB may be interpreted and used differently from the existing information. For example, a specific MSB or LSB may indicate whether it is an on-demand SIB1 cell. For example, the MSB or LSB of ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 may indicate that the cell corresponding to the MIB is an on-demand SIB1 cell. ssb-SubcarrierOffset and / or pdcch-ConfigSIB1 are examples, and other IEs within other MIBs may be used. For example, the MSB or LSB of an IE within a specific MIB may indicate that the cell corresponding to the MIB is an on-demand SIB1 cell. For example, if the MSB or LSB has a predefined / set value, the cell corresponding to the MIB may be determined to be an on-demand SIB1 cell.

[0290] A combination of the above cellBarred information and spare information may be used. If the cellBarred information is barred and the spare information is set to '1', the cell corresponding to the MIB may be determined as a cell with the on-demand SIB1 operation enabled. If the cellBarred information is barred and the spare information is set to '0', the cell corresponding to the MIB may be determined as a cell with the on-demand SIB1 operation disabled.

[0291] [Method 3]

[0292] The terminal can determine whether a cell is an on-demand SIB1 cell based on whether SIB1 is transmitted from the cell during a specific period. That is, whether a specific cell is an on-demand SIB1 cell can be determined based on whether SIB1 was received from a specific cell during a specific period.

[0293] More specifically, the terminal may be configured with a window for monitoring SIB1 in advance. If SIB1 is not received during that period, the terminal may determine at least one cell corresponding to that SIB1 as an on-demand SIB1 cell. For example, if a PDSCH for SIB1 is not received during that period, the terminal may determine at least one cell corresponding to that SIB1 as an on-demand SIB1 cell.

[0294] The terminal may determine an on-demand SIB1 cell through the number of searchspace monitorings (e.g., the number of times the terminal has performed monitoring for the corresponding searchspace (within the window)) for receiving a PDCCH (e.g., a PDCCH addressed by SI-RNTI (system information radio network temporary identifier)) for SIB1 scheduling (i.e., containing scheduling information for SIB1). For example, if the number of searchspace monitorings is above or exceeds a preset / predefined threshold, the cell may be determined to be an on-demand SIB1 cell.

[0295] In this case, the measurement taken by the terminal from the cell's SSB must satisfy the requirements for RRM measurement. This may be a requirement for accessing the cell. That is, if a specific cell satisfies the requirements but SIB1 is not received from that specific cell, that specific cell may be determined to be an on-demand SIB1 cell. For example, if the RSRP and / or RSRQ measured from the cell's SSB satisfy the RRM requirements but SIB1 is not received from that specific cell, that specific cell may be determined to be an on-demand SIB1 cell.

[0296] Through at least one of the above methods, the terminal can determine whether the cell is activating or deactivating on-demand SIB1 operation.

[0297] In the subsequent section (B) (1702), after the terminal determines whether the on-demand SIB1 operation of the cell is enabled, if it is enabled, the terminal can request SIB1 by transmitting a WUS based on pre-configured WUS resource information to transmit the WUS when access is needed. In the subsequent section (C) (1703) after transmitting the WUS based on the terminal's configuration information, the terminal can monitor the PDCCH for scheduling SIB1 from the cell and can perform initial access to the cell after receiving the SIB1. The base station may not monitor the WUS in the cell after receiving the WUS. That is, the base station may stop monitoring the WUS in the cell after receiving the WUS.

[0298] Using FIGS. 18 and 19, a method is described in which a terminal transmits a WUS (or UL WUS), receives a PDCCH that schedules the on-demand SIB1 to receive the on-demand SIB1 from a base station, and receives a PDSCH that transmits the on-demand SIB1. In various embodiments of the present disclosure, receiving a down-control channel, identifying a down-control channel resource, or identifying a resource or CORESET for receiving a PDCCH is collectively referred to as receiving a PDCCH. Furthermore, receiving a PDCCH may be interpreted as receiving a DCI through the PDCCH. Additionally, receiving a PDSCH containing the on-demand SIB1 may be interpreted as receiving the on-demand SIB1. In particular, various embodiments of the present disclosure propose methods for application not only to a terminal that requests the on-demand SIB1 by transmitting a WUS, but also to cases where multiple terminals within a cell receive the on-demand SIB1 or periodic SIB1. The methods proposed below can be applied to on-demand SIB1 operations considering multi-cell and single-cell as described in FIGS. 16 and 17. That is, various embodiments of the present disclosure can be applied to determine the resources required for receiving a PDCCH that schedules the on-demand SIB1 or a PDSCH that includes the on-demand SIB1 when a terminal in an on-demand SIB1 cell that supports on-demand SIB1 transmits a UL WUS to request an on-demand SIB1 and attempts to receive the on-demand SIB1 accordingly.The embodiments of the present disclosure may also be applied to other terminals within the cell to determine the time at which the transmission of an on-demand SIB1 requested by a specific terminal in an on-demand SIB1 cell begins or ends, or the time at which the transmission of a periodic SIB1 determined by a base station begins or ends.

[0299] A situation may be considered in which the NES cell is not transmitting SIB1 (or on-demand SIB1 or periodic SIB) before the terminal transmits the UL WUS. In the above situation, the base station may be in energy saving mode (or NES mode), and the base station in the NES cell can save energy by not transmitting the SIB1. When the terminal transmits the uplink (UL) WUS to the NES cell and the on-demand SIB1 is requested by the UL WUS, at least one of the following methods may be used to transmit the SIB1 to the base station.

[0300] According to the first method, when an on-demand SIB1 is requested by the UL WUS, the base station of the NES cell can transmit a periodic SIB1. The periodic SIB1 transmitted as the on-demand SIB1 is transmitted when the NES cell is in energy-saving mode and uses the same time / frequency resources as the PDCCH / PDSCH for transmitting periodic SIB1 in normal mode, but is transmitted only for a certain period, so it can be distinguished from the periodic SIB1 transmitted by the NES cell in normal mode. The NES cell can decide on its own whether to operate in energy-saving mode or normal mode.

[0301] According to the second method, when an on-demand SIB1 is requested by the UL WUS, the base station of the NES cell can transmit an on-demand SIB1 different from the periodic SIB1. The on-demand SIB1 is transmitted only a certain number of times or in a defined interval when the NES cell is in energy-saving mode, and may be configured to be transmitted over time / frequency resources such as the PDCCH / PDSCH used for transmitting periodic SIB1 in normal mode, or over other time / frequency resources. When the NES cell is in normal mode, it can transmit a periodic SIB1. The NES cell can decide whether to operate in energy-saving mode or normal mode based on its own judgment.

[0302] First, the first method described above will be explained using Fig. 18, and a method for determining whether another terminal in the cell is transmitting SIB1 regarding periodic SIB1 transmission will be explained. By the above method, the Rel-19 terminal can distinguish between periodic SIB1 transmission transmitted as on-demand SIB1 and periodic SIB1 transmission in normal mode, and by determining the transmission interval, it can take advantage of saving terminal reception power required when receiving and decoding SIB1.

[0303] FIG. 18 is a diagram illustrating an example of a downstream channel for scheduling an on-demand SIB1 according to one embodiment of the present disclosure.

[0304] FIG. 18 illustrates a situation in which a UL WUS is transmitted by a specific terminal, and a periodic SIB1 is transmitted as an on-demand SIB1 requested by the UL WUS in the NES cell.

[0305] First, it is explained that a terminal transmits a UL WUS to request an on-demand SIB1, and a periodic SIB1 is transmitted as the on-demand SIB1. The terminal receives WUS configuration information and can transmit a WUS based on the WUS configuration information. Subsequently, the terminal can receive feedback from the base station as a response to the WUS. The feedback may be information indicating whether the base station has received the WUS. The feedback may be transmitted via a downlink control channel or a downlink data channel. Alternatively, it may be transmitted via a Random Access Response (RAR). The receiving beam of the feedback may be quasi-co-located with the transmitting beam of the WUS. The time between the transmission of the WUS and the reception of the feedback may be defined in the standard or may be included within the WUS configuration. Specifically, the time from the slot in which the WUS was transmitted or the last OFDM symbol containing the WUS to the slot in which the feedback is received or the first OFDM symbol containing the feedback may be defined in the standard or may be included within the WUS configuration. If feedback is not received within the above time, the terminal may transmit a WUS requesting an on-demand SIB1 again. If the above feedback is not defined, the terminal may substitute the feedback by receiving a PDCCH scheduling an on-demand SIB1 as a response to the WUS. That is, if the terminal receives a PDCCH scheduling SIB1 after transmitting the WUS, the base station may determine that the WUS has been received. The receiving beam of the PDCCH may be QCL with the transmitting beam of the WUS.The processing time required for the base station to prepare a PDCCH for scheduling an on-demand SIB1 or a PDSCH for transmitting an on-demand SIB1 from the slot in which the above WUS was transmitted or the last OFDM symbol including the WUS may be defined in the specification or may be included within the WUS configuration. Additionally, in addition to the processing time, the time to the radio frame, subframe, or slot in which the PDCCH for scheduling the on-demand SIB1 is transmitted may be additionally defined in the specification or may be included within the WUS configuration.

[0306] According to one embodiment, the time between the reception of the feedback and the transmission of the PDCCH scheduling the on-demand SIB1 may be defined in the specification, or included in the WUS configuration, or included in the feedback. Specifically, the time from the slot in which the feedback is received or the last OFDM symbol containing the feedback to the slot or the first OFDM symbol containing the on-demand SIB1 may be defined by the specification, or included in the WUS configuration, or included in the feedback. The time / frequency resources, period or offset, number of repetitions, and repeating time intervals of the repeating PDCCHs, including the first PDCCH scheduling the on-demand SIB1 to the terminal, may be included in the WUS configuration or RAR, or defined by the specification.

[0307] Resource information required for a terminal to receive on-demand SIB1 is indicated by a CORESET for on-demand SIB1, and the CORESET may be configured through time-frequency resource configuration information of CORESET#0 and control area#0 indicated by an 8-bit (pdcch-ConfigSIB1) within the MIB, or may be configured by WUS configuration information. FIG. 18 shows an embodiment in which CORESET#0, which is QCLed with the SSB determined by the standard to be transmitted by the base station or the SSB actually transmitted (e.g., the first SSB, second SSB, and fourth SSB within the SSB burst of FIG. 18) among CORESET#0 indicated by pdcch-ConfigSIB1, is transmitted as a CORESET for on-demand SIB1.

[0308] The SSBs illustrated in FIG. 18 are illustrated as an example of SSBs actually transmitted from a base station in FIG. 18, and can be applied without limitation based on various SSB resource cases described in FIG. 5, FIG. 6, and FIG. 7.

[0309] In one embodiment, the terminal may determine that the CORESET is QCLed to an SSB having the same index. Based on the QCL, the terminal may receive a PDCCH or PDSCH to receive an on-demand SIB1 from the CORESET.

[0310] In one embodiment, since periodic SIB1 is transmitted only within a certain interval or a certain number of times in the on-demand SIB1 cell, the base station can save energy. The certain interval or the certain number of times may be set by UL WUS configuration information or instructed by the base station by RAR.

[0311] Next, methods for another terminal within the cell to determine whether the base station is transmitting a periodic SIB1 as an on-demand SIB1 requested by a specific terminal's WUS transmission in NES mode, or whether the periodic SIB1 is being transmitted in normal mode, will be explained.

[0312] According to the first method, bits within the PBCH and MIB may be used to indicate to the terminal whether periodic SIB1 is being transmitted as on-demand SIB1 or whether periodic SIB1 is being transmitted in normal mode. In one embodiment, a combination of cellBarred information and spare information in the MIB may be used to indicate whether the cell is one in which on-demand SIB1 operation is enabled. The cellBarred information being barred and spare information being set to '1' may indicate that the cell corresponding to the MIB is a cell in which on-demand SIB1 operation is enabled (or a cell in which energy saving mode is operating or a cell in which on-demand SIB1 transmission is requested by the terminal's UL WUS transmission). If the cellBarred information is barred and the spare information is set to '0', it may indicate that the cell corresponding to the MIB is a cell in which on-demand SIB1 operation is disabled (or a cell in which energy saving mode is not operating, or a cell in which on-demand SIB1 transmission is not requested by the terminal's UL WUS transmission and periodic SIB1 is being transmitted continuously).

[0313] In one embodiment, in a cell where on-demand SIB1 operation is enabled, other terminals within the cell (including terminals in the RRC connected state or terminals in the RRC idle / inactive state) may be indicated that a periodic SIB1 is not being transmitted as an on-demand SIB1 or that a periodic SIB1 is not being transmitted in normal mode by the ssb-SubcarrierOffset in the MIB alone or in combination with an additional 1 bit in the PBCH. For example, the ssb-SubcarrierOffset alone or in combination with an additional 1 bit in the PBCH may indicate the value of k_SSB. A k_SSB of a predetermined value (e.g., 30 or 31) may indicate that the periodic SIB1 is not being transmitted. If the k_SSB value is not the predetermined value (e.g., 30 or 31), it may indicate that the periodic SIB1 is being transmitted.

[0314] k_SSB is subcarrier 0 of the SS / PBCH block and the common resource block Corresponds to the gap between.

[0315] According to one embodiment, whether an on-demand SIB1 is transmitted can be indicated through a Global Synchronization Channel Number (GSCN) range indicated by an MIB. If the GSCN range is a predetermined value, it can indicate that the SIB1 is not transmitted. The GSCN range is [N^Reference_GSCN - N^Start_GSCN, N^Reference_GSCN + N^END_GSCN]. If the on-demand SIB1 is not transmitted, N^Start_GSCN and N^END_GSCN can each be set to 0 by controlResourceSetZero and searchSpaceZero of pdcch-ConfibSIB1 in the MIB, so the GSCN range can be [N^Reference_GSCN, N^Reference_GSCN]. That is, a GSCN range of [N^Reference_GSCN, N^Reference_GSCN] can indicate that the on-demand SIB1 is not transmitted. A GSCN range other than [N^Reference_GSCN, N^Reference_GSCN] may indicate that on-demand SIB1 is transmitted.

[0316] According to the second method, the base station can indicate through L1 signaling whether a periodic SIB1 is being transmitted as an on-demand SIB1 or in normal mode. For example, if the short message indicator in DCI format 1_0, which is CRC scrambled by P-RNTI, is reserved as "00", the periodic SIB1 can be indicated by using a specific bit field in DCI format 1_0, for example, an 8-bit Short Message field. If the short message indicator is set to "01" to indicate only paging and TRS availability, the 8-bit Short Message field can indicate that the on-demand SIB1 or periodic SIB1 is being transmitted. If the short message indicator is set to "10" to indicate only short message and TRS availability, at least one of the following fields may indicate that the on-demand SIB1 or periodic SIB1 is being transmitted: the frequency domain resource assignment field, the time domain resource assignment (TDRA) field, the virtual resource block-to-physical resource block (VRB-to-PRB) mapping field, the modulation and coding scheme (MCS) field, and the transport block (TB) scaling field.If the short message indicator is set to "11" to indicate short message, paging, and TRS availability, some bits of the TRS (tracking reference signal) availability indication or the Reserved bit field may indicate that the on-demand SIB1 or periodic SIB1 is being transmitted.

[0317] According to one embodiment, in the second method using L1 signaling, a specific field within DCI format 1_0 CRC-scraminated with SI-RNTI, DCI format 1_0 CRC-scraminated with a new RNTI for on-demand SIB1, or DCI format 2_9 CRC-scraminated with CellDTRX-RNTI may be reinterpreted, or a new (bit) field may be added thereto to indicate that on-demand SIB1 or periodic SIB1 is being transmitted. In the above example, the DCI format may be changed. That is, this method may be applied to DCI_formats other than the DCI format described above.

[0318] According to one embodiment, the combination of the first and second methods may indicate whether the cell is active for on-demand SIB1 operation, or indicate that periodic SIB1 is transmitted as on-demand SIB1 or that periodic SIB1 is transmitted in normal mode.

[0319] Although the above description indicates that the periodic SIB1 is transmitted, it may also include an indication that the periodic SIB1 is not transmitted.

[0320] According to one embodiment, indicating that the periodic SIB1 is transmitted may indicate that the on-demand SIB1 is not transmitted. Indicating that the periodic SIB1 is not transmitted may also indicate that the on-demand SIB1 is transmitted.

[0321] Next, using FIG. 19, the second method described above will be explained, and a method for another terminal within the cell to determine whether on-demand SIB1 or periodic SIB1 is transmitted will be explained. By the above method, the Rel-19 terminal can distinguish between on-demand SIB1 transmission in energy-saving mode and periodic SIB1 transmission in normal mode, and by determining the transmission interval, it can take advantage of saving terminal reception power required when receiving and decoding SIB1.

[0322] FIG. 19 is a diagram illustrating an example of a downstream channel for scheduling an on-demand SIB1 according to one embodiment of the present disclosure and scheduling a periodic SIB1 after a certain period of time based on a base station judgment.

[0323] FIG. 19 illustrates a situation in which UL WUS is transmitted by a specific terminal, an on-demand SIB1 requested by UL WUS in an NES cell is transmitted, and after a certain period of time, a periodic SIB1 is transmitted in normal mode by the judgment of the base station.

[0324] First, it is explained that a terminal transmits a UL WUS to request an on-demand SIB1, and that the on-demand SIB1 is transmitted. The terminal receives WUS configuration information and can transmit a WUS based on the WUS configuration information. Subsequently, the terminal can receive feedback from the base station as a response to the WUS. The feedback may be information indicating whether the base station has received the WUS. The feedback may be transmitted via a downlink control channel or a downlink data channel. Alternatively, it may be transmitted via a Random Access Response (RAR). The receiving beam of the feedback may be quasi-co-located with the transmitting beam of the WUS. The time between the transmission of the WUS and the reception of the feedback may be defined in the standard or may be included within the WUS configuration. Specifically, the time from the slot in which the WUS was transmitted or the last OFDM symbol containing the WUS to the slot in which the feedback is received or the first OFDM symbol containing the feedback may be defined in the standard or may be included within the WUS configuration. If feedback is not received within the above time, the terminal may transmit a WUS requesting an on-demand SIB1 again. If the above feedback is not defined, the terminal may substitute the feedback by receiving a PDCCH scheduling an on-demand SIB1 as a response to the WUS. That is, if the terminal receives a PDCCH scheduling SIB1 after transmitting the WUS, the base station may determine that the WUS has been received. The receiving beam of the PDCCH may be QCL with the transmitting beam of the WUS.The processing time required for the base station to prepare a PDCCH for scheduling an on-demand SIB1 or a PDSCH for transmitting an on-demand SIB1 from the slot in which the above WUS was transmitted or the last OFDM symbol including the WUS may be defined in the specification or may be included within the WUS configuration. Additionally, in addition to the processing time, the time to the radio frame, subframe, or slot in which the PDCCH for scheduling the on-demand SIB1 is transmitted may be additionally defined in the specification or may be included within the WUS configuration.

[0325] According to one embodiment, the time between the reception of the feedback and the transmission of the PDCCH scheduling the on-demand SIB1 may be defined in the specification, or included in the WUS configuration, or included in the feedback. Specifically, the time from the slot in which the feedback is received or the last OFDM symbol containing the feedback to the slot or the first OFDM symbol containing the on-demand SIB1 may be defined in the specification, or included in the WUS configuration, or included in the feedback. The time / frequency resources, period or offset, number of repetitions, and repeating time intervals of the repeating PDCCHs, including the first PDCCH scheduling the on-demand SIB1 to the terminal, may be included in the WUS configuration or RAR, or defined by the specification.

[0326] Resource information required for a terminal to receive on-demand SIB1 is indicated by a CORESET for on-demand SIB1, and the CORESET may be configured through time-frequency resource configuration information of CORESET#0 and control area#0 indicated by an 8-bit (pdcch-ConfigSIB1) in the MIB, or may be configured by WUS configuration information.

[0327] In one embodiment, in the on-demand SIB1 cell, the on-demand SIB1 is transmitted only within a certain interval or transmitted a certain number of times, so the base station can save energy. The certain interval or the certain number of times may be set by UL WUS setting information or may be instructed by the base station by RAR.

[0328] The base station can change the NES cell from energy-saving mode to normal mode and transmit periodic SIB1 to terminals within the cell. At this time, the transmission resources for periodic SIB1 may follow the existing specifications for Rel-18 terminals. That is, the transmission resources for periodic SIB1 may be determined as the CORESET for periodic SIB1 transmission by the CORESET#0 that is QCLed with the SSB specified in the specifications for the base station to transmit, or the SSB actually transmitted (e.g., the first SSB, second SSB, and fourth SSB within the SSB burst of FIG. 18) among the CORESET#0 indicated by pdcch-ConfigSIB1.

[0329] The above SSBs can be applied without limitation based on various SSB resource cases described in FIGS. 5, 6, and 7.

[0330] In one embodiment, the terminal may determine that the CORESET is QCLed to an SSB having the same index. Based on the QCL, the terminal may receive a PDCCH or PDSCH to receive a periodic SIB1 from the CORESET.

[0331] Next, methods are described for other terminals within the cell to determine whether the base station is transmitting an on-demand SIB1 requested by a specific terminal's WUS transmission in NES mode, or transmitting a periodic SIB1 in normal mode.

[0332] According to the first method, bits within the PBCH and MIB may be used to indicate to the terminal whether on-demand SIB1 is being transmitted in NES mode or periodic SIB1 is being transmitted in normal mode. In one embodiment, a combination of cellBarred information and spare information in the MIB may be used to indicate whether the cell is one in which on-demand SIB1 operation is enabled. When the cellBarred information is barred and the spare information is set to '1', it may indicate that the cell corresponding to the MIB is a cell in which on-demand SIB1 operation is enabled (or a cell in which energy saving mode is operating or a cell in which on-demand SIB1 transmission is requested by the terminal's UL WUS transmission). If the cellBarred information is barred and the spare information is set to '0', it may indicate that the cell corresponding to the MIB is a cell in which on-demand SIB1 operation is disabled (or a cell in which energy saving mode is not operating, or a cell in which on-demand SIB1 transmission is not requested by the terminal's UL WUS transmission and periodic SIB1 is being transmitted continuously).

[0333] In one embodiment, in a cell where on-demand SIB1 operation is enabled, other terminals within the cell (including terminals in the RRC connected state or terminals in the RRC idle / inactive state) may be indicated that the on-demand SIB1 is not being transmitted or that the periodic SIB1 is not being transmitted in normal mode by the ssb-SubcarrierOffset in the MIB alone or in combination with an additional 1 bit in the PBCH. For example, the ssb-SubcarrierOffset alone or in combination with an additional 1 bit in the PBCH may indicate the value of k_SSB. A k_SSB of a predetermined value (e.g., 30 or 31) may indicate that the on-demand SIB1 or periodic SIB1 is not being transmitted. If the k_SSB value is not the predetermined value (e.g., 30 or 31), it may indicate that the on-demand SIB1 or periodic SIB1 is being transmitted. If the on-demand SIB1 and periodic SIB1 transmission resources are configured differently in the UL WUS settings or MIB, the terminals can determine through blind decoding whether the SIB1 being transmitted from a resource is an on-demand SIB1 or a periodic SIB1.

[0334] According to one embodiment, the Global Synchronization Channel Number (GSCN) range indicated by the MIB can indicate whether an on-demand SIB1 or a periodic SIB1 is transmitted. If the GSCN range is a predetermined value, it can indicate that an on-demand SIB1 or a periodic SIB1 is not transmitted. The GSCN range is [N^Reference_GSCN - N^Start_GSCN, N^Reference_GSCN + N^END_GSCN]. If an on-demand SIB1 or a periodic SIB1 is not transmitted, N^Start_GSCN and N^END_GSCN can each be set to 0 by controlResourceSetZero and searchSpaceZero of pdcch-ConfibSIB1 in the MIB, so the GSCN range can be [N^Reference_GSCN, N^Reference_GSCN]. That is, the GSCN range of [N^Reference_GSCN, N^Reference_GSCN] may indicate that on-demand SIB1 or periodic SIB1 is not transmitted. The GSCN range other than [N^Reference_GSCN, N^Reference_GSCN] may indicate that on-demand SIB1 or periodic SIB1 is transmitted. If the transmission resources for on-demand SIB1 and periodic SIB1 are configured differently in the UL WUS configuration or MIB, the terminals can determine through blind decoding whether the SIB1 being transmitted from a given resource is on-demand SIB1 or periodic SIB1.

[0335] According to the second method, the base station can indicate through L1 signaling whether an on-demand SIB1 is being transmitted in NES mode or a periodic SIB1 is being transmitted in normal mode. For example, if the short message indicator in DCI format 1_0, which is CRC scrambled by P-RNTI, is reserved as "00", the on-demand SIB1 or periodic SIB1 can be indicated by using a specific bit field in DCI format 1_0, such as an 8-bit Short Message field. If the short message indicator is set to "01" to indicate only paging and TRS availability, the 8-bit Short Message field can indicate that the on-demand SIB1 or periodic SIB1 is being transmitted. If the short message indicator is set to "10" to indicate only short messages and TRS availability, at least one of the Frequency domain resource assignment field, TDRA field, VRB-to-PRB mapping field, MCS field, and TB scaling field may indicate that the on-demand SIB1 or periodic SIB1 is being transmitted. If the short message indicator is set to "11" to indicate short messages, paging, and TRS availability, some bits of the TRS availability indication or the Reserved bit field may indicate that the on-demand SIB1 or periodic SIB1 is being transmitted.

[0336] According to one embodiment, in the second method using L1 signaling, a specific field within DCI format 1_0 CRC-scraminated with SI-RNTI, DCI format 1_0 CRC-scraminated with a new RNTI for on-demand SIB1, or DCI format 2_9 CRC-scraminated with CellDTRX-RNTI may be reinterpreted, or a new (bit) field may be added thereto to indicate that on-demand SIB1 or periodic SIB1 is being transmitted. In the above example, the DCI format may be changed. That is, this method may be applied to DCI_formats other than the DCI format described above.

[0337] According to one embodiment, the combination of the first and second methods may indicate whether the cell is active for on-demand SIB1 operation, or indicate that on-demand SIB1 is transmitted or periodic SIB1 is transmitted in normal mode.

[0338] Although the above description explains that the on-demand SIB1 or periodic SIB1 is transmitted, it is also possible to include an indication that the on-demand SIB1 or periodic SIB1 is not transmitted.

[0339] FIG. 20 is a flowchart of the operation of a terminal applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.

[0340] Various modifications may be made to the method illustrated in the flowchart of FIG. 20. For example, although it is illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0341] Based on Fig. 20, the base station describes the operation of the terminal during on-demand operation for energy saving.

[0342] Referring to FIG. 20, in step 2001, the terminal can receive an SSB from a base station through one or multiple cells.

[0343] In step 2002, the terminal can determine whether to activate on-demand SIB1 in the cell that received the corresponding SSB. Step 2002 may be omitted.

[0344] In step 2003, the terminal can receive WUS configuration information including information according to an embodiment of the present disclosure.

[0345] In step 2004, the terminal transmits a WUS to request SIB1 based on the information (WUS configuration information). Afterwards, the terminal can monitor the PDCCH for scheduling SIB1.

[0346] In step 2005, the terminal may receive a scheduled SIB1, i.e., an on-demand SIB1 or a periodic SIB1, through a PDCCH (or a DCI detected by the PDCCH) according to an embodiment of the present disclosure in the cell. The terminal may receive the SIB1 based on scheduling information provided through the PDCCH.

[0347] Specific details of the terminal operation according to one embodiment of the present disclosure described above may be referenced to the description of one embodiment of the present disclosure described above.

[0348] FIG. 21 is a flowchart of the operation of a base station applying an energy saving method of a wireless communication system according to one embodiment of the present disclosure.

[0349] Various modifications may be made to the method illustrated in the flowchart of FIG. 21. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0350] Referring to FIG. 21, in step 2101, the base station transmits an SSB through an NES cell. The SSB may be transmitted periodically and may be transmitted for at least one terminal within a cell operated by the base station. Based on WUS configuration information including information according to an embodiment of the present disclosure, the base station may perform WUS monitoring transmitted from the terminal.

[0351] In step 2102, after the base station receives a WUS from the terminal, it may transmit a PDCCH to schedule the transmission of an on-demand SIB1 through an NES cell in accordance with an embodiment of the present disclosure.

[0352] In step 2103, the base station may transmit an on-demand SIB1 to the terminal via an NES cell. The base station may transmit the on-demand SIB1 based on scheduling information provided via the PDCCH (or the DCI detected by the PDCCH). Alternatively, the base station may transmit a periodic SIB1.

[0353] The base station may additionally transmit information indicating whether an on-demand SIB1 is transmitted via an NES cell (or information indicating whether an on-demand SIB1 is transmitted or a periodic SIB1 is transmitted). Such information may be transmitted using at least one of PBCH, MIB, or L1 signaling as previously described.

[0354] Specific details of the base station operation according to one embodiment of the present disclosure described above may be referenced to the description of one embodiment of the present disclosure described above.

[0355] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0356] FIG. 22 is a block diagram of a terminal according to one embodiment of the present disclosure.

[0357] Referring to FIG. 22, the terminal (2200) may include a transceiver (2201), a control unit (e.g., a processor) (2202), and a storage unit (e.g., a memory) (2203). The transceiver (2201), control unit (2202), and storage unit (2203) of the terminal (2200) may operate according to at least one or a combination thereof of the methods corresponding to the above-described embodiments. However, the components of the terminal (2200) are not limited to the illustrated examples. According to other embodiments, the terminal (2200) may include more components or fewer components than the above-described components. Furthermore, in certain cases, the transceiver (2201), control unit (2202), and storage unit (2203) may be implemented in the form of a single chip.

[0358] According to one embodiment, the transceiver (2201) may be composed of a transmitter and a receiver. The transceiver (2201) may transmit and receive signals with a base station. The signals may include control information and data. The transceiver (2201) may be configured to include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (2201) may receive a signal through a wireless channel and output it to a control unit (2202), and transmit the signal output from the control unit (2202) through a wireless channel.

[0359] The control unit (2202) can control a series of procedures that allow the terminal (2200) to operate according to the embodiments of the present disclosure described above. For example, the control unit (2202) can perform or control the operation of the terminal to perform at least one of the methods according to the embodiments of the present disclosure or a combination thereof. The control unit (2202) may include at least one processor. For example, the control unit (2202) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls an upper layer (e.g., an application).

[0360] The storage unit (2203) can store control information (e.g., information related to channel estimation using DMRSs transmitted from a PUSCH included in a signal obtained from a terminal (2200)) or data, and may have an area for storing data required for control of the control unit (2202) and data generated during control by the control unit (2202).

[0361] FIG. 23 is a block diagram of a base station according to one embodiment of the present disclosure.

[0362] Referring to FIG. 23, a base station (2300) may include a transceiver (2301), a control unit (e.g., a processor) (2302), and a storage unit (e.g., a memory) (2303). The transceiver (2301), control unit (2302), and storage unit (2303) of the base station (2300) may be operated according to at least one or a combination thereof of the methods corresponding to the above-described embodiments. However, the components of the base station (2300) are not limited to the illustrated examples. According to other embodiments, the base station (2300) may include more components or fewer components than the above-described components. Furthermore, in certain cases, the transceiver (2301), control unit (2302), and storage unit (2303) may be implemented in the form of a single chip.

[0363] According to one embodiment, the transceiver (2301) may be composed of a transmitter and a receiver. The transceiver (2301) may transmit and receive signals with a terminal. The signals may include control information and data. The transceiver (2301) may be configured to include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (2301) may receive a signal through a wireless channel and output it to a control unit (2302), and transmit the signal output from the control unit (2302) through a wireless channel.

[0364] The control unit (2302) can control a series of procedures to enable the base station (2300) to operate according to the embodiments of the present disclosure described above. For example, the control unit (2302) can perform or control the operation of the base station to perform at least one of the methods according to the embodiments of the present disclosure or a combination thereof. The control unit (2302) may include at least one processor. For example, the control unit (2302) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls an upper layer (e.g., an application).

[0365] The storage unit (2303) can store control information (e.g., information related to channel estimation generated using DMRSs transmitted in a PUSCH determined by the base station (2300)), data, control information received from a terminal, or data, and may have an area for storing data required for control of the control unit (2302) and data generated during control by the control unit (2302).

[0366] The drawings illustrate different examples of user devices / base stations, but various modifications to the drawings may be made. For example, a user device / base station may include any number of individual components in any suitable arrangement. In general, the drawings do not limit the scope of the disclosure to any specific configuration. Furthermore, while the drawings illustrate operating environments in which various user device / base station features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0367] Although the present disclosure has been described by exemplary embodiments, various changes and modifications may be presented to those skilled in the art. The present disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any specific element, step, or function is an essential element to be included in the claims. The scope of the patented subject matter is defined by the claims.

Claims

1. A method for communication by a base station providing an NES (network energy saving) cell in a wireless communication system, wherein A step of receiving a WUS (wake-up signal) for the above NES cell; Based on receiving the above WUS, the step of transmitting an on-demand SIB1 (system information block 1) through the NES cell; and A method comprising the step of transmitting information indicating whether the on-demand SIB1 is transmitted through the NES cell, method.

2. In Paragraph 1, Information indicating whether the above-mentioned on-demand SIB1 is transmitted is transmitted via the MIB (master information block), method.

3. In Paragraph 2, The cellBarred information and spare information within the above MIB indicate whether the above On-Demand SIB1 is transmitted, method.

4. In Paragraph 1, Information indicating whether the above-mentioned on-demand SIB1 is transmitted is transmitted via a master information block (MIB) or a combination of the MIB and a physical broadcast channel (PBCH). method.

5. In Paragraph 4, The sub-SubcarrierOffset of the above MIB or the combination of the above sub-SubcarrierOffset and 1 bit in the above PBCH represents the value of k_SSB, and The above k_SSB having a predetermined value indicates that the on-demand SIB1 is being transmitted, and A k_SSB value other than the above-determined value indicates that the above-determined on-demand SIB1 is not being transmitted, method.

6. In Paragraph 1, Information indicating whether the above-mentioned on-demand SIB1 is transmitted is transmitted via L1 (layer 1) signaling, method.

7. In Paragraph 6, If the short message indicator in DCI (downlink control information) format 1_0 is set to "00" or "01", the short message field indicates whether the on-demand SIB1 is transmitted, and When the above short message indicator is set to "10", at least one of the frequency domain resource assignment field, the time domain resource assignment (TDRA) field, the virtual resource block-to-physical resource block (VRB-to-PRB) mapping field, the modulation and coding scheme (MCS) field, and the transport block (TB) scaling field indicates whether the on-demand SIB1 is transmitted, and If the above short message indicator is set to "11", at least one bit of the tracking reference signal (TRS) availability, or a reserved bit, indicates whether the on-demand SIB1 is transmitted, method.

8. In Paragraph 1, The above-mentioned on-demand SIB1 is transmitted for a predetermined period or a predetermined number of times, method.

9. In Paragraph 1, Step of stopping the transmission of the above-mentioned on-demand SIB1; After stopping the transmission of the above-mentioned on-demand SIB1, a step of switching from NES mode to normal mode; and In the above normal mode, further comprising the step of transmitting periodic SIB1, method.

10. In Paragraph 9, Information indicating whether the above-mentioned on-demand SIB1 is transmitted, indicating that the above-mentioned on-demand SIB1 is not transmitted, indicates that the above-mentioned periodic SIB1 is transmitted. method.

11. As a base station providing NES (network energy saving) cells in a wireless communication system, Transmitter / receiver; and It includes at least one processor, and the at least one processor is: Receive a WUS (wake-up signal) for the above NES cell; Based on receiving the above WUS, transmit on-demand SIB1 (system information block 1) through the above NES cell; and Configured to transmit information indicating whether the on-demand SIB1 is transmitted through the above NES cell, Base station.

12. In Paragraph 11, Information indicating whether the above-mentioned on-demand SIB1 is transmitted is transmitted via the MIB (master information block), Base station.

13. In Paragraph 12, The cellBarred information and spare information within the above MIB indicate whether the above On-Demand SIB1 is transmitted, Base station.

14. In Paragraph 11, Information indicating whether the above-mentioned on-demand SIB1 is transmitted is transmitted via a master information block (MIB) or a combination of the MIB and a physical broadcast channel (PBCH). Base station.

15. In Paragraph 11, The above at least one processor is configured to operate according to the method of any one of claims 5 to 10, Base station.

Images