Method and apparatus for communicating in a wireless communication system - Patents.com

Abstract

A method and an apparatus for communicating in a wireless communication system are disclosed. A method for a terminal to communicate in accordance with an embodiment of the present disclosure includes receiving a PBCH from a base station and monitoring a PDCCH for at least one of a first DCI or a second DCI, and a size of the first DCI including indication information indicating a channel access type may be equal to a size of the second DCI not including the indication information.

Description

[Technical field]

[0001] The present disclosure relates to wireless communication systems, and more particularly, to an uplink transmission and reception method and apparatus in a wireless communication system. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, resource shortages are occurring due to the explosive increase in traffic, and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for the next generation mobile communication system are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, support very low end-to-end latency, and high energy efficiency.To achieve this, various technologies such as dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving communications in a wireless communication system.

[0005] Furthermore, a further technical objective of the present disclosure is to provide a method and apparatus for transmitting and receiving SS / PBCH blocks in an unlicensed band.

[0006] The technical problems to be achieved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] According to one embodiment of the present disclosure, there is provided a method for a terminal to communicate in a wireless communication system, the method including: a step of receiving a physical broadcast channel (PBCH) from a base station; and a step of monitoring a physical downlink control channel (PDCCH) for at least one of a first downlink control information (DCI) or a second DCI, wherein a size of the first DCI including indication information indicating a channel access type and a size of the second DCI not including the indication information may be identical.

[0008] A method for a base station to communicate in a wireless communication system, the method including: a step of transmitting a physical broadcast channel (PBCH) to a terminal; and a step of transmitting a physical downlink control channel (PDCCH) to the terminal for at least one of a first downlink control information (DCI) or a second DCI, wherein a size of the first DCI including indication information indicating a channel access type and a size of the second DCI not including the indication information may be the same. Effect of the Invention

[0009] According to an embodiment of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system can be provided.

[0010] According to one embodiment of the present disclosure, a method and apparatus for transmitting and receiving SS / PBCH blocks in an unlicensed band can also be provided.

[0011] According to one embodiment of the present disclosure, even if it is not confirmed whether the band is unlicensed or not through MIB information, etc., the fallback DCI size can be made uniform to reduce the complexity of PDCCH blind decoding of the terminal.

[0012] According to one embodiment of the present disclosure, the probability of transmission failure due to CAP failure can be reduced by increasing the opportunities for transmitting SS / PBCH blocks in the unlicensed band of the FR2-2 band.

[0013] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief description of the drawings]

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure.

[0015] [Figure 1] FIG. 1 illustrates a structure of a wireless communication system to which the present disclosure can be applied. [Diagram 2] 1 is a diagram illustrating a frame structure in a wireless communication system to which the present disclosure can be applied. [Diagram 3] FIG. 1 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4]FIG. 1 is a diagram illustrating a physical resource block in a wireless communication system to which the present disclosure can be applied. [Diagram 5] FIG. 1 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 is a diagram illustrating physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission / reception method using the physical channels. [Figure 7] FIG. 1 is a diagram for explaining a wireless communication system that supports an unlicensed band according to one embodiment of the present disclosure. [Figure 8] FIG. 2 illustrates a symbol-level diagram of an SS / PBCH block transmission over time according to one embodiment of the present disclosure. [Figure 9] FIG. 2 illustrates a symbol-level diagram of an SS / PBCH block transmission over time according to one embodiment of the present disclosure. [Figure 10] FIG. 2 illustrates a symbol-level diagram of an SS / PBCH block transmission over time according to one embodiment of the present disclosure. [Figure 11] FIG. 2 is a diagram for explaining a method for a terminal to perform communication according to an embodiment of the present disclosure. [Figure 12] FIG. 1 is a diagram for explaining a method in which a base station performs communication according to one embodiment of the present disclosure. [Figure 13] A diagram for explaining the signaling procedures of the network side and the terminal to which the present disclosure can be applied. [Figure 14] FIG. 2 is a block diagram of a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to show the only embodiment in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0017] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or may be shown in the form of a block diagram focusing on the core functions of each structure and device.

[0018] In the present disclosure, when an element is "coupled," "coupled," or "connected" to another element, this can include a direct connection as well as an indirect connection where there is still another element between them. Also, in the present disclosure, the terms "including" or "having" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0019] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0020] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0021] The present disclosure is described with respect to a wireless communication network or wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in a process in which a terminal coupled to the wireless network transmits or receives signals to or between the network.

[0022] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0023] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, road side unit (RSU), robot, Artificial Intelligence (AI) module, drone (UAV: Unmanned Aerial Vehicle), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

[0024] The following technologies may be used for various wireless access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project)® LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0025] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be called a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be called a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published before the present disclosure. For example, the following documents may be referenced.

[0026] In 3GPP LTE, reference can be made to TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (general description), and TS 36.331 (radio resource control).

[0027] For 3GPP NR, reference can be made to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (General description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio resource control protocol standard).

[0028] The following terminology abbreviations may be used in this disclosure:

[0029] - BM: Beam management

[0030] - CQI: channel quality indicator

[0031] - CRI: channel state information- reference signal resource indicator

[0032] - CSI: channel state information

[0033] - CSI-IM: channel state information-interference measurement

[0034] - CSI-RS: Channel state information-reference signal

[0035] - DMRS: Demodulation Reference Signal

[0036] - FDM: Frequency division multiplexing

[0037] - FFT: Fast Fourier transform

[0038] - IFDMA: Interleaved frequency division multiple access

[0039] - IFFT: inverse fast Fourier transform

[0040] - L1-RSRP: Layer 1 reference signal received power

[0041] - L1-RSRQ: Layer 1 reference signal received quality

[0042] - MAC: medium access control

[0043] - NZP: non-zero power

[0044] - OFDM: Orthogonal frequency division multiplexing

[0045] - PDCCH: physical downlink control channel

[0046] - PDSCH: physical downlink shared channel

[0047] - PMI: Precoding matrix indicator

[0048] - RE: resource element

[0049] - RI: Rank indicator

[0050] - RRC: Radio resource control

[0051] - RSSI: received signal strength indicator

[0052] - Rx: Reception

[0053] - QCL: quasi co-location

[0054] - SINR: signal to interference and noise ratio

[0055] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH))

[0056] - TDM: time division multiplexing

[0057] - TRP: transmission and reception point

[0058] - TRS: Tracking reference signal

[0059] - Tx: transmission

[0060] - UE: User Equipment

[0061] - ZP: Zero power

[0062] System in general

[0063] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. Massive Machine Type Communications (MTC), which connects a large number of devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system design considering reliability and latency-sensitive services / terminals is also being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience in this disclosure, the technology is referred to as NR. NR is an expression representing an example of 5G RAT.

[0064] New RAT systems including NR use an OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist in one cell.

[0065] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0066] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0067] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) user plane (i.e., new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for UEs. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

[0068] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0069] The NR system can support multiple numerologies, where the numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, the multiple subcarrier spacing may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). In addition, the numerology used may be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.

[0070] The following describes OFDM numerologies and frame structures that can be considered in the NR system. A number of OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0071] [Table 1]

[0072] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in a traditional cellular band, when the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 may be configured as shown in Table 2 below. Also, FR2 can mean millimeter wave (mmW).

[0073] [Table 2]

[0074] In relation to the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f= 4096. Downlink and uplink transmissions are f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, the transmission from the terminal in the uplink frame number i starts T from the start of the corresponding downlink frame in the terminal. TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols. symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ), and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0075] [Table 3]

[0076] [Table 4]

[0077] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe can include four slots. One subframe={1, 2, 4} slots shown in FIG. 2 is an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot can include 2, 4, or 7 symbols, or more or less symbols. In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, and the like may be considered.

[0078] The physical resources that can be considered in the NR system will be specifically described below. First, in relation to antenna ports, the antenna ports are defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. If the large-scale property of a channel on which a symbol on one antenna port is carried can be inferred from a channel on which a symbol on the other antenna port is carried, the two antenna ports are said to be in a quasi co-located (QC / QCL) relationship. Here, the large-scale property includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0079] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure is applicable.

[0080] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB Each subframe consists of 14.2 subcarriers. μ In the present embodiment, the OFDM symbol is used as an example, but is not limited to, an OFDM symbol. RB μ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RB μ ≦N RB max,μ The above N RBmax,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as numerology. In this case, one resource grid may be set for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair. It is uniquely identified by JPEG0007608634000005.jpg8118, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG0007608634000006.jpg10133 represents the position of the symbol within a subframe. When referring to resource elements in a slot, the index pair (k,l) is used, where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG0007608634000007.jpg8118 is a complex value JPEG0007608634000008.jpg12113. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indexes p and μ may be dropped, so that the complex value is JPEG0007608634000009.jpg12110 or JPEG0007608634000010.jpg11105. Also, a resource block (RB) is N sc RB = 12 consecutive subcarriers.

[0081] Point A serves as a common reference point for the resource block grid and is obtained as follows:

[0082] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0083] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number).

[0084] Common resource blocks are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n CRB μ The relationship between k, l and the resource element (k, l) for the subcarrier spacing setting μ is given by the following Equation 1.

[0085]

number

[0086] In Equation 1, k is defined relative to point A such that k=0 corresponds to the subcarrier centered at point A. A physical resource block is a number ranging from 0 to N within a bandwidth part (BWP). BWP,i size,μ The numbering is from -1 to i, where i is the number of the BWP. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0087]

number

[0088] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0089] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0090] 4 and 5, a slot includes a number of symbols in the time domain. For example, in the general CP, one slot includes seven symbols, whereas in the extended CP, one slot includes six symbols.

[0091] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed in the activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0092] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating in one wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band in the CC. Alternatively, the capability for maximum bandwidth may differ for each terminal. In consideration of this, the base station may instruct the terminal to operate only in a part of the bandwidth rather than the entire bandwidth of the wideband CC, and the part of the bandwidth is defined as a bandwidth part (BWP) for convenience. The BWP may be composed of continuous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0093] Meanwhile, the base station can set multiple BWPs even within one CC set in the terminal. For example, a BWP occupying a relatively small frequency region can be set in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, when UEs are concentrated in a specific BWP, other BWPs can be set in some terminals for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between adjacent cells, some spectrums of the entire bandwidth can be excluded and both BWPs can be set in the same slot. That is, the base station can set at least one DL / UL BWP in the terminal associated with the wideband CC. The base station can activate at least one DL / UL BWP set at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). Also, the base station may instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Or, the base station may switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in a situation where the UE is performing an initial access process or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP. In such a situation, the DL / UL BWP assumed by the UE is defined as an initially active DL / UL BWP.

[0094] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0095] In a wireless communication system, a terminal receives information from a base station through a downlink, and transmits information to the base station through an uplink. Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information they transmit and receive.

[0096] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). After that, the terminal receives a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the downlink channel state.

[0097] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on the information carried on the PDCCH, and can obtain more specific system information (S602).

[0098] Meanwhile, when the terminal first connects to the base station or has no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) to the base station (steps S603 to S606). To this end, the terminal can transmit a specific sequence as a preamble on a physical random access channel (PRACH) (S603 and S605) and receive a response message to the preamble on a PDCCH and a corresponding PDSCH (S604 and S606). In the case of a contention-based RACH, the terminal can also perform a contention resolution procedure.

[0099] After performing the above-mentioned procedures, the terminal can then perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the terminal receives Downlink Control Information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and has different formats depending on its purpose.

[0100] Meanwhile, control information that a terminal transmits to a base station in an uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI in a PUSCH and / or a PUCCH.

