Method and apparatus for transmitting / receiving wireless signals in a wireless communication system

Abstract

The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for a wireless communication system, the method comprising the steps of: detecting an SSB in an unlicensed band, the SSB including an index related to a CORESET configuration; determining, based on the index, a RB offset for identifying a frequency location of a CORESET associated with the SSB; and monitoring the CORESET in the unlicensed band based on the RB offset.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems, and more particularly, to a method and apparatus for transmitting and receiving wireless signals. Background Art

[0002] Wireless access systems have been widely deployed to provide various types of communication services, such as voice and data. Typically, wireless access systems are multiple-access systems that support communication for multiple users by sharing available system resources (bandwidth, transmission power, etc.) among them. For example, multiple-access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems. Summary of the Invention

[0003] Technical issues

[0004] Provided are a method and apparatus for efficiently performing wireless signal transmission and reception procedures.

[0005] Those skilled in the art will recognize that the objectives that can be achieved by the present disclosure are not limited to the objectives that have been specifically described above, and the above and other objectives that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] According to a first aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided. The method may include: detecting a synchronization signal block (SSB) in an unlicensed frequency band, wherein the SSB may include an index related to a control resource set (CORESET) configuration; determining a resource block (RB) offset for identifying a frequency location of a CORESET associated with the SSB based on the index; and monitoring the CORESET in the unlicensed frequency band based on the RB offset. Based on a subcarrier spacing (SCS) of the SSB, a relationship between the index and the RB offset may include the relationship in the following table.

[0008]

[0009]

[0010] In the above table, n, a, b, c, and d can be integers.

[0011] According to a second aspect of the present disclosure, a UE for use in a wireless communication system is provided. The UE may include: at least one processor; at least one computer memory, the at least one computer memory being operatively connected to the at least one processor and configured to, when executed, cause the at least one processor to perform operations. The operations may include: detecting an SSB in an unlicensed band, wherein the SSB may include an index related to a core set configuration; determining, based on the index, an RB offset for identifying a frequency location of a core set associated with the SSB; and monitoring the core set in the unlicensed band based on the RB offset. Based on the SCS of the SSB, the relationship between the index and the RB offset may include the relationship in the following table.

[0012] SSB SCS=30kHz SSB SCS=15kHz index RB offset RB offset n a 2a+10 n+1 b 2b+10 n+2 c 2c+10 n+3 d 2d+10

[0013] In the above table, n, a, b, c, and d can be integers.

[0014] According to a third aspect of the present disclosure, an apparatus for a user equipment (UE) is provided. The apparatus may include: at least one processor; at least one computer memory, the at least one computer memory being operatively connected to the at least one processor and configured to, when executed, cause the at least one processor to perform operations. The operations may include: detecting an SSB in an unlicensed band, wherein the SSB may include an index related to a core set configuration; determining, based on the index, an RB offset for identifying a frequency location of a core set associated with the SSB; and monitoring the core set in the unlicensed band based on the RB offset. Based on the SCS of the SSB, the relationship between the index and the RB offset may include the relationship in the following table.

[0015]

[0016]

[0017] In the above table, n, a, b, c, and d can be integers.

[0018] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, the computer-readable storage medium having at least one computer program configured to cause at least one processor to perform operations. The operations may include: detecting an SSB in an unlicensed band, wherein the SSB may include an index related to a core set configuration; determining, based on the index, a RB offset for identifying a frequency location of a core set associated with the SSB; and monitoring the core set in the unlicensed band based on the RB offset. Based on the SCS of the SSB, the relationship between the index and the RB offset may include the relationship in the following table.

[0019] SSB SCS=30kHz SSB SCS=15kHz index RB offset RB offset n a 2a+10 n+1 b 2b+10 n+2 c 2c+10 n+3 d 2d+10

[0020] In the above table, n, a, b, c, and d can be integers.

[0021] Preferably, a, b, c and d may be a, a+1, a+2 and a+3 respectively.

[0022] Preferably, the center frequency of the SSB may correspond to the synchronization grid.

[0023] Preferably, the method and operation may further include detecting a physical downlink control channel PDCCH from the CORESET based on monitoring.

[0024] Preferably, the method and operations may include receiving system information via a physical downlink shared channel (PDSCH) associated with the PDCCH.

[0025] Beneficial effects

[0026] According to the present disclosure, wireless signals can be efficiently transmitted and received in a wireless communication system.

[0027] Those skilled in the art will recognize that the effects that can be achieved using the present disclosure are not limited to those specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the principle of the disclosure.

[0029] Figure 1 Physical channels and a general signal transmission method using the physical channels in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system are illustrated;

[0030] Figure 2 illustrates the radio frame structure;

[0031] Figure 3 A resource grid of time slots is illustrated;

[0032] Figure 4 The mapping of physical channels in time slots is illustrated;

[0033] Figure 5 An exemplary wireless communication system supporting an unlicensed frequency band is illustrated;

[0034] Figure 6 An exemplary method of occupying resources in an unlicensed frequency band is illustrated;

[0035] Figures 7 to 9 illustrates the synchronization signal block (SSB) structure / transmission;

[0036] Figure 10 Illustrate the process of obtaining system information;

[0037] Figure 11 The location of the SSB and control resource set (CORESET) is illustrated;

[0038] Figures 12 to 20 illustrates the configuration of the proposed SSB / CORESET according to the present disclosure;

[0039] Figures 21 to 22 illustrates signal transmission and reception according to the proposals of the present disclosure; and

[0040] Figures 23 to 26 The communication system 1 and wireless device applied to the present disclosure are exemplified. DETAILED DESCRIPTION

[0041] The following technologies may be used for various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolved version of 3GPP LTE / LTE-A.

[0042] As more and more communication devices require greater communication capacity, there has been a need for enhanced mobile broadband communications relative to traditional radio access technologies (RATs). Large-scale machine type communications (MTC), which provide various services to multiple interconnected devices and things at any time and any place, is one of the important issues to be solved by the next generation of communications. The design of communication systems that take into account services that are sensitive to reliability and latency is also under discussion. Therefore, the introduction of next-generation radio access technologies (RATs) for enhanced mobile broadband communications (eMBB), massive MTC (mMTC) and ultra-reliable low-latency communications (URLLC) is under discussion. For convenience, this technology is referred to as NR or new RAT in this disclosure.

[0043] Although the following description is given in the context of a 3GPP communication system (e.g., NR) for clarity, the technical spirit of the present disclosure is not limited to the 3GPP communication system.

[0044] In a wireless access system, a user equipment (UE) receives information from a base station (BS) on the downlink (DL) and transmits information to the BS on the uplink (UL). Information sent and received between the UE and BS includes general data and various types of control information. Depending on the type and purpose of the information sent and received between the BS and UE, various physical channels exist.

[0045] Figure 1 Physical channels in a 3GPP system and a general signal transmission method using the physical channels are illustrated.

[0046] When the UE is powered on or enters a new cell, the UE performs an initial cell search (S101). The initial cell search involves acquiring synchronization with the BS. For this purpose, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). Based on the PSS / SSS, the UE synchronizes its timing to the BS and obtains information such as a cell identifier (ID). In addition, the UE can obtain information broadcast in the cell by receiving the PBCH from the BS. During the initial cell search, the UE can also monitor the DL channel status by receiving a downlink reference signal (DL RS).

[0047] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.

[0048] The UE may perform a random access procedure with the BS (S103 to S106). Specifically, the UE may transmit a preamble on a physical random access channel (PRACH) (S103), and may receive a PDCCH and a random access response (RAR) for the preamble on a PDSCH corresponding to the PDCCH (S104). The UE may then transmit a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S105), and perform a contention resolution procedure including receiving a PDCCH and a PDSCH signal corresponding to the PDCCH (S106).

[0049] After the above process, in the general UL / DL signal transmission process, the UE can receive PDCCH and / or PDSCH from the BS (S107), and send a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH) to the BS (S108). The control information sent by the UE to the BS is generally referred to as uplink control information (UCI). UCI includes hybrid automatic repeat request acknowledgement / negative acknowledgement (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix index (PMI), rank indication (RI), etc. Typically, UCI is sent on PUCCH. However, if control information and data should be sent at the same time, the control information and data can be sent on PUSCH. In addition, upon receiving a request / command from the network, the UE can send UCI on PUSCH aperiodically.

[0050] Figure 2 The radio frame structure is illustrated. In NR, UL and DL transmissions are configured per frame. Each radio frame is 10 ms long and is divided into two half-frames of 5 ms. Each half-frame is divided into five subframes of 1 ms. A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM (A) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols. Symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols).

[0051] Table 1 exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS in the normal CP case.

[0052] [Table 1]

[0053] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 15KHz (u=0) 14 10 1 30KHz (u=1) 14 20 2 60KHz (u=2) 14 40 4 120KHz (u=3) 14 80 8 240KHz (u=4) 14 160 16

[0054] *N slot symb : The number of symbols in a time slot

[0055] *N frame，u slot : The number of time slots in a frame

[0056] *N subframe，u slot : The number of time slots in a subframe

[0057] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS in the extended CP case.

[0058] [Table 2]

[0059] SCS(15*2^u) <![CDATA[N slot syymb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 60KHz (u=2) 12 40 4

[0060] The frame structure is merely an example, and the number of subframes, the number of slots, and the number of symbols in a frame may be changed in various ways.

[0061] In an NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a transmission time interval (TTI)) consisting of the same number of symbols (referred to as a time unit (TU) for convenience) can be configured differently between aggregated cells. Symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols).

[0062] NR can support various parameter sets (or subcarrier spacing (SCS)) to provide various 5G services. For example, NR can support wide areas in conventional cellular bands in 15kHz SCS and support dense urban areas and wide carrier bandwidth with lower latency in 30 / 60kHz SCS. In SCS of 60kHz or above, NR can support bandwidths higher than 24.25GHz to overcome phase noise.

[0063] The NR frequency band can be divided into two frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). The values ​​of the frequency ranges can vary. FR1 and FR2 can be configured as shown in Table 3 below. FR2 can represent millimeter wave (mmW).

[0064] [Table 3]

[0065] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0066] Figure 3 The resource grid during the duration of a time slot is illustrated. A time slot includes multiple symbols in the time domain. For example, a time slot includes 14 symbols in the normal CP case and 12 symbols in the extended CP case. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) can be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be carried out in an active BWP, and only one BWP can be activated for a UE. Each element in the resource grid can be called a resource element (RE), and a complex symbol can be mapped to this resource element.

[0067] Figure 4 The structure of the time slot is illustrated. In the NR system, the frame has a self-contained structure, in which DL control channels, DL or UL data, UL control channels, etc. can all be contained in one time slot. For example, the first N symbols in the time slot (hereinafter, the DL control region) can be used to send DL control channels (e.g., PDCCH), and the last M symbols in the time slot (hereinafter, the UL control region) can be used to send UL control channels (e.g., PUCCH). N and M are integers greater than or equal to 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region can be used for DL ​​data (e.g., PDSCH) transmission or UL data (e.g., PUSCH) transmission. GP provides a time gap for the BS and UE to switch from transmit mode to receive mode or from receive mode to transmit mode. Some symbols at the time of DL to UL switching in a subframe can be configured as GP.

[0068] PDCCH delivers DCI. For example, PDCCH (i.e., DCI) can carry information about the transport format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of high-layer control messages such as RAR sent on PDSCH, transmit power control commands, information about activation / release of configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). Depending on the owner or purpose of the PDCCH, the CRC is masked with various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)). For example, if the PDCCH is for a specific UE, the CRC is masked by the UE ID (e.g., cell RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., system information block (SIB)), the CRC is shielded by the system information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by a random access RNTI (RA-RNTI).

[0069] The PDCCH can be transmitted in a control resource set (CORESET). A CORESET is defined as a set of resource element groups (REGs) with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs of a UE can overlap with each other in the time / frequency domain. The CORESET can be configured through system information (e.g., Master Information Block (MIB)) or through UE-specific higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3 symbols) included in the CORESET can be configured through higher-layer signaling.

[0070] The UE can obtain the DCI sent on the PDCCH by decoding (blind decoding) a set of PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as a PDCCH search space set. The search space set can be a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring the PDCCH candidates in one or more search space sets configured by the MIB or higher-layer signaling. Each CORESET configuration can be associated with one or more search space sets, and each search space set can be associated with one CORESET configuration. A search space set can be determined based on the following parameters.

[0071] -controlResourceSetId: A set of control resources associated with the search space set

[0072] -monitoringSlotPeriodicityAndOffset: PDCCH monitoring period (in time slots) and PDCCH monitoring offset (in time slots)

[0073] -monitoringSymbolsWithinSlot: PDCCH monitoring pattern in the PDCCH monitoring slot (e.g., the first symbol in CORESET)

[0074] -nrofCandidates: number of PDCCH candidates for each AL={1,2,4,8,16} (one of 0,1,2,3,4,5,6 and 8)

[0075] Table 4 shows the characteristics of each search space type.

[0076] [Table 4]

[0077]

[0078] Table 5 exemplarily shows the DCI format transmitted on the PDCCH.

[0079] [Table 5]

