Method and device for configuring synchronization signals in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. In addition, the present disclosure provides a method and device for reducing energy consumption of a base station in a mobile communication system. According to the present disclosure, the problem of excessive energy consumption of a base station can be solved and higher energy efficiency can be achieved in a mobile communication system. A method by which a terminal performs communication in a wireless communication system, according to one embodiment of the present disclosure, involves detecting a synchronization signal burst through beam sweeping. The method involves performing synchronization on the basis of the synchronization signal burst, wherein the synchronization signal burst includes at least one synchronization signal block and has a two-dimensional structure with respect to a time axis and a frequency axis.

Description

Method and device for configuring a synchronization signal in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for configuring a synchronization signal 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 configuring a synchronization signal in a wireless communication system.

[0009] The technical problems to be achieved in the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from the various embodiments of the present disclosure described below.

[0010] In a method for a terminal to perform communication in a wireless communication system according to one embodiment of the present disclosure, a synchronization signal burst can be detected through beam sweeping. The method can perform synchronization based on the synchronization signal burst. The synchronization signal burst can have a two-dimensional structure with respect to the time axis and the frequency axis, including at least one synchronization signal block.

[0011] In a wireless communication system according to one embodiment of the present disclosure, a terminal performing communication may include a transceiver and at least one processor connected to the transceiver, and the at least one processor may detect a synchronization signal through beam sweeping. The at least one processor may perform synchronization based on a synchronization signal burst. The synchronization signal burst may include at least one synchronization signal block and may have a two-dimensional structure with respect to the time axis and the frequency axis.

[0012] In a wireless communication system according to one embodiment of the present disclosure, a method for performing communication by a base station may transmit a synchronization signal burst via a beam. The method may perform synchronization based on the synchronization signal burst. The synchronization signal burst may include at least one synchronization signal block and may have a two-dimensional structure with respect to the time axis and the frequency axis.

[0013] 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: synchronizing with a first cell; receiving a first control signal from the first cell, the first control signal including information about a cell controllable by the first cell; and transmitting data to a second cell based on the first control signal.

[0014] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.

[0015] According to one embodiment of the present disclosure, by defining a signal transmission method of a base station in a wireless communication system, ambiguity in the detection of a synchronization signal by a terminal can be reduced. Furthermore, high energy efficiency of the base station can be achieved through related operations.

[0016] The effects that can be obtained from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.

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

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

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

[0020] 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.

[0021] 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.

[0022] 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.

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

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

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

[0026] 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.

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

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

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

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

[0031] Fig. 15 is a drawing for explaining the existing synchronization signal of the present disclosure.

[0032] FIG. 16 is a diagram of a synchronization signal structure for realizing energy saving according to one embodiment of the present disclosure.

[0033] FIG. 17 is a diagram for explaining beam allocation in a synchronization signal structure for realizing energy saving according to one embodiment of the present disclosure.

[0034] Figure 18 is a drawing of a conventional channel raster and a sync raster.

[0035] Figure 19 relates to the payload of PBCH (1503) within the synchronization signal block.

[0036] Figure 20 illustrates the process by which a terminal searches for CORESET 0.

[0037] Figure 21 is a diagram illustrating a method for a terminal to implicitly find the location of the 0th subcarrier of the corresponding CRB.

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

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

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

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

[0042] 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.

[0043] 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 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 solely to ensure that the 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 designate like elements throughout the specification.

[0044] 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).

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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."

[0050] 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).

[0051] 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.

[0052] 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.

[0053] To handle the explosive growth in mobile data traffic, the initial standards for the 5G (5th Generation) system, or New Radio access technology (NR), the next-generation communication system following LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)) and LTE-A (LTE-Advanced or E-UTRA Evolution), 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 for improving existing voice / data communications, Ultra-Reliable and Low Latency Communication (URLLC) services for high reliability / ultra-low latency communications, and massive Machine Type Communication (MTC) services for supporting massive machine-to-machine communications.

[0054] 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.

[0055] 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.

[0056] 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 focus 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 focused 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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, , and the data rate can increase in proportion to the number of RBs scheduled to the terminal.

[0061] 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.

[0062] 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, , when Extended CP is applied It can be. Extended CP can be applied to a system with a relatively long transmission distance than the general CP, so that orthogonality between symbols can be maintained. In the case of the general CP, since the ratio of the CP length to the symbol length is maintained at a constant value, the overhead due to the 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.

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

[0064] - 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.

[0065] - From the perspective of transmission time, 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.

[0066] - 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.

[0067] The above subcarrier spacing, CP length, etc. are essential information for OFDM transmission and reception. The base station and the terminal must recognize the subcarrier spacing, CP length, etc. as common values ​​to enable smooth transmission and reception. [Table 1] shows the subcarrier spacing configuration supported by the 5G system. ), subcarrier spacing ( ), which represents the relationship between CP length.

[0068] [Table 1]

[0069]

[0070] [Table 2] shows the subcarrier spacing settings for the general CP ( ) not much, each with a different number of symbols per slot ( ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.

[0071] [Table 2]

[0072]

[0073] [Table 3] shows the subcarrier spacing settings for extended CP ( ) by number of symbols per slot ( ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.

[0074] [Table 3]

[0075]

[0076] 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).

[0077] For example, setting the subcarrier spacing In-frame structure (hereinafter referred to as frame structure A) and subcarrier spacing settings Comparing the in-frame structure (hereinafter referred to as frame structure B), compared to frame structure A, frame structure B has a subcarrier spacing and RB size that are twice as large, and a slot length and symbol length that 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

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

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

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

[0086] - 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.

[0087] - 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.

[0088] - 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] FIG. 3 illustrates a random access procedure according to one embodiment of the present disclosure. FIG. 3 illustrates an example of a random access procedure, and the present disclosure is not limited thereto. Furthermore, the present disclosure is not limited to the 4-step random access procedure illustrated in FIG. 3, and can also be applied to a 2-step random access procedure (transmitting and receiving message A (a message including information corresponding to message 1 and message 3) and transmitting and receiving message B (a message including information corresponding to message 2 and message 4)).

[0093] 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.

