JP7644016B2 - Terminal device and method - Google Patents

Description

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

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

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

Furthermore, studies are being conducted on NR-U (NR-Unlicensed), a wireless communication method and/or system that applies NR Radio Access Technology (NR-RAT) to unlicensed frequency bands (unlicensed bands, unlicensed spectrum) (Non-Patent Document 2).

"New SID proposal: Study on New Radio Access Technology", RP-160671, NTT DOCOMO, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. "TR38.889 v0.0.2 Study on NR-based Access to Unlicensed Spectrum", R1-1807617, Qualcomm Incorporated, 3GPP TSG RAN WG1 Meeting #93, Busan,Korea, 21st - 25th May, 2018.

One aspect of the present invention provides a terminal device for efficient communication and a method for use with the terminal device.

(1) A first aspect of the present invention is a terminal device comprising a receiving unit that receives SIB1 and an upper layer processing unit that applies a channel bandwidth based on receiving the SIB1, wherein if nr-Unlicensed is present in servingCellConfigCommon, the upper layer processing unit assumes that an NR-U is configured in the serving cell, and if the upper layer processing unit supports a channel bandwidth with a maximum transmission bandwidth setting that is the same as or wider than the bandwidth of the initial BWP of the NR-U and the same as or narrower than carrierBandwidth, applies the channel bandwidth of the supported NR-U with a maximum transmission bandwidth that is the same as or wider than the bandwidth of the initial BWP of the NR-U and included in carrierBandwidth.

(2) A second aspect of the present invention is a method for use in a terminal device, comprising the steps of receiving SIB1, applying a channel bandwidth based on receiving the SIB1, assuming that an NR-U is configured in the serving cell if nr-Unlicensed is present in servingCellConfigCommon, and, if the terminal device supports a channel bandwidth with a maximum transmission bandwidth setting that is the same or wider than the bandwidth of the initial BWP of the NR-U and equal to or narrower than carrierBandwidth, applying the channel bandwidth of the supported NR-U with a maximum transmission bandwidth that is the same or wider than the bandwidth of the initial BWP of the NR-U and included within carrierBandwidth.

According to one aspect of the present invention, a terminal device can communicate efficiently. Also, a base station device can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. 1 is an example illustrating a relationship between N ^slot _symb , an SCS setting μ, and a CP setting according to an aspect of the present embodiment. FIG. 2 is a schematic diagram illustrating an example of a resource grid in a subframe according to an aspect of the present embodiment. FIG. 11 is a diagram illustrating an example of a relationship between a PUCCH format and a length N ^PUCCH _symb of the PUCCH format according to one aspect of the present embodiment. A figure showing an example of parameters included in PUCCH-Config and PUCCH-FormatConfig according to one embodiment of the present invention. A figure showing an example of parameters included in a PUCCH-ResourceSet and a PUCCH-Resource according to one embodiment of this invention. FIG. 11 is a diagram illustrating an example of parameters that can be set specifically for a PUCCH format according to one aspect of the present embodiment. FIG. 11 is a diagram illustrating an example of parameters included in a PUCCH resource set and a PUCCH resource according to an aspect of the present embodiment. FIG. 11 is a diagram illustrating another example of parameters included in a PUCCH resource set and a PUCCH resource according to an aspect of the present embodiment. A figure showing an example of DCI format 1_0 relating to one aspect of this embodiment. 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an aspect of the present embodiment. 1 is a schematic block diagram showing a configuration of a base station device 3 according to one aspect of the present embodiment. A diagram showing an example of a channel access procedure (CAP) according to one aspect of this embodiment. A diagram showing an example of a channel access priority class (CAPC) and a CW adjustment procedure (CWAP) according to one aspect of the present embodiment. FIG. 11 is a diagram showing an example of frequency mapping (resource allocation, mapping to physical resources, and frequency resource allocation type) according to the present embodiment. FIG. 13 is a diagram showing an example of a field (PUCCH starting position field, PSP field) indicating the transmission start position of the PUCCH in the time domain (start position of the time domain, start position within a slot) in this embodiment, and the start position of the PUCCH corresponding to each SCS.

The following describes an embodiment of the present invention.

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 terminal devices 1. The base station device 3 may include some or all of a communication device, a node, an NB (NodeB), an eNB, a gNB, a network device (core network, gateway), and an access point. The terminal device 1 may also 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 an eNB that is connected to a fifth generation core network (5GC) via an NG (Next Generation) interface is referred to as an ng-eNB. 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 the 5GC via an NG interface.

The base station device 3 may configure one or both of an MCG (Master Cell Group) and an SCG (Secondary Cell Group). The MCG is a group of serving cells including at least a PCell (Primary Cell). The SCG is a group of serving cells including at least a PSCell (Primary Secondary Cell). The PCell may be a serving cell provided based on an 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. The PCell and the PSCell may be referred to as SpCells (Special Cells). Configuring one CG using one SpCell and one or more SCells and performing communication may be referred to as carrier aggregation.

The MCG may be configured with one or more serving cells on the EUTRA. The SCG may be configured with one or more serving cells on the NR. The MCG may be configured with one or more serving cells on the NR. The SCG may be configured with one or more serving cells on the EUTRA. The MCG and the SCG may be configured with one or more serving cells of either the EUTRA or the NR. Here, "on the EUTRA" may include the meaning that the EUTRA RAT (Radio Access Technology) is applied. "on the NR" may include the meaning that the NR RAT is applied.

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

The operating bands (carrier frequencies and frequency bandwidths) applicable to each of EUTRA, NR, and NR-U may be defined (specified) separately.

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

The frame structure is explained below.

In a wireless communication system according to one aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of OFDM in the time domain. An OFDM symbol includes at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal in baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is 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 obtained by applying transform precoding to CP-OFDM.

The subcarrier spacing (SCS) may be given by the subcarrier spacing Δf=2 ^μ ·15 kHz. 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 a higher layer parameter. That is, regardless of the downlink and/or uplink, the value of μ may be set for each BWP (each downlink BWP, each uplink BWP).

In the wireless communication system according to an aspect of the present embodiment, a time unit _Tc is used to express the length of the time domain. The time unit _Tc may be given by _Tc = 1/(Δf _max · N _f ). Δf _max may be the maximum value of the SCS supported in the wireless communication system according to an 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,ref} may be 2048.

The constant κ may be a value indicating the relationship between the reference SCS and _Tc . The constant κ may be used for the length of the subframe. The number of slots included in the subframe may be given based at least on the constant κ. Δf _ref is the reference SCS, and N _f,ref is a value corresponding to the reference SCS.

The transmission of signals in the downlink and/or the transmission of signals in 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 length of the frame may be given regardless of SCSΔf. That is, the setting of the frame may be given regardless of the value of μ. The length of the subframe may be given regardless of SCSΔf. That is, the setting of the subframe may be given regardless of μ.

For a certain SCS setting μ, the number of slots included in one subframe and indexes may be given. For example, the slot number n ^μ _s may be given in the subframe in ascending order from 0 to N ^subframe,μ _slot −1. For the SCS setting μ, the number of slots included in one frame and indexes may be given. Also, the slot number n ^μ _s,f may be given in the frame in ascending order from 0 to N ^frame,μ _slot −1. Consecutive N ^slot _symb OFDM symbols may be included in one slot. ^{N slot} _symb may be given at least based on and/or a part or all of a cyclic prefix (CP) setting. The CP setting may be given at least based on a parameter of a higher layer. The CP setting 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 N ^slot _symb , SCS setting μ, and 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, and N ^{subframe, μ} _slot = 4. Also, 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, and N ^{subframe, μ} _slot = 4.

Below, we will explain the physical resources related to this embodiment.

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

For a set of SCS configurations μ and carriers, a resource grid is given, defined by N ^size,μ _grid,x N ^RB _sc subcarriers and N ^subframe,μ _symb OFDM symbols. ^{N size,μ grid} _,x may indicate the number of resource blocks given for SCS configuration μ for carrier x. N size,μ _grid,x may indicate the carrier bandwidth. ^{N size,μ} _grid,x may correspond to the value of the higher layer parameter CarrierBandwidth. Carrier x may indicate either a downlink carrier or an uplink carrier. That is, x may be either "DL" or "UL". N ^RB _sc may indicate the number of subcarriers contained in one resource block. ^{N RB} _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 setting of a transmission direction. The transmission direction includes at least a downlink (DL) and an uplink (UL). Hereinafter, a set of parameters including at least the antenna port p, the SCS setting μ, and a part or all of the setting of the transmission direction may be referred to as a first radio parameter set. That is, one resource grid may be provided for each first radio parameter set. Note that the radio parameter set may be one or more sets including one or more radio parameters (physical layer parameters or higher layer parameters).

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

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

Each element in the resource grid provided for each first radio parameter set may be referred to as a resource element (RE). The resource element is identified by a frequency domain index k _sc and a time domain index l _sym . For a certain first radio parameter set, the resource element is identified by a frequency domain index k _sc and a time domain index l _sym . The resource element identified 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 provided for the SCS configuration μ. N ^μ _RB may be N ^{size, μ} _{grid, x} . ^{N RB} _sc is the number of subcarriers included in a resource block, and N ^RB _sc =12. The frequency domain index k _sc may correspond to a subcarrier index k _sc . The time domain index l _sym may correspond to an OFDM symbol index l _sym . One or more resource elements may correspond to a physical resource and a complex value (complex-valued modulation symbol). One or more information bits (information bits for control information, transport blocks, and higher layer parameters) may be mapped to each of the one or more resource elements corresponding to the physical resource and/or complex value.

FIG. 3 is a schematic diagram showing an example of a resource grid in a subframe according to an aspect of the present embodiment. In the resource grid of FIG. 3, the horizontal axis is a time domain index l _sym and the vertical axis is a frequency domain index k _sc . In one subframe, the frequency domain of the resource grid includes N ^μ _RB N ^RB _sc subcarriers. In one subframe, the time domain of the resource grid may include 14·2 ^μ OFDM symbols. One resource block includes N ^RB _sc subcarriers. The time domain of the resource block may correspond to one 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 transmit and receive using only a subset of the resource grid. The subset of the resource grid may also be referred to as a BWP, and the BWP may be given based on at least a part or all of the higher layer parameters and/or the DCI. The BWP may also be referred to as a CBP (Carrier Bandwidth Part). The terminal device 1 may not be instructed to transmit and receive using all the sets of the resource grid. The terminal device 1 may be instructed to transmit and receive using some of the frequency resources in the resource grid. One BWP may be composed of multiple resource blocks in the frequency domain. One BWP may be composed of multiple consecutive 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 configured for each serving cell. One or more uplink BWPs may be configured for each serving cell.

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

In an active downlink BWP, DL-SCH may be received. In an active downlink BWP, PDCCH may be monitored. In an active downlink BWP, PDSCH may be received.

In an inactive downlink BWP, DL-SCH may not be received. In an inactive downlink BWP, PDCCH may not be monitored. CSI for an inactive downlink BWP may not be reported.