[0101] Table 5 shows an example of a DCI format in an NR system.

[0102] [Table 5]

[0103] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid- Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each of the DCI formats may be predefined.

[0104] DCI format 0_0 is used for scheduling PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0105] DCI format 0_1 ​​is used to indicate to a terminal the scheduling of one or more PUSCHs in one cell or downlink feedback information of a configured grant (CG). Information included in DCI format 0_1 ​​is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and transmitted.

[0106] DCI format 0_2 is used for PUSCH scheduling in one cell. Information included in DCI format 0_2 is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and transmitted.

[0107] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each of the DCI formats may be pre-defined.

[0108] DCI format 1_0 is used for scheduling the PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0109] DCI format 1_1 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0110] DCI format 1_2 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0111] Wireless communication system supporting unlicensed band / shared spectrum

[0112] Below, with reference to FIG. 7, a wireless communication system supporting an unlicensed spectrum (e.g., an unlicensed spectrum (NR-U) system) applicable to the present disclosure will be described.

[0113] In the following description, a cell operating in a licensed band (L-band) is defined as an LCell, and a carrier of the LCell is defined as an LCC (downlink / uplink). A cell operating in an unlicensed band (U-band) is defined as an UCell, and a carrier of the UCell is defined as an UCC (downlink / uplink).

[0114] A cell's carrier / carrier frequency may refer to the operating frequency (e.g., center frequency) of a cell. A cell / carrier (e.g., a component carrier (CC) is collectively referred to as a cell).

[0115] As shown in (a) of Figure 7, when a terminal and a base station transmit and receive signals using a carrier aggregated (CA) LCC and UCC, the LCC may be configured as a PCC (primary CC) and the UCC may be configured as a SCC (secondary CC).

[0116] As shown in (b) of FIG. 7, the terminal and the base station can transmit and receive signals using one UCC or multiple UCCs that are carrier aggregated. That is, the terminal and the base station can transmit and receive signals using only UCCs without an LCC. For standalone operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supported in the UCell.

[0117] For example, an unlicensed band may include a particular frequency range (eg, above 52.6 GHz to 71 GHz) that is higher than existing frequency ranges (eg, FR1 and FR2).

[0118] The specific frequency range may be referred to as FR2-2 (in this case, the existing FR2 (i.e., 24250 MHz to 52600 MHz) may be referred to as FR2-1) or FR3. The scope of the present disclosure is not limited to the names FR2-2 or FR3.

[0119] The following describes operations related to the channel access procedure (CAP) (in FR2-2) and their corresponding types (ie, channel access types).

[0120] In the description of the present disclosure, the type 1 CAP among the CAP types refers to a CAP that backs off at a fixed contention window size (CWS). Specifically, the type 1 CAP is a CAP in which a transmitting node selects a back-off counter N integer value from 0 to CWS, and then decreases the counter value every time it is confirmed that the channel is idle. When the back-off counter value becomes 0, transmission is allowed.

[0121] Among the CAP types, type 2 CAP refers to a CAP in which transmission is permitted only when it is confirmed that the channel is idle at a specific time immediately before transmission without a backoff process.

[0122] A CAP for accessing a channel on which a transmission operation is to be performed by a base station / terminal may be applied when the base station / terminal is required by (predefined) regulations to sense the channel for availability to transmit on the channel, or when the base station provides the terminal with an upper layer parameter "LBT-Mode" or a dedicated configuration by SIB1 (system information block type 1) indicating that a CAP is to be performed for transmitting on the channel.

[0123] Here, when sensing is applicable, the basic unit for sensing is a duration (e.g., T sl The sensing slot has a sensing slot period (T sl ) and senses the channel, and the energy detected after the antenna assembly in the sensing slot section is equal to or greater than the energy detection threshold (X thres ), the channel is in the sensing slot period (Tsl ) may be considered to be idle. Otherwise, the channel is in a sensing slot period (T sl ) may be considered to be in a busy state (or in use).

[0124] A spatial domain filter for sensing beams in the sensing slot section can cover the transmission beams of the intended transmission within the channel occupancy. The above operations may be performed by the base station, or by the terminal when the terminal does not indicate a capability for beam correspondence without uplink beam sweeping, or by the terminal when the terminal uses a beam different from the beam used for transmission for sensing.

[0125] If the terminal indicates capability for beam correspondence without uplink beam sweeping and the terminal selects the same sensing beam as the transmission beam, a spatial domain filter for the sensing beam may be determined.

[0126] When the channel occupancy involves transmission of different beams multiplexed in the spatial domain, any one of the following may be applied to the corresponding sensing for transmitting within the channel occupancy.

[0127] - Type 1 CAP may be applied before the start of channel occupancy using a single sensing beam, which may cover all transmission beams in the channel occupancy. Once the channel is accessed, transmissions using other beams may take place (or occur) in the channel occupancy.

[0128] - Type 1 CAP may be applied simultaneously for each sensing beam before the start of channel occupancy, and each sensing beam may cover a transmission beam within the channel occupancy. Once the channel is accessed, transmission with other beams may take place (or occur) within the channel occupancy.

[0129] When a channel occupancy involves transmission of different beams multiplexed in the time domain, any one of the following may be applied to the corresponding sensing for transmitting within the channel occupancy.

[0130] Type 1 CAP may be applied before the start of channel occupancy with a single sensing beam, which may cover all transmission beams in the channel occupancy. Once the channel is accessed, transmissions with other beams may be performed by procedures (e.g. according to Type 3 CAP) in the channel occupancy.

[0131] - If the base station / terminal can perform simultaneous sensing on different beams, Type 1 CAP may be applied for each sensing beam before the start of channel occupancy, and each sensing beam may cover a transmission beam in the channel occupancy. Once the channel is accessed, transmission using other beams may occur by a procedure (e.g., a procedure according to Type 3 CAP) in the channel occupancy.

[0132] In the case where the base station / terminal can perform simultaneous sensing on different beams, Type 1 CAP may be applied before the start of channel occupation for each sensing beam where each sensing beam covers a transmission beam in the channel occupation. Once the channel is accessed, transmission may occur according to a procedure (e.g., a procedure according to Type 2 CAP) before switching to another beam in the channel occupation.

[0133] The following describes operations associated with type-specific CAPs (eg, Type 1 CAP, Type 2 CAP, and Type 3 CAP).

[0134] For example, a CAP (i.e., Type 1 CAP) may be performed by a base station / terminal when the time duration spanning a sensing slot sensed as idle before transmission is random based on a fixed contention window (CW) size. Type 1 CAP may be applied to all transmission operations that initiate channel occupation by a base station / terminal.

[0135] The base station / terminal determines the defer duration (T d ) the channel is first sensed to be in an idle state, and then transmission may be performed after counter N reaches 0 in step 4.

[0136] The counter N may be adjusted by sensing the channel for the additional sensing slot period according to the following steps.

[0137] 1st stage)N=N init and move to step 4, where N init is a random number uniformly distributed between 0 and CW.

[0138] 2nd stage) If N>0 and the terminal chooses to decrement the counter, set N=N-1.

[0139] Step 3) Senses the channel during the additional slot section, and if the additional slot section is idle, moves to step 4, otherwise moves to step 5.

[0140] Step 4) If N=0, stop (or terminate) the CAP operation, otherwise move to step 2.

[0141] 5 steps) Channel sensing is performed until a busy slot is detected in the additional delay section or until all slots in the additional delay section are detected as idle.

[0142] 6th step) If the channel is sensed as being idle for all slots of the additional delay section, it moves to 4th step, otherwise it moves to 5th step.

[0143] In the above procedure, the CW may be 3, but is not limited thereto. And, the delay period (e.g., 8 us) may include at least a sensing slot period for performing a single measurement to determine whether the channel is idle. The base station / terminal may not perform a transmission operation on the channel during a channel occupancy time exceeding 5 ms.

[0144] As yet another example, when the time duration extended by a sensing slot sensed as idle before DL / UL transmission is deterministic, another type of CAP (i.e., Type 2 CAP) may be performed (or applied) by the base station / terminal.

[0145] For example, when Type 2 CAP is applied, the base station / terminal may sense the channel as being in an idle state during a period (T sl = 5us) including the sensing slot T d A transmission can take place on the immediately following channel.

[0146] As yet another example, when Type 3 CAP is applied, the base station / terminal can perform a transmission operation without sensing the channel.

[0147] The method proposed in this disclosure will be specifically described below.

[0148] As many communication devices require larger communication capacity, wireless communication systems need to efficiently use limited frequency bands. Among wireless communication systems, cellular communication systems can use the unlicensed 2.4 GHz band or use unlicensed bands such as the 5 GHz and / or 60 GHz bands for traffic offloading.

[0149] In this case, since it is assumed that in the unlicensed band, each communication node performs wireless communication through contention, each communication node must perform channel sensing before transmitting a signal to check whether other communication nodes are transmitting a signal.

[0150] For the convenience of the description of the present disclosure, the operations of the communication nodes are collectively referred to as LBT (listen before talk) or channel access procedure (CAP). Hereinafter, in the description of the present disclosure, LBT may be substituted with CAP.

[0151] The operation of checking whether other communication nodes are transmitting signals is defined as carrier sensing (CS), and when it is determined that other communication nodes are not transmitting signals, it is defined that clear channel assessment (CCA) is confirmed.

[0152] In order for an eNB / gNB or terminal to transmit a signal in the unlicensed band (called U-band), it must perform LBT. When an eNB / gNB or terminal in an LTE / NR system transmits a signal, other communication nodes such as Wi-Fi (or WiGig (wireless gigabit alliance) such as 802.11ad / ay) also need to perform LBT to avoid interference.

[0153] The basic wireless communication system may operate in bands below 52.6 GHz, but is not limited to such, and may also operate in licensed and / or unlicensed bands above 52.6 GHz (eg, the 60 / 70 GHz bands).

[0154] This disclosure discloses an initial access method including SS / PBCH block transmission and reception operations on the 52.6 GHz unlicensed band. Specifically, this disclosure discloses a method for increasing the transmission opportunities of SS / PBCH blocks in the CAP-based unlicensed band. The method disclosed herein may be equally applied to the licensed band of the same band.

[0155] In a basic wireless communication system, the mmWave band (e.g., 7.125 or above 24 GHz, up to 52.6 GHz) may be defined as frequency range (FR) 2 (or FR2-1), and the SCS of the SS / PBCH band in that band may be 120 or 240 kHz.

[0156] Specifically, referring to Fig. 8, a maximum of four or eight SS / PBCH block transmissions are possible within 0.25 ms (for example, two slots based on a 120 kHz SCS, or four slots based on a 240 kHz SCS). Here, Fig. 8 is a diagram showing SS / PBCH block transmissions by SCS at the symbol level on the time axis.

[0157] For example, in the 120 kHz SCS standard, SS / PBCH block (candidate) index n may be transmitted in symbols 4 / 5 / 6 / 7 of the first slot, SS / PBCH block (candidate) index n+1 may be transmitted in symbols 8 / 9 / 10 / 11 of the first slot, SS / PBCH block (candidate) index n+2 may be transmitted in symbols 2 / 3 / 4 / 5 of the second slot, and SS / PBCH block (candidate) index n+3 may be transmitted in symbols 6 / 7 / 8 / 9 of the second slot.