[0094] 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). Additionally, 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.

[0095] 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).

[0096] 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.

[0097] 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 was successfully received to the base station through an uplink control channel (Physical Uplink Control Channel, PUCCH).

[0098] 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).

[0099] 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 of 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.

[0100] 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.

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

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

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

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

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

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

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

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

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

[0110] 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.

[0111] 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.

[0112] 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.

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

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

[0115] - Obtain system information

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

[0117] 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:

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

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

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

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

[0122] 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.

[0123] 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).

[0124] 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.

[0125] 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.

[0126] 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.

[0127] 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.

[0128] 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).

[0129] 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.

[0130] A base station can configure one or more CORESETs for a terminal via 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].

[0131] [Table 4]

[0132]

[0133] 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.

[0134] 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.

[0135] [Table 5]

[0136]

[0137] 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.

[0138] 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.

[0139] 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 regions to which DMRS (605), a reference signal for decoding the REs, is mapped. Additionally, three DMRSs (605) may be transmitted within one REG (603).

[0140] 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, which detects 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.

[0141] 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.

[0142] 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 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 can be defined according to the 3GPP TS 38.331 document.

[0143] 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.

[0144] 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.

[0145] 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.

[0146] - 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

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

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

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

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

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

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

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

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

[0155]

[0156] 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.

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

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

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

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

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

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

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

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

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

[0166] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is punctured.

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

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

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

[0170] The above-described DCI formats can follow the definitions shown in [Table 6] below.

[0171] [Table 6]

[0172]

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

[0174] [Mathematical Formula 1]

[0175]

[0176] 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.

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

[0178] 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 7 below.

[0179] [Table 7]

[0180]

[0181] 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.

[0182] The above QCL relationship can be set to the terminal through the RRC parameters TCI-State and QCL-Info. The base station can set one or more TCI states to the terminal and inform the RS that references 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 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.

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

[0184] 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.

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

[0186] [Table 8]

[0187]

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

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

[0190] 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.

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

[0192] 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).

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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.

[0197] 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.

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

[0199] 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.

[0200] DCI can be transmitted over 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 has been transmitted to the UE.

[0201] 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).

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

[0203] 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 at 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 9 and 10 below may be notified from the base station to the terminal.

[0204] [Table 9]

[0205]

[0206] [Table 10]

[0207]

[0208] 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.

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

[0210] 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.

[0211] Resource Allocation Type 0

[0212] 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 11 below.

[0213] [Table 11]

[0214]

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

[0216]

[0217] - 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.

[0218] Resource Allocation Type 1

[0219] - 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.

[0220]

[0221] 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.

[0222] To be more specific, it is as follows:

[0223] 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 12 through upper layer signaling (e.g., RRC signaling).

[0224] [Table 12]

[0225]

[0226] 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.

[0227] 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.

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

[0229] In non-grant-based PUSCH transmission type-1, the base station can set specific time / frequency resources (600) that allow non-grant-based PUSCH transmission to the terminal through higher layer signaling, for example, RRC signaling. For example, as illustrated in FIG. 6, time axis allocation information (601), frequency axis allocation information (602), period information (603), etc. for the resource (600) can be set. 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, MCS, RBG (Resource Block Group) size, number of repetition transmissions, RV (Redundancy Version), etc.).

[0230] 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.

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

[0232] 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.).

[0233] 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.

[0234] To be more specific, it is as follows:

[0235] 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 13 below, the terminal can regard the DCI as a command to activate transmission and reception for DL ​​SPS or UL grant Type 2.

[0236] [Table 13]

[0237]

[0238] 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 142 below, the terminal can regard the DCI as a command to release transmission and reception for DL ​​SPS or UL grant Type 2.

[0239] [Table 14]

[0240]

[0241] 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.

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

[0243] 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.

[0244] Cross-carrier scheduling method

[0245] ◆ 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 X=4 symbol, When X=4 symbol, When , X=8 can be defined as a symbol.

[0246] ◆ 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 X=4 symbol, When X=8 symbols, When , X=12 can be defined as a symbol.

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

[0248] 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.

[0249] Rate Matching Operation

[0250] - 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.

[0251] 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}, 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 symbol sequence A was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A except for {resource #3} corresponding to resource C. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4} and transmitted, respectively, and perform a series of subsequent receiving operations.

[0252] Puncture action

[0253] 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.

[0254] 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 transmitted only in the remaining area excluding resource C among resource area A mapped to the entire resource A. 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 mapped to {resource #1, resource #2, resource #4} and transmitted, respectively, and perform a series of subsequent receiving operations.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

[0259] RB symbol level

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

[0261] - 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.

[0262] - 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.

[0263] RE level

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

[0265] - 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.

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

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

[0268] 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.

[0269] For the aforementioned CSI measurement and reporting, the terminal may receive setting information for N (≥1) CSI reports (CSI-ReportConfig), setting information for M (≥1) RS transmission resources (CSI-ResourceConfig), and one or two trigger state lists (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList) through upper layer signaling. The corresponding information and parameters may be defined by 3GPP TS 38.331.

[0270] 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).

[0271] 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.

[0272] - CSI-IM resources for interference measurements

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

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

[0275] 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 (CCs) can be set with the upper layer parameter CSI-AperiodicTriggerStateList.

[0276] 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 15 below.

[0277] [Table 15]

[0278]

[0279] Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1 ​​corresponding to scheduling DCI for 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 can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by higher layer signaling (reportTriggerSize). One of 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.

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

[0281] - 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.

[0282] - 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.

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

[0284] [Table 16]

[0285]

[0286] 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.

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

[0288] 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 set 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 17 below.

[0289] [Table 17]

[0290]

[0291] 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 a K2 value corresponding to a 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.

[0292] 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).

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

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

[0295] 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 18.

[0296] [Table 18]

[0297]

[0298] 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).

[0299] 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.

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

[0301] In one embodiment, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth part settings. For example, by setting the frequency location (setting information 2) of the bandwidth part to the terminal, the base station can enable the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0302] 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.

[0303] 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.

[0304] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting 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 downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the physical downlink shared channel (PDSCH) 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.