[0080]

[0081]

[0082] Figure 5 An exemplary wireless communication system supporting an unlicensed band applicable to the present disclosure is illustrated. In the following description, a cell operating in an authorized band (L-band) is defined as an L-cell, and the carrier of the L-cell is defined as a (DL / UL) LCC. A cell operating in an unlicensed band (U-band) is defined as a U-cell, and the carrier of the U-cell is defined as a (DL / UL) UCC. The carrier / carrier frequency of a cell may refer to the operating frequency (e.g., central frequency) of the cell. A cell / carrier (e.g., CC) is generally referred to as a cell.

[0083] When carrier aggregation is supported, a UE can use multiple aggregated cells / carriers to exchange signals with the base station. When a UE is configured with multiple CCs, one CC can be set as the primary CC (PCC), and the remaining CCs can be set as secondary CCs (SCCs). Specific control information / channels (e.g., CSS PDCCH, PUCCH) can be sent and received only on the PCC. Data can be sent and received on the PCC / SCC. Figure 7(a) shows a case where the UE and the BS exchange signals on both the LCC and the UCC (non-standalone (NSA) mode). In this case, the LCC and the UCC can be set as the PCC and SCC, respectively. When the UE is configured with multiple LCCs, one specific LCC can be set as the PCC, and the remaining LCCs can be set as SCCs. Figure 7 (a) corresponds to LAA of the 3GPP LTE system. Figure 7 (b) shows a case where the UE and the BS exchange signals on one or more UCCs without an LCC (standalone (SA) mode). In this case, one of the UCCs can be set as a PCC, and the remaining UCCs can be set as SCCs. Both the NSA mode and the SA mode can be supported in the U-band of the 3GPP NR system.

[0084] Figure 6 An exemplary method for occupying resources in an unlicensed band is illustrated. Regional regulations for unlicensed bands require that a communication node determine whether other communication nodes are using a channel in the unlicensed band before transmitting a signal. Specifically, a communication node can determine whether other communication nodes are using the channel by performing carrier sensing (CS) before transmitting a signal. When a communication node confirms that no other communication node is sending a signal, this is defined as confirming a clear channel assessment (CCA). In the presence of a CCA threshold predefined by higher-layer signaling (RRC signaling), when a communication node detects energy in the channel that is higher than the CCA threshold, the communication node can determine that the channel is busy; otherwise, the communication node can determine that the channel is idle. For reference, the WiFi standard (e.g., 801.11ac) specifies a CCA threshold of -62dBm for non-WiFi signals and a CCA threshold of -82dBm for WiFi signals. Upon determining that the channel is idle, the communication node can begin signal transmission in the UCell. The above series of operations can be referred to as listen-before-talk (LBT) or a channel access procedure (CAP). LBT and CAP can be used interchangeably.

[0085] In Europe, two LBT operations are defined: frame-based equipment (FBE) and load-based equipment (LBE). In FBE, a fixed frame consists of a channel occupancy time (e.g., 1ms to 10ms) (which is the time period during which a communication node can continue to transmit once it successfully accesses the channel) and an idle period corresponding to at least 5% of the channel occupancy time, and CCA is defined as an operation that observes the channel during a CCA time slot (at least 20us) at the end of the idle period. Communication nodes perform CCA periodically based on the fixed frame. When the channel is not occupied, the communication node transmits during the channel occupancy time, and when the channel is occupied, the communication node postpones transmission and waits until the CCA time slot in the next cycle.

[0086] In LBE, a communication node can set q∈{4,5,…,32} and then perform CCA for one CCA slot. When the channel is unoccupied in the first CCA slot, the communication node can secure a time period of at most (13 / 32)q ms and transmit data during the time period. When the channel is occupied in the first CCA slot, the communication node randomly selects N∈{1,2,…,q}, stores the selected value as the initial value, and then senses the channel state based on the CCA slot. Each time the channel is unoccupied in the CCA slot, the communication node decrements the stored counter value by 1. When the counter value reaches 0, the communication node can secure a time period of at most (13 / 32)q ms and transmit data.

[0087] Implementation Method

[0088] Figure 7 The structure of the SSB is illustrated. The UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on the SSB. The term SSB is used interchangeably with the SS / PBCH block. The SSB consists of four consecutive OFDM symbols, each of which carries PSS, PBCH, SSS / PBCH, or PBCH. Each of the PSS and SSS includes one OFDM symbol and 127 subcarriers, and the PBCH may include 3 OFDM symbols and 576 subcarriers. Polarization coding and quadrature phase shift keying (QPSK) are applied to the PBCH. In each OFDM symbol, the PBCH includes data REs and demodulation reference signal (DMRS) REs. Each RB can have three DMRS REs, and there can be three data REs between the DMRS REs.

[0089] Figure 8 An exemplary SSB transmission is illustrated. Figure 8 , the SSB is periodically transmitted according to the SSB period. The default SSB period assumed by the UE during the initial cell search is defined as 20ms. After cell access, the SSB period can be set to one of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms} by the network (e.g., BS). An SSB burst set is configured at the beginning of the SSB period. The SSB burst set includes a 5ms time window (i.e., half a frame), and the SSB can be transmitted up to L times in the SSB burst set. The maximum number of transmissions L of the SSB can be given according to the frequency band of the carrier as follows. One time slot includes a maximum of two SSBs.

[0090] - For the frequency range up to 3 GHz, L = 4

[0091] - For the frequency range from 3 GHz to 6 GHz, L = 8

[0092] - For the frequency range from 6 GHz to 52.6 GHz, L = 64

[0093] The temporal position of an SSB candidate in an SS burst set may be defined according to the SCS as follows. The temporal position of an SSB candidate is assigned an index (SSB index) from 0 to L-1 in temporal order within the SSB burst set (i.e., half-frame). In this document, the term "candidate SSB" is used interchangeably with the term "SSB candidate."

[0094] - Case A (15kHz SCS): The starting symbol index of the candidate SSB is given as {2, 8}+14*n.

[0095] - For operation without shared spectrum channel access (e.g., Licensed Band (L-band), Licensed Cell (LCell) etc.): For carrier frequencies below 3 GHz, n = 0 or 1. For carrier frequencies between 3 and 6 GHz, n = 0, 1, 2 or 3.

[0096] - For operation with shared spectrum channel access (e.g., Unlicensed Band (U-band), Unlicensed Cell (UCell) etc.): n=0, 1, 2, 3 or 4.

[0097] - Case B (30kHz SCS): The index of the starting symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n. For carrier frequencies below 3 GHz, n = 0. For carrier frequencies between 3 and 6 GHz, n = 0 or 1.

[0098] - Case C (30kHz SCS): The index of the starting symbol of the candidate SSB is given as {2, 8}+14*n.

[0099] -For operation without shared spectrum channel access: (1) Assuming paired spectrum operation, n=0 or 1 for carrier frequencies below 3 GHz, and n=0, 1, 2, or 3 for carrier frequencies within FR1 and above 3 GHz; (2) Assuming unpaired spectrum operation, n=0 or 1 for carrier frequencies below 2.4 GHz, and n=0, 1, 2, or 3 for carrier frequencies within FR1 and above 2.4 GHz.

[0100] - For operation with shared spectrum channel access: n=0, 1, 2, 3, 4, 6, 7, 8 or 9.

[0101] - Case D (120kHz SCS): The index of the starting symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n. For carrier frequencies in FR2, n = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.

[0102] - Case E (240kHz SCS): The indices of the starting symbols of the candidate SSBs are given as {8, 12, 16, 20, 32, 36, 40, 44} + 56*n. For carrier frequencies in FR2, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0103] For operation with shared spectrum channel access, the UE may assume that the transmission of SSBs in a half-frame is within a discovery burst transmission window starting from the first symbol of the first time slot in the half-frame. The duration of the discovery burst transmission for each serving cell may be provided to the UE. If the discovery burst transmission window duration is not provided, the UE may assume that the discovery burst transmission window duration is half a frame. For each serving cell, the UE may assume that the repetition period of the discovery burst transmission window is the same as the repetition period of the half-frame used for SSB reception. The UE may assume that among the SSBs of the serving cell, within the same discovery burst transmission window or on different discovery burst transmission windows, the same value (N PBCH DM-RS mod N QCL SSB ) is quasi-collocated (QCLed), where N PBCH DM-RS represents the index of the DM-RS sequence of PBCH, and N can be obtained as follows QCL SSB :(i) N can be provided by ssbPositionQCL-Relationship QCL SSB , or (ii) if ssbPositionQCL-Relationship is not provided, N can be obtained from the MIB in the SSB according to Table 6 QCL SSB .

[0104] [Table 6]

[0105]

[0106] ssbSubcarrierSpacingCommon represents the SCS of RMSI only in the case of "no shared spectrum operation". The UE can assume that the number of SSBs sent on the serving cell within the discovery burst transmission window is not greater than N QCLSSB UE can be based on (N PBCH DM-RS mod N QCL SSB ) or (i ～ mod N QCL SSB ) to determine the index of SSB, where i ～ Represents the index of the candidate SSB. Therefore, one or more candidate SSBs can correspond to one SSB index. Candidate SSBs corresponding to the same SSB index can be quasi-co-located.

[0107] Figure 9 An example of SS / PBCH block candidate positions is illustrated. Specifically, Figure 9 Shown where N QCL SSB is set to 4 and ssb-PositionsInBurst is set to "10100000". In this case, only SSB with SSB (=SS / PBCH block) index #0 / #2 can be transmitted. ssb-PositionsInBurst and N QCL SSB Can be used to provide a rate matching pattern within the Discovery Reference Signal (DRS) transmission window (or Discovery Burst transmission window). For example, the UE can perform rate matching on all SSB candidate position indices that are quasi-co-located with the actual transmitted SSB index provided by ssb-PositionsInBurst. Figure 9 In the UE-SMS protocol, the UE may perform rate matching on the time / frequency resources of SSB candidate position indices 0 / 2 / 4 / 6 / 8 / 10 / 12 / 14 / 16 / 18. Thereafter, when receiving a PDSCH scheduled by a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, RA-RNTI, MsbB-RNTI, P-RNTI, TC-RNTI, etc., or a PDSCH with SPS (or with a CRC scrambled by SI-RNTI if the system information indicator in the PDCCH (i.e., DCI) is set to 1), if the PDSCH resource allocation overlaps with a PRB including SSB transmission resources (e.g., SSB candidate position indices 0 / 2 / 4 / 6 / 8 / 10 / 12 / 14 / 16 / 18), the UE may assume SSB transmission according to ssb-PositionsInBurst. That is, the UE may assume that the PRBs including SSB transmission resources are unavailable (not mapped) for the PDSCH in the OFDM symbol in which the SSB is transmitted.

