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

Abstract

The present invention relates to a wireless communication system, and particularly, to a method including steps of receiving group common DCI including slot format information and channel occupancy duration information, determining a slot format of one or more slots based on the slot format information and the channel occupancy duration information, and performing communication based on the determined slot format of the one or more slots, and an apparatus therefor.

Description

Technical Field

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

[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, which support communication among multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). Summary of the Invention

[0003] Technical issues

[0004] A method and apparatus are provided for efficiently performing wireless signal transmission and reception processes.

[0005] Those skilled in the art will recognize that the purposes that can be achieved by using this disclosure are not limited to those specifically described above, and that the above and other purposes that can be achieved by this disclosure will become clearer from the following detailed description.

[0006] Technical solution

[0007] In a first aspect of this disclosure, a method for performing communication by a terminal in a wireless communication system may include: receiving Group Common Downlink Control Information (DCI) including time slot format information and channel occupancy duration information; determining a time slot format for one or more time slots based on the time slot format information and the channel occupancy duration information; and performing communication based on the determined time slot format for one or more time slots. The time slot format information may correspond to N time slot formats, each time slot format corresponding to a symbol configuration of a corresponding time slot within N consecutive time slots, where N may be an integer greater than or equal to 1. The channel occupancy duration information may correspond to a channel occupancy duration comprising M consecutive time slots, where M may be an integer greater than or equal to 1.

[0008] In a second aspect of this disclosure, a terminal used in a wireless communication system may include: at least one processor; and at least one computer memory operably coupled to the at least one processor and configured to cause the at least one processor to perform operations when executed. The operations may include: receiving Group Common Downlink Control Information (DCI) including time slot format information and channel occupancy duration information; determining a time slot format for one or more time slots based on the time slot format information and the channel occupancy duration information; and performing communication based on the determined time slot format for the one or more time slots. The time slot format information may correspond to N time slot formats, each time slot format corresponding to a symbol configuration of a corresponding time slot within N consecutive time slots, where N may be an integer greater than or equal to 1. The channel occupancy duration information may correspond to a channel occupancy duration comprising M consecutive time slots, where M may be an integer greater than or equal to 1.

[0009] In a third aspect of this disclosure, an apparatus for a terminal may include: at least one processor; and at least one computer memory operatively coupled to the at least one processor and configured to cause the at least one processor to perform operations when executed. The operations may include: receiving Group Common Downlink Control Information (DCI) including time slot format information and channel occupancy duration information; determining a time slot format for one or more time slots based on the time slot format information and the channel occupancy duration information; and performing communication based on the determined time slot format for the one or more time slots. The time slot format information may correspond to N time slot formats, each time slot format corresponding to a symbol configuration of a corresponding time slot within N consecutive time slots, where N may be an integer greater than or equal to 1. The channel occupancy duration information may correspond to a channel occupancy duration comprising M consecutive time slots, where M may be an integer greater than or equal to 1.

[0010] In a fourth aspect of this disclosure, a computer-readable storage medium is provided including at least one computer program configured to cause at least one processor to perform operations when executed. The operations may include: receiving Group Common Downlink Control Information (DCI) including time slot format information and channel occupancy duration information; determining a time slot format for one or more time slots based on the time slot format information and the channel occupancy duration information; and performing communication based on the determined time slot format for the one or more time slots. The time slot format information may correspond to N time slot formats, each time slot format corresponding to a symbol configuration of a corresponding time slot within N consecutive time slots, where N may be an integer greater than or equal to 1. The channel occupancy duration information may correspond to a channel occupancy duration comprising M consecutive time slots, where M may be an integer greater than or equal to 1.

[0011] Based on the assumption that N is less than M, communication can be performed under the premise that the N time slot formats sequentially correspond to the time slot following the Nth time slot in the channel occupancy duration.

[0012] Based on the assumption that N is less than M, communication can be performed under the assumption that the last time slot format in N time slot formats can repeatedly correspond to the time slot following the Nth time slot in the channel occupancy duration.

[0013] Since N is greater than M, communication can be performed only during the channel occupancy duration based on the time slot format information, while ignoring the time slot formats after the Mth time slot format among the N time slot formats.

[0014] Based on the assumption that N is greater than M, communication can be performed in the time slot formats after the Mth time slot format among the N time slot formats, where only the UL symbol is valid.

[0015] Beneficial effects

[0016] According to this disclosure, wireless signals can be transmitted and received efficiently in a wireless communication system.

[0017] Those skilled in the art will recognize that the effects achievable using this disclosure are not limited to those specifically described above, and that other advantages of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. Attached Figure Description

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

[0019] Figure 1 The physical channel in a 3GPP system, which serves as an exemplary wireless communication system, and a general signal transmission method using the physical channel are illustrated.

[0020] Figure 2 The structure of a radio frame is illustrated.

[0021] Figure 3 An example of a time-slot resource grid is shown.

[0022] Figure 4 This illustrates the mapping of physical channels within a time slot.

[0023] Figure 5 An example of the ACK / NACK transmission process is shown.

[0024] Figure 6 The Physical Uplink Shared Channel (PUSCH) transmission process is illustrated.

[0025] Figure 7 An exemplary wireless communication system supporting unlicensed frequency bands is illustrated.

[0026] Figure 8 An exemplary method for occupying resources in an unlicensed frequency band is illustrated.

[0027] Figure 9 The Channel Access Procedure (CAP) is illustrated.

[0028] Figure 10 An example of CAP-BW is shown.

[0029] Figures 11 to 16 The methods presented in this specification are illustrated.

[0030] Figure 17 An example of a network access procedure applied to this disclosure is provided.

[0031] Figures 18 to 21 The communication system 1 and wireless device used in this disclosure are illustrated. Detailed Implementation

[0032] The following technologies can be used in various radio 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), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Global Microwave Access Interoperability (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3GPP Long Term Evolution (LTE) is part of Evolved UMTS using E-UTRA (E-UMTS), and LTE-Advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolution of 3GPP LTE / LTE-A.

[0033] With an increasing number of communication devices requiring greater communication capacity, the need has arisen for enhanced mobile broadband communications compared to conventional radio access technologies (RATs). Massive machine-type communications (MTC) providing various services to multiple interconnected devices and things anytime, anywhere is one of the key challenges to be addressed in next-generation communications. The design of communication systems for services 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 being discussed. For convenience, this technology is referred to herein as NR or New RAT.

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

[0035] In a radio access system, a user equipment (UE) receives information from a base station (BS) on the DL and transmits information to the BS on the UL. The information transmitted and received between the UE and the BS includes general data and various types of control information. Depending on the type / purpose of the information transmitted and received between the BS and the UE, there are many physical channels.

[0036] Figure 1 The physical channel in the 3GPP system and the general signal transmission method using the physical channel are illustrated.

[0037] When the UE powers on or enters a new cell, it 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 the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH). The UE synchronizes its timing with the BS based on the PSS / SSS and obtains information such as the cell identifier (ID). Furthermore, the UE can obtain information broadcast within 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 the downlink reference signal (DL RS).

[0038] Subsequently, to establish a connection with the BS, the UE can perform a random access procedure with the BS (S103 to S106). Specifically, the UE can transmit a preamble on the Physical Random Access Channel (PRACH) (S103), and can receive the PDCCH for the preamble and the Random Access Response (RAR) on the PDSCH corresponding to the PDCCH (S104). Then, the UE can transmit the Physical Uplink Shared Channel (PUSCH) using the scheduling information in the RAR (S105), and perform a contention resolution procedure including receiving the PDCCH and the PDSCH signal corresponding to the PDCCH (S106).

[0039] Following the above process, during the general UL / DL signal transmission, the UE can receive PDCCH and / or PDSCH from the BS (S107) and send the Physical Uplink Shared Channel (PUSCH) and / or 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 and Request Acknowledgment / Negative Acknowledgment (HARQ-ACK / NACK), Scheduling Request (SR), Channel State Information (CSI), etc. CSI includes Channel Quality Indicator (CQI), Precoding Matrix Index (PMI), Rank Indicator (RI), etc. Typically, UCI is sent on the PUCCH. However, if control information and data should be sent simultaneously, they can be sent on the PUSCH. Furthermore, the UE can periodically send UCI on the PUSCH when receiving requests / commands from the network.

[0040] Figure 2 The structure of a radio frame is illustrated.

[0041] In NR, UL and DL transmissions are frame-based. Each radio frame is 10ms long and is divided into two 5ms half-frames. Each half-frame is further divided into five 1ms subframes. Subframes are divided into one or more time slots, and the number of time slots within 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 using normal CP, each time slot includes 14 OFDM symbols. When using extended CP, each time slot includes 12 OFDM symbols. Symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) symbols).

[0042] Table 1 illustrates, for example, how the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS under normal CP conditions.

[0043] [Table 1]

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

[0045] *N slot symb Number of symbols in a time slot

[0046] *N frame，u slot Number of time slots in a frame

[0047] *N subframe，u slot Number of time slots in a subframe

[0048] Table 2 illustrates how 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 case of extended CP.

[0049] [Table 2]

[0050] SCS(15*2^u) <![CDATA[N slot stmb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe，u slot ]]> 60kHz (u=2) 12 40 4

[0051] The frame structure is just an example, and the number of subframes, the number of time slots, and the number of symbols in a frame can be changed in various ways.

[0052] In NR systems, different sets of OFDM(A) parameters (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for a single UE. Therefore, the (absolute time) duration of time resources (e.g., subframes, slots, or transmission time intervals (TTI)) consisting of the same number of symbols (for convenience, referred to as time units (TU)) can be configured differently across aggregated cells. Symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) symbols).

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

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

[0055] [Table 3]

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

[0057] Figure 3 An example of a resource grid during the duration of a time slot is illustrated. A time slot comprises multiple symbols in the time domain. For example, a time slot comprises 14 symbols in the normal CP case and 12 symbols in the extended CP case. A carrier comprises 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 portion (BWP) can be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can take place in active BWPs, and only one BWP can be activated for a UE. Each element in the resource grid can be referred to as a resource element (RE), and a complex symbol can be mapped to that resource element.

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

[0059] The PDCCH delivers the DCI. For example, the PDCCH (i.e., the DCI) can carry information about the transmission format and resource allocation of the DL-SCH, resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about the DL-SCH, resource allocation information about higher-layer control messages such as RARs transmitted on the PDCCH, transmission power control commands, information about the activation / release of configured schedules, etc.

[0060] Various DCI formats are provided based on the information in the DCI.

[0061] Table 4 illustrates, for example, the DCI format transmitted on the PDCCH.

[0062] [Table 4]

[0063]

[0064] DCI includes Cyclic Redundancy Check (CRC). Depending on the owner or purpose of the PDCCH, the CRC is masked using various identifiers (IDs) (e.g., Radio Network Temporary Identifier (RNTI)). For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., Cell RNTI (C-RNTI)). If the PDCCH is used for paging messages, 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 masked by the System Information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by the Random Access RNTI (RA-RNTI).

[0065] Table 5 illustrates, for example, the uses and transport channels of the PDCCH according to the RNTI. The transport channel is associated with the data carried by the PDSCH / PUSCH scheduled by the PDCCH.

[0066] [Table 5]

[0067]

[0068] The modulation scheme of the PDCCH is fixed (e.g., Quadrature Phase Shift Keying (QPSK)), and a PDCCH consists of 1, 2, 4, 8, or 16 Control Channel Elements (CCEs) depending on the Aggregation Level (AL). A CCE consists of six Resource Groups (REGs). A REG is defined as an OFDMA symbol and a (P)RB. The PDCCH is transmitted via a Control Resource Set (CORESET). A CORESET corresponds to a set of physical resources / parameters used to carry the PDCCH / DCI within a BWP. For PDCCH reception, the UE can monitor (e.g., blindly decode) a set of PDCCH candidates in the CORESET. A PDCCH candidate represents a CCE monitored by the UE for PDCCH reception / detection. PDCCH monitoring can be performed in one or more CORESETs in each active DLBWP in each active cell configured with PDCCH monitoring. A set of PDCCH candidates monitored by the UE is defined as a PDCCH Search Space (SS) set. The SS set can be a Common Search Space (CSS) set or a UE-Specific Search Space (USS) set.

[0069] Table 6 provides an example of a PDCCH SS.

