Terminal device, base station device, and communication method
Patent Information
- Application Number
- JP2022203559
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2022-12-20
- Publication Date
- 2025-11-18
AI Technical Summary
Existing radio access technologies in LTE and NR systems face challenges in efficiently managing beam information and timing relationships for PDCCH and PDSCH communications, which affect communication efficiency and reliability.
The solution involves a terminal device and base station device that manage beam information and timing relationships by selecting appropriate beam information based on the time difference between PDCCH and PDSCH, using OFDM symbols and beam information to optimize communication efficiency.
This approach enhances communication efficiency and reliability by optimizing beam management and timing relationships, improving overall performance in wireless communication systems.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a terminal device and a base station device. [Background technology]
[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: 3 rd The LTE standard is being considered in the LTE Generation Partnership Project (registered trademark). In LTE, a base station device is also called eNodeB (evolved NodeB), and a terminal device is also called UE (User Equipment). LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cell shapes. A single base station device may manage multiple serving cells.
[0003] 3GPP is currently studying the next-generation standard (NR: New Radio) to propose it 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 meet the 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] In 3GPP, the extension of services supported by NR is being studied (Non-Patent Document 2 and Non-Patent Document 3). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. [Non-Patent Document 2] “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 [Non-Patent Document 3] “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #94-e, 6th ― 17th December, 2021 Summary of the Invention [Problem to be solved by the invention]
[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. [Means for solving the problem]
[0007] (1) A first aspect of the present invention is a terminal device comprising: a receiving unit that receives a first PDCCH in which a first DCI is arranged; and a first PDSCH scheduled by the first DCI; and a transmitting unit that transmits a PUCCH in which uplink control information for the first PDSCH is arranged, wherein one or more first beam information are indicated by the first DCI, one or two second beam information are selected by the first DCI from the one or more first beam information, one or two third beam information are different from a part or all of the one or two second beam information, a first time is a time between the first PDCCH and the first PDSCH, and the second time is set as a number of OFDM symbols by a first upper layer parameter, and when the first time is the same as or longer than the second time, one or two of the second beam information are applied to the first PDSCH, and when the first time is shorter than the second time, one or two of the third beam information are applied to the first PDSCH.
[0008] (2) Also, a second aspect of the present invention is a base station device comprising: a transmitter that transmits a first PDCCH in which a first DCI is arranged and a first PDSCH scheduled by the first DCI; and a receiver that receives a PUCCH in which uplink control information for the first PDSCH is arranged, wherein one or more first beam information are indicated by the first DCI, one or two second beam information are selected by the first DCI from the one or more first beam information, one or two third beam information are different from a part or all of the one or two second beam information, a first time is a time between the first PDCCH and the first PDSCH, and the second time is set as a number of OFDM symbols by a first upper layer parameter, and when the first time is the same as the second time or longer than the second time, one or two of the second beam information are applied to the first PDSCH, and when the first time is shorter than the second time, one or two of the third beam information are applied to the first PDSCH. Effect of the Invention
[0009] According to the present invention, the terminal device can perform communication efficiently, and the base station device can perform communication efficiently. [Brief description of the drawings]
[0010] [Figure 1] 1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. [Diagram 2] 1 is an example showing a relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and a cyclic prefix (CP) setting according to an aspect of the present embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. [Figure 4] FIG. 3 is a diagram illustrating an example of the configuration of a resource grid 3001 according to an aspect of the present embodiment. [Diagram 5] 2 is a schematic block diagram illustrating a configuration example of a base station device 3 according to an aspect of the present embodiment. FIG. [Figure 6] 1 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. [Figure 8] A diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. [Figure 9] FIG. 13 is a diagram showing an example of an activation command A according to an aspect of the present embodiment. [Figure 10] FIG. 13 is a diagram showing an example of an activation command B according to an aspect of the present embodiment. [Figure 11] FIG. 13 is a diagram showing an example of an activation command C according to an aspect of the present embodiment. [Figure 12] FIG. 13 is a diagram showing an example of an activation command D according to an embodiment of the present invention. [Figure 13]FIG. 13 is a diagram showing an example of an activation command E according to an aspect of the present embodiment. [Figure 14] A diagram showing an example of TCI state management according to one embodiment of the present invention. [Figure 15] FIG. 13 is a diagram illustrating an example of timeline management of TCI states according to one embodiment of the present invention. [Figure 16] A figure showing a second example of timeline management of TCI states in one embodiment of this invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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. Here, e is Napier's constant. H^I indicates 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 OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of OFDM in the time domain. The OFDM symbol includes at least one or a plurality of subcarriers. The OFDM symbol is converted into a time-continuous signal in baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) is used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be provided by applying transform precoding to CP-OFDM.
[0014] The OFDM symbol may be a name including a CP added to the OFDM symbol, that is, a certain OFDM symbol may be configured to include the certain OFDM symbol and a CP added to the certain OFDM symbol.
[0015] Fig. 1 is a conceptual diagram of a wireless communication system according to an 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, the terminal devices 1A to 1C are also 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 transmission devices (or transmission points, transmission / reception devices, transmission / reception points). When the base station device 3 is configured with multiple transmission devices, each of the multiple transmission devices may be located at a different position.
[0017] The base station device 3 may provide one or more serving cells. The serving cell may be defined as a set of resources used for wireless communication. The serving cell may also be called a cell.
[0018] A serving cell may be configured to include one downlink component carrier (downlink carrier) and / or one uplink component carrier (uplink carrier). A serving cell may be configured to include two or more downlink component carriers and / or 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. Also, 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 an 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 referred to as the reference point of the resource grid.
[0021] The resource grid is subframe,μ symbIt 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 CarrierBandwidth parameter). start,μ grid,x is a bandwidth configuration indicated by a parameter provided by the RRC layer (eg, parameter OffsetToCarrier). The offset configuration and the bandwidth 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 μ 15 kHz, where the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.
[0025] FIG. 2 shows a subcarrier interval setting μ and the number of OFDM symbols per slot N according to one embodiment of the present invention. slot symb 2A is an example showing the relationship between the subcarrier interval setting μ and the CP setting of normal cyclic prefix (CP). slot symb =14, N frame,μ slot =40, N subframe,μ slot In FIG. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is the 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 = 480kHz. f = 4096. The constant κ is κ = Δf max N f / (Δf ref N f,ref ) = 64. Δf ref is 15kHz. 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 frames (system frames, frames) may be organized into T f =(Δf max N f / 100)·T s = 10 ms. A radio frame is made up 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 It is.
[0028] An OFDM symbol is a unit of time domain for one communication method. For example, an OFDM symbol may be a unit of time domain for CP-OFDM. Also, an OFDM symbol may be a unit of time domain for DFT-s-OFDM.
[0029] A slot may consist of multiple OFDM symbols. For example, N consecutive slot symb One slot may be composed of N OFDM symbols. For example, in the normal CP setting, 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 a subframe may be given. For example, slot index n μ s ranges from 0 to N in the subframe. subframe,μ slot For the subcarrier spacing setting μ, the number and index of slots included in the radio frame may be given. Also, the slot index n μ s,f ranges from 0 to N in the radio frame. frame,μ slot Integer values in the range -1 through increasing order may be given.
[0031] FIG. 3 is a diagram showing an example of a method for configuring a resource grid according to one aspect of the present embodiment. The horizontal axis in FIG. 3 indicates the frequency domain. FIG. 3 shows a configuration example of a resource grid with a subcarrier spacing μ1 in a component carrier 300, and a configuration example of a resource grid with a subcarrier spacing μ2 in the certain component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier. In FIG. 3, it is assumed that μ1=μ2-1, but various aspects of the present embodiment are not limited to the condition of μ1=μ2-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 common resource blocks for a subcarrier spacing setting μ1.
[0034] In the common resource block set 3100, the common resource block including the point 3000 (a black block in the common resource block set 3100 in FIG. 3 ) is also referred to as a 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 an offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks for a subcarrier spacing setting μ1. The resource grid 3001 is an N size,μ grid1,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,i1 )
[0037] Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting μ2.
[0038] In the common resource block set 3200, the common resource block including the point 3000 (a 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 an offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing μ. The resource grid 3002 is N size,μ grid2,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,i2 )
[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,μ grid1,x N RB sc It 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] A resource block (RB) is N RB sc A resource block includes 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 the frequency domain in ascending order starting from 0 in a given common resource block set. 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 A subcarrier with a center frequency of 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 configuration μ are indexed in the frequency domain starting from 0 in ascending order in a given BWP. μ PRB is n μ CRB =nμ PRB +N start,μ BWP,i Here, 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 the downlink carrier is also called downlink BWP. The BWP configured for the uplink component carrier is also called uplink BWP.
[0047] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel, and the symbol may correspond to an OFDM symbol, and the symbol may correspond to a resource block unit, and the symbol may correspond to a resource element.
[0048] When the large scale properties of a channel through which a symbol is transmitted at one antenna port can be estimated from the channel through which a symbol is 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 antenna port and the second antenna port being QCL with respect to beam parameters may mean that a receiving beam assumed by the receiving side for the first antenna port is the same (or corresponds) as a receiving beam assumed by the receiving side for the second antenna port. The first antenna port and the second antenna port being QCLs in terms of beam parameters may mean that a transmission beam assumed by the receiving side for the first antenna port and a 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 typeA, typeB, typeC, and typeD.
[0050] The two antenna ports may be type A QCLs, which may indicate that a first large-scale characteristic of a channel in which a symbol is transmitted at one antenna port can be estimated from a channel in which a symbol is transmitted at the other antenna port. The two antenna ports may be type B QCLs, which may indicate that a second large-scale characteristic of a channel in which a symbol is transmitted at one antenna port can be estimated from a channel in which a symbol is transmitted at the other antenna port. The two antenna ports may be type C QCLs, which may indicate that a third large-scale characteristic of a channel in which a symbol is transmitted at one antenna port can be estimated from a channel in which a symbol is transmitted at the other antenna port. The two antenna ports may be type D QCLs, which may indicate that a fourth large-scale characteristic of a channel in which a symbol is transmitted at one antenna port can be estimated from a channel in which a symbol is transmitted at the other antenna port. The first large-scale characteristic may include all of Doppler shift, Doppler spread, average delay, and delay spread. The second large-scale characteristic may include all of Doppler shift and Doppler spread. The third large-scale characteristic may include all of the Doppler shift and the average delay. The fourth large-scale characteristic may include spatial reception parameters (spatial direction information, beam information). The antenna port for the DMRS may be a DMRS port. The antenna port for the PTRS may be a PTRS port. The antenna port associated with the PTRS may be a PTRS port. The antenna port for the SRS may be an SRS port. The antenna port for the DMRS may be a DMRS port. The antenna port associated with the DMRS may be a DMRS port.
[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] Fig. 5 is a schematic block diagram showing a configuration example 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 transmission / reception unit (physical layer processing unit) 30 and / or a part or all of a higher layer processing unit 34. The radio transmission / reception unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and a 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 a 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 a part or all of a wireless receiver 30b. Here, the device configurations of the baseband unit included in the wireless transmitter 30a and the baseband unit included in the wireless receiver 30b may be the same or different. Furthermore, the device configurations of the RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may be the same or different. Furthermore, the device configurations of the antenna unit included in the wireless transmitter 30a and the antenna unit included in the wireless receiver 30b may be the same or different.
[0054] For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDSCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDCCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PBCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a synchronization signal. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDSCH DMRS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDCCH DMRS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a CSI-RS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a DL PTRS.
[0055] For example, the wireless receiving unit 30b may receive a PRACH. For example, the wireless receiving unit 30b may receive and demodulate a PUCCH. The wireless receiving unit 30b may receive and demodulate a PUSCH. For example, the wireless receiving unit 30b may receive a PUCCH DMRS. For example, the wireless receiving unit 30b may receive a PUSCH DMRS. For example, the wireless receiving unit 30b may receive a UL PTRS. For example, the wireless 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 of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and an RRC layer.
[0057] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer.
[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 wireless transceiver unit 30 (or the wireless receiver unit 30b) performs processes such as demodulation and decoding. The wireless transceiver unit 30 (or the wireless receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The wireless transceiver unit 30 (or the wireless receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.
[0061] The RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation (down-converts) 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 CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed, and extracts a signal in the frequency domain.
[0063] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal 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, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. The RF unit 32 may also have a function of controlling transmission power. The RF unit 32 is also referred to as a transmission power control unit.
[0065] For the terminal device 1, one or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured.
[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 a SCell (Secondary Cell).
[0067] The PCell is a serving cell included in a Master Cell Group (MCG). The PCell is a cell in which an initial connection establishment procedure or a connection re-establishment procedure is performed by the terminal device 1 (a cell in which the procedure has been performed).
[0068] The PSCell is a serving cell included in a secondary cell group (SCG). The PSCell is a serving cell to which the terminal device 1 performs random access.
[0069] The SCell may be included in either the MCG or the SCG.
[0070] The term "serving cell group" (cell group) refers to at least the MCG and the SCG. The serving cell group may include one or more serving cells (or component carriers). The one or more serving cells (or component carriers) included in the serving cell group may be operated by carrier aggregation.
[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 the 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 the 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 may not be received in a downlink BWP (inactive downlink BWP) other than the active downlink BWP. The terminal device 1 may not attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP. The PUCCH and PUSCH may not be transmitted in an uplink BWP (inactive uplink BWP) that is not an active uplink BWP. The terminal device 1 may not transmit the PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are collectively referred to as the inactive BWP.
[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 the downlink control information. The downlink BWP switch may be controlled based on higher layer parameters.
[0076] The uplink BWP switching is used to deactivate one active uplink BWP and activate any inactive uplink BWP 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 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 certain 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. For a serving cell, one uplink BWP may be active at a given time.
[0079] Fig. 6 is a schematic block diagram showing a configuration example 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 a part or all of a wireless receiver 10b. Here, the device configurations of the baseband unit 13 included in the wireless transmitter 10a and the baseband unit 13 included in the wireless receiver 10b may be the same or different. The device configurations of the RF unit 12 included in the wireless transmitter 10a and the RF unit 12 included in the wireless receiver 10b may be the same or different. The device configurations of the antenna unit 11 included in the wireless transmitter 10a and the antenna unit 11 included in the wireless receiver 10b may be the same or different.
[0081] For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PRACH. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUCCH. The radio transmission unit 10a may generate and transmit a baseband signal of a PUSCH. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUCCH DMRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUSCH DMRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a UL PTRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of 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 of 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 processing of the MAC layer.
[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 place the physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.
[0087] The wireless transceiver unit 10 (or the wireless receiver unit 10b) performs processes such as demodulation and decoding. The wireless transceiver unit 10 (or the wireless receiver unit 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The wireless transceiver unit 10 (or the wireless receiver unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver unit 10 (wireless receiver unit 10b) may perform a channel access procedure prior to transmitting the physical signal.
[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 CP (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.
[0090] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.
[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, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 may also have a function of controlling 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 be called a reference signal.
[0094] The uplink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by a terminal device 1. The uplink physical channel may be received by a base station device 3. 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), a 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 the decoding of the transport block has been successfully completed. The NACK may indicate that the decoding of the transport block has not been successfully completed. The HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.
[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 from an UpLink-Shared CHannel (UL-SCH) of the transport layer.
[0100] The HARQ-ACK for the transport block may be referred to as the HARQ-ACK for the PDSCH. In this case, the "HARQ-ACK for the PDSCH" refers to the HARQ-ACK for the transport block included in the PDSCH.
[0101] The HARQ-ACK may indicate an ACK or NACK corresponding to one Code Block Group (CBG) 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. The scheduling request bit indicating a positive SR is also referred to as "a positive SR is transmitted". The positive SR may indicate that UL-SCH resources for an initial transmission are requested by the terminal device 1. The positive SR may indicate that a scheduling request is triggered by a higher layer. The positive SR may be transmitted when a scheduling request is indicated by a higher layer. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted". The negative SR may indicate that UL-SCH resources for an initial transmission are not requested by the terminal device 1. The negative SR may indicate that a scheduling request is not triggered by a higher layer. The 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 index related to the quality of a propagation path (e.g., propagation strength) or the quality of a physical channel, and the PMI is an index related to a precoder. The RI is an index related to a transmission rank (or the number of transmission layers).
[0104] The channel state information is an indicator regarding the reception state of at least a physical signal (e.g., CSI-RS) used for channel measurement. The value of the channel state information may be determined by the terminal device 1 based on the reception state assumed by at least a physical signal used for channel measurement. The channel measurement may include an 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 to 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 arranged in the PUSCH. The transport block delivered by the UL-SCH may be arranged in the PUSCH. The uplink control information may be arranged in the PUSCH. The terminal device 1 may transmit a PUSCH in which a transport block and one or both of the uplink control information are arranged. The base station device 3 may receive a PUSCH in which a transport block and one or both of the uplink control information are arranged.
[0107] The PRACH may be transmitted to convey a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The sequence x of the PRACH u,v (n) is x u,v (n)=x u (mod(n+C v ,L RA ) where x u is a ZC (Zadoff Chu) sequence. Also, x u x u =exp(-jπui(i+1) / L RA ), where j is the imaginary unit, and π is the ratio of the circumference of a circle to its circumference. 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 where u is an integer in the range of -1 to u, 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 the cyclic shifts of the PRACH sequence C v , and a sequence index u for the PRACH sequence. An index may be provided for 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 may not be used to transmit information generated in a higher layer. In addition, the uplink physical signal may be used to transmit information generated in a physical layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. 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 of a DMRS for a PUSCH (a DMRS related to a PUSCH, a DMRS included in a PUSCH, a DMRS corresponding to a PUSCH) may be given based on a set of antenna ports for the PUSCH. For example, the set of antenna ports of a DMRS 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 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 the PUCCH and the transmission of the 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 the PUCCH may be transmitting the PUCCH and the 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 convey information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. 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 arranged in a Broadcast Control CHannel (BCCH), which is a logical channel of the MAC layer. The BCCH is arranged in a BCH, which is a channel of the transport layer. The BCH may be arranged (mapped) in the PBCH. The terminal device 1 may receive the PBCH in which the MIB and one or both of the physical layer control information are arranged. The base station device 3 may transmit the PBCH in which the MIB and one or both of the physical layer control information are arranged.
[0119] For example, the physical layer control information may be configured with 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D. 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 at least to identify 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, the half radio frame may be configured to include five subframes. Alternatively, the half radio frame may be configured to include the first five subframes of the ten subframes included in the radio frame. Alternatively, the half radio frame may be configured to include the last five subframes of the ten subframes included in the radio frame.
[0122] The SS / PBCH block index bits are used to indicate an SS / PBCH block index. The SS / PBCH block index bits include 3 bits. The SS / PBCH block index bits may be composed of 3 bits of a 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used at least to identify SS / PBCH blocks from index 0 to index 63.
[0123] The subcarrier offset bit is 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 be interpreted as a set of downlink control information set to a certain format of the downlink control information.
[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 a PUSCH arranged in 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 specification field may indicate whether the DCI format including the DCI format specification field is an uplink DCI format or a downlink DCI format. That is, the DCI format specification field may be included in each of the uplink DCI format and the downlink DCI format. Here, the DCI format specification field included in the 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 at least to indicate 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 arranged in the PUSCH. The size of the transport block (TBS: Transport Block Size) arranged in 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, a serving cell to which an uplink component carrier in which a PUSCH scheduled by DCI format 0_0 is arranged may be the same as a serving cell of an uplink component carrier in which a PDCCH including the DCI format 0_0 is arranged. Based on detecting DCI format 0_0 in a downlink component carrier of a serving cell, the terminal device 1 may recognize that a PUSCH scheduled by the DCI format 0_0 is arranged in an uplink component carrier of the serving cell.
[0135] The DCI format 0_0 may not include a BWP field (BWP indication field). Here, the DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing an 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 0_0 used for scheduling the PUSCH.
[0136] DCI format 0_1 is used at least for scheduling a PUSCH allocated to a certain cell. DCI format 0_1 includes at least a part or all of fields 2A to 2H. 2A) DCI format specific fields 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 some or all of the modulation scheme and / or the target coding rate for the PUSCH.
[0141] The BWP field of the 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, the DCI format 0_1 may involve a change in the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting the 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 that schedules a PUSCH without changing an 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 the 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 function of switching the BWP by the DCI format 0_1, the BWP field may be ignored by the terminal device 1. That is, the terminal device 1 that does not support the function of switching the BWP may recognize that the PUSCH is transmitted without switching the active uplink BWP based on detecting the DCI format 0_1 that is used for scheduling the PUSCH and includes the BWP field. Here, if the terminal device 1 supports the function of switching the BWP, it may report that "the terminal device 1 supports the function of switching the BWP" in the function information reporting procedure of the RRC layer.
[0144] The CSI request field is used to indicate the reporting of CSI.
[0145] When the DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier on which the PUSCH is arranged. When the DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is arranged may be the same as the uplink component carrier on which the PDCCH including the DCI format 0_1 used for scheduling the PUSCH is arranged. When the number of uplink component carriers configured in the 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 the DCI format 0_1 used for scheduling the PUSCH arranged in the certain serving cell group may be one bit or more (for example, three bits). When the number of uplink component carriers configured in a terminal device 1 in a serving cell group is 1 (when uplink carrier aggregation is not operated in a 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 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 serving cell group).
[0146] DCI format 1_0 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_0 includes at least a part or all of 3A to 3F. 3A) DCI format specific fields 3B) Frequency domain resource allocation field 3C) Time Domain Resource Allocation Field 3D) MCS field 3E) PDSCH_HARQ feedback timing indicator field 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 at least to indicate 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 arranged in the PDSCH. The size of the transport block (TBS: Transport Block Size) arranged in 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 an 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, a downlink component carrier on which a PDSCH scheduled by DCI format 1_0 is arranged may be the same as a downlink component carrier on which a PDCCH including the DCI format 1_0 is arranged. The terminal device 1 may recognize that a PDSCH scheduled by the DCI format 1_0 is arranged on a downlink component carrier based on detecting DCI format 1_0 in the downlink component carrier.
[0154] The DCI format 1_0 may not include a BWP field. Here, the DCI format 1_0 may be a DCI format for scheduling a PDSCH without changing an active downlink BWP. The terminal device 1 may recognize that the PDSCH is to be received without switching the active downlink BWP based on detecting the DCI format 1_0 used for scheduling the PDSCH.
[0155] DCI format 1_1 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_1 includes at least some or all of 4A to 4I. 4A) DCI format specific fields 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 4I) Career 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 at least to indicate 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 a slot including the last OFDM symbol of the PDSCH to a slot including 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 a slot including the last OFDM symbol of the PDSCH to a slot including the first OFDM symbol of the PUCCH may be specified by a higher layer parameter.
[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 the DCI format 1_1 may be used to indicate a downlink BWP in which a PDSCH scheduled by the DCI format 1_1 is arranged. That is, the DCI format 1_1 may involve a change in the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged based on detecting the 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 that schedules a PDSCH without changing an active downlink BWP. The terminal device 1 may recognize that the PDSCH is received 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 the DCI format 1_1 includes a BWP field, but the terminal device 1 does not support the function of switching the BWP by the DCI format 1_1, the BWP field may be ignored by the terminal device 1. That is, the terminal device 1 that does not support the function of switching the BWP may recognize that the PDSCH is received without switching the active downlink BWP based on detecting the DCI format 1_1 that is used for scheduling the PDSCH and includes the BWP field. Here, if the terminal device 1 supports the function of switching the BWP, it may report that "the terminal device 1 supports the function of switching the BWP" in the function information reporting procedure of the RRC layer.
[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 a DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink component carriers configured in a 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 a 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 in a terminal device 1 in a serving cell group is 1 (when downlink carrier aggregation is not operated in a 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 serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group).
[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. The transport block may be arranged in the PDSCH. A transport block corresponding to the DL-SCH may be arranged in 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 may not carry information generated in a higher layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. 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 primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
[0169] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym), with the vertical axis indicating the frequency domain. Block 700 indicates a set of resource elements for the PSS. Block 720 indicates a set of resource elements for the SSS. Four blocks (blocks 710, 711, 712, and 713) indicate sets of resource elements for the PBCH and DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).
[0170] As shown in FIG. 7, the SS / PBCH block includes a PSS, an SSS, and a PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is arranged in the 57th to 183rd subcarriers of the first OFDM symbol. The SSS is arranged in the 57th to 183rd subcarriers of the third OFDM symbol. The 1st to 56th subcarriers of the first OFDM symbol may be set to zero. The 184th to 240th subcarriers of the first OFDM symbol may be set to zero. The 49th to 56th subcarriers of the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol may be set to zero. The PBCH is arranged in the 1st to 240th subcarriers of the second OFDM symbol, which are subcarriers in which the DMRS for the PBCH is not arranged. 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 a 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 is included.
[0173] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.
[0174] A set of antenna ports of DMRS for PDSCH (DMRS related to PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) may be given based on the set of antenna ports for the PDSCH, i.e., the set of antenna ports of 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 be 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 on which a symbol of a certain PDSCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH on which a symbol of the PDSCH in a certain antenna port is transmitted 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 (assumed to be applied, assumed to be applied) to a set of resource elements on which a symbol of a certain PDCCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDCCH is transmitted, a PDCCH on which a symbol of the PDCCH in 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 a physical layer channel and a MAC layer channel (also called a logical channel).
[0180] The BCH of the transport layer is mapped to the PBCH of the physical layer, i.e., the transport block carried by the BCH of the transport layer is delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer, i.e., the transport block carried by the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer, i.e., the transport block carried by the DL-SCH of the transport layer is delivered to the PDSCH of the physical layer.
[0181] For each serving cell, one UL-SCH and one DL-SCH may be provided. The BCH may be provided for the PCell. The BCH does not have to be provided for the PSCell or SCell.
[0182] In the MAC layer, hybrid automatic repeat reQuest (HARQ) control is performed for each transport block.
[0183] The BCCH (Broadcast Control CHannel), the CCCH (Common Control CHannel), and the 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 an RRC message common to a plurality of terminal devices 1. Here, the CCCH may be used, for example, for a terminal device 1 that is not RRC-connected. The DCCH (Dedicated Control CHannel) may be used at least for transmitting an RRC message dedicated to the terminal device 1. Here, the DCCH may be used, for example, for a terminal device 1 that is RRC-connected.
[0184] The upper layer parameters common to a plurality of 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, B, and C) in which the serving cell is set.
[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 the common upper layer parameters are also called 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 set. In other words, the dedicated RRC parameters are upper layer parameters that can provide unique settings for each of the terminal devices 1-A, B, and 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 including MIB information is delivered to the BCH of the transport layer. A transport block including system information other than MIB is delivered to the DL-SCH of the transport layer. A CCCH is mapped to the DL-SCH or UL-SCH. That is, a transport block mapped to a CCCH is delivered to the DL-SCH or UL-SCH. A DCCH is mapped to the DL-SCH or UL-SCH. That is, a transport block mapped to a 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. The RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.
[0189] The upper layer parameters are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element). In other words, 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 procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C. 5A) Cell search 5B) Random access 5C) Data communication
[0191] The cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in terms of 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 terms of the time domain and the frequency domain and detect a physical cell ID.
[0192] The sequence of the PSS is based at least on the physical cell ID. The sequence of the SSS is based at least on the physical cell ID.
[0193] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH block is permitted (possible, reserved, configured, defined, possible).
[0194] A set of SS / PBCH block candidates in a half radio frame is also called an SS burst set. The SS burst set is also called a transmission window, an SS transmission window, or a Discovery Reference Signal transmission window (DRS transmission window). The SS burst set is a general term including 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 is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.
[0197] Message 1 is a procedure for transmitting a PRACH by a terminal device 1. The terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based on at least an index of an SS / PBCH block candidate detected based on a cell search. Each of the PRACH opportunities is defined based on at least 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] Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including the DCI format in a control resource set given based on an MIB included in a PBCH included in an SS / PBCH block detected based on a cell search, and in resources indicated based on the setting of a search space set. Message 2 is also called a random access response.
[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 for message 2. Here, the random access response grant is indicated by a MAC CE included in a PDSCH scheduled by the 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 a 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 C-RNTI (Cell-Radio Network Temporary Identifier) 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 specified 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 continuous resources (non-interleaved mapping) or may be composed of distributed resources (interleaver mapping).
[0207] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter. 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 a search space set, may be attempting to detect a DCI format in a search space set, may be attempting to detect a PDCCH in a control resource set, may be attempting to detect a PDCCH candidate in a control resource set, or may be attempting to detect a DCI format in a 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 a part 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 dedicated PDCCH search space set.
[0212] A search space set is associated with (contains, corresponds to) a control resource set. The index of the control resource set associated with the search space set may be indicated by a higher layer parameter.
[0213] For a given search area set, some or all of 6A to 6C may be indicated by at least higher layer parameters. 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 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 a resource 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 given based on at least some or all of a PDCCH monitoring interval, a PDCCH monitoring pattern in a slot, and a PDCCH monitoring offset.
[0215] 8 is a diagram showing an example of a monitoring opportunity of the 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,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunities of search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each of the slots.
[0218] The monitoring interval of search space set 92 is set to 2 slots, the monitoring offset of search space set 92 is set to 0 slots, and the monitoring pattern of search space set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search space set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.
[0219] The monitoring interval of search space set 93 is set to 2 slots, the monitoring offset of search space set 93 is set to 0 slots, and the monitoring pattern of search space set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0,0], i.e., the monitoring opportunity of search space set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.
[0220] The monitoring interval of search space set 94 is set to 2 slots, the monitoring offset of search space set 94 is set to 1 slot, and the monitoring pattern of search space set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search space 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 Cyclic Redundancy Check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).
[0222] The Type 0a PDCCH common search space set may be used at least for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).
[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 resource allocation of the PDSCH. The detected downlink DCI format is also called a downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, the terminal device 1 reports a HARQ-ACK corresponding to the PDSCH (a HARQ-ACK corresponding to a transport block included in the PDSCH) to the base station device 3.
[0228] In uplink communication, the terminal device 1 detects an uplink DCI format. The detected DCI format is used at least for resource allocation of a PUSCH. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.
[0229] In configured scheduling, 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, part or all of the information indicated by the uplink DCI format may be indicated by an 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 configured scheduling type 1 PUSCH transmission may be configured semi-statically. For example, the configured scheduling type 1 PUSCH transmission may be operated in response to reception of certain higher layer parameters. The certain higher layer parameters may be configuredGrantConfig. For example, the configuredGrantConfig may include rrc-ConfiguredUplinkGrant. The PUSCH transmission may be operated without detection of 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 an uplink grant. The uplink grant may be included in an activation DCI (activation DCI or valid activation DCI). For example, after receiving certain higher layer parameters, the configured scheduling type 2 PUSCH transmission may be scheduled by an uplink grant. The certain higher layer parameters may be configuredGrantConfig. For example, configuredGrantConfig may not include rrc-ConfiguredUplinkGrant.
[0232] System frame number (SFN) f may be a number assigned to a radio frame and / or an index for a radio frame. The system frame number may be composed of 10 bits. At least a part of the system frame number may be signaled in the MIB. For example, 6 bits (e.g., 6 most significant bits) of the 10-bit system frame number may be signaled in the MIB. At least a part of the system frame number may be determined based on the PBCH for conveying the MIB. For example, 4 bits (e.g., 4 least significant bits) of the 10-bit system frame number may be conveyed in the PBCH transport block as part of the channel coding.
[0233] The PDCCH-Config may be a dedicated higher layer parameter. The PDCCH-Config may configure parameters for the PDCCH. In the PDCCH-Config, multiple (e.g., up to three) CORESETs may be configured. In one CORESET, a CORESET ID may be configured. In one CORESET, one CORESET pool index may be configured.
[0234] The PDSCH-Config may be a dedicated higher layer parameter. The PDSCH-Config may configure parameters for the PDSCH.
[0235] 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 among the two PDCCH candidates. The higher layer parameter may be searchSpaceLinking.
[0236] At least two transmission schemes may be supported for the PUSCH. For example, codebook-based transmission may be one of the transmission schemes for the PUSCH. For example, non-codebook-based transmission may be one of the transmission schemes for the PUSCH. The higher layer parameters may provide either codebook transmission or non-codebook transmission. For example, if 'codebook' is set for the higher layer parameters, the terminal device 1 may be configured for codebook transmission. For example, if 'nonCodebook' is set for the higher layer parameters, the terminal device 1 may be configured for non-codebook transmission. The higher layer parameters may be txConfig. The higher layer parameters may be usage. For example, if the higher layer parameters are not set, the terminal device 1 may not expect to be scheduled by either DCI format 0_1 or DCI format 0_2. If the PUSCH is scheduled by DCI format 0_0, the transmission of the PUSCH may be based on at least one antenna port.
[0237] In the codebook transmission, the PUSCH may be scheduled by a DCI format. The DCI format may be any of DCI format 0_0, DCI format 0_1, and DCI format 0_2. In the codebook transmission, the PUSCH may be set to be transmitted semi-statically. The terminal device 1 may determine one or more precoders for the PUSCH transmission. For example, the precoder may be determined based on at least some or all of an SRS resource indicator (SRI), a Transmitted Precoding Matrix Indicator (TPMI), and a transmission rank (Transmission rank, or rank). For example, the SRI may be provided by a DCI field of an SRS resource indicator of 1 or 2. For example, the TPMI may be provided by a DCI field of precoding information of 1 or 2. For example, the transmission rank may be provided by a DCI field of a layer number (transmission layer number). The SRI may be provided by a first higher layer parameter. The TPMI and transmission rank may be provided by a second higher layer parameter. The first higher layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2. The second higher layer parameter may be precodingAndNumberOfLayers or precodingAndNumberOfLayers2.
[0238] The SRS resource set applied to the PUSCH may be determined based on a higher layer parameter. The PUSCH may be scheduled by DCI format 0_1 or DCI format 0_2. The higher layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModeListDCI-0-2. The higher layer parameter may be a higher layer parameter configured in SRS-Config.
[0239] If the higher layer parameter usage is set to 'codebook', one or two SRS resource sets may be configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The higher layer parameter usage may be configured in the higher layer parameter SRS-ResourceSet.
[0240] When one SRS resource set is configured, the SRI and the TPMI may be given by the DCI field. The TPMI may be used to indicate a precoder. The precoder may be applied across v layers. When multiple SRS resources are configured, one SRS resource may be selected by the SRI. The transmission precoder (precoder) may be selected from a codebook (uplink codebook). For example, the codebook may have the number of antenna ports. The number of antenna ports may be equal to the higher layer parameter nrofSRS-Ports. When the higher layer parameter txConfig is set to 'codebook', the terminal device 1 may be configured with at least one SRS resource. The indicated SRI may be related to the transmission of the SRS resource identified by the SRI.
[0241] When two SRS resource sets are configured, one or two SRIs and one or two TPMIs may be given by a DCI field. For example, the DCI field may be one or both of a DCI field of an SRS resource indication and a DCI field of precoding information and a number of layers. The terminal device 1 may apply the indicated SRI and TPMI to one or more PUSCH repetitions. The TPMI may be used to indicate a precoder based on a code point of the SRS resource set indication. The precoder may be applied to the 0th to v-1th layers. The precoder may correspond to an SRS resource selected by the SRI. Multiple SRS resources may be configured for the applicable SRS resource set. With one or two TPMIs, a transmission precoder (precoder) may be selected from a codebook (uplink codebook). When two SRIs are indicated, the terminal device 1 may expect the number of antenna ports for the two indicated SRS resources to be the same. The number of antenna ports may be provided by a higher layer parameter.
[0242] In codebook transmission, the terminal device 1 may determine a codebook subset. For example, the codebook subset may be determined based at least on the TPMI. The codebook subset may be determined in response to receiving a certain higher layer parameter. The certain higher layer parameter may be codebookSubset or codebookSubsetDCI-0-2. The certain higher layer parameter may be set to any of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', and 'nonCoherent'. For example, if at least a certain higher layer parameter is set to 'partialAndNonCoherent', the codebook subset associated with a two-port SRS resource (SRS resource having two ports) may be 'nonCoherent'. For example, the codebook may include at least one SRS resource with four ports and at least one SRS resource with two ports.
[0243] The terminal device 1 may report a UE capability. When the terminal device 1 reports a UE capability of 'partialAndNonCoherent' transmission, the terminal device 1 may not expect a codebook subset having 'fullyAndPartialAndNonCoherent' to be configured.
[0244] When the terminal device 1 reports a UE capability of 'nonCoherent' transmission, the terminal device 1 may not expect a codebook subset with 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent' to be configured.
[0245] If the number of antenna ports indicates that the maximum number of SRS antenna ports to be configured is 2, the terminal device 1 may not expect that a higher layer parameter to which 'partialAndNonCoherent' is set is configured. The higher layer parameter may be codebookSubset or codebookSubsetForDCI-Format0-2. The number of antenna ports may be determined by the higher layer parameter nrofSRS-Ports.
[0246] In codebook transmission, one SRS resource may be determined based on the SRI from the SRS resource set. The maximum number of SRS resources configured for codebook transmission may be two, except when 'fullpowerMode2' is set in the first higher layer parameter. The first higher layer parameter may be ul-FullPowerTransmission. The DCI may indicate transmission of the SRS resource. For example, when aperiodic SRS is configured, the SRS request field in the DCI may indicate transmission of the aperiodic SRS resource. The terminal device 1 may not expect that the first higher layer parameter to be set to 'fullpowerMode1' and the second higher layer parameter to be set to 'fullAndPartialAndNonCoherent' are configured.
[0247] The terminal device 1 may transmit the PUSCH using the same one or more antenna ports as one or more SRS ports in the SRS resource indicated by the DCI format or the higher layer parameter. For example, the SRS port may be the same as the antenna port for PUSCH transmission. The DMRS antenna port may be determined according to the ordering of the DMRS port.
[0248] If multiple SRS resources are configured by an SRS resource set, the terminal device 1 may expect that the higher layer parameter nrofSRS-Ports with the same value is configured for these SRS resources. The SRS resource set may be the higher layer parameter SRS-ResourceSet with the higher layer parameter usage set to 'codebook'.
[0249] When 'fullpowerMode2' is set for the higher layer parameters, one or more SRS resources with the same or different SRS port counts may be configured in an SRS resource set. When 'fullpowerMode2' is set for the higher layer parameters, up to two different spatial relations may be configured for all SRS resources in an SRS resource set. When 'fullpowerMode2' is set for the higher layer parameters, up to two or four SRS resources may be configured in an SRS resource set. Also, up to eight SRS resources may be configured in an SRS resource set. An SRS resource set may be an SRS resource set with the higher layer parameter usage set to 'codebook'.
[0250] In non-codebook transmission, the PUSCH may be scheduled by DCI format 0_0, DCI format 0_1, or DCI format 0_2. The terminal device 1 may determine the precoder and transmission rank of the PUSCH based on the SRI. For example, when multiple SRS resources are configured, the SRI may be given by one or two SRS resource indications in the DCI. For example, the SRI may be given by a higher layer parameter. The SRS resource set applied to the PUSCH may be defined by an entry in the higher layer parameter. The higher layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.
[0251] The terminal device 1 may use one or more SRS resources for SRS transmission. The maximum number of SRS resources in one SRS resource set may be transmitted to the base station device 3 as UE capability (terminal capability). The SRS resources may be configured for simultaneous transmission in the same OFDM symbol. Multiple SRS resources transmitted simultaneously may occupy the same resource block. One SRS port may be configured in each SRS resource. One or two SRS resource sets may be configured in the upper layer parameter srs-ResourceSetToAddModList in which the upper layer parameter usage in the upper layer parameter SRS-ResourceSet is set to 'nonCodebook'. When two SRS resource sets are configured, one or two SRIs may be given by the DCI field. The DCI field may be a DCI field of two SRS resource indications.
[0252] The terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions. For example, according to the SRS resource set of the PUSCH repetition, the terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions. The maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be four. The maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be eight. Each of the one or two indicated SRIs may be related to the latest transmission of the SRS resource of the SRS resource set identified by the SRI. The SRS transmission may be before the PDCCH that conveys the SRI. The terminal device 1 may not expect that different numbers of SRS resources are configured in the two SRS resource sets.
[0253] The terminal device 1 may apply the "indicated TCI state" to one or more PUSCH repetitions. For example, according to an SRS resource set indication field or a TRP indication field, the terminal device 1 may apply the "indicated TCI state" to one or more PUSCH repetitions. Each of the one or two "indicated TCI states" may relate to a latest indication of the TCI state indicated by the first DCI format. The first DCI format may be transmitted before the second DCI format that schedules the PUSCH repetition.
[0254] 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 among the two PDCCH candidates. The higher layer parameter may be searchSpaceLinking.
[0255] In non-codebook transmission, the terminal device 1 may calculate a precoder. For example, a precoder used for SRS transmission may be calculated based on measurements of NZP CSI-RS resources. One NZP CSI-RS resource may be configured for one SRS resource set. For example, one SRS resource set may be an SRS resource set with higher layer parameters set to 'nonCodebook'.
[0256] When an aperiodic SRS resource set is configured, the NZP-CSI RS may be indicated via an SRS request field. The SRS request field may be one of the DCI fields in any of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2. A first upper layer parameter may indicate an association between an aperiodic SRS (aperiodic SRS triggering state) and an SRS resource set. The first upper layer parameter, the triggered SRS resource, srs-ResourceSetId, and csi-RS may be configured in an upper layer parameter SRS-ResourceSet. The upper layer parameter csi-RS may indicate the NZP-CSI-RS-ResourceId. The upper layer parameter SRS-ResourceSet associated with the SRS request may be defined by an entry in a list that is an upper layer parameter. The list, which is an upper layer parameter, may be the upper layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The terminal device 1 may not be expected to update the precoding information (SRS precoding information). For example, if the gap from the last OFDM symbol of reception of the aperiodic NZP-CSI-RS resource to the first OFDM symbol of the aperiodic SRS transmission is 42 OFDM symbols or less, the terminal device 1 may not be expected to update the precoding information.
[0257] If an aperiodic SRS associated with the aperiodic NZP CSI-RS resource is configured, the presence of the CSI-RS may be indicated by the SRS request field. If the value of the SRS request field is not '00' and the scheduling DCI is not used for cross carrier scheduling or cross bandwidth part scheduling, the presence of the CSI-RS may be indicated by the SRS request field.
[0258] The terminal device 1 may perform one-to-one mapping. The one-to-one mapping may be a mapping from the SRI to the DMRS port and the corresponding PUSCH layer. PUSCH layers from 0 to v-1 may be provided. v may be the number of layers. The number of layers may be set by a higher layer parameter. The number of layers may be indicated by the DCI. The terminal device 1 may transmit the PUSCH using the same antenna port as the SRS port. For example, the SRS port in the SRS resource indicated by the SRI may be indexed as pi = 1000 + i. For example, the SRS port in the (i + 1)th SRS resource may be pi. Also, the SRS port in the (i + 1)th SRS resource may be indexed as pi. pi may be 1000 + i. That is, pi = 1000 + i.
[0259] In non-codebook transmission, the terminal device 1 may not expect that both the spatial relation information (info) for the SRS resource and the upper layer parameter associatedCSI-RS in the upper layer parameter SRS-ResourceSet for the SRS resource set are configured. The spatial relation information may be determined by the upper layer parameter. The spatial relation information may be the upper layer parameter spatialRelationInfo. In non-codebook transmission, when at least one SRS resource is configured in an SRS resource set with the upper layer parameter set to 'nonCodebook', the terminal device 1 may be scheduled by DCI format 0_1 or DCI format 0_2. The spatial relation information may be determined by the TCI state. The spatial relation information may be determined by the "indicated TCI state".
[0260] One or more SRS resource sets (Sounding Reference Signal resource sets) may be configured by a first higher layer parameter. The first higher layer parameter may be SRS-ResourceSet or SRS-PosResourceSet. In each SRS resource set, K SRS resources may be configured. K may be an integer equal to or greater than 1. The maximum value of K may be indicated by the UE capability. The maximum value of K may be 16. The adaptability of the SRS resource set may be configured in a second higher layer parameter. The second higher layer parameter may be usage. For example, when 'beamManagement' is set for the second higher layer parameter, one SRS resource may be transmitted in each of the one or more SRS resource sets. For example, an SRS resource may be transmitted at a given time instance. Multiple SRS resources in different SRS resource sets may be transmitted simultaneously. For example, multiple SRS resources with the same time domain behavior in different SRS resource sets of the same BWP may be transmitted simultaneously.
[0261] For aperiodic SRS, at least one DCI field may be used to select at least one from the configured SRS resource set.
[0262] When two SRS resource sets (a first SRS resource set and a second SRS resource set) are configured and the number of repetitions K in the PUSCH repetition type A is greater than 1, the same OFDM symbol allocation may be applied over K consecutive slots, and the PUSCH may be limited to one transmission layer. The terminal device 1 may repeat a transport block over K consecutive slots. When the code point "00" in the SRS resource set indication field is indicated, the first SRS resource set may be associated with K consecutive slots. When the code point "01" in the SRS resource set indication field is indicated, the second SRS resource set may be associated with K consecutive slots. When the code point "10" in the SRS resource set indication field is indicated, the first SRS resource set and the second SRS resource set may be associated with K consecutive slots. For example, when K=2, the first SRS resource set may be applied to the first slot, and the second SRS resource set may be applied to the second slot. If K>2 and cyclicMapping is enabled, the first and second SRS resource sets may be applied to the first and second slots of K consecutive slots, respectively, and the same SRS resource set mapping pattern may be followed for the remaining slots of the K consecutive slots. If K>2 and sequentialMapping is enabled, the first SRS resource set may be applied to the first and second slots of K consecutive slots, and the second SRS resource set may be applied to the third and fourth slots of K consecutive slots, and the same SRS resource set mapping pattern may be followed for the remaining slots of the K consecutive slots. If codepoint “11” is indicated in the SRS resource set indication field, the first SRS resource set and the second SRS resource set may be associated with K consecutive slots. For example, if K=2, the second SRS resource set may be applied to the first slot, and the first SRS resource set may be applied to the second slot.If K>2 and cyclicMapping is enabled, the second and first SRS resource sets may be applied to the first and second slots of K consecutive slots, respectively, and the same SRS resource set mapping pattern may be followed for the remaining slots of the K consecutive slots. If K>2 and sequentialMapping is enabled, the second SRS resource set may be applied to the first and second slots of K consecutive slots, and the first SRS resource set may be applied to the third and fourth slots of K consecutive slots, and the same SRS resource set mapping pattern may be followed for the remaining slots of the K consecutive slots. The SRS resource set indicator field may be included in one or both of DCI format 0_1 and DCI format 0_2. Two SRS resource sets may be configured with usage set to 'codebook' or 'noncodebook' in SRS-ResourceSet.
[0263] The SRS resource set indication field may determine one or two TCI states. For example, if the SRS resource set indication field indicates “00” or “01”, one TCI state may be used. For example, if the SRS resource set indication field indicates “10” or “11”, two TCI states may be used. The one or two TCI states may be one or both of a UL TCI state (UL-TCIState) and a DL / Joint TCI state (DLorJoint-TCIState). The one or two TCI states may be one or both of an “indicated UL TCI state (UL-TCIState)” and an “indicated DL / Joint TCI state (DLorJoint-TCIState)”.
[0264] The SRS resource set indication field may determine that one or both of the first TCI state and the second TCI state are used. For example, if the SRS resource set indication field indicates "00", the first TCI state may be used. For example, if the SRS resource set indication field indicates "01", the second TCI state may be used. For example, if the SRS resource set indication field indicates "10" or "11", the first TCI state and the second TCI state may be used.
[0265] The terminal device 1 may be applied with STxMP (Simultaneous Transmission with Multi panel). STxMP (Simultaneous Transmission with Multi panel) may be applied for one or both of the first uplink physical channel and the second uplink physical channel. When STxMP is applied, the terminal device 1 may transmit the first uplink physical channel and the second uplink physical channel simultaneously. When STxMP is applied, the terminal device 1 may transmit the first uplink physical channel and the second uplink physical channel in the same time resource and the same frequency resource. When STxMP is applied, a first CDM (Code Division Multiplexing) group of a first DMRS port indicated for the first uplink physical channel may be different from a second CDM group of a second DMRS port indicated for the second uplink physical channel. It may not be expected that the first CDM group and the second CDM group are the same. One or both of the first DMRS port and the second DMRS port may be indicated by an antenna port field in one DCI format. The first CDM group and the second CDM group may be indicated by an antenna port field. When STxMP is applied, the first uplink physical channel and the second uplink physical channel may correspond to one precoding matrix. The one precoding matrix may be determined by a TPMI field in the DCI format. When STxMP is applied, the first uplink physical channel may correspond to a first TCI state, and the second uplink physical channel may correspond to a second TCI state. The first TCI state and the second TCI state may be indicated by a TCI (Transmission Configuration Indication) field in DCI format 1_1 / 1_2.When STxMP is applied, the first uplink physical channel may correspond to a first uplink transmit spatial filter (UL Tx Spatial filter), and the second uplink physical channel may correspond to a second uplink transmit spatial filter. The first uplink transmit spatial filter may be determined by an SRS resource indication (SRI) field in the DCI format. The second uplink transmit spatial filter may be determined by a Second SRI field in the DCI format.
[0266] When STxMP is applied, the first transmission layer number (rank number) corresponding to the first uplink physical channel may be the same as or different from the second transmission layer number (rank number) corresponding to the second uplink physical channel. The difference between the first transmission layer number and the second transmission layer number may not be expected to be two or more. When STxMP is applied, the first uplink physical channel and the second uplink physical channel may fully overlap. When STxMP is applied, the first uplink physical channel and the second uplink physical channel may not be expected to partially overlap. When STxMP is applied, the first transport block corresponding to the first uplink physical channel may not be expected to differ from the second transport block corresponding to the second uplink physical channel. When STxMP is applied, each of the first uplink physical channel and the second uplink physical channel may not be expected to carry two transport blocks (codewords). When STxMP is applied, it may not be expected that the higher layer parameter sfnSchemePusch or the higher layer parameter sfnSchemePucch is configured for one or both of the first uplink physical channel and the second uplink physical channel. When the higher layer parameter sfnSchemePusch is configured for a PUSCH, the DMRS port of the PUSCH may be a reference signal and a QCL for multiple (e.g., two) TCI states. When the higher layer parameter sfnSchemePucch is configured for a PUCCH, the DMRS port of the PUCCH may be a reference signal and a QCL for multiple (e.g., two) TCI states.
[0267] The application of STxMP may be configured by a higher layer parameter. For example, the application of STxMP for PUSCH may be configured by a dedicated higher layer parameter for PUSCH. For example, the application of STxMP for PUCCH may be configured by a dedicated higher layer parameter for PUCCH. The application of STxMP may be indicated by a DCI format.
[0268] The PUSCH-MTRP method may be a general term for PUSCH repetition when cyclicMapping is enabled, PUSCH repetition when sequentialMapping is enabled, and STxMP. For example, the application of the PUSCH-MTRP method may be any of the following: cyclicMapping is enabled, sequentialMapping is enabled, and STxMP is applied.
[0269] A plurality of TRPs (Transmission Reception Points, or Transmit / Receive Points) may be used. The base station device 3 may be configured with a plurality of TRPs (Multi-TRPs). The terminal device 1 may be scheduled by two TRPs in one serving cell. In the Multi-TRP, one of the operation modes of single-DCI and multi-DCI may be used. In the Multi-TRP, uplink control may be completed in the MAC layer and the physical layer. In the Multi-TRP, downlink control may be completed in the MAC layer and the physical layer. In the Single-DCI mode, the terminal device 1 may be scheduled by the same DCI for two TRPs. In the Multi-DCI mode, the terminal device 1 may be scheduled by independent DCI from each TRP. In the Multi-DCI mode, each TRP in the Multi-TRP may be identified by TRP information. That is, one TRP of the Multi-TRP may be identified by one TRP information. The TRP information may be used to select one TRP. Also, an index of a CORESET resource pool may be associated with one control resource set (CORESET). The terminal device 1 may transmit a PUSCH based on the index of the CORESET resource pool. The terminal device 1 may transmit a PDCCH and a PDSCH based on the index of the CORESET resource pool. The TRP information may be a CORESET pool index. The TRP information may be provided by a TRP indication field.
[0270] 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 one or both of transmitting and receiving radio waves. A radio wave having directionality may be called a beam. Information related to a beam may be called 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 relationship.
[0271] 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) the PDSCH according to the PDCCH with DCI. M may depend on the terminal capability (UE capability). For example, M may depend on the terminal capability maxNumberConfiguredTCIStatePerCC. The TCI-State may be referred to as a TCI state.
[0272] 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 a channel / signal A and a channel / signal B may indicate that the channel / signal A is QCL with the channel / signal B.
[0273] 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 typeA, typeB, typeC, and typeD.
[0274] The terminal device 1 may be configured with an upper layer parameter DLorJointTCIState. 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 128 upper layer parameters DLorJointTCIState (TCIState). One list may be a list of up to 128 upper layer parameters DLorJointTCIState (TCIState). One list may be configured to provide one reference signal. The upper layer parameter DLorJointTCIState (TCIState) may be configured to provide one reference signal. The one reference signal may be a reference signal for the DMRS of the PDSCH and the QCL for the DMRS of the PDCCH. The one reference signal may be a reference signal for the CSI-RS. One list may be configured to provide one reference. The upper layer parameter DLorJointTCIState may be configured to provide one reference. The one reference may be used to determine an uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter may be used for PUSCH, PUCCH, and SRS. That is, one reference may be provided to determine the uplink transmit spatial filter for PUSCH, PUCCH, and SRS. The TCI state may be DLorJointTCIState (TCIState). DLorJointTCIState may be referred to as DL / Joint TCI state or unified TCI state. One list may be dl-OrJoint-TCIStateList.
[0275] The terminal device 1 may be configured with an upper layer parameter UL-TCIState. For example, the terminal device 1 may be configured with one list in the upper layer parameter BWP-UplinkDedicated. One list may include up to 64 upper layer parameters UL-TCIState. One list may be a list of up to 64 upper layer parameters UL-TCIState. Each UL-TCIState (or UL-TCIState setting) may include a parameter for setting one reference signal. For example, each UL-TCIState may include one parameter for setting one reference signal for determining an uplink transmission spatial filter for a part or all of the PUSCH, the PUCCH, and the SRS. One list may be the upper layer parameter ul-TCI-StateList. The TCI state may be a UL-TCIState. The UL-TCIState may be referred to as a UL TCI state or a unified TCI state.
[0276] The UL-TCIState may be a higher layer parameter TCI-UL-State. The UL-TCIState may be set by the higher layer parameter TCI-UL-State. The higher layer parameter TCI-UL-State may associate one or two downlink reference signals with one corresponding QCL type.
[0277] When DLorJointTCIState or UL-TCIState is set, 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 transmission spatial filter. The one reference signal may be a reference signal set in a qcl-Type in which typeD is set in the "indicated TCI state". The "indicated TCI state" may be the indicated DLorJointTCIState or the indicated UL-TCIState. The reference RS in the indicated DLorJointTCIState may be a CSI-RS resource in the higher layer parameter NZP-CSI-RS-ResourceSet. The reference RS in the indicated UL-TCIState may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet. The indicated UL-TCIState (Indicated UL-TCIState) 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 DLorJointTCIState (Indicated DLorJointTCIState) 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.
[0278] DLorJointTCIState (e.g., upper layer parameter DLorJointTCIState) and UL-TCIState (e.g., upper layer parameter UL-TCIState) may be set in one BWP of one component carrier. If the setting of DLorJointTCIState or the setting of UL-TCIState is not present in one BWP, the terminal device 1 may apply the setting of DLorJointTCIState or the setting of UL-TCIState from a reference BWP.
[0279] The terminal device 1 may not expect both the first higher layer parameter and the second higher layer parameter to be set. The first higher layer parameter may be any of TCI-State, SpatialRelationInfo, and PUCCH-SpatialRelationInfo. The second higher layer parameter may be any of DLorJointTCIState and UL-TCIState. When TCI-State is set in any component carrier in a certain list, the second higher layer parameter may not be set in any component carrier in the same band in the certain list. The certain list may be set by the higher layer parameter simultaneousTCI-UpdateList1, the higher layer parameter simultaneousTCI-UpdateList2, the higher layer parameter simultaneousSpatial-UpdatedList1, or the higher layer parameter simultaneousSpatial-UpdatedList2.
[0280] The terminal device 1 may receive an activation command. The activation command may be used to map up to eight "TCI states and / or pairs of TCI states" to code points of the DCI field 'Transmission Configuration Indication'. The pair of TCI states may involve one TCI state (DL TCI state) for multiple downlink channels / signals and one TCI state (UL TCI state) for multiple uplink channels / signals. The multiple downlink channels / signals may be a part or all of the PDSCH, PDCCH, and CSI-RS. The multiple uplink channels / signals may be a part or all of the PUSCH, PUCCH, and 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).
[0281] If a first set of one or more TCI status IDs is activated in the second set, the first set may be applied for downlink BWPs in the indicated component carrier. If a first set of one or more TCI status IDs is activated in the third set, the first set may be applied for downlink BWPs and uplink BWPs in the indicated component carrier. The second set may be a set of one or more component carriers and one or more downlink BWPs. The third set may be a set of some or all of one or more component carriers, one or more downlink BWPs, and one or more uplink BWPs.
[0282] If the activation command maps one or both of DLorJointTCIState and UL-TCIState to one TCI code point (code point of DCI field 'Transmission Configuration Indication'), the terminal device 1 may apply one or both of the indicated DLorJointTCIState (Indicated DLorJointTCIState) and the indicated UL-TCIState (Indicated UL-TCIState).
[0283] The terminal device 1 may receive DCI format 1_1 / 1_2 that provides the indicated DLorJointTCIState or the indicated UL-TCIState. The DCI format may not be accompanied by a downlink assignment. For example, when DCI format 1_1 / 1_2 is not 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 DCI, RV (Redundancy version) is all 1's, MCS is all 1's, NDI is 0, all 0's are set for FDRA type 0, and all 1's are set for FDRA type 1.
[0284] 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 state may be referred to as an "applied TCI state". When one TCI state is selected, 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, 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 DLorJointTCIState or an "indicated UL-TCIState". The DCI format may be referred to as a DCI.
[0285] N conf N TCI states may be set. For example, conf The TCI states may be configured in the radio resource control layer. For example, conf The 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.
[0286] N act N TCI states may be activated. For example, act The TCI states are N conf For example, N act N TCI states may be activated in the medium access control layer. For example, actN 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.
[0287] N ind N TCI states may be indicated. For example, ind The TCI states are N act For example, N ind The TCI states may be indicated at the physical layer. For example, ind N TCI states may be indicated by the DCI. For example, 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 "indicated TCI state." A "indicated TCI state" may apply to the PDSCH, the PDCCH, and the CSI-RS. A "indicated TCI state" may apply to the PUSCH, the PUCCH, and the SRS. A "indicated TCI state" may apply to the PDSCH, the PDCCH, the CSI-RS, the PUSCH, the PUCCH, and the SRS. ind may be an integer from 1 to 4.
[0288] N app N TCI states may be indicated and / or applied. For example, app The TCI states are N ind For example, N app The TCI states may be indicated at the physical layer. For example, app N TCI states may be indicated by the DCI. For example, app The TCI states may be indicated by the TRP indication field in the DCI. app Each of the N TCI states may be referred to as an "applicable TCI state." app may be 1 or 2.
[0289] The terminal device 1 may receive a higher layer configuration. After the "TCI state to be set" is set and before one "instructed TCI state" is applied from the "TCI state to be set", 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 the SS / PBCH block and the QCL. For example, after the terminal device 1 receives the first configuration of multiple DLorJoint-TCIState and before one instructed TCI state is applied from the set 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 the SS / PBCH block and the QCL.
[0290] The terminal device 1 may receive an upper layer configuration. After the terminal device 1 is configured with a "set TCI state" and before one "indicated TCI state" is applied from the "set TCI state", the terminal device 1 may assume that a first uplink transmission spatial filter for the PUSCH, PUCCH, and SRS to which the "indicated TCI state" is applied is the same as a second uplink transmission spatial filter. For example, after the terminal device 1 receives the first configuration of a plurality of DLorJoint-TCIStates or a plurality of UL-TCIStates and before one indicated TCI state is applied from the set TCI state, the terminal device 1 may assume that a first uplink transmission spatial filter (UL TX spatial filter) for the PUSCH, PUCCH, and SRS to which the indicated TCI state is applied is the same as a second uplink transmission spatial filter. The second uplink transmission spatial filter may be an uplink transmission spatial filter for PUSCH transmission scheduled by a random access response grant in an initial access procedure.
[0291] After the terminal device 1 receives multiple DLorJoint-TCIState settings ("TCI states to be set") and before one "indicated TCI state" is applied from the set 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 reconfiguration with synchronization. For example, the terminal device 1 may receive the DLorJoint-TCIState setting as part of a reconfiguration with synchronization.
[0292] After the terminal device 1 receives multiple DLorJoint-TCIState or multiple UL-TCIState settings ("set TCI states") and before one "indicated TCI state" is applied from the set TCI states, it may be assumed that the first uplink transmit spatial filter for PUSCH, PUCCH, and SRS to which the indicated TCI state is applied is the same as the second uplink transmit spatial filter. 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.
[0293] DLorJoint-TCIState may be used as a "specified TCI state". For example, the terminal device 1 may obtain a QCL assumption (QCL relation, QCL) for the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the "specified TCI state" applies from the "set TCI state". The "specified TCI state" may be applied to the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS. The "specified 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.
[0294] The UL-TCIState 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, the PUCCH, and the SRS to which the “indicated TCI state” applies.
[0295] 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 conveying a TCI state indication without a downlink assignment. The HARQ-ACK information may be HARQ-ACK information corresponding to a PDSCH scheduled by a DCI conveying a TCI state indication. The second indicated TCI state may be indicated before (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 a terminal capability. The indicated TCI state may be an indicated DLorJointTCIState or an indicated UL-TCIState.
[0296] If the higher layer parameter PDCCH-Config includes two different values of a CORESET pool index (CORESET Pool Index or coresetPoolIndex), 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 a code point of 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'.
[0297] One code point of the DCI field 'Transmission Configuration Indication' 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 status pairs" in an activation command.
[0298] 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 the 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.
[0299] When the first higher layer parameter is configured, and when the first time offset is greater than or equal to the first value, and after the terminal device 1 receives the first configuration of the TCI state (TCI state to be configured), and before an activation command (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.
[0300] 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 to which 'enabled' is set. The first higher layer parameter may be tci-PresentInDCI to which 'enabled' is set for a CORESET that schedules a PDSCH or a multicast PDSCH. The first higher layer parameter may be tci-PresentDCI-1-2.
[0301] If the first DCI format schedules a PDSCH and if 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 a 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.
[0302] When the first higher layer parameter and the second higher layer parameter are configured, and when the time offset is equal to or greater than a threshold, and when DCI scheduling without TCI state is supported, the TCI state or QCL assumption for the PDSCH may be the same as the TCI state or QCL assumption applied to the CORESET used for receiving DL DCI. The sameness may be independent of the number of activated TCI states of the CORESET. When dynamic switching between SFN PDSCH and non-SFN PDSCH is not supported, the terminal device 1 may be activated with a CORESET including two TCI states. When dynamic switching between SFN PDSCH and non-SFN PDSCH is not supported, two "indicated TCI states" (applied TCI states) may be applied to the PDSCH. For example, when dynamic switching between SFN PDSCH and non-SFN PDSCH is not supported, it may not be expected that one "indicated TCI state" (applied TCI state) is applied to the PDSCH. DL DCI may be received in an active BWP of the serving cell. The DL DCI may be a DCI for a downlink channel (downlink physical channel). The SFN PDSCH may be a PDSCH to which SFN is applied. The first higher layer parameter may be sfnSchemePdcch. The second higher layer parameter may be sfnSchemePdsch. The time offset may be a time offset between reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL. Setting sfnSchemePdcch may mean that a Single Frequency Network (SFN) is applied to the PDCCH. Applying the SFN scheme may mean that the same DMRS port is transmitted from different panels at the same time. One beam may correspond to one panel. One TSI state may correspond to one panel.
[0303] If the first upper layer parameter and the second upper layer parameter are not set, if scheduling is performed by DCI format 1_1 / 1_2, and if the time offset is equal to or greater than a threshold, the terminal device 1 may expect the TCI field to be present. The first upper layer parameter may be sfnSchemePdcch. The second upper layer parameter may be sfnSchemePdsch.
[0304] If the PDSCH is scheduled with DCI format 1_0 / 1_1 / 1_2, and the first higher layer parameter is configured, and the second higher layer parameter is not configured, and there is no TCI codepoint (codepoint in TCI field) with two TCI states in the activation command, and the time offset is equal to or greater than a threshold, the TCI state or QCL assumption for the PDSCH may be the first TCI state or QCL assumption applied to the CORESET used for the PDCCH when the CORESET schedules the PDSCH indicated with two TCI states. The first higher layer parameter may be sfnSchemePdcch where 'sfnSchemeA' is set. The second higher layer parameter may be sfnSchemePdsch.
[0305] If the time offset is less than or equal to a threshold and if at least one "TCI state to be configured" includes a QCL type of typeD, some or all of operations 1, 2, 3, 4, and 5 may be performed. The time offset may be a time offset between reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL.
[0306] In operation 1, the DMRS port of the first PDSCH may be a first reference signal and a QCL with respect to a first QCL parameter. The first QCL parameter may be used for a PDCCH QCL indication of a CORESET. The CORESET may be associated with a search space (search space set) with a smallest CORESET ID (controlResourceSetId) among one or more CORESETs in an active BWP. The CORESET may also be a CORESET in a latest slot among one or more CORESETs in an active BWP.
[0307] In operation 2, when the first higher layer parameter and the second higher layer parameter are configured, the DMRS port of the second PDSCH associated with the first value of the CORESET pool index may be a reference signal and a QCL for the second QCL parameter. The second QCL parameter may be used for a PDCCH QCL indication of the CORESET. The CORESET may be configured with the same CORESET pool index as the PDCCH that schedules the second PDSCH. The CORESET may be associated with a search space with the smallest CORESET ID. The CORESET may be the CORESET in the latest slot. The first higher layer parameter may be enableDefaultTCI-StatePerCoresetPoolIndex. The second higher layer parameter may be a PDCCH-Config including two different values of the CORESET pool index (coresetPoolIndex).
[0308] In act 3, if a third higher layer parameter is configured and at least one TCI codepoint indicates two TCI states, the DMRS port of the PDSCH (or PDSCH transmission opportunity) may be a reference signal and a QCL for a third QCL parameter. The third QCL parameter may be associated with a TCI state corresponding to a minimum codepoint of a plurality of TCI codepoints. Each of the plurality of TCI codepoints may include two different TCI states. Also, if a fourth higher layer parameter is configured and the time offset is less than or equal to a threshold, a mapping of TCI states to PDSCH transmission opportunities may be determined. For example, an "indicated TCI state" with a TCI state corresponding to a minimum codepoint of a plurality of TCI codepoints may be applied to the PDSCH transmission opportunity. One TCI codepoint may indicate up to four TCI states. The third higher layer parameter may be enableTwoDefaultTCI-States. The fourth higher layer parameter may be a repetitionScheme set to 'tdmSchemeA'. The fourth higher layer parameter may be repetitionNumber. The repetitionScheme may be configured for the PDSCH to apply a time division multiplexing (TDM) scheme for the PDSCH. The time offset may be a time offset between the reception of the DL DCI and the first PDSCH transmission opportunity.
[0309] In operation 4, if the fifth higher layer parameter is not configured, and if the sixth higher layer parameter is configured, and if there is no TCI codepoint with multiple TCI states in the activation command, and if the CORESET with the smallest ID is indicated with multiple (e.g., two) TCI states, the DMRS port of the PDSCH may be the reference signal and QCL for the fourth QCL parameter. The fourth QCL parameter may be associated with a first TCI state of the multiple (e.g., two) TCI states indicated for the CORESET. The CORESET may be the CORESET in the latest slot. The fifth higher layer parameter may be sfnSchemePdsch. The sixth higher layer parameter may be sfnSchemePdcch where 'sfnSchemeA' is set.
[0310] In operation 5, if the "TCI state to be set" for the serving cell of the scheduled PDSCH is not set with a QCL type of type D, the terminal device 1 may obtain a QCL assumption from the "TCI state to be indicated".
[0311] If the PDCCH carrying the scheduling DCI is received on the first component carrier, and if the PDSCH scheduled by the scheduling DCI is on the second component carrier, the threshold may be determined based on the subcarrier spacing (subcarrier spacing setting) of the scheduled PDSCH, and an additional time may be added to the threshold. The additional time may be determined based on the subcarrier spacing (subcarrier spacing setting) of the PDCCH and the PDSCH. If the PDCCH carrying the scheduling DCI is received on the first component carrier, and if the PDSCH scheduled by the scheduling DCI is on the second component carrier, and if the first higher layer parameter is configured, and if the time offset is less than or equal to the threshold, the terminal device 1 may obtain a QCL assumption for the scheduled PDSCH from the "activated TCI state" or the "indicated TCI state". The "activated TCI state" or the "indicated TCI state" may be accompanied by a minimum ID and may be applied to the PDSCH in the active BWP of the scheduled serving cell. The scheduling DCI may be a DCI for scheduling a downlink physical channel or an uplink physical channel. The first higher layer parameter may be enableDefaultBeamForCCS.
[0312] 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 in 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 a TCI state setting (TCI state to be set) with DLorJointTCIState or UL-TCIState 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 set to '1'.
[0313] In order to determine the time offset, if the PDCCH reception includes two PDCCHs from two associated search space sets, a PDCCH candidate may be used. The time offset may be a time offset between the reception of DL DCI and the corresponding PDSCH. The PDCCH candidate may be a PDCCH candidate that terminates later in time. In the configuration of the first higher layer parameter, if the PDCCH reception includes two PDCCH candidates from two associated search space sets, the terminal device 1 may expect the same configuration in the first CORESET and the second CORESET that are related to the two PDCCH candidates. The PDCCH reception including two PDCCHs (PDCCH candidates) from two associated search space sets may be that search space linking is applied. The application of PDCCH repetition may be that one PDCCH reception including two PDCCHs (PDCCH candidates) from two associated search space sets is applied.
[0314] If the Periodic CSI-RS resources in the NZP-CSI-RS-ResourceSet are configured with a first higher layer parameter, the TCI state may indicate one of multiple QCL types. The multiple QCL types may include type C for the SS / PBCH block. The first higher layer parameter may be trs-Info. The first higher layer parameter may indicate that the antenna ports for all Non Zero Power CSI-RS (NZP-CSI-RS) resources in the CSI-RS resource set are the same.
[0315] In periodic CSI-RS and semi-persistent CSI-RS, the indicated TCI state (e.g., indicated DLorJointTCIState) may not apply.
[0316] For CSI-RS resources in the NZP-CSI-RS resource set (NZP-CSI-RS-ResourceSet) without the first higher layer parameter and the second higher layer parameter, the TCI state may indicate one of a plurality of QCL types. The plurality of QCL types may include type A for the CSI-RS in the NZP-CSI-RS resource set with the first higher layer parameter. The plurality of QCL types may include type B for the CSI-RS in the NZP-CSI-RS resource set with the first higher layer parameter. The first higher layer parameter may be trs-Info. The second higher layer parameter may be repetition.
[0317] For a CSI-RS resource in the NZP-CSI-RS resource set with the second higher layer parameter, the TCI state may indicate one of multiple QCL types. The multiple QCL types may include type B for the CSI-RS in the NZP-CSI-RS resource set with the first higher layer parameter. The multiple QCL types may include type C for the SS / PBCH block. The second higher layer parameter may be repetition.
[0318] The DMRS port of the PDCCH may be DL-RS (Downlink Reference Signal) and QCL in multiple (e.g., two) TCI states. For example, if a first higher layer parameter is configured and CORESET is activated in multiple (e.g., two) TCI states, the DMRS port of the PDCCH in CORESET may be DL-RS and QCL in multiple (e.g., two) TCI states. The first higher layer parameter may be sfnSchemePdcch. The first higher layer parameter may be sfnSchemePdcch with 'sfnSchemeA' set. The first higher layer parameter may be sfnSchemePdcch with 'sfnSchemeB' set. The second of the two TCI states may not include the QCL parameter {Doppler shift, Doppler spread}. For example, when the first higher layer parameter is configured and the CORESET is activated in one TCI state, the DMRS port of the PDCCH in the CORESET may be a DL-RS and a QCL of multiple (e.g., two) "indicated TCI states". For example, when the first higher layer parameter is configured, the DMRS port of the PDCCH in the CORESET may be a DL-RS and a QCL of multiple (e.g., two) "indicated TCI states", regardless of the number of activated TCI states of the CORESET. Setting the first higher layer parameter may be an application of an SFN scheme for the PDCCH.
[0319] For DMRS of PDSCH, the TCI state may indicate one QCL type, which may be typeA for CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info. For DMRS of PDCCH, the TCI state may indicate one QCL type, which may be typeA for CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info.
[0320] If the first higher layer parameter is configured and multiple (e.g., two) TCI states are indicated, the DMRS port of the PDSCH may be DL-RS and QCL in multiple (e.g., two) TCI states. Multiple TCI states may be indicated in one codepoint of the DCI field 'Transmission Configuration Indication' in the DCI scheduling the PDSCH. The first higher layer parameter may be sfnSchemePdsch. The first higher layer parameter may be sfnSchemePdsch with 'sfnSchemeA' set. The first higher layer parameter may be sfnSchemePdsch with 'sfnSchemeB' set. The second of the two TCI states may not include the QCL parameter {Doppler shift, Doppler spread}. When the first higher layer parameter is configured, and when multiple (e.g., two) TCI states are indicated, and when the TRP indication field indicates a third indication or a fourth indication, the DMRS port of the PDSCH may be DL-RS and QCL of multiple (e.g., two) TCI states. Configuring the first higher layer parameter may be applying an SFN scheme for the PDSCH.
[0321] The terminal device 1 may receive a DMRS for a PDSCH scheduled by a PDCCH with a DCI format. If two TCI states are indicated and the terminal device 1 receives the DMRS and SS / PBCH block of the PDSCH in the same OFDM symbol, at least one DMRS port for the PDSCH and the SS / PBCH block may be QCL in type D ('QCL-Type D'). If the first higher layer parameter is configured and if 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 a DMRS port in one CDM group. The first higher layer parameter may be a PDCCH-Config including two different CORESET pool indexes.
[0322] In the downlink, a maximum of 16 or 32 HARQ processes may be supported in one serving cell. The number of HARQ processes may be configured by higher layer parameters. If the higher layer parameters are not configured, the number of HARQ processes may be 8.
[0323] 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.
[0324] The higher layer parameters may include values of two different CORESET pool indices. PDCCHs that schedule two PDSCHs (a first PDSCH and a second PDSCH) may be associated with CORESETs having different values of a CORESET pool index. The higher layer parameters may be PDCCH-Config. The terminal device 1 may receive the first PDSCH and the second PDSCH.
[0325] 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, the P-RNTI, and the 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. The second PDSCH may be scheduled with the RA-RNTI and the 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 in 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.
[0326] 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.
[0327] 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 be overlapping or non-overlapping in the time-frequency domain. If the multiple PDCCHs are associated with different CORESETs, the terminal device 1 may receive multiple PDSCHs simultaneously. The different CORESETs may have different CORESET pool index (coresetPoolIndex) values.
[0328] If CORESET (upper layer parameter ControlResourceSet) is not accompanied by a CORESET pool index (upper layer parameter coresetPoolIndex), the terminal device 1 may assume that CORESET is assigned a CORESET pool index of 0.
[0329] A first physical cell ID associated with the first CORESET may be different from a second physical cell ID associated with the second CORESET. For example, the first CORESET and the second CORESET may be associated with different physical cell IDs via an activated TCI state. The first CORESET and the second CORESET may correspond to different CORESET pool indices.
[0330] When repetition is configured for the PDSCH, the first higher layer parameter may not be expected to be configured. The first higher layer parameter may be a repetitionScheme. The repetition may be configured for the PDSCH by configuring a repetitionNumber for the PDSCH. The first higher layer parameter may be configured by applying a frequency division multiplexing (FDM) scheme, a time division multiplexing (TDM) scheme, or a spatial division multiplexing (SDM) scheme.
[0331] If the first higher layer parameter is configured and if multiple (e.g., two) TCI states and one or more DMRS ports are indicated, some or all of operations 6, 7 and 8 may be performed. The first higher layer parameter may be repetitionScheme. In repetitionScheme, 'fdmSchemeA', 'fdmSchemeB' or 'tdmSchemeA' may be set. Multiple TCI states may be included in one code point of DCI field 'Transmission Configuration Indication'. One or more DMRS ports may be DMRS ports in one CDM group. One CDM (Code division multiplexing) group may be indicated by DCI field 'Antenna Port(s)'.
[0332] In operation 6, when 'fdmSchemeA' is set in the terminal device 1 and multiple (e.g., two) TCI states are indicated by one DCI, the terminal device 1 may receive one PDSCH transmission opportunity for one transport block or transmit one PUSCH transmission opportunity in each TCI state. The application of FDM scheme A may be the setting of 'fdmSchemeA' in the terminal device 1. Each TCI state may be associated with a non-overlapping frequency domain resource allocation.
[0333] In operation 7, when 'fdmSchemeB' is set in the terminal device 1 and multiple (e.g., two) TCI states are indicated by one DCI, the terminal device 1 may receive two PDSCH transmission opportunities of the same transport block or transmit two PUSCH transmission opportunities in each TCI state. The application of FDM scheme B may be the setting of 'fdmSchemeB' in the terminal device 1. Each TCI state may be associated with a first PDSCH transmission opportunity of the two PDSCH transmission opportunities. The first PDSCH transmission opportunity may have a non-overlapping frequency domain resource allocation for the second PDSCH transmission opportunity of the two PDSCH transmission opportunities. Each TCI state may be associated with a first PUSCH transmission opportunity of the two PUSCH transmission opportunities. The first PUSCH transmission opportunity may have a non-overlapping frequency domain resource allocation for the second PUSCH transmission opportunity of the two PUSCH transmission opportunities.
[0334] In operation 8, when 'tdnSchemeA' is set in the terminal device 1 and multiple (e.g., two) TCI states are indicated by one DCI, the terminal device 1 may receive two PDSCH transmission opportunities of the same transport block in each TCI state. Each TCI state may be associated with a first PDSCH transmission opportunity of the two PDSCH transmission opportunities. The first PDSCH transmission opportunity may have a non-overlapping time domain resource allocation for a second PDSCH transmission opportunity of the two PDSCH transmission opportunities. The two PDSCH transmission opportunities may be received within one slot. The application of the TDM scheme A may be a setting of 'tdmSchemeA' in the terminal device 1. The application of the TDM scheme A may be a setting of an upper layer parameter repetitionScheme in which 'tdmSchemeA' is set in the terminal device 1.
[0335] A frequency division multiplexing (FDM) scheme (fdmScheme) may be applied to one or both of the PDSCH and the PUSCH. An FDM scheme A (fdmSchemeA) may be applied to one or both of the PDSCH and the PUSCH. An FDM scheme B (fdmSchemeB) may be applied to one or both of the PDSCH and the PUSCH. A time division multiplexing (TDM) scheme (tdmScheme) may be applied to one or both of the PDSCH and the PUSCH. A TDM scheme A (tdmSchemeA) may be applied to one or both of the PDSCH and the PUSCH. A TDM scheme B (tdmSchemeB) may be applied to one or both of the PDSCH and the PUSCH. An fdmScheme may be a collective term for fdmSchemeA and fdmSchemeB. The tdmScheme may be a general term for tdmScheme A and tdmScheme B. A spatial division multiplexing (SDM) scheme (sdmScheme) may be applied to one or both of the PDSCH and the PUSCH.
[0336] If an FDM scheme is applied, if multiple (e.g., two) TCI states are indicated, and if a DMRS port in one CDM group is indicated, the first plurality of physical resource blocks may be assigned to the first TCI state, and the second plurality of physical resource blocks may be assigned to the second TCI state. The sum of the first plurality of physical resource blocks and the second plurality of physical resource blocks may be the total number of physical resource blocks allocated for the terminal device 1. If an FDM scheme is applied, if multiple (e.g., two) TCI states are indicated, and if a DMRS port in one CDM group is indicated, the even physical resource block group may be assigned to the first TCI state, and the odd physical resource block group may be assigned to the second TCI state. Both the even physical resource block group and the odd physical resource block group may be within the allocated frequency domain resources. If an FDM scheme is applied, and if multiple (e.g., two) TCI states are indicated, and if a DMRS port in one CDM group is indicated, the terminal device 1 may not expect more than two PDSCH transmission layers for each PDSCH transmission opportunity. The application of an FDM scheme may mean that the higher layer parameter repetitionScheme is set to 'fdmSchemeA' or 'fdmSchemeB' in the terminal device 1.
[0337] When FDM scheme B is applied, and two TCI states are indicated, and a DMRS port in one CDM group is indicated, each PDSCH transmission opportunity may be mapped to a resource element. The resource element may be determined by the physical resource block allocated for the TCI state of the PDSCH transmission opportunity. When FDM scheme B is applied, and two TCI states are indicated, and a DMRS port in one CDM group is indicated, and a transmission layer 1 is scheduled, the terminal device 1 may expect up to two code blocks per PDSCH transmission opportunity. When FDM scheme B is applied, and two TCI states are indicated, and a DMRS port in one CDM group is indicated, and a transmission layer 2 is scheduled, the terminal device 1 may expect one code block per PDSCH transmission opportunity. In the two PDSCH transmission opportunities, a first redundancy version may be applied to the first TCI state, and a second redundancy version may be applied to the second TCI state. The application of FDM scheme B may be achieved by setting the upper layer parameter repetitionScheme in terminal device 1 to 'fdmSchemeB'.
[0338] If FDM scheme B is applied, and if two TCI states are indicated, and if a DMRS port in one CDM group is indicated, then a modulation order of the first PDSCH transmission opportunity may be applied to the second PDSCH transmission opportunity. The first PDSCH transmission opportunity may be associated with the first TCI state. The second PDSCH transmission opportunity may be associated with the second TCI state.
[0339] When FDM scheme B is applied, and when two TCI states are indicated, and when a DMRS port in one CDM group is indicated, the terminal device 1 may determine a total number of resource elements for the PDSCH. The total number of allocated physical resource blocks may correspond to a first TCI state. The TBS of a first PDSCH transmission opportunity associated with the first TCI state may be applied to a second PDSCH transmission opportunity associated with the second TCI state.
[0340] When TDM scheme A is applied, and when two TCI states are indicated, and when a DMRS port in one CDM group is indicated, the terminal device 1 may determine the total number of resource elements in one physical resource block for the PDSCH. The number of OFDM symbols for the PDSCH allocation in one slot may correspond to the first TCI state. The TBS of the first PDSCH transmission opportunity associated with the first TCI state may be applied to the second PDSCH transmission opportunity associated with the second TCI state.
[0341] When TDM scheme A is applied and DMRS ports in one CDM group are indicated, the number of PDSCH transmission opportunities may be the number of TCI states indicated by the DCI field 'Transmission Configuration Indication'. Also, when two TCI states (a first TCI state and a second TCI state) are indicated, two PDSCH transmission opportunities (a first PDSCH transmission opportunity and a second PDSCH transmission opportunity) may be expected to be received. Also, when one TCI state is indicated, the terminal device 1 may be expected to receive one PDSCH transmission opportunity. The first TCI state may be applied to the first PDSCH transmission opportunity. The second TCI state may be applied to the second PDSCH transmission opportunity. The second PDSCH transmission opportunity may have the same number of OFDM symbols as the first PDSCH transmission opportunity. The number of OFDM symbols K_bar may be the number of OFDM symbols from the last OFDM symbol of the first PDSCH transmission opportunity to the first OFDM symbol of the second PDSCH transmission opportunity. K_bar may be determined by higher layer parameters. The terminal device 1 may not expect to receive more than two PDSCH transmission layers for each PDSCH transmission opportunity. The first redundancy version may be applied to a first TCI state. The second redundancy version may be applied to a second TCI state. The PDSCH mapping type indicated by the DCI field 'Time domain resource assignment' may be expected to be mapping type B, and the PDSCH mapping type may be applied to two PDSCH transmission opportunities.
[0342] Repetition may be applied to one or both of the PDSCH and the PUSCH. The application of repetition may be the setting of a higher layer parameter repetitionNumber in the higher layer parameter PDSCH-TimeDomainResourceAllocation. When repetition is applied, the terminal device 1 may expect one or more (for example, two) TCI states to be indicated. One or more TCI states may be included in one code point of the DCI field 'Transmission Configuration Indication'. Also, the DCI field 'Time domain resource assignment' may indicate an entry including the higher layer parameter repetitionNumber. The DMRS port indicated to the terminal device 1 may be within one CDM group. When multiple TCI states are indicated, the terminal device 1 may receive PDSCH transmission opportunities of the same TB with multiple TCI states over multiple slots. When one TCI state is indicated, the terminal device 1 may receive PDSCH transmission opportunities of the same TB with one TCI state over multiple slots. The PDSCH transmission opportunity may be a multiple slot level PDSCH transmission opportunity. The repetition may be applied such that the DCI field 'Time domain resource assignment' indicates an entry that includes the repetitionNumber. The repetitionNumber may be included in the PDSCH-TimeDomainResourceAllocation in the PDSCH-Config.
[0343] If repetition is applied for the PDSCH, the same SLIV may be applied to all PDSCH transmission opportunities across multiple consecutive slots. The number of multiple consecutive slots may be determined by repetitionNumber. The SLIV may determine the starting OFDM symbol and the number of OFDM symbols.
[0344] If repetition is applied for PDSCH and two TCI states are indicated by the DCI field 'Transmission Configuration Indication' and DMRS ports within one CDM group are indicated, the same SLIV may be applied to all PDSCH transmission opportunities across multiple consecutive slots and a first TCI state may be applied to the first PDSCH transmission opportunity. If the repetition count is 2, a second TCI state may be applied to the second PDSCH transmission opportunity. If the repetition count is 3 or more and cyclic mapping is enabled, a first TCI state may be applied to the first PDSCH transmission opportunity and a second TCI state may be applied to the second PDSCH transmission opportunity, and the same TCI state mapping pattern may be followed for the remaining PDSCH transmission opportunities. Also, if the repetition count is 3 or more and sequential mapping is enabled, a first TCI state may be applied to the first and second PDSCH transmission opportunities, a second TCI state may be applied to the third and fourth PDSCH transmission opportunities, and the same TCI state mapping pattern may continue for the remaining PDSCH transmission opportunities. The number of multiple consecutive slots may be determined by repetitionNumber. The repetition count may be the value of repetitionNumber.
[0345] Each PDSCH transmission opportunity may be limited to two transmission layers. If all PDSCH transmission opportunities are associated with the first TCI state, the redundancy version (index for determining the redundancy version) may be counted considering only the PDSCH transmission opportunities associated with the first TCI state.
[0346] If repetition is applied for PDSCH and one TCI state is indicated by the DCI field 'Transmission Configuration Indication' and one DMRS port in one CDM group is indicated, the same SLIV may be applied to all PDSCH transmission opportunities across multiple consecutive slots and the same TCI state may be applied to all PDSCH transmission opportunities.
[0347] If repetition is not applied by the first DCI format, if multiple (e.g., two) TCI states are indicated by the first DCI format, if DMRS ports in two CDM groups are indicated by the first DCI format, and if SFN (SFN technique) is not applied, then the SDM technique may be applied. For example, the application of the SDM technique may be when condition 1, condition 2, condition 3, and condition 4 are satisfied. Condition 1 may be that repetition is not applied by the first DCI format. Condition 2 may be that multiple (e.g., two) TCI states are indicated by the first DCI format. Condition 3 may be that DMRS ports in two CDM groups are indicated by the first DCI format. Condition 4 may be that SFN (SFN technique) is not applied. If repetition is not applied by the first DCI format, if multiple (e.g., two) TCI states are indicated by the first DCI format, if DMRS ports in two CDM groups are indicated by the first DCI format, and if SFN (SFN technique) is not applied, the terminal device 1 may receive one PDSCH based on the SDM technique. Not applying repetition may be that the DCI field 'Time domain resource assignment' in the first DCI format does not indicate an entry including repetitionNumber. The multiple TCI states may be included in one code point of the DCI field 'Transmission Configuration Indication' in the first DCI format. The DMRS ports in the two CDM groups may be indicated by the DCI field 'Antenna Port(s)' in the first DCI format. If the SDM technique is applied, the first TCI state may correspond to a first CDM group of the first antenna port. The second TCI state may correspond to a second CDM group.
[0348] A Single Frequency Network (SFN) scheme may be applied to one or both of the PDSCH and the PUSCH. Setting the first higher layer parameter may mean that the SFN scheme is applied. The first higher layer parameter may be sfnSchemePdsch. The first higher layer parameter may be sfnSchemePdsch to which 'sfnSchemeA' is set. The first higher layer parameter may be sfnSchemePdsch to which 'sfnSchemeB' is set. The SFN scheme may be a general term for SFN scheme A and SFN scheme B.
[0349] When the SFN method is applied for the PDSCH and when the terminal device 1 reports a first terminal capability, the terminal device 1 may be indicated one or multiple (e.g., two) TCI states. The first terminal capability may be dynamicSFN. The first terminal capability may be dynamic switching of the SFN method. When the SFN method is applied and the terminal device 1 does not report a first terminal capability, the terminal device 1 may not expect one TCI state to be indicated in the TCI codepoint by the MAC CE, and multiple (e.g., two) TCI states may be indicated.
[0350] A Single Frequency Network (SFN) scheme may be applied to the PDCCH. Setting the first higher layer parameter may mean that the SFN scheme is applied. The first higher layer parameter may be sfnSchemePdcch. The first higher layer parameter may be sfnSchemePdcch to which 'sfnSchemeA' is set. The first higher layer parameter may be sfnSchemePdcch to which 'sfnSchemeB' is set. The SFN scheme may be a general term for SFN scheme A and SFN scheme B.
[0351] When an SFN scheme is applied for PDSCH and PDCCH, it may be expected that sfnSchemePdsch and sfnSchemePdcch are set to the same scheme (e.g., 'sfnSchemeA' or 'sfnSchemeB'). When an SFN scheme is applied for PDSCH, it may be that sfnSchemePdsch is set. When an SFN scheme is applied for PDCCH, it may be that sfnSchemePdcch is set.
[0352] When SFN scheme B is applied for the PDCCH and multiple (e.g., two) TCI states are activated by the MAC CE, the terminal device 1 may expect that SFN scheme B is applied for the PDSCH and that two TCI states are indicated. The application of SFN scheme B for the PDSCH may mean that sfnSchemePdsch is set to 'sfnSchemeB'. The application of SFN scheme B for the PDCCH may mean that sfnSchemePdcch is set to 'sfnSchemeB'. The PDSCH may be scheduled by DCI format 1_1 / 1_2.
[0353] When the 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 the PDCCH reception may be the start of the earlier PDCCH candidate, and the end of the PDCCH reception may be the end of the later PDCCH candidate.
[0354] In a BWP in a serving cell, if no CORESET pool index is provided, a CORESET less than or equal to 3 may be provided. In a BWP in a serving cell, if the same CORESET pool index is provided for all CORESETs, a CORESET less than or equal to 3 may be provided. In a BWP in a 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 less than or equal to 5 may be provided.
[0355] In each CORESET, at least a CORESET index may be provided by a first higher layer parameter, a QCL relation (antenna port QCL) by a second higher layer parameter, and an indication of whether a TCI field is present by a third higher layer parameter. The first higher layer parameter may be controlResourceSetId. The second higher layer parameter may be TCI-State. The third higher layer parameter may be tci-PresentInDCI or tci-PresentDCI-1-2.
[0356] If a value 0 is provided for the search space ID, the terminal device 1 may determine a search opportunity for the PDCCH candidate. The search space ID may be searchSpaceID. The search space ID may be included in the PDCCH-Config or PDCCH-ConfigCommon.
[0357] 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.
[0358] If no TCI state configuration is provided in one CORESET, or if two or more TCI state initial configurations are provided and no MAC CE activation command is received, the terminal device 1 may assume that the DMRS antenna port associated with PDCCH reception is the SS / PBCH block and the QCL. The SS / PBCH block may be identified by the terminal device 1 during the initial access procedure.
[0359] If two or more TCI state configurations are provided by reconfiguration with synch in one CORESET and if no MAC CE activation command is 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 the 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.
[0360] In the CORESET with index 0, if a TCI state (for example, a unified TCI state) is provided and the unified TCI state is applied, the terminal device 1 may assume that the DMRS antenna port (DMRS port) for the first PDCCH reception and the DMRS antenna port for the first PDSCH reception are the reference signal and QCL indicated in the TCI state. The application of the unified TCI state may be that followUnifiedTCIstate in which 'enable' is set is set. The first PDSCH reception may be scheduled by the DCI format provided by the first PDCCH reception. The unified TCI state may be DLorJoint-TCIState.
[0361] In a CORESET with index 0, if a TCI state (e.g., a unified TCI state) is provided and the unified TCI state is not applied, the terminal device 1 may select a DMRS antenna port (DMRS port) for receiving the first PDCCH as one or more reference signals and a QCL according to the activated TCI state.
[0362] If one TCI state is provided in a CORESET with 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".
[0363] When a unified TCI state is provided, the DMRS antenna ports for PDCCH reception in one CORESET with index other than 0 and the DMRS antenna ports for PDSCH scheduled by the DCI format provided by the PDCCH reception may be the reference signal and QCL provided by the indicated unified TCI state (the "indicated TCI state").
[0364] When multiple (e.g., two) unified TCI states are provided (or indicated), a DMRS antenna port for PDCCH reception in one CORESET with index other than 0 and a DMRS antenna port for PDSCH scheduled by the DCI format provided by the PDCCH reception may have a reference signal and QCL provided by one or both of the indicated unified TCI states ("indicated TCI states").
[0365] When a unified TCI state is applied, the DMRS antenna ports for PDCCH reception in one CORESET with index other than 0 and the DMRS antenna ports for PDSCH scheduled by the DCI format provided by the PDCCH reception may be the reference signal and QCL provided by the indicated unified TCI state (the "indicated TCI state").
[0366] Ten or less 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 by a second higher layer parameter, and a search space set (search space set index) linked by a third higher layer parameter may be determined. The first higher layer parameter may be searchSpaceId. The second higher layer parameter may be controlResourceSetId. In 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 be applying search space linking.
[0367] 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. The first search space set and the second search space set being linked may be 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.
[0368] When the first search space set and the second search space set are linked, and when 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. Also, the terminal device 1 may monitor the third PDCCH candidate corresponding to the third search space set for the second DCI format. Also, 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 set of CCEs and may be scrambled the same. Also, the third PDCCH candidate corresponding to the third search space set may not be counted for monitoring. Also, the detected DCI format may not be assumed to be the first DCI format.
[0369] When the first search space set and the second search space set are linked, and when the third search space set and the fourth search space set are linked, and when the size of the detected DCI format is the same, the terminal device 1 may expect different CCEs or different scrambling in one CORESET.
[0370] If 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 'typeD' property as the first CORESET. Repetition may be applied for the PDCCH. The repetition applied for the PDCCH may be provided as two-QCLTypeDforPDCCHRepetition.
[0371] When the first search space set and the second search space set are linked, the terminal device 1 may detect that the later terminated one of the two PDCCH receptions is a DCI format.
[0372] 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 starting from the first bit. 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.
[0373] 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. The MAC SDUs may be of variable size. Each MAC subheader may correspond to one MAC SDU, one MAC CE, or padding. One MAC PDU may be one transport block.
[0374] 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 LCID (Logical channel ID). For example, a value of the first LCID may be "TCI States Activation / Deactivation for UE-specific PDSCH".
[0375] FIG. 9 is a diagram showing an example of an activation command A according to an embodiment of the present invention. The serving cell ID field may indicate an identifier of a serving cell to which the first MAC CE is applied. The BWP ID field may indicate a DL BWP to which the MAC CE is applied as a code point of the 'bandwidth part indicator field' of the DCI. If the first MAC CE is applied to a set of multiple serving cells, the BWP ID field may be ignored. i The “T” field may indicate the activation / deactivation status of the TCI state with TCI state ID i. i The "T" field being set to 1 may indicate that the TCI state with TCI state ID i is activated. i The “T” 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 The "T" field being set to 0 may indicate that the TCI state with TCI state ID i is deactivated. iThe " 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). The 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 the mapping of the "activated TCI states" and the "T i A mapping between the code point of the DCI 'Transmission Configuration Indication' set by the "CoresetPoolIndex" field and the code point of the DCI 'Transmission Configuration Indication' set by the "CoresetPoolIndex" field may be used. 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.
[0376] 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, a value of the second LCID may be "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH".
[0377] 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 For example, "C i If the " field is set to 1, the 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-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 "C i" may be optional based on the indication of the field. i may be an index of the codepoint of the DCI 'Transmission configuration indication' field. j may be 1 or 2.
[0378] 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 MAC CE for activation / deactivation of the unified TCI states may be identified by the third MAC subheader. 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, a value of the third LCID may be "Unified TCI States Activation / Deactivation MAC CE".
[0379] FIG. 11 is a diagram showing an example of an activation command C according to an embodiment of the present invention. The DL BWP ID field may indicate one downlink BWP to which MAC CE is applied as one code point in the DCI's 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's bandwidth part indicator' field. i The “P” field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, i If the “P” field is set to 1, the i-th TCI codepoint may contain both DL and UL TCI states. For example, iIf the “D / U” field is set to 0, the i-th TCI code point may contain one of DL TCI state and UL TCI state. The “D / U” field may indicate whether the TCI state ID in the same octet is for joint (both DL and UL) / DL or UL. For example, if the “D / U” field is set to 1, the TCI state ID in the same octet may be for DL / joint. For example, if the “D / U” field is set to 0, the TCI state ID in the same octet may be for UL. The “TCI state ID” field may indicate the TCI state identified by the TCI state ID (TCI-StateId). 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 set to 0. 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. The DLorJointTCIState may be a DL TCI state or a Joint TCI state. The UL-TCIState may be a UL TCI state. The DL TCI state may be a TCI state for DL. The Joint TCI state may be a TCI state for both DL and UL. The UL TCI state may be a TCI state for UL. The TCI codepoint may be the codepoint of the DCI 'Transmission configuration indication' field. The "R" field in the MAC CE may be a reserved bit. The reserved bit may be set to 0.
[0380] 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".
[0381] FIG. 12 is a diagram showing an example of an activation command D according to an aspect of the present embodiment. The serving cell ID field may indicate an identifier of a serving cell to which the fourth MAC CE is applied. The DL BWP ID field may indicate one downlink BWP to which the fourth MAC CE is applied, as one code point 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 “P” field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, i If the “P” field is set to 1, the i-th TCI codepoint may contain both DL and UL TCI states. For example, i If the "D / U" field is set to 0, the i-th TCI codepoint may contain either DL TCI state or UL TCI state. i The “D / U” 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 "T" 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. jThe field “T” set to 1 may indicate that the TCI state with TCI state ID j is activated. j The “T” 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 The “T” field being set to 0 may indicate that the TCI state with TCI state ID j is deactivated. j The field “T” 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 i-th TCI code point corresponds to a UL TCI state, then “T j The “Activation / deactivation status” field may indicate the activation / deactivation status of the TCI state with TCI state ID j-128. For example, if the i-th TCI codepoint corresponds to the DL TCI state or the Joint TCI state, then the “T j The “Activation / deactivation status” field may indicate the activation / deactivation status of the TCI state with TCI state ID j-64. 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 activated. For example, if the i-th TCI codepoint corresponds to the UL TCI state, then "T j A field of “T” set to 1 may indicate that the TCI state with TCI state ID j-128 is mapped to the i-th TCI code point. For example, if the i-th TCI code point corresponds to the DL TCI state or the Joint TCI state, then “T j The “T” 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 the "TCI state to be activated" and the "TCI code point with TCI state ID j-64" set to 1. iA mapping between the MAC CE and the code point of the DCI 'Transmission Configuration Indication' set by the "Coreset Pool ID" field. Setting the CORESET Pool ID field to 1 may indicate that the MAC CE applies to downlink or uplink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET pool index) of value 1. Setting the CORESET Pool ID field to 0 may indicate that the MAC CE applies to downlink or uplink transmissions scheduled by a CORESET with a CORESET Pool ID (CORESET pool index) of value 0. If the CORESET Pool Index (coresetPoolIndex) is not set, the CORESET Pool ID field in the fourth MAC CE may be ignored.
[0382] FIG. 13 is a diagram showing an example of an activation command E according to an aspect of this embodiment. The field of the CORESET pool ID in FIG. 13 may be reserved. i,j The “P” field may indicate whether each TCI codepoint has multiple TCI states or one TCI state. For example, i,j If the “P” field is set to 1, the j-th TCI state in the i-th TCI codepoint may be two (e.g., DL TCI state and UL TCI state). For example, i,j If the “D / U” field is set to 0, the j-th TCI state in the i-th TCI codepoint may be one (e.g., DL TCI state or UL TCI state). j 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. jThe “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, “D / U j If the “D / U” field is set to 1, the TCI state ID in the same octet may be for DL / joint. For example, 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 “D / U” 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).
[0383] 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,j The “P” 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, i,j When the “P” field is set to 1, it may correspond to both DL and UL TCI states of the i-th 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 (higher layer parameter coresetPoolIndex) is not set, j may not correspond to a CORESET Pool-ID.
[0384] 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.
[0385] The activation command G may be a MAC CE for TCI state indication for 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 PDCCH, the activation command G may be applied. The application of SFN for PDCCH may be the setting of sfnSchemePdcch.
[0386] 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.
[0387] DCI formats 1_0 / 1_1 / 1_2 may be used for scheduling of PDSCH. A BWP indication (Bandwidth part indicator) field may be included in one or both of DCI format 1_1 and DCI format 1_2. The number of information bits constituting the BWP indication field may be determined based on the number of DL BWPs. A TPC command (TPC command for scheduled PUCCH) field may be included in one or both of DCI format 1_1 and DCI format 1_2. A second TPC command (Second TPC command for scheduled PUCCH) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when the higher layer parameter SecondTPCFieldDCI is configured, a second TPC command (Second TPC command for scheduled PUCCH) field may be included in DCI format 1_1.
[0388] 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.
[0389] The antenna port field may be included in DCI format 1_1 and DCI format 1_2. The number of information bits constituting the antenna port field may be 4, 5, or 6 bits. The number of information bits constituting the antenna port field may be 4, 5, 6, or 7 bits. The number of information bits constituting the antenna port field may be 4, 5, 6, 7, or 8 bits. The number of CDM groups without data may be any of value 1, value 2, and value 3. The number of CDM groups without data with value 1 may refer to CDM group 0. The number of CDM groups without data with value 2 may refer to CDM group {0, 1}. The number of CDM groups without data with value 3 may refer to CDM group {0, 1, 2}.
[0390] The upper layer parameter dmrs-Type being 1 may mean that DMRS configuration type 1 is configured. The upper layer parameter dmrs-Type being 2 may mean that DMRS configuration type 2 is configured. The upper layer parameter maxLength being 1 may mean that the maximum number of forward DMRS symbols is 1 symbol. The upper layer parameter maxLength being 2 may mean that the maximum number of forward DMRS symbols is 2 symbols. For example, the upper layer parameter maxLength being 1 may mean that a single-symbol forward DMRS (forward DMRS symbol) is configured. For example, the upper layer parameter maxLength being 2 may mean that a single-symbol forward DMRS (forward DMRS symbol) or a double-symbol forward DMRS is configured.
[0391] 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 port {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}.
[0392] 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.
[0393] DCI format 0_0 / 0_1 / 0_2 may be used for scheduling of PUSCH. A BWP indication (Bandwidth part indicator) field may be included in part or all of DCI format 0_1 and DCI format 0_2. The number of information bits constituting the BWP indication field may be determined based on the number of UL BWPs. A TPC command (TPC command for scheduled PUSCH) field may be included in one or both of DCI format 0_1 and DCI format 0_2. A second TPC command (Second TPC command for scheduled PUSCH) field may be included in one or both of DCI format 0_1 and DCI format 0_2. For example, when the higher layer parameter SecondTPCFieldDCI is configured, a second TPC command (Second TPC command for scheduled PUSCH) field may be included in DCI format 1_1.
[0394] An SRS resource indicator field may be included in one or both of DCI format 0_1 and DCI format 0_2. An SRS resource set indicator field may be included in one or both of DCI format 0_1 and DCI format 0_2. If the SRS resource set indicator field indicates 0 ("00"), the SRS resource indicator field and the fields of precoding information and number of layers may be associated with a first SRS resource set. If the SRS resource set indicator field indicates 1 ("01"), the SRS resource indicator field and the fields of precoding information and number of layers may be associated with a second SRS resource set. If the SRS resource set indicator field indicates 2 ("10"), the SRS resource indicator field and the fields of precoding information and number of layers 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.
[0395] One or both of a plurality of uplink channels / signals (e.g., PUSCH, PUCCH, SRS) and a plurality of downlink channels / signals (e.g., PDSCH, PDCCH, CSI-RS) can be beam-managed by one TCI state. That is, by applying one TCI state to a plurality of channels / signals, it is expected that the efficiency of beam management is improved. However, in the case of multiple transmission and reception points (Multiple-TRPs), it is difficult to switch the beam for each TRP by applying one TCI state to a plurality of channels / signals. Therefore, as a problem, it is necessary to apply one TCI state to a plurality of channels / signals and each TRP. This may enable efficient communication and efficient beam management. In addition, efficient beam management is expected in consideration of the time from when a beam is specified to when it is applied. As a means for solving the problem, the present invention may be used for beam management for a physical channel in consideration of the switching time of a part and all of the "TCI state to be set", the "TCI state to be activated", the "TCI state to be specified", and the "TCI state to be applied".
[0396] Fig. 14 is a diagram showing an example of management of a TCI state according to one embodiment of the present invention. The terminal device 1 may receive one or both of a PDSCH 1403 and a PDCCH 1404. The PDSCH 1403 may be transmitted to convey a transport block. The terminal device 1 may receive a PDCCH 1404 in which a DCI is arranged (mapped). A black circle in Fig. 14 may represent one TCI state.
[0397] One or more TCI states 1400 may be configured by higher layer parameters. For example, one or more UL TCI states (UL-TCIState) may be configured by higher layer parameters for each uplink BWP (BWP-UplinkDedicated). For example, one or more DL / Joint TCI states (DLorJointTCIState) 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 1400.
[0398] One or more TCI states 1401 may be activated by a MAC CE (e.g., an activation command). A first PDSCH may carry a first transport block. The first transport block may be a MAC PDU. The MAC PDU may include a MAC CE, which may be referred to as an activation command. For example, the activation command may be an activation command D or an activation command E. One or more TCI states and one or both of one or more “TCI state pairs” may be mapped to one or more code points. For example, one or more TCI states and one or both of one or more “TCI state pairs” may be mapped to one or more code points by an activation command. Each TCI state or each TCI state pair may be mapped to one code point. For example, each TCI state or each TCI state pair may be mapped to one code point by an activation command. The code points to which the TCI states or TCI state pairs are mapped may be code points in the TCI field. The code point to which the TCI state or pair of TCI states is mapped may be a code point of a TCI field in DCI format 1_1 or DCI format 1_2. The code point to which the TCI state or pair of TCI states is mapped may be a code point of a TCI field in DCI 1410. The TCI state activated by the MAC CE may be the activated TCI state 1401. The TCI state mapped to the code point of the TCI field may be the activated TCI state 1401.
[0399] If the CORESET pool index (coresetPoolIndex) is not set in one or more CORESETs (Control Resource Sets), activation command E may be used. If the CORESET pool index (coresetPoolIndex) is set in one or more CORESETs (Control Resource Sets), 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.
[0400] One or more TCI states 1402 may be indicated by a first DCI. The first DCI may be DCI format 1_1 or DCI format 1_2. The first DCI may include a Transmission configuration indication (TCI) 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 first DCI format may be the indicated TCI state 1402. The indicated TCI state 1402 may be some or all of a UL TCI state, a DL TCI state, and a Joint TCI state. The UL TCI state may be a TCI state for a PUSCH, a PUCCH, and an SRS. The DL TCI state may be a TCI state for a PDSCH, a PDCCH, and a CSI-RS. The Joint TCI state may be the TCI state for PUSCH, PUCCH, SRS, PDSCH, PDCCH, and CSI-RS.
[0401] The number of indicated TCI states 1402 may be four. For example, the indicated TCI states 1402 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.
[0402] The number of indicated TCI states 1402 may be three. For example, the indicated TCI states 1402 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.
[0403] The number of indicated TCI states 1402 may be two. For example, the indicated TCI states 1402 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.
[0404] The number of indicated TCI states 1402 may be two. For example, the indicated TCI states 1402 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.
[0405] The number of indicated TCI states 1402 may be one. For example, the indicated TCI state 1402 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.
[0406] The indicated TCI state 1402 is N from the last OFDM symbol of the PDCCH to which the DCI format 1_1 / 1_2 is mapped. symb The TCI state 1402 may be applied from the first slot after the symbol. The indicated TCI state 1402 may be applied to multiple channels / signals. symb may be BeamAppTime.
[0407] Some or all of the one or more TCI states 1402 may apply to the PDSCH 1403. The “indicated TCI state 1402” applied to the PDSCH 1403 may be one or both of one or more DL TCI states and one or more Joint TCI states. The “indicated TCI state” 1402 applied to the PDSCH 1403 may be an “applied TCI state” 1460. The TCI state 1460 may be an “applied TCI state” for the PDSCH 1403.
[0408] Some or all of the one or more TCI states 1402 may be applied to the PDCCH 1404. The “indicated TCI state 1402” applied to the PDCCH 1404 may be one or both of one or more DL TCI states and one or more Joint TCI states. The “indicated TCI state” 1402 applied to the PDCCH 1404 may be an “applied TCI state” 1461. The TCI state 1461 may be an “applied TCI state” for the PDCCH 1404.
[0409] The indicated TCI state 1402 may include at least a TCI state 1450 and a TCI state 1451. One or both of the TCI state 1450 and the TCI state 1451 may apply to the PDSCH 1403. One or both of the TCI state 1450 and the TCI state 1451 may apply to the PDCCH 1404. One or both of the TCI state 1450 and the TCI state 1451 that apply to the PDSCH 1403 may be a TCI state 1460. One or both of the TCI state 1450 and the TCI state 1451 that apply to the PDCCH 1404 may be a TCI state 1461.
[0410] The DCI format for the PDSCH 1403 may perform some or all of the first indication, the second indication, the third indication, and the fourth indication. The DCI format for the PDSCH 1403 may provide any of the first indication, the second indication, the third indication, and the fourth indication. For example, one field in the DCI format for the PDSCH 1403 may perform any of the first indication, the second indication, the third indication, and the fourth indication. One field in the DCI format for the PDSCH 1403 may provide any of the first indication, the second indication, the third indication, and the fourth indication. The DCI format for the PDSCH 1403 may perform any of the first indication, the second indication, the third indication, and the fourth indication for the PDSCH 1403 scheduled by the DCI format.
[0411] The higher layer parameters for the PDCCH 1404 may perform some or all of the first indication, the second indication, the third indication, and the fourth indication. The higher layer parameters for the PDCCH 1404 may provide any of the first indication, the second indication, the third indication, and the fourth indication. The higher layer parameters for the PDCCH 1404 may perform any of the first indication, the second indication, the third indication, and the fourth indication for the PDCCH 1404. The higher layer parameters for the PDCCH 1404 may be set for a CORESET for the PDCCH 1404.
[0412] Some or all of the first instruction, the second instruction, the third instruction, and the fourth instruction may be provided to determine an “applied TCI state” 1460 or an “applied TCI state” 1461. Determining an “applied TCI state” may include providing some or all of the first instruction, the second instruction, the third instruction, and the fourth instruction.
[0413] The first and second indications may be that one of the first TCI state 1450 and the second TCI state 1451 is applied to one or both of the PDSCH 1403 and the PDCCH 1404. The first indication may be that the first TCI state 1450 is applied to one or both of the PDSCH 1403 and the PDCCH 1404. The second indication may be that the second TCI state 1451 is applied to one or both of the PDSCH 1403 and the PDCCH 1404. The third and fourth indications may be that both the first TCI state 1450 and the second TCI state 1451 are applied to one or both of the PDSCH 1403 and the PDCCH 1404. The first indication may be that the first TCI state 1450 is used. The second indication may be that the second TCI state 1451 is used. The third and fourth indications may be that both the first TCI state 1450 and the second TCI state 1451 are used. The first indication may be that the first TCI state 1450 is applied to a plurality of downlink channels / signals including the PDSCH 1403. The second indication may be that the second TCI state 1451 is applied to a plurality of downlink channels / signals including the PDSCH 1403. The third and fourth indications may be that both the first TCI state 1450 and the second TCI state 1451 are applied to a plurality of uplink channels / signals including the PDSCH 1403.
[0414] The DCI format for the PDSCH 1403 may include a TRP indication field. The TRP indication field may provide any of a first indication, a second indication, a third indication, and a fourth indication. For example, if the TRP indication field indicates 0 ("00"), the first indication may be executed. For example, if the TRP indication field indicates 1 ("01"), the second indication may be executed. For example, if the TRP indication field indicates 2 ("10"), the third indication may be executed. For example, if the TRP indication field indicates 3 ("11"), the fourth indication may be executed. For example, the TRP indication field being 0 ("00") may be that the first indication is given. For example, the TRP indication field being 1 ("01") may be that the second indication is given. For example, the TRP indication field being 2 ("10") may be that the third indication is given. For example, the TRP indication field being 3 ("11") may be that the fourth indication is given. The TRP indication field may be a field different from the TCI field. When the higher layer parameter is configured, the number of information bits constituting the TRP indication field may be 2. When the higher layer parameter is not configured, the number of information bits constituting the TRP indication field may be 0. The TRP indication field may be included in both the UL scheduling DCI format and the DL scheduling DCI format. The UL scheduling DCI format may be a part or all of DCI format 0_0, DCI format 0_1, and DCI format 0_2. The DL scheduling DCI format may be a part or all of DCI format 1_0, DCI format 1_1, and DCI format 1_2.
[0415] The DCI format for the PDSCH 1403 may include a TCI field. The TCI field may provide any of a first indication, a second indication, a third indication, and a fourth indication. For example, if the TCI field indicates 0 ("00"), the first indication may be executed. For example, if the TCI field indicates 1 ("01"), the second indication may be executed. For example, if the TCI field indicates 2 ("10"), the third indication may be executed. For example, if the TCI field indicates 3 ("11"), the fourth indication may be executed. For example, the TCI field being 0 ("00") may be that the first indication is given. For example, the TCI field being 1 ("01") may be that the second indication is given. For example, the TCI field being 2 ("10") may be that the third indication is given. For example, the TCI field being 3 ("11") may be that the fourth indication is given.
[0416] The upper layer parameters for the PDCCH 1403 may provide any of a first indication, a second indication, a third indication, and a fourth indication. For example, if the upper layer parameters for the PDCCH 1403 indicate 0 ("00"), the first indication may be executed. For example, if the upper layer parameters for the PDCCH 1403 indicate 1 ("01"), the second indication may be executed. For example, if the upper layer parameters for the PDCCH 1403 indicate 2 ("10"), the third indication may be executed. For example, if the upper layer parameters for the PDCCH 1403 indicate 3 ("11"), the fourth indication may be executed. For example, the upper layer parameters for the PDCCH 1403 being 0 ("00") may be that the first indication is given. For example, the upper layer parameters for the PDCCH 1403 being 1 ("01") may be that the second indication is given. For example, the upper layer parameters for the PDCCH 1403 being 2 ("10") may be that the third indication is given. For example, a fourth indication may be given that the higher layer parameter for PDCCH 1403 is 3 ("11").
[0417] 15 is a diagram showing an example of timeline management of a TCI state according to one aspect of the present embodiment. The terminal device 1 may receive a PDCCH 1500. The terminal device 1 may receive a PDCCH 1500 in which a DCI 1590 is arranged. The DCI 1590 in the PDCCH 1500 may include one or both of a TCI field and a TRP indication field. The DCI 1590 may schedule a PDSCH 1501. The DCI 1590 may instruct reception of the PDSCH 1501. The DCI 1590 may instruct transmission of the PDSCH 1501.
[0418] The terminal device 1 may receive the PDSCH 1501. The terminal device 1 may receive the PDSCH 1501 after a time offset 1520 from the last OFDM symbol of the PDCCH 1500. The time offset 1520 may be a time offset between the reception of the DL DCI (DCI 1590) and the PDSCH 1501. The DL DCI may be placed in the PDCCH 1500. The PDSCH 1501 may correspond to the DL DCI (DCI 1590). The time offset 1520 may be a time offset between the last OFDM symbol of the PDCCH 1500 and the first OFDM symbol of the PDSCH 1501. The time offset may be expressed in number of OFDM symbols. The time offset may be expressed in milliseconds. The time offset may be expressed in number of slots. The time offset may be a time offset between the reception of the DL DCI and the corresponding PDSCH.
[0419] The time offset 1520 may be equal to or greater than the threshold 1510. The threshold 1510 may be a time for the “indicated TCI state” 1581 to be applied. For example, the threshold 1510 may be a time for the “indicated TCI state” 1581 to be applied for multiple channels including the PDSCH 1501. The threshold 1510 may be used to determine a TCI state or QCL assumption for the PDSCH 1501. The threshold 1510 may be used to determine an antenna port QCL for the PDSCH 1501. The threshold 1510 may be set by a higher layer parameter. The threshold 1510 may be determined based on the terminal capability. The threshold 1510 may be BeamAppTime. The threshold 1510 may be timeDurationForQCL. The threshold 1510 may not be expected to be less than the threshold 1511.
[0420] The time offset 1520 may be equal to or greater than the threshold 1511. The threshold 1511 may be a time for the “applied TCI state” 1570 to be applied. For example, the threshold 1511 may be a time for one or two “indicated TCI states” 1570 to be applied for the PDSCH 1501. The threshold 1511 may be used to determine a TCI state or QCL assumption for the PDSCH 1501. The threshold 1511 may be used to determine a TCI state or QCL assumption for the PDSCH 1501. The threshold 1511 may be used to determine an antenna port QCL for the PDSCH 1501. The threshold 1511 may be set by a higher layer parameter. The threshold 1511 may be determined based on the terminal capability. The threshold 1511 may be BeamAppTime. The threshold 1511 may be BeamAppTime-r18. The threshold 1511 may be timeDurationForQCL. The threshold 1511 may be the same as the threshold 1510 or may be smaller than the threshold 1510 .
[0421] If the time offset 1520 is greater than or equal to the threshold 1510 or 1511, some or all of the “indicated TCI states” 1581 may be applied to the PDSCH 1501. Some or all of the “indicated TCI states” 1581 applied to the PDSCH 1501 may be “applied TCI states” 1570. For example, the DCI 1590 may indicate one or more “indicated TCI states” 1581. For example, the DCI 1590 may determine one or two “applied TCI states” 1570 from one or more “indicated TCI states” 1581 for the PDSCH 1501.
[0422] The DCI 1590 may indicate one or more "indicated TCI states" 1581. For example, a TCI field in the DCI 1590 may indicate one or more "indicated TCI states" 1581. Some or all of the one or more "indicated TCI states" 1581 may apply to the PDSCH 1501 if the time offset 1520 is greater than or equal to the threshold 1510.
[0423] The DCI 1590 may indicate one or two "applied TCI states" 1570. For example, the TRP indication field in the DCI 1590 may be used to determine one or two "applied TCI states" 1570. For example, the TRP indication field in the DCI 1590 may be used to determine one or two "applied TCI states" 1570 for the PDSCH 1501. If the time offset 1520 is greater than or equal to the threshold 1511, the "applied TCI state" 1570 may be applied to the PDSCH 1501.
[0424] If the one or more TCI states 1581 are different from some or all of the one or more TCI states 1580 and if the time offset 1520 is greater than or equal to the threshold 1510, then one or two TCI states 1570 may be applied to the PDSCH 1501. The one or more TCI states 1581 may be indicated by the DCI 1590. For example, the one or more TCI states 1581 may be indicated by a TCI field in the DCI 1590. The one or two TCI states 1570 may be some or all of the one or more TCI states 1581. The one or two TCI states 1570 may be indicated by the DCI 1590. For example, the one or two TCI states 1570 may be indicated by a TRP indication field in the DCI 1590. The TCI state 1580 may be indicated before (before) the TCI state 1581. That is, TCI status 1580 may be older information than TCI status 1581. That is, TCI status 1580 may be indicated before TCI status 1581 is indicated.
[0425] If one or more TCI states 1581 are the same as one or more TCI states 1580 and if the time offset 1520 is greater than or equal to the threshold 1511 , then one or two TCI states 1570 may be applied to the PDSCH 1501 .
[0426] If one or more TCI states 1581 are different from some or all of one or more TCI states 1580, and if the time offset 1520 is greater than or equal to the threshold 1511, and if the time offset 1520 is less than the threshold 1510, then some or all of actions a, b, c, d, e, f, g, h, and i may be performed. Action a may be that one or two TCI conditions 1570 and one or more TCI conditions 1581 do not apply to the PDSCH 1501 . Action b may be that some or all of one or more TCI conditions 1580 are applied to the PDSCH 1501 . Action c may be to apply some or all of the one or more TCI states 1580 to the PDSCH 1501 based on higher layer parameters. The higher layer parameters may be used to determine the “applied TCI state”. Action d may be to apply some or all of the one or more TCI states 1580 to the PDSCH 1501 based on a PDSCH-MTRP technique. The PDSCH-MTRP technique may be some or all of an SFN technique, an FDM technique, a TDM technique, and an SDM technique. Action e may be that the TCI state applied to the PDCCH 1500 or to a CORESET of the PDCCH 1500 is applied to the PDSCH 1501 . Action f may be that the TCI state applied to a CORESET with the lowest CORESET ID among one or more CORESETs in one BWP associated with the PDCCH 1500 is applied to the PDSCH 1501 . Action g may be that two of the multiple “set TCI states” are applied to the PDSCH 1501 . The operation may be that one or two of one or more TCI states 1580 are applied to the PDSCH 1501 based on a DCI. The DCI may be received before the DCI 1590. The DCI may determine the “applied TCI state”. The DCI may indicate a TCI state for a PDSCH different from the PDSCH 1501. The DCI may be a DCI that indicates the TCI state 1580. Action i may be that some or all of one or more TCI conditions 1580 are applied to the PDSCH 1501 based on the DCI 1590 or a TRP indication field in the DCI 1590.
[0427] If the time offset 1520 is less than the threshold 1511, some or all of actions a, b, c, d, e, f, g, and h may be performed. If the time offset 1520 is less than the threshold 1511, action i may not be performed.
[0428] The terminal device 1 may receive the PDCCH 1404. The terminal device 1 may receive the PDCCH 1404 in which the DCI 1591 is arranged. The time interval 1530 may be a time between the PDCCH 1500 and the PDCCH 1404. For example, the time interval 1530 may be a time from the last OFDM symbol of the PDCCH 1500 to the first OFDM symbol of the PDCCH 1404. For example, the time interval 1530 may be represented in OFDM symbols.
[0429] If the time interval 1530 is greater than or equal to the threshold 1510, some or all of the one or more TCI states 1581 may be applied to the PDCCH 1404. If the time interval 1530 is greater than or equal to the threshold 1510, some or all of the one or more TCI states 1581 may be applied to the PDCCH 1404 based on higher layer parameters. If the time interval 1530 is less than the threshold 1510, some or all of the one or more TCI states 1580 may be applied to the PDCCH 1404. If the time interval 1530 is less than the threshold 1510, some or all of the one or more TCI states 1580 may be applied to the PDCCH 1404 based on higher layer parameters. The higher layer parameters may be used to determine the “applied TCI state” for the PDCCH.
[0430] The terminal device 1 may receive the PDSCH 1403. The DCI 1591 may schedule the PDSCH 1403. The DCI 1591 may indicate reception or transmission of the PDSCH 1403. The DCI 1591 may include a TCI field. The DCI 1591 may include a TRP indication field. The DCI 1591 may include a PUCCH resource indication field. The time offset 1522 may be a time between the PDCCH 1404 and the PDSCH 1403. For example, the time offset 1522 may be a time from the last OFDM symbol of the PDCCH 1404 to the first OFDM symbol of the PDSCH 1403. The time offset 1522 may be expressed in OFDM symbols.
[0431] The threshold 1512 may be a time for the “indicated TCI state” 1582 to be applied. For example, the threshold 1512 may be a time for the “indicated TCI state” 1582 to be applied for multiple channels including the PDSCH 1403. The threshold 1512 may be used to determine a TCI state or QCL assumption for the PDSCH 1403. The threshold 1511 may be used to determine an antenna port QCL for the PDSCH 1403. The threshold 1512 may be set by a higher layer parameter. The threshold 1512 may be determined based on the terminal capability. The threshold 1512 may be the same as the threshold 1510. The threshold 1512 may be BeamAppTime. The threshold 1512 may be timeDurationForQCL. The threshold 1512 may not be expected to be smaller than the threshold 1511.
[0432] The threshold 1513 may be a time for the "applied TCI state" 1571 to be applied. For example, the threshold 1513 may be a time for one or two "indicated TCI states" 1571 to be applied for the PDSCH 1403. The threshold 1513 may be used to determine a TCI state or QCL assumption for the PDSCH 1403. The threshold 1513 may be used to determine a TCI state or QCL assumption for the PDSCH 1403. The threshold 1513 may be used to determine an antenna port QCL for the PDSCH 1403. The threshold 1513 may be set by a higher layer parameter. The threshold 1513 may be determined based on the terminal capability. The threshold 1513 may be BeamAppTime. The threshold 1513 may be BeamAppTime-r18. The threshold 1513 may be timeDurationForQCL. The threshold 1513 may be the same as the threshold 1512 or less than the threshold 1510. The threshold 1513 may be the threshold 1511 .
[0433] If the time offset 1521 is greater than or equal to the threshold 1512 or the threshold 1513, some or all of the “indicated TCI states” 1582 may be applied to the PDSCH 1403. Some or all of the TCI states 1581 applied to the PDSCH 1403 may be the “applied TCI states” 1571. For example, the DCI 1591 may indicate one or more “indicated TCI states” 1582. For example, the DCI 1591 may determine one or two “applied TCI states” 1571 from one or more “indicated TCI states” 1582 for the PDSCH 1403.
[0434] The DCI 1591 may indicate one or more "indicated TCI states" 1582. For example, the TCI field in the DCI 1591 may indicate one or more "indicated TCI states" 1582. If the time offset 1521 is greater than or equal to the threshold 1512, some or all of the one or more "indicated TCI states" 1582 may apply to the PDSCH 1403.
[0435] The DCI 1590 may indicate one or two "applied TCI states" 1570. For example, the TRP indication field in the DCI 1590 may be used to determine one or two "applied TCI states" 1570. For example, the TRP indication field in the DCI 1590 may be used to determine one or two "applied TCI states" 1570 for the PDSCH 1501. If the time offset 1520 is greater than or equal to the threshold 1511, the "applied TCI state" 1570 may be applied to the PDSCH 1501.
[0436] If the one or more TCI states 1582 are different from some or all of the one or more TCI states 1581 and if the time offset 1521 is greater than or equal to the threshold 1512, then one or two TCI states 1571 may be applied to the PDSCH 1403. The one or more TCI states 1582 may be indicated by the DCI 1591. For example, the one or more TCI states 1582 may be indicated by a TCI field in the DCI 1591. The one or two TCI states 1571 may be some or all of the one or more TCI states 1582. The one or two TCI states 1571 may be indicated by the DCI 1591. For example, the one or two TCI states 1571 may be indicated by a TRP indication field in the DCI 1591.
[0437] If one or more TCI states 1582 are the same as one or more TCI states 1581 and if the time offset 1521 is greater than or equal to the threshold 1512 , then one or two TCI states 1571 may be applied to the PDSCH 1403 .
[0438] If one or more TCI states 1582 are different from some or all of one or more TCI states 1581, and if the time offset 1521 is greater than or equal to the threshold 1513, and if the time offset 1521 is less than the threshold 1512, then some or all of actions aa, bb, cc, dd, ee, ff, gg, hh, and ii may be performed. Action aa may be that one or two TCI conditions 1571 and one or more TCI conditions 1582 do not apply to the PDSCH 1403 . Action bb may be that some or all of one or more TCI conditions 1581 are applied to the PDSCH 1403 . The action cc may be that some or all of the one or more TCI states 1581 are applied to the PDSCH 1403 based on higher layer parameters. The higher layer parameters may be used to determine the “applied TCI state”. The action dd may be that some or all of the one or more TCI states 1581 are applied to the PDSCH 1403 based on a PDSCH-MTRP scheme. The PDSCH-MTRP scheme may be some or all of an SFN scheme, an FDM scheme, a TDM scheme, and an SDM scheme. The action ee may be that the TCI state applied to the PDCCH 1404 or to the CORESET of the PDCCH 1404 is applied to the PDSCH 1403. Action ff may be that the TCI state applied to the CORESET with the lowest CORESET ID among one or more CORESETs in one BWP associated with the PDCCH 1404 is applied to the PDSCH 1403. Action gg may be that two of the multiple “set TCI states” are applied to the PDSCH 1403 . Action hh may be that one or two of one or more TCI states 1581 are applied to the PDSCH 1403 based on the DCI 1590 . Action ii may be that some or all of one or more TCI conditions 1581 are applied to the PDSCH 1403 based on the DCI 1591 or a TRP indication field in the DCI 1591.
[0439] If the time offset 1521 is less than the threshold 1513, some or all of actions aa, bb, cc, dd, ee, ff, gg, and hh may be performed. If the time offset 1521 is less than the threshold 1513, action ii may not be performed.
[0440] Applying one or more TCI states to a physical channel may be that a DMRS port (DMRS antenna port) of the physical channel is DL-RS and QCL in one or more TCI states. Applying one or more TCI states to a PDCCH may be that one or more TCI states are applied to a CORESET for the PDCCH. Applying one or more TCI states to a physical channel may be that an uplink transmit spatial filter of the physical channel is determined based on the one or more TCI states.
[0441] The terminal device 1 may transmit a PUCCH 1502. The terminal device 1 may transmit a PUCCH 1502 in which uplink control information for a PDSCH 1403 is arranged. The terminal device 1 may provide (transmit) HARQ-ACK information in the PUCCH 1502. The terminal device 1 may provide (transmit) HARQ-ACK information in the PUSCCH 1502 in response to detection of a DCI 1404 that schedules the PDSCH 1403.
[0442] The time offset 1522 may be the time between the PDCCH 1404 and the PUCCH 1502. For example, the time offset 1522 may be the time from the last OFDM symbol of the PDCCH 1404 to the first OFDM symbol of the PUCCH 1502.
[0443] If the time offset 1522 is greater than or equal to the threshold 1512, some or all of the one or more TCI states 1582 may be applied to the PUCCH 1502. For example, if the time offset 1522 is greater than or equal to the threshold 1512, some or all of the one or more TCI states 1582 may be applied to the PUCCH 1502 based on higher layer parameters. The higher layer parameters may be configured for one PUCCH resource. The one PUCCH resource may be indicated by the DCI 1591. The one PUCCH resource may be indicated by a PUCCH resource indication field in the DCI 1591. The higher layer parameters may be used to determine an “applied TCI state” for the PUCCH 1502.
[0444] If the time offset 1522 is greater than or equal to the threshold 1512 and if the time offset 1521 is less than the threshold 1513 , then one or more TCI conditions applied to the PDSCH 1403 may be applied to the PUCCH 1502 .
[0445] If the time offset 1522 is less than the threshold 1512 , some or all of the one or more TCI states 1581 may be applied to the PUCCH 1502 .
[0446] 16 is a diagram showing a second example of timeline management of a TCI state according to one aspect of the present embodiment. The terminal device 1 may receive a PDCCH 1600. The terminal device 1 may receive a PDCCH 1600 in which a DCI 1690 is arranged. The DCI 1690 in the PDCCH 1600 may include a TRP indication field. The DCI 1690 may schedule a PUSCH 1601. The DCI 1690 may instruct reception of the PUSCH 1601. The DCI 1690 may instruct transmission of the PUSCH 1601.
[0447] The terminal device 1 may transmit the PUSCH 1601. The terminal device 1 may transmit the PUSCH 1601 after a time offset 1621 from the last OFDM symbol of the PDCCH 1600. The time offset 1621 may be a time offset between the reception of the UL DCI (DCI 1690) and the PUSCH 1601. The UL DCI may be placed in the PDCCH 1600. The PUSCH 1601 may correspond to the UL DCI (DCI 1690). The time offset 1621 may be a time offset between the last OFDM symbol of the PDCCH 1600 and the first OFDM symbol of the PUSCH 1601. The time offset 1620 may be a time offset between the reception of the DCI 1591 and the PUSCH 1601. The time offset 1620 may be a time offset between the last OFDM symbol of the PDCCH 1404 and the first OFDM symbol of the PUSCH 1601. The time offset may be expressed in number of OFDM symbols. The time offset may be expressed in milliseconds. The time offset may be expressed in number of slots. The time offset may be the time offset between reception of the UL DCI and the corresponding PUSCH.
[0448] The threshold 1610 does not have to be the time for which the “indicated TCI state” applies. For example, the time for which the “indicated TCI state” 1581 applies for multiple channels including the PUSCH 1601 may be the threshold 1512.
[0449] The threshold 1610 may be a time for the “applied TCI state” 1670 to be applied. For example, the threshold 1610 may be a time for one or two “indicated TCI states” 1670 to be applied for the PUSCH 1601. The threshold 1610 may be used to determine a TCI state or QCL assumption for the PUSCH 1601. The threshold 1610 may be used to determine a TCI state or QCL assumption for the PUSCH 1601. The threshold 1610 may be used to determine an antenna port QCL for the PUSCH 1601. The threshold 1610 may be used to determine an uplink transmit spatial filter for the PUSCH 1601. The threshold 1610 may be set by a higher layer parameter. The threshold 1610 may be determined based on the terminal capability. The threshold 1610 may be BeamAppTime. The threshold 1610 may be BeamAppTime-r18. The threshold value 1610 may be the timeDurationForQCL. The threshold value 1610 may be the threshold value 1513.
[0450] If the time offset 1621 is greater than or equal to the threshold 1610, some or all of the “indicated TCI states” 1582 may be applied to the PUSCH 1601. Some or all of the “indicated TCI states” 1582 applied to the PUSCH 1601 may be “applied TCI states” 1670. For example, the DCI 1690 may determine one or two “applied TCI states” 1670 for the PUSCH 1601 from one or more “indicated TCI states” 1582.
[0451] The DCI 1690 may indicate one or two “applied TCI states” 1670. For example, the TRP indication field in the DCI 1690 may be used to determine one or two “applied TCI states” 1670. For example, the TRP indication field in the DCI 1690 may be used to determine one or two “applied TCI states” 1670 for the PUSCH 1601. If the time offset 1621 is greater than or equal to the threshold 1610, the “applied TCI state” 1670 may be applied to the PUSCH 1601.
[0452] The time offset 1620 may be greater than or equal to the threshold 1512. If the time offset 1621 is greater than or equal to the threshold 1610, then one or two TCI states 1670 may be applied to the PUSCH 1601. The one or two TCI states 1670 may be part or all of the one or more TCI states 1582. The one or two TCI states 1670 may be indicated by the DCI 1690. For example, the one or two TCI states 1670 may be indicated by a TRP indication field in the DCI 1690.
[0453] The time offset 1620 may be greater than or equal to the threshold 1512. If the time offset 1621 is less than the threshold 1610, some or all of actions aaa, bbb, ccc, ddd, eee, fff, ggg, hhh, and iii may be performed. Action aaa may be that one or two TCI states 1670 do not apply to the PUSCH 1601. Action bbb may be that some or all of one or more TCI conditions 1582 are applied to the PUSCH 1601. Action ccc may be that some or all of one or more TCI states 1582 are applied to the PUSCH 1601 based on higher layer parameters. The higher layer parameters may be used to determine the “applied TCI state.” Action ddd may be that all of one or more TCI states 1582 are applied to the PUSCH 1601. Action eee may be that the TCI state applied to the PUCCH 1502 is applied to the PUSCH 1601 . Action fff may be that two of the multiple “set TCI states” are applied to the PUSCH 1601 . Action ggg may be that some or all of one or more TCI states 1582 are applied to the PUSCH 1601 based on the DCI 1404 or a PUCCH resource indication field in the DCI 1404. A DCI may be received before the DCI 1590. A DCI may determine the “applied TCI state”. A DCI may indicate a TCI state for a PDSCH different from the PDSCH 1501. A DCI may be a DCI indicating the TCI state 1580. Operation hhh may be to determine an uplink transmit spatial filter for the PUSCH 1601 based on the SRS resource indication field in the DCI 1690.
[0454] The terminal device 1 may receive a first PDCCH in which a first DCI is arranged. The terminal device 1 may receive a first PDSCH scheduled by the first DCI. The terminal device 1 may receive a second PDCCH in which a second DCI is arranged. The terminal device 1 may receive a second PDSCH scheduled by the second DCI. The terminal device 1 may transmit a PUCCH in which uplink control information for the second PDSCH is arranged. The uplink control information may be HARQ-ACK (HARQ-ACK information). The terminal device 1 may perform transmission and reception in the following order: reception of the first PDCCH, reception of the first PDSCH, reception of the second PDCCH, reception of the second PDSCH, and transmission of the PUCCH.
[0455] The one or more first beam information may be indicated by the first DCI. For example, the one or more first beam information may be indicated by a TCI field in the first DCI. The one or two second beam information may be indicated by the first DCI. For example, the one or two second beam information may be indicated by a TRP indication field in the first DCI. For example, the one or two second beam information may be selected by the first DCI from the one or more first beam information. The first beam information may be a "TCI state to be indicated". The second beam information may be a "TCI state to be applied". For example, the beam information may be a TCI state. For example, the one or two second beam information may be a part or all of the one or more first beam information.
[0456] The one or more third beam information may be indicated by the second DCI. For example, the one or more third beam information may be indicated by a TCI field in the second DCI. The one or two fourth beam information may be indicated by the second DCI. For example, the one or two fourth beam information may be indicated by a TRP indication field in the second DCI. For example, the one or two fourth beam information may be selected by the second DCI from the one or more third beam information. The third beam information may be a "TCI state to be indicated". The fourth beam information may be a "TCI state to be applied". For example, the one or two fourth beam information may be a part or all of the one or more third beam information.
[0457] The first time (time offset) may be a time between reception of the first PDCCH or the first DCI and reception of the first PDSCH. For example, the first time may be a time from the last OFDM symbol of the first PDCCH to the first OFDM symbol of the first PDSCH. The second time (threshold) may be a time for application of the first beam information. The third time (threshold) may be a time for application of the second beam information.
[0458] The fourth time (time offset) may be a time between the reception of the second PDCCH or the second DCI and the reception of the second PDSCH. For example, the fourth time may be a time from the last OFDM symbol of the second PDCCH to the first OFDM symbol of the second PDSCH. The fifth time (threshold) may be a time for application of the third beam information. The sixth time (threshold) may be a time for application of the fourth beam information.
[0459] A time from the last OFDM symbol of the first PDCCH to the first OFDM symbol of the second PDSCH may be equal to or greater than the second time. A time between the first PDCCH and the second PDSCH may be equal to or greater than the second time.
[0460] The first time may be equal to or greater than the second time. The first time may be equal to or greater than the third time. That is, one or two pieces of second beam information may be applied to the first PDSCH.
[0461] When the fourth time is equal to or longer than the fifth time, one or two pieces of fourth beam information may be applied to the second PDSCH. Also, when the fourth time is equal to or longer than the sixth time, one or two pieces of fourth beam information may be applied to the second PDSCH.
[0462] If the fourth time is shorter than the fifth time, a part or all of the one or more first beam information may be applied to the second PDSCH. For example, if the fourth time is shorter than the fifth time and the fourth time is equal to or longer than the sixth time, a part or all of the one or more first beam information may be applied to the second PDSCH based on the second DCI or the TRP indication field in the second DCI. For example, if the third beam information is the same as the first beam information, and the fourth time is shorter than the fifth time, and the fourth time is equal to or longer than the sixth time, a part or all of the one or more first beam information may be applied to the second PDSCH based on the second DCI. For example, if the third beam information is the same as the first beam information, and the fourth time is shorter than the fifth time, and the fourth time is equal to or longer than the sixth time, a part or all of the one or more first beam information may be applied to the second PDSCH based on the TRP indication field in the second DCI.
[0463] If the fourth time is shorter than the sixth time, a part or all of the one or more pieces of first beam information may be applied to the second PDSCH. For example, in this case, one or two pieces of second beam information may be applied to the second PDSCH. For example, in this case, a part or all of the one or more pieces of first beam information may be applied to the second PDSCH based on a higher layer parameter. For example, in this case, a part or all of the one or more pieces of first beam information may be applied to the second PDSCH based on the second PDCCH or a CORESET for the second PDCCH. For example, in this case, a part or all of the one or more pieces of first beam information may be applied to the second PDSCH based on whether the PDSCH-MTRP method is applied. For example, in this case, the beam information applied to the second PDSCH may be determined based on the SS / PBCH block. The terminal device 1 may receive the SS / PBCH block before the first PDCCH. For example, the terminal device 1 may not expect this case. The higher layer parameter may be used to determine the "applied TCI state" of the PDSCH.
[0464] If the fourth time period is shorter than the sixth time period, one or two beam information applied to the second PDCCH or the CORESET for the second PDCCH may be applied to the second PDSCH.
[0465] The number of beam information to be applied to the second PDSCH may be given by any of the first indication, the second indication, the third indication, and the fourth indication. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the second PDSCH may be given by DCI. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the second PDSCH may be given by higher layer parameters. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the second PDSCH may be given depending on whether the PDSCH-MTRP method is applied to the second PDSCH. For example, the application of the PDSCH-MTRP method for the second PDSCH may mean that one or both of the third indication and the fourth indication are given for the second PDSCH. For example, the non-application of the PDSCH-MTRP method for the second PDSCH may mean that one of the first indication and the second indication is given for the second PDSCH. Giving either the first instruction or the second instruction may mean that one beam information is applied, and giving either the third instruction or the fourth instruction may mean that two beam information is applied.
[0466] The terminal device 1 may receive a third PDCCH in which a third DCI is arranged. The terminal device 1 may transmit a first PUSCH scheduled by the third DCI. The terminal device 1 may perform transmission and reception in the following order: reception of the first PDCCH, reception of the first PDSCH, reception of the second PDCCH, reception of the second PDSCH, transmission of the PUCCH, reception of the third PDCCH, and transmission of the first PUSCH.
[0467] The one or more fifth beam information may be indicated by the third DCI. For example, the one or more fifth beam information may be indicated by a TRP indication field in the third DCI. For example, the one or more fifth beam information may be indicated by an SRS resource indication field in the third DCI. For example, the one or more fifth beam information may be a part or all of the one or more third beam information. The TRP indication field in the third DCI may be an SRS resource set indication field. Applying the beam information to the PUSCH may be determining an uplink transmit spatial filter for the PUSCH.
[0468] The seventh time (time offset) may be a time between the reception of the third PDCCH or the third DCI and the transmission of the first PUSCH. For example, the seventh time may be a time from the last OFDM symbol of the third PDCCH to the first OFDM symbol of the first PUSCH. The eighth time (threshold) may be a time for application of the fifth beam information.
[0469] The time from the last OFDM symbol of the second PDCCH to the first OFDM symbol of the first PUSCH may be equal to or longer than the fifth time. The time between the second PDCCH and the first PUSCH may be equal to or longer than the fifth time.
[0470] If the seventh time is the same as or longer than the eighth time, one or more pieces of fifth beam information may be applied to the first PUSCH.
[0471] If the seventh time is shorter than the eighth time, one or more sixth beam information may be applied to the first PUSCH. Or, the terminal device 1 may not expect the seventh time to be shorter than the eighth time. The one or more sixth beam information may be different from a part or all of the one or more fifth beam information. The one or more sixth beam information may be a part or all of the one or more third beam information.
[0472] The one or more sixth beam information may be beam information applied to the first PUCCH. The one or more sixth beam information may be determined based on a higher layer parameter. The higher layer parameter may be used to determine an “applied TCI state” of the PUSCH. The one or more sixth beam information may be beam information applied to the third PDCCH or a CORESET for the third PDCCH. The one or more sixth beam information may be determined by an SRS resource indication field in the third DCI. The one or more sixth beam information may be determined based on whether a PUSCH-MTRP scheme is applied for the first PUSCH. The one or more sixth beam information may be determined at least based on whether the third beam information is in a Joint TCI state. For example, if the third beam information is in a Joint TCI state, the one or more sixth beam information may be indicated by a second DCI or a TRP indication field in the second DCI. The sixth beam information applied to the first PUSCH may be one of the one or more third beam information. The one or more sixth beam information may be determined based on the message 3 PUSCH. The one or more sixth beam information may be applied to the second PUSCH. For example, the second PUSCH may be a latest PUSCH among the one or more PUSCHs transmitted before the first PUSCH.
[0473] The number of beam information applied to the first PUSCH may be given by any of the first indication, the second indication, the third indication, and the fourth indication. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the first PUSCH may be given by DCI. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the first PUSCH may be given by higher layer parameters. For example, some or all of the first indication, the second indication, the third indication, and the fourth indication for the first PUSCH may be given depending on whether the PUSCH-MTRP method is applied to the first PDSCH. For example, the application of the PUSCH-MTRP method for the first PUSCH may mean that one or both of the third indication and the fourth indication are given for the first PUSCH. For example, the non-application of the PUSCH-MTRP method for the first PUSCH may mean that one of the first indication and the second indication is given for the first PUSCH. Giving either the first instruction or the second instruction may mean that one beam information is applied, and giving either the third instruction or the fourth instruction may mean that two beam information is applied.
[0474] Various aspects of the device according to one aspect of this embodiment will be described below.
[0475] The programs operating in the base station device 3 and terminal device 1 according to the present invention may be programs (programs that make a computer function) that control a CPU (Central Processing Unit) or the like so as to realize the functions of the above-mentioned embodiments according to the present invention. Information handled by these devices is temporarily stored in a RAM (Random Access Memory) during processing, and is then stored in various ROMs such as a Flash ROM (Read Only Memory) or an HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.
[0476] In addition, a part of the terminal device 1 and the base station device 3 in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to realize the control function.
[0477] The "computer system" 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 "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.
[0478] 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, and a medium that stores a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such a case. The above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.
[0479] Furthermore, the base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) consisting of a plurality of 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 an aggregate.
[0480] In addition, the base station device 3 in the above-mentioned embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). In addition, the base station device 3 in the above-mentioned embodiment may have a part or all of the functions of an upper node for an eNodeB and / or a gNB.
[0481] In addition, some or all of the terminal device 1 and base station device 3 in the above-mentioned embodiment may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that replaces LSI appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.
[0482] In addition, in the above-described embodiment, a terminal device is described as an example of a communication device, but the present invention is not limited to this and can also be applied to terminal devices or communication devices such as stationary or non-movable electronic devices installed indoors or outdoors, for example, AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
[0483] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways 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 replaced with elements that have the same effect are also included. [Explanation of symbols]
[0484] 1(1A, 1B, 1C) Terminal equipment 3 Base station equipment 10, 30 Radio transmitter / receiver 10a, 30a Radio transmitter 10b, 30b Wireless receiver 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component Carriers 301 Primary Cell 302, 303 Secondary Cell A set of resource elements for 700 PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of Resource Elements for SSS 3000 points 3001, 3002 Resource Grid 3003, 3004 BWP 3011, 3012, 3013, 3014 offset 3100, 3200 common resource block set 1400 TCI state to be set 1401 Activated TCI state 1402 TCI status indicated 1403, 1501 PDSCH 1404, 1500, 1600 PDCCH 1590, 1591, 1690 DCI 1450, 1451 TCI status 1460, 1461 Applicable TCI conditions 1502 PUCCH 1510, 1511, 1512, 1513, 1610 Threshold (hours) 1520, 1521, 1522, 1620, 1621 time offsets 1530 Time Interval 1570, 1571, 1670 Applicable TCI Conditions 1580, 1581, 1582 TCI status indicated 1601 PUSCH
Claims
1. A receiver that receives a PDCCH (Physical Downlink Control Channel) on which DCI (Downlink Control Information) is arranged and a PDSCH (Physical Downlink Shared Channel) scheduled by the DCI; a transmitter that transmits a PUCCH (Physical Uplink Control Channel) in which uplink control information for the PDSCH is arranged, one or more first Transmission Configuration Indication (TCI) states are indicated by the DCI; one or two second TCI states are selected by the DCI from the one or more first TCI states; The time offset is the time between the PDCCH and the PDSCH, The period is determined based on the device capabilities, If the time offset is equal to or longer than the certain period, one or two of the second TCI states are applied to the PDSCH; If the time offset is less than the certain period, one of the one or more first TCI states is applied to the PDSCH. Terminal device.
2. A transmitter that transmits a PDCCH (Physical Downlink Control Channel) on which DCI (Downlink Control Information) is arranged and a PDSCH (Physical Downlink Shared Channel) scheduled by the DCI; a receiving unit that receives a PUCCH (Physical Uplink Control Channel) in which uplink control information for the PDSCH is arranged, one or more first Transmission Configuration Indication (TCI) states are indicated by the DCI; one or two second TCI states are selected by the DCI from the one or more first TCI states; The time offset is the time between the PDCCH and the PDSCH, The period is determined based on the device capabilities, If the time offset is equal to or longer than the certain period, one or two of the second TCI states are applied to the PDSCH; If the time offset is less than the certain period, one of the one or more first TCI states is applied to the PDSCH. Base station equipment.
3. A communication method for a terminal device, comprising: receiving a PDCCH (Physical Downlink Control Channel) on which DCI (Downlink Control Information) is arranged and a PDSCH (Physical Downlink Shared Channel) scheduled by the DCI; transmitting a PUCCH (Physical Uplink Control Channel) in which uplink control information for the PDSCH is arranged; and one or more first Transmission Configuration Indication (TCI) states are indicated by the DCI; one or two second TCI states are selected by the DCI from the one or more first TCI states; The time offset is the time between the PDCCH and the PDSCH, The period is determined based on the device capabilities, If the time offset is equal to or longer than the certain period, one or two of the second TCI states are applied to the PDSCH; If the time offset is less than the certain period, one of the one or more first TCI states is applied to the PDSCH. Communication method.