[0305] 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.

[0306] 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 19 below.

[0307] [Table 19]

[0308]

[0309] 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.

[0310] According to the requirement for 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 a 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 a 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 a 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).

[0311] 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).

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

[0313] 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 and reception parameter #1 for bandwidth part #1 (1301), and can be configured with transmission and 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 and 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 and reception parameter #2.

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

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

[0316] [Table 20]

[0317]

[0318] According to [Table 20], 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).

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

[0320] [Table 21]

[0321]

[0322] According to [Table 22], 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 a radio link monitoring (RLM)) from the base station (corresponding to BWP-UplinkDedicated).

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

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

[0325] 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.

[0326] 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.

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

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

[0329] - 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

[0330] 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.

[0331] 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 the 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 the uplink HARQ procedure. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL can be set as, for example, time, number of subframes, number of slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring PDCCH in random access procedure.

[0332] 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.

[0333] 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.

[0334] 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.

[0335] [Equation 2]

[0336]

[0337] 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.

[0338] 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.

[0339] 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.

[0340] [Equation 3]

[0341]

[0342] 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.

[0343] 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.

[0344] 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 can perform the following processes:

[0345] - Storage of AS (Access stratum) information required for cell connection

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

[0347] - Setting up and periodically updating RNA (RAN (radio access network)-based notification area) that can be utilized during handover by the RRC layer

[0348] - Monitoring of RAN-based paging messages transmitted via I-RNTI (inactive-radio network temporary identifier)

[0349] A terminal in RRC_CONNECTED state can change from RRC_CONNECTED to RRC_INACTIVE or RRC_IDLE state by receiving an RRC Release instruction from the base station.

[0350] A terminal in RRC_INACITVE or RRC_IDLE state can change from RRC_INACTIVE or RRC_IDLE to RRC_CONNECTED state by performing random access and completing all random access procedures.

[0351] Below, a scheduling method for a base station to transmit downlink data to a terminal or instruct the terminal to transmit uplink data is described.

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

[0353] The base station can operate by applying a DCI format determined for the purpose of scheduling, such as whether it is scheduling information for downlink data (downlink assignment), scheduling information for uplink data (uplink grant), or DCI for power control.

[0354] The base station can transmit downlink data to the terminal via the Physical Downlink Shared Channel (PDSCH), a physical channel for downlink data transmission. The base station can inform the terminal of scheduling information such as the specific mapping location in the time and frequency domain of the PDSCH, modulation method, HARQ-related control information, and power control information through DCI related to downlink data scheduling information among the DCI transmitted via the PDCCH.

[0355] A terminal can transmit uplink data to a base station via the Physical Uplink Shared Channel (PUSCH), a physical channel for uplink data transmission. The base station can inform the terminal of 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 through DCI related to uplink data scheduling information among the DCI transmitted via the PDCCH.

[0356] For RRC_IDLE / RRC_INACTIVE terminals, the above-mentioned DRX operation is performed and a paging message is received. The terminal can monitor one paging occasion (PO) during a DRX cycle. A PO may be a set of PDCCH monitoring occasions and may include multiple time slots (or subframes, or OFDM symbols) in which paging control information may be transmitted and received. A paging frame (PF) may be one radio frame (10 ms) and may include one or multiple POs or starting points (e.g., offsets) of POs.

[0357] PF and PO can be determined by the following formulas:

[0358] The SFN (System Frame Number) for PF can be determined by (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N), where PF_offset is an offset for PF determination, T is a DRX cycle, N is the number of PFs per DRX cycle (e.g., cell common, cell specific), which can be determined by higher-level signals such as system information, and UE_ID is a terminal ID (e.g., 5G-S-TMSI), which can be determined by the core network.

[0359] The PFs determined by N may refer to paging frames commonly applied to terminals within a cell, and may be referred to as cell common PFs for convenience hereinafter.

[0360] i_s, which indicates the PO index, can be determined by i_s = floor (UE_ID / N) mod Ns, where Ns can mean the number of POs in one PF and can be determined by a higher-order signal such as system information.

[0361] For example, if PF_offset=3, T=128, N=T / 4=32, Ns=4, and UE_ID mod 32 is 1, and floor (UE_ID / 32) mod 4 is 1, then the values ​​of the parameters can be determined by the following formula.

[0362] (SFN + 3) mod 128 = (128 div 32)*(UE_ID mod 32) = 4*1 = 4,

[0363] i_s = floor (UE_ID / 32) mod 4 = 1

[0364] Accordingly, the PF, which is a paging frame that a terminal with the above UE_ID must receive, can be determined as a radio frame with SFN of 1, 129, 257, ... among the common PFs of the cell, and the PO can be determined as the (i_s + 1)th PO among the four POs in the PF.

[0365] Hereinafter, the reception of PEI (Paging Early Indication) is described in more detail. In order to reduce terminal power consumption while monitoring and receiving the paging control channel and paging data channel in each DRX cycle, the terminal can receive PEI.

[0366] According to various embodiments of the present disclosure, a terminal may monitor or receive one PEI Occasion (PEI-O) before receiving paging during a DRX cycle. When the terminal receives a PEI and the PEI indicates a subgroup and a paging occasion to which the terminal belongs, the terminal belonging to the subgroup may monitor the associated paging occasion (PO). If the terminal does not detect the PEI in the PEI occasion or the PEI does not indicate a subgroup and a paging occasion to which the terminal belongs, the terminal does not need to monitor the associated paging occasion (PO), thereby reducing terminal power consumption.

[0367] The terminal can determine the PEI occasion as follows. The PEI occasion can be located behind the radio frame of the reference point that is located ahead of the PF containing the associated PO by the number of subframe offsets. The terminal can monitor the PEI in the PEI occasion determined by the above method. Here, pei-FrameOffset, subframe offset, etc. can be determined by higher-level signals such as system information.

[0368] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD, TDD and / or XDD (and / or SBFD, full duplex) systems. In the present disclosure below, upper signaling (or upper 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 a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0369] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions, which can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be uniformly described as TRP (transmission reception point), beam, or TCI state. Therefore, when actually applying the present disclosure, TRP, beam, or TCI state may be appropriately replaced with one of the above terms.

