Method and device for energy saving in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In addition, the present disclosure provides a method and a device for reducing the energy consumption of a base station in a mobile communication system. According to the present disclosure, the problem of excessive energy consumption in a base station in a mobile communication system is resolved, and higher energy efficiency can be achieved. A method of transmitting and receiving a signal by a terminal in a wireless communication system according to an embodiment of the present disclosure comprises the steps of: synchronizing with a first cell; receiving, from the first cell, a first control signal including information on a cell controllable by the first cell; and transmitting data to a second cell on the basis of the first control signal.

Description

Method and device for energy saving in wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for energy saving of a base station 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 the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure provides a method and device for energy saving in a wireless communication system.

[0009] The present disclosure relates to a method for processing a control signal in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0010] A method for transmitting and receiving a signal by a terminal in a wireless communication system according to one embodiment of the present disclosure comprises the steps of: synchronizing with a first cell; receiving a first control signal from the first cell, the first control signal including information about a cell that the first cell can control; and

[0011] A step of transmitting data to a second cell based on the first control signal is included.

[0012] According to one embodiment of the present disclosure, by defining a signal transmission method of a base station in a wireless communication system, the problem of excessive energy consumption can be solved and high energy efficiency can be achieved.

[0013] FIG. 1 illustrates the basic structure of a time-frequency resource domain of a 5G system according to one embodiment of the present disclosure.

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

[0015] FIG. 3 illustrates a random access procedure according to one embodiment of the present disclosure.

[0016] FIG. 4 illustrates a procedure for a terminal to report terminal capability information to a base station according to one embodiment of the present disclosure.

[0017] FIG. 5 illustrates a control resource set (CORESET) as a time-frequency resource to which a PDCCH is mapped according to one embodiment of the present disclosure.

[0018] FIG. 6 illustrates the mapping of DCI and DMRS in REG, which is a basic unit of a downlink control channel according to one embodiment of the present disclosure.

[0019] FIG. 7 illustrates base station beam allocation according to TCI state setting according to one embodiment of the present disclosure.

[0020] FIG. 8 illustrates a hierarchical signaling method for dynamic allocation of PDCCH beams of NR according to one embodiment of the present disclosure.

[0021] FIG. 9 illustrates a TCI indication MAC CE signaling structure for PDCCH DMRS according to one embodiment of the present disclosure.

[0022] FIG. 10 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

[0023] FIG. 11 illustrates an aperiodic CSI reporting method when a CSI-RS offset is 0 according to one embodiment of the present disclosure.

[0024] FIG. 12 illustrates an aperiodic CSI reporting method when a CSI-RS offset is 1 according to one embodiment of the present disclosure.

[0025] FIG. 13 illustrates settings for a bandwidth part in a 5G communication system according to one embodiment of the present disclosure.

[0026] FIG. 14 illustrates DRX (Discontinuous Reception) in a 5G communication system according to one embodiment of the present disclosure.

[0027] Figure 15 is a drawing for explaining an existing network communication system.

[0028] FIG. 16A is a diagram for explaining a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0029] FIG. 16b is a diagram for explaining a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0030] FIG. 17A is a diagram for explaining a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0031] FIG. 17b is a diagram illustrating a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0032] FIG. 18a illustrates the SSB structure of a sync cell and a data cell according to one embodiment of the present disclosure (excluding PBCH).

[0033] FIG. 18b illustrates the SSB structure of a sync cell and a data cell according to one embodiment of the present disclosure (excluding PBCH).

[0034] FIG. 18c illustrates the SSB structure of a sync cell and a data cell according to one embodiment of the present disclosure (excluding PBCH).

[0035] FIG. 19 illustrates a procedure for obtaining PCI between a sync cell, a data cell, and a terminal according to one embodiment of the present disclosure.

[0036] FIG. 20 illustrates a terminal transceiver device according to one embodiment of the present disclosure.

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

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

[0039] For convenience of explanation, devices not directly related to the present disclosure may be omitted from the illustration and description.

[0040] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on their functions in the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0041] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0042] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0043] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0044] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0045] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0046] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0047] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH may also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" may be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0048] Hereinafter, in the present disclosure, higher layer signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Higher layer signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0049] For convenience of explanation, this disclosure uses terms and names defined in the 3GPP NR (New Radio: 5th generation mobile communications standard) standards. However, this disclosure is not limited to these terms and names and can be equally applied to systems conforming to other standards. Furthermore, the term "terminal" can refer to not only mobile phones, smartphones, IoT devices, and sensors, but also other wireless communication devices.

[0050] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, an eNB, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.

[0051] To handle the explosive growth in mobile data traffic, 5G (5G), the next-generation communication system after LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)) and LTE-A (LTE-Advanced or E-UTRA Evolution), is being developed. thThe initial standards for the 5G (New Radio Access Technology Generation) system or New Radio access technology (NR) have been completed. While existing mobile communication systems have focused on conventional voice / data communications, the 5G system aims to satisfy various services and requirements, such as enhanced Mobile Broadband (eMBB) services to improve existing voice / data communications, Ultra-Reliable and Low Latency Communication (URLLC) services to support high-reliability / ultra-low latency communications, and massive Machine Type Communication (MTC) services to support massive machine-to-machine communications.

[0052] While the transmission bandwidth of existing LTE and LTE-A systems per single carrier is limited to a maximum of 20MHz, the 5G system aims to provide ultra-high-speed data services of up to several Gbps by utilizing a much wider ultra-wide bandwidth. Accordingly, the 5G system is considering ultra-high frequency bands from several GHz up to 100 GHz as candidate frequencies, where securing ultra-wide bandwidth frequencies is relatively easy. Additionally, it is possible to secure wide bandwidth frequencies for the 5G system through frequency reallocation or allocation among frequency bands included in the hundreds of MHz to several GHz used in existing mobile communication systems.

[0053] Radio waves in the ultra-high frequency band are sometimes called millimeter waves (mmWave) because their wavelengths are on the order of millimeters. However, in the ultra-high frequency band, the path loss of radio waves increases in proportion to the frequency band, reducing the coverage of mobile communication systems.

[0054] In order to overcome the disadvantage of reduced coverage in the above ultra-high frequency band, beamforming technology can be applied, which uses multiple antennas to concentrate the radiated energy of radio waves to a predetermined target point and increase the transmission distance of radio waves. That is, the beam width of the signal to which the beamforming technology is applied becomes relatively narrow, and the radiated energy is concentrated within the narrowed beam width, thereby increasing the transmission distance. The beamforming technology can be applied to both the transmitter and the receiver. In addition to the effect of increasing coverage, the beamforming technology has the effect of reducing interference in areas other than the beamforming direction. In order for the beamforming technology to operate properly, accurate measurement and feedback methods of the transmission / reception beams are required. The beamforming technology can be applied to a control channel or a data channel that corresponds one-to-one between a predetermined terminal and a base station. Additionally, beamforming technology can be applied to common signals transmitted by a base station to multiple terminals within a system, such as synchronization signals, physical broadcast channels (PBCH), control channels for transmitting system information, and data channels, to increase coverage. When beamforming technology is applied to common signals, beam sweeping technology, which transmits signals by changing the beam direction, is additionally applied so that the common signal can reach terminals located at any location within the cell.

[0055] Another requirement for 5G systems is ultra-low latency services, with transmission delays of approximately 1 ms between transmitters and receivers. One way to reduce transmission delay is to design a frame structure based on a short TTI (Transmission Time Interval), which is shorter than that of LTE and LTE-A. A TTI is the basic time unit used for scheduling, and the TTI of existing LTE and LTE-A systems is 1 ms, which corresponds to the length of one subframe. For example, to meet the requirements for ultra-low latency services in the 5G system, possible short TTIs are 0.5 ms, 0.25 ms, and 0.125 ms, which are shorter than those of existing LTE and LTE-A systems.

[0056] FIG. 1 illustrates the basic structure of a time-frequency resource domain of a 5G system according to one embodiment of the present disclosure. That is, FIG. 1 is a diagram illustrating the basic structure of a time-frequency resource domain, which is a radio resource domain in which data or control channels of a 5G system are transmitted.

[0057] Referring to Figure 1, the horizontal axis in Figure 1 represents the time domain and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain of the 5G system is an OFDM (Orthogonal Frequency Division Multiplexing) symbol. (102) symbols are grouped together to form one slot (106), A plurality of slots can be gathered to form a subframe (105). The length of the subframe is 1.0 ms, and 10 subframes can be gathered to form a 10 ms frame (114). The minimum transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth is the total It can be composed of (104) subcarriers.

[0058] The basic unit of resources in the time-frequency domain is a Resource Element (RE) (112), which can be represented by an OFDM symbol index and a subcarrier index. A Resource Block (RB or Physical Resource Block, PRB) is a resource block in the frequency domain. It can be defined as (110) consecutive subcarriers. In 5G systems, =12, and the data rate can increase in proportion to the number of RBs scheduled to the terminal.

[0059] In a 5G system, a base station maps data in RB units, and scheduling can be performed for RBs, which typically constitute a slot for a given terminal. That is, in a 5G system, the basic time unit for scheduling may be a slot, and the basic frequency unit for scheduling may be an RB.

[0060] Number of OFDM symbols It is determined by the length of the cyclic prefix (CP) added to each symbol to prevent interference between symbols. For example, if the normal CP is applied, =14, when Extended CP is applied =12. Extended CP can be applied to systems with relatively long transmission distances compared to general CP, so that orthogonality between symbols can be maintained. In the case of general CP, since the ratio of CP length to symbol length is maintained at a constant value, the overhead due to CP can be maintained constant regardless of the subcarrier spacing. That is, if the subcarrier spacing is small, the symbol length becomes longer, and thus the CP length can also become longer. Conversely, if the subcarrier spacing is large, the symbol length becomes shorter, and thus the CP length can be reduced. The symbol length and CP length can be inversely proportional to the subcarrier spacing.

[0061] In 5G systems, various frame structures can be supported by adjusting the subcarrier spacing to meet diverse services and requirements. For example,

[0062] - From the perspective of the operating frequency band, the larger the subcarrier spacing, the more advantageous it is for recovering phase noise in the high-frequency band.

[0063] - From a transmission time perspective, if the subcarrier spacing is large, the symbol length in the time domain becomes shorter, and consequently, the slot length becomes shorter, which is advantageous for supporting ultra-low delay services such as URLLC.

[0064] - From a cell size perspective, a longer CP length allows for larger cells to be supported, so a smaller subcarrier spacing allows for relatively larger cells to be supported. In mobile communications, a cell is a concept that refers to the area covered by a single base station.

[0065] The above subcarrier spacing, CP length, etc. are essential information for OFDM transmission and reception. For smooth transmission and reception, the base station and terminal must recognize the subcarrier spacing, CP length, etc. as common values. [Table 1] shows the relationship between the subcarrier spacing configuration (μ), subcarrier spacing (△f), and CP length supported by the 5G system.

[0066] [Table 1]

[0067]

[0068] [Table 2] shows the number of symbols per slot for each subcarrier spacing setting (μ) in the case of the general CP. ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.

[0069] [Table 2]

[0070]

[0071] [Table 3] shows the number of symbols per slot for each subcarrier spacing setting (μ) in the case of extended CP. ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.

[0072] [Table 3]

[0073]

[0074] In the early stages of 5G system deployment, coexistence or dual-mode operation with existing LTE and / or LTE-A (hereinafter referred to as LTE / LTE-A) systems is expected. This allows existing LTE / LTE-A to provide stable system operation to terminals, while the 5G system can provide enhanced services to these terminals. Therefore, the 5G system's frame structure must at least include the LTE / LTE-A frame structure or essential parameter set (subcarrier spacing = 15 kHz).

[0075] For example, comparing a frame structure with a subcarrier spacing setting μ=0 (hereinafter referred to as frame structure A) and a frame structure with a subcarrier spacing setting μ=1 (hereinafter referred to as frame structure B), compared to frame structure A, the subcarrier spacing and RB size of frame structure B are twice as large, and the slot length and symbol length are twice as small. In the case of frame structure B, two slots can be configured into one subframe, and 20 subframes can be configured into one frame.

[0076] Generalizing the frame structure of the above 5G system provides high scalability by ensuring that essential parameter sets, such as subcarrier spacing, CP length, and slot length, have integer multiple relationships for each frame structure. Furthermore, a fixed-length subframe of 1 ms can be defined to represent a reference time unit independent of the frame structure.

[0077] The above frame structure can be applied to correspond to various scenarios. From a cell size perspective, since a longer CP length can support a larger cell, the frame structure A can support a relatively larger cell than the frame structure B. From an operating frequency band perspective, since a larger subcarrier spacing is advantageous for phase noise recovery in a high-frequency band, the frame structure B can support a relatively higher operating frequency than the frame structure A. From a service perspective, since a shorter slot length, which is a basic time unit of scheduling, is advantageous for supporting an ultra-low delay service such as URLLC, the frame structure B can be relatively more suitable for the URLLC service than the frame structure A.

[0078] In the following description of the present disclosure, uplink (UL) may refer to a wireless link through which a terminal transmits data or a control signal to a base station, and downlink (DL) may refer to a wireless link through which a base station transmits data or a control signal to a terminal.

[0079] In the initial access stage where a terminal first accesses the system, the terminal can synchronize downlink time and frequency from a synchronization signal transmitted by a base station through cell search, and obtain a cell identifier (cell ID). Then, the terminal can receive a Physical Broadcast Channel (PBCH) using the obtained cell ID, and obtain a Master Information Block (MIB), which is essential system information, from the PBCH. Additionally, the terminal can obtain cell-common transmission and reception-related control information by receiving system information (System Information Block, SIB) transmitted by the base station. The cell-common transmission and reception-related control information may include random access-related control information, paging-related control information, and common control information for various physical channels.