[0158] As yet another example, in the 240 kHz SCS standard, SS / PBCH block (candidate) index n may be transmitted in symbols 8 / 9 / 10 / 11 of the first slot, SS / PBCH block (candidate) index n+1 may be transmitted in symbols 12 / 13 of the first slot and symbols 0 / 1 of the second slot, SS / PBCH block (candidate) index n+2 may be transmitted in symbols 2 / 3 / 4 / 5 of the second slot, and SS / PBCH block (candidate) index n+3 may be transmitted in symbols 6 / 7 / 8 / 9 of the second slot. Then, SS / PBCH block (candidate) index n+4 may be transmitted in symbols 4 / 5 / 6 / 7 of the third slot, SS / PBCH block (candidate) index n+5 may be transmitted in symbols 8 / 9 / 10 / 11 of the third slot, SS / PBCH block (candidate) index n+6 may be transmitted in symbols 12 / 13 of the third slot and 0 / 1 of the fourth slot, and SS / PBCH block (candidate) index n+7 may be transmitted in symbols 2 / 3 / 4 / 5 of the fourth slot.

[0159] In this disclosure, the window (S_window) in which SS / PBCH blocks can be transmitted is assumed to be a 5 ms window, however, this is only one example and the base station can set the duration of the window to other values ​​(e.g., 0.5 / 1 / 2 / 3 / 4 msec, etc.).

[0160] In a 5 msec window, there are a total of 40 slots based on the 120 kHz SCS standard, and SS / PBCH may be transmitted in 8 consecutive slots, and a 2-slot gap (e.g., slots 8-9) may exist in the 8 consecutive slots (e.g., slots 0-7 / 10-17). In this case, a maximum of 4 SS / PBCH blocks may be transmitted in 2 slots (e.g., slots 0-1 / 2-3 / 4-5 / 6-7) out of the 8 consecutive slots (e.g., slots 0-7) in which SS / PBCH blocks may be transmitted, as in the 120 kHz standard case shown in FIG. 8.

[0161] Similarly, in a 5 msec window, there are a total of 80 slots based on the 240 kHz SCS standard, and SS / PBCH blocks may be transmitted in 16 consecutive slots, with a 4-slot gap (e.g., slots 16-19) in the 16 consecutive slots (e.g., slots 0-15 / 20-35). In this case, up to 8 SS / PBCH blocks may be transmitted in 4 slots (e.g., slots 0-3 / 4-7 / 8-11 / 12-15) out of the 16 consecutive slots (e.g., slots 0-15) in which SS / PBCH blocks may be transmitted, as in the 240 kHz standard case shown in FIG. 8.

[0162] That is, the maximum number of SS / PBCH block (candidate) indexes allowed in 120 kHz and 240 kHz SCS may be limited to 64, and which index out of the maximum 64 SS / PBCH blocks actually correspond to may be configured to be transmitted by cell-specific or UE-specific RRC signaling.

[0163] Even if the wireless communication system is extended to bands above 52.6 GHz (eg, 60 / 70 GHz) (ie, FR3 or FR2-2), the SCS for the SS / PBCH block may be 120 kHz or 240 kHz as defined in FR2.

[0164] Furthermore, in consideration of wideband operation up to 2 GHz bandwidth (approximately 2.16 GHz), 480 kHz or 960 kHz may be applied as the SCS for the SS / PBCH block. The present disclosure discloses a method for increasing transmission opportunities during unlicensed band operation of the SS / PBCH block.

[0165] The present disclosure also discloses a method for obtaining serving cell timing, obtaining quasi-co-location (QCL) relationships between SS / PBCH blocks, or informing an SS / PBCH block (candidate) index that is actually transmitted among a maximum of 64 SS / PBCH blocks.

[0166] In the context of this disclosure, having a QCL relationship between two SS / PBCH blocks can mean that the two SS / PBCH blocks have identical (large-scale) channel properties (e.g., average gain, Doppler shift, average delay, delay spread, spatial Rx parameters, etc.).

[0167] The following describes in detail how to resolve the ambiguity regarding the payload size of DCI in the FR2-2 band.

[0168] Fig. 11 is a flowchart for explaining a method in which a terminal performs communication according to an embodiment of the present disclosure. Fig. 11 shows a case in which a terminal operates in a wireless communication system in the FR2-2 band. However, this is only one embodiment, and the operation described with reference to Fig. 11 may be expanded and applied to operations in bands other than the FR2-2 band.

[0169] The terminal can receive a physical broadcast channel (PBCH) from the base station (S1110).

[0170] Here, the PBCH (or the master information block (MIB) transmitted in the PBCH) does not need to include information indicating whether or not to perform LBT (listen before talk). In other words, whether or not to perform LBT does not need to be explicitly (or / and implicitly) indicated using the PBCH (or the MIB).

[0171] Here, the information indicating whether or not to perform LBT may be replaced with information indicating whether or not to perform CAP and / or information indicating whether the cell belongs to a licensed band or an unlicensed band.

[0172] The process of the terminal receiving (or acquiring) the PBCH may be included in the process of receiving system information (SI). The system information may include an MIB and a plurality of system information blocks (SIB). System information other than the MIB may be collectively referred to as Remaining Minimum System Information (RMSI).

[0173] The MIB may include information / parameters related to system information block type 1 (SIB1) reception and may be transmitted on the PBCH of the SSB. The MIB may include a "subCarrierSpacingCommon" field, an "ssb-SubcarrierOffset" field, and a "pdcch-ConfigSIB1" field.

[0174] Here, SIB1 may include information related to availability and scheduling (e.g., transmission period, SI window size, etc.) of the remaining SIBs (hereinafter, referred to as SIBx, where x is an integer equal to or greater than 1). For example, SIB1 may indicate whether SIBx is broadcast periodically or / and provided in response to a request from a terminal in an on-demand manner. If SIBx is provided in an on-demand manner, SIB1 may include information required for a terminal to make an SI request. SIB1 may be transmitted on a PDSCH, a PDCCH that schedules SIB1 may be transmitted in a Type0-PDCCH common search space, and SIB1 may be transmitted on a PDSCH indicated by the PDCCH. Then, SIBx may be included in an SI message and transmitted on the PDSCH. Each SI message may be transmitted within a periodically occurring time window (i.e., an SI window).

[0175] The terminal may monitor a physical downlink control channel (PDCCH) for at least one of the first downlink control information (DCI) or the second DCI (S1120).

[0176] Here, the terminal may monitor the PDCCH in a common search space (CSS) (e.g., a type 0-PDCCH CSS, etc.), and at least one of the first DCI or the second DCI may be cyclic redundancy check (CRC) scrambled by a system information (SI)-radio network temporary identifier (RNTI).

[0177] The size (or size) of a first DCI including indication information (e.g., information corresponding to the "ChannelAccess-CPext" field) indicating a channel access type (or LBT type) and the size (or size) of a second DCI not including the indication information may be the same.

[0178] That is, when whether or not to perform LBT is not configured by the PBCH (or MIB), a specific bit (for example, 2 bits or 1 bit) may be added to the DCI detected by PDCCH monitoring.

[0179] For example, the reserved bit size in at least one of the first DCI or the second DCI may be 16 bits or 17 bits, and the size of the indication information may be 1 bit or 2 bits. Here, the indication information (or / and the size of the indication information) may be the same as the specific bit (or / and the size of the specific bit) added to the DCI.

[0180] The terminal may be instructed / configured as to whether to perform LBT by a system information block (SIB) received from the base station. Then, based on the instruction / configuration as to whether to perform LBT by the SIB, the terminal may detect the first DCI or the second DCI by using PDCCH monitoring.

[0181] For example, the PDCCH may be monitored for the first DCI based on the setting of performing the LBT by the SIB. That is, when the setting of performing the LBT by the SIB is set, the terminal may monitor for the first DCI including indication information indicating a channel access type (or an LBT type).

[0182] As yet another example, the terminal may monitor for a second DCI that does not include indication information based on the setting of not performing LBT by the SIB. Based on the second DCI being monitored (or detected), the terminal may ignore a bit corresponding to the position of the indication information in the second DCI. That is, the terminal may ignore a specific bit included in the second DCI without using it to indicate a channel access type (or an LBT type).

[0183] Fig. 12 is a flowchart for explaining a method for a base station to perform communication according to an embodiment of the present disclosure. Fig. 12 shows a case where a base station operates in a wireless communication system in the FR2-2 band. However, this is only one embodiment, and the operation described with reference to Fig. 12 may be expanded and applied to operations in bands other than the FR2-2 band.

[0184] The base station may transmit the PBCH to the terminal (S1210). Here, the PBCH may not include information indicating whether or not to perform the LBT. That is, whether or not to perform the LBT may not be explicitly (or / and implicitly) indicated by the PBCH (or the MIB).

[0185] The base station may transmit a PDCCH for at least one of the first DCI or the second DCI to the terminal (S1220). That is, the terminal may monitor a PDCCH for at least one of the first DCI or the second DCI.

[0186] Here, the size of the first DCI including information indicating the channel access type (or LBT type) and the size of the second DCI not including the indication information may be the same. The sizes of the first DCI and the second DCI have been described with reference to FIG. 11, so duplicated description will be omitted.

[0187] The base station can use the SIB to instruct / set the terminal as to whether or not to perform LBT. The SIB transmitted by the base station may change the DCI detected by the terminal. For example, based on the SIB setting to perform LBT, the terminal can detect the first DCI by PDCCH monitoring. As yet another example, based on the SIB setting to not perform BT, the terminal can detect the second DCI by PDCCH monitoring.

[0188] Hereinafter, an embodiment related to an initial access procedure including an SS / PBCH block transmission / reception operation in an unlicensed band will be described in detail.

[0189] Example 1

[0190] The LBT scheme to be performed by the base station may be configured (or signaled) to the terminal by a downlink (DL) signal / channel (for example, SS / PBCH block, etc.) (in a specific section).

[0191] A base station (operating in a specific unlicensed band of FR3 (or FR2-2)) may be allowed to transmit without determining whether the channel is idle / busy depending on specific conditions (e.g., the interference level is low, the probability of downlink success is high so that the frequency of collisions is low, the transmission frequency is low, the transmission power is low, etc.).

[0192] In the description of this disclosure, an LBT scheme in which transmission is permitted without determining whether the channel is idle / busy is named LBT scheme A, and an LBT scheme in which transmission is permitted only when the channel is determined to be idle is named LBT scheme B.

[0193] Alternatively, a terminal may be configured (or signaled) as to whether or not it is given multiple transmission opportunities for SS / PBCH blocks that are QCLed within the S_window.

[0194] For example, in the case of 120 kHz SCS, SS / PBCH block (candidate) indexes 0 to 63 can be defined within a 5 msec window as shown in Fig. 9. Then, when the QCL parameter (i.e., QCL_para) value is 32, SS / PBCH block (candidate) index #N (N<32) and SS / PBCH block (candidate) index #N+32 can have a QCL relationship with each other within the 5 msec window.

[0195] That is, the base station's LBT failure may be compensated for by providing an opportunity to transmit SS / PBCH blocks having the same beam twice within a 5 msec window.

[0196] For the convenience of explanation of the present disclosure, a mode in which multiple transmission opportunities may be provided for a QCLed SS / PBCH block within the S_window (or discovery burst transmission window, DBTW) (i.e., a QCL_para value may be set) is defined as DBTW_on, and a mode in which a terminal cannot assume that there is a QCL relationship between different candidate SS / PBCH block indexes is defined as DBTW_off.

[0197] In this case, the base station can instruct / set to the terminal whether the LBT scheme performed by the base station is LBT scheme A or LBT scheme B using higher layer signaling (e.g., cell-specific RRC signaling, UE-specific RRC signaling, medium access control (MAC)-CE (control element)) or (terminal-specific or group-common) DCI.

