Terminal device and base station device

Abstract

The present invention comprises: a reception unit that receives a PDCCH order that triggers a random access procedure; and a transmission unit that transmits either a first random access preamble, a second random access preamble, or a third random access preamble in the random access procedure. The PDCCH order includes a PCI instruction field when TwoTA is configured. The PDCCH order includes a cell instruction field when early UL synchronization is configured. The first random access preamble is used when the PCI instruction field indicates a first value. The second random access preamble is used when the PCI instruction field indicates a second value. The first random access preamble is used when the cell instruction field indicates the first value. The third random access preamble is used when the cell instruction field indicates the second value. The size of the cell instruction field is not expected to be 1 bit or more when the size of the PCI instruction field is 1 bit or more.

Description

Terminal device and base station device

[0001] The present invention relates to a terminal device and a base station device. This application claims priority to Japanese Patent Application No. 2023-185304, filed on October 30, 2023, the contents of which are incorporated herein by reference.

[0002] The radio access method and radio network for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is being developed by the Third Generation Partnership Project (3GPP). rd This is being studied under the LTE Generation Partnership Project (registered trademark). In LTE, base station devices are also called eNodeBs (evolved NodeBs), and terminal devices are also called UEs (User Equipment). LTE is a cellular communication system in which multiple areas covered by base station devices are arranged in the form of cells. A single base station device may manage multiple serving cells.

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

[0004] 3GPP is currently studying the extension of services supported by NR (Non-Patent Document 2 and Non-Patent Document 3).

[0005] "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. “Release 17 package for RAN”, RP-193216, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #86, Sitges, Spain, 9th ― 12th December, 2019 “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 Chairman, 3GPP TSG RAN Meeting #94-e, 6th ― 17th December, 2021

[0006] The present invention provides a terminal device that performs efficient communication, a communication method used in the terminal device, a base station device that performs efficient communication, and a communication method used in the base station device.

[0007] (1) A first aspect of the present invention is a terminal device comprising: a receiving unit that receives a PDCCH order that triggers a random access procedure; and a transmitting unit that transmits one of a first random access preamble, a second random access preamble, and a third random access preamble in the random access procedure, wherein when TwoTA is configured, the PDCCH order includes a PCI indication field; when early UL synchronization is configured, the PDCCH order includes a cell indication field; when the PCI indication field indicates a first value, the first random access preamble is used; when the PCI indication field indicates a second value, the second random access preamble is used; when the cell indication field indicates the first value, the first random access preamble is used; when the cell indication field indicates the second value, the third random access preamble is used; and when the size of the PCI indication field is 1 bit or more, it is not expected that the size of the cell indication field is 1 bit or more.

[0008] (2) Also, a second aspect of the present invention is a base station device comprising: a transmitter that transmits a PDCCH order that triggers a random access procedure; and a receiver that receives any one of a first random access preamble, a second random access preamble, and a third random access preamble in the random access procedure, wherein when TwoTA is configured, the PDCCH order includes a PCI indication field; when early UL synchronization is configured, the PDCCH order includes a cell indication field; when the PCI indication field indicates a first value, the first random access preamble is used; when the PCI indication field indicates a second value, the second random access preamble is used; when the cell indication field indicates the first value, the first random access preamble is used; when the cell indication field indicates the second value, the third random access preamble is used; and when the size of the PCI indication field is 1 bit or more, it is not expected that the size of the cell indication field is 1 bit or more.

[0009] According to the present invention, the terminal device can perform communication efficiently, and the base station device can perform communication efficiently.

[0010] 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. The subcarrier spacing setting μ and the number of OFDM symbols per slot N according to an aspect of the present embodiment are shown. slot symb, and an example showing a relationship between CP (cyclic prefix) configuration. FIG. 1 is a diagram showing an example of a method for configuring a resource grid according to an aspect of the present embodiment. FIG. 2 is a diagram showing an example of the configuration of a resource grid 3001 according to an aspect of the present embodiment. FIG. 3 is a schematic block diagram showing an example of the configuration of a base station device 3 according to an aspect of the present embodiment. FIG. 4 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. FIG. 5 is a diagram showing an example of the configuration of an SS / PBCH block according to an aspect of the present embodiment. FIG. 6 is a diagram showing an example of a monitoring opportunity for a search space set according to an aspect of the present embodiment. FIG. 7 is a diagram showing an example of an activation command A according to an aspect of the present embodiment. FIG. 8 is a diagram showing an example of an activation command B according to an aspect of the present embodiment. FIG. 9 is a diagram showing an example of an activation command C according to an aspect of the present embodiment. FIG. 10 is a diagram showing an example of an activation command D according to an aspect of the present embodiment. FIG. 11 is a diagram showing an example of an activation command E according to an aspect of the present embodiment. FIG. 12 is a diagram showing an example of TCI state management according to an aspect of the present embodiment. FIG. 13 is a diagram showing an example of a random access procedure according to an aspect of the present embodiment.

[0011] Hereinafter, an embodiment of the present invention will be described.

[0012] floor(C) may be a floor function for real number C. For example, 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. For example, 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, where e is Napier's constant. H^I denotes H to the Ith power. max(J,K) is a function that outputs the maximum value of J and K. Here, max(J,K) is a function that outputs J or K when J and K are equal. min(L,M) is a function that outputs the maximum value of L and M. Here, min(L,M) is a function that outputs L or M when L and M are equal. round(N) is a function that outputs the integer value closest to N. "·" indicates multiplication.

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

[0014] The OFDM symbol may be a name including a CP added to the OFDM symbol. In other words, a certain OFDM symbol may be configured to include the certain OFDM symbol and the CP added to the certain OFDM symbol.

[0015] Fig. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In Fig. 1, the wireless communication system includes at least terminal devices 1A to 1C and a base station device 3 (BS#3: Base station#3). Hereinafter, terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1: User Equipment#1).

[0016] The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting / receiving devices, or transmitting / receiving points). When the base station device 3 is configured by multiple transmitting devices, the multiple transmitting devices may be located at different positions.

[0017] 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 may also be referred to as a cell.

[0018] A serving cell may be configured to include one or both of a downlink component carrier (downlink carrier) and one or both of an uplink component carrier (uplink carrier). A serving cell may be configured to include two or more downlink component carriers and one or both of two or more uplink component carriers. Downlink component carriers and uplink component carriers are also collectively referred to as component carriers (carriers).

[0019] For example, one resource grid may be provided for each component carrier. Alternatively, one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration μ, where the subcarrier spacing configuration μ is also referred to as numerology. For example, 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.

[0020] The resource grid is size，μ grid，x N RB sc where the resource grid includes common resource blocks N start，μ grid，x Also, common resource block N start，μ grid，x is also called the reference point of the resource grid.

[0021] The resource grid is subframe，μ symb It contains OFDM symbols.

[0022] The subscript x added to the resource grid related parameters indicates the transmission direction, for example, the subscript x may be used to indicate either the downlink or the uplink.

[0023] N size，μ grid，x is the offset setting indicated by a parameter provided by the RRC layer (e.g., the parameter CarrierBandwidth). start，μ grid，x is a band configuration indicated by a parameter provided by the RRC layer (for example, the parameter OffsetToCarrier). The offset configuration and band configuration are configurations used to configure an SCS-specific carrier.

[0024] The subcarrier spacing (SCS: SubCarrier Spacing) Δf for a certain subcarrier spacing setting μ is Δf = 2 μ It may be 15 kHz. Here, the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.

[0025] FIG. 2 shows a subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb 2A, for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N slot symb = 14, N frame，μ slot = 40, N subframe，μ slot In addition, in FIG. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is an extended cyclic prefix (CP), N slot symb = 12, N frame，μ slot = 40, N subframe，μ slot =4.

[0026] Time unit T c may be used to express a length in the time domain. c is T c = 1 / (Δf max ・N f ) Δf max = 480 kHz. f = 4096. The constant κ is κ = Δf max ・N f / (Δf ref N f，ref ) = 64. Δf ref is 15 kHz. f，ref is 2048.

[0027] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be of length T f The radio frame (system frame, frame) may be organized into T f =(Δf max N f / 100) T s = 10 ms. A radio frame is composed of 10 subframes. The length of a subframe is T sf =(Δf max N f / 1000) T s = 1 ms. The number of OFDM symbols per subframe is N subframe，μ symb = N slot symb N subframe，μ slot is.

[0028] An OFDM symbol is a time domain unit of a communication method. For example, an OFDM symbol may be a time domain unit of CP-OFDM. Alternatively, an OFDM symbol may be a time domain unit of DFT-s-OFDM.

[0029] A slot may consist of multiple OFDM symbols, for example, N consecutive OFDM symbols. slot symbFor example, in the normal CP setting, N OFDM symbols may constitute one slot. slot symb In addition, in the setting of the extended CP, N slot symb =12.

[0030] For a given subcarrier spacing setting μ, the number and index of slots contained in the subframe may be given. For example, slot index n μ s is the number of subframes from 0 to N subframe，μ slot The number and index of slots included in the radio frame may be given for the subcarrier spacing setting μ. μ s，f ranges from 0 to N in the radio frame. frame，μ slot The values ​​may be given in ascending order as integers ranging from -1.

[0031] 3 is a diagram illustrating an example of a method for configuring a resource grid according to one aspect of the present embodiment. The horizontal axis of FIG. 3 represents the frequency domain. In FIG. 3, the subcarrier spacing μ １ and the subcarrier spacing μ ２ 3 shows an example of the configuration of a resource grid of . In this way, one or more subcarrier spacings may be set for a certain component carrier. １ = μ ２ -1, various aspects of the present embodiment １ = μ ２ It is not limited to the condition of -1.

[0032] The component carrier 300 is a band having a predetermined width in the frequency domain.

[0033] 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 subcarrier intervals μ １ is the set of common resource blocks for

[0034] In the common resource block set 3100, the common resource block including the 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.

[0035] 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 determined by the subcarrier spacing setting μ １ The resource grid 3001 is represented by the number of common resource blocks for N size，μ grid１，x It contains common resource blocks.

[0036] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N start，μ BWP，i１ ) is the offset to

[0037] The common resource block set 3200 is a set of subcarrier spacing μ ２ is the set of common resource blocks for

[0038] In the common resource block set 3200, the common resource block including the 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.

[0039] 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 the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. ２ The resource grid 3002 is represented by the number of common resource blocks relative to the N size，μ grid２，x It contains common resource blocks.

[0040] The offset 3014 is the distance from the reference point of the resource grid 3002 to the reference point of the BWP 3004 with index i2 (N start，μ BWP，i２ ) is the offset to

[0041] 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of FIG. 4, the horizontal axis represents the OFDM symbol index l sym and the vertical axis is the subcarrier index k sc The resource grid 3001 is size，μ grid１，x N RB sc contains N subcarriers, subframe，μ symb Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The resource specified by is also called a resource element (RE).

[0042] Resource Block (RB) is N RBsc A resource block is a collective term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). RB sc =12.

[0043] A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block, i.e., one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.

[0044] 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 index n of the common resource block for a given subcarrier spacing setting μ μ CRB is n μ CRB = ceil(k sc / N RB sc ) relationship is satisfied. Here, k sc The subcarrier with .gt.=0 is a subcarrier having the same center frequency as the subcarrier corresponding to point 3000.

[0045] 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. The index n of the physical resource block for a given subcarrier spacing setting μ is μ PRB is n μ CRB = n μ PRB +N start，μ BWP，i where N start，μBWP，i denotes the reference point of the BWP with index i.

[0046] A BWP is defined as a subset of common resource blocks contained in the resource grid. start，μ BWP，i Starting with N size，μ BWP，i The BWP configured for a downlink carrier is also referred to as a downlink BWP. The BWP configured for an uplink component carrier is also referred to as an uplink BWP.

[0047] An antenna port may be 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. For example, a channel may correspond to a physical channel, a symbol may correspond to an OFDM symbol, a symbol may correspond to a resource block unit, or a symbol may correspond to a resource element.

[0048] When the large-scale properties of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are said to be quasi-co-located (QCL). Here, the large-scale properties may include at least long-range properties of the channel. The large-scale properties may include at least some or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first and second antenna ports being QCL with respect to beam parameters may mean that a receive beam assumed by the receiver for the first antenna port is the same as (or corresponds to) a receive beam assumed by the receiver for the second antenna port. 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 another 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.

[0049] The QCL type may be any of type A, type B, type C, and type D.

[0050] The two antenna ports may be type A QCLs, which may indicate that a first large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The two antenna ports may be type B QCLs, which may indicate that a second large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The two antenna ports may be type C QCLs, which may indicate that a third large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The two antenna ports may be type D QCLs, which may indicate that a fourth large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The first large-scale characteristic may include all of Doppler shift, Doppler spread, mean 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). An antenna port for a DMRS may be a DMRS port. An antenna port for a PTRS may be a PTRS port. An antenna port associated with a PTRS may be a PTRS port. An antenna port for an SRS may be an SRS port. An antenna port for a DMRS may be a DMRS port. An antenna port associated with a DMRS may be a DMRS port.

[0051] Carrier aggregation may be performing communication using a plurality of aggregated serving cells. Also, carrier aggregation may be performing communication using a plurality of aggregated component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated downlink component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated uplink component carriers.

[0052] 5 is a schematic block diagram showing an example configuration of a base station device 3 according to one aspect of the present embodiment. As shown in FIG. 5, 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) layer processing unit 36.

[0053] The wireless transceiver 30 includes at least a wireless transmitter 30a and part or all of a wireless receiver 30b. Here, the baseband unit included in the wireless transmitter 30a and the baseband unit included in the wireless receiver 30b may have the same or different device configurations. Furthermore, the RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may have the same or different device configurations. Furthermore, the antenna unit included in the wireless transmitter 30a and the antenna unit included in the wireless receiver 30b may have the same or different device configurations.

[0054] For example, the radio transmitting unit 30a may generate and transmit a PDSCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PBCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a synchronization signal baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDSCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a CSI-RS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a DL PTRS baseband signal.

[0055] For example, the radio receiving unit 30b may receive a PRACH. For example, the radio receiving unit 30b may receive and demodulate a PUCCH. The radio receiving unit 30b may receive and demodulate a PUSCH. For example, the radio receiving unit 30b may receive a PUCCH DMRS. For example, the radio receiving unit 30b may receive a PUSCH DMRS. For example, the radio receiving unit 30b may receive an UL PTRS. For example, the radio receiving unit 30b may receive an SRS.