[0080] A synchronization signal is a signal that serves as a reference for cell search, and subcarrier spacing can be applied to suit channel environments such as phase noise for each frequency band. In the case of a data channel or control channel, as described above, different subcarrier spacings can be applied depending on the service type in order to support various services.

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

[0082] For the purpose of explanation, the following components can be defined:

[0083] - PSS (Primary Synchronization Signal): This signal serves as the basis for DL ​​time / frequency synchronization and provides some cell ID information.

[0084] - SSS (Secondary Synchronization Signal): Serves as a reference for DL ​​time / frequency synchronization and provides some remaining information, including the cell ID. Additionally, it can serve as a reference signal for PBCH demodulation.

[0085] - PBCH (Physical Broadcast Channel): Provides MIB (Master Information Block), which is essential system information required for transmission and reception of data channels and control channels of the terminal. The essential system information may include search space-related control information indicating radio resource mapping information of the control channel, scheduling control information for a separate data channel that transmits system information, and SFN (System Frame Number), which is a frame-unit index that serves as a timing reference.

[0086] - SS / PBCH Block (Synchronization Signal / PBCH Block or SSB): An SS / PBCH block consists of N OFDM symbols and is a combination of PSS, SSS, PBCH, etc. In a system 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. The base station can transmit up to L SS / PBCH blocks, and the L SS / PBCH blocks are mapped within a half frame (0.5 ms). In addition, the L SS / PBCH blocks are periodically repeated in units of a predetermined period P. The period P can be notified to the terminal by the base station through signaling. If there is no separate signaling for the period P, the terminal applies a pre-agreed default value.

[0087] FIG. 2 illustrates an example in which beam sweeping is applied to SS / PBCH block units over time. Referring to FIG. 2, terminal 1 (205) receives an SS / PBCH block using a beam radiated in the direction of #d0 (203) by beamforming applied to SS / PBCH block #0 at time t1 (201). Terminal 2 (206) receives an SS / PBCH block using a beam radiated in the direction of #d4 (204) by beamforming applied to SS / PBCH block #4 at time t2 (202). 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, terminal 1 (205) may have difficulty in obtaining time / frequency synchronization and essential system information from an SS / PBCH block through a beam radiated in the direction of #d4, which is far from the location of terminal 1.

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

[0089] After the terminal acquires MIB and system information from the base station through the initial access procedure, the terminal can perform a random access procedure to transition the link with the base station to a connected state (or RRC_CONNECTED state). Upon completion of the random access procedure, the terminal transitions to the connected state, enabling one-to-one communication between the base station and the terminal. The random access procedure is described in detail below with reference to FIG. 3.

[0090] FIG. 3 illustrates a random access procedure according to one embodiment of the present disclosure.

[0091] Referring to FIG. 3, in the first step (310) of the random access procedure, the terminal transmits a random access preamble to the base station. The random access preamble, which is the first transmission message of the terminal in the random access procedure, may be referred to as message 1. The base station can measure the transmission delay value between the terminal and the base station from the random access preamble and synchronize the uplink. At this time, the terminal can arbitrarily select which random access preamble to use within the random access preamble set given in advance by system information. In addition, the initial transmission power of the random access preamble can be determined according to the path loss between the terminal and the base station measured by the terminal. In addition, the terminal can determine the transmission beam direction of the random access preamble from the synchronization signal received from the base station and transmit the random access preamble.

[0092] In the second step (320), the base station transmits an uplink transmission timing adjustment command to the terminal based on the transmission delay value measured from the random access preamble received in the first step (310). In addition, the base station may transmit uplink resources and power control commands to be used by the terminal as scheduling information. The scheduling information may include control information regarding the terminal's uplink transmission beam.

[0093] If the terminal does not receive the Random Access Response (RAR) (or message 2), which is scheduling information for message 3, from the base station within a predetermined time in the second step (320), the first step (310) can be performed again. If the first step (310) is performed again, the terminal can increase the probability of the base station receiving the random access preamble by transmitting it while increasing the transmission power of the random access preamble by a predetermined step (power ramping).

[0094] In the third step (330), the terminal transmits uplink data (message 3) including its terminal ID to the base station through an uplink data channel (Physical Uplink Shared Channel, PUSCH) using the uplink resources allocated in the second step (320). The transmission timing of the uplink data channel for transmitting Message 3 may follow the timing control command received from the base station in the second step (320). In addition, the transmission power of the uplink data channel for transmitting Message 3 may be determined by considering the power control command received from the base station in the second step (320) and the power ramping value of the random access preamble. The uplink data channel for transmitting Message 3 may mean the first uplink data signal that the terminal transmits to the base station after the terminal transmits the random access preamble.

[0095] In step 4 (340), if the base station determines that the terminal has performed random access without collision with other terminals, it transmits data (message 4) including the ID of the terminal that transmitted uplink data in step 3 (330) to the terminal. If the terminal receives the signal transmitted by the base station in step 4 (340) from the base station, it can determine that the random access has been successful. In addition, the terminal can transmit HARQ-ACK information indicating whether message 4 has been successfully received to the base station through an uplink control channel (Physical Uplink Control Channel, PUCCH).

[0096] If the data transmitted by the terminal in step 3 (330) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not transmit any more data to the terminal. Accordingly, if the terminal fails to receive the data transmitted from the base station in step 4 (340) within a certain period of time, it may determine that the random access procedure has failed and restart from step 1 (310).

[0097] Upon successful completion of the random access procedure, the terminal transitions to the connected state, enabling one-to-one communication between the base station and the terminal. The base station receives UE capability information from the connected terminal and can adjust scheduling by referencing the UE capability information of the terminal. Through the UE capability information, the terminal can inform the base station whether it supports a certain function, the maximum allowable value of the function supported by the terminal, etc. Therefore, the UE capability information reported by each terminal to the base station may have different values ​​for each terminal.

[0098] For example, the terminal may report UE capability information including at least a portion of the following control information as the UE capability information to the base station.

[0099] - Control information related to frequency bands supported by the terminal

[0100] - Control information related to channel bandwidth supported by the terminal

[0101] - Control information related to the maximum modulation method supported by the terminal

[0102] - Control information related to the maximum number of beams supported by the terminal

[0103] - Control information related to the maximum number of layers supported by the terminal

[0104] - Control information related to CSI reporting supported by the terminal

[0105] - Control information on whether the terminal supports frequency hopping

[0106] - Bandwidth-related control information when supporting carrier aggregation (CA)

[0107] - Control information on whether cross carrier scheduling is supported when carrier aggregation is supported.

[0108] FIG. 4 illustrates a procedure for a terminal to report terminal capability information to a base station according to one embodiment of the present disclosure.

[0109] Referring to FIG. 4, at step 410, the base station (402) can transmit a UE capability information request message to the terminal (401). In response to the base station's request for UE capability information, the terminal transmits UE capability information to the base station at step 420.

[0110] Through the above process, terminals connected to the base station are placed in the RRC_CONNECTED state, enabling one-to-one communication. Conversely, terminals that are not connected are placed in the RRC_IDLE state. The operations of terminals in this state are divided as follows.

[0111] - Operates terminal-specific DRX (Discontinuous Reception) cycle set by upper layer

[0112] - Action to receive paging messages from the core network

[0113] - Obtain system information

[0114] - Measurement operations related to surrounding cells and cell reselection

[0115] In 5G systems, a new terminal state called RRC_INACTIVE has been defined to reduce the energy and time consumed during initial access. In addition to the actions performed by RRC_IDLE terminals, RRC_INACTIVE terminals perform the following actions:

[0116] - Storage of AS (Access stratum) information required for cell access

[0117] - Terminal-specific DRX cycle operation set by the RRC layer

[0118] - Setting up and periodically updating an RNA (RAN-based notification area) that can be used during handover by the RRC layer.

[0119] - Monitoring RAN-based paging messages transmitted via I-RNTI

[0120] Below, a scheduling method is described in which a base station transmits downlink data to a terminal or instructs the terminal to transmit uplink data.

[0121] Downlink Control Information (DCI) is control information transmitted from a base station to a terminal via the downlink. It may include downlink data scheduling information or uplink data scheduling information for a given terminal. Typically, the base station independently channel-codes DCI for each terminal and then transmits it to each terminal via the Physical Downlink Control Channel (PDCCH).

[0122] The base station can operate by applying a predetermined DCI format according to the purpose, such as whether it is scheduling information for downlink data (downlink assignment) for the terminal to be scheduled, whether it is scheduling information for uplink data (uplink grant), and whether it is DCI for power control.

[0123] The base station can transmit downlink data to the terminal via the Physical Downlink Shared Channel (PDSCH), a physical channel for downlink data transmission. Scheduling information, such as the specific mapping location in the time and frequency domains of the PDSCH, modulation scheme, HARQ-related control information, and power control information, can be provided by the base station to the terminal via DCI related to downlink data scheduling information among the DCIs transmitted via the PDCCH.

[0124] A terminal can transmit uplink data to a base station via the Physical Uplink Shared Channel (PUSCH), a physical channel for uplink data transmission. Scheduling information, such as specific mapping locations in the time and frequency domains of the PUSCH, modulation schemes, HARQ-related control information, and power control information, can be provided to the terminal by the base station via DCI related to uplink data scheduling information, among the DCIs transmitted via the PDCCH.

[0125] FIG. 5 illustrates a control resource set (CORESET) as a time-frequency resource to which a PDCCH is mapped according to one embodiment of the present disclosure.

[0126] Referring to FIG. 5, two control resource sets (Control Resource Set #1 (501), Control Resource Set #2 (502)) can be set within a UE bandwidth part (510) along the frequency axis and within one slot (520) along the time axis. The Control Resource Sets (501, 502) can be set to specific frequency resources (503) within the entire UE bandwidth part (510) along the frequency axis. The Time Axis can be set to one or more OFDM symbols, and this can be defined as the Control Resource Set Duration (504).

[0127] Control resource set #1 (501) can be set to a control resource set length of 2 symbols, and control resource set #2 (502) can be set to a control resource set length of 1 symbol.

[0128] A base station can configure one or more CORESETs for a terminal through higher layer signaling (e.g., system information, MIB (Master Information Block), RRC (Radio Resource Control) signaling). Configuring a CORESET for a terminal may mean providing information such as a CORESET identifier, the frequency location of the CORESET, and the symbol length of the CORESET. The information that the base station provides to the terminal to configure a CORESET may include at least some of the information included in [Table 4].

[0129] [Table 4]

[0130]

[0131] CORESET is in the frequency domain It can be composed of RBs and in the time domain It can be composed of symbols. The NR PDCCH can be composed of one or more CCEs (Control Channel Elements). One CCE can be composed of six REGs (Resource Element Groups), and a REG can be defined as one RB during one OFDM symbol. Within one CORESET, REGs can be indexed in time-first order, starting with REG index 0 from the first OFDM symbol of the CORESET, the lowest RB.

[0132] Interleaved and non-interleaved transmission methods for PDCCH can be supported. The base station can configure whether to use interleaved or non-interleaved transmission for each CORESET to the terminal through upper layer signaling. Interleaving can be performed in units of REG bundles. A REG bundle can be defined as a set of one or more REGs. The terminal can determine the CCE-to-REG mapping method in the corresponding CORESET based on whether to use interleaved or non-interleaved transmission as configured by the base station, as shown in [Table 5] below.

[0133] [Table 5]

[0134]

[0135] The base station can inform the terminal of configuration information such as which symbol within the slot the PDCCH is mapped to and the transmission cycle through signaling.

[0136] FIG. 6 illustrates the mapping of DCI and DMRS in REG, which is a basic unit of a downlink control channel according to one embodiment of the present disclosure.

[0137] Referring to FIG. 6, the basic unit of the downlink control channel, i.e., REG (603), may include both REs to which DCI is mapped and areas to which DMRS (605), which is a reference signal for decoding the REs, is mapped. Additionally, three DMRSs (605) may be transmitted within one REG (603).

[0138] Hereinafter, the search space of the PDCCH is described. The number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs can be used for link adaptation of the downlink control channel. For example, when AL=L, a single downlink control channel can be transmitted through L CCEs. The UE performs blind decoding to detect a signal without knowing information about the downlink control channel, and for this purpose, a search space representing a set of CCEs can be defined. The search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode at a given aggregation level. Since there are various aggregation levels that create a single group with 1, 2, 4, 8, or 16 CCEs, the UE can have multiple search spaces. A search space set can be defined as the set of search spaces at all established aggregation levels.

[0139] Search spaces can be classified into a common search space (CSS) and a UE-specific search space (USS). A certain group of UEs or all UEs can scan the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling for the System Information Block (SIB) or paging messages. For example, a UE can receive scheduling allocation information for the PDSCH for system information reception by scanning the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs or all UEs must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. UEs can receive scheduling allocation information for the PDSCH or PUSCH by scanning the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's ID and various system parameters.

[0140] The base station can set the search space configuration information of the PDCCH to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can set the number of PDCCH candidates in each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of the DCI format and RNTI to be monitored in the corresponding search space, the CORESET index to be monitored for the search space, etc. to the terminal. For example, the parameters for the search space for the PDCCH may include information such as the following [Table 6].

[0141] [Table 6]

[0142]

[0143]

[0144]

[0145] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal. In search space set 1, the terminal may be configured to monitor DCI format A scrambled with X-RNTI in a common search space, and in search space set 2, the terminal may be configured to monitor DCI format B scrambled with Y-RNTI in a terminal-specific search space.

[0146] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

[0147] In a common search space, a terminal can monitor the following combinations of DCI formats and RNTIs, although these are not limited to the following examples.

[0148] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0149] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0150] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0151] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0152] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0153] - DCI format 2_4 with CRC scrambled by CI-RNTI

[0154] - DCI format 2_5 with CRC scrambled by AI-RNTI

[0155] - DCI format 2_6 with CRC scrambled by PS-RNTI