[0198] Alternatively, the base station may use higher layer signaling or DCI to indicate to the terminal whether the current mode is DBTW_on or DBTW_off.

[0199] When LBT scheme B is set / instructed as the LBT scheme performed by the base station (or when DBTW_on is set / instructed), multiple transmission opportunities may be provided for the QCLed SS / PBCH blocks within the S_window as shown in Fig. 10. Then, the terminal may assume that some of them may be transmitted from the base station depending on the success / failure of the LBT of the base station. Thus, when the terminal performs measurement operations such as RLM / RRM using the SS / PBCH blocks (within the S_window), it may perform the measurement operations over the entire interval within the S_window.

[0200] For example, the terminal may use all SS / PBCH block (candidate) indexes that have a QCL relationship with a specific SS / PBCH block (candidate) index for radio link monitoring corresponding to the SS / PBCH block (candidate) index, where the specific SS / PBCH block (candidate) may include an SS / PBCH block whose MIB has been acquired (by the terminal).

[0201] Radio link monitoring may also include PUSCH / SRS pass loss (PL) estimation based on SS / PBCH blocks, in which case the terminal may calculate the PL using RS resources from SS / PBCH (candidate) blocks having the same SS / PBCH block index as used in acquiring the MIB.

[0202] As yet another example, when LBT scheme A is set / instructed as the LBT scheme performed by the base station (or when DBTW_off is set / instructed), the terminal can assume that only a specific QCL_para number of SS / PBCH blocks (within S_window) (or 64 blocks (without signaling for QCL_para)) are transmitted.

[0203] That is, when QCL_para is set / instructed as 64, the terminal can only expect to receive SS / PBCH with SS / PBCH block (candidate) indexes 0 to 63 in FIG. 10. The base station is expected to use LBT scheme A, and therefore DL signal transmission such as SS / PBCH blocks may always be possible. Therefore, when the terminal performs measurements such as RLM / RRM using SS / PBCH blocks (within S_window), it only performs measurements in a specific (compressed) interval within S_window and does not need to perform measurements in the remaining intervals, which may reduce power consumption.

[0204] When LBT scheme A is set / instructed as the LBT scheme to be performed by the base station (or when DBTW_off is set / instructed), the indicated LBT scheme (or LBT scheme A) may be valid in a specific interval, and the specific interval may be defined or set in advance (e.g., a period during which SIB information may be modified, such as 1 sec).

[0205] When the specific period expires, the terminal can assume LBT scheme B (or DBTW_on). In addition, the LBT scheme indication (or DBTW_on or DBTW_off indication) may be indicated to neighbor cells as well as the serving cell by a UE-common or UE-specific higher layer (e.g., RRC signaling such as "MeasObjectNR IE (Information Element)").

[0206] Furthermore, when LBT scheme A (or DBTW_off) is instructed for a neighboring cell, RRM measurements are performed only for the QCL_para value (or up to 64 SS / PBCH blocks) for that cell within the S_window (e.g., from the start of the S_window), and RRM measurements do not need to be performed in other sections.

[0207] Similarly, an LBT scheme indication (or a DBTW_on or DBTW_off indication) may be indicated by terminal-common or terminal-specific higher layer signaling (e.g., RRC signaling such as "MeasObjectNR IE") for inter-frequency measurements and / or SCell addition, etc.

[0208] The signaling may be specified commonly for a specific frequency (or a frequency band or a frequency carrier) (option 1), or may be specified for each specific (adjacent) cell (option 2). When option 1 and option 2 are both configured for a specific frequency and a specific cell, the terminal may prioritize option 2 (i.e., cell-specific signaling) for the cell and ignore option 1.

[0209] Specifically, when DBTW_off (or LBT scheme A) is indicated / configured for a specific frequency, the terminal may expect that a QCL_para value will not be configured for that frequency, or may ignore the value even if it is configured.

[0210] Alternatively, when DBTW_off (or LBT scheme A) is indicated / configured for a specific cell, the terminal may expect that the QCL_para value will not be configured for the cell or for the frequency in which the cell is located, or may ignore the QCL_para value even if it is configured. In this case, the terminal expecting that the QCL_para value will not be configured or ignoring the QCL_para value even if it is configured may mean that the terminal cannot assume that there is a QCL relationship between different candidate SS / PBCH block indexes. Conversely, the terminal may expect that the QCL_para value will be configured only for cells or frequencies in which DBTW_on (or LBT scheme B) is configured.

[0211] In addition, the method of monitoring the Type0-PDCCH CSS set may change depending on the indicated LBT scheme (or indicated DBTW_on or DBTW_off).

[0212] For example, when LBT scheme B is configured / indicated (or DBTW_on is configured / indicated), the terminal can assume that a Type 0-PDCCH CSS set corresponding to all SS / PBCH block (candidate) indices that have a QCL relationship with a specific SS / PBCH block (candidate) index (within S_window) can be transmitted.

[0213] On the other hand, when LBT scheme A is configured / indicated (or DBTW_off is configured / indicated), the terminal can assume that only a Type 0-PDCCH CSS set corresponding to one of multiple SS / PBCH block (candidate) indexes that have a QCL relationship with a specific SS / PBCH block (candidate) index (within S_window) (e.g., the first SS / PBCH block (candidate) index that has a QCL relationship with a specific SS / PBCH block (candidate) index within S_window) can be transmitted.

[0214] In this disclosure, the first SS / PBCH block (candidate) index having a QCL relationship with a particular SS / PBCH (candidate) index within the S_window may refer to the first QCL_para number (or the first 64) of SS / PBCH blocks within the S_window.

[0215] Furthermore, the PDSCH reception method may change depending on the indicated LBT scheme (or indicated DBTW_on or DBTW_off).

[0216] When LBT scheme B is indicated (or DBTW_on is indicated), the terminal can assume that PDSCH mapping is not available for resources (e.g., RBs) of all SS / PBCH block (candidate) indexes that have a QCL relationship with a specific SS / PBCH block (candidate) index (within S_window).

[0217] For example, a codeword carried on a PDSCH is generated taking into consideration the amount of all resources (e.g., RBs) allocated for PDSCH transmission, but if the resources (e.g., RBs) allocated for PDSCH transmission overlap with resources (e.g., RBs) of an SS / PBCH (candidate) having a QCL relationship with a specific SS / PBCH block (candidate), the PDSCH may not be mapped to the overlapping resources (e.g., RBs). Here, the specific SS / PBCH (candidate) index may include an SS / PBCH block (candidate) index that the base station has notified the terminal to be actually transmitted.

[0218] As yet another example, when LBT scheme A is indicated (or DBTW_off is indicated), the terminal can assume that PDSCH mapping is not available only to one of multiple SS / PBCH block (candidate) indexes that have a QCL relationship with a specific SS / PBCH block (candidate) index (within S_window) (e.g., the resource (e.g., RB) of the first SS / PBCH block (candidate) index that has a QCL relationship with a specific SS / PBCH block (candidate) index within S_window), but that PDSCH mapping is available to the resources (e.g., RBs) of the remaining SS / PBCH block (candidate) indexes that have a QCL relationship.

[0219] This allows PDSCH mapping to exist in all resources (e.g., RBs) allocated for PDSCH when the resources (e.g., RBs) of the remaining SS / PBCH block (candidate) indexes in a QCL relationship overlap with the PDSCH resources (e.g., RBs).

[0220] In addition, the PDSCH time domain resource allocation (TDRA) method may change depending on the LBT scheme (or the indicated DBTW_on or DBTW_off). Before a specific TDRA table is configured by the base station, the terminal may be scheduled for PDSCH according to a default TDRA table. Here, the default TDRA table may be defined differently depending on whether or not a shared spectrum access operation is performed.

[0221] For example, when LBT scheme B is indicated (or DBTW_on is indicated), the terminal may be scheduled for PDSCH according to the default TDRA table defined for shared spectrum connection operation before a specific TDRA table is configured from the base station.

[0222] As yet another example, when LBT scheme A is indicated (or DBTW_off is indicated), the terminal may be scheduled for PDSCH according to a default TDRA table defined for operation other than a shared spectrum connection before a specific TDRA table is configured by the base station.

[0223] Each TDRA table may include multiple columns, and each column may include at least one of: (1) DMRS symbol index within a slot; (2) PDSCH mapping type; (3) PDCCH-to-PDSCH slot offset; (4) PDSCH starting symbol index within a slot; and (5) number of PDSCH symbols.

[0224] Example 2

[0225] To indicate (or signal) the application of DBTW_on or DBTW_off, separate synchronization rasters may be defined along which SS / PBCH blocks may be transmitted.

[0226] For example, when a synchronization raster set #1 (e.g., a set that is DBTW_off or a set associated with a licensed band) and a synchronization raster set #2 (e.g., a set that is DBTW_on or a set associated with an unlicensed band) may be defined in FR3 (or FR2-2), when an SS / PBCH block based on a synchronization raster belonging to synchronization raster set #1 is found, the terminal can recognize this as the same SS / PBCH block as FR2.

[0227] As yet another example, if an SS / PBCH block based on a synchronization raster belonging to synchronization raster set #2 is found, the terminal can recognize this as an SS / PBCH block that has been enhanced in FR3 (or FR2-2) (as opposed to FR2 operation).

[0228] In this case, the RB offset value between the SS / PBCH block and CORESET#0 may be different for each synchronization raster set. For convenience of explanation of the present disclosure, when an index set capable of indicating an RB offset value between the SS / PBCH block and CORESET#0 is named SET_RB, when a specific value of the indexes belonging to SET_RB is indicated, the terminal may estimate the position of CORESET#0 using the RB offset value starting from the position of the SS / PBCH block.

[0229] That is, a SET_RB linked to an SS / PBCH block based on a synchronization raster belonging to synchronization raster set #1 and a SET_RB linked to an SS / PBCH block based on a synchronization raster belonging to synchronization raster set #2 may be configured separately.

[0230] Example 3

[0231] When the SS / PBCH block in the initial access phase is composed of only the 120 kHz SCS and the SS / PBCH block of the 480 kHz SCS or 960 kHz SCS is not used for initial access but for ANR (automatic neighbor relation) purposes, the PBCH in the SS / PBCH block of the 480 kHz SCS or 960 kHz SCS may carry information regarding the position of the SS / PBCH block of the 120 kHz SCS and / or CORESET index 0 (and type0-PDCCH common search space set) and / or global cell ID related information (to provide SIB1 information within the same cell).

[0232] Specifically, since the SS / PBCH block of the 480 / 960 kHz SCS is not used for initial connection, it may be transmitted with a center frequency that is not in the synchronization raster. Therefore, the base station needs to provide CORESET#0 frequency resource information even if it uses the SS / PBCH block that is not in the synchronization raster.

[0233] In unlicensed bands, different operators may coexist, and even the same operator may have an unplanned deployment environment, so the (physical) cell IDs used between cells in the same band may be identical.

[0234] In order to prevent possible confusion in the terminal caused by this, the base station can transmit information regarding CORESET#0 and type0-PDCCH CSS set for higher layer signaling (e.g., SIB1) including operator ID and / or PLMN ID and / or global cell ID information to the terminal (even for SS / PBCH blocks that are not transmitted in the synchronization raster).

[0235] As an example, it can be assumed that a measurement report for the purpose of "reportCGI" is set in the measurement configuration. SS / PBCH block transmissions for such purposes can be collectively referred to as ANR purposes.