[0108] Figure 10The system information (SI) acquisition process is illustrated. In the NR system, when the UE attempts initial access, the UE can obtain PDCCH configuration information for receiving SI (e.g., SIB1) from the PBCH payload (or MIB) (S1102). In this case, the PDCCH configuration information can represent: (1) information about the time / frequency resources of the CORESET (hereinafter referred to as CORESET#0) in which the PDCCH scheduling the PDSCH carrying SI is to be transmitted; and information about the CSS set associated with CORESET#0 (hereinafter referred to as Type0-PDCCHCSS set). Therefore, the UE can receive the PDCCH (scheduling the PDSCH carrying SI) based on the PDCCH configuration information and obtain SI from the PDSCH scheduled by the corresponding PDCCH (S1104). In addition, the UE can send a request for on-demand SI to the BS (S1106) and receive the requested SI (S1108).

[0109] SI other than the MIB may be referred to as remaining minimum system information (RMSI). The MIB includes information / parameters related to the reception of SIB1 (System Information Block Type 1) and is sent on the PBCH of the SSB. The information in the MIB may include the following fields, and their details can be found in 3GPP TS 38.331.

[0110] -subCarrierSpacingCommon ENUMERATED{scs15or60,scs30or120}

[0111] -ssb-SubcarrierOffset INTEGER(0··15),

[0112] -pdcch-ConfigSIB1 INTEGER(0··255)

[0113] -dmrs-TypeA-Position ENUMERATED{pos2, pos3}

[0114] The details of each field are summarized in Table 7.

[0115] [Table 7]

[0116]

[0117]

[0118] Figure 11The frequency positions of SSB and CORESET#0 are illustrated. The channel grid is defined by a subset of RF reference frequencies used to identify RF channel positions. RF reference frequencies are defined for all frequency bands, and the granularity (i.e., frequency interval) of the RF reference frequencies can be, for example, 5 kHz (in the frequency range of 0 to 3000 MHz) and 15 kHz (in the frequency range of 3000 to 24250 MHz). The synchronization grid is a subset of the channel grid and indicates the frequency bands used by the UE to obtain SI, SS, and RF reference frequencies. REF The frequency position of SSB. REF It can coincide with the center frequency of the 20 PRBs occupied by SSB. Table 8 shows the SSB REF and the Global Synchronization Channel Number (GSCN).

[0119] [Table 8]

[0120]

[0121] After SSB detection, the UE can determine, based on the information in the MIB (e.g., pdcch-ConfigSIB1), (i) one or more consecutive symbols and multiple consecutive RBs included in a CORESET (e.g., CORESET#0), and (ii) the PDCCH opportunity (i.e., the time domain position for PDCCH reception) (e.g., search space #0). Specifically, pdcch-ConfigSIB1 is 8-bit information. In this case, (i) is determined based on the four most significant bits (MSBs) (or four bits of the MSB) of pdcch-ConfigSIB1 (see 3GPP TS 38.213 Tables 13-1 to 13-10), and (ii) is determined based on the four least significant bits (LSBs) (or four bits of the LSB) of pdcch-ConfigSIB1 (see 3GPP TS 38.213 Tables 13-11 to 13-15).

[0122] Table 9 shows information indicated by the four MSBs of pdcch-ConfigSIB1.

[0123] [Table 9]

[0124]

[0125] *: Indicates the offset between the first RB of the SSB and the first RB of the RMSI CORESET.

[0126] The position of CORESET#0 in the frequency domain is determined by the RB offset and subcarrier offset relative to the SSB. Figure 11 , k SSBIndicates the number of common resource blocks (CRBs) N SSB CRB The subcarrier offset of subcarrier #0 of SSB to subcarrier #0 of SSB. SSB CRB Identified by a higher layer (eg, RRC) parameter (offsetToPointA), and k SSB It is a 5-bit value and consists of the following: MSB 1 bit of the 3 bits of the MIB for the candidate SSB index (=k SSB MSB 1 bit) + ssb-SubcarrierOffset 4 bits (= k SSB LSB 4 bits). RB offset represents the offset from the minimum RB index of CORESET#0 to the minimum RB index of the CRB overlapping with the first RB of the corresponding SSB, which can be determined based on the offset (RB) of Table 9.

[0127] As described above, the channel raster is defined to have a spacing of 15 kHz in the NR system (in the frequency band above 3 GHz) (see Table 8), and the corresponding value is used by the UE as a reference frequency for signal transmission and reception on the carrier. For example, the channel raster may represent the center frequency of the PRB resource region associated with the corresponding carrier / BWP. NR-U may be defined in the 5 GHz and / or 6 GHz bands. In an environment where NR-U coexists with Wi-Fi (and / or LTE LAA), the resource region of the carrier / BWP bandwidth may be aligned with the resource region of Wi-Fi. For example, considering that Wi-Fi is defined based on 20-MHz spacing channelization (such as 5150 to 5170 MHz and 5170 to 5190 MHz), the channel raster value may be defined to be aligned with 5150 to 5170 MHz and 5170 to 5190 MHz for a 20 MHz NR-U carrier bandwidth, or with 5150 to 5190 MHz for a 40 MHz NR-U carrier bandwidth. In addition, a specific channel raster value may be selected from the channel raster values ​​defined in NR according to the carrier / BWP bandwidth and the related frequency region to be aligned with the Wi-Fi channel (hereinafter, selected downward). As an example, for a 20 MHz carrier bandwidth corresponding to 5150 to 5170 MHz or 5170 to 5190 MHz, the channel raster value may be defined as 5160 MHz (corresponding to N in Table 8). REF =744000) or 5180.01MHz (N in Table 8 REF =745334). As another example, for a 40 MHz carrier bandwidth corresponding to 5150 to 5190 MHz, the channel grid value may be defined as 5169.99 MHz (corresponding to N in Table 8). REF=744666). In addition, in an environment where NR-U does not coexist with Wi-Fi (and / or LTE LAA), all channel grid values ​​with 15kHz SCS may be allowed without downselection, or if downselection is performed, multiple channel grid values ​​may be defined according to the carrier bandwidth and the relevant frequency region.

[0128] In NR, the synchronization raster is defined with a density sparser than the channel raster, taking into account the UE complexity for SS / PBCH block detection. The TX synchronization raster may coincide with the center frequency of the 20 PRBs occupied by the SS / PBCH blocks. Some of the synchronization raster values ​​with an interval of 1.44 MHz (defined in NR) may be defined as synchronization raster for NR-U, which may be defined in the 5 GHz and / or 6 GHz bands. Specifically, one synchronization raster value may be defined for each 20 MHz. The corresponding synchronization raster value may be defined to be close to the center frequency of 20 MHz. Alternatively, the corresponding synchronization raster values ​​may be defined so that the SS / PBCH blocks are located at the end of the 20 MHz as much as possible. For example, in Figure 12 In the region corresponding to 5150 to 5170 MHz shown in , the synchronization grid value can be defined as 5155.68 MHz (corresponding to GSCN=8996 in Table 8), so that the synchronization grid value belongs to the existing synchronization grid candidate of NR and is as close to 5150 MHz as possible, and the 20 PRBs of the SS / PBCH block are included in the corresponding region. In addition, in the present disclosure, it is basically assumed that the RB grid of the carrier / BWP (composed of 51 PRBs) is aligned with the RB grid of CORESET#0 (composed of 48 PRBs), as shown in FIG. Figure 12 as shown in the example.

[0129] Hereinafter, the present disclosure proposes a method for configuring resources of CORESET#0 for SI acquisition in an NR system operating in an unlicensed band, and a method for UE to analyze resources. For example, the present disclosure proposes a method for configuring the resource region of CORESEST#0 based on the PBCH payload (or MIB) when defining the synchronization grid and the channel grid. In addition, the present disclosure proposes a method for configuring the resource region of CORESEST#0 based on the PBCH payload (or MIB) in the SS / PBCH block when the SS / PBCH block is transmitted at a center frequency that does not correspond to the synchronization grid.

[0130] The proposed methods of the present disclosure are applicable to operations in only NR-U systems / cells (e.g., shared spectrum). For example, if the system is not an NR-U system / cell (e.g., shared spectrum), the methods proposed in this disclosure can be combined with the methods used in the current NR system.

[0131] 1) Receiver (Entity A) (e.g., UE):

[0132] [Method #1] The offset value from a specific RE of the SS / PBCH block (e.g., the first RE in the smallest RB index) to a specific RE of CORESET#0 (e.g., the first RE in the smallest RB index) can be configured by the PBCH payload of the corresponding SS / PBCH block. In this case, the offset value can be defined at the RB and / or RE level, and the RB level offset value can have a range determined based on the synchronization grid and channel grid defined for the NR-U band (which varies according to each band). Here, RE refers to a unit on the frequency axis, and the order of REs can be equal to the order of REs in one OFDM symbol. Therefore, REs can be replaced with subcarriers.

[0133] When the UE attempts initial access in the frequency band of the NR-U system, the UE may expect SS / PBCH and CORESET#0 with an SCS of 30kHz. In this case, the frequency region / position and time domain duration of CORESET#0 may be defined as the same as the frequency domain position and time domain duration of the current NR system. Table 10 shows the set of slot symbols and RBs for the CORESET of the Type0-PDCCH search space set when the SCS of {SS / PBCH block, PDCCH} is {30, 30}kHz for a frequency band with a minimum channel bandwidth of 5MHz or 10MHz in the current NR system.

[0134] [Table 10]

[0135]

[0136] However, the following restrictions may be imposed in NR-U: the number of RBs of 30kHz CORESET#0 is 48, and its time domain duration is one or two (OFDM) symbols. In addition, the range of RB level offset values ​​may be determined by the synchronization grid and channel grid defined for the NR-U band. For example, for each combination of frequency band and carrier / BWP bandwidth used to operate the NR-U system, if the maximum / minimum value of the RB level offset value between the minimum RB index of the SS / PBCH block and the minimum RB index of CORESET#0 is in the range of [A, B], some or all values ​​between A and B in the column corresponding to the offset of Table 10 may be signaled. For example, when A=-2 and B=5, 8 states out of a total of 16 states correspond to one symbol, and the remaining 8 states correspond to two symbols. Each of the 8 states may signal an RB level offset value between -2 and 5. Additionally, the RE level offset value may be determined by k in the same manner as in the NR system. SSBThe value of is signaled.

[0137] Table 11 shows the configuration of CORESET#0 in the case where A=-2 and B=5.

[0138] [Table 11]

[0139]

[0140] As an example, Figure 13 As shown, when the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is a synchronization raster defined for the 5150 to 5170 MHz band), the UE can be signaled "offset X" from the PBCH payload of the corresponding SS / PBCH block, which is the frequency offset between the SS / PBCH block and CORESET #0. For example, when the UE is signaled with index #4 and k in Table 11 through the PBCH payload, SSB =6, the UE can identify that the frequency region of CORESET#0 starts from the position separated by 2 RBGs and 6 REs from the SS / PBCH block.

[0141] As another example, the frequency domain position difference between RB#0 of the SS / PBCH block and RB#0 of the 51 PRBs can be as follows: Figure 14 The frequency domain position difference between RB#0 of the SS / PBCH block and RB#0 of the 51 PRBs can be greater than 4 PRBs, as shown in FIG. Figure 15 As shown in . Figure 14 , considering the interference with the adjacent 20MHz band, it may be preferable to align the first PRB of CORESET#0 with the second PRB among the 51 PRBs. In this case, -1 PRB may be required as the RB offset. Similarly, for Figure 15 , considering the interference with the adjacent 20MHz band, it may be preferable to align the last PRB of CORESET#0 with the second last PRB among the 51 PRBs. In this case, 2 PRBs may be required as RB offsets. To this end, information about RB offset values ​​from a minimum of -1 PRB to a maximum of 2 PRBs needs to be configured. The location of the time domain / frequency domain resources of CORESET#0 can be configured by the PBCH payload according to the method shown in Table 12 below. In Table 12, the "reserved" state is to prepare for when an RB offset value that is not in the range of [-1, 2] is required. RB offsets and reservation states in the range of [-k, k] (e.g., k=2) can be signaled.

[0142] In addition, when an SS / PBCH block is transmitted based on a 15 kHz SCS, the number of RBs (or PRBs) may be set to 96, and the RB offset may be set to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12), as shown in Table 13. Alternatively, as shown in Table 14, the number of RBs (or PRBs) may be set to 96, and the RB offset may be determined by an RB granularity based on a 15 kHz SCS, in addition to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12). Alternatively, as shown in Table 15, in addition to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12), the RB offset may also be determined by a value reflecting the difference between the absolute frequency domain resources corresponding to the 20 PRBs of the SS / PBCH block. That is, since an SS / PBCH block consists of 20 PRBs regardless of the SCS, when the SCS is 15 kHz, the frequency domain resources may be reduced (by 20 PRBs) compared to when the SCS is 30 kHz. Thereafter, the RB offset value may be filled with a value corresponding to {twice the RB offset value based on 30kHz SCS} + 10 (because 10 PRBs are reduced relative to the center frequency of the SS / PBCH block) (or an RB granularity value between the minimum / maximum values ​​with corresponding values), as shown in Table 15.

[0143] Table 12 shows the configuration of CORESET#0 when the SS / PBCH block is based on a 30kHz SCS, and Tables 13 to 15 show the configuration of CORESET#0 when the SS / PBCH block is based on a 15kHz SCS. In the tables, a to d represent integers, respectively. The RB offset is defined based on the SCS of the CORESET (i.e., CORESET#0) for the Type0-PDCCH CSS set. Figures 12 to 15 As shown in , the SCS of CORESET#0 is the same as the SCS of the corresponding SS / PBCH block.

[0144] [Table 12]

[0145]

[0146]

[0147] [Table 13]

[0148]

[0149]

[0150] [Table 14]

[0151]

[0152] [Table 15]

[0153]

[0154]

[0155] Figure 16 The operation of the example according to the present disclosure is illustrated. Figure 16 , the UE may detect an SSB in an unlicensed band (S1602). In this case, the SSB may include an index related to the CORESET configuration (see the indexes in Tables 12 to 15). Thereafter, the UE may determine an RB offset for identifying a frequency position of a CORESET associated with the SSB based on the index (S1604). The UE may monitor the CORESET in the unlicensed band based on the RB offset (S1606). In this case, the relationship between the index and the RB offset based on the SCS of the SSB may include the following relationship. The following relationship shows Figure 12 and Figure 15 In addition, Figure 12 Can also be used with Figure 13 / Figure 14 combination.

[0156] SSB SCS=30kHz SSB SCS=15kHz index RB offset RB offset n a 2a+10 n+1 b 2b+10 n+2 c 2c+10 n+3 d 2d+10

[0157] In the above table, each of n, a, b, c, and d is an integer, where a, b, c, and d can be a, a+1, a+2, and a+3, respectively. The center frequency of SSB can correspond to Figures 12 to 15 In addition, the UE may detect the PDCCH from the CORESET based on monitoring (S1606), and then receive system information (not shown in the figure) through the PDSCH related to the detected PDCCH.

[0158] [Method #2] The offset value from the channel raster corresponding to the frequency band in which the SS / PBCH block is transmitted to a specific frequency resource (e.g., center frequency) of CORESET #0 can be configured by the PBCH payload of the corresponding SS / PBCH block. In this case, the offset value can be defined at the RB and / or RE level, and the RB-level offset value can have a range determined based on the channel raster defined for the NR-U band (which varies according to each frequency band).

[0159] If the channel grid candidates vary depending on coexistence with Wi-Fi, the proposed channel grid may represent the channel grid when coexistence with Wi-Fi is assumed. Alternatively, if the channel grid candidates vary depending on carrier / BWP bandwidth, the proposed channel grid may represent the channel grid when a specific carrier bandwidth (e.g., 20 MHz) is assumed.

[0160] For example, for each combination of frequency band and specific carrier bandwidth (e.g., 20 MHz) for NR-U operation, if the maximum / minimum value of the RB level offset value from the channel grid to a specific frequency resource (e.g., center frequency) of CORESET#0 is within the range of [A, B], some or all values ​​between A and B in the column corresponding to the offset of Table 10 may be signaled. For example, when A=3 and B=4, 8 states out of a total of 16 states correspond to one symbol, and the remaining 8 states correspond to two symbols. Each of the 8 states may signal an RB level offset value between -3 and 4. In addition, the RE level offset value may be represented by k in the same manner as in the NR system. SSB The value of is signaled.

[0161] Table 16 shows the configuration of CORESET#0 in the case where A=-3 and B=4.

[0162] [Table 16]

[0163]

[0164]

[0165] As an example, Figure 17 As shown in FIG. 16 , when the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is a synchronization grid defined for the 5150 to 5170 MHz band), the UE can obtain the offset value between the specific channel grid value defined in the corresponding frequency band (e.g., 5160 MHz) and the center frequency of CORESET#0 from the PBCH payload of the corresponding SS / PBCH block. For example, when the UE is signaled with index #3 and k in Table 16 through the PBCH payload, the UE can obtain the offset value between the specific channel grid value defined in the corresponding frequency band (e.g., 5160 MHz) and the center frequency of CORESET#0. SSB=0, the UE can identify the frequency resource region of CORESET#0 consisting of 48 PRBs with the channel raster as the center frequency. As another example, when the offset value from the channel raster corresponding to the frequency band in which the SS / PBCH block is transmitted to the specific frequency resource (e.g., center frequency) of CORESET#0 is configured by the PBCH payload of the SS / PBCH block, only the RE level offset value (in addition to the RB level offset) can be signaled as the corresponding offset value. That is, the center frequency of CORESET#0 can be aligned with the specific channel raster, and the center frequency of CORESET#0 can be aligned with the specific channel raster by k SSB The RB grid of CORESET#0 can be aligned with the RB grid of the carrier / BWP, which is managed by the BS in the corresponding frequency band. SSB The value may represent n RE offsets (in the lower frequency direction) relative to the channel grid as a reference point (in which case n may be a negative number), or n RE offsets (in the higher frequency direction) (in which case n may be a positive number). SSB If the value is between 1 and 12, it can represent the RE shift in the direction of higher frequency (for example, if k SSB =n, it can represent n RE offsets in the higher frequency direction). If k SSB If the value is between 13 and 23, it may indicate an RE shift in the lower frequency direction (e.g. if k SSB =n, then it can represent (n-12) RE offsets in the lower frequency direction).

[0166] [Method #3] Candidates may be defined for multiple CORESET#0 frequency resource regions corresponding to the frequency band in which the SS / PBCH block is transmitted, and which of the candidates is actually used may be configured by the PBCH payload of the corresponding SS / PBCH block. In this case, the multiple candidates for the CORESET#0 frequency resource region may vary depending on the carrier / BWP bandwidth, the number of PRBs used in the carrier / BWP bandwidth, and / or the position of the 20 MHz frequency band in which the SS / PBCH block is transmitted in the carrier / BWP bandwidth (e.g., whether the SS / PBCH block is located in the higher 20 MHz frequency band or the lower 20 MHz frequency band in the 40 MHz carrier bandwidth). In addition, the RB grid and the position of CORESET#0 may be signaled.

[0167] For convenience, when the 20 MHz carrier is configured as 51 PRBs in the 5150 to 5170 MHz band (e.g. Figure 17When the 20 MHz carrier is configured with 50 PRBs in the 5150 to 5170 MHz band (as shown in FIG5 ), the offset value between the SS / PBCH block and CORESET#0 can be defined as offset X. Figure 18 When the 40 MHz carrier is configured with 106 PRBs in the 5150 to 5190 MHz band (as shown in FIG5 ), the offset value between the SS / PBCH block and CORESET#0 may be defined as offset Y. Figure 19 As shown), the offset value between the SS / PBCH block and CORESET#0 can be defined as offset Z.

[0168] The BS may notify one of the offsets X / Y / Z through the PBCH payload. When the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is the synchronization grid defined in the 5150 to 5170 MHz band), the UE may obtain one of the offsets X / Y / Z from the PBCH payload of the corresponding SS / PBCH block. The UE may identify the position of the minimum RB of CORESET#0 by applying the received offset. This example is related to the signaling of the offset value between the SS / PBCH block and CORESET#0, but the offset value between a specific frequency resource (e.g., the center frequency) of CORESET#0 and the channel grid may also be signaled as in [Method #2]. In addition, the corresponding offset value may be defined / interpreted differently depending on the frequency band of the SS / PBCH block.

[0169] [Method #4] If the UE needs to decode the PBCH payload of an SS / PBCH block other than the synchronization grid to determine the location of the frequency resources of CORESET#0, the UE may reinterpret the information in the decoded PBCH payload by assuming that the SS / PBCH block is transmitted in the synchronization grid defined for the frequency band corresponding to the corresponding SS / PBCH block.

[0170] According to the following motivation, the BS may need to provide information on CORESET#0 frequency resources even for SS / PBCH blocks other than the synchronization raster.

[0171] Different operators can coexist in unlicensed bands, and the same operator can coexist in unplanned deployment environments, so the same (physical) cell ID may be used across cells in the same band. To prevent UEs from being confused by this issue, the BS may need to send information about CORESET#0 and Type0-PDCCH CSS sets (even for SS / PBCH blocks that are not sent in the synchronization raster) for higher layer signaling (e.g., SIB1) containing information about the operator ID, public land mobile network (PLMN) ID, or global cell ID. For example, assuming gNB#X transmits SS / PBCH blocks in frequency #X and UE#Y is associated with gNB#Y, gNB#Y may instruct UE#Y to perform measurements on frequency #X (which may not match the synchronization raster). After performing the measurements on frequency #X, UE#Y may report the discovered cell ID of gNB#X and the measurement results of the corresponding cells to gNB#Y. If gNB#Y does not know whether gNB#X is the same operator, gNB#Y can instruct UE#Y to read gNB#X's higher-layer signaling (e.g., SIB1) containing information about the operator ID, PLMN ID, or global cell ID, and report the information about the operator ID, PLMN ID, or global cell ID. Upon receiving the corresponding information, gNB#Y can update the operator information about gNB#X. In view of this operation, gNB#X transmitting SS / PBCH blocks in frequency #X may need to explicitly / implicitly transmit information about CORESET#0 and Type0-PDCCHCSS set in the SS / PBCH blocks for scheduling PDSCH carrying higher-layer signaling containing information about the operator ID, PLMN ID, or global cell ID (for convenience, although such higher-layer signaling is named SIB1, it may correspond to cell-common higher-layer signaling).

[0172] For example, Figure 20As shown in [Method #1], if the UE decodes a PBCH payload of an SS / PBCH block having frequency #X instead of the synchronization raster as the center frequency, the UE may interpret information in the decoded PBCH payload based on the SS / PBCH block having a center frequency of 5155.68 MHz, which is the synchronization raster defined for the 5150 to 5170 frequency band corresponding to the corresponding SS / PBCH block. Specifically, if the UE receives an RB / RE level offset value from a PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an offset value from a specific RE of the SS / PBCH block on the synchronization raster (e.g., the first RE at the minimum RB index) to a specific RE of CORESET#0 (e.g., the first RE at the minimum RB index) so as to identify the location of the frequency resource of CORESET#0 as in [Method #1]. If the UE receives an RB / RE level offset value from a PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an offset value from the channel grid of the frequency band to which frequency #X belongs to a specific frequency resource (e.g., center frequency) of CORESET#0, so as to identify the location of the frequency resource of CORESET#0 as in [Method #2]. Alternatively, if the UE receives one of multiple candidates from a PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an actual resource among multiple candidates of the frequency resource region of CORESET#0 corresponding to the 5150 and 5170 MHz frequency bands to which frequency #X belongs, so as to identify the location of the frequency resource of CORESET#0 as in [Method #3].

[0173] [Method #5] If the UE needs to decode the PBCH payload of the SS / PBCH blocks in addition to the synchronization raster to determine the location of the frequency resources of CORESET#0, there may be restrictions on the center frequency resources allowed for SS / PBCH block transmission in addition to the synchronization raster, taking into account the limited PBCH payload. The spacing between the center frequencies allowed for SS / PBCH block transmissions may be PRBs or multiples of PRBs, where the PRBs may be based on a 30kHz SCS (or 15kHz SCS). In this case, it may be necessary to signal the offset between the SS / PBCH blocks and CORESET#0 with a spacing of one or more PRBs. If the number of values ​​required for the corresponding signaling is less than or equal to 8, it may be configured through the CORESET configuration in the MIB, as shown in Table 11 / 12. If the number of values ​​required for the corresponding signaling is greater than 8, it may be configured through the k in the MIB. SSB values ​​and / or some or all bits of the CORESET configuration.

[0174] [Method #6] If the UE needs to decode the PBCH payload of the SS / PBCH block other than the synchronization grid to determine the location of the frequency resource of CORESET#0, then N QCL SSB The signaling of the value of may be different from the signaling of the SS / PBCH blocks sent in the synchronization raster in order to support the center frequency value of the SS / PBCH blocks to be in place without any restriction on the 15kHz SCS granularity.

[0175] N QCL SSB The value indicates the QCL relationship between different candidate SSB indices. In the current NR-U, one of {1, 2, 4, 8} is indicated by the PBCH payload based on a combination of: (1) 1 bit of subCarrierSpacingCommon and (2) 1 bit of spare or LSB 1 bit of ssb-SubcarrierOffset (see Table 6). The value of ssb-SubcarrierOffset is used to indicate the k in FR 1. SSB In the current NR-U, since both the synchronization grid and the channel grid are at a granularity of 30kHz, the LSB 1 bit of ssb-SubcarrierOffset indicated in units of 15kHz is redundant. Thereafter, the corresponding LSB 1 bit can be used to signal N QCL SSB value.

[0176] However, for SS / PBCH blocks with center frequencies of frequency resources other than the synchronization grid (e.g., SS / PBCH blocks for automatic neighbor relations (ANR)), transmission may be allowed at any 15kHz granularity in the frequency domain. ANR refers to a method for minimizing or eliminating manual work on neighbor information when installing a new BS and optimizing neighbor information. When there is an SS / PBCH block for ANR in a cell, the UE can read the cell global identifier (CGI) of the cell from the SS / PBCH block and report the CGI to the BS. On the other hand, when there is an SS / PBCH block for non-ANR in the cell, the UE can perform channel measurement for the corresponding cell based only on the SS / PBCH block. Since the channel grid defined in the 5GHz band for the NR-U system is at a 30kHz granularity, the RE of CORESET#0 may also be at a 30kHz granularity. Therefore, if the SS / PBCH block is sent at a 15kHz granularity and CORESET#0 is sent at a 30kHz granularity, the LSB 1 bit of ssb-SubcarrierOffset may also be required for k SSB In this case, due to the existence of NQCL SSB The value is not signaled by the LSB 1 bit of ssb-SubcarrierOffset, so another way to signal N is proposed. QCL SSB That is, for SS / PBCH blocks transmitted based on the synchronization grid, N can be signaled in the same way as in Table 6. QCL SSB value, but for SS / PBCH blocks with center frequencies of frequency resources other than the synchronization grid, N may be signaled according to Option 1 or Option 2 QCL SSB value.

[0177] - Option 1: Instead of the LSB of ssb-SubcarrierOffset, N can be signaled by combining subCarrierSpacingCommon with other bits in the PBCH payload QCL SSB value.

[0178] - Option 2: N QCL SSB Signaling of the value may be configured with only 1 bit of subCarrierSpacingCommon.

[0179] Option 1 is to signal N as shown in Table 6 by combining 1 bit of the PBCH payload (e.g., the MSB 1 bit of the 4 bits of pdcch-ConfigSIB1, 1 bit of dmrs-TypeA-Position, etc.) with subCarrierSpacingCommon. QCL SSB The reason why the MSB 1 bit of the 4 bits of pdcch-ConfigSIB1 is available is that the 8 reservation states may not be signaled, as shown in Table 9. In addition, if 1 bit of dmrs-TypeA-Position is used, the position of the type ADMRS needs to be assumed. When receiving a PDCCH / PDSCH for receiving SI corresponding to an SS / PBCH block having a frequency resource other than the synchronization grid as the center frequency, the UE may assume that the first type ADMRS is always transmitted in the third (or fourth) symbol in the time slot.

[0180] According to option 2, when it is difficult to use the additional 1 bit of PBCH payload, N can be signaled only through subCarrierSpacingCommon. QCL SSBThe values ​​are as shown in Table 17. Table 17 merely shows an example of signaling, and actual values ​​corresponding to scs15or60 and scs30or120 may be replaced by any one of 1, 2, 4, and 8.

[0181] [Table 17]

[0182] subCarrierSpacingCommon <![CDATA[N QCL SSB ]]> scs15or60 1 [or 2] scs30or120 4 [or 8]

[0183] [Method #7] When the PBCH payload indicates N using a combination of 1 bit corresponding to subcarrierSpacingCommon and 1 bit of the LSB of ssb-SubcarrierOffset QCL SSB When the value is one of {1, 2, 4, 8} (see Table 6), it may be necessary to define k SSB Specifically, in the following case, k SSB The LSB of k can be defined as 0: 1) when the center frequency of the SS / PBCH block is equal to the synchronization raster; 2) when the center frequency of the SS / PBCH block is equal to the channel raster; or 3) when the spacing between the center frequency of the SS / PBCH block and the channel / synchronization raster is an integer multiple of 30 kHz. When the spacing between the center frequency of the SS / PBCH block and the channel / synchronization raster is an integer multiple of 15 kHz (except zero), k SSB The LSB can be defined as "1".

[0184] The spacing of the synchronization / channel raster for the NR-U system in the 5 GHz band is all defined as an integer multiple of 30 kHz. Therefore, if the carrier bandwidth is configured by considering the channel raster as the center frequency and if the SS / PBCH block and CORESET#0 are transmitted / configured in a portion of the corresponding bandwidth (centered on the synchronization raster), the spacing between the minimum RE of CORESET#0 (e.g., the first subcarrier) and the minimum RE of the SS / PBCH block (e.g., the first subcarrier) must be an integer multiple of 30 kHz. Specifically, the RE / RB level spacing between the minimum RE of CORESET#0 and the minimum RE of the SS / PBCH block can be signaled by the PBCH payload. Here, the RE level spacing can be represented by a 5-bit k SSB (i.e., the MSB 1 bit of the 3 bits included in the MIB used for the candidate SSB index in FR 2 + 4 bits of ssb-SubcarrierOffset). The RB level interval can be signaled based on the CORESET configuration table as described in [Method #1]. Specifically, the RB level interval can be signaled by considering the k bits corresponding to the smallest RE from the SS / PBCH block. SSBThe CRB grid is generated by using the points separated by the corresponding RE level as reference points, and the RB level offset configured by CORESET#0 can be applied to the reference points (see Figure 11 ) to determine the position of the minimum RE of CORESET#0. In this case, considering k SSB Corresponding to the signaling of 15kHz interval (that is, the number of subcarriers based on SCS=15kHz) and in the NR-U system, the spacing between the minimum RE of CORESET#0 and the minimum RE of the SS / PBCH block (centered on the synchronization grid) meets the integer multiple of 30kHz, the LSB 1 bit of ssb-SubcarrierOffset can always be "0". Therefore, the corresponding value can be used for other purposes, for example, to signal N QCL SSB value.

[0185] However, as described in [Method #6], it may be necessary to find the location of CORESET#0 corresponding to an SS / PBCH block that is not centered on the synchronization raster (for ANR purposes). In this case, (1) if the center frequency of the SS / PBCH block is the same as the channel raster, or (2) if the spacing between the center frequency of the SS / PBCH block and the channel / synchronization raster is an integer multiple of 30 kHz (e.g., 0, 30, 60, ...), then k SSB The LSB of the SS / PBCH block may also be defined as “0” (in the same manner as the SS / PBCH block transmitted in the synchronization raster) (e.g., k SSB =00000, 00010, 00100, ..., xxxx0, where x = 0 or 1). On the other hand, if the center frequency of the SS / PBCH block that is not centered on the synchronization grid and the interval between the channel / synchronization grid is not an integer multiple of 30 kHz, but an integer multiple of 15 kHz (excluding zero) (e.g., 15, 45, ...), then k can be set to SSB The LSB of the SS / PBCH block is defined as "1" (e.g., k_SSB = 00001, 00011, ..., xxxx1, where x = 0 or 1). This is because the spacing between each RE of CORESET#0 and the channel grid can be kept as an integer multiple of 30kHz to align the grid of CORESET#0 with the channel grid. Therefore, if the spacing between the center frequency of the SS / PBCH block that is not centered on the synchronization grid and the channel / synchronization grid is not an integer multiple of 30kHz, but an integer multiple of 15kHz (except zero), k can be signaled. SSB An odd value of (i.e., a value where LSB=1).

[0186] In other words, when the PBCH payload indicates N with a combination of 1 bit corresponding to subcarrierSpacingCommon and 1 bit of the LSB of ssb-SubcarrierOffset QCL SSB When the value is one of {1, 2, 4, 8},

[0187] - If the center frequency of the SS / PBCH block and the interval between the channel / synchronization grid meet the integer multiples of 30kHz (including zero), it can be assumed that ssb-SubcarrierOffset (or k SSB ) is "0".

[0188] - On the other hand, if the spacing between the center frequency of the SS / PBCH block and the channel / synchronization grid does not satisfy an integer multiple of 30kHz (including zero), but satisfies an integer multiple of 15kHz (excluding zero), then it can be assumed that ssb-SubcarrierOffset (or k SSB ) is "1".

[0189] The above suggestions can be summarized as follows in conjunction with Table 6.

[0190] [Table 18]

[0191]

[0192] *Case A: The spacing between the center frequency of the SS / PBCH block and the channel / synchronization grid is an integer multiple of 30kHz (including zero).

[0193] *Case B: The spacing between the center frequency of the SS / PBCH block and the channel / synchronization grid is not an integer multiple of 30kHz (including zero).

[0194] Alternatively, k SSB It can be defined as follows (see Table 19).

[0195] - If an SS / PBCH block is detected on a licensed carrier: k_SSB = MSB 1 bit of 3 bits included in the MIB for the candidate SSB index + 4 bits of ssb-SubcarrierOffset.

[0196] - If an SS / PBCH block is detected in an unlicensed carrier: k_SSB = MSB 1 bit of the 3 bits of the MIB for the candidate SSB index + MSB 3 bits of ssb-SubcarrierOffset + X (where X = 0 for case A or X = 1 for case B; see Table 9).

[0197] [Table 19]

[0198]

[0199] The authorized carrier and the unlicensed carrier can be identified based on the frequency of the carrier where the SS / PBCH block is detected, and the interval with the channel / synchronization grid can be predefined for each carrier (type) in the specification. Alternatively, even when the same frequency is used, the carrier type (authorized or unlicensed carrier) can vary according to the region. In this case, the authorized and unlicensed carriers can be identified by different PBCH payloads or CRC values. In order to identify the carrier type at the corresponding frequency, the synchronization grid for the authorized band and the synchronization grid for the unlicensed band can be defined separately in the specification. The UE can SSB The value of N can be used to find the location of CORESET#0 to perform PDCCH monitoring. QCL SSB The value to execute Figure 9 operation.

[0200] Additionally, in the current Rel-15 NR, it is possible to SSB This method is applied when the MSB 2 bits of k (i.e., the MSB 1 bit of the 3 bits of MIB for the candidate SSB index and the MSB 1 bit of the 4 bits of ssb-SubcarrierOffset in FR 2) are not "11". This is because in the Rel-15 NR system, when k SSB When the value of is greater than or equal to 24 (that is, when k SSB When each of the MSB 2 bits is "1", k SSB The value of is used to notify the location of the nearest SS / PBCH block (including CORESET#0 information) because CORESET#0 is not provided in the corresponding SS / PBCH block, as shown in Table 20. In other words, in the current Rel-15 NR system, if k SSB If the MSB 2 bits of the MIB for the candidate SSB index in FR 2 (i.e., the MSB 1 bit of the 3 bits of the MIB for the candidate SSB index and the MSB 1 bit of the 4 bits of ssb-SubcarrierOffset in FR 2) are "11" (even for the unlicensed band), the LSB of ssb-SubcarrierOffset can be set to k SSB LSB, then as explained in Table 20. On the other hand, if k SSB If the MSB 2 bits are "00", "10" or "01", k can be configured according to this method. SSB Alternatively, if k SSBIf the MSB 2 bits of ssb-SubcarrierOffset are "11" (even for unlicensed bands), the LSB of ssb-SubcarrierOffset can be set to k SSB LSB of k, as in the current Rel-15 NR system. SSB If the MSB 2 bits are "00", "10" or "01", then k SSB The LSB of may always be set to '0'. The location of SS / PBCH blocks that are not centered on the synchronization raster (where the location of CORESET#0 needs to be found for ANR purposes) may be restricted so that the location is only a multiple of 30 kHz from the synchronization raster.

[0201] [Table 20]

[0202]

[0203] 2) Sender (Entity B) (e.g., BS):

[0204] [Method #1A] The BS may signal an offset value from a specific RE of the SS / PBCH block (e.g., the first RE in the smallest RB index) to a specific RE of CORESET#0 (e.g., the first RE in the smallest RB index) through the PBCH payload of the corresponding SS / PBCH block. In this case, the offset value may be defined at the RB and / or RE level, and the RB level offset value may have a range determined based on the synchronization grid and channel grid defined for the NR-U band (which varies according to each band). Here, RE refers to a unit on the frequency axis, and the order of REs may be equal to the order of REs in one OFDM symbol. Therefore, REs may be replaced with subcarriers.

[0205] When the UE attempts to make initial access in the frequency band of the NR-U system, the UE may expect SS / PBCH and CORESET#0 with an SCS of 30kHz. In this case, the frequency domain position and time domain duration of CORESET#0 may be defined as the same as the frequency domain position and time domain duration of the current NR system. Table 10 shows the set of slot symbols and RBs for the CORESET of the Type0-PDCCH search space set when the SCS of {SS / PBCH block, PDCCH} is {30, 30}kHz for a frequency band with a minimum channel bandwidth of 5MHz or 10MHz in the current NR system.

[0206] However, the following restrictions may be imposed in NR-U: the number of RBs of 30kHz CORESET#0 is 48, and its time domain duration is one or two (OFDM) symbols. In addition, the range of RB level offset values ​​may be determined by the synchronization grid and channel grid defined for the NR-U band. For example, for each combination of frequency band and carrier / BWP bandwidth used to operate the NR-U system, if the maximum / minimum value of the RB level offset value between the minimum RB index of the SS / PBCH block and the minimum RB index of CORESET#0 is in the range of [A, B], some or all values ​​between A and B in the column corresponding to the offset of Table 10 may be signaled. For example, when A=-2 and B=5, 8 states out of a total of 16 states correspond to one symbol, and the remaining 8 states correspond to two symbols. Each of the 8 states may signal an RB level offset value between -2 and 5. Additionally, the RE level offset value may be determined by k in the same manner as in the NR system. SSB Table 11 shows the configuration of CORESET#0 in the case of A=-2 and B=5.

[0207] As an example, Figure 13 As shown in FIG11 , when the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is a synchronization grid defined for the 5150 to 5170 MHz band), the UE can obtain "offset X" from the PBCH payload of the corresponding SS / PBCH block, which is the frequency offset between the SS / PBCH block and CORESET#0. For example, when the UE is signaled with index #4 and k in Table 11 through the PBCH payload, SSB =6, the UE can identify that the frequency region of CORESET#0 starts from the position separated by 2 RBGs and 6 REs from the SS / PBCH block.

[0208] As another example, the frequency domain position difference between RB#0 of the SS / PBCH block and RB#0 of the 51 PRBs can be as follows: Figure 14 The frequency domain position difference between RB#0 of the SS / PBCH block and RB#0 of the 51 PRBs can be greater than 4 PRBs, as shown in FIG. Figure 15 As shown in . Figure 14 , considering the interference with the adjacent 20MHz band, it may be preferable to align the first PRB of CORESET#0 with the second PRB among the 51 PRBs. In this case, -1 PRB may be required as the RB offset. Similarly, for Figure 15, considering the interference with the adjacent 20MHz band, it may be preferable to align the last PRB of CORESET#0 with the second last PRB among the 51 PRBs. In this case, 2 PRBs may be required as RB offsets. To this end, information about RB offset values ​​from a minimum of -1 PRB to a maximum of 2 PRBs needs to be configured. The location of the time domain / frequency domain resources of CORESET#0 can be configured by the PBCH payload according to the method shown in Table 12 above. In Table 12, the "reserved" state is to prepare for when an RB offset value that is not in the range of [-1, 2] is required. RB offsets and reservation states in the range of [-k, k] (e.g., k=2) can be signaled.

[0209] In addition, when an SS / PBCH block is transmitted based on a 15 kHz SCS, the number of RBs (or PRBs) may be set to 96, and the RB offset may be set to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12), as shown in Table 13. Alternatively, as shown in Table 14, the number of RBs (or PRBs) may be set to 96, and the RB offset may be determined by an RB granularity based on a 15 kHz SCS, in addition to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12). Alternatively, as shown in Table 15, in addition to a value corresponding to twice the RB offset value based on a 30 kHz SCS (in Table 12), the RB offset may also be determined by a value reflecting the difference between the absolute frequency domain resources corresponding to the 20 PRBs of the SS / PBCH block. That is, since an SS / PBCH block consists of 20 PRBs regardless of the SCS, when the SCS is 15 kHz, the frequency domain resources may be reduced (by 20 PRBs) compared to when the SCS is 30 kHz. Thereafter, the RB offset value may be filled with a value corresponding to {twice the RB offset value based on 30kHz SCS} + 10 (because 10 PRBs are reduced relative to the center frequency of the SS / PBCH block) (or an RB granularity value between the minimum / maximum values ​​with corresponding values), as shown in Table 15.

[0210] Table 12 shows the configuration of CORESET#0 when the SS / PBCH block is based on a 30kHz SCS, and Tables 13 to 15 show the configuration of CORESET#0 when the SS / PBCH block is based on a 15kHz SCS. In the tables, a to d represent integers, respectively. The RB offset is defined based on the SCS of the CORESET (i.e., CORESET#0) for the Type0-PDCCH CSS set. Figures 12 to 15 As shown in , the SCS of CORESET#0 is the same as the SCS of the corresponding SS / PBCH block.

[0211] [Method #2A] The offset value from the channel raster corresponding to the frequency band in which the SS / PBCH block is transmitted to a specific frequency resource (e.g., center frequency) of CORESET #0 can be configured by the PBCH payload of the corresponding SS / PBCH block. In this case, the offset value can be defined at the RB and / or RE level, and the RB-level offset value can have a range determined based on the channel raster defined for the NR-U band (which varies according to each frequency band).

[0212] If the channel grid candidates vary depending on coexistence with Wi-Fi, the proposed channel grid may represent the channel grid when coexistence with Wi-Fi is assumed. Alternatively, if the channel grid candidates vary depending on carrier / BWP bandwidth, the proposed channel grid may represent the channel grid when a specific carrier bandwidth (e.g., 20 MHz) is assumed.

[0213] For example, for each combination of frequency band and specific carrier bandwidth (e.g., 20 MHz) for NR-U operation, if the maximum / minimum value of the RB level offset value from the channel grid to a specific frequency resource (e.g., center frequency) of CORESET#0 is within the range of [A, B], some or all values ​​between A and B in the column corresponding to the offset of Table 10 may be signaled. For example, when A=3 and B=4, 8 states out of a total of 16 states correspond to one symbol, and the remaining 8 states correspond to two symbols. Each of the 8 states may signal an RB level offset value between -3 and 4. In addition, the RE level offset value may be represented by k in the same manner as in the NR system. SSB Table 16 shows the configuration of CORESET#0 in the case of A=-3 and B=4.

[0214] As an example, Figure 17 As shown in FIG. 16 , when the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is a synchronization grid defined for the 5150 to 5170 MHz band), the UE can obtain the offset value between the specific channel grid value defined in the corresponding frequency band (e.g., 5160 MHz) and the center frequency of CORESET#0 from the PBCH payload of the corresponding SS / PBCH block. For example, when the UE is signaled with index #3 and k in Table 16 through the PBCH payload, the UE can obtain the offset value between the specific channel grid value defined in the corresponding frequency band (e.g., 5160 MHz) and the center frequency of CORESET#0. SSB =0, the UE can identify the frequency resource region of CORESET#0 consisting of 48 PRBs with the channel grid as the center frequency.

[0215] As another example, when an offset value from a channel raster corresponding to a frequency band in which an SS / PBCH block is transmitted to a specific frequency resource (e.g., center frequency) of CORESET#0 is configured by a PBCH payload of the SS / PBCH block, only an RE-level offset value (in addition to an RB-level offset) may be signaled as the corresponding offset value. That is, the center frequency of CORESET#0 may be aligned with a specific channel raster, and the center frequency of CORESET#0 may be aligned with the specific channel raster, and the center frequency of CORESET#0 may be aligned with the center frequency of CORESET#0 by k SSB The RB grid of CORESET#0 can be aligned with the RB grid of the carrier / BWP, which is managed by the BS in the corresponding frequency band. SSB The value may represent n RE offsets (in the lower frequency direction) relative to the channel grid as a reference point (in which case n may be a negative number), or n RE offsets (in the higher frequency direction) (in which case n may be a positive number). SSB If the value is between 1 and 12, it can represent the RE shift in the direction of higher frequency (for example, if k SSB =n, it can represent n RE offsets in the higher frequency direction). If k SSB If the value is between 13 and 23, it may indicate an RE shift in the lower frequency direction (e.g. if k SSB =n, then it can represent (n-12) RE offsets in the lower frequency direction).

[0216] [Method #3A] Candidates may be defined for multiple CORESET#0 frequency resource regions corresponding to the frequency band in which the SS / PBCH block is transmitted, and which of the candidates is actually used may be configured by the PBCH payload of the corresponding SS / PBCH block. In this case, the multiple candidates for the CORESET#0 frequency resource region may vary depending on the carrier / BWP bandwidth, the number of PRBs used in the carrier / BWP bandwidth, and / or the position of the 20 MHz frequency band in which the SS / PBCH block is transmitted in the carrier / BWP bandwidth (e.g., whether the SS / PBCH block is located in the higher 20 MHz frequency band or the lower 20 MHz frequency band in the 40 MHz carrier bandwidth). In addition, the RB grid and the position of CORESET#0 may be signaled.

[0217] For convenience, when the 20 MHz carrier is configured as 51 PRBs in the 5150 to 5170 MHz band (e.g. Figure 17 When the 20 MHz carrier is configured with 50 PRBs in the 5150 to 5170 MHz band (as shown in FIG5 ), the offset value between the SS / PBCH block and CORESET#0 can be defined as offset X. Figure 18When the 40 MHz carrier is configured with 106 PRBs in the 5150 to 5190 MHz band (as shown in FIG5 ), the offset value between the SS / PBCH block and CORESET#0 may be defined as offset Y. Figure 19 As shown), the offset value between the SS / PBCH block and CORESET#0 can be defined as offset Z.

[0218] The BS may notify one of the offsets X / Y / Z through the PBCH payload. When the UE receives an SS / PBCH block with a center frequency of 5155.68 MHz (which is the synchronization grid defined in the 5150 to 5170 MHz band), the UE may obtain one of the offsets X / Y / Z from the PBCH payload of the corresponding SS / PBCH block. The UE may identify the position of the minimum RB of CORESET#0 by applying the received offset. This example is related to the signaling of the offset value between the SS / PBCH block and CORESET#0, but the offset value between a specific frequency resource (e.g., center frequency) of CORESET#0 and the channel grid may also be signaled as in [Method #2A]. In addition, the corresponding offset value may be defined / interpreted differently depending on the frequency band of the SS / PBCH block.

[0219] [Method #4A] If the UE needs to decode the PBCH payload of an SS / PBCH block other than the synchronization grid to determine the location of the frequency resources of CORESET#0, the UE may reinterpret the information in the decoded PBCH payload by assuming that the SS / PBCH block is transmitted in the synchronization grid defined for the frequency band corresponding to the corresponding SS / PBCH block.

[0220] According to the following motivation, the BS may need to provide information on CORESET#0 frequency resources even for SS / PBCH blocks other than the synchronization raster.

[0221] Different operators can coexist in unlicensed bands, and the same operator can be deployed in unplanned environments, so the same (physical) cell ID may be used across cells in the same band. To prevent UEs from being confused by this issue, the BS may need to send information about CORESET#0 and Type0-PDCCH CSS sets for higher layer signaling (e.g., SIB1) containing information about the operator ID, PLMN ID, or global cell ID (even for SS / PBCH blocks that are not sent in the synchronization raster). For example, assuming gNB#X sends SS / PBCH blocks in frequency #X and UE#Y is associated with gNB#Y, gNB#Y may instruct UE#Y to perform measurements on frequency #X (which may not match the synchronization raster). After performing the measurements on frequency #X, UE#Y may report the discovered cell ID of gNB#X and the measurement results of the corresponding cells to gNB#Y. If gNB#Y does not know whether gNB#X is the same operator, gNB#Y can instruct UE#Y to read gNB#X's higher-layer signaling (e.g., SIB1) containing information about the operator ID, PLMN ID, or global cell ID, and report the information about the operator ID, PLMN ID, or global cell ID. Upon receiving the corresponding information, gNB#Y can update the operator information about gNB#X. In view of this operation, gNB#X transmitting SS / PBCH blocks in frequency #X may need to explicitly / implicitly transmit information about CORESET#0 and Type0-PDCCHCSS set in the SS / PBCH blocks for scheduling PDSCH carrying higher-layer signaling containing information about the operator ID, PLMN ID, or global cell ID (for convenience, although such higher-layer signaling is named SIB1, it may correspond to cell-common higher-layer signaling).

[0222] For example, Figure 20As shown in [Method #1A], if the UE decodes a PBCH payload of an SS / PBCH block having frequency #X instead of the synchronization raster as the center frequency, the BS may configure and transmit the corresponding PBCH payload based on the SS / PBCH block having a center frequency of 5155.68 MHz, which is the synchronization raster defined for the 5150 to 5170 frequency band corresponding to the corresponding SS / PBCH block. Specifically, if the UE receives an RB / RE level offset value from the PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an offset value from a specific RE of the SS / PBCH block on the synchronization raster (e.g., the first RE at the minimum RB index) to a specific RE of CORESET#0 (e.g., the first RE at the minimum RB index) so as to identify the location of the frequency resource of CORESET#0 as in [Method #1A]. If the UE receives an RB / RE level offset value from a PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an offset value from the channel grid of the frequency band to which frequency #X belongs to a specific frequency resource (e.g., center frequency) of CORESET #0, so as to identify the location of the frequency resource of CORESET #0 as in [Method #2A]. Alternatively, if the UE receives one of multiple candidates from a PBCH payload corresponding to frequency #X, the UE may interpret the corresponding value as an actual resource among multiple candidates of the frequency resource region of CORESET #0 corresponding to the 5150 and 5170 MHz frequency bands to which frequency #X belongs, so as to identify the location of the frequency resource of CORESET #0 as in [Method #3A].

[0223] [Method #5A] If the UE needs to decode the PBCH payload of the SS / PBCH blocks in addition to the synchronization raster to determine the location of the frequency resources of CORESET#0, there may be restrictions on the center frequency resources allowed for SS / PBCH block transmission in addition to the synchronization raster, taking into account the limited PBCH payload. The spacing between the center frequencies allowed for SS / PBCH block transmissions may be PRBs or multiples of PRBs, where the PRBs may be based on a 30kHz SCS (or 15kHz SCS). In this case, it may be necessary to signal the offset between the SS / PBCH blocks and CORESET#0 with a spacing of one or more PRBs. If the number of values ​​required for the corresponding signaling is less than or equal to 8, it may be configured through the CORESET configuration in the MIB, as shown in Table 11 / 12. If the number of values ​​required for the corresponding signaling is greater than 8, it may be configured through the k in the MIB. SSB values ​​and / or some or all bits of the CORESET configuration.

[0224] [Method #6A] If the UE needs to decode the PBCH payload of the SS / PBCH block other than the synchronization grid to determine the location of the frequency resource of CORESET#0, then N QCL SSB The signaling of the value of may be different from the signaling of the SS / PBCH blocks sent in the synchronization raster in order to support the center frequency value of the SS / PBCH blocks to be in place without any restriction on the 15kHz SCS granularity.

[0225] N QCL SSB The value indicates the QCL relationship between different candidate SSB indices. In the current NR-U, one of {1, 2, 4, 8} is indicated by the PBCH payload based on a combination of: (1) 1 bit of subCarrierSpacingCommon and (2) 1 bit of spare or LSB 1 bit of ssb-SubcarrierOffset (see Table 6). The value of ssb-SubcarrierOffset is used to indicate the k in FR 1. SSB In the current NR-U, since both the synchronization grid and the channel grid are at a granularity of 30kHz, the LSB 1 bit of ssb-SubcarrierOffset indicated in units of 15kHz is redundant. Thereafter, the corresponding LSB 1 bit can be used to signal N QCL SSB value.

[0226] However, for SS / PBCH blocks with center frequencies of frequency resources other than the synchronization grid (e.g., SS / PBCH blocks for ANR), transmission may be allowed at any 15kHz granularity in the frequency domain. Since the channel grid defined in the 5GHz band for the NR-U system is at a 30kHz granularity, the REs of CORESET#0 may also be at a 30kHz granularity. Therefore, if the SS / PBCH blocks are transmitted at a 15kHz granularity and CORESET#0 is transmitted at a 30kHz granularity, the LSB 1 bit of ssb-SubcarrierOffset may also be required for k SSB In this case, due to the existence of N QCL SSB The value is not signaled by the LSB 1 bit of ssb-SubcarrierOffset, so another way to signal N is proposed. QCL SSB That is, for SS / PBCH blocks transmitted based on the synchronization grid, N can be signaled in the same way as in Table 6. QCLSSB value, but for SS / PBCH blocks with center frequencies of frequency resources other than the synchronization grid, N may be signaled according to Option 1 or Option 2 QCL SSB value.

[0227] - Option 1: Instead of the LSB of ssb-SubcarrierOffset, N can be signaled by combining subCarrierSpacingCommon with other bits in the PBCH payload QCL SSB value.

[0228] - Option 2: N QCL SSB Signaling of the value may be configured with only 1 bit of subCarrierSpacingCommon.

[0229] Option 1 is to signal N as shown in Table 6 by combining 1 bit of the PBCH payload (e.g., the MSB 1 bit of the 4 bits of pdcch-ConfigSIB1, 1 bit of dmrs-TypeA-Position, etc.) with subCarrierSpacingCommon. QCL SSB The reason why the MSB 1 bit of the 4 bits of pdcch-ConfigSIB1 is available is that the 8 reservation states may not be signaled, as shown in Table 9. In addition, if 1 bit of dmrs-TypeA-Position is used, the position of the type ADMRS needs to be assumed. If the UE receives a PDCCH / PDSCH for receiving SI corresponding to an SS / PBCH block having a frequency resource other than the synchronization grid as the center frequency, the BS may always transmit the first type ADMRS in the third (or fourth) symbol in the time slot.

[0230] According to option 2, when it is difficult to use the additional 1 bit of PBCH payload, N can be signaled only through subCarrierSpacingCommon. QCL SSB The values ​​are as shown in Table 17. Table 17 merely shows an example of signaling, and actual values ​​corresponding to scs15or60 and scs30or120 may be replaced by any one of 1, 2, 4, and 8.

[0231] [Method #7A] When the PBCH payload indicates N using a combination of 1 bit of subcarrierSpacingCommon and 1 bit of the LSB of ssb-SubcarrierOffset QCLSSB When the value is one of {1, 2, 4, 8} (see Table 6), it may be necessary to define k SSB Specifically, in the following case, k SSB The LSB of k can be defined as 0: 1) when the center frequency of the SS / PBCH block is equal to the synchronization raster; 2) when the center frequency of the SS / PBCH block is equal to the channel raster; and 3) when the spacing between the center frequency of the SS / PBCH block and the channel / synchronization raster is an integer multiple of 30 kHz. When the spacing between the center frequency of the SS / PBCH block and the channel / synchronization raster is an integer multiple of 15 kHz (except zero), k SSB The LSB can be defined as "1".

[0232] The intervals of the synchronization / channel raster for the NR-U system in the 5 GHz band are all defined as integer multiples of 30 kHz. Therefore, if the carrier bandwidth is configured by considering the channel raster as the center frequency and if the SS / PBCH block and CORESET#0 are transmitted / configured in a portion of the corresponding bandwidth (centered on the synchronization raster), the interval between the minimum RE of CORESET#0 (e.g., the first subcarrier) and the minimum RE of the SS / PBCH block (e.g., the first subcarrier) can be an integer multiple of 30 kHz. Specifically, the RE / RB level interval between the minimum RE of CORESET#0 and the minimum RE of the SS / PBCH block can be signaled by the PBCH payload. Here, the RE level interval can be represented by a 5-bit k SSB (i.e., the MSB 1 bit of the 3 bits of the MIB used for the candidate SSB index in FR 2 + the 4 bits of ssb-SubcarrierOffset). The RB level interval can be signaled based on the CORESET configuration table as described in [Method #1A]. Specifically, the RB level interval can be represented by k bits of the smallest RE from the SS / PBCH block. SSB The CRB grid is created by considering the points separated by the corresponding RE level intervals as reference points and the RB level offsets in the CORESET#0 configuration can be applied to the reference points (see Figure 11 ) to determine the position of the minimum RE of CORESET#0. In this case, considering k SSBCorresponding to the signaling of 15kHz interval (that is, the number of subcarriers based on SCS=15kHz) and in the NR-U system, the spacing between the minimum RE of CORESET#0 and the minimum RE of the SS / PBCH block (centered on the synchronization grid) meets the integer multiple of 30kHz, the LSB 1 bit of ssb-SubcarrierOffset can always be "0". Therefore, the corresponding value can be used for other purposes, for example, to signal N QCL SSB value.

[0233] However, as described in [Method #6A], for SS / PBCH blocks that are not centered on the synchronization grid, it may be necessary to find the location of CORESET#0 associated with them. In this case, (1) if the center frequency of the SS / PBCH block is the same as the channel grid, and / or (2) if the spacing between the center frequency of the SS / PBCH block and the channel / synchronization grid is an integer multiple of 30 kHz (e.g., 0, 30, 60, ...), then k SSB The LSB of the SS / PBCH block may also be defined as “0” (in the same manner as the SS / PBCH block transmitted in the synchronization raster) (e.g., k SSB =00000, 00010, 00100, ..., xxxx0, where x = 0 or 1). On the other hand, if the center frequency of the SS / PBCH block that is not centered on the synchronization grid and the interval between the channel / synchronization grid is not an integer multiple of 30 kHz, but an integer multiple of 15 kHz (excluding zero) (e.g., 15, 45, ...), then k can be set to SSB The LSB of the SS / PBCH block is defined as "1" (e.g., k_SSB = 00001, 00011, ..., xxxx1, where x = 0 or 1). This is because the spacing between each RE of CORESET#0 and the channel grid can be kept as an integer multiple of 30kHz to align the grid of CORESET#0 with the channel grid. Therefore, if the spacing between the center frequency of the SS / PBCH block that is not centered on the synchronization grid and the channel / synchronization grid is not an integer multiple of 30kHz, but an integer multiple of 15kHz (except zero), k can be signaled. SSB odd value (ie, LSB=1).

[0234] In other words, when the PBCH payload indicates N using a combination of 1 bit of subcarrierSpacingCommon and 1 bit of the LSB of ssb-SubcarrierOffset QCL SSB When the value is one of {1, 2, 4, 8},

[0235] - If the center frequency of the SS / PBCH block and the interval between the channel / synchronization grid meet the integer multiples of 30kHz (including zero), it can be assumed that ssb-SubcarrierOffset (or k SSB ) is "0".

[0236] - On the other hand, if the spacing between the center frequency of the SS / PBCH block and the channel / synchronization grid does not satisfy an integer multiple of 30kHz (including zero), but satisfies an integer multiple of 15kHz (excluding zero), then it can be assumed that ssb-SubcarrierOffset (or k SSB The above proposals can be summarized as follows in conjunction with Table 6.

[0237] Alternatively, k SSB It can be defined as follows (see Table 19).

[0238] - If an SS / PBCH block is detected on a licensed carrier: k_SSB = MSB 1 bit of the 3 bits of the MIB for the candidate SSB index + 4 bits of ssb-SubcarrierOffset.

[0239] - If an SS / PBCH block is detected in an unlicensed carrier: k_SSB = MSB 1 bit of the 3 bits of the MIB for the candidate SSB index + MSB 3 bits of ssb-SubcarrierOffset + X (where X = 0 for case A or X = 1 for case B; see Table 9).

[0240] The licensed carriers and unlicensed carriers can be identified based on the frequency of the carrier where the SS / PBCH block is detected, and the interval with channel / synchronization grid can be predefined for each carrier (type) in the specification. SSB The PDCCH is transmitted at the location of CORESET#0. Alternatively, even when the same frequency is used, the carrier type (licensed or unlicensed carrier) may vary depending on the region. In this case, the licensed and unlicensed carriers may be identified by different PBCH payloads or CRC values. In order to identify the carrier type at the corresponding frequency, the synchronization grid for the licensed band and the synchronization grid for the unlicensed band may be defined separately in the specification. In addition, the BS may QCL SSB The value to execute Figure 9 operation.

[0241] Additionally, in the current Rel-15 NR, it is possible to SSBThis method is applied when the MSB 2 bits of k (i.e., the MSB 1 bit of the 3 bits of MIB for the candidate SSB index and the MSB 1 bit of the 4 bits of ssb-SubcarrierOffset in FR 2) are not "11". This is because in the Rel-15 NR system, when k SSB When the value of is greater than or equal to 24 (that is, when k SSB When each of the MSB 2 bits is "1", k SSB The value of is used to notify the location of the nearest SS / PBCH block (including CORESET#0 information) because CORESET#0 is not provided in the corresponding SS / PBCH block, as shown in Table 20. In other words, in the current Rel-15 NR system, if k SSB If the MSB 2 bits of the MIB for the candidate SSB index in FR 2 (i.e., the MSB 1 bit of the 3 bits of the MIB for the candidate SSB index and the MSB 1 bit of the 4 bits of ssb-SubcarrierOffset in FR 2) are "11" (even for the unlicensed band), the LSB of ssb-SubcarrierOffset can be set to k SSB LSB, then as explained in Table 20. On the other hand, if k SSB If the MSB 2 bits are "00", "10" or "01", k can be configured according to this method. SSB Alternatively, if k SSB If the MSB 2 bits of ssb-SubcarrierOffset are "11" (even for unlicensed bands), the LSB of ssb-SubcarrierOffset can be set to k SSB LSB of k, as in the current Rel-15 NR system. SSB If the MSB 2 bits are "00", "10" or "01", then k SSB The LSB of may always be set to '0'. The location of SS / PBCH blocks that are not centered on the synchronization raster (where the location of CORESET#0 needs to be found for ANR purposes) may be restricted so that the location is only a multiple of 30 kHz from the synchronization raster.

[0242] 3) Receiver & Transmitter (between receiver and transmitter)

[0243] According to the proposal of the present disclosure, a BS operating in a bandwidth of 5 or 6 GHz may transmit an SS / PBCH block (S2102) by considering a synchronization raster defined in the corresponding bandwidth as a center frequency and transmitting information on a frequency resource of CORESET#0 through a PBCH payload of the corresponding SS / PBCH block, as shown in FIG. Figure 21When receiving an SS / PBCH block, the UE can detect the bandwidth of the SS / PBCH block and / or the PBCH payload of the SS / PBCH block by analyzing (e.g., CORESET configuration (pdcch-ConfigSIB1), k SSB or other information) to identify the frequency resource region of CORESET#0 (S2104). In addition, the UE can obtain information about the Type0-PDCCH monitoring opportunity by interpreting the PBCH payload (e.g., pdcch-ConfigSIB1) in the SS / PBCH block. Thereafter, the UE can receive the PDCCH in the frequency resource region of CORESET#0 at the type0-PDCCH monitoring opportunity and obtain SI (e.g., SIB1) from the PDSCH scheduled by the corresponding PDCCH.

[0244] Alternatively, according to the proposal of the present disclosure, even when the BS transmits an SS / PBCH block having a frequency not defined as a synchronization grid as a center frequency in an unlicensed band for the purpose of ANR, the corresponding SS / PBCH block may carry information on CORESET#0 and / or information on type0-PDCCH monitoring opportunities (S2202), as shown in FIG. Figure 22 As shown in . In the case of applying the PBCH information obtained from the corresponding bandwidth and the detected SS / PBCH block, the UE may assume that the received SS / PBCH block is an SS / PBCH block transmitted in the synchronization grid in the bandwidth to which the corresponding SS / PBCH block belongs, and interpret that the corresponding SS / PBCH block is transmitted in the synchronization grid, so as to obtain information about CORESET#0 and / or information about type0-PDCCH monitoring opportunity (S2204). Thereafter, the UE may receive the PDCCH in the frequency resource region of CORESET#0 at the Type0-PDCCH monitoring opportunity, and obtain SI (e.g., SIB1) from the PDSCH scheduled by the corresponding PDCCH.

[0245] In the proposal of the present disclosure, the 5 GHz or 6 GHz band can be replaced with an unlicensed band / UCell. In addition, the proposal of the present disclosure can be considered as a method of configuring / interpreting the MIB information related to CORESET#0 differently according to the type of frequency band (or cell) in which the SS / PBCH block is detected. For example, according to method #1, the UE can obtain pdcch-ConfigSIB1 from the MIB after detecting the SS / PBCH block. Thereafter, the UE can interpret pdcch-ConfigSIB1 differently depending on whether the frequency band (or cell) in which the SS / PBCH block is detected is a licensed band / LCell or an unlicensed band / UCell. For example, the UE can interpret the MSB 4 bits of pdcch-ConfigSIB1 as follows.

[0246] [Table 21]

[0247]

[0248]

[0249] * Table 21 shows CORESET #0 configuration information. CORESET #0 configuration information may also include, for example, at least one of a multiplexing pattern, the number of RBs, and / or the number of symbols. * The offset for the LCell and the offset for the UCell may be configured independently. For example, the offset for the LCell may be defined based on 3GPP TS 38.213 Tables 13-11 to 13-15, and the offset for the UCell may be defined in consideration of the channel / synchronization grid according to the proposal of the present disclosure.

[0250] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described above in this document may be applied to (but not limited to) various fields requiring wireless communication / connection between devices (e.g., 5G).

[0251] Hereinafter, a description will be given in more detail with reference to the accompanying drawings.In the following drawings / descriptions, unless otherwise specified, the same reference symbols may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0252] Figure 23 A communication system 1 applied to the present disclosure is illustrated.

[0253] Reference Figure 23, the communication system 1 applied to the present disclosure includes a wireless device, a BS and a network. The wireless device is a device that performs communication using a radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also known as a communication / radio / 5G device. The wireless device may include, but is not limited to: a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with wireless communication capabilities, an autonomous vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. In this article, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television (TV), a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include televisions, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, the BS and network may be implemented as wireless devices, and a specific wireless device 200a may serve as a BS / network node for other wireless devices.

[0254] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can communicate directly with each other (e.g., sidelink communication) without the intervention of the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., V2V / Vehicle-to-Everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0255] Wireless communications / connections 150a, 150b, and 150c may be established between wireless devices 100a to 100f / BS 200, and between BSs 200. Hereinafter, wireless communications / connections may be established via various RATs (e.g., 5G NR), such as UL / DL communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay or integrated access backhaul (IAB)). Wireless signals may be transmitted and received between wireless devices, between wireless devices and BSs, and between BSs via the wireless communications / connections 150a, 150b, and 150c. For example, signals may be transmitted and received over various physical channels via the wireless communications / connections 150a, 150b, and 150c. To this end, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving wireless signals may be performed based on various proposals of the present disclosure.

[0256] Figure 24 A wireless device suitable for use with the present disclosure is illustrated.

[0257] Reference Figure 24 , the first wireless device 100 and the second wireless device 200 can transmit wireless signals through various RATs (e.g., LTE and NR). {The first wireless device 100 and the second wireless device 200} may correspond to Figure 23 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0258] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may also include one or more transceivers 106 and / or one or more antennas (antenna units) 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals through the transceiver 106. The processor 102 may receive a wireless signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. The processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive wireless signals via one or more antennas 108. Each of the transceivers 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may be a communication modem / circuit / chip.

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

[0260] The hardware elements of the wireless devices 100 and 200 will now be described in more detail. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). The one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document and provide the messages, control information, data, or information to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from the one or more transceivers 106 and 206, and obtain the PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0261] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in one or more processors 102 and 202, or may be stored in one or more memories 104 and 204 and executed by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, instructions and / or instruction sets using firmware or software.

[0262] One or more memories 104 and 204 can be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 can be configured to include read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104 and 204 can be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 can be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0263] One or more transceivers 106 and 206 may transmit user data, control information, and / or wireless signals / channels described in the methods and / or operational flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or wireless signals / channels described in the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive wireless signals. For example, one or more processors 102 and 202 may control one or more transceivers 106 and 206 to transmit user data, control information, or wireless signals to one or more other devices. One or more processors 102 and 202 may control one or more transceivers 106 and 206 to receive user data, control information, or wireless signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or wireless signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received wireless signals / channels from RF band signals to baseband signals to facilitate processing of the received user data, control information, and wireless signals / channels using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, and wireless signals / channels processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0264] Herein, at least one memory (e.g., 104 or 204) may store instructions or programs. When executed, the instructions or programs may cause at least one processor operably coupled to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.

[0265] In the present disclosure, a computer-readable (storage) medium may store at least one instruction or computer program, wherein the at least one instruction or computer program may cause the at least one processor to perform operations according to some embodiments or implementations of the present disclosure when executed by the at least one processor.

[0266] In the present disclosure, a processing device or apparatus may include at least one processor and at least one computer memory connectable to the at least one processor. The at least one computer memory may store instructions or programs. When executed, the instructions or programs may cause the at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present disclosure.

[0267] Figure 25 Another example of a wireless device applied to the present disclosure is illustrated. The wireless device can be implemented in various forms according to use cases / services (see Figure 23 ).

[0268] Reference Figure 25 , wireless devices 100 and 200 can communicate with Figure 24 The wireless devices 100 and 200 correspond to each other and may be configured to include various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 24 The one or more processors 102 and 202 and / or the one or more memories 104 and 204 of the present invention may include: Figure 24 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and provides overall control of the wireless device. For example, the control unit 120 can control the electrical / mechanical operation of the wireless device based on the program / code / instructions / information stored in the memory unit 130. The control unit 120 can transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 via a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 via the wireless / wired interface in the memory unit 130.

[0269] The additional component 140 may be configured in various ways depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the form of, but not limited to, a robot ( Figure 23 100a), vehicles ( Figure 23 100b-1 and 100b-2), XR devices ( Figure 23 100c), handheld device ( Figure 23 100d), household appliances ( Figure 23 100e), IoT devices ( Figure 23 100f), digital broadcast terminal, hologram device, public safety device, MTC device, medical device, FinTech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 23 400), BS( Figure 23 200), network nodes, etc. Depending on the use case / service, the wireless device can be mobile or fixed.

[0270] exist Figure 25 In the wireless devices 100 and 200, all the various elements, components, units / parts, and / or modules can be connected to each other via a wired interface, or at least a portion thereof can be wirelessly connected via the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 can be connected via a wired interface, and the control unit 120 and the first unit (e.g., 130 and 140) can be wirelessly connected via the communication unit 110. Each element, component, unit / part, and / or module in the wireless devices 100 and 200 can also include one or more elements. For example, the control unit 120 can be configured with a set of one or more processors. For example, the control unit 120 can be configured with a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. In another example, the memory unit 130 can be configured with RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0271] Figure 26 The vehicle or autonomous driving vehicle applied to the present disclosure is illustrated. The vehicle or autonomous driving vehicle can be implemented as a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0272] Reference Figure 26 , the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Figure 25 Box 110 / 130 / 140.

[0273] The communication unit 110 can transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, base stations (e.g., gNBs and roadside units), and servers. The control unit 120 can perform various operations by controlling components of the vehicle or autonomous vehicle 100. The control unit 120 may include an ECU. The drive unit 140a can enable the vehicle or autonomous vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a powertrain, wheels, brakes, a steering system, and the like. The power supply unit 140b can provide power to the vehicle or autonomous vehicle 100 and may include a wired / wireless charging circuit, a battery, and the like. The sensor unit 140c can acquire information about the vehicle's status, surrounding environment information, user information, and the like. The sensor unit 140 c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a location module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140 d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed such as adaptive cruise control, a technology for autonomous driving along a determined path, a driving technology for automatically setting a route when a destination is set, etc.

[0274] For example, the communication unit 110 can receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d can generate an autonomous driving route and driving plan from the obtained data. The control unit 120 can control the drive unit 140a so that the vehicle or autonomous driving vehicle 100 moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 can aperiodically or periodically obtain the latest traffic information data from the external server and can obtain surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c can obtain information about the vehicle status and / or surrounding environment information. The autonomous driving unit 140d can update the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 can transmit information about the vehicle's location, autonomous driving route, and / or driving plan to the external server. The external server can use AI technology to predict traffic information data based on the information collected from the vehicle or autonomous driving vehicle and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0275] The embodiments of the present disclosure described above are combinations of elements and features of the present disclosure. Unless otherwise stated, elements or features may be considered to be selective. Each element or feature may be put into practice without being combined with other elements or features. In addition, the embodiments of the present disclosure may be constructed by combining parts of elements and / or features. The order of operations described in the embodiments of the present disclosure may be rearranged. Some configurations of any one embodiment may be included in another embodiment and may be replaced by corresponding configurations of another embodiment. It will be apparent to those skilled in the art that claims that are not explicitly cited in the appended claims may be presented as combinations of embodiments of the present disclosure, or may be included as new claims through subsequent amendments after submitting this application.

[0276] Those skilled in the art will recognize that the present disclosure may be implemented in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments should be interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalent range of the appended claims should be included therein.

[0277] Industrial Applicability

[0278] The present disclosure is applicable to user equipment, base stations or other devices in a wireless mobile communication system.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Detecting a synchronization signal / physical broadcast channel SS / PBCH block in a shared spectrum, wherein the SS / PBCH block includes an index related to a configuration of a control resource set CORESET; determining an offset from a minimum resource block (RB) index of the CORESET to a minimum RB index of the SS / PBCH block based on the index, wherein the CORESET is for a Type 0-Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) set; and monitoring the Type 0-PDCCH CSS set associated with the CORESET in the shared spectrum based on the offset, Wherein, based on the subcarrier spacing SCS of the SS / PBCH block being 30 kHz, the offset is determined to be N1 for the index, The SCS of the SS / PBCH block is 15 kHz, and for the index, the offset is determined to be N2. Where N1 and N2 are non-negative integers, and Among them, N2=2*N1+10.

2. The method according to claim 1, in, Based on the index being the first value, N1=0 and N2=10, Wherein, based on the index being the second value, N1=1 and N2=12, and Wherein, based on the index being the third value, N1=2 and N2=14.

3. The method according to claim 1, in, The center frequency of the SS / PBCH block corresponds to the synchronization grid.

4. The method according to claim 1, further comprising the steps of: A PDCCH from the Type0-PDCCH CSS is detected based on the monitoring.

5. The method according to claim 4, further comprising: System information is received via a physical downlink shared channel (PDSCH) associated with the PDCCH.

6. A user equipment (UE), comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured, when executed, to cause the at least one processor to perform operations comprising: Detecting a synchronization signal / physical broadcast channel SS / PBCH block in a shared spectrum, wherein the SS / PBCH block includes an index related to a configuration of a control resource set CORESET; determining an offset from a minimum resource block (RB) index of the CORESET to a minimum RB index of the SS / PBCH block based on the index, wherein the CORESET is for a Type 0-Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) set; and monitoring the Type 0-PDCCH CSS set associated with the CORESET in the shared spectrum based on the offset, Wherein, based on the subcarrier spacing SCS of the SS / PBCH block being 30 kHz, the offset is determined to be N1 for the index, The SCS of the SS / PBCH block is 15 kHz, and for the index, the offset is determined to be N2. Where N1 and N2 are non-negative integers, and Among them, N2=2*N1+10.

7. The UE according to claim 6, in, Based on the index being the first value, N1=0 and N2=10, Wherein, based on the index being the second value, N1=1 and N2=12, and Wherein, based on the index being the third value, N1=2 and N2=14.

8. The UE according to claim 6, in, The center frequency of the SS / PBCH block corresponds to the synchronization grid.

9. The UE according to claim 6, in, The operations also include detecting a PDCCH from the Type 0-PDCCH CSS based on the monitoring.

10. The UE according to claim 9, in, The operation includes receiving system information via a physical downlink shared channel (PDSCH) related to the PDCCH.

11. A device for a user equipment (UE), comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured, when executed, to cause the at least one processor to perform operations comprising: Detecting a synchronization signal / physical broadcast channel SS / PBCH block in a shared spectrum, wherein the SS / PBCH block includes an index related to a configuration of a control resource set CORESET; determining an offset from a minimum resource block (RB) index of the CORESET to a minimum RB index of the SS / PBCH block based on the index, wherein the CORESET is for a Type 0-Physical Downlink Control Channel (PDCCH) Common Search Space (CSS) set; and monitoring the Type 0-PDCCH CSS set associated with the CORESET in the shared spectrum based on the offset, Wherein, based on the subcarrier spacing SCS of the SS / PBCH block being 30 kHz, the offset is determined to be N1 for the index, The SCS of the SS / PBCH block is 15 kHz, and for the index, the offset is determined to be N2. Where N1 and N2 are non-negative integers, and Among them, N2=2*N1+10.

12. The device according to claim 11, in, Based on the index being the first value, N1=0 and N2=10, Wherein, based on the index being the second value, N1=1 and N2=12, and Wherein, based on the index being the third value, N1=2 and N2=14.

13. The device according to claim 11, in, The center frequency of the SS / PBCH block corresponds to the synchronization grid.

14. The apparatus according to claim 11, in, The operations also include detecting a PDCCH from the Type 0-PDCCH CSS based on the monitoring.

15. The device according to claim 14, in, The operation includes receiving system information via a physical downlink shared channel (PDSCH) related to the PDCCH.

16. A method performed by a base station BS, the method comprising the following steps: Send synchronization signal / physical broadcast channel SS / PBCH blocks in the shared spectrum, The SS / PBCH block includes an index associated with an index-based offset from a minimum resource block (RB) index of a control resource set (CORESET) to a minimum RB index of the SS / PBCH block, wherein the CORESET is for a Type 0-physical downlink control channel (PDCCH) common search space (CSS) set; transmitting a PDCCH on a Type 0-PDCCH CSS set associated with the CORESET in the shared spectrum, The index is mapped to an offset value N1 based on a subcarrier spacing SCS of 30 kHz for the SS / PBCH block, and is mapped to an offset value N2 based on a SCS of 15 kHz for the SS / PBCH block. Where N1 and N2 are non-negative integers, and Wherein, for the index, N2=2*N1+10.

17. A base station (BS), comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and configured, when executed, to cause the at least one processor to perform operations comprising: Send synchronization signal / physical broadcast channel SS / PBCH blocks in the shared spectrum, The SS / PBCH block includes an index associated with an index-based offset from a minimum resource block (RB) index of a control resource set (CORESET) to a minimum RB index of the SS / PBCH block, wherein the CORESET is for a Type 0-physical downlink control channel (PDCCH) common search space (CSS) set; transmitting a PDCCH on a Type 0-PDCCH CSS set associated with the CORESET in the shared spectrum, The index is mapped to an offset value N1 based on a subcarrier spacing SCS of 30 kHz for the SS / PBCH block, and is mapped to an offset value N2 based on a SCS of 15 kHz for the SS / PBCH block. Where N1 and N2 are non-negative integers, and Wherein, for the index, N2=2*N1+10.

Images