Of one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs.

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

In an active uplink BWP, a UL-SCH may be transmitted. In an active uplink BWP, a PUCCH may be transmitted. In an active uplink BWP, a PRACH may be transmitted. In an active uplink BWP, an SRS may be transmitted.

In an inactive uplink BWP, UL-SCH may not be transmitted. In an inactive uplink BWP, PUCCH may not be transmitted. In an inactive uplink BWP, PRACH may not be transmitted. In an inactive uplink BWP, SRS may not be transmitted.

Of one or more uplink BWPs configured for one serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. In other words, there may be at least one active uplink BWP for the serving cell that includes the uplink BWP.

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

The higher layer signaling may be common RRC signaling. The common RRC signaling may have at least some or all of the following features C1 to C3:
C1) Mapped to the BCCH logical channel or the CCCH logical channel C2) Includes at least the ReconfigurationWithSync information element C3) Mapped to the PBCH

The ReconfigurationWithSync information element may include information indicating a configuration commonly used in the serving cell. The configuration commonly used in the serving cell may include at least a PRACH configuration. The PRACH configuration may at least indicate one or more random access preamble indices. The PRACH configuration may at least indicate a time/frequency resource of the PRACH.

The common RRC signaling may include at least common RRC parameters. The common RRC parameters may be parameters that are commonly used in the serving cell (cell-specific).

The higher layer signaling may be dedicated RRC signaling. The dedicated RRC signaling may comprise at least some or all of the following features D1 to D2:
D1) Mapped to DCCH logical channel D2) Does not include ReconfigurationWithSync information element

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

In addition, the upper layer parameters including one or more upper layer parameters may be referred to as information elements (IEs). In addition, the upper layer parameters including one or more upper layer parameters and/or one or more IEs and/or IEs may be referred to as messages (upper layer messages, RRC messages), information blocks (IBs), or system information.

The SIB may at least indicate a time index of the SSB. The SIB may at least include information related to PRACH resources. The SIB may at least include information related to setting up an initial connection.

The ReconfigurationWithSync information element may include at least information related to PRACH resources. The ReconfigurationWithSync information element may include at least information related to setting up an initial connection.

The dedicated RRC signaling may include at least dedicated RRC parameters. The dedicated RRC parameters may be parameters that are used exclusively for the terminal device 1 (UE-specific). The dedicated RRC signaling may include at least common RRC parameters.

Common RRC parameters and dedicated RRC parameters may also be referred to as higher layer parameters.

The following describes physical channels and physical signals relating to various aspects of this embodiment.

An uplink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. An uplink physical channel is a physical channel used in an uplink carrier. In a 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)

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

One or more types of uplink control information may be multiplexed onto the PUCCH. The multiplexed PUCCH may be transmitted. That is, the PUCCH may be multiplexed with multiple HARQ-ACKs, multiple CSIs, multiple SRs, HARQ-ACKs and CSIs, HARQ-ACKs and SRs, or other types of UCI.

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

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

The SR may be used at least to request PUSCH resources for the initial transmission. The SR may also be used to request UL-SCH resources for a new transmission. The SR bit may be used to indicate either a positive SR or a negative SR. The SR bit indicating a positive SR may also be referred to as "a positive SR is transmitted". A positive SR may indicate that a PUSCH resource for the initial transmission is requested by the terminal device 1. A positive SR may indicate that an SR is triggered by a higher layer. A positive SR may be transmitted when an SR is instructed to be transmitted by a higher layer. The SR bit indicating a negative SR may also be referred to as "a negative SR is transmitted". A negative SR may indicate that a PUSCH resource for the initial transmission is not requested by the terminal device 1. A negative SR may indicate that an SR is not triggered by a higher layer. A negative SR may be transmitted if no SR is indicated to be transmitted by higher layers.

The SR bit may be used to indicate either a positive SR or a negative SR for one or more SR configurations. Each of the one or more SR configurations may correspond to one or more logical channels. A positive SR for an SR configuration may be a positive SR for any or all of the one or more logical channels corresponding to the SR configuration. A negative SR may not correspond to a specific SR configuration. An indication of a negative SR may be an indication of a negative SR for all SR configurations.

The SR setting may be a Scheduling Request ID (SR-ID). The SR-ID may be provided by a higher layer parameter.

The CSI may include at least some or all of a channel quality index (CQI), a precoder matrix index (PMI), and a rank index (RI). The CQI is an index related to the quality of the channel (e.g., propagation strength), the PMI is an index indicating the precoder, and the RI is an index indicating the transmission rank (or the number of transmission layers).

The CSI may be provided based at least on receiving a physical signal (e.g., CSI-RS) used at least for channel measurement. The CSI may include a value selected by the terminal device 1. The CSI may be selected by the terminal device 1 based at least on receiving a physical signal used at least for channel measurement. The channel measurement may include interference measurement. Note that the CSI-RS may be set based on the CSI-RS configuration or may be set based on the SSB configuration.

The CSI report is a report of CSI. The CSI report may include CSI part 1 and/or CSI part 2. The CSI part 1 may be configured to include at least a wideband channel quality information (wideband CQI), a wideband precoder matrix index (wideband PMI), and a part or all of the RI. The number of bits of the CSI part 1 multiplexed onto the PUCCH may be a predetermined value regardless of the value of the RI of the CSI report. The number of bits of the CSI part 2 multiplexed onto the PUCCH may be given based on the value of the RI 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 a value indicated by the RI field included in the CSI report.

The set of RIs allowed in a CSI report may be some or all of 1 to 8. The set of RIs allowed in a CSI report may also be given based at least on a higher layer parameter RankRestriction. If the set of RIs allowed in a CSI report includes only one value, the RI of the CSI report may be that one value.

Priority may be set for the CSI report. The priority of the CSI report may be based on at least some or all of the following: a configuration for the time domain behavior (processing) of the CSI report, a type of content of the CSI report, an index of the CSI report, and/or an index of a serving cell for which the measurement of the CSI report is configured.

The settings regarding the time domain behavior (processing) of the CSI reporting may be settings indicating whether the CSI reporting is performed aperiodic, whether the CSI reporting is performed semi-persistent, or whether the CSI reporting is performed quasi-statically.

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

Layer 1 refers to the physical layer, and may be a layer that performs processing such as a physical layer processing unit, a radio transmitting unit, a transmitting unit, and/or a radio receiving unit, a receiving unit. Layers higher than Layer 1 include the MAC layer, the RRC layer, and a higher layer processing unit. For example, Layer 2 may be the MAC layer, the RLC layer, the PDCP layer, the MAC layer processing unit, the RLC layer processing unit, and the PDCP layer processing unit. Layer 3 may be the RRC layer and the RRC layer processing unit.

The index of the CSI report may be given by a higher layer parameter.

Next, we will explain the PUCCH of this embodiment.

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

If terminal device 1 transmits UCI (Uplink Control Information) without transmitting a PUSCH, terminal device 1 transmits UCI on a PUCCH using a PUCCH format that satisfies specified conditions.

PUCCH format 0 is used when transmission is 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 than 4 symbols and the number of HARQ-ACK/SR bits is 1 or 2 bits.

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

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

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

The frequency resource allocation for PUCCH formats 0, 1, and 4 may be 1 PRB regardless of the number of UCI information bits transmitted on the PUCCH. The frequency resource allocation for PUCCH formats 2 and 3 may be based on an upper layer parameter (nrofPRBs: number of Physical Resource Blocks) related to the maximum number of PRBs and an optimal number of PRBs depending on the number of UCI information bits transmitted on the PUCCH. Note that nrofPRBs may be set for each of PUCCH formats 2 and 3. For the PUCCH resources of PUCCH formats 2 and/or 3, the number of PRBs may be adjusted so as not to exceed the number of UCI information bits and nrofPRBs that the terminal device 1 wishes to transmit.

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^α ₂ *3^α ₃ *5^α ₅ , the number of PRBs may be increased until the number of PRBs required for PUCCH format 3 satisfies 2^α ₂ *3^α ₃ *5^α ₅ so as not to exceed nrofPRBs. Here, α ₂ , α ₃ , and α ₅ may each be 0 or an integer greater than 0.

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 1 or 2 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 1 is any of 4 to 14 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 2 is 1 or 2 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 3 is any of 4 to 14 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 4 is any of 4 to 14 OFDM symbols.

Figure 5 is a diagram showing an example of parameters included in PUCCH-Config and PUCCH-FormatConfig according to one aspect of the present embodiment. The time-frequency resource of the PUCCH may be determined and transmitted based on the PUCCH-Config. The parameters included in the PUCCH-Config and PUCCH-Config may be RRC information elements. The PUCCH-Config may be used to set one or more PUCCH parameters specific to the terminal device 1 for each BWP. resourceSetToAddModList and resourceSetToReleaseList are lists used to add and/or release a PUCCH resource set, and the size of the list may be based on the maximum number of PUCCH resource sets. resourceToAddModList and resourceToReleaseList are lists used to add and/or release one or more PUCCH resources applied to the uplink BWP and serving cell in which the PUCCH setting is defined, and the size of the list may be based on the maximum number of PUCCH resources. spatialRelationInfoToAddModList may be used to indicate the setting of a spatial relation between the reference RS and the PUCCH. The reference RS may be SSB/CSI-RS/SRS. If the list has more than one element, the MAC-CE selects one element. PUCCH-FormatConfig may be configured 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. dl-DataToUL-ACK may be used to indicate a list of PDSCH and the timing for HARQ-ACK corresponding to the PDSCH.

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

interslotFrequencyHopping is used to indicate that the terminal device 1 can perform interslot frequency hopping when PUCCH format 1, 3 or 4 is repeated across multiple slots. For long PUCCH (PUCCH formats 1, 3, 4), the terminal device 1 cannot simultaneously perform intraslot frequency hopping and interslot frequency hopping.

additionalDMRS may be used to indicate that for PUCCH format 3 or 4, two DMRS symbols per hop can be included, and four DMRS symbols can be included without frequency hopping. 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 format 2, 3 or 4. This field may not apply for 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 present in PUCCH-FormatConfig, the terminal device 1 may apply n1. This field may not be applied for PUCCH format 2.

pi2BPSK may indicate that the terminal device 1 can use pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. This field may not apply to PUCCH formats 1 and 2.

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

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

resourceList is a list of one or more PUCCH resources included in the PUCCH resource set. One or more PUCCH resources of PUCCH formats 0 and 1 may be permitted 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 of PUCCH formats 2, 3, and 4 may be permitted to be included only in PUCCH resource sets with pucch-ResourceSetId > 0. These PUCCH resource sets may include up to 8 PUCCH resources. Up to 4 PUCCH resource sets may be configured.

maxPayloadMinus1 may be used to indicate the maximum number of payload bits that the terminal device 1 can transmit using the PUCCH resource set minus 1. In other words, maxPayloadMinus1 may indicate the maximum number of UCI bits that can be transmitted using the PUCCH resource set (maximum value of the number of UCI bits). When a 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 may not be included in the PUCCH-ResourceSet. Also, in a PUCCH resource set other than the first PUCCH resource set, this field may not be included in the PUCCH-ResourceSet if it is the maximum payload size.

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