[0236] Therefore, the PBCH payload in an SS / PBCH block with a 480 / 960 kHz SCS may transmit frequency axis offset information (e.g., the number of REs and / or the number of RBs and / or synchronization raster index information) between the SS / PBCH block and an SS / PBCH block with a 120 kHz SCS, and the offset information may be based on the 120 kHz SCS (or the SCS of the SS / PBCH block including the PBCH payload).

[0237] For example, the RE may be based on the SCS of the SS / PBCH block containing the PBCH payload, and the RB may be based on the 120 kHz SCS, and the terminal may use this information to receive the SIB1 PDCCH / PDSCH according to the PBCH information in the SS / PBCH block with the 120 kHz SCS.

[0238] The terminal can report the received SIB1 information (e.g., ANR-related information such as NCGI(s) (NR Cell Global Identifier) / ECGI(s) (extended CGI), TAC(s) (tracking area code), RANAC(s) (RAN-based Notification Area Code), PLMN ID(s) (Public Land Mobile Network), etc.) to the base station.

[0239] At a frequency resource position for a 120 kHz SCS SS / PBCH block, physical cell ID information (or information of a part (bits) of the ID) transmitted in the PSS / SSS may be transmitted in the PBCH payload in the 480 / 960 kHz SCS SS / PBCH block. This is to allow the base station to notify the SS / PBCH block to be received (or transmitted by the same base station as the base station transmitting the 480 / 960 kHz SCS SS / PBCH block) among the multiple SS / PBCH blocks when multiple SS / PBCH blocks are found at the frequency resource position.

[0240] The terminal can receive SIB1 information linked to the SS / PBCH block corresponding to the indicated physical cell ID information at a frequency resource location where the SS / PBCH block of the 120 kHz SCS can be transmitted, and can report the acquired SIB1 information to the serving cell.

[0241] Alternatively, resource information of the 120 kHz SCS-based CORESET index 0 (and type0-PDCCH CSS set) may be directly transmitted by the PBCH payload in the SS / PBCH block of the 480 / 960 kHz SCS, which allows the terminal to receive the SIB1 PDCCH / PDSCH without receiving the SS / PBCH block of the 120 kHz SCS.

[0242] In this case, the information of the 120 kHz SCS-based CORESET index 0 may include the RE / RB offset between the 480 / 960 kHz SCS SS / PBCH block and the CORESET (as another example, this may be based on the SCS of the 120 kHz SCS or the SS / PBCH block including the PBCH payload, and the reference SCS may change depending on the RE / RB), the time / frequency domain occupied by the CORESET (e.g., X RB(s), Y symbols), etc.

[0243] Furthermore, the 120 kHz SCS-based type 0-PDCCH CSS set information is information regarding SIB1 PDCCH monitoring occasions, and may include the number of occasions per slot, symbol position information of the occasions within a slot, and the like.

[0244] SIB1 information (e.g., ANR-related information such as NCGI(s) (NR Cell Global Identifier) / ECGI(s) (extended CGI), TAC(s) (tracking area code), RANAC(s) (RAN-based Notification Area Code), PLMN ID(s) (Public Land Mobile Network), etc.) obtained based on the resource information of the CORESET index 0 (and type0-PDCCH CSS set) may be reported to the base station.

[0245] Specifically, the SS / PBCH block position and / or CORESET index 0 (and / or type0-PDCCH common search space set) information provided on the PBCH within a 480 and / or 960 kHz SCS based SS / PBCH block may include information regarding a 120 kHz SCS based SS / PBCH block and / or CORESET index 0 (and / or type0-PDCCH common search space set) (even if there is no indicator in the PBCH payload indicating a separate SCS value).

[0246] As yet another example, ANR-related information (e.g., NCGI(s) / ECGI(s), TAC(s), RANAC(s), PLMN ID(s), etc.) may be directly carried in the PBCH payload in the SS / PBCH block of the 480 / 960 kHz SCS. For example, the entire NCGI information (or a part of it (e.g., LSB X bits)) may be included in the PBCH payload in the SS / PBCH block of the 480 / 960 kHz SCS, and the terminal receiving the information can report the NCGI-related information to the serving base station (which has requested the ANR).

[0247] Example 4

[0248] When 480 kHz (and / or 960 kHz) is applied as the SCS of an SS / PBCH block in addition to 120 kHz (and / or 240 kHz) in the FR3 (or FR2-2) band, the number / combination of (candidate) SS / PBCH blocks and / or the DBTW_on / off setting method may be set for each SCS.

[0249] That is, the number / combination of (candidate) SS / PBCH blocks corresponding to SS / PBCH blocks may be set individually for each SCS. Also, application of DBTW_on or DBTW_off corresponding to SS / PBCH blocks may be set individually for each SCS.

[0250] Specifically, if no explicit signaling for the application of DBTW_on or DBTW_off is configured, the terminal may assume that DBTW_on applies to 120 kHz (and / or 240 kHz) SCS SS / PBCH blocks and that DBTW_off applies to 480 kHz and / or 960 kHz SCS SS / PBCH blocks.

[0251] In this case, the SS / PBCH blocks in the initial access stage are configured with only 120 kHz SCS (and / or 240 kHz SCS), and the SS / PBCH blocks with 480 kHz SCS or 960 kHz SCS do not need to be used for initial access purposes.

[0252] Example 5

[0253] In one cell, SS / PBCH blocks having individual numerologies may be configured (by BWP or within the same BWP). For example, the initial BWP#0 may be configured for SS / PBCH block reception with 120 kHz SCS, and the BWP#1 in the same cell may be configured for SS / PBCH block reception with 480 kHz SCS (or 960 kHz SCS).

[0254] For example, when switching to BWP#0 while performing RRM measurements, etc. on a 480 kHz SCS (or 960 kHz SCS) SS / PBCH block basis in BWP#1 (set for performing RRM measurements, etc.), a QCL relationship may be set between the 120 kHz SCS SS / PBCH block index and the 480 kHz SCS (or 960 kHz SCS) SS / PBCH block index so that the terminal can continue performing operations such as RRM measurements.

[0255] That is, it may be set that SS / PBCH block (candidate) index n of 120 kHz SCS and SS / PBCH block (candidate) index m of 480 kHz SCS (or 960 kHz SCS) have a QCL relationship with each other, or a rule may be defined so that a QCL relationship can be assumed between the same (candidate) indexes.

[0256] The above-mentioned method may be extended to other operations such as radio link monitoring, candidate beam detection, beam failure detection, beam management, etc., in addition to the RRM measurement operation. Also, the method may be extended to neighbor cell measurement in addition to the serving cell (PCell and / or PSCell and / or SCell).

[0257] Alternatively, when SS / PBCH blocks in the initial connection phase are limited to 120 kHz SCS due to signaling complexity considerations, a rule may be defined that SS / PBCH blocks based on 480 kHz SCS or 960 kHz SCS can be configured only for an SCell (not a PCell or a PSCell).

[0258] In the following, a method of performing SSB-to-RO mapping based on SS / PBCH blocks when a PRACH opportunity is set in BWP#1, which is not the first BWP, will be disclosed.

[0259] When it is assumed that multiple SCSs are applied in the initial access phase of a terminal, the number of SCS values ​​applied to an SS / PBCH block in the initial access phase may be minimized taking into account implementation complexity.

[0260] For example, the SS / PBCH block in the initial connection phase may be limited to 120 kHz SCS. As yet another example, after the initial connection, another dedicated BWP (e.g., BWP#1) that is not the minimum BWP (depending on whether the terminal supports it) may be set to 480 kHz SCS (or 960 kHz SCS).

[0261] When SSB-to-RO mapping is performed for a PRACH configured in a dedicated BWP#2 (or BWP#1 in which a 480 kHz SCS (or 960 kHz SCS) SS / PBCH block is configured), the SSB-to-RO mapping may be performed based on a 120 kHz SCS SS / PBCH block (alt1), based on a 480 kHz SCS (or 960 kHz SCS) SS / PBCH block (alt2), or based on higher layer signaling that configures a reference SCS SS / PBCH block (alt3). Alternatively, SSB-to-RO mapping may be performed based on the SCS of the configured RACH (i.e., based on the SS / PBCH block of the same SCS as the RACH SCS).

[0262] As yet another example, when SSB-to-RO mapping is performed for a PRACH set in BWP#1 in which a 480 kHz SCS (or 960 kHz SCS) SS / PBCH block is set, the SSB-to-RO mapping may be performed based on the SS / PBCH block set in the initial BWP (opt1), based on the SS / PBCH block set in the same (active) BWP (opt2), or based on higher layer signaling set based on either the initial BWP or the same (active) BWP (opt3).

[0263] Example 6

[0264] Example 6 discloses a method in which 64 or more SS / PBCH block (candidate) indexes and / or QCL_para and / or ANR information, etc. are transmitted in the PBCH payload.

[0265] Table 6 below shows the 23-bit configuration of the MIB (24 bits) excluding "BCCH-BCH-Message", and Table 7 shows the PBCH payload. Here, the PBCH payload may be a total of 32 bits, consisting of the MIB (24 bits) plus 8 bits.

[0266] [Table 6]

[0267] [Table 7]

[0268] As an embodiment of the present disclosure, when the SS / PBCH block of the 480 kHz SCS or the 960 kHz SCS is not used for initial access but may be used for ANR, the entire NCGI information (or a part (e.g., LSB X bits) information) is JPEG0007608634000016.jpg13135 may be transmitted based on 29 bits (or a part thereof) excluding the above. JPEG0007608634000017.jpg13137 can be used to obtain the SS / PBCH block index of a neighboring cell when a measurement operation is performed on the neighboring cell.

[0269] When receiving an SS / PBCH block with a 120 kHz SCS (or a 240 kHz SCS), the PBCH payload may be interpreted as shown in Tables 6 and 7 above (or with some bits changed for other purposes). When receiving an SS / PBCH block with a 480 kHz SCS or a 960 kHz SCS, the PBCH payload is interpreted as follows for ANR purposes: JPEG0007608634000018.jpg14109 may be interpreted as 29 bits (or any part thereof) excluding the above.

[0270] As yet another embodiment of the present disclosure, one MIB bit corresponding to "dmrs-TypeA-Position" may be replaced with a purpose of expressing QCL_para or a candidate SS / PBCH block index. In this case, until a separate configuration for the position of the DMRS is received when receiving PDSCH mapping type A, the terminal may assume that the position of the DMRS is the third symbol (or the fourth symbol) when receiving PDSCH mapping type A.

[0271] As yet another embodiment of the present disclosure, a method similar to the embodiment described above (embodiment related to “dmrs-TypeA-Position”) may also be applied to “subCarrierSpacingCommon”, “ssb-SubcarrierOffset”, “pdcch-ConfigSIB1”, “cellBarred”, and / or “intraFreqReselection”.

[0272] For example, one MIB bit corresponding to "subCarrierSpacingCommon" can be replaced with a use for expressing QCL_para or a candidate SS / PBCH block index. In this case, the SCS for the PDSCH scheduled by CORESET#0 and the PDCCH in the CORESET may be defined according to a predetermined rule.

[0273] For example, if there is a 120 kHz SCS or 240 kHz SCS SS / PBCH block, the SCS for the PDSCH may be defined as a 120 kHz SCS, if there is a 480 kHz SCS SS / PBCH block, the SCS for the PDSCH may be defined as a 480 kHz SCS, and if there is a 960 kHz SCS SS / PBCH block, the SCS for the PDSCH may be defined as a 960 kHz SCS.

[0274] As another example, the 4 MIB bits (or some of them) corresponding to "ssb-SubcarrierOffset" can be replaced with a use for expressing QCL_para or a candidate SS / PBCH block index. In this case, the "ssb-SubcarrierOffset" value (e.g., "0000") may be defined according to a predetermined rule.

[0275] As yet another example, the 8 MIB bits (or some of the bits) corresponding to "pdcch-ConfigSIB1" can be replaced with a use for expressing QCL_para or a candidate SS / PBCH block index.

[0276] As another example, one MIB bit corresponding to "cellBarred" or "intraFreqReselection" can be replaced with a use for expressing QCL_para or a candidate SS / PBCH block index. In this case, the terminal can obtain "cellBarred" or "intraFreqReselection" information by higher layer signaling such as SIB1 or other system information after initial connection.

[0277] Example 7

[0278] Example 7 discloses a method for supporting ANR when the SCS of an SS / PBCH block is set to SCS_b and no configuration information is provided for CORESET#0 and type0-PDCCH CSS set of SCS_b (i.e., the same SCS as the SS / PBCH block) in the SS / PBCH block.

[0279] In one embodiment (opt1) of the present disclosure, ANR-related information (e.g., at least one of NCGI(s) / ECGI(s), TAC(s), RANAC(s), or PLMN ID(s)) may be directly transmitted by the PBCH payload. In this case, if the PBCH payload is not large enough to carry all of the information, the ANR-related information may be divided into N (N>1) PBCHs and transmitted.

[0280] As yet another embodiment (opt1-1) of the present disclosure, PBCHs corresponding to N (candidate) SS / PBCH block indexes may be transmitted separately within the same SS / PBCH block period. In this case, a method for grouping N indexes among a total of M (candidate) SS / PBCH block indexes may be defined in advance. For example, when M=64 and N=2, PBCHs corresponding to indexes with mod(M,N)=0 and indexes with mod(M,N)=1 may be transmitted separately.

[0281] As yet another embodiment (opt1-2) of the present disclosure, ANR-related information may be transmitted separately over N SS / PBCH block periods. For example, when N=2, ANR information may be transmitted separately to a PBCH within a k-th SS / PBCH period and a PBCH within a k+1-th SS / PBCH period. In particular, to resolve ambiguity regarding the order in which the N pieces of ANR information are carried, an indicator indicating that the information is 1, 2, ..., N-th may be added to each PBCH.

[0282] For example, when ANR information is divided and transmitted on N PBCHs, each detailed information included in the ANR information can be 1) transmitted every N times, 2) transmitted only a part (e.g., once) of N times, or 3) transmitted divided into N pieces. For example, among the ANR information, 'mcc' and / or 'mnc' can be transmitted on every PBCH, 'cellIdentity' can be transmitted divided into N pieces, and 'cellReservedForOperatorUse' can be transmitted only once.

