[go: up one dir, main page]

WO2025018400A1 - Dispositif terminal, dispositif de station de base et procédé de communication - Google Patents

Dispositif terminal, dispositif de station de base et procédé de communication Download PDF

Info

Publication number
WO2025018400A1
WO2025018400A1 PCT/JP2024/025843 JP2024025843W WO2025018400A1 WO 2025018400 A1 WO2025018400 A1 WO 2025018400A1 JP 2024025843 W JP2024025843 W JP 2024025843W WO 2025018400 A1 WO2025018400 A1 WO 2025018400A1
Authority
WO
WIPO (PCT)
Prior art keywords
tci state
tci
random access
pusch
terminal device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/025843
Other languages
English (en)
Japanese (ja)
Inventor
崇久 福井
一成 横枕
涼太 森本
晃大 園田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Corp filed Critical Sharp Corp
Publication of WO2025018400A1 publication Critical patent/WO2025018400A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • LTE Long Term Evolution
  • EUTRA Evolved Universal Terrestrial Radio Access
  • 3GPP 3rd Generation Partnership Project
  • a base station device is also called eNodeB (evolved NodeB)
  • UE User Equipment
  • LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cells. A single base station device may manage multiple serving cells.
  • Non-Patent Document 2 Non-Patent Document 3
  • One aspect of the present invention provides a terminal device that communicates efficiently, a communication method used in the terminal device, a base station device that communicates efficiently, and a communication method used in the base station device.
  • a first aspect of the present invention is a terminal device comprising a receiving unit that receives a first PDCCH in which a first DCI is arranged or a PDSCH including an RAR, and a transmitting unit that transmits a PUSCH, and when a unified TCI state is set, a first TCI state and a second TCI state are maintained, and when the PUSCH is scheduled by the first DCI and when the first DCI includes a CRC scrambled by a TC-RNTI, one of the first TCI state and the second TCI state is set for the PUSCH.
  • the PUSCH is scheduled by the first DCI and the first DCI involves a CRC scrambled by at least one of C-RNTI, CS-RNTI, and MCS-C-RNTI, one or both of the first TCI state and the second TCI state are applied to the PUSCH, and if the PUSCH is scheduled by an RAR UL grant in the RAR, one of the first TCI state and the second TCI state are applied to the PUSCH.
  • a second aspect of the present invention is a base station device comprising a transmitter that transmits a first PDCCH in which a first DCI is arranged or a PDSCH including an RAR, and a receiver that receives a PUSCH, and when a unified TCI state is set, a first TCI state and a second TCI state are maintained, and when the PUSCH is scheduled by the first DCI and when the first DCI includes a CRC scrambled by a TC-RNTI, one of the first TCI state and the second TCI state is set to the PUSCH.
  • the PUSCH is scheduled by the first DCI and the first DCI involves a CRC scrambled by at least one of the C-RNTI, CS-RNTI, and MCS-C-RNTI, one or both of the first TCI state and the second TCI state are applied to the PUSCH, and if the PUSCH is scheduled by an RAR UL grant in the RAR, one of the first TCI state and the second TCI state are applied to the PUSCH.
  • a terminal device can communicate efficiently. Also, a base station device can communicate efficiently.
  • FIG. 1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention.
  • 1 is an example showing a relationship between a subcarrier spacing setting ⁇ , the number of OFDM symbols per slot N slot symb , and a cyclic prefix (CP) setting according to an aspect of the present embodiment.
  • FIG. 2 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment.
  • FIG. 30 is a diagram illustrating an example of the configuration of a resource grid 3001 according to one aspect of the present embodiment.
  • 1 is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of the present embodiment.
  • FIG. 1 is a schematic block diagram showing a configuration example of a terminal device 1 according to an aspect of the present embodiment.
  • FIG. 13 is a diagram showing an example of an activation command A according to an aspect of the present embodiment.
  • FIG. 13 is a diagram showing an example of an activation command B according to an aspect of the present embodiment.
  • FIG. 13 is a diagram showing an example of an activation command C according to an aspect of the present embodiment.
  • FIG. 13 is a diagram showing an example of an activation command D according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing an example of an activation command E according to an aspect of the present embodiment.
  • floor(C) may be a floor function for real number C.
  • floor(C) may be a function that outputs the largest integer not exceeding real number C.
  • ceil(D) may be a ceiling function for real number D.
  • ceil(D) may be a function that outputs the smallest integer not below real number D.
  • mod(E,F) may be a function that outputs the remainder when E is divided by F.
  • mod(E,F) may be a function that outputs a value corresponding to the remainder when E is divided by F.
  • exp(G) e ⁇ G.
  • e Napier's constant.
  • H ⁇ I indicates H to the power I.
  • max(J,K) is a function that outputs the maximum value of J and K.
  • At least OFDM Orthogonal Frequency Division Multiplex
  • An OFDM symbol is a time domain unit of OFDM.
  • An OFDM symbol includes at least one or more subcarriers.
  • the OFDM symbol is converted into a time-continuous signal in baseband signal generation.
  • CP-OFDM Cyclic Prefix - Orthogonal Frequency Division Multiplex
  • DFT-s-OFDM Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex
  • the base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting/receiving devices, transmitting/receiving points). When the base station device 3 is configured with multiple transmitting devices, each of the multiple transmitting devices may be located at a different position.
  • the base station device 3 may provide one or more serving cells.
  • a serving cell may be defined as a set of resources used for wireless communication.
  • a serving cell is also referred to as a cell.
  • one resource grid may be provided for each component carrier.
  • one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration ⁇ .
  • the subcarrier spacing configuration ⁇ is also referred to as numerology.
  • one resource grid may be provided for a set of a certain antenna port p, a certain subcarrier spacing configuration ⁇ , and a certain transmission direction x.
  • the resource grid includes N size, ⁇ grid,x N RB sc subcarriers, where the resource grid starts from a common resource block N start, ⁇ grid , x , which is also referred to as the reference point of the resource grid.
  • the resource grid includes N subframes, ⁇ symb OFDM symbols.
  • the subscript x that is added to the resource grid related parameters indicates the transmission direction.
  • the subscript x may be used to indicate either the downlink or the uplink.
  • N size, ⁇ grid, x is an offset setting indicated by a parameter provided by the RRC layer (e.g., the parameter CarrierBandwidth).
  • N start, ⁇ grid, x is a band setting indicated by a parameter provided by the RRC layer (e.g., the parameter OffsetToCarrier).
  • the offset setting and band setting are settings used to configure an SCS-specific carrier.
  • FIG. 2 is an example showing the relationship between the subcarrier spacing setting ⁇ , the number of OFDM symbols per slot N slot symb , and the CP (cyclic prefix) setting according to one embodiment of the present invention.
  • N slot symb 14
  • a time unit Tc may be used to express a length in the time domain.
  • ⁇ f max 480 kHz.
  • N f 4096.
  • ⁇ f ref is 15 kHz.
  • N f,ref is 2048.
  • a radio frame is made up of 10 subframes.
  • An OFDM symbol is a unit of time domain for one communication method.
  • an OFDM symbol may be a unit of time domain for CP-OFDM.
  • an OFDM symbol may be a unit of time domain for DFT-s-OFDM.
  • a slot may be configured to include a plurality of OFDM symbols.
  • one slot may be configured by consecutive N slot symb OFDM symbols.
  • the number and index of slots included in a subframe may be given.
  • slot index n ⁇ s may be given in ascending order as integer values in the range from 0 to N subframe, ⁇ slot ⁇ 1 in the subframe.
  • the number and index of slots included in a radio frame may be given.
  • slot index n ⁇ s,f may be given in ascending order as integer values in the range from 0 to N frame, ⁇ slot ⁇ 1 in the radio frame.
  • Fig. 3 is a diagram showing an example of a method for configuring a resource grid according to one aspect of this embodiment.
  • the horizontal axis in Fig. 3 indicates the frequency domain.
  • Fig. 3 shows a configuration example of a resource grid with a subcarrier spacing of ⁇ 1 in a component carrier 300, and a configuration example of a resource grid with a subcarrier spacing of ⁇ 2 in the certain component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier.
  • ⁇ 1 ⁇ 2 - 1
  • the component carrier 300 is a band having a predetermined width in the frequency domain.
  • a point 3000 is an identifier for identifying a certain subcarrier.
  • the point 3000 is also called point A.
  • a common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier spacing setting ⁇ 1 .
  • the common resource block that includes point 3000 (the black block in the common resource block set 3100 in FIG. 3) is also referred to as the reference point of the common resource block set 3100.
  • the reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.
  • the offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001.
  • the offset 3011 is indicated by the number of common resource blocks for the subcarrier spacing setting ⁇ 1.
  • the resource grid 3001 includes N size, ⁇ grid 1, x common resource blocks starting from the reference point of the resource grid 3001.
  • Offset 3013 is the offset from the reference point of resource grid 3001 to the reference point (N start , ⁇ BWP, i1 ) of BWP (BandWidth Part) 3003 of index i1.
  • Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting ⁇ 2 .
  • the common resource block that includes point 3000 (the black block in the common resource block set 3200 in FIG. 3) is also referred to as the reference point of the common resource block set 3200.
  • the reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.
  • the offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002.
  • the offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing ⁇ 2.
  • the resource grid 3002 includes N size, ⁇ grid 2, x common resource blocks starting from the reference point of the resource grid 3002.
  • Offset 3014 is the offset from the reference point of resource grid 3002 to the reference point (Nstart , ⁇ BWP ,i2 ) of BWP 3004 with index i2.
  • Fig. 4 is a diagram showing a configuration example of a resource grid 3001 according to one aspect of the present embodiment.
  • the horizontal axis is the OFDM symbol index l sym
  • the vertical axis is the subcarrier index k sc .
  • the resource grid 3001 includes N size, ⁇ grid 1, ⁇ N RB sc subcarriers and N subframe, ⁇ symb OFDM symbols.
  • a resource specified by the subcarrier index k sc and the OFDM symbol index l sym is also called a resource element (RE).
  • RE resource element
  • a resource block (RB) includes N RB sc consecutive subcarriers.
  • a resource block unit is a set of resources that corresponds to one OFDM symbol in one resource block. That is, one resource block unit contains 12 resource elements that correspond to one OFDM symbol in one resource block.
  • the common resource blocks for a given subcarrier spacing setting ⁇ are indexed in a given common resource block set in the frequency domain in ascending order starting from 0.
  • the common resource block with index 0 for a given subcarrier spacing setting ⁇ contains (or collides with, or coincides with) point 3000.
  • the physical resource blocks for a given subcarrier spacing setting ⁇ are indexed in the frequency domain in ascending order starting from 0 in a given BWP.
  • a BWP is defined as a subset of common resource blocks included in a resource grid.
  • a BWP includes N size , ⁇ BWP,i common resource blocks starting from a reference point N start , ⁇ BWP,i of the BWP.
  • a BWP configured for a downlink carrier is also called a downlink BWP.
  • a BWP configured for an uplink component carrier is also called an uplink BWP.
  • An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed.
  • the channel may correspond to a physical channel.
  • the symbol may correspond to an OFDM symbol.
  • the symbol may correspond to a resource block unit.
  • the symbol may correspond to a resource element.
  • the two antenna ports are said to be 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 delay spread, Doppler spread, Doppler shift, average gain, average delay, and some or all of the spatial Rx parameters.
  • the first antenna port and the second antenna port being QCL with respect to the beam parameters may mean that the receiving beam assumed by the receiver for the first antenna port and the receiving beam assumed by the receiver for the second antenna port are identical (or correspond).
  • the first antenna port and the second antenna port being QCLs in terms of 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 (or correspond to each other).
  • the terminal device 1 may assume that the two antenna ports are QCLs if the large-scale characteristics of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port.
  • the two antenna ports being QCLs may mean that the two antenna ports are assumed to be QCLs.
  • the large-scale characteristics may be referred to as QCL parameters.
  • the QCL type may be any of typeA, typeB, typeC, and typeD.
  • the two antenna ports being type D QCLs may mean that a fourth large-scale characteristic of a channel in which a symbol is transmitted at one antenna port can be estimated from a channel in which a symbol is transmitted at the other antenna port.
  • the first large-scale characteristic may include all of Doppler shift, Doppler spread, average delay, and delay spread.
  • the second large-scale characteristic may include all of Doppler shift and Doppler spread.
  • the third large-scale characteristic may include all of the Doppler shift and the average delay.
  • the fourth large-scale characteristic may include spatial reception parameters (spatial direction information, beam information).
  • the antenna port for the DMRS may be a DMRS port.
  • the antenna port for the PTRS may be a PTRS port.
  • the antenna port associated with the PTRS may be a PTRS port.
  • the antenna port for the SRS may be an SRS port.
  • the antenna port for the DMRS may be a DMRS port.
  • the antenna port associated with the DMRS may be a DMRS port.
  • Carrier aggregation may be performing communication using multiple aggregated serving cells. Also, carrier aggregation may be performing communication using multiple aggregated component carriers. Also, carrier aggregation may be performing communication using multiple aggregated downlink component carriers. Also, carrier aggregation may be performing communication using multiple aggregated uplink component carriers.
  • FIG. 5 is a schematic block diagram showing an example configuration of a base station device 3 according to one aspect of this embodiment.
  • the base station device 3 includes at least a radio transceiver unit (physical layer processing unit) 30 and/or part or all of a higher layer processing unit 34.
  • the radio transceiver unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and part or all of a baseband unit 33.
  • the higher layer processing unit 34 includes at least a medium access control layer processing unit 35, and part or all of a radio resource control (RRC: Radio Resource Control) layer processing unit 36.
  • RRC Radio Resource Control
  • the wireless transceiver unit 30 includes at least a wireless transmitter unit 30a and part or all of a wireless receiver unit 30b.
  • the device configurations of the baseband unit included in the wireless transmitter unit 30a and the baseband unit included in the wireless receiver unit 30b may be the same or different.
  • the device configurations of the RF unit included in the wireless transmitter unit 30a and the RF unit included in the wireless receiver unit 30b may be the same or different.
  • the device configurations of the antenna unit included in the wireless transmitter unit 30a and the antenna unit included in the wireless receiver unit 30b may be the same or different.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a PDSCH.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a PDCCH.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a PBCH.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a synchronization signal.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a PDSCH DMRS.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a PDCCH DMRS.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a CSI-RS.
  • the wireless transmission unit 30a may generate and transmit a baseband signal of a DL PTRS.
  • the wireless receiving unit 30b may receive a PRACH.
  • the wireless receiving unit 30b may receive and demodulate a PUCCH.
  • the wireless receiving unit 30b may receive and demodulate a PUSCH.
  • the wireless receiving unit 30b may receive a PUCCH DMRS.
  • the wireless receiving unit 30b may receive a PUSCH DMRS.
  • the wireless receiving unit 30b may receive a UL PTRS.
  • the wireless receiving unit 30b may receive an SRS.
  • the upper layer processing unit 34 outputs downlink data (transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a).
  • the upper layer processing unit 34 processes the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.
  • MAC Medium Access Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • RRC Radio Link Control
  • the media access control layer processing unit 35 provided in the upper layer processing unit 34 performs MAC layer processing.
  • the radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs RRC layer processing.
  • the radio resource control layer processing unit 36 manages various setting information/parameters (RRC parameters) of the terminal device 1.
  • RRC parameters setting information/parameters
  • the radio resource control layer processing unit 36 sets parameters based on the RRC message received from the terminal device 1.
  • the wireless transceiver unit 30 (or the wireless transmitter unit 30a) performs processes such as modulation and encoding.
  • the wireless transceiver unit 30 (or the wireless transmitter unit 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) the downlink data, and transmits it to the terminal device 1.
  • the wireless transceiver unit 30 (or the wireless transmitter unit 30a) may place the physical signal on a certain component carrier and transmit it to the terminal device 1.
  • the wireless transceiver unit 30 (or the wireless receiver unit 30b) performs processes such as demodulation and decoding.
  • the wireless transceiver unit 30 (or the wireless receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34.
  • the wireless transceiver unit 30 (or the wireless receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.
  • the RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal by orthogonal demodulation (down-converts) and removes unnecessary frequency components.
  • the RF unit 32 outputs the processed analog signal to the baseband unit.
  • the baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal.
  • the baseband unit 33 removes the portion corresponding to the CP (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract the signal in the frequency domain.
  • FFT Fast Fourier Transform
  • the baseband unit 33 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.
  • IFFT inverse fast Fourier transform
  • the RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, upconverts the analog signal to a carrier frequency, and transmits it via the antenna unit 31.
  • the RF unit 32 may also have a function for controlling transmission power.
  • the RF unit 32 is also referred to as a transmission power control unit.
  • One or more serving cells may be configured for the terminal device 1.
  • Each of the serving cells configured for the terminal device 1 may be any of a PCell (Primary cell), a PSCell (Primary SCG cell), and a SCell (Secondary Cell).
  • PCell Primary cell
  • PSCell Primary SCG cell
  • SCell Secondary Cell
  • the PCell is a serving cell included in the MCG (Master Cell Group).
  • the PCell is the cell on which the initial connection establishment procedure or the connection re-establishment procedure is performed by the terminal device 1 (the cell on which the procedure has been performed).
  • the PSCell is a serving cell included in the SCG (Secondary Cell Group).
  • the PSCell is a serving cell to which random access is performed by the terminal device 1.
  • the SCell may be included in either the MCG or the SCG.
  • serving cell group includes at least the MCG and the SCG.
  • the serving cell group may include one or more serving cells (or component carriers).
  • the one or more serving cells (or component carriers) included in the serving cell group may be operated by carrier aggregation.
  • One or more downlink BWPs may be configured for each serving cell (or downlink component carrier).
  • One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).
  • one downlink BWP may be set as an active downlink BWP (or one downlink BWP may be activated).
  • one uplink BWP may be set as an active uplink BWP (or one uplink BWP may be activated).
  • the PDSCH, PDCCH, and CSI-RS may be received in an active downlink BWP.
  • the terminal device 1 may attempt to receive the PDSCH, PDCCH, and CSI-RS in an active downlink BWP.
  • the PUCCH and PUSCH may be transmitted in an active uplink BWP.
  • the terminal device 1 may transmit the PUCCH and PUSCH in an active uplink BWP.
  • the active downlink BWP and the active uplink BWP are also collectively referred to as the active BWP.
  • the PDSCH, PDCCH, and CSI-RS may not be received in a downlink BWP other than an active downlink BWP (an inactive downlink BWP).
  • the terminal device 1 may not attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP.
  • the PUCCH and PUSCH may not be transmitted in an uplink BWP that is not an active uplink BWP (an inactive uplink BWP).
  • the terminal device 1 may not transmit the PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP.
  • the inactive downlink BWP and the inactive uplink BWP are collectively referred to as the inactive BWP.
  • Downlink BWP switch is a procedure for deactivating one active downlink BWP of a serving cell and activating one of the inactive downlink BWPs of the serving cell.
  • Downlink BWP switch may be controlled by a BWP field included in downlink control information.
  • Downlink BWP switch may be controlled based on higher layer parameters.
  • Uplink BWP switching is used to deactivate one active uplink BWP and activate one of the inactive uplink BWPs that is not the one active uplink BWP.
  • Uplink BWP switching may be controlled by a BWP field included in downlink control information. Uplink BWP switching may be controlled based on higher layer parameters.
  • two or more downlink BWPs may not be configured as active downlink BWPs.
  • one downlink BWP may be active at a given time.
  • uplink BWPs configured for a serving cell
  • two or more uplink BWPs may not be configured as active uplink BWPs.
  • one uplink BWP may be active at a given time.
  • FIG. 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of this embodiment.
  • the terminal device 1 includes at least a radio transceiver unit (physical layer processing unit) 10 and one or all of an upper layer processing unit 14.
  • the radio transceiver unit 10 includes at least an antenna unit 11, an RF unit 12, and some 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 some or all of a radio resource control layer processing unit 16.
  • the wireless transceiver unit 10 includes at least a wireless transmitter unit 10a and part or all of a wireless receiver unit 10b.
  • the device configurations of the baseband unit 13 included in the wireless transmitter unit 10a and the baseband unit 13 included in the wireless receiver unit 10b may be the same or different.
  • the device configurations of the RF unit 12 included in the wireless transmitter unit 10a and the RF unit 12 included in the wireless receiver unit 10b may be the same or different.
  • the device configurations of the antenna unit 11 included in the wireless transmitter unit 10a and the antenna unit 11 included in the wireless receiver unit 10b may be the same or different.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of PRACH.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of PUCCH.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of PUSCH.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of PUCCH DMRS.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of PUSCH DMRS.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of UL PTRS.
  • the wireless transmission unit 10a may generate and transmit a baseband signal of SRS.
  • the wireless receiving unit 10b may receive and demodulate a PDSCH.
  • the wireless receiving unit 10b may receive and demodulate a PDCCH.
  • the wireless receiving unit 10b may receive and demodulate a PBCH.
  • the wireless receiving unit 10b may receive a synchronization signal.
  • the wireless receiving unit 10b may receive a PDSCH DMRS.
  • the wireless receiving unit 10b may receive a PDCCH DMRS.
  • the wireless receiving unit 10b may receive a CSI-RS.
  • the wireless receiving unit 10b may receive a DL PTRS.
  • the upper layer processing unit 14 outputs the uplink data (transport block) to the wireless transceiver unit 10 (or the wireless transmitter unit 10a).
  • the upper layer processing unit 14 processes the MAC layer, the packet data integration protocol layer, the radio link control layer, and the RRC layer.
  • the media access control layer processing unit 15 provided in the upper layer processing unit 14 performs MAC layer processing.
  • 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 (RRC parameters) of the terminal device 1.
  • the radio resource control layer processing unit 16 sets the RRC parameters based on the RRC message received from the base station device 3.
  • the wireless transceiver unit 10 (or wireless transmitter unit 10a) performs processes such as modulation and encoding.
  • the wireless transceiver unit 10 (or wireless transmitter unit 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits it to the base station device 3.
  • the wireless transceiver unit 10 (or wireless transmitter unit 10a) may place the physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.
  • the wireless transceiver unit 10 (or wireless receiver unit 10b) performs processes such as demodulation and decoding.
  • the wireless transceiver unit 10 (or wireless receiver unit 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell.
  • the wireless transceiver unit 10 (or wireless receiver unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14.
  • the wireless transceiver unit 10 (wireless receiver unit 10b) may perform a channel access procedure prior to transmitting the physical signal.
  • the RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation (down-converts) and removes unnecessary frequency components.
  • the RF unit 12 outputs the processed analog signal to the baseband unit 13.
  • 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 (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract the signal in the frequency domain.
  • FFT Fast Fourier Transform
  • the baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink 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.
  • IFFT inverse fast Fourier transform
  • the RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, upconverts the analog signal to a carrier frequency, and transmits it via the antenna unit 11.
  • the RF unit 12 may also have a function for controlling transmission power.
  • the RF unit 12 is also referred to as a transmission power control unit.
  • the physical signal is a general term for the downlink physical channel, the downlink physical signal, the uplink physical channel, and the uplink physical channel.
  • the physical channel is a general term for the downlink physical channel and the uplink physical channel.
  • the physical signal is a general term for the downlink physical signal and the uplink physical signal.
  • the physical signal may be referred to as a reference signal.
  • the uplink physical channel may correspond to a set of resource elements that convey information generated in a higher layer.
  • the uplink physical channel may be a physical channel used in an uplink component carrier.
  • the uplink physical channel may be transmitted by a terminal device 1.
  • the uplink physical channel may be received by a base station device 3.
  • at least some or all of the following uplink physical channels may be 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 PUCCH may be transmitted to deliver, transmit, or convey the uplink control information.
  • the uplink control information may be mapped to the PUCCH.
  • the terminal device 1 may transmit a PUCCH in which the uplink control information is mapped.
  • the base station device 3 may receive a PUCCH in which the uplink control information is mapped.
  • the uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes at least some or all of the channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) information.
  • CSI Channel State Information
  • SR Scheduling Request
  • HARQ-ACK Hybrid Automatic Repeat request ACKnowledgement
  • the channel state information is also called a channel state information bit or a channel state information sequence.
  • the scheduling request is also called a scheduling request bit or a scheduling request sequence.
  • the HARQ-ACK information is also called a HARQ-ACK information bit or a HARQ-ACK information sequence.
  • the HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB).
  • the HARQ-ACK may indicate an acknowledgement (ACK) or a negative-acknowledgement (NACK) corresponding to the transport block.
  • the ACK may indicate that the decoding of the transport block has been successfully completed.
  • the NACK may indicate that the decoding of the transport block has not been successfully completed.
  • the HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.
  • a transport block is a sequence of information bits delivered from a higher layer.
  • the sequence of information bits is also called a bit sequence.
  • the transport block may be delivered from the UL-SCH (UpLink-Shared CHannel) of the transport layer.
  • the HARQ-ACK for a transport block may be referred to as the HARQ-ACK for a PDSCH.
  • HARQ-ACK for a PDSCH refers to the HARQ-ACK for the transport block included in the PDSCH.
  • HARQ-ACK may indicate an ACK or NACK corresponding to one CBG (Code Block Group) contained in a transport block.
  • CBG Code Block Group
  • the scheduling request may be used at least to request UL-SCH resources for the initial transmission.
  • the scheduling request bit may be used to indicate either a positive SR or a negative SR.
  • the scheduling request bit indicating a positive SR is also referred to as "a positive SR is transmitted".
  • a positive SR may indicate that UL-SCH resources for the initial transmission are requested by the terminal device 1.
  • a positive SR may indicate that a scheduling request is triggered by an upper layer.
  • a positive SR may be transmitted when a scheduling request is indicated by an upper layer.
  • the scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted”.
  • a negative SR may indicate that UL-SCH resources for the initial transmission are not requested by the terminal device 1.
  • a negative SR may indicate that a scheduling request is not triggered by an upper layer.
  • a negative SR may be transmitted when a scheduling request is not indicated by an upper layer.
  • the channel state information may include at least some or all of a Channel Quality Indicator (CQI), a Precoder Matrix Indicator (PMI), and a Rank Indicator (RI).
  • CQI is an indicator related to the quality of the propagation path (e.g., propagation strength) or the quality of the physical channel
  • PMI is an indicator related to the precoder
  • RI is an indicator related to the transmission rank (or the number of transmission layers).
  • the channel state information is an indicator regarding the reception state of at least a physical signal (e.g., CSI-RS) used for channel measurement.
  • the value of the channel state information may be determined by the terminal device 1 based on the reception state assumed by at least a physical signal used for channel measurement.
  • the channel measurement may include interference measurement.
  • the PUCCH may correspond to a PUCCH format.
  • the PUCCH may be a set of resource elements used to convey the PUCCH format.
  • the PUCCH may include a PUCCH format.
  • the PUCCH may be transmitted with a certain PUCCH format.
  • the PUCCH format may be interpreted as a format of information.
  • the PUCCH format may be interpreted as a set of information set to a certain information format.
  • PUSCH may be used to transmit one or both of a transport block and uplink control information.
  • the transport block may be placed in the PUSCH.
  • the transport block delivered by the UL-SCH may be placed in the PUSCH.
  • the uplink control information may be placed in the PUSCH.
  • the terminal device 1 may transmit a PUSCH in which a transport block and one or both of the uplink control information are placed.
  • the base station device 3 may receive a PUSCH in which a transport block and one or both of the uplink control information are placed.
  • the PRACH may be transmitted to convey a random access preamble.
  • the terminal device 1 may transmit the PRACH.
  • the base station device 3 may receive the PRACH.
  • xu is a ZC (Zadoff Chu) sequence.
  • j is an imaginary unit.
  • ⁇ is the ratio of a circumference to a circumference of a circle.
  • Cv corresponds to a cyclic shift of the PRACH sequence.
  • LRA corresponds to the length of the PRACH sequence.
  • LRA is 839 or 139.
  • i is an integer ranging from 0 to LRA -1.
  • u is a sequence index for the PRACH sequence.
  • the random access preambles are defined for each PRACH opportunity.
  • the random access preambles are identified based on the cyclic shift C v of the PRACH sequence and the sequence index u for the PRACH sequence.
  • An index may be assigned to each of the 64 identified random access preambles.
  • the uplink physical signal may correspond to a set of resource elements.
  • the uplink physical signal may not be used to transmit information generated in a higher layer.
  • the uplink physical signal may be used to transmit information generated in a physical layer.
  • the uplink physical signal may be a physical signal used in an uplink component carrier.
  • the terminal device 1 may transmit the uplink physical signal.
  • the base station device 3 may receive the uplink physical signal.
  • at least some or all of the following uplink physical signals may be used.
  • ⁇ UL DMRS UpLink Demodulation Reference Signal
  • SRS Sounding Reference Signal
  • UL PTRS UpLink Phase Tracking Reference Signal
  • UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.
  • the set of antenna ports for the DMRS for the PUSCH may be given based on the set of antenna ports for the PUSCH.
  • the set of antenna ports for the DMRS for the PUSCH may be the same as the set of antenna ports for the PUSCH.
  • the transmission of the PUSCH and the transmission of the DMRS for the PUSCH may be indicated (or scheduled) by one DCI format.
  • the PUSCH and the DMRS for the PUSCH may be collectively referred to as the PUSCH.
  • Transmitting the PUSCH may be transmitting the PUSCH and the DMRS for the PUSCH.
  • the propagation path of the PUSCH may be estimated from the DMRS for that PUSCH.
  • the set of antenna ports for DMRS for PUCCH may be the same as the set of antenna ports for PUCCH.
  • the transmission of a PUCCH and the transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format.
  • One or both of the mapping of the PUCCH to resource elements and the mapping of the DMRS for the PUCCH to resource elements may be provided by one PUCCH format.
  • the propagation path of the PUCCH may be estimated from the DMRS for that PUCCH.
  • the downlink physical channel may correspond to a set of resource elements that convey information generated in a higher layer.
  • the downlink physical channel may be a physical channel used in a downlink component carrier.
  • the base station device 3 may transmit the downlink physical channel.
  • the terminal device 1 may receive the downlink physical channel.
  • at least some or all of the following downlink physical channels may be used.
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • the PBCH may be transmitted to convey one or both of the MIB (Master Information Block) and physical layer control information.
  • the physical layer control information is information generated in the physical layer.
  • the MIB is a set of parameters placed on a BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer.
  • the BCCH is placed on a BCH, which is a channel of the transport layer.
  • the BCH may be placed (mapped) on the PBCH.
  • the terminal device 1 may receive a PBCH in which the MIB and one or both of the physical layer control information are placed.
  • the base station device 3 may transmit a PBCH in which the MIB and one or both of the physical layer control information are placed.
  • the physical layer control information may be configured with 8 bits.
  • the physical layer control information may include at least some or all of the following 0A to 0D.
  • the radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame that includes the slot in which the PBCH is transmitted).
  • the radio frame bits include 4 bits.
  • the radio frame bits may be composed of 4 bits of a 10-bit radio frame indicator.
  • the radio frame indicator may be used at least to identify radio frames from index 0 to index 1023.
  • the half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of the radio frame in which the PBCH is transmitted.
  • the half radio frame may be configured to include five subframes.
  • the half radio frame may be configured to include the first five subframes of the ten subframes included in the radio frame.
  • the half radio frame may be configured to include the last five subframes of the ten subframes included in the radio frame.
  • the SS/PBCH block index bits are used to indicate the SS/PBCH block index.
  • the SS/PBCH block index bits include 3 bits.
  • the SS/PBCH block index bits may be composed of 3 bits of a 6-bit SS/PBCH block index indicator.
  • the SS/PBCH block index indicator may be used at least to identify SS/PBCH blocks from index 0 to index 63.
  • the subcarrier offset bit is used to indicate a subcarrier offset.
  • the subcarrier offset may be used to indicate the difference between the first subcarrier onto which the PBCH is mapped and the first subcarrier onto which the control resource set with index 0 is mapped.
  • the PDCCH may be transmitted to transmit downlink control information (DCI).
  • DCI downlink control information
  • the downlink control information may be placed in the PDCCH.
  • the terminal device 1 may receive the PDCCH in which the downlink control information is placed.
  • the base station device 3 may transmit the PDCCH in which the downlink control information is placed.
  • the downlink control information may be transmitted with a DCI format.
  • the DCI format may be interpreted as a format of the downlink control information.
  • the DCI format may also be interpreted as a set of downlink control information set to a certain downlink control information format.
  • DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats.
  • the uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1.
  • the downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.
  • DCI format 0_0 is used at least for scheduling a PUSCH arranged in a certain cell.
  • DCI format 0_0 includes at least some or all of fields 1A to 1E.
  • the DCI format specification field may indicate whether the DCI format including the DCI format specification field is an uplink DCI format or a downlink DCI format. In other words, the DCI format specification field may be included in both the uplink DCI format and the downlink DCI format.
  • the DCI format specification field included in DCI format 0_0 may indicate 0.
  • the frequency domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of frequency resources for the PUSCH.
  • the time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for the PUSCH.
  • the frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.
  • the MCS field included in DCI format 0_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PUSCH.
  • the target coding rate may be a target coding rate for a transport block placed in the PUSCH.
  • the size of the transport block (TBS: Transport Block Size) placed in the PUSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PUSCH.
  • DCI format 0_0 does not have to include fields used for CSI requests.
  • DCI format 0_0 may not include a carrier indicator field.
  • the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is placed belongs may be the same as the serving cell of the uplink component carrier on which the PDCCH including the DCI format 0_0 is placed.
  • the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is to be placed on the uplink component carrier of the serving cell.
  • DCI format 0_0 may not include a BWP field (BWP indication field).
  • DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing the active uplink BWP.
  • the terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP.
  • DCI format 0_1 is used at least for scheduling a PUSCH allocated to a certain cell.
  • DCI format 0_1 includes at least a part or all of fields 2A to 2H.
  • the DCI format specific field included in DCI format 0_1 may indicate 0.
  • the frequency domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of frequency resources for the PUSCH.
  • the time domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of time resources for the PUSCH.
  • the MCS field included in DCI format 0_1 may be used to indicate at least some or all of the modulation scheme and/or target coding rate for the PUSCH.
  • the BWP field of DCI format 0_1 may be used to indicate the uplink BWP in which the PUSCH scheduled by the DCI format 0_1 is placed.
  • DCI format 0_1 may involve a change in the active uplink BWP.
  • the terminal device 1 may recognize the uplink BWP in which the PUSCH is placed based on detecting DCI format 0_1 used for scheduling the PUSCH.
  • the DCI format 0_1 that does not include a BWP field may be a DCI format that schedules a PUSCH without changing the active uplink BWP.
  • the terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting DCI format D0_1 that is DCI format 0_1 used for scheduling a PUSCH and does not include a BWP field.
  • the BWP field may be ignored by the terminal device 1.
  • a terminal device 1 that does not support the BWP switching function may recognize that the PUSCH is transmitted without switching the active uplink BWP based on detecting DCI format 0_1 that is used for PUSCH scheduling and includes a BWP field.
  • the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.
  • the CSI request field is used to indicate a CSI report.
  • DCI format 0_1 includes a carrier indicator field
  • the carrier indicator field may be used to indicate the uplink component carrier on which the PUSCH is arranged. If DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is arranged may be the same as the uplink component carrier on which the PDCCH including the DCI format 0_1 used for scheduling the PUSCH is arranged.
  • the number of bits of the carrier indicator field included in DCI format 0_1 used for scheduling the PUSCH arranged in the serving cell group may be one bit or more (e.g., three bits).
  • the number of bits of the carrier indicator field included in the DCI format 0_1 used for scheduling the PUSCH placed in the certain serving cell group may be 0 bits (or the carrier indicator field may not be included in the DCI format 0_1 used for scheduling the PUSCH placed in the certain serving cell group).
  • DCI format 1_0 is used at least for scheduling a PDSCH arranged in a certain cell.
  • DCI format 1_0 includes at least a part or all of 3A to 3F.
  • the DCI format specific field included in DCI format 1_0 may indicate 1.
  • the frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of frequency resources for the PDSCH.
  • the time domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of time resources for the PDSCH.
  • the MCS field included in DCI format 1_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PDSCH.
  • the target coding rate may be a target coding rate for a transport block placed in the PDSCH.
  • the size of the transport block (TBS: Transport Block Size) placed in the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.
  • the PDSCH_HARQ feedback timing indication field may be used to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.
  • the PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.
  • a PUCCH resource set may include one or more PUCCH resources.
  • DCI format 1_0 may not include a carrier indicator field.
  • the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_0 is arranged.
  • the terminal device 1 may recognize that the PDSCH scheduled by the DCI format 1_0 is to be arranged on the downlink component carrier.
  • DCI format 1_0 may not include a BWP field.
  • DCI format 1_0 may be a DCI format that schedules a PDSCH without changing the active downlink BWP. Based on detecting DCI format 1_0 used for scheduling a PDSCH, the terminal device 1 may recognize that the PDSCH will be received without switching the active downlink BWP.
  • DCI format 1_1 is used at least for scheduling a PDSCH arranged in a certain cell.
  • DCI format 1_1 includes at least some or all of 4A to 4I.
  • the DCI format specific field contained in DCI format 1_1 may indicate 1.
  • the frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of frequency resources for the PDSCH.
  • the time domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of time resources for the PDSCH.
  • the MCS field included in DCI format 1_1 may be used to indicate at least one or both of the modulation scheme and the target coding rate for the PDSCH.
  • DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field
  • the PDSCH_HARQ feedback timing indication field may be used at least to indicate an offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be specified by a higher layer parameter.
  • the PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.
  • the BWP field of DCI format 1_1 may be used to indicate the downlink BWP in which the PDSCH scheduled by the DCI format 1_1 is placed.
  • DCI format 1_1 may involve a change in the active downlink BWP.
  • the terminal device 1 may recognize the downlink BWP in which the PUSCH is placed based on detecting DCI format 1_1 used for scheduling the PDSCH.
  • the DCI format 1_1 that does not include a BWP field may be a DCI format that schedules a PDSCH without changing the active downlink BWP.
  • the terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting the DCI format 1_1 that is used for scheduling a PDSCH and does not include a BWP field.
  • DCI format 1_1 includes a BWP field but terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by terminal device 1.
  • a terminal device 1 that does not support the BWP switching function may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for PDSCH scheduling and includes a BWP field.
  • terminal device 1 supports the BWP switching function, it may report that "terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.
  • DCI format 1_1 includes a carrier indicator field
  • the carrier indicator field may be used to indicate the downlink component carrier on which the PDSCH is arranged. If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_1 used for scheduling the PDSCH is arranged. If the number of downlink component carriers configured in the terminal device 1 in a serving cell group is two or more (if downlink carrier aggregation is operated in a serving cell group), the number of bits of the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH arranged in the serving cell group may be one bit or more (e.g., three bits).
  • the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group).
  • the PDSCH may be transmitted to transmit a transport block.
  • the PDSCH may be used to transmit a transport block delivered by the DL-SCH.
  • the PDSCH may be used to transmit a transport block.
  • the transport block may be placed in the PDSCH.
  • the transport block corresponding to the DL-SCH may be placed in the PDSCH.
  • the base station device 3 may transmit the PDSCH.
  • the terminal device 1 may receive the PDSCH.
  • the downlink physical signal may correspond to a set of resource elements.
  • the downlink physical signal may not carry information generated in a higher layer.
  • the downlink physical signal may be a physical signal used in a downlink component carrier.
  • the downlink physical signal may be transmitted by a base station device 3.
  • the downlink physical signal may be transmitted by a terminal device 1.
  • at least some or all of the following downlink physical signals may be used.
  • SS Synchronization signal
  • DL DMRS DownLink DeModulation Reference Signal
  • CSI-RS Channel State Information-Reference Signal
  • DL PTRS DownLink Phase Tracking Reference Signal
  • the synchronization signal may be used by the terminal device 1 to synchronize one or both of the frequency domain and the time domain of the downlink.
  • the synchronization signal is a general term for the PSS (Primary Synchronization Signal) and the SSS (Secondary Synchronization Signal).
  • Fig. 7 is a diagram showing an example of the configuration of an SS/PBCH block according to one embodiment of the present invention.
  • the horizontal axis indicates the time axis (OFDM symbol index lsym ), and the vertical axis indicates the frequency domain.
  • Block 700 indicates a set of resource elements for PSS.
  • Block 720 indicates a set of resource elements for SSS.
  • Four blocks (blocks 710, 711, 712, and 713) indicate sets of resource elements for PBCH and DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).
  • the SS/PBCH block includes a PSS, SSS, and PBCH.
  • the SS/PBCH block also includes four consecutive OFDM symbols.
  • the SS/PBCH block includes 240 subcarriers.
  • the PSS is placed in the 57th to 183rd subcarriers of the first OFDM symbol.
  • the SSS is placed in the 57th to 183rd subcarriers of the third OFDM symbol.
  • the 1st to 56th subcarriers of the first OFDM symbol may be set to zero.
  • the 184th to 240th subcarriers of the first OFDM symbol may be set to zero.
  • the 49th to 56th subcarriers of the third OFDM symbol may be set to zero.
  • the 184th to 192nd subcarriers of the third OFDM symbol may be set to zero.
  • the PBCH is placed in the 1st to 240th subcarriers of the second OFDM symbol, which are subcarriers in which the DMRS for the PBCH is not placed.
  • the PBCH is placed in the 1st to 48th subcarriers of the third OFDM symbol, and in subcarriers where DMRS for the PBCH is not placed.
  • the PBCH is placed in the 193rd to 240th subcarriers of the third OFDM symbol, and in subcarriers where DMRS for the PBCH is not placed.
  • the PBCH is placed in the 1st to 240th subcarriers of the fourth OFDM symbol, and in subcarriers where DMRS for the PBCH is not placed.
  • the antenna ports for PSS, SSS, PBCH, and DMRS for PBCH may be the same.
  • the PBCH to which the PBCH symbol is transmitted at a certain antenna port is a DMRS for the PBCH that is placed in the slot to which the PBCH is mapped, and may be estimated by the DMRS for the PBCH included in the SS/PBCH block to which the PBCH belongs.
  • DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.
  • the set of antenna ports for a DMRS for a PDSCH may be given based on the set of antenna ports for the PDSCH.
  • the set of antenna ports for a DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.
  • the transmission of the PDSCH and the transmission of the DMRS for the PDSCH may be indicated (or scheduled) by one DCI format.
  • the PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH.
  • Transmitting the PDSCH may be transmitting the PDSCH and the DMRS for the PDSCH.
  • the propagation path of a PDSCH may be estimated from the DMRS for the PDSCH. If a set of resource elements through which a PDSCH symbol is transmitted and a set of resource elements through which a DMRS symbol for the PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH through which the PDSCH symbol is transmitted at an antenna port may be estimated by the DMRS for the PDSCH.
  • PRG precoding resource group
  • the antenna port for DMRS for PDCCH (DMRS related to PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as the antenna port for PDCCH.
  • the PDCCH may be estimated from the DMRS for the PDCCH. That is, the propagation path of the PDCCH may be estimated from the DMRS for the PDCCH. If the same precoder is applied (assumed to be applied, assumed to be applied) to a set of resource elements on which a symbol of a certain PDCCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDCCH is transmitted, the PDCCH on which a symbol of the PDCCH at a certain antenna port is transmitted may be estimated by the DMRS for the PDCCH.
  • BCH Broadcast CHannel
  • UL-SCH Uplink-Shared CHannel
  • DL-SCH Downlink-Shared CHannel
  • Transport channels define the relationship between physical layer channels and MAC layer channels (also called logical channels).
  • the BCH of the transport layer is mapped to the PBCH of the physical layer. That is, a transport block passing through the BCH of the transport layer is delivered to the PBCH of the physical layer.
  • the UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, a transport block passing through the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer.
  • the DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, a transport block passing through the DL-SCH of the transport layer is delivered to the PDSCH of the physical layer.
  • One UL-SCH and one DL-SCH may be provided for each serving cell.
  • the BCH may be provided for the PCell.
  • the BCH does not have to be provided for the PSCell or SCell.
  • HARQ Hybrid Automatic Repeat reQuest
  • BCCH Broadcast Control CHannel
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • BCCH is an RRC layer channel used to transmit MIB or system information.
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • BCCH is an RRC layer channel used to transmit MIB or system information.
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • DCCH may also be used at least to transmit RRC messages dedicated to terminal devices 1.
  • DCCH may be used, for example, for terminal devices 1 that are RRC connected.
  • the upper layer parameters common to multiple terminal devices 1 are also referred to as common upper layer parameters.
  • the common upper layer parameters may be defined as parameters specific to the serving cell.
  • the parameters specific to the serving cell may be parameters common to the terminal devices (e.g., terminal devices 1-A, B, C) in which the serving cell is set.
  • the common upper layer parameters may be included in an RRC message delivered on the BCCH.
  • the common upper layer parameters may be included in an RRC message delivered on the DCCH.
  • the dedicated upper layer parameters can provide dedicated RRC parameters to the terminal device 1-A in which the serving cell is set.
  • the dedicated RRC parameters are upper layer parameters that can provide unique settings for each of the terminal devices 1-A, 1-B, and 1-C.
  • the BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer.
  • a transport block containing MIB information is delivered to the BCH of the transport layer.
  • a transport block containing system information that is not MIB is delivered to the DL-SCH of the transport layer.
  • a CCCH is mapped to the DL-SCH or UL-SCH.
  • a transport block mapped to a CCCH is delivered to the DL-SCH or UL-SCH.
  • a DCCH is mapped to the DL-SCH or UL-SCH.
  • a transport block mapped to a DCCH is delivered to the DL-SCH or UL-SCH.
  • the RRC message includes one or more parameters managed in the RRC layer.
  • the parameters managed in the RRC layer are also referred to as RRC parameters.
  • the RRC message may include an MIB.
  • the RRC message may also include system information.
  • the RRC message may also include a message corresponding to a CCCH.
  • the RRC message may also include a message corresponding to a DCCH.
  • An RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.
  • Upper layer parameters are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element).
  • upper layer parameters are a general term for MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE.
  • Parameters included in MAC CE are transmitted by MAC CE (Control Element) commands.
  • the procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C.
  • Cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in the time domain and the frequency domain and detect the physical cell ID (physical cell identity).
  • the terminal device 1 may use cell search to synchronize with a certain cell in the time domain and the frequency domain and detect the physical cell ID.
  • the PSS sequence is based at least on the physical cell ID.
  • the SSS sequence is based at least on the physical cell ID.
  • SS/PBCH block candidates indicate resources on which transmission of SS/PBCH blocks is permitted (possible, reserved, configured, specified, possible).
  • the set of SS/PBCH block candidates in a half radio frame is also referred to as the SS burst set.
  • the SS burst set is also referred to as the transmission window, SS transmission window, or Discovery Reference Signal transmission window (DRS transmission window).
  • the SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.
  • the base station device 3 transmits SS/PBCH blocks of one or more indexes at a predetermined period.
  • the terminal device 1 may detect at least one of the SS/PBCH blocks of the one or more indexes and attempt to decode the PBCH contained in the SS/PBCH block.
  • Random access is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.
  • the random access procedure may be triggered in response to a request for PRACH transmission by higher layer parameters or a PDCCH order.
  • Message 1 is a procedure in which a PRACH is transmitted by terminal device 1.
  • Terminal device 1 transmits a random access preamble in a PRACH as message 1.
  • Terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based at least on an index of an SS/PBCH block candidate detected based on a cell search.
  • Each PRACH opportunity is defined based at least on resources in the time domain and the frequency domain.
  • the terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS/PBCH block candidate in which the SS/PBCH block is detected.
  • the terminal device 1 may attempt to detect DCI format 1_0 with a CRC scrambled with RA-RNTI.
  • Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier).
  • the terminal device 1 attempts to detect a PDCCH including the DCI format in a control resource set given based on the MIB included in the PBCH included in the SS/PBCH block detected based on the cell search and in resources indicated based on the setting of the search area set.
  • Message 2 is also called a random access response (RAR).
  • the terminal device 1 may receive a random access response (or a random access response message) with a PDCCH/PDSCH as a message.
  • Message 3 is a procedure for transmitting a PUSCH scheduled by the random access response grant included in DCI format 1_0 detected by the message 2 procedure.
  • the random access response grant is indicated by the MAC CE included in the PDSCH scheduled by DCI format 1_0.
  • the PUSCH scheduled based on the random access response grant is either message 3 PUSCH or PUSCH.
  • Message 3 PUSCH contains a contention resolution identifier (ID) MAC CE.
  • the contention resolution identifier MAC CE contains a contention resolution ID.
  • Message 3 PUSCH retransmission is scheduled using DCI format 0_0 with scrambled CRC based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).
  • TC-RNTI Temporary Cell - Radio Network Temporary Identifier
  • Message 4 is a procedure that attempts to detect DCI format 1_0 with a CRC scrambled based on either the Cell-Radio Network Temporary Identifier (C-RNTI) or the TC-RNTI.
  • the terminal device 1 receives a PDSCH scheduled based on the DCI format 1_0.
  • the PDSCH may include a collision resolution ID.
  • Data communication is a general term for downlink communication and uplink communication.
  • the terminal device 1 attempts to detect the PDCCH in resources identified based on the control resource set and the search space set (monitors the PDCCH, monitors the PDCCH).
  • a control resource set is a set of resources consisting of a certain number of resource blocks and a certain number of OFDM symbols.
  • a control resource set may consist of contiguous resources (non-interleaved mapping) or distributed resources (interleaver mapping).
  • the set of resource blocks constituting the control resource set may be indicated by higher layer parameters.
  • the number of OFDM symbols constituting the control resource set may be indicated by higher layer parameters.
  • the terminal device 1 attempts to detect a PDCCH in the search space set.
  • attempting to detect a PDCCH in the search space set may be attempting to detect a PDCCH candidate in the search space set, may be attempting to detect a DCI format in the search space set, may be attempting to detect a PDCCH in the control resource set, may be attempting to detect a PDCCH candidate in the control resource set, or may be attempting to detect a DCI format in the control resource set.
  • the search space set is defined as a set of PDCCH candidates.
  • the search space set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.
  • the terminal device 1 attempts to detect PDCCH candidates in some or all of the Type 0 PDCCH common search space set, the Type 0a PDCCH common search space set, the Type 1 PDCCH common search space set, the Type 2 PDCCH common search space set, the Type 3 PDCCH common search space set, and/or the UE-specific search space set.
  • the type 0 PDCCH common search space set may be used as the common search space set with index 0.
  • the type 0 PDCCH common search space set may be the common search space set with index 0.
  • the CSS set is a collective term for the Type 0 PDCCH common search space set, Type 0a PDCCH common search space set, Type 1 PDCCH common search space set, Type 2 PDCCH common search space set, and Type 3 PDCCH common search space set.
  • the USS set is also called the UE-specific PDCCH search space set.
  • a search space set is associated with (contained in, corresponds to) a control resource set.
  • the index of the control resource set associated with the search space set may be indicated by a higher layer parameter.
  • 6A to 6C may be indicated by at least higher layer parameters.
  • a monitoring occasion for a search space set may correspond to an OFDM symbol in which the first OFDM symbol of a control resource set associated with the search space set is located.
  • a monitoring occasion for a search space set may correspond to a resource of a control resource set starting from the first OFDM symbol of the control resource set associated with the search space set.
  • the monitoring occasion for the search space set is given based on at least some or all of the PDCCH monitoring interval, the PDCCH monitoring pattern in the slot, and the PDCCH monitoring offset.
  • FIG. 8 is a diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment.
  • a search area set 91 and a search area set 92 are set in a primary cell 301
  • a search area set 93 is set in a secondary cell 302
  • a search area set 94 is set in a secondary cell 303.
  • the solid white blocks in primary cell 301 indicate search area set 91
  • the solid black blocks in primary cell 301 indicate search area set 92
  • the blocks in secondary cell 302 indicate search area set 93
  • the blocks in secondary cell 303 indicate search area set 94.
  • the monitoring interval of search area set 91 is set to 1 slot, the monitoring offset of search area set 91 is set to 0 slots, and the monitoring pattern of search area set 91 is set to [1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunities of search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.
  • the monitoring interval of search area set 92 is set to 2 slots, the monitoring offset of search area set 92 is set to 0 slots, and the monitoring pattern of search area set 92 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunity of search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.
  • the monitoring interval of search area set 93 is set to 2 slots, the monitoring offset of search area set 93 is set to 0 slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.
  • OFDM symbol #7 8th OFDM symbol
  • the monitoring interval of search area set 94 is set to 2 slots, the monitoring offset of search area set 94 is set to 1 slot, and the monitoring pattern of search area set 94 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunity of search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.
  • the Type 0 PDCCH common search space set may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by the SI-RNTI (System Information-Radio Network Temporary Identifier).
  • CRC Cyclic Redundancy Check
  • the Type 0a PDCCH common search space set may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by the SI-RNTI (System Information-Radio Network Temporary Identifier).
  • CRC Cyclic Redundancy Check
  • the Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by the Random Access-Radio Network Temporary Identifier (RA-RNTI) and/or a CRC sequence scrambled by the Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).
  • RA-RNTI Random Access-Radio Network Temporary Identifier
  • TC-RNTI Temporary Cell-Radio Network Temporary Identifier
  • the Type 2 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by the Paging-Radio Network Temporary Identifier (P-RNTI).
  • P-RNTI Paging-Radio Network Temporary Identifier
  • the Type 3 PDCCH common search space set may be used for DCI formats with CRC sequences scrambled by the Cell-Radio Network Temporary Identifier (C-RNTI).
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the UE dedicated PDCCH search space set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.
  • the terminal device 1 In downlink communication, the terminal device 1 detects the downlink DCI format.
  • the detected downlink DCI format is used at least for resource allocation of the PDSCH.
  • the detected downlink DCI format is also called a downlink assignment.
  • the terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, the terminal device 1 reports a HARQ-ACK corresponding to the PDSCH (a HARQ-ACK corresponding to a transport block included in the PDSCH) to the base station device 3.
  • the terminal device 1 In uplink communication, the terminal device 1 detects the uplink DCI format.
  • the detected DCI format is used at least for resource allocation of the PUSCH.
  • the detected uplink DCI format is also called an uplink grant.
  • the terminal device 1 transmits the PUSCH.
  • an uplink grant for scheduling a PUSCH is configured for each transmission period of the PUSCH.
  • a PUSCH is scheduled by an uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured in the case of configured scheduling.
  • the PUSCH transmission may correspond to a configured scheduling type 1 or a configured scheduling type 2. That is, the configured scheduling may be either a configured scheduling type 1 or a configured scheduling type 2.
  • the configured scheduling type 1 PUSCH transmission may be configured semi-statically.
  • the configured scheduling type 1 PUSCH transmission may be operated in response to receiving certain higher layer parameters.
  • the certain higher layer parameters may be configuredGrantConfig.
  • the configuredGrantConfig may include rrc-ConfiguredUplinkGrant.
  • the PUSCH transmission may be operated without detection of an uplink grant in the DCI.
  • the configured scheduling type 2 PUSCH transmission may be scheduled semi-persistently. For example, it may be scheduled by an uplink grant.
  • the uplink grant may be included in an activation DCI (activation DCI or valid activation DCI).
  • the configured scheduling type 2 PUSCH transmission may be scheduled by an uplink grant.
  • the certain higher layer parameters may be configuredGrantConfig.
  • configuredGrantConfig may not include rrc-ConfiguredUplinkGrant.
  • a system frame number (SFN) n f may be a number assigned to a radio frame and/or an index for a radio frame.
  • the system frame number may be composed of 10 bits. At least a part of the system frame number may be signaled in the MIB. For example, 6 bits (e.g., 6 most significant bits) of the 10-bit system frame number may be signaled in the MIB. At least a part of the system frame number may be determined based on a PBCH for carrying the MIB. For example, 4 bits (e.g., 4 least significant bits) of the 10-bit system frame number may be carried in a PBCH transport block as part of channel coding.
  • PDCCH-Config may be dedicated higher layer parameters.
  • PDCCH-Config may set parameters for PDCCH.
  • Multiple CORESETs (e.g., up to three) may be set in PDCCH-Config.
  • a CORESET ID may be set in one CORESET.
  • a CORESET pool index may be set in one CORESET.
  • the PDCCH configuration may include two different CORESET pool indexes. For example, two CORESET pool index values (0 and 1) may be provided. For example, two CORESET pool index values may be provided for First CORESET and Second CORESET.
  • the PDCCH configuration may be PDCCH-Config.
  • PDSCH-Config may be dedicated higher layer parameters.
  • PDSCH-Config may configure parameters for the PDSCH.
  • PDCCH candidate(s) If multiple PDCCH candidates (PDCCH candidate(s)) are associated with a search space set configured by a higher layer parameter, one PDCCH candidate is used.
  • the one PDCCH candidate may be the earlier initiated PDCCH candidate of the two PDCCH candidates.
  • the higher layer parameter may be searchSpaceLinking.
  • the base station device 3 may be configured with multiple TRPs (Multi-TRP).
  • the terminal device 1 may be scheduled by two TRPs in one serving cell.
  • Multi-TRP one of the operation modes of single-DCI and multi-DCI may be used.
  • uplink control may be completed in the MAC layer and the physical layer.
  • Multi-TRP downlink control may be completed in the MAC layer and the physical layer.
  • Single-DCI mode the terminal device 1 may be scheduled by the same DCI for multiple TRPs.
  • Multi-DCI mode the terminal device 1 may be scheduled by independent DCI from each TRP.
  • the terminal device 1 may form a beam (beamforming).
  • the terminal device 1 may transmit radio waves (electromagnetic waves) in a specific spatial direction by beamforming.
  • the terminal device 1 may receive radio waves from a specific spatial direction by beamforming.
  • the terminal device 1 may be equipped with and use one or more antennas for one or both of transmitting and receiving radio waves.
  • a directional radio wave may be referred to as a beam.
  • Information related to a beam may be referred to as beam information.
  • the beam information may be a specific spatial direction.
  • the beam information may be the direction of arrival of the radio waves.
  • the beam information may be a TCI state.
  • the beam information may be an uplink transmit spatial filter.
  • the beam information may be an SRS resource indication.
  • the beam information may be a QCL assumption or a QCL relationship.
  • the terminal device 1 may be configured with the upper layer parameter TCI-State.
  • the terminal device 1 may be configured with one list in the upper layer parameter PDSCH-Config.
  • One list may include up to M upper layer parameters TCI-State.
  • One list may be a list of up to M upper layer parameters TCI-State.
  • the terminal device 1 may be configured with one list to decode (receive) the PDSCH according to the PDCCH with DCI.
  • M may depend on the terminal capability (UE capability).
  • M may depend on the terminal capability maxNumberConfiguredTCIStatePerCC.
  • the TCI-State may be referred to as the TCI state.
  • Each TCI-State may include parameters for setting a QCL (Quasi co-location relationship).
  • a QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDSCH.
  • a QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDCCH.
  • a QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a CSI-RS (CSI-RS port) of one CSI-RS resource.
  • a QCL relationship between channel/signal A and channel/signal B may represent that channel/signal A is QCL with channel/signal B.
  • the QCL relationship may be set by one or both of the upper layer parameters qcl-Type1 and qcl-Type2.
  • the QCL relationship may be set by one or both of the upper layer parameters qcl-Type1 for the first downlink reference signal (DL RS) and qcl-Type2 for the second downlink reference signal. If the first downlink reference signal and the second downlink reference signal are different, the QCL type of qcl-Type1 may not be the same as the QCL type of qcl-Type2.
  • the QCL type corresponding to each downlink reference signal may be given by the upper layer parameter qcl-Type in the upper layer parameter QCL-Info.
  • the QCL type may be any of typeA, typeB, typeC, and typeD.
  • One list may be configured by the upper layer parameter dlOrJointTCI-StateList.
  • one list may be configured in the upper layer parameter PDSCH-Config.
  • One list may include up to 128 upper layer parameters DLorJointTCIState (or TCI-State).
  • One list may be a list of up to 128 upper layer parameters DLorJointTCIState (TCI-State).
  • One list may be configured to provide one reference signal.
  • the upper layer parameter DLorJointTCIState (TCI-State) may be configured to provide one reference signal.
  • the one reference signal may be a reference signal for DMRS of PDSCH and QCL for DMRS of PDCCH.
  • the one reference signal may be a reference signal for CSI-RS.
  • One list may be configured to provide one reference.
  • the upper layer parameter DLorJointTCIState may be configured to provide one reference.
  • a single reference may be used to determine the uplink transmit spatial filter (UL TX spatial filter).
  • the uplink transmit spatial filter may be used for PUSCH, PUCCH, and SRS. That is, a single reference may be provided to determine the uplink transmit spatial filter for PUSCH, PUCCH, and SRS.
  • the TCI state may be DLorJointTCIState (TCI-State).
  • DLorJointTCIState may be referred to as DL/Joint TCI state or Unified TCI state.
  • TCI-State e.g., upper layer parameter TCI-State
  • TCI-UL-State e.g., upper layer parameter TCI-UL-State
  • the terminal device 1 may apply the TCI-State setting or the TCI-UL-State setting from the reference BWP.
  • the terminal device 1 may not expect both the first upper layer parameter and the second upper layer parameter to be set.
  • the first upper layer parameter may be any of tci-StatesToAddModList, SpatialRelationInfo, and PUCCH-SpatialRelationInfo.
  • the second upper layer parameter may be any of dl-OrJointTCI-StateList and TCI-UL-State.
  • TCI-State is set in any component carrier in a list
  • the second upper layer parameter may not be set in any component carrier in the same band in the list.
  • the list may be set by the upper layer parameter simultaneousTCI-UpdateList1, the upper layer parameter simultaneousTCI-UpdateList2, the upper layer parameter simultaneousSpatial-UpdatedList1, or the upper layer parameter simultaneousSpatial-UpdatedList2.
  • the first upper layer parameter is set, it may not be expected that two TAs are provided in one serving cell.
  • the terminal device 1 may receive an activation command.
  • the activation command may be used to map up to eight “TCI states and/or pairs of TCI states” to code points of the DCI field ‘Transmission Configuration Indication’.
  • the activation command may be used to map up to eight pairs of TCI states or sets of TCI states to code points of the DCI field ‘Transmission Configuration Indication’.
  • Each set may be one or two TCI states for a downlink channel/signal.
  • Each set may be one or two TCI states for an uplink channel/signal.
  • a pair of TCI states may involve one TCI state for multiple downlink channels/signals (DL TCI states) and one TCI state for multiple uplink channels/signals (UL TCI states).
  • the multiple downlink channels/signals may be some or all of the PDSCH, PDCCH and CSI-RS.
  • the multiple uplink channels/signals may be some or all of the PUSCH, PUCCH, and SRS.
  • the DCI (DCI format) may be composed of one or more DCI fields.
  • the DCI (DCI format) may be composed to include a TCI field ('Transmission Configuration Indication' field).
  • the first set may be applied for downlink BWPs in the indicated component carriers. If a first set of one or more TCI status IDs is activated in the third set, the first set may be applied for downlink BWPs and uplink BWPs in the indicated component carriers.
  • the second set may be a set of one or more component carriers and one or more downlink BWPs.
  • the third set may be a set of some or all of one or more component carriers, one or more downlink BWPs, and one or more uplink BWPs.
  • the N conf TCI states may be configured.
  • the N conf TCI states may be configured in a radio resource control layer.
  • the N conf TCI states may be configured by a higher layer parameter.
  • Each of the N conf TCI states may be referred to as a "configured TCI state.”
  • N conf may be an integer from 1 to 128. If the TCI state is a DL TCI state or a Joint TCI state, N conf may be an integer from 1 to 128. If the TCI state is a UL TCI state, N conf may be an integer from 1 to 64.
  • the terminal device 1 may receive an upper layer configuration. After the "TCI state to be set” is set and before one "indicated TCI state” is applied from the "TCI state to be set", the terminal device 1 may assume that the first uplink transmission spatial filter for PUSCH, PUCCH, and SRS to which the "indicated TCI state" is applied is the same as the second uplink transmission spatial filter.
  • the terminal device 1 may assume that the first uplink transmission spatial filter (UL TX spatial filter) for PUSCH, PUCCH, and SRS to which the indicated TCI state is applied is the same as the second uplink transmission spatial filter.
  • the second uplink transmit spatial filter may be an uplink transmit spatial filter for a PUSCH transmission scheduled by a random access response grant in an initial access procedure.
  • TCI-State may be used as the "indicated TCI state".
  • the terminal device 1 may obtain the QCL assumption (QCL relationship, QCL) from the "set TCI state" for the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the "indicated TCI state" applies.
  • the “indicated TCI state” may be applied to the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS.
  • the “indicated TCI state” may be applied to the DMRS of the PDSCH, the DMRS of the PDCCH, the CSI-RS, the PUSCH, the PUCCH, and the SRS.
  • the terminal device 1 may determine the uplink transmission spatial filter from the "set TCI state" for the PUSCH, PUCCH, and SRS to which the "indicated TCI state" applies.
  • the first "indicated TCI state” may be applied from the first slot.
  • the first channel may be a PUCCH with HARQ-ACK information or a PUSCH with HARQ-ACK information.
  • the HARQ-ACK information may be HARQ-ACK information corresponding to a DCI conveying a TCI state indication (TCI State indication) without downlink assignment.
  • the HARQ-ACK information may be HARQ-ACK information corresponding to a PDSCH scheduled by a DCI conveying a TCI state indication.
  • the second indicated TCI state may be indicated before (or earlier than) the first indicated TCI state.
  • the first slot may be the first slot at least beamAppTime symbols after the last OFDM symbol of the first channel.
  • BeamAppTime may be the number of OFDM symbols.
  • BeamAppTime may be set by an upper layer parameter.
  • BeamAppTime may be determined by the terminal capabilities.
  • the indicated TCI state may be the indicated TCI-State or the indicated TCI-UL-State.
  • the terminal device 1 may receive an activation command ("activated TCI state") for each CORESET associated with the CORESET pool index.
  • the activation command may be used to map up to eight TCI states to a code point in the DCI field 'Transmission Configuration Indication'.
  • the "activated TCI state" corresponding to the one CORESET pool index may be associated with one physical cell ID and the "activated TCI state” corresponding to a CORESET pool index different from the one CORESET pool index may be associated with a physical cell ID different from the one physical cell ID.
  • the activation command may be received as a MAC CE.
  • One or multiple CORESETs may be configured in one BWP.
  • One CORESET may correspond to a CORESET pool index of '0' or '1'.
  • the multi-DCI mode may be configured such that the higher layer parameter PDCCH-Config contains two different values of the CORESET pool index (CORESET Pool Index, or coresetPoolIndex).
  • the activation command may be used to map up to eight combinations of up to four TCI states to a code point of the DCI field 'Transmission Configuration Indication'.
  • the activation command may be used to map up to eight combinations of one or two "TCI state pairs" to a code map of the DCI field 'Transmission Configuration Indication'.
  • Terminal device 1 may not expect to receive more than eight TCI states in an activation command.
  • Terminal device 1 may not expect to receive more than eight "TCI state pairs" in an activation command.
  • the mapping between the TCI state and the code point may be applied from the second slot.
  • the first PUCCH may be accompanied by first HARQ-ACK information.
  • the first PUCCH may be transmitted in response to a first PDSCH.
  • the first PDSCH may convey an activation command.
  • the DMRS port of the PDSCH may be the SS/PBCH block and the QCL for QCL type A.
  • the first upper layer parameter may be set for a CORESET that schedules the PDSCH.
  • the CORESET may schedule the PDSCH.
  • the first time offset may be an offset between reception of the DL DCI and the PDSCH.
  • the first value may be timeDurationForQCL.
  • the terminal device 1 may assume that a TCI field is present in the DCI format of the PDCCH transmitted in the CORESET.
  • the first upper layer parameter may be tci-PresentInDCI to which 'enabled' is set.
  • the first upper layer parameter may be tci-PresentInDCI to which 'enabled' is set for a CORESET that schedules a PDSCH or a multicast PDSCH.
  • the first upper layer parameter may be tci-PresentDCI-1-2.
  • SFN is configured for the PDCCH, and if SFN is configured for the PDSCH, and if the PDSCH is scheduled by a DCI format, and if the time offset is greater than or equal to a threshold, and if the default beam is not supported, it may be assumed that a TCI field is present.
  • Configuring SFN for the PDCCH may be configuring the upper layer parameter sfnSchemePdcch.
  • Configuring SFN for the PDSCH may be configuring the upper layer parameter sfnSchemePdsch.
  • the DCI format may be one of DCI format 1_0, DCI format 1_1, and DCI format 1_2.
  • the default beam may be sfn-DefaultDL-BeamSetup for DCI without a TCI field.
  • the time offset may be the time offset between reception of the DL DCI and the corresponding PDSCH.
  • the threshold may be timeDurationForQCL.
  • the presence of the TCI field may be expected.
  • the TCI state or QCL assumption for the PDSCH may be the same as the first TCI state and the first QCL assumption applied for the CORESET.
  • Configuring SFN scheme A for the PDCCH may also mean configuring sfnSchemePdcch where 'sfnSchemeA' is set.
  • the DMRS port of the PDSCH may be RS and QCL with respect to a certain QCL parameter.
  • the certain QCL parameter may be used for PDCCH QCL indication of a certain CORESET.
  • the certain CORESET may be a CORESET associated with a search space with the lowest CORESET ID (controlResourceSetId) among the CORESETs monitored by the terminal device 1 in the latest slot.
  • the indicated TCI state may be applied to PDSCH reception.
  • a unified TCI state is configured, and the time offset is less than a threshold, and at least one configured TCI state includes a qcl-Type with typeD set, and the indicated TCI state is associated with a PCI (Physical Cell ID) other than the serving cell
  • the DMRS port of the PDSCH in the serving cell may be the reference signal and QCL associated with the QCL parameter of the CORESET associated with the lowest CORESET ID.
  • Configuring the unified TCI state may also be configuring the higher layer parameter dl-OrJointTCI-StateList.
  • the terminal device 1 may determine a spatial domain filter.
  • the spatial domain filter may be used while performing an applicable channel access procedure before UL transmission on the channel. If an SRI corresponding to UL transmission is indicated, the terminal device 1 may use the same spatial domain filter as the spatial domain filter associated with the indicated SRI.
  • the terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive a DL reference signal associated with the indicated TCI state. For example, if TCI-State or TCI-UL-State is set, the terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive a DL reference signal associated with the indicated TCI state.
  • the first terminal capability may be beamCorrespondenceWithoutUL-BeamSweeping, in which '1' is set.
  • the DMRS ports of the PDCCH in CORESET may be DL RS (downlink reference signal) and QCL for the two TCI states.
  • the DMRS ports of the PDCCH in CORESET may be DL RS and QCL for the two TCI states, and the second TCI state may not include the QCL parameters ⁇ Doppler shift, Doppler spread ⁇ .
  • Configuring SFN scheme A for the PDCCH may be configuring sfnSchemePdcch with 'sfnSchemeA' set.
  • Configuring SFN scheme B for the PDCCH may be configuring sfnSchemePdcch with 'sfnSchemeB' set.
  • CJT Coherent Joint Transmission
  • Configuring CJT may mean configuring the higher layer parameter cjtSchemePDSCH.
  • the DMRS port of the PDSCH may be QCL for the reference signals of the two indicated TCI states and QCL type A.
  • the DMRS port of the PDSCH may be QCL for the reference signals of the two indicated TCI states and QCL type A excluding the QCL parameters ⁇ Doppler shift, Doppler spread ⁇ .
  • the DMRS port of the PDSCH may be DL-RS and QCL in two TCI states.
  • SFN scheme B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be DL-RS and QCL in two TCI states and the second TCI state may not include the QCL parameter ⁇ Doppler shift, Doppler spread ⁇ .
  • the two TCI states may be indicated by one code point of the DCI field 'Transmission Configuration Indication' in the DCI scheduling the PDSCH.
  • Configuring SFN scheme A for the PDSCH may be configuring sfnSchemePdsch with 'sfnSchemeA' set.
  • Configuring SFN scheme B for the PDSCH may be configuring sfnSchemePdsch with 'sfnSchemeB' set.
  • the second of the two TCI states does not have to include the QCL parameters ⁇ Doppler shift, Doppler spread ⁇ .
  • a unified TCI state is set and if multi-DCI mode is set and if one indicated TCI state is indicated by a TCI field in DCI format 1_1/1_2 associated with one CORESET pool index value (DCI field 'Transmission Configuration Indication'), one indicated TCI state may correspond to one CORESET pool index value.
  • Setting the unified TCI state may mean setting dl-OrJointTCI-StateList or TCI-UL-State.
  • Setting the multi-DCI mode may mean setting the higher layer parameter PDCCH-Config including two different CORESET pool index values.
  • the CORESET pool index may be set in the higher layer parameter ControlResourceSet.
  • the first indicated TCI-State may be applied to PDSCH reception.
  • the terminal capability of the default beam may be a capability to use the two indicated TCI states to buffer the received signal before the threshold.
  • the terminal capability of the default beam may be a capability for single-DCI mode in FR2 (Frequency Range 2).
  • FR2 may be a frequency range from 24250 MHz to 52600 MHz.
  • the time offset may be an offset between the reception of the scheduled DCI format 1_0/1_1/1_2 and the scheduled PDSCH reception.
  • the time offset may be an offset between the reception of the activated DCI format 1_0/1_1/1_2 and the activated PDSCH reception.
  • the threshold may be timeDurationForQCL or a value less than timeDurationForQCL.
  • the upper layer parameter applyIndicatedTCIState may indicate that the first indicated TCI-State, the second indicated TCI-State or the two indicated TCI-States are applied to PDSCH reception scheduled by DCI format 1_0.
  • the upper layer parameter applyIndicatedTCIState may indicate "first", “second” or “both", where "first” may correspond to the first indicated TCI state, "second” may correspond to the second indicated TCI state and "both" may correspond to the two indicated TCI states. If CJT is set for PDSCH or SFN is set for PDSCH, the upper layer parameter applyIndicatedTCIState may indicate "both".
  • a certain condition may be FR1 (Frequency Range 1).
  • FR1 Frequency Range 1
  • One condition may be that the terminal capability of the default beam is reported.
  • One condition may be that the time offset is greater than or equal to a threshold.
  • FR1 may be the frequency range from 410 MHz to 7125 MHz.
  • the first indicated TCI-State may be applied to the PDSCH scheduled by DCI format 1_0.
  • a first indicated DL/Joint TCI state may be applied to the PDSCH.
  • a second indicated DL/Joint TCI state may be applied to the PDSCH.
  • two indicated DL/Joint TCI states may be applied to the PDSCH. If a unified TCI state is set, and if the terminal device 1 has two indicated TCI-States, and if certain conditions are met, and if the TCI indication field is not set, two DL/Joint TCI states may be applied to the PDSCH.
  • the PDSCH may be scheduled by DCI format 1_1/1_2.
  • the TCI indication field may be a DCI field in DCI format 1_1/1_2.
  • the terminal device 1 may receive a DMRS for a PDSCH scheduled by a PDCCH with a DCI format. If two TCI states are indicated and the terminal device 1 receives the DMRS of the PDSCH and the SS/PBCH block in the same OFDM symbol, at least one DMRS port for the PDSCH and the SS/PBCH block may be QCL of type D ('QCL-Type D'). If the first upper layer parameter is configured and if multiple PDSCHs overlap in the time-frequency domain due to multiple PDCCHs, different DMRS settings may not be expected and the two TCI states may not indicate a DMRS port in one CDM group. The first upper layer parameter may be a PDCCH-Config including two different CORESET pool indices.
  • the SS/PBCH block may belong to either group 1 or group 2. For example, group 1 may correspond to a first TAG ID or a second subTAG ID. Group 2 may correspond to a second TAG ID or a second subTAG ID.
  • up to 16 or 32 HARQ processes may be supported in one serving cell.
  • the number of HARQ processes may be configured by higher layer parameters. If higher layer parameters are not configured, the number of HARQ processes may be 8.
  • the terminal device 1 may receive (decode) the corresponding PDSCH as indicated by the DCI format.
  • the terminal device 1 may assume that the DMRS port of the first PDSCH is a first SS/PBCH block with respect to the first QCL parameter.
  • the first PDSCH may be scheduled with the SI-RNTI, P-RNTI, and G-RNTI for broadcast.
  • the terminal device 1 may assume that the DMRS port of the second PDSCH is a second SS/PBCH block or a second CSI-RS resource and QCL with respect to the first QCL parameter.
  • the second SS/PBCH block or the second CSI-RS resource may be used for RACH-related purposes.
  • the second PDSCH may be scheduled with the RA-RNTI and MSGB-RNTI.
  • the terminal device 1 may assume that the DMRS port of the first PDCCH order and the DMRS port of the third PDSCH are a second SS/PBCH block or a second CSI-RS resource and QCL with respect to the first QCL parameter.
  • the third PDSCH may be scheduled in the RA-RNTI for a random access procedure triggered by the first PDCCH order.
  • the first QCL parameters may include some or all of the Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters.
  • the terminal device 1 may receive a PDSCH without a corresponding PDCCH.
  • the terminal device 1 may receive multiple PDCCHs.
  • the first upper layer parameter may be PDCCH-Config.
  • the first upper layer parameter may include two different CORESET pool index values.
  • the multiple PDCCHs may schedule multiple PDSCHs.
  • the multiple PDSCHs may or may not overlap in the time-frequency domain. If the multiple PDCCHs are associated with different CORESETs, the terminal device 1 may receive multiple PDSCHs simultaneously.
  • the different CORESETs may have different CORESET pool index (coresetPoolIndex) values.
  • CORESET upper layer parameter ControlResourceSet
  • CORESET pool index upper layer parameter coresetPoolIndex
  • the terminal device 1 may assume that CORESET is assigned a CORESET pool index of 0. If two TAG IDs or two subTAG IDs are provided in one serving cell, CORESET may include a CORESET pool index.
  • the first physical cell ID associated with the first CORESET may be different from the second physical cell ID associated with the second CORESET.
  • the first CORESET and the second CORESET may be associated with different physical cell IDs.
  • the first CORESET and the second CORESET may correspond to different CORESET pool indices.
  • the terminal device 1 may monitor PDCCH candidates. For example, the terminal device 1 may monitor a set of PDCCH candidates in one serving cell, in one DL BWP, and in one or more CORESETs. Monitoring the PDCCH candidates may also mean receiving the PDCCH candidates.
  • one PDCCH monitoring occasion may be the union of the PDCCH monitoring occasions for the two PDCCH candidates.
  • the start of the PDCCH reception may be the start of the earlier PDCCH candidate.
  • the end of the PDCCH reception may be the end of the later PDCCH candidate.
  • a CORESET of 3 or less may be provided. If the same CORESET pool index is provided for all CORESETs in a BWP in a serving cell, a CORESET of 3 or less may be provided. If a CORESET pool index of 0 is provided for the first CORESET and a CORESET pool index of 1 is provided for the second CORESET in a BWP in a serving cell, a CORESET of 5 or less may be provided.
  • At least a CORESET index may be provided by a first higher layer parameter, a QCL relation (antenna port QCL) by a second higher layer parameter, and an indication of whether a TCI field is present by a third higher layer parameter.
  • the first higher layer parameter may be controlResourceSetId.
  • the second higher layer parameter may be TCI-State.
  • the third higher layer parameter may be tci-PresentInDCI or tci-PresentDCI-1-2.
  • the terminal device 1 may determine a search opportunity for PDCCH candidates.
  • the search space ID may be searchSpaceID.
  • the search space ID may be included in PDCCH-Config or PDCCH-ConfigCommon.
  • the terminal device 1 may assume QCL information indicated by both of the two TCI states for PDCCH reception in one CORESET.
  • the two TCI states may indicate QCL information (QCL relationship) of the DMRS antenna port for PDCCH reception.
  • the terminal device 1 may assume that the DMRS antenna port associated with PDCCH reception is an SS/PBCH block or a CSI-RS resource and a QCL.
  • the SS/PBCH block or the CSI-RS resource may be identified to the terminal device 1 in a random access procedure initiated by reconfiguration with synch.
  • One CORESET may be a CORESET without index 0.
  • the terminal device 1 may assume that the DMRS antenna port (DMRS port) for the first PDCCH reception and the DMRS antenna port for the first PDSCH reception are the reference signal and QCL provided by the indicated TCI state.
  • Setting the unified TCI state may also mean setting followUnifiedTCIstate, in which 'enable' is set.
  • the first PDSCH reception may be scheduled by the DCI format provided by the first PDCCH reception.
  • the DMRS port for PDCCH reception in the CORESET may be the reference signal and QCL provided by the first indicated TCI state (TCI-State). If a unified TCI state is configured in the CORESET and two indicated TCI states are maintained, and if the upper layer parameter applyIndicatedTCIState is configured for the CORESET to be set to "second", the DMRS port for PDCCH reception in the CORESET may be the reference signal and QCL provided by the second indicated TCI state (TCI-State).
  • the DMRS port for PDCCH reception in the CORESET may be a reference signal and a QCL provided by the two indicated TCI states (TCI-State).
  • Setting the unified TCI state may mean that a dl-OrJointTCI-StateList is provided.
  • Maintaining the two indicated TCI states may mean that the terminal device 1 has two indicated TCI states. Maintaining the two indicated TCI states may mean that a first TCI state and a second TCI state are indicated to the terminal device 1.
  • the DMRS port for PDCCH reception in the CORESET may be the reference signal and QCL set by the TCI state indicated by the MAC CE activation command for the CORESET. If a unified TCI state is not set in a CORESET with index 0, the DMRS port for PDCCH reception in the CORESET may be the SS/PBCH block and QCL.
  • the terminal device 1 may assume that the DMRS antenna ports for PDCCH reception are one or more DL RS and QCL configured by the TCI state.
  • the TCI state indicated by the MAC CE activation command may be the "activated TCI state".
  • the DMRS antenna ports for PDCCH reception in one CORESET with index other than 0 and the DMRS antenna ports for PDSCH scheduled by the DCI format provided by the PDCCH reception may be the reference signal and QCL provided by the indicated TCI-State.
  • the DMRS port for the first PDSCH reception may be a first reference signal and a QCL.
  • the first PDSCH reception may be scheduled by a DCI format provided by PDCCH reception in the first CORESETs.
  • the first reference signal may be provided by a "specified TCI-State" corresponding to the first CORESETs.
  • the DMRS port for the second PDSCH reception may be a second reference signal and a QCL.
  • the second PDSCH reception may be scheduled by a DCI format provided by PDCCH reception in the second CORESETs.
  • the second reference signal may be provided by a "specified TCI-State" corresponding to the second CORESETs.
  • Configuring multi-DCI mode may include some or all of the following: providing CORESET pool index 0 for the first CORESETs in one BWP, providing CORESET pool index 1 for the second CORESETs in one BWP, and providing followUnifiedTCI-State for the first CORESETs and the second CORESETs.
  • the MAC CE activation command for the first CORESETs may include a first CORESET pool index.
  • the MAC CE activation command for the second CORESETs may include a second CORESET pool index.
  • the "activated TCI state" for the first CORESETs may be related to a physical cell ID from the serving cell (e.g., ServingCellConfigCommon) and the "activated TCI state" for the second CORESETs may be related to a physical cell ID from an additional PCI index (e.g., AdditionalPCI).
  • SSB_MTC_AdditionalPCI may be configured.
  • an additional PCI index may be configured.
  • two CORESET pool index values 0 and 1 are provided for the first CORESETs and the second CORESETs.
  • a search space set index may be determined by a first upper layer parameter, a relationship between the search space set and a CORESET by a second upper layer parameter, and a search space set (search space set index) linked by a third upper layer parameter.
  • the first upper layer parameter may be searchSpaceId.
  • the second upper layer parameter may be controlResourceSetId.
  • a second search space set index may be provided by a third upper layer parameter.
  • the third upper layer parameter may link the first search space set and the second search space set.
  • the third upper layer parameter may be searchSpaceLinking. Providing the third upper layer parameter may mean applying search space linking.
  • the terminal device 1 may monitor according to each search space set at a monitoring opportunity in one slot.
  • the count of PDCCH candidates corresponding to the first search space set and the second search space set may be 3.
  • the CORESET pool index for the first CORESET associated with the first search space set may be different from the CORESET pool index for the second CORESET associated with the second search space set.
  • the first search space set and the second search space set being linked may be the first search space set including a searchSpaceLinking with the second search space set, and the second search space set including a searchSpaceLinking with the first search space set.
  • the terminal device 1 may monitor the first PDCCH candidate corresponding to the first search space set for the first DCI format, and may monitor the second PDCCH candidate corresponding to the second search space set.
  • the terminal device 1 may also monitor the third PDCCH candidate corresponding to the third search space set for the second DCI format.
  • the first PDCCH candidate corresponding to the first search space set or the second PDCCH candidate corresponding to the second search space set and the third PDCCH candidate corresponding to the third search space set may use the same CCE set and may be scrambled the same.
  • the third PDCCH candidate corresponding to the third search space set may not be counted for monitoring.
  • the detected DCI format may not be assumed to be the first DCI format.
  • the terminal device 1 may expect different CCEs or different scrambling in one CORESET.
  • the first CORESET may correspond to the CSS set with the smallest index or may correspond to the USS set with the smallest index.
  • the second CORESET may have the same 'typeD' property as the first CORESET.
  • Repetition may be applied for the PDCCH.
  • the repetition applied for the PDCCH may be provided as two-QCLTypeDforPDCCHRepetition.
  • the upper layer parameter TCI-UL-State may be set in the terminal device 1.
  • the terminal device 1 may have one list set in the upper layer parameter BWP-UplinkDedicated.
  • One list may include up to 64 upper layer parameters TCI-UL-State.
  • One list may be a list of up to 64 upper layer parameters TCI-UL-State.
  • Each TCI-UL-State (or UL-TCI-State setting) may include a parameter for setting one reference signal.
  • each TCI-UL-State may include one parameter for setting one reference signal for determining an uplink transmission spatial filter for some or all of the PUSCH, PUCCH, and SRS.
  • One list may be the upper layer parameter ul-TCI-StateList.
  • the TCI state may be the TCI-UL-State.
  • the UL-TCIState (TCI-UL-State) may be referred to as the ULTCI state or the unified TCI state.
  • UL-TCIState may be the higher layer parameter TCI-UL-State.
  • UL-TCIState may be set by the higher layer parameter TCI-UL-State.
  • the higher layer parameter TCI-UL-State may associate one or two downlink reference signals with one corresponding QCL type.
  • An upper layer parameter twoTAGs may be configured. When twoTAGs is configured, two TAs, subTAGs or TAGs may be used in one serving cell. When twoTAGs is configured, the terminal device 1 may maintain or manage two uplink timings.
  • a unified TCI state may be configured. The unified TCI state may be configured by setting dl-OrJointTCI-StateList or TCI-UL-State.
  • a unified TCI state may be configured for one serving cell. Each unified TCI state may be associated with one TAG ID or subTAG ID. For example, to determine a timing adjustment for uplink transmission, each unified TCI state may be associated with one TAG ID or subTAG ID. The unified TCI state may be TCI-State or TCI-UL-State.
  • the timing adjustment for uplink transmission may be an adjustment of the uplink timing.
  • each unified TCI state may be associated with one TAG ID or one subTAG ID for determining uplink timing adjustment.
  • Condition 1 may be that a multi-DCI mode is set. Setting the multi-DCI mode may be that a PDCCH configuration including two different CORESET pool indices is set. Setting the multi-DCI mode may be that an SSB-MTC-AdditionalPCI is set and a PDCCH configuration including two different CORESET pool indices is set. Setting the multi-DCI mode may be that a PDCCH-Config including two different CORESET pool index values in different CORESETs is set.
  • Condition 2 may be that two TAs are set.
  • Setting the two TAs may be that the upper layer parameter twoTAGs is set.
  • Condition 3 may be that a unified TCI state is set. Setting the unified TCI state may be that the upper layer parameter dl-OrJointTCI-StateList or the upper layer parameter TCI-UL-State is set. Condition 1, condition 2, and condition 3 may be met for one serving cell.
  • the unified TCI state associated with one TAG ID is not expected to correspond to two TAGs. If terminal capabilities are reported, the unified TCI state associated with one TAG ID (or subTAG ID) may correspond to two TAGs.
  • the terminal device 1 may transmit a PUSCH according to a spatial relation.
  • the spatial relation may be a relation based on one reference signal (RS).
  • the one reference signal may be a reference signal for determining an uplink transmission spatial filter.
  • the one reference signal may be a reference signal set with qcl-Type set to typeD in the "indicated TCI state".
  • the "indicated TCI state" may be the indicated TCI-State or the indicated TCI-UL-State.
  • the reference RS in the indicated TCI-State may be a CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet.
  • the reference RS in the indicated TCI-UL-State may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet.
  • the indicated TCI-UL-State (Indicated TCI-UL-State) may be the TCI state indicated by DCI format 1_1 or DCI format 1_2, the UL TCI state, or the unified TCI state.
  • the indicated TCI-State (Indicated TCI-State) may be the TCI state indicated by DCI format 1_1 or DCI format 1_2, the DL/Joint TCI state, or the unified TCI state.
  • the higher layer parameter applyIndicatedTCIState may be expected to be configured.
  • the higher layer parameter applyIndicatedTCIState may indicate to apply a first indicated TCI state to the PUSCH, to apply a second indicated TCI state to the PUSCH, or to apply two indicated TCI states to the PUSCH. If two indicated TCI states are applied to the PUSCH, the first indicated TCI state may be associated with a first SRS resource set and the second indicated TCI state may be associated with a second SRS resource set.
  • the first TCI state may correspond to CORESET pool index 0, and the second TCI state may correspond to CORESET pool index 1.
  • the indicated TCI state may be an indicated TCI-State or an indicated TCI-UL-State.
  • the first indicated Joint/UL TCI state may be applied to the PUSCH. If a unified TCI state is configured, and two indicated TCI states are held, and two SRS resource sets are configured, and the SRS resource set indication field in the DCI format indicates "00", then the first indicated Joint/UL TCI state may be applied to the PUSCH. If a unified TCI state is configured, and two indicated TCI states are held, and two SRS resource sets are configured, and the SRS resource set indication field in the DCI format indicates "01", then the second indicated Joint/UL TCI state may be applied to the PUSCH.
  • the first indicated Joint/UL TCI state and the second indicated Joint/UL TCI state may be applied to the PUSCH.
  • the PUSCH may be scheduled according to a DCI format (e.g., DCI format 0_1 or DCI format 0_2).
  • the Joint/UL TCI state may be an indicated TCI-State or an indicated TCI-UL-State.
  • a MAC protocol data unit may be a bit string whose length is byte aligned (i.e. a multiple of 8 bits).
  • a MAC service data unit may be a bit string whose length is byte aligned (i.e. a multiple of 8 bits).
  • a MAC SDU may be contained within a MAC PDU from the first bit onwards.
  • a MAC CE may be a bit string whose length is byte aligned (i.e. a multiple of 8 bits).
  • a MAC subheader may be a bit string whose length is byte aligned (i.e. a multiple of 8 bits). Each MAC subheader may be placed immediately before the corresponding MAC SDU, MAC CE or padding.
  • a MAC protocol data unit may consist of one or more MAC subPDUs.
  • Each MAC subPDU may consist of one MAC subheader.
  • Each MAC subPDU may consist of one MAC subheader and one MAC service data unit (SDU).
  • SDU MAC service data unit
  • Each MAC subPDU may consist of one MAC subheader and one MAC CE.
  • Each MAC subPDU may consist of one MAC subheader and padding.
  • the MAC SDUs may be of variable size.
  • Each MAC subheader may correspond to one MAC SDU, one MAC CE or padding.
  • One MAC PDU may be one transport block.
  • the first MAC CE may be an activation command A.
  • the first MAC CE may be a MAC CE for activation or deactivation of TCI states for PDSCH (UE-specific PDSCH).
  • the first MAC subheader may identify the MAC CE for activation/deactivation of TCI states for PDSCH.
  • the first MAC subheader may be accompanied by a first LCID (Logical channel ID).
  • the value of the first LCID may be “TCI States Activation/Deactivation for UE-specific PDSCH”.
  • FIG. 9 is a diagram showing an example of an activation command A according to an embodiment of the present invention.
  • the serving cell ID field may indicate an identifier of a serving cell to which the first MAC CE is applied.
  • the BWP ID field may indicate a DL BWP to which the MAC CE is applied as a code point of the 'bandwidth part indicator field' of the DCI. If the first MAC CE is applied to a set of multiple serving cells, the BWP ID field may be ignored.
  • the "T i " field may indicate an activation/deactivation status of the TCI state with TCI state ID i.
  • the "T i " field set to 1 may indicate that the TCI state with TCI state ID i is activated.
  • the "T i " field set to 1 may indicate that the TCI state with TCI state ID i is mapped to one code point of the 'Transmission Configuration Indication field' of the DCI.
  • the "T i " field set to 0 may indicate that the TCI state with TCI state ID i is deactivated.
  • the "T i " field set to 1 may indicate that the TCI state with TCI state ID i is not mapped to one code point of the 'Transmission Configuration Indication field' of the DCI.
  • i may be a TCI state ID (or TCI-StateID).
  • the TCI state may be associated with a TCI state ID.
  • the maximum number of "activated TCI states" may be 8.
  • the CORESET Pool ID field may indicate that the first mapping is specific to the CORESET ID (ControlResourceSetId) set with the CORESET Pool ID (CORESET Pool Index).
  • the first mapping may be a mapping between the "activated TCI states" and the code point of the DCI 'Transmission Configuration Indication' set by the "T i " field.
  • the CORESET Pool ID field set to 1 may indicate that the first MAC CE applies to downlink transmissions scheduled by the CORESET with the CORESET Pool ID (CORESET Pool Index) of value 1.
  • Setting the CORESET Pool ID field to 0 may indicate that the first MAC CE applies to downlink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET Pool Index) of value 0. If the CORESET Pool Index (coresetPoolIndex) is not set, the CORESET Pool ID field in the first MAC CE may be ignored.
  • the second MAC CE may be an activation command B.
  • the second MAC CE may be a MAC CE for activation or deactivation of TCI states for PDSCH (UE-specific PDSCH).
  • the second MAC subheader may identify the MAC CE for activation/deactivation of TCI states for PDSCH.
  • the second MAC subheader may be accompanied by a second LCID (Logical channel ID).
  • the second LCID may be an eLCID.
  • the value of the second LCID may be “Enhanced TCI States Activation/Deactivation for UE-specific PDSCH”.
  • FIG. 10 is a diagram showing an example of an activation command B according to an embodiment of the present invention.
  • the “C i ” field may indicate whether an octet including a TCI state ID i,2 exists. For example, when the “C i ” field is set to 1, an octet including a TCI state ID i,2 may exist. For example, when the “C i ” field is set to 0, an octet including a TCI state ID i,2 may not exist.
  • the TCI state ID i,j field may indicate a TCI state identified by a TCI state ID (TCI-StateId).
  • the TCI state ID i,j may represent the j-th TCI state indicated for the i-th codepoint of the DCI 'Transmission configuration indication' field.
  • the TCI state ID i,2 may be optional based on the indication of the “C i ” field.
  • i may be an index of the codepoint of the DCI 'Transmission configuration indication' field.
  • j may be 1 or 2.
  • the third MAC CE may be an activation command C.
  • the third MAC CE may be a MAC CE for activation or deactivation of the unified TCI states.
  • the third MAC subheader may identify the MAC CE for activation/deactivation of the unified TCI states.
  • the third MAC subheader may be accompanied by a third LCID (Logical channel ID).
  • the third LCID may be an eLCID.
  • the value of the third LCID may be “Unified TCI States Activation/Deactivation MAC CE”.
  • FIG. 11 is a diagram showing an example of an activation command C according to an embodiment of the present invention.
  • the DL BWP ID field may indicate one downlink BWP to which MAC CE is applied as one code point of the DCI'bandwidth part indicator' field.
  • the UL BWP ID field may indicate one uplink BWP to which MAC CE is applied as one code point of the DCI'bandwidth part indicator' field.
  • the "P i " field may indicate whether each TCI code point has multiple TCI states or one TCI state. For example, if the "P i " field is set to 1, the i-th TCI code point may include both DL TCI state and UL TCI state.
  • the i-th TCI code point may include one of DL TCI state and UL TCI state.
  • the "D/U” field may indicate whether the TCI state ID in the same octet is for joint (both DL and UL)/DL or UL. For example, if the “D/U” field is set to 1, the TCI state ID in the same octet may be for DL/joint. For example, if the “D/U” field is set to 0, the TCI state ID in the same octet may be for UL.
  • the “TCI state ID” field may indicate the TCI state identified by the TCI state ID (TCI-StateId).
  • the DL TCI state may be a TCI state that applies to some or all of the PDSCH, PDCCH, and CSI-RS.
  • the UL TCI state may be a TCI state that applies to some or all of the PUSCH, PUCCH, and SRS.
  • the Joint TCI state may be a TCI state representing both DL TCI state and UL TCI state.
  • the DLorJointTCIState may be a DL TCI state or a Joint TCI state.
  • the UL-TCIState may be a UL TCI state.
  • the DL TCI state may be a TCI state for DL.
  • the Joint TCI state may be a TCI state for both DL and UL.
  • the UL TCI state may be a TCI state for UL.
  • the TCI codepoint may be the codepoint of the DCI 'Transmission configuration indication' field.
  • the "R" field in the MAC CE may be a Reserved bit.
  • the Reserved bit may be set to 0.
  • the fourth MAC CE may be an activation command D.
  • the fifth MAC CE may be an activation command E.
  • the fourth MAC CE may be a MAC CE for activation or deactivation of the unified TCI state.
  • the fourth MAC CE may be a MAC CE for activation or deactivation of the Enhanced unified TCI state.
  • the fifth MAC CE may be a MAC CE for activation or deactivation of the unified TCI state.
  • the fifth MAC CE may be a MAC CE for activation or deactivation of the Enhanced unified TCI state.
  • the fourth MAC subheader may identify a MAC CE for activation/deactivation of the unified TCI state.
  • the fifth MAC subheader may identify a MAC CE for activation/deactivation of the unified TCI state.
  • the fourth MAC subheader may be accompanied by a fourth LCID (Logical channel ID).
  • the fifth MAC subheader may be accompanied by a fifth LCID (Logical channel ID).
  • the fourth LCID may be an eLCID.
  • the fifth LCID may be an eLCID.
  • the value of the fourth LCID may be "Enhanced unified TCI States Activation/Deactivation MAC CE 1".
  • the value of the fifth LCID may be "Enhanced unified TCI States Activation/Deactivation MAC CE 2".
  • FIG. 12 is a diagram showing an example of an activation command D according to an aspect of the present embodiment.
  • the serving cell ID field may indicate an identifier of a serving cell to which the fourth MAC CE is applied.
  • the DL BWP ID field may indicate one downlink BWP to which the fourth MAC CE is applied as one code point of a DCI'bandwidth part indicator' field.
  • the UL BWP ID field may indicate one uplink BWP to which the fourth MAC CE is applied.
  • the UL BWP ID field may indicate one uplink BWP to which the fourth MAC CE is applied as one code point of a DCI'bandwidth part indicator' field.
  • the "P i " field may indicate whether each TCI code point has multiple TCI states or one TCI state.
  • the i th TCI codepoint may include both DL TCI state and UL TCI state.
  • the i th TCI codepoint may include one of DL TCI state and UL TCI state.
  • the “D/U i ” field may indicate whether each TCI codepoint is for joint (both DL and UL)/DL or UL. For example, if the “D/U i ” field is set to 1, the i th TCI codepoint may be for DL/joint. For example, if the “D/U i ” field is set to 0, the i th TCI codepoint may be for UL.
  • the “T j ” field may indicate the activation/deactivation status of the TCI state with TCI state ID j.
  • the “T j ” field being set to 1 may indicate that the TCI state with TCI state ID j is activated.
  • the field “T j " set to 1 may indicate that the TCI state with TCI state ID j is mapped to one code point in the 'Transmission Configuration Indication field' of the DCI.
  • the field “T j " set to 0 may indicate that the TCI state with TCI state ID j is deactivated.
  • the field “T j " set to 1 may indicate that the TCI state with TCI state ID j is not mapped to one code point in the 'Transmission Configuration Indication field' of the DCI.
  • j may be a UL TCI state ID (UL-TCIState-Id) or a DL/Joint TCI state ID (DLorJoint-TCIState-Id).
  • the number of UL TCI state IDs may be up to 64.
  • the number of DL/Joint TCI state IDs may be up to 128.
  • j may be ⁇ 0, ..., 63 ⁇ .
  • j may be ⁇ 0, ..., 127.
  • j may be ⁇ 0, ..., 191 ⁇ .
  • the "T j " field may indicate the activation/deactivation status of the TCI state with TCI state ID j-128.
  • the "T j " field may indicate the activation/deactivation status of the TCI state with TCI state ID j-64.
  • the "T j " field set to 1 may indicate that the TCI state with TCI state ID j-128 is activated.
  • the "T j " field set to 1 may indicate that the TCI state with TCI state ID j-128 is mapped to the i-th TCI codepoint.
  • the "T j " field set to 1 may indicate that the TCI state with TCI state ID j-64 is activated.
  • the "T j " field set to 1 may indicate that the TCI state with TCI state ID j-64 is mapped to the i-th TCI codepoint.
  • the CORESET Pool ID field may indicate that the second mapping is specific to the CORESET (Control Resource Set Id) configured with the CORESET Pool ID (CORESET Pool Index).
  • the second mapping may be a mapping between the "activated TCI state" and the codepoint of the DCI 'Transmission Configuration Indication' set by the "T i " field.
  • Setting the CORESET Pool ID field to 1 may indicate that the MAC CE applies to downlink or uplink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET Pool Index) of value 1.
  • Setting the CORESET Pool ID field to 0 may indicate that the MAC CE applies to downlink or uplink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET Pool Index) of value 0. If the CORESET Pool Index (coresetPoolIndex) is not set, the CORESET Pool ID field in the fourth MAC CE may be ignored.
  • FIG. 13 is a diagram showing an example of an activation command E according to an aspect of the present embodiment.
  • the CORESET pool ID field in FIG. 13 may be reserved.
  • the “P i,j ” field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, if the “P i,j ” field is set to 1, the j th TCI state in the i th TCI codepoint may be two (e.g., DL TCI state and UL TCI state). For example, if the “P i,j ” field is set to 0, the j th TCI state in the i th TCI codepoint may be one (e.g., DL TCI state or UL TCI state).
  • the “D/U j ” field may indicate whether the TCI state ID in the same octet is for joint (both DL and UL)/DL or UL.
  • the “D/U j " field may indicate whether the TCI state ID in the same octet is for joint (both DL and UL)/DL or UL. For example, if the "D/U j " field is set to 1, the TCI state ID in the same octet may be for DL/joint. For example, if the "D/U j " field is set to 0, the TCI state ID in the same octet may be for UL.
  • the "TCI state ID i,j” field may indicate the TCI state identified by the DL/Joint TCI State ID (TCI-StateId) or the UL TCI State ID (UL-TCIState-Id). If the "D/U j " field is set to 1, the 7-bit long "TCI state ID i,j " may be used. If the "D/U j " field is set to 0, the most significant bit of the "TCI state ID i,j " may be considered as reserved and the remaining 6 bits may indicate the ID of the UL-TCIState (UL TCI state Id, UL-TCIState-Id).
  • j may correspond to a CORESET pool ID (CORESET pool index).
  • Whether j corresponds to a CORESET pool ID (CORESET pool index) may be determined by a “J” field.
  • j may correspond to a CORESET pool ID (CORESET pool index). For example, if the “J” field is set to 0, j may correspond to an index of a TCI state at one codepoint.
  • the “P i,j ” field may indicate whether each TCI codepoint of the DCI associated with the CORESET pool ID corresponding to j has multiple TCI states or has one TCI state. For example, when the "P i,j " field is set to 1, it may correspond to both DL TCI state and UL TCI state of the i-th TCI codepoint of the DCI associated with the CORESET Pool-ID corresponding to j.
  • the "P i,j " field when the "P i,j " field is set to 0, it may correspond to either DL TCI state or UL TCI state of the i-th TCI codepoint of the DCI associated with the CORESET Pool-ID corresponding to j. If the CORESET pool index (higher layer parameter coresetPoolIndex) is not set, j may not correspond to a CORESET Pool-ID.
  • the activation command F may be a MAC CE for TCI state indication for the PDCCH.
  • the activation command F may consist of a 5-bit serving cell ID, a 4-bit CORESET ID and a 7-bit TCI state ID.
  • the activation command G may be a MAC CE for TCI state indication for PDCCH.
  • the activation command G may consist of a 5-bit serving cell ID, a 4-bit CORESET ID, a 7-bit first TCI state ID, and a 7-bit second TCI state ID. If one or more CORESETs in one BWP are configured with different CORESET pool index values, the activation command G may not be applied to one or more CORESETs. If SFN is applied for PDCCH, the activation command G may be applied. The application of SFN for PDCCH may be the setting of sfnSchemePdcch.
  • the terminal device 1 may receive an activation command.
  • the activation command may be a collective term for activation command A, activation command B, activation command C, activation command D, activation command E, activation command F, and activation command G.
  • One TA offset (Timing advance offset) value may be provided by higher layer parameters for one serving cell. If multi-DCI mode is configured, two TA offset values may be provided by two higher layer parameters for a transmission.
  • a transmission may be a transmission with multiple TCI states associated with the first CORESETs and the second CORESETs.
  • the first TA offset may correspond to a transmission with TCI states associated with the first CORESETs.
  • the second TA offset may correspond to a transmission with TCI states associated with the second CORESETs.
  • Configuring multi-DCI mode may mean that two CORESET pool index values 0 and 1 are provided for the first CORESETs and the second CORESETs in one serving cell.
  • a second TA offset value may be provided for a transmission with a second spatial domain filter.
  • a first TA offset value may be provided for a transmission with a first spatial domain filter.
  • the second spatial domain filter may correspond to a TCI state associated with a physical cell ID from other than the serving cell (e.g., an additional PCI index).
  • the first spatial domain filter may correspond to a TCI state associated with a physical cell ID for the serving cell.
  • the first TA offset value may correspond to some or all of the first TAG, the first TAG ID, the first subTAG, and the first subTAG ID.
  • the second TA offset value may correspond to some or all of the second TAG, the second TAG ID, the second subTAG, and the second subTAG ID.
  • the first TAG may be associated with the first TAG ID or the first subTAG ID.
  • the second TAG may be associated with the second TAG ID or the second subTAG ID.
  • the first TAG ID or the first subTAG ID may be included in the first TCI state.
  • the second TAG ID or the second subTAG ID may be included in the second TCI state.
  • Both the first TCI state and the second TCI state may be a unified TCI state.
  • the first TCI state and the second TCI state may be Joint TCI states or may be UL TCI states.
  • One or both of the Joint TCI states and the DL TCI states may be provided by dl-OrJointTCI-StateList.
  • the UL TCI state may be provided by TCI-UL-State (or ul-TCIState-List).
  • a timing advance may be determined based at least on a TA offset.
  • One TA offset may be provided in one serving cell.
  • Two TA offsets may be provided in one serving cell.
  • the terminal device 1 may determine a value of the TA offset.
  • the terminal device 1 may determine two values of TA offsets in one serving cell.
  • the value of the TA offset may be N TA,offset .
  • one TA offset value may be applied to the two uplink carriers for transmission in a serving cell associated with the same TAG or the same subTAG.
  • the terminal device 1 may adjust the uplink timing. For example, the terminal device 1 may adjust the uplink timing in response to receiving a TA command (Timing advance command). For example, in response to receiving one TA command (Timing advance command) for one TAG (Timing advance group), the terminal device 1 may adjust the uplink timing for PUSCH/SRS/PUCCH transmission in all serving cells in one TAG. For example, in response to receiving one TA command for one TAG, the terminal device 1 may adjust the uplink timing for PUSCH/SRS/PUCCH transmission in one or more serving cells belonging to one TAG. For example, the terminal device 1 may adjust the uplink timing based on the value of N TA,offset .
  • N TA,offset may be the same for all serving cells in one TAG.
  • N TA,offset may not be the same for all serving cells in one TAG.
  • the terminal device 1 may adjust the uplink timing based on one or both of the value of N TA,offset and the TA command.
  • the uplink timing may be the same for all serving cells in one TAG.
  • the terminal device 1 may adjust uplink timing for PUSCH/SRS/PUCCH transmission corresponding to one subTAG (or subTAG ID). For example, in response to receiving one TA command for one subTAG, the terminal device 1 may adjust uplink timing for PUSCH/SRS/PUCCH transmission in one or more serving cells belonging to one subTAG and one or both of the TRPs. N TA,offset may be the same for all serving cells in one subTAG. The uplink timing may be the same for all serving cells in one subTAG. Two subTAGs may be used in one serving cell.
  • the TAG ID may be used to identify a TAG or a subTAG.
  • the subTAG ID may be used to identify a subTAG.
  • one subTAG ID may be associated with each TAG. For example, when two TAs are configured, two subTAG IDs may be determined from M TAG IDs.
  • two TAGs in one serving cell may be associated with two subTAG IDs.
  • the TAG associated with the serving cell may be associated with a first subTAG ID and the TAG associated with the non-serving cell may be associated with a second subTAG ID.
  • the non-serving cell may be a cell corresponding to an additional PCI index.
  • the non-serving cell may be a cell associated with an additional PCI.
  • two TAs may be configured.
  • the first uplink timing may be determined based on a timing adjustment indication for one TAG from the MCG.
  • the second uplink timing may be determined based on a timing adjustment indication for one TAG from the SCG.
  • the first uplink timing and the second uplink timing may be determined based on a timing adjustment indication for two TAGs from the MCG.
  • the TA (Timing advance) of the random access preamble may be 0.
  • the TA command may be included in a random access response.
  • a TA command for one TAG may be included in a random access response related to one TAG (or subTAG).
  • a TA command related to one TAG ID or one subTAG ID may be included in a random access response in a random access procedure related to one TAG ID or one subTAG ID.
  • the TA command may be transmitted as a MAC CE command.
  • the TA command may be an Absolute timing advance command MAC CE.
  • the TA command in the case of a random access response or an Absolute timing advance command MAC CE.
  • T A may indicate a value of N TA for one TAG.
  • T A may be an integer from 0 to 3846.
  • N TA may be T A *16*64/2 ⁇ .
  • N TA may be related to a subcarrier interval of a certain uplink transmission.
  • a certain uplink transmission may be an uplink transmission from a terminal device 1.
  • an uplink transmission may be the first uplink transmission after receiving a random access response.
  • an uplink transmission may be the first uplink transmission after receiving an absolute timing advance command MAC CE.
  • T A may be an index value.
  • the uplink transmission may be an uplink channel transmission.
  • whether to receive the absolute timing advance command MAC CE or the random access response may be determined by a higher layer parameter.
  • the random access procedure may be initiated (triggered) by a PDCCH order.
  • a TA command TA may indicate an adjustment of the current N TA value for one TAG.
  • a TA command TA may indicate an adjustment from N TA,old to N TA,new , where N TA,new may be N TA,old +(T A -31)*16*64/2 ⁇ .
  • T A may be an integer between 0 and 63.
  • the TA command (TA command value) may be related to the maximum subcarrier spacing of one or more active uplink BWPs.
  • the TA command may be a TA command in one TAG including uplink BWPs in two uplink carriers of one serving cell.
  • N TA,new for one uplink BWP with initial subcarrier spacing may be rounded to match the timing advance granularity for one uplink BWP with initial subcarrier spacing.
  • Rounding a value may be a rounding of a value.
  • N TA,new may be rounded while maintaining the TA accuracy requirements.
  • the uplink transmission timing adjustment may be applied from the beginning of the second slot.
  • the first slot n may be an uplink slot.
  • the uplink slot may be a slot corresponding to an uplink frame.
  • the second slot may be n+k+1+2 ⁇ *K offset . That is, the second slot may be k+1+2 ⁇ *K offset slots after the first slot n.
  • the K offset may be provided by a higher layer parameter.
  • k may be ceil(N subframe, ⁇ slot ⁇ (N T,1 +N T,2 +N TA,max +0.5)/T sf ).
  • the unit of N T,1 may be milliseconds.
  • N T,1 may be a period in milliseconds of N 1 symbols.
  • the N 1 symbols may correspond to a PDSCH processing time.
  • N T,2 may be a period in milliseconds of N 2 symbols.
  • N 2 symbols may correspond to a PUSCH preparation time.
  • N TA,max may be a maximum timing advance value in milliseconds.
  • N TA,max may be a maximum TA value that can be provided by a 12-bit TA command field.
  • N subframe, ⁇ slot may be the number of slots in one subframe.
  • T sf may be 1 millisecond.
  • T sf may be the duration of a subframe.
  • K offset may be K cell,offset -K UE,offset .
  • K cell,offset may be provided by a higher layer parameter.
  • K UE,offset may be provided by one MAC CE command.
  • the terminal device 1 may determine a TA command (TA command value) based on the subcarrier spacing of the changed active uplink BWP. For example, when the terminal device 1 changes the active uplink BWP between the time of receiving the TA command and the time of applying an adjustment for the uplink transmission timing, the terminal device 1 may determine the TA command based on the subcarrier spacing of the new active uplink BWP.
  • the terminal device 1 may assume the same absolute timing advance command value (absolute timing advance command MAC CE). That is, the first absolute timing advance command value before the active uplink BWP change may be the same as the second absolute timing advance command value after the active uplink BWP change.
  • the terminal device 1 may change the N TA .
  • the terminal device 1 may change the N TA .
  • the uplink timing adjustment may be that the uplink timing is determined or changed.
  • the difference between the first downlink timing associated with the first TAG and the second downlink timing associated with the second TAG may be less than or equal to the CP (Cyclic Prefix) length.
  • the CP length may correspond to an active UL BWP.
  • the difference between the first downlink timing associated with the first TAG and the second downlink timing associated with the second TAG may be greater than the CP (Cyclic Prefix) length.
  • Setting two TAs may mean that the terminal device 1 operates with two TAGs in one BWP (for example, active UL BWP) in one serving cell.
  • Setting two TAs may mean that the terminal device 1 operates with two TAGs in one serving cell.
  • a TAG may be a group of one or more serving cells and/or one or more TRPs.
  • One or more serving cells/TRPs may be configured by RRC.
  • One or more serving cells/TRPs may use one TA value.
  • One or more serving cells/TRPs may use one timing reference cell.
  • a PTAG Primary TAG
  • a STAG Secondary TAG
  • One TAG may include two subTAGs. Two TAGs may be provided, configured or determined in one serving cell. Each TAG may be associated with a TAG ID.
  • a subTAG may be a group of one or more serving cells and/or one or more TRPs.
  • a subTAG may be a group of serving cells/TRPs that use the same TA (TA value).
  • TA value TA
  • a subTAG may be associated with one TRP.
  • a subTAG may be associated with one serving cell.
  • a subTAG may be a TA group for one serving cell.
  • Two subTAGs may be provided, configured or determined in one serving cell.
  • Each subTAG may be associated with a subTAG ID.
  • a subTAG may be a type of TAG. That is, TAG and subTAG may be referred to as TAGs.
  • the RRC layer may configure one or more upper layer parameters for maintenance of uplink time alignment.
  • the RRC layer may configure a time alignment timer.
  • the time alignment timer may be configured by an upper layer parameter timeAlignmentTimer.
  • the time alignment timer may control a first time.
  • the first time may be a time at which the MAC entity considers that multiple serving cells/TRPs belong to the associated TAG/subTAG.
  • the time alignment timer may be a time for uplink time alignment. That is, the time alignment timer being operational may mean that time synchronization has been achieved. That is, the time synchronization may mean that uplink timing has been determined (or adjusted). That is, the TA may perform time synchronization.
  • the time synchronization timer may correspond to one subTAG.
  • the time synchronization timer may control the time at which the MAC entity considers one or more serving cells/TRPs to belong to the subTAG.
  • the time synchronization timer may control the time at which the MAC entity considers one or more TRPs to belong to the subTAG.
  • the MAC entity may perform some or all of the first through fourth steps.
  • the MAC entity may apply the TA command for the indicated TAG/subTAG.
  • the MAC entity may start or restart a time synchronization timer associated with the indicated TA command.
  • the time synchronization timer may be a timeAlignmentTimer.
  • the second process may be a process when the TA command is received in a random access response (random access response message).
  • the second process may be a process when the TA command is received in message B (MSGB).
  • the second process may be a process in a serving cell belonging to one TAG/subTAG.
  • the second process may be a process in an SpCell.
  • the MAC entity may apply the TA command for one TAG/subTAG and may start or restart a time synchronization timer associated with one TAG/subTAG.
  • the TA command may be received by a random access response.
  • the MAC entity may apply a TA command for a TAG/subTAG and may start the time synchronization timer. Additionally, if contention resolution is not completed successfully, the MAC entity may stop the time synchronization timer.
  • the MAC entity may apply a TA command in a random access response in the first random access procedure and may start the time synchronization timer. Furthermore, if the contention resolution is not completed successfully, the MAC entity may stop the time synchronization timer.
  • the first random access procedure may be a random access procedure associated with one subTAG.
  • the first random access procedure may be a random access procedure for TA acquisition.
  • the MAC entity may ignore the received TA command.
  • the MAC entity may apply the absolute timing advance command for a PTAG (Primary TAG) and may start or restart a time synchronization timer associated with the PTAG (Primary TAG). If an absolute TA command is received for a random access preamble transmission, the MAC entity may apply the absolute TA command for the TAG or subTAG. Also, in this case, the time synchronization timer associated with the PTAG may not be started or restarted.
  • the MAC entity may apply the absolute TA command for the one subTAG and may start or restart a time synchronization timer associated with the one subTAG.
  • MSGA Message A
  • the fourth operation may be an operation when the time synchronization timer expires.
  • the MAC entity may perform some or all of the first to seventh suboperations.
  • the first suboperation may be flushing all HARQ buffers for all serving cells.
  • the second suboperation may be informing the RRC to release PUCCHs for all serving cells.
  • the third suboperation may be informing the RRC to release SRSs for all serving cells.
  • the fourth suboperation may be clearing the configured downlink assignments and the configured uplink grants.
  • the fifth suboperation may be clearing PUSCH resources for semi-persistent CSI reporting.
  • the sixth suboperation may be considering all time synchronization timers as expired.
  • the seventh sub-operation may be to maintain the N TA for all TAGs (or subTAGs). That is, if the time synchronization timer is not running, the MAC entity may not change the N TA .
  • the MAC entity may perform some or all of the eighth to thirteenth sub-operations.
  • the eighth sub-operation may be to flush all HARQ buffers for serving cells belonging to this TAG (or this subTAG).
  • the ninth sub-operation may be to inform the RRC to release the PUCCH for serving cells belonging to this TAG (or this subTAG).
  • the tenth sub-operation may be to inform the RRC to release the SRS for serving cells belonging to this TAG (or this subTAG).
  • An eleventh sub-operation may be to clear configured downlink assignments and configured uplink grants for serving cells belonging to this TAG (or this subTAG).
  • a twelfth sub-operation may be to clear PUSCH resources for semi-static CSI reporting for serving cells belonging to this TAG (or this subTAG).
  • a thirteenth sub-operation may be to maintain N TAs for this TAG (or this subTAG).
  • the HARQ buffer may store MAC PDUs for transmission.
  • One HARQ buffer may be associated with one HARQ process.
  • One HARQ process may correspond to one HARQ process ID. Flushing an HARQ buffer may result in the HARQ buffer becoming empty.
  • the HARQ process may store the MAC PDU in the associated HARQ buffer.
  • the MAC entity may not perform an uplink transmission. If the time synchronization timer is not running, the MAC entity may not perform an uplink transmission.
  • the uplink transmission may not include a random access preamble transmission.
  • the uplink transmission may not include a message A transmission.
  • the uplink transmission may be an uplink transmission in one serving cell.
  • the uplink transmission may be an uplink transmission in one TRP.
  • the time synchronization timer may be a time synchronization timer associated with a TAG to which one serving cell belongs.
  • the time synchronization timer may be a time synchronization timer associated with a subTAG to which one serving cell belongs.
  • the time synchronization timer may be a time synchronization timer associated with a subTAG to which one TRP belongs.
  • the MAC entity may not perform uplink transmissions to one or more serving cells/TRPs included in that subTAG. If the time synchronization timer associated with a subTAG has expired, the MAC entity may not perform uplink transmissions associated with that subTAG. This uplink transmission may not include either or both of a random access preamble transmission and a message A transmission.
  • the MAC entity may not perform uplink transmissions in any serving cell.
  • This uplink transmission may not include a random access preamble transmission in the SpCell.
  • This uplink transmission may not include a message A transmission in the SpCell.
  • a MAC PDU may be a byte-aligned bit string.
  • a MAC PDU may be a transport block.
  • a MAC PDU may consist of one or more MAC subPDUs.
  • Each MAC subPDU may consist of a MAC subheader.
  • Each MAC subPDU may consist of a MAC subheader and a MAC SDU (Service Data Unit).
  • Each MAC subPDU may consist of a MAC subheader and a MAC CE (Control Element).
  • Each MAC subPDU may consist of a MAC header and padding.
  • a MAC SDU may be data from an upper layer.
  • a MAC SDU may be data to an upper layer.
  • the TA command may be a MAC CE.
  • the TA command may also be included in the MAC CE.
  • the TA command may be included in the TA command MAC CE.
  • the TA command MAC CE may consist of a TAG ID and a TA command.
  • the TAG ID may indicate one or both of a TAG and a subTAG.
  • the TAG including the SpCell may correspond to TAG ID 0.
  • the TAG ID may be indicated by 2 bits.
  • the TAG ID may indicate one subTAG.
  • the TAG ID may indicate one TRP.
  • the TA command may indicate a T A.
  • the T A may be an integer between 0 and 63.
  • the T A may be used to control the amount of timing adjustment.
  • the timing adjustment may be applied by the MAC entity.
  • the TA command may be indicated by 6 bits.
  • the TA command MAC CE may be identified by a MAC subheader with a certain LCID (Logical channel ID).
  • the TA command may be included in an absolute Timing advance command MAC CE.
  • the absolute TA command MAC CE may consist of a TA command and a TAG ID.
  • the TA command may indicate an index value T A.
  • the T A may be used to control the amount of timing adjustment.
  • the TA command may be indicated by 12 bits.
  • the TAG ID may indicate one TAG/subTAG.
  • the TAG ID may indicate one serving cell/TRP.
  • the absolute TA command MAC CE may be identified by a MAC subheader with an eLCID.
  • the eLCID may be the corresponding eLCID at index 316.
  • the TA command may be included in the random access response.
  • the TA command may be included in the MAC payload of the random access response.
  • the TA command may indicate an index value T A.
  • T A may be used to control the amount of timing adjustment.
  • the size of the TA command field may be 12 bits.
  • the random access response may be composed of a TA command, an uplink grant, and a Temporary C-RNTI.
  • the uplink grant may indicate resources to be used in the uplink.
  • the uplink grant field may be 27 bits.
  • the Temporary C-RNTI may indicate a temporary ID used by the MAC entity during random access.
  • the Temporary C-RNTI field may be 16 bits.
  • the random access response may be a MAC RAR.
  • the random access response may be a fallbackRAR.
  • the TA command may be included in a message B (MSGB).
  • the TA command may be included in the MAC payload of the message B.
  • the TA command may be included in a successRAR.
  • the random access response may also include a TAG ID/subTAG ID.
  • a TA command may correspond to one TAG/subTAG.
  • One TAG/subTAG may correspond to one TAG ID/subTAG ID.
  • One TAG/subTAG may be determined based on an SS/PBCH block index indicated by a PDCCH order.
  • One TAG ID/subTAG ID may be determined based on an SS/PBCH block index indicated by a PDCCH order.
  • Random access may be initiated by the MAC entity. Random access may be initiated by a PDCCH order (or PDCCH). Random access may be initiated by RRC. Random access in an SCell may be initiated by a PDCCH order. Random access may also be triggered by the MAC entity. Random access may be triggered by a PDCCH order. Random access may also be triggered by RRC. Random access may be referred to as a Random Access Procedure.
  • an event may be an initial access from an RRC_IDLE state.
  • an event may be an RRC connection Re-establishment procedure.
  • an event may be arrival of uplink or downlink data in an RRC_CONNECTED state when the uplink synchronization state is 'non-synchronised'.
  • an event may be arrival of uplink data in an RRC_CONNECTED state when there are no PUCCH resources.
  • an event may be a failure of a scheduling request.
  • an event may be a request by RRC in response to a handover.
  • an event may be an RRC connection Resume.
  • an event may be establishing time alignment.
  • an event may be establishing time alignment for a STAG.
  • an event may be establishing time alignment for a serving cell/TRP.
  • an event may be to request Other SI.
  • an event may be Beam failure recovery.
  • an event may be TA acquisition.
  • an event may be Secondary TA acquisition.
  • An event may be the purpose of a random access procedure.
  • the random access may be 4-step random access (4-step random access type).
  • the random access may be 2-step random access (2-step random access type).
  • the random access may support CBRA (Contention-based random access). That is, the random access may be CBRA.
  • the random access may support CFRA (Contention-free random access). That is, the random access may be CFRA.
  • the random access may be CBRA of 4-step random access type.
  • the random access may be CFRA of 4-step random access type.
  • the random access may be CBRA of 2-step random access type.
  • the random access may be CFRA of 2-step random access type.
  • the terminal device 1 may transmit message 1 (random access preamble), receive message 2 (random access response), transmit message 3, and receive message 4 (contention resolution).
  • the terminal device 1 may transmit message A (random access preamble and PUSCH payload) and receive message B (contention resolution).
  • the terminal device 1 may receive an allocation of a random access preamble, transmit a random access preamble, and receive a random access response.
  • the terminal device 1 may receive an allocation of a random access preamble and PUSCH, transmit a random access preamble and PUSCH, and receive a random access response.
  • an RSRP Reference signal received power
  • the terminal device 1 may perform a 4-step random access type random access.
  • the terminal device 1 may perform a 2-step random access type random access.
  • Message 1 may consist of one preamble in PRACH. After transmitting message 1, the terminal device 1 may monitor one response (random access response) within a set window. In CFRA, a dedicated preamble may be assigned. In CFRA, in response to receiving the random access response, the terminal device 1 may terminate the random access. In CBRA, in response to receiving the random access response, the terminal device 1 may transmit message 3. For example, the terminal device 1 may transmit message 3 using an uplink grant (random access response grant). In CBRA, the terminal device 1 may monitor message 4 (contention resolution). If contention resolution after transmitting message 3 is not successful, the terminal device 1 may transmit message 1.
  • CFRA random access response
  • CBRA in response to receiving the random access response, the terminal device 1 may transmit message 3. For example, the terminal device 1 may transmit message 3 using an uplink grant (random access response grant).
  • the terminal device 1 may monitor message 4 (contention resolution). If contention resolution after transmitting message 3 is not successful, the terminal device 1 may transmit message 1.
  • Message A may include one preamble in the PRACH. Message A may also include a payload in the PUSCH.
  • the terminal device 1 may monitor one response within a set window.
  • CFRA a dedicated preamble and PUSCH resources may be allocated for transmitting message A.
  • CFRA in response to receiving one response, the terminal device 1 may terminate the random access.
  • CBRA if contention resolution is successful, the terminal device 1 may terminate the random access.
  • the terminal device 1 may transmit message 3 based on the fallback indication and monitor contention resolution. If contention resolution is not successful after transmitting message 3, the terminal device 1 may transmit message A. If the random access of the 2-step random access type is not completed, the terminal device 1 may be configured to switch to the 4-step random access type CBRA.
  • the random access procedure may be initiated (triggered) by a PDCCH order.
  • the random access procedure may be initiated (triggered) by MAC.
  • the random access procedure may be initiated (triggered) by RRC.
  • the random access procedure in the SCell may be initiated by a PDCCH order.
  • the random access procedure in the cell associated with the additional PCI index may be initiated by a PDCCH order.
  • only one random access may be in progress at the same time. If a first random access is in progress and a second random access is triggered, the terminal device 1 may continue with the first random access. If a first random access is in progress and a second random access is triggered, the terminal device 1 may start the second random access.
  • the RRC may configure some or all of the first through ninth upper layer parameters for random access.
  • a first set of PRACH occasions for message 1 (random access preamble) transmission may be configured by the first upper layer parameters.
  • the first set may be used for message A PRACH.
  • a second set of PRACH opportunities for random access preamble transmission for message A may be configured by the first upper layer parameters. That is, the first upper layer parameters may determine the available set of PRACH opportunities for transmission of the random access preamble.
  • the PRACH opportunities may be referred to as RA opportunities.
  • the PRACH opportunities may be referred to as RACH opportunities.
  • the RACH configuration may be configured in the upper layer parameter SI-RequestConfig, the upper layer parameter ReconfigurationWithSync, the upper layer parameter BeamFailureRecoveryConfig, the upper layer parameter RACH-ConfigCommon, the upper layer parameter TwoTA-Config1-r18, and the upper layer parameter TwoTA-Config2-r18.
  • the RACH configuration may be included in some or all of the upper layer parameter SI-RequestConfig, the upper layer parameter ReconfigurationWithSync, the upper layer parameter BeamFailureRecoveryConfig, the upper layer parameter RACH-ConfigCommon, the upper layer parameter TwoTA-Config1-r18, and the upper layer parameter TwoTA-Config2-r18.
  • the RACH configuration may be RACH-ConfigGeneric.
  • the RACH configuration may be associated with one additional PCI index.
  • the first upper layer parameter may be prach-ConfigurationIndex.
  • the first upper layer parameter may be set in a configuration for second TA acquisition (one or both of the upper layer parameter twoTA-Config1-r18 and the upper layer parameter twoTA-Config2-r18).
  • the second TA acquisition may be that two TAs (TAGs or subTAGs) are determined, provided, or configured in one serving cell.
  • the power of the random access preamble may be set by a third higher layer parameter.
  • the power of the initial (first transmission) random access preamble may be set by a third higher layer parameter.
  • the RSRP threshold may be set by a fourth higher layer parameter.
  • the RSRP threshold may be an RSRP threshold for SS/PBCH block selection, or CSI-RS selection.
  • the RSRP threshold may be an RSRP threshold for selection between two uplink carriers.
  • the two uplink carriers may be NUL (Normal Uplink) and SUL (Supplementary Uplink).
  • the maximum number of transmissions of message 1 and/or message A may be set by a fifth upper layer parameter.
  • One or both of message 1 and message A may have their transmission power changed for each transmission.
  • the power of one or both of message 1 and message A may be changed based on the sixth upper layer parameter.
  • the sixth upper layer parameter may be a power ramping factor.
  • the random access preamble may be set by a seventh upper layer parameter.
  • an index of a random access preamble used in a PRACH opportunity may be set by the seventh upper layer parameter.
  • the seventh upper layer parameter may indicate any value from 0 to 63.
  • the seventh upper layer parameter may be ra-PreambleIndex.
  • the number of SS/PBCH blocks mapped to each PRACH opportunity may be defined by an eighth upper layer parameter.
  • the number of CBRA random access preambles mapped to each SS/PBCH block may be defined by an eighth upper layer parameter.
  • the CBRA random access preamble may be a Contention-based Random Access Preamble. Transmission of one or both of message 1 and message A may use a random access preamble corresponding to group A or group B. For example, terminal device 1 may perform message A transmission using random access preamble group A. For example, terminal device 1 may perform message A transmission using random access preamble group B.
  • the ninth higher layer parameter may define a PRACH opportunity associated with one SS/PBCH block (SSB).
  • the MAC entity may transmit a random access preamble in the PRACH opportunity.
  • the ninth higher layer parameter may be ra-ssb-OccasionMaskIndex.
  • the first to twelfth variables may be used for the random access procedure.
  • the first variable may be PREAMBLE_INDEX.
  • the second variable may be PREAMBLE_TRANSMISSION_COUNTER.
  • the third variable may be PREAMBLE_POWER_RAMPING_COUNTER.
  • the fourth variable may be PREAMBLE_POWER_RAMPING_STEP.
  • the fifth variable may be PREAMBLE_RECEIVED_TARGET_POWER.
  • the sixth variable may be PREAMBLE_BACKOFF.
  • the seventh variable may be PCMAC.
  • the eighth variable may be SCALING_FACTOR_BI.
  • the ninth variable may be TEMPORARY_C-RNTI.
  • the tenth variable may be RA_TYPE.
  • the eleventh variable may be POWER_OFFSET_2STEP_RA.
  • the twelfth variable may be MSGA_PREAMBLE_POWER_RAMPIPNG_STEP.
  • RA_TYPE may be set to 4-stepRA. For example, if a random access procedure is initiated by a PDCCH order, and if the random access preamble index (ra-PreambleIndex) is provided by the PDCCH, and if the random access preamble index is not 0b000000, RA_TYPE may be set to 4-stepRA. For example, if a random access procedure is initiated for an SI request, and if random access resources (RACH configuration) are provided by RRC for the SI request, RA_TYPE may be set to 4-stepRA.
  • RACH configuration random access resources
  • RA_TYPE may be set to 4-stepRA. If a random access procedure is initiated for reconfiguration with sync, and if a CFRA resource for 4-step random access type is provided in the upper layer parameter rach-ConfigDedicated, RA_TYPE may be set to 4-stepRA. For example, if a random access procedure is initiated for second TA acquisition, and if a random access resource (e.g., a CFRA resource) is provided for second TA acquisition, RA_TYPE may be set to 4-stepRA.
  • a random access resource e.g., a CFRA resource
  • the random access resource may be one or both of a CFRA resource and a CBRA resource.
  • Providing a random access resource may mean that a RACH configuration is set.
  • Acquiring a second TA may mean acquiring a second (or two) TAs in one serving cell. If RA_TYPE is set to 4-stepRA, a random access of 4-step random access type may be performed. If RA_TYPE is set to 2-stepRA, a random access of 2-step random access type may be performed.
  • the MAC entity may perform any of the first through sixth operations.
  • the first operation may be performed if a random access procedure is initiated for beam failure recovery.
  • the first operation may be performed if a beam failure recovery timer (beamFailureRecoveryTimer) is running or not set.
  • the first operation may be performed if contention-free Random Access Resources (CFRA) for the beam failure recovery request are provided by RRC.
  • the beam failure recovery request may relate to either an SSB and a CSI-RS.
  • the first operation may be performed if at least one SSB or at least one CSI-RS is available.
  • the at least one SSB may be an SSB with a Reference Signal Received Power (RSRP) exceeding a threshold.
  • the at least one CSI-RS may be a CSI-RS with an RSRP exceeding a threshold.
  • the second operation may be performed if a random access preamble index (ra-PreambleIndex) is provided by the PDCCH (PDCCH order).
  • the second operation may be performed if the random access preamble index is not 0b000000.
  • the MAC entity may set PREAMBLE_INDEX to the random access preamble index.
  • one SSB may be signaled by the PDCCH.
  • the second random access preamble index may be a ra-PreambleIndex corresponding to an indicated SSB from a set of random access preambles for acquiring the second TA.
  • the first value may identify one RACH configuration.
  • the first value may identify one upper layer parameter including the RACH configuration.
  • the first value may be an additional PCI index, a TAG ID, and TRP information.
  • a third operation may be performed. If CFRA resources related to the SSB are provided in rach-ConfigDedicated, the third operation may be performed. If at least one SSB is available, the third operation may be performed. The at least one SSB may be an SSB with an RSRP above a threshold. In the third operation, the MAC entity may select an SSB. The SSB may be with an RSRP above a threshold. In the third operation, PREAMBLE_INDEX may be set to ra-PreambleIndex corresponding to the selected SSB.
  • a fourth operation may be performed. If a random access procedure for the SI request is initiated, the fourth operation may be performed. If random access resources for the SI request are provided by RRC, the fourth operation may be performed. In the fourth operation, if at least one SSB is available, the MAC entity may select one SSB. The at least one SSB may be with an RSRP above a threshold. The one SSB may be with an RSRP above a threshold. In the fourth operation, the MAC entity may select any SSB. In the fourth operation, from the random access preambles determined according to the higher layer parameter ra-PreambleStartIndex, one random access preamble corresponding to the selected SSB may be selected. In the fourth operation, PREAMBLE_INDEX may be set to the selected random access preamble.
  • a fifth operation may be performed.
  • a fifth operation may be performed for CBRA preamble selection.
  • the MAC entity may select an SSB.
  • the SSB may have an RSRP above a certain threshold. Also, in the fifth operation, the MAC entity may select any SSB.
  • a sixth operation may be performed. If a random access procedure for the second TA acquisition is initiated, the sixth operation may be performed. If a random access resource for the second TA acquisition is provided by RRC, the sixth operation may be performed. In the sixth operation, the MAC entity may select an SSB. The SSB may have an RSRP above a certain threshold. In the sixth operation, any SSB may be selected. In the sixth operation, a random access preamble index (ra-PreambleIndex) corresponding to the selected SSB may be set. The random access resource for the second TA acquisition may be determined in one or both of the upper layer parameters twoTA-Config1-r18 and twoTA-Config2-r18.
  • the MAC entity may determine a first PRACH opportunity.
  • the first PRACH opportunity may be associated with a selected SSB.
  • the first PRACH opportunity may be determined based on a first restriction.
  • the first restriction may be given by the higher layer parameter ra-ssb-OccasionMaskIndex.
  • the first PRACH opportunity may be the next valid PRACH opportunity.
  • the first higher layer parameter may be one or both of ra-AssociationPeriodIndex and si-RequestPeriod.
  • the MAC entity may determine a second PRACH opportunity.
  • the selected SSB may be permitted by the first restriction.
  • the selected SSB may be indicated by the PDCCH (PDCCH order).
  • the MAC entity may determine a third PRACH opportunity based on the SSB.
  • the MAC entity may determine a fourth PRACH opportunity corresponding to the selected CSI-RS.
  • the MAC entity may flush the message 3 buffer, may flush the message A buffer, may select a carrier to perform the random access, may determine the random access type, and may perform a Random Access Resource Selection Procedure.
  • Random Access Procedure Random Access Procedure
  • the MAC entity may then perform the random access preamble transmission procedure.
  • the MAC entity may determine the power for each random access type based on the counter.
  • the MAC entity may calculate the RA-RNTI associated with the PRACH opportunity on which the random access preamble is transmitted.
  • the MAC entity may instruct the physical layer to transmit the random access preamble using the selected PRACH opportunity.
  • the RA-RNTI associated with the PRACH opportunity may be calculated based on some or all of the index of the first OFDM symbol of the PRACH opportunity, the index of the first slot of the PRACH opportunity in one system frame, the index of the PRACH opportunity in the frequency domain, and the uplink carrier on which the random access preamble is transmitted.
  • the MAC entity may start the first window from the end of the random access preamble transmission.
  • the random access preamble may be a CFRA random access preamble (Contention-free Random Access Preamble).
  • the random access preamble may be a CBRA random access preamble (Contention-based Random Access Preamble).
  • the MAC entity may monitor the PDCCH for the random access response. For example, while the first window is running, the MAC entity may monitor the PDCCH.
  • the PDCCH may be a PDCCH in the SpCell. An indication of receipt of the PDCCH may be received from the physical layer.
  • the PDCCH transmission may be addressed to the C-RNTI. If the CFRA random access preamble is transmitted by the MAC entity, the MAC entity may consider the random access to be successfully completed.
  • a valid downlink assignment may be received on a PDCCH corresponding to the RA-RNTI.
  • the received transport block may be decoded.
  • the random access response may include a MAC subPDU.
  • the MAC subPDU may be accompanied by a random access preamble ID. Based at least on the random access response including the MAC subPDU, the MAC entity may consider reception of the random access response successful.
  • the MAC entity may consider the random access response to be successfully received. Based at least on the random access response being deemed to be successfully received, the MAC entity may consider the random access to be successfully completed and may indicate to upper layers the receipt of an acknowledgement and may apply the received TA command. For example, the MAC entity may process the value of the received UL grant. For example, the MAC entity may indicate to the physical layer the received UL grant.
  • the MAC entity may process a TA command for the one serving cell. Based at least on the reception of the random access response being deemed successful and the random access preamble being transmitted in one serving cell, the MAC entity may apply a TA command for the one serving cell. Based at least on the reception of the random access response being deemed successful, the MAC entity may apply a TA command for one TRP. For example, if a MAC PDU includes a TA command (e.g. an absolute TA command MAC CE), the MAC entity may process the TA command. For example, the MAC PDU may be included in a transport block. For example, one or more MAC SDUs may be multiplexed into a transport block. For example, one or more MAC SDUs may be demultiplexed from the transport block.
  • a MAC PDU may be included in a transport block.
  • one or more MAC SDUs may be multiplexed into a transport block.
  • one or more MAC SDUs may be demultiplex
  • a beam failure recovery (BFR) procedure may be configured by RRC.
  • the configuration of the BFR procedure may include RACH configuration.
  • the configuration of the BFR procedure may be an upper layer parameter BeamFailureRecoveryConfig.
  • the MAC entity may trigger BFR based on the value of BFI_COUNTER.
  • BFI_COUNTER may be a counter for beam failure instance indications. If BFR is triggered, a first random access procedure may be initiated.
  • the first random access procedure may be a random access procedure for beam failure recovery.
  • the terminal device 1 may receive upper layer parameters.
  • the terminal device 1 may initiate a random access procedure in response to receiving the upper layer parameter RRCReconfiguration.
  • RRCReconfiguration may be received for NR SCG RRC Reconfiguration.
  • the second random access procedure may be a random access procedure for reconfiguration with sync.
  • the random access procedure for the second TA acquisition may be initiated in the MAC or the RRC.
  • Setting two TAs may mean setting up a procedure for obtaining a second TA.
  • the physical layer Before the start of random access (physical random access procedure), the physical layer may receive a set of SS/PBCH block indexes from the upper layer and may provide a set of RSRP measurements to the upper layer. Before the start of random access, the physical layer may instruct the upper layer to perform type 1-random access. Before the start of random access, the physical layer may instruct the upper layer to perform type 2-random access. The type 1-random access may be a 4-step-random access type of random access. The type 2-random access may be a 2-step-random access type of random access. Before the start of random access, the physical layer may receive one or more parameters from the upper layer. The one or more parameters may include a configuration of PRACH transmission parameters. The configuration of PRACH transmission parameters may be a RACH configuration.
  • the PRACH transmission parameters may be a PRACH preamble format, a time resource, or a frequency resource for PRACH transmission.
  • the one or more parameters may include a parameter for determining a root sequence.
  • the one or more parameters may include a parameter determining a cyclic shift in the PRACH preamble sequence (a sequence of random access preambles).
  • the one or more parameters may include a TAG ID/subTAG ID. For example, one random access preamble may be associated with one TAG/subTAG.
  • the random access may include at least the transmission of message 1 on the PRACH and message 2.
  • the random access may include the transmission of message 1 on the PRACH, message 2, a PUSCH scheduled by a random access response grant, and a PDSCH for contention resolution.
  • Message 1 may be a random access preamble.
  • Message 2 may be a random access response message (random access response).
  • message 2 may be a random access response accompanied by a PDCCH/PDSCH.
  • the random access procedure may be referred to as random access.
  • the random access may include at least the transmission of message A and the reception of message B.
  • the random access may include the transmission of message A, the reception of message B, the transmission of PUSCH scheduled by the random access response grant, and PDSCH for contention resolution.
  • Message A may be a random access preamble and PUSCH in the PRACH.
  • Message B may be a random access response.
  • message B may be a random access response accompanied by PDCCH/PDSCH.
  • the random access response grant may be a fallback random access response grant.
  • the PRACH transmission (random access preamble transmission) may have the same subcarrier spacing as the PRACH transmission initiated by the higher layer. If two uplink carriers are configured in one serving cell and the terminal device 1 detects a PDCCH order, the terminal device 1 may use the value of the UL/SUL indication field from the detected PDCCH order to determine one uplink carrier for the PRACH transmission. If two TAs are configured and the terminal device 1 detects a PDCCH order, the terminal device 1 may use one field (or the value of a field) of the detected PDCCH order to determine one serving cell/TRP/TAG/subTAG/TAG ID/subTAG ID for the PRACH transmission. In the random access procedure for obtaining the second TA, one field of the PDCCH order may include an additional PCI index.
  • Random access may be triggered by higher layers or a PDCCH order in response to a request for PRACH transmission.
  • the configuration by higher layers for PRACH transmission may include some or all of the following: configuration for PRACH transmission, preamble index (index of the random access preamble), preamble SCS (subcarrier spacing of the random access preamble), RA-RNTI, PRACH resources, and TAG ID/subTAG ID.
  • the random access preamble may be a contention-based preamble.
  • the random access preamble may be a contention-free preamble.
  • the number of contention-based preambles per valid PRACH opportunity and per SS/PBCH block index may be configured by higher layer parameters.
  • the PRACH opportunity may be valid. For example, the PRACH opportunity may be valid based at least on the OFDM symbol configured for time division duplex.
  • the terminal device 1 may attempt to decode DCI format 1_0 with a CRC scrambled with RA-RNTI. For example, in response to a PRACH transmission, the terminal device 1 may attempt to decode DCI format 1_0 with a CRC scrambled with RA-RNTI within a certain window.
  • the certain window may start based at least on the first OFDM symbol of the CORESET.
  • the terminal device 1 may pass the transport block to an upper layer.
  • the transport may be received in a PDSCH within a window.
  • the upper layer may parse the transport block corresponding to a random access preamble identity (RAPID) associated with the PRACH transmission. If the upper layer identifies the RAPID in the random access response (random access response message), the upper layer may indicate an uplink grant (random access response grant) to the physical layer.
  • the random access response may be a random access response for the transport block.
  • the random access response grant may be a random access response uplink grant.
  • the upper layer may instruct the physical layer to transmit a PRACH. Also, if the upper layer does not identify a RAPID related to the PRACH transmission, the upper layer may instruct the physical layer to transmit a PRACH. For example, the terminal device 1 may be expected to transmit a PRACH within a predetermined time after the last OFDM symbol of the window. Also, the terminal device 1 may be expected to transmit a PRACH within a predetermined time after the last OFDM symbol of the PDSCH reception. Transmitting a PRACH may be transmitting a random access preamble.
  • the random access response grant may be composed of one or more fields.
  • the one or more fields may include a frequency hopping flag field.
  • the one or more fields may include a frequency domain resource allocation field (or a PUSCH frequency resource allocation field).
  • the one or more fields may include a time domain resource allocation field (or a PUSCH time resource allocation field).
  • the one or more fields may include a Transmission power control (TPC) command field.
  • TPC Transmission power control
  • the one or more fields may include a CSI request field.
  • the one or more fields may include a field having TRP information.
  • DCI format 1_0 may be used for a first random access procedure.
  • the first random access procedure may be referred to as a random access procedure initiated by a PDCCH order. That is, the PDCCH to which DCI format 1_0 is mapped may be a PDCCH order.
  • the DCI format in the PDCCH order may include a Random Access Preamble Index field.
  • the Random Access Preamble Index may be ra-PreambleIndex.
  • the DCI format in the PDCCH order may include a UL/SUL indicator field.
  • the UL/SUL indicator field may indicate an UL carrier.
  • the DCI format in the PDCCH order may include a SS/PBCH index field.
  • the SS/PBCH index field may indicate one SS/PBCH.
  • the one SS/PBCH may be used to determine a RACH opportunity for a PRACH transmission. If the value of the Random Access Preamble Index is not all "0", the SS/PBCH index field may indicate one SS/PBCH.
  • the DCI format in the PDCCH order may include a PRACH Mask Index field.
  • the PRACH mask index field may indicate one RACH opportunity.
  • One RACH opportunity may be associated with one SS/PBCH. If the value of the random access preamble index is not all "0", the PRACH mask index field may indicate one RACH opportunity.
  • the DCI format in the PDCCH order may include an Additional PCI Index field.
  • the Additional PCI Index field may indicate a first upper layer parameter including a RACH configuration.
  • the Additional PCI Index field may indicate one additional PCI index.
  • the one additional PCI index may be associated with a first upper layer parameter including a RACH configuration.
  • the first upper layer parameter may be twoTA-Config1-r18.
  • the first upper layer parameter may be twoTA-Config2-r18.
  • the PCI Physical Cell ID
  • the additional PCI may be a physical cell ID for a non-serving cell.
  • the additional PCI index may be an index for identifying the additional PCI.
  • the additional PCI index may be set by an upper layer parameter.
  • the additional PCI index may be indicated by a DCI field.
  • the additional PCI index may be used to indicate a physical cell ID.
  • DCI formats 1_0/1_1/1_2 may be used for scheduling PDSCH.
  • a BWP indication (Bandwidth part indicator) field may be included in one or both of DCI format 1_1 and DCI format 1_2. The number of information bits constituting the BWP indication field may be determined based on the number of DL BWPs.
  • a TPC command (TPC command for scheduled PUCCH) field may be included in one or both of DCI format 1_1 and DCI format 1_2.
  • a second TPC command (Second TPC command for scheduled PUCCH) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, if the upper layer parameter SecondTPCFieldDCI is set, a second TPC command (Second TPC command for scheduled PUCCH) field may be included in DCI format 1_1.
  • DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be DCI formats for scheduling the PDSCH.
  • DCI format 1_0 may be used for scheduling the PDSCH in one downlink cell.
  • the antenna port field may be included in DCI format 1_1 and DCI format 1_2.
  • the number of information bits constituting the antenna port field may be 4, 5, or 6 bits.
  • the number of information bits constituting the antenna port field may be 4, 5, 6, or 7 bits.
  • the number of information bits constituting the antenna port field may be 4, 5, 6, 7, or 8 bits.
  • the number of CDM groups without data may be any of value 1, value 2, and value 3.
  • the number of CDM groups without data with value 1 may refer to CDM group 0.
  • the number of CDM groups without data with value 2 may refer to CDM group ⁇ 0, 1 ⁇ .
  • the number of CDM groups without data with value 3 may refer to CDM group ⁇ 0, 1, 2 ⁇ .
  • the upper layer parameter dmrs-Type being 1 may mean that DMRS configuration type 1 is set.
  • the upper layer parameter dmrs-Type being 2 may mean that DMRS configuration type 2 is set.
  • the upper layer parameter maxLength being 1 may mean that the maximum number of forward DMRS symbols is 1 symbol.
  • the upper layer parameter maxLength being 2 may mean that the maximum number of forward DMRS symbols is 2 symbols.
  • the upper layer parameter maxLength being 1 may mean that a single-symbol forward DMRS (forward DMRS symbol) is set.
  • the upper layer parameter maxLength being 2 may mean that a single-symbol forward DMRS (forward DMRS symbol) or a double-symbol forward DMRS is set.
  • the number of DMRS ports may be the number of layers (number of transmission layers) v.
  • Antenna ports ⁇ p0,...,pv-1 ⁇ (antenna port value, antenna port number) may be the sum of DMRS ports (DMRS port value, DMRS port number) and 1000.
  • the TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, if an upper layer parameter is configured, the TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, if the upper layer parameter tci-PresentInDCI is configured, the TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. One or two TCI states may be indicated by the DCI format. One or more (e.g., two) TCI states may be indicated by the TCI field in the DCI format.
  • the TCI indication field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when higher layer parameters are configured, the TCI indication field may be included in the DCI format.
  • the TCI indication field may apply one or two indicated TCI states to the PDSCH. For example, when the TCI indication field indicates "00", a first indicated TCI state may be applied to the PDSCH. For example, when the TCI indication field indicates "01", a second indicated TCI state may be applied to the PDSCH. For example, when the TCI indication field indicates "10", a first indicated TCI state and a second indicated TCI state may be applied to the PDSCH.
  • DCI formats 0_0/0_1/0_2 may be used for scheduling PUSCH.
  • a BWP indication (Bandwidth part indicator) field may be included in part or all of DCI format 0_1 and DCI format 0_2. The number of information bits constituting the BWP indication field may be determined based on the number of UL BWPs.
  • a TPC command (TPC command for scheduled PUSCH) field may be included in one or both of DCI format 0_1 and DCI format 0_2.
  • a second TPC command (Second TPC command for scheduled PUSCH) field may be included in one or both of DCI format 0_1 and DCI format 0_2. For example, if the upper layer parameter SecondTPCFieldDCI is set, a second TPC command (Second TPC command for scheduled PUSCH) field may be included in DCI format 1_1.
  • An SRS resource indicator field may be included in one or both of DCI format 0_1 and DCI format 0_2.
  • An SRS resource set indicator field may be included in one or both of DCI format 0_1 and DCI format 0_2. If the SRS resource set indicator field indicates 0 ("00"), the SRS resource indicator field and the fields for precoding information and number of layers may relate to a first SRS resource set. If the SRS resource set indicator field indicates 1 ("01"), the SRS resource indicator field and the fields for precoding information and number of layers may relate to a second SRS resource set. If the SRS resource set indicator field indicates 2 ("10"), the SRS resource indicator field and the fields for precoding information and number of layers may relate to a first SRS resource set.
  • the second SRS resource indication field and the second "precoding information and number of layers field" may be associated with a second SRS resource set. If the SRS resource set indication field indicates 3 ("11"), the SRS resource indication field and the precoding information and number of layers field may be associated with a first SRS resource set. If the SRS resource set indication field indicates 3 ("11"), the second SRS resource indication field and the second "precoding information and number of layers field” may be associated with a second SRS resource set.
  • the terminal device 1 transmits an uplink physical channel/signal (e.g., PUSCH, PUCCH, SRS) based on an uplink timing (Timing Advance: TA). Furthermore, one uplink timing may belong to one TAG/subTAG. One TAG/subTAG may be associated with one TAG ID/subTAG ID and may be identified by one TAG ID/subTAG ID. Therefore, as a problem, when the terminal device 1 transmits an uplink physical channel/signal in a random access procedure, one TAG ID/subTAG ID needs to be indicated or determined. As a means for solving the problem, one aspect of the present invention may be used for determining a TAG ID/suTAG ID when two uplink timings are provided in one serving cell.
  • an uplink physical channel/signal e.g., PUSCH, PUCCH, SRS
  • FIG. 14 is a diagram showing an example of TCI state management according to one aspect of this embodiment. Each black circle in FIG. 14 may represent one TCI state.
  • One or more TCI states 1000 may be configured by higher layer parameters.
  • one or more UL TCI states may be configured by higher layer parameters for each uplink BWP (BWP-UplinkDedicated).
  • BWP-UplinkDedicated For example, one or more DL/Joint TCI states (TCI-State) may be configured by higher layer parameters for each PDSCH configuration (PDSCH-Config).
  • One TCI state may be associated with one TCI state ID.
  • one UL TCI state may be associated with one UL TCI state ID (TCI-UL-State-Id, UL-TCIState-Id).
  • TCI-state may be associated with one TCI state ID (TCI-stateId).
  • TCI state ID TCI-stateId
  • TCI states 1000 One or more TCI states configured by higher layer parameters may be configured TCI states 1000.
  • Each TCI state 1000 may contain one TAG ID or subTAG ID.
  • One or more TCI states 1001 may be part or all of one or more TCI states 1000.
  • One or more TCI states 1001 may be activated by a MAC CE (e.g., an activation command).
  • the PDSCH may carry a first transport block.
  • the first transport block may be a MAC PDU.
  • the MAC PDU may include an activation command or a MAC CE referred to as an activation command.
  • the activation command may be an activation command D or an activation command E.
  • One or more TCI states and one or both of one or more "TCI state pairs" may be mapped to one or more code points.
  • one or more TCI states and one or both of one or more "TCI state pairs" may be mapped to one or more code points by an activation command.
  • Each TCI state or each TCI state pair may be mapped to one code point.
  • each TCI state or each TCI state pair may be mapped to one code point by an activation command.
  • the code point to which the TCI state or pair of TCI states is mapped may be a code point in a TCI field.
  • the code point to which the TCI state or pair of TCI states is mapped may be a code point in a TCI field in DCI format 1_1 or DCI format 1_2.
  • the code point to which the TCI state or pair of TCI states is mapped may be a code point in a TCI field in DCI 1040.
  • a TCI state or pair of TCI states may be mapped to a code point in a TCI field in DCI 1040 by an activation command in a CORESET pool index to which DCI 1040 is associated.
  • the TCI state activated by a MAC CE activation command
  • the TCI state mapped to a code point in a TCI field may be the activated TCI state 1001.
  • activation command E may be used. If the CORESET pool index (coresetPoolIndex) is not set in one or more CORESETs (ControlResourceSets), activation command E may be used. If the CORESET pool index (coresetPoolIndex) is set in one or more CORESETs (ControlResourceSets), activation command D or activation command E may be used. For example, in single-DCI mode, activation command E may be used. For example, in multi-DCI mode, activation command D may be used. For example, in both single-DCI mode and multi-DCI mode, activation command E may be used.
  • the one or more TCI states 1002 may be some or all of the one or more TCI states 1001.
  • the one or more TCI states 1002 may be indicated by DCI 1040.
  • DCI 1040 may be DCI format 1_1 or DCI format 1_2.
  • DCI 1040 may include a Transmission configuration indication (TCI) field.
  • TCI field may indicate one or more (e.g., two or four) TCI states. For example, one value of the TCI field may correspond to one code point of the TCI field.
  • the TCI state indicated by DCI 1040 may be an indicated TCI state 1002.
  • the indicated TCI state 1002 may be some or all of a UL TCI state, a DL TCI state, and a Joint TCI state.
  • the UL TCI state may be a TCI state for PUSCH, PUCCH, and SRS.
  • the DL TCI state may be the TCI state for PDSCH, PDCCH, and CSI-RS.
  • the Joint TCI state may be the TCI state for PUSCH, PUCCH, SRS, PDSCH, PDCCH, and CSI-RS.
  • the number of indicated TCI states 1002 may be four.
  • the indicated TCI states 1002 may be a first pair of a first UL TCI state and a first DL TCI state, and a second pair of a second UL TCI state and a second DL TCI state.
  • the first pair may be associated with a first TRP.
  • the second pair may be associated with a second TRP.
  • the number of indicated TCI states 1002 may be three.
  • the indicated TCI states 1002 may be a first pair of a first UL TCI state and a first DL TCI state, and a third DL/UL/Joint TCI state.
  • the first pair may be associated with a first TRP and the third DL/UL/Joint TCI state may be associated with a second TRP.
  • the first pair may be associated with a second TRP and the third DL/UL/Joint TCI state may be associated with the first TRP.
  • the number of indicated TCI states 1002 may be two.
  • the indicated TCI states 1002 may be a first DL/UL/Joint TCI state and a second DL/UL/Joint TCI state.
  • the first DL/UL/Joint may be associated with a first TRP and the second DL/UL/Joint TCI state may be associated with a second TRP.
  • the number of indicated TCI states 1002 may be two.
  • the indicated TCI states 1002 may be a first pair of a first DL TCI state and a first UL TCI state.
  • the first pair may be associated with a first TRP.
  • the first pair may be associated with a second TRP.
  • the number of indicated TCI states 1002 may be one.
  • the indicated TCI state 1002 may be a first DL/UL/Joint TCI state.
  • the first DL/UL/Joint may not be associated with a TRP.
  • the first DL/UL/Joint TCI state may be associated with a first TRP.
  • the first DL/UL/Joint TCI state may be associated with a second TRP.
  • the indicated TCI state 1002 may be applied from the first slot N symb symbols after the last OFDM symbol of the PUCCH. For example, the indicated TCI state 1002 may be applied from the first slot N symb symbols after the last OFDM symbol of the PUCCH whose transmission is indicated by the DCI 1040. The indicated TCI state 1002 may be applied to multiple channels/signals. N symb may be BeamAppTime. For example, if the DCI 1040 is associated with a CORESET pool index 1080, the indicated TCI state 1002 may be a first indicated TCI state 1010. For example, if the DCI 1040 is associated with a CORESET pool index 1081, the indicated TCI state 1002 may be a second indicated TCI state 1011.
  • Some of the one or more TCI states 1002 may be applied to an uplink channel (uplink physical channel) 1070.
  • the "indicated TCI state 1002" applied to the uplink channel 1070 may be one or both of one or more UL TCI states and one or more Joint TCI states.
  • the "indicated TCI state” 1002 applied to the uplink channel 1070 may be the "applied TCI state 1020".
  • the indicated TCI state 1002 may include at least TCI state 1010 and TCI state 1011.
  • TCI state 1010 and TCI state 1011 may be applied to the uplink channel 1070.
  • TCI state 1010 and TCI state 1011 applied to the uplink channel 1070 may be TCI state 1020.
  • FIG. 15 is a diagram showing an example of a random access procedure according to one aspect of the present embodiment.
  • the terminal device 1 may receive a PDCCH 1031.
  • the terminal device 1 may receive a PDCCH 1031 in which a DCI 1041 is arranged.
  • the DCI 1041 may be DCI format 1_0.
  • the PDCCH 1031 may be a PDCCH order.
  • the PDCCH 1031 may initiate or trigger a random access procedure 1100.
  • the PDCCH 1031 may trigger the transmission of a PRACH 1050.
  • the random access procedure 1100 may be triggered by the PDCCH 1031 in response to a transmission request of the PRACH 1050.
  • two TAs may be set.
  • the PDCCH 1031 may indicate one RACH configuration. For example, if an inter-cell Multi-TRP mode is configured, the PDCCH 1031 may indicate one RACH configuration. Based on the SS/PBCH index indicated by the PDCCH 1031 or the DCI 1041, a TAG or TAG ID associated with the random access procedure 1100 may be identified.
  • the terminal device 1 may transmit PRACH 1050.
  • the terminal device 1 may transmit PRACH 1050 in the random access procedure 1100.
  • the terminal device 1 may transmit PRACH 1050 in the PRACH resource.
  • the PL-RS (Pathloss reference signal) for PRACH1050 may be SSB as indicated by PDCCH1031.
  • the terminal device 1 may receive PDCCH1032.
  • the terminal device 1 may receive PDCCH1032 in which DCI1042 is placed.
  • the terminal device 1 may receive PDCCH1032 in response to the transmission of PRACH1050.
  • the terminal device 1 may detect DCI1042.
  • the terminal device 1 may attempt to detect DCI format 1_0 with a CRC scrambled by the RA-RNTI in response to the transmission of PRACH1050.
  • the CORESET corresponding to PDCCH1032 may be associated with a Type 1 PDCCH common search space set. If two TA is configured, PDCCH1032 or the DMRS port of PDCCH1032 may be associated with the QCL information of the CORESET associated with the Type 1 PDCCH common search space set. If two TA is not configured, PDCCH1031 and PDCCH1032 may be associated with the same QCL assumption.
  • applyIndicatedTCIState may be set for the CORESET corresponding to PDCCH1032. For example, if multi-DCI mode is not configured, applyIndicatedTCIState may be set for the CORESET corresponding to PDCCH1032. If applyIndicatedTCIState indicates "first”, the first indicated TCI state 1010 may be applied to PDCCH1032. If applyIndicatedTCIState indicates "second”, the second indicated TCI state 1011 may be applied to PDCCH1032. It may not be expected that applyIndicatedTCIState will indicate "both”.
  • the TCI state to be applied to the PDCCH 1032 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the multi-DCI mode is configured, the TCI state to be applied to the PDCCH 1032 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to the CORESET pool index 1080, the first indicated TCI state 1010 may be applied to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to the CORESET pool index 1081, the second indicated TCI state 1011 may be applied to the PDCCH 1032.
  • the terminal device 1 may receive the PDSCH 1060.
  • the DCI 1042 may schedule the PDSCH 1060 or the reception of the PDSCH 1060.
  • the DCI 1042 may instruct the reception of the PDSCH 1060.
  • the terminal device 1 may receive a transport block 1090 in the PDSCH 1060 in response to detection of the DCI 1042.
  • the terminal device 1 may pass the transport block 1090 to an upper layer.
  • the transport block 1090 may include a random access response (RAR) 1110 or may include a RAR message 1110.
  • the terminal device 1 may obtain a random access response (UL) grant (RAR UL grant) 1120 based on the transport block 1090. That is, terminal device 1 may receive RAR1110 in PDSCH1060.
  • the terminal device 1 may receive a TA command 1130.
  • the TA command 1130 may be included in the RAR 1110.
  • the TA command 1130 may be associated with one TAG ID or one subTAG ID.
  • the one TAG ID or one subTAG ID may be included in the RAR 1110.
  • the one TAG ID or one subTAG ID may be determined based on the SSB indicated by the PDCCH order 1031. If two TAs are configured, the TA command 1130 may be associated with one of the two TAG IDs/subTAG IDs.
  • the two TAG IDs/subTAG IDs may be determined for one serving cell.
  • applyIndicatedTCIState may be set for the PDSCH 1060. For example, if multi-DCI mode is not set, applyIndicatedTCIState may be set for the PDSCH 1060. If applyIndicatedTCIState indicates "first”, the first indicated TCI state 1010 may be applied to the PDSCH 1060. If applyIndicatedTCIState indicates "second", the second indicated TCI state 1011 may be applied to the PDSCH 1060. If an SFN technique is applied for the PDSCH 1060 and if applyIndicatedTCIState indicates "both", the first indicated TCI state 1010 and the second indicated TCI state 1011 may be applied to the PDSCH 1060. If an SFN technique is not applied for the PDSCH 1060, applyIndicatedTCIState may not be expected to indicate "both".
  • the TCI state applied to the PDSCH 1060 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the multi-DCI mode is configured, the TCI state applied to the PDSCH 1060 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to the CORESET pool index 1080, the first indicated TCI state 1010 may be applied to the PDSCH 1060. For example, when the CORESET of the PDCCH 1032 corresponds to the CORESET pool index 1081, the second indicated TCI state 1011 may be applied to the PDSCH 1060.
  • the terminal device 1 may transmit a PUSCH 1071.
  • the PUSCH 1071 or the transmission of the PUSCH 1071 may be scheduled by an RAR UL grant 1110.
  • the RAR UL grant 1110 may instruct the transmission of the PUSCH 1071.
  • the PUSCH 1071 may be a Msg3 PUSCH (message 3 PUSCH).
  • the uplink channel 1070 may be a PUSCH 1071.
  • a case may be assumed in which the unified TCI state is not set. Also, in the means 1-1, 1-2, 1-3, and 1-4, a case may be assumed in which the unified TCI state is set and the two indicated TCI states are not maintained. Also, in the means 1-1, 1-2, 1-3, and 1-4, a case may be assumed in which two TAs are set and the unified TCI state is not set. Also, in the means 1-1, 1-2, 1-3, and 1-4, a case may be assumed in which two TAs are set and the unified TCI state is set and the two indicated TCI states are not maintained.
  • the random access procedure 1100 may not be triggered. In means 1-1, if two TAs are set, it may not be expected that the unified TCI state is not set.
  • the random access procedure 1100 may be a random access procedure for two TAs/TAGs.
  • the random access procedure 1100 may be a random access procedure in a multi-DCI mode.
  • the two indicated TCI states may be TCI state 1010 and TCI state 1011.
  • PUSCH1071 does not need to be transmitted.
  • PUSCH 1071 may be transmitted.
  • one uplink timing for PUSCH 1071 may be determined.
  • the transmission of PUSCH 1071 may correspond to one uplink timing.
  • the transmission of PUSCH 1071 may correspond to a first uplink timing.
  • the uplink timing for transmitting PUSCH 1071 may be determined regardless of the TAG ID to which the TA command 1130 is associated.
  • the TA command 1130 or the TAG ID to which the TA command 1130 is associated may be ignored in determining the uplink timing for transmitting PUSCH 1071.
  • two uplink timings may be determined.
  • the uplink timings may be referred to as timing adjustments.
  • Corresponding to one uplink timing may correspond to one or both of one TA and one TAG.
  • PUSCH 1071 may be transmitted.
  • one uplink timing for PUSCH 1071 may be determined.
  • the transmission of PUSCH 1071 may correspond to one uplink timing.
  • the uplink timing for PUSCH 1071 may be determined based on the TAG ID to which the TA command 1130 is associated. For example, if the TAG ID included in RAR 1110 has a first value, a first uplink timing may be applied to PUSCH 1071. For example, if the TAG ID included in RAR 1110 has a second value, a second uplink timing may be applied to PUSCH 1071.
  • a first uplink timing may be applied to PUSCH 1071.
  • the second uplink timing may be applied to the PUSCH 1071.
  • a case may be assumed in which a unified TCI state is set. Also, in the means 2-1 and 2-2, a case may be assumed in which a unified TCI state is set and two indicated TCI states are held. Also, in the means 2-1 and 2-2, a case may be assumed in which two TAs are set and a unified TCI state is set. Also, in the means 2-1 and 2-2, a case may be assumed in which two TAs are set and a unified TCI state is set and two indicated TCI states are held.
  • PUSCH 1071 may be transmitted.
  • one uplink timing for PUSCH 1071 may be determined.
  • the transmission of PUSCH 1071 may correspond to one uplink timing.
  • the uplink timing for PUSCH 1071 may be determined based on a TAG ID to which the TA command 1130 is associated.
  • the uplink timing for PUSCH 1071 may be determined based on a TAG ID to which the TA command 1130 is associated. For example, if the TAG ID included in RAR 1110 is a first value, a first uplink timing may be applied to PUSCH 1071.
  • a second uplink timing may be applied to PUSCH 1071.
  • a first uplink timing may be applied to PUSCH 1071.
  • a second uplink timing may be applied to PUSCH 1071.
  • the TAG ID/subTAG ID included in the TCI state applied to PUSCH 1071 may be ignored.
  • PUSCH 1071 may be transmitted.
  • one uplink timing for PUSCH 1071 may be determined.
  • the transmission of PUSCH 1071 may correspond to one uplink timing.
  • one uplink timing for PUSCH 1071 may be determined based on a TAG ID (or subTAG ID) included in a TCI state applied to PUSCH 1071. For example, when a first TCI state 1010 is applied to PUSCH 1071, a first uplink timing may be applied to PUSCH 1071. For example, when a second TCI state 1011 is applied to PUSCH 1071, a second uplink timing may be applied to PUSCH 1071.
  • a TAG ID associated with a TA command 1130 may be ignored.
  • a case may be assumed in which a unified TCI state is set. Also, in the means 3-1, 3-2, and 3-3, a case may be assumed in which a unified TCI state is set and two indicated TCI states are maintained.
  • one of the first indicated TCI state 1010 and the second indicated TCI state 1011 may be applied to the PUSCH 1071.
  • applyIndicatedTCIState may be set for the PUSCH 1071.
  • applyIndicatedTCIState indicates "first”
  • the first indicated TCI state 1010 may be applied to the PUSCH 1071.
  • applyIndicatedTCIState indicates "second”
  • the second indicated TCI state 1011 may be applied to the PUSCH 1071. It may not be expected that applyIndicatedTCIState for the PUSCH 1071 indicates "both".
  • one of the first indicated TCI state 1010 and the second indicated TCI state 1011 may be applied to the PUSCH 1071.
  • the TCI state applied to the PUSCH 1071 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032.
  • the TCI state applied to the PUSCH 1071 may be determined based on the CORESET pool index of the CORESET corresponding to the PDCCH 1032.
  • the first indicated TCI state 1010 may be applied to the PUSCH 1071.
  • the second indicated TCI state 1011 may be applied to the PUSCH 1071.
  • the first indicated TCI state 1010 may be applied to the PUSCH 1071.
  • the first indicated TCI state 1010 and the second indicated TCI state are held, the first indicated TCI state 1010 may be applied to the PUSCH 1071.
  • two subTAG IDs may be configured by higher layer parameters.
  • the first subTAG ID may be associated with one of the M TAG IDs.
  • the second subTAG ID may be associated with one of the M TAG IDs.
  • the first subTAG ID may correspond to one or both of the first TCI state 1010 and the first CORESET pool index 1080.
  • the second subTAG ID may correspond to one or both of the second TCI state 1011 and the second CORESET pool index 1081.
  • the terminal device 1 may adjust the uplink timing for the PUSCH 1071. For example, in response to receiving a TA command 1130 for the TAG, the terminal device 1 may adjust the uplink timing.
  • the TA command 1130 may be received by a random access response or a MAC CE.
  • the TAG may correspond to a first TAG ID or a second TAG ID.
  • the first TAG and the second TAG may be provided in one serving cell.
  • Any of ⁇ Means 1-1, Means 1-2, Means 1-3, Means 1-4 ⁇ , any of ⁇ Means 2-1, Means 2-2 ⁇ , and any of ⁇ Means 3-1, Means 3-2, Means 3-3, Means 3-1 and Means 3-2 ⁇ may be combined.
  • the terminal device 1 may include a receiving unit that receives a PDSCH including an RAR.
  • the RAR may include some or all of an RAR UL grant, a TA command, a TAG ID, and a subTAG ID.
  • the terminal device 1 may include a transmitting unit that transmits a PUSCH scheduled by the RAR UL grant.
  • the PUSCH scheduled by the RAR UL grant may be an Msg3 PUSCH.
  • a unified TCI state may be set for the terminal device 1.
  • Setting the unified TCI state may mean setting one or both of dl-OrJointTCI-StateList and TCI-UL-State. If two TAs are set, it may not be expected that the unified TCI state will not be set.
  • the terminal device 1 may hold a first TCI state and a second TCI state.
  • Each of the first TCI state and the second TCI state may be determined from multiple TCI states set by dl-OrJointTCI-StateList or TCI-UL-State.
  • each of the first TCI state and the second TCI state may be a UL TCI state or a Joint TCI state.
  • Each of the first TCI state and the second TCI state may be a "indicated TCI state". If the unified TCI state is set, the first TCI state and the second TCI state may be held.
  • the first TCI state may correspond to or be associated with a first TAG.
  • a first TAG ID or a first subTAG ID may be configured for the first TCI state.
  • the second TCI state may correspond to or be associated with a second TAG.
  • a second TAG ID or a second subTAG ID may be configured for the second TCI state.
  • the TA command may be associated with the first TAG ID or the second TAG ID.
  • the TA command may be associated with the first subTAG ID or the second subTAG ID.
  • the TA command may also be associated with the first TAG or the second TAG.
  • the RAR may be associated with the first TAG ID or the second TAG ID.
  • the RAR may be associated with the first subTAG ID or the second subTAG ID.
  • the RAR may also be associated with the first TAG or the second TAG.
  • a first uplink timing or a second uplink timing may be determined for the Msg3 PUSCH.
  • the first uplink timing may correspond to some or all of the first TAG, the first subTAG, the first TAG ID, and the first subTAG ID.
  • the second uplink timing may correspond to some or all of the second TAG, the second subTAG, the second TAG ID, and the second subTAG ID.
  • the first TAG or the second TAG may be applied for the Msg3 PUSCH.
  • One of a first TCI state and a second TCI state may be applied for the Msg3 PUSCH. If the first TCI state applies to the Msg3 PUSCH and the RAR is associated with a first TAG, the first TAG may correspond to or be applied to the Msg3 PUSCH. If the first TCI state applies to the Msg3 PUSCH and the RAR is associated with a second TAG, the first TAG may correspond to or be applied to the Msg3 PUSCH. If the second TCI state applies to the Msg3 PUSCH and the RAR is associated with the first TAG, the second TAG may correspond to or be applied to the Msg3 PUSCH.
  • the second TAG may correspond to or be applied to the Msg3 PUSCH.
  • the first TAG corresponding to the Msg3 PUSCH may mean that the first uplink timing corresponds to the Msg3 PUSCH.
  • the second TAG corresponding to the Msg3 PUSCH may mean that the second uplink timing corresponds to the Msg3 PUSCH.
  • the RAR may be associated with a first TAG. However, if a unified TCI state is not configured, the RAR may not be expected to be associated with a second TAG. For example, if a unified TCI state is not configured, the first TAG may be applied to the Msg3 PUSCH. However, if a unified TCI state is not configured, the second TAG may not be expected to be applied to the Msg3 PUSCH.
  • the terminal device 1 may receive a first PDCCH in which a first DCI is placed.
  • the terminal device 1 may receive a second PDCCH in which a second DCI is placed.
  • the second DCI may schedule a PDSCH including an RAR.
  • the terminal device 1 may receive a PDSCH including an RAR.
  • the terminal device 1 may transmit a PUSCH.
  • one of the first TCI state and the second TCI state may be applied to the PUSCH.
  • the first TCI state may be applied to the PUSCH.
  • the second TCI state may be applied to the PUSCH.
  • the first TCI state may be applied to the PUSCH.
  • the PUSCH is scheduled by the first DCI and the first DCI involves a scrambled CRC by at least any of the C-RNTI, CS-RNTI, and MCS-C-RNTI
  • one or both of the first TCI state and the second TCI state may be applied to the PUSCH.
  • the first TCI state may be applied to the PUSCH.
  • the second TCI state may be applied to the PUSCH.
  • both the first TCI state and the second TCI state may be applied to the PUSCH.
  • the first TCI state may be applied to the PUSCH.
  • the second TCI state may be applied to the PUSCH.
  • one of the first TCI state and the second TCI state may be applied to PUSCH. If two TA is not configured, the first TCI state may be applied to PUSCH and the second TCI state may not be applied to PUSCH. If multi-DCI mode is not configured, the first TCI state may be applied to PUSCH and the second TCI state may not be applied to PUSCH. If two TA is configured or multi-DCI mode is configured, one of the first TCI state and the second TCI state may be applied to PUSCH based on the CORESET pool index.
  • the first TCI state may be applied to PUSCH.
  • the second TCI state may be applied to PUSCH.
  • one of the first TCI state and the second TCI state may be applied to the PUSCH based on a higher layer parameter.
  • the higher layer parameter may be applyIndicatedTCIState.
  • the applyIndicatedTCIState may be set for one BWP.
  • the programs operating in the base station device 3 and terminal device 1 relating to one aspect of the present invention may be programs (programs that cause a computer to function) that control a CPU (Central Processing Unit) or the like 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 RAM (Random Access Memory) during processing, and is then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.
  • a part of the terminal device 1 and the base station device 3 in the above-mentioned embodiment may be realized by a computer.
  • 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. Additionally, “computer-readable recording media” refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems.
  • “computer-readable recording medium” may 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 certain 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 be one that realizes part of the functions described above, or may be 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 a collection (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 the 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 a collection.
  • the base station device 3 in the above-mentioned embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and/or NG-RAN (NextGen RAN, NR RAN).Furthermore, the base station device 3 in the above-mentioned embodiment may have some or all of the functions of an upper node for eNodeB and/or gNB.
  • EUTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN NextGen RAN, NR RAN
  • gNB NextGen RAN
  • some or all of the terminal device 1 and base station device 3 may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all may be integrated into a chip.
  • 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 appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.
  • 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.
  • 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, etc.
  • 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
  • program e.g., a program, etc.
  • Reference Signs List 1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transceiver unit 10a, 30a Radio transmitter unit 10b, 30b Radio receiver 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 91, 92, 93, 94 Search space set 300 Component carrier 301 Primary cell 302, 303 Secondary cell 700 Set of resource elements for PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of resource elements for SSS 3000 Points 3001, 3002 Resource grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common resource block set 1000 Set TCI state 1001 Activated TCI state 1002, 1010, 1011 Indicated TCI state 1020 Applied TCI state 1030, 1031, 1032 PDCCH 1040, 1041, 1042 DCI 1050 PRACH 1060

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention comprend : une unité de réception qui reçoit un premier PDCCH dans lequel des premières DCI sont placées ou reçoit un PDSCH comprenant une RAR ; et une unité d'émission qui émet un PUSCH, si un premier état TCI et un second état TCI sont maintenus, le PUSCH étant planifié par les premières DCI, et si les premières DCI sont accompagnées d'un CRC qui est brouillé par le TC-RNTI, l'un parmi le premier état TCI et le second état TCI étant appliqué au PUSCH, si le PUSCH est planifié par les premières DCI et que les premières DCI sont accompagnées d'un CRC qui est brouillé par au moins l'un parmi un C-RNTI, un CS-RNTI et un MCS-C-RNTI, l'un ou les deux du premier état TCI et du second état TCI étant appliqués au PUSCH, et si le PUSCH est planifié par une autorisation UL RAR dans la RAR, l'un parmi le premier état TCI et le second état TCI étant appliqué au PUSCH.
PCT/JP2024/025843 2023-07-18 2024-07-18 Dispositif terminal, dispositif de station de base et procédé de communication Pending WO2025018400A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-116384 2023-07-18
JP2023116384 2023-07-18

Publications (1)

Publication Number Publication Date
WO2025018400A1 true WO2025018400A1 (fr) 2025-01-23

Family

ID=94282317

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/025843 Pending WO2025018400A1 (fr) 2023-07-18 2024-07-18 Dispositif terminal, dispositif de station de base et procédé de communication

Country Status (1)

Country Link
WO (1) WO2025018400A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220006575A1 (en) * 2020-07-01 2022-01-06 Samsung Electronics Co., Ltd. Mechanisms and conditions for supporting repetitions for a pucch transmission
JP2023517732A (ja) * 2020-03-16 2023-04-26 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいてｐｕｓｃｈ送受信方法及び装置
JP2023068721A (ja) * 2021-11-04 2023-05-18 シャープ株式会社 端末装置、基地局装置、および、通信方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023517732A (ja) * 2020-03-16 2023-04-26 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおいてｐｕｓｃｈ送受信方法及び装置
US20220006575A1 (en) * 2020-07-01 2022-01-06 Samsung Electronics Co., Ltd. Mechanisms and conditions for supporting repetitions for a pucch transmission
JP2023068721A (ja) * 2021-11-04 2023-05-18 シャープ株式会社 端末装置、基地局装置、および、通信方法

Similar Documents

Publication Publication Date Title
WO2021162045A1 (fr) Équipement terminal, dispositif de station de base et procédé de communication
JP2024094447A (ja) 端末装置、基地局装置、および、通信方法
EP4598160A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
EP4568398A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
JP7747492B2 (ja) 端末装置、基地局装置、および、通信方法
WO2024135009A1 (fr) Dispositif terminal et dispositif de station de base
JP2024160191A (ja) 端末装置、および、基地局装置
WO2025018400A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2025018395A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
US20250247844A1 (en) Terminal apparatus, base station apparatus, and communication method
WO2025094662A1 (fr) Équipement terminal et dispositif de station de base
EP4510719A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024210181A1 (fr) Dispositif terminal et dispositif de station de base
WO2024090181A1 (fr) Équipement de terminal et dispositif de station de base
WO2024090180A1 (fr) Dispositif terminal
WO2025173545A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2025173306A1 (fr) Dispositif terminal et dispositif de station de base
WO2025173304A1 (fr) Équipement terminal et dispositif de station de base
WO2025173546A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
JP2025170449A (ja) 端末装置、および、基地局装置
WO2024062939A1 (fr) Équipement terminal et dispositif de station de base
WO2025063126A1 (fr) Équipement terminal, dispositif de station de base et procédé de communication
WO2024135008A1 (fr) Dispositif terminal et dispositif de station de base
WO2024171523A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2025210971A1 (fr) Équipement terminal et dispositif de station de base

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24843188

Country of ref document: EP

Kind code of ref document: A1