WO2021066135A1 - Terminal device and method - Google Patents

Abstract

A receiving unit that receives an SIB1 and a higher-layer processing unit that applies a channel bandwidth on the basis of receiving the SIB1 are provided. If nr-Unlicensed is present in servingCellConfigCommon, the higher-layer processing unit considers NR-U to have been set for a serving cell, and, if a channel bandwidth associated with a maximum transmission bandwidth setting that is the same as, or wider than, the bandwidth of an initial BWP of the NR-U and the same as, or narrower than, carrierBandwidth, is supported, the higher-layer processing unit applies a supported NR-U channel bandwidth in association with a maximum transmission bandwidth that is the same as, or wider than, the initial BWP bandwidth of the NR-U and is encompassed by carrierBandwidth.

Description

Terminal device and method

The present invention relates to terminal devices and methods.
The present application claims priority with respect to Japanese Patent Application No. 2019-183241 filed in Japan on October 3, 2019, the contents of which are incorporated herein by reference.

Cellular mobile communication radio access scheme and a radio network (. Hereinafter "LTE (Long Term Evolution)" or the "EUTRA (Evolved Universal Terrestrial Radio Access)" hereinafter) is, Third Generation Partnership Project (3GPP: 3 ^rd Generation It is being considered in the Partnership Project). In LTE, the base station device may be referred to as an eNodeB (evolved NodeB), and the terminal device may be referred to as a UE (User Equipment). LTE is a cellular communication system in which a plurality of areas covered by a base station apparatus are arranged in a cell shape. One base station device may manage one or more serving cells.

At 3GPP, the next-generation wireless communication standard (NR: New Radio) will be examined in order to propose to IMT (International Mobile Telecommunication) -2020, which is the standard for next-generation mobile communication systems established by the International Telecommunication Union (ITU). (Non-Patent Document 1). NR is required to meet the requirements assuming three scenarios of eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication) within the framework of a single technology. There is.

Furthermore, NR-U (NR-Unlicensed) is a wireless communication system and / or wireless communication system that applies NR wireless access technology (NR-RAT: NR Radio Access Technology) to unlicensed bands (Unlicensed spectrum). Is being studied (Non-Patent Document 2).

One aspect of the present invention provides a terminal device that efficiently communicates, and a method used for the terminal device.

(1) The first aspect of the present invention is a terminal device, which includes a receiving unit that receives SIB1 and an upper layer processing unit that applies channel bandwidth based on receiving SIB1. If nr-Unlicensed exists in the servingCellConfigCommon, the upper layer processing unit considers that NR-U is set in the serving cell, and has the same or wider bandwidth as the initial BWP of the NR-U, and the carrierBandwidth If it supports channel bandwidth with a maximum transmit bandwidth setting that is the same or narrower, then the maximum transmit that is equal to or greater than the bandwidth of the initial BWP of the NR-U and is contained within the carrierBandwidth. Apply the supported NR-U channel bandwidth with bandwidth.

(2) A second aspect of the present invention is a method used for a terminal device, which includes a step of receiving SIB1, a step of applying a channel bandwidth based on receiving the SIB1, and a servingCellConfigCommon. If nr-Unlicensed is present, the step of assuming that the serving cell is set to NR-U and the maximum transmission equal to or wider than the bandwidth of the initial BWP of the NR-U and the same as or narrower than the carrier Bandwidth. If channel bandwidth with bandwidth setting is supported, it is supported with the maximum transmit bandwidth contained within the carrierBandwidth, which is equal to or wider than the bandwidth of the initial BWP of the NR-U. Includes a step of applying the channel bandwidth of the NR-U.

According to one aspect of the present invention, the terminal device can efficiently communicate. In addition, the base station device can efficiently perform communication.

It is a conceptual diagram of the wireless communication system which concerns on one aspect of this Embodiment. ^{This is an example showing the relationship between the N slot} _symb , the SCS setting μ, and the CP setting according to one aspect of the present embodiment. It is a schematic diagram which shows an example of the resource grid in the subframe which concerns on one aspect of this Embodiment. It is a figure which shows an example of the relationship between the PUCCH format and the length N ^PUCCH _{symb of the PUCCH format which concerns on one aspect of this embodiment.} It is a figure which shows an example of the parameter included in PUCCH-Config and PUCCH-FormatConfig which concerns on one aspect of this Embodiment. It is a figure which shows an example of the parameter included in PUCCH-ResourceSet and PUCCH-Resource which concerns on one aspect of this Embodiment. It is a figure which shows an example of the parameter which can be set only in a PUCCH format which concerns on one aspect of this Embodiment. It is a figure which shows an example of the parameter included in the PUCCH resource set and PUCCH resource which concerns on one aspect of this embodiment. It is a figure which shows another example of the PUCCH resource set which concerns on one aspect of this Embodiment, and the parameter included in a PUCCH resource. It is a figure which shows an example of DCI format 1_0 which concerns on one aspect of this Embodiment. It is a schematic block diagram which shows the structure of the terminal apparatus 1 which concerns on one aspect of this Embodiment. It is a schematic block diagram which shows the structure of the base station apparatus 3 which concerns on one aspect of this Embodiment. It is a figure which shows an example of the channel access procedure (CAP) which concerns on one aspect of this Embodiment. It is a figure which shows an example of the channel access priority class (CAPC) and CW adjustment procedure (CWAP) which concerns on one aspect of this Embodiment. It is a figure which shows an example of the frequency mapping (resource allocation, mapping to a physical resource, frequency resource allocation type) which concerns on this embodiment. An example of a field (PUCCH starting position field, PSP field) indicating a PUCCH transmission start position (time domain start position, start position in a slot) in the time domain according to the present embodiment and a PUCCH start position corresponding to each SCS. It is a figure which shows.

Hereinafter, embodiments of the present invention will be described.

FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In FIG. 1, the wireless communication system includes terminal devices 1A to 1C and a base station device 3. Hereinafter, the terminal devices 1A to 1C may also be referred to as the terminal device 1. The base station device 3 may include a communication device, a node, an NB (NodeB), an eNB, a gNB, a network device (core network, a gateway), and a part or all of an access point. Further, the terminal device 1 may be referred to as a UE (User equipment). The eNB is a node that provides EUTRA user plane and control plane protocol termination for one or more terminal devices 1, and is particularly connected to a fifth generation core network (5GC) via an NG (Next Generation) interface. The eNB to be generated is referred to as ng-eNB. Further, the gNB is a node that provides NR user plane and control plane protocol termination for one or more terminal devices 1, and is connected to 5GC via an NG interface.

The base station device 3 may constitute one or both of the MCG (Master Cell Group) and the SCG (Secondary Cell Group). MCG is a group of serving cells composed of at least PCell (Primary Cell). Further, SCG is a group of serving cells including at least PSCell (Primary Secondary Cell). The PCell may be a serving cell given based on the initial connection. The MCG may be configured to include one or more SCells (Secondary Cells). The SCG may be configured to include one or more SCells. PCell and PSCell may be referred to as SpCell (Special Cell). It may be referred to as carrier aggregation to construct one CG by using one SpCell and one or a plurality of SCells and perform communication.

The MCG may consist of one or more serving cells on the EUTRA. Further, the SCG may be composed of one or more serving cells on the NR. Further, the MCG may be composed of one or more serving cells on the NR. Further, the SCG may be composed of one or more serving cells on the EUTRA. Further, the MCG and SCG may be composed of one or more serving cells of either EUTRA or NR. Here, on EUTRA may mean that EUTRA RAT (Radio Access Technology) has been applied. In addition, NR may mean that NR RAT has been applied.

The MCG may consist of one or more serving cells on the EUTRA. Further, the SCG may be composed of one or more serving cells on NR-U. Further, the MCG may be composed of one or more serving cells on the NR. Further, the SCG may be composed of one or more serving cells on NR-U. Further, the MCG may be composed of one or more serving cells of either EUTRA or NR or NR-U. Further, the SCG may be composed of one or more serving cells of either EUTRA or NR or NR-U. The purpose of NR-U is to perform NR communication / access / service in a frequency band (operating band) that does not require a frequency license. In the frequency band where NR-U communication is performed, wireless LAN (Wireless Local Area Network, Radio LAN) service (communication and / or method), WAS (Wireless Access Systems) service, IEEE802.11 service, WiFi service, FWA (Fixed) Communication may be performed between a terminal device and / or an access point and / or a base station device that performs a Wireless Access) service, an ITS (Intelligent Transport Systems) service, and a LAA (Licensed Assisted Access) service. On the other hand, NR aims to provide NR communication / access / service in a frequency band that requires a frequency license. In addition, LTE is intended to provide LTE communication / access / service in a frequency band that requires a frequency license. Further, LAA aims to perform LTE communication / access / service in a frequency band that does not require a frequency license. The wireless carrier may provide commercial services in the frequency band assigned by the frequency license.

The operating bands (carrier frequency and frequency bandwidth) applied to each of EUTRA, NR, and NR-U may be individually defined (specified).

Further, the MCG may be configured by the first base station device. Further, the SCG may be configured by a second base station device. That is, the PCell may be configured by the first base station apparatus. The PSCell may be configured by a second base station device. The first base station apparatus and the second base station apparatus may be the same as the base station apparatus 3, respectively.

The frame configuration will be described below.

At least OFDM (Orthogonal Frequency Division Multiplex) is used in the wireless communication system according to one aspect of the present embodiment. The OFDM symbol is a unit of the OFDM time domain. The OFDM symbol comprises at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal in the baseband signal generation. In the downlink, CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is at least used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be given by applying Transform precoding to CP-OFDM.

The subcarrier spacing (SCS) may be given by the ^{subcarrier spacing Δf = 2μ · 15kHz.} For example, the SCS setting μ may be set to any of 0, 1, 2, 3, 4, and / or 5. For a certain BWP (BandWidth Part), the SCS setting μ may be given by the parameters of the upper layer. That is, a value of μ may be set for each BWP (for each downlink BWP, for each uplink BWP) regardless of the downlink and / or the uplink.

In the wireless communication system according to one aspect of the present embodiment, the time unit T _c is used to express the length of the time domain. The time unit T _c may be given by T _c = 1 / (Δf _max · N _f). Δf _max may be the maximum value of SCS supported in the wireless communication system according to one aspect of the present embodiment. Δf _max may be Δf _max = 480 kHz. N _f may be N _f = 4096. The constant κ is κ = Δf _max · N _f / (Δf _ref N _{f, ref} ) = 64. Δf _ref may be 15 kHz. N _{f and ref} may be 2048.

The constant κ may be a value indicating the relationship between the reference SCS and T _c. The constant κ may be used for the length of the subframe. The number of slots contained in the subframe may be given, at least based on the constant κ. Δf _ref is a reference SCS, and N _{f and ref} are values corresponding to the reference SCS.

The transmission of the signal on the downlink and / or the transmission of the signal on the uplink is composed of a frame of 10 ms. The frame is composed of 10 subframes. The length of the subframe is 1 ms. The frame length may be given regardless of SCSΔf. That is, the frame setting may be given regardless of the value of μ. The length of the subframe may be given regardless of SCSΔf. That is, the subframe setting may be given regardless of μ.

For a given SCS setting μ, the number and index of slots contained in one subframe may be given. For example, the slot number n ^mu _s is from 0 to ^{N subframe} in a subframe ^may be given in ascending order in the range of ^mu _slot -1. The number and index of slots contained in one frame may be given to the SCS setting μ. Further, the slot numbers n ^μ _{s and f} may be given in ascending order in the range of 0 to N ^{frame and μ} _{slot -1 in the frame.} One slot may contain consecutive N ^slot _{symbs of OFDM symbols.} The N ^slot _symb may be given at least based on some or all of the CP (CyclicPrefix) settings. The CP setting may be given at least based on the parameters of the upper layer. CP settings may be given at least based on dedicated RRC signaling. The slot number may also be referred to as a slot index.

^{FIG. 2 is an example showing the relationship between the N slot} _symb , the SCS setting μ, and the CP setting according to one aspect of the present embodiment. In FIG. 2A, for example, when the SCS setting μ is 2 and the CP setting is normal CP (NCP), N ^slot _symb = 14, N ^{frame, μ} _slot = 40, N ^{subframe, μ} _slot = 4. Further, in FIG. 2B, for example, when the SCS setting μ is 2 and the CP setting is extended CP (ECP), N ^slot _symb = 12, N ^{frame, μ} _slot = 40, N ^{subframe, μ} _slot = 4. is there.

Hereinafter, the physical resources related to this embodiment will be described.

An antenna port is defined by the fact that the channel through which a symbol is transmitted in one antenna port can be estimated from the channel through which another symbol is transmitted in the same antenna port. If the large scale property of the channel on which the symbol is transmitted on one antenna port can be estimated from the channel on which the symbol is transmitted on the other antenna port, the two antenna ports are QCL (Quasi Co-Located). ) May be referred to as. Large scale characteristics may include at least the long interval characteristics of the channel. Large-scale characteristics include delay spread (delay spread), Doppler spread (Doppler spread), Doppler shift (Doppler shift), average gain (average gain), average delay (average delay), and beam parameters (spatial Rx parameters). It may include at least some or all. The fact that the first antenna port and the second antenna port are QCL with respect to the beam parameters means that the receiving beam assumed by the receiving side with respect to the first antenna port and the receiving beam assumed by the receiving side with respect to the second antenna port. May be the same. The fact that the first antenna port and the second antenna port are QCL with respect to the beam parameters means that the transmitting beam assumed by the receiving side with respect to the first antenna port and the transmitting beam assumed by the receiving side with respect to the second antenna port. May be the same. The terminal device 1 assumes that the two antenna ports are QCLs when the large-scale characteristics of the channel through which the symbol is transmitted in one antenna port can be estimated from the channel in which the symbol is transmitted in the other antenna port. May be done. The fact that the two antenna ports are QCLs may mean that the two antenna ports are QCLs.

For SCS set mu and sets of _{^{carriers, N size, μ grid, x}} N RB sc subcarriers and ^{N subframe,} a resource grid defined by ^mu _symb OFDM symbols is given. N ^{size, μ} _{grid, x} may indicate the number of resource blocks given for the SCS setting μ for carrier x. N ^{size, μ} _{grid, x} may indicate the bandwidth of the carrier. N ^{size, μ} _{grid, x} may correspond to the value of the parameter CarrierBandwith of the upper layer. The carrier x may indicate either a downlink carrier or an uplink carrier. That is, x may be either "DL" or "UL". ^NRB _sc may indicate the number of subcarriers contained in one resource block. ^NRB _sc may be 12. At least one resource grid may be provided for each antenna port p and / or for each SCS setting μ and / or for each transmission direction setting. The transmission direction includes at least a downlink (DL: DownLink) and an uplink (UL: UpLink). Hereinafter, a set of parameters including at least a part or all of the antenna port p, the SCS setting μ, and the setting of the transmission direction may also be referred to as a first radio parameter set. That is, one resource grid may be given for each first set of radio parameters. The radio parameter set may be one or more sets including one or more radio parameters (physical layer parameters or upper layer parameters).

In the downlink, the carrier included in the serving cell is referred to as a downlink carrier (or downlink component carrier). In the uplink, the carrier included in the serving cell is referred to as an uplink carrier (uplink component carrier). The downlink component carrier and the uplink component carrier may be collectively referred to as a component carrier (or carrier).

The type of serving cell may be any of PCell, PSCell, and SCell. The PCell may be a serving cell that is identified at least based on the cell ID (physical layer cell ID, physical cell ID) acquired from the SSB (Synchronization signal / Physical broadcast channel block) in the initial connection. SCell may be a serving cell used in carrier aggregation. The SCell may be a serving cell given at least based on dedicated RRC signaling.