[0283] As yet another embodiment (opt2a) of the present disclosure, information of SS / PBCH blocks based on SCS_sib1 (eg, 120 kHz) rather than SCS_b (eg, 480 or 960 kHz) may be provided.

[0284] Here, the SCS_sib1-based SS / PBCH block may mean that configuration information for CORESET#0 and type0-PDCCH CSS set may be provided in the SS / PBCH block. That is, the PBCH payload in the SCS_b-based SS / PBCH block may indicate the frequency axis position (e.g., the center frequency of the SCS_sib1-based SS / PBCH block) at which the SCS_sib1-based SS / PBCH block is transmitted and / or the PSS / SSS cell ID (e.g., one of a total of 1008 cell IDs) information transmitted in the SCS_sib1-based SS / PBCH block.

[0285] Upon receiving this, the terminal moves to the corresponding frequency axis resource, searches for an SCS_sib1-based SS / PBCH block containing the same ID information as the PSS / SSS cell ID, receives SIB1 using CORESET#0 and type0-PDCCH CSS set provided in the SCS_sib1-based SS / PBCH block, and then reports the ANR information included in the SIB1 to the serving base station.

[0286] If the terminal moves to the corresponding frequency axis resource and fails to find an SCS_sib1-based SS / PBCH block containing the same ID information as the PSS / SSS cell ID within a certain period of time, or if the terminal finds the SS / PBCH block but does not actually provide configuration information for CORESET#0 and type0-PDCCH CSS set, the terminal can report "no SIB1" to the serving base station.

[0287] As yet another embodiment (opt2b) of the present disclosure, information regarding SCS_sib1 (eg, 120 kHz) based CORESET#0 and type0-PDCCH CSS set may be provided in an SCS_b (eg, 480 or 960 kHz) based SS / PBCH block.

[0288] Specifically, information regarding CORESET#0 and the type0-PDCCH CSS set may be signaled similarly to FR2 operation, and the frequency axis location of the SCS_sib1-based SS / PBCH block required for RB location determination of CORESET#0 may be signaled separately by the PBCH payload.

[0289] Alternatively, the frequency axis position of the SCS_sib1-based SS / PBCH block required for determining the RB position of CORESET#0 may be signaled similarly to FR2 operation, and information regarding CORESET#0 and the type0-PDCCH CSS set may be individually signaled by the PBCH payload. Also, after receiving the SCS_b-based SS / PBCH block, the beam connection relationship between the SCS_b-based SS / PBCH block and the SCS_sib1-based CORESET#0 may be set upon receiving the SCS_sib1-based CORESET#0 and the type0-PDCCH CSS set. This may reduce power consumption of the terminal upon receiving the SIB1 PDCCH on CORESET#0.

[0290] As an example, if the (candidate) SS / PBCH block index on the SCS_b-based SS / PBCH block and the (candidate) SS / PBCH block index corresponding to the SCS_sib1-based CORESET#0 are the same, the terminal can assume that the same beam reception is possible. That is, if the (candidate) SS / PBCH block index #a on the SCS_b-based SS / PBCH block has the best beam quality, the terminal can preferentially receive the CORESET#0 linked to the SCS_sib1-based (candidate) SS / PBCH block index #a. This can save the terminal time to search for the best beam when monitoring the SCS_sib1-based PDCCH.

[0291] As yet another example, the link relationship between the (candidate) SS / PBCH block index on the SCS_b-based SS / PBCH block and the (candidate) SS / PBCH block index corresponding to the SCS_sib1-based CORESET#0 may be signaled separately by the SCS_b-based PBCH.

[0292] Example 8

[0293] Example 8 relates to a method of interpreting DCI scrambled with SI-RNTI depending on whether the band is licensed or unlicensed and / or whether CAP is performed or not.

[0294] The size of the reserved bits included in the CRC-scrambled DCI in the SI-RNTI may vary depending on whether shared spectrum channel access is applied.

[0295] For example, the reserved bits in the DCI for a cell to which a shared spectrum channel connection is applied (e.g., a cell on an unlicensed band or a cell to which CAP is applied) may be 17 bits, and the reserved bits in the DCI for other cells may be 15 bits. In this case, in a cell to which a shared spectrum channel connection is applied, two bits further included in the DCI may be used to indicate a channel access (or CAP) type and / or a CP extension length when another RNTI (e.g., C-RNTI) is scrambled for the same DCI format.

[0296] That is, the total payload size of the DCI may differ depending on whether the cell is a cell to which the shared spectrum channel connection is applied. Therefore, if there is no information on whether the cell is a cell to which the shared spectrum channel connection is applied before receiving DCI CRC-scrambled by the SI-RNTI (or before receiving system information), ambiguity may occur regarding the payload size of the DCI.

[0297] In a basic wireless communication system, whether a cell is a cell to which a shared spectrum channel connection is applied is determined according to the location of the frequency band, and a terminal connecting to a cell can determine whether the cell is a cell to which a shared spectrum channel connection is applied without separate information. For example, when connecting to a cell on a frequency band corresponding to 5150-5925 MHz and / or 5925-7125 MHz, the terminal can recognize that the cell is a cell to which a shared spectrum channel connection is applied.

[0298] However, in the FR3 (or FR2-2) band, even specific frequency bands may be licensed or unlicensed depending on the region, and even in unlicensed bands, CAP may or may not be applied depending on regulations.

[0299] Therefore, Example 8 discloses a method for solving the problem of ambiguity regarding the payload size of DCI CRC-scrambled by SI-RNTI, which may occur in the FR3 (or FR2-2) band.

[0300] For example, the state corresponding to "ChannelAccess-CPext" may be configured as four in total, and the corresponding field may be configured as two bits. However, instructions for "type 2A CAP" (i.e., CAP in which transmission is permitted if the channel is idle for a certain period of time without random backoff) by DCI format 0_0 or 1_0 in the FR3 (or FR2-2) band may not be permitted. Thus, the state corresponding to "ChannelAccess-CPext" may be configured as two, and the corresponding field may be configured as one bit.

[0301] As an example, whether or not two bits are added to the payload of the DCI CRC-scrambled by the SI-RNTI may be determined depending on whether the synchronization raster is individually defined and / or whether the cell belongs to a licensed band or an unlicensed band by the PBCH payload (i.e., as in Example 1), and / or whether the CAP is applied, whether the licensed band operation is performed, and / or whether the LBT scheme A or B is set (i.e., as in Example 9). In this case, the two bits may be used to indicate a channel access (or CAP) type and / or a CP extension length.

[0302] The following examples illustrate (or assume) the case where the PBCH payload indicates whether the CAP applies or not, but the following examples may also be applied when the synchronization raster is defined individually, when the PBCH payload identifies whether the cell belongs to a licensed or unlicensed band, and / or when it indicates whether the CAP applies or not, and / or when it indicates whether licensed band operation is performed, and / or when it indicates LBT scheme A or B.

[0303] In the description of the present disclosure, a CAP indication by the PBCH payload may mean an explicit indication, or, as in Example 9, may mean that CAP application (or LBT scheme A or B) is implicitly indicated by QCL_para.

[0304] As an example, for a cell for which CAP application is instructed by the PBCH payload, the terminal may receive DCI on the assumption that the reserved bits in the DCI are 17 bits (16 bits when the "ChannelAccess-CPext" field is configured with 1 bit). In addition, the above example may be extended to DCI format 1_0 and / or DCI format 0_0 CRC scrambled by an RNTI other than SI-RNTI.

[0305] For example, when the DCI is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and is not associated with a random access process based on the PDCCH order (e.g., DCI format 1_0), for a cell for which CAP application is indicated by the PBCH payload, the terminal can receive the DCI by assuming that the "ChannelAccess-CPext" field in the DCI is configured with 2 bits (1 bit if the "ChannelAccess-CPext" field is configured with 1 bit).

[0306] Conversely, for a cell for which the PBCH payload indicates that CAP does not apply, the terminal can receive the DCI assuming that the "ChannelAccess-CPext" field in the DCI is 0 bit.

[0307] As yet another example, when the DCI is CRC-scrambled with the C-RNTI, CS-RNTI, or MCS-C-RNTI and is associated with a random access process according to a PDCCH order (e.g., DCI format 1_0), for a cell for which CAP application is indicated by the PBCH payload, the terminal can receive the DCI assuming that the reserved bits in the DCI are composed of 12 bits (11 bits if the 'ChannelAccess-CPext' field is composed of 1 bit).

[0308] Conversely, for a cell for which the PBCH payload indicates that the CAP does not apply, the terminal may receive the DCI on the assumption that the reserved bits in the DCI consist of 10 bits.

[0309] For example, for a cell in which the DCI is CRC scrambled by the P-RNTI (e.g., DCI format 1_0) and CAP application is indicated by the PBCH payload, the terminal can receive the DCI assuming that the reserved bits in the DCI are composed of 8 bits (7 bits when the "ChannelAccess-CPext" field is composed of 1 bit).