startingPRB indicates the PRB index of the PUCCH. The value of this field indicates the first PRB index if the PUCCH consists of multiple PRBs.

intraSlotFrequencyHopping may be used to indicate whether intra-slot frequency hopping is performed. Intra-slot frequency hopping may be applied to all types of PUCCH formats. Intra-slot frequency hopping and inter-slot frequency hopping are not performed simultaneously for long PUCCH (PUCCH formats 1, 3, 4) in multiple slots.

secondHopPRB may be used to indicate the index of the first PRB after frequency hopping. This value may apply for intra-slot frequency hopping.

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

Figure 7 is a diagram showing an example of parameters that can be set specific to a PUCCH format relating to one aspect of this embodiment.

The PUCCH resources for PUCCH format 0 may be configured based on PUCCH-Format0 including initialCyclicShift, nrofSymbols, and startingSymbolIndex.

PUCCH resources for PUCCH format 1 may be configured based on PUCCH-Format1 including initialCyclicShift, nrofSymbols, startingSymbolIndex, and timeDomainOCC.

PUCCH resources for PUCCH format 2 may be configured based on PUCCH-Format2 including nrofPRBs, nrofSymbols, and startingSymbolIndex.

PUCCH resources for PUCCH format 3 may be configured based on PUCCH-Format3 including nrofPRBs, nrofSymbols, and startingSymbolIndex.

PUCCH resources for PUCCH format 4 may be configured based on PUCCH-Format4 including nrofSymbols, occ-Length, occ-Index, and startingSymbolIndex.

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

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

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

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

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

Next, we will explain the PUCCH resources and PUCCH resource sets related to this embodiment.

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

If the PUCCH resource set includes more than a predetermined number of PUCCH resources, the terminal device 1 may determine which PUCCH resource in the PUCCH resource set to use 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. Also, if the PUCCH resource set includes more than a predetermined number of PUCCH resources, the size (number of bits, bit size) of the PRI field included in the DCI format may be extended. If the PUCCH resource set includes a predetermined number or a number of PUCCH resources less than the predetermined number, the terminal device 1 may determine the PUCCH resource based on the value of the PRI included in the DCI format. Also, it may be determined whether the PUCCH resource set uses a first PUCCH resource set to which a first frequency resource allocation type is applied or a second PUCCH resource set to which a second frequency resource allocation type is applied based on the first information included in the DCI format. The first information may be information indicating whether the PUCCH is transmitted within the COT or outside the COT, may be information indicating a frequency resource allocation type of the PUCCH, or may be information indicating a type of CAP before transmission of the PUCCH.

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

The PUCCH resource set may be accompanied by a set of PUCCH resource indices provided by resourceList providing the set of pucch-ResourceIds used for the PUCCH resource set. The PUCCH resource set may also be accompanied by a maximum number of UCI information bits that can be transmitted using the PUCCH resources 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 indices for one PUCCH resource set may be provided by maxNrofPUCCH-ResourcesPerSet. For NR-U, the maximum number of PUCCH resources included in all PUCCH resource sets may be 32.

If the terminal device 1 provides, as capability information, that it supports maxNrofPUCCH-ResourceSets-r16, which is greater than maxNrofPUCCH-ResourceSets, more PUCCH resource sets than the four sets supported by maxNrofPUCCH-ResourceSets may be configured for the terminal device 1. In this case, the PUCCH resource set may be provided by PUCCH-ResourceSet-r16 and may be associated with the PUCCH resource set index provided by pucch-ResourceSetId-r16. In other words, the value that pucch-ResourceSetId-r16 can take may be any value from 0 to maxNrofPUCCH-ResourceSets-r16-1.

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

When the terminal device 1 provides capability information indicating that it supports maxNrofPUCCH-ResourceSets-r16 with a value greater than a predetermined value, or when the terminal device 1 provides capability information indicating that different frequency resource allocation types are possible, or when the terminal device 1 provides capability information indicating that it supports PUCCH-ResourceSet-r16 and/or PUCCH-Resource-r16, the base station device 3 may set PUCCH-ResourceSet-r16 or PUCCH-Resource-r16 to include a parameter related to the frequency resource allocation type (e.g., freqResourceAllocType-r16) for the terminal device 1 that provided the capability information. Note that even if maxNrofPUCCH-Resources-r16 with a value greater than a predetermined value is provided instead of maxNrofPUCCH-ResourceSets-r16, the base station device 3 may perform the same process.

If the base station device 3 sets a PUCCH-ResourceSet with a pucch-ResourceSetId value greater than a predetermined value, it may set each PUCCH-ResourceSet to include freqResourceAllocType.

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

A PUCCH resource set with a value of 1 in pucch-ResourceSetId-r16 may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and/or 4. The number of UCI information bits transmittable by the PUCCH resources of a PUCCH resource set with pucch-ResourceSetId-r16=1 may range from 3 to _N2 . The value of _N2 may be given by maxPayloadMinus1 included in the PUCCH resource set.

A PUCCH resource set with a value of 2 in pucch-ResourceSetId-r16 may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and/or 4. The number of UCI information bits transmittable by the PUCCH resources of a PUCCH resource set with pucch-ResourceSetId-r16=2 may range from _N2 +1 to _N3 . The value of _N3 may be given by maxPayloadMinus1 included in the PUCCH resource set.

A 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 transmittable by the PUCCH resources of a PUCCH resource set in which pucch-ResourceSetId-r16=3 may range from N ₃ +1 to 1706. In this case, maxPayloadMinus1 may not be included in the PUCCH resource set.

A PUCCH resource set with a value of pucch-ResourceSetId-r16 of 4 may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and/or 4. The number of UCI information bits transmittable by the PUCCH resources of a PUCCH resource set with pucch-ResourceSetId-r16=4 may range from 3 to _N2 . The value of _N2 may be given by maxPayloadMinus1 included in the PUCCH resource set.

A PUCCH resource set with a value of pucch-ResourceSetId-r16 of 5 may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and/or 4. The number of UCI information bits transmittable by the PUCCH resources of a PUCCH resource set with pucch-ResourceSetId-r16=5 may range from _N2 +1 to N3. The value of _N3 may be given by maxPayloadMinus1 included in the PUCCH resource set.

A PUCCH resource set in which the value of pucch-ResourceSetId-r16 is 6 may be a PUCCH resource set including PUCCH resources of PUCCH formats 2, 3, and/or 4. The number of UCI information bits transmittable by the PUCCH resources of a PUCCH resource set in which pucch-ResourceSetId-r16=6 may range from N ₃ +1 to 1706. In this case, maxPayloadMinus1 may not be included in the PUCCH resource set.

If different PUCCH resource set IDs are set in multiple PUCCH resource sets to which the same or same range of UCI information bit numbers (i.e., the same value of maxPayloadMinus1) are applied, the physical resource mapping or frequency resource allocation type may be different between the multiple PUCCH resource sets. For example, different frequency resource allocation types may be set for the PUCCH resources of the PUCCH resource sets of pucch-ResourceSetId-r16=1 and pucch-ResourceSetId-r16=4, and the frequency resource allocation type of the PUCCH resource set of the PUCCH resource set of pucch-ResourceSetId-r16=1 may be contiguous, and the frequency resource allocation type of the PUCCH resource set of the PUCCH resource set of pucch-ResourceSetId-r16=4 may be interlaced. Other IDs (pucch-ResourceSetId-r16=2 and 5, and pucch-ResourceSetId-r16=3 and 6) may be set in a similar manner.

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

In each PUCCH resource set, if maxPayloadMinus1 corresponding to _N2 or _N3 is not set, _N2 or _N3 may be regarded as 1706.

If the terminal device 1 has the capability of setting more than a predetermined number of PUCCH resource sets, and if more than the predetermined number of PUCCH resource sets are set for the terminal device 1, or if a PUCCH resource set ID (pucch-ResourceSetId-r16) with a value greater than a predetermined value (pucch-ResourceSetId) is set, a PUCCH resource set corresponding to the frequency resource arrangement of the PUCCH may be set for the terminal device 1. In such a case, for the same or similar number of UCI information bits, a PUCCH resource set to which the first frequency resource arrangement type is applied and a PUCCH resource set to which the second frequency resource arrangement type is applied may be set for the terminal device 1. In addition, a PUCCH resource set including at least one PUCCH resource of the first frequency resource arrangement type and a PUCCH resource set including at least one PUCCH resource of the second frequency resource arrangement 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 contiguous allocation, or the first frequency resource allocation type and the second frequency resource allocation type may be vice versa.

When a resourceSetToAddModList-r16 is configured to which a number greater than a predetermined number or a maxNrofPUCCH-ResourceSets-r16 greater than a value greater than maxNrofPUCCH-ResourceSets is applied, or when a PUCCH resource set is configured that includes a pucch-ResourceSetId-r16 greater than a predetermined value, PUCCH-ResourceSet-r16 or PUCCH-Resource-r16 may include a parameter indicating the frequency resource allocation type of the PUCCH resource (e.g., freqResourceAllocType-r16).

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

For a terminal device 1 in which a first PUCCH resource set and a second PUCCH resource set to which the same maximum UCI bit number is applied are configured, it may be determined whether to transmit a HARQ-ACK for the PDSCH using a PUCCH resource included in the first PUCCH resource set or to transmit a HARQ-ACK for the PDSCH using a PUCCH resource included in the second PUCCH resource set, based on the first information included in the DCI format used for scheduling the 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 this embodiment, the frequency resource allocation type (first resource allocation type, second frequency resource allocation type) may refer to an interlaced arrangement or a contiguous arrangement, or may refer to other frequency resource arrangements.

Figure 8 is a diagram showing an example of parameters included in a PUCCH resource set and a 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 may be set to a value larger than pucch-ResourceSetId. In other words, maxNrofPUCCH-ResourceSets-r16 may be set to a value larger than maxNrofPUCCH-ResourceSets (i.e., 4 sets).

freqResourceAllocType-r16 may indicate a frequency resource allocation type to be 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 configurable types may change depending on the number of frequency resource allocation types supported. The frequency resource allocation type may be information indicating interlaced allocation and contiguous allocation. The frequency resource allocation type may also be information indicating whether interlaced allocation is possible.

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

maxPayloadMinus1 is information indicating the maximum number of UCI information bits that can be transmitted in the PUCCH resources of the PUCCH resource set, and corresponds to _N2 or _N3 described above. maxPayloadMinus1-r16 may support a different maximum number of UCI information bits compared to maxPayloadMinus1. That is, the range of the number of UCI information bits supported by maxPayloadMinus1-r16 may be wider or narrower than maxPayloadMinus1. The maximum value of the number of UCI information bits supported by maxPayloadMinus1-r16 may be larger or smaller than maxPayloadMinus1.