Each element in the resource grid given for each first radio parameter set may be referred to as a resource element (RE). The resource element is specified by the _{frequency domain index k sc} and the time domain index l _sym. For a first set of radio parameters, resource elements are identified by a _{frequency domain index k sc} and a time domain index l _sym. The resource element specified by the frequency domain index k _sc and the time domain index l _sym may also be referred to as a _{resource element (k sc} , l _sym). The frequency domain index k _sc indicates any value from 0 to N ^μ _RB N ^RB _{sc -1.} N ^μ _RB may be the number of resource blocks given for the SCS setting μ. N ^μ _RB may be N ^{size, μ} _{grid, x} . ^NRB _sc is the number of subcarriers included in the resource block, and ^NRB _sc = 12. The frequency domain index k _sc may correspond to the subcarrier index k _sc. The time domain index l _sym may correspond to the OFDM symbol index l _sym. One or more resource elements may correspond to physical resources and complex values (complex value modulation symbols). Even if one or more information bits (control information, transport blocks, information bits for higher layer parameters) are mapped to each of one or more resource elements corresponding to physical resources and / or complex values. Good.

FIG. 3 is a schematic view showing an example of a resource grid in the subframe according to one aspect of the present embodiment. In the resource grid of FIG. 3, the horizontal axis is the time domain index l _sym , and the vertical axis is the frequency domain index k _sc . In one subframe, the frequency domain of the resource grid contains N ^μ _RB N ^RB _sc subcarriers. In one subframe, the time domain of the resource grid may contain 14.2 ^{μ OFDM symbols.} One resource block ^is configured to include ^N _{RB sc} subcarriers. The time domain of the resource block may correspond to a 1 OFDM symbol. The time domain of the resource block may correspond to 14 OFDM symbols. The time domain of the resource block may correspond to one or more slots. The time domain of the resource block may correspond to one subframe.

The terminal device 1 may be instructed to perform transmission / reception using only a subset of the resource grid. A subset of the resource grid, also referred to as BWP, may be given based on at least some or all of the upper layer parameters and / or DCI. BWP may also be referred to as CBP (Carrier Bandwidth Part). The terminal device 1 may not be instructed to perform transmission / reception using the entire set of resource grids. The terminal device 1 may be instructed to perform transmission / reception using some frequency resources in the resource grid. One BWP may be composed of a plurality of resource blocks in the frequency domain. One BWP may be composed of a plurality of continuous resource blocks in the frequency domain. The BWP set for the downlink carrier may also be referred to as a downlink BWP. The BWP set for the uplink carrier may also be referred to as an uplink BWP. The BWP may be a subset of the carrier's band (a subset of the frequency domain in the carrier).

One or more downlink BWPs may be set for each of the serving cells. One or more uplink BWPs may be set for each of the serving cells.

Of one or more downlink BWPs set for the serving cell, one downlink BWP may be set as the active downlink BWP. The downlink BWP switch may be used to deactivate one active downlink BWP and activate an inactive downlink BWP other than the one active downlink BWP. The switching of the downlink BWP may be controlled by the BWP field included in the downlink control information. The switching of the downlink BWP may be controlled based on the parameters of the upper layer.

DL-SCH may be received in the active downlink BWP. PDCCH may be monitored in the active downlink BWP. PDSCH may be received in the active downlink BWP.

DL-SCH may not be received in the inactive downlink BWP. The PDCCH does not have to be monitored in the inactive downlink BWP. The CSI for inactive downlink BWP does not have to be reported.

Of the one or more downlink BWPs set for the serving cell, two or more downlink BWPs need not be set as the active downlink BWP.

Of one or more uplink BWPs set for the serving cell, one uplink BWP may be set as the active uplink BWP. The uplink BWP switch is used to deactivate one active uplink BWP and activate an inactive uplink BWP other than the one active uplink BWP. The switching of the uplink BWP may be controlled by the BWP field included in the downlink control information. The switching of the uplink BWP may be controlled based on the parameters of the upper layer.

UL-SCH may be transmitted in the active uplink BWP. PUCCH may be transmitted in the active uplink BWP. PRACH may be transmitted in the active uplink BWP. SRS may be transmitted in the active uplink BWP.

UL-SCH does not have to be transmitted in the inactive uplink BWP. PUCCH may not be transmitted in the inactive uplink BWP. In the inactive uplink BWP, PRACH may not be transmitted. In the inactive uplink BWP, SRS does not have to be transmitted.

Of one or more uplink BWPs set for one serving cell, two or more uplink BWPs need not be set as active uplink BWPs. That is, only one active uplink BWP is required for the serving cell containing the uplink BWP.

The parameters of the upper layer are the parameters included in the signal of the upper layer. The signal of the upper layer may be RRC (Radio Resource Control) signaling or MAC CE (Medium Access Control Control Element). Here, the signal of the upper layer may be a signal of the RRC layer or a signal of the MAC layer. The signal of the upper layer may be a signal of a layer higher than the physical layer. The upper layer parameter given by the signal of the RRC layer may be notified from the base station device 3 to the terminal device 1 and set. The upper layer parameter given by the signal of the RRC layer may be referred to as an RRC parameter or an RRC information element (IE).

The signal of the upper layer may be common RRC signaling. The common RRC signaling may include at least some or all of the following features C1 to C3.
C1) Map to BCCH logical channel or CCCH logical channel C2) Map to PBCH containing at least the ConfigurationWithSync information element

The ReconfigurationWithSync information element may include information indicating a setting commonly used in the serving cell. The settings commonly used in the serving cell may include at least the PRACH setting. The PRACH setting may indicate at least one or more random access preamble indexes. The PRACH setting may indicate at least the PRACH time / frequency resources.

The common RRC signaling may include at least the common RRC parameters. The common RRC parameter may be a Cell-specific parameter commonly used within the serving cell.

The signal of the upper layer may be dedicated RRC signaling. Dedicated RRC signaling may include at least some or all of the following features D1 to D2.
D1) Map to DCCH logical channel D2) Does not include ReconfigurationWithSync information element

For example, MIB (Master Information Block) and SIB (System Information Block) may be included in the common RRC signaling. Further, the upper layer messages that are mapped to the DCCH logical channel and include at least the ReconnectionWithSync information element may be included in the common RRC signaling. Further, the upper layer message that is mapped to the DCCH logical channel and does not include the ReconnectionWithSync information element may be included in the dedicated RRC signaling. The MIB and SIB may be collectively referred to as system information.

Note that the upper layer parameter including one or more upper layer parameters may be referred to as an information element (IE). In addition, one or more upper layer parameters and / or upper layer parameters including one or more IEs and / or IEs include messages (upper layer messages, RRC messages), information blocks (IB), and system information. May be referred to.

The SIB may at least indicate the time index of the SSB. The SIB may include at least information related to the PRACH resource. The SIB may contain at least information related to the initial connection settings.

The ReconfigurationWithSync information element may include at least information related to the PRACH resource. The ReconnectionWithSync information element may include at least information related to the initial connection settings.

Dedicated RRC signaling may include at least dedicated RRC parameters. The dedicated RRC parameter may be a (UE-specific) parameter dedicated to the terminal device 1. Dedicated RRC signaling may include at least common RRC parameters.

The common RRC parameter and the dedicated RRC parameter may also be referred to as upper layer parameters.

Hereinafter, physical channels and physical signals according to various aspects of the present embodiment will be described.

The uplink physical channel may correspond to a set of resource elements that carry information that occurs in the upper layers. The uplink physical channel is a physical channel used in the uplink carrier. In the wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels are used.
・ PUCCH (Physical Uplink Control CHannel)
・ PUSCH (Physical Uplink Shared CHannel)
・ PRACH (Physical Random Access CHannel)

PUCCH may be used to transmit uplink control information (UCI). The uplink control information includes a part or all of HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement) information corresponding to the channel state information (CSI), scheduling request (SR), and transport block (TB). The TB may be referred to as MAC PDU (Medium Access Control Protocol Data Unit), DL-SCH (Downlink-Shared Channel) or PDSCH (Physical Downlink Shared Channel).

One or more types of uplink control information may be multiplexed on the PUCCH. The multiplexed PUCCH may be transmitted. That is, a plurality of HARQ-ACKs may be multiplexed, a plurality of CSIs may be multiplexed, a plurality of SRs may be multiplexed, and HARQ-ACK and CSI may be multiplexed in the PUCCH. HARQ-ACK and SR may be multiplexed, or may be multiplexed with other UCI types.

The HARQ-ACK information may include at least the HARQ-ACK bit corresponding to TB. The HARQ-ACK bit may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to TB. ACK may be a value indicating that the decoding of the TB has been successfully completed. NACK may be a value indicating that the decoding of the TB has not been completed successfully. The HARQ-ACK information may include at least one HARQ-ACK codebook containing one or more HARQ-ACK bits. The fact that the HARQ-ACK bit corresponds to one or more TBs may mean that the HARQ-ACK bit corresponds to a PDSCH containing the one or more TBs.

The HARQ-ACK bit may indicate ACK or NACK corresponding to one CBG (Code Block Group) included in TB. HARQ-ACK may also be referred to as HARQ feedback, HARQ information, and HARQ control information.

SR may at least be used to request PUSCH resources for initial transmission. The SR may also be used to request UL-SCH resources for new transmissions. The SR bit may be used to indicate either a positive SR (positive SR) or a negative SR (negative SR). The fact that the SR bit indicates a positive SR may also be referred to as "a positive SR is transmitted". A positive SR may indicate that the terminal device 1 requires PUSCH resources for initial transmission. A positive SR may indicate that the SR is triggered by an upper layer. The positive SR may be transmitted when the upper layer instructs the SR to be transmitted. The fact that the SR bit indicates a negative SR may also be referred to as "a negative SR is transmitted". A negative SR may indicate that the terminal device 1 does not require PUSCH resources for initial transmission. A negative SR may indicate that the SR is not triggered by the upper layer. Negative SR may be transmitted if the upper layer does not instruct it to transmit SR.

The SR bit may be used to indicate either a positive SR or a negative SR for any one or more SR configurations. Each of the one or more SR settings may correspond to one or more logical channels. A positive SR for an SR setting may be a positive SR for any or all of the one or more logical channels corresponding to that SR setting. Negative SRs do not have to correspond to a particular SR setting. Showing a negative SR may mean showing a negative SR for all SR settings.

The SR setting may be SR-ID (Scheduling Request ID). The SR-ID may be given by the parameters of the upper layer.

The CSI may include at least some or all of the Channel Quality Index (CQI), Precoder Matrix Index (PMI), and Rank Index (RI). CQI is an index related to channel quality (for example, propagation intensity), and PMI is an index indicating a precoder. RI is an index that indicates the transmission rank (or the number of transmission layers).

CSI may be given at least on the basis of receiving at least a physical signal (eg, CSI-RS) used for channel measurement. The CSI may include a value selected by the terminal device 1. The CSI may be selected by terminal device 1 at least based on receiving the physical signal used for channel measurement. The channel measurement may include an interference measurement. The CSI-RS may be set based on the CSI-RS setting or may be set based on the SSB setting.

The CSI report is a CSI report. The CSI report may include CSI Part 1 and / or CSI Part 2. CSI Part 1 may be configured to include at least some or all of the Broadband Channel Quality Information (wideband CQI), Wideband Precoder Matrix Index (wideband PMI), and RI. The number of bits of the CSI part 1 multiplexed on the PUCCH may be a predetermined value regardless of the RI value of the CSI report. The number of bits of the CSI part 2 to be multiplexed on the PUCCH may be given based on the RI value of the CSI report. The rank index of the CSI report may be the value of the rank index used for calculating the CSI report. The RI of the CSI information may be the value indicated by the RI field included in the CSI report.

The set of RIs allowed in the CSI report may be part or all of 1-8. Also, the set of RIs allowed in the CSI report may be given at least based on the upper layer parameter RankReaction. If the set of RIs allowed in a CSI report contains only one value, the RI in the CSI report may be that one value.

Priority may be set for CSI reports. The priority of a CSI report is the setting for the behavior (processing) of the time domain of the CSI report, the type of content of the CSI report, the index of the CSI report, and / or the serving cell in which the measurement of the CSI report is set. It may be given at least on the basis of part or all of the index.

The time domain behavior (processing) of the CSI report can be set so that the CSI report is aperiodic, the CSI report is semi-persistent, or quasi-static. It may be a setting indicating either of the above.

The type of content in the CSI report may indicate whether the CSI report includes Layer 1 RSRP (Reference Signals Received Power).

The layer 1 is a physical layer, and may be a layer that performs processing such as a physical layer processing unit, a wireless transmission unit, a transmission unit, and / or a wireless reception unit and a reception unit. The layer higher than the layer 1 includes a MAC layer, an RRC layer, an upper layer processing unit, and the like. For example, layer 2 may be a MAC layer, an RLC layer or a PDCP layer, a MAC layer processing unit, an RLC layer processing unit or a PDCP layer processing unit. The layer 3 may be an RRC layer or an RRC layer processing unit.

The index of the CSI report may be given by the parameters of the upper layer.

Next, the PUCCH of the present embodiment will be described.

PUCCH supports one or more PUCCH formats (PUCCH format 0 to PUCCH format 4). The PUCCH format may be transmitted in PUCCH. The transmission of the PUCCH format may mean that the PUCCH is transmitted.

If the terminal device 1 transmits UCI (Uplink Control Information) without transmitting the PUSCH, the terminal device 1 transmits the UCI in the PUCCH using the PUCCH format satisfying a predetermined condition.

PUCCH format 0 is used when transmission with 1 or 2 symbols and the number of HARQ-ACK information bits (HARQ-ACK / SR bit (s)) with positive or negative SR is 1 or 2 bits. ..

PUCCH format 1 is used when transmitting with 4 or more symbols and when the number of HARQ-ACK / SR bits is 1 or 2 bits.

PUCCH format 2 is used when transmission with 1 or 2 symbols and the number of UCI information bits is more than 2 bits.

PUCCH format 3 is used when transmission with 4 or more symbols and the number of UCI information bits is more than 2 bits.

PUCCH format 4 is used when transmission with 4 or more symbols, the number of UCI information bits is more than 2 bits, and the PUCCH resource includes OCC (Orthogonal CoverCode).

The frequency resource allocation of PUCCH formats 0, 1 and 4 may be 1 PRB regardless of the number of UCI information bits transmitted by PUCCH. The frequency resource allocation of PUCCH formats 2 and 3 is based on the upper layer parameters (nrofPRBs: number of Physical Resource Blocks) related to the maximum number of PRBs and the optimum number of PRBs according to the number of UCI information bits transmitted by PUCCH. May be good. The nrofPRBs may be set in PUCCH formats 2 and 3, respectively. For PUCCH resources of PUCCH format 2 and / or 3, the number of PRBs may be adjusted so that the terminal device 1 does not exceed the number of UCI information bits and nrofPRBs desired to be transmitted.

In PUCCH format 3, if the number of PRBs appropriately required for the number of UCI information bits to be transmitted _{does not satisfy 2 ^ α 2} * 3 ^ α ₃ * 5 ^ α ₅ , do not exceed nrofPRBs. The number of PRBs may be increased until the number of PRBs required for PUCCH format 3 _{satisfies 2 ^ α 2} * 3 ^ α ₃ * 5 ^ α _5. Here, α ₂ , α ₃ , and α ₅ may be 0 or an integer larger than 0, respectively.

FIG. 4 is a diagram showing an example of the relationship between the ^{PUCCH format and the length N PUCCH} _symb of the PUCCH format according to one aspect of the present embodiment. ^{The length N PUCCH} _symb of PUCCH format 0 is a 1 or 2 OFDM symbol. ^{The length N PUCCH} _symb of PUCCH format 1 is one of 4 to 14 OFDM symbols. ^{The length N PUCCH} _symb of PUCCH format 2 is a 1 or 2 OFDM symbol. ^{The length N PUCCH} _symb of PUCCH format 3 is one of 4 to 14 OFDM symbols. ^{The length N PUCCH} _symb of PUCCH format 4 is one of 4 to 14 OFDM symbols.