[0310] Conversely, for a cell for which the PBCH payload indicates that the CAP does not apply, the terminal may receive the DCI on the assumption that the reserved bits in the DCI consist of 6 bits.

[0311] For a cell in which DCI is CRC scrambled by RA-RNTI or MsgB-RNTI (e.g., DCI format 1_0) and CAP application is indicated by the PBCH payload, the terminal can receive the DCI assuming that the reserved bits in the DCI are composed of (18-A) bits (17-A bits when the "ChannelAccess-CPext" field is composed of 1 bit).

[0312] Conversely, for a cell in which the PBCH payload indicates that CAP does not apply, the terminal can receive the DCI assuming that the reserved bits in the DCI consist of (16-A) bits.

[0313] For a cell in which DCI is CRC scrambled with TC-RNTI and CAP application is indicated by the PBCH payload, the terminal can receive the DCI by assuming that the "ChannelAccess-CPext field" in the DCI is composed of 2 bits (1 bit if the "ChannelAccess-CPext" field is composed of 1 bit).

[0314] Conversely, for a cell for which the PBCH payload indicates that CAP does not apply, the terminal can receive the DCI by assuming that the "ChannelAccess-CPext" field in the DCI is 0 bits.

[0315] For a cell for which CAP application is indicated by the PBCH payload, the terminal can receive the DCI by assuming that the “ChannelAccess-CPext” field in the DCI (e.g., DCI format 0_0) is composed of 2 bits (1 bit if the “ChannelAccess-CPext field” is composed of 1 bit).

[0316] Conversely, for a cell for which the PBCH payload indicates that CAP does not apply, the terminal can receive the DCI assuming that the "ChannelAccess-CPext" field in the DCI is 0 bit.

[0317] As another example, when whether the cell belongs to a licensed or unlicensed band and / or whether CAP applies is not defined by a specific synchronization raster or is not set by the PBCH payload, or when the terminal does not know whether it operates in a licensed band and / or whether LBT scheme A or B is used, as in Example 9, 2 bits (or 1 bit if the "ChannelAccess-CPext" field is configured with 1 bit) are always added to the DCI size, and whether the 2 bits are used for CAP purposes (i.e., for indicating the channel connection type and / or the length of the CP extension) or ignored may be based on the setting of whether or not CAP is applied using the SIB.

[0318] The above-described embodiments may also be applied in cases where whether the cell belongs to a licensed or unlicensed band is not defined by a specific synchronization raster or is not set by the PBCH payload as in embodiment 1, but whether the CAP applies is indicated / set by the SIB.

[0319] In the description of this disclosure, the fact that the SIB indicates that the CAP is applied can mean an explicit indication, or it can mean that the application of the CAP (or LBT scheme A or B) is implicitly indicated by QCL_para, as in Example 9.

[0320] As one example, if the PBCH payload or synchronization raster does not indicate whether CAP applies, the terminal can receive the DCI assuming that the reserved bits in the DCI consist of 17 bits (or 16 bits if the "ChannelAccess-CPext" field consists of 1 bit).

[0321] In addition, when DCI format 1_0 scrambled with another RNTI (e.g., C-RNTI) rather than SI-RNTI is transmitted, if it is signaled in the SIB that CAP is applied, the terminal can receive the DCI by assuming that the (last) 2 bits (or 1 bit if the "ChannelAccess-CPext" field consists of 1 bit) are the "ChannelAccess-CPext" field.

[0322] On the other hand, if the SIB signals that CAP is not applied when DCI format 1_0 scrambled with another RNTI (e.g., C-RNTI) rather than SI-RNTI is transmitted, the terminal can ignore the (last) two bits (or 1 bit if the "ChannelAccess-CPext" field consists of 1 bit).

[0323] Specifically, the following method may be applied to other RNTIs (other than the SI-RNTI) scrambled into the DCI format 1_0 and / or to DCI format 0_0.

[0324] For example, when DCI is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI and is not associated with a random access process by PDCCH order (e.g., DCI format 1_0), if it is signaled in the SIB that CAP is applied, the terminal can receive the DCI by assuming that the (last) 2 bits (or 1 bit if the 'ChannelAccess-CPext' field consists of 1 bit) are 'ChannelAccess-CPext'.

[0325] On the other hand, if it is signaled in the SIB that CAP does not apply, the terminal may ignore these (last) two bits (or the 1 bit, if the "ChannelAccess-CPext" field consists of 1 bit).

[0326] As yet another example, when a DCI is CRC scrambled by a C-RNTI, CS-RNTI, or MCS-C-RNTI and is associated with a random access procedure by PDCCH order (e.g., DCI format 1_0), if the PBCH payload or synchronization raster does not indicate whether CAP applies, the terminal may receive the DCI assuming that the reserved bits in the DCI are 12 bits (or 11 bits if the "ChannelAccess-CPext" field is 1 bit).

[0327] As yet another example, when a DCI is CRC scrambled by a P-RNTI (e.g., DCI format 1_0), if the PBCH payload or synchronization raster does not indicate whether CAP is applied or not, the terminal may receive the DCI assuming that the reserved bits in the DCI consist of 8 bits (or 7 bits if the "ChannelAccess-CPext" field consists of 1 bit).

[0328] As yet another example, when a DCI is CRC scrambled by the RA-RNTI or MsgB-RNTI (e.g., DCI format 1_0), if the PBCH payload or synchronization raster does not indicate whether CAP is applied or not, the terminal can receive the DCI assuming that the reserved bits in the DCI are composed of 18-A bits (or 17-A bits if the "ChannelAccess-CPext" field is composed of 1 bit).

[0329] As yet another example, when the DCI is CRC scrambled by the TC-RNTI (e.g., DCI format 1_0), if the SIB signals that CAP is applied, the terminal can receive the DCI by assuming that the (last) two bits (or one bit, if the "ChannelAccess-CPext" field consists of one bit) are the "ChannelAccess-CPext" field.

[0330] On the other hand, if it is signaled by the SIB that CAP does not apply, the terminal may ignore these (last) two bits (or the 1 bit, if the "ChannelAccess-CPext" field consists of 1 bit).

[0331] If the SIB signals that CAP applies, the terminal can receive DCI format 0_0 assuming that the (last) two bits (or one bit, if the "ChannelAccess-CPext" field consists of one bit) are the "ChannelAccess-CPext" field.

[0332] On the other hand, if it is signaled by the SIB that CAP does not apply, the terminal may ignore these (last) two bits (or the 1 bit, if the "ChannelAccess-CPext" field consists of 1 bit).

[0333] Example 8 may be equally applied to the FR3 (or FR2-2) band, as well as to frequency bands in which licensed and unlicensed bands (or whether or not CAP is applied) differ from region to region (for example, the 6 GHz band).

[0334] Example 9

[0335] Example 9 relates to a method for indicating whether licensed band operation or unlicensed band operation is performed based on a set QCL_para value and / or a method for indicating whether LBT scheme A or LBT scheme B is performed based on a set QCL_para value.

[0336] Here, licensed band operation may refer to operation without shared spectrum channel access, and unlicensed band operation may refer to operation with shared spectrum channel access.

[0337] LBT scheme A refers to an LBT scheme in which transmission is permitted without determining the channel state (e.g., idle / busy state), and LBT scheme B refers to an LBT scheme in which transmission is permitted only when the channel is determined to be idle.

[0338] When transmitting an SS / PBCH block, the DBTW may be enabled / disabled, but if the maximum value of the SS / PBCH block (candidate) index is 64 (the same as FR2), the licensed or unlicensed band indication and / or LBT scheme A or B indication in the SIB may differ depending on whether the QCL_para value acquired by the terminal through the PBCH payload during the initial connection process is 64 or less than 64.

[0339] For example, when the QCL_para value is set to 64, the terminal's SS / PBCH block reception and a series of initial connection procedures are the same as FR2 operations, so it is not possible to determine from the QCL_para value alone whether the cell belongs to a licensed or unlicensed band and / or whether it uses LBT scheme A or LBT scheme B. Therefore, when the QCL_para value is set to 64, the base station can use the SIB to set whether the cell belongs to a licensed or unlicensed band and / or whether it uses LBT scheme A or LBT scheme B. Alternatively, the terminal can expect that the SIB will set whether the cell belongs to a licensed or unlicensed band and / or whether it uses LBT scheme A or B.

[0340] On the other hand, when the QCL_para value is set to less than 64, the terminal can recognize that the DBTW is enabled, and the terminal can know whether the cell belongs to an unlicensed band and whether the LBT scheme B is set without any additional signaling. Therefore, when the QCL_para value is set to less than 64, the base station does not need to set whether the cell belongs to a licensed band or an unlicensed band and / or whether the LBT scheme is A or B by the SIB. Alternatively, the terminal can recognize that the cell belongs to an unlicensed band and that the LBT scheme B is set, even if the SIB does not set whether the cell belongs to a licensed band or an unlicensed band and / or whether the LBT scheme is A or B.

[0341] As yet another embodiment, in the case where DBTW may be enabled / disabled in SS / PBCH block transmission, if the maximum value of SS / PBCH block (candidate) index is 64 (same as FR2), the terminal can determine the licensed or unlicensed band and / or LBT scheme A or B state as a default, even if the SIB does not indicate a licensed or unlicensed band and / or an LBT scheme A or B, depending on whether the QCL_para value acquired by the terminal through the PBCH payload in the initial access process is 64 or less than 64. For example, if the QCL_para value is set to less than 64, the terminal can recognize that DBTW is activated, and therefore the terminal can know that it is an unlicensed band and LBT scheme B without another SIB setting.

[0342] On the other hand, when the QCL_para value is set to 64, if the base station does not set LBT scheme A or B by the SIB, the terminal can determine that the LBT scheme is LBT scheme B (or LBT scheme A) by default. If the terminal is notified of whether the band is licensed or unlicensed in the PBCH payload or in a previous process (for example, by a synchronization raster value), when the QCL_para value is set to 64 and the base station does not set LBT scheme A or B by the SIB, the terminal can determine that the LBT scheme is LBT scheme A if it is notified of the licensed band (by default), and can determine that the LBT scheme is LBT scheme B if it is notified of the unlicensed band.

[0343] The above-mentioned method may be applied not only to the initial access procedure, but also when setting information regarding a serving cell (e.g., 'SCell addition', 'hand-over', etc.) or a neighboring cell (e.g., 'measObjectNR IE' setting, etc.) after the initial access.

[0344] As an example, when "SCell addition" is applied, if the QCL_para value for the serving cell in the FR3 (or FR2-2) band is set to less than 64, the terminal can determine that the cell belongs to an unlicensed band and that LBT scheme B is set without any other higher layer configuration.

[0345] Alternatively, when higher layer signaling is sent (after initial connection), the QCL_para value and / or licensed or unlicensed band indication and / or LBT scheme A or B indication may be set by joint coding using a single RRC parameter (e.g., {QCL_para=64 & licensed band & LBT scheme A, QCL_para=64 & unlicensed band & LBT scheme A, QCL_para=64 & unlicensed band & LBT scheme B, QCL_para<64 & unlicensed band & LBT scheme B}).

[0346] The above method may be applied only to a specific SCS (eg, 120 kHz) on FR3 (or FR2-2), but is not limited thereto.

[0347] Example 10