[0056] The upper layer processing unit 34 outputs the downlink data (transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The upper layer processing unit 34 performs processing on the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

[0057] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing.

[0058] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 ​​sets parameters based on an RRC message received from the terminal device 1.

[0059] The radio transceiver 30 (or the radio transmitter 30a) performs processes such as modulation and encoding. The radio transceiver 30 (or the radio transmitter 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting into a time-continuous signal) downlink data, and transmits the physical signal to the terminal device 1. The radio transceiver 30 (or the radio transmitter 30a) may allocate the physical signal to a certain component carrier and transmit the physical signal to the terminal device 1.

[0060] The radio transceiver unit 30 (or the radio receiver unit 30b) performs processes such as demodulation and decoding. The radio transceiver unit 30 (or the radio receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The radio transceiver unit 30 (or the radio receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.

[0061] The RF unit 32 converts (down-converts) the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation and removes unnecessary frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.

[0062] The baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal. The baseband unit 33 removes a portion corresponding to a cyclic prefix (CP) from the converted digital signal, and performs a fast Fourier transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

[0063] 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 baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 33 outputs the converted analog signals to the RF unit 32.

[0064] 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 the carrier frequency via the antenna unit 31. The RF unit 32 may also have a function to control transmission power. The RF unit 32 is also referred to as a transmission power control unit.

[0065] One or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured for the terminal device 1.

[0066] 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 an SCell (Secondary Cell).

[0067] The PCell is a serving cell included in a Master Cell Group (MCG). The PCell is a cell on which the terminal device 1 performs an initial connection establishment procedure or a connection re-establishment procedure (a cell on which the procedure has been performed).

[0068] The PSCell is a serving cell included in an SCG (Secondary Cell Group). The PSCell is a serving cell to which random access is performed by the terminal device 1.

[0069] An SCell may be included in either an MCG or an SCG.

[0070] A serving cell group (cell group) is a term that includes at least an MCG and an SCG. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be operated by carrier aggregation.

[0071] 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).

[0072] Of one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP may be configured as an active downlink BWP (or one downlink BWP may be activated). Of one or more uplink BWPs configured for a serving cell (or an uplink component carrier), one uplink BWP may be configured as an active uplink BWP (or one uplink BWP may be activated).

[0073] 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 an active BWP.

[0074] The PDSCH, PDCCH, and CSI-RS do not have to be received in a downlink BWP (inactive downlink BWP) other than an active downlink BWP. The terminal device 1 does not have to attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP. The PUCCH and PUSCH do not have to be transmitted in an uplink BWP (inactive uplink BWP) that is not an active uplink BWP. The terminal device 1 does not have to 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.

[0075] A 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. The downlink BWP switch may be controlled by a BWP field included in downlink control information. The downlink BWP switch may also be controlled based on higher layer parameters.

[0076] The uplink BWP switching is used to deactivate one active uplink BWP and activate one of the inactive uplink BWPs other than the one active uplink BWP. The uplink BWP switching may be controlled by a BWP field included in the downlink control information. The uplink BWP switching may also be controlled based on higher layer parameters.

[0077] Of one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs.For a serving cell, one downlink BWP may be active at a given time.

[0078] Of one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. At any given time, one uplink BWP may be active for a serving cell.

[0079] Fig. 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of the present embodiment. As shown in Fig. 6, the terminal device 1 includes at least a radio transmission / reception unit (physical layer processing unit) 10 and one or all of an upper layer processing unit 14. The radio transmission / reception 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.

[0080] The wireless transceiver 10 includes at least a wireless transmitter 10a and part or all of a wireless receiver 10b. Here, the baseband unit 13 included in the wireless transmitter 10a and the baseband unit 13 included in the wireless receiver 10b may have the same or different device configurations. Furthermore, the RF unit 12 included in the wireless transmitter 10a and the RF unit 12 included in the wireless receiver 10b may have the same or different device configurations. Furthermore, the antenna unit 11 included in the wireless transmitter 10a and the antenna unit 11 included in the wireless receiver 10b may have the same or different device configurations.

[0081] For example, the radio transmitting unit 10a may generate and transmit a baseband signal for a PRACH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for a PUCCH. The radio transmitting unit 10a may generate and transmit a baseband signal for a PUSCH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for a PUCCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for a PUSCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for a UL PTRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for an SRS.

[0082] For example, the wireless receiving unit 10b may receive and demodulate a PDSCH. For example, the wireless receiving unit 10b may receive and demodulate a PDCCH. For example, the wireless receiving unit 10b may receive and demodulate a PBCH. For example, the wireless receiving unit 10b may receive a synchronization signal. For example, the wireless receiving unit 10b may receive a PDSCH DMRS. For example, the wireless receiving unit 10b may receive a PDCCH DMRS. For example, the wireless receiving unit 10b may receive a CSI-RS. For example, the wireless receiving unit 10b may receive a DL PTRS.

[0083] The upper layer processing unit 14 outputs the uplink data (transport block) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 performs processing on the MAC layer, the packet data integration protocol layer, the radio link control layer, and the RRC layer.

[0084] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs MAC layer processing.

[0085] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. 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 an RRC message received from the base station device 3.

[0086] The wireless transceiver 10 (or the wireless transmitter 10a) performs processes such as modulation and encoding. The wireless transceiver 10 (or the wireless transmitter 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits the physical signal to the base station device 3. The wireless transceiver 10 (or the wireless transmitter 10a) may allocate the physical signal to a certain BWP (active uplink BWP) and transmit it to the base station device 3.

[0087] The radio transceiver unit 10 (or the radio receiver unit 10b) performs processes such as demodulation and decoding. The radio transceiver unit 10 (or the radio receiver unit 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The radio transceiver unit 10 (or the radio receiver unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The radio transceiver unit 10 (radio receiver unit 10b) may perform a channel access procedure prior to transmitting the physical signal.

[0088] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-converts) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13.

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

[0090] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate OFDM symbols, adds CPs to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 13 outputs the converted analog signals to the RF unit 12.

[0091] 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 the signal via the antenna unit 11. The RF unit 12 may also have a function to control transmission power. The RF unit 12 is also referred to as a transmission power control unit.

[0092] The physical signals (signals) will be explained below.

[0093] The physical signal is a general term for a downlink physical channel, a downlink physical signal, an uplink physical channel, and an uplink physical channel. The physical channel is a general term for a downlink physical channel and an uplink physical channel. The physical signal is a general term for a downlink physical signal and an uplink physical signal. The physical signal may also be called a reference signal.

[0094] The uplink physical channel may correspond to a set of resource elements that transmit 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 the terminal device 1. The uplink physical channel may be received by the base station device 3. In a wireless communication system according to one aspect of the present embodiment, 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)

[0095] 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 the PUCCH in which the uplink control information is mapped. The base station device 3 may receive the PUCCH in which the uplink control information is mapped.

[0096] The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of channel state information (CSI), scheduling request (SR), and hybrid automatic repeat request ACKnowledgement (HARQ-ACK) information.

[0097] The channel state information is also referred to as a channel state information bit or a channel state information sequence. The scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. The HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0098] 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 decoding of the transport block has been successfully completed. The NACK may indicate that 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.

[0099] A transport block is a sequence of information bits delivered from a higher layer. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be delivered via the Uplink-Shared Channel (UL-SCH) of the transport layer.

[0100] The HARQ-ACK for a transport block may be referred to as the HARQ-ACK for a PDSCH. In this case, the "HARQ-ACK for a PDSCH" refers to the HARQ-ACK for a transport block included in the PDSCH.

[0101] The HARQ-ACK may indicate an ACK or NACK corresponding to one CBG (Code Block Group) included in the transport block.

[0102] The scheduling request may be used at least to request UL-SCH resources for an initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, this 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 a higher layer. A positive SR may be transmitted when a scheduling request is indicated by a higher layer. When the scheduling request bit indicates a negative SR, this 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 a higher layer. A negative SR may be transmitted when a scheduling request is not indicated by a higher layer.

[0103] 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). The CQI is an indicator related to the quality of the propagation path (e.g., propagation strength) or the quality of the physical channel, the PMI is an indicator related to the precoder, and the RI is an indicator related to the transmission rank (or the number of transmission layers).

[0104] The channel state information is an indicator related to 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.

[0105] 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 also be interpreted as a set of information set in a certain information format.

[0106] The PUSCH may be used to transmit one or both of a transport block and uplink control information. The transport block may be allocated to the PUSCH. The transport block delivered by the UL-SCH may be allocated to the PUSCH. The uplink control information may be allocated to the PUSCH. The terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are allocated. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are allocated.

[0107] The PRACH may be transmitted to transmit a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The PRACH sequence x u，v (n) x u，v (n) = x u (mod(n+C v , L RA ) where x u is a ZC (Zadoff-Chu) series. u x u =exp(-jπui(i+1) / L RA ) where j is the imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, C v corresponds to the cyclic shift of the PRACH sequence. RA corresponds to the length of the PRACH sequence. RA is 839 or 139. Also, i ranges from 0 to L RA is an integer in the range of -1, and u is the sequence index for the PRACH sequence.

[0108] For each PRACH opportunity, 64 random access preambles are defined. The random access preambles are cyclically shifted C v , and the sequence index u for the PRACH sequence. An index may be assigned to each of the 64 identified random access preambles.

[0109] The uplink physical signal may correspond to a set of resource elements. The uplink physical signal does not have to be used to transmit information generated in a higher layer. The uplink physical signal may be used to transmit information generated in the 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. In a wireless communication system according to one aspect of the present embodiment, 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)

[0110] UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

[0111] A set of antenna ports for DMRSs for a PUSCH (DMRSs associated with a PUSCH, DMRSs included in a PUSCH, and DMRSs corresponding to a PUSCH) may be given based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for DMRSs for a PUSCH may be the same as the set of antenna ports for the PUSCH.

[0112] 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 equivalent to transmitting the PUSCH and the DMRS for the PUSCH.

[0113] The propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

[0114] The set of antenna ports for DMRS for PUCCH (DMRS related to PUCCH, DMRS included in PUCCH, DMRS corresponding to PUCCH) may be the same as the set of antenna ports for PUCCH.

[0115] 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 PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting a PUCCH may also mean transmitting a PUCCH and a DMRS for the PUCCH.

[0116] The propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

[0117] The downlink physical channel may correspond to a set of resource elements that transmit 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. In a wireless communication system according to one aspect of the present embodiment, 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)

[0118] The PBCH may be transmitted to convey one or both of a Master Information Block (MIB) and physical layer control information. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters allocated to a Broadcast Control Channel (BCCH), which is a logical channel of the MAC layer. The BCCH is allocated to a BCH, which is a channel of the transport layer. The BCH may be mapped to the PBCH. The terminal device 1 may receive a PBCH in which one or both of the MIB and physical layer control information are allocated. The base station device 3 may transmit a PBCH in which one or both of the MIB and physical layer control information are allocated.

[0119] For example, the physical layer control information may be composed of 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D: 0A) Radio frame bit 0B) Half radio frame (half system frame, half frame) bit 0C) SS / PBCH block index bit 0D) Subcarrier offset bit

[0120] The radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame bits include 4 bits. The radio frame bits may be configured by 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator may be used to identify at least radio frames with index 0 to index 1023.

[0121] 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 a radio frame in which the PBCH is transmitted. Here, a half radio frame may include five subframes. Alternatively, a half radio frame may include the first five subframes of ten subframes included in a radio frame. Alternatively, a half radio frame may include the last five subframes of ten subframes included in a radio frame.

[0122] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include three bits. The SS / PBCH block index bits may be configured with three bits of a six-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.

[0123] The subcarrier offset bits are used to indicate a subcarrier offset, which may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.

[0124] The PDCCH may be transmitted to convey downlink control information (DCI). The downlink control information may be arranged in the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is arranged. The base station device 3 may transmit the PDCCH in which the downlink control information is arranged.

[0125] 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 in a certain downlink control information format.

[0126] 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.

[0127] DCI format 0_0 is used at least for scheduling of PUSCHs allocated to a certain cell. DCI format 0_0 includes at least some or all of fields 1A to 1E. 1A) Identifier field for DCI formats 1B) Frequency domain resource assignment field 1C) Time domain resource assignment field 1D) Frequency hopping flag field 1E) MCS field (Modulation and Coding Scheme field)

[0128] The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. That is, the DCI format identification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format identification field included in DCI format 0_0 may indicate 0.

[0129] 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.

[0130] 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.

[0131] The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.

[0132] 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 assigned to the PUSCH. The size of the transport block (TBS) assigned to the PUSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PUSCH.

[0133] DCI format 0_0 may not include fields used for CSI requests.

[0134] DCI format 0_0 may not include a carrier indicator field. That is, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated may be the same as the serving cell of the uplink component carrier on which the PDCCH including DCI format 0_0 is allocated. By detecting DCI format 0_0 on a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is allocated on the uplink component carrier of the serving cell.

[0135] DCI format 0_0 may not include a BWP field (BWP indication field). Here, DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing the active uplink BWP. Based on detecting DCI format 0_0 used for scheduling a PUSCH, the terminal device 1 may recognize that the PUSCH will be transmitted without switching the active uplink BWP.

[0136] DCI format 0_1 ​​is used at least for scheduling PUSCHs allocated to a certain cell. DCI format 0_1 ​​includes at least some or all of fields 2A to 2H. 2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field 2G) BWP field 2H) Carrier indicator field

[0137] The DCI format specific field included in DCI format 0_1 ​​may indicate 0.

[0138] 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.

[0139] 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.

[0140] The MCS field included in DCI format 0_1 ​​may be used to indicate at least part or all of the modulation scheme and / or target coding rate for the PUSCH.

[0141] The BWP field of DCI format 0_1 ​​may be used to indicate an uplink BWP in which a PUSCH scheduled by the DCI format 0_1 ​​is arranged. That is, DCI format 0_1 ​​may involve a change of the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting DCI format 0_1 ​​used for scheduling the PUSCH.

[0142] The DCI format 0_1 ​​that does not include a BWP field 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 based on detecting the DCI format D0_1 that is DCI format 0_1 ​​used for scheduling a PUSCH and does not include a BWP field.

[0143] If the DCI format 0_1 ​​includes a BWP field but the terminal device 1 does not support the BWP switching function using the DCI format 0_1, the BWP field may be ignored by the terminal device 1. That is, a terminal device 1 that does not support the BWP switching function may recognize that it transmits the PUSCH without switching the active uplink BWP based on detecting DCI format 0_1 ​​that is used for PUSCH scheduling and includes the BWP field. Here, if 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 capability information reporting procedure.

[0144] The CSI request field is used to indicate the reporting of CSI.

[0145] When DCI format 0_1 ​​includes a carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier on which a PUSCH is arranged. When DCI format 0_1 ​​does not include a carrier indicator field, the uplink component carrier on which a PUSCH is arranged may be the same as an uplink component carrier on which a PDCCH including DCI format 0_1 ​​used for scheduling the PUSCH is arranged. When the number of uplink component carriers configured in a terminal device 1 in a certain serving cell group is two or more (when uplink carrier aggregation is operated in a certain serving cell group), the number of bits of the carrier indicator field included in DCI format 0_1 ​​used for scheduling a PUSCH arranged in the certain serving cell group may be one bit or more (e.g., three bits). When the number of uplink component carriers configured for a terminal device 1 in a certain serving cell group is 1 (when uplink carrier aggregation is not operated in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 ​​used for scheduling a PUSCH placed in the certain serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 0_1 ​​used for scheduling a PUSCH placed in the certain serving cell group).

[0146] DCI format 1_0 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_0 includes at least some or all of 3A to 3F. 3A) DCI format specific field, 3B) Frequency domain resource allocation field, 3C) Time domain resource allocation field, 3D) MCS field, 3E) PDSCH to HARQ feedback timing indicator field, and 3F) PUCCH resource indicator field.

[0147] The DCI format specific field included in DCI format 1_0 may indicate 1.

[0148] 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.

[0149] 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.

[0150] 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 allocated to the PDSCH. The size of the transport block (TBS) allocated to the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.

[0151] 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.

[0152] 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.

[0153] DCI format 1_0 may not include a carrier indicator field. That is, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is allocated. By detecting DCI format 1_0 on a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_0 is allocated to the downlink component carrier.

[0154] DCI format 1_0 may not include a BWP field. Here, DCI format 1_0 may be a DCI format for scheduling 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 it will receive the PDSCH without switching the active downlink BWP.

[0155] DCI format 1_1 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_1 includes at least some or all of 4A to 4I. 4A) DCI format specific field, 4B) Frequency domain resource allocation field, 4C) Time domain resource allocation field, 4E) MCS field, 4F) PDSCH_HARQ feedback timing indication field, 4G) PUCCH resource indication field, 4H) BWP field, and 4I) Carrier indicator field.

[0156] The DCI format specific field included in DCI format 1_1 may indicate 1.

[0157] 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.

[0158] 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.

[0159] 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.

[0160] If 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 parameter of a higher layer.

[0161] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.

[0162] The BWP field of DCI format 1_1 may be used to indicate the downlink BWP in which the PDSCH scheduled by DCI format 1_1 is arranged. That is, DCI format 1_1 may involve a change of the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged by detecting DCI format 1_1 used for scheduling the PDSCH.

[0163] The DCI format 1_1 that does not include a BWP field may be a DCI format for scheduling 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.

[0164] If DCI format 1_1 includes a BWP field but the terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by the terminal device 1. In other words, 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. Here, if 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 capability information reporting procedure.

[0165] When DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate a downlink component carrier on which a PDSCH is arranged. When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which a PDSCH is arranged may be the same as a downlink component carrier on which a PDCCH including DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink component carriers configured in the terminal device 1 in a certain serving cell group is two or more (when downlink carrier aggregation is operated in a certain 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 certain serving cell group may be one bit or more (for example, three bits). When the number of downlink component carriers configured for a terminal device 1 in a certain serving cell group is 1 (when downlink carrier aggregation is not operated in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH placed in the certain 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 certain serving cell group).

[0166] 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. A transport block may be allocated to the PDSCH. A transport block corresponding to the DL-SCH may be allocated to the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

[0167] The downlink physical signal may correspond to a set of resource elements. The downlink physical signal does not need to 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. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical signals may be used: Synchronization signal (SS) DL DMRS (DownLink Demodulation Reference Signal) CSI-RS (Channel State Information-Reference Signal) DL PTRS (DownLink Phase Tracking Reference Signal)

[0168] 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 a PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal).

[0169] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym ), where the vertical axis represents the frequency domain. Block 700 represents a set of resource elements for the PSS. Block 720 represents a set of resource elements for the SSS. Four blocks (blocks 710, 711, 712, and 713) represent sets of resource elements for the PBCH and DMRS for the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

[0170] As shown in Figure 7, the SS / PBCH block includes a PSS, SSS, and PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is allocated to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is allocated to the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers in the first OFDM symbol may be set to zero. The 184th to 240th subcarriers in the first OFDM symbol may be set to zero. The 49th to 56th subcarriers in the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers in the third OFDM symbol may be set to zero. The PBCH is allocated to the 1st to 240th subcarriers in the second OFDM symbol, which are subcarriers where the DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated.

[0171] The antenna ports for the PSS, SSS, PBCH, and DMRS for the PBCH may be the same.

[0172] The PBCH on which the PBCH symbol is transmitted at a certain antenna port may be estimated by the DMRS for the PBCH that is placed in the slot to which the PBCH is mapped and is included in the SS / PBCH block to which the PBCH belongs.

[0173] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.

[0174] The set of antenna ports for DMRS for PDSCH (DMRS related to PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) may be determined based on the set of antenna ports for the PDSCH, i.e., the set of antenna ports for DMRS for PDSCH may be the same as the set of antenna ports for the PDSCH.

[0175] 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 also mean transmitting the PDSCH and the DMRS for the PDSCH.

[0176] A propagation path of a PDSCH may be estimated from a DMRS for the PDSCH. If a set of resource elements carrying a certain PDSCH symbol and a set of resource elements carrying a DMRS symbol for the PDSCH are included in the same precoding resource group (PRG), the PDSCH carrying the PDSCH symbol for a certain antenna port may be estimated by the DMRS for the PDSCH.

[0177] The antenna port of the DMRS for the PDCCH (DMRS related to the PDCCH, DMRS included in the PDCCH, DMRS corresponding to the PDCCH) may be the same as the antenna port for the PDCCH.

[0178] A PDCCH may be estimated from a DMRS for the PDCCH. That is, a propagation path of a PDCCH may be estimated from a DMRS for the PDCCH. If the same precoder is applied (or assumed to be applied) to a set of resource elements on which a certain PDCCH symbol is transmitted and a set of resource elements on which a DMRS symbol for the PDCCH is transmitted, the PDCCH on which the PDCCH symbol for a certain antenna port is transmitted may be estimated by the DMRS for the PDCCH.

[0179] The BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels that define the relationship between physical layer channels and MAC layer channels (also called logical channels).

[0180] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, transport blocks carried on the BCH of the transport layer are 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, transport blocks carried on the UL-SCH of the transport layer are 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, transport blocks carried on the DL-SCH of the transport layer are delivered to the PDSCH of the physical layer.

[0181] 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 necessarily have to be provided for the PSCell or SCell.

[0182] In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block.

[0183] The BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, the BCCH is a channel of the RRC layer used for transmitting MIB or system information. The CCCH (Common Control CHannel) may be used for transmitting RRC messages common to multiple terminal devices 1. Here, the CCCH may be used, for example, for terminal devices 1 that are not RRC connected. The DCCH (Dedicated Control CHannel) may be used at least for transmitting RRC messages dedicated to the terminal device 1. Here, the DCCH may be used, for example, for terminal devices 1 that are RRC connected.

[0184] Upper layer parameters common to multiple terminal devices 1 are also referred to as common upper layer parameters. Here, the common upper layer parameters may be defined as parameters specific to a serving cell. Here, the parameters specific to a serving cell may be parameters common to terminal devices (e.g., terminal devices 1-A, 1-B, and 1-C) in which the serving cell is configured.

[0185] For example, the common upper layer parameters may be included in an RRC message delivered on the BCCH. For example, the common upper layer parameters may be included in an RRC message delivered on the DCCH.

[0186] Among certain upper layer parameters, upper layer parameters different from common upper layer parameters are also referred to as dedicated upper layer parameters. Here, the dedicated upper layer parameters can provide dedicated RRC parameters to the terminal device 1-A in which the serving cell is configured. In other words, 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.

[0187] The BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information other than MIB is delivered to the DL-SCH of the transport layer. The CCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the CCCH is delivered to the DL-SCH or UL-SCH. The DCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the DCCH is delivered to the DL-SCH or UL-SCH.

[0188] The RRC message includes one or more parameters managed in the RRC layer. Here, the parameters managed in the RRC layer are also referred to as RRC parameters. For example, 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 a dedicated RRC message.

[0189] The upper layer parameters (upper layer parameters) are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element). That is, the upper layer parameters are a collective term for MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE. The parameters included in MAC CE are transmitted by MAC CE (Control Element) commands.

[0190] The procedures performed by the terminal device 1 include at least some or all of the following steps 5A to 5C: 5A) Cell search, 5B) Random access, and 5C) Data communication.

[0191] The 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 a physical cell identity. That is, the terminal device 1 may perform the cell search to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell ID.

[0192] The sequence of PSSs is based at least on a physical cell ID. The sequence of SSSs is based at least on a physical cell ID.

[0193] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH blocks is permitted (possibly, reserved, configured, defined, possible).

[0194] The set of SS / PBCH block candidates in a half radio frame is also called the SS burst set. The SS burst set is also called the transmission window, SS transmission window, or DRS (Discovery Reference Signal) 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.

[0195] 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 included in the SS / PBCH block.

[0196] Random access (random access procedure) 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 a higher layer parameter or a PDCCH order.

[0197] Message 1 is a procedure for transmitting a PRACH by a terminal device 1. The terminal device 1 transmits a random access preamble on the PRACH as message 1. The terminal device 1 transmits the PRACH on 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.

[0198] The terminal device 1 transmits one random access preamble selected from among the PRACH opportunities corresponding to the index of the SS / PBCH block candidate from which the SS / PBCH block is detected.