[0070] [Table 6]

[0071]

[0072] PUCCH transmits uplink control information (UCI). UCI includes the following information.

[0073] -SR: Information used to request UL-SCH resources.

[0074] - HARQ-ACK: A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet has been successfully received. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term "HARQ-ACK" is used interchangeably with HARQACK / NACK and ACK / NACK.

[0075] -CSI: Feedback information for the DL channel. MIMO-related feedback information includes RI and PMI.

[0076] Table 7 illustrates exemplary PUCCH formats. PUCCH formats can be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4) based on the duration of PUCCH transmission.

[0077] [Table 7]

[0078]

[0079] Figure 5 The ACK / NACK transmission process is illustrated. (Refer to...) Figure 5 The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates the DL assignment to the PDSCH offset K0 and the PDSCH to the HARQ-ACK reporting offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0080] - Frequency domain resource assignment: Indicates the set of RBs assigned to the PDSCH.

[0081] - Time-domain resource assignment: Indicates the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot, as well as K0.

[0082] -PDSCH to HARQ_ Feedback Timing Indicator: Indicates K1.

[0083] - HARQ process number (4 bits): The HARQ process ID that indicates the data (e.g., PDSCH or TB).

[0084] -PUCCH Resource Indicator (PRI): Indicates the PUCCH resource used for UCI transmission among multiple PUCCH resources in the PUCCH resource set.

[0085] After receiving a PDSCH in time slot #(n+K0) according to the scheduling information of time slot #n, the UE can transmit a UCI on the PUCCH in time slot #(n+K1). The UCI includes a HARQ-ACK response to the PDSCH. When the PDSCH is configured to carry at most one TB, the HARQ-ACK response can be configured as one bit. When the PDSCH is configured to carry up to two TBs, the HARQ-ACK response can be configured as two bits without spatial binding and as one bit with spatial binding configured. When time slot #(n+K1) is designated as the timing for HARQ-ACK transmission of multiple PDSCHs, the UCI transmitted in time slot #(n+K1) includes HARQ-ACK responses to multiple PDSCHs.

[0086] Figure 6 An exemplary PUSCH transmission process is illustrated. (Refer to...) Figure 6 The UE can detect the PDCCH in time slot #n. The PDCCH may include UL scheduling information (e.g., DCI format 0_0 or DCI format 0_1). DCI format 0_0 and DCI format 0_1 ​​may include the following information.

[0087] - Frequency domain resource assignment: Indicates the set of RBs allocated to the PDSCH.

[0088] - Time-domain resource assignment: Specifies the time slot offset K2 for the start position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH in the time slot. The start symbol and length of the PUSCH can be indicated by the start and length indicator values ​​(SLIV) or separately.

[0089] Then, the UE can transmit PUSCH in time slot #(n+K2) according to the scheduling information in time slot #n. PUSCH includes UL-SCH TB. When PUCCH transmission time and PUSCH transmission time overlap, UCI can be transmitted via PUSCH (PUSCH-equipped).

[0090] Figure 7Exemplary wireless communication systems supporting unlicensed frequency bands applicable to this disclosure are illustrated. In the following description, a cell operating in a licensed frequency band (L-band) is defined as an L-cell, and the carrier of an L-cell is defined as (DL / UL)LCC. A cell operating in an unlicensed frequency band (U-band) is defined as a U-cell, and the carrier of a U-cell is defined as (DL / UL)UCC. The carrier / carrier frequency of a cell may refer to the cell's operating frequency (e.g., center frequency). The cell / carrier (e.g., CC) is commonly referred to as a cell.

[0091] When carrier aggregation is supported, a UE can use multiple aggregated cells / carriers to exchange signals with the BS. 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 transmitted and received only on the PCC. Data can be transmitted and received on both the PCC and SCC. Figure 7 (a) illustrates a scenario where the UE and BS exchange signals on both the LCC and UCC (Non-Standalone (NSA) mode). In this case, the LCC and UCC can be set to PCC and SCC, respectively. When the UE is configured with multiple LCCs, a specific LCC can be set to PCC, and the remaining LCCs can be set to SCC. Figure 7 (a) corresponds to the LAA of the 3GPP LTE system. Figure 7 (b) illustrates a scenario where the UE and 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 the PCC, and the remaining UCCs can be set as the SCC. Both NSA and SA modes can be supported in the U-band of the 3GPP NR system.

[0092] The signal transmission / reception operations in the unlicensed band described in this disclosure can be performed based on the deployment scenarios described above (unless otherwise stated). Furthermore, the following definitions may be applied to the terminology used herein.

[0093] - Channel: can consist of consecutive RBs (where the channel access procedure is performed in a shared spectrum) and can refer to a carrier or a portion of a carrier.

[0094] - Channel Access Procedure (CAP): This refers to the process used to assess channel availability based on sensing in order to determine whether other communication nodes are using the channel before signal transmission. The basic unit for sensing is the duration T. sl= 9µs sensing time slot. If the BS or UE senses the channel during the sensing time slot duration, and the power detected is less than the energy detection threshold X for at least 4µs within the sensing time slot duration. Thresh Then the duration of the sensing time slot T sl It is considered to be in an idle state. Otherwise, the sensing time slot duration T sl =9us is considered a busy state. CAP can be referred to as Listen Before Talk (LBT).

[0095] - Channel occupancy: This refers to the corresponding transmission performed by the BS / UE on the channel after CAP is executed.

[0096] - Channel Occupancy Time (COT): Refers to the total time that the BS / UE and any BS / UE sharing the channel occupancy can perform transmissions on the channel after the BS / UE performs CAP. When determining COT, the gap period is also counted in COT when the transmission gap is 25µs or less. COT can be shared for transmissions between the BS and the corresponding UE.

[0097] -DL transmission burst: Defined as a group of transmissions from the BS with no gaps exceeding 16µs. Transmissions from the BS separated by gaps exceeding 16µs are considered separate DL transmission bursts. In a DL transmission burst, the BS can perform a transmission after the gap even without sensing channel availability.

[0098] - UL Transmission Burst: Defined as a set of transmissions from the UE with no gaps exceeding 16µs. Transmissions from the UE separated by gaps exceeding 16µs are considered separate UL transmission bursts. Within a UL transmission burst, the UE can perform a transmission after the gap even without sensing channel availability.

[0099] Figure 8 An exemplary method for occupying resources in an unlicensed frequency band is illustrated. A communication node (e.g., BS, UE) within the unlicensed frequency band must determine whether the channel is being used by other communication nodes before signal transmission. To this end, a communication node in the unlicensed frequency band can perform a Carrier Sense (CAP) to access the channel on which transmission is performed. CAP can be performed based on sensing. For example, a communication node can first perform Carrier Sense (CS) before signal transmission to check whether other communication nodes are transmitting signals. The determination that other communication nodes are not transmitting signals is defined as Acknowledging Clear Channel Assessment (CCA). When a CCA threshold (e.g., X) predefined or set by a higher layer (e.g., RRC) exists... ThreshIf energy above the CCA threshold is detected on the channel, the communication node determines the channel state to be busy. Otherwise, the channel state can be determined to be idle. When the channel state is determined to be idle, the communication node can begin transmitting signals in the unlicensed frequency band.

[0100] Table 8 illustrates the types of CAP exemplarily.

[0101] [Table 8]

[0102]

[0103] Figure 9 This is a flowchart of the CAP operation used by the BS to transmit downlink signals through the unlicensed frequency band. (Refer to...) Figure 9 The BS first senses the channel during the delay duration T. d Whether the channel is idle during the duration of the additional sensing time slot is determined, and then transmission can be performed when the counter N reaches 0 (S1234). Here, the counter N is adjusted by sensing the channel for the duration of the additional sensing time slot according to the following process.

[0104] Step 1)(S1220) Set N = N init Here, N init It is uniformly distributed between 0 and CW p A random value between [a certain range]. Then, proceed to step 4.

[0105] Step 2)(S1240) If N>0 and BS selects a decrementing counter, then set N=N-1.

[0106] Step 3)(S1250) senses the channel for the duration of the additional sensing time slot. Then, if the duration of the additional sensing time slot is idle (Y), proceed to step 4. If not (N), proceed to step 5.

[0107] Step 4)(S1230) If N = 0 (Y), then terminate CAP (S1232). Otherwise (N), proceed to step 2.

[0108] Step 5)(S1260) Sensing the channel until the additional delay duration T d The system detects a busy sensing slot or an additional delay duration T. d All sensing time slots within were detected as idle.

[0109] Step 6)(S1270) If for the additional delay duration T d If the channel is sensed as idle (Y) for all sensing time slot durations, proceed to step 4. If not (N), proceed to step 5.

[0110] Table 9 provides an example of m applied to CAP. p The minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW size vary depending on the channel access priority category.

[0111] [Table 9]

[0112]

[0113] Delay duration T d By m p A continuous sensing time slot T sl (9us) + duration T f The duration is composed of (16us). T f The sensing time slot duration T is included at the beginning of the 16µs duration. sl .

[0114] Implementation method: Signal transmission in NR-U

[0115] For the UE, in an unlicensed frequency band, only a single carrier can be configured, or multiple carriers can be aggregated / configured. In this case, up to four BWPs can be configured for each carrier, and only one BWP can be activated. When the frequency band unit forming the basis of the CAP in the unlicensed frequency band is defined as a CAP-BW, each carrier / BWP can correspond to one CAP-BW, or can correspond to multiple CAP-BWs. The size of a CAP-BW can be a fixed value, or it can be set differently depending on the network (or BS) configuration. For example, the size of a CAP-BW can be fixed at 20MHz, or it can be variably set within the carrier based on higher-layer (e.g., RRC) signaling and / or DCI. When CAP-BW configuration information is not configured, the CAP-BW size / deployment can follow predefined values ​​based on the frequency region of the carrier. A CAP-BW can consist of consecutive RBs (hereinafter referred to as an RB set). In this disclosure, CAP-BW and RB set can have the same meaning.

[0116] Figure 10 This example illustrates the configuration of CAP-BW in a carrier wave. (See reference...) Figure 10 Three component carriers (CCs) are configured. CC#1 can correspond to two CAP-BWs, and each of CC#2 and #3 can correspond to one CAP-BW. CC#1 / #2 can be defined as in-band carrier aggregation (CA), and CC#1 / #2 and CC#3 can be defined as inter-band CA.

[0117] In this scenario, the BS can perform CAP for each CAP-BW and can transmit DL bursts in (CAP-successful) CAP-BWs, skipping the transmission of DL bursts in other (CAP-failed) CAP-BWs based on the CAP result. Furthermore, in CAP-BWs that have been occupied for a predetermined time through CAP, a portion of the occupancy time can be shared with UL bursts. Additionally, it is advantageous to notify the UE of the BS's frequency domain occupancy information at least in the following aspects.

[0118] - The UE can perform power saving by skipping PDCCH monitoring in CAP-BWs that are known not to be occupied by the BS (e.g., CAP-BW off state). Here, skipping PDCCH monitoring can include skipping monitoring of DCI formats used for data scheduling (e.g., DCI format 0_X, DCI format 1_X). However, PDCCH monitoring for receiving group common DCI formats (e.g., DCI format 2_0) during the CAP-BW off duration can be performed with exception.

[0119] - The UE can save power by skipping CSI / RRM (Radio Resource Management) / RLM (Radio Link Monitoring) measurements in CAP-BWs that are known to be unoccupied by the BS. For example, when CSI-RS is configured to be transmitted in CAP-BW closing slots, the UE can skip channel measurements based on CSI-RS in CAP-BW closing slots. Alternatively, CSI-RS in CAP-BW closing slots can be excluded from the channel measurement process.

[0120] - For CAP used for UL burst transmission shared with DL bursts occupied by BS, UL transmission may be allowed if the channel is idle for a certain period of time without random backoff, or even if the channel is not checked for idle / busy conditions.