[0348] When transmitting an SS / PBCH block, DBTW can be enabled / disabled, but when the maximum value of the SS / PBCH block (candidate) index is 64 (same as FR2), if the QCL_para value acquired by the terminal through the PBCH payload in the initial connection process is 64, the terminal's SS / PBCH block reception and a series of initial connection processes can be the same as FR2 operations. Therefore, the code point corresponding to the "QCL_para=64" setting on the PBCH payload can be set to be the same as the MIB decoding in FR2-1. Specifically, there is an advantage that even a terminal without DBTW function can decode the PBCH payload according to the FR2-1 method.

[0349] As an example, as shown in Table 8 below, one MIB bit corresponding to "subCarrierSpacingCommon" may be substituted for the QCL_para value usage. For example, when the QCL_para value is set to 64 or less than 64 (e.g., 32) depending on whether the bit is "0" or "1", signaling as shown in Table 8 may be introduced. That is, the value of QCL_para may be set to 64 in a state indicating "SCS120".

[0350] [Table 8]

[0351] As yet another embodiment, as shown in Table 9 below, one MIB bit corresponding to "subCarrierSpacingCommon" and one LSB bit of "ssb-SubcarrierOffset" may be substituted for the QCL_para value. For example, when the QCL_para value can be set to 64 or less than 64 (e.g., 32, 16, 8) depending on whether the information corresponding to the two bits is "00", "01", "10", or "11", signaling as shown in Table 9 may be introduced. That is, when the state indicates "SCS120" and the one LSB bit of "SubcarrierOffset" is "0", the value of QCL_para may be set to 64. This may be applied when the channel and synchronization raster are designed so that there is no problem with the frequency axis position setting method of CORESE#0 even if the one LSB bit of "SubcarrierOffset" is interpreted as "0".

[0352] [Table 9]

[0353] Fig. 13 is a diagram for explaining a signaling procedure between a network side and a terminal according to the present disclosure. Fig. 13 illustrates an example of signaling between a network side and a terminal (UE) in a situation where the above-mentioned examples of the present disclosure (e.g., one or more combinations of Example 1, Example 2, Example 3, Example 4, Example 5, Example 6, Example 7, Example 8, Example 9, Example 10, or detailed examples thereof) can be applied.

[0354] Here, the terminal / network side is exemplary, and various devices may be applied instead, as described with reference to Fig. 13. Fig. 14 is for convenience of explanation and does not limit the scope of the present disclosure.

[0355] Also, some steps shown in Fig. 13 may be omitted depending on the situation and / or settings, etc. Also, in the operation of the network side / UE in Fig. 13, the above-mentioned uplink transmission / reception operation, etc. may be referred to or used.

[0356] In the following description, the network side may be one base station including multiple TRPs, or one cell including multiple TRPs. Or, the network side may include multiple RRHs (remote radio heads) / RRUs (remote radio units). As an example, an ideal / non-ideal backhaul may be set between TRP 1 and TRP 2 constituting the network side.

[0357] In addition, although the following description is based on multiple TRPs, this may be equally extended and applied to transmissions by multiple panels / cells, and may also be extended and applied to transmissions by multiple RRHs / RRUs, etc.

[0358] In addition, the following description will be based on "TRP", but as described above, "TRP" may be applied instead of expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.), etc. As described above, TRP may be classified according to information (e.g., CORESET index, ID) related to a CORESET group (or CORESET pool).

[0359] As an example, when one terminal is configured to transmit and receive from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal. Such configuration of the CORESET group (or CORESET pool) may be performed by higher layer signaling (e.g., RRC signaling, etc.).

[0360] Also, the base station may be a collective term for an object that transmits and receives data to and from a terminal. For example, the base station may be a concept including one or more TPs (Transmission Points), one or more TRPs (Transmission and Reception Points), etc. Also, the TPs and / or TRPs may include a panel of the base station, a transmission and reception unit, etc.

[0361] The terminal can receive the SS / PBCH from the network side (S105). For example, the network side operating on the FR2-2 band can transmit the SS / PBCH to the terminal with the synchronization raster defined in the corresponding band as the center frequency.

[0362] For example, the operation of the terminal (100 or 200 in FIG. 14) receiving the SS / PBCH from the network side (200 or 100 in FIG. 14) in step S105 described above may be implemented by the apparatus of FIG. 14 described below.

[0363] For example, referring to FIG. 14, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104 to receive the SS / PBCH, and the one or more transceivers 106 can receive the SS / PBCH from the network side.

[0364] The terminal may identify information included in the SS / PBCH block (S110). For example, the terminal may obtain cell timing and / or a QCL relationship between SS / PBCH blocks using the information in the SS / PBCH block.

[0365] As yet another example, the terminal may use information in an SS / PBCH block to determine whether DBTW is applied to the SS / PBCH block, and may obtain ANR information using a 480 kHz or 960 kHz SCS SS / PBCH block.

[0366] For example, the process in step S110 in which the terminal (100 or 200 in FIG. 14) identifies information included in the SS / PBCH block may be implemented by the apparatus in FIG. 14 described below. For example, referring to FIG. 14, one or more processors 102 may control one or more memories 104, etc. to identify information included in the SS / PBCH.

[0367] The terminal can transmit uplink based on the information contained in the SS / PBCH block (S115).

[0368] For example, the terminal may receive SIB1 through PBCH information included in the SS / PBCH block and report the SIB1 information to the network side. As yet another example, the terminal may receive ANR-related information (e.g., NCGI(s) / ECGI(s) / TAC(s) / RANAC(s) / PLMN ID(s), etc.) using the SS / PBCH block and report the NCGI-related information to the network side.

[0369] However, this is only one embodiment, and the terminal can transmit an uplink to the network side based on the above-mentioned embodiments (e.g., one or more combinations of embodiment 1, embodiment 2, embodiment 3, embodiment 4, embodiment 5, embodiment 6, embodiment 7, embodiment 8, embodiment 9, embodiment 10, or detailed examples thereof).

[0370] For example, the operation of the terminal (100 or 200 in FIG. 14) transmitting an uplink in step S115 described above may be implemented by the apparatus in FIG.

[0371] For example, referring to FIG. 14, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc., to transmit an uplink, and the one or more transceivers 106 can transmit a network uplink.

[0372] As described above, the above network side / UE signaling and embodiments (e.g., one or more combinations of Example 1, Example 2, Example 3, Example 4, Example 5, Example 6, Example 7, Example 8, Example 9, Example 10, or detailed examples thereof) may be implemented by the apparatus described with reference to Fig. 14. For example, the network side (e.g., TRP1 / TRP2) may correspond to the first device 100 and the UE may correspond to the second device 200, and vice versa may also be considered in some cases.

[0373] For example, the above-mentioned network side / UE signaling and operations (e.g., one or more combinations of Example 1, Example 2, Example 3, Example 4, Example 5, Example 6, Example 7, Example 8, Example 9, Example 10, or detailed examples thereof) may be processed by one or more processors (e.g., 102, 202) of FIG. 14, and the above-mentioned network side / UE signaling and operations (e.g., one or more combinations of Example 1, Example 2, Example 3, Example 4, Example 5, Example 6, Example 7, Example 8, Example 9, Example 10, or detailed examples thereof) may be stored in a memory (e.g., one or more memories (e.g., 104, 204) of FIG. 14) in the form of instructions / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 102, 202) of FIG. 14.

[0374] Apparatus to which the present disclosure is applicable

[0375] FIG. 14 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0376] Referring to FIG. 14, a first device 100 and a second device 200 can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR).

[0377] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal from the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal from the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be referred to as a Radio Frequency (RF) unit. In the present invention, a wireless device may mean a communication modem / circuit / chip.

[0378] The second wireless device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal from the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal from the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to embody a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be referred to as an RF unit. In the present invention, a wireless device may mean a communication modem / circuit / chip.

[0379] The hardware elements of the wireless devices 100, 200 are described in more detail below. Without being limited thereto, one or more protocol layers may be embodied by one or more processors 102, 202. For example, one or more processors 102, 202 may embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information to one or more transceivers 106, 206 according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure.

[0380] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be embodied in firmware or software in the form of code, instructions and / or collections of instructions.

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

[0382] The one or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flow diagrams of the present disclosure, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present disclosure, from one or more other devices. For example, the one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as described, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed in the present disclosure, via the one or more antennas 108, 208. In the present disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0383] The above-described embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to configure the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in another embodiment, or may be replaced with corresponding configurations or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to configure an embodiment, or may be included as a new claim by amendment after filing.

[0384] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0385] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, and non-transitory computer-readable media on which such software or instructions or the like can be stored and executed on a device or computer. Instructions available for programming a processing system to perform features described in the present disclosure may be stored on / in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in the present disclosure. The storage medium may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but is not limited thereto, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices that are located remotely from the processor. The memory or alternatively the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

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

[0387] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for a terminal to communicate in a wireless communication system, comprising: receiving a system information block (SIB) from a base station; monitoring a physical downlink control channel (PDCCH) for at least one of a first DCI, a second DCI, or a third DCI; Based on the information related to a channel access procedure (CAP) provided via the SIB, the PDCCH is monitored for the first DCI including an indication information indicating a channel access type and a cyclic prefix (CP) extension in a frequency range (FR) 2-2; Based on the fact that the information related to the CAP is not provided via the SIB, the PDCCH is monitored for the second DCI not including the indication information in the FR2-2; A method, wherein the size of the first DCI and the size of the second DCI are the same.

2. The method described in claim 1, wherein the first DCI and the second DCI are CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI and are not related to a random connection process by a PDCCH order.

3. The method described in claim 1, wherein the third DCI is CRC scrambled by the SI-RNTI.

4. The method of claim 1 , wherein the PDCCH is monitored in a common search space (CSS).

5. In a cell to which a shared spectrum channel connection is applied for FR1, a size of reserved bits included in the third DCI is 17 bits; The method of claim 1 , wherein in a cell to which a non-shared spectrum channel connection is applied for FR1, the size of reserved bits included in the third DCI is 15 bits.

6. The method of claim 5 , wherein, based on the second DCI being detected, a bit corresponding to a position of the indication information of the second DCI is reserved.

7. The size of the instruction information included in the first DCI is 2 bits, The method of claim 1 , wherein a reserved bit size included in the second DCI is 2 bits.

8. The method of claim 1, wherein the reserved bit size included in the third DCI in FR2-2 is 17 bits.

9. A terminal that communicates in a wireless communication system, At least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor: receiving a system information block (SIB) from a base station via the at least one transceiver; configured to monitor a physical downlink control channel (PDCCH) for at least one of a first DCI, a second DCI, or a third DCI; Based on the information related to a channel access procedure (CAP) provided via the SIB, the PDCCH is monitored for the first DCI including an indication information indicating a channel access type and a cyclic prefix (CP) extension in a frequency range (FR) 2-2; Based on the fact that the information related to the CAP is not provided via the SIB, the PDCCH is monitored for the second DCI not including the indication information in the FR2-2; A terminal, wherein the size of the first DCI and the size of the second DCI are the same.

10. A base station for communicating in a wireless communication system, At least one transceiver; at least one processor coupled to the at least one transceiver; The at least one processor: Transmitting a system information block (SIB) from a base station via the at least one transceiver; configured to transmit a physical downlink control channel (PDCCH) in response to at least one of a first DCI, a second DCI, or a third DCI via the at least one transceiver; Based on the information related to a channel access procedure (CAP) provided via the SIB, the PDCCH is monitored for the first DCI including an indication information indicating a channel access type and a cyclic prefix (CP) extension in a frequency range (FR) 2-2; Based on the fact that the information related to the CAP is not provided via the SIB, the PDCCH is monitored for the second DCI not including the indication information in the FR2-2; A base station, wherein the size of the first DCI and the size of the second DCI are the same.

Images