[0199] The terminal device 1 may attempt to detect DCI format 1_0 with a CRC scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier). Message 2 is a procedure by 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 this DCI format in a control resource set given based on an MIB included in a PBCH included in an SS / PBCH block detected based on cell search and in resources indicated based on the setting of a search space set. Message 2 is also referred to as 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.

[0200] Message 3 is a procedure for transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected by the procedure of message 2. Here, the random access response grant is indicated by a MAC CE included in a PDSCH scheduled by DCI format 1_0.

[0201] The PUSCH scheduled based on the random access response grant is either a message 3 PUSCH or a PUSCH. The message 3 PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier (MAC CE) includes the contention resolution ID.

[0202] Message 3 PUSCH retransmissions are scheduled with DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

[0203] Message 4 is a procedure for attempting to detect DCI format 1_0 with a CRC scrambled based on either a Cell-Radio Network Temporary Identifier (C-RNTI) or a 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.

[0204] Data communication is a general term for downlink communication and uplink communication.

[0205] In data 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).

[0206] A control resource set (CORESET) is a set of resources consisting of a predetermined number of resource blocks and a predetermined number of OFDM symbols. In the frequency domain, a control resource set may be composed of contiguous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

[0207] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter, and the number of OFDM symbols constituting the control resource set may be indicated by a higher layer parameter.

[0208] The terminal device 1 attempts to detect a PDCCH in a search space set. Here, attempting to detect a PDCCH in a 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 a 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.

[0209] 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 a Type 0 PDCCH common search space set, a Type 0a PDCCH common search space set, a Type 1 PDCCH common search space set, a Type 2 PDCCH common search space set, a Type 3 PDCCH common search space set, and / or a UE-specific search space set.

[0210] 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.

[0211] The CSS set is a collective term for a Type 0 PDCCH common search space set, a Type 0a PDCCH common search space set, a Type 1 PDCCH common search space set, a Type 2 PDCCH common search space set, and a Type 3 PDCCH common search space set. The USS set is also called a UE-specific PDCCH search space set.

[0212] A search space set is associated with (included in, corresponds to) a control resource set, and the index of the control resource set associated with the search space set may be indicated by a higher layer parameter.

[0213] For a given search space set, some or all of 6A to 6C may be indicated by higher layer parameters: 6A) PDCCH monitoring periodicity, 6B) PDCCH monitoring pattern within a slot, and 6C) PDCCH monitoring offset.

[0214] A monitoring occasion for a search space set may correspond to an OFDM symbol in which a 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 resources of a control resource set starting from a first OFDM symbol of the control resource set associated with the search space set. The monitoring occasion for the search space set is determined based on at least some or all of a PDCCH monitoring interval, a PDCCH monitoring pattern within a slot, and a PDCCH monitoring offset.

[0215] 8 is a diagram illustrating an example of a monitoring opportunity for a search area set according to one aspect of the present embodiment. In FIG. 8, 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, and a search area set 94 is set in a secondary cell 303.

[0216] In Figure 8, 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, and the blocks in secondary cell 303 indicate search area set 94.

[0217] 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 slot, and the monitoring pattern of search area set 91 is set to [1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0]. That is, the monitoring opportunities for search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0218] 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,0,0,0]. That is, the monitoring opportunity for search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.

[0219] 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,1,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 93 corresponds to the eighth OFDM symbol (OFDM symbol #7) in each of the even slots.

[0220] 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,0,0,0]. That is, the monitoring opportunity for search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.

[0221] 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 a SI-RNTI (System Information-Radio Network Temporary Identifier).

[0222] The Type 0 aPDCCH common search space set may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0223] The Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and / or a CRC sequence scrambled by a Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).

[0224] A Type 2 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by a Paging-Radio Network Temporary Identifier (P-RNTI).

[0225] A Type 3 PDCCH common search space set may be used for a DCI format with a CRC sequence scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI).

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

[0227] In downlink communication, the terminal device 1 detects a downlink DCI format. The detected downlink DCI format is used at least for PDSCH resource allocation. The detected downlink DCI format is also referred to as 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.

[0228] In uplink communication, the terminal device 1 detects an uplink DCI format. The detected DCI format is used at least for PUSCH resource allocation. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.

[0229] In configured scheduling (configured grant), an uplink grant for scheduling a PUSCH is configured for each transmission period of the PUSCH. When 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.

[0230] 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 PUSCH transmission of the configured scheduling type 1 may be configured semi-statically. For example, the PUSCH transmission of the configured scheduling type 1 may be operated in response to reception of certain higher layer parameters. The certain higher layer parameters may be configuredGrantConfig. For example, configuredGrantConfig may include rrc-ConfiguredUplinkGrant. The PUSCH transmission may be operated without detecting an uplink grant in DCI.

[0231] The configured scheduling type 2 PUSCH transmission may be semi-persistently scheduled. For example, it may be scheduled by a certain uplink grant. The certain uplink grant may be included in an activation DCI (or a valid activation DCI). For example, after receiving certain higher layer parameters, the configured scheduling type 2 PUSCH transmission may be scheduled by a certain uplink grant. The certain higher layer parameters may be configuredGrantConfig. For example, configuredGrantConfig may not include rrc-ConfiguredUplinkGrant.

[0232] System frame number (SFN) n ｆ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 portion 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 portion of the system frame number may be determined based on the PBCH that carries the MIB. For example, 4 bits (e.g., 4 least significant bits) of the 10-bit system frame number may be transmitted in the PBCH transport block as part of channel coding.

[0233] The PDCCH-Config may be a dedicated higher layer parameter. The PDCCH-Config may configure parameters for the PDCCH. Multiple (for example, up to three) CORESETs may be configured in the PDCCH-Config. A CORESET ID may be configured in one CORESET. One CORESET pool index may be configured in one CORESET.

[0234] The PDCCH configuration may include two different CORESET pool indices. For example, two CORESET pool index values ​​(0 and 1) may be provided. For example, two CORESET pool index values ​​may be provided for the First CORESET and the Second CORESET. The PDCCH configuration may be PDCCH-Config.

[0235] The PDSCH-Config may be a dedicated higher layer parameter. The PDSCH-Config may configure parameters for the PDSCH.

[0236] When 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 an earlier-started PDCCH candidate of the two PDCCH candidates. The higher layer parameter may be searchSpaceLinking.

[0237] Multiple TRPs (Transmission Reception Points, or Transmit / Receive Points) may be used. 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. In Multi-TRP, one of the operation modes of single-DCI and multi-DCI may be used. In Multi-TRP, uplink control may be completed in the MAC layer and the physical layer. In Multi-TRP, downlink control may be completed in the MAC layer and the physical layer. In Single-DCI mode, the terminal device 1 may be scheduled by the same DCI for multiple TRPs. In Multi-DCI mode, the terminal device 1 may be scheduled by independent DCI from each TRP.

[0238] The terminal device 1 may form a beam (beamforming). For example, the terminal device 1 may transmit radio waves (electromagnetic waves) in a specific spatial direction by beamforming. For example, 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 transmitting and / or 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. For example, the beam information may be a specific spatial direction. For example, 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-related information.

[0239] The terminal device 1 may be configured with an upper layer parameter TCI-State. For example, 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) a PDSCH according to a PDCCH with DCI. M may depend on the terminal capability. For example, M may depend on the terminal capability maxNumberConfiguredTCIStatePerCC. TCI-State may be referred to as a TCI state.

[0240] Each TCI-State (i.e., higher layer parameter TCI-State) may include a parameter for setting a QCL (Quasi co-location relationship). The QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDSCH. The QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDCCH. The 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. For example, the QCL relationship between channel / signal A and channel / signal B may indicate that channel / signal A is QCL with channel / signal B.

[0241] The QCL relationship may be set by one or both of the higher layer parameters qcl-Type1 and qcl-Type2. For example, the QCL relationship may be set by one or both of the higher layer parameters qcl-Type1 for a first downlink reference signal (DL RS) and qcl-Type2 for a 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 higher layer parameter qcl-Type in the higher layer parameter QCL-Info. The QCL type may be any of type A, type B, type C, and type D.

[0242] One list may be configured by the upper layer parameter dlOrJointTCI-StateList. For example, 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. One reference signal may be a reference signal for DMRS of PDSCH and QCL for DMRS of PDCCH. 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. One reference may be used to determine the uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter may be used for the PUSCH, the PUCCH, and the SRS. That is, one reference may be provided to determine the uplink transmit spatial filter for the PUSCH, the PUCCH, and the SRS. The TCI state may be DLorJointTCIState (TCI-State). The DLorJointTCIState may also be referred to as the DL / Joint TCI state or the unified TCI state.

[0243] The TCI-State (e.g., the upper layer parameter TCI-State) and the TCI-UL-State (e.g., the upper layer parameter TCI-UL-State) may be set in one BWP of one component carrier. If the TCI-State setting or the TCI-UL-State setting is not set in one BWP, the terminal device 1 may apply the TCI-State setting or the TCI-UL-State setting from the reference BWP.

[0244] The terminal device 1 may not expect both the first upper layer parameter and the second upper layer parameter to be configured. 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. When TCI-State is configured for any component carrier in a list, the second upper layer parameter may not be configured for any component carrier in the same band in the list. The list may be configured 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. When the first upper layer parameter is configured, it may not be expected that two TAs are provided in one serving cell. Providing two TAs in one serving cell may mean that two TAG IDs are configured in the serving cell configuration (e.g., the higher layer parameter ServingCellConfig). The higher layer parameter tag-Id and the higher layer parameter tag-Id2 may be configured in the higher layer parameter ServingCellConfig.

[0245] The terminal device 1 may receive an activation command. The activation command may be used to map up to eight "TCI states and / or TCI state pairs" 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 include one or two TCI states for downlink channels / signals. Each set may include one or two TCI states for uplink channels / signals. A pair of TCI states may include 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, the PUCCH, and the SRS. The DCI (DCI format) may be configured with one or more DCI fields. For example, the DCI (DCI format) may be configured to include a TCI field ('Transmission Configuration Indication' field).

[0246] If a first set of one or more TCI state IDs are activated in the second set, the first set may be applied for downlink BWPs on the indicated component carrier. If a first set of one or more TCI state IDs are activated in the third set, the first set may be applied for downlink BWPs and uplink BWPs on the indicated component carrier. The second set may be a set of one or more component carriers and / or one or more downlink BWPs. The third set may be a set of one or more component carriers, one or more downlink BWPs, and / or one or more uplink BWPs.

[0247] If the activation command maps one or both of DLorJointTCIState (TCI-State) and UL-TCIState (TCI-UL-State) to one TCI code point (the code point of the DCI field 'Transmission Configuration Indication'), the terminal device 1 may apply one or both of the indicated DLorJointTCIState and the indicated UL-TCIState.

[0248] The terminal device 1 may receive DCI format 1_1 / 1_2 that provides the indicated TCI-State or the indicated TCI-UL-State. The DCI format does not need to be accompanied by a downlink assignment. For example, if DCI format 1_1 / 1_2 is accompanied by a downlink assignment, the terminal device 1 may assume some or all of the following: CS-RNTI is used to scramble the CRC for the DCI, RV (Redundancy version) is all ones, MCS is all ones, NDI is 0, all zeros are set for FDRA type 0, and all ones are set for FDRA type 1.

[0249] The terminal device 1 may receive a DCI format including a TRP indication field. The TRP indication field may select one or two TCI states from one or more "indicated TCI states." The TCI states may be referred to as "applied TCI states." When one TCI state is selected, the one TCI state may be applied to the PDSCH, PUSCH, PUCCH, CSI-RS, or SRS scheduled by the DCI format. When two TCI states are selected, the two TCI states may be applied to the PDSCH, PUSCH, PUCCH, CSI-RS, or SRS scheduled by the DCI format. The "indicated TCI state" may be an indicated TCI-State or an "indicated TCI-UL-State." The DCI format may be referred to as a DCI. The indicated TCI-State may be referred to as an indicated DL / Joint TCI-State. The indicated TCI-UL-State may be referred to as an indicated UL TCI-State.

[0250] N conf N TCI states may be set. For example, N conf The TCI states may be configured in the radio resource control layer. For example, N conf N TCI states may be configured by higher layer parameters. conf Each of the N TCI states may be referred to as a "configured TCI state." conf may be an integer between 1 and 128. If the TCI state is a DL TCI state or a Joint TCI state, N conf may be an integer between 1 and 128. If the TCI state is a UL TCI state, N conf may be an integer between 1 and 64.

[0251] N act N TCI states may be activated. For example, N act The TCI states are N conf For example, N actN TCI states may be activated in the medium access control layer. For example, N act N TCI states may be activated by the MAC CE. act Each of the N TCI states may be referred to as an "activated TCI state." act may be an integer between 1 and 32.

[0252] N ind N TCI states may be indicated. For example, N ind The TCI states are N act For example, N ind The TCI states may be indicated at the physical layer. For example, N ind N TCI states may be indicated by a DCI. For example, N ind The TCI states may be indicated by the TCI field in the DCI. ind Each of the TCI states may be referred to as a "directed TCI state." A "directed TCI state" may apply to the PDSCH, PDCCH, and CSI-RS. A "directed TCI state" may apply to the PUSCH, PUCCH, and SRS. A "directed TCI state" may apply to the PDSCH, PDCCH, CSI-RS, PUSCH, PUCCH, and SRS. ind may be an integer between 1 and 4.

[0253] N app N TCI states may be indicated and applied. For example, N app The TCI states are N ind For example, N app The TCI states may be indicated at the physical layer. For example, N app N TCI states may be indicated by a DCI. For example, N app The TCI states may be indicated by the TRP indication field in the DCI. app The TCI states may be indicated by higher layer parameters. appEach of the N TCI states may be referred to as an "applicable TCI state." app may be 1 or 2. For example, a DCI or higher layer parameter may select one of the first indicated TCI state, the second indicated TCI state, and the two indicated TCI states. app may be 1. For example, the corresponding CORESET pool index may indicate a first indicated TCI state or a second indicated TCI state.

[0254] The terminal device 1 may receive an upper layer configuration. After the "TCI state to be configured" is configured by the terminal device 1 and before one "instructed TCI state" is applied from the "TCI state to be configured", the terminal device 1 may assume that the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the "instructed TCI state" is applied are an SS / PBCH block and a QCL. For example, after the terminal device 1 receives the first configuration of DLorJoint-TCIStateList and before one instructed TCI state is applied from the configured TCI state, the terminal device 1 may assume that the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the instructed TCI state is applied are an SS / PBCH block and a QCL. Configuring the upper layer parameter DLorJoint-TCIStateList may be configuring the "TCI state to be configured". Configuring the upper layer parameter DLorJoint-TCIStateList may be configuring a unified TCI state. The "TCI state to be set" may be set to a unified TCI state. DLorJoint-TCIStateList may be accompanied by multiple upper layer parameters TCI-State.

[0255] The terminal device 1 may receive an upper layer configuration. After the "configured TCI state" is configured and before one "indicated TCI state" is applied from the "configured TCI state," the terminal device 1 may assume that the first uplink transmit spatial filter for the PUSCH, PUCCH, and SRS applying the "indicated TCI state" is the same as the second uplink transmit spatial filter. For example, after the terminal device 1 receives a first configuration of a DLorJoint-TCIStateList including multiple TCI-States or multiple TCI-UL-States and before one indicated TCI state is applied from the configured TCI states, the terminal device 1 may assume that the first uplink transmit spatial filter (UL TX spatial filter) for the PUSCH, PUCCH, and SRS applying the indicated TCI state is the same as the second uplink transmit 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.

[0256] After the terminal device 1 receives a configuration of dl-OrJointTCI-StateList including multiple TCI-States ("configured TCI states"), and before applying one "indicated TCI state" from the configured TCI states, the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the indicated TCI state is applied may be an SS / PBCH block or a CSI-RS resource and a QCL. For example, the SS / PBCH block or the CSI-RS resource may be identified in a random access procedure initiated by synchronized reconfiguration.

[0257] After the terminal device 1 receives a configuration of dl-OrJointTCI-StateList including multiple TCI-States or multiple TCI-UL-States ("configured TCI states") and before applying one "indicated TCI state" from the configured TCI states, it may be assumed that the first uplink transmit spatial filter for the PUSCH, PUCCH, and SRS applying the indicated TCI state is the same as the second uplink transmit spatial filter. The second uplink transmit spatial filter may be an uplink spatial filter for PUSCH transmission scheduled by a random access response grant (RAR UL grant) in a random access procedure. The second uplink transmit spatial filter may be an uplink transmit spatial filter for PUSCH transmission scheduled by a random access response grant in a random access procedure initiated by synchronized reconfiguration.

[0258] The TCI-State may be used as the "indicated TCI state." For example, the terminal device 1 may acquire a QCL assumption (QCL relation, QCL) for the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the "indicated TCI state" applies from the "configured TCI state." 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.

[0259] The UL-TCI-State may be used as the “indicated TCI state.” For example, the terminal device 1 may determine an uplink transmit spatial filter from the “set TCI state” for the PUSCH, PUCCH, and SRS to which the “indicated TCI state” applies.

[0260] When the terminal device 1 transmits a first channel and the first "indicated TCI state" is different from the second "indicated TCI state," 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 carrying a TCI state indication without downlink assignment. The HARQ-ACK information may be HARQ-ACK information corresponding to a PDSCH scheduled by a DCI carrying a TCI state indication. The second indicated TCI state may be indicated before (before) 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 a higher layer parameter. BeamAppTime may be determined by terminal capabilities. The indicated TCI state may be an indicated TCI-State or an indicated TCI-UL-State.

[0261] When the multi-DCI mode is configured, the terminal device 1 may receive an activation command ("activated TCI state") for a CORESET associated with each CORESET pool index. The activation command may be used to map up to eight TCI states to code points in the DCI field 'Transmission Configuration Indication'. When a set of TCI state IDs is activated for one CORESET pool index, 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 more 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 includes two different values ​​of the CORESET Pool Index (CORESET Pool Index or coresetPoolIndex).

[0262] One code point of the DCI field 'Transmission Configuration Indication' (i.e., the TCI field) may include up to four TCI states. For example, one of the up to four TCI states may be a Joint TCI state. One of the up to four TCI states may be a DL TCI state. One of the up to four TCI states may be a UL TCI state. One code point of the DCI field 'Transmission Configuration Indication' may include two "TCI state pairs." The TCI state pair may be a pair of a DL TCI state and a UL TCI state. The terminal device 1 may receive an activation command. The activation command may be used to map up to eight combinations of four or less 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'. The terminal device 1 may not expect to receive more than eight TCI states in the activation command. The terminal device 1 may not expect to receive more than eight "TCI state pairs" in an activation command.

[0263] When the terminal device 1 transmits a first PUCCH in a first slot, the mapping between the TCI state and the code point may be applied from a second slot. The first PUCCH may be accompanied by first HARQ-ACK information. The first PUCCH may be transmitted corresponding to a first PDSCH. The first PDSCH may carry an activation command.

[0264] When the first higher layer parameter is configured, and the first time offset is greater than or equal to the first value, and after the terminal device 1 receives the initial configuration of the TCI state (the TCI state to be configured), and before an activation command (the TCI state to be activated) is received, the DMRS port of the PDSCH may be the SS / PBCH block and the QCL for QCL type A. The first higher layer parameter may be configured 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.