FIG. 5 is a diagram showing an example of parameters included in PUCCH-Config and PUCCH-FormatConfig according to one aspect of the present embodiment. For PUCCH, the time frequency resource may be determined based on PUCCH-Config and transmitted. The parameters contained in PUCCH-Config and PUCCH-Config may be RRC information elements. PUCCH-Config may be used to set one or more PUCCH parameters specific to the terminal device 1 for each BWP. The resourceSetToAddModList and resourceSetToReleaseList are lists used to add and / or release PUCCH resource sets, and the size of the lists may be based on the maximum number of PUCCH resource sets. The resourceToAddModList and resourceToReleaseList are lists used to add and / or release one or more PUCCH resources that apply to uplink BWPs and serving cells with PUCCH settings defined, and their size is that of the PUCCH resources. It may be based on the maximum number. The spatialRelationInfoToAddModList may be used to indicate the spatial relation settings between reference RS and PUCCH. The reference RS may be SSB / CSI-RS / SRS. If the list has more than one element, MAC-CE selects one element. PUCCH-FormatConfig may be set for each of PUCCH formats 1 to 4. The PUCCH-FormatConfig corresponding to each PUCCH format may be shared among all PUCCH resources corresponding to each PUCCH format. The dl-DataToUL-ACK may be used to indicate a list of timings for the PDSCH and the HARQ-ACK corresponding to the PDSCH.

PUCCH-FormatConfig may include one or all of interslotFrequencyHopping, additionalDMRS, maxCodeRate, nrofSlots, pi2BPSK, and simultaneousHARQ-ACK-CSI.

Interslot Frequency Hopping is used to show that the terminal device 1 can perform inter-slot frequency hopping when PUCCH formats 1, 3 or 4 are repeated between a plurality of slots. For long PUCCH (PUCCH formats 1, 3, 4), the terminal device 1 cannot perform intra-slot frequency hopping and inter-slot frequency hopping at the same time.

Additional DMRS may also be used to indicate for PUCCH format 3 or 4 that it can contain two DMRS symbols per hop and, without frequency hopping, it can contain four DMRS symbols. Good. This field does not apply to PUCCH format 1 or 2.

MaxCodeRate may indicate the maximum coding rate for determining how to feed back UCI in PUCCH formats 2, 3 or 4. This field does not have to apply to PUCCH format 1.

NrofSlots indicates the number of slots with the same PUCCH format for each of PUCCH formats 1, 3 or 4. When this field is not in PUCCH-FormatConfig, terminal device 1 may apply n1. This field does not have to apply to PUCCH format 2.

Pi2BPSK may indicate to PUCCH that the terminal device 1 can use pi / 2BPSK as the UCI symbol instead of QPSK. This field does not have to apply to PUCCH formats 1 and 2.

SimultaneousHARQ-ACK-CSI may be used to indicate in PUCCH format 2, 3 or 4 whether HARQ-ACK feedback with or without SR and simultaneous transmission of CSI can be used. When this field is not in PUCCH-FormatConfig, terminal device 1 may apply off. This field does not have to apply to PUCCH format 1.

FIG. 6 is a diagram showing an example of parameters included in the PUCCH-ResourceSet and the PUCCH-Resource according to one aspect of the present embodiment. PUCCH-ResourceSet may include pucch-ResourceSetId, resourceList, maxPayloadMinus1.

The resourceList is a list of one or more PUCCH resources included in the PUCCH resource set. One or more PUCCH resources in PUCCH formats 0 and 1 may be allowed to be included only in the first PUCCH resource set. The first PUCCH resource set may be a PUCCH resource set with pucch-ResourceSetId = 0. The first PUCCH resource set may include up to 32 PUCCH resources. One or more PUCCH resources in PUCCH formats 2, 3 and 4 may be allowed to be included only in the PUCCH resource set with pucch-ResourceSetId> 0. These PUCCH resource sets may include up to 8 PUCCH resources. The PUCCH resource set may be set up to 4 sets.

MaxPayloadMinus1 may be used to indicate the maximum number of payload bits-1 that the terminal device 1 can transmit using the PUCCH resource set. That is, maxPayloadMinus1 may indicate the maximum number of UCI bits (maximum value of the number of UCI bits) that can be transmitted by the PUCCH resource set. When PUCCH occurs, the terminal device 1 may select a PUCCH-ResourceSet that supports the number of bits that the terminal device 1 wants to transmit. In the first PUCCH resource set, this field does not have to be included in the PUCCH-ResourceSet. Further, in the PUCCH resource set other than the first PUCCH resource set, this field does not have to be included in the PUCCH-ResourceSet as long as it is the maximum payload size.

PUCCH-Resource may include pucch-ResourceId, startingPRB, intraSlotFrequencyHopping, secondHopPRB, format.

Starting PRB indicates the PRB index of PUCCH. The value in this field indicates the first PRB index if the PUCCH is composed of multiple PRBs.

IntraSlotFrequencyHopping may be used to indicate whether or not to perform intra-slot frequency hopping. In-slot frequency hopping may be applied to all types of PUCCH formats. In-slot frequency hopping and inter-slot frequency hopping are not performed simultaneously for long PUCCH (PUCCH formats 1, 3, and 4) in a plurality of slots.

SecondHopPRB may be used to indicate the index of the first PRB after frequency hopping. The values may be applied for in-slot frequency hopping.

Format may be used to select the type of PUCCH format (PUCCH formats 0-4) and format-specific parameters. PUCCH formats 0 and 1 may only be allowed for PUCCH resources included in the first PUCCH resource set. PUCCH formats 2, 3 and 4 may be allowed only for PUCCH resources contained in PUCCH resource sets other than the first PUCCH resource set.

FIG. 7 is a diagram showing an example of parameters that can be set uniquely to the PUCCH format according to one aspect of the present embodiment.

The PUCCH resource of PUCCH format 0 may be set based on PUCCH-Format0 including initialCyclicShift, nrofSymbols, and startingSymbolIndex.

The PUCCH resource of PUCCH format 1 may be set based on PUCCH-Format1 including initialCyclicShift, nrofSymbols, startingSymbolIndex, and timeDomainOCC.

The PUCCH resource of PUCCH format 2 may be set based on PUCCH-Format2 including nrofPRBs, nrofSymbols, and startingSymbolIndex.

The PUCCH resource of PUCCH format 3 may be set based on PUCCH-Format3 including nrofPRBs, nrofSymbols, and startingSymbolIndex.

The PUCCH resource of PUCCH format 4 may be set based on PUCCH-Format 4 including nrofSymbols, occ-Length, occ-Index, and startingSymbolIndex.

If the format indicates PUCCH-format0, the PUCCH format set for the PUCCH resource is PUCCH format 0. The PUCCH resource may be determined based on the values of various parameters contained in PUCCH-format 0.

If the format indicates PUCCH-format1, the PUCCH format set for the PUCCH resource is PUCCH format 1. The PUCCH resource may be determined based on the values of various parameters contained in PUCCH-format1.

If the format indicates PUCCH-format2, the PUCCH format set for the PUCCH resource is PUCCH format2. The PUCCH resource may be determined based on the values of various parameters contained in PUCCH-format2.

If the format indicates PUCCH-format3, the PUCCH format set for the PUCCH resource is PUCCH format 3. PUCCH resources may be determined based on the values of various parameters contained in PUCCH-format 3.

If the format indicates PUCCH-format 4, the PUCCH format set for the PUCCH resource is PUCCH format 4. PUCCH resources may be determined based on the values of various parameters contained in PUCCH-format 4.

Next, the PUCCH resource and the PUCCH resource set according to the present embodiment will be described.

The terminal device 1 may determine the PUCCH resource used for transmitting the HARQ-ACK corresponding to the PDSCH based on the PRI value included in the DCI format used for PDSCH scheduling.

If the PUCCH resource set contains more PUCCH resources than a predetermined number, the terminal device 1 is based on the value of the PRI (PUCCH resource indicator) field included in the DCI format and the CCE index that detected the DCI format. , Which PUCCH resource in the PUCCH resource set may be used. Further, if the PUCCH resource set contains more PUCCH resources than a predetermined number, the size (number of bits, bit size) of the PRI field included in the DCI format may be expanded. Assuming that the PUCCH resource set contains a predetermined number or a number less than a predetermined number of PUCCH resources, the terminal device 1 may determine the PUCCH resources based on the value of PRI included in the DCI format. Further, the PUCCH resource set uses the first PUCCH resource set to which the first frequency resource allocation type is applied or the second frequency resource allocation type is applied based on the first information contained in the DCI format. It may also be decided whether to use a second PUCCH resource set. The first information may be information indicating whether the PUCCH is transmitted inside the COT or outside the COT, may be information indicating the frequency resource allocation type of the PUCCH, or may be the information indicating the frequency resource allocation type of the PUCCH. It may be information indicating the type of CAP before transmission of.

For example, when more than 8 PUCCH resources are set for a PUCCH resource set other than the first PUCCH resource set, the terminal device 1 has a PUCCH resource (PUCCH resource ID) for transmitting UCI information bits. May be determined based on the value of the PRI and the value of the CCE index. Further, when the bit size of the PRI field is expanded, the UCI information bit may be transmitted using the PUCCH resource corresponding to the PRI value.

The PUCCH resource set may be accompanied by a set of PUCCH resource indexes provided by a resourceList that provides a set of pucch-ResourceId used for the PUCCH resource set. The PUCCH resource set may also include the maximum number of UCI information bits that can be transmitted using the PUCCH resource in the PUCCH resource set provided by maxPayloadMinus1. The maximum number of UCI information bits for the first PUCCH resource set may be 2 bits. The maximum number of PUCCH resource indexes per PUCCH resource set may be provided by maxNrofPUCCH-ResourcesPerSet. For NR-U, the maximum number of PUCCH resources contained in all PUCCH resource sets may be 32.

If terminal device 1 supports maxNrofPUCCH-ResourceSets-r16 with a value larger than maxNrofPUCCH-ResourceSets as capability information, 4 sets supported by maxNrofPUCCH-ResourceSets for terminal device 1 More PUCCH resource sets may be set. At that time, the PUCCH resource set may be associated with the PUCCH resource set index provided by PUCCH-ResourceSet-r16 and provided by pucch-ResourceSetId-r16. That is, the value that pucch-ResourceSetId-r16 can take may be any of 0 to maxNrofPUCCH-ResourceSets-r16-1.

Terminal device 1 supports maxNrofPUCCH-ResourceSets-r16, and if a PUCCH resource set is set in which pucch-ResourceSetId-r16 is greater than a predetermined value, a different frequency resource allocation type will be applied. PUCCH resource set may be set. Furthermore, maxPayloadMinus1 set to the same value may be applied to PUCCH resource sets of different pucch-ResourceSetId-r16.

The base station apparatus 3 provides as capability information that the terminal apparatus 1 supports maxNrofPUCCH-ResourceSets-r16 having a value larger than a predetermined value, or the terminal apparatus 1 has a different frequency resource allocation type. If the ability information is provided that the terminal device 1 supports PUCCH-ResourceSet-r16 and / or PUCCH-Resource-r16, the ability information is provided. PUCCH-ResourceSet-r16 or PUCCH-Resource-r16 may be set to include parameters related to the frequency resource allocation type (for example, freqResourceAllocType-r16) for the terminal device 1. Even when maxNrofPUCCH-Resources-r16 having a value larger than a predetermined value is provided instead of maxNrofPUCCH-ResourceSets-r16, the base station apparatus 3 may perform the same processing.

If the base station device 3 sets a PUCCH-ResourceSet in which a pucch-ResourceSetId having a value larger than a predetermined value is set, the base station apparatus 3 may be set including freqResourceAllocType for each PUCCH-ResourceSet.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 0 may be the first PUCCH resource set containing up to 32 PUCCH resources of PUCCH format 0 or 1. The UCI information bits for the PUCCH resource set with pucch-ResourceSetId-r16 = 0 may only be supported up to 2 bits.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 1, may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set of pucch-ResourceSetId-r16 = 1 may be _{from 3 to N 2.} The value of N ₂ may be given by maxPayloadMinus1 contained in the PUCCH resource set.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 2, may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set of pucch-ResourceSetId-r16 = 2 may be _{from N 2} + 1 to N _3. The value of N ₃ may be given by maxPayloadMinus1 contained in the PUCCH resource set.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 3, may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set with pucch-ResourceSetId-r16 = 3 _{may be from N 3} + 1 to 1706. At this time, maxPayloadMinus1 may not be included in the PUCCH resource set.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 4, may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set of pucch-ResourceSetId-r16 = 4 may be _{from 3 to N 2.} The value of N ₂ may be given by maxPayloadMinus1 contained in the PUCCH resource set.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 5, may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set of pucch-ResourceSetId-r16 = 5 may be from _{N 2 + 1 to N 3.} The value of N ₃ may be given by maxPayloadMinus1 contained in the PUCCH resource set.

The PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 6, may be a PUCCH resource set containing PUCCH resources of PUCCH formats 2, 3, and / or 4. The number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set with pucch-ResourceSetId-r16 = 6 _{may be from N 3} + 1 to 1706. At this time, maxPayloadMinus1 may not be included in the PUCCH resource set.

If different PUCCH resource set IDs are set in a plurality of PUCCH resource sets to which the same or the same range of UCI information bits (that is, maxPayloadMinus1 having the same value) is applied, the plurality of PUCCH resource sets are set. , Physical resource mapping or frequency resource allocation type may be different. For example, the PUCCH resources of the PUCCH resource set of pucch-ResourceSetId-r16 = 1 and pucch-ResourceSetId-r16 = 4 may have different frequency resource allocation types set, and of the PUCCH resource set of pucch-ResourceSetId-r16 = 1. The frequency resource allocation type of the PUCCH resource set may be continuous allocation, and the frequency resource allocation type of the PUCCH resource set of the PUCCH resource set of pucch-ResourceSetId-r16 = 4 may be interlaced allocation. Other IDs (pucch-ResourceSetId-r16 = 2 and 5 and pucch-ResourceSetId-r16 = 3 and 6) may be set in the same manner.

If different PUCCH resource set IDs are set in multiple PUCCH resource sets to which the same or the same range of UCI information bits (that is, maxPayloadMinus1 of the same value) is applied, physical resources are set between PUCCH resource sets. The mapping or frequency resource allocation type may be different. For example, the PUCCH resources of the PUCCH resource set of pucch-ResourceSetId-r16 = 1 and pucch-ResourceSetId-r16 = 4 may have different frequency resource allocation types set, and of the PUCCH resource set of pucch-ResourceSetId-r16 = 1. The frequency resource allocation type of the PUCCH resource set may be interlaced allocation, and the frequency resource allocation type of the PUCCH resource set of the PUCCH resource set of pucch-ResourceSetId-r16 = 4 may be continuous allocation. Other IDs may be set in the same manner.

In each PUCCH resource set, if maxPayloadMinus1 corresponding to _{N 2} and _{N 3} is not set, _{N 2} and _{N 3} may be regarded as 1706.

When the terminal device 1 has the ability to set more PUCCH resource sets than a predetermined number, and when the terminal device 1 is set with more PUCCH resource sets than the predetermined number, or , When a PUCCH resource set ID (pucch-ResourceSetId-r16) having a value larger than a predetermined value (pucch-ResourceSetId) is set, the PUCCH resource set corresponding to the frequency resource allocation of the PUCCH is set for the terminal device 1. May be set. In such a case, the PUCCH resource set and the second frequency resource allocation type to which the first frequency resource allocation type is applied to the terminal device 1 for the same or the same number of UCI information bits. A PUCCH resource set to which is applied may be set. Further, a PUCCH resource set containing at least one PUCCH resource of the first frequency resource allocation type and a PUCCH resource set containing at least one PUCCH resource of the second frequency resource allocation type may be set. For example, the first frequency resource allocation type may be an interlaced allocation, the second frequency resource allocation type may be a continuous allocation, and the first frequency resource allocation type and the second frequency resource allocation type may be. Each frequency resource allocation type may be vice versa.

When resourceSetToAddModList-r16 is set with a value greater than the specified number or with a value greater than maxNrofPUCCH-ResourceSets-r16 applied, or with a value greater than the specified value pucch-ResourceSetId- When a PUCCH resource set including r16 is set, PUCCH-ResourceSet-r16 or PUCCH-Resource-r16 may include a parameter indicating the frequency resource allocation type of the PUCCH resource (for example, freqResourceAllocType-r16).

If the maximum number of UCI information bits of at least two PUCCH resource sets with different pucch-ResourceSetIds is the same, the frequency of the PUCCH resource is for a different PUCCH resource set or a PUCCH resource contained in a different PUCCH resource set. A parameter indicating the resource allocation type (for example, freqResourceAllocType-r16) may be included, and different frequency resource allocation types may be set for each.