[0121] In existing NR systems, DL / UL direction can be dynamically signaled via DCI. Specifically, the DCI can include SFI fields for multiple cells, and the location of the SFI field for a cell in the DCI bitstream can be determined based on the offset set for each cell. For example, assume the SFI field corresponding to cell #1 is represented by 3 bits and the SFI field corresponding to cell #2 is represented by 5 bits. In this case, in a DCI for an SFI indication with a total size of 100 bits, the segment corresponding to cell #1 could be 3 bits starting from N1 (e.g., N1 = 14) bits, and the segment corresponding to cell #2 could be 5 bits starting from N2 (e.g., N2 = 50) bits. N1 and N2 are set for each cell. The SFI field includes an SFI-index. The SFI-index corresponds to a SlotFormatCombination, which indicates the slot format for K (=> 1) consecutive slots. The slot format indicates DL / UL / flexible for each symbol in the slot. For each SFI-index, K can also be set differently. In the existing NR, the DCI used for SFI indication can correspond to DCI format 2_0 as a group common PDCCH, and can be scrambled with SFI-RNTI. The UE can perform communication in a time slot based on the time slot format. For example, in a time slot, PDCCH monitoring / reception, PDSCH reception, and / or CSI-RS reception / measurement can be performed in DL symbols, and PUCCH transmission, PUSCH transmission, and / or SRS transmission can be performed in UL symbols.

[0122] Table 10 illustrates the slot format exemplarily. Here, D represents the DL symbol, U represents the UL symbol, and F represents the flexible symbol.

[0123] [Table 10]

[0124]

[0125] Below, this disclosure proposes a method for notifying DL / UL direction and / or frequency domain occupancy information. Specifically, this disclosure proposes a method for notifying DL / UL direction information and / or frequency domain occupancy information about a BS for each CAP-BW (or each BWP / carrier, each CAP-BW / BWP / carrier group). The proposals of this disclosure can be applied, with limitation, to carriers operating in unlicensed frequency bands (or shared spectrum bands).

[0126] In this disclosure, physical layer control information (e.g., DCI) can be used to signal DL / UL direction and / or frequency domain occupancy information. For simplicity, in this disclosure, DCI is referred to as Channel Occupancy-DCI (CO-DCI). CO-DCI can be configured based on existing DCI format 2_0. As an example, CO-DCI can be defined in DCI format 2_0. In this case, to indicate CO-DCI information (e.g., DL / UL direction and / or frequency domain occupancy information), new fields can be added to DCI format 2_0, or some fields of DCI format 2_0 can be reinterpreted. Alternatively, a new group common DCI format can be defined for CO-DCI. Alternatively, CO-DCI can be configured based on existing UE-specific DCI formats. For example, CO-DCI can be defined with existing UE-specific DCI formats. In this case, to indicate CO-DCI information, new fields can be added to the existing UE-specific DCI format, or some fields of the existing UE-specific DCI format can be reinterpreted. Alternatively, a new UE-specific DCI format can be defined for CO-DCI.

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