[0265] When the first higher layer parameter is configured, 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 higher layer parameter may be tci-PresentInDCI set to 'enabled'. The first higher layer parameter may be tci-PresentInDCI set to 'enabled' for the CORESET that schedules the PDSCH or multicast PDSCH. The first higher layer parameter may be tci-PresentDCI-1-2.

[0266] If the first DCI format schedules a PDSCH and the time offset is greater than or equal to a threshold, the TCI state or QCL assumption for the PDSCH may be the same as the TCI state or QCL assumption applied for the CORESET used for the PDCCH to determine the PDSCH antenna port QCL. The time offset may be the time offset between reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL. The first DCI format may not include a TCI field.

[0267] If SFN is configured for the PDCCH, if SFN is configured for the PDSCH, if the PDSCH is scheduled according to a DCI format, if the time offset is equal to or greater than a threshold, and if the default beam is supported, the QCL assumption or TCI state for the PDSCH may be the same as the QCL assumption or TCI state applied for CORESET. Also, if dynamic switching is not supported, CORESET may be activated in two TCI states. CORESET may be the CORESET for receiving DL DCI. If SFN is configured for the PDCCH, if SFN is configured for the PDSCH, if the PDSCH is scheduled according to a DCI format, if the time offset is equal to or greater than a threshold, and if the default beam is not supported, the presence of a TCI field may be assumed. Configuring SFN for the PDCCH may mean configuring the higher layer parameter sfnSchemePdcch. Configuring SFN for the PDSCH may mean configuring the higher layer parameter sfnSchemePdsch. The DCI format may be any 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.

[0268] If SFN is configured for PDSCH, and if SFN is not configured for PDCCH, and if PDSCH is scheduled by DCI format 1_1 / 1_2, and if the time offset is greater than or equal to a threshold, the presence of the TCI field may be expected.

[0269] If the PDSCH is scheduled by DCI format 1_0 / 1_1 / 1_2, and SFN scheme A is configured for the PDCCH, and SFN is not configured for the PDSCH, and there is no TCI codepoint (a codepoint in the TCI field) with two TCI states, and the time offset is equal to or greater than a threshold, and the CORESET that schedules the PDSCH is indicated by two TCI states, 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 with 'sfnSchemeA' set.

[0270] If the unified TCI state is not configured, and the time offset is smaller than the threshold, and at least one configured TCI state includes a qcl-Type set to typeD, the DMRS port of the PDSCH may be an RS and QCL for a certain QCL parameter. The certain QCL parameter may be used for the 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.

[0271] If the 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 set to typeD, and the indicated TCI state is associated with the PCI (Physical Cell ID) of the serving cell, the indicated TCI state may be applied to PDSCH reception. If the 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 set to typeD, and the indicated TCI state is associated with the PCI (Physical Cell ID) of the serving cell, the DMRS port of the PDSCH in the serving cell may use 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 mean configuring the higher layer parameter dl-OrJointTCI-StateList.

[0272] If a first terminal capability is indicated to the terminal device 1, 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, which is set to '1'.

[0273] When SFN scheme A is configured for the PDCCH and CORESET is activated in two TCI states, the DMRS ports of the PDCCH in CORESET may be DL RS (downlink reference signal) and QCL for the two TCI states. When SFN scheme B is configured for the PDCCH and CORESET is activated in 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 mean configuring sfnSchemePdcch with 'sfnSchemeA' set. Configuring SFN scheme B for the PDCCH may mean configuring sfnSchemePdcch with 'sfnSchemeB' set.

[0274] Coherent Joint Transmission (CJT) may be configured for the PDSCH. Configuring CJT may also mean configuring the higher layer parameter cjtSchemePDSCH. When CJT is configured for the PDSCH, the DMRS port of the PDSCH may be QCL for reference signals of two indicated TCI states and QCL type A, excluding the QCL parameters {Doppler shift, Doppler spread}.

[0275] When SFN scheme A is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be the two TCI states DL-RS and QCL. When SFN scheme B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be the two TCI states DL-RS and QCL, and the second TCI state may not include the QCL parameters {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 mean configuring sfnSchemePdsch with 'sfnSchemeA' set. Configuring SFN scheme B for the PDSCH may mean configuring sfnSchemePdsch with 'sfnSchemeB' set. The second of the two TCI states may not include the QCL parameters {Doppler shift, Doppler spread}.

[0276] When the unified TCI state is configured, and when the multi-DCI mode is configured, and when 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. Configuring the unified TCI state may mean that dl-OrJointTCI-StateList or TCI-UL-State is configured. Configuring the multi-DCI mode may mean that the higher layer parameter PDCCH-Config, which includes two different CORESET pool index values, is configured. The CORESET pool index may be configured in the higher layer parameter ControlResourceSet.

[0277] When the unified TCI state is configured, and the terminal device 1 has two indicated TCI-States, and the terminal capability of the default beam is not reported, and if the time offset is smaller than a threshold, 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 a 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). For example, FR2 may be a frequency range from 24250 MHz to 52600 MHz. The time offset may be an offset between the reception of scheduled DCI format 1_0 / 1_1 / 1_2 and scheduled PDSCH reception. The time offset may be an offset between the reception of activated DCI format 1_0 / 1_1 / 1_2 and activated PDSCH reception. The threshold may be timeDurationForQCL or a value smaller than timeDurationForQCL.

[0278] When a unified TCI state is configured, and when the terminal device 1 has two indicated TCI-States, and when a certain condition is met, the higher layer parameter applyIndicatedTCIState may indicate that the first indicated TCI-State, the second indicated TCI-State, or the two indicated TCI-States is applied to PDSCH reception scheduled by DCI format 1_0. The higher 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. When CJT is configured for the PDSCH or SFN is configured for the PDSCH, the higher layer parameter applyIndicatedTCIState may indicate "both". The certain condition may be FR1 (Frequency Range 1). One condition may be that the terminal capability of the default beam is reported. Another condition may be that the time offset is greater than or equal to a threshold.

[0279] 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 upper layer parameter applyIndicatedTCIState is not set, the first indicated TCI-State may be applied to the PDSCH scheduled by DCI format 1_0.

[0280] When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "00", a first indicated DL / Joint TCI state may be applied to the PDSCH. When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "01", a second indicated DL / Joint TCI state may be applied to the PDSCH. When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "10", two indicated DL / Joint TCI states may be applied to the PDSCH. If the unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and certain conditions are met, and 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.

[0281] The terminal device 1 may receive a DMRS for a PDSCH scheduled by a PDCCH with a DCI format. When 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'). When the first higher layer parameter is configured and when multiple PDSCHs overlap in the time-frequency domain due to multiple PDCCHs, different DMRS configurations may not be expected, and the two TCI states may not indicate DMRS ports within one CDM group. The first higher 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.

[0282] In the downlink, a serving cell may support up to 16 or 32 HARQ processes. 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.

[0283] In response to detecting a PDCCH with a DCI format, the terminal device 1 may receive (decode) a corresponding PDSCH as indicated by the DCI format.

[0284] The terminal device 1 may assume that the DMRS port of the first PDSCH is the 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 the second SS / PBCH block or the 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 the second SS / PBCH block or the second CSI-RS resource and QCL with respect to the first QCL parameter. The third PDSCH may be scheduled with the RA-RNTI for the random access procedure triggered by the first PDCCH order. The first QCL parameters may include some or all of a Doppler shift, a Doppler spread, an average delay, a delay spread, and spatial RX parameters.

[0285] If decoding of a PDCCH with a CRC scrambled by the CS-RNTI is configured by a higher layer, the terminal device 1 may receive a PDSCH without a corresponding PDCCH.

[0286] If a first higher layer parameter is configured, the terminal device 1 may receive multiple PDCCHs. The first higher layer parameter may be PDCCH-Config. The first higher 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 simultaneously receive the multiple PDSCHs. The different CORESETs may have different CORESET pool index (coresetPoolIndex) values.

[0287] If CORESET (higher layer parameter ControlResourceSet) does not accompany a CORESET pool index (higher 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 accompany a CORESET pool index.

[0288] A first physical cell ID associated with a first CORESET may be different from a second physical cell ID associated with a second CORESET. For example, the first CORESET and the second CORESET may be associated with different physical cell IDs via activated TCI states. The first CORESET and the second CORESET may correspond to different CORESET pool indices.

[0289] 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 be receiving the PDCCH candidates.

[0290] When PDCCH reception includes two PDCCH candidates from the search space set, one PDCCH monitoring occasion may be the union of the PDCCH monitoring occasions for the two PDCCH candidates, and the start of PDCCH reception may be the start of the earlier PDCCH candidate, and the end of PDCCH reception may be the end of the later PDCCH candidate.

[0291] In one BWP in one serving cell, if no CORESET pool index is provided, a CORESET of 3 or less may be provided. In one BWP in one serving cell, if the same CORESET pool index is provided for all CORESETs, a CORESET of 3 or less may be provided. In one BWP in one serving cell, if CORESET pool index 0 is provided for the first CORESET and CORESET pool index 1 is provided for the second CORESET, a CORESET of 5 or less may be provided.

[0292] For each CORESET, at least a CORESET index may be provided by a first higher layer parameter, a QCL relation (antenna port QCL) may be provided by a second higher layer parameter, and an indication of whether a TCI field is present may be provided 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.

[0293] If a value of 0 is provided for the search space ID, 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.

[0294] When two TCI states are provided in one CORESET, 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.

[0295] If a TCI state setting is not provided in one CORESET, or if two or more TCI state initial settings are provided and a MAC CE activation command is not received, the terminal device 1 may assume that the DMRS antenna port associated with PDCCH reception is the SS / PBCH block and QCL. The SS / PBCH block may be identified by the terminal device 1 during the initial access procedure. One CORESET may be a CORESET without index 0.

[0296] If two or more TCI state settings are provided in one CORESET by reconfiguration with synch and if a MAC CE activation command is not received, the terminal device 1 may assume that the DMRS antenna port associated with PDCCH reception is the SS / PBCH block or CSI-RS resource and QCL. The SS / PBCH block or CSI-RS resource may be identified to the terminal device 1 in a random access procedure initiated by reconfiguration with synch. One CORESET may also be a CORESET without index 0.

[0297] When the unified TCI state is set in a CORESET with index 0, the terminal device 1 may assume that the DMRS antenna port (DMRS port) for first PDCCH reception and the DMRS antenna port for 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, which is set to 'enable'. The first PDSCH reception may be scheduled by the DCI format provided by the first PDCCH reception.

[0298] If a unified TCI state is configured in CORESET and two indicated TCI states are maintained, and if the upper layer parameter applyIndicatedTCIState is configured for CORESET to be set to "first", the DMRS port for PDCCH reception in 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 CORESET and two indicated TCI states are maintained, and if the upper layer parameter applyIndicatedTCIState is configured for CORESET to be set to "second", the DMRS port for PDCCH reception in CORESET may be the reference signal and QCL provided by the second indicated TCI state (TCI-State). When a unified TCI state is set in CORESET and two indicated TCI states are maintained, and when the upper layer parameter applyIndicatedTCIState set to "both" is set for CORESET, the DMRS port for PDCCH reception in CORESET may be the reference signal and QCL provided by the two indicated TCI states (TCI-State). Setting a unified TCI state may mean that dl-OrJointTCI-StateList is provided. Maintaining two indicated TCI states may mean that the terminal device 1 has two indicated TCI states. Maintaining two indicated TCI states may mean that a first TCI state and a second TCI state are indicated to the terminal device 1.

[0299] If a unified TCI state is not configured in a CORESET with index 0, the DMRS ports for PDCCH reception in the CORESET may be the reference signal and QCL configured by the TCI state indicated by the MAC CE activation command for the CORESET. If a unified TCI state is not configured in a CORESET with index 0, the DMRS ports for PDCCH reception in the CORESET may be the SS / PBCH block and QCL.

[0300] If one TCI state is provided in a CORESET with an index other than 0, or if a MAC CE activation command is received for one or two provided TCI states, the terminal device 1 may assume that the DMRS antenna port for PDCCH reception is one or more DL RSs and QCLs configured by the TCI state. The TCI state indicated by the MAC CE activation command may be the "activated TCI state."

[0301] When a unified TCI state is configured, the DMRS antenna ports for PDCCH reception in one CORESET with an 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.

[0302] If the unified TCI state is configured and the multi-DCI mode is configured, the DMRS port for the first PDSCH reception may be a first reference signal and QCL. The first PDSCH reception may be scheduled according to a DCI format provided by PDCCH reception in the first CORESETs. The first reference signal may be provided by a "directed TCI-State" corresponding to the first CORESETs. If the unified TCI state is configured and the multi-DCI mode is configured, the DMRS port for the second PDSCH reception may be a second reference signal and QCL. The second PDSCH reception may be scheduled according to a DCI format provided by PDCCH reception in the second CORESETs. The second reference signal may be provided by a "directed TCI-State" corresponding to the second CORESETs. Configuring multi-DCI mode may involve 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.

[0303] When the multi-DCI mode is configured, the MAC CE activation command for the first CORESETs may include a first CORESET pool index. When the multi-DCI mode is configured, the MAC CE activation command for the second CORESETs may include a second CORESET pool index. Also, when the inter-cell multi-TRP mode is configured, the "activated TCI state" for the first CORESETs may be associated with a physical cell ID from the serving cell (e.g., ServingCellConfigCommon), and the "activated TCI state" for the second CORESETs may be associated with a physical cell ID from an additional PCI index (e.g., AdditionalPCI). Configuring the inter-cell multi-TRP mode may also mean configuring SSB_MTC_AdditionalPCI. Configuring the inter-cell multi-TRP mode may also mean configuring an additional PCI index. Configuring the multi-DCI mode may also mean providing two CORESET pool indexes, values ​​0 and 1, for the first and second CORESETs.

[0304] Ten or fewer search space sets may be provided in one BWP in one serving cell. For each search space set, at least a search space set index may be determined by a first higher layer parameter, a relationship between the search space set and a CORESET may be determined by a second higher layer parameter, and linked search space sets (search space set indexes) may be determined by a third higher layer parameter. The first higher layer parameter may be searchSpaceId. The second higher layer parameter may be controlResourceSetId. For the first search space set, a second search space set index may be provided by a third higher layer parameter. The third higher layer parameter may link the first search space set and the second search space set. The third higher layer parameter may be searchSpaceLinking. Providing the third higher layer parameter may mean that search space linking is applied.

[0305] When the first search space set and the second search space set are linked, 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. Linking the first search space set and the second search space set may be such that the first search space set includes a searchSpaceLinking with the second search space set, and the second search space set includes a searchSpaceLinking with the first search space set.

[0306] When the first search space set and the second search space set are linked and the third search space set is not linked, 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. Furthermore, the terminal device 1 may monitor the third PDCCH candidate corresponding to the third search space set for the second DCI format. Furthermore, in one CORESET and in the same symbol in one slot, 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. Furthermore, the third PDCCH candidate corresponding to the third search space set may not be counted for monitoring. Furthermore, the detected DCI format may not be assumed to be the first DCI format.

[0307] If the first search area set and the second search area set are linked, and if the third search area set and the fourth search area set are linked, and if the size of the detected DCI format is the same, the terminal device 1 may expect different CCEs or different scrambling in one CORESET.

[0308] When the terminal device monitors multiple PDCCHs in a first CORESET and a second 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 'type D' property as the first CORESET. Repetition may be applied for the PDCCH. The application of repetition for the PDCCH may be provided as two-QCLTypeDforPDCCHRepetition.

[0309] When the first search space set and the second search space set are linked, the terminal device 1 may detect that the one that finishes later from the two PDCCH receptions is a DCI format.

[0310] The terminal device 1 may be configured with an upper layer parameter TCI-UL-State. For example, the terminal device 1 may configure one list 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 configuration) may include a parameter for configuring one reference signal. For example, each TCI-UL-State may include a parameter for configuring one reference signal for determining uplink transmit spatial filters 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.

[0311] The UL-TCIState may be an upper layer parameter TCI-UL-State. The UL-TCIState may be set by the upper layer parameter TCI-UL-State. The upper layer parameter TCI-UL-State may associate one or two downlink reference signals with one corresponding QCL type.

[0312] The higher 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. Configuring the unified TCI state may mean configuring 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 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 uplink timing adjustment.

[0313] When some or all of Condition 1, Condition 2, and Condition 3 are satisfied, 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 the multi-DCI mode is configured. Configuring the multi-DCI mode may be that a PDCCH configuration including two different CORESET pool indices is configured. Configuring the multi-DCI mode may be that SSB-MTC-AdditionalPCI is configured and a PDCCH configuration including two different CORESET pool indices is configured. Configuring the multi-DCI mode may be that a PDCCH-Config including two different CORESET pool index values ​​in different CORESETs is configured. Condition 2 may be that TwoTA is configured. Configuring TwoTA may be that the higher layer parameter twoTAGs is configured. Configuring TwoTA may be that two TAG IDs are configured in one serving cell. Condition 3 may be that the unified TCI state is configured. Setting the unified TCI state may be setting the higher layer parameter dl-OrJointTCI-StateList or the higher layer parameter TCI-UL-State. Conditions 1, 2, and 3 may be satisfied for one serving cell.

[0314] If terminal capabilities are not reported, it may not be expected that the unified TCI state associated with one TAG ID (or subTAG ID) corresponds 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 capability may be the ability for one unified TCI state to correspond to two TAGs.

[0315] When a unified TCI state is configured, the terminal device 1 may transmit a PUSCH according to a spatial relation. For example, the spatial relation may be a relation based on one reference signal (RS). For example, the one reference signal may be a reference signal for determining an uplink transmit spatial filter. The one reference signal may be a reference signal configured with qcl-Type set to type D 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, the UL TCI state, or the unified TCI state indicated by DCI format 1_1 or DCI format 1_2. The indicated TCI-State (Indicated TCI-State) may be the TCI state, the DL / Joint TCI state, or the unified TCI state indicated by DCI format 1_1 or DCI format 1_2.

[0316] When the unified TCI state is configured, when two indicated TCI states are maintained, and when a PUSCH transmission corresponding to the configured uplink grant is configured, the higher layer parameter applyIndicatedTCIState may be expected to be configured. The higher layer parameter applyIndicatedTCIState may indicate applying a first indicated TCI state to the PUSCH, applying a second indicated TCI state to the PUSCH, or applying two indicated TCI states to the PUSCH. When 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. When the unified TCI state is configured, when two indicated TCI states are maintained, and when a PUSCH transmission corresponding to the configured uplink grant is configured, and when multi-DCI mode is configured, 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.

[0317] If the unified TCI state is configured, two indicated TCI states are maintained, two SRS resource sets are configured, and the SRS resource set indication field in the DCI format indicates "00", a first indicated Joint / UL TCI state may be applied to the PUSCH. If the unified TCI state is configured, two indicated TCI states are maintained, two SRS resource sets are configured, and the SRS resource set indication field in the DCI format indicates "01", a second indicated Joint / UL TCI state may be applied to the PUSCH. If the unified TCI state is configured, two indicated TCI states are maintained, two SRS resource sets are configured, and the SRS resource set indication field in the DCI format indicates "10" or "11", a first indicated Joint / UL TCI state and a 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.