Based on the first information contained in the DCI format used for PDSCH scheduling for the terminal device 1 to which the first PUCCH resource set and the second PUCCH resource set to which the same maximum UCI bit number is applied are set. Then, it may be determined whether the PUCCH resource included in the first PUCCH resource set transmits HARQ-ACK for PDSCH or the PUCCH resource included in the second PUCCH resource set transmits HARQ-ACK for PDSCH. .. At this time, at least the PUCCH resource set ID and the frequency resource allocation type may be different between the first PUCCH resource set and the second PUCCH resource set.

Here, in the present embodiment, the frequency resource allocation type (first resource allocation type, second frequency resource allocation type) may refer to interlaced arrangement or continuous arrangement, or other frequency resources. You may point to the placement.

FIG. 8 is a diagram showing an example of a PUCCH resource set and parameters included in the PUCCH resource according to one aspect of the present embodiment. PUCCH-ResourceSet-r16 may include pucch-ResourceSetId-r16, freqResourceAllocType-r16, resourceList or resourceList-r16, maxPayloadMinus1 or maxPayloadMinus1-r16.

Pucch-ResourceSetId-r16 indicates the ID of PUCCH-ResourceSet-r16, and a value larger than pucch-ResourceSetId may be set. That is, maxNrofPUCCH-ResourceSets-r16 may have a larger value than maxNrofPUCCH-ResourceSets (that is, 4 sets).

FreqResourceAllocType-r16 may indicate the frequency resource allocation type applied to all PUCCH resources indicated by the resourceList included in the PUCCH resource set. Although two types are shown in FIG. 8, the number of types that can be set may vary depending on the number of frequency resource allocation types that are supported. The frequency resource allocation type may be information indicating interlaced allocation and continuous allocation. Further, the frequency resource allocation type may be information indicating whether or not interlaced allocation is possible.

The resourceList is a list of PUCCH resources included in the PUCCH resource set. The resourceList may show up to 32 PUCCH resources for one PUCCH resource set. When set as resourceList-r16, up to 32 PUCCH resources may be shown regardless of the value of pucch-ResourceSetId.

maxPayloadMinus1 is information indicating the maximum number of UCI information bits that can be transmitted by the PUCCH resource of the PUCCH resource set, and corresponds to _{N 2} and N _{3 described above.} maxPayloadMinus1-r16 may differ in the maximum number of UCI information bits supported compared to maxPayloadMinus1. That is. The range of UCI information bits supported by maxPayloadMinus1-r16 may be wider or narrower than maxPayloadMinus1. The maximum number of UCI information bits supported by maxPayloadMinus1-r16 may be larger or smaller than maxPayloadMinus1.

PUCCH-Resource-r16 may be a resourceList or a PUCCH resource listed by resourceList-r16. PUCCH-Resource-r16 may include pucch-ResourceId-r16, startingPRB, intraSlotFrequencyHopping, secondHopPRB, format.

Pucch-ResourceId-r16 may be used to indicate the PUCCH resource ID. A value larger than pucch-ResourceId may be set for pucch-ResourceId-r16. That is, maxNrofPUCCH-Resources-r16 indicating the maximum number of PUCCH resources may be set to a value larger than maxNrofPUCCH-Resources.

The information shown in the starting PRB may change based on the frequency resource allocation type indicated by freqResourceAllocType-r16. For example, if freqResourceAllocType-r16 corresponding to the PUCCH resource indicates the frequency resource allocation type corresponding to the continuous allocation, the starting PRB may be information indicating the first PRB index of the PUCCH resource. If the freqResourceAllocType-r16 corresponding to the PUCCH resource indicates the interlaced arrangement, the startingPRB may indicate the index of the interlaced. It may also be used to calculate the interlaced index. For example, the index of interlace may be obtained from startingPRB mod M. M indicates the total number of interlaces. X mod Y is used to calculate the remainder when X is divided by Y.

IntraSlotFrequencyHopping and secondHopPRB may be set only when the frequency resource allocation type indicated by freqResourceAllocType-r16 is the frequency resource allocation type corresponding to continuous allocation. intraSlotFrequencyHopping may be information indicating whether or not frequency hopping in the slot is supported, and secondHopPRB may be information indicating the first PRB index after frequency hopping.

Format is information indicating the type of PUCCH format applied to PUCCH-Resource-r16. The parameters applied may differ depending on the PUCCH format. The parameters specifically applied may be the same as in FIG. 7 or may be different. Since format4 is not applied by NR-U, it may be set as an optional parameter. That is, format4 may be included when applied to other than NR-U.

FIG. 9 is a diagram showing another example of the PUCCH resource set and the parameters included in the PUCCH resource according to one aspect of the present embodiment. Compared with FIG. 8, freqResourceAllocType-r16 is included in PUCCH-Resource-r16. The frequency resource allocation type may be set for each PUCCH resource.

FIG. 10 is a diagram showing an example of DCI format 1_0 according to one aspect of the present embodiment. FIG. 10A is an example of DCI format 1_0 for NR. FIG. 10B is an example of DCI format 1_0 for NR-U. Fields related to PUCCH channel access procedures may be added to DCI format 1_0 for NR-U. The size of the PRI may vary depending on the number of PUCCH resources. Further, the DCI format 1_0 for NR-U may include information indicating the frequency resource allocation type for the PUCCH resource. In that case, the parameters shown in FIGS. 8 and 9 do not have to be set as RRC parameters. The details of PUCCH starting position, Channel access type, and Channel access priority class will be described later. Further, the PUCCH starting position, the Channel access type, and the Channel access priority class do not have to be included in the DCI format when they are determined based on the specifications and the upper layer parameters.

PUSCH is at least used to transmit TB (MAC PDU, UL-SCH). PUSCH may be used to transmit at least some or all of TB, HARQ-ACK information, CSI, and SR. PUSCH is at least used to send a random access message 3 (message 3 (Msg3)) corresponding to the RAR (Msg2) and / or RAR grant in the random access procedure. The TB may correspond to each of the uplink and the downlink. That is, the PUSCH may be used to transmit the TB to the uplink. The PDSCH may be used to transmit a TB to the downlink.

PRACH is at least used to transmit a random access preamble (random access message 1, message 1 (Msg1)). The PRACH is an initial connection establishment procedure, a handover procedure, a connection re-establishment procedure, an initial access procedure, synchronization (timing adjustment) for PUSCH transmission, and resource request for PUSCH. It may be used at least to indicate part or all. The random access preamble may be used to notify the base station device 3 of an index (random access preamble index) given by the upper layer of the terminal device 1.

The random access preamble may be given by cyclically shifting the Zadoff-Chu sequence corresponding to the physical route sequence index u. The Zadoff-Chu sequence may be generated based on the physical route sequence index u. A plurality of random access preambles may be defined in one serving cell. The random access preamble may be specified at least based on the index of the random access preamble. Different Random Access Preambles Corresponding to Different Indexes of Random Access Preambles The different random access preambles may correspond to different combinations of physical route sequence index u and cyclic shift. The physical route sequence index u and cyclic shift may be given at least based on the information contained in the system information. The physical route sequence index u may be an index that identifies a series included in the random access preamble. The random access preamble may be specified at least based on the physical route sequence index u.

In FIG. 1, the following uplink physical signals are used in the uplink wireless communication. The uplink physical signal does not have to be used to transmit the information output from the upper layer, but it is used by the physical layer.
・ UL DMRS (UpLink Demodulation Reference Signal)
・ SRS (Sounding Reference Signal)
・ UL PTRS (UpLink Phase Tracking Reference Signal)

UL DMRS is associated with PUSCH and / or PUCCH transmission. UL DMRS is multiplexed with PUSCH or PUCCH. The base station apparatus 3 may use UL DMRS to correct the propagation path of PUSCH or PUCCH. Hereinafter, transmitting both the PUSCH and the UL DMRS related to the PUSCH is referred to simply as transmitting the PUSCH. Hereinafter, transmitting PUCCH and UL DMRS related to the PUCCH together is referred to simply as transmitting PUCCH. UL DMRS related to PUSCH is also referred to as UL DMRS for PUSCH. UL DMRS related to PUCCH is also referred to as UL DMRS for PUCCH.

SRS does not have to be related to PUSCH or PUCCH transmission. The base station apparatus 3 may use SRS for measuring the channel state. The SRS may be transmitted at the end of the subframe in the uplink slot, or at a predetermined number of OFDM symbols from the end.

UL PTRS may be at least a reference signal used for phase tracking. The UL PTRS may be associated with a UL DMRS group that includes at least the antenna ports used for one or more UL DMRSs. The association between the UL PTRS and the UL DMRS group may be that the antenna port of the UL PTRS and a part or all of the antenna ports included in the UL DMRS group are at least QCL. The UL DMRS group may be identified at least based on the antenna port with the smallest index in the UL DMRS included in the UL DMRS group. UL PTRS may be mapped to the antenna port with the smallest index in one or more antenna ports to which one codeword is mapped. UL PTRS may be mapped to the first layer if one codeword is at least mapped to the first layer and the second layer. UL PTRS does not have to be mapped to the second layer. The index of the antenna port to which the UL PTRS is mapped may be given at least based on the downlink control information.

In FIG. 1, the following downlink physical channels are used in the downlink wireless communication from the base station device 3 to the terminal device 1. The downlink physical channel is used by the physical layer to transmit the information output from the upper layer.
・ PBCH (Physical Broadcast Channel)
・ PDCCH (Physical Downlink Control Channel)
・ PDSCH (Physical Downlink Shared Channel)

The PBCH is at least used to transmit the MIB and / or the PBCH payload. The PBCH payload may include at least information indicating an index regarding the transmission timing (SSB occupation) of the SSB. The PBCH payload may include information related to the SSB identifier (index). PBCH may be transmitted based on a predetermined transmission interval. PBCH may be transmitted at intervals of 80 milliseconds (ms). PBCH may be transmitted at intervals of 160 ms. The content of the information contained in the PBCH may be updated every 80 ms. Part or all of the information contained in the PBCH may be updated every 160 ms. The PBCH may be composed of 288 subcarriers. The PBCH may be configured to include 2, 3, or 4 OFDM symbols. The MIB may include information related to the SSB identifier (index). The MIB may include information indicating at least a portion of the slot number, subframe number, and / or radio frame number through which the PBCH is transmitted.

PDCCH is at least used for transmitting downlink control information (DCI). PDCCH may be transmitted including at least DCI. PDCCH may be transmitted including DCI. DCI may also be referred to as DCI format. The DCI may at least indicate either a downlink grant or an uplink grant. The DCI format used for PDSCH scheduling may also be referred to as the downlink DCI format and / or the downlink grant. The DCI format used for PUSCH scheduling may also be referred to as the uplink DCI format and / or the uplink grant. Downlink grants may also be referred to as downlink assignments or downlink assignments. The uplink DCI format includes at least one or both of DCI format 0_0 and DCI format 0_1.

DCI format 0_0 may be configured to include at least part or all of 1A to 1I.
1A) Identifier for DCI formats field
1B) Frequency domain resource allocation field
1C) Time domain resource allocation field
1D) Frequency hopping flag field
1E) MCS field (MCS field: Modulation and Coding Scheme field)
1F) NDI field (New Data Indicator field)
1G) RV field (Redundancy Version field)
1H) HPID field (HARQ process ID field, HARQ process number field)
1I) TPC command for scheduled PUSCH field (TPC command for scheduled PUSCH field)

1A may be at least used to indicate whether the DCI format containing the 1A corresponds to any of the DCI formats of one or more DCI formats. The one or more DCI formats may be given at least on the basis of DCI format 1_1, DCI format 1-11, DCI format 0_0, and / or part or all of DCI format 0_1. That is, the number of bits in 1A may be determined based on the number of corresponding DCI formats.

1B may at least be used to indicate the allocation of frequency resources for the PUSCH scheduled by the DCI format containing the 1B. The number of bits of the 1B may be determined based on the maximum number of PRBs used to allocate the frequency resources of the PUSCH, or may be determined based on the upper layer parameters.

1C may at least be used to indicate the allocation of time resources for PUSCH scheduled by the DCI format containing the 1C. The number of bits in the 1C may be determined based on the maximum number of symbols used to allocate the PUSCH time resource.

1D may at least be used to indicate whether frequency hopping is applied to the PUSCH scheduled by the DCI format containing the 1D.

1E may be at least used to indicate a modulation scheme for PUSCH scheduled by the DCI format containing the 1E and / or part or all of the target code rate. The target code rate may be the target code rate for the TB of the PUSCH. The size of the TB (TBS) may be given at least based on the target code rate.

The 1F determines whether the PUSCH transmission corresponding to the HPID value indicated by the 1H, scheduled by the DCI format, is a new transmission or a retransmission, based on whether the value of the 1F is toggled. Used to indicate. If the value of the 1F is toggled, the PUSCH corresponding to the 1H is a new transmission, otherwise the PUSCH corresponding to the 1H is a retransmission. The 1F may be a DCI indicating whether the base station apparatus 3 requests the retransmission of the PUSCH corresponding to the 1H.

1G is used to indicate the start position of the PUSCH bit sequence scheduled by the DCI format.

1H is used by the PUSCH scheduled by the DCI format to indicate the corresponding HARQ process number (HPID).

1I is used to adjust the PUSCH transmission power scheduled by the DCI format.

DCI format 0-1 is configured to include at least part or all of 2A to 2K.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field 2G) BWP field 2H) NDI field 2I) RV field 2J) HPID Field 2K) TPC command field for PUSCH

2F is at least used to direct CSI reporting. The size of the 2nd floor may be a predetermined value. The size of the 2nd floor may be 0, 1, may be 2, or may be 3. The size of the 2nd floor may be determined according to the number of CSI settings set in the terminal device 1.

2G may be used to indicate the uplink BWP to which the PUSCH scheduled in DCI format 0_1 is mapped.

The second CSI request field is at least used to direct CSI reporting. The size of the second CSI request field may be given at least based on the upper layer parameter ReportTriggerSize.

Of 2A to 2K, the fields with the same names as 1A to 1I described above include the same contents, so the description thereof will be omitted.

The downlink DCI format includes at least one or both of DCI format 1_0 and DCI format 1_1.

The DCI format 1_0 may be configured to include at least a part or all of 3A to 3K.
3A) Identifier for DCI formats field
3B) Frequency domain resource allocation field
3C) Time domain resource allocation field
3D) Frequency hopping flag field
3E) MCS field (MCS field: Modulation and Coding Scheme field)
3F) PDSCH to HARQ feedback timing indicator field
3G) PUCCH resource indicator field (PRI: PUCCH resource indicator field)
3H) NDI field 3I) RV field 3J) HPID field 3K) TPC command for scheduled PUCCH field

3B to 3E may be used for PDSCH scheduled by the DCI format.

The 3rd floor may be a field indicating timing K1. When the index of the slot containing the last OFDM symbol of the PDSCH is slot n, the index of the PUCCH containing at least HARQ-ACK corresponding to the TB contained in the PDSCH or the slot containing the PUSCH may be n + K1. .. When the index of the slot containing the last OFDM symbol of the PDSCH is slot n, the first OFDM symbol of the PUCCH containing at least the HARQ-ACK corresponding to the TB contained in the PDSCH or the first OFDM symbol of the PUSCH is included. The slot index may be n + K1.

3G may be a field indicating the index of one or more PUCCH resources included in the PUCCH resource set, or may be a value used to determine the PUCCH resource.

3H determines whether the PDSCH transmission corresponding to the HPID value indicated by the 3J, scheduled by the DCI format, is a new transmission or a retransmission, based on whether the value of the 3H is toggled. Used to indicate. If the value of the 3J is toggled, the PDSCH corresponding to the 3J is a new transmission, otherwise the PDSCH corresponding to the 3J is a retransmission.

3I may be used to indicate the start position of the PDSCH bit sequence scheduled by the DCI format.

3J may be used to indicate the number of the HARQ process to which the PDSCH scheduled by the DCI format corresponds.