[0128] [Method #1] Configure the SFI field for each CAP-BW in CO-DCI.

[0129] For example, in Figure 10 In the CA scenario, N1 can be set for CAP-BW#1-1, N2 can be set for CAP-BW#1-2, N3 can be set for CAP-BW#2-1, and N4 can be set for CAP-BW#3-1, such as... Figure 11 As shown. Therefore, the SFI for each CAP-BW can be indicated in the CO-DCI.

[0130] [Method #1-1] Configure the SFI field in CO-DCI for each CAP-BW, where a specific CAP-BW can share... Enjoy the same offset value

[0131] exist Figure 11In this configuration, all or some of N1 / N2 / N3 / N4 can be set to the same value. For example, CAP-BW#1-1 / #1-2 belong to the same carrier. Therefore, assuming the BS indicates the same D / U direction for CAP-BW#1-1 / #1-2, DCI overhead can be reduced by indicating the D / U direction of CAP-BW#1-1 / #1-2 in the CO-DCI using the same field. That is, the D / U direction (e.g., SFI field) can be configured for each carrier. However, since the on / off (or available / unavailable) state of CAP-BW#1-1 / #1-2 can also be shared, it is not necessary to indicate the on / off state for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0132] Alternatively, the transmission mode associated with the transmission method for each CAP-BW of the BS can be configured individually. For example, the signaling mode can be individually configured as either mode 1 (hereinafter, Mode 1) where transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful, or mode 2 (hereinafter, Mode 2) where transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful. When configuring Mode 1, the UE can assume that the SFI field is shared for all CAP-BWs belonging to the carrier / active BWP (i.e., the same offset value is set, or an offset value is set for each cell). When configuring Mode 2, the UE can assume that the SFI field is configured for each CAP-BW belonging to the carrier / active BWP (i.e., a separate offset value is set, or an offset value is set for each CAP-BW).

[0133] In [Method #1] and [Method #1-1], a specific state of the SFI field can indicate that the CAP-BW is off (that is, the BS does not attempt to transmit due to CAP failure). For example, when the SFI field is configured to 3 bits and set to '000', it can indicate that the CAP-BW corresponding to the SFI field is off. As another example, the SlotFormatCombination can be used to indicate the off state of the CAP-BW when it is not linked to a specific state of the SFI field (e.g., SFI-index). The size of the SFI field can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when the value of the SFI-index for which the SlotFormatCombination is not configured is signaled, the UE can recognize that the corresponding CAP-BW is off.

[0134] When a CAP-BW is in a closed state, UL slot / symbol information about an open CAP-BW belonging to the same carrier / BWP can be communicated to the closed CAP-BW. As an example, CAP-BW#1-1 can be signaled as closed, but CAP-BW#1-2 can be signaled as open (when separate SFI fields are configured for CAP-BW#1-1 and CAP-BW#1-2). In this case, for example, if all symbols for slot #k / k+1 of CAP-BW#1-2 are signaled as UL via CO-DCI, the UE can recognize that CAP-BW#1-1 is also UL for slot #k / k+1. This is because, under the assumption that a BS operating in an unlicensed band typically operates through a single radio frequency (RF) module, it is considered impossible to perform transmission in an adjacent band while simultaneously performing reception in an adjacent band. Therefore, the UE can recognize that during slot #k / k+1, PDCCH monitoring is not performed in CAP-BW#1-1 or CAP-BW#1-2, and configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured licensed PUSCH, etc.) are allowed.

[0135] (For all cells or a portion thereof configured in the unlicensed frequency band) the channel occupancy or DL ​​burst of the BS can be divided into two durations. One is the duration within the first k time slots (duration 1), and the other is the duration after the first k time slots (duration 2). Here, k can be predefined as an integer greater than or equal to 1, or it can be set via separate RRC signaling. The reason for dividing the channel occupancy or DL ​​burst of the BS into two durations is that the BS does not know in which period the BS will actually successfully perform CAP-BW, and therefore the CAP-BW state information is uncertain in duration 1. Therefore, even if CAP-BW is indicated to be on, duration 1 can be handled similarly to the case of CAP-BW being off. For example, the UE can perform PDCCH monitoring in the same way as during the duration of CAP-BW being off (e.g., the same as PDCCH monitoring before CO-DCI is discovered), and CSI measurement can be omitted. On the other hand, in duration 2, it can be clearly determined whether CAP-BW is on or off based on the CAP-BW state information. Therefore, in duration 2, the UE can perform operations based on CAP-BW being on / off. For example, when CAP-BW is enabled, the UE can perform PDCCH monitoring based on a scheme defined for the duration of CAP-BW enabled (e.g., search space set / DCI format), and also perform CSI measurements. For example, PDCCH monitoring during the CAP-BW enabled duration may include DCI format 0_X / 1_X / 2_0 monitoring. On the other hand, when CAP-BW is disabled, the UE can perform PDCCH monitoring based on a scheme defined for the duration of CAP-BW disabled (e.g., search space set / DCI format), and may not perform (e.g., may omit / skip) CSI measurements. For example, during the CAP-BW disabled duration, PDCCH monitoring may include DCI format 2_0 monitoring, but may not include DCI format 0_X / 1_X monitoring.

[0136] Therefore, a specific state of the SFI field can indicate whether the corresponding CAP-BW (in the slot where CO-DCI was detected) belongs to the first transmission slot (e.g., DL burst) or to the first k slots during the duration occupied by the BS. For example, when the SFI field is configured to 3 bits and set to '111', it can indicate that the CAP-BW corresponding to the SFI field (in the slot where CO-DCI was detected) belongs to the first slot (or the first k slots) of the DL burst. As another example, this state can be utilized when the SlotFormatCombination is not linked to a specific state of the SFI field (e.g., SFI-index). The SFI field size can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when signaling the value of the SFI-index for which the SlotFormatCombination is not configured, the UE can recognize that the CAP-BW belongs to the first slot (or the first k slots) of the DL burst (in the slot where CO-DCI was detected). Then, the UE can assume DL (for all cells or a portion thereof configured in the unlicensed band) during the first time slot (or the first k time slots) of the DL burst. That is, in the time slot where CAP-BW is identified as belonging to the DL burst, all symbols can be assumed to be DL. Therefore, the UE can perform PDCCH monitoring in CAP-BW under the assumption that all symbols in the time slot are DL. In this method, in order to update the time slot format of CAP-BW, the BS can retransmit DCI format 2_0 within the same DL burst. For example, upon receiving SFI=111, the UE can only recognize that CAP-BW is the start of the DL burst and identify the time slot format (e.g., D / U / F) in the DL burst / COT based on the updated SFI information, while monitoring PDCCH as if CAP-BW were outside the DL burst.

[0137] Furthermore, (for all cells or a portion thereof configured in the unlicensed frequency band) the channel occupancy or DL ​​burst of the BS can be divided into two durations, and the search space set (or PDCCH) can be configured independently for each duration. For example, duration 1 can be defined as the duration within the first k timeslots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed frequency band), and duration 2 can be defined as the duration after the first k timeslots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed frequency band). Here, k can be predefined as an integer greater than or equal to 1, or can be set via separate RRC signaling. Specifically, when the UE signals / recognizes that CAP-BW belongs to the first time slot (or the first k time slots) of a DL burst (within the time slot where CO-DCI is detected), the UE can monitor PDCCHs belonging to a specific first search space set, which is configured to be monitored for a corresponding duration (e.g., duration 1) (for all cells or a portion thereof configured in the unlicensed band), or can monitor specific first PDCCHs configured to be monitored for a corresponding duration (e.g., duration 1). On the other hand, when the UE signals / recognizes that CAP-BW is enabled (in the time slot where CO-DCI is detected), but does not belong to the first time slot (or the first k time slots) of a DL burst, the UE can monitor PDCCHs belonging to a specific second search space set, which is configured to be monitored for a corresponding duration (e.g., duration 2) (for all cells or a portion thereof configured in the unlicensed band), or can monitor specific second PDCCHs configured to be monitored for a corresponding duration (e.g., duration 2). Here, the specific first search space set and the second search space set can be different from each other. For example, the specific first search space set and the second search space set can have different PDCCH monitoring periods. Furthermore, the specific first PDCCH and the second PDCCH can be different from each other. For example, the DCI formats transmitted on the specific first PDCCH and the second PDCCH can be different from each other. For example, the DCI format transmitted on the specific first PDCCH can include a group common DCI format (e.g., DCI format 2_0). Furthermore, the DCI format transmitted on the specific second PDCCH can include a DCI format for data scheduling (e.g., DCI format 0_X / 1_X) and a group common DCI format (e.g., DCI format 2_0).

[0138] [Method #2] Configure the SFI field in CO-DCI for each CAP-BW, and configure it through a separate field. Bitmap used to indicate the on / off state of each CAP-BW

[0139] In such Figure 10In the CA scenario shown, N1 can be set for CAP-BW#1-1, N2 can be set for CAP-BW#1-2, N3 can be set for CAP-BW#2-1, and N4 can be set for CAP-BW#3-1, as follows. Figure 12 As shown in the diagram, the on / off state and SFI can be indicated for each CAP-BW in the CO-DCI. Although the SFI field and the field indicating on / off are shown as being positioned consecutively in the diagram, the bit indicating the on / off state can be added after the SFI field, or the bitmap or bit field indicating on / off can be configured for each CAP-BW with a separate offset value.

[0140] [Method #2-1] Configure the SFI field in CO-DCI for each CAP-BW, and configure it through a separate field. A bitmap is set to indicate the on / off state of each CAP-BW, where specific CAP-BWs may share the SFI field and / or Bit field value indicating on / off state

[0141] exist Figure 12 In this configuration, all or some of N1 / N2 / N3 / N4 can be set to the same value. For example, CAP-BW#1-1 / #1-2 belong to the same carrier. Therefore, assuming the BS indicates the same D / U direction for CAP-BW#1-1 / #1-2, DCI overhead can be reduced by indicating the D / U direction of CAP-BW#1-1 / #1-2 in the CO-DCI using the same field. That is, the D / U direction (e.g., SFI field) can be configured for each carrier. However, since the on / off state of CAP-BW#1-1 / #1-2 can also be shared, it is not necessary to indicate the on / off state for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0142] Alternatively, the transmission mode associated with the transmission method for each CAP-BW of the BS can be configured individually. For example, the signaling mode can be individually configured as either a mode in which transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful (among all CAP-BWs) (hereinafter, Mode 1), or a mode 2 in which transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful (hereinafter, Mode 2). When configuring Mode 1, the UE can assume that the SFI field and bitmap field are shared for all CAP-BWs belonging to the carrier / active BWP (e.g., only 1 bit is configured for the bitmap field corresponding to the cell, and only one SFI field is configured). When configuring Mode 2, the UE can assume that the bit fields in the bitmap are configured for each CAP-BW belonging to the carrier / active BWP (that is, the offset value of the SFI field and the bitmap field are configured for each CAP-BW).

[0143] As another example, such as Figure 13 As shown, the offset value of N1 can be set jointly for the SFI field of CAP-BW#1-1 / 1-2 / 2-1 / 3-1. Furthermore, in the bitmap indicating the on / off state, the offset values ​​of N2 / N3 / N4 / N5 can be set for each CAP-BW, or all or some of N2 / N3 / N4 / N5 can be set to the same value. If N2 and N3 are set to the same value, the on / off state of CAP-BW#1-1 / #1-2 can also be shared, and therefore the on / off state does not need to be indicated for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0144] As another example, such as Figure 14As shown, for each CC (or BWP), a common offset N1 (relative to the SFI field position) can be set, and the bitmap indicating the on / off state can be signaled via a k-bit bitmap after the offset value (or before the offset value, after the end of the field size configured after N1, or after the field size configured after N1). Here, k can be equal to the number of CAP-BWs corresponding to the CC (or BWP), and can be less than or equal to the number of CAP-BWs corresponding to the CC (or BWP). When k is less than CAP-BW, the value of k can be signaled individually. Furthermore, when k is less than CAP-BW, the relationship between each bit of the k-bit bitmap and its corresponding CAP-BW can be pre-configured by the BS. When k = 1, the on / off states of CAP-BW#1-1 / #1-2 can also be shared, so the on / off state does not need to be indicated for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the bit values ​​corresponding to the on / off states of CAP-BW#1-1 / #1-2 belonging to the same carrier to the same position can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH, and / or CSI-RS transmissions) (or can be interpreted as meaning the guard band is not configured).

[0145] Alternatively, the transmission mode associated with the transmission method for each CAP-BW of the BS can be configured individually. For example, the signaling mode can be individually configured as either mode 1 (hereinafter, mode 1) where transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful, or mode 2 (hereinafter, mode 2) where transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful. When configuring mode 1, the UE can assume that the bitmap field indicating the on / off state is shared for all CAP-BWs belonging to the carrier / active BWP (that is, only 1 bit is configured for the bitmap field corresponding to the cell). Alternatively, if the bit field in the bitmap is configured for each CAP-BW belonging to the carrier / active BWP when configuring mode 1, the UE can assume that only '1' or '0' is signaled in the bitmap. When configuring mode 2, the UE can assume that the bit fields in the configuration bitmap are configured for each CAP-BW belonging to the carrier / active BWP (that is, the offset value of the bitmap field is set for each CAP-BW).

[0146] In [Method #2] and [Method #2-1], the UE can recognize that if the 1-bit information corresponding to each CAP-BW is '0' (or '1'), the corresponding CAP-BW is off, and if the information is '1' (or '0'), the corresponding CAP-BW is on. When a CAP-BW is off, UL slot / symbol information about an on CAP-BW belonging to the same carrier / BWP or the same frequency band as that CAP-BW can be communicated to the off CAP-BW. As an example, CAP-BW#1-1 can be signaled as off, but CAP-BW#1-2 can be signaled as on (when the on / off information about CAP-BW#1-1 and the on / off information about CAP-BW#1-2 are signaled through separate bit fields, and the SFI field is signaled publicly). In this scenario, for example, if the CO-DCI signals that all symbols for slot #k / k+1 of CAP-BW#1-2 are UL (Unlicensed), the UE can recognize that CAP-BW#1-1 is also UL for slot #k / k+1. This is because, under the assumption that a BS operating in an unlicensed band typically operates through a single radio frequency (RF) module, it is considered impossible to perform transmission and reception simultaneously in adjacent bands. Therefore, the UE can recognize that during slot #k / k+1, PDCCH monitoring is not performed in either CAP-BW#1-1 or CAP-BW#1-2, and configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured licensed PUSCH, etc.) are permitted.

[0147] Alternatively, even if CAP-BW is signaled as being off, the UE can recognize that the UL information on the SFI signaling corresponding to CAP-BW is valid. For example, when CAP-BW#1-1 is signaled as off, and all symbols in time slot #k / k+1 are signaled as DL and all symbols in time slot #k+2 / k+3 are signaled as UL for CAP-BW#1-1, the UE can recognize time slot #k+2 / k+3 as UL and ignore the SFI signaling in time slot #k / k+1. In this case, the UE can recognize that PDCCH monitoring is not performed in CAP-BW#1-1 during time slots #k / k+1 / k+2 / k+3, and that configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured authorized PUSCH, etc.) are allowed during time slot #k+2 / k+3.

[0148] Alternatively, the specific state of the SFI field and / or bitmap field can indicate whether the CAP-BW (in the time slot where the CO-DCI is detected) belongs to the first transmission time slot (e.g., DL burst) or to the first k time slots during the duration occupied by the BS. Here, the value of k can be predefined as an integer greater than or equal to 1, or it can be set by separate RRC signaling. As one method, when all bits in the bitmap corresponding to all CAP-BWs corresponding to the cell in which the CO-DCI is transmitted are off, it can indicate that the CAP-BW (in the time slot where the CO-DCI is detected) belongs to the first time slot (or the first k time slots) of the DL burst. Paradoxically, when the CO-DCI is transmitted from the cell, all CAP-BWs corresponding to the cell are off. Therefore, this transmission can be used for the aforementioned signaling. That is, through the CO-DCI transmission, this can indirectly indicate that the CAP-BW is on. Furthermore, through the CAP-BW on / off information, this can indicate that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst. For example, when a CO-DCI is sent on CC#1, if all the on / off information corresponding to CAP-BW#1-1 and CAP-BW#1-2 in the bitmap is off, this can indicate that CAP-BW#1-1 and CAP-BW#1-2 (in the time slot where the CO-DCI is detected) belong to the first time slot (or the first k time slots) of the DL burst.

[0149] Furthermore, a CO-DCI can be transmitted on CC#A, and all on / off information corresponding to CC#A / B can be included in the CO-DCI (i.e., cross-carrier indication). In this case, since the CAP-BW on / off information for CC#B is transmitted on another CC (e.g., CC#A), the actual transmission of a BS on CC#B may be ambiguous. Therefore, if all CAP-BWs of CC#A are off, the UE can assume that the DL burst even started on CC#B (even if the transmission actually only occurred on CC#A). On the other hand, if some or all of the CAP-BWs of CC#A are later updated to on, the information about CC#B can only be identified as truly off if all CAP-BW on / off information for CC#B is off. For example, a CO-DCI can be transmitted on CC#1, and all on / off information corresponding to CC#1 / 2 / 3 can be included in the CO-DCI. In this scenario, a UE receiving a CO-DCI in which all on / off information on the bitmaps corresponding to CAP-BW#1-1 / CAP-BW#1-2 / CAP-BW#2-1 / CAP-BW#3-1 is off can recognize that CC#2 and CC#3, as well as CC#1 (in the time slot where the CO-DCI is detected), belong to the first time slot (or the first k time slots) of the DL burst. Furthermore, a CO-DCI can be transmitted on CC#2, and all on / off information corresponding to CC#1 / 2 / 3 can be included in the CO-DCI. In this scenario, a UE receiving a CO-DCI on CC#2, including bitmap information corresponding to CAP-BW#1-1 = Off, CAP-BW#1-2 = Off, CAP-BW#2-1 = On, and CAP-BW#3-1 = Off, can recognize that either CAP-BW#1-1 or CAP-BW#1-2 belonging to CC#1 does not belong to the first time slot (or the first k time slots) of the DL burst, because CC#2 does not belong to the first time slot (or the first k time slots) of the DL burst (in the time slot where the CO-DCI is detected). Therefore, the UE can recognize that actual DL reception is unavailable in CAP-BW#1-1 and CAP-BW#1-2.

[0150] As an example, when the SFI field is configured to 3 bits and set to '111', it can indicate that the CAP-BW corresponding to the SFI field (in the time slot where CO-DCI is detected) belongs to the first time slot (or the first k time slots) of the DL burst. As another example, this state can be utilized when the SlotFormatCombination is not linked to a specific state (e.g., SFI-index) of the SFI field. The SFI field size can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when signaling the value of the SFI-index for which the SlotFormatCombination is not configured, the UE can recognize that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI is detected). The UE can then assume the DL (for all cells or a portion thereof configured in the unlicensed band) during the first time slot (or the first k time slots) of the DL burst. In other words, within the first (or the first k) time slots of the CAP-BW burst, where the CAP-BW is identified as belonging to the DL burst, all symbols can be assumed to be DL. Therefore, the UE can perform PDCCH monitoring within the CAP-BW under the assumption that all symbols in the time slot are DL. In this method, to update the time slot format of the CAP-BW, the BS can retransmit DCI format 2_0 within the same DL burst. For example, upon receiving SFI=111, the UE can recognize only that the CAP-BW is the start of the DL burst and identify the time slot format (e.g., D / U / F) within the DL burst / COT based on the updated SFI information, while simultaneously monitoring the PDCCH as if the CAP-BW were outside the DL burst.

[0151] Furthermore, (for all cells or a portion thereof configured in the unlicensed frequency band) the channel occupancy or DL ​​burst of the BS can be divided into two durations, and the search space set (or PDCCH) to be monitored can be configured independently for each duration. For example, duration 1 can be defined as the duration within the first k timeslots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed frequency band), and duration 2 can be defined as the duration after the first k timeslots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed frequency band). Here, k can be predefined as an integer greater than or equal to 1, or can be set via separate RRC signaling. Specifically, when signaling / recognizing that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (within the time slot where CO-DCI is detected), the UE can monitor PDCCHs belonging to a specific first search space set, which is configured to be monitored for a corresponding duration (e.g., duration 1) (for all cells or a portion thereof configured in the unlicensed band), or can monitor a specific first PDCCH configured to be monitored for a corresponding duration (e.g., duration 1). Alternatively, since it is uncertain whether CSI-RS will be transmitted in the CAP-BW during the corresponding duration (e.g., duration 1), the UE may not need to perform CSI measurements (or RRM / RLM measurements) via CSI-RS configured to be transmitted during the corresponding duration (e.g., duration 1). On the other hand, when signaling / recognizing that CAP-BW is enabled (in the time slot where CO-DCI is detected), but not belonging to the first time slot (or the first k time slots) of the DL burst, the UE can monitor PDCCHs belonging to a specific second search space set, which is configured to be monitored for a corresponding duration (e.g., duration 2) (for all cells or a portion thereof configured in the unlicensed band), or can monitor specific second PDCCHs configured to be monitored for a corresponding duration (e.g., duration 2). Alternatively, the UE can perform CSI measurements (or RRM / RLM measurements) via CSI-RS configured to be transmitted for a corresponding duration (e.g., duration 2). Here, the specific first and second search space sets can be different from each other. For example, the specific first and second search space sets can have different PDCCH monitoring periods. Furthermore, the specific first and second PDCCHs can be different from each other. The DCI formats transmitted on the specific first and second PDCCHs can be different from each other.

[0152] [Method #3] Method for configuring temporal DL / UL orientation

[0153] The Maximum Channel Occupied Time (MCOT) can be determined based on the priority category corresponding to the CAP performed by the BS (see Table 9), and the BS can set a time less than or equal to the MCOT as its COT duration. In this case, the BS can notify the UE of a COT less than or equal to the MCOT as the COT duration. Therefore, the UE can perform PDCCH monitoring configured outside the COT duration. For example, outside the COT duration, it does not know when the BS will send the PDCCH. Therefore, monitoring can be performed very frequently, but can be performed at a much slower pace during the COT duration. Such monitoring can be beneficial in terms of UE power consumption. Furthermore, the UE can distinguish between UL during the COT duration and UL outside the COT duration. In the case of UL during the COT duration, it can determine whether the channel is idle / busy only for a predetermined time period. When the channel is idle, UL transmission can be allowed without random backoff. Alternatively, UL transmission can be allowed after the predetermined time without determining whether the channel is idle / busy. On the other hand, in the case of UL outside the COT duration, UL transmission can be allowed only when performing CAP based on random backoff.

[0154] [Method #3-1] Explicitly signal the duration of COT in CO-DCI.

[0155] In CO-DCI, the COT start slot index and / or COT end slot index and / or COT duration from a specific slot can be signaled via a separate field. This field can be configured for each CAP-BW, for each carrier / active BWP, or for a set of CAP-BWs, a set of carriers / active BWPs, or unlicensed frequency bands in common.

[0156] There can be a difference between the duration of SFI information and the COT duration. For example, when the period used to monitor CO-DCI is set to 4 slots, the COT information in COT-DCI may indicate that the COT duration is 1 slot. In this case, the SFI information should include information about at least 4 slots, and how the UE interprets the SFI information indicating the remaining 3 slots may be challenging.

[0157] For example, when the SFI information in the SFI field corresponds to k time slots and the CO-DCI is received at time slot #n, the DL / UL information corresponding to time slots #n to #n+k-1 can be signaled via the SFI information. In this case, the last time slot index indicated by the field indicating the COT duration can be after time slot #n+k-1. In this scenario, the SFI information can be applied to the DL / UL information corresponding to time slots #n to #n+k-1, but assumptions may be necessary for DL / UL information after time slot #n+k-1. The method of assumption by the UE is discussed below.

[0158] Option 1) By applying the surround scheme, rules can be set such that the SFI information corresponding to time slot #n+k corresponds to time slot #n, and the SFI information corresponding to time slot #n+k+1 corresponds to time slot #n+1.

[0159] Option 2) allows setting a rule so that the SFI in slot #n+k-1 (or the one corresponding to the last symbol of slot #n+k-1) repeats after slot #n+k-1.

[0160] Option 3) allows setting rules to repeat a specific SFI (e.g., all DL or all UL) after slot #n+k-1.