PUCCH-Resource-r16 may refer to the PUCCH resources listed by resourceList or resourceList-r16. PUCCH-Resource-r16 may include pucch-ResourceId-r16, startingPRB, intraSlotFrequencyHopping, secondHopPRB, and format.

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

The information indicated by startingPRB may change based on the frequency resource allocation type indicated by freqResourceAllocType-r16. For example, if freqResourceAllocType-r16 corresponding to the PUCCH resource indicates a frequency resource allocation type corresponding to continuous allocation, startingPRB may be information indicating the first PRB index of the PUCCH resource. If freqResourceAllocType-r16 corresponding to the PUCCH resource indicates an interlace allocation, startingPRB may indicate an interlace index. It may also be used to calculate an interlace index. For example, the interlace index 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 a frequency resource allocation type corresponding to continuous allocation. intraSlotFrequencyHopping is information indicating whether intra-slot frequency hopping 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 specific parameters applied may be the same as those in FIG. 7 or may be different. Since format4 is not applied in NR-U, it may be set as an optional parameter. In other words, format4 may be included when applied to other than NR-U.

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

Figure 10 is a diagram showing an example of DCI format 1_0 according to one aspect of the present embodiment. Figure 10 (a) is an example of DCI format 1_0 for NR. Figure 10 (b) is an example of DCI format 1_0 for NR-U. A field related to the channel access procedure of PUCCH may be added to DCI format 1_0 for NR-U. The size of PRI may change depending on the number of PUCCH resources. In addition, DCI format 1_0 for NR-U may include information indicating the frequency resource allocation type for PUCCH resources. In that case, the parameters shown in Figures 8 and 9 may not be set as RRC parameters. Details of PUCCH starting position, Channel access type, and Channel access priority class will be described later. In addition, PUCCH starting position, Channel access type, and Channel access priority class may not be included in the DCI format when they are determined based on specifications or higher layer parameters.

PUSCH is used at least for transmitting TBs (MAC PDU, UL-SCH). PUSCH may be used at least for transmitting TBs, HARQ-ACK information, CSI, and some or all of SRs. PUSCH is used at least for transmitting RAR (Msg2) in the random access procedure and/or random access message 3 (message 3 (Msg3)) corresponding to RAR grant. Note that TBs may correspond to both uplink and downlink. That is, PUSCH may be used for transmitting TBs for uplink. PDSCH may be used for transmitting TBs for downlink.

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

The random access preamble may be provided by cyclically shifting a Zadoff-Chu sequence corresponding to a physical root sequence index u. The Zadoff-Chu sequence may be generated based on the physical root sequence index u. A plurality of random access preambles may be defined in one serving cell. The random access preamble may be identified based at least on an index of the random access preamble. Different random access preambles corresponding to different indices of the random access preamble may correspond to different combinations of the physical root sequence index u and the cyclic shift. The physical root sequence index u and the cyclic shift may be provided based at least on information included in the system information. The physical root sequence index u may be an index that identifies a sequence included in the random access preamble. The random access preamble may be identified based at least on the physical root sequence index u.

In Fig. 1, the following uplink physical signals are used in uplink wireless communication: The uplink physical signals may not be used to transmit information output from higher layers, but are 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 related to the transmission of PUSCH and/or PUCCH. UL DMRS is multiplexed with PUSCH or PUCCH. Base station device 3 may use UL DMRS to perform propagation path correction of PUSCH or PUCCH. Hereinafter, transmitting PUSCH and UL DMRS related to the PUSCH together is simply referred to as transmitting PUSCH. Hereinafter, transmitting PUCCH and UL DMRS related to the PUCCH together is simply referred to 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.

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

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

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

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

The PDCCH is used at least for transmitting downlink control information (DCI). The PDCCH may be transmitted including at least the DCI. The PDCCH may be transmitted including the DCI. The DCI may also be referred to as a DCI format. The DCI may indicate at least either a downlink grant or an uplink grant. The DCI format used for scheduling the PDSCH may also be referred to as a downlink DCI format and/or a downlink grant. The DCI format used for scheduling the PUSCH may also be referred to as an uplink DCI format and/or an uplink grant. The downlink grant may also be referred to as a downlink assignment or a downlink allocation. 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 some or all of 1A to 1I.
1A) Identifier for DCI formats field
1B) Frequency domain resource assignment field
1C) Time Domain Resource Assignment Field
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)
1F) NDI field (New Data Indicator field)
1G) RV field (Redundancy Version field)
1H) HARQ process ID field, HARQ process number field
1I) TPC (Transmission Power Control) command field for scheduled PUSCH

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

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

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

1D may be used at least to indicate whether frequency hopping is applied to a PUSH scheduled by a DCI format that includes the 1D.

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

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

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

1H is used to indicate the HARQ process number (HPID) to which the PUSH scheduled by the DCI format corresponds.

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

DCI format 0_1 is configured to include at least some 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 used at least to indicate the reporting of CSI. The size of 2F may be a predetermined value. The size of 2F may be 0, 1, 2, or 3. The size of 2F 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 PUSH scheduled by DCI format 0_1 is mapped.

The second CSI request field is at least used to indicate a CSI report. The size of the second CSI request field may be based at least on the higher layer parameter ReportTriggerSize.

Of fields 2A to 2K, those with the same names as fields 1A to 1I described above contain the same content, so their explanations will be omitted.

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

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

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

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

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

3H is used to indicate whether the transmission of the PDSCH scheduled by the DCI format corresponding to the value of HPID indicated by 3J is a new transmission or a retransmission based on whether the value of 3H is toggled. If the value of 3J is toggled, the PDSCH corresponding to 3J is a new transmission, otherwise the PDSCH corresponding to 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.

DCI format 1_1 may be configured to include at least some 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) PDSCH to HARQ feedback timing indication field 4G) PUCCH resource indication 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.

When 1A, 2A, 3A, and 4A are each composed of 1 bit, they may be used to indicate either DCI format 0_0 or DCI format 1_0, or either DCI format 0_1 or DCI format 1_1, and when composed of 2 bits, they may be used to indicate any one of the four formats DCI format 0_0 to DCI format 1_1.

4B to 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 by DCI format 1_1 is mapped.

Of fields 4A to 4L, those with the same names as fields 3A to 3K described above contain the same content, so their explanations will be omitted.

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

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

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

One physical channel may be mapped to one serving cell. One physical channel may be mapped to one CBP configured on one carrier included in one serving cell.

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

The CORESET may indicate a time-frequency region to which one or more PDCCHs may be mapped. The CORESET may be a region in which the terminal device 1 monitors the PDCCHs. The CORESET may be configured with continuous resources (localized resources). The CORESET may be configured with non-continuous resources (distributed resources).

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

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

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

A CORESET may be a common CORESET. The common CORESET may be a CORESET that is set in common for multiple terminal devices 1. The common CORESET may be given based on at least a part or all of the MIB, SIB, common RRC signaling, and cell ID. For example, the time resources and/or frequency resources of the CORESET that is set to monitor the PDCCH used for scheduling the SIB may be given based on at least the MIB.

A CORESET may be a dedicated CORESET. The dedicated CORESET may be a CORESET that is set to be used exclusively for the terminal device 1. The dedicated CORESET may be provided based at least on dedicated RRC signaling.

The set of PDCCH candidates monitored by the terminal device 1 may be defined in terms of a search space. That is, the set of PDCCH candidates monitored by the terminal device 1 may be given by a search space.

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

The terminal device 1 may monitor at least one or more search space sets in slots where DRX (Discontinuous reception) is not set. DRX may be provided based at least on higher layer parameters. The terminal device 1 may monitor at least one or more search space sets in slots where DRX is not set.

The search space set may be configured to include at least one or more search spaces. The type of the search space set may be any of a type 0 PDCCH common search space, a type 0a PDCCH common search space, a type 1 PDCCH common search space, a type 2 PDCCH common search space, a type 3 PDCCH common search space, and/or a UE-specific PDCCH search space.

The Type 0 PDCCH common search space, the Type 0a PDCCH common search space, the Type 1 PDCCH common search space, the Type 2 PDCCH common search space, and the Type 3 PDCCH common search space may also be referred to as a Common Search Space (CSS). The UE-specific PDCCH search space may also be referred to as a UE specific Search Space (USS).

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

The type 0 PDCCH common search space may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The configuration of the type 0 PDCCH common search space may be based at least on the four least significant bits (LSBs) of the upper layer parameter PDCCH-ConfigSIB1. The upper layer parameter PDCCH-ConfigSIB1 may be included in the MIB. The configuration of the type 0 PDCCH common search space may be based at least on the upper layer parameter SearchSpaceZero. The interpretation of the bits of the upper layer parameter SearchSpaceZero may be similar to the interpretation of the four least significant bits (LSBs) of the upper layer parameter PDCCH-ConfigSIB1. The setting of the type 0 PDCCH common search space may be based at least on the higher layer parameter SearchSpaceSIB1. The higher layer parameter SearchSpaceSIB1 may be included in the higher layer parameter PDCCH-ConfigCommon. The PDCCH detected in the type 0 PDCCH common search space may be used at least for scheduling the PDSCH including SIB1 and transmitted. SIB1 is a type of SIB. SIB1 may include scheduling information of SIBs other than SIB1. The terminal device 1 may receive the higher layer parameter PDCCH-ConfigCommon in EUTRA. The terminal device 1 may receive the higher layer parameter PDCCH-ConfigCommon in MCG.

The type 0a PDCCH common search space may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The configuration of the type 0a PDCCH common search space may be based at least on the higher layer parameter SearchSpaceOtherSystemInformation. The higher layer parameter SearchSpaceOtherSystemInformation may be included in SIB1. The higher layer parameter SearchSpaceOtherSystemInformation may be included in the higher layer parameter PDCCH-ConfigCommon. The PDCCH detected in the type 0 PDCCH common search space may be used at least for scheduling the PDSCH transmitted including SIBs other than SIB1.

The type 1 PDCCH common search space may be used at least for a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and/or a DCI format with a CRC sequence scrambled by a Temporary Common-Radio Network Temporary Identifier (TC-RNTI). The RA-RNTI may be given at least based on the time/frequency resources of a random access preamble transmitted by the terminal device 1. The TC-RNTI may be given by a PDSCH (also called a random access message 2, message 2 (Msg2), or random access response (RAR)) scheduled by a DCI format with a CRC sequence scrambled by the RA-RNTI. The type 1 PDCCH common search space may be given at least based on a higher layer parameter ra-SearchSpace. The higher layer parameter ra-SearchSpace may be included in SIB1. The higher layer parameter ra-SearchSpace may be included in the higher layer parameter PDCCH-ConfigCommon.

The type 2 PDCCH common search space may be used for DCI formats with a CRC sequence scrambled by a P-RNTI (Paging-Radio Network Temporary Identifier). The P-RNTI may be used at least for transmission of DCI formats including information notifying a change in the SIB. The type 2 PDCCH common search space may be given based at least on the higher layer parameter PagingSearchSpace. The higher layer parameter PagingSearchSpace may be included in SIB1. The higher layer parameter PagingSearchSpace may be included in the higher layer parameter PDCCH-ConfigCommon.