3K may be used to adjust the transmission power of the PUCCH corresponding to the PDSCH scheduled by the DCI format.

The DCI format 1-11 may be configured to include at least a part or all of 4A to 4L.
4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4D) Frequency hopping flag field 4E) MCS field 4F) Timing instruction field from PDSCH to HARQ feedback 4G) PUCCH resource allocation field 4H) BWP Field 4I) NDI field 4J) RV field 4
K) HPID field 4L) TPC command field for PUCCH

3A, 4A, like 1A and 2A, are used to identify the DCI format.

1A, 2A, 3A, and 4A are used to indicate whether DCI format 0_0 or DCI format 1_0, or DCI format 0_1 or DCI format 1-11 when composed of 1 bit, respectively, in 2 bits. When configured, it may be used to indicate any one of the four DCI formats 0_1 to DCI format 1-1.1.

4B-4E may be used for PDSCH scheduled by the DCI format.

4J may be used to indicate the downlink BWP to which the PDSCH scheduled in DCI format 1-1-1 is mapped.

Of the 4A to 4L, the fields with the same names as the above-mentioned 3A to 3K include the same contents, so the description thereof will be omitted.

Each DCI format may include padding bits to fit a predetermined bit size (payload size). That is, it may be adjusted using one or more padding bits so that the size of each DCI format indicated by the DCI format specific field is the same.

DCI format 2 may include parameters used for PUSCH or PUCCH transmission power control.

In various aspects of this embodiment, unless otherwise specified, the number of resource blocks (RBs) indicates the number of resource blocks in the frequency domain. In addition, the index of the resource block is assigned in ascending order from the resource block mapped to the low frequency domain to the resource block mapped to the high frequency domain. The resource block is a general term for a common resource block and a physical resource block.

One physical channel may be mapped to one serving cell. One physical channel may be mapped to one CBP set for one carrier contained in one serving cell.

The terminal device 1 is given one or more control resource sets (CORESET). The terminal device 1 monitors the PDCCH in one or more CORESETs.

CORESET may indicate a time-frequency domain in which one or more PDCCHs can be mapped. CORESET may be an area in which the terminal device 1 monitors PDCCH. CORESET may be composed of continuous resources (Localized resources). CORESET may be composed of discontinuous resources.

In the frequency domain, the unit of CORESET mapping may be a resource block (RB). For example, in the frequency domain, the unit of CORESET mapping may be 6 resource blocks. That is, the mapping of the frequency domain of CORESET may be performed by 6RB × n (n is 1, 2, ...). In the time domain, the unit of CORESET mapping may be an OFDM symbol. For example, in the time domain, the unit of CORESET mapping may be one OFDM symbol.

The frequency domain of CORESET may be given at least based on the signal of the upper layer and / or DCI.

The time domain of CORESET may be given at least based on the signal of the upper layer and / or DCI.

A certain CORESET may be a common CORESET (Common CORESET). The common CORESET may be a CORESET that is commonly set for a plurality of terminal devices 1. Common CORESET may be given at least on the basis of MIB, SIB, common RRC signaling, and some or all of the cell IDs. For example, a CORESET time resource and / or frequency resource that is set to monitor the PDCCH used for SIB scheduling may be given at least based on the MIB.

A certain CORESET may be a dedicated CORESET (Dedicated CORESET). The dedicated CORESET may be a CORESET that is set to be used exclusively for the terminal device 1. Dedicated CORESET may be given at least on the basis of dedicated RRC signaling.

The set of PDCCH candidates monitored by the terminal device 1 may be defined from the viewpoint of the search area. That is, the set of PDCCH candidates monitored by the terminal device 1 may be given by the search area.

The search area may be configured to include one or more PDCCH candidates of one or more aggregation levels (AL). The aggregation level of PDCCH candidates may indicate the number of CCEs constituting the PDCCH.

The terminal device 1 may monitor at least one or a plurality of search areas in a slot in which DRX (Discontinuous reception) is not set. DRX may be given at least based on the parameters of the upper layer. The terminal device 1 may monitor at least one or a plurality of search area sets (Search space sets) in slots in which DRX is not set.

The search area set may be configured to include at least one or a plurality of search areas. The types of the search area set are type 0PDCCH common search area (common search space), type 0a PDCCH common search area, type 1 PDCCH common search area, type 2 PDCCH common search area, type 3 PDCCH common search area, and / or UE individual PDCCH search. It may be any of the regions.

The type 0PDCCH common search area, the type 0aPDCCH common search area, the type 1PDCCH common search area, the type 2PDCCH common search area, and the type 3PDCCH common search area may also be referred to as CSS (Common Search Space). The UE individual PDCCH search area may also be referred to as USS (UE specific Search Space).

Each of the search area sets may be related to one control resource set. Each of the search area sets may be included in at least one control resource set. For each of the search area sets, an index of the control resource set associated with the search area set may be given.

The type 0PDCCH common search area may be at least used for DCI formats with CRC (Cyclic Redundancy Check) sequences scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The setting of the type 0 PDCCH common search area may be given at least based on 4 bits of the LSB (Least Significant Bits) of the upper layer parameter PDCCH-ConfigSIB1. The upper layer parameter PDCCH-ConfigSIB1 may be included in the MIB. The setting of the type 0PDCCH common search area may be given at least based on the parameter SearchSpaceZero of the upper layer. The interpretation of the bits of the upper layer parameter SearchSpaceZero may be the same as the interpretation of the LSB of the upper layer parameter PDCCH-ConfigSIB1. The setting of the type 0PDCCH common search area may be given at least based on the parameter SearchSpaceSIB1 of the upper layer. The upper layer parameter SearchSpaceSIB1 may be included in the upper layer parameter PDCCH-ConfigCommon. The PDCCH detected in the type 0 PDCCH common search area may be at least used for scheduling the PDSCH transmitted including the SIB1. SIB1 is a kind of SIB. SIB1 may include scheduling information of SIB other than SIB1. The terminal device 1 may receive the parameter PDCCH-ConfigCommon of the upper layer in EUTRA. The terminal device 1 may receive the parameter PDCCH-ConfigCommon of the upper layer in the MCG.

The type 0aPDCCH common search area may be at least used for DCI formats with CRC (Cyclic Redundancy Check) sequences scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The setting of the type 0aPDCCH common search region may be given at least based on the upper layer parameter SearchSpaceOtherSystemInformation. The upper layer parameter SearchSpaceOtherSystemInformation may be included in SIB1. The upper layer parameter SearchSpaceOtherSystemInformation may be included in the upper layer parameter PDCCH-ConfigCommon. The PDCCH detected in the type 0 PDCCH common search area may be at least used for scheduling PDSCHs transmitted including SIBs other than SIB1.

The Type 1 PDCCH common search region is accompanied by a CRC sequence scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) and / or a CRC sequence scrambled by TC-RNTI (Temporary Common-Radio Network Temporary Identifier). It may be at least used for the DCI format. RA-RNTI may be given at least based on the time / frequency resources of the random access preamble transmitted by terminal device 1. TC-RNTI is provided by PDSCH (also referred to as Random Access Message 2, Message 2 (Msg2), or Random Access Response (RAR)) scheduled by the DCI format with a CRC sequence scrambled by RA-RNTI. May be done. The type 1 PDCCH common search area may be given at least based on the upper layer parameter ra-SearchSpace. The upper layer parameter ra-SearchSpace may be included in SIB1. The upper layer parameter ra-SearchSpace may be included in the upper layer parameter PDCCH-ConfigCommon.

The Type 2 PDCCH common search area may be used for DCI formats with CRC sequences scrambled by P-RNTI (Paging-Radio Network Temporary Identifier). P-RNTI may at least be used for transmission of DCI format containing information notifying SIB changes. The type 2 PDCCH common search area may be given at least based on the upper layer parameter PagingSearchSpace. The upper layer parameter PagingSearchSpace may be included in SIB1. The upper layer parameter PagingSearchSpace may be included in the upper layer parameter PDCCH-ConfigCommon.

The Type 3 PDCCH common search area may be used for DCI formats with CRC sequences scrambled by C-RNTI (Cell-Radio Network Temporary Identifier). C-RNTI is on a PDSCH (also referred to as Random Access Message 4, Message 4 (Msg4), or Contention Resolution) scheduled by the DCI format with a CRC sequence scrambled by TC-RNTI. It may be given at least on the basis. The type 3 PDCCH common search area may be a search area set given when the parameter SearchSpaceType of the upper layer is set to common.

The UE individual PDCCH search region may be at least used for DCI formats with CRC sequences scrambled by C-RNTI.

When C-RNTI is given to the terminal device 1, the type 0PDCCH common search area, the type 0aPDCCH common search area, the type 1PDCCH common search area, and / or the type 2PDCCH common search area are CRC scrambled by C-RNTI. It may be used at least for DCI formats with sequences.

When C-RNTI is given to the terminal device 1, the upper layer parameter PDCCH-ConfigSIB1, the upper layer parameter SearchSpaceZero, the upper layer parameter SearchSpaceSIB1, the upper layer parameter SearchSpaceOtherSystemInformation, the upper layer parameter scrace The search region set given at least based on any of the parameters PagingSearchSpace may be used at least for DCI formats with CRC sequences scrambled with C-RNTI.

The common CORESET may include at least one or both of CSS and USS. The dedicated CORESET may include at least one or both of CSS and USS.

The physical resources in the search area are composed of control channel configuration units (CCE: Control Channel Element). CCE is composed of 6 resource element groups (REG: ResourceElementGroup). The REG may be composed of one OFDM symbol of one PRB (Physical Resource Block). That is, the REG may be configured to include 12 resource elements (RE: ResourceElement). The PRB may also be simply referred to as a resource block (RB).

PDSCH is at least used to transmit TB. The PDSCH may also be at least used to transmit a random access message 2 (RAR, Msg2). The PDSCH may also be at least used to transmit system information, including parameters used for initial access.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. The downlink physical signal does not have to be used to transmit the information output from the upper layer, but it is used by the physical layer.
-Synchronization signal
・ DL DMRS (DownLink DeModulation Reference Signal)
・ CSI-RS (Channel State Information-Reference Signal)
・ DL PTRS (DownLink Phase Tracking Reference Signal)
・ TRS (Tracking Reference Signal)

The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and / or the time domain. The synchronization signal includes PSS (PrimarySynchronizationSignal) and SSS (SecondarySynchronizationSignal).

SSB (SS / PBCH block) is composed of PSS, SSS, and at least a part or all of PBCH. The antenna ports of PSS, SSS, and a part or all of PBCH included in the SS block may be the same. Some or all of the PSS, SSS, and PBCH contained in the SSB may be mapped to consecutive OFDM symbols. The CP settings of PSS, SSS, and part or all of PBCH contained in SSB may be the same. The same value may be applied to the SCS setting μ for each of PSS, SSS, and a part or all of PBCH contained in SSB.

DL DMRS is associated with the transmission of PBCH, PDCCH, and / or PDSCH. DL DMRS is multiplexed on PBCH, PDCCH, and / or PDSCH. The terminal device 1 may use the PBCH, the PDCCH, or the DL DMRS corresponding to the PDSCH to correct the propagation path of the PBCH, PDCCH, or PDSCH. Hereinafter, the transmission of PBCH and DL DMRS related to the PBCH together may be referred to as transmission of PBCH. Further, the transmission of the PDCCH and the DL DMRS associated with the PDCCH together may be referred to simply as the transmission of the PDCCH. Further, the transmission of the PDSCH and the DL DMRS related to the PDSCH together may be referred to simply as the PDSCH being transmitted. DL DMRS related to PBCH may also be referred to as DL DMRS for PBCH. The DL DMRS associated with the PDSCH may also be referred to as the PDSCH DL DMRS. DL DMRS associated with PDCCH may also be referred to as DL DMRS associated with PDCCH.

The DL DMRS may be a reference signal individually set in the terminal device 1. The DL DMRS sequence may be given at least based on parameters individually set in the terminal device 1. The DL DMRS sequence may be given at least based on UE-specific values (eg, C-RNTI, etc.). DL DMRS may be transmitted individually for PDCCH and / or PDSCH.

CSI-RS may be at least a signal used to calculate CSI. Further, CSI-RS may be used for measuring RSRP (Reference Signal Received Power) and RSRQ (Reference Signal Received Quality). The pattern of CSI-RS assumed by the terminal device 1 may be given by at least the parameters of the upper layer.

The PTRS may be at least a signal used to compensate for phase noise. The pattern of PTRS assumed by the terminal device 1 may be given at least based on the parameters of the upper layer and / or DCI.

The DL PTRS may be associated with a DL DMRS group that includes at least the antenna ports used for one or more DL DMRSs. The association between the DL PTRS and the DL DMRS group may be that the antenna port of the DL PTRS and a part or all of the antenna ports included in the DL DMRS group are at least QCL. The DL DMRS group may be identified based on at least the antenna port having the smallest index in the DL DMRS included in the DL DMRS group.

The TRS may be at least a signal used for time and / or frequency synchronization. The pattern of TRS assumed by the terminal device may be given at least based on the parameters of the upper layer and / or DCI.

The downlink physical channel and the downlink physical signal may also be referred to as a downlink physical signal. The uplink physical channel and the uplink physical signal may also be referred to as an uplink signal. The downlink signal and the uplink signal may be collectively referred to as a physical signal or a signal. The downlink physical channel and the uplink physical channel may be collectively referred to as a physical channel. In the downlink, the physical signal may include a part or all of SSB, PDCCH (CORESET), PDSCH, DL DMRS, CSI-RS, DL PTRS, and TRS. Further, in the uplink, the physical signal may include a part or all of PRACH, PUCCH, PUSCH, UL DMRS, UL PTRS, and SRS. The physical signal may be a signal other than the above-mentioned signal. That is, the physical signal may include one or more types of physical channels and / or physical signals, or may include one or more physical channels and / or physical signals.

BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel) and DL-SCH (Downlink-Shared CHannel) are transport channels. The channels used in the medium access control (MAC) layer may be referred to as transport channels. The unit of the transport channel used in the MAC layer may also be referred to as TB or MAC PDU. HARQ is controlled for each TB in the MAC layer. TB is a unit of data delivered by the MAC layer to the physical layer. In the physical layer, TB is mapped to codewords, and modulation processing is performed for each codeword.

The base station device 3 and the terminal device 1 exchange (transmit / receive) signals of the upper layer in the upper layer. For example, the base station device 3 and the terminal device 1 may transmit and receive RRC signaling (RRC message, RRC information, RRC parameter, RRC information element) in the radio resource control (RRC) layer. Further, the base station device 3 and the terminal device 1 may transmit and receive MAC CE (Control Element) in the MAC layer. Here, RRC signaling and / or MAC CE is also referred to as higher layer signaling.

PUSCH and PDSCH may at least be used to transmit RRC signaling and / or MAC CE. Here, the RRC signaling transmitted from the base station device 3 by PDSCH may be a signal common to a plurality of terminal devices 1 in the serving cell. Signaling common to a plurality of terminal devices 1 in the serving cell may also be referred to as common RRC signaling. The RRC signaling transmitted from the base station apparatus 3 by PDSCH may be a dedicated signaling (also referred to as dedicated signaling or UE specific signaling) for a certain terminal apparatus 1. The signaling dedicated to the terminal device 1 may also be referred to as dedicated RRC signaling. The parameters of the upper layer unique to the serving cell may be transmitted by using common signaling to a plurality of terminal devices 1 in the serving cell or by using dedicated signaling to a certain terminal device 1. UE-specific upper layer parameters may be transmitted to a terminal device 1 using dedicated signaling.

BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. For example, BCCH is a higher layer channel used to transmit MIBs. Further, CCCH (Common Control CHannel) is an upper layer channel used for transmitting common information in a plurality of terminal devices 1. Here, CCCH may be used, for example, for a terminal device 1 that is not RRC-connected. Further, the DCCH (Dedicated Control Channel) is an upper layer channel that is at least used for transmitting dedicated control information to the terminal device 1. Here, the DCCH may be used, for example, for the terminal device 1 connected by RRC.