[0156] - DCI format 2_7 with CRC scrambled by PEI-RNTI

[0157] In a terminal-specific search space, a terminal can monitor the following combinations of DCI formats and RNTIs, although these are not limited to the following examples.

[0158] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0159] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0160] The above RNTIs may follow the following definitions and uses:

[0161] C-RNTI (Cell RNTI): For terminal-specific PDSCH or PUSCH scheduling purposes.

[0162] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0163] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0164] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

[0165] P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.

[0166] SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.

[0167] INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.

[0168] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0169] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0170] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

[0171] The DCI formats described above can follow the definitions shown in [Table 7] below.

[0172] [Table 7]

[0173]

[0174] CORESET p, the search space of aggregation level L in the search space set s can be expressed as the following mathematical formula.

[0175] [Mathematical Formula 1]

[0176]

[0177]

[0178] The value can be 0 for a common search space.

[0179] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's ID (C-RNTI or ID set to the terminal by the base station) and the time index.

[0180] Below, we will specifically describe how to set the TCI state for PDCCH (or PDCCH DMRS) in a 5G communication system.

[0181] The base station can set and indicate the TCI state for the PDCCH (or PDCCH DMRS) through appropriate signaling. According to the above description, the base station can set and indicate the TCI state for the PDCCH (or PDCCH DMRS) through appropriate signaling. The TCI state is to notify the QCL (Quasi co-location) relationship between the PDCCH (or PDCCH DMRS) and other RSs or channels. When a certain reference antenna port A (reference RS #A) and another target antenna port B (target RS #B) are QCLed with each other, it means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated at the antenna port A to the channel measurement from the antenna port B. QCL may need to relate different parameters depending on the situation, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Accordingly, NR supports four types of QCL relationships, as shown in Table 8 below.

[0182] [Table 8]

[0183]

[0184] The above spatial RX parameter may collectively refer to some or all of various parameters, such as Angle of arrival (AoA), Power Angular Spectrum (PAS) of AoA, Angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0185] The above QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info as shown in Table 9 below. Referring to Table 9, the base station can set one or more TCI states to the terminal and inform the RS referencing the ID of the TCI state, i.e., up to two QCL relationships (qcl-Type1, qcl-Type2) for the target RS. At this time, each QCL information (QCL-Info) included in the above TCI state includes the serving cell index and BWP index of the reference RS indicated by the corresponding QCL information, the type and ID of the reference RS, and the QCL type as shown in Table 8 above.

[0186] [Table 9]

[0187]

[0188] FIG. 7 illustrates base station beam allocation according to TCI state setting according to one embodiment of the present disclosure.

[0189] Referring to FIG. 7, the base station can transmit information about N different beams to the terminal through N different TCI states. For example, when N=3, the base station can notify that the antenna ports referencing the different TCI states 700, 705, or 710 have different spatial Rx parameters, i.e., are associated with different beams, by setting the qcl-Type2 parameter included in the three TCI states (700, 705, 710) to be associated with the CSI-RS or SSB corresponding to the different beams and to QCL type D.

[0190] Specifically, the TCI state combinations applicable to the PDCCH DMRS antenna port are as shown in Table 10 below. The fourth row in Table 10 is the combination assumed by the terminal before RRC configuration, and configuration after RRC is not possible.

[0191] [Table 10]

[0192]

[0193] NR supports a hierarchical signaling method as illustrated in FIG. 8 for dynamic allocation of PDCCH beams.

[0194] FIG. 8 illustrates a hierarchical signaling method for dynamic allocation of PDCCH beams of NR according to one embodiment of the present disclosure.

[0195] Referring to FIG. 8, the base station can set N TCI states (805, 810, ..., 820) to the terminal via RRC signaling (800), and can set some of them as TCI states for CORESET (825). Thereafter, the base station can indicate one of the TCI states (830, 835, 840) for CORESET to the terminal via MAC CE signaling (845). Thereafter, the terminal receives the PDCCH based on the beam information included in the TCI state indicated by the MAC CE signaling.

[0196] FIG. 9 illustrates a TCI indication MAC CE signaling structure for PDCCH DMRS according to one embodiment of the present disclosure.

[0197] Referring to FIG. 9, the TCI indication MAC CE signaling for the PDCCH DMRS consists of 2 bytes (16 bits) and includes 1 bit of reserved bit (910), 5 bits of serving cell ID (915), 2 bits of BWP ID (920), 2 bits of CORESET ID (925), and 6 bits of TCI state ID (930).

[0198] A base station can indicate one of the TCI state lists included in the CORESET configuration via MAC CE signaling. Until another TCI state is indicated to the corresponding CORESET via another MAC CE signaling, the terminal assumes that the same QCL information applies to all one or more search spaces connected to the CORESET.

[0199] The above-described PDCCH beam allocation method has a problem in that it is difficult to instruct a beam change faster than the MAC CE signaling delay, and also has a disadvantage in that the same beam is applied to all CORESETs regardless of the search space characteristics, which makes flexible PDCCH beam operation difficult. The following embodiments of the present disclosure provide a more flexible PDCCH beam setting and operation method. In describing the embodiments of the present disclosure below, several distinct examples are provided for the convenience of explanation, but these are not mutually exclusive and can be applied in appropriate combination depending on the situation.

[0200] A base station can set one or more TCI states for a specific control resource set to a terminal, and can activate one of the set TCI states through a MAC CE activation command. For example, if {TCI state#0, TCI state#1, TCI state#2} are set as TCI states for control resource set #1, the base station can transmit a command to the terminal to activate TCI state#0 for control resource set #1 through MAC CE. Based on the activation command for the TCI state received through MAC CE, the terminal can correctly receive DMRS of the corresponding control resource set based on QCL information in the activated TCI state.

[0201] For a control resource set (control resource set #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control resource set #0, the terminal can assume that the DMRS transmitted in control resource set #0 has been QCL'd with the SS / PBCH block identified during the initial access process or the non-contention-based random access process that is not triggered by a PDCCH command.

[0202] For a control resource set (control resource set #X) whose index is set to a value other than 0, if the terminal has not set a TCI state for the control resource set #X, or has set one or more TCI states but has not received a MAC CE activation command to activate one of them, the terminal may assume that the DMRS transmitted in the control resource set #X is QCL'd with the SS / PBCH block identified during the initial access process.

[0203] Next, we will specifically explain downlink control information (DCI) in the 5G system.

[0204] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) can be transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0205] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

[0206] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

[0207] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 11.

[0208] [Table 11]

[0209]

[0210]

[0211]

[0212] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 12.

[0213] [Table 12]

[0214]

[0215]

[0216]

[0217]

[0218]

[0219]

[0220]

[0221]

[0222]

[0223]

[0224]

[0225] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 13.

[0226] [Table 13]

[0227]

[0228]

[0229]

[0230] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 14.

[0231] [Table 14]

[0232]

[0233]

[0234]

[0235]

[0236]

[0237]

[0238]

[0239]

[0240] Below, a time domain resource allocation method for a data channel in a 5G communication system is described.

[0241] The base station can set up a table for time domain resource allocation information for the downlink data channel (Physical Downlink Shared Channel; PDSCH) and the uplink data channel (Physical Uplink Shared Channel; PUSCH) to the terminal through higher layer signaling (e.g., RRC signaling). For the PDSCH, a table consisting of up to maxNrofDL-Allocations=16 entries can be set up, and for the PUSCH, a table consisting of up to maxNrofUL-Allocations=16 entries can be set up. For example, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0) or PDCCH-to-PUSCH slot timing (the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as those in Tables 15 and 16 below may be notified from the base station to the terminal.

[0242] [Table 15]

[0243]

[0244] [Table 16]

[0245]

[0246] The base station can notify the terminal of one of the entries in the table for the above time domain resource allocation information via L1 signaling (e.g., DCI) (e.g., by indicating it with the 'Time Domain Resource Allocation' field in the DCI). The terminal can obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0247] Below, a method for allocating frequency domain resources for data channels in a 5G communication system is described.

[0248] In 5G, two types of methods for indicating frequency domain resource allocation information for downlink data channels (Physical Downlink Shared Channel; PDSCH) and uplink data channels (Physical Uplink Shared Channel; PUSCH) are supported: Resource Allocation Type 0 and Resource Allocation Type 1.

[0249] Resource Allocation Type 0

[0250] RB allocation information can be notified from the base station to the terminal in the form of a bitmap for an RBG (Resource Block Group). At this time, the RBG can be composed of a set of consecutive VRBs (Virtual RBs), and the size P of the RBG can be determined based on a value set as a higher layer parameter (rbg-Size) and the size value of the bandwidth part defined in Table 17 below.

[0251] [Table 17]

[0252]

[0253] - Size The total number of RBGs in bandwidth part i ( ) can be defined as follows.

[0254]

[0255] - Each bit in the bitmap of bit size can correspond to each RBG. RBGs can be indexed in order of increasing frequency starting from the lowest frequency position in the bandwidth part. Within the bandwidth part For the RBGs of the dog, from RBG#0 to RBG#( -1) can be mapped from MSB to LSB of the RBG bitmap. If a specific bit value in the bitmap is 1, the terminal can determine that the RBG corresponding to the bit value is allocated, and if a specific bit value in the bitmap is 0, the terminal can determine that the RBG corresponding to the bit value is not allocated.

[0256] Resource Allocation Type 1

[0257] - RB allocation information can be notified from the base station to the terminal as information on the starting position and length of consecutively allocated VRBs. At this time, interleaving or non-interleaving can be additionally applied to consecutively allocated VRBs. The resource allocation field of resource allocation type 1 can be composed of a resource indication value (RIV), and the RIV indicates the starting point of the VRB ( ) and the length of the consecutively allocated RB ( ) can be composed of. More specifically, RIV within the bandwidth part of the size can be defined as follows.

[0258]

[0259] For the purpose of supporting non-grant-based transmission and reception for a downlink data channel (Physical Downlink Shared Channel; PDSCH) or an uplink data channel (Physical Uplink Shared Channel; PUSCH) to a terminal, a base station can semi-statically set time and frequency transmission resources and various transmission and reception parameters for PDSCH and PUSCH.

[0260] To be more specific,

[0261] For the purpose of supporting downlink (DL) SPS (Semi-Persistent Scheduling) to a terminal, the base station can set the following information as shown in Table 18 through upper layer signaling (e.g. RRC signaling).

[0262] [Table 18]

[0263]

[0264] DL SPS can be set in a primary cell or a secondary cell, and DL SPS can be set in one cell within one cell group.

[0265] In 5G, two types of non-grant (also called Configured Grant, Grant free, etc.)-based transmission methods for uplink data channels (Physical Uplink Shared Channel; PUSCH) can be supported: Type-1 non-grant-based PUSCH transmission with a configured grant and Type-2 non-grant-based PUSCH transmission with a configured grant.

[0266] Non-acknowledgement-based PUSCH transmission type-1

[0267] In non-grant-based PUSCH transmission type-1, the base station can configure specific time / frequency resources (600) that allow non-grant-based PUSCH transmission to the terminal through higher layer signaling, such as RRC signaling. For example, as illustrated in FIG. 6, time-domain allocation information (601), frequency-domain allocation information (602), and period information (603) for the resource (600) can be configured. In addition, the base station can configure various parameters for PUSCH transmission to the terminal through higher layer signaling, such as frequency hopping, DMRS configuration, MCS table, MCS, RBG (Resource Block Group) size, number of repetition transmissions, RV (Redundancy Version), etc. More specifically, the configuration information of Table 19 below can be included.

[0268] [Table 19]

[0269]

[0270]

[0271]

[0272] When the configuration information for non-grant-based PUSCH transmission type-1 is received from the base station, the terminal can transmit the PUSCH periodically with the configured resources (600) without the base station's approval. Various parameters required for transmitting the PUSCH (e.g., frequency hopping, DMRS configuration, MCS, RBG (Resource Block Group) size, number of repeated transmissions, RV (Redundancy Version), number of precoding and layers, antenna ports, frequency hopping offset, etc.) can all follow the configuration values ​​notified by the base station.

[0273] Non-acknowledgement-based PUSCH transmission type-2

[0274] In non-grant-based PUSCH transmission type-2, the base station can set some of the information (e.g., period information (603), etc.) regarding specific time / frequency resources (600) that allow non-grant-based PUSCH transmission to the terminal through higher layer signaling (e.g., RRC signaling). In addition, the base station can set various parameters for PUSCH transmission to the terminal through higher layer signaling (e.g., frequency hopping, DMRS configuration, MCS table, RBG (Resource Block Group) size, number of repetition transmissions, RV (Redundancy Version), etc.). More specifically, the base station can set the configuration information of Table 20 below to the terminal through higher layer signaling.

[0275] [Table 20]

[0276]

[0277]

[0278]

[0279] A base station may transmit a DCI composed of specific DCI field values ​​to a terminal for the purpose of scheduling activation or scheduling release for DL ​​SPS and UL grant Type 2.

[0280] To be more specific,

[0281] The base station can set a Configured Scheduling-RNTI (CS-RNTI) for the terminal, and the terminal can monitor the DCI format in which the CRC is scrambled with the CS-RNTI. If the CRC of the DCI format received by the terminal is scrambled with the CS-RNTI, the New Data Indicator (NDI) is set to '0', and the DCI field satisfies Table 21 below, the terminal can regard the DCI as a command to activate transmission and reception for DL ​​SPS or UL grant Type 2.

[0282] [Table 21]

[0283]

[0284] The base station can set a Configured Scheduling-RNTI (CS-RNTI) for the terminal, and the terminal can monitor the DCI format in which the CRC is scrambled with the CS-RNTI. If the CRC of the DCI format received by the terminal is scrambled with the CS-RNTI, the New Data Indicator (NDI) is set to '0', and the DCI field satisfies Table 22 below, the terminal can regard the DCI as a command to release transmission and reception for DL ​​SPS or UL grant Type 2.