[0370] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. 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, 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. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included here. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure can be applied to FDD, TDD, XDD (or SBFD, full duplex) systems.

[0371] Additionally, when describing the present disclosure, detailed descriptions of related 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 the functions of 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 contents of this specification.

[0372] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0373] - MIB (Master Information Block)

[0374] - SIB (System Information Block) or SIB

[0375] - RRC (Radio Resource Control)

[0376] - MAC (Medium Access Control) CE (Control Element)

[0377] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the physical layer channel or signaling below.

[0378] - PDCCH (Physical Downlink Control Channel)

[0379] - DCI (Downlink Control Information)

[0380] - UE-specific DCI

[0381] - Group common DCI

[0382] - Common DCI

[0383] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

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

[0385] - PUCCH (Physical Uplink Control Channel)

[0386] - UCI (Uplink Control Information)

[0387] The term slot used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a TTI (Transmit Time Interval), and specifically may mean a slot to be used in a 6G system, a slot to be used in a 5G NR system, or a slot or subframe to be used in a 4G LTE system.

[0388] The present disclosure can be applied to RRC idle, RRC inactive, and RRC connected terminals.

[0389] In the present disclosure, the statement that a particular cell is for data communication and / or only for data communication may include that the particular cell performs not only data communication but also other signal transmission and reception. For example, signal transmission and reception other than sync and / or connection may be included in data communication.

[0390]

[0391] In the present disclosure below, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination.

[0392] <Example 1>

[0393] The first embodiment is about a synchronization signal transmission structure of a base station.

[0394] Fig. 15 is a drawing for explaining the existing synchronization signal of the present disclosure.

[0395] Referring to Fig. 15, the existing synchronization signal (e.g., SSB / PBCH, 1504) has a structure consisting of PSS (1501), SSS (1502), and PBCH (1503) in the resource of 4 symbols in the time domain and 12 RBs in the frequency domain. In addition, it has an SSB burst form in which a separate beam in a different direction is transmitted to each SSB / PBCH for beam sweeping. Therefore, each terminal receives all SSB bursts and performs random access using the RACH occasion QCLed to the best beam. If we assume a subcarrier spacing of 120 kHz, 32 beams are applied to each SSB / PBCH as shown in Fig. 15, and SSB bursts are transmitted in a TDM form with different time domains within the same frequency. In other words, each terminal requires a total of 38 slots to set a beam once, which causes a very large delay during initial access and also consumes a lot of energy.

[0396] FIG. 16 is a diagram of a synchronization signal structure for realizing energy saving according to one embodiment of the present disclosure.

[0397] Referring to Fig. 16, each synchronization signal (1601) may include signals for time and frequency synchronization, such as PSS / SSS, similar to the synchronization signal of Fig. 15, and may also include PBCH. In addition, compared to the existing synchronization signal, it may have a structure that includes additional signals, and even if it is composed of only the same signals, the order and amount of resources may be different from the existing one. The synchronization signal structure may have a 2D synchronization signal pattern for both time and frequency domains. That is, as the synchronization signals are FDM'd in the frequency domain instead of the time domain, the length of the synchronization signal burst in the time domain becomes shorter, so the transmission time of the base station is shortened, and the terminal can also have a lower delay time. For example, in Fig. 16, if FDM is performed on the same 32 beams with 4 frequencies, it is TDM'd with 8 slots in the time domain. That is, the advantage of a 2D structure with 8 slots compared to a 1D structure that required 38 slots is clear. In the FDM process of a synchronization signal, a synchronization signal burst may include a guard band, such as (1602). This can be set to reduce the influence of interference between FDMed synchronization signals, and other data may or may not be carried in the guard band.

[0398] A synchronization burst signal, such as that in FIG. 16, can completely replace a synchronization burst signal, such as that in FIG. 15, or can only be used as a replacement in certain circumstances. For example, in environments requiring a very large bandwidth and multiple antennas, such as frequency ranges (FR) 2 or FR 3, performing FDM can significantly reduce energy consumption at the base station and delay time at the terminal due to the large number of beams. In addition, in cases where a synchronization signal is required aperiodicly, such as an on-demand synchronization signal, in addition to a periodic synchronization signal, the terminal must synchronize with the base station as quickly as possible, and thus the synchronization signal burst structure of FIG. 16 can be helpful.

[0399] FIG. 17 is a diagram for explaining beam allocation in a synchronization signal structure for realizing energy saving according to one embodiment of the present disclosure.

[0400] Referring to Fig. 17, instead of assigning different beams to each synchronization signal in the synchronization signal structure of Fig. 16, the same beam can be transmitted by time domain. That is, beams can be distinguished and used only in different frequency bands. In this case, different beams can be transmitted simultaneously and retransmitted in the time domain, or beam combinations that go out simultaneously in the frequency domain, as shown in Fig. 17, can be transmitted in different orders by time domain. This is effective when the RF of the terminal has the capability to receive all synchronization signal bursts (especially idle terminals), even if it has different beams for all synchronization signals, but when the RF of the terminal has only a very small RF bandwidth that cannot receive all synchronization signal bursts. That is, a terminal with good RF bandwidth capability can receive a beam only at one time, as in (1701), and a terminal with poor capability can receive only one sub-band, as in (1702), but can receive beams over multiple times. This operation can reduce the power consumption of the terminal for beam search. However, since the number of beams can be determined by the number of FDM sub-bands, the number of beams is very small compared to the transmitted resources. This means that the base station may cause inefficient resource use and large energy consumption.

[0401] <Example 2>

[0402] The second embodiment relates to a channel raster and a sync raster in a synchronization signal structure according to an embodiment of the present disclosure mentioned in FIGS. 16 and 17.

[0403] Figure 18 is a drawing of a conventional channel raster and a sync raster.

[0404] Due to the extremely large system bandwidth, flexible subcarrier spacing, and support for beam sweeping, the process by which a terminal searches for a synchronization signal (1802) has a significant impact on the design of initial access. During the cell search procedure, the terminal locates a base station and attempts to connect to it. It is neither desirable nor practical for the terminal to blindly search for cells across all frequencies to detect a base station. Therefore, to efficiently perform the cell search procedure, a channel raster (1801) and a synchronization raster (1802) were introduced.