[0161] Option 4) allows setting rules so that the UE does not expect the above situation. Alternatively, the UE may expect to receive DL / UL information for the corresponding duration by receiving additional CO-DCI, and if it fails to receive the information, one of options 1 to 3 may be applied.

[0162] [Method #3-2] Implicitly signal the duration of COT through a combination of specific SFIs in CO-DCI.

[0163] The SFI information for time slot #k can be copied / transmitted in time slots #n and #m. Here, when the SFI information corresponding to time slot #k signaled in time slot #n is A, and the SFI information corresponding to time slot #k signaled in time slot #m is B, time slot #k can be defined as the last time slot of the COT occupied by the BS. As an example, A can be all DL, and B can be all UL.

[0164] SFI information may exist following the last slot index of the COT identified by [Method #3-1] and / or [Method #3-2]. As an example, the SFI information of CAP-BW #1-1 of the CO-DCI received in slot #n may extend to slot #n+k, but the last slot index of the COT indicated by the CO-DCI may be slot #n+k-2. In this regard, a method for processing the SFI information of slots #n+k-1 and #n+k is proposed.

[0165] Option A) allows you to ignore the SFI information for time slots #n+k-1 and #n+k. For example, even if the UE receives the SFI information for time slots #n+k-1 and #n+k, it can operate as if it did not receive the SFI information for time slots #n+k-1 and #n+k.

[0166] Option B) Only the UL information in the SFI information of slots #n+k-1 and #n+k can be considered valid. In this case, the UE may not perform PDCCH monitoring within the corresponding UL duration, and the duration can be identified as a UL duration outside the COT duration.

[0167] Option C) UE may not expect this situation to occur.

[0168] Figure 15 A communication process according to an example of this disclosure is illustrated. (See also...) Figure 15 The UE can receive a group common DCI including time slot format information and channel occupancy duration information (S1502). Here, the time slot format information can correspond to N time slot formats. Each time slot format can correspond to the symbol configuration of the corresponding time slot within N consecutive time slots, where N can be an integer greater than or equal to 1. The channel occupancy duration information corresponds to the channel occupancy duration. The channel occupancy duration can include M consecutive time slots, where M can be an integer greater than or equal to 1. The group common DCI can include a CO-DCI (e.g., DCI format 2_0), and the CRC can be scrambled using a group common RNTI (e.g., SFI RNTI). Thereafter, the UE can determine the time slot format of one or more time slots based on the time slot format information and the channel occupancy duration information (S1504), and can perform communication based on the determined time slot format of one or more time slots (S1506). For details, see method #3 / #3-1 / #3-2.

[0169] For example, based on the assumption that N is less than M, communication can be performed under the assumption that the N time slot formats sequentially correspond to the time slot following the Nth time slot in the channel occupancy duration (Method #3-1, Option 1). Furthermore, based on the assumption that N is less than M, communication can be performed under the assumption that the last time slot format among the N time slot formats repeatedly corresponds to the time slot following the Nth time slot in the channel occupancy duration (Method #3-1, Option 2). As another example, based on the assumption that N is greater than M, communication can be performed only within the channel occupancy duration based on the time slot format information, ignoring the time slot formats following the Mth time slot format among the N time slot formats (Method #3-2, Option A). Furthermore, based on the assumption that N is greater than M, communication can be performed under the assumption that only the UL symbol is valid in the time slot formats following the Mth time slot format among the N time slot formats (Method #3-2, Option B).

[0170] [Method #4] When transmitting CO-DCI, a group of carriers / active BWPs and / or CAP-BWs can be configured. Rules can be set to include all SFI information and on / off information about carriers / active BWPs and / or CAP-BWs belonging to the configured group in the CO-DCI, and to transmit CO-DCI on all carriers / active BWPs and / or CAP-BWs belonging to the configured group.

[0171] 2) Transmitter (Entity B (e.g., BS))

[0172] [Method #1A] Assign the SFI field for each CAP-BW in the CO-DCI.

[0173] For example, in Figure 10 In the CA scenario, N1 can be assigned to CAP-BW#1-1, N2 can be assigned to CAP-BW#1-2, N3 can be assigned to CAP-BW#2-1, and N4 can be assigned to CAP-BW#3-1, as follows. Figure 11 As shown. Therefore, the SFI for each CAP-BW can be indicated in the CO-DCI.

[0174] [Method #1A-1] Configure the SFI field in CO-DCI for each CAP-BW, where a specific CAP-BW can share... Enjoy the same offset value

[0175] exist Figure 11In this configuration, all or some of N1 / N2 / N3 / N4 can be set to the same value. For example, CAP-BW#1-1 / #1-2 belong to the same carrier. Therefore, assuming the BS indicates the same D / U direction for CAP-BW#1-1 / #1-2, DCI overhead can be reduced by indicating the D / U direction of CAP-BW#1-1 / #1-2 in the CO-DCI using the same field. That is, the D / U direction (e.g., SFI field) can be configured for each carrier. However, since the on / off state of CAP-BW#1-1 / #1-2 can also be shared, it is not necessary to indicate the on / off state for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0176] Alternatively, the transmission mode associated with the transmission method for each CAP-BW of the BS can be configured individually. For example, the signaling mode can be individually configured as either mode 1 (hereinafter, Mode 1) where transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful, or mode 2 (hereinafter, Mode 2) where transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful. When configuring Mode 1, the UE can assume that the SFI field is shared for all CAP-BWs belonging to the carrier / active BWP (i.e., the same offset value is set, or an offset value is set for each cell). When configuring Mode 2, the UE can assume that the SFI field is configured for each CAP-BW belonging to the carrier / active BWP (i.e., a separate offset value is set, or an offset value is set for each CAP-BW).

[0177] In [Method #1A] and [Method #1-1A], a specific state of the SFI field can indicate that the CAP-BW is off (that is, the BS does not attempt to transmit due to CAP failure). For example, when the SFI field is configured to 3 bits and set to '000', it can indicate that the CAP-BW corresponding to the SFI field is off. As another example, the SlotFormatCombination can be used to indicate the off state of the CAP-BW when it is not linked to a specific state of the SFI field (e.g., SFI-index). The size of the SFI field can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when the value of the SFI-index for which the SlotFormatCombination is not configured is signaled, the UE can recognize that the corresponding CAP-BW is off.

[0178] When a CAP-BW is in a closed state, UL slot / symbol information about an open CAP-BW belonging to the same carrier / BWP as that CAP-BW can be communicated to the closed CAP-BW. As an example, CAP-BW#1-1 can be signaled as closed, but CAP-BW#1-2 can be signaled as open (when separate SFI fields are configured for CAP-BW#1-1 and CAP-BW#1-2). In this case, for example, if all symbols for slot #k / k+1 of CAP-BW#1-2 are signaled as UL via CO-DCI, then the BS can signal that CAP-BW#1-1 is also UL for slot #k / k+1. This is because, under the assumption that BSs operating in unlicensed bands typically operate via a single radio frequency (RF) module, it is considered impossible to perform transmission in an adjacent band while simultaneously performing reception in an adjacent band. Therefore, the BS can notify that PDCCH monitoring will not be performed in CAP-BW#1-1 or CAP-BW#1-2 during time slot #k / k+1, and that configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured authorized PUSCH, etc.) are allowed.

[0179] Furthermore, a specific state of the SFI field can indicate whether the corresponding CAP-BW (in the time slot where CO-DCI was detected) belongs to the first transmission time slot (e.g., DL burst) or to the first k time slots during the duration occupied by the BS. For example, when the SFI field is configured to 3 bits and set to '111', it can indicate that the CAP-BW corresponding to the SFI field (in the time slot where CO-DCI was detected) belongs to the first time slot (or the first k time slots) of the DL burst. As another example, this state can be utilized when the SlotFormatCombination is not linked to a specific state of the SFI field (e.g., SFI-index). The SFI field size can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when signaling the value of the SFI-index for which the SlotFormatCombination is not configured, the BS can indicate that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI was detected). In this scenario, the BS can notify the configuration of DL (for all cells or a portion thereof) in the first time slot (or the first k time slots) of the DL burst. That is, in the time slot where CAP-BW is identified as belonging to the DL burst, all symbols can be assumed to be DL. Therefore, the BS can perform PDCCH transmission in CAP-BW under the assumption that all symbols in the time slot are DL. In this method, to update the time slot format of CAP-BW, the BS can retransmit DCI format 2_0 within the same DL burst. For example, upon receiving SFI=111, the UE can only recognize that CAP-BW is the start of the DL burst and identify the time slot format (e.g., D / U / F) in the DL burst / COT based on the updated SFI information, while monitoring PDCCH as if CAP-BW were outside the DL burst.

[0180] Furthermore, (for all cells or a portion thereof configured in the unlicensed band) the channel occupancy or DL ​​burst of the BS can be divided into two durations, and the search space set (or PDCCH) can be configured independently for each duration. For example, duration 1 can be defined as the duration within the first k time slots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed band), and duration 2 can be defined as the duration after the first k time slots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed band). Here, k can be predefined as an integer greater than or equal to 1, or can be set by separate RRC signaling. Specifically, when signaling / recognizing that CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI is detected), the BS can send a PDCCH within the specific first search space set (for all cells or a portion thereof configured in the unlicensed band) within the corresponding duration (e.g., duration 1), or it can send a specific first PDCCH within the corresponding duration (e.g., duration 1). On the other hand, when a signal is sent notifying / recognizing that CAP-BW is enabled (in the time slot where CO-DCI is detected), but not belonging to the first time slot (or the first k time slots) of the DL burst, the BS may transmit PDCCH (for all cells or a portion thereof configured in the unlicensed band) through a specific second search space set for the corresponding duration (e.g., duration 2), or may transmit a specific second PDCCH for the corresponding duration (e.g., duration 2). Here, the specific first search space set and the specific second search space set may be different from each other. For example, the specific first search space set and the specific second search space set may have different PDCCH monitoring periods. Furthermore, the specific first PDCCH and the specific second PDCCH may be different from each other. For example, the DCI format transmitted on the specific first PDCCH and the specific second PDCCH may be different from each other. For example, the DCI format transmitted on the specific first PDCCH may include a group common DCI format (e.g., DCI format 2_0). In addition, the DCI format transmitted on a specific second PDCCH may include a DCI format for data scheduling (e.g., DCI format 0_X / 1_X) and a group common DCI format (e.g., DCI format 2_0).