[0285] [Table 22]

[0286]

[0287] The DCI indicating a release for the above DL SPS or UL grant Type 2 follows a DCI format corresponding to DCI format 0_0 or DCI format 1_0, and since DCI format 0_0 or 1_0 does not include a Carrier Indicator Field (CIF), the UE must always monitor the PDCCH in a cell in which the DL SPS or UL grant Type 2 is configured in order to receive a release command for the DL SPS or UL grant Type 2 for a specific cell. Even if a specific cell is configured for cross-carrier scheduling, the UE must always monitor the DCI format 1_0 or DCI format 0_0 in the cell in order to receive a release command for the DL SPS or UL grant Type 2 configured for the cell.

[0288] Below, carrier aggregation and scheduling methods in 5G communication systems are described in detail.

[0289] A terminal can be configured with multiple cells (Cells or CCs (Component Carriers)) from a base station, and can be configured with whether to perform cross-carrier scheduling for the cells configured in the terminal. If cross-carrier scheduling is configured for a specific cell (Cell A, Scheduled Cell), PDCCH monitoring for Cell A may not be performed in Cell A, but may be performed in another cell indicated by cross-carrier scheduling (Cell B, Scheduling Cell). In this case, the scheduled cell (Cell A) and the scheduling cell (Cell B) may be configured with different numerologies. Here, the numerologies may include subcarrier spacing, cyclic prefix, etc. When the numerologies of Cell A and Cell B are different, when the PDCCH of Cell B schedules the PDSCH of Cell A, the following minimum scheduling offset may be additionally considered between the PDCCH and the PDSCH.

[0290] Cross-carrier scheduling method

[0291] ◆ Subcarrier spacing of cell B ( ) is the subcarrier spacing of cell A ( ) is less than, the PDSCH can be scheduled from the next PDSCH slot corresponding to X symbols after the last symbol of the PDCCH received from cell B. Here, X is It may vary depending on When =15kHz, X=4 symbols, When =30kHz, X=4 symbols, When =60kHz, it can be defined as X=8 symbols.

[0292] ◆ Subcarrier spacing of cell B ( ) is the subcarrier spacing of cell A ( ) is greater than, the PDSCH can be scheduled from the point in time corresponding to X symbols after the last symbol of the PDCCH received from cell B. Here, X is It may vary depending on When =30kHz, X=4 symbols, When =60kHz, X=8 symbols, When =120kHz, it can be defined as X=12 symbols.

[0293] Below, the rate matching operation and puncturing operation are described in detail.

[0294] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and reception operations of channel A considering resource C, an area in which resources A and B overlap. The specific operations may follow the contents below.

[0295] Rate Matching Operation

[0296] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that want to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0297] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except for {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0298] Puncture action

[0299] If a base station wants to transmit symbol sequence A to a terminal, and there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0300] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0301] FIG. 10 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by taking into account downlink data channels and rate matching resources according to one embodiment of the present disclosure.

[0302] Referring to FIG. 10, a downlink data channel (PDSCH, 1001) and a rate matching resource (1002) are illustrated. A base station can configure one or more rate matching resources (1002) to a terminal through upper layer signaling (e.g., RRC signaling). The rate matching resource (1002) configuration information may include time-domain resource allocation information (1003), frequency-domain resource allocation information (1004), and period information (1005). In the following, the bitmap corresponding to the frequency-domain resource allocation information (1004) is named "the first bitmap", the bitmap corresponding to the time-domain resource allocation information (1003) is named "the second bitmap", and the bitmap corresponding to the period information (1005) is named "the third bitmap". When all or part of the time and frequency resources of a scheduled data channel (1001) overlap with the set rate matching resources (1002), the base station can rate-match and transmit the data channel (1001) in the rate matching resource (1002) portion, and the terminal can perform reception and decoding after assuming that the data channel (1001) is rate-matched in the rate matching resource (1002) portion.

[0303] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the "rate-matching indicator" in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, the base station can instruct the terminal to perform rate matching by indicating "1" when rate matching is required, and to not perform rate matching by indicating "0" when rate matching is not required.

[0304] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following setting method can be followed.

[0305] RB symbol level

[0306] A terminal can receive up to four RateMatchPatterns for each bandwidth part through upper layer signaling, and one RateMatchPattern can include the following contents.

[0307] - As a reserved resource within the bandwidth part, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may additionally be set.

[0308] - The bandwidth part may include a time and frequency domain resource area set as a control resource set and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0309] RE level

[0310] The terminal can be configured with the following contents through upper layer signaling.

[0311] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0312] - It may contain configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth part.

[0313] Below, we will specifically describe a method for measuring and reporting channel status in a 5G communication system.

[0314] Channel state information (CSI) may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), and / or L1-RSRP (Reference Signal Received Power). The base station may control time and frequency resources for the aforementioned CSI measurement and reporting of the terminal.

[0315] For the aforementioned CSI measurement and reporting, the terminal may receive setting information (CSI-ReportConfig) for N (≥1) CSI reports, setting information (CSI-ResourceConfig) for M (≥1) RS transmission resources, and one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) through upper layer signaling.

[0316] The setup information for the aforementioned CSI measurement and reporting may be as described more specifically in Tables 23 to 29 below.

[0317] [Table 23]

[0318]

[0319]

[0320]

[0321]

[0322] [Table 24]

[0323]

[0324] [Table 25]

[0325]

[0326] [Table 26]

[0327]

[0328] [Table 27]

[0329]

[0330] [Table 28]

[0331]

[0332] [Table 29]

[0333]

[0334] For the aforementioned CSI report setting (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with one downlink (DL) bandwidth part identified by the upper layer parameter bandwidth part identifier (bwp-id) given by the CSI resource setting, CSI-ResourceConfig, associated with the corresponding report setting. For the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, which can be configured from the base station to the terminal by the reportConfigType parameter configured from the upper layer. The semi-persistent CSI reporting method supports 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. For periodic or semi-permanent CSI reporting methods, the UE can receive PUCCH or PUSCH resources for transmitting CSI from the base station through higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources for transmitting CSI can be given as numerology of the uplink (UL) bandwidth portion configured for CSI report transmission. For aperiodic CSI reporting methods, the UE can receive scheduling of PUSCH resources for transmitting CSI from the base station through L1 signaling (the aforementioned DCI format 0_1).

[0335] For the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig can include S (≥1) CSI resource sets (given by the upper layer parameter csi-RS-ResourceSetList). The CSI resource set list can be composed of a non-zero power (NZP) CSI-RS resource set and a SS / PBCH block set, or a CSI-interference measurement (CSI-IM) resource set. Each CSI resource setting can be located in a downlink (DL) bandwidth segment identified by the upper layer parameter bwp-id, and the CSI resource setting can be linked to a CSI reporting setting in the same downlink bandwidth segment. The time domain operation of the CSI-RS resources within the CSI resource setting can be set to one of 'aperiodic', 'periodic', or 'semi-persistent' from the upper layer parameter resourceType. For periodic or semi-permanent CSI resource settings, the number of CSI-RS resource sets can be limited to S=1, and the configured period and slot offset can be given as a numerology of a downlink bandwidth portion identified by bwp-id. A terminal can receive one or more CSI resource settings for channel or interference measurement from a base station through higher layer signaling, and may include, for example, the following CSI resources.

[0336] - CSI-IM resources for interference measurements

[0337] - NZP CSI-RS resources for interference measurements

[0338] - NZP CSI-RS resources for channel measurements

[0339] For CSI-RS resource sets associated with resource settings where the upper layer parameter resourceType is set to 'aperiodic', 'periodic', or 'semi-persistent', the trigger state for the CSI report setting where reportType is set to 'aperiodic' and the resource settings for channel or interference measurements for one or more component cells (CC) can be set with the upper layer parameter CSI-AperiodicTriggerStateList.

[0340] Aperiodic CSI reporting of a terminal can utilize PUSCH, periodic CSI reporting can utilize PUCCH, and semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or PUCCH after activation by MAC control element (MAC CE). As mentioned above, CSI resource settings can also be configured as aperiodic, periodic, or semi-persistent. Combinations between CSI reporting settings and CSI resource settings can be supported based on Table 30 below.

[0341] [Table 30]

[0342]

[0343] Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1 ​​corresponding to the scheduling DCI for the PUSCH. The UE can monitor the PDCCH, acquire the DCI format 0_1, and acquire scheduling information and a CSI request indicator for the PUSCH. The CSI request indicator is N TS(=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by higher layer signaling (reportTriggerSize). One or more aperiodic CSI reporting trigger states that can be set by higher layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0344] - If all bits in the CSI request field are 0, this may mean that no CSI report is requested.

[0345] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, M CSI trigger states can be mapped to 2NTs-1 according to the mapping relationship defined, and one of the trigger states of 2NTs-1 can be indicated by the CSI request field.

[0346] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states can be indicated by the CSI request field.

[0347] Table 31 below shows an example of the relationship between a CSI request indicator and the CSI trigger state that can be indicated by the indicator.

[0348] [Table 31]

[0349]

[0350] A terminal may perform measurement on a CSI resource within a CSI trigger state triggered by a CSI request field, and may generate CSI (including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) therefrom. The terminal may transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in the DCI format 0_1 ​​indicates "1", the terminal may multiplex and transmit the acquired CSI with uplink data (UL-SCH) on the PUSCH resource scheduled by the DCI format 0_1. When 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", the terminal can transmit only CSI without uplink data (UL-SCH) by mapping it to the PUSCH resource scheduled by DCI format 0_1.

[0351] FIGS. 11 and 12 illustrate aperiodic CSI reporting methods when the CSI-RS offset is 0 according to an embodiment of the present disclosure.

[0352] Referring to FIG. 11, the terminal can monitor the PDCCH (1101) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (1105). The terminal can obtain resource information for the CSI-RS (1102) to be measured from the received CSI request indicator. The terminal can determine when to perform measurement on the transmitted CSI-RS (1102) resource based on the time point of receiving DCI format 0_1 ​​and the parameter (aperiodicTriggeringOffset described above) for the offset in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). More specifically, the terminal can receive an offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station through upper layer signaling, and the configured offset value X can mean an offset between a slot in which a DCI that triggers aperiodic CSI reporting is received and a slot in which a CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have a mapping relationship as described in Table 32 below.

[0353] [Table 32]

[0354]

[0355] Referring to FIG. 12, the aforementioned offset value may be set to X=0. In this case, the terminal may receive the CSI-RS (1102) in a slot (corresponding to slot 0 in FIG. 11) in which the DCI format 0_1 ​​that triggers the aperiodic CSI report is received, and may report the CSI information measured with the received CSI-RS to the base station via the PUSCH (1105). The terminal may obtain scheduling information (information corresponding to each field of the aforementioned DCI format 0_1) for the PUSCH (1105) for CSI reporting from the DCI format 0_1. For example, the terminal may obtain information on a slot in which the PUSCH (1105) is to be transmitted from the aforementioned time domain resource allocation information for the PUSCH (1105) in the DCI format 0_1. In an example of FIG. 11, the terminal acquires the K2 value corresponding to the slot offset value for PDCCH-to-PUSCH as 3, and accordingly, the PUSCH (1105) can be transmitted in slot 3 (1109), which is 3 slots away from slot 0 (1106), at the time when the PDCCH (1101) is received.

[0356] In an example of FIG. 12, the terminal can monitor the PDCCH (1201) to obtain DCI format 0_1, and can obtain scheduling information and CSI request information for the PUSCH (1205) from this. The terminal can obtain resource information for the CSI-RS (1202) to be measured from the received CSI request indicator. An example of FIG. 12 shows an example in which the offset value for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (1202) in a slot in which the DCI format 0_1 ​​that triggers aperiodic CSI reporting is received (corresponding to slot 0 (1206) of FIG. 13), and can report the CSI information measured with the received CSI-RS to the base station through the PUSCH (1205).

[0357] Next, we will specifically explain the bandwidth part (BWP) settings in the 5G communication system.

[0358] FIG. 13 illustrates settings for a bandwidth part in a 5G communication system according to one embodiment of the present disclosure.

[0359] Referring to FIG. 13, the UE bandwidth (1400) can be set to two bandwidth parts, namely, bandwidth part #1 (BWP#1) (1301) and bandwidth part #2 (BWP#2) (1302). The base station can set one or more bandwidth parts to the UE, and can set the following information for each bandwidth part, as shown in Table 33.

[0360] [Table 33]

[0361]

[0362] The above information can be transmitted from the base station to the terminal via higher-layer signaling, such as RRC (Radio Resource Control) signaling. At least one bandwidth part among one or more configured bandwidth parts can be activated. Whether or not the configured bandwidth part is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (Downlink Control Information).

[0363] Before RRC (Radio Resource Control) connection, a terminal can receive the initial bandwidth part (Initial BWP) for initial connection from the base station through MIB (Master Information Block). More specifically, during the initial connection phase, the terminal can receive configuration information about a control region (Control Resource Set, CORESET) and a search space where a PDCCH (Physical Downlink Control Channel) for receiving system information (Remaining System Information; which may correspond to RMSI or System Information Block 1; SIB1) required for initial connection can be transmitted through MIB. The control region and search space configured by MIB can each be regarded as identifier (Identity, ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through MIB. Additionally, the base station can notify the terminal of the monitoring cycle and occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range designated as control area #0, obtained from the MIB, as the initial bandwidth part for initial access. At this time, the identifier (ID) of the initial bandwidth part can be considered as 0.

[0364] The settings for the bandwidth part supported by the above 5G can be used for various purposes.

[0365] In one embodiment, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth part configuration. For example, the base station can configure the frequency position (configuration information 2) of the bandwidth part to the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency position within the system bandwidth.

[0366] To support different numerologies, a base station can configure multiple bandwidth parts for a terminal. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth parts can be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. These different bandwidth parts can be frequency-division multiplexed, and when data is to be transmitted or received using a specific subcarrier spacing, the bandwidth part configured for that subcarrier spacing can be activated.

[0367] Additionally, for the purpose of reducing power consumption of the terminal, the base station can configure bandwidth parts with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data using that bandwidth, it can result in very high power consumption. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a traffic-free environment can be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station can configure a bandwidth part with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free environment, the terminal can perform monitoring operations using the 20 MHz bandwidth part, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth part according to the instructions of the base station.

[0368] In the method for setting the bandwidth part, terminals prior to RRC connection can receive configuration information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) for scheduling a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0369] When one or more bandwidth parts are set for a terminal, the base station can instruct the terminal to change the bandwidth part using the bandwidth part indicator field in the DCI. For example, referring to FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0370] As described above, since DCI-based bandwidth part changes can be indicated by DCI scheduling PDSCH or PUSCH (Physical Uplink Shared Channel), when a UE receives a bandwidth part change request, it must be able to seamlessly receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part. To this end, the standard specifies requirements for the delay time (TBWP) required when changing the bandwidth part, which can be defined, for example, as shown in Table 34 below.