[0405] A synchronization raster (1802) is a list of frequency points that can be used for transmitting a synchronization signal. For example, point X in the frequency domain can be a synchronization raster. If an operator operates a base station having a carrier frequency close to point X, the synchronization signal of the base station can be configured at point X. Therefore, when a terminal searches for a base station in the frequency band where point X is located, the terminal can find a cell through the synchronization signal at point X. A channel raster is a frequency point that can be used to operate a base station. For example, if the cell bandwidth is 100 MHz, a center frequency point can be set on the channel raster at frequency point Y, and the range of the base station in the frequency domain can be set to [Y-50 MHz, Y+50 MHz]. In other words, the synchronization raster indicates a frequency domain location at which a synchronization signal can be transmitted, and the channel raster indicates a frequency domain location at which a base station carrier frequency can be configured. The synchronization raster is used to help the terminal reduce access delay and power waste caused by the uncertainty of blind cell search. The more granular the synchronization raster is, the smaller the synchronization raster becomes in the frequency domain. This will reduce the time consumed by base station search. However, the granularity of the synchronization raster cannot be increased indefinitely. At least one synchronization raster must exist within the frequency bandwidth of a base station. For example, if the base station bandwidth is 20 MHz and the synchronization raster granularity is 40 MHz, some frequency resources will be unavailable to that base station.

[0406] Additionally, there is only one complete synchronization signal block within the minimum channel bandwidth (1803). That is, in FIG. 18, the terminal detects a synchronization signal (1804) obtainable for each of several synchronization rasters (1802).

[0407] If a constraint is set that only one complete synchronization signal block exists within the minimum channel bandwidth in the structure of FIG. 16, the minimum channel bandwidth must be set to the size of the multiple FDM sub-bands of FIG. 16, and even if a synchronization signal block is detected in the synchronization raster, multiple attempts may be required to find a synchronization raster in which all of the corresponding sub-bands are aligned in order to find a complete synchronization signal.

[0408] Therefore, to reduce the complexity described above, instead of a single complete synchronization signal block within the minimum channel bandwidth, a synchronization signal block composed of a single sub-band can be configured. In this case, the terminal cannot detect the entire synchronization signal burst at once, but can determine the index of the detected synchronization signal block composed of the sub-band, thereby locating the remaining blocks. A detailed description of this will be described in the third embodiment.

[0409] <Example 3>

[0410] The third embodiment relates to a synchronization signal index indication in a synchronization signal structure according to an embodiment of the present disclosure mentioned in FIGS. 16 and 17.

[0411] For the existing synchronization signal index indication, up to 64 indices can be distinguished using the DM-RS and PBCH for PBCH decoding of (1503).

[0412] First, the formula for generating PBCH DM-RS within the existing synchronization signal block is as shown in [Mathematical Formula 4].

[0413] [Equation 4]

[0414]

[0415] As with many other physical layer signals, the pseudo random sequence is generated by [Equation 5].

[0416] [Equation 5]

[0417]

[0418] Here is 31, class are as in [Mathematical Formula 6] and [Mathematical Formula 7], respectively.

[0419] [Equation 6]

[0420]

[0421] [Equation 7]

[0422]

[0423] At this time, a sequence is generated using the unique c_init (initialization value) of the PBCH DM-RS. As shown in [Mathematical Formula 8], the initialization value is the physical cell ID. , synchronization signal (here, SSB) Index , half frame number It is composed of various components.

[0424] [Equation 8]

[0425]

[0426] is as in [Mathematical Formula 9].

[0427] [Equation 9]

[0428]

[0429] [Equation 9] and is the maximum number of beams assigned to a synchronization signal The value varies depending on the . For example, ramen One bit is allocated, 0 if it is the first half frame in the frame, and 1 if it is the second half frame. Also, the LSB of the two bits is will be directed. If If, since The bits for are not allocated separately. Also, the three bits of the LSB are , will be directed.

[0430] That is, the terminal can determine the synchronization signal Index and whether the corresponding time is a half frame by decoding the PBCH DM-RS.

[0431] Figure 19 relates to the payload of PBCH (1503) within the synchronization signal block.

[0432] According to FIG. 19, within the PBCH payload, MIB (1901) is allocated a total of A bits from 0 to A-1, and the subsequent bits are augmented with additional bits encoding specific system information.

[0433] First, a total of 4 bits from A to A+3 are allocated to SFN (1902).

[0434] The A+4th bit represents the half radio frame bit.

[0435] If there are 64 synchronization signals (SSBs in this case), the three bits of A+5 to A+7 (1904 to 1906) indicate the synchronization signal index. If there are fewer than 64 synchronization signals, there are cases of 4 or 8, so the three bits of the PBCH DM-RS can be sufficiently distinguished, and therefore no additional bits need to be considered in the PBCH payload. Therefore, A+5 (1904) will be described in the fourth embodiment. is set to the MSB of , and A+6 (1905) and A+7 (1906) are set as reserved bits.

[0436] After these bits are inserted, an interleaving process is applied to rearrange the sequence and complete the payload generation step.

[0437] When following the synchronization signal structure of FIGS. 16 and 17, the existing synchronization signal index indication method may be limited. For example, since the existing synchronization signal shares the same frequency (e.g., sub-band) as in FIG. 15 and is distinguished only by the time domain, the index could be identified using the bits obtained from the simple PBCH DM-RS and the PBCH payload. However, in the synchronization signal structure of FIGS. 16 and 17, in order to indicate the synchronization signal index, information regarding the frequency domain as well as the time domain may need to be indicated.