[0318] A MAC protocol data unit (MAC PDU) may be a bit string whose length is byte-aligned (i.e., a multiple of 8 bits). A MAC service data unit (MAC SDU) may be a bit string whose length is byte-aligned (i.e., a multiple of 8 bits). A MAC SDU may be contained in 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 located immediately before the corresponding MAC SDU, MAC CE, or padding.

[0319] A MAC protocol data unit (MAC PDU) 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). Each MAC subPDU may consist of one MAC subheader and one MAC CE. Each MAC subPDU may consist of one MAC subheader and padding. 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.

[0320] The first MAC CE may be an activation command A. The first MAC CE may be a MAC CE for activation or deactivation of a TCI state for a PDSCH (UE-specific PDSCH). The first MAC subheader may identify a MAC CE for activation / deactivation of a TCI state for a PDSCH. For example, the first MAC subheader may be accompanied by a first Logical channel ID (LCID). For example, the value of the first LCID may be "TCI States Activation / Deactivation for UE-specific PDSCH."

[0321] FIG. 9 is a diagram showing an example of an activation command A according to one aspect of this embodiment. 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. i The "T" field may indicate the activation / deactivation status of the TCI state with TCI state ID i. i " field set to 1 may indicate that the TCI state with TCI state ID i is activated. i " field set to 1 may indicate that the TCI state with TCI state ID i is mapped to one code point in the 'Transmission Configuration Indication field' of the DCI. i " field set to 0 may indicate that the TCI state with TCI state ID i is deactivated. i" field set to 1 may indicate that the TCI state with TCI state ID i is not mapped to one code point in the 'Transmission Configuration Indication field' of the DCI. i may be a TCI state ID (or TCI-StateID). A TCI state may be accompanied by 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) configured with the CORESET Pool ID (CORESET Pool Index). The first mapping is specific to the "activated TCI states" and the "T i Setting the CORESET Pool ID field to 1 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 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.

[0322] The second MAC CE may be an activation command B. The second MAC CE may be a MAC CE for activation or deactivation of a TCI state for a PDSCH (UE-specific PDSCH). The second MAC subheader may identify a MAC CE for activation / deactivation of a TCI state for a PDSCH. For example, the second MAC subheader may be accompanied by a second LCID (Logical channel ID). The second LCID may be an eLCID. For example, the value of the second LCID may be "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH."

[0323] FIG. 10 is a diagram showing an example of an activation command B according to one aspect of this embodiment. i " field is the TCI state ID i,2 It may also indicate whether an octet containing i " field is set to 1, TCI State ID i,2 There may be an octet containing "C i If the " field is set to 0, the TCI state ID i,2 The octet containing the TCI Status ID may not be present. i,j The field may indicate a TCI state identified by a TCI State ID (TCI-StateId). i,j may represent the j-th TCI state indicated for the i-th codepoint of the DCI 'Transmission configuration indication' field. i,2 is "C i " may be optional based on the indication of the field. i may be the index of the codepoint in the DCI 'Transmission configuration indicating' field. j may be 1 or 2.

[0324] 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. For example, the third MAC subheader may be accompanied by a third LCID (Logical channel ID). The third LCID may be an eLCID. For example, the value of the third LCID may be "Unified TCI States Activation / Deactivation MAC CE."

[0325] FIG. 11 is a diagram showing an example of an activation command C according to an aspect of this embodiment. The DL BWP ID field may indicate one downlink BWP to which MAC CE is applied as one code point in 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 in the DCI 'bandwidth part indicator' field. i The " field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, "P i If the " field is set to 1, the ith TCI codepoint may contain both DL TCI status and UL TCI status. For example, iIf the "D / U" field is set to 0, the i-th TCI code point may contain one of the DL TCI state and the 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). If the "D / U" field is set to 1, a 7-bit long "TCI state ID" may be used. If the "D / U" field is set to 0, the most significant bit of the "TCI state ID" may be used. The first 6 bits may be considered as reserved, and the remaining 6 bits may indicate the ID of the UL-TCIState (UL-TCIState-Id). 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 that represents both the DL TCI state and the UL TCI state. 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.

[0326] 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. For example, 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. For example, 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. For example, the fourth MAC subheader may be accompanied by a fourth LCID (Logical channel ID). For example, 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. For example, the value of the fourth LCID may be "Enhanced unified TCI States Activation / Deactivation MAC CE 1". For example, the value of the fifth LCID may be "Enhanced unified TCI States Activation / Deactivation MAC CE 2".

[0327] FIG. 12 is a diagram showing an example of an activation command D according to one aspect of this 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 in the 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 in the DCI 'bandwidth part indicator' field. "P i The " field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, "P i If the " field is set to 1, the ith TCI codepoint may contain both DL TCI status and UL TCI status. For example, i If the " field is set to 0, the i-th TCI codepoint may contain either DL TCI state or UL TCI state. i The " field may indicate whether each TCI codepoint is for joint (both DL and UL) / DL or UL. For example, "D / U i If the " field is set to 1, the i-th TCI codepoint may be for DL / joint. For example, "D / U i If the " field is set to 0, the i-th TCI codepoint may be for UL. j The "T" field may indicate the activation / deactivation status of the TCI state with TCI state ID j. j" field set to 1 may indicate that the TCI state with TCI state ID j is activated. j " field 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. j " field set to 0 may indicate that the TCI state with TCI state ID j is deactivated. j " field 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}. For example, if the ith TCI code point corresponds to a UL TCI state, then "T j The " field may indicate the activation / deactivation status of the TCI state with TCI state ID j-128. For example, if the ith TCI codepoint corresponds to the DL TCI state or the Joint TCI state, then "T j The " field may indicate the activation / deactivation status of the TCI state with TCI state ID j-64. For example, if the ith TCI codepoint corresponds to the UL TCI state, then "T j" field set to 1 may indicate that the TCI state with TCI state ID j-128 is activated. For example, if the i-th TCI codepoint corresponds to the UL TCI state, then "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. For example, if the i-th TCI codepoint corresponds to the DL TCI state or the Joint TCI state, then "T j " field set to 1 may indicate that the TCI state with TCI state ID j-64 is activated. For example, if the i-th TCI codepoint corresponds to the DL TCI state or the Joint TCI state, then "T j The " field set to 1 may indicate that the TCI state with TCI state ID j-64 is mapped to the i-th TCI code point. The CORESET Pool ID field may indicate that the second mapping is specific to the CORESET ID (ControlResourceSetId) set with the CORESET Pool ID (CORESET Pool Index). The second mapping is specific to the "TCI state to be activated" and the "TCI state to be activated" field. iSetting the CORESET Pool ID field to 1 may indicate that 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 MAC CE applies to downlink or uplink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET Pool Index) of value 0. If CORESET Pool Index (coresetPoolIndex) is not set, the CORESET Pool ID field in the fourth MAC CE may be ignored.

[0328] FIG. 13 is a diagram showing an example of an activation command E according to one aspect of this embodiment. The CORESET pool ID field in FIG. 13 may be reserved. i,j The " field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, "P i,j If the " field is set to 1, the j-th TCI state at the i-th TCI codepoint may be two (e.g., DL TCI state and UL TCI state). For example, i,j If the "D / U" field is set to 0, the j-th TCI state at the i-th TCI codepoint may be one (e.g., DL TCI state or UL TCI state). j The " field may indicate whether the TCI state ID in the same octet is for joint (both DL and UL) / DL or UL. 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, "D / Uj If the " field is set to 1, the TCI state ID in the same octet may be for DL / joint. For example, "D / U j If the "TCI state ID" field is set to 0, the TCI state ID in the same octet may be for UL. i,j The " 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). j If the " field is set to 1, the 7-bit "TCI state ID i,j " may be used. j If the "TCI state ID" field is set to 0, i,j The most significant bit of " may be considered as a reserve, and the remaining 6 bits may indicate the ID of the UL-TCIState (UL TCI State Id, UL-TCIState-Id).

[0329] In FIG. 13, j may correspond to a CORESET pool ID (CORESET pool index). For example, j=1 may correspond to a CORESET pool ID (CORESET pool index)=0. For example, j=2 may correspond to a CORESET pool ID (CORESET pool index)=1. For example, j=0 may correspond to a CORESET pool ID (CORESET pool index)=0. For example, j=1 may correspond to a CORESET pool ID (CORESET pool index)=1. Whether j corresponds to a CORESET pool ID (CORESET pool index) may be determined by the "J" field. For example, if the "J" field is set to 1, 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 in one codepoint. "P i,jThe " field may indicate whether each TCI codepoint of the DCI associated with the CORESET Pool ID corresponding to j has multiple TCI states or one TCI state. For example, "P i,j If the " field is set to 1, it may correspond to both the DL TCI state and the UL TCI state of the ith TCI codepoint of the DCI associated with the CORESET Pool ID corresponding to j. For example, i,j If the " field is set to 0, it may correspond to either the DL TCI state or the 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 (upper layer parameter coresetPoolIndex) is not set, j may not correspond to a CORESET Pool ID.

[0330] The activation command F may be a MAC CE for TCI state indication for the PDCCH. The activation command F may be composed of a 5-bit serving cell ID, a 4-bit CORESET ID, and a 7-bit TCI state ID.

[0331] The activation command G may be a MAC CE for TCI state indication for the PDCCH. The activation command G may be composed 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. When 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. When SFN is applied for the PDCCH, the activation command G may be applied. When SFN for the PDCCH is applied, the sfnSchemePdcch may be configured.

[0332] 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.

[0333] One TA offset (Timing advance offset) value for one serving cell may be provided by a higher layer parameter. When the multi-DCI mode is configured, two TA offset values ​​for one transmission may be provided by two higher layer parameters. A transmission may be a transmission with multiple TCI states associated with first and 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. The configuration of the multi-DCI mode may mean that two CORESET pool index values, 0 and 1, are provided for the first and second CORESETs in one serving cell. The second TA offset value may be provided for a transmission with a second spatial domain filter. The first TA offset value may be provided for a transmission with the first spatial domain filter. The second spatial domain filter may correspond to a TCI state associated with a physical cell ID from a cell 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 value of the first TA offset may correspond to some or all of the first TAG, the first TAG ID, the first subTAG, and the first subTAG ID. The value of the second TA offset 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.For example, the first TCI state and the second TCI state may be a Joint TCI state or a UL TCI state. One or both of the Joint TCI state and the DL TCI state may be provided by dl-OrJointTCI-StateList. The UL TCI state may be provided by TCI-UL-State (or ul-TCIState-List).

[0334] A timing advance (TA) 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. If higher layer parameters are not provided, the terminal device 1 may determine the value of the TA offset. The terminal device 1 may determine two TA offset values ​​in one serving cell. The TA offset value is N TA,offset The higher layer parameter may be n-TimingAdvanceOffset. Determining the TA may be adjusting the uplink timing. That is, the uplink timing may be referred to as TA.

[0335] When two uplink carriers are configured in one serving cell, one TA offset value may be applied to the two uplink carriers for transmission in the serving cell associated with the same TAG or the same subTAG.

[0336] 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 for PUSCH / SRS / PUCCH transmission in one or more serving cells belonging to one TAG. TA,offet The uplink timing may be adjusted based on the value of N TA,offset may be the same for all serving cells in one TAG. TA,offset may not be the same for all serving cells in one TAG. TA,offset The uplink timing may be adjusted based on one or both of the values ​​of Λ and TA commands. The uplink timing may be the same for all serving cells in one TAG.

[0337] In response to receiving one TA command (Timing advance command) for one subTAG, the terminal device 1 may adjust the 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 the uplink timing for PUSCH / SRS / PUCCH transmission in one or more serving cells belonging to one subTAG and one or both of the TRPs. TA,offsetmay be the same for all serving cells in one subTAG. Uplink timing may be the same for all serving cells in one subTAG. Two subTAGs may be used in one serving cell.

[0338] The TAG ID may be used to identify a TAG or a subTAG. The subTAG ID may be used to identify a subTAG. When TwoTA is configured, one subTAG ID may be associated with each TAG. For example, when TwoTA is configured, two subTAG IDs may be determined from M TAG IDs. When TwoTA is configured, two TAGs in one serving cell may be associated with two subTAG IDs. When TwoTA is configured, a TAG associated with a serving cell may be associated with a first subTAG ID, and a TAG associated with a non-serving cell may be associated with a second subTAG ID. A non-serving cell may be a cell corresponding to an additional PCI index. A non-serving cell may be a cell associated with an additional PCI. When multi-DCI mode is configured, TwoTA may be configured. The non-serving cell may be different from a candidate cell. A candidate cell may be different from a cell corresponding to an additional PCI index.

[0339] A first uplink timing may be determined based on a timing adjustment indication for one TAG from the MCG, a second uplink timing may be determined based on a timing adjustment indication for one TAG from the SCG, or a first uplink timing and a second uplink timing may be determined based on timing adjustment indications for two TAGs from the MCG.

[0340] The TA command may be changed based on the subcarrier spacing. For example, for a subcarrier spacing setting μ, one TA command for one TAG may indicate a change in uplink timing. For example, the uplink timing may be 16*64*Tc / 2 μ "*" may be a multiplication operator.

[0341] The TA (Timing advance) of the random access preamble may be zero.

[0342] The TA command may be included in a random access response. For example, a TA command for one TAG (or subTAG) may be included in a random access response related to one TAG (or subTAG). For example, 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. For example, the TA command may be an Absolute timing advance command MAC CE. The TA command may be included in a cell switch command. For example, the TA command in a cell switch command may not be related to a subTAG ID. For example, the TA command in a cell switch command may not be related to a TAG corresponding to a serving cell. The subTAG ID may be one or two TAG IDs configured in one serving cell. The TA command T in a random access response, an Absolute timing advance command MAC CE, or a cell switch command A For one TAG, N TA You may also specify a value for T. A may be an integer between 0 and 3846. For example, N TA is T A *16*64 / 2 μ N TAmay be related to the subcarrier spacing of a certain uplink transmission. For example, the certain uplink transmission may be an uplink transmission from the terminal device 1. For example, the certain uplink transmission may be the first uplink transmission after receiving a random access response. For example, the certain uplink transmission may be the first uplink transmission after receiving an absolute timing advance command MAC CE. For example, the certain uplink transmission may be the first uplink transmission after receiving a cell switch command. T A may be an index value. The uplink transmission may be an uplink channel transmission. In the random access procedure, whether to receive a cell switch command or a random access response may be determined by a higher layer parameter. For example, the random access procedure may be initiated (triggered) by a PDCCH order.

[0343] TA Command T A For one TAG, the current N TA You can also specify the value adjustment. For example, the TA command T A is N TA,old From N TA,new N TA,new is N TA,old +(T A -31)*16*64 / 2 μ For example, T A may be an integer between 0 and 63.

[0344] If the terminal device has one or more active uplink BWPs, 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. For example, N for one uplink BWP with initial subcarrier spacing. TA,newmay be rounded to fit the timing advance granularity for one uplink BWP with initial subcarrier spacing. Rounding a value may involve rounding off a value. For example, N TA,new may be rounded.

[0345] N by positive value TA The adjustment of N may indicate an advance in uplink transmission timing (uplink timing) for one TAG (Timing advance group). TA The adjustment may indicate a delaying of uplink transmission timing for one TAG.

[0346] If a TA command is received in the first slot n, an uplink transmission timing adjustment may be applied starting 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 the first slot n to k+1+2. μ *K offset It may be a slot after a slot. offset may be provided by higher layer parameters. k is the sum of ceil(N subframe,μ slot ・(N T,1 +N T,2 +N TA,max +0.5) / T sf ) may be used. T,1 The unit of N may be milliseconds. T,1 may be a duration in milliseconds of N1 symbols, which may correspond to a PDSCH processing time. T,2may be a duration in milliseconds of N2 symbols, which may correspond to a PUSCH preparation time. TA,max N may be the maximum timing advance value (TA) in milliseconds. TA,max N may be the maximum TA value that can be provided by the 12-bit TA command field. subframe,μ slot may be the number of slots in one subframe. sf T may be 1 millisecond. sf may be the duration of a subframe. offset is K cell,offset -K UE,offset It may be. K cell,offset may be provided by a higher layer parameter. UE,offset may be provided by one MAC CE command. cell,offset may be 0. UE,offset may be 0. One or both of N1 and N2 may be determined relative to the minimum subcarrier spacing (SCS). The minimum subcarrier spacing may be the smallest subcarrier spacing among the subcarrier spacings of all configured downlink BWPs and all configured uplink BWPs. When μ=0, N1 may be 14. Slots n and N subframe,μ slot may be determined relative to the minimum subcarrier spacing. TA,max may be determined relative to the minimum subcarrier spacing. Slot n may be the last slot of one or more slots that overlap with the slots for PDSCH reception. For PDSCH reception, T TA = 0. One TA command may be received in the PDSCH. A PDSCH containing one TA command may be received. The PDSCH may provide one TA command.

[0347] When the terminal device 1 changes the active uplink BWP, 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 a TA command and the time of applying an adjustment for uplink transmission timing, the terminal device 1 may determine a TA command based on the subcarrier spacing of the new active uplink BWP. When the active uplink BWP is changed after applying an adjustment for uplink transmission timing, the terminal device 1 may assume the same absolute timing advance command value (absolute timing advance command MAC CE). That is, a first absolute timing advance command value before changing the active uplink BWP may be the same as a second absolute timing advance command value after changing the active uplink BWP.

[0348] When the downlink timing is changed and the downlink timing is not corrected, the terminal device 1 TA When the downlink timing is changed and when the downlink timing is partially corrected by uplink timing adjustment without a TA command, the terminal device 1 may change N TAmay be changed. The uplink timing adjustment may be determining or changing the uplink timing. When TwoTA is configured and when terminal capability is not reported, 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 the active UL BWP. When TwoTA is configured and when terminal capability is reported, 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. The terminal capability may be a capability that allows the difference between the first downlink timing and the second downlink timing to be greater than the CP length. Configuring TwoTA may mean that the terminal device 1 operates with two TAGs in one BWP (e.g., active UL BWP) in one serving cell. Configuring TwoTA may mean that the terminal device 1 operates with two TAGs in one serving cell.

[0349] If TwoTA is not configured and one TA command causes two adjacent slots to overlap, the latter slot may be reduced. If TwoTA is configured and two uplink transmissions are scheduled, two uplink transmissions with different TAGs may not be expected to overlap. If TwoTA is configured and two uplink transmissions are not scheduled, the latter uplink transmission may be reduced. Not configuring TwoTA may mean operating with one TAG in one serving cell.

[0350] A TAG (Timing Advance Group) 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) may be a TAG that includes an SpCell. A STAG (Secondary TAG) may be a TAG that does not include an SpCell. 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.

[0351] 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). For example, a subTAG may be associated with one TRP. For example, 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, a TAG and a subTAG may be referred to as TAGs.

[0352] The RRC layer may configure one or more higher layer parameters for maintenance of uplink time alignment. For example, the RRC layer may configure a time alignment timer. For example, 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 a MAC entity considers multiple serving cells / TRPs to belong to the associated TAG / subTAG. For example, the time synchronization timer may be a time for uplink time alignment. That is, the time synchronization timer running may indicate that time synchronization has been achieved. That the time synchronization has been achieved may indicate that uplink timing has been determined (or adjusted). That is, the TA may perform time synchronization.

[0353] The RRC layer may configure one or more higher layer parameters for maintaining uplink time synchronization. For example, the RRC layer may configure multiple time synchronization timers. At least one of the multiple time synchronization timers may be associated with a TAG / subTAG.