[0371] [Table 34]

[0372]

[0373] The bandwidth part change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth part delay time type to the base station.

[0374] According to the requirement on the bandwidth part change delay time described above, when a terminal receives a DCI including a bandwidth part change indicator in slot n, the terminal can complete the change to the new bandwidth part indicated by the bandwidth part change indicator no later than slot n + TBWP, and can perform transmission and reception for the data channel scheduled by the corresponding DCI in the changed new bandwidth part. When the base station wants to schedule a data channel with the new bandwidth part, the base station can determine the time domain resource allocation for the data channel by considering the bandwidth part change delay time (TBWP) of the terminal. That is, when the base station schedules a data channel with the new bandwidth part, the data channel can be scheduled after the bandwidth part change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal may not expect that the DCI indicating the bandwidth part change indicates a slot offset (K0 or K2) value smaller than the bandwidth part change delay time (TBWP).

[0375] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth part change, the terminal may not perform any transmission or reception during the time period corresponding to the third symbol of the slot in which the PDCCH including the DCI is received, to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth part change in slot n and the slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0376] Next, we will explain how to set transmission and reception related parameters for each bandwidth part in 5G.

[0377] The terminal can be configured with one or more bandwidth parts from the base station, and can additionally be configured with parameters to be used for transmission and reception for each configured bandwidth part (e.g., configuration information related to uplink / downlink data channels and control channels, etc.). For example, referring to FIG. 13, if the terminal is configured with bandwidth part #1 (1301) and bandwidth part #2 (1302), the terminal can be configured with transmission / reception parameter #1 for bandwidth part #1 (1301), and can be configured with transmission / reception parameter #2 for bandwidth part #2 (1302). When bandwidth part #1 (1301) is activated, the terminal can perform transmission and reception with the base station based on transmission / reception parameter #1, and when bandwidth part #2 (1302) is activated, the terminal can perform transmission and reception with the base station based on transmission / reception parameter #2.

[0378] More specifically, the following parameters can be set from the base station to the terminal.

[0379] First, for the uplink bandwidth part, the information in Table 35 can be set.

[0380] [Table 35]

[0381]

[0382] According to [Table 35], the terminal can be configured with cell-specific (or cell common or common) transmission-related parameters (e.g., parameters related to a Random Access Channel (RACH), a Physical Uplink Control Channel (PUCCH), and a Physical Uplink Shared Channel)) from the base station (corresponding to BWP-UplinkCommon). In addition, the terminal can be configured with terminal-specific (or dedicated) transmission-related parameters (e.g., parameters related to a PUCCH, a PUSCH, a Configured Grant PUSCH, and a Sounding Reference Signal (SRS)) from the base station (corresponding to BWP-UplinkDedicated).

[0383] Next, for the downlink bandwidth part, the following information can be set as in Table 36.

[0384] [Table 36]

[0385]

[0386] According to [Table 36], the terminal can be configured with cell-specific (or cell common or common) reception-related parameters (e.g., parameters related to a downlink control channel (PDCCH) and a downlink data channel (Physical Downlink Shared Channel)) from the base station (corresponding to BWP-DownlinkCommon). In addition, the terminal can be configured with terminal-specific (or dedicated) reception-related parameters (e.g., parameters related to a PDCCH, a PDSCH, a semi-persistent scheduled PDSCH, and radio link monitoring (RLM)) from the base station (corresponding to BWP-UplinkDedicated).

[0387] Below, we will specifically explain the DRX (Discontinuous Reception) settings in a 5G communication system.

[0388] FIG. 14 illustrates DRX (Discontinuous Reception) in a 5G communication system according to one embodiment of the present disclosure.

[0389] DRX is an operation in which a terminal using a service discontinuously receives data while in an RRC Connected state, where a wireless link is established between the base station and the terminal. When DRX is applied, the terminal turns on the receiver at a specific time to monitor the control channel, and if no data is received for a certain period of time, the receiver is turned off, reducing the terminal's power consumption. DRX operation can be controlled by the MAC layer device based on various parameters and timers.

[0390] Referring to Figure 14, Active time (1405) is the time when the terminal wakes up every DRX cycle and monitors the PDCCH. Active time (1405) can be defined as follows.

[0391] - drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running; or

[0392] - a Scheduling Request is sent on PUCCH and is pending; or

[0393] - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble

[0394] drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer, etc. are timers whose values ​​are set by the base station, and have the function of setting the terminal to monitor the PDCCH when a certain condition is met.

[0395] drx-onDurationTimer(1415) is a parameter for setting the minimum time for which the terminal stays awake in the DRX cycle. drx-InactivityTimer(1420) is a parameter for setting the additional time for which the terminal stays awake when receiving (1430) a PDCCH indicating a new uplink transmission or downlink transmission. drx-RetransmissionTimerDL is a parameter for setting the maximum time for which the terminal stays awake to receive a downlink retransmission in a downlink HARQ procedure. drx-RetransmissionTimerUL is a parameter for setting the maximum time for which the terminal stays awake to receive an uplink retransmission grant in an uplink HARQ procedure. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL can be set as, for example, time, the number of subframes, the number of slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring PDCCH in random access procedure.

[0396] The inActive time (1410) is a time set not to monitor PDCCH during DRX operation and / or a time set not to receive PDCCH. The remaining time excluding the Active time (1405) from the entire time of performing the DRX operation can be the inActive time (1410). If the terminal does not monitor the PDCCH during the Active time (1405), it can enter a sleep or inActive state to reduce power consumption.

[0397] DRX cycle refers to the period during which the terminal wakes up and monitors the PDCCH. In other words, it refers to the time interval or on duration that occurs after the terminal monitors the PDCCH until it monitors the next PDCCH. There are two types of DRX cycles: short DRX cycle and long DRX cycle. Short DRX cycle can be applied optionally.

[0398] Long DRX cycle (1425) is the longer cycle among the two DRX cycles set in the terminal. While operating in Long DRX, the terminal starts drx-onDurationTimer (1415) again at a point in time when Long DRX cycle (1425) has elapsed from the starting point (e.g., start symbol) of drx-onDurationTimer (1415). When operating in Long DRX cycle (1425), the terminal can start drx-onDurationTimer (1415) in a slot after drx-SlotOffset in a subframe satisfying [Mathematical Formula 2] below. Here, drx-SlotOffset means a delay before starting drx-onDurationTimer (1415). drx-SlotOffset can be set to, for example, time, the number of slots, etc.

[0399] [Equation 2]

[0400] [(SFN*10)+subframe number] modulo (drx-LongCycle)= drx-StartOffset

[0401] At this time, drx-LongCycleStartOffset can include Long DRX cycle (1525) and drx-StartOffset, and can be used to define a subframe to start Long DRX cycle (1425). For example, drx-LongCycleStartOffset can be set to time, number of subframes, number of slots, etc.

[0402] A Short DRX cycle is a shorter cycle among the two DRX cycles defined in a terminal. The terminal operates in a Long DRX cycle (1425), and when a certain event occurs during the Active time (1405), for example, when a PDCCH indicating a new uplink transmission or downlink transmission is received (1430), the terminal starts or restarts the drx-InactivityTimer (1420), and if the drx-InactivityTimer (1420) expires or a DRX command MAC CE is received, the terminal may operate in a short DRX cycle. For example, in FIG. 14, the terminal starts the drx-ShortCycleTimer at the time when the previous drx-onDurationTimer (1415) or drx-InactivityTimer (1420) expires, and may operate in a short DRX cycle until the drx-ShortCycleTimer expires. When the terminal receives (1430) a PDCCH indicating a new uplink transmission or downlink transmission, the terminal may extend the Active Time (1405) or delay the arrival of the InActive Time (1410) in anticipation of additional uplink transmission or downlink transmission in the future. While operating in short DRX, the terminal starts drx-onDurationTimer (1415) again when the short DRX cycle has elapsed from the start point of the previous on duration. After that, when drx-ShortCycleTimer expires, the terminal operates in the Long DRX cycle (1425) again.

[0403] When operating in a short DRX cycle, the terminal can start drx-onDurationTimer (1415) after drx-SlotOffset in a subframe satisfying [Mathematical Formula 3] below. Here, drx-SlotOffset refers to a delay before starting drx-onDurationTimer (1415). For example, drx-SlotOffset can be set to time, number of slots, etc.

[0404] [Equation 3]

[0405] [(SFN*10)+subframe number] modulo (drx-ShortCycle)

[0406] = (drx-StartOffset)modulo(drx-ShortCycle)

[0407] Here, drx-ShortCycle and drx-StartOffset can be used to define the subframe at which the Short DRX cycle will start. drx-ShortCycle and drx-StartOffset can be set to, for example, time, number of subframes, number of slots, etc.

[0408] The DRX operation has been described with reference to FIG. 14 so far. According to one embodiment, the terminal can reduce its power consumption by performing the DRX operation. However, even if the terminal performs the DRX operation, the terminal does not always receive the PDCCH related to the terminal during the Active Time (1405). Therefore, in one embodiment of the present disclosure, a signal for controlling the operation of the terminal can be provided to more efficiently save the power of the terminal.

[0409] As mentioned above, in order to achieve ultra-high-speed data services reaching several Gbps, 5G systems support ultra-wide-bandwidth signal transmission and reception or utilize spatial multiplexing methods using multiple transmit / receive antennas, while supporting various power-saving modes to reduce power consumption of terminals. On the other hand, base stations also incur excessive power consumption. For example, the number of required power amplifiers (PAs) increases in proportion to the number of transmit antennas installed in the base station or terminal. The maximum output of the base station and terminal depends on the characteristics of the PA, and the maximum output of the base station generally varies depending on the cell size covered by the base station. The maximum output is usually expressed in dBm. The maximum output of the terminal is usually 23 dBm or 26 dBm. As an example, a commercial 5G base station can be equipped with 64 transmit antennas and corresponding 64 PAs in the 3.5 GHz frequency band and can operate with a 100 MHz bandwidth. Ultimately, the energy consumption of base stations increases in proportion to the power amplifier output and operating time. Compared to LTE base stations, 5G base stations feature relatively high operating frequency bands, resulting in wider bandwidth and numerous transmit antennas. While these features have the effect of increasing data rates, they come at the cost of increased base station energy consumption. Therefore, the more base stations that comprise a mobile communications network, the greater the energy consumption of the entire mobile communications network.

[0410] As mentioned above, the energy consumption of a base station is largely dependent on the operation of the power amplifier. Since the power amplifier is involved in the base station's transmission operation, the downlink (DL) transmission operation of the base station is closely related to the base station's energy consumption. The uplink (UL) reception operation of the base station accounts for a relatively small portion of the base station's energy consumption. The physical channels and physical signals transmitted by the base station in the downlink are as follows.

[0411] - PDSCH (Physical Downlink Shared Channel): A downlink data channel containing data to be transmitted to one or more terminals.

[0412] - PDCCH (Physical Downlink Control Channel): A downlink control channel that contains scheduling information for the PDSCH and PUSCH (Physical Uplink Control Channel). Alternatively, the PDCCH alone can transmit control information such as slot format and power control commands without the PDSCH or PUSCH to be scheduled. The scheduling information includes resource information to which the PDSCH or PUSCH is mapped, HARQ-related information, power control information, etc.

[0413] - PBCH (Physical Broadcast Channel): A downlink broadcast channel that provides MIB (Master Information Block), which is essential system information required for transmission and reception of data channels and control channels of the terminal.

[0414] - PSS (Primary Synchronization Signal): This signal serves as the basis for DL ​​time / frequency synchronization and provides some cell ID information.

[0415] - SSS (Secondary Synchronization Signal): A signal that serves as a basis for DL ​​time and / or frequency (hereinafter referred to as time / frequency) synchronization and provides some remaining information such as cell ID.

[0416] - DM-RS (Demodulation Reference Signal): Reference signal for channel estimation of terminals for each of PDSCH, PDCCH, and PBCH.

[0417] - CSI-RS (Channel-state Information Reference Signal): A downlink signal that serves as a basis for measuring the terminal's downlink channel status.

[0418] - PT-RS (Phase-tracking Reference Signal): Downlink signal for phase tracking

[0419] From a base station energy saving perspective, when the base station stops downlink transmission, the power amplifier operation is also stopped, which increases the base station energy saving effect. In addition, the operation of the remaining base station devices, such as the baseband device, is also reduced, enabling additional energy savings. Similarly, although uplink reception operation accounts for a relatively small portion of the base station's overall energy consumption, if uplink reception can be stopped, additional energy savings can be achieved.

[0420] The downlink transmission behavior of a base station fundamentally depends on the amount of downlink traffic. For example, if there is no data to transmit to the terminal via the downlink, the base station does not need to transmit the PDSCH or the PDCCH to schedule the PDSCH. Alternatively, if the data can be temporarily delayed for reasons such as insensitivity to transmission delay, the base station may refrain from transmitting the PDSCH and / or PDCCH.