BCCH in the logical channel may be mapped to BCH, DL-SCH, or UL-SCH in the transport channel. CCCH in a logical channel may be mapped to DL-SCH or UL-SCH in a transport channel. DCCH in a logical channel may be mapped to DL-SCH or UL-SCH in a transport channel.

UL-SCH in the transport channel may be mapped to PUSCH in the physical channel. The DL-SCH in the transport channel may be mapped to the PDSCH in the physical channel. BCH in the transport channel may be mapped to PBCH in the physical channel.

Hereinafter, a configuration example of the terminal device 1 according to one aspect of the present embodiment will be described.

FIG. 11 is a schematic block diagram showing the configuration of the terminal device 1 according to one aspect of the present embodiment. As shown in the figure, the terminal device 1 includes a wireless transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes at least a part or all of an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes at least a part or all of the medium access control layer processing unit 15 and the radio resource control layer processing unit 16. The wireless transmission / reception unit 10 may also be referred to as a transmission unit, a reception unit, a physical layer processing unit, and / or a lower layer processing unit.

The upper layer processing unit 14 outputs the uplink data (TB, UL-SCH) generated by the user's operation or the like to the wireless transmission / reception unit 10. The upper layer processing unit 14 processes the MAC layer, the packet data integration protocol (PDCP) layer, the wireless link control (RLC) layer, and the RRC layer.

The medium access control layer processing unit 15 included in the upper layer processing unit 14 processes the MAC layer.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 processes the RRC layer. The wireless resource control layer processing unit 16 manages various setting information / parameters of its own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on the signal of the upper layer received from the base station apparatus 3. That is, the radio resource control layer processing unit 16 sets various setting information / parameters based on the information indicating various setting information / parameters received from the base station apparatus 3. The parameter may be an upper layer parameter and / or an information element.

The wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, coding, and decoding. The wireless transmission / reception unit 10 separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. These processes may be referred to as reception processes. The wireless transmission / reception unit 10 generates a physical signal (uplink signal) by modulating, encoding, and generating a baseband signal (converting to a time continuous signal), and transmits the physical signal (uplink signal) to the base station apparatus 3. These processes may be referred to as transmission processes.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation (down-conversion), and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to the CP from the converted digital signal, performs a fast Fourier transform (FFT) on the signal from which the CP has been removed, and extracts a signal in the frequency domain.

The baseband unit 13 performs inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds CP to the generated OFDM symbol, generates a baseband digital signal, and generates a baseband digital signal. Convert to analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 removes an extra frequency component from the analog signal input from the baseband unit 13 using a low-pass filter, up-converts the analog signal to a carrier frequency, and transmits the analog signal via the antenna unit 11. Further, the RF unit 12 amplifies the electric power. Further, the RF unit 12 may have a function of controlling the transmission power. The RF unit 12 is also referred to as a transmission power control unit.

Hereinafter, a configuration example of the base station device 3 according to one aspect of the present embodiment will be described.

FIG. 12 is a schematic block diagram showing the configuration of the base station device 3 according to one aspect of the present embodiment. As shown in the figure, the base station apparatus 3 includes a wireless transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transmission / reception unit 30 is also referred to as a transmission unit, a reception unit, or a physical layer processing unit.

The upper layer processing unit 34 processes the MAC layer, PDCP layer, RLC layer, and RRC layer.

The medium access control layer processing unit 35 included in the upper layer processing unit 34 processes the MAC layer.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 processes the RRC layer. The wireless resource control layer processing unit 36 generates downlink data (TB, DL-SCH), system information, RRC message, MAC CE, etc., which are arranged in the PDSCH, or acquires them from a higher-level node and sends them to the wireless transmission / reception unit 30. Output. Further, the wireless resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1. The wireless resource control layer processing unit 36 may set various setting information / parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 transmits / notifies information indicating various setting information / parameters.

Since the basic functions of the wireless transmission / reception unit 30 are the same as those of the wireless transmission / reception unit 10, the description thereof will be omitted. The physical signal generated by the wireless transmission / reception unit 30 is transmitted to the terminal device 1 (that is, transmission processing is performed). In addition, the wireless transmission / reception unit 30 performs reception processing of the received physical signal.

The medium access control layer processing unit 15 and / or 35 may be referred to as a MAC entity.

Each part of the terminal device 1 with reference numerals 10 to 16 may be configured as a circuit. Each part of the base station apparatus 3 with reference numerals 30 to 36 may be configured as a circuit. A part or all of the parts of reference numerals 10 to 16 included in the terminal device 1 may be configured as a memory and a processor connected to the memory. A part or all of the part of the base station apparatus 3 with reference numerals 30 to 36 may be configured as a memory and a processor connected to the memory. Various aspects (operations, processes) according to the present embodiment may be realized (performed) in the memory included in the terminal device 1 and / or the base station device 3 and the processor connected to the memory.

FIG. 13 is a diagram showing an example of a channel access procedure (CAP) according to one aspect of the present embodiment. The terminal device 1 or the base station device 3 performs energy detection before transmitting a predetermined physical signal, and carries out NR-U cell transmission (that is, NR-U carrier) or BWP (that is, NR-U BWP). ) Or channel (that is, NR-U channel), idle (clear, free, no communication, no specific physical signal transmitted, power (energy) of a specific physical signal for a predetermined period of time. If it is determined that undetected, detected (measured) power (energy) or total power does not exceed a predetermined threshold), a physical signal may be transmitted on the carrier or BWP or channel. That is, when the terminal device 1 or the base station device 3 communicates in the NR-U cell, CCA (Clear Channel Assessment) or channel measurement for confirming that the NR-U cell is idle for a predetermined period of time. To do. The predetermined period may be determined from the delay period T _d , the counter N, and the CCA slot period T _sl. It should be noted that when the CCA is performed, the fact that the person is not an idol may be referred to as busy. The CCA may be performed by the wireless transmission / reception unit 10 of the terminal device 1 and / or the wireless transmission / reception unit 30 of the base station device 3. The channel access procedure may include performing CCA for a predetermined period of time before the terminal device 1 or the base station device 3 transmits a physical signal on a certain channel. Before sending such a physical signal, a procedure that performs energy detection to determine if the channel is idle, or a procedure that determines if the channel is idle and sends the physical signal if it is idle. The procedure to be transmitted may be referred to as a channel access procedure and / or a CCA procedure and / or an LBT (Listen Before Talk) procedure. Here, the NR-U cell may be an NR-U carrier and / or an NR-U BWP and / or an NR-U channel, and includes at least a frequency band available for transmitting the physical signal of the NR-U. But it may be. That is, NR-U cells and NR-U carriers and NR-U BWP and NR-U channels may be synonymous. In this embodiment, the NR-U cell may be paraphrased as an NR-U carrier, an NR-U BWP, and / or an NR-U channel. The NR-U cell may be configured to include at least one of an NR-U carrier, an NR-U BWP, and an NR-U channel. The NR cell may be configured to include at least one of an NR carrier, an NR BWP, and an NR channel.

Here, if the base station apparatus 3 and / or the terminal apparatus 1 can (capacity) perform a multicarrier access procedure (CAP for each of the multicarriers) in one NR-U operating band, 1 A plurality of carriers (NR-U carriers) and / or a plurality of BWPs (NR-U BWPs) may be set for one NR-U cell.

The predetermined period is a period during which the counter N becomes 0 in the channel that first senses that it is idle in the delay period after detecting a signal other than the own device. The terminal device 1 or the base station device 3 can transmit a signal after the value of the counter N becomes 0. If it is determined that the counter is busy during the CCA slot period, the decrement of the counter N may be postponed. The initial value N _int of the counter N may be determined based on the value of the channel access priority class and the corresponding CW _p (Contention Window) value (CWS: CW size). For example, the value of _{N int} may be determined based on a randomly distributed random function between _{0 and CW p values.} Possible values of N _int by the value of CW _p is updated (value range) it may be enlarged.

The terminal device 1 or the base station device 3 sets _{the value of the counter N to N int} when transmitting one or more physical signals in the NR-U cell.

When the value of N is larger than 0, the terminal device 1 or the base station device 3 sets the value of N to N-1 if it determines that the value is clear in one CCA slot period. That is, if the terminal device 1 or the base station device 3 determines that the value is clear in one CCA slot period, only one value of the counter N may be decremented.

When the decremented value of N becomes 0, the terminal device 1 or the base station device 3 may stop the CCA during the CCA slot period. If this is not the case, that is, if the value of N is greater than 0, the terminal device 1 or base station device 3 continues to perform CCA for the CCA slot period until the value of N becomes 0. You may.

The terminal device 1 or the base station device 3 can perform CCA in the added CCA slot period, determine that it is idle, and transmit a physical signal if the value of N is 0. ..

The terminal device 1 or the base station device 3 may perform CCA until it is determined to be busy in the added delay period or idle in all the slots of the added delay period. .. If it is determined to be idle and the value of N is 0 in the added delay period, the terminal device 1 or the base station device 3 can transmit a physical signal. The terminal device 1 or the base station device 3 may continue the CCA if it determines that it is busy in the added delay period.

A channel access procedure in which the values of CAPC p and CW _p are variable based on the set information and conditions is called a type 1 channel access procedure (type 1 CAP), and _{the value of CW p} is always 0 or is always 0. A _{channel access procedure that does not use the counter N corresponding to the value of CW p} or that performs CCA only once before transmission may be referred to as a type 2 channel access procedure (type 2 CAP). That is, the type 1 channel access procedure is a channel access procedure in which the CCA period changes depending _{on the set CAPC value p or the CW p value updated based on the condition.} Further, the type 2 channel access procedure is a channel access procedure capable of performing CCA only once before transmitting a physical signal, and if it is determined that the channel (frequency band) for transmitting the physical signal is idle, transmission can be performed. That is. Here, the term "before transmission" may include immediately before transmission. If the channel access procedure is not completed before the transmission of the physical signal, the terminal device 1 and / or the base station device 3 does not transmit the physical signal at the transmission timing, or even if the physical signal is postponed. Good. Further, a channel access procedure that does not perform CCA before transmission may be referred to as a type 3 channel access procedure (type 3 CAP). Whether it is type 2 CAP or type 3 CAP may be determined based on the upper layer parameters.

FIG. 14 is a diagram showing an example of a channel access priority class (CAPC) and a CW adjustment procedure according to one aspect of the present embodiment.

The value p of CAPC is to indicate the number _{m p} of CCA slot period _{T sl} included in the delay time _{T d,} the minimum and maximum values of CW, the maximum channel occupation time, acceptable values of CW _p a (CWS) Used for. The value p of the CAPC may be set according to the priority of the physical signal. The value p of the CAPC may be included and shown in the DCI format.

The terminal device 1 may adjust the value of CW for determining the value of _{N init} before setting the value of counter N to N _init. The terminal device 1 may maintain the updated CW value for the random access procedure when the random access procedure is completed successfully. Further, the terminal device 1 may set _{the updated CW value to CW min} for the random access procedure when the random access procedure is completed successfully. Here, in the present embodiment, CW _min may be, for example, CW # 0 shown in FIG. 14, that is, the initial value of _{CW p corresponding to the value p of CAPC.} Here, the value of the updated CW to set the CW _min may be to update the value of CW is updated if it meets one or more predetermined conditions in CW _min. Further, the value of the updated CW to set the _{CW min} may be that re-sets the value of CW to _{CW min.}

Terminal device 1, before setting the _{N init} to the value of the counter N which corresponds to the CCA performed before sending _Msg1, may adjust the value of CW for determining the value of _{N init.} The terminal device 1 may maintain the updated CW value when it considers that the reception of Msg2 is successful and / or when it considers that the reception of Msg4 is successful. Further, the terminal device 1 may set _{the updated CW value to CW min} when it considers that the reception of Msg2 is successful and / or when it considers that the reception of Msg4 is successful. ..

Here, adjusting the value of CW _{may mean increasing the value of CW p} one step at a time from CW _{min to reaching CW max} when a predetermined condition is satisfied. When it reaches _{CW max,} it increases step by step from _{CW min.} That is, adjusting the value of CW may mean updating the value of _{CW p.} And updates the value of CW _p is the value of CW _p may be to one step larger value. For example, it may be changed from CW # 3 to CW # 4, or it may be changed from CW # n-1 to CW # n. The terminal device 1 and / or the base station apparatus 3, each time adjusting the value of CW, from 0, the value of N _init based on random function that is uniformly distributed between the updated value of the CW _p You may decide.

The channel access priority class (CAPC) value p applied to the transmission of Msg1 may be determined based on system information, may be determined based on higher layer parameters, or may be associated with SSB. Good. For example, when the value p of CAPC corresponding to Msg1 is P, _{the value of Init} is determined based on a random function uniformly distributed between 0 and CW # 0.

The CAPC value p may be set individually for each of PUSCH, PUCCH, and PRACH. Further, the CAPC value p may be set to a value common to PUSCH, PUCCH, and PRACH as a cell-specific upper layer parameter. Further, the value p of CAPC may be set as an individual upper layer parameter for each of PUSCH, PUCCH, and PRACH. Also, the CAPC value p for PUSCH may be included and shown in the DCI format used for PUSCH scheduling. Also, the CAPC value p for PUCCH may be included and shown in the DCI format including the PUCCH resource indicator field. Also, the CAPC value p for PRACH may be included and shown in the DCI format for PDCCH order. Further, the value p of CAPC for PRACH may be determined according to the type of random access procedure. For example, the value p of CAPC for CBRA may be determined based on system information and / or higher layer parameters. Further, the value p of CAPC with respect to CFRA may be determined based on the upper layer parameter, or may be included in the DCI format corresponding to the PDCCH order and set. In the CFRA, whether the value p of the CAPC is based on the upper layer parameters or the DCI format fields may be determined based on the system information and / or the setting of the upper layer parameters.

When the terminal device 1 transmits HARQ-ACK to the PDSCH with the PUCCH resource, the type of channel access procedure for the PUCCH and / or the value p of the CAPC may be one or more dedicated to the DCI format used for scheduling the PDSCH. Fields may be included and set. The DCI format may include a PUCCH resource indicator field. That is, for the PUCCH resource indicated by the PUCCH resource indicator field, the type and / or CAPC value of the channel access procedure for the PUCCH may be used. Further, when the terminal device 1 transmits SR by the PUCCH resource, the type of the channel access procedure for PUCCH and / or the value p of CAPC is based on one or more upper layer parameters included in the PUCCH setting or SR setting. May be set.

The value p of CAPC may be determined for PUSCH and PUCCH in association with the information to be transmitted. For example, when UCI is included in PUSCH or PUCCH for transmission, the CAPC value p may be set individually according to the type (HARQ-ACK, SR, CSI, etc.) and combination of information included in UCI.

In this embodiment, the CAPC value p is described, but the channel access procedure (CAP) type (type 1 CAP, type 2 CAP, that is, CAT (Channel Access Type)), CW value, and / or T. _{The value of mcot} may be set in the same manner. Further, regarding CAT, CAT1 may indicate type 1 CAP, and CAT 2 may indicate type 2 CAP.

For example, in the DCI format (DCI format 0_0, 0_1, 1_0, 1_1) used for PDSCH and PUSCH scheduling and PRACH resource allocation in the NR-U cell, the following 8A to the following 8E are used to perform a channel access procedure. Part or all of may be included as fields respectively.
8A) Channel access procedure (CAP) type (channel access type (CAT))
8B) Channel access priority class (CAPC) value p
8C) Maximum channel exclusive time T _mcot
8D) CW value 8E) Maximum number of m in CCA slot period

For PUCCH, some or all of 8A to 8E may be predetermined values, or may be determined based on the upper layer parameters for each.

If the DCI format (1_0, 1_1) used for PDSCH scheduling includes a PUCCH resource indicator field in addition to some or all of the 8A to 8E, the channel access before transmission of the PUCCH to the PDSCH HARQ-ACK. The procedure may be based on at least one of 8A to 8E included in the DCI format.

If the received DCI format indicates a random access preamble resource allocation, that is, if a PDCCH order is received and the PDCCH order contains part or all of the 8A to 8E, then the random access preamble is used. The channel access procedure before transmission may be performed based on a part or all of the above 8A to the above 8E included in the PDCCH order.