The Type 3 PDCCH common search space may be used for a DCI format with a CRC sequence scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI). The C-RNTI may be provided based at least on a PDSCH (which may also be referred to as a Random Access Message 4, Message 4 (Msg4), or Contention Resolution) scheduled by a DCI format with a CRC sequence scrambled by a TC-RNTI. The Type 3 PDCCH common search space may be the search space set provided when the higher layer parameter SearchSpaceType is set to common.

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

When a C-RNTI is provided to the terminal device 1, a Type 0 PDCCH common search space, a Type 0a PDCCH common search space, a Type 1 PDCCH common search space, and/or a Type 2 PDCCH common search space may be used at least for DCI formats with a CRC sequence scrambled with the C-RNTI.

When a C-RNTI is provided to the terminal device 1, a search space set provided based at least on any of 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 ra-SearchSpace, or the upper layer parameter PagingSearchSpace may be used at least for a DCI format with a CRC sequence scrambled with the C-RNTI.

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

The physical resources of the search area are composed of control channel units (CCE: Control Channel Element). A CCE is composed of six resource element groups (REG: Resource Element Group). A REG may be composed of one OFDM symbol of one PRB (Physical Resource Block). In other words, a REG may be composed of 12 resource elements (RE: Resource Element). A PRB may also be simply referred to as a resource block (RB).

The PDSCH is used at least to transmit the TB. The PDSCH may also be used at least to transmit a random access message 2 (RAR, Msg2). The PDSCH may also be used at least 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 signals may not be used to transmit information output from higher layers, but are 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 frequency domain and/or time domain of the downlink. The synchronization signal includes a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).

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

DL DMRS is related to 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 DL DMRS corresponding to the PBCH, the PDCCH, or the PDSCH to perform propagation path correction of the PBCH, the PDCCH, or the PDSCH. Hereinafter, the transmission of the PBCH and the DL DMRS associated with the PBCH together may be referred to as the transmission of the PBCH. Also, the transmission of the PDCCH and the DL DMRS associated with the PDCCH together may be simply referred to as the transmission of the PDCCH. Also, the transmission of the PDSCH and the DL DMRS associated with the PDSCH together may be simply referred to as the transmission of the PDSCH. The DL DMRS associated with the PBCH may also be referred to as the DL DMRS for the PBCH. The DL DMRS associated with the PDSCH may also be referred to as a DL DMRS for the PDSCH. The DL DMRS associated with the PDCCH may also be referred to as a DL DMRS associated with the PDCCH.

The DL DMRS may be a reference signal that is individually set to the terminal device 1. The sequence of the DL DMRS may be provided based at least on a parameter that is individually set to the terminal device 1. The sequence of the DL DMRS may be provided based at least on a UE-specific value (e.g., C-RNTI, etc.). The DL DMRS may be transmitted individually for the PDCCH and/or the PDSCH.

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

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

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

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

The downlink physical channel and the downlink physical signal may also be referred to as downlink signals. The uplink physical channel and the uplink physical signal may also be referred to as uplink signals. The downlink signal and the uplink signal may also be referred to as physical signals or signals. The downlink physical channel and the uplink physical channel may also be referred to as physical channels. In the downlink, the physical signal may include some or all of SSB, PDCCH (CORESET), PDSCH, DL DMRS, CSI-RS, DL PTRS, and TRS. In the uplink, the physical signal may include some or all of PRACH, PUCCH, PUSCH, UL DMRS, UL PTRS, and SRS. The physical signal may be a signal other than the above-mentioned signals. 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. A channel used in the Medium Access Control (MAC) layer may be called a transport channel. The unit of the transport channel used in the MAC layer may be called a TB or MAC PDU. In the MAC layer, HARQ control is performed for each TB. A TB is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, a TB is mapped to a codeword, and modulation processing is performed for each codeword.

The base station device 3 and the terminal device 1 exchange (transmit and receive) higher layer signals in a higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive RRC signaling (RRC messages, RRC information, RRC parameters, RRC information elements) in the radio resource control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive MAC CE (Control Element) in the MAC layer. Here, the RRC signaling and/or MAC CE are also referred to as higher layer signaling.

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

BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, BCCH is an upper layer channel used to transmit MIB. CCCH (Common Control CHannel) is an upper layer channel used to transmit information common to multiple terminal devices 1. Here, CCCH may be used, for example, for terminal devices 1 that are not RRC-connected. DCCH (Dedicated Control CHannel) is an upper layer channel that is used at least to transmit dedicated control information to terminal device 1. Here, DCCH may be used, for example, for terminal devices 1 that are RRC-connected.

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

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

Below, we will explain an example configuration of a terminal device 1 related to one aspect of this embodiment.

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

The upper layer processing unit 14 outputs uplink data (TB, UL-SCH) generated by user operation, etc., to the wireless transceiver unit 10. The upper layer processing unit 14 processes the MAC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer.

The media access control layer processing unit 15 provided in the upper layer processing unit 14 performs processing of the MAC layer.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing. The radio resource control layer processing unit 16 manages various setting information/parameters of the own device. The radio resource control layer processing unit 16 sets various setting information/parameters based on upper layer signals received from the base station device 3. In other words, the radio resource control layer processing unit 16 sets various setting information/parameters based on information indicating the various setting information/parameters received from the base station device 3. The parameters may be upper layer parameters and/or information elements.

The wireless transceiver unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver 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 processing. The wireless transceiver unit 10 generates a physical signal (uplink signal) by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) on the data, and transmits the physical signal to the base station device 3. These processes may be referred to as transmission processing.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation (down-converts it) 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 the 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 the signal in the frequency domain.

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

The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies the power. The RF unit 12 may also have a function of controlling the transmission power. The RF unit 12 is also referred to as a transmission power control unit.

Below, we will explain an example configuration of a base station device 3 related to one aspect of this embodiment.

Figure 12 is a schematic block diagram showing the configuration of a base station device 3 according to one aspect of this embodiment. As shown in the figure, the base station device 3 includes a radio 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 radio transmission/reception unit 30 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing unit.

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

The media access control layer processing unit 35 provided in the upper layer processing unit 34 performs processing of the MAC layer.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 generates downlink data (TB, DL-SCH), system information, RRC messages, MAC CE, etc. to be placed in the PDSCH, or acquires them from the upper node, and outputs them to the radio transceiver unit 30. The radio resource control layer processing unit 36 also manages various setting information/parameters for each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via signals from the upper layer. That is, the radio resource control layer processing unit 36 transmits/reports information indicating various setting information/parameters.

The basic functions of the wireless transceiver unit 30 are the same as those of the wireless transceiver unit 10, so a description thereof will be omitted. The wireless transceiver unit 30 transmits the physical signal generated in the wireless transceiver unit 30 to the terminal device 1 (i.e., performs transmission processing). The wireless transceiver unit 30 also 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 of the units numbered 10 to 16 in the terminal device 1 may be configured as a circuit. Each of the units numbered 30 to 36 in the base station device 3 may be configured as a circuit. Some or all of the units numbered 10 to 16 in the terminal device 1 may be configured as a memory and a processor connected to the memory. Some or all of the units numbered 30 to 36 in the base station device 3 may be configured as a memory and a processor connected to the memory. Various aspects (operations, processing) of this 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 if it is determined that the carrier (i.e., NR-U carrier) or BWP (i.e., NR-U BWP) or channel (i.e., NR-U channel) in which the NR-U cell transmission is performed is idle (clear, free, no communication is being performed, a specific physical signal is not being transmitted, the power (energy) of a specific physical signal is not detected, the detected (measured) power (energy) or the total power does not exceed a predetermined threshold) for a predetermined period, the terminal device 1 or the base station device 3 may transmit a physical signal in the carrier, BWP, or channel. In other words, when the terminal device 1 or the base station device 3 communicates in the NR-U cell, it performs CCA (Clear Channel Assessment) or channel measurement for a predetermined period to confirm that the NR-U cell is idle. The predetermined period may be determined from the delay period T _d , the counter N, and the CCA slot period T _sl . In addition, when CCA is performed, not being idle may be referred to as being busy. In addition, CCA may be performed by the radio transmission/reception unit 10 of the terminal device 1 and/or the radio transmission/reception unit 30 of the base station device 3. In addition, 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 in a certain channel. A procedure for performing energy detection to determine whether the channel is idle before transmitting such a physical signal, or a procedure for determining whether the channel is idle and transmitting a physical signal if it is idle, 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 may include at least a frequency band available for transmitting a physical signal of NR-U. In other words, the NR-U cell, the NR-U carrier, the NR-U BWP, and the NR-U channel may be synonymous. In this embodiment, the NR-U cell may be rephrased 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 the NR-U carrier, the NR-U BWP, and the NR-U channel. The NR cell may be configured to include at least one of the NR carrier, the NR BWP, and the NR channel.

Here, if the base station device 3 and/or terminal device 1 are capable of performing (have the ability to perform) a multi-carrier access procedure (CAP for each of the multiple carriers) in one NR-U operating band, multiple carriers (NR-U carriers) and/or multiple BWPs (NR-U BWPs) may be configured for one NR-U cell.

The predetermined period is a period in which the counter N becomes 0 in a channel that is first sensed as being idle in a delay period after detecting a signal other than that of 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. Note that, if it is determined to be busy in a 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 value of CW _p (Contention Window) (CWS: CW size). For example, the value of N _int may be determined based on a random function uniformly distributed from 0 to the value of CW _p . The possible values (value range) of N _int may be expanded by updating the value of CW _p .

When the terminal device 1 or the base station device 3 transmits one or more physical signals in an NR-U cell, it sets the value of the counter N to N _int .

If the terminal device 1 or base station device 3 determines that the CCA slot period is cleared when the value of N is greater than 0, the terminal device 1 or base station device 3 sets the value of N to N-1. In other words, if the terminal device 1 or base station device 3 determines that the CCA slot period is cleared, the terminal device 1 or base station device 3 may decrement the value of counter N by 1.

If the decremented value of N becomes 0, the terminal device 1 or the base station device 3 may stop 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 the base station device 3 may continue CCA during the CCA slot period until the value of N becomes 0.

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

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

A channel access procedure in which the values of CAPC p and CW _p are variable based on set information and conditions may be referred to as a type 1 channel access procedure (type 1 CAP), and a channel access procedure in which the value of CW _p is always 0, or a counter N corresponding to the value of CW _p is not used, or a CCA is performed only once before transmission may be referred to as a type 2 channel access procedure (type 2 CAP). In other words, the type 1 channel access procedure is a channel access procedure in which the period of CCA changes depending on the value of CW _p updated based on the set CAPC value p and conditions. In addition, the type 2 channel access procedure is a channel access procedure in which CCA is performed only once before the transmission of a physical signal, and if it is determined that the channel (frequency band) for transmitting the physical signal is idle, transmission can be performed. Here, before transmission may include immediately before transmission. If the channel access procedure is not completed before the transmission of a physical signal, the terminal device 1 and/or the base station device 3 may not transmit the physical signal at that transmission timing, or may postpone the transmission of the physical signal. 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 higher layer parameters.