[0421] In contrast, physical channels and physical signals such as PSS, SSS, PBCH, and CSI-RS have the characteristic of being repeatedly transmitted at a predetermined, promised cycle, regardless of data transmission to the terminal. Therefore, even if the terminal does not receive data, it can continuously update downlink time / frequency synchronization, downlink channel status, radio link quality, etc. In other words, the PSS, SSS, PBCH, and CSI-RS must be transmitted on the downlink regardless of downlink data traffic, and this causes base station energy consumption. Therefore, base station energy savings can be achieved by controlling the transmission of the signals unrelated to (or with low relevance to) data traffic to occur less frequently.

[0422] Through the above two base station energy saving methods, the energy saving effect of the base station can be maximized by stopping or minimizing the operation of the base station's power amplifier and related RF devices, baseband devices, etc. during the time period when the base station does not perform downlink transmission.

[0423] Alternatively, the energy consumption of the base station can be reduced by switching off some of the base station antennas or power amplifiers (hereinafter referred to as 'Base Station Energy Saving Method 2'). In this case, as a countermeasure to the energy saving effect of the base station, adverse effects such as a decrease in cell coverage or throughput may accompany. For example, if a base station equipped with 64 transmit antennas and corresponding 64 power amplifiers in the 3.5 GHz frequency band as described above and operating with a bandwidth of 100 MHz activates only 4 transmit antennas and 4 power amplifiers for a certain period of time and switches off the rest in order to save base station energy, the base station energy consumption during that period will be reduced to approximately 1 / 16 (= 4 / 64), but it will be difficult to achieve the cell coverage and throughput that would be achieved if the existing 64 antennas and power amplifiers were assumed due to the decrease in maximum transmit power and beamforming gain.

[0424] The above-mentioned base station energy saving methods can be further categorized into three types. There is a base station energy saving method in the frequency domain that adjusts the size of the BWP according to the base station traffic, a base station energy saving method in the space domain that adaptively reduces the number of antenna ports, and a base station energy saving method in the time domain that adjusts the cycles of CSI-RS, SSB, and DRX. These three base station energy saving methods can be used alone or in combination according to the characteristics of the base station, such as base station traffic or coverage, and the corresponding change information must be shared with the terminal.

[0425] As a result, in a situation where the information changed above or the energy saving mode is shared with the terminal, the impact of energy-consuming technologies such as existing CA / DC, PDSCH / PUSCH / PUCCH repetition, and mTRP on coexistence with the energy saving mode must also be examined.

[0426] The base station energy saving method proposed in the present disclosure is explained below through specific examples.

[0427] <Example 1>

[0428] The first embodiment describes the structure of a network communication system for realizing energy saving.

[0429] Figure 15 is a drawing for explaining an existing network communication system.

[0430] Referring to Figure 15, multiple cells Cell 1, Cell 2, 3, and 4 are illustrated. Since all cells must support not only connected terminals (or connected terminals) but also idle terminals (or idle terminals), even when there is no traffic, the base station has no choice but to save energy in short periods, such as light sleep or micro sleep, for periodic reference signal (e.g., SSB) transmission.

[0431] In Fig. 15, multiple cells are illustrated, but it should be noted that a cell may correspond to at least one of a Distributed Unit (DU), a Radio Unit (RU), a Transmission and Reception Point (TRP), or a carrier, but is not limited thereto. Referring to Fig. 15, an idle terminal synchronizes with a cell transmitting a sync signal, selects a cell to perform initial access, and performs a Random Access Channel (RACH) procedure to finally access the cell. Fig. 15 illustrates a case where a terminal accesses Cell 1 to perform communication. In the existing communication system of Fig. 15, it may be difficult to save network power because all cells are powered on for synchronization / access with the terminal in consideration of the mobility of the idle terminal.

[0432] FIG. 16a and FIG. 16b are diagrams for explaining a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0433] Referring to Fig. 16a, a plurality of cells Cell 1 and Cell 2 (Cell 2A, Cell 2B, Cell 2C) are illustrated. Unlike Fig. 15, Cell 1 may be a sync / access cell, and Cell 2 (Cell 2A, Cell 2B, Cell 2C) may be cells that only perform data communication with a terminal without performing a sync / access function (data cells). Although a plurality of cells are illustrated in Fig. 16a, it should be noted that a cell may correspond to at least one of a Distributed Unit (DU), a Radio Unit (RU), a Transmission and Reception Point (TRP), or a carrier, but is not limited thereto.

[0434] Referring to Fig. 16a, an idle terminal synchronizes with Cell 1 transmitting a sync signal and performs a RACH (Random Access Channel) procedure to finally make an initial connection to Cell 1. After making an initial connection to Cell 1, the terminal attempts to connect to a cell (e.g., Cell 2A, Cell 2B, or Cell 2C) where it will ultimately transmit and receive actual data. In Fig. 16a, it is assumed that Cell 1 can control Cell 2A, Cell 2B, and Cell 2C to save network power. Accordingly, Cell 1 can provide the terminal with settings for the cells controlled by Cell 1 (1601) and determine the cells to be controlled through the inter-cell interface (1602).

[0435] Specifically, Cell 1 may be able to control the Tx / Rx power on / off of the cell(s) it controls, for example, Cell 2A, Cell 2B, and / or Cell 2C. Accordingly, when Cell 1 requests (1603) the cell(s) it controls to turn on the Tx / Rx power, the cell(s) will be able to transmit and receive signals with the terminal. There may be various methods for turning on / off the Tx / Rx power of the cell(s) it controls. For example, the location information of the terminal may be utilized. However, it is noted that the present invention does not limit the method to a specific method.

[0436] Through the method presented in Fig. 16a, Cell 2A, Cell 2B, and Cell 2C can be in a deep sleep state, and only the cell(s) with Tx / Rx on at the request of Cell 1 will be powered on (On state) and be able to transmit a signal to the terminal. In Fig. 16a, a reference signal is illustrated as a signal transmitted by the cell(s) with Tx / Rx on, but it should be noted that the present invention does not limit the signal transmitted by the cell(s) with Tx / Rx on to a specific signal. Therefore, the terminal will be able to receive the reference signal from the cell(s) with Tx / Rx on and perform data communication. In Fig. 16a, a case in which the terminal performs data communication with Cell 2A is illustrated.

[0437] Next, referring to Fig. 16b, a plurality of cells Cell 1 and Cell 2 (Cell 2A, Cell 2B, Cell 2C) are illustrated. Unlike Fig. 16a, Cell 1 is a sync cell, and Cell 2 (Cell 2A, Cell 2B, Cell 2C) may be cells that perform initial connection and data communication with a terminal (access / data cells) without performing the sync function. It should be noted that although a plurality of cells are illustrated in Fig. 16b, a cell may correspond to at least one of a Distributed Unit (DU), a Radio Unit (RU), a Transmission and Reception Point (TRP), or a carrier, but is not limited thereto.

[0438] Referring to Fig. 16b, an idle terminal can synchronize with a cell transmitting a sync signal and select the corresponding cell. In Fig. 16b, a case in which Cell 1 is selected is illustrated. In Fig. 16b, it is assumed that Cell 1 can control Cell 2 (Cell 2A, Cell 2B, Cell 2C) to save network power. Accordingly, Cell 1 can provide the terminal with settings for the cells controlled by Cell 1 (1604) and determine the cells to be controlled through the inter-cell interface (1605).

[0439] Specifically, Cell 1 may be able to control the Tx / Rx power on / off of the cell(s) it controls, for example, Cell 2A, Cell 2B, and / or Cell 2C. Accordingly, when Cell 1 requests (1606) the cell(s) it controls to turn on the Tx / Rx power, the cell(s) will be able to transmit and receive signals with the terminal. There may be various methods for turning on / off the Tx / Rx power of the cell(s) it controls. For example, the location information of the terminal may be utilized. However, it is noted that the present invention does not limit the method to a specific method.

[0440] Through the method presented in Fig. 16b, Cell 2 (Cell 2A, Cell 2B, Cell 2C) can be in deep sleep state, and only the cell(s) that have Tx / Rx on at the request of Cell 1 will be powered on (On state) and be able to transmit a signal to the terminal. In Fig. 16b, a reference signal is illustrated as a signal transmitted by the cell(s) that have Tx / Rx on, but it should be noted that the present invention does not limit the signal transmitted by the cell(s) that have Tx / Rx on to a specific signal. Unlike Fig. 16a, Fig. 16b illustrates a case where a RACH (Random Access Channel) procedure is performed with the cell(s) that have Tx / Rx on by Cell 1, not Cell 1. Fig. 16b illustrates a case where a terminal performs a RACH procedure with Cell 2A and then connects to perform data communication.

[0441] FIG. 17a and FIG. 17b are diagrams for explaining a network communication system for realizing energy saving according to one embodiment of the present disclosure.

[0442] Referring to Fig. 17a, a plurality of cells Cell 1 and Cell 2 (Cell 2A, Cell 2B, Cell 2C) are illustrated. Cell 1 is a sync / access cell, and Cell 2 (Cell 2A, Cell 2B, Cell 2C) may be data cells that do not perform sync / access functions and only perform data communication to a terminal. Unlike Figs. 16a and 16b, in the system of Figs. 17a and 17b, Cell 2A, Cell 2B, and Cell 2C may include a WUR (Wake-up receiver). In the case of including a WUR, Cell 2 (Cell 2A, Cell 2B, Cell 2C) may turn off the MR (Main Radio) and go into an ultra deep sleep state, which may be more advantageous for energy saving. Although multiple cells are illustrated in FIG. 17a, it is noted that a cell may correspond to at least one of a Distributed Unit (DU), a Radio Unit (RU), a Transmission and Reception Point (TRP), or a carrier, but is not limited thereto.

[0443] Referring to Fig. 17a, an idle terminal synchronizes with Cell 1 transmitting a sync signal, selects a cell among Cell 1, Cell 2A, Cell 2B, or Cell 2C to perform initial access, and performs a RACH (Random Access Channel) procedure to finally access the cell. In Fig. 17a, it is assumed that Cell 1 can provide information about Cell 2 (Cell 2A, Cell 2B, Cell 2C). Therefore, Cell 1 can provide the terminal with settings for other cells (Cell 2A, Cell 2B, Cell 2C) (1701). The terminal that receives the information can transmit a WUS (Wake-up signal) to other cells (Cell 2A, Cell 2B, Cell 2C) (1702). And the cells (Cell 2A, Cell 2B, Cell 2C) that were in the ultra deep sleep state will be able to receive the WUS signal and turn on the MR (On state) to transmit the signal to the terminal. At this time, the settings for the other cells (Cell 2A, Cell 2B, Cell 2C) may include settings for the power saving mode operation of each cell.

[0444] If the MR of all cells (Cell 2A, Cell 2B, Cell 2C) are turned on, the network power saving effect may be reduced. Therefore, it is necessary to use various methods to wake up only the necessary cells. For example, a method may be considered in which the MR is turned on only when the strength of the WUS signal received by cells (Cell 2A, Cell 2B, Cell 2C) that were in an ultra deep sleep state is higher than a predetermined threshold. Here, the strength of the WUS signal may be named WUSRP (Wake-up signal received power). Various methods may be considered for setting the threshold. Specifically, settings may be considered through RRC, MAC-CE, DCI, or a combination thereof. It should be noted that the method for increasing the network power saving effect in the present invention is not limited to the above method.

[0445] In Fig. 17a, a reference signal is illustrated as a signal transmitted by cells with MRs turned on, but it should be noted that the present invention does not limit the signal to a specific signal. In Fig. 17a, a case is illustrated where the MR of Cell 2A, which has received a WUS, is turned on, transmits a reference signal to the terminal, and performs data communication. At this time, the MRs of Cell 2B and Cell 2C maintain an ultra deep sleep state.

[0446] Next, referring to FIG. 17b, a plurality of cells Cell 1 and Cell 2 (Cell 2A, Cell 2B, Cell 2C) are illustrated. Unlike FIG. 17a, Cell 1 is a sync cell, and Cell 2 (Cell 2A, Cell 2B, Cell 2C) may be access / data cells that perform initial connection and data communication with a terminal without performing the sync function. Unlike FIG. 16, in the system of FIG. 17, Cell 2 (Cell 2A, Cell 2B, Cell 2C) may include a WUR (Wake-up receiver). In the case of including a WUR, Cell 2 (Cell 2A, Cell 2B, Cell 2C) may turn off the MR (Main Radio) and go into an ultra deep sleep state, which may be more advantageous for energy saving. Although multiple cells are illustrated in FIG. 17b, it is noted that a cell may correspond to at least one of a Distributed Unit (DU), a Radio Unit (RU), a Transmission and Reception Point (TRP), or a carrier, but is not limited thereto.

[0447] Referring to Fig. 17b, an idle terminal can synchronize with a cell transmitting a sync signal and select the corresponding cell. In Fig. 17b, a case where Cell 1 is selected is illustrated. In Fig. 17b, it is assumed that Cell 1 can provide information about Cell 2 (Cell 2A, Cell 2B, Cell 2C). Therefore, Cell 1 can provide the terminal with settings for other cells (Cell 2A, Cell 2B, Cell 2C) (1703). The terminal that receives the information can transmit a WUS (Wake-up signal) to other cells (Cell 2A, Cell 2B, Cell 2C) (1704). In addition, the cells that were in an ultra deep sleep state (Cell 2A, Cell 2B, Cell 2C) will receive the WUS signal and turn on the MR (On state) to transmit a signal to the terminal. At this time, the settings for other cells (Cell 2A, Cell 2B, Cell 2C) may include settings for power saving mode operation of each cell.