[0181] [Method #2A] Assign an SFI field for each CAP-BW in the CO-DCI and configure it via a separate field. Bitmap used to indicate the on / off state of each CAP-BW

[0182] In such Figure 10In the CA scenario shown, N1 can be assigned to CAP-BW#1-1, N2 can be assigned to CAP-BW#1-2, N3 can be assigned to CAP-BW#2-1, and N4 can be assigned to CAP-BW#3-1, as follows. Figure 12 As shown in the diagram, the on / off state and SFI can be indicated for each CAP-BW in the CO-DCI. Although the SFI field and the field indicating on / off are shown as being positioned consecutively in the diagram, the bit indicating the on / off state can be added after the SFI field, or the bitmap or bit field indicating on / off can be configured for each CAP-BW with a separate offset value.

[0183] [Method #2A-1] Configure the SFI field in CO-DCI for each CAP-BW, and configure it through a separate field. A bitmap is set to indicate the on / off state of each CAP-BW, where specific CAP-BWs may share the SFI field and / or Bit field value indicating on / off state

[0184] exist Figure 12 In this configuration, all or some of N1 / N2 / N3 / N4 can be set to the same value. For example, CAP-BW#1-1 / #1-2 belong to the same carrier. Therefore, assuming the BS indicates the same D / U direction for CAP-BW#1-1 / #1-2, DCI overhead can be reduced by indicating the D / U direction of CAP-BW#1-1 / #1-2 in the CO-DCI using the same field. That is, the D / U direction (e.g., SFI field) can be configured for each carrier. However, since the on / off state of CAP-BW#1-1 / #1-2 can also be shared, it is not necessary to indicate the on / off state for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0185] Alternatively, the transmission mode associated with the transmission method can be configured individually for each CAP-BW of the BS. For example, the signaling mode can be individually configured as either mode 1 (hereinafter, Mode 1) where transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful, or mode 2 (hereinafter, Mode 2) where transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful. When configuring Mode 1, the BS can assume that the SFI field and bitmap field are shared for all CAP-BWs belonging to the carrier / active BWP (e.g., only 1 bit is configured for the bitmap field corresponding to the cell, and only one SFI field is configured). When configuring Mode 2, the BS can assume that the bit fields in the bitmap are configured for each CAP-BW belonging to the carrier / active BWP (that is, the offset value of the SFI field and the bitmap field are configured for each CAP-BW).

[0186] As another example, such as Figure 13 As shown, the offset value of N1 can be set jointly for the SFI field of CAP-BW#1-1 / 1-2 / 2-1 / 3-1. Furthermore, in the bitmap indicating the on / off state, the offset values ​​of N2 / N3 / N4 / N5 can be set for each CAP-BW, or all or some of N2 / N3 / N4 / N5 can be set to the same value. If N2 and N3 are set to the same value, the on / off state of CAP-BW#1-1 / #1-2 can also be shared, and therefore the on / off state does not need to be indicated for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the offsets corresponding to CAP-BW#1-1 / #1-2 belonging to the same carrier to the same value can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH and / or CSI-RS transmission) (or can be interpreted as meaning that the guard band is not configured).

[0187] As another example, such as Figure 14As shown, for each CC (or BWP), a common offset N1 (relative to the SFI field position) can be set, and the bitmap indicating the on / off state can be signaled via a k-bit bitmap after the offset value (or before the offset value, after the end of the field size configured after N1, or after the field size configured after N1). Here, k can be equal to the number of CAP-BWs corresponding to the CC (or BWP), and can be less than or equal to the number of CAP-BWs corresponding to the CC (or BWP). When k is less than CAP-BW, the value of k can be signaled individually. Furthermore, when k is less than CAP-BW, the relationship between each bit of the k-bit bitmap and its corresponding CAP-BW can be pre-configured by the BS. When k = 1, the on / off states of CAP-BW#1-1 / #1-2 can also be shared, so the on / off state does not need to be indicated for each CAP-BW. This signaling configuration implicitly instructs the BS to attempt transmission only if the CAP for both CAP-BW#1-1 and CAP-BW#1-2 belonging to CC#1 is successful; otherwise, it does not send DL bursts. Furthermore, setting the bit values ​​corresponding to the on / off states of CAP-BW#1-1 / #1-2 belonging to the same carrier to the same position can mean that the RB corresponding to the guard band existing between CAP-BW#1-1 / #1-2 is available (e.g., for mapping / transmission) (e.g., for PDCCH, PDSCH, and / or CSI-RS transmissions) (or can be interpreted as meaning the guard band is not configured).

[0188] Alternatively, the transmission mode associated with the transmission method for each CAP-BW of the BS can be configured individually. For example, the signaling mode can be individually configured as either mode 1 (hereinafter, mode 1) where transmission is performed only when the CAP of all CAP-BWs belonging to the carrier / active BWP is successful, or mode 2 (hereinafter, mode 2) where transmission is attempted for some CAP-BWs when the CAP of some CAP-BWs belonging to the carrier / active BWP is successful. When configuring mode 1, the BS can assume that the bitmap field indicating the on / off state is shared for all CAP-BWs belonging to the carrier / active BWP (that is, only 1 bit is configured for the bitmap field corresponding to the cell). Alternatively, if the bit field in the bitmap is configured for each CAP-BW belonging to the carrier / active BWP when configuring mode 1, the BS can assume that only '1' or '0' is signaled in the bitmap. When configuring mode 2, the BS can assume that the bit fields in the configuration bitmap are configured for each CAP-BW belonging to the carrier / active BWP (that is, the offset value of the bitmap field is set for each CAP-BW).

[0189] In [Method #2A] and [Method #2-1A], the BS can notify that if the 1-bit information corresponding to each CAP-BW is '0' (or '1'), the corresponding CAP-BW is off, and if the information is '1' (or '0'), the corresponding CAP-BW is on. When a CAP-BW is off, UL timeslot / symbol information about an on CAP-BW belonging to the same carrier / BWP or the same frequency band as that CAP-BW can be communicated to the off CAP-BW. As an example, CAP-BW#1-1 can be signaled as off, but CAP-BW#1-2 can be signaled as on (when the on / off information about CAP-BW#1-1 and the on / off information about CAP-BW#1-2 are signaled through separate bit fields, and the SFI field is signaled publicly). In this scenario, for example, if the CO-DCI signals that all symbols for slot #k / k+1 of CAP-BW#1-2 are UL (Unlicensed), the UE can recognize that CAP-BW#1-1 is also UL for slot #k / k+1. This is because, under the assumption that a BS operating in an unlicensed band typically operates through a single radio frequency (RF) module, it is considered impossible to perform transmission and reception simultaneously in adjacent bands. Therefore, the BS can notify that PDCCH monitoring is not performed in CAP-BW#1-1 or CAP-BW#1-2 during slot #k / k+1, and that configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured licensed PUSCH, etc.) are permitted.

[0190] Alternatively, even if CAP-BW is signaled as being off, the BS can recognize that the UL information on the SFI signaling corresponding to CAP-BW is valid. As an example, when CAP-BW#1-1 is signaled as off, and all symbols in time slot #k / k+1 are signaled as DL and all symbols in time slot #k+2 / k+3 are signaled as UL for CAP-BW#1-1, the BS can notify that time slot #k+2 / k+3 is UL and ignore the SFI signaling in time slot #k / k+1. In this case, the BS can notify that PDCCH monitoring is not performed in CAP-BW#1-1 during time slots #k / k+1 / k+2 / k+3, and that configured UL transmissions (e.g., periodic / semi-persistent PUCCH / SRS, configured authorized PUSCH, etc.) are allowed during time slot #k+2 / k+3.

[0191] Alternatively, the specific state of the SFI field and / or bitmap field can indicate whether the CAP-BW (in the time slot where the CO-DCI is detected) belongs to the first transmission time slot (e.g., DL burst) or to the first k time slots during the duration occupied by the BS. Here, the value of k can be predefined as an integer greater than or equal to 1, or it can be set by separate RRC signaling. As one method, when all bits in the bitmap corresponding to all CAP-BWs corresponding to the cell in which the CO-DCI is transmitted are off, it can indicate that the CAP-BW (in the time slot where the CO-DCI is detected) belongs to the first time slot (or the first k time slots) of the DL burst. Paradoxically, when the CO-DCI is transmitted from the cell, all CAP-BWs corresponding to the cell are off. Therefore, this transmission can be used for the aforementioned signaling. That is, through the CO-DCI transmission, this can indirectly indicate that the CAP-BW is on. Furthermore, through the CAP-BW on / off information, this can indicate that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst. For example, when a CO-DCI is sent on CC#1, if all the on / off information corresponding to CAP-BW#1-1 and CAP-BW#1-2 in the bitmap is off, this can indicate that CAP-BW#1-1 and CAP-BW#1-2 (in the time slot where the CO-DCI is detected) belong to the first time slot (or the first k time slots) of the DL burst.

[0192] Furthermore, a CO-DCI can be transmitted on CC#A, and all on / off information corresponding to CC#A / B can be included in the CO-DCI (i.e., cross-carrier indication). In this case, since the CAP-BW on / off information for CC#B is transmitted on another CC (e.g., CC#A), the actual transmission of a BS on CC#B may be ambiguous. Therefore, if all CAP-BWs of CC#A are off, the UE can assume that the DL burst even started on CC#B (even if the transmission actually only occurred on CC#A). On the other hand, if some or all of the CAP-BWs of CC#A are later updated to on, the information about CC#B can only be identified as truly off if all CAP-BW on / off information for CC#B is off. For example, a CO-DCI can be transmitted on CC#1, and all on / off information corresponding to CC#1 / 2 / 3 can be included in the CO-DCI. In this scenario, the BS transmitting a CO-DCI in which all on / off information on the bitmaps corresponding to CAP-BW#1-1 / CAP-BW#1-2 / CAP-BW#2-1 / CAP-BW#3-1 is off can notify the UE that CC#2 and CC#3, as well as CC#1 (in the slot where the CO-DCI is detected), belong to the first slot (or the first k slots) of the DL burst. Furthermore, the CO-DCI can be transmitted on CC#2, and all on / off information corresponding to CC#1 / 2 / 3 can be included in the CO-DCI. In this scenario, the BS transmitting CO-DCI on CC#2, including bitmap information corresponding to CAP-BW#1-1 = Off, CAP-BW#1-2 = Off, CAP-BW#2-1 = On, and CAP-BW#3-1 = Off, can notify the UE that either CAP-BW#1-1 or CAP-BW#1-2 belonging to CC#1 does not belong to the first time slot (or the first k time slots) of the DL burst, because CC#2 does not belong to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI is detected). Therefore, the UE can recognize that actual DL reception is unavailable in CAP-BW#1-1 and CAP-BW#1-2.

[0193] As an example, when the SFI field is configured to 3 bits and set to '111', it can indicate that the CAP-BW corresponding to the SFI field (in the time slot where CO-DCI is detected) belongs to the first time slot (or the first k time slots) of the DL burst. As another example, this state can be utilized when the SlotFormatCombination is not linked to a specific state (e.g., SFI-index) of the SFI field. The SFI field size can be determined by the maximum number of SFI-indexes set. When the SFI field size is 3 bits, the SlotFormatCombination may not be configured for some of the 8 SFI-indexes. In this case, when signaling the value of the SFI-index for which the SlotFormatCombination is not configured, the UE can recognize that the CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI is detected). The UE can then assume the DL (for all cells or a portion thereof configured in the unlicensed band) during the first time slot (or the first k time slots) of the DL burst. In other words, within the first (or the first k) time slots of the CAP-BW burst, where the CAP-BW is identified as belonging to the DL burst, all symbols can be assumed to be DL. Therefore, the UE can perform PDCCH monitoring within the CAP-BW under the assumption that all symbols in the time slot are DL. In this method, to update the time slot format of the CAP-BW, the BS can retransmit DCI format 2_0 within the same DL burst. For example, upon receiving SFI=111, the UE can recognize only that the CAP-BW is the start of the DL burst and identify the time slot format (e.g., D / U / F) within the DL burst / COT based on the updated SFI information, while simultaneously monitoring the PDCCH as if the CAP-BW were outside the DL burst.

[0194] Furthermore, (for all cells or a portion thereof configured in the unlicensed band) the channel occupancy or DL ​​burst of the BS can be divided into two durations, and the search space set (or PDCCH) to be monitored can be configured independently for each duration. For example, duration 1 can be defined as the duration within the first k time slots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed band), and duration 2 can be defined as the duration after the first k time slots of the BS's channel occupancy or DL ​​burst (for all cells or a portion thereof configured in the unlicensed band). Here, k can be predefined as an integer greater than or equal to 1, or can be set by separate RRC signaling. Specifically, when signaling / recognizing that CAP-BW belongs to the first time slot (or the first k time slots) of the DL burst (in the time slot where CO-DCI is detected), the BS can send a PDCCH within the specific first search space set (for all cells or a portion thereof configured in the unlicensed band) within the corresponding duration (e.g., duration 1), or it can send a specific first PDCCH within the corresponding duration (e.g., duration 1). Alternatively, since it is uncertain whether CSI-RS will be transmitted in CAP-BW during the corresponding duration (e.g., duration 1), the BS may not expect reports from the UE regarding CSI measurements (or RRM / RLM measurements) transmitted via CSI-RS configured to be transmitted during the corresponding duration (e.g., duration 1). On the other hand, when signaling / recognizing that CAP-BW is on (in the time slot where CO-DCI is detected), but not belonging to the first time slot (or the first k time slots) of the DL burst, the BS may transmit PDCCHs belonging to a specific second search space set (for all cells or a portion thereof configured in the unlicensed band) during the corresponding duration (e.g., duration 2), or may transmit a specific second PDCCH during the corresponding duration (e.g., duration 2). Alternatively, the BS may not expect reports from the UE regarding CSI measurements (or RRM / RLM measurements) transmitted via CSI-RS configured to be transmitted during the corresponding duration (e.g., duration 2). Here, the specific first search space set and the second search space set may be different from each other. For example, a specific first search space set and a second search space set can have different PDCCH monitoring periods. Furthermore, a specific first PDCCH and a specific second PDCCH can be different from each other. The DCI format transmitted on a specific first PDCCH and a specific second PDCCH can also be different from each other.

[0195] [Method #3A] Method for configuring temporal DL / UL orientation

[0196] The Maximum Channel Occupied Time (MCOT) can be determined based on the priority category corresponding to the CAP performed by the BS (see Table 9), and the BS can set a time less than or equal to the MCOT as its COT duration. In this case, the BS can notify the UE of a COT less than or equal to the MCOT as the COT duration. Therefore, the UE can perform PDCCH monitoring configured outside the COT duration. For example, outside the COT duration, it does not know when the BS will send the PDCCH. Therefore, monitoring can be performed very frequently, but can be performed at a much slower pace during the COT duration. Such monitoring can be beneficial in terms of UE power consumption. Furthermore, the UE can distinguish between UL during the COT duration and UL outside the COT duration. In the case of UL during the COT duration, it can determine whether the channel is idle / busy only for a predetermined time period. When the channel is idle, UL transmission can be allowed without random backoff. Alternatively, UL transmission can be allowed after the predetermined time without determining whether the channel is idle / busy. On the other hand, in the case of UL outside the COT duration, UL transmission can be allowed only when performing CAP based on random backoff.

[0197] [Method #3A-1] Explicitly signal the duration of COT in CO-DCI.

[0198] In CO-DCI, the COT start slot index and / or COT end slot index and / or COT duration from a specific slot can be signaled via a separate field. This field can be configured for each CAP-BW, for each carrier / active BWP, or for a set of CAP-BWs, a set of carriers / active BWPs, or unlicensed frequency bands in common.

[0199] There can be a difference between the duration of SFI information and the COT duration. For example, when the period used to monitor CO-DCI is set to 4 slots, the COT information in COT-DCI may indicate that the COT duration is 1 slot. In this case, the SFI information should include information about at least 4 slots, and how the UE interprets the SFI information indicating the remaining 3 slots may be challenging.

[0200] For example, when the SFI information in the SFI field corresponds to k time slots and the CO-DCI is received at time slot #n, the DL / UL information corresponding to time slots #n to #n+k-1 can be signaled via the SFI information. In this case, the last time slot index indicated by the field indicating the COT duration can be after time slot #n+k-1. In this scenario, the SFI information can be applied to the DL / UL information corresponding to time slots #n to #n+k-1, but assumptions may be necessary for DL / UL information after time slot #n+k-1. The method of assumption by the UE is discussed below.

[0201] Option 1) By applying the surround scheme, rules can be set such that the SFI information corresponding to time slot #n+k corresponds to time slot #n, and the SFI information corresponding to time slot #n+k+1 corresponds to time slot #n+1.

[0202] Option 2) allows setting a rule so that the SFI in slot #n+k-1 (or the one corresponding to the last symbol of slot #n+k-1) repeats after slot #n+k-1.

[0203] Option 3) allows setting rules to repeat a specific SFI (e.g., all DL or all UL) after slot #n+k-1.