[0354] A time synchronization timer may correspond to one subTAG. For example, 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. For example, the time synchronization timer may control the time at which the MAC entity considers one or more TRPs to belong to the subTAG.

[0355] The MAC entity may perform some or all of the first to fourth processes.

[0356] In the first process, a TA command MAC CE (Timing advance command MAC CE) is received and N TAIf N is held in the indicated TAG / subTAG, the MAC entity may apply the TA command for the indicated TAG / subTAG. In the first process, a TA command MAC CE (Timing advance command MAC CE) is received and N TA is held in 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.

[0357] 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. In the second process, if a random access preamble is not selected from a preamble in Contention-based random access (CBRA), the MAC entity may apply the TA command for one TAG / subTAG and may start or restart a time synchronization timer associated with the one TAG / subTAG. The TA command may be received via a random access response.

[0358] In a second process, when the time synchronization timer associated with a TAG / subTAG is not running, the MAC entity may apply a TA command for the TAG / subTAG and start the time synchronization timer. Furthermore, if contention resolution is not completed successfully, the MAC entity may stop the time synchronization timer.

[0359] In a second process, when a time synchronization timer associated with one subTAG is stopped, the MAC entity may apply a TA command in a random access response in the first random access procedure and start the time synchronization timer. Furthermore, if 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.

[0360] In the second process, if a random access preamble is selected from the preambles in the CBRA and if the time synchronization timer associated with one TAG / subTAG is running, the MAC entity may ignore the received TA command.

[0361] In a third process, if an Absolute Timing Advance Command is received for a Message A (MSGA) transmission containing a C-RNTI MAC CE, the MAC entity may apply the absolute TA command for the Primary TAG (PTAG) and may start or restart a time synchronization timer associated with the Primary TAG (PTAG). 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. In this case, the time synchronization timer associated with the PTAG may not be started or restarted.

[0362] In a third process, if an Absolute Timing Advance Command associated with a subTAG is received for a Message A (MSGA) transmission containing a C-RNTI MAC CE or a Message 1 transmission, the MAC entity may apply the absolute TA command for the subTAG and may start or restart the time synchronization timer associated with the subTAG.

[0363] The fourth operation may be an operation when the time synchronization timer expires. In the fourth operation, if the time synchronization timer is associated with a PTAG (or a subTAG associated with the first TRP), the MAC entity may perform some or all of the first to seventh suboperations. The first suboperation may be to flush all HARQ buffers for all serving cells. The second suboperation may be to notify RRC to release PUCCHs for all serving cells. The third suboperation may be to notify RRC to release SRSs for all serving cells. The fourth suboperation may be to clear configured downlink assignments and configured uplink grants. The fifth suboperation may be to clear PUSCH resources for semi-persistent CSI reporting. The sixth suboperation may be to consider all time synchronization timers as having expired. The seventh suboperation may be to clear N for all TAGs (or subTAGs). TA That is, if the time synchronization timer is not running, the MAC entity may maintain N TAIn the fourth process, if the time synchronization timer is associated with the STAG (or subTAG associated with the second TRP), the MAC entity may perform some or all of the eighth to thirteenth suboperations. The eighth suboperation may be to flush all HARQ buffers for serving cells belonging to this TAG (or this subTAG). The ninth suboperation may be to notify RRC to release PUCCH for serving cells belonging to this TAG (or this subTAG). The tenth suboperation may be to notify RRC to release SRS for serving cells belonging to this TAG (or this subTAG). The eleventh suboperation 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 clear N PUSCH resources for semi-static CSI reporting for serving cells belonging to this TAG (or this subTAG). TA It may also be to maintain.

[0364] 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. When an HARQ entity requests a new transmission for a transport block, the HARQ process may store MAC PDUs in the associated HARQ buffer.

[0365] If the MAC entity stops uplink transmission for the SCell because the maximum uplink transmission timing difference is exceeded, the MAC entity may consider the stoppage as expiring a time synchronization timer, which may be a time synchronization timer associated with the SCell.

[0366] If the time synchronization timer has expired, 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 for a serving cell. The uplink transmission may be an uplink transmission for a TRP. The time synchronization timer may be a time synchronization timer associated with a TAG to which a serving cell belongs. The time synchronization timer may be a time synchronization timer associated with a subTAG to which a serving cell belongs. The time synchronization timer may be a time synchronization timer associated with a subTAG to which a TRP belongs.

[0367] If the time synchronization timer associated with a subTAG has expired, 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 one or both of a random access preamble transmission and a message A transmission.

[0368] If the time synchronization timer associated with the PTAG is not running, the MAC entity may not perform uplink transmissions in any serving cell, which may not include random access preamble transmissions in the SpCell, and which may not include message A transmissions in the SpCell.

[0369] A MAC Protocol Data Unit (PDU) may be a byte-aligned bit string. A MAC PDU may be a transport block. For example, 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 Service Data Unit (SDU). Each MAC subPDU may consist of a MAC subheader and a MAC Control Element (CE). 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.

[0370] The TA command may be a MAC CE. Also, the TA command may be included in a MAC CE. For example, the TA command may be included in a TA command MAC CE. The TA command MAC CE may be composed of a TAG ID and a TA command. The TAG ID may indicate one TAG and / or one subTAG. A TAG including a 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 be composed of a TAG ID and a TA command. A You may also specify T A can be an integer between 0 and 63. Amay 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 certain LCID may be the LCID corresponding to index 61.

[0371] 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 is included in an absolute Timing advance command MAC CE. A You may also specify 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 eLCID corresponding to the index 316.

[0372] The TA command may be included in the random access response. For example, the TA command may be included in the MAC payload of the random access response. For example, the TA command may be included in the MAC payload of the random access response. A You may also specify T Amay 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. For example, the random access response may be a fallbackRAR. The TA command may be included in message B (MSGB). For example, the TA command may be included in the MAC payload of message B. The TA command may be included in a successRAR. The random access response may also include a TAG ID / subTAG ID. The 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 the SS / PBCH block index indicated by the PDCCH order. One TAG ID / subTAG ID may be determined based on the SS / PBCH block index indicated by the PDCCH order.

[0373] 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. Alternatively, random access may be triggered by the MAC entity. Random access may be triggered by a PDCCH order. Random access may be triggered by RRC. Random access may also be referred to as a random access procedure.

[0374] For example, random access may be triggered by an event. For example, an event may be initial access from the RRC_IDLE state. For example, an event may be an RRC connection re-establishment procedure. For example, an event may be arrival of uplink or downlink data in the RRC_CONNECTED state when the uplink synchronization state is 'non-synchronized'. For example, an event may be arrival of uplink data in the RRC_CONNECTED state when there are no PUCCH resources. For example, an event may be a failure of a scheduling request. For example, an event may be a request by RRC in response to handover. For example, an event may be RRC connection resume. For example, an event may be establishing time synchronization. For example, an event may be establishing time synchronization for a STAG. For example, an event may be establishing time synchronization with a serving cell / TRP. For example, an event may be requesting Other SI. For example, an event may be beam failure recovery. For example, an event may be TA acquisition. For example, an event may be secondary TA acquisition. An event may be the purpose of a random access procedure. An event may be cell switching.

[0375] The random access (random access type) may be a 4-step random access (4-step random access type). The random access (random access type) may be a 2-step random access (2-step random access type). The random access may support contention-based random access (CBRA). That is, the random access may be a CBRA. The random access may support contention-free random access (CFRA). That is, the random access may be a CFRA. For example, the random access may be a 4-step random access type CBRA. For example, the random access may be a 4-step random access type CFRA. For example, the random access may be a 2-step random access type CBRA. For example, the random access may be a 2-step random access type CFRA.

[0376] In a 4-step random access type CBRA, 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). In a 2-step random access type CBRA, the terminal device 1 may transmit message A (random access preamble and PUSCH payload) and receive message B (contention resolution). In a 4-step random access type CFRA, the terminal device 1 may receive an allocation of a random access preamble, transmit a random access preamble, and receive a random access response. In a 2-step random access type CFRA, the terminal device 1 may receive an allocation of a random access preamble and a PUSCH, transmit a random access preamble and a PUSCH, and receive a random access response.

[0377] If a CFRA resource is not configured, a Reference Signal Received Power (RSRP) threshold may be used to select one of the two-step random access type and the four-step random access type. If a four-step random access type CFRA resource is configured, the terminal device 1 may perform a four-step random access type random access. If a two-step random access type CFRA resource is configured, the terminal device 1 may perform a two-step random access type random access.

[0378] Message 1 may be configured with 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.

[0379] Message A may include one preamble in the PRACH. Message A may also include a payload in the PUSCH. After transmitting message A, the terminal device 1 may monitor for one response within a configured window. In CFRA, a dedicated preamble and PUSCH resources may be allocated for transmitting message A. In CFRA, in response to receiving one response, the terminal device 1 may terminate random access. In CBRA, if contention resolution is successful, the terminal device 1 may terminate random access. If a fallback indication is received in message B, 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 two-step random access type is not completed, the terminal device 1 may be configured to switch to the four-step random access type CBRA.

[0380] 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 an SCell may be initiated by a PDCCH order. The random access procedure in a cell associated with an additional PCI index may be initiated by a PDCCH order.

[0381] In the MAC entity, only one random access may be in progress at a time. If a first random access is in progress and a second random access is triggered, the terminal device 1 may continue 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.

[0382] For random access, the RRC may configure some or all of the first to ninth higher layer parameters. A first set of PRACH occasions for transmitting message 1 (random access preamble) may be configured by the first higher layer parameter. The first set may be used for message A PRACH. A second set of PRACH occasions for transmitting the random access preamble for message A may be configured by the first higher layer parameter. That is, the first higher layer parameter may determine the available set of PRACH occasions for transmitting the random access preamble. The PRACH occasions may be referred to as RA opportunities. The PRACH occasions may be referred to as RACH occasions.

[0383] Some or all of the first to ninth upper layer parameters may be referred to as a RACH configuration. 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. Configuring TwoTA may be configuring second TA acquisition. The RACH configuration may be associated with a candidate cell or the ID of a candidate cell. If TwoTA is configured, the RACH configuration may be associated with one additional PCI index. If early UL synchronization is configured, the RACH configuration may be associated with a candidate cell or an ID of a candidate cell. If early UL synchronization is configured, a RACH configuration associated with the candidate cell may be provided. Early UL synchronization may be configured for the candidate cell or for the RACH configuration corresponding to the candidate cell.

[0384] 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 determining, providing, or configuring two TAs (TAGs or subTAGs) in one serving cell. The first upper layer parameter may be provided as a configuration for early UL synchronization.

[0385] The power of the random access preamble may be set by a third higher layer parameter, for example, the power of the initial (first transmission) random access preamble may be set by a third higher layer parameter.

[0386] The RSRP threshold may be configured by a fourth higher layer parameter. For example, the RSRP threshold may be the RSRP threshold for SS / PBCH block selection or CSI-RS selection. For example, the RSRP threshold may be the RSRP threshold for selection between two uplink carriers. The two uplink carriers may be a normal uplink (NUL) and a supplementary uplink (SUL).

[0387] The maximum number of transmissions of one or both of message 1 and message A may be set by a fifth upper layer parameter. One or both of message 1 and message A may change their transmission power for each transmission. For example, the power of one or both of message 1 and message A may be changed based on a sixth upper layer parameter. The sixth upper layer parameter may be a power ramping factor.

[0388] The random access preamble may be configured by a seventh higher layer parameter. For example, an index of a random access preamble used in a PRACH opportunity may be configured by the seventh higher layer parameter. The seventh higher layer parameter may indicate a value from 0 to 63. The seventh higher layer parameter may be ra-PreambleIndex.

[0389] The number of SS / PBCH blocks mapped to each PRACH opportunity may be defined by an eighth higher layer parameter. The number of CBRA random access preambles mapped to each SS / PBCH block may also be defined by an eighth higher 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 transmit Message A using random access preamble Group A. For example, terminal device 1 may transmit Message A using random access preamble Group B.

[0390] 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.

[0391] First through twelfth UE 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_RAMPIPING_STEP.

[0392] RA_TYPE may be set to 4-step RA. For example, if a random access procedure is initiated by a PDCCH order, and the random access preamble index (ra-PreambleIndex) is provided by the PDCCH, and the random access preamble index is not 0b000000, RA_TYPE may be set to 4-step RA. For example, if a random access procedure is initiated for an SI request, and the random access resource (RACH configuration) for the SI request is provided by RRC, RA_TYPE may be set to 4-step RA. If a random access procedure is initiated for beam failure recovery (or beam failure recovery for an SpCell), and the CFRA resource corresponding to the beam failure recovery request for the 4-step random access type is provided, RA_TYPE may be set to 4-step RA. When a random access procedure is initiated for reconfiguration with sync and a CFRA resource for the 4-step random access type is provided in the higher layer parameter rach-ConfigDedicated, RA_TYPE may be set to 4-stepRA. For example, when a random access procedure is initiated for acquiring a second TA and a random access resource (e.g., a CFRA resource) is provided for acquiring the second TA, RA_TYPE may be set to 4-stepRA. The random access resource may be one or both of a CFRA resource and a CBRA resource. Providing a random access resource may mean configuring a RACH. Acquiring a second TA may mean acquiring a second (or two) TAs in one serving cell. When RA_TYPE is set to 4-stepRA, a 4-step random access type random access may be performed. When RA_TYPE is set to 2-stepRA, a 2-step random access type random access may be performed.If early UL synchronization is configured, the index of the random access preamble may not be expected to be 0b000000.

[0393] If RA_TYPE is set to 4-StepRA, the MAC entity may perform any of the first to sixth operations.

[0394] The first operation may be performed when a random access procedure is initiated for beam failure recovery. The first operation may be performed when a beam failure recovery timer (beamFailureRecoveryTimer) is running or is not set. The first operation may be performed when contention-free random access resources (CFRA) for the beam failure recovery request are provided by RRC. The beam failure recovery request may be associated with either an SSB or a CSI-RS. The first operation may be performed when 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. In the first operation, the MAC entity may select a first SSB. The first SSB may be an SSB included in a first reference signal set. The first SSB may be an SSB with an RSRP exceeding a certain threshold. In a first operation, the MAC entity may select a first CSI-RS. The first CSI-RS may be a CSI-RS included in a first reference signal set. The first CSI-RS may be a CSI-RS with an RSRP exceeding a certain threshold. The first reference signal set may be configured by candidateBeamRSList. If the first SSB is selected, PREAMBLE_INDEX may be set to a first random access preamble index (ra-PreambleIndex). The first random access preamble index may be ra-PreambleIndex corresponding to the selected SSB from a set of random access preambles for beam failure recovery.

[0395] A second operation may be performed if a random access preamble index (ra-PreambleIndex) is provided by the PDCCH (PDCCH order). A second operation may be performed if the random access preamble index is not 0b000000. In the second operation, the MAC entity may set PREAMBLE_INDEX to the random access preamble index. In the second operation, one SSB may be indicated (signaled) by the PDCCH.

[0396] 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 second operation may be performed if the PDCCH provides a first value. The second operation may be performed if the first value is determined by the PDCCH. In the second operation, the MAC entity may set PREAMBLE_INDEX to a second random access preamble index. The second random access preamble index may be a random access preamble index for second TA acquisition. The second random access preamble index may be ra-PreambleIndex corresponding to an indicated SSB from a set of random access preambles for second TA acquisition. The first value may specify one RACH configuration. The first value may specify one higher layer parameter including the RACH configuration. The first value may be an additional PCI index, a TAG ID, and TRP information.

[0397] A third operation may be performed. If CFRA resources associated with 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 certain threshold. In the third operation, the MAC entity may select one SSB. The one SSB may have an RSRP above a certain threshold. In the third operation, PREAMBLE_INDEX may be set to ra-PreambleIndex corresponding to the selected SSB.

[0398] 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 have an RSRP above a certain threshold. The one SSB may have an RSRP above a certain threshold. In the fourth operation, the MAC entity may select any SSB. In the fourth operation, the MAC entity may select one random access preamble corresponding to the selected SSB from random access preambles determined according to the higher layer parameter ra-PreambleStartIndex. In the fourth operation, PREAMBLE_INDEX may be set to the selected random access preamble.

[0399] A fifth operation may be performed. The fifth operation may be performed for CBRA preamble selection. In the fifth operation, 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.

[0400] A sixth operation may be performed. If a random access procedure for acquiring the second TA is initiated, the sixth operation may be performed. If a random access resource for acquiring the second TA is provided by RRC, the sixth operation may be performed. In the sixth operation, the MAC entity may select one SSB. The one SSB may have an RSRP exceeding a certain threshold. In the sixth operation, an arbitrary 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 acquiring the second TA may be determined in one or both of the upper layer parameter twoTA-Config1-r18 and the upper layer parameter twoTA-Config2-r18.

[0401] The random access preamble may be associated with a reference signal (either SSB or CSI-RS). For example, the number of random access preambles per reference signal may be determined by a higher layer parameter.

[0402] When a random access procedure is initiated for an SI request and when the first higher layer parameter is configured, the MAC entity may determine a first PRACH occasion. The first PRACH occasion may be associated with a selected SSB. The first PRACH occasion 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 occasion may be the next valid PRACH occasion. The first higher layer parameter may be one or both of ra-AssociationPeriodIndex and si-RequestPeriod.

[0403] In any of the first to sixth operations when RA_TYPE is set to 4-Step RA, if an SSB is selected, 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).

[0404] In any of the first to sixth operations when RA_TYPE is set to 4-StepRA, if a CSI-RS is selected and there is no CFRA resource associated with the selected CSI-RS, the MAC entity may determine a third PRACH opportunity based on the SSB.

[0405] In any of the first to sixth operations when RA_TYPE is set to 4-StepRA, if a CSI-RS is selected, the MAC entity may determine a fourth PRACH opportunity corresponding to the selected CSI-RS.

[0406] When a random access (Random Access Procedure) is initiated in one serving cell, 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.

[0407] The MAC entity may randomly select one PRACH opportunity from the multiple PRACH opportunities.

[0408] The MAC entity may perform a random access preamble transmission procedure.

[0409] The MAC entity may determine the power for each random access type based on a counter. The MAC entity may calculate an RA-RNTI associated with a 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 a system frame, the index of the PRACH opportunity in the frequency domain, and the uplink carrier on which the random access preamble is transmitted.

[0410] 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 a 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 an SpCell. A notification of the reception 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.

[0411] 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 the random access response to have been successfully received.

[0412] The MAC entity may consider the random access response to be successfully received. Based at least on the considered successful reception of the random access response, the MAC entity may consider the random access to be successfully completed, indicate the receipt of an acknowledgement (ACK) to upper layers, and 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 the received UL grant to the physical layer.

[0413] If the random access response is deemed to be successfully received and if a random access preamble is transmitted in one serving cell, the MAC entity may process a TA command for one serving cell. Based at least on the deemed successful reception of the random access response and the transmission of a random access preamble in one serving cell, the MAC entity may apply a TA command for one serving cell. Based at least on the deemed successful reception of the random access response, 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 the transport block. For example, one or more MAC SDUs may be demultiplexed from the transport block.

[0414] A beam failure recovery (BFR) procedure may be configured by RRC for the MAC entity. 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.