When SR is transmitted by PUCCH in the NR-U carrier, a part or all of the above 8A to 8E may be included in the PUCCH setting or SR setting. That is, when the channel access procedure is performed on the PUCCH including the SR, the parameters for the channel access procedure may be set based on the upper layer parameters. When the channel access procedure is performed on the PUCCH including the SR, the parameters for the channel access procedure are transmitted from the base station device 3 to the terminal device 1 via the signal of the RRC layer and set. May be good.

Next, the HARQ operation according to this embodiment will be described.

The MAC entity of the terminal device 1 may include at least one HARQ entity for each serving cell. At least one HARQ entity can maintain many parallel HARQ processes. Each HARQ process may be associated with one HPID. The HARQ entity directs the HARQ information and the associated TB received in the DL-SCH to the corresponding HARQ process.

The number (maximum number) of DL HARQ processes that can be parallelized for each HARQ entity may be set based on the upper layer parameter (for example, RRC parameter), or the default value if the upper layer parameter is not received. May be. A dedicated broadcast HARQ process may be used for BCCH. The broadcast HARQ process may be referred to as a broadcast process.

The HARQ process supports one TB when the physical layer is not configured for downlink spatial multiplexing. The HARQ process also supports one or two TBs when the physical layer is configured for downlink spatial multiplexing.

The MAC entity of the terminal device 1 may provide the number of TB transmissions in the bundle of dynamic downlink assignments when the higher layer parameter pdsch-AggressionFactor with a value greater than 1 is set. .. The bundling operation (HARQ-ACK bundling operation) relies on a HARQ entity to call (launch) the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, the retransmission of HARQ that is one less than the value set by the pdsch-AggressionFactor (ie, pdsch-AggressionFactor-1) may continue within the bundle.

The MAC entity of terminal device 1 may assign one or more TBs received from the physical layer and associated HARQ information to the HARQ process indicated by the associated HARQ information, given that the downlink assignment is indicated. Good. Further, the MAC entity of the terminal device 1 may assign the received TB to the broadcast HARQ process if the downlink assignment is indicated to the broadcast HARQ process.

When a transmission is made for the HARQ process, HARQ information associated with one or two TBs (in the case of downlink space multiplexing) may be received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process (the HARQ process associated with an HPID), when provided with an NDI, corresponds to this TB, the value of the previously received transmission. If toggled in comparison to (value of NDI associated with HPID contained in PDCCH), or the HARQ process corresponds to the broadcast process and this corresponds to the system information schedule indicated by the RRC. If it is the first received transmission to the TB, or if this is really the first received transmission to this TB (ie, there is no previous NDI for this TB (does not exist). ), New transmission), this transmission is regarded as a new transmission. If not, the HARQ process considers this transmission to be a retransmission. The previously received transmission may be a transmission received in the past. Here, the transmission may be a TB transmitted from the base station apparatus 3.

The MAC entity attempts to decode the received data (data for the received TB) if this (received TB) is a new transmission. The MAC entity also combines the physical layer with the data that received the latest data in the soft buffer for this TB, if this is a retransmission and the data for this TB has not yet been successfully decoded. Instruct to do and decode the combined data. Also, the MAC entity is HARQ if the data that the MAC entity tried to decode was successfully decoded for this TB, or if the data for this TB was previously successfully decoded. If the process is the same as the broadcast process, the decoded MAC PDU is transferred to the upper layer (RLC layer, PDCP layer, and / or RRC layer). Also, if this is the first successful decoding of the data for this TB, the MAC entity transfers the decoded MAC PDU to the disassembly and demultiplexing entity. If not, the MAC entity instructs the physical layer to replace the data that the MAC entity tried to decode with the data in the soft buffer for this TB. The MAC entity if the HARQ process is associated with the transmission shown with TC-RNTI and the contention resolution is not yet successful, or if the HARQ process corresponds to the broadcast process, or When the timeIdententTime related to the TAG containing the serving cell to which the HARQ feedback is transmitted stops or expires, it instructs the physical layer to generate an acquiredgement (s) of data in this TB. The acknowledgment may be ACK or NACK.

In the NR-U cell, the MAC entity of terminal device 1 and / or terminal device 1 is instructed to generate an acknowledgment (s) of data in this TB when this transmission is considered to be a retransmission in this HARQ process. The physical layer of the terminal device 1 may update the value of CW used for _{N init} if the type 1 channel access procedure is performed before the transmission of PUCCH or PUSCH including HARQ-ACK. Also, in the NR-U cell, the MAC entity of terminal device 1 and / or terminal device 1 acknowledges the data acknowledgedgement (s) in this TB when this transmission is considered to be a new transmission in this HARQ process. It indicated physical layer of the terminal device 1 produced is, if performing the type 1 channel access procedure before the PUCCH or PUSCH transmissions including _HARQ-ACK, the initial value of the CW used in the _{N init} of CW _p It may be set to a value or the CW value may not be updated (that is, the CW value may be maintained). If the physical layer of the terminal device 1 performs a type 2 channel access procedure before the transmission of PUCCH or PUSCH including HARQ-ACK, regardless of whether this transmission is a new transmission or a retransmission, HARQ If the CCA is performed only once before the transmission of the PUCCH or PUSCH containing -ACK and it is determined that the NR-U channel is idle, the PUCCH or PUSCH containing HARQ-ACK may be transmitted.

Here, updating the CW value means that, for example, there are three types of CW allowable values that can be set: CW # 0, CW # 1, and CW # 2 (CW # 0 <CW # 1 <CW # 2). Then, when the value of CW is CW # 0, the value of CW is updated to CW # 1, which is one value higher. Further, updating the CW value means updating the CW value to CW # 2, which is one higher value, when the CW value is CW # 1. In addition, updating the CW value means that when the CW value is CW # 2 (CW _max ) and there is no value one level higher than the CW value, it is set _{to CW # 0 (CW min).} It may include re-doing.

Here, the physical layer may include at least one of a transmission unit, a reception unit, a wireless transmission / reception unit, and / or a measurement unit, and may be a physical layer processing unit. The MAC entity may be a MAC layer or a MAC layer processing unit.

When the MAC entity determines that the NDI in PDCCH for that C-RNTI is toggled compared to the value in the previous transmission, it determines the NDI received in all downlink assignments in PDCCH for that TC-RNTI. ignore.

When the terminal device 1 detects in the PDCCH the DCI format used for scheduling the PDSCH in the NR-U cell, it is said that the DCI format contains the HARQ process ID (HPID) and the NDI. For example, it can be determined whether the PDSCH transmission is a new transmission or a retransmission based on whether NDI is toggled for the HPID. Further, if the DCI format contains a field indicating a PUCCH resource, it may be determined whether or not to adjust the value of CW based on whether or not the NDI is toggled. For example, terminal device 1 sets the value of CW _{p corresponding to the value p of each CAPC to CW min} if the value of NDI for the HARQ process associated with the first HPID is toggled, otherwise. If so (that is, if the value of the NDI is not toggled), the terminal device 1 _{may increase the value of CW p} to the next higher tolerance (the value of CW) (ie, the terminal). The device 1 _{may update the value of CW p} (value of CW)).

When the terminal device 1 generates a HARQ-ACK codebook for a HARQ process related to one or more HPIDs, the HARQ-ACK codebook if the value of NDI is not toggled for at least one HPID. The value of CW for a type 1 channel access procedure performed prior to transmission of the PUCCH or PUSCH containing the above may be updated.

When transmitting the PDCCH including the DCI format used for scheduling the PDSCH in the NR-U cell and the PDSCH, the base station apparatus 3 performs a type 1 channel access procedure before transmitting the PDCCH and the PDSCH. If it is determined that the NR-U channel is idle for all CCA slot periods, then the PDCCH and the PDSCH are transmitted, and if it is determined that the NR-U channel is not idle, then the NR-U channel is all CCA. Transmission of the PDCCH and the PDSCH may be postponed until it can be determined to be idle during the slot period.

If the base station apparatus 3 cannot successfully receive the PUCCH or PUSCH containing HARQ-ACK for the PDCCH even after a predetermined period of time has elapsed after transmitting the PDCCH and the PDSCH, the PDCCH and the PDCCH and the PDCCH The PDSCH may be retransmitted. When the base station apparatus 3 retransmits the PDCCH and the PDSCH, the value of NDI for the HPID is transmitted without toggle. That is, the base station apparatus 3 may indicate that the PDSCH is retransmission by not toggle the value of NDI for the HPID. At that time, when the base station apparatus 3 performs the type 1 channel access procedure, the value of CW may be updated.

After transmitting the PDCCH and the PDSCH, the base station apparatus 3 successfully receives the PUCCH or PUSCH containing the HARQ-ACK for the PDSCH corresponding to the HARQ process related to the HPID within a predetermined period of time. If possible, the value of CW corresponding to the HARQ process for the HPID may be reset to _{CW min.} That is, in order to toggle the value of NDI for the HARQ process associated with the HPID, if the base station apparatus 3 performs a channel access procedure before transmission of the PDCCH and the PDSCH, the value of the CW is set to CW _min . You may set it. Here, if the base station apparatus 3 can manage the HARQ process related to a plurality of HPIDs, the base station apparatus 3 may perform a channel access procedure and / or a CW adjustment procedure for each HPID.

When the base station apparatus 3 transmits the PDCCH and the PDSCH scheduled by the PDCCH, the HARQ-ACK corresponding to the PDSCH (that is, the PDSCH) within a predetermined period (for example, until a predetermined timer expires) If the PUCCH or PUSCH containing HARQ-ACK) for the corresponding HPID cannot be successfully received, the base station apparatus 3 may update the PDCCH and the CW value for the PDSCH. If the base station apparatus 3 successfully receives the PUSCH containing HARQ-ACK for the HPID corresponding to the PDSCH instead of the PUCCH, the base station apparatus 3 does not have to update the values of the PDCCH and the CW for the PDSCH. ..

If the base station apparatus 3 and / or the terminal apparatus 1 considers that the HARQ operation of the HARQ process of a certain HPID is successful, the value of CW updated in connection with the operation may be set to _{CW min.} ..

If the terminal device 1 receives the HARQ-ACK for the received PDSCH via the PUCCH or the PUSCH and then receives the PDSCH having the same HPID and indicating retransmission, or the HARQ for the PDSCH. if the request for retransmission of -ACK, if performing type 1 channel access procedure before the transmission of the PUCCH including the HARQ-ACK for the _PDSCH, also update the value of CW used in the _{N init} Good. That is, if retransmission is indicated for a PDSCH with the same HPID, the terminal device 1 performs a type 1 channel access procedure prior to transmission of the PUCCH containing HARQ-ACK to the PDSCH, if any, the corresponding N _init. The value of CW used for may be updated.

SSB and / or CSI-RS in the NR-U cell may be collectively referred to as NR-U DRS (Discovery Reference Signal). The NR-U DRS may be detected so that the terminal device 1 can confirm whether the NR-U cell is activated or deactivated.

FIG. 15 is a diagram showing an example of frequency mapping (resource allocation, mapping to physical resources, frequency resource allocation type) according to the present embodiment. FIG. 15A is an example (contiguous mapping, localized mapping) in which a plurality of PRBs are continuously arranged with respect to one terminal device 1 and / or a base station device 3. The frequency mapping (frequency resource allocation type) of FIG. 15A may be used to realize low PAPR (Peak to Average Power Ratio) characteristics due to a single carrier such as a DFT-s-OFDM signal. FIG. 15B is an example (interlaced mapping, distributed mapping) in which a plurality of PRBs are arranged at equal intervals or non-equal intervals with respect to one terminal device 1 and / or base station device 3. The frequency mapping (frequency resource allocation type) in FIG. 15B shows that 80% or more of the transmission bandwidth (maximum transmission bandwidth, channel bandwidth, carrier bandwidth, BWP bandwidth) is used in the frequency domain with a small number of PRBs. It may be used to achieve this. That is, the frequency mapping of FIG. 15B may be performed in order to satisfy the OCB (Occupied Channel Bandwidth) requirement. Also, the number of interlaces may be determined according to the SCS. For example, if the SCS is 15 kHz, the number of interlaces may be 10 or 11. Further, when the SCS is 30 kHz, the number of interlaces may be 5 or 6. The number of interlaces may be the maximum number of multiplex terminals 1 in the frequency domain. The number of interlaces may be the same regardless of the magnitude of the frequency bandwidth. For example, if the frequency bandwidth is 20 MHz or 40 MHz and the SCS is 15 kHz, the number of interlaces may be 10 or 11. The base station device 3 and / or the terminal device 1 can transmit a physical channel and / or a physical signal using one or a plurality of interlaces.

FIG. 16 shows fields (PUCCH starting position field, PSP field) indicating PUCCH transmission start positions (start position in the time domain, start position in the slot) in the time domain according to the present embodiment, and PUCCH corresponding to each SCS. It is a figure which shows an example of a start position. 16 (a) and 16 (b) show an example of a field (2-bit field, 1-bit field) indicating a transmission start position of PUCCH. The field is a field used to provide a gap (period) for the terminal device 1 to perform LBT by adjusting the transmission timing in the time symbol area. For example, when the value "00" or "0" is set in the field, it indicates that the physical channel / physical signal can be transmitted from the start of the head time symbol area. When the value "01", "10", or "1" is set in the field, it indicates that the physical channel / physical signal can be transmitted from the middle of the head time symbol area. When the value "01" or "1" is set in the field, it indicates that transmission is possible from 25 μsec (us) in the time symbol region at the beginning of PUCCH. For example, in this 25 μs, the terminal device 1 can perform the LBT for 25 μs only once and then perform the transmission. When the value "10" is set in the field, it indicates that transmission is possible from (25 + TA (Timing Advance)) μs (us) in the time symbol area at the beginning of PUCCH. When the value "11" is set in the field, it indicates that the physical channel / physical signal can be transmitted from the next time symbol area. Further, depending on the value of SCS, the length of one time symbol region corresponding to SCS may be shorter than 25 μsec and / or (25 + TA) μsec. In such a case, if the value "11" is set in the field, the first time symbol region after 25 μsec or (25 + TA) μ sec from the first time symbol region may be indicated. FIG. 16C shows an example of the PUCCH start position of each value when the SCS is 15 kHz. FIG. 16D shows an example of the PUCCH start position of each value when the SCS is 30 kHz.

Next, the SIB1 (System Information Block Type 1) reception procedure according to this embodiment will be described.

Upon receiving the SIB1, the terminal device 1 holds the captured SIB1 and if the cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN (Public Land Mobile Network), later in this procedure, Received during RRC_CONNECTED, if timer T311 is not running, using plmn-IdentityList, trackingAreaCode, cellIdentity for cells received in the corresponding PLMN-IdentityInfo, including the selected PLMN. You may ignore the frequencyBandList, transfer the cellIdentity to one or more upper layers, transfer the trackingAreaCode to one or more upper layers, and apply the settings contained in the servingCellConfigCommon.

Instead, the terminal device 1 supports one or more frequency bands indicated by frequencyBandList, and the supported frequency band is a frequency band corresponding to NR-U (for example, an operating band), and , The terminal device 1 supports at least one additional Spectrum Emission in the NR-NS-PmaxList for the downlink supported band and the uplink supported band for the NR-U, and the terminal device 1 supports the NR-U. If the terminal device 1 supports the bandwidth of the initial uplink BWP and / or the initial downlink BWP indicated in the locationAndBandwidth field in each of the uplinkConfigCommon and / or downlinkConfigCommon of the terminal device 1, the terminal device 1 is of the initial BWP for the uplink. Even if the supported NR-U uplink channel bandwidth is applied, with the maximum transmit bandwidth that is equal to or greater than the bandwidth and is included in the carrierBandwidth indicated by uplinkConfigCommon for the SCS of the initial uplink BWP. Alternatively, the supported NR-U downlink channel bandwidth is equal to or wider than the initial BWP bandwidth for the downlink, with the maximum transmit bandwidth included in the carrierBandwidth indicated by downlinkConfigCommon for the SCS of the initial downlink BWP. A width may be applied, and if any, of a frequencyBandList that supports at least one of one or more additionalSpectrumEmission values in the nr-NS-PmaxList (and / or NR-NS-PmaxList). The first frequency band may be selected, or the cell Identity for the NR-U serving cell may be transferred to one or more upper layers.