Figure 14 is a diagram showing an example of a channel access priority class (CAPC) and CW adjustment procedure relating to one aspect of this embodiment.

The CAPC value p is used to indicate the number m _p of CCA slot periods _Tsl included in the delay period _Td , the minimum and maximum values of CW, the maximum channel occupancy time, and the allowable value of CW _p (CWS). The CAPC value p may be set according to the priority of the physical signal. The CAPC value p may be included and indicated in the DCI format.

Before setting the value of the counter N to N _init , the terminal device 1 may adjust the value of CW for determining the value of N _init . In addition, when the random access procedure is successfully completed, the terminal device 1 may maintain the updated value of CW for the random access procedure. In addition, when the random access procedure is successfully completed, the terminal device 1 may set the updated value of CW to CW _min for the random access procedure. Here, in this 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, setting the updated value of CW to CW _min may be updating the value of CW that is updated when one or more predetermined conditions are satisfied to CW _min . In addition, setting the updated value of CW to CW _min may be resetting the value of CW to CW _min .

The terminal device 1 may adjust the value of CW for determining the value of _Ninit before setting _Ninit to the value of counter N corresponding to CCA performed before transmitting Msg1. Note that the terminal device 1 may maintain the updated value of CW when it determines that it has successfully received Msg2 and/or when it determines that it has successfully received Msg4. Also, the terminal device 1 may set the updated value of CW to _CWmin when it determines that it has successfully received Msg2 and/or when it determines that it has successfully received Msg4.

Here, adjusting the value of CW may mean increasing the value of CW _p by one step from CW _min until it reaches CW _max when the value of CW p satisfies a predetermined condition. When it reaches CW _max , it also increases by one step from CW _min . In other words, adjusting the value of CW may mean updating the value of CW _p . Updating the value of CW _p may mean changing the value of CW _p to a value one step larger. For example, it may be changing the value of CW p from CW #3 to CW #4, or from CW #n-1 to CW #n. Furthermore, the terminal device 1 and/or the base station device 3 may determine the value of N _init based on a random function uniformly distributed between 0 and the updated value of CW _p every time the value of CW is adjusted.

The value p of the channel access priority class (CAPC) applied to the transmission of Msg1 may be determined based on system information, higher layer parameters, or associated with the SSB. For example, if the value p of the CAPC corresponding to Msg1 is P, the value of _Ninit 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 the PUSCH, PUCCH, and PRACH. A common value may be set for the CAPC value p as a cell-specific upper layer parameter for the PUSCH, PUCCH, and PRACH. The CAPC value p may be set as an individual upper layer parameter for each of the PUSCH, PUCCH, and PRACH. The CAPC value p for the PUSCH may be included and indicated in a DCI format used for scheduling the PUSCH. The CAPC value p for the PUCCH may be included and indicated in a DCI format including a PUCCH resource indication field. The CAPC value p for the PRACH may be included and indicated in a DCI format for the PDCCH order. The CAPC value p for the PRACH may be determined according to the type of random access procedure. For example, the CAPC value p for the CBRA may be determined based on system information and/or upper layer parameters. In addition, the CAPC value p for CFRA may be determined based on higher layer parameters, or may be included in and set in a DCI format corresponding to a PDCCH order. In CFRA, whether the CAPC value p is based on higher layer parameters or on a field of a DCI format may be determined based on system information and/or higher layer parameter settings.

When the terminal device 1 transmits a HARQ-ACK for the PDSCH on the PUCCH resource, the type of channel access procedure for the PUCCH and/or the CAPC value p may be set by including one or more dedicated fields in the DCI format used for scheduling the PDSCH. The DCI format may include a PUCCH resource indication field. That is, the type of channel access procedure for the PUCCH and/or the CAPC value may be used for the PUCCH resource indicated by the PUCCH resource indication field. Also, when the terminal device 1 transmits an SR on the PUCCH resource, the type of channel access procedure for the PUCCH and/or the CAPC value p may be set based on one or more higher layer parameters included in the PUCCH configuration or the SR configuration.

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

In this embodiment, the value p of CAPC is described, but the type of channel access procedure (CAP) (type 1 CAP, type 2 CAP, i.e., CAT (Channel Access Type)), the value of CW, and/or the value of _Tmcot may be set in the same manner. In addition, for CAT, CAT1 may indicate type 1 CAP, and CAT2 may indicate type 2 CAP.

For example, in an NR-U cell, DCI formats (DCI formats 0_0, 0_1, 1_0, 1_1) used for scheduling PDSCH and PUSCH and allocating resources for PRACH may include some or all of fields 8A to 8E below in order to perform a channel access procedure.
8A) Type of Channel Access Procedure (CAP) (Channel Access Type (CAT))
8B) Channel Access Priority Class (CAPC) value p
8C) Maximum channel occupancy time T _mcot
8D) The value of CW 8E) The maximum number of CCA slot periods m

For PUCCH, some or all of 8A to 8E may each be a predetermined value or may be determined based on higher layer parameters for each.

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

If the received DCI format indicates resource allocation for a random access preamble, i.e., if a PDCCH order is received and the PDCCH order includes some or all of 8A to 8E, the channel access procedure before transmitting the random access preamble may be performed based on some or all of 8A to 8E included in the PDCCH order.

In the case of transmitting SR on PUCCH in the NR-U carrier, some or all of the above 8A to 8E may be included in the PUCCH setting or SR setting. In other words, when a channel access procedure is performed for a PUCCH including an SR, parameters for the channel access procedure may be set based on higher layer parameters. Also, when a channel access procedure is performed for a PUCCH including an SR, parameters for the channel access procedure may be transmitted from the base station device 3 to the terminal device 1 via a signal in the RRC layer and set.

Next, we will explain the HARQ operation related to this embodiment.

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

The number (maximum number) of parallel DL HARQ processes per HARQ entity may be set based on higher layer parameters (e.g., RRC parameters) or may be a default value if the higher layer parameters are not received. A dedicated broadcast HARQ process may be used for the 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 supports one or two TBs when the physical layer is configured for downlink spatial multiplexing.

When the higher layer parameter pdsch-AggregationFactor is set to a value greater than 1, the MAC entity of the terminal device 1 may provide the number of TB transmissions in a bundle of dynamic downlink assignments. The bundling operation (HARQ-ACK bundling operation) relies on the HARQ entity to invoke (activate) the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, one less HARQ retransmissions than the value set by pdsch-AggregationFactor (i.e., pdsch-AggregationFactor-1) may follow in the bundle.

The MAC entity of the terminal device 1 may assign one or more TBs and associated HARQ information received from the physical layer to the HARQ process indicated by the associated HARQ information if a downlink assignment is indicated. The MAC entity of the terminal device 1 may also assign the received TBs to a broadcast HARQ process if a downlink assignment is indicated for a broadcast HARQ process.

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

For each received TB and associated HARQ information, the HARQ process (HARQ process associated with a certain HPID) considers this transmission as a new transmission if, when an NDI is provided, the NDI is toggled compared to the value of the previously received transmission corresponding to this TB (the value of the NDI associated with the HPID included in the PDCCH), or if the HARQ process corresponds to a broadcast process and this is the first received transmission for the TB according to the system information schedule indicated by the RRC, or if this is indeed the first received transmission for this TB (i.e. a new transmission with no previous NDI for this TB). Otherwise, the HARQ process considers this transmission as a retransmission. Note that the previously received transmission may be a transmission received in the past. Here, the transmission may refer to a TB transmitted from the base station device 3.

The MAC entity attempts to decode the received data (data for the received TB) if this is a new transmission. If this is a retransmission, the MAC entity instructs the physical layer to combine the latest data received in the soft buffer for this TB and decode the combined data if the data for this TB has not yet been successfully decoded. The MAC entity also forwards the decoded MAC PDU to the upper layer (RLC layer, PDCP layer, and/or RRC layer) if the data it attempted to decode is successfully decoded for this TB, or if the data for this TB has been successfully decoded before, and if the HARQ process is the same as the broadcast process. If this is the first successful decoding of data for this TB, the MAC entity also forwards the decoded MAC PDU to the disassembly and demultiplexing entity. If not, the MAC entity instructs the physical layer to replace the data in the soft buffer for this TB with the data it has attempted to decode. The MAC entity instructs the physical layer to generate acknowledgment(s) for the data in this TB if the HARQ process is associated with the transmission indicated with the TC-RNTI and contention resolution has not yet been successful, or if the HARQ process corresponds to a broadcast process, or if the timeAlignmentTimer associated with the TAG containing the serving cell for which the HARQ feedback is transmitted has stopped or expired. Note that the acknowledgment may be an ACK or a NACK.

In the NR-U cell, the terminal device 1 and/or the MAC entity of the terminal device 1 may, in this HARQ process, generate acknowledgment(s) for the data in this TB if this transmission is considered to be a retransmission. The physical layer of the instructed terminal device 1 may update the value of CW used for N _init if a type 1 channel access procedure is performed before transmitting the PUCCH or PUSCH including the HARQ-ACK. Furthermore, in the NR-U cell, when the terminal device 1 and/or the MAC entity of the terminal device 1 considers this transmission to be a new transmission in this HARQ process, the physical layer of the instructed terminal device 1 that generates acknowledgment(s) for the data in this TB may set the value of CW used in N _init to the initial value of CW _p , or may not update the value of CW (i.e., may maintain the value of CW), if a type 1 channel access procedure is performed before transmitting a PUCCH or PUSCH including a HARQ-ACK. In addition, if the physical layer of the terminal device 1 performs a type 2 channel access procedure before transmitting a PUCCH or PUSCH including a HARQ-ACK, regardless of whether the transmission is a new transmission or a retransmission, it may perform CCA only once before transmitting a PUCCH or PUSCH including a HARQ-ACK, and if it determines that the NR-U channel is idle, it may transmit a PUCCH or PUSCH including a HARQ-ACK.

Here, updating the CW value means, for example, if there are three allowable settable CW values, CW#0, CW#1, and CW#2 (CW#0<CW#1<CW#2), updating the CW value to the next higher value, CW#1, when the CW value is CW#0. Also, updating the CW value means updating the CW value to the next higher value, CW#2, when the CW value is CW#1. Also, updating the CW value may include resetting the CW value to CW#0 ( _CWmin ) when the CW value is CW#2 ( _CWmax ) and there is no next higher value.

Here, the physical layer may include at least one of a transmitter, a receiver, a radio transceiver, and/or a measurement unit, and may be a physical layer processing unit. The MAC entity may be a MAC layer or may be a MAC layer processing unit.

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