[0415] The terminal device 1 may receive higher layer parameters. The terminal device 1 may initiate a random access procedure in response to receiving the higher layer parameter RRCReconfiguration. For example, when the higher layer parameter RRCReconfiguration is received in the higher layer parameter nr-SCG, and when the higher layer parameter nr-SCG includes the higher layer parameter reconfigurationWithSync, the terminal device 1 may initiate a second random access procedure in RRC. RRCReconfiguration may be received for NR SCG RRC Reconfiguration. The second random access procedure may be a random access procedure for reconfiguration with sync.

[0416] A second TA acquisition procedure may be configured by the RRC for the MAC entity. The configuration of the second TA acquisition procedure may include RACH configuration. The configuration of the second TA acquisition procedure may be one or both of TwoTA-Config1-r18 and TwoTA-Config2-r18. The MAC entity may trigger the second TA acquisition. For example, the MAC entity may trigger the second TA acquisition based on expiration of a timer associated with a subTAG. Up to two subTAGs may be provided in one serving cell. The second TA acquisition may be triggered to configure two TAs (TAGs) in one serving cell. A third random access procedure may be initiated based on the second TA acquisition being triggered. The third random access procedure may be a random access procedure for the second TA acquisition. If one or both of TwoTA-Config1-r18 and TwoTA-Config2-r18 are provided, the random access procedure for the second TA acquisition may be initiated in the MAC or the RRC. Configuring twoTAs may also be configuring the second TA acquisition procedure.

[0417] Before initiating random access (physical random access procedure), the physical layer may receive a set of SS / PBCH block indices from a higher layer and may provide a set of RSRP measurements to the higher layer. Before initiating random access, the physical layer may instruct the higher layer to perform Type 1 random access. Before initiating random access, the physical layer may instruct the higher 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 initiating random access, the physical layer may receive one or more parameters from the higher layer. The one or more parameters may include PRACH transmission parameter configuration. The PRACH transmission parameter configuration may be RACH configuration. The PRACH transmission parameter may be a PRACH preamble format, time resource, or 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 that determines a cyclic shift in a PRACH preamble sequence (a sequence of a random access preamble). 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.

[0418] The random access may include at least transmission of message 1 on the PRACH and message 2. The random access may include transmission of message 1 on the PRACH, message 2, transmission of a PUSCH scheduled by a random access response uplink 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). For example, message 2 may be a random access response accompanied by a PDCCH / PDSCH. The random access procedure may be referred to as random access.

[0419] The random access may include at least transmitting a message A and receiving a message B. The random access may also include transmitting the message A, receiving the message B, transmitting a PUSCH scheduled by a random access response grant, and a PDSCH for contention resolution. The message A may be a random access preamble and a PUSCH on a PRACH. The message B may be a random access response. For example, the message B may be a random access response accompanied by a PDCCH / PDSCH. The random access response grant may be a fallback random access response grant.

[0420] When random access is initiated by a PDCCH order, the PRACH transmission (random access preamble transmission) may be accompanied by the same subcarrier spacing as the PRACH transmission initiated by a higher layer. When 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 PRACH transmission. When TwoTA is 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 PRACH transmission. In the random access procedure for acquiring the second TA, one field of the PDCCH order may include an additional PCI index.

[0421] Random access may be triggered by a higher layer or a PDCCH order in response to a PRACH transmission request. The configuration by the higher layer 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 resource, and TAG ID / subTAG ID.

[0422] 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 enabled PRACH opportunity and per SS / PBCH block index may be configured by higher layer parameters. The PRACH opportunity may be enabled. For example, the PRACH opportunity may be enabled based at least on OFDM symbols configured for time division duplex.

[0423] The terminal device 1 may attempt to decode DCI format 1_0 with a CRC scrambled with the 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 the RA-RNTI within a certain window. The certain window may start based at least on the first OFDM symbol of the CORESET.