[0438] In this case, the synchronization signal index indication can be distinguished based on three bits indicated through PBCH DMRS (wherein, PBCH can be a channel with a different name that plays a similar role, and the same applies to DMRS. It is also assumed that the synchronization signal index is transmitted similarly in PBCH DMRS as before. Therefore, the number of bits can be the same or different from before.) For example, assuming that the synchronization signal index and the half-frame index are indicated only in PBCH DMRS, according to the number of beams as in [Mathematical Formula 9] In addition to the index being distinguished by inclusion, additional branching can occur depending on the number of synchronization signal blocks in the time domain or frequency domain. That is, assuming that there are A synchronization signal blocks in the time domain and B synchronization signal blocks in the frequency domain, The remaining N bits, excluding the bits for , can indicate that it is a synchronization signal block in the a-th time domain and the b-th frequency domain. If B=1, it can operate in the same way as before. Information about the maximum A and B for the time and frequency domains, respectively, can be shared in advance or the terminal can already recognize them. If there is no such information, the values ​​of A and B can be included in the PBCH DMRS considering the initial access stage.

[0439] Alternatively, the index indications for up to M synchronization signal blocks can be provided using the existing bits as before, but the mapping method can be recognized by the terminal. For example, if indexing is performed from the time domain and the indexing for A synchronization signal blocks ends with 0 to A-1, the A synchronization signal blocks for the synchronization signal block of the next sub-band can be performed with A to 2A-1. In other words, if the terminal is aware of the situation where time domain indexing is performed first and then frequency domain indexing is performed, or vice versa, the terminal can accurately recognize the index of the synchronization signal block detected within the synchronization signal block burst based on the existing bits.

[0440] Another way is that the synchronization signal block indicated in the PBCH payload (here, PBCH can be a channel with a different name that plays a similar role. It can have the same number of bits or different depending on the existing PBCH payload, and the index of the synchronization signal block can be specified here) can also specify the index of the block indicated in the time domain and the frequency domain. For example, assuming that the three bits of (1904~1906) indicate this, (1904) can represent the block index in the time domain, and (1905, 1906) can represent the block index in the frequency domain. Through this, the terminal can find out information about the a-th time domain and the b-th frequency domain. Information about the maximum A and B for the time and frequency domains, respectively, can be shared in advance or the terminal can already recognize them. If the information is not available, the values ​​of A and B can be included in the payload considering the initial access phase.

[0441] As a final method, the PBCH DM-RS and PBCH payload can each indicate the indices of synchronization signal blocks in the time domain, frequency domain, or vice versa. For example, assuming no change in the number of bits, the PBCH DMRS distinguishes up to eight synchronization signal blocks in the time domain, so the remaining synchronization signal blocks in the frequency domain can be distinguished up to eight through the PBCH payload.

[0442] <Example 4>

[0443] The fourth embodiment relates to an operation of indicating a frequency offset from a reference subcarrier spacing in a system having multiple subcarrier spacings in a synchronization signal structure according to an embodiment of the present disclosure mentioned in FIGS. 16 and 17.

[0444] In a system with multiple subcarrier spacings (e.g., 15, 30, 60, 120, 240 kHz, etc.), there may be a full resource block grid generated using a reference subcarrier spacing (e.g., generated based on 15 kHz), and a resource block grid generated with an actually used subcarrier spacing. In this case, since multiple subcarrier spacings may be used in a mixed manner, the positions of specific channels and signals can be indicated based on the full resource block grid generated using the reference subcarrier spacing. For example, when there is a synchronization signal generated based on 30 kHz (SSB here), the position of CORESET 0 is indicated based on the resource grid generated based on 15 kHz, which is the reference, rather than the resource grid generated based on 30 kHz, in order to indicate the position of the control channel indicating system information (CORESET 0 here). To achieve this, the base station must inform the terminal of the location of the synchronization signal generated based on the 30 kHz currently secured by the terminal and the frequency offset from the common RB containing the synchronization signal based on the 15 kHz standard. In existing technology, this is indicated as ssb-SubcarrierOffset through the MIB, and the frequency offset between the synchronization signal and the entire resource grid is indicated as the number of subcarriers. In this case, the value 0 means no offset. For Type A SSB in the 6 GHz band or lower can have values ​​from 0 to 23. That is, 4 LSB bits are indicated as ssb-SubcarrierOffset in the MIB, and additionally, this can be indicated in (1904) in the PBCH payload. For Type B SSB in the 6 GHz band or higher can have values ​​from 0 to 11. That is, 4 LSB bits are indicated as ssb-SubcarrierOffset within the MIB.

[0445] Figure 20 illustrates the process by which a terminal searches for CORESET 0.

[0446] After the terminal detects the synchronization signal (2001), it uses the ssb-SubcarrierOffset detected from the MIB or additional information in the PBCH payload. (2006) obtains the value. Based on the 0th subcarrier of the detected (2001). By subtracting the value, the terminal can accurately identify the 0th subcarrier of the CRB including this SSB in the reference resource grid generated based on 15 kHz. The 0th subcarrier of this CRB is offset by offsetToPoinA (2004) from Point A (2003), which is the common reference point of the resource block grid, and this is information that the terminal can only know after decoding the system information. After decoding the MIB, the terminal can identify the location of (2005), and through the additional offset information of (2007), it can identify the location of the 0th subcarrier of CORESET 0 (2002).

[0447] so The value of plays a very important role in situations where multiple subcarrier spacings are mixed. In the synchronization signal structure of Fig. 15, all synchronization signal blocks exist in the same frequency domain, so the same synchronization signal is transmitted through all synchronization signal blocks within the burst. can be detected. However, in the case of having a structure of a synchronization signal as in Figs. 16 and 17, synchronization signals in different frequency domains have different can have a value. (here is a term used for convenience and may be replaced by other terms that perform similar actions.)

[0448] As a solution to this, first You can change the definition of . For example, the existing The definition of is the frequency offset of the 0th subcarrier of the corresponding CRB and the 0th subcarrier of the synchronization signal expressed as the number of subcarriers. However, for the 2D structure of time-frequency, the frequency offset of the 0th subcarrier of the corresponding CRB and the 0th subcarrier of the 'reference' synchronization signal is expressed as the number of subcarriers or RBs or an equivalent granularity. Here, the 'reference' synchronization signal is the synchronization signal located in the subband at the bottom or top of the synchronization signal burst. For example, if the terminal When the synchronization signal index is detected, the location of the reference synchronization signal can be known, and this reference synchronization signal and The location of the 0th subcarrier for the corresponding CRB can also be found through the combination of the liver.