When the terminal device 1 detects a DCI format used for scheduling the PDSCH in the NR-U cell in the PDCCH, if the DCI format includes a HARQ process ID (HPID) and an NDI, the terminal device 1 can determine whether the transmission of the PDSCH is a new transmission or a retransmission based on whether the NDI is toggled for the HPID. Furthermore, if the DCI format includes a field indicating a PUCCH resource, the terminal device 1 may determine whether to adjust the value of the CW based on whether the NDI is toggled. For example, if the value of NDI for the HARQ process associated with the first HPID is toggled, the terminal device 1 sets the value of CW _p corresponding to each CAPC value p to CW _min ; if not (i.e., if the value of NDI is not toggled), the terminal device 1 may increase the value of CW _p to the next higher allowed value (the value of CW) (i.e., the terminal device 1 may update the value of CW _p (the value of CW)).

When the terminal device 1 generates a HARQ-ACK codebook for a HARQ process associated with one or more HPIDs, it may update the value of CW for the type 1 channel access procedure performed before transmitting a PUCCH or PUSCH including the HARQ-ACK codebook, provided that the value of NDI has not been toggled for at least one HPID.

When base station device 3 transmits a PDCCH and a PDSCH including a DCI format used for scheduling the PDSCH in an NR-U cell, it performs a type 1 channel access procedure before transmitting the PDCCH and the PDSCH, and if it determines that the NR-U channel is idle in all CCA slot periods, it transmits the PDCCH and the PDSCH, and if it determines that the NR-U channel is not idle, it may postpone the transmission of the PDCCH and the PDSCH until it can determine that the NR-U channel is idle in all CCA slot periods.

If the base station device 3 fails to successfully receive the PUCCH or PUSCH including the HARQ-ACK for the PDSCH after a predetermined period of time has elapsed after transmitting the PDCCH and the PDSCH, the base station device 3 may retransmit the PDCCH and the PDSCH. When the base station device 3 retransmits the PDCCH and the PDSCH, the base station device 3 transmits the PDCCH and the PDSCH without toggling the value of the NDI for the HPID. In other words, the base station device 3 may indicate that the PDSCH is a retransmission by not toggling the value of the NDI for the HPID. In that case, if the base station device 3 performs a type 1 channel access procedure, the value of the CW may be updated.

In addition, if the base station device 3 successfully receives a PUCCH or PUSCH including a HARQ-ACK for the PDSCH corresponding to the HARQ process associated with the HPID within a predetermined period after transmitting the PDCCH and the PDSCH, the base station device 3 may reset the value of the CW corresponding to the HARQ process for the HPID to CW _min . In other words, in order to toggle the value of the NDI for the HARQ process associated with the HPID, the base station device 3 may set the value of the CW to CW _min if the base station device 3 performs a channel access procedure before transmitting the PDCCH and the PDSCH. Here, if the base station device 3 can manage HARQ processes associated with multiple HPIDs, the base station device 3 may perform a channel access procedure and/or a CW adjustment procedure for each HPID.

When the base station device 3 transmits a PDCCH and a PDSCH scheduled by the PDCCH, if the base station device 3 fails to successfully receive a PUCCH or PUSCH including a HARQ-ACK corresponding to the PDSCH (i.e., a HARQ-ACK for the HPID corresponding to the PDSCH) within a predetermined period (e.g., until a predetermined timer expires), the base station device 3 may update the values of the CW for the PDCCH and the PDSCH. Note that, if the base station device 3 successfully receives a PUSCH including a HARQ-ACK for the HPID corresponding to the PDSCH instead of a PUCCH, the base station device 3 does not need to update the values of the CW for the PDCCH and the PDSCH.

If the base station device 3 and/or the terminal device 1 determines that the HARQ operation of a HARQ process for a certain HPID is successful, it may set the updated CW value associated with that operation to CW _min .

If the terminal device 1 receives a PDSCH having the same HPID and indicating retransmission after transmitting a HARQ-ACK for a received PDSCH via PUCCH or PUSCH, or if retransmission of the HARQ-ACK for the PDSCH is requested, the terminal device 1 may update the value of the CW used for N _init if a type 1 channel access procedure is performed before transmitting a PUCCH including a HARQ-ACK for the PDSCH. In other words, every time retransmission is indicated for a PDSCH with the same HPID, the terminal device 1 may update the value of the CW used for the corresponding N _init if a type 1 channel access procedure is performed before transmitting a PUCCH including a HARQ-ACK for the PDSCH.

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

Figure 15 is a diagram showing an example of frequency mapping (resource allocation, mapping to physical resources, frequency resource allocation type) according to this embodiment. Figure 15(a) is an example (contiguous mapping, localized mapping) in which multiple PRBs are contiguously arranged for one terminal device 1 and/or base station device 3. The frequency mapping (frequency resource allocation type) of Figure 15(a) may be used, for example, to achieve low PAPR (Peak to Average Power Ratio) characteristics by a single carrier such as a DFT-s-OFDM signal. Figure 15(b) is an example (interlaced mapping, distributed mapping) in which multiple PRBs are arranged at equal or non-equal intervals for one terminal device 1 and/or base station device 3. The frequency mapping (frequency resource allocation type) of Figure 15(b) may be used to achieve 80% or more of the transmission bandwidth (maximum transmission bandwidth, channel bandwidth, carrier bandwidth, BWP bandwidth) in the frequency domain with a small number of PRBs. That is, the frequency mapping in FIG. 15(b) may be performed to satisfy the OCB (Occupied Channel Bandwidth) requirement. The number of interlaces may be determined according to the SCS. For example, when the SCS is 15 kHz, the number of interlaces may be 10 or 11. When the SCS is 30 kHz, the number of interlaces may be 5 or 6. The number of interlaces may be the maximum multiplexing number of the terminal device 1 in the frequency domain. The number of interlaces may be the same regardless of the size of the frequency bandwidth. For example, when the SCS is 15 kHz, even if the frequency bandwidth is 20 MHz or 40 MHz, 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 more interlaces.

Figure 16 is a diagram showing an example of a field (PUCCH starting position field, PSP field) indicating the transmission start position of the PUCCH in the time domain (start position of the time domain, start position in a slot) according to this embodiment, and the start position of the PUCCH corresponding to each SCS. Figures 16(a) and (b) show an example of a field (2-bit field, 1-bit field) indicating the transmission start position of the PUCCH. The field is used to provide a gap (period) for the terminal device 1 to perform LBT by adjusting the transmission timing in the time symbol domain. 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 first time symbol domain. 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 first time symbol domain. When the value "01" or "1" is set in the field, it indicates that the transmission can be performed from 25 μs (us) in the first time symbol domain of the PUCCH. For example, in this 25 μsec, the terminal device 1 can perform a 25 μsec LBT only once before transmitting. When the value "10" is set in this field, it indicates that transmission is possible from (25 + TA (Timing Advance)) μsec (us) in the first time symbol area of the PUCCH. When the value "11" is set in this field, it indicates that transmission of the physical channel/physical signal can be performed from the next time symbol area. Also, depending on the value of SCS, the length of one time symbol area 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 this field, it may indicate the first time symbol area 25 μsec or (25 + TA) μsec after the first time symbol area. Figure 16 (c) shows an example of the start position of the PUCCH for each value when the SCS is 15 kHz. Figure 16 (d) shows an example of the start position of the PUCCH for each value when the SCS is 30 kHz.

Next, we will explain the reception procedure for SIB1 (System Information Block Type 1) in this embodiment.

Upon receiving SIB1, the terminal device 1 retains the captured SIB1 and, if the cellAccessRelatedInfo includes an entry with the PLMN-Identity of the selected PLMN (Public Land Mobile Network), in the second half of the procedure, uses the plmn-IdentityList, trackingAreaCode and cellIdentity for the cell received in the corresponding PLMN-IdentityInfo that includes the selected PLMN, and, if in RRC_CONNECTED and timer T311 is not running, may ignore the received frequencyBandList while in RRC_CONNECTED, forward the cellIdentity to one or more higher layers, forward the trackingAreaCode to one or more higher layers, and apply the settings included in servingCellConfigCommon.

Otherwise, if the terminal device 1 supports one or more frequency bands indicated in frequencyBandList, the supported frequency bands are frequency bands (e.g., operating bands) corresponding to the NR-U, and the terminal device 1 supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for the bands supported in the downlink for the NR-U and the bands supported in the uplink, and 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 NR-U, the terminal device 1 may support an initial uplink BWP with a bandwidth equal to or wider than the bandwidth of the initial BWP for the uplink. The supported NR-U uplink channel bandwidth may be applied with a maximum transmission bandwidth included in carrierBandwidth indicated in uplinkConfigCommon for the SCS of the WP, or the supported NR-U downlink channel bandwidth may be applied with a maximum transmission bandwidth included in carrierBandwidth indicated in downlinkConfigCommon for the SCS of the initial downlink BWP that is the same as or wider than the bandwidth of the initial BWP for the downlink, or the first frequency band in frequencyBandList, if any, that supports at least one of one or more additionalSpectrumEmission values in nr-NS-PmaxList (and/or NR-NS-PmaxList) may be selected, or the cellIdentity for the NR-U serving cell may be forwarded to one or more higher layers.

Alternatively, if the terminal device 1 supports one or more frequency bands indicated in frequencyBandList and the supported frequency bands are frequency bands corresponding to the NR-U (e.g., operating bands), then the terminal device 1 may apply the supported NR-U uplink channel bandwidth with a maximum transmission bandwidth included in the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP that is equal to or wider than the bandwidth of the initial BWP for the uplink, or may apply a maximum transmission bandwidth included in the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP that is equal to or wider than the bandwidth of the initial BWP for the downlink. The UE may apply the supported NR-U downlink channel bandwidth together with the maximum transmission bandwidth included in the carrierBandwidth indicated in downlinkConfigCommon for the SCS of the link BWP, may select the first frequency band in frequencyBandList, if any, that supports at least one of one or more additionalSpectrumEmission values in nr-NS-PmaxList (and/or NR-NS-PmaxList), and may forward the cellIdentity for the NR-U serving cell to one or more higher layers.

Here, the values of the uplink channel bandwidth and downlink channel bandwidth (i.e., channel bandwidth) for the NR-U may be a predetermined bandwidth (e.g., 20 MHz), may be a bandwidth value used for measuring the LBT, may be a value determined based on the NR-U settings, may correspond to a frequency domain value used for mapping the physical resources of the NR-U's physical channel and/or physical signal, or may be a channel bandwidth including the range of PRBs given by availableRB-RangesPerCell (valid frequency domain, transmission bandwidth, measurement bandwidth).