[0204] Option 4) allows setting rules so that the UE does not expect the above situation. Alternatively, the UE may expect to receive DL / UL information for the corresponding duration by receiving additional CO-DCI, and if it fails to receive the information, one of options 1 to 3 may be applied.

[0205] [Method #3A-2] Implicitly signal the duration of COT through a combination of specific SFIs in CO-DCI.

[0206] The SFI information for time slot #k can be copied / transmitted in time slots #n and #m. Here, when the SFI information corresponding to time slot #k signaled in time slot #n is A, and the SFI information corresponding to time slot #k signaled in time slot #m is B, time slot #k can be defined as the last time slot of the COT occupied by the BS. As an example, A can be all DL, and B can be all UL.

[0207] SFI information may exist following the last slot index of the COT identified by [Method #3-1] and / or [Method #3-2]. As an example, the SFI information of CAP-BW #1-1 of the CO-DCI received in slot #n may extend to slot #n+k, but the last slot index of the COT indicated by the CO-DCI may be slot #n+k-2. In this regard, a method for processing the SFI information of slots #n+k-1 and #n+k is proposed.

[0208] Option A) allows ignoring the SFI information for time slots #n+k-1 and #n+k. For example, even if the UE receives the SFI information for time slots #n+k-1 and #n+k, it can operate as if it hadn't received them. Therefore, communication can be performed based solely on the SFI information within the COT duration.

[0209] Option B) Only the UL information in the SFI information of time slots #n+k-1 and #n+k can be considered valid. Therefore, the UE can skip PDCCH monitoring during the corresponding UL duration and identify that duration as a UL duration outside the COT duration. In other words, during time slots #n+k-1 and #n+k, the UE can skip PDCCH monitoring and identify the UL duration of time slots #n+k-1 and #n+k as a UL duration outside the COT duration.

[0210] Option C) UE may not expect this situation to occur.

[0211] [Method #4A] When transmitting CO-DCI, a group of carriers / active BWPs and / or CAP-BWs can be configured. Rules can be set to include all SFI information and on / off information about carriers / active BWPs and / or CAP-BWs belonging to the configured group in the CO-DCI, and to transmit CO-DCI on all carriers / active BWPs and / or CAP-BWs belonging to the configured group.

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

[0213] like Figure 16 As shown, firstly, the UE can receive the configuration of the CCs and the BWPs of each CC in the unlicensed band from the BS (S1602). Furthermore, the UE can receive the configuration of the CC group from the BS. Such a configuration can be established based on higher-layer (e.g., RRC) signaling and / or DCI. Additionally, the SFI field in the CO-DCI corresponding to the CAP-BW in the CC group, and / or the bitmap field indicating the CAP-BW on / off state, and / or the COT duration information field can be assigned to the UE by the BS (S1604). Here, the configuration for assignment can be established based on higher-layer (e.g., RRC) signaling and / or DCI. For example, information about the start position (e.g., offset) of the information in the CO-DCI can be shared via higher-layer signaling.

[0214] Subsequently, the UE can receive the CO-DCI from the BS (S1606). Here, the CO-DCI can be transmitted in an unlicensed band or a licensed band. In this case, the UE can receive on / off information, DL / UL information, and / or COT duration information regarding the corresponding CAP-BW based on the field information configured in the CO-DCI. Based on the received information, the UE can achieve power savings by skipping PDCCH monitoring and / or channel measurements for CAP-BWs that are in the off state or during the UL duration. Furthermore, the BS can transmit signals to the UE based on the CO-DCI via the unlicensed band occupied by the BS. In response, the UE can receive signals based on the CO-DCI via the unlicensed band occupied by the BS.

[0215] The UE can perform a network access procedure to execute the procedures and / or methods described / presented above. For example, the UE can receive and store in its memory the system information and configuration information required to perform the procedures and / or methods described / presented above while performing access to a network (e.g., a BS). The configuration information required by this disclosure can be received via higher-layer signaling (e.g., RRC layer, Media Access Control (MAC) layer, etc.).

[0216] Figure 17 The network access procedure and subsequent communication procedure are illustrated. In NR, beamforming can be used to transmit physical channels and reference signals. When beamforming-based signal transmission is supported, beam management procedures may be involved to align beams between the BS and UE. Furthermore, the signals proposed in this disclosure can be transmitted / received using beamforming. In Radio Resource Control (RRC) IDLE mode, beam alignment can be performed based on the SSB. On the other hand, in RRC CONNECTED mode, beam alignment can be performed based on CSI-RS (in DL) and SRS (in UL). When beamforming-based signal transmission is not supported, beam-related operations may be omitted in the following description.

[0217] Reference Figure 17The BS (e.g., gNB) can periodically transmit SSBs (S702). Here, the SSB includes PSS / SSS / PBCH. Beam scanning can be used to transmit the SSB. Afterwards, the BS can transmit the remaining Minimal System Information (RMSI) and other System Information (OSI) (S704). The RMSI may include information required for the UE's initial access to the BS (e.g., PRACH configuration information). After performing SSB detection, the UE identifies the optimal SSB. Afterwards, the UE can transmit a RACH preamble (Message 1 (Msg1)) to the BS via the PRACH resource linked / corresponding to the index (i.e., beam) of the optimal SSB (S706). The beam direction of the RACH preamble is associated with the PRACH resource. The association between the PRACH resource (and / or RACH preamble) and the SSB (index) can be configured via system information (e.g., RMSI). Then, as part of the RACH procedure, the BS may send a Random Access Response (RAR) (Msg2) in response to the RACH preamble (S708), and the UE may use the UL grant in the RAR to send Msg3 (e.g., RRC connection request) (S710). The BS may send a contention resolution message (Msg4) (S720). Msg4 may include RRC connection establishment.

[0218] Once an RRC connection is established between the BS and UE via the RACH procedure, subsequent beam alignment can be performed based on the SSB / CSI-RS (in the DL) and SRS (in the UL). For example, the UE can receive the SSB / CSI-RS (S714). The SSB / CSI-RS can be used by the UE to generate a beam / CSI report. The BS can request a beam / CSI report from the UE via DCI (S716). In this case, the UE can generate a beam / CSI report based on the SSB / CSI-RS and send the generated beam / CSI report to the BS on the PUSCH / PUCCH (S718). The beam / CSI report may include beam measurement results, information about the preferred beam, etc. The BS and UE can switch beams based on the beam / CSI report (S720a, S720b).

[0219] Subsequently, the UE and BS can execute the processes and / or methods described / proposed above. For example, based on configuration information obtained during network access procedures (e.g., system information acquisition procedures, RRC connection procedures via RACH, etc.), the UE and BS can process information in memory and transmit radio signals according to the proposals of this disclosure, or they can process received radio signals and store them in memory. Here, in the case of downlink, the radio signals may include at least one of PDCCH, PDSCH, and reference signal (RS), and in the case of uplink, the radio signals may include at least one of PUCCH, PUSCH, and SRS. Specifically, as part of the network access procedures (e.g., system information acquisition procedures, RRC connection procedures via RACH, etc.), the UE can receive configuration information from the BS regarding at least one of the CC, BWP, SFI, LTE-BW, COT, and / or transmission modes described herein. Therefore, communication can be performed between the UE and BS according to the methods proposed herein. For example, according to the methods proposed in this disclosure, the BS can send CO-DCI to the UE, and the UE can perform communication based on the CO-DCI (e.g., reference signal). Figures 11 to 16 ).