[0449] Next, different synchronization signals in different frequency domains can be determined. In this case, the terminal is detected Using only , we can find the location of the 0th subcarrier for the corresponding CRB.

[0450] Finally, as before, all sync signals within a sync signal burst have the same value. can have. That is, based on the 'reference' synchronization signal at the bottom or top as explained above. The value can be defined. However, in this case, The definition may not change, but the behavior of the terminal may change.

[0451] Figure 21 is a diagram illustrating a method for a terminal to implicitly find the location of the 0th subcarrier of the corresponding CRB.

[0452] According to Fig. 21, it is assumed that the terminal has detected the synchronization signal block of (2103) and the synchronization signal block at the bottom left is assumed to be the 'reference' synchronization signal block. The terminal detects the synchronization signal index of 16 through (2103). The value (2102) was obtained. The terminal implicitly By recognizing that the value is set based on the 'reference' synchronization signal block, the difference between the reference and the detected synchronization signal can be found out using the reference synchronization signal index. For example, it can be assumed that the terminal knows the frequency resources occupied by a synchronization signal block and the guard band between synchronization signals with different frequencies in advance, as there may be a convention between the base station and the terminal. Since the synchronization signal index of 16 is obtained, the terminal can recognize that there are two sub-bands up to the 'reference' synchronization signal, and through this, it can predict the frequency offset (2104) between (2103) and (2101). Through this, the terminal can know the location of the 0th subcarrier of (2101), and the detected In combination with , the location of the 0th subcarrier of the corresponding CRB can be predicted.

[0453] An idle terminal (2101) camps on three base stations (2102, 2103, 2104) with the same cell ID in the same TA (2111). At this time, all three base stations activate only half of the PAs and periodically transmit TA-RS (2112) and light system information (2113) for the idle terminals. In addition, paging (2114) is transmitted to notify the idle terminal of changes in system information or traffic occurrence. During this process, sync cells can inform the idle terminal of the cell IDs or RS locations of candidate data cells in advance. The idle terminal (2101), which recognizes the occurrence of traffic, transmits (2115) a PRACH / WUS on the connection RO (RACH occasion) using the same beam and QCL that received the TA-RS and paging. In this example, base stations (2102, 2103, 2104) are all in the same tracking area, but depending on the implementation, only certain base stations (e.g., 2102, 2103) can transmit beams. The role of the transmitted (2115) is that of an on-demand RS. Through this, the terminal receives the RS transmitted from (2102) and (2103) (2116, 2117). In this process, each data cell activates all PAs, so that RSs with different cell IDs are transmitted. The terminal measures the signal strength of these two RSs (e.g., RSRP) and transmits PRACH / WUS (2118) to the data cell with the best signal strength. At this time, the transmission power of the terminal is determined based on (2116) or (2117). The RS transmitted by the data cells may be the same as SSB or DMRS. Since the terminal has already synchronized with base stations 1 to 3 through cooperative communication, there may be no need for additional synchronization with SSB, and the terminal can measure the signal strength through DMRS.At this time, DMRS from two data cells can be distinguished by the terminal through FDM, TDM, or CDM. If the terminal selects a specific data cell as the PRACH / WUS, a specific time period after the DMRS is transmitted. Uplink resources for PRACH / WUS may be allocated thereafter. DMRS may also be transmitted on multiple beams, and these DMRS and PRACH / WUS may have a QCL relationship. The UE may transmit the PRACH / WUS set to the same beam as the beam of the selected DMRS. Alternatively, the base station may determine an appropriate beam based on the beam transmitted in (2115) without step (2118) and transmit it in (2116, 2117). In this case, the UE transmits Msg 2 based on the beam connected to the RS.

[0454] Also, after (2116, 2117) a certain time If no PRACH / WUS is transmitted thereafter, the base station (2102) deactivates half of the PAs again and enters NES mode. On the other hand, the base station (2103) that received (2118) performs the remaining RACH procedures (2119-2121). After this, (2101) switches from idle (2131) to connected (2132) and can switch to BWP indicated by data cell (2103) for data reception. After this, (2103) transmits cell-specific system information (2122) to (2101). The (2122) process may also transmit cell-specific system information for candidate data cells in the sync cell in (2113) or (2114).

[0455] Figure 22 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.

[0456] Referring to FIG. 22, the terminal may include a transmitter (2204) including an uplink transmission processing block (2201), a multiplexer (2202), and a transmission RF block (2203), a receiver (2208) including a downlink reception processing block (2205), a demultiplexer (2206), and a reception RF block (2207), and a control unit (2209). The control unit (2209) may control each of the configuration blocks of the receiver (2208) 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 (2204) for transmitting an uplink signal.

[0457] In the transmitter (2204) of the terminal, the uplink transmission processing block (2201) 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 (2201) can be multiplexed with another uplink signal by a multiplexer (2202), and then transmitted to the base station after signal processing in the transmission RF block (2203).

[0458] The terminal's receiving unit (2208) demultiplexes the signal received from the base station and distributes it to each downlink receiving processing block. The downlink receiving processing block (2205) 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 (2208) can support the operation of the control unit (2209) by applying the output result of the downlink receiving processing block to the control unit (2209).

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

[0460] As illustrated in FIG. 23, the terminal of the present disclosure may include a processor (2330), a transceiver (2310), and a memory (2320). 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 (2330), the transceiver (2310), and the memory (2320) may be implemented in the form of a single chip. According to one embodiment, the transceiver (2310) of FIG. 23 may include the transmitter (2204) and receiver (2208) of FIG. 22. In addition, the processor (2330) of FIG. 23 may include the control unit (2209) of FIG. 22.

[0461] According to one embodiment, the processor (2330) 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 (2330), and the processors (2330) may execute a program stored in the memory (2320) to perform transmission and reception operations of the terminal in a wireless communication system that applies the carrier bundle of the present disclosure described above.