Alternatively, the terminal device 1 supports one or more frequency bands indicated in frequencyBandList for the downlink and/or one or more frequency bands indicated in frequencyBandList for the uplink for FDD (i.e., they are not downlink-only bands), supports at least one additionalSpectrumEmission in NR-NS-PmaxList for the supported bands in the downlink and the supported bands for the uplink for FDD, supports the bandwidths of the initial uplink BWP and the initial downlink BWP indicated in the locationAndBandwidth field in uplinkConfigCommon and downlinkConfigCommon, respectively, supports an uplink channel bandwidth with a maximum transmission bandwidth setting that is equal to or wider than the bandwidth of the initial uplink BWP and equal to or narrower than carrierBandwidth, and supports a maximum transmission bandwidth setting that is equal to or narrower than the bandwidth of the initial downlink BWP. or wider and with a maximum transmission bandwidth setting equal to or narrower than carrierBandwidth, the terminal device 1 may apply a supported uplink channel bandwidth equal to or wider than the bandwidth of the initial BWP for the uplink and with a maximum transmission bandwidth included in the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP, or may apply a supported downlink channel bandwidth equal to or wider than the bandwidth of the initial BWP for the downlink and with a maximum transmission bandwidth included in the carrierBandwidth indicated in downlinkConfigCommon for the SCS of the initial downlink BWP, or may select a first frequency band in frequencyBandList that supports at least one of one or more additionalSpectrumEmission values in nr-NS-PmaxList (and/or NR-NS-PmaxList), if any.

The terminal device 1 may forward the cellIdentity to one or more upper layers.

If trackingAreaCode is not provided for the selected PLMN, nor for the registered PLMN or for PLMNs in the same PLMN list, the terminal device 1 may regard the cell as barred. Also, if intraFreqReselection is set to notAllowed, the terminal device 1 may regard cell reselection to other cells at the same frequency as the barred cell as notAllowed. Otherwise, the terminal device 1 may regard cell reselection to other cells at the same frequency as the barred cell as Allowed.

Otherwise, the terminal device 1 may forward the trackingAreaCode to one or more higher layers.

The terminal device 1 may forward the PLMN Identity to one or more higher layers.

In RRC_INACTIVE, if the transferred information does not trigger a message transmission by one or more higher layers and if the serving cell does not belong to the configured ran-NotificationAreaInfo, an RNA (RAN-based Notification Area) update may be initiated.

If present, ims-EmergencySupport may be forwarded to one or more higher layers.

If present, uac-AccessCategory1-SelectionAssistanceInfo may be forwarded to one or more higher layers.

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

The terminal device 1 may apply the specified PCCH settings.

If the terminal device 1 has a stored valid version of the SIB required for the operation of the cell, it may use the retained version of the required SIB.

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

The terminal device 1 may apply the first listed additionalSpectrumEmission that is supported by multiple values included in the NR-NS-PmaxList in the frequencyBandList of uplinkConfigCommon.

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

If supplementaryUplink exists in servingCellConfigCommon, and the terminal device 1 supports one or more frequency bands in the frequencyBandList of the supplementary uplink (SUL), and the terminal device 1 supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for the supported supplementary uplink band, and the terminal device 1 supports the bandwidth of the initial uplink BWP indicated in the locationAndBandwidth field of the supplementary uplink, and the terminal device 1 supports an uplink channel bandwidth with a maximum transmission bandwidth setting that is equal to or narrower than carrierBandwidth and equal to or wider than the bandwidth of the initial uplink BWP of the SUL, the terminal device shall consider the supplementary uplink, or apply the supported uplink channel bandwidth included in carrierBandwidth and with a maximum transmission bandwidth equal to or wider than the bandwidth of the initial uplink BWP of the SUL, or apply the first listed additionalSpectrumEmission supporting one or more values included in NR-NS-PmaxList in the frequencyBandList for supplementaryUplink.

Here, supplementaryUplink may include at least one parameter related to supplementary uplink. In other words, supplementaryUplink may include settings necessary to perform supplementary uplink.

If additionalPmax is present in the same entry of the selected additionalSpectrumEmission in the NR-NS-PmaxList for supplementaryUplink, the terminal device 1 may apply the additionalPmax of supplementaryUplink to SUL, otherwise it may apply the p-Max of supplementaryUplink to SUL.

nr-Unlicensed exists in servingCellConfigCommon, and the terminal device 1 supports one or more frequency bands in the frequencyBandList of NR-unlicensed (NR-U), and the terminal device 1 supports NR-unlicensed If the terminal device 1 supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for the band, and the terminal device 1 supports the bandwidth of the initial BWP indicated in the locationAndBandwidth field of the NR-unlicensed, and the terminal device 1 supports a channel bandwidth with a maximum transmission bandwidth setting equal to or narrower than the carrierBandwidth and equal to or wider than the bandwidth of the initial BWP of the NR-U, the terminal device may regard the NR-unlicensed as configured in the serving cell, may apply the channel bandwidth included in the carrierBandwidth and supported with a maximum transmission bandwidth equal to or wider than the bandwidth of the initial BWP of the NR-U, or may apply the first listed additionalSpectrumEmission supporting one or more values included in the NR-NS-PmaxList in the frequencyBandList for the nr-Unlicensed. Here, the initial BWP of the NR-U may include at least one of the initial uplink BWP and/or the initial downlink BWP.

If the terminal device 1 does not support a channel bandwidth with a maximum transmission bandwidth setting that is equal to or narrower than carrierBandwidth and equal to or wider than the bandwidth of the initial BWP of the NR-U, the terminal device 1 may apply a channel bandwidth with a maximum transmission bandwidth that is equal to the bandwidth of the initial BWP of the NR-U, or may apply the first listed additionalSpectrumEmission that supports one or more values included in the NR-NS-PmaxList in the frequencyBandList for nr-Unlicensed.

Here, nr-Unlicensed may include at least one parameter related to NR-U. In other words, nr-Unlicensed may include the settings necessary to perform NR-U.

If additionalPmax is present in the same entry of the selected additionalSpectrumEmission in the NR-NS-PmaxList for nr-Unlicensed, the terminal device 1 may apply the additionalPmax of nr-Unlicensed to NR-U, otherwise it may apply the p-Max of nr-Unlicensed to NR-U.

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

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

servingCellConfigCommon is an information element (IE) used to configure one or more cell-specific parameters of the serving cell of the terminal device 1. This IE contains one or more parameters for the terminal device 1 to normally acquire the SSB. By including this IE, the network (base station device 3) can provide this information in dedicated signaling when configuring the terminal device 1 with one or more secondary cells or additional cell groups (i.e., SCGs). This IE may be provided to SpCells (MCG and SCG) based on reconfiguration with 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 configure one or more basic parameters of the downlink carrier and transmission.

initialDownlinkBWP may be used to indicate the initial downlink BWP configuration for SpCell and SCell. The network may configure 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 absolute uplink frequency configuration and subcarrier-specific virtual carrier.

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

frequencyBandList may indicate a list of one or more frequency bands to which the NR cell reselection parameters apply.

nr-NS-PmaxList and/or NR-NS-PmaxList may be used to provide a list of additionalPmax and additionalSpectrumEmission, and if the field is not present (or the value is not set), the terminal device may set the value for additionalSpectrumEmission to 0.

locationAndBandwidth indicates the frequency domain location and bandwidth of the BWP. The value of the field may be interpreted as a Resource Indicator Value (RIV). The first PRB (the PRB at the beginning of this BWP) may be the PRB determined by the subcarrierSpacing of this BWP and the offsetToCarrier corresponding to this subcarrier spacing.

Various aspects of the device relating to one aspect of this embodiment are described below.

(1) In order to achieve the above object, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device comprising a receiving unit that receives SIB1 and an upper layer processing unit that applies a channel bandwidth based on receiving the SIB1, and if nr-Unlicensed is present in servingCellConfigCommon, the upper layer processing unit assumes that an NR-U is set in the serving cell, and if a channel bandwidth with a maximum transmission bandwidth setting that is equal to or wider than the bandwidth of the initial BWP of the NR-U and equal to or narrower than carrierBandwidth is supported, the upper layer processing unit applies the channel bandwidth of the supported NR-U with a maximum transmission bandwidth that is equal to or wider than the bandwidth of the initial BWP of the NR-U and included in carrierBandwidth.

(2) A second aspect of the present invention is a method used in a terminal device, comprising the steps of receiving SIB1, applying a channel bandwidth based on receiving the SIB1, determining that an NR-U is configured in the serving cell if nr-Unlicensed is present in servingCellConfigCommon, and, if a channel bandwidth with a maximum transmission bandwidth setting that is the same as or wider than the bandwidth of the initial BWP of the NR-U and equal to or narrower than carrierBandwidth is supported, applying the channel bandwidth of the supported NR-U with a maximum transmission bandwidth that is the same as or wider than the bandwidth of the initial BWP of the NR-U and included within carrierBandwidth.

The base station device 3 and the program operating in the terminal device 1 relating to one aspect of the present invention may be a program that controls a CPU (Central Processing Unit) or the like (a program that causes a computer to function) so as to realize the functions of the above-described embodiment relating to one aspect of the present invention. Information handled by these devices is temporarily stored in a RAM (Random Access Memory) during processing, and is then stored in various ROMs such as a Flash ROM (Read Only Memory) or a HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.

In addition, a part of the terminal device 1 and the base station device 3 in the above-mentioned 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 into a computer system and executed to realize the control function.

The "computer system" referred to here is a computer system built into the terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. Furthermore, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.

Furthermore, "computer-readable recording medium" may also include something that dynamically holds a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or something that holds a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The above program may also be one that realizes part of the functions described above, or one that can realize the functions described above in combination with a program already recorded in the computer system.

The base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. It is sufficient for an device group to have all of the functions or functional blocks of the base station device 3. The terminal device 1 related to the above-described embodiment can also communicate with the base station device as an aggregate.

In addition, the base station device 3 in the above-mentioned embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and/or an NG-RAN (NextGen RAN, NR RAN). In addition, the base station device 3 in the above-mentioned embodiment may have some or all of the functions of an upper node for an eNodeB and/or a gNB.

In addition, some or all of the terminal device 1 and base station device 3 in the above-mentioned embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually chipped, or some or all may be integrated and chipped. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.

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

Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications and the like that do not depart from the gist of the invention are also included. Furthermore, various modifications of one aspect of the present invention are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also included are configurations in which elements described in the above embodiments are substituted for elements that have similar effects.

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

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

Claims (2)

A receiving unit for receiving SIB1;
and an upper layer processing unit for applying a channel bandwidth based on receiving the SIB1;
The upper layer processing unit:
If nr-Unlicensed exists in servingCellConfigCommon, it is assumed that NR-U is set in the serving cell.
If the NR-U supports a channel bandwidth with a maximum transmission bandwidth equal to or greater than the bandwidth of the initial BWP and equal to or less than the carrierBandwidth,
A terminal device that applies the channel bandwidth of a supported NR-U with the maximum transmission bandwidth being the same as or wider than the bandwidth of the initial BWP of the NR-U and included within the carrierBandwidth. receiving an SIB1;
adapting a channel bandwidth based on receiving the SIB1;
If nr-Unlicensed is present in servingCellConfigCommon, it is assumed that NR-U is configured in the serving cell;
If the NR-U supports a channel bandwidth with a maximum transmission bandwidth equal to or wider than the bandwidth of the initial BWP of the NR-U and equal to or narrower than carrierBandwidth, applying the channel bandwidth of the supported NR-U with the maximum transmission bandwidth equal to or wider than the bandwidth of the initial BWP of the NR-U and contained within the carrierBandwidth.

Images