Alternatively, the terminal device 1 supports one or more frequency bands indicated by frequencyBandList, and the supported frequency band is a frequency band corresponding to NR-U (for example, an operating band). If so, the terminal device 1 is supported with the maximum transmission bandwidth included in the carrierBandwidth indicated by uplinkConfigCommon for the SCS of the initial uplink BWP, which is equal to or wider than the bandwidth of the initial BWP for the uplink. The NR-U uplink channel bandwidth given may be applied, or the maximum transmission bandwidth included in the carrierBandwidth indicated by downlinkConfigCommon for the SCS of the initial downlink BWP, which is the same as or wider than the bandwidth of the initial BWP for the downlink. Supported NR-U downlink channel bandwidths may be applied with width, and one or more in the nr-NS-PmaxList (and / or NR-NS-PmaxList), if any. The first frequency band of the frequencyBandList that supports at least one of the additionalSpectrumEmission values may be selected, or the cellIdentity for the NR-U serving cell may be transferred to one or more upper layers.

Here, the values of the uplink channel bandwidth and the downlink channel bandwidth (that is, the channel bandwidth) with respect to the NR-U may be values of a predetermined bandwidth (for example, 20 MHz), or the measurement of the LBT. It may be the value of the bandwidth used for, the value determined based on the setting of NR-U, or the mapping of the physical channel of NR-U and / or the physical resource of the physical signal. It may correspond to the value of the frequency domain used, or it may be a channel bandwidth including the range of PRB (valid frequency domain, transmission bandwidth, measurement bandwidth) given by availableRB-RangesPerCell.

Alternatively, the terminal device 1 has one or more frequency bands indicated by the frequencyBandList for the downlink and / or one or more frequency bands indicated by the frequencyBandList for the uplink for the FDD (ie, they). Supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for supported bands on the downlink and supported bands on the uplink for FDD), uplinkConfigCommon, And supports the bandwidth of the initial uplink BWP and initial downlink BWP indicated in the locationAndBandwidth field in each of the downlinkConfigCommon, equal to or wider than the bandwidth of the initial uplink BWP, and equal to or greater than the carrierBandwidth. Supports uplink channel bandwidth with narrow maximum transmit bandwidth setting, downlink with maximum transmit bandwidth setting equal to or wider than the initial downlink BWP bandwidth, and equal to or narrower than carrierBandwidth. If the link channel bandwidth is supported, the terminal device 1 is equal to or wider than the bandwidth of the initial BWP for the uplink and is included in the carrierBandwidth indicated by uplinkConfigCommon for the SCS of the initial uplink BWP. A supported uplink channel bandwidth may be applied with the maximum transmit bandwidth, or the carrierBandwidth indicated by downlinkConfigCommon for the SCS of the initial downlink BWP that is equal to or wider than the bandwidth of the initial BWP for the downlink. A supported downlink channel bandwidth with the maximum transmit bandwidth contained in may be applied, and if any, one or more in the nr-NS-PmaxList (and / or NR-NS-PmaxList). The first frequency band of the frequencyBandList that supports at least one of the additionalSpectrumEmission values of may be selected.

The terminal device 1 may transfer the cellIdentity to one or a plurality of upper layers.

If the trackingAreaCode is not provided not only to the selected PLMN but also to the registered PLMN and the PLMN of the same PLMN list, the terminal device 1 may consider the cell as a barred. Further, if intraFreqReselection is set to notAllowed, the terminal device 1 may consider cell reselection to another cell at the same frequency as the barred cell as notAllowed. If this is not the case, the terminal device 1 may consider cell reselection to another cell at the same frequency as the barred cell as Allowed.

If not, the terminal device 1 may transfer the trackingAreaCode to one or more upper layers.

The terminal device 1 may transfer PLMN Identity to one or a plurality of upper layers.

In RRC_INACTIVE, if the transferred information does not trigger message transmission by one or more upper layers, and if the serving cell does not belong to the set ran-NotificationAreaInfo, then RNA (RAN-based Notification Area) You may start the update.

If there is, ims-Emergency Support may be transferred to one or more upper layers.

If there is, uac-AccessCategory1-SelectionAssistanceInfo may be transferred to one or more upper layers.

The terminal device 1 may apply the settings included in the servingCellCommon.

The terminal device 1 may apply the specified PCCH setting.

If the terminal device 1 has a valid version in which the SIB required for cell operation is stored, the required version of the SIB may be used.

If the terminal device 1 does not store a valid version of one SIB out of one or more required SIBs, then the SI message and si containing at least one required SIB, depending on the si-SchedulingInfo. -You may capture SI messages with BroadcastStatus set to broadcasting, or SI messages with at least one required SIB and SI messages with si-BroadcastStatus set to notbroadcasting. You may trigger a request to capture.

The terminal device 1 may apply the first listed additionalSpectrumEmission that supports a plurality of values included in the NR-NS-PmaxList in the frequencyBandList of uplinkConfigCommon.

If the additionalPmax exists in the same entry of the selected additionalSpectrumEmission in the NR-NS-PmaxList, the terminal device 1 may apply the additionalPmax of uplinkConfigCommon to UL. If not, the terminal device 1 may apply p-Max of uplinkConfigCommon to UL.

NR-NS- for a supplementary uplink band where supplementaryUplink exists in servingCellConfigCommon, terminal device 1 supports one or more frequency bands in the frequencyBandList of supplementary uplink (SUL), and terminal device 1 supports. Supports at least one additionalSpectrumEmission in the PmaxList, terminal device 1 supports the bandwidth of the initial uplink BWP indicated in the locationAndBandwidth field of the supplementary uplink, and terminal device 1 is equal to or greater than carrierBandwidth. Also narrow, and if it supports uplink channel bandwidth with a maximum transmit bandwidth setting that is equal to or greater than the bandwidth of SUL's initial uplink BWP, then the terminal device is supplementary as configured in the serving cell. The uplink may be considered, applying the uplink channel bandwidth included in the carrierBandwidth and supported with a maximum transmit bandwidth equal to or greater than the bandwidth of the SUL's initial uplink BWP. Alternatively, a first listed additionalSpectrum Emission that supports one or more values contained in the NR-NS-PmaxList in the frequencyBandList for the supplementaryUplink may be applied.

Here, the supplementaryUplink may include at least one parameter related to the supplementary uplink. That is, the supplementaryUplink may include the settings necessary for performing the supplementary uplink.

If the additional Pmax is in the same entry of the selected additionalSpectrumEmission in the NR-NS-PmaxList for the supplementaryUplink, then terminal 1 may or may not apply the additionalPmax of the supplementaryUplink to the SUL. , P-Max of supplementary Uplink may be applied to SUL.

NR-unlicensed where nr-Unlicensed exists in servingCellConfigCommon, terminal device 1 supports one or more frequency bands in the frequencyBandList of NR-unlincesed (NR-U), and terminal device 1 is supported. Supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for band, terminal device 1 supports the bandwidth of the initial BWP indicated in the locationAndBandwidth field of NR-unlicensed, and terminal device 1 supports carrierBandwidth. If the terminal device supports a channel bandwidth with a maximum transmit bandwidth setting equal to or narrower than the initial BWP bandwidth of the NR-U and greater than or equal to, the terminal device is configured in the serving cell. As NR-unlicensed, the channel bandwidth included in the carrierBandwidth and supported with a maximum transmit bandwidth equal to or greater than the initial BWP bandwidth of the NR-U is applied. Alternatively, a first listed additionalSpectrum Emission that supports one or more values contained in the NR-NS-PmaxList in the frequencyBandList for nr-Unlicensed may be applied. Here, the initial BWP of NR-U may include at least one of the initial uplink BWP and / or the initial downlink BWP.

If terminal device 1 is equal to or narrower than carrierBandwidth and does not support channel bandwidth with maximum transmit bandwidth setting equal to or greater than the initial BWP bandwidth of NR-U, terminal device 1 1 may apply a channel bandwidth with the same maximum transmit bandwidth as the initial BWP bandwidth of the NR-U, or one or more included in the NR-NS-PmaxList in the frequencyBandList for nr-Unlicensed. A first listed additional Spectrum Emission that supports the value of may be applied.

Here, nr-Unlicensed may contain at least one parameter related to NR-U. That is, nr-Unlicensed may include the settings required to perform NR-U.

If the additional Pmax is in the same entry of the selected additional Spectrum Emission in the NR-NS-PmaxList for nr-Unlicensed, terminal 1 may apply the nr-Unlicensed additional Pmax to NR-U. If not, nr-Unlicensed p-Max may be applied to NR-U.

If this is not the case, the terminal device 1 may consider the cell as barred, or may perform barring if intraFreqReselection is set to notAllowed.

Note that the trackingAreaCode may indicate the tracking area code to which the cell indicated by cellIdentity belongs. The presence of that field may indicate that the cell supports at least stand-alone operation (per PLMN). The absence of that field may indicate that the cell supports only EN-DC functionality (per PLMN).

ServingCellConfigCommon is an IE (Information Element) used to set one or more cell-specific parameters of the serving cell of the terminal device 1. This IE includes one or more parameters for the terminal device 1 to normally capture the SSB. With this IE, the network (base station device 3) provides this information in dedicated signaling when configuring terminal device 1 with one or more secondary cells or additional cell groups (ie, SCG). can do. This IE may be provided to SpCells (MCG and SCG) based on the (with sync) reconfiguration when in sync.

DownlinkConfigCommon and / or DownlinkConfigCommon may be used to provide one or more common downlink parameters for a cell. downlinkConfigCommon and / or DownlinkConfigCommon may include frequencyInfoDL and / or initialDownlinkBWP.

FrequencyInfoDL may be used to set one or more basic parameters for downlink carriers and transmissions.

The initialDownlinkBWP may be used to indicate the initial downlink BWP settings for SpCell and SCell. The network may set a locationAndBandwidth for the initial downlink BWP to include the entire CORESET # 0 of the serving cell in the frequency domain.

UplinkConfigCommon and / or UplinkConfigCommon may be used to provide one or more common uplink parameters for a cell.

FrequencyInfoUL may be used to indicate the absolute uplink frequency setting and subcarrier-specific virtual carriers.

The initialUplinkBWP may be used to indicate the initial uplink BWP settings for SpCell and SCell.

The frequencyBandList may indicate a list of one or more frequency bands to which the NR cell reselection parameter applies.

The nr-NS-PmaxList and / or NR-NS-PmaxList may be used to provide a list of additionalPmax and additionalSpectrum Emissions. Also, if the field does not exist (or the value is not set), the terminal device may set the value to 0 for the additionalSpectrum Emission.

LocationAndBandwidth indicates the arrangement and bandwidth of the BWP frequency domain. The value of the field may be interpreted as RIV (Resource Indicator Value). The first PRB (PRB at the beginning of this BWP) may be the PRB determined by the subcarrier Spacing of this BWP and the offsetToCarrier corresponding to this subcarrier interval.

Hereinafter, aspects of various devices according to one aspect of the present embodiment will be described.

(1) In order to achieve the above object, the aspect of the present invention has taken the following measures. That is, the first aspect of the present invention is a terminal device, which includes a receiving unit that receives SIB1 and an upper layer processing unit that applies channel bandwidth based on receiving the SIB1. If nr-Unlicensed exists in the servingCellConfigCommon, the upper layer processing unit considers that NR-U is set in the serving cell, and is equal to or wider than the initial BWP bandwidth of the NR-U, and is the same as the carrierBandwidth. If it supports a channel bandwidth with a maximum transmit bandwidth setting that is narrower than or equal to that, the maximum transmit bandwidth contained within the carrierBandwidth that is equal to or greater than the bandwidth of the initial BWP of the NR-U. Apply the supported NR-U channel bandwidth with width.

(2) Further, a second aspect of the present invention is a method used for a terminal device, which includes a step of receiving SIB1 and a step of applying a channel bandwidth based on receiving the SIB1. If nr-Unlicensed exists in servingCellConfigCommon, the step that considers the serving cell to have NR-U and the bandwidth equal to or wider than the initial BWP bandwidth of the NR-U and the same or narrower than the carrierBandwidth. Given that it supports channel bandwidth with a maximum transmit bandwidth setting, it is equal to or wider than the initial BWP bandwidth of the NR-U, with the maximum transmit bandwidth contained within the carrierBandwidth. Includes a step of applying the supported NR-U channel bandwidth.

The program operating on the base station device 3 and the terminal device 1 according to one aspect of the present invention controls a CPU (Central Processing Unit) and the like so as to realize the functions of the above embodiment related to one aspect of the present invention. It may be a program (a program that makes a computer function). Then, the information handled by these devices is temporarily stored in RAM (Random Access Memory) at the time of processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) and HDD (Hard Disk Drive). The CPU reads, corrects, and writes as necessary.

Note that the terminal device 1 and a part of the base station device 3 in the above-described embodiment may be realized by a computer. In that case, the program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed.

The "computer system" referred to here is a computer system built in the terminal device 1 or the base station device 3, and includes hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built in a computer system.

Furthermore, a "computer-readable recording medium" is a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In that case, a program may be held for a certain period of time, such as a volatile memory inside a computer system serving as a server or a client. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, and may be one for realizing the above-mentioned functions in combination with a program already recorded in the computer system.

Further, the base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) composed of a plurality of devices. Each of the devices constituting the device group may include a part or all of each function or each function block of the base station device 3 according to the above-described embodiment. As the device group, it suffices to have each function or each function block of the base station device 3. Further, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as an aggregate.

Further, the base station device 3 in the above-described embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGen RAN, NR RAN). Further, the base station apparatus 3 in the above-described embodiment may have a part or all of the functions of the upper node with respect to the eNodeB and / or the gNB.

Further, a part or all of the terminal device 1 and the base station device 3 in the above-described embodiment may be realized as an LSI which is typically an integrated circuit, or may be realized as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chipped, or a part or all of them may be integrated into a chip. Further, the method of making an integrated circuit is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, when an integrated circuit technology that replaces an LSI appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.

Further, in the above-described embodiment, the terminal device is described as an example of the communication device, but the present invention is not limited to this, and the present invention is not limited to this, and is a stationary or non-movable electronic device installed indoors or outdoors. For example, it can be applied to terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. In addition, one aspect of the present invention can be variously modified within the scope of the claims, and the technical aspects of the present invention are also obtained by appropriately combining the technical means disclosed in the different embodiments. Included in the range. In addition, the elements described in each of the above embodiments include a configuration in which elements having the same effect are replaced with each other.

One aspect of the present invention is used, for example, in a communication system, a communication device (for example, a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (for example, a communication chip), a program, or the like. be able to.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Wireless transmission / reception section 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper layer Processing section 15, 35 Medium access control layer Processing unit 16, 36 Radio resource control layer processing unit

Claims (2)

1. A receiver that receives SIB1 and
   A higher layer processing unit that applies channel bandwidth based on receiving the SIB1 is provided.
   The upper layer processing unit
   If nr-Unlicensed exists in servingCellConfigCommon, it is considered that NR-U is set in the serving cell.
   Given that it supports channel bandwidth with a maximum transmit bandwidth setting that is equal to or greater than the initial BWP bandwidth of the NR-U and equal to or smaller than the carrierBandwidth.
   A terminal device that applies a supported NR-U channel bandwidth with a maximum transmit bandwidth that is equal to or greater than the initial BWP bandwidth of the NR-U and is contained within the carrierBandwidth.
2. The step of receiving SIB1 and
   A step of applying channel bandwidth based on receiving the SIB1 and
   If nr-Unlicensed exists in servingCellConfigCommon, the step that considers that NR-U is set in the serving cell, and
   If a channel bandwidth with a maximum transmit bandwidth setting equal to or wider than the initial BWP bandwidth of the NR-U and equal to or narrower than the carrierBandwidth is supported, then the NR-U A method comprising applying a supported NR-U channel bandwidth with a maximum transmit bandwidth that is equal to or greater than the initial BWP bandwidth and is contained within the carrierBandwidth.

Images