[0448] If the MR of all cells (Cell 2A, Cell 2B, Cell 2C) are turned on, the network power saving effect may be reduced. Therefore, it is necessary to use various methods to wake up only the necessary cells. For example, a method may be considered in which the MR is turned on only when the strength of the WUS signal received by cells (Cell 2A, Cell 2B, Cell 2C) that were in an ultra deep sleep state is higher than a predetermined threshold. Here, the strength of the WUS signal may be named WUSRP (Wake-up signal received power). However, it should be noted that the method for increasing the network power saving effect in the present invention is not limited to the above method.

[0449] In Fig. 17b, a reference signal is illustrated as a signal transmitted by cells with MR turned on, but it should be noted that the present invention does not limit the signal to a specific signal. Unlike Fig. 17a, Fig. 17b illustrates a case where a terminal performs a RACH (Random Access Channel) procedure with access / data cells (Cell 2A, Cell 2B, Cell 2C). Fig. 17b illustrates a case where a terminal performs data communication by connecting after performing the RACH procedure with Cell 2A. At this time, the MR of Cell 2B and Cell 2C maintains an ultra deep sleep state.

[0450] <Second embodiment>

[0451] The second embodiment relates to the allocation of physical cell IDs (PCIs). PCIs are primarily used by terminals to decode DL PHY layer channels.

[0452] In the case of LTE, PCI is typically used for initialization of the following sequence generation.

[0453] - CRS sequence generation

[0454] - Scrambling sequence generation for DL ​​PHY channels (ie, PDCCH, PDSCH, PMCH, PBCH, and etc)

[0455] - RS group hopping pattern for PUCCH and PUSCH

[0456] - RS sequence hopping for PUSCH

[0457] In the case of NR, PCI is typically used for initialization of the following sequence generation.

[0458] - Scrambling sequence generation for PBCH

[0459] - Scrambling sequence generation for PDCCH (if pdcch-DMRS-ScramblingID is not configured)

[0460] - Scrambling sequence generation for PXSCH and PUCCH formats 2 / 3 / 4 (if dataScrablingIdentityPXSCH is not configured)

[0461] - DMRS sequence generation for PDCCH (if pdcch-DMRS-ScramblingID is not configured)

[0462] - DMRS sequence generation for PDSCH and PUCCH formats 2 / 3 / 4 (if scramblingID is not configured)

[0463] - DMRS sequence generation for PUSCH (if scramblingID is not configured in case of OFDM or if nPUSCH-Identity is not configured in case of DFT-s-OFDM)

[0464] For example, a DMRS sequence for PDSCH is generated as shown in the following mathematical formula.

[0465] [Equation 4]

[0466]

[0467] Here, c(i) is a gold sequence of length 31, and the initialization of this sequence is generated as follows.

[0468] [Equation 5]

[0469]

[0470] Here is the number of symbols per slot, is the slot number within a frame, and l is the OFDM symbol number within the slot.

[0471] If the higher-layer parameter DMRS-DownlinkConfigIE is provided and the PDSCH is scheduled by the PDCCH using DCI format 1_1 CRC scrambled with C-RNTI or CS-RNTI, About are indicated in scramblingID0 and scramblingID1 respectively in DMRS-DownlinkConfigIE.

[0472] If the higher-layer parameter DMRS-DownlinkConfigIE is provided and the PDSCH is scheduled by the PDCCH using DCI format 1_0 CRC scrambled with C-RNTI or CS-RNTI, About Each is indicated in scramblingID0 within DMRS-DownlinkConfigIE.

[0473] Except for the above cases That is, in most cases, it is PCI. It is involved in the initialization of most sequence generations, and each terminal obtains this PCI from the SSB and uses it to decode DL PHY layer channels.

[0474] PCI It consists of two parts as shown in the mathematical formula below, and can be obtained from PSS and SSS, respectively.

[0475] [Equation 6]

[0476]

[0477] Here is the cell group ID that can be obtained from SSS, is the sector ID that can be obtained from PSS. It can have three sequences from 0 to 2, and while LTE uses the Zadoff-Chu sequence, NR uses the M-sequence. In LTE, 168 sequences from 0 to 167 can be created by concatenating two M-sequences, whereas in NR, 336 sequences from 0 to 335 can be created by utilizing the PN Gold sequence (XOR of two M-sequences).

[0478] Therefore, the PCI calculated through [Mathematical Formula 6] makes it more robust to inter-cell interference by strengthening the randomization of sequences, as LTE can have 504 unique sequences, while NR can have a total of 1008 unique sequences.

[0479] Considering the scenarios of the first embodiment, the existing gNB can perform functional split according to the function suitable for idle / inactive UE and connected UE. However, if the two functions are divided in the existing deployed gNB, the coverage of the data cell or access data cell for the connected UE may be reduced and the data rate may be reduced. Therefore, in order to satisfy the requirements for coverage and data rate for the connected UE, the gNB may be converted to a data cell or access / data cell to primarily support the connected UE, and an additional sync cell or sync / access cell may be required to support the idle / inactive UE. Therefore, the following contents are about PCI allocation at the time of initial connection in a situation where a sync cell or sync / access cell (conveniently referred to as a sync cell) and an access / data cell or data cell (conveniently referred to as a data cell) coexist.

[0480] As can be seen in the first embodiment, a sync cell manages multiple data cells. At this time, the PCI of a data cell may be the same as or different from the PCI of a sync cell. If the PCI of a data cell and the PCI of a sync cell are the same, all data cells use the same scramble, making it impossible for the terminal to determine which data cell is transmitting. Therefore, each data cell can be distinguished by using a separate ID, such as the logical ID determined by the sync cell. On the other hand, if the PCI of a data cell and the PCI of a sync cell are different, each data cell uses a different scramble sequence, allowing the terminal to distinguish each data cell. However, in the target scenario, the number of cells per unit area increases compared to the existing scenario (addition of sync cells), requiring more sequence randomization to reduce inter-cell interference. Therefore, in this case, more PCIs may be required.

[0481] Here, if the data cell is in a deep sleep state, the terminal cannot obtain the PCI of the data cell because it does not receive SSB from the data cell. Therefore, in this case, each sync cell must transmit information of the data cell containing the PCI to the terminal (e.g., WUS configuration, SSB configuration, carrier frequency of the data cell, bandwidth, etc.). This information can be transmitted from the sync cell to the terminal through the 'Configurations for data cell' transmission performed in (1601) and (1604) of FIG. 16 and (1701) and (1703) of FIG. 17. In this process, if the terminal does not access the sync cell and receives the 'Configurations for data cell' as shown in (b) of FIG. 16 and (b) of FIG. 17, the 'Configurations for data cell' can be received through SIB because the terminal has not established an RRC connection. On the other hand, if 'Configurations for data cell' is received after random access to a sync cell as in (a) of Fig. 16 and (a) of Fig. 17, since the terminal is in an RRC connection state, 'Configurations for data cell' can be received through SIB or RRC configuration.

[0482] However, when information about the PCI of a data cell is transmitted in a sync cell, significant overhead can occur due to PCI. This overhead can be reduced by correlating the PCI between the sync cell and the data cell.

[0483] For example, there may be differences in the specific method of reducing overhead due to PCI depending on whether the PCI of a sync cell and the PCI of a data cell are the same or have different values. First, let's assume that the PCI of a sync cell and the PCI of a data cell are the same. In this case, since the PCI of a sync cell and the PCI of a data cell are the same, the sequence initialization values ​​of various channels / signals such as DMRS are also the same. Therefore, from the perspective of the terminal, if the frequency bands of the sync cell and the data cell are the same, it is impossible to tell whether the received information is from the sync cell or the data cell. If the frequency bands of the sync cell and the data cell are different, there is a problem in that the terminal cannot distinguish multiple data cells within a sync cell. Therefore, to solve this problem, the 'Configurations for data cell' transmitted in the sync cell can transmit a logical cell ID that can distinguish each data cell instead of the PCI of the data cells.

[0484] Second, let's assume that the PCI of the sync cell and the PCI of the data cell are different. In this case, since the sequence initialization values ​​of various channels / signals are different, the terminal can easily distinguish between the sync cell, the data cell, and each data cell. However, this can lead to a significant amount of PCI overhead, and interference randomization may not be effective as the PCI increases. To mitigate this drawback, it may be necessary to structure the PCI of the sync cell and the data cell as hierarchically as possible. A specific example of this is described in the third embodiment.

[0485] To reduce PCI overhead, the method by which a terminal acquires the PCI or logical ID described above is also a key factor. First, a sync cell can transmit configuration information for a data cell to the terminal via "Configurations for data cell." This operation increases overhead linearly with the number of data cells. Second, each terminal can acquire the PCI of a data cell through SSB detection without the help of a sync cell. In this case, the overhead is not significantly different from the existing method. However, a method that appropriately considers both methods may exist, and this is described in the third embodiment.

[0486] <Third Embodiment>

[0487] The third embodiment relates to PCI settings and SSB structure when the PCI of the sync cell and the data cell are different or the same.

[0488] First, there is the case where the PCI of the sync cell is different from the PCI of the data cell. As mentioned in the second embodiment, the PCI of the sync cell and the data cell may have a hierarchical structure. In this case, the sync cell and the data cell may share a partial or full set of each other's PICs.

[0489] [Table 37] lists the number of cases in which a data cell can have PCIs when the PCIs of the sync cell and data cell are different.

[0490] [Table 37]

[0491]

[0492] Alt 1 is when the sync cell and data cell fully or partially share the PCI, and Alt 2 is when the sync cell and data cell's PCI are completely different. Alt 1-1 is when the sync cell's PCI is class (The shaded values ​​in [Table 37]) can only be detected in PSS. This is the case when only the sync cell and the data cell are shared. In this case, for the data cell, Additional definitions are needed (values ​​not shaded in [Table 37]). At least Since the PCI of the data cell has a different set from the PCI of the sync cell, a separate sequence different from the sequence used in the sync cell (e.g., the combination of two M-sequences in LTE and the XOR of two M-sequences in NR, i.e., the PN Gold sequence) must be used so that the minimum distance of the sequence between the sync cell and the data cell is not reduced. If multiple data cells exist in one sync cell, the minimum sequence for the sync cell is For more data cells This can be greater than or equal to the PCI that can be expressed for the data cell. It can be the same as before.

[0493] Alt 1-2 can only be detected in SSS This is the case when only the sync cell and the data cell are shared. In this case, for the data cell, Additional definitions are needed for (values ​​not shaded in [Table 37]). At least Since the PCI of the data cell has a different set from the PCI of the sync cell, a separate sequence different from the sequence used in the sync cell (e.g., Zadoff-Chu sequence in LTE, M-sequence for NR) must be used, and the minimum distance of the sequence between the sync cell and the data cell does not decrease. If multiple data cells exist in one sync cell, the minimum distance for the sync cell is For more data cells This can be greater than or equal to the PCI that can be expressed for the data cell. It can be the same as before.

[0494] Alt 1-3 can be detected in PSS and SSS , is shared by sync cell and data cell, but has a third ID, This is the case where it exists. In this case, for the data cell Additional definitions are needed for (values ​​not shaded in [Table 37]). At least Since the PCI of the data cell has a different set from the PCI of the sync cell, a separate sequence (e.g., tertiary SS (TSS)) different from the PSS and SSS used in the sync cell must be used so that the minimum sequence distance between the sync cell and the data cell is not reduced. Or, through “Configurations for data cell” without a separate sequence (e.g., TSS) The value for can be transmitted from the sync cell to the terminal. The PCI that can be expressed for the data cell is Here silver This is the maximum number of IDs that can be held.

[0495] FIGS. 18A to 18C illustrate the SSB structure of a sync cell and a data cell according to one embodiment of the present disclosure (excluding PBCH).

[0496] The terminal must synchronize with the sync cell to receive information about the data cell from the sync cell regardless of whether it accesses the sync cell. To this end, the SSB structure of the sync cell may have a PSS (1801) and an SSS (1802) as shown in Fig. 18a. A terminal that receives an SSB having a PSS (1801) and an SSS (1802) of the sync cell and After obtaining , the data cell is searched, the SSB is received from the activated data cell, and the PCI of the data cell is calculated. If the SSB structure of the data cell is as shown in Fig. 18a, for Alt 1-1 and Alt 1-2 in [Table 37], either the PSS or the SSS will be identical to that of the sync cell. On the other hand, for the PSS or SSS that is not identical to that of the sync cell, a value having a different sequence from that of the sync cell will exist. Alternatively, as shown in Fig. 18b, since there is no need to additionally know the value already known through the sync cell, only one of the PSS or SSS may be transmitted (1805). Alternatively, only one of the PSS, SSS, or TSS may be transmitted.

[0497] For Alt 1-3, additional Since the value is required, as in Fig. 18c and are received through SSS (1811) and PSS (1812) respectively, can also be received through TSS (1813). In this case, since the structure of SSB is changed in the case of data cells, additional settings for TSS, etc. must be defined. First, the type and number of sequences must be defined. Assuming that PSS and SSS are the same as NR, TSS can increase linearly according to the increasing number of data cells, and must have a large enough value to ensure sufficient interference randomization. Second, the location of resources for TSS must be defined. As shown in Fig. 18c, there may be a one symbol difference between SSS and TSS (in this case, PBCH can be transmitted within the symbol), or TSS can be transmitted in the symbol immediately following SSS. In the case of Alt 1-3, it can be transmitted as shown in Fig. 18a and Fig. 18b. For example, in the case of transmission as shown in Fig. 18b, it is already from the sync cell. and is transmitted Since only information about the SS is required, only one SS may be transmitted. Or, as in Fig. 18b, it may be difficult to synchronize with only one SS, so the existing SSB structure is used as is, as in Fig. 18a, and the terminal receives the scrambled PSS or SSS from the received SSB. Based on the ID, check whether the data cell you are looking for is under the selected sync cell, and in the remaining SSS or PSS, Through PCI for actual You can extract the value.