[0462] The transceiver (2310) 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 (2310) 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 a received signal and down-converts the frequency, etc. However, the transceiver (2310) is only one embodiment, and the components of the transceiver (2310) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (2310) can receive a signal through a wireless channel and output it to the processor (2330), and transmit a signal output from the processor (2330) through the wireless channel.

[0463] According to one embodiment, the memory (2320) can store programs and data necessary for the operation of the terminal. In addition, the memory (2320) can store control information or data included in signals transmitted and received by the terminal. The memory (2320) 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, the number of memories (2320) can be plural. According to one embodiment, the memory (2320) 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.

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

[0465] As illustrated in FIG. 24, the base station of the present disclosure may include a processor (2430), a transceiver (2410), and a memory (2420). 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 (2430), the transceiver (2410), and the memory (2420) may be implemented in the form of a single chip.

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

[0467] The transceiver (2410) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (2410) 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 (2410) is only one embodiment, and the components of the transceiver (2410) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (2410) can receive a signal through a wireless channel and output it to the processor (2430), and transmit a signal output from the processor (2430) through the wireless channel.

[0468] According to one embodiment, the memory (2420) can store programs and data necessary for the operation of the base station. In addition, the memory (2420) can store control information or data included in signals transmitted and received by the base station. The memory (2420) 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 (2420). According to one embodiment, the memory (2420) can store a program for performing the methods of the embodiments of the present disclosure described above.

[0469] 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.

[0470] 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 aid in understanding 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. Furthermore, each of the above embodiments can be combined and operated as needed.

[0471] 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.

[0472] In a method for a terminal to perform communication in a wireless communication system according to one embodiment of the present disclosure, a synchronization signal burst can be detected through beam sweeping. The method can perform synchronization based on the synchronization signal burst. The synchronization signal burst can have a two-dimensional structure with respect to the time axis and the frequency axis, including at least one synchronization signal block.

[0473] In one embodiment, the synchronization signal burst may be beam-allocated based on either the time axis or the frequency axis.

[0474] In one embodiment, the method can detect a synchronization signal based on a sync raster.

[0475] In one embodiment, the sync raster may be applied per at least one sync signal block unit or per sync signal burst unit.

[0476] In one embodiment, a synchronization signal block index for identifying a synchronization signal block among a synchronization signal burst may be indicated by at least one of a PBHC DM-RS or a PBCH payload.

[0477] In one embodiment, a guard band may be included between at least one synchronization signal block included in a synchronization signal burst.

[0478] In one embodiment, the location of CORESET 0 can be determined based on a value indicating a frequency offset obtained based on PBCH and a synchronization signal block index.

[0479] In a wireless communication system according to one embodiment of the present disclosure, a terminal performing communication may include a transceiver and at least one processor connected to the transceiver, and the at least one processor may detect a synchronization signal through beam sweeping. The at least one processor may perform synchronization based on a synchronization signal burst. The synchronization signal burst may include at least one synchronization signal block and may have a two-dimensional structure with respect to the time axis and the frequency axis.

[0480] In a wireless communication system according to one embodiment of the present disclosure, a method for performing communication by a base station may transmit a synchronization signal burst via a beam. The method may perform synchronization based on the synchronization signal burst. The synchronization signal burst may include at least one synchronization signal block and may have a two-dimensional structure with respect to the time axis and the frequency axis.

[0481] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0482] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

Claims

1. In a method for a terminal to perform communication in a wireless communication system, A step of detecting a synchronization signal burst through beam sweeping; and A step of performing synchronization based on the above synchronization signal burst; including; A method wherein the above-mentioned synchronization signal burst has a two-dimensional structure with respect to the time axis and the frequency axis, including at least one synchronization signal block.

2. In paragraph 1, A method in which the above-mentioned synchronization signal burst is assigned a beam based on one of the time axis or the frequency axis.

3. In the first paragraph, the step of detecting the synchronous signal burst comprises: A method comprising: a step of detecting a synchronization signal based on a sync raster; 4. In paragraph 3, A method wherein the above sync raster is applied per at least one sync signal block unit or per sync signal burst unit.

5. In paragraph 1, A method wherein a synchronization signal block index for identifying at least one synchronization signal block included in the synchronization signal burst is indicated by at least one of a physical broadcast channel (PBCH) demodulation reference signal (DM-RS) or a PBCH payload.

6. In paragraph 1, A method comprising a guard band between at least one synchronization signal block included in the synchronization signal burst.

7. In paragraph 1, A method further comprising: a step of determining a location of CORESET (control resource set) 0 based on a value indicating a frequency offset obtained based on a PBCH and a synchronization signal block index; 8. In a terminal performing communication in a wireless communication system, Transmitter and receiver; and At least one processor connected to the transceiver, wherein the at least one processor comprises: Detecting a synchronization signal burst through beam sweeping, Synchronization is performed based on the above synchronization signal burst, A terminal in which the above-mentioned synchronization signal burst has a two-dimensional structure with respect to the time axis and the frequency axis, including at least one synchronization signal block.

9. In paragraph 8, A terminal in which the above synchronization signal burst is assigned a beam based on one of the time axis or the frequency axis.

10. In the 8th paragraph, the at least one processor, A terminal that detects a synchronization signal based on a sync raster.

11. In paragraph 10, The above sync raster is applied to at least one synchronization signal block unit or synchronization signal burst unit of the terminal.

12. In paragraph 8, A terminal, wherein a synchronization signal block index for identifying at least one synchronization signal block included in the synchronization signal burst is indicated by at least one of a physical broadcast channel (PBCH) demodulation reference signal (DM-RS) or a PBCH payload.

13. In paragraph 8, A terminal comprising a guard band between at least one synchronization signal block included in the synchronization signal burst.

14. In the 8th paragraph, the at least one processor, A terminal that determines the location of CORESET (control resource set) 0 based on a value indicating a frequency offset obtained based on PBCH and a synchronization signal block index.

15. In a method for a base station to perform communication in a wireless communication system, A step of transmitting a synchronization signal burst through a beam; and A step of performing synchronization based on the above synchronization signal burst; including; A method wherein the above-mentioned synchronization signal burst has a two-dimensional structure with respect to the time axis and the frequency axis, including at least one synchronization signal block.

Images