[0424] Based at least on the terminal device 1 detecting DCI format 1_0 with a CRC scrambled by the RA-RNTI and the terminal device 1 receiving the transport block, the terminal device 1 may pass the transport block to a higher layer. For example, the transport may be received on a PDSCH within a certain window. The higher layer may parse the transport block corresponding to a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layer identifies the RAPID in a random access response (a random access response message), the higher layer may indicate an uplink grant (a 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.

[0425] If the terminal device 1 does not detect DCI format 1_0 with a CRC scrambled with the RA-RNTI within the window or does not receive a transport block in the PDSCH within the window, the higher layer may instruct the physical layer to transmit a PRACH. Also, if the higher layer does not identify a RAPID associated with the PRACH transmission, the higher layer may instruct the physical layer to transmit a PRACH. For example, the terminal device 1 may be expected to transmit the PRACH within a predetermined time after the last OFDM symbol of the window. Also, the terminal device 1 may be expected to transmit the PRACH within a predetermined time after the last OFDM symbol of the PDSCH reception. Transmitting the PRACH may be transmitting a random access preamble.

[0426] The PDCCH order may trigger a contention-free random access procedure (CFRA). For example, the PDCCH order may trigger a CFRA in one SpCell. The PDCCH order may initiate a PRACH transmission. When the terminal device 1 attempts to detect DCI format 1_0 with a CRC scrambled by the RA-RNTI in response to a PRACH transmission initiated by the PDCCH order, the PDCCH including DCI format 1_0 and the PDCCH may be assumed to have the same QCL characteristics of the DMRS antenna port. The QCL characteristics may be large-scale characteristics of the channel.

[0427] The random access response grant (random access response) may be configured with one or more fields. For example, the one or more fields may include a frequency hopping flag field. For example, the one or more fields may include a frequency domain resource allocation field (or a PUSCH frequency resource allocation field). For example, the one or more fields may include a time domain resource allocation field (or a PUSCH time resource allocation field). For example, the one or more fields may include a Transmission Power Control (TPC) command field. For example, the one or more fields may include a CSI request field. For example, the one or more fields may include a field having TRP information.

[0428] When the CRC of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource allocation field is all "1", 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.

[0429] 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 an SS / PBCH index field. The SS / PBCH index field may indicate one SS / PBCH. One SS / PBCH may be used to determine a RACH opportunity for 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.

[0430] The DCI format in the PDCCH order may include an Additional PCI Index field. The Additional PCI Index field may indicate a first higher 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 the first higher layer parameter including a RACH configuration. The first higher layer parameter may be twoTA-Config1-r18. The first higher layer parameter may be twoTA-Config2-r18. The Additional PCI Index field may be referred to as a PCI indication field.

[0431] The DCI format in the PDCCH order may include a cell indication field. The size of the cell indication field may be Ceil(log2(C+1)) bits. The cell indication field may indicate one cell. One cell may correspond to PRACH transmission. For example, if a first higher layer parameter is configured, the cell indication field may indicate one cell for PRACH transmission. C may be the number of candidate cells configured by the first higher layer parameter. If the first higher layer parameter is not configured, the size of the cell indication field may be 0 bits. Index 0 of the cell indication field may be mapped to the serving cell. Other indices of the cell indication field may be mapped to configured candidate cells. The candidate ID may be determined by a second higher layer parameter. For example, the candidate cell associated with the smallest candidate ID may be mapped to index 1 of the cell indication field. Configuring the first higher layer parameter may indicate configuring early UL synchronization. The first higher layer parameter may be EarylyUlSyncConfig. The second higher layer parameter may be ltm-CandidateId. Early UL synchronization may be configured to set the cell indication field.

[0432] The DCI format in the PDCCH order may include a PCI indication field. The PCI indication field may indicate one PCI. One PCI may be associated with a PRACH transmission. For example, if TwoTA is configured, the size of the PCI indication field may be 1 bit. Configuring TwoTA may mean some or all of configuring a second TAG ID (e.g., tag-Id2) in one serving cell, configuring an additional PCI index (e.g., SSB-MTC-AdditionalPCI), and configuring multi-DCI mode.

[0433] The DCI format in the PDCCH order may include a retransmission field. The retransmission field may indicate a retransmission of the PRACH transmission. For example, if early UL synchronization is configured, the PDCCH order may include the retransmission field. If a retransmission of the PRACH transmission is indicated, the power of the PRACH transmission may be increased. Early UL synchronization may be configured to set the retransmission field.

[0434] The PCI (Physical Cell ID) may be referred to as a 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 a higher 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.

[0435] In the means 1, when the size of the cell indication field is 1 or more, the size of the PCI indication field may be 0. Also, when the size of the PCI indication field is 1 or more, the size of the cell indication field may be 0. For example, when the size of the cell indication field is 1 or more, the size of the PCI indication field may not be expected to be 1 or more. For example, when the size of the PCI indication field is 1 or more, the size of the cell indication field may not be expected to be 1 or more. When early UL synchronization is configured, TwoTA may not be expected to be configured. When TwoTA is configured, early UL synchronization may not be expected to be configured. For example, it may not be expected that a PDCCH order includes both a PCI indication field and a cell indication field.

[0436] DCI formats 1_0 / 1_1 / 1_2 may be used for scheduling PDSCH. A BWP (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, when the higher layer parameter SecondTPCFieldDCI is configured, the second TPC command (Second TPC command for scheduled PUCCH) field may be included in DCI format 1_1.

[0437] 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.

[0438] The antenna port(s) 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}.

[0439] When the upper layer parameter dmrs-Type is 1, it may mean that DMRS configuration type 1 is configured. When the upper layer parameter dmrs-Type is 2, it may mean that DMRS configuration type 2 is configured. When the upper layer parameter maxLength is 1, it may mean that the maximum number of forward DMRS symbols is 1 symbol. When the upper layer parameter maxLength is 2, it may mean that the maximum number of forward DMRS symbols is 2 symbols. For example, when the upper layer parameter maxLength is 1, it may mean that a single-symbol forward DMRS (forward DMRS symbol) is configured. For example, when the upper layer parameter maxLength is 2, it may mean that a single-symbol forward DMRS (forward DMRS symbol) or a double-symbol forward DMRS is configured.

[0440] 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. For example, DMRS port 0 may correspond to antenna port p0=1000. For example, DMRS port 1 may correspond to antenna port p1=1001. For example, DMRS ports {0,1} may correspond to antenna ports {p0=1000,p1=1001}. For example, DMRS port {2,3} may correspond to antenna ports {p2=1002,p3=1003}.

[0441] A TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when an upper layer parameter is configured, a TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when an upper layer parameter tci-PresentInDCI is configured, a 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 a TCI field in the DCI format.

[0442] The TCI indication field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when a higher layer parameter is 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.

[0443] DCI formats 0_0 / 0_1 / 0_2 may be used for scheduling PUSCH. A BWP (Bandwidth part indicator) field may be included in some 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, when the higher layer parameter SecondTPCFieldDCI is configured, the second TPC command (Second TPC command for scheduled PUSCH) field may be included in DCI format 1_1.

[0444] 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. When the SRS resource set indicator field indicates 0 (“00”), the SRS resource indicator field and the precoding information and number of layers fields may be associated with a first SRS resource set. When the SRS resource set indicator field indicates 1 (“01”), the SRS resource indicator field and the precoding information and number of layers fields may be associated with a second SRS resource set. When the SRS resource set indicator field indicates 2 (“10”), the SRS resource indicator field and the precoding information and number of layers fields may be associated with a first SRS resource set. If the SRS resource set indication field indicates 2 ("10"), the second SRS resource indication field and the second "precoding information and number of layers field" (second precoding information 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.

[0445] DCI format 1_0 may be used for scheduling the PDSCH. DCI format 1_0 may be mapped to the PDCCH. The PDCCH to which DCI format 1_0 is mapped may be referred to as a PDCCH order.

[0446] Configuring early UL synchronization may be configuring Layer-1 / 2 Triggered Mobility (LTM). Configuring early UL synchronization may be configuring LTM-Config. Multiple candidate cells may be indicated by the higher layer parameter LTM-Config. SS / PBCH blocks for each candidate cell may be indicated by the higher layer parameter LTM-Config. Multiple candidate cells and SS / PBCH blocks for each candidate cell may be indicated for obtaining synchronization (e.g., early UL synchronization) and L1-RSRP measurements. One MAC CE command may activate a TCI state. The TCI state may be related to the SS / PBCH block or a Tracking Reference Signal (TRS) of the candidate cell. The TCI state may be a unified TCI state. For example, the TCI state may be provided by a higher layer parameter. One MAC CE command may be referred to as a cell switch command. For example, one MAC CE command may include some or all of a TCI state ID, a TA command, a cell ID, and resources for CFRA. The TCI state activated by one MAC CE command may be referred to as an LTM-TCI state. One MAC CE command may be received at the serving cell.

[0447] The terminal device 1 may receive a cell switch command. The cell switch command may correspond to one candidate cell. The one candidate cell may correspond to a cell ID in the cell switch command. The terminal device 1 may transmit in one candidate cell. For example, after receiving the cell switch command, the terminal device 1 may estimate one TA from the first transmission in one candidate cell. Early UL synchronization may be configured for PRACH transmission parameters for each candidate cell. A PDCCH order may trigger PRACH transmission in one candidate cell. The PDCCH order may be received in the serving cell. The PDCCH order may include an indication of one candidate cell for PRACH transmission (e.g., a cell indication field).

[0448] The LTM-TCI state may not be applied to transmission of uplink and downlink channels in the serving cell. The LTM-TCI state may be used in a cell corresponding to the cell ID in one MAC CE command. For example, the LTM-TCI state may not be indicated by the SRS resource set indication field. For example, the LTM-TCI state may not be related to the applyIndicatedTCIState. The applyIndicatedTCIState may ignore the LTM-TCI state. The TCI indication field may not indicate that the LTM-TCI state is applied.

[0449] The LTM-TCI state may be used for power control of PRACH transmissions in the candidate cell. For example, a reference signal corresponding to the LTM-TCI state may be used for path loss calculation of PRACH transmissions in the candidate cell. For example, uplink power control parameters associated with the LTM-TCI state may be applied to uplink channel transmissions in the candidate cell.

[0450] The TCI field may indicate both a first Joint / DL / UL TCI state and a second Joint / DL / UL TCI state. For example, one code point in the TCI field may be mapped to both the first TCI state and the second TCI state. If the multi-DCI mode is configured, the TCI field associated with the first CORESET pool index may indicate a third Joint / DL / UL TCI state. If the multi-DCI mode is configured, the TCI field associated with the second CORESET pool index may indicate a fourth Joint / DL / UL TCI state. The LTM-TCI state may be one of the third Joint / DL / UL TCI state and the fourth Joint / DL / UL TCI state. The Joint / DL / UL TCI state that is the LTM-TCI state may be associated with one additional PCI index. If the multi-DCI mode is not configured, the LTM-TCI state may not be used in the serving cell.

[0451] 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, 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, the present invention may be used for determining a TAG ID / subTAG ID when two uplink timings are provided in one serving cell. Furthermore, when acquiring a TA in a random access procedure, communication efficiency is improved by switching the acquisition method depending on the role of the TA. The present invention may be used for switching this acquisition method.

[0452] 14 is a diagram illustrating an example of TCI status management according to one aspect of the present embodiment, in which a black circle may represent one TCI status.

[0453] One or more TCI states 1000 may be configured by higher layer parameters. For example, one or more UL TCI states (TCI-UL-State) may be configured by higher layer parameters for each uplink BWP (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. For example, one UL TCI state may be associated with one UL TCI state ID (TCI-UL-State-Id, UL-TCIState-Id). For example, one DL / Joint TCI state (TCI-state) may be associated with one TCI state ID (TCI-stateId). One or more TCI states configured by higher layer parameters may be configured TCI states 1000. Each TCI state 1000 may include one TAG ID or subTAG ID. For example, among the TCI states 1000, the TCI state that becomes the activated TCI state 1001 may include one TAG ID or subTAG ID. For example, among the TCI states 1000, the TCI state that becomes the activated TCI state 1002 may not include one TAG ID or subTAG ID.

[0454] 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 one MAC PDU. One MAC PDU may include an activation command or a MAC CE referred to as an activation command. For example, the activation command may be activation command D or activation command E. One or more TCI states and / or one or more "TCI state pairs" may be mapped to one or more code points. For example, one or more TCI states and / or 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. For example, each TCI state or each TCI state pair may be mapped to one code point by an activation command. The code point to which a TCI state or a pair of TCI states is mapped may be a code point in a TCI field. The code point to which a TCI state or a 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 a TCI state or a pair of TCI states is mapped may be a code point in a TCI field in DCI 1040. For example, a TCI state or a 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) may be the activated TCI state 1001. The TCI state mapped to a code point in the TCI field may be the activated TCI state 1001.

[0455] If the CORESET pool index (coresetPoolIndex) is not configured in one or more CORESETs (ControlResourceSets), activation command E may be used. If the CORESET pool index (coresetPoolIndex) is configured 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.

[0456] One or more TCI states 1002 may be part or all of one or more TCI states 1000. One or more TCI states 1002 may be activated by a MAC CE (e.g., a MAC CE command). The MAC CE may be a cell switch command. One TCI state or one “TCI state pair” may be included in the MAC CE. In the first embodiment, if multiple TCI states are mapped to at least one code point in the TCI field, a cell switch command may not be expected to be received. In the first embodiment, if an activation command for the TCI state 1001 is received, a cell switch command may not be received. Also, if a cell switch command is received, an activation command for the TCI state 1001 may not be received. The TCI state activated by the cell switch command may be the activated TCI state 1002. The activated TCI state 1002 may be associated with an SS / PBCH block or TRS corresponding to a candidate cell.

[0457] The activated TCI state 1002 may be an LTM-TCI state. In the first embodiment, if the TCI state 1001 is activated, the TCI state 1002 may not be expected to be activated. If the TCI state 1002 is activated, the TCI state 1001 may not be expected to be activated.

[0458] The one or more TCI states 1003 may be some or all of one or more TCI states 1001. The one or more TCI states 1003 may be indicated by a DCI 1040. The DCI 1040 may be DCI format 1_1 or DCI format 1_2. The DCI 1040 may include a TCI (Transmission Configuration Indication) field. The 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 the DCI 1040 may be the indicated TCI state 1003. The indicated TCI state 1003 may be some or all of the UL TCI state, DL TCI state, and Joint TCI state. For example, the indicated TCI state 1003 may be indicated by the value of the TCI field and a CORESET pool index associated with the PDCCH 1030. The UL TCI state may be the 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 DCI 1040 may not be able to indicate the TCI state 1002.

[0459] The number of indicated TCI states 1003 may be four. For example, the indicated TCI states 1003 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 first pair may be associated with a first TAG ID. The second pair may be associated with a second TAG ID. The first TAG ID and the second TAG ID may be configured for one serving cell.

[0460] The number of indicated TCI states 1003 may be three. For example, the indicated TCI states 1003 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 first pair may be associated with a first TAG ID, and the third DL / UL / Joint TCI state may be associated with a second TAG ID. The first pair may be associated with a second TAG ID, and the third DL / UL / Joint TCI state may be associated with the first TAG ID.

[0461] The number of indicated TCI states 1003 may be two. For example, the indicated TCI states 1003 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 first DL / UL / Joint may be associated with a first TAG ID, and the second DL / UL / Joint TCI state may be associated with a second TAG ID.

[0462] The number of indicated TCI states 1003 may be two. For example, the indicated TCI states 1003 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 first pair may be associated with a first TAG ID. The first pair may be associated with a second TAG ID.

[0463] The number of indicated TCI states 1003 may be 1. For example, the indicated TCI state 1003 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 first DL / UL / Joint may not be associated with a TAG ID. The first DL / UL / Joint TCI state may be associated with a first TAG ID. The first DL / UL / Joint TCI state may be associated with a second TAG ID.

[0464] The indicated TCI state 1003 is N from the last OFDM symbol of the PUCCH. symb For example, the indicated TCI state 1003 may be applied from the first slot after the last OFDM symbol of the PUCCH whose transmission is indicated by the DCI 1040. symb The TCI state 1003 may be applied from the first slot after the symbol. The indicated TCI state 1003 may be applied to multiple channels / signals. symb may be BeamAppTime. For example, if DCI 1040 is associated with CORESET pool index 1080, indicated TCI state 1003 may be first indicated TCI state 1010. For example, if DCI 1040 is associated with CORESET pool index 1081, indicated TCI state 1003 may be second indicated TCI state 1011.

[0465] One or more TCI states 1003 may be applied to an uplink channel (uplink physical channel) 1070. The “indicated TCI state 1003” applied to the uplink channel 1070 may be one or more UL TCI states and / or one or more Joint TCI states. The “indicated TCI state” 1003 applied to the uplink channel 1070 may be the “applied TCI state 1020.” The TCI state 1002 may not be applied to the uplink channel (uplink physical channel) 1070. For example, the uplink channel (uplink physical channel) 1070 may be associated with a serving cell.

[0466] The indicated TCI state 1003 may include at least a TCI state 1010 and a TCI state 1011. One or both of the TCI state 1010 and the TCI state 1011 may be applied to the uplink channel 1070. One or both of the TCI state 1010 and the TCI state 1011 applied to the uplink channel 1070 may be a TCI state 1020. The terminal device 1 may hold both the TCI state 1010 and the TCI state 1011. The terminal device 1 may hold only one TCI state (e.g., the TCI state 1002) in the candidate cell.

[0467] 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 start or trigger a random access procedure 1100. The PDCCH 1031 may trigger 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.

[0468] In FIG. 15, TwoTA may be configured. The PDCCH 1031 may indicate one RACH configuration. For example, when an inter-cell multi-TRP mode is configured, the PDCCH 1031 may indicate one RACH configuration. For example, the one RACH configuration may be indicated by a PCI indication field. Indicating one RACH configuration may mean that the PCI indication field indicates one cell ID. The PDCCH 1031 may include a PCI indication field. When the PCI indication field is a first value (e.g., 0), the first RACH configuration may be used. When the PCI indication field is a second value (e.g., 1), the second RACH configuration may be used. The first RACH configuration may be associated with a serving cell. For example, the first RACH configuration may be a common upper layer parameter. The second RACH configuration may be associated with one additional PCI index. A cell corresponding to one PCI index may be activated. It is not expected that multiple cells corresponding to multiple PCI indices will be activated. The inter-cell multi-TRP mode may be configured by configuring an additional PCI index. If the PCI indication field is a first value (e.g., 0), a random access procedure associated with a first cell ID may be initiated. If the PCI indication field is a second value (e.g., 1), a random access procedure associated with a second cell ID may be initiated. The second cell ID may be a non-serving cell. If the PCI indication field is a first value (e.g., 0), a random access procedure associated with a first TAG ID may be initiated. If the PCI indication field is a second value (e.g., 1), a random access procedure associated with a second TAG ID may be initiated. The first TAG ID and the second TAG ID may be configured in one serving cell. If the PCI indication field is a first value, one or both of a first random access preamble and a first RACH opportunity may be used. If the PCI indication field is a second value, one or both of a second random access preamble and a second RACH opportunity may be used.The first random access preamble and the first RACH opportunity may be associated with a serving cell. For example, the first random access preamble and the first RACH opportunity may be associated with an SS / PBCH block for the serving cell. The second random access preamble and the second RACH opportunity may be associated with a non-serving cell. For example, the second random access preamble and the second RACH opportunity may be associated with an SS / PBCH block for the non-serving cell.

[0469] In FIG. 15, early UL synchronization may be configured. The PDCCH 1031 may indicate one RACH configuration. The one RACH configuration may be indicated by a cell indication field. Indicating one RACH configuration may mean that the cell indication field indicates one cell ID. The PDCCH 1031 may include a cell indication field. If the cell indication field has a first value, the first RACH configuration may be used. If the cell indication field has a second value, the third RACH configuration may be used. The third RACH configuration may be associated with one cell ID. A cell corresponding to one cell ID may be a candidate cell. The number of candidate cells may be one or more. The PDCCH 1031 may include a cell indication field. If the cell indication field has a first value, the first RACH configuration may be used. If the cell indication field has a second value, the third RACH configuration may be used. If the cell indication field has a first value, a random access procedure associated with the first cell ID may be initiated. If the cell indication field has a second value, a random access procedure associated with a third cell ID may be initiated. The third cell ID may be the ID of a candidate cell. If the cell indication field has a first value, a random access procedure associated with a first TAG ID may be initiated. If the cell indication field has a second value, a random access procedure associated with a third TAG ID may be initiated. The first TAG ID may be configured for one serving cell. The third TAG ID may not be configured for one serving cell. For example, the third TAG ID may be configured for a candidate cell. If the cell indication field has a first value, one or both of the first random access preamble and the first RACH opportunity may be used. If the cell indication field has a second value, one or both of the third random access preamble and the third RACH opportunity may be used. The third random access preamble and the third RACH opportunity may be associated with the candidate cell. For example, the third random access preamble and the third RACH opportunity may be associated with an SS / PBCH block for the candidate cell.

[0470] In means 2, if TwoTA is set, early UL synchronization may be set. If the PCI indication field is a second value, the cell indication field may not be expected to be the second value. If the cell indication field is a second value, the PCI indication field may not be expected to be the second value. If the PCI indication field is a first value, the cell indication field may be the first value or the second value. If the cell indication field is the first value, the PCI indication field may be the first value or the second value. In means 2, if the retransmission field indicates a retransmission, the PCI indication field may not be expected to be the second value.

[0471] The terminal device 1 may transmit the PRACH 1050. The terminal device 1 may transmit the PRACH 1050 in the random access procedure 1100. The terminal device 1 may transmit the PRACH 1050 in the PRACH resource.

[0472] When TwoTA is configured, the PL-RS (Pathloss Reference Signal) for the PRACH 1050 may be an SSB indicated by the PDCCH 1031. When early UL synchronization is configured, the PL-RS for the PRACH 1050 may be a reference signal corresponding to a QCL assumption of the PDCCH order. When early UL synchronization is configured, the PL-RS for the PRACH 1050 may be a reference signal that is the PDCCH order and QCL. When TwoTA and early UL synchronization are configured, the PL-RS for the PRACH 1050 may be determined based on the PCI indication field and the cell indication field.

[0473] The terminal device 1 may receive the PDCCH 1032. The terminal device 1 may receive the PDCCH 1032 in which the DCI 1042 is arranged. The terminal device 1 may receive the PDCCH 1032 in response to the transmission of the PRACH 1050. The terminal device 1 may detect the DCI 1042. For example, in response to the transmission of the PRACH 1050, the terminal device 1 may attempt to detect DCI format 1_0 with a CRC scrambled by the RA-RNTI.

[0474] The CORESET corresponding to the PDCCH 1032 may be associated with a Type 1 PDCCH common search space set. If twoTA is configured, the PDCCH 1032 or a DMRS port of the PDCCH 1032 may be associated with QCL information in the CORESET associated with the Type 1 PDCCH common search space set. If twoTA is not configured, the PDCCH 1031 and the PDCCH 1032 may be associated with the same QCL assumption. If early UL synchronization is configured and the first higher layer parameter is configured, the PDCCH 1032 or a DMRS port of the PDCCH 1032 may be associated with QCL information in the CORESET associated with the Type 1 PDCCH common search space set. If early UL synchronization is configured and the first higher layer parameter is not configured, the PDCCH 1031 and the PDCCH 1032 may be associated with the same QCL assumption. If twoTA and early UL synchronization are configured, the QCL assumption for the PDCCH 1032 may be determined based on the PCI indication field and the cell indication field. The first higher layer parameter may be configured for a QCL assumption of the PDCCH that schedules the RAR.

[0475] applyIndicatedTCIState may be set for the CORESET corresponding to the PDCCH 1032. For example, if multi-DCI mode is not configured, applyIndicatedTCIState may be set for the CORESET corresponding to the PDCCH 1032. If applyIndicatedTCIState indicates "first", the first indicated TCI state 1010 may be applied to the PDCCH 1032. If applyIndicatedTCIState indicates "second", the second indicated TCI state 1011 may be applied to the PDCCH 1032. It may not be expected that applyIndicatedTCIState will indicate "both".

[0476] The TCI state to be applied to the PDCCH 1032 may be determined based on a 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 a CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to CORESET pool index 1080, a first indicated TCI state 1010 may be applied to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to CORESET pool index 1081, a second indicated TCI state 1011 may be applied to the PDCCH 1032.

[0477] The terminal device 1 may receive the PDSCH 1060. The DCI 1042 may schedule the PDSCH 1060 or the reception of the PDSCH 1060. For example, 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 an 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, the terminal device 1 may receive the RAR 1110 in the PDSCH 1060.

[0478] When TwoTA is configured, the PDSCH 1060 may include a transport block 1090. When TwoTA is configured, the terminal device 1 may receive the transport block 1090 in the PDSCH 1060. When early UL synchronization is configured, the terminal device 1 may receive the transport block 1090 in the PDSCH 1060. When early UL synchronization is configured and the first upper layer parameter is configured, the terminal device 1 may receive the transport block 1090 in the PDSCH 1060. When early UL synchronization is configured and the first upper layer parameter is not configured, the terminal device 1 may receive the transport block 1091 in the PDSCH 1060. The first upper layer parameter may be a parameter indicating reception of an RAR. When the first upper layer parameter is not configured, the DCI 1041 may include a retransmission field.

[0479] The terminal device 1 may receive a TA command 1130. For example, 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. For example, if TwoTA is configured, the TA command 1130 may be associated with one TAG ID or one subTAG ID. For example, if TwoTA is configured, one TAG ID or one subTAG ID may be included in the RAR 1110. If early UL synchronization is configured, one TAG ID and one subTAG ID may not be included in the RAR 1110. If TwoTA is configured and inter-cell Multi-TRP is not configured, one TAG ID or one subTAG ID may be included in the RAR 1110. If early UL synchronization is configured, the TA command 1130 may be associated with one cell ID. The one cell ID may be indicated by a cell indication field. When TwoTA and early UL synchronization are configured, whether one TAG ID is included in the RAR 1110 may be determined based on the cell indication field and the PCI indication field.

[0480] The terminal device 1 may receive a TA command 1131. For example, the TA command 1131 may be included in a MAC CE command 1140. The TA command 1131 may not be associated with one TAG ID or one subTAG ID. The transport block 1091 may include the MAC CE command 1140. The terminal device 1 may measure the TA corresponding to the TA command 1131.

[0481] applyIndicatedTCIState may be set for the PDSCH 1060. For example, if multi-DCI mode is not configured, 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 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".

[0482] The TCI state to be applied to the PDSCH 1060 may be determined based on a 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 PDSCH 1060 may be determined based on a CORESET pool index of the CORESET corresponding to the PDCCH 1032. For example, when the CORESET of the PDCCH 1032 corresponds to CORESET pool index 1080, a first indicated TCI state 1010 may be applied to the PDSCH 1060. For example, when the CORESET of the PDCCH 1032 corresponds to CORESET pool index 1081, a second indicated TCI state 1011 may be applied to the PDSCH 1060.

[0483] The terminal device 1 may transmit a PUSCH 1071. The PUSCH 1071 or transmission of the PUSCH 1071 may be scheduled by an RAR UL grant 1110. For example, the RAR UL grant 1110 may instruct transmission of the PUSCH 1071. The PUSCH 1071 may be an Msg3 PUSCH (message 3 PUSCH). The uplink channel 1070 may be the PUSCH 1071. The RAR UL grant 1110 does not need to be included in the transport block 1091.

[0484] 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 a TCI state 1010 and a TCI state 1011.

[0485] When two TAs are configured, two uplink timings may be determined in one serving cell. The uplink timings may be referred to as timing adjustments. Corresponding to one uplink timing may correspond to one TA and / or one TAG.

[0486] When twoTA is configured, 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.

[0487] The terminal device 1 may adjust uplink timing for the PUSCH 1071. For example, in response to receiving a TA command 1130 for a 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. For example, the first TAG and the second TAG may be provided in one serving cell.

[0488] The terminal device 1 may receive a PDCCH order. For example, the terminal device 1 may receive a PDCCH to which DCI format 1_0 is mapped. A random access procedure may be initiated (triggered) by the PDCCH order. The terminal device 1 may transmit a PRACH in the random access procedure.

[0489] When TwoTA is configured, the PDCCH order may include a PCI indication field. When TwoTA is configured, DCI format 1_0 may include a PCI indication field. When early UL synchronization is configured, the PDCCH order may include a cell indication field. When early UL synchronization is configured, DCI format 1_0 may include a cell indication field. When early UL synchronization is configured, the PDCCH order may include a retransmission field. When early UL synchronization is configured, DCI format 1_0 may include a retransmission field.

[0490] In the first means, if TwoTA is configured, it may not be expected that early UL synchronization is configured. Also, if early UL synchronization is configured, it may not be expected that TwoTA is configured. That is, it may not be expected that TwoTA and early UL synchronization are configured simultaneously. If TwoTA is configured and the PCI indication field indicates a first value, a first RACH configuration may be applied to the random access procedure. If TwoTA is configured and the PCI indication field indicates a second value, a second RACH configuration may be applied to the random access procedure. The second RACH configuration may correspond to one additional PCI index. The one additional PCI index may be indicated by the PCI indication field. If early UL synchronization is configured, it may not be expected that TwoTA is configured. If early UL synchronization is configured and the cell indication field indicates a third value, a first RACH configuration may be applied to the random access procedure. If early UL synchronization is configured and the cell indication field indicates a fourth value, a third RACH configuration may be applied to the random access procedure. The third RACH configuration may correspond to one candidate cell. The one candidate cell may be indicated by a cell indication field. In the first means, if the size of the PCI indication field is one bit or more, the size of the cell indication field may not be expected to be one bit or more. If the size of the PCI indication field is one bit or more, the size of the retransmission field may not be expected to be one bit or more.

[0491] In the means 2, TwoTA and early UL synchronization may be configured. If the PCI indication field indicates a first value, a first RACH configuration may be applied to the random access procedure. If the PCI indication field indicates a second value, a second RACH configuration may be applied to the random access procedure. If the cell indication field indicates a third value, a first RACH configuration may be applied to the random access procedure. If the cell indication field indicates a fourth value, a third RACH configuration may be applied to the random access procedure. If the PCI indication field indicates a first value, the cell indication field may indicate a third value or a fourth value. If the PCI indication field indicates a first value and the cell indication field indicates a fourth value, a third RACH configuration may be applied to the random access procedure. If the PCI indication field indicates a first value and the cell indication field indicates a third value, the terminal device 1 may receive an RAR. If the PCI indication field indicates a first value and the cell indication field indicates a fourth value, whether the terminal device 1 receives an RAR may be determined by an upper layer parameter. If the PCI indication field indicates a second value, it may not be expected that the cell indication field indicates a fourth value. If the PCI indication field indicates a second value, the retransmission field may not be expected to indicate a retransmission. If the PCI indication field indicates a second value, the cell indication field may be ignored. If the PCI indication field indicates a second value, the retransmission field may be ignored. If the cell indication field indicates a third value, the PCI indication field may indicate the first value or the second value. If the cell indication field indicates a third value and the PCI indication field indicates a second value, a second RACH configuration may be applied to the random access procedure. If the cell indication field indicates a third value and the PCI indication field indicates a second value, the terminal device 1 may receive an RAR. If the cell indication field indicates a fourth value, the PCI indication field may not be expected to indicate the second value. If the cell indication field indicates a fourth value, the PCI indication field may be ignored.

[0492] In the second means, TwoTA and early UL synchronization may be configured. If the PCI indication field indicates a first value and the cell indication field indicates a third value, a first RACH configuration may be applied to the random access procedure. The first RACH configuration may be configured for the serving cell. For example, the first RACH configuration may be configured by a common upper layer parameter. If the PCI indication field indicates a second value, the cell indication field may be ignored and a second RACH configuration may be applied to the random access procedure. If the cell indication field indicates a fourth value, the PCI indication field may be ignored and a third RACH configuration may be applied to the random access procedure. It may not be expected that the PCI indication field indicates the second value and the cell indication field indicates the fourth value.

[0493] Various aspects of the device according to one aspect of this embodiment will be described below.

[0494] The programs operating in the base station device 3 and terminal device 1 according to 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 embodiments according to the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and 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 needed.

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

[0496] The term "computer system" used here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as an OS and peripheral devices. Also, the term "computer-readable recording medium" 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 the computer system.

[0497] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores 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 a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

[0498] Furthermore, 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 according 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. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as a collection.

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

[0500] Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all of them may be integrated into a chip. Furthermore, the integrated circuit method is not limited to LSI, and may be realized using a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.

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

[0502] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included.

[0503] The present invention can be used in, for example, a communication system, a communication device (for example, a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (for example, a communication chip), or a program.

[0504] 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 Medium 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 Point 3001, 3002 Resource grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common resource block set 1000 TCI state to be configured 1001, 1002 TCI state to be activated 1003, 1010, 1011 Indicated TCI state 1020 Applied TCI state 1030, 1031, 1032 PDCCH 1040, 1041, 1042 DCI 1050 PRACH 1060 PDSCH 1070 Uplink channel 1071 PUSCH 1080, 1081 CORESET pool index 1090, 1091 Transport block 1100 Random access procedure 1110 Random access response (RAR) 1120 Random access response grant (RAR UL grant) 1130, 1131 TA command

Claims

1. A terminal device comprising: a receiving unit that receives a PDCCH order that triggers a random access procedure; and a transmitting unit that transmits one of a first random access preamble, a second random access preamble, or a third random access preamble in the random access procedure, wherein when TwoTA is set, the PDCCH order includes a PCI indication field; when early UL synchronization is set, the PDCCH order includes a cell indication field; when the PCI indication field indicates a first value, the first random access preamble is used; when the PCI indication field indicates a second value, the second random access preamble is used; when the cell indication field indicates the first value, the first random access preamble is used; when the cell indication field indicates the second value, the third random access preamble is used; and when the size of the PCI indication field is 1 bit or more, the size of the cell indication field is not expected to be 1 bit or more.

2. A base station device comprising: a transmitter unit that transmits a PDCCH order that triggers a random access procedure; and a receiver unit that receives in the random access procedure any one of a first random access preamble, a second random access preamble, or a third random access preamble, wherein when TwoTA is set, the PDCCH order includes a PCI indication field; when early UL synchronization is set, the PDCCH order includes a cell indication field; when the PCI indication field indicates a first value, the first random access preamble is used; when the PCI indication field indicates a second value, the second random access preamble is used; when the cell indication field indicates the first value, the first random access preamble is used; when the cell indication field indicates the second value, the third random access preamble is used; and when the size of the PCI indication field is 1 bit or more, the size of the cell indication field is not expected to be 1 bit or more.

Images