[0498] In [Table 37], Alt 2 refers to a situation where the PCIs of sync and data cells have completely different sets. Therefore, the sequences for the PCIs used in sync cells and the sequences for the PCIs used in data cells must be completely different. In this case, the PCI for the data cell is received by the terminal via SSB, and the terminal can compare the PCI list for the data cell for Alt 2, which was pre-shared via the sync cell, with the PCI for the data cell received via sync and SSB.

[0499] FIG. 19 illustrates a procedure between a sync cell, a data cell, and a terminal for obtaining PCI according to one embodiment of the present disclosure.

[0500] First, the sync cell transmits the SSB, which is a periodic signal (1901), and the UE synchronizes with the sync cell and performs random access (1902) depending on whether it has access to the sync cell. Then, the terminal receives configurations for data cells from the sync cell (1903) and obtains information about the data cell based on the received configurations for data cells. The information about the data cell may include at least one of information that the terminal can obtain through SIB, such as carrier frequency and bandwidth for the data cell, SSB structure or location, or full or partial information of PCI. For example, in the case of partial information, assuming that the sync cell and data cell have a hierarchical structure, as in Alt 1-3 may include. A terminal that receives (1903) Configurations for data cell may transmit (1904) a WUS according to its capability. At this time, the terminal may transmit the WUS by scrambling the PCI of the sync cell so that it can be received in the data cell within the selected sync cell, or by scrambling the UE ID, which is the unique ID of the terminal. When the WUS is transmitted (1904), the data cell measures the size of the received WUS and then determines whether to wake up the main radio of the data cell through coordination with the sync cell. For example, whether to wake up the main radio of the data cell may be instructed through a wake-up indication (1905) received from the sync cell. If the data cell does not have a function for WUR, the sync cell may determine whether to wake up the main radio of the data cell and transmit the wake-up indication. The data cell that receives the wake-up indication wakes up the main radio and transmits an SSB (1906) to synchronize with the terminal. Although not shown in the drawing, the terminal may receive an indication to receive an SSB from a sync cell, or may receive an SSB from a data cell when a predetermined amount of time has elapsed after a WUS transmission (e.g., when a timer expires after a WUS transmission).

[0501] The SSB of a data cell may vary depending on whether it fully or partially shares the PCI with the sync cell. For example, in cases where the PCI of the sync cell and the PCI of the data cell are completely different, as in Alt-2 in [Table 37], the sync cell may fully indicate the PCI of the data cell in the configurations for data cell (1903), or the data cell may scramble the PCI in the sequence initialization of the PSS and SSS, similar to the existing SSB, and transmit it. On the other hand, in an environment where some or all parts are shared, as in Alt-1 in [Table 37], the terminal may extract some of the PCI of the data cell based on the PCI of the sync cell, and thus the SSB structure may be transformed and transmitted as in Alt 1-1 to 1-3. This SSB structure can be transmitted through the configurations for data cell (1903) of the sync cell.

[0502] Next, consider the case where the PCI of a sync cell is the same as the PCI of a data cell. As mentioned in the second embodiment, the PCI of sync cells and data cells can have a hierarchical structure. In this case, since the PCIs of sync cells and data cells are externally identical, the data cells within the sync cell must be distinguished through the logical cell ID. Just as the PCI is used for scrambling each channel or generating DMRS sequences, the logical cell ID can also be used for sequence generation. If the logical cell ID functions identically to the PCI, it will not differ significantly from the virtual cell ID used in existing CA or mTRP. However, unlike the virtual cell ID, the logical cell ID can also be transmitted to idle / inactive terminals. If the logical cell ID does not function identically to the PCI, all data cells will have the same cell ID, making it difficult for the terminal to distinguish between them. Consequently, as in the former case, the logical ID must be involved in each sequence generation, and the logical cell ID must be transmitted as shown in [Table 38].

[0503] [Table 38]

[0504]

[0505] Alt 1 is the Sync cell class (The shaded values ​​in [Table 38]) can only be detected in PSS. This data cell is retransmitted and additionally is transmitted via SSS. The terminal receives it via PSS. After checking once more that it is identical to the sync cell, through SSS Receives and calculates the cell ID of the data cell. Cell ID calculation is performed class In addition, it is received from the SSS of the sync cell. It is determined based on the three ID values.

[0506] Alt 2 can only be detected in SSS This data cell is retransmitted and additionally is transmitted through PSS. The terminal receives it through SSS. After checking once more that it is the same as the sync cell, through PSS Receives and calculates the cell ID of the data cell. Cell ID calculation is performed class In addition, it is received from the PSS of the sync cell. It is determined based on the three ID values.

[0507] Alt 3 can be detected in PSS and SSS , This data cell is retransmitted and additionally is transmitted through TSS. The terminal receives it through PSS. and received through SSS After checking once more that it is identical to the sync cell, through TSS Receives and calculates the cell ID of the data cell. Cell ID calculation is performed class , and received by TSS It is determined based on the three ID values.

[0508] Alt 4 is the SSB transmitted in the data cell and the PSS and SSS transmitted in the sync cell. , In this case, the terminal recognizes that the transmitted SSB is a data cell controlled by the sync cell, and then transmits it in the sync cell. Based on the cell ID calculated by considering the PCI of the sync cell, scramble or DMRS sequence generation of other channels is performed. In the sync cell, in “Configurations for data cell” Only the terminal can be notified, or when the terminal has the ability to access the sync cell, information about the data cells can be received at the terminal when the terminal receives a random access response (RAR) after transmitting the PRACH.

[0509] Figure 20 illustrates a terminal transceiver device according to one embodiment of the present disclosure. For convenience of explanation, the illustration and description of devices not directly related to the present disclosure may be omitted.

[0510] Referring to FIG. 20, the terminal may include a transmitter (2004) including an uplink transmission processing block (2001), a multiplexer (2002), and a transmission RF block (2003), a receiver (2008) including a downlink reception processing block (2005), a demultiplexer (2006), and a reception RF block (2007), and a control unit (2009). The control unit (2009) may control each of the configuration blocks of the receiver (2008) for receiving a data channel or control channel transmitted by the base station as described above, and each of the configuration blocks of the transmitter (2004) for transmitting an uplink signal.

[0511] In the transmitter (2004) of the terminal, the uplink transmission processing block (2001) can generate a signal to be transmitted by performing processes such as channel coding and modulation. The signal generated in the uplink transmission processing block (2001) can be multiplexed with another uplink signal by a multiplexer (2002), and then transmitted to the base station after signal processing in the transmission RF block (2003).

[0512] The terminal's receiving unit (2008) demultiplexes the signal received from the base station and distributes it to each downlink receiving processing block. The downlink receiving processing block (2005) can perform processes such as demodulation and channel decoding on the downlink signal of the base station to obtain control information or data transmitted by the base station. The terminal receiving unit (2008) can support the operation of the control unit (2009) by applying the output result of the downlink receiving processing block to the control unit (2009).

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

[0514] As illustrated in FIG. 21, the terminal of the present disclosure may include a processor (2130), a transceiver (2110), and a memory (2120). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the processor (2130), the transceiver (2110), and the memory (2120) may be implemented in the form of a single chip. According to one embodiment, the transceiver (2110) of FIG. 21 may include the transmitter (2004) and receiver (2008) of FIG. 20. In addition, the processor (2130) of FIG. 21 may include the control unit (2009) of FIG. 20.

[0515] According to one embodiment, the processor (2130) may control a series of processes that enable the terminal to operate according to the embodiments of the present disclosure described above. For example, according to the embodiments of the present disclosure, the components of the terminal may be controlled to perform a transmission and reception method of the terminal depending on whether the base station mode is the base station energy saving mode or the base station normal mode. There may be one or more processors (2130), and the processors (2130) may perform transmission and reception operations of the terminal in a wireless communication system that applies the carrier bundle of the present disclosure described above by executing a program stored in the memory (2120).

[0516] The transceiver (2110) can transmit and receive signals with a base station. The signals transmitted and received with the base station can include control information and data. The transceiver (2110) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (2110) is only one embodiment, and the components of the transceiver (2110) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (2110) can receive a signal through a wireless channel and output it to the processor (2130), and transmit a signal output from the processor (2130) through the wireless channel.

[0517] According to one embodiment, the memory (2120) can store programs and data necessary for the operation of the terminal. In addition, the memory (2120) can store control information or data included in signals transmitted and received by the terminal. The memory (2120) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (2120). According to one embodiment, the memory (2620) can store a program for performing transmission and reception operations of the terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.

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

[0519] As illustrated in FIG. 22, the base station of the present disclosure may include a processor (2230), a transceiver (2210), and a memory (2220). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the processor (2230), the transceiver (2210), and the memory (2220) may be implemented in the form of a single chip.

[0520] The processor (2230) may control a series of processes so that the base station can operate according to the above-described embodiments of the present disclosure. For example, the processor may control components of the base station to perform a method for scheduling a terminal according to whether the base station mode is the base station energy saving mode or the base station normal mode according to the above-described embodiments of the present disclosure. There may be one or more processors (2230), and the processors (2230) may execute a program stored in the memory (2220) to perform the method for scheduling a terminal according to whether the base station mode of the above-described embodiments of the present disclosure is the base station energy saving mode or the base station normal mode.

[0521] The transceiver (2210) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (2210) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal and down-converts the frequency, etc. However, the transceiver (2210) is only one embodiment, and the components of the transceiver (2210) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (2210) can receive a signal through a wireless channel and output it to the processor (2230), and transmit a signal output from the processor (2230) through the wireless channel.

[0522] According to one embodiment, the memory (2220) can store programs and data required for the operation of the base station. In addition, the memory (2220) can store control information or data included in signals transmitted and received by the base station. The memory (2220) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (2220). According to one embodiment, the memory (2220) can store a program for performing a method for scheduling a terminal depending on whether the base station mode, which is an embodiment of the present disclosure described above, is a base station energy saving mode or a base station normal mode.

[0523] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0524] Meanwhile, the present specification and drawings disclose preferred embodiments of the present disclosure, and although specific terms are used, they are used in a general sense only to easily explain the technical contents of the present disclosure and to help understand the disclosure, and are not intended to limit the scope of the present disclosure. It will be apparent to those skilled in the art to which the present disclosure pertains that other modified examples based on the technical idea of ​​the present disclosure are possible in addition to the embodiments disclosed herein. In addition, each of the above embodiments can be combined and operated as needed.

[0525] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of operating a terminal in a wireless communication system, A step of obtaining a synchronization signal (SS) of the first cell from the first cell; A step of synchronizing with the first cell based on the synchronization signal of the first cell; A step of receiving, from the first cell, configuration information for at least one second cell controllable by the first cell; A step of obtaining a PCI (physical cell identification) of a data cell to be connected among the at least one second cell based on the synchronization information and the setting information for the at least one second cell; and A method comprising: a step of connecting to the data cell based on the PCI; 2. In paragraph 1, A method wherein the configuration information for said at least one second cell includes synchronization information for each of said at least one second cell.

3. In paragraph 2, A method according to claim 1, wherein each of the synchronization information of the at least one second cell comprises at least one of a PSS (primary synchronization signal) identical to a PSS of the first cell or a SSS (secondary synchronization signal) identical to a SSS of the first cell.

4. In paragraph 3, A method wherein, when the synchronization information of each of said at least one second cell has a PSS identical to the PSS of the synchronization information of said first cell and an SSS identical to the SSS of said first cell, the synchronization information of each of said at least one second cell further includes an additional synchronization signal.

5. In paragraph 1, A method wherein at least one of the second cells comprises a wake-up receive (WUR).

6. In the first paragraph, the method, A step of transmitting a WUS (wake-up signal) to the above data cell; and A method further comprising the step of receiving an SSB from the data cell.

7. In paragraph 1, A method wherein the terminal operates in idle mode or inactive mode.

8. In a terminal operating in a wireless communication system, transceiver; and At least one processor operatively connected to said transceiver, said at least one processor comprising: By controlling the above transceiver, a synchronization signal (SS) of the first cell is obtained from the first cell, Based on the synchronization signal of the first cell, synchronize with the first cell, Controlling the transceiver, receiving, from the first cell, configuration information for at least one second cell controllable by the first cell, Based on the above synchronization information and the configuration information for the at least one second cell, a PCI (physical cell identification) of a data cell to be connected among the at least one second cell is obtained, A terminal that controls the transceiver and connects to the data cell based on the PCI.

9. In paragraph 8, A terminal, wherein the configuration information for at least one of the second cells includes synchronization information for each of the at least one second cell.

10. In paragraph 9, A terminal, wherein each of the synchronization information of the at least one second cell includes at least one of a PSS (primary synchronization signal) identical to a PSS of the first cell or an SSS (secondary synchronization signal) identical to a SSS of the first cell.

11. In Article 10, A terminal wherein, when the synchronization information of each of said at least one second cell has a PSS identical to the PSS of the synchronization information of said first cell and an SSS identical to the SSS of said first cell, said synchronization information of each of said at least one second cell further includes an additional synchronization signal.

12. In paragraph 8, A terminal, wherein at least one of the second cells comprises a wake-up receive (WUR).

13. In the 8th paragraph, at least one processor, A terminal that controls the transceiver to transmit a WUS (wake-up signal) to the data cell and receive an SSB from the data cell.

14. In paragraph 8, The above terminal is a terminal operating in idle mode or inactive mode.

15. In a wireless communication system, terminal; 1st cell; and The first cell comprises at least one controllable second cell, and the terminal: Obtaining a synchronization signal (SS) of the first cell from the first cell, Based on the synchronization signal of the first cell, synchronize with the first cell, Receive setting information for at least one second cell from the first cell, Based on the above synchronization information and the configuration information for the at least one second cell, a PCI (physical cell identification) of a data cell to be connected among the at least one second cell is obtained, A system for accessing the data cell based on the above PCI.

Images