[0220] The various descriptions, functions, processes, proposals, methods, and / or operation flowcharts described herein can be applied to, but are not limited to, various fields where wireless communication / connectivity (e.g., 5G) is required between devices.

[0221] More specific examples will now be described with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise stated, similar reference numerals denote the same or corresponding hardware blocks, software blocks, or functional blocks.

[0222] Figure 18 An example of a communication system 1 applied to this disclosure is shown.

[0223] Reference Figure 18The communication system 1 applied to this disclosure includes wireless devices, a network (BS), and a network. Wireless devices are devices that perform communication using radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also referred to as communication / radio / 5G devices. Wireless devices may include, but are not limited to: robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, IoT devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of vehicle-to-vehicle (V2V) communication. In this document, vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions (TVs), smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches 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 can be implemented as wireless devices, and a particular wireless device 200a can be used as a BS / network node for other wireless devices.

[0224] Wireless devices 100a to 100f can connect to network 300 via BS200. 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 BS200 / network 300, wireless devices 100a to 100f can also communicate directly with each other (e.g., sidelink communication) without intervention from 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.

[0225] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f / BS200 and between BS200. Hereinafter, wireless communication / connections can 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 can be transmitted and received between wireless devices, between wireless devices and BSs, and between BSs via wireless communication / connections 150a, 150b, and 150c. For example, signals can be transmitted and received on various physical channels via wireless communication / 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 can be performed based on various proposals of this disclosure.

[0226] Figure 19 Wireless devices applicable to this disclosure are illustrated.

[0227] Reference Figure 19 The first wireless device 100 and the second wireless device 200 can transmit wireless signals via various RATs (e.g., LTE and NR). {The first wireless device 100 and the second wireless device 200} can correspond to... Figure 18 {Wireless Device 100x and BS200} and / or {Wireless Device 100x and Wireless Device 100x}.

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

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

[0230] The hardware elements of 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, 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)). 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) in accordance with the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document, and provide such messages, control information, data, or information to one or more transceivers 106 and 206. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206, and acquire PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0231] 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 operation flowcharts disclosed in this document can be implemented using firmware or software in the form of code, instructions, and / or instruction sets.

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

[0233] One or more transceivers 106 and 206 can transmit user data, control information, and / or wireless signals / channels as mentioned in the methods and / or operation flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or wireless signals / channels as mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 can 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 can perform control to enable 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 can perform control to enable 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 radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document via 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 radio signals / channels from RF band signals to baseband signals for processing by one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, and radio signals / channels processed by one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0234] In this document, 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 operatively linked to at least one memory to perform operations according to some embodiments or implementations of this disclosure.

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

[0236] In this disclosure, a processing apparatus or device 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 operatively connected to the at least one memory to perform operations according to some embodiments or implementations of this disclosure.

[0237] Figure 20 Another example of a wireless device applied to this disclosure is illustrated. The wireless device can be implemented in various forms depending on the use case / service (see reference). Figure 18 ).

[0238] Reference Figure 20 Wireless devices 100 and 200 can communicate with Figure 19 Corresponding to wireless devices 100 and 200, they can be configured to include various elements, components, units / parts, and / or modules. For example, each of 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 19 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 19 One or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory unit 130, and add-on components 140, and provides overall control of the wireless device. For example, control unit 120 can control the electrical / mechanical operation of the wireless device based on programs / code / instructions / information stored in memory unit 130. Control unit 120 can transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface in memory unit 130.

[0239] The add-on component 140 can be configured in various ways depending on the type of wireless device. For example, the add-on 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 can be used in, but is not limited to, robotic applications. Figure 18 100a), vehicles ( Figure 18 100b-1 and 100b-2), XR device ( Figure 18 100c), handheld device ( Figure 18 100d), home appliances ( Figure 18 100e), IoT devices ( Figure 18 100f), digital broadcasting terminals, holographic devices, public safety devices, MTC devices, medical devices, FinTech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 18 400), BS ( Figure 18 It can be implemented in the form of 200 (network nodes, etc.). Depending on the use case / service, the wireless device can be mobile or fixed.

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

[0241] Figure 21 Examples of vehicles or autonomous vehicles applicable to this disclosure are shown. Vehicles or autonomous vehicles can be implemented as mobile robots, automobiles, trains, manned / unmanned aerial vehicles (AVs), or ships, etc.

[0242] Reference Figure 21 The vehicle or autonomous 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 part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to... Figure 20 The frame size is 110 / 130 / 140.

[0243] The communication unit 110 can send signals (e.g., data and control signals) to and receive signals (e.g., data and control signals) from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 can perform various operations by controlling elements of the vehicle or autonomous vehicle 100. The control unit 120 may include an ECU. The drive unit 140a enables the vehicle or autonomous vehicle 100 to travel on a road. The drive unit 140a may include an engine, electric motor, powertrain, wheels, brakes, steering system, etc. The power supply unit 140b can provide power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuitry, batteries, etc. The sensor unit 140c can acquire information about the vehicle's status, surrounding environment, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, slope sensors, weight sensors, heading sensors, position modules, vehicle forward / reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, humidity sensors, ultrasonic sensors, illuminance sensors, pedal position sensors, etc. Autonomous driving unit 140d can implement technologies for maintaining the vehicle within its lane, technologies for automatically adjusting speed such as adaptive cruise control, technologies for autonomous driving along a defined path, and driving technologies for automatically setting routes when a destination is set, etc.

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

[0245] The embodiments of this disclosure described above are combinations of the elements and features of this disclosure. Unless otherwise stated, elements or features may be considered selective. Each element or feature may be practiced without combination with other elements or features. Furthermore, embodiments of this disclosure may be constructed by combining portions of elements and / or features. The order of operations described in the embodiments of this disclosure may be rearranged. Some constructions of any embodiment may be included in another embodiment and may be replaced by corresponding constructions of another embodiment. It will be apparent to those skilled in the art that claims not expressly referenced in the appended claims may be presented as combinations of embodiments of this disclosure, or may be included as new claims by subsequent amendments after the filing of this application.

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

[0247] Industrial applicability

[0248] This disclosure can be used in UE, BS or other devices in wireless mobile communication systems.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive synchronization signal block SSB; Based on the received SSB, configuration information related to the transmission mode in the unlicensed frequency band is obtained; Receive downlink control information (DCI) including fields indicating whether multiple frequency bands of the serving cell are available. The size of the field is determined based on the transmission mode. Based on the transmission mode, each bit of the field indicates i) the availability of all of the plurality of frequency bands, or ii) the availability of each of the plurality of frequency bands. Specifically, based on the transmission mode, the configuration information configures it to a first mode, and the field is configured as a 1-bit indicating whether all of the multiple frequency bands of the serving cell are available. Wherein, based on the transmission mode, the configuration information is configured to a second mode, the field is configured as multiple bits, and each of the multiple bits indicates whether each of the multiple frequency bands of the serving cell is available; and Receive downlink data within at least one of the plurality of frequency bands indicated by the field.

2. The method according to claim 1, in, Based on the first mode, the downlink data is transmitted only within the multiple frequency bands when the Channel Access Procedure (CAP) for all of the multiple frequency bands is successful, and In this mode, the downlink data is transmitted when the CAP is successful for any of the plurality of frequency bands, based on the second mode.

3. The method according to claim 2, in, The CAP is performed for each of the plurality of frequency bands.

4. The method according to claim 1, in, The DCI is a group common DCI.

5. The method according to claim 1, in, Based on the first mode, a value of "1" in the field indicates that all of the plurality of frequency bands are available, and a value of "0" in the field indicates that all of the plurality of frequency bands are unavailable.

6. The method according to claim 1, in, The fields include information related to the on / off status of the channel access procedure-bandwidth CAP-BW, and Each of the CAP-BWs is a frequency band unit that performs CAP in the unlicensed frequency band.

7. A user equipment (UE), the UE comprising: At least one processor; as well as At least one computer memory, operatively coupled to the at least one processor and configured to, when executed, cause the at least one processor to perform operations, said operations including: Receive synchronization signal block SSB; Based on the received SSB, configuration information related to the transmission mode in the unlicensed frequency band is obtained; Receive downlink control information (DCI) including fields indicating whether multiple frequency bands of the serving cell are available. The size of the field is determined based on the transmission mode. Based on the transmission mode, each bit of the field indicates i) the availability of all of the plurality of frequency bands, or ii) the availability of each of the plurality of frequency bands. Specifically, based on the transmission mode, the configuration information configures it to a first mode, and the field is configured as a 1-bit indicating whether all of the multiple frequency bands of the serving cell are available. Wherein, based on the transmission mode, the configuration information is configured to a second mode, the field is configured as multiple bits, and each of the multiple bits indicates whether each of the multiple frequency bands of the serving cell is available; and Receive downlink data within at least one of the plurality of frequency bands indicated by the field.

8. The UE according to claim 7, in, Based on the first mode, the downlink data is transmitted only within the multiple frequency bands when the Channel Access Procedure (CAP) for all of the multiple frequency bands is successful, and In this mode, the downlink data is transmitted when the CAP is successful for any of the plurality of frequency bands, based on the second mode.

9. The UE according to claim 8, in, The CAP is performed for each of the plurality of frequency bands.

10. The UE according to claim 7, in, The DCI is a group common DCI.

11. The UE according to claim 7, in, Based on the first mode, a value of "1" in the field indicates that all of the plurality of frequency bands are available, and a value of "0" in the field indicates that all of the plurality of frequency bands are unavailable.

12. The UE according to claim 7, in, The fields include information related to the on / off status of the channel access procedure-bandwidth CAP-BW, and Each of the CAP-BWs is a frequency band unit that performs CAP in the unlicensed frequency band.

13. A method performed by a base station (BS), the method comprising the following steps: Send synchronization signal block SSB; Based on the SSB, configuration information related to the transmission mode in the unlicensed frequency band is sent; Send downlink control information (DCI) including fields indicating whether multiple frequency bands of the serving cell are available. The size of the field is determined based on the transmission mode. Based on the transmission mode, each bit of the field indicates i) the availability of all of the plurality of frequency bands, or ii) the availability of each of the plurality of frequency bands. Specifically, based on the transmission mode, the configuration information configures it to a first mode, and the field is configured as a 1-bit indicating whether all of the multiple frequency bands of the serving cell are available. Wherein, based on the transmission mode, the configuration information is configured to a second mode, the field is configured as multiple bits, and each of the multiple bits indicates whether each of the multiple frequency bands of the serving cell is available; and Downlink data is transmitted within at least one of the plurality of frequency bands indicated by the field.

14. A base station (BS), the BS comprising: At least one processor; as well as At least one computer memory, operatively coupled to the at least one processor and configured to, when executed, cause the at least one processor to perform operations, said operations including: Send synchronization signal block SSB; Based on the SSB, configuration information related to the transmission mode in the unlicensed frequency band is sent; Send downlink control information (DCI) including fields indicating whether multiple frequency bands of the serving cell are available. The size of the field is determined based on the transmission mode. Based on the transmission mode, each bit of the field indicates i) the availability of all of the plurality of frequency bands, or ii) the availability of each of the plurality of frequency bands. Specifically, based on the transmission mode, the configuration information configures it to a first mode, and the field is configured as a 1-bit indicating whether all of the multiple frequency bands of the serving cell are available. Wherein, based on the transmission mode, the configuration information is configured to a second mode, the field is configured as multiple bits, and each of the multiple bits indicates whether each of the multiple frequency bands of the serving cell is available; and Downlink data is transmitted within at least one of the plurality of frequency bands indicated by the field.

Images