Terminal equipment and base station equipment

Abstract

To provide terminal equipment and base station equipment that enable efficient communication. [Solution] In a wireless communication system, the terminal device comprises a receiving unit that receives a first PDCCH where a first DCI is located, a second PDCCH where a second DCI is located, and a PDSCH scheduled by the first DCI, and a transmitting unit that transmits an uplink channel scheduled by the second DCI. The first beam information indicated by the TCI field in the first DCI is applied for the uplink channel, the first PDCCH and the second PDCCH are associated with a first CORESET pool index, the first uplink timing for the uplink channel is determined by a first TAG ID, the first TAG ID is determined based on the TCI field, and the code points in the TCI field correspond to one or both of the first TAG ID and the second TAG ID.

Description

[Technical Field]

[0001] This invention relates to terminal equipment and base station equipment. [Background technology]

[0002] The cellular mobile communication radio access method and radio network (hereinafter also referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is part of the Third Generation Partnership Project (3GPP:3 rd This is being considered in the Generation Partnership Project. In LTE, base station equipment is also called eNodeB (evolved NodeB), and terminal equipment is also called UE (User Equipment). LTE is a cellular communication system in which multiple base station devices are arranged in a cell-like structure to cover different areas. A single base station device may manage multiple serving cells.

[0003] 3GPP is considering a next-generation standard (NR: New Radio) to propose to the International Mobile Telecommunication Union (ITU) for next-generation mobile communication systems, IMT-2020 (Non-Patent Literature 1). NR is a single technological framework that utilizes eMBB (enhanced Mobile Broadband) It is required to meet the requirements for three scenarios: ), mMTC (massive machine type communication), and URLLC (ultra-reliable and low-latency communication). .

[0004] 3GPP is considering expanding the services supported by NR (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 [Overview of the project] [Problems that the invention aims to solve]

[0006] The present invention provides a terminal device for efficient communication, a communication method used in the terminal device, a base station device for 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 first PDCCH on which a first DCI is located, a second PDCCH on which a second DCI is located, and a first DCI scheduled by the first DCI The system comprises a PDSCH that receives and a receiving unit that receives and a transmitting unit that transmits the uplink channel scheduled by the second DCI, wherein the first beam information is transmitted to the first DCI. Indicated by the TCI field, the first beam information is directed to the uplink channel Applied for the purpose of the first PDCCH and the second PDCCH, the first CORESET pool In relation to the DEX, the first uplink timing for the uplink channel is determined by the first TAG ID, which is determined based on the TCI field. The code point of the TCI field is one of the first TAG ID and the second TAG ID. Or it can support both.

[0008] (2) A second aspect of the present invention is a base station device in which the first DCI is located The system comprises a transmitting unit that transmits a first PDCCH, a second PDCCH in which a second DCI is located, and a PDSCH scheduled by the first DCI, and a receiving unit that receives an uplink channel scheduled by the second DCI, wherein the first beam information is indicated by the TCI field in the first DCI, the first beam information is applied for the uplink channel, and the first PDCCH and the second PDCCH are connected to the first CORESET pool In relation to the index, the first uplink timing for the uplink channel is determined by the first TAG ID, which is based on the TCI field. The code point of the TCI field is determined to be the first TAG ID and the second TAG ID It corresponds to one or both of the above. [Effects of the Invention]

[0009] According to this invention, terminal devices can communicate efficiently. Furthermore, base station devices can communicate efficiently. [Brief explanation of the drawing]

[0010] [Figure 1] This is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. [Figure 2] This is an example showing the relationship between the subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and the CP (cyclic prefix) setting according to one aspect of this embodiment. [Figure 3] This figure shows an example of a method for configuring a resource grid according to one aspect of this embodiment. [Figure 4] This figure shows an example configuration of a resource grid 3001 according to one aspect of this embodiment. [Figure 5] This is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of this embodiment. [Figure 6] This is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one aspect of this embodiment. [Figure 7] This figure shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. [Figure 8] This figure shows an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. [Figure 9] This figure shows an example of an activation command A according to one aspect of this embodiment. [Figure 10] This figure shows an example of an activation command B according to one aspect of this embodiment. [Figure 11] This figure shows an example of an activation command C according to one aspect of this embodiment. [Figure 12] This figure shows an example of an activation command D according to one aspect of this embodiment. [Figure 13] This figure shows an example of an activation command E according to one aspect of this embodiment. [Figure 14] This figure shows an example of TCI state management according to one aspect of this embodiment. [Figure 15] This figure shows an example of timeline management of TCI status according to one aspect of this embodiment. [Figure 16] This figure shows an example of uplink channel transmission according to one aspect of this embodiment. [Modes for carrying out the invention]

[0011] Embodiments of the present invention will be described below.

[0012] floor(C) may also be a floor function for a real number C. For example, floor(C) may be a function that outputs the largest integer within the range not exceeding a real number C. ceil(D) may be a function for a real number D. It may also be a ceiling function. For example, ceil(D) may be a function that outputs the smallest integer not less than the real number D. mod(E,F) is a function that outputs the remainder when E is divided by F. That's fine. mod(E,F) is a function that outputs the value corresponding to the remainder when E is divided by F. This is also acceptable. exp(G) = e^G, where e is Napier's number. H^I represents H to the power of I. max(J,K) is a function that outputs the maximum value among J and K. Here, if J and K are equal, max(J,K) is a function that outputs either J or K. min(L,M) is a function that outputs the maximum value among L and M. Here, if L and M are equal, min(L,M) is a function that outputs either L or M. round(N) is a function that outputs the integer value closest to N. "·" represents multiplication.

[0013] In a wireless communication system according to one aspect of this embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. OFDM symbols are units in the time domain of OFDM. OFDM symbols include at least one or more subcarriers. OFDM symbols are converted to time-continuous signals in baseband signal generation. At least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) is used on the downlink. CP-OFDM is used on the uplink. Either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM is different from CP-OFDM. This may be given by applying transform precoding. .

[0014] An OFDM symbol may be a designation that includes a CP (Character Protection) attached to the OFDM symbol. In other words, an OFDM symbol may consist of the OFDM symbol itself and a CP attached to it.

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

[0016] The base station device 3 may consist of one or more transmitting devices (or a transmitting point, a transceiver, and a transceiver). If the base station device 3 consists of multiple transmitting devices, each of the multiple transmitting devices may be located in a different position.

[0017] The base station device 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used for wireless communication. Also, a serving cell is also referred to as a cell.

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

[0019] For example, one resource grid may be given for each component carrier. Also, one resource grid may be given for each set of a component carrier and a subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be given for a certain antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x's symbol.

[0020] The resource grid includes N size,μ grid,x N RB sc subcarriers. Here, the reso -urce grid starts from the common resource block N start,μ grid,x . Also, the common resource block N start,μ grid,x is also referred to as the reference point of the resource grid.

[0021] The resource grid is Nsubframe,μ symb Includes individual OFDM symbols.

[0022] Subscript x, which is attached to parameters related to the resource grid, specifies the transmission direction. For example, subscript x indicates either a downlink or an uplink. It may be used for that purpose.

[0023] N size,μ grid,x This is indicated by the parameters provided by the RRC layer (for example, parameters This is the offset setting for CarrierBandwidth. start,μ grid,x This is a bandwidth setting indicated by parameters provided by the RRC layer (e.g., parameter OffsetToCarrier). Offset setting and bandwidth setting refer to the configuration of the SCS-specific carrier. This is the setting used.

[0024] Subcarrier Spacing (SCS) for a given subcarrier spacing μ )Δf is Δf=2 μ It may also be 15kHz. Here, the setting μ for the subcarrier interval is 0 It may represent 1, 2, 3, or 4.

[0025] Figure 2 shows the subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb This is an example illustrating the relationship between the cyclic prefix (CP) setting and the subcarrier spacing μ is 2, and the CP setting is normal CP (normal cyclic prefix). slot symb =14, N frame,μ slot =40, N subframe, μ slot = 4. Also, in Figure 2B, for example, if the subcarrier spacing μ is set to 2, Furthermore, if the CP setting is an extended cyclic prefix, N slot symb =12, N frame ,μ slot =40, N subframe,μ slot = 4

[0026] Time unit (T) c This may be used to represent length in the time domain. Time unit T c is, T c = 1 / (Δf max ·N f ) is Δf max = 480kHz. f =409 The answer is 6. The constant κ is given by κ = Δf max ·N f / (Δf ref N f,ref ) = 64. Δf ref is, 1 It is 5kHz. f,ref The answer is 2048.

[0027] The transmission of a signal on the downlink and / or the uplink is of length T. f It may be organized into wireless frames (system frames, frames). f =(Δf max N f / 100)·T s = 10ms. A wireless frame consists of 10 subframes. The length of a subframe is T. sf =(Δf max N f / 1000)·T s = 1ms. The number of OFDM symbols per subframe is N. subframe,μ symb =Nslot symb N subframe,μ slot That is the case.

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

[0029] A slot may consist of multiple OFDM symbols, for example, N consecutive symbols. slot symb A single OFDM symbol may constitute one slot. For example, a normal CP In the settings, N slot symb =14 is also acceptable. Furthermore, in the settings for extended CP, N slot symb =12 is also acceptable.

[0030] For a certain subcarrier interval setting μ, the number of slots and their indices within the subframe may be given. For example, slot index n μ s In the subframe, the range is from 0 to N subframe,μ slot The integer values ​​may be given in ascending order within the range of -1. For setting the rear spacing μ, the number and index of slots included in the wireless frame may be given. Also, slot index n μ s,f In wireless frames, the range is 0 to N frame,μ slot The integer values ​​may also be given in ascending order within the range of -1.

[0031] Figure 3 shows an example of a resource grid configuration method according to one aspect of this embodiment. The horizontal axis of Figure 3 represents the frequency domain. Figure 3 shows an example of a resource grid configuration with a subcarrier spacing μ1 in a component carrier 300, and an example of a resource grid configuration with a subcarrier spacing μ2 in a certain component carrier. In this way, one or more subcarrier spacings may be set for a given component carrier. In Figure 3, it is assumed that μ1 = μ2 - 1, but the various aspects of this embodiment are not limited to the condition μ1 = μ2 - 1.

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

[0033] Point 3000 is an identifier used to identify a specific subcarrier. Point 3000 is also called Point A. Common resource block (CRB) set 3100 is a common resource block for setting the subcarrier interval μ1. It's a rock set.

[0034] Among the common resource block set 3100, the common resource block containing point 3000 (the black block in the common resource block set 3100 in Figure 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block at index 0 in the common resource block set 3100.

[0035] Offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. Offset 3011 is indicated by the number of common resource blocks relative to the subcarrier spacing setting μ1. The resource grid 3001 starts from the reference point of the resource grid 3001. size,μgrid1,x Includes several common resource blocks.

[0036] Offset 3013 is the distance from the reference point of resource grid 3001 to the reference point of BWP (BandWidth Part) 3003 of index i1 (N start,μ BWP,i1 This is the offset up to ).

[0037] The common resource block set 3200 is a set of common resource blocks for the subcarrier interval setting μ2.

[0038] Among the common resource block set 3200, the common resource block containing point 3000 (the solid black block in the common resource block set 3200 in Figure 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 also be the common resource block with index 0 in the common resource block set 3200.

[0039] Offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. Offset 3012 is subcarrier This is indicated by the number of common resource blocks relative to the interval μ2. The resource grid 3002 is N starting from the reference point of the resource grid 3002. size,μ grid2,x Includes several common resource blocks.

[0040] Offset 3014 is the distance from the reference point of resource grid 3002 to the reference point of BWP3004 of index i2 (N start,μ BWP,i2 This is the offset up to ).

[0041] Figure 4 shows an example configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of Figure 4, the horizontal axis is the OFDM symbol index l sym The vertical axis represents the subcarrier index k.sc is. The resource grid 3001 has N size,μ grid1,x N RB sc sub - carriers and N subframe,μ symb OFDM symbols. Within the resource grid, the resource specified by the sub - carrier index k sc and the OFDM symbol index l sym is also referred to as a resource element (RE).

[0042] A resource block (RB) contains N RB sc consecutive sub - carriers . The resource block is a general term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). Here, N = 12. RB sc

[0043] A resource block unit is a set of resources corresponding to 1 OFDM symbol in one resource block. That is, one resource block unit contains 12 resource elements corresponding to 1 OFDM symbol in one resource block.

[0044] For a common resource block with a sub - carrier spacing setting μ, in a certain common resource block set, it is indexed in ascending order from 0 in the frequency domain (indexing). The common resource block with index 0 for a sub - carrier spacing setting μ contains (or collides with, coincides with) point 3000. The index n μ CRB of the common resource block for a sub - carrier spacing setting μ is n​μ CRB =ceil(k sc / N RB sc The relationship ) is satisfied. Here, k sc A subcarrier with =0 corresponds to point 3000. This is a subcarrier that has the same center frequency as the other subcarrier.

[0045] For a given subcarrier interval setting μ, the physical resource block in a given BWP is: In the frequency domain, indexing is performed in ascending order from 0. The index n of a physical resource block for a given subcarrier interval setting μ. μ PRB is, n μ CRB =n μ PRB +N start,μ BWP,i The following relationship is satisfied. Here, N start,μ BWP,i This indicates the baseline for BWP of index i.

[0046] BWP is defined as a subset of common resource blocks included in a resource grid. The BWP is defined as the reference point N of the BWP. start,μ BWP,i N starting with size,μ BWP,i Individual common lith Includes the link block. The BWP set for the downlink carrier is also called the downlink BWP. The BWP set for the uplink component carrier is also called the uplink BWP.

[0047] An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel, and the symbol may correspond to an OFDM symbol. Furthermore, the symbol may correspond to a resource block unit. Also, the symbol may correspond to a resource element.

[0048] The fact that the large-scale properties of a channel through which symbols are transmitted in one antenna port can be estimated from the channels through which symbols are transmitted in another antenna port is referred to as QCL (Quasi Co-Located). Here, the large-scale characteristics may include at least the long-interval characteristics of the channel. The large-scale characteristics include at least some or all of the delay spread, Doppler spread, Doppler shift, average gain, average delay, and some or all of the spatial Rx parameters. That's fine. The first and second antenna ports are QCL with respect to beam parameters if the received beam assumed by the receiver for the first antenna port and the second antenna port are QCL. The receiving beam assumed by the receiving side for the antenna port may be the same (or corresponding) as the receiving beam. The first antenna port and the second antenna port are QCL with respect to beam parameters if the transmitting beam assumed by the receiving side for the first antenna port and The transmitting beam assumed by the receiving side for the second antenna port may be the same (or corresponding). Terminal device 1 assumes that the two antenna ports are QCLs if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. It is also acceptable to assume that two antenna ports are QCLs. Large-scale characteristics may also be referred to as QCL parameters. stomach.

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

[0050] Two antenna ports being type A QCLs may mean that the first large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being type B QCLs may mean that the second large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being type C QCLs may mean that the third large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being type D QCLs may mean that the fourth large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. The first large-scale characteristic may include Doppler shift, Doppler spread, mean delay, and delay spread. The second large-scale characteristic may include Doppler shift and Doppler spread. The third large-scale characteristic may include the Doppler shift and the mean delay. The fourth large-scale characteristic may include spatial reception parameters (spatial direction information, beam information). The antenna port for DMRS may be a DMRS port. The antenna port for PTRS may be a PTRS port. The antenna port associated with PTRS may be a PTRS port. The antenna port for SRS may be an SRS port. The antenna port for DMRS may be a DMRS port. The antenna port associated with DMRS may be a DMRS port.

[0051] Carrier aggregation is the aggregation of multiple servings Communication may be performed using cells. Alternatively, carrier aggregation may be performed using multiple aggregated component carriers. Communication may also be performed using multiple aggregated uplink component carriers.

[0052] Figure 5 is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of this embodiment. As shown in Figure 5, the base station device 3 includes at least a part or all of a wireless transceiver unit (physical layer processing unit) 30 and / or a higher layer processing unit 34. The wireless transceiver unit 30 includes an antenna unit 31, an RF (Radio Frequency) unit 32, and a baseband The upper layer processing unit 34 includes at least part or all of the D unit 33. The upper layer processing unit 34 includes at least part or all of the media access control layer processing unit 35 and the radio resource control (RRC) layer processing unit 36.

[0053] The wireless transmitting / receiving unit 30 includes at least part or all of the wireless transmitting unit 30a and the wireless receiving unit 30b. Here, the device configuration of the baseband unit included in the wireless transmitting unit 30a and the baseband unit included in the wireless receiving unit 30b may be the same or different. Also, the device configuration of the RF unit included in the wireless transmitting unit 30a and the RF unit included in the wireless receiving unit 30b may be the same or different. Also, the antenna unit included in the wireless transmitting unit 30a and the wireless receiving unit The device configuration of the antenna section included in the signal terminal 30b may be the same or different.

[0054] For example, the wireless transmission unit 30a may generate and transmit a PDSCH baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PDCCH baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PBCH baseband signal. For example, The line transmission unit 30a may generate and transmit a baseband signal of the synchronization signal. For example, The line transmission unit 30a may generate and transmit a PDSCH DMRS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PDCCH DMRS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a CSI-RS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a DL PTRS baseband signal.

[0055] For example, the wireless receiver 30b may receive PRACH. For example, the wireless receiver 30b may receive and demodulate PUCCH. The wireless receiver 30b may receive and demodulate PUSCH. For example, the wireless receiver 30b may receive PUCCH DMRS. For example, the wireless receiver 30b The wireless receiver 30b may receive PUSCH DMRS. For example, the wireless receiver 30b may receive UL PTRS. For example, the wireless receiver 30b may receive SRS.

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

[0057] The media access control layer processing unit 35, which is part of the upper layer processing unit 34, performs MAC layer processing.

[0058] The wireless resource control layer processing unit 36, which is part of the upper layer processing unit 34, performs RRC layer processing. The line resource control layer processing unit 36 ​​processes various setting information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 36 ​​manages the RRC message received from terminal device 1. Set the parameters based on the sage.

[0059] The wireless transceiver unit 30 (or wireless transmission unit 30a) performs processing such as modulation and encoding. The wireless transceiver unit 30 (or wireless transmission unit 30a) modulates and encodes the downlink data. A physical signal is generated by generating a baseband signal (conversion to a time-continuous signal) and transmitted to the terminal device 1. The wireless transceiver 30 (or wireless transmitter 30a) then transmits the physical signal. It may be placed on a component carrier and transmitted to terminal device 1.

[0060] The wireless transceiver unit 30 (or wireless receiver unit 30b) performs processing such as demodulation and decoding. The wireless transmitting / receiving unit 30 (or wireless receiving unit 30b) separates, demodulates, and processes the received physical signal. The signal is decoded, and the decoded information is output to the upper layer processing unit 34. The wireless transceiver 30 (or wireless receiver 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 (downconvert) by quadrature demodulation, removing unwanted frequencies. The fractional part is removed. The RF unit 32 outputs the processed analog signal to the baseband unit.

[0062] The baseband section 33 receives the analog signal input from the RF section 32. It converts to a digital signal. The baseband section 33 removes the portion corresponding to the Cyclic Prefix (CP) from the converted digital signal, and then processes the signal from which the CP has been removed. A Fast Fourier Transform (FFT) is performed to extract the signal in the frequency domain.

[0063] The baseband section 33 performs an inverse fast Fourier transform (IFFT) on the data to generate OFDM symbols, adds CP to the generated OFDM symbols, and base The baseband unit 33 generates a digital signal for the band 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 section 32 uses a low-pass filter to remove unwanted frequency components from the analog signal input from the baseband section 33 and upconverts the analog signal to the carrier frequency. The signal is converted and transmitted via the antenna unit 31. The RF unit 32 may also have a function to control the transmission power. The RF unit 32 is also referred to as the transmission power control unit.

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

[0066] Each of the serving cells set for terminal device 1 is PCell(Primary cell, It may be any of the following: Primary Cell, PSCell (Primary SCG cell), or SCell (Secondary Cell).

[0067] A PCell is a serving cell included in an MCG (Master Cell Group). A PCell is a cell that performs the initial connection establishment procedure or the connection re-establishment procedure by terminal device 1. (The cells that have been treated.)

[0068] PSCells are serving cells included in the SCG (Secondary Cell Group). This is a serving cell that is accessed randomly by terminal device 1.

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

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

[0071] One or more downlink BWPs may be set for each serving cell (or downlink component carrier). One or more uplink BWPs are configured for each component carrier. That's fine.

[0072] Of the one or more downlink BWPs set for a serving cell (or downlink component carrier), one downlink BWP becomes the active downlink BWP. It may be set (or one downlink BWP may be activated). Of the one or more uplink BWPs set for a moving cell (or uplink component carrier), one uplink BWP is set as the active uplink BWP. This may be done (or one uplink BWP may be activated).

[0073] PDSCH, PDCCH, and CSI-RS may be received on the active downlink BWP. Terminal device 1 may attempt to receive PDSCH, PDCCH, and CSI-RS on the active downlink BWP. PUCCH and PUSCH are transmitted on the active uplink BWP. It may be done. Terminal device 1 performs PUCCH and PUSCH on the active uplink BWP. You may send this. Active downlink BWP and active uplink BWP are also collectively referred to as active BWP.

[0074] PDSCH, PDCCH, and CSI-RS are downlink BWPs other than active downlink BWPs. It does not need to be received in an inactive downlink (BWP). Terminal device 1 is active In a BWP downlink that is not a BWP, PDSCH, PDCCH, and CSI-RS are received. There is no need to try to trust it. PUCCH and PUSCH are not active uplink BWP. It is not necessary to transmit in an inactive uplink BWP. Terminal device 1 does not need to transmit PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP. Inactive downlink BWP and inactive uplink BWP is collectively referred to as inactive BWP.

[0075] Downlink BWP switching is performed by one active serving cell. Deactivate the downlink BWP and the in-service of the serving cell. This is the procedure for activating one of the active downlink BWPs. The BWP switching of the downlink may be controlled by the BWP field included in the downlink control information. The BWP switching of the downlink may also be controlled based on parameters of the higher layer. good.

[0076] Uplink BWP switching is used to deactivate one active uplink BWP and activate one of the inactive uplink BWPs that is not the active one. The replacement may be controlled by the BWP field included in the downlink control information. Uplink The BWP switching of links may be controlled based on parameters at a higher level.

[0077] Two or more of the one or more downlink BWPs set for a serving cell A downlink BWP does not necessarily have to be set as the active downlink BWP. For a serving cell, one downlink BWP may be active at any given time.

[0078] Two or more of the one or more uplink BWPs set for a serving cell An uplink BWP does not have to be set as the active uplink BWP. For a serving cell, one uplink BWP may be active at a given time.

[0079] Figure 6 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one aspect of this embodiment. As shown in Figure 6, the terminal device 1 includes at least one or all of a wireless transceiver unit (physical layer processing unit) 10 and a higher layer processing unit 14. The wireless transceiver unit 10 includes at least part or all of an antenna unit 11, an RF unit 12, and a baseband unit 13. The higher layer processing unit 14 includes at least part or all of a media access control layer processing unit 15 and a wireless resource control layer processing unit 16.

[0080] The wireless transceiver 10 includes at least part or all of the wireless transmission unit 10a and the wireless reception unit 10b. Here, the baseband unit 13 included in the wireless transmission unit 10a and the wireless reception unit The device configuration of the baseband section 13 included in 10b may be the same or different. Furthermore, the device configuration of the RF unit 12 included in the wireless transmission unit 10a and the RF unit 12 included in the wireless reception unit 10b may be the same or different. The device configuration of the antenna unit 11 and the antenna unit 11 included in the wireless receiver unit 10b are the same. It's fine if it's different, or it's fine if it's not.

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

[0082] For example, the wireless receiver 10b may receive and demodulate a PDSCH. For example, the wireless receiver 10b may receive and demodulate a PDCCH. For example, the wireless receiver 10b may receive a PBCH. Demodulation is also possible. For example, the wireless receiver 10b may receive a synchronization signal. For example, The line receiver 10b may receive PDSCH DMRS. For example, the wireless receiver 10b may receive PDCCH DMRS. For example, the wireless receiver 10b may receive CSI-RS. For example, the wireless receiver 10b may receive DL PTRS.

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

[0084] The media access control layer processing unit 15, which is part of the upper layer processing unit 14, performs MAC layer processing.

[0085] The wireless resource control layer processing unit 16, which is part of the upper layer processing unit 14, performs RRC layer processing. The line resource control layer processing unit 16 processes various setting information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 16 manages the RRC messages received from the base station device 3. Set the RRC parameters based on the message.

[0086] The wireless transceiver unit 10 (or wireless transmission unit 10a) performs processing such as modulation and encoding. The wireless transceiver unit 10 (or wireless transmission unit 10a) modulates and encodes the uplink data. A physical signal is generated by generating a baseband signal (conversion to a time-continuous signal) and transmitted to the base station device 3. The wireless transceiver 10 (or wireless transmitter 10a) transmits the physical signal It may be placed on a BWP (Active Uplink BWP) and transmitted to the base station device 3.

[0087] The wireless transceiver unit 10 (or wireless receiver unit 10b) performs processing such as demodulation and decoding. The wireless transceiver 10 (or wireless receiver 30b) may receive a physical signal in a BWP (active downlink BWP) of a serving cell. The wireless receiver 10b) separates, demodulates, and decodes the received physical signal, and the decoded information The output is sent to the upper layer processing unit 14. The wireless transceiver unit 10 (wireless receiver unit 10b) transmits the physical signal. Prior to this, the channel access procedure may be performed.

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

[0089] The baseband section 13 converts the analog signal input from the RF section 12 into a digital signal. The baseband section 13 then calculates the CP (Cyclic Prefix) from the converted digital signal. The unwanted portion is removed, and a Fast Fourier Transform (FFT) is performed on the signal from which the CP has been removed to extract the signal in the frequency domain.

[0090] The baseband section 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, and then adds a CP to the generated OFDM symbol. The baseband unit 13 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 section 12 uses a low-pass filter to remove unwanted frequency components from the analog signal input from the baseband section 13 and upconverts the analog signal to the carrier frequency. The signal is converted and transmitted via the antenna unit 11. The RF unit 12 may also have a function to control the transmission power. The RF unit 12 is also referred to as the transmission power control unit.

[0092] The following will explain physical signals (signals).

[0093] Physical signals are a collective term for downlink physical channels, downlink physical signals, uplink physical channels, and uplink physical channels. Physical channels are a collective term for downlink physical channels and uplink physical channels. Physical signals are a collective term for downlink physical signals and uplink physical signals. Physical signals may also be called reference signals.

[0094] An uplink physical channel may correspond to a set of resource elements that transmit information generated in the higher layer. An uplink physical channel may also be a physical channel used in an uplink component carrier. An uplink physical channel may be transmitted by terminal device 1. An uplink physical channel may be received by base station device 3. In a wireless communication system according to one aspect of this 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] PUCCH transmits Uplink Control Information (UCI) It may be used. PUCCH may be transmitted to deliver, transmit, or convey uplink control information. Uplink control information may be mapped to PUCCH. Terminal device 1 may transmit PUCCH on which uplink control information is mapped. Base station Device 3 may receive a PUCCH containing uplink control information.

[0096] Uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) is channel state information (CSI), schedule This includes at least some or all of the Scheduling Request (SR) and HARQ-ACK (Hybrid Automatic Repeat Request ACKnowledgement) information.

[0097] Channel status information is also referred to as channel status information bits or channel status information sequences. Scheduling requests are also referred to as scheduling request bits or scheduling request sequences. HARQ-ACK information is also referred to as HARQ-ACK information bits or HARQ-ACK information sequences.

[0098] HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). A HARQ-ACK may indicate an ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to a transport block. An ACK may indicate that the transport block has been decoded successfully. A NACK may indicate that the transport block has not been decoded successfully. HARQ-ACK information may include a HARQ-ACK codebook containing 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 the UL-SCH (UpLink - Shared Channel) of the transport layer.

[0100] In some cases, the HARQ-ACK for the transport block is referred to as the HARQ-ACK for the PDSCH. There is a match. In this case, “HARQ-ACK for PDSCH” refers to the transport included in PDSCH. Shows the HARQ-ACK for the block.

[0101] HARQ-ACK may represent an ACK or NACK corresponding to a single CBG (Code Block Group) contained within a transport block.

[0102] The scheduling request is for UL-SCH for new transmission. It may be used to request a source. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, it is also referred to as "a positive SR is transmitted". A positive SR is used by terminal device 1 for initial transmission of UL-SCH This may indicate that the resources are requested. A positive SR may indicate that the scheduling request is triggered by a higher layer. A positive SR may be transmitted when the scheduling request is instructed by a higher layer. When the scheduling request bit indicates a negative SR, it is also referred to as "a negative SR is sent." A negative SR may indicate that the terminal device 1 does not request UL-SCH resources for initial transmission. A negative SR may indicate that the upper layer has not triggered a scheduling request. A negative SR may be propagated when the upper layer has not instructed a scheduling request.

[0103] Channel status information may include at least some or all of the Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). CQI is an indicator related to the quality of the propagation path (e.g., propagation intensity) or the quality of the physical channel, and PMI is related to the precoder. These are related metrics. RI is a metric related to the transmit rank (or transmit layer count).

[0104] Channel status information is an indicator of the reception status of at least the physical signal (e.g., CSI-RS) used for channel measurement. The value of channel status information is used for channel measurement. The channel measurement may be determined by the terminal device 1 based on the reception conditions assumed by at least the physical signals used. The channel measurement may include interference measurement.

[0105] PUCCH may support the PUCCH format. PUCCH may be a set of resource elements used to transmit the PUCCH format. PUCCH may contain the PUCCH format. PUCCH may be transmitted with a certain PUCCH format. The PUCCH format may be interpreted as a format of information. Alternatively, the PUCCH format may be interpreted as a set of information set into a certain format of information.

[0106] PUSCH provides either or both of the transport block and the uplink control information. It may be used for transmission. The transport block may be placed in PUSCH. i. Transport blocks delivered by UL-SCH may be placed in PUSCH. Uplink control information may be placed in PUSCH. Terminal device 1 is transport block A PUSCH may be transmitted containing either or both of the uplink control information. The base station device 3 may receive a PUSCH containing either or both a transport block and uplink control information.

[0107] PRACH may be transmitted to convey the random access preamble. Device 1 may transmit PRACH. Base station device 3 may receive PRACH. column x u,v (n) is x u,v (n) = x u (mod(n+C v ,L RA Defined by )), where x u It belongs to the ZC (Zadoff Chu) series. Also, x u is x u =exp(-jπui(i+1) / L RA ) by It may also be defined as follows: j is the imaginary unit. Also, π is the ratio of a circle's circumference to its diameter. Also, C v This corresponds to the cyclic shift of the PRACH series. Also, L RA This corresponds to the length of the PRACH sequence. Also, L RA It is 839 or 139. Also, i is from 0 to L RA -1 It is an integer within the range of . Also, u is the series index for the PRACH series.

[0108] For each PRACH opportunity, 64 random access preambles are defined. The access preamble is a cyclic shift C in the PRACH family. v , and identified based on the sequence index u for the PRACH sequence. 64 random access prians identified Each bull may be assigned an index.

[0109] Uplink physical signals may correspond to a set of resource elements. Uplink physical signals do not have to be used to transmit information generated in the upper layer. However, uplink physical signals may be used to transmit information generated in the physical layer. Uplink physical signals may also be physical signals used in the uplink component carrier. Terminal device 1 may transmit uplink physical signals. Base station device 3 may receive uplink physical signals. In a wireless communication system according to one aspect of this 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] The set of antenna ports for a PUSCH (DMRS associated with a PUSCH, DMRS included in a PUSCH, DMRS corresponding to a PUSCH) is given based on the set of antenna ports for the PUSCH. It may be obtained. For example, the set of antenna ports for a DMRS for a PUSCH may be the same as the set of antenna ports for the PUSCH.

[0112] The transmission of a PUSCH and the transmission of a DMRS for said PUSCH are indicated by a single DCI format. It may be (or may be scheduled). PUSCH and DMRS for said PUSCH These may be collectively referred to as PUSCH. Sending a PUSCH may also involve sending a PUSCH and a DMRS for that PUSCH.

[0113] The propagation path of a pusher may be estimated from the DMRS for that pusher.

[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. stomach.

[0115] The transmission of PUCCH and the transmission of DMRS for said PUCCH are indicated by a single DCI format. It may (or may be triggered). Mapping of PUCCH to resource element (resource element mapping), and to the DMRS resource element for the PUCCH. One or both of the mappings may be given by a single PUCCH format. The PUCCH and the DMRS for said PUCCH may be collectively referred to as PUCCH. Sending a PUCCH This may involve sending a PUCCH and a DMRS for the PUCCH.

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

[0117] A downlink physical channel may correspond to a set of resource elements that transmit information generated in the upper layer. A downlink physical channel may also be a physical channel used in a downlink component carrier. Base station device 3 may transmit a downlink physical channel. Terminal device 1 may receive a downlink physical channel. In a wireless communication system according to one aspect of this 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] PBCH may be transmitted to transmit either or both MIB (Master Information Block) and / or physical layer control information, where physical layer control information is information generated at the physical layer. MIB is a set of parameters placed in BCCH (Broadcast Control Channel), which is a logical channel of the MAC layer. The BCCH is a channel of the transport layer. It is placed on a BCH. The BCH may be placed (mapped) on a PBCH. Terminal device 1 may receive a PBCH on which the MIB and / or physical layer control information are placed. Base station device 3 may transmit a PBCH on which the MIB and / or physical layer control information are placed. stomach.

[0119] For example, the physical layer control information may consist of 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D. 0A) Wireless frame bit 0B) Half Wireless Frame (Half System Frame, Half Frame) Bits 0C)SS / PBCH Block Index Bit 0D) Subcarrier offset bit

[0120] The wireless frame bits are used to indicate the wireless frame transmitted by the PBCH (the wireless frame containing the slot from which the PBCH is transmitted). The wireless frame bits consist of 4 bits. The wireless frame bits may consist of 4 bits from a 10-bit wireless frame indicator. For example, the wireless frame indicator may be used to identify wireless frames from 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 the radio frame in which the PBCH is transmitted. Here, the half-radio frame may consist of five subframes. Alternatively, the half-radio frame may consist of the first five subframes of the ten subframes included in the radio frame. Alternatively, the half-radio frame may consist of the last five subframes of the ten subframes included in the radio frame.

[0122] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include 3 bits. The SS / PBCH block index bits may be constituted by 3 bits out of the 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used at least to identify the SS / PBCH blocks from index 0 to index 63.

[0123] The subcarrier offset bits are used to indicate the subcarrier offset. The subcarrier offset 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 of index 0 is mapped.

[0124] The PDCCH may be transmitted to transmit downlink control information (DCI: Downlink Control Information). 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. Note that the DCI format may be interpreted as the format of the downlink control information. Also, the DCI format may be interpreted as a set of downlink control information set for a certain downlink control information format.

[0126] DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. The uplink DCI format is DCI It is a general term for 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 at least used for scheduling the PUSCH arranged in a certain cell. DCI Format 0_0 is composed of at least a part or all of Fields 1A to 1E. 1A) DCI Format Specific Field (Identifier field for DCI formats) 1B) Frequency Domain Resource Allocation Field (Frequency domain resource assignment field) 1C) Time Domain Resource Allocation Field (Time domain resource assignment field) 1D) Frequency Hopping Flag Field (Frequency hopping flag field) 1E) MCS Field (MCS field: Modulation and Coding Scheme field)

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

[0129] The frequency domain resource allocation field included in DCI Format 0_0 may be used to indicate the allocation of frequency resources for the PUSCH.

[0130] ​The time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for PUSCH.

[0131] The frequency hopping flag field indicates whether frequency hopping is applied to PUSCH. It may be used to indicate whether or not something is true.

[0132] The MCS field included in DCI format 0_0 is the modulation scheme for PUSCH, and , may be used to indicate at least one or both of the target coding rates. The target coding rate is the target code for the transport block placed in PUSCH. The coding rate may also be the size of the transport block (TBS) placed in the PUSCH, which is one of the target coding rate and the modulation scheme for the PUSCH. The decision may be based on both factors.

[0133] DCI format 0_0 includes fields used in CSI requests. It's not necessary.

[0134] DCI format 0_0 does not need to include a carrier indicator field. In other words, the serving cell to which the uplink component carrier to which the PUSCH scheduled by DCI format 0_0 is located belongs is DCI format 0_0 The PDCCH is located in the same serving cell as the uplink component carrier. It is also possible. Terminal device 1 detects DCI format 0_0 on a downlink component carrier of a serving cell and, based on that, sends a PUSCH scheduled by DCI format 0_0 to the uplink component of the serving cell. It may be acceptable to consider placing them on the carrier.

[0135] DCI format 0_0 does not need to include a BWP field (BWP indicator field). Here, DCI format 0_0 is PUSCH without changing the active uplink BWP. The DCI format used for scheduling may also be used. Terminal device 1 detects DCI format 0_0 used for scheduling PUSCH and then performs an active uplink. It may be recognized that the PUSCH message is sent without switching the link BWP.

[0136] DCI format 0_1 ​​is used at least for scheduling PUSCHs placed in a cell. DCI format 0_1 ​​is used for part of fields 2A to 2H or It consists of at least all of the above. 2A) DCI Format Specific Fields 2B) Frequency Domain Resource Allocation Field 2C) Time-domain resource allocation field for uplink 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 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 PUSCH.

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

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

[0142] DCI format 0_1 that does not include a BWP field may be a DCI format that schedules PUSCH without a change in the active uplink BWP. The terminal device 1 may recognize that it transmits the PUSCH without switching the active uplink BWP based on detecting the DCI format 0_1 used for the scheduling of the PUSCH and that 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 is the DCI format 0_1 used for the scheduling of the PUSCH and that does not include a BWP field. ​​​​​​Based on the detection of DCI format 0_1 ​​including the field, it may be recognized that the PUSCH should be transmitted without switching the active uplink BWP. Here, terminal device 1 If the terminal supports the BWP switching function, the RRC layer's function information reporting procedure may report that "Terminal device 1 supports the BWP switching function."

[0144] The CSI request field is used to instruct the CSI report.

[0145] If DCI format 0_1 ​​includes a carrier indicator field, then The rear indicator field is located on the upward link component carrier where the PUSCH is positioned. It may be used to indicate A. DCI format 0_1 ​​carrier indicator If no field is included, the uplink component carrier where PUSCH is located is, A PDCCH containing DCI format 0_1, which is used for scheduling the PUSCH, is configured. It may be the same as the uplink component carrier. If the number of uplink component carriers set on terminal device 1 in a serving cell group is 2 or more (when uplink carrier aggregation is operated in a serving cell group), the scheduler of PUSCH placed in that serving cell group The carrier indicator field included in DCI format 0_1 ​​used in the game The number of bits may be 1 or more (for example, 3 bits). If the number of uplink component carriers set on terminal device 1 in a serving cell group is 1 (i.e., uplink carrier aggregation is not operated in a serving cell group), the schedule of PUSCH placed in that serving cell group Carrier indicator field included in DCI format 0_1 ​​used for ing The number of bits may be 0 bits (or the carrier indicator in DCI format 0_1 ​​used for scheduling PUSCH placed in the serving cell group). (Caterfields may not be included.)

[0146] DCI format 1_0 is used at least for scheduling PDSCHs located in a given cell. DCI format 1_0 is used less than some or all of 3A through 3F. It is composed of including the above. 3A) DCI Format Specific Fields 3B) Frequency Domain Resource Allocation Field 3C) Time Domain Resource Allocation Field 3D) MCS Field 3E) PDSCH to 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 to indicate the allocation of frequency resources for PDSCH.

[0149] The time domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of time resources for PDSCH.

[0150] The MCS field included in DCI format 1_0 is the modulation scheme for PDSCH, and , may be used to indicate at least one or both of the target coding rates. The target coding rate is the target code for the transport block placed in the PDSCH. The coding rate may also be the target coding rate. The size of the transport block (TBS) placed in the PDSCH is determined by the target coding rate and the modulation scheme for the PDSCH. The decision may be based on both factors.

[0151] The PDSCH_HARQ feedback timing instruction field is set to the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. It may be used to indicate a set.

[0152] The PUCCH resource reference field may be a field that indicates the index of one or more PUCCH resources included in the PUCCH resource set. The PUCCH resource set may contain one or more PUCCH resources.

[0153] DCI format 1_0 does not need to include a carrier indicator field. In other words, the downlink component carrier on which a PDSCH scheduled by DCI format 1_0 is located may be the same as the downlink component carrier on which a PDCCH containing DCI format 1_0 is located. Based on the detection of DCI format 1_0 in a certain downlink component carrier, terminal device 1 places the PDSCH scheduled by DCI format 1_0 in the downlink component It may be acceptable to consider placing them on the carrier.

[0154] DCI format 1_0 does not have to include the BWP field. Here DCI format The format 1_0 may be a DCI format that schedules the PDSCH without changing the active downlink BWP. The terminal device 1 may recognize that it can receive the PDSCH 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 PDSCHs located in a given cell. DCI format 1_1 is used less than some or all of 4A to 4I It is composed of including the above. 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 Indicator Field 4G)PUCCH resource instruction field 4H) BWP Field 4I) Carrier Indicator Field

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

[0157] The frequency domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of frequency resources for PDSCH.

[0158] The time domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of time resources for PDSCH.

[0159] The MCS field included in DCI format 1_1 is the modulation scheme for PDSCH, and This may be used to indicate at least one or both of the target coding rates.

[0160] If DCI format 1_1 includes a PDSCH_HARQ feedback timing indicator field, the PDSCH_HARQ feedback timing indicator field extends from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. This may be used to indicate the offset. If DCI format 1_1 does not include the PDSCH_HARQ feedback timing indicator field, the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be determined by a parameter in the upper layer.

[0161] The PUCCH resource reference field may be a field that indicates the index of one or more PUCCH resources included in the PUCCH resource set.

[0162] The BWP field of DCI format 1_1 is used in the schedule according to DCI format 1_1. It may be used to indicate the downlink BWP on which the scheduled PDSCH is located. In other words, DCI format 1_1 may be accompanied by a change in the active downlink BWP. Terminal device 1 may recognize the downlink BWP on which the PDSCH is located based on detecting the DCI format 1_1 used for scheduling the PDSCH.

[0163] DCI format 1_1, which does not include the BWP field, indicates a change in the active downlink BWP. It may also be a DCI format that schedules PDSCH without BWP. Terminal device 1 is a DCI format 1_1 used for scheduling PDSCH, and BWP Based on detecting DCI format 1_1 that does not include a field, active downlink It is acceptable to recognize that the PDSCH is being received without switching the link BWP.

[0164] DCI format 1_1 includes a BWP field, but terminal device 1 is DCI format If the BWP switching function by 1_1 is not supported, the BWP field will be in terminal device 1. Therefore, it can be ignored. In other words, terminal device 1 that does not support the BWP switching function is , DCI format 1_1 used for scheduling PDSCH, and BWP format Based on the detection of DCI format 1_1 including the field, it may be recognized that the PDSCH can be received without switching the active downlink BWP. Here, terminal device 1 If the terminal supports the BWP switching function, the RRC layer's function information reporting procedure may report that "Terminal device 1 supports the BWP switching function."

[0165] If DCI format 1_1 includes a carrier indicator field, the carrier The rear indicator field is the downlink component carrier where the PDSCH is located. It may be used to indicate A. DCI format 1_1 carrier indicator If no field is included, the downlink component carrier where the PDSCH is located is, A PDCCH containing DCI format 1_1, which is used for scheduling the PDSCH, is configured. It may be the same as the downlink component carrier. If the number of downlink component carriers set on terminal device 1 in a serving cell group is 2 or more (when downlink carrier aggregation is operated in a serving cell group), the scheduler of the PDSCH placed in that serving cell group The carrier indicator field included in DCI format 1_1 used in the game The number of bits may be 1 or more (for example, 3 bits). If the number of downlink component carriers set on terminal device 1 in a serving cell group is 1 (i.e., downlink carrier aggregation is not operated in a serving cell group), the scheduler of the PDSCH placed in that serving cell group Carrier indicator field included in DCI format 1_1 used for ing The number of bits may be 0 bits (or the DCI format 1_1 used for scheduling PDSCHs placed in a given serving cell group may not include a carrier indicator field).

[0166] PDSCH may be transmitted to transmit transport blocks. PDSCH may be used to transmit transport blocks delivered from DL-SCH. PDSCH may be used to transmit transport blocks. Transport blocks may be placed on PDSCH. Transport blocks corresponding to DL-SCH are on PDSCH. They may be arranged. Base station device 3 may transmit PDSCH. Terminal device 1 may receive PDSCH.

[0167] Downlink physical signals may correspond to a set of resource elements. Downlink physical signals do not have to carry information generated in the upper layer. Downlink physical signals may be physical signals used in the downlink component carrier. Downlink physical signals may be transmitted by base station device 3. Downlink physical signals may be transmitted by terminal device 1. In a wireless communication system according to one aspect of this 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 to synchronize the terminal device 1 in either the frequency domain or the time domain of the downlink, or both. The synchronization signal is a general term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0169] Figure 7 shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In this case, the horizontal axis is the time axis (OFDM symbol index l sym ) and the vertical axis represents the frequency domain. Block 700 also shows the set of resource elements for PSS. Block 720 shows a set of resource elements for SSS. Also, four blocks Blocks 710, 711, 712, and 713 represent a set of resource elements for a PBCH and a DMRS for the PBCH (DMRS associated with the PBCH, DMRS contained within the PBCH, and DMRS corresponding to the PBCH).

[0170] As shown in Figure 7, the SS / PBCH block contains PSS, SSS, and PBCH. The SS / PBCH block also contains four consecutive OFDM symbols. The SS / PBCH block contains 240 subcarriers. PSS is the 57th to 183rd subcarriers in the first OFDM symbol. It is placed on the subcarrier. SSS is from the 57th to the 183rd OFDM symbol in the third OFDM symbol. It is placed in the nth subcarrier. Subcarriers 1 through 56 of the first OFDM symbol may be set to zero. Subcarriers 184 through 240 of the first OFDM symbol may be set to zero. Subcarriers 49 through 56 of the third OFDM symbol may be set to zero. Subcarriers 184 through 192 of the third OFDM symbol may be set to zero. The PBCH is placed in subcarriers 1 through 240 of the second OFDM symbol, where a DMRS for the PBCH is not placed. The PBCH is placed in subcarriers 1 through 48 of the third OFDM symbol, where a DMRS for the PBCH is not placed. The PBCH is placed in subcarriers 193 through 240 of the third OFDM symbol, where a DMRS for the PBCH is not placed. The PBCH is placed on the subcarriers from the 1st to the 240th subcarrier of the 4th OFDM symbol, where a DMRS for the PBCH is not located.

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

[0172] The PBCH whose symbol is transmitted at a given antenna port may be estimated by a DMRS for the PBCH located in the slot to which the PBCH is mapped, and which is included in the SS / PBCH block containing the PBCH.

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

[0174] The set of antenna ports for DMRS for PDSCH (DMRS associated with PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) is given based on the set of antenna ports for said PDSCH. It may be obtained. In other words, the set of antenna ports for a DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

[0175] The transmission of PDSCH and the transmission of DMRS for said PDSCH are indicated by a single DCI format. This may be done (or scheduled). The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting a PDSCH may be done by transmitting the PDSCH and the DMRS for the PDSCH.

[0176] The propagation path of a PDSCH may be estimated from the DMRS for that PDSCH. A set of resource elements on which the signal is transmitted, and a DMRS symbol for the PDSCH. If the set of resource elements on which the symbol is transmitted belongs to the same Precoding Resource Group (PRG), the PDSCH on which the symbol of that PDSCH is transmitted at a given antenna port may be estimated by the DMRS for that PDSCH.

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

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

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

[0180] The BCH in the transport layer is mapped to the PBCH in the physical layer. In other words, the transport layer Transport blocks passing through the BCH are delivered to the PBCH in the physical layer. The UL-SCH in the transport layer is mapped to the PUSCH in the physical layer. In other words, transport blocks passing through the UL-SCH in the transport layer are delivered to the PUSCH in the physical layer. Also, the DL-SCH in the transport layer is mapped to the PDSCH in the physical layer. In other words, the DL-SCH in the transport layer The transport blocks that pass through are delivered to the PDSCH in the physical layer.

[0181] Each serving cell may be given one UL-SCH and one DL-SCH. BCH may be given to the PCell. BCH may not be given to the PSCell or SCell.

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

[0183] BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. For example, BCCH is MIB. Alternatively, it is a channel in the RRC layer used to transmit system information. Also, CCCH The Common Control Channel transmits a common RRC message across multiple terminal devices. It may be used for the purpose of... Here, CCCH is, for example, a terminal device that is not connected to RRC. It may be used for 1. Also, DCCH (Dedicated Control Channel) is a terminal device It may be used at least to send a dedicated RRC message to 1. Here, DCCH This may be used, for example, for terminal device 1 that is connected via RRC.

[0184] Higher-level parameters common to multiple terminal devices 1 are also called common higher-level parameters. Here, common higher-level parameters may be defined as parameters specific to a serving cell. Here, parameters specific to a serving cell are parameters common to the terminal devices (e.g., terminal devices 1-A, B, C) on which the serving cell is set. That's fine.

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

[0186] Among certain upper-level parameters, those that differ from common upper-level parameters are also called dedicated upper-level parameters. Here, dedicated upper-level parameters can provide dedicated RRC parameters to terminal device 1-A on which a serving cell is configured. In other words, the dedicated RRC parameters are higher-level parameters that can provide unique settings for each of the terminal devices 1-A, B, and C.

[0187] The BCCH of a logical channel is mapped to the BCH of the transport layer or the DL-SCH. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. Also, a transport block containing system information that is not an MIB is delivered to the transport layer. It is delivered to DL-SCH in the T layer. Also, CCCH is mapped to DL-SCH or UL-SCH. Transport blocks mapped to CCCH are delivered to DL-SCH or UL-SCH. Similarly, DCCH is mapped to DL-SCH or UL-SCH. In other words, transport blocks mapped to DCCH are delivered to DL-SCH or UL-SCH.

[0188] An RRC message contains one or more parameters managed in the RRC layer. These parameters are also referred to as RRC parameters. For example, RRC Messages may include MIBs. RRC messages may also include system information. Furthermore, RRC messages may include messages corresponding to CCCHs. RRC messages may also include messages corresponding to DCCHs. RRC messages containing messages corresponding to DCCHs are also referred to as individual RRC messages.

[0189] Higher-level parameters are parameters included in RRC parameters or MAC CE (Medium Access Control Control Element). Lameter is a message corresponding to MIB, system information, CCCH, and DCCH. This refers to the parameters included in MAC CE. The parameters included in MAC CE are sent via the MAC CE (Control Element) command.

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

[0191] Cell search is a procedure used by terminal device 1 to synchronize with a cell in the time domain and frequency domain and to detect its physical cell identity. In other words, terminal device 1 may use cell search to synchronize with a cell in the time domain and frequency domain and detect its physical cell identity.

[0192] The PSS series is assigned based on at least the physical cell ID. The SSS series is assigned based on at least the physical cell ID.

[0193] SS / PBCH block candidates indicate resources that are permitted (possible, reserved, configured, specified, or potentially) to send SS / PBCH blocks.

[0194] A set of SS / PBCH block candidates in a half-wireless frame is also called an SS burst set. An SS burst set is a transmission window. It is also called the SS transmission window or the Discovery Reference Signal transmission window. An SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.

[0195] Base station device 3 transmits SS / PBCH blocks of one or more indices at predetermined intervals. Terminal device 1 detects at least one of the SS / PBCH blocks of the one or more indices and decodes the PBCH contained in the SS / PBCH block. You may try this.

[0196] Random access is a procedure that includes at least part or all of message 1, message 2, message 3, and message 4.

[0197] Message 1 is the procedure for sending PRACH by terminal device 1. Terminal device 1, Based on an index of SS / PBCH block candidates detected through cell search, a PRACH is sent in one PRACH opportunity selected from among one or more PRACH opportunities. Each PRACH opportunity is defined based on at least time-domain and frequency-domain resources. It can be done.

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

[0199] Message 2 is a DCI message with a CRC (Cyclic Redundancy Check) that has been scrambled by terminal device 1 using RA-RNTI (Random Access - Radio Network Temporary Identifier). This is a procedure to attempt to detect format 1_0. Terminal device 1 receives a control resource set based on the MIB contained in the PBCH contained in the SS / PBCH block detected based on cell search. In the resources indicated based on the settings of the search area set, the DCI format Attempts to detect PDCCH containing the . Message 2 is also called a random access response. To be called.

[0200] Message 3 is included in DCI format 1_0 detected by the Message 2 procedure. Send a PUSCH scheduled by a random access response grant. This is the procedure. Here, random access response grant The grant is indicated by the MAC CE included in the PDSCH scheduled according to the DCI format 1_0.

[0201] PUSCH, which is scheduled based on random access response grants, Message 3 PUSCH, or simply PUSCH. Message 3 PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier MAC CE is a collision Includes the resolution ID.

[0202] The retransmission of message 3 PUSCH is scheduled in DCI format 0_0 with a scrambled CRC based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

[0203] Message 4 is a procedure to attempt to detect DCI format 1_0 with a CRC scrambled based on either C-RNTI (Cell - Radio Network Temporary Identifier) ​​or TC-RNTI. Terminal device 1 schedules based on the DCI format 1_0. The PDSCH to be received may contain a collision resolution ID.

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

[0205] In data communication, terminal device 1 attempts to detect PDCCH in resources identified based on the control resource set and the search area set (monitor PDCCH, PDCCH (Monitor).

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

[0207] The set of resource blocks that constitute the control resource set may be indicated by a higher-level parameter. The number of OFDM symbols that constitute the control resource set may also be indicated by a higher-level parameter.

[0208] Terminal device 1 attempts to detect PDCCH in the search area set. Here, the search area set Attempting to detect PDCCH in the search domain set may also mean attempting to detect candidate PDCCHs in the search domain set, or attempting to detect DCI formats in the search domain set. It may be either a good idea or an attempt to detect PDCCH in the control resource set. Alternatively, you could try to detect candidates for PDCCH in the control resource set. Alternatively, an attempt may be made to detect the DCI format in the control resource set.

[0209] A search space set is defined as a set of candidate PDCCHs. A search space set may be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. Terminal device 1 may be part 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. We attempt to detect PDCCH candidates in all cases.

[0210] The Type 0PDCCH common search region set is used as the common search region set for index 0. It is permissible to stay there. The Type 0PDCCH common search area set is the common search area at index 0. It's fine as a set.

[0211] The CSS set is a collective term for the Type 0 PDCCH common search area set, Type 0a PDCCH common search area set, Type 1 PDCCH common search area set, Type 2 PDCCH common search area set, and Type 3 PDCCH common search area set. The USS set is the UE individual PDCCH search area set. It is also called by this name.

[0212] A set of search domains is associated with (contains, corresponds to) a set of control resources. The index of the control resource set associated with the search domain set may be indicated by a higher-level parameter.

[0213] For a given set of search domains, some or all of 6A through 6C may be represented by at least the upper layer parameters. 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 6C) PDCCH monitoring offset

[0214] A monitoring occasion for a certain set of search regions occurs when that set of search regions The leading OFDM symbol of the associated control resource set may correspond to the OFDM symbol in which it is located. The monitoring opportunity for a search region set may correspond to the resources of the control resource set associated with the search region set, starting from the leading OFDM symbol of that control resource set. The monitoring opportunity for the search region set is given based on at least some or all of the monitoring interval of the PDCCH, the monitoring pattern of the PDCCH in the slot, and the monitoring offset of the PDCCH.

[0215] Figure 8 shows an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. In Figure 8, search area set 91 and search area set 92 are set in primary cell 301, search area set 93 is set in secondary cell 302, and search area set 94 is set in secondary cell 303.

[0216] In Figure 8, the white monochrome blocks in primary cell 301 represent search region set 91, the black monochrome blocks in primary cell 301 represent search region set 92, the blocks in secondary cell 302 represent search region set 93, and the blocks in secondary cell 303 represent search region set 94.

[0217] The monitoring interval for the search area set 91 is set to 1 slot, and the monitoring of the search area set 91 The offset is set to slot 0, and the monitoring pattern for the search area set 91 is [1,0 It is set to [0,0,0,0,0,1,0,0,0,0,0,0]. In other words, it searches The monitoring opportunities in search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0218] The monitoring interval for the search area set 92 is set to 2 slots, the monitoring offset for the search area set 92 is set to 0 slots, and the monitoring pattern for the search area set 92 is [1,0 It is set to [0,0,0,0,0,0,0,0,0,0,0,0,0]. In other words, it is searched The monitoring opportunities in search area set 92 correspond to the leading OFDM symbol (OFDM symbol #0) in each even-numbered slot.

[0219] The monitoring interval for the search area set 93 is set to 2 slots, the monitoring offset for the search area set 93 is set to 0 slots, and the monitoring pattern for the search area set 93 is [0,0 It is set to [0,0,0,0,0,1,0,0,0,0,0,0]. In other words, it searches The monitoring opportunities in search area set 93 correspond to the 8th OFDM symbol (OFDM symbol #7) in each of the even-numbered slots.

[0220] The monitoring interval for the search area set 94 is set to 2 slots, the monitoring offset for the search area set 94 is set to 1 slot, and the monitoring pattern for the search area set 94 is [1,0 It is set to [0,0,0,0,0,0,0,0,0,0,0,0,0]. In other words, it is searched The monitoring opportunities in search area set 94 correspond to the leading OFDM symbol (OFDM symbol #0) in each odd-numbered slot.

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

[0222] The Type 0aPDCCH common search area set is SI-RNTI (System Information-Radio Network). CRC (Cyclic Redundancy Check) scrambled by a Temporary Identifier It may be used, at least, for DCI formats that involve sequences.

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

[0224] The Type 2 PDCCH common search region set is used for the DCI format with a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier). That's fine.

[0225] The Type 3 PDCCH common search region set is used for the DCI format with a CRC sequence scrambled by C-RNTI (Cell-Radio Network Temporary Identifier). That's good too.

[0226] The UE individual PDCCH search region set may be used for the DCI format with a CRC sequence scrambled by C-RNTI.

[0227] In downlink communication, terminal device 1 detects the downlink DCI format. The detected downlink DCI format is used at least for resource allocation on the PDSCH. The detected downlink DCI format is also called the downlink assignment. Terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource shown in DCI format, the HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block contained in the PDSCH) is reported to the base station device 3.

[0228] In uplink communication, terminal device 1 detects the uplink DCI format. The DCI format that is provided will be used at least for resource allocation in PUSCH. The detected uplink DCI format is also referred to as an uplink grant. Terminal device 1 transmits the PUSCH.

[0229] In configured grant scheduling, PUSCH is used in the scheduler The uplink grant to be set is configured for each transmission cycle of the PUSCH. When the PUSCH is scheduled using the uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured for the scheduling.

[0230] The PUSCH transmission may correspond to the configured scheduling type 1 or the configured scheduling type 2. That is, the configured scheduling is The scheduling type may be either scheduling type 1 or scheduling type 2. The PUSCH transmission for scheduling type 1 may be set semi-statically. For example, the PUSCH transmission for scheduling type 1 may operate in response to the reception of a certain upper-layer parameter. The `rrc-ConfiguredUplinkGrant` may also be configuredGrantConfig. For example, configuredGrantConfig may include rrc-ConfiguredUplinkGrant. The PUSCH transmission is for the uplink grant in DCI. It may operate without detection.

[0231] The PUSCH transmission for scheduling type 2 is semi-persistently. It may be scheduled by an uplink grant. For example, it may be scheduled by an uplink grant. An uplink grant is an activated DCI, or It may be included in the valid activation DCI. For example, a PUSCH transmission of scheduling type 2, which is set after receiving a certain upper-layer parameter, may be scheduled by a certain uplink grant. The certain upper-layer parameter is configuredGrantConfig For example, configuredGrantConfig does not need to include rrc-ConfiguredUplinkGrant.

[0232] System frame number (SFN) n f This is added to the wireless frame. The number may be an index for wireless frames. The system frame number may consist of 10 bits. At least a portion of the system frame number is The system frame number may be notified by the MIB. For example, 6 bits of the 10-bit system frame number (e.g., 6 most significant bits) may be notified by the MIB. At least a portion of the system frame number may be determined based on the PBCH for transmitting the MIB. For example, the 10-bit system frame number may be notified by the MIB. Four bits of the stem frame number (for example, the four least significant bits) may be transmitted in the PBCH transport block as part of the channel coding.

[0233] PDCCH-Config may be a dedicated upper-layer parameter. PDCCH-Config is for PDCCH You may set parameters. Multiple (for example, up to 3) CORESETs may be configured in PDCCH-Config. A CORESET ID may be set for a single CORESET. In each CORESET, one CORESET pool index may be set up.

[0234] PDSCH-Config may be a dedicated upper-layer parameter. PDSCH-Config is for PDSCH You can also set the parameters.

[0235] Multiple PDCCH candidates (PDCCH candidate(s)) are selected based on the upper-level parameters. When related to a set of search regions, one PDCCH candidate is used. This one PDCCH candidate has two Among the PDCCH candidates, the one that starts earlier may also be selected. The upper-level parameter may be searchSpaceLinking.

[0236] At least two transmission methods may be supported for PUSCH. For example, codebook-based transmission may be one of the transmission methods for PUSCH. For example, non-codebook-based transmission may be one of the transmission methods for PUSCH. The upper layer parameter may provide either codebook transmission or non-codebook transmission. For example, if 'codebook' is set for the upper layer parameter, terminal device 1 may be configured for codebook transmission. For example If 'nonCodebook' is set for the upper-layer parameter, terminal device 1 may be configured to send non-codebook messages. The upper-layer parameter may be txConfig. The upper-layer parameter may be usage. For example, if the upper-layer parameter is not set... In this case, terminal device 1 does not need to expect that it will be scheduled according to either DCI format 0_1 ​​or DCI format 0_2. If PUSCH is scheduled according to DCI format 0_0, the transmission of PUSCH may be based on at least one antenna port. If PUSCH is scheduled according to DCI format 0_0, even if the first TA is used Often, a second TA is not required.

[0237] In codebook transmissions, PUSCH may be scheduled by DCI format. The DCI format may be any of DCI format 0_0, DCI format 0_1, or DCI format 0_2. In codebook transmissions, PUSCH may be set to be transmitted semi-statically. Terminal device 1 may determine one or more precoders for PUSCH transmission. For example, the precoder may be determined based on at least some or all of the SRI (SRS Resource indicator), TPMI (Transmitted Precoding Matrix Indicator), and Transmission rank (or rank). For example, the SRI may be the DCI fee of one or two SRS resource indicators. It may be provided by the rud. For example, TPMI may be provided by the DCI field of 1 or 2 precoding information. For example, transmit rank may be provided by the DCI field of layer number (transmit layer number). SRI is first The TPMI and transmit rank may be provided by the second upper layer parameter. The first upper-layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2. The second upper-layer parameter may be precodingAndNumberOfLayers or precodingAndNumberOfLayers2.

[0238] The SRS resource set applied to PUSCH may be determined based on higher-level parameters. PUSCH is scheduled according to DCI format 0_1 ​​or DCI format 0_2. It may also be set to srs-ResourceSetToAddModList or srs-ResourceSetToAddModeListDCI-0-2. The higher-level parameter may also be a higher-level parameter set in SRS-Config.

[0239] If the upper-level parameter usage is set to 'codebook', then one or two SRS resource sets will be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 The higher-level parameter usage may be set in the higher-level parameter SRS-ResourceSet.

[0240] When one SRS resource set is configured, the SRI and TPMI may be given by the DCI field. The TPMI may be used to indicate the precoder. The precoder has v It may be applied across layers. If multiple SRS resources are configured, one SRS resource may be selected by the SRI. The transmit precoder (precoder) may be selected from the codebook (uplink codebook). For example, the codebook may have the number of antenna ports. The number of antenna ports is determined by the upper layer parameter nrofSRS-Ports and They may be the same. If the upper-level parameter txConfig is set to 'codebook', terminal device 1 may have at least one SRS resource configured. The indicated SRI is determined by the SRI. This may also relate to the transmission of SRS resources that are identified as such.

[0241] If two SRS resource sets are configured, one or two SRIs and one or two TPMIs are , or may be given by the DCI field. For example, the DCI field may be the SRS resource index The DCI field may be either or both of the DCI fields for precoding information and layer count. Terminal device 1 may apply the indicated SRI and TPMI to one or more push repetitions. The TA applied to one or more push repetitions may be the same. The TPMI indicates the precoder based on the code point of the SRS resource set indication. It may be used for the following purposes. The precoder may be applied to layers 0 through v-1. The precoder may correspond to SRS resources selected by the SRI. Multiple SRS Resources may be configured for the applicable SRS resource set. In one or two TPMIs, the transmit precoder (precoder) is the codebook (uplink codebook) or They may be selected. When two SRIs are specified, terminal device 1 will select the two specified SRSs. You can expect the number of antenna ports for the source to be the same. The number of antenna ports may be provided by higher-layer parameters.

[0242] In codebook transmission, terminal device 1 may determine a codebook subset. For example, the codebook subset may be determined based at least on TPMI. The codebook subset may also be determined in response to the reception of a certain upper-layer parameter, which is codebookSubset or codebookSubsetDCI-0-2. It is also acceptable to do so. A certain higher-level parameter may be set to one of the following: 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent'. For example If at least one of the higher-level parameters is set to 'partialAndNonCoherent' A subset of codebooks associated with 2-port SRS resources (SRS resources with 2 ports) may be 'nonCoherent'. For example, a codebook may contain at least one SRS resource with 4 ports and at least one SRS resource with 2 ports.

[0243] Terminal device 1 may report its UE capability. If terminal device 1 reports a UE capability of sending 'partialAndNonCoherent', terminal device 1 does not expect a subset of codebooks to be set with 'fullyAndPartialAndNonCoherent'. That's fine.

[0244] If terminal device 1 reports UE capability for 'nonCoherent' transmission, terminal device 1 does not need to expect that a subset of codebooks with 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent' will be configured.

[0245] If the number of antenna ports indicates that the maximum number of SRS antenna ports to be configured is 2, terminal device 1 does not need to expect that a higher-layer parameter set to 'partialAndNonCoherent' is configured. The higher-layer parameter may be codebookSubset or codebookSubsetForDCI-Format0-2. The number of antenna ports may also be determined by the higher-layer parameter nrofSRS-Ports.

[0246] In codebook submission, one SRS resource may be determined from the SRS resource set based on the SRI, except when the first upper-level parameter is set to 'fullpowerMode2'. The maximum number of SRS resources to be set for codebook submission may be 2. The higher-level parameter may be ul-FullPowerTransmission. DCI may instruct the transmission of SRS resources. For example, if aperiodic SRS is configured, DCI may The SRS request field may instruct the transmission of a non-periodic SRS resource. Terminal device 1 does not need to expect that the first upper-layer parameter, set to 'fullpowerMode1', and the second upper-layer parameter, set to 'fullAndPartialAndNonCoherent', will be set.

[0247] Terminal device 1 uses DCI format or SRS as instructed by higher-layer parameters. The same one or more antenna ports are used as one or more SRS ports in the source. You may also send a PUSCH signal. For example, the SRS port is an antenna port for sending PUSCH signals. It may be the same as the other. The DMRS antenna port may be determined according to the DMRS port ordering.

[0248] If multiple SRS resources are configured by an SRS resource set, terminal device 1 will... You can expect the upper-layer parameter nrofSRS-Ports to have the same value for your SRS resources. The SRS resource set is the upper-layer parameter nrofSRS-Ports which has 'codebook' set. The upper-level parameter SRS-ResourceSet may also have a meter usage.

[0249] When 'fullpowerMode2' is set for the upper-level parameter, one or more SRS resources with the same or different number of SRS ports in a single SRS resource set It may be set. If 'fullpowerMode2' is set for the higher-level parameter, up to two different spatial relations may be set for all SRS resources in one SRS resource set. If 'fullpowerMode2' is set for the higher-level parameter, up to two or four SRS resources may be set in one SRS resource set. Also, up to eight SRS resources may be set in one SRS resource set. The SRS resource set is set to 'codebook'. This may also be an SRS resource set with upper-level parameter usage. The two spatial relationships are two uplink timings (timing advance: TA), or two The uplink timing ID (Timing Advance group ID: TAG ID), or subTAG ID may be associated with the two SRS resource sets, which are two TAs. It may be related to two subTAG IDs, or two TAG IDs.

[0250] For non-codebook submissions, PUSCH is DCI format 0_0, DCI format 0_1, or , scheduling may be done according to DCI format 0_2. Terminal device 1 may determine the precoder and transmit rank of PUSCH based on the SRI. For example, when multiple SRS resources are configured, the SRI is given by one or two SRS resource indications in DCI. This may also be the case. For example, SRI may be given by a higher-level parameter. The SRS resource set applied to PUSCH may be defined by an entry in the higher-level parameter. The upper-level parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0251] Terminal device 1 may use one or more SRS resources for SRS transmission. The maximum number of SRS resources in a single SRS resource set may be transmitted to base station device 3 as UE capability (terminal capability). SRS resources are configured for simultaneous transmission of the same OFDM symbol. This may be done. Multiple SRS resources sent simultaneously may occupy the same resource block. It is also possible that one SRS port is configured for each SRS resource. One or two SRS resource sets may be configured in the upper-level parameter srs-ResourceSetToAddModList, where the upper-level parameter usage in the upper-level parameter SRS-ResourceSet is set to 'nonCodebook'. If two SRS resource sets are configured, one or two SRIs may be provided by the DCI field. The DCI field is a reference for the two SRS resources. It may also be a DCI field.

[0252] Terminal device 1 may apply the instructed SRI to one or more PUSCH repetitions. For example, according to the SRS resource set of the PUSCH repetition, terminal device 1 may apply the instructed SRI to one Alternatively, it may be applied to multiple PUSCH iterations. Set for non-codebook submission. The maximum number of SRS resources per SRS resource set may be 4. The maximum number of SRS resources per SRS resource set configured for transmission is 8, even if Good. Each of the one or two SRIs indicated is an SRS resource identified by the SRI. This may also relate to the latest transmission of the SRS resources in the set. The SRS transmission may precede the PDCCH that transmits the SRI. A different number of SRS resources may be set in the two SRS resource sets. Terminal device 1 does not need to expect this.

[0253] Terminal device 1 may apply “indicated TCI states” to one or more PUSCH iterations. For example, according to the SRS resource set instruction field or the TRP instruction field, terminal device 1 may apply “indicated TCI states” to one or more PUSCH iterations. Each of one or two “indicated TCI states” may be associated with the latest instruction of a TCI state indicated by a first DCI format. The first DCI format may be sent before the second DCI format that schedules the PUSCH iterations. A single “indicated TCI state” may be associated with one TA, one subTAG ID, or one TAG ID.

[0254] Multiple PDCCH candidates (PDCCH candidate(s)) are selected based on the upper-level parameters. When related to a set of search regions, one PDCCH candidate is used. This one PDCCH candidate has two Among the PDCCH candidates, the one that starts earlier may also be selected. The upper-level parameter may be searchSpaceLinking.

[0255] In non-codebook transmissions, terminal device 1 may calculate the precoder. For example, the precoder used for SRS transmission may be calculated based on the measurement of NZP CSI-RS resources. It may be calculated. One NZP CSI-RS resource is configured for one SRS resource set. It is also possible that one SRS resource set has 'nonCodebook' set on it. This may also be an SRS resource set with a stratification parameter.

[0256] If an aperiodic SRS resource set is configured, the NZP-CSI RS may be indicated via the SRS request field. The SRS request field may be one of the DCI fields in DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2. The first upper layer parameter is aperiodic SRS. The triggering state may indicate the association between the SRS resource set. The first upper-layer parameter, the SRS resource to be triggered, srs-ResourceSetId, and csi-RS may be set in the upper-layer parameter SRS-ResourceSet. The upper-layer parameter csi-RS may indicate NZP-CSI-RS-ResourceId. The upper-layer parameter SRS-ResourceSet related to the SRS request may be defined by an entry in a list that is an upper-layer parameter. The list that is an upper-layer parameter may be the upper-layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. Terminal device 1 does not need to expect to update the precoding information (SRS precoding information). For example, if the gap from the last OFDM symbol of the received non-periodic NZP-CSI-RS resource to the first OFDM symbol of the non-periodic SRS transmission is 42 OFDM symbols or less, terminal device 1 will not update the precoding information You don't need to expect updates.

[0257] If an aperiodic SRS is set up in relation to an aperiodic NZP CSI-RS resource, the presence of the CSI-RS is considered. This may be indicated by the SRS request field. If the value of the SRS request field is not '00', and the scheduling DCI is cross-carrier scheduling or cross-bandwidth part scheduling. If not used for scheduling, the presence of CSI-RS may be indicated by the SRS request field.

[0258] Terminal device 1 may perform one-to-one mapping. One-to-one mapping may be mapping from SRI to the DMRS port and the corresponding PUSCH layer. A number of PUSCH layers from 0 to v-1 may be provided, where v is the number of layers. The number of layers is set by the upper layer parameters. This may be done. The number of layers may be indicated by DCI. Terminal device 1 may transmit PUSCH using the same antenna port as the SRS port. For example, the SRS port in an SRS resource indicated by 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 submissions, spatial relation information (info) for SRS resources and the higher-level parameter SRS-ResourceSet for SRS resource sets are used. Terminal device 1 expects both the upper-level parameter associatedCSI-RS and the other parameter to be set. Waiting is not necessary. Spatial relation information may be determined by higher-level parameters. Spatial relation information may also be the higher-level parameter `spatialRelationInfo`. (Non-codebook) During transmission, if at least one SRS resource is configured in an SRS resource set with a higher-level parameter set to 'nonCodebook', terminal device 1 may be scheduled using DCI format 0_1 ​​or DCI format 0_2. Spatial relationship Information may be determined by the TCI state. Spatial relational information may be determined by the “indicated TCI state”. When spatial relational information is determined by the TCI state, spatial relation The information may be associated with a single subTAG ID.

[0260] One or more SRS resource sets (Sounding Reference Signal resource sets) are, This may be set by the higher-level parameters. The first higher-level parameter may be SRS-ResourceSet or SRS-PosResourceSet. Each SRS resource set contains K SRS resources A value may be set. K may be an integer greater than or equal to 1. The maximum value of K may be indicated by UE capability. The maximum value of K may be 16. The adaptability of the SRS resource set may be set in a second upper-layer parameter. The second upper-layer parameter is usage. It is acceptable. For example, if 'beamManagement' is set for the second higher-level parameter. If so, in each of the one or more SRS resource sets, one SRS resource will be sent. This may also be the case. For example, if an SRS resource is sent in a given time instance This is also acceptable. Multiple SRS resources in different SRS resource sets may be sent simultaneously. For example, different SRS resource sets of the same BWP may be sending the same time-domain behavior. Multiple SRS resources with the same properties may be sent simultaneously.

[0261] In aperiodic SRS, to select at least one from the set of SRS resources, At least one DCI field may be used.

[0262] If two SRS resource sets (the first SRS resource set and the 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 assignment may be applied across K consecutive slots, and PUSCH is one It may be restricted to the transmission layer. Terminal device 1 may repeat transport blocks across consecutive K slots. Code point of the SRS resource set instruction field If “00” is indicated, the first SRS resource set may be associated with consecutive K slots. If the code point “01” in the SRS resource set indication field is indicated, The second SRS resource set may also be associated with consecutive K slots. If the code point “10” in the indicated field is indicated, the first SRS resource set and the second The two SRS resource sets may also be associated with consecutive K slots. For example, if 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 cyclic mapping is enabled, the first and second SRS resource sets may be applied to the first and second slots of consecutive K slots, respectively, and the same SRS resource set mapping may apply. The pattern may continue to the remaining slots of the consecutive K slots. If K > 2 and sequential mapping is enabled, the first SRS resource set may be applied to the first and second slots of the consecutive K slots, and the second SRS resource set may be applied to the third and fourth slots of the consecutive K slots, or The same SRS resource set mapping pattern may continue to the remaining slots of the consecutive K slots. Code point "11" in the SRS resource set instruction field is indicated. In this case, the first SRS resource set and the second SRS resource set are in consecutive K slots. They may be related. 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 cyclic mapping is enabled, the second and first SRS resource sets may be applied to the first and second slots of consecutive K slots, respectively. Furthermore, the same SRS resource set mapping pattern may continue to the remaining slots of the consecutive K slots. If K > 2 and sequential mapping is enabled, the second SRS resource set may be applied to the first and second slots of the consecutive K slots, and the first SRS resource set may be applied to the third and fourth slots of the consecutive K slots, and the same SRS resource set mapping pattern may continue This may continue to the remaining slots of the consecutive K slots. The SRS resource set indicator field may be included in either or both of DCI format 0_1 ​​and DCI format 0_2. Two SRS resource sets may be configured with usage in SRS-ResourceSet set to 'codebook' or 'noncodebook'. You do not need to expect the applied TA to change in consecutive K slots.

[0263] The SRS resource set instruction field may determine one or two TCI states. For example, if the SRS resource set instruction field indicates "00" or "01", one TCI state may be used. For example, if the SRS resource set instruction field indicates "10" or "11", two TCI states may be used. The one or two TCI states may be either or both of the "indicated UL TCI state (UL-TCIState)" and the "indicated DL / Joint TCI state (DLorJoint-TCIState)". That's fine.

[0264] The SRS resource set instruction field indicates either or both of the first and second TCI states. It may be decided that the first TCI state is used. For example, if the SRS resource set instruction field indicates "00", the first TCI state may be used. If the indicator field indicates "01", a second TCI state may be used. For example, if the SRS resource set indicator field indicates "10" or "11", the first TCI state The state and the second TCI state may also be used.

[0265] Terminal device 1 may have STxMP (Simultaneous Transmission with Multi panel) applied to it. STxMP (Simultaneous Transmission with Multi panel) may be applied to one or both of the first uplink physical channel and the second uplink physical channel. When STxMP is applied, terminal device 1 may have STxMP applied to the first uplink physical channel and the second uplink physical channel The physical channels may be transmitted simultaneously. When STxMP is applied, terminal device 1 may transmit the first uplink physical channel and the second uplink physical channel on the same time and frequency resources. When STxMP is applied, the first uplink physical channel The first CDM (Code Division Multiplexing) on ​​the first DMRS port designated for the channel. The group may be different from the second CDM group of the second DMRS port directed for the second uplink physical channel. The first CDM group and the second CDM group are the same. This is not expected. Either the first DMRS port or the second DMRS port, or both, may be indicated by the antenna port field in one DCI format. The first CDM group and the second CDM group may be indicated by the antenna port field. If STxMP is applied, the first uplink physical channel and the second uplink A physical channel may correspond to a single precoding matrix. This single precoding matrix may be determined by the TPMI field in the DCI format. When STxMP is applied, the first uplink physical channel corresponds to the first TCI state, and Furthermore, the second uplink physical channel may correspond to the second TCI state. The first and second TCI states may be indicated by the TCI (Transmission Configuration Indication) field in DCI format 1_1 / 1_2. When STxMP is applied, the first uplink physical channel may correspond to the first uplink transmit space filter (UL Tx Spatial filter), and the second uplink physical channel may correspond to the second uplink transmit space filter. The first uplink transmit space filter may be determined by the SRI (SRS resource indication) field in DCI format. The value may be determined by the Second SRI field in the DCI format.

[0266] When STxMP is applied, the first transmit layer corresponds to the first uplink physical channel. The number (rank number) is the second transmit layer number (rank) corresponding to the second uplink physical channel. The difference between the number of first and second transmission layers. (The number may be the same or different.) It is not required that the number be 2 or greater. When STxMP is applied, the first uplink physical channel and the second uplink physical channel may not be fully overlapping. Good. When STxMP is applied, the first uplink physical channel and the second uplink physical Channels are not expected to partially overlap. When STxMP is applied, the first transport block corresponding to the first uplink physical channel is not expected to be different from the second transport block corresponding to the second uplink physical channel. When STxMP is applied, the first uplink physical channel Nell and the second uplink physical channel do not necessarily have to be expected to transmit two transport blocks (codewords). When STxMP is applied, it is not necessary to expect the upper layer parameter sfnSchemePusch to be set for either or both of the first uplink physical channel and the second uplink physical channel. If this is set, the DMRS port of a PUCCH may have multiple (e.g., two) TCI state reference signals and QCL. If the upper layer parameter sfnSchemePucch is set for a PUCCH, the DMRS port of that PUCCH may have multiple (e.g., two) TCI state reference signals and QCL.

[0267] The application of STxMP may be set by a higher-layer parameter. For example, the application of STxMP for PUSCH may be set by a dedicated higher-layer parameter for PUSCH. For example, the application of STxMP for PUCCH may be set by a dedicated higher-layer parameter for PUCCH. This may be set by the level parameters. The application of STxMP may be indicated by the DCI format.

[0268] The PUSCH-MTRP method may also be a general term encompassing PUSCH iterations when cyclic mapping is enabled, PUSCH iterations when sequential mapping is enabled, and STxMP. For example, the application of the PUSCH-MTRP method may be any one of the following: cyclic mapping is enabled, sequential mapping is enabled, or STxMP is applied.

[0269] Multiple TRPs (Transmission Reception Points, or Transmit / Receive Points) are used. It may be done. The base station device 3 may consist of multiple TRPs (Multi-TRP). The terminal device 1 may be scheduled by two TRPs in one serving cell. In Multi-TRP, either single-DCI or multi-DCI operating mode may be used. In Multi-TRP, uplink control may be completed at the MAC layer and physical layer. In Multi-TRP, MAC Downlink control may be completed at the layer and physical layer. In Single-DCI mode, terminal device 1 may be scheduled by the same DCI for two TRPs. In Multi-DCI mode, terminal device 1 may be scheduled by independent DCIs from each TRP. In Multi-DCI mode, each TRP in a Multi-TRP may be identified by TRP information. That is, one TRP in a Multi-TRP may be identified by one TRP piece of information. i. TRP information may be used to select one TRP. Also, an index of the CORESET resource pool may be associated with one Control Resource Set (CORESET). Terminal device 1 may send PUSCH based on the index of the CORESET resource pool. Terminal device 1 may send PDCCH and PDSCH based on the index of the CORESET resource pool. TRP information is the CORESET pool index. Alternatively, TRP information may be provided by the TRP indicator field.

[0270] Terminal device 1 may form a beam (beamforming). For example, terminal device 1 may transmit radio waves (electromagnetic waves) in a specific spatial direction by beamforming. For example, terminal device 1 may receive radio waves from a specific spatial direction by beamforming. The terminal device 1 may have and may use one or more antennas for either or both of transmitting and receiving radio waves. Directional radio waves may be referred to as beams. Information related to beams may be referred to as beam information. For example, beam information may be a specific spatial direction. For example, beam information may be the direction of arrival of the radio waves. Beam information may be TCI status. Beam information may be uplink transmit space fill It may also be a TA. The beam information may be an SRS resource instruction. The beam information may be a QCL assumption or QCL relationship.

[0271] Terminal device 1 may have the upper-layer parameter TCI-State set. For example, terminal device 1 A list may be set in the upper layer parameter PDSCH-Config. A list may contain up to M upper layer parameters TCI-State. A list may also contain up to M upper layer parameters TCI-State. Terminal device 1 may have a list set to decode (receive) the PDSCH according to the PDCCH with DCI. M may depend on the terminal capability (UE capability). For example, M may be terminal capability maxNumberConfiguredTCIState It may depend on PerCC. TCI-State may also be referred to as TCI state.

[0272] Each TCI-State (i.e., the upper-level parameter TCI-State) may include parameters for setting QCL (QCL relationship: Quasi co-location relationship). The QCL relationship is 1 or 2 Relationship between two downlink reference signals (downlink physical signals) and the PDSCH's DMRS (DMRS port). The QCL relationship may also be a relationship between one or two downlink reference signals (downlink physical signals) and the DMRS (DMRS port) of the PDCCH. Link reference signal (downlink physical signal) and CSI-RS (CSI-RS port) for one CSI-RS resource. The relationship may also be as follows. For example, the QCL relationship between channel / signal A and channel / signal B is as follows: Channel / signal A may also represent channel / signal B and QCL. If channel / signal B and QCL, then the first TA for channel / signal A and for channel / signal B The second TA can be the same.

[0273] QCL relationships are either or both of the upper layer parameter qcl-Type1 and the upper layer parameter qcl-Type2. It may be set by the method. For example, the QCL relationship is the upper layer parameter qcl-Type1 for the first downlink reference signal (DL RS) and the upper layer parameter for the second downlink reference signal The first downlink reference signal and may be set by either or both of the following. If the second downlink reference signal is different, the QCL type of qcl-Type1 does not have to be the same as the QCL type of qcl-Type2. The QCL type corresponding to each downlink reference signal may be given by the upper-layer parameter qcl-Type in the upper-layer parameter QCL-Info. The QCL type may be one of typeA, typeB, typeC, and typeD.

[0274] Terminal device 1 may have the upper-layer parameter DLorJointTCIState set. For example, terminal device 1 may have one list set in the upper-layer parameter PDSCH-Config. One list may contain up to 128 upper-layer parameters DLorJointTCIState(TCIState). One list is a list of up to 128 upper-layer parameters DLorJointTCIState(TCIState). It may also be the case that one list is set to provide one reference signal. The upper layer parameter DLorJointTCIState(TCIState) may be set to provide one reference signal. One reference signal may be the DMRS of PDSCH and the QCL for the DMRS of PDCCH. One reference signal may be the reference signal for CSI-RS. One list may be set to provide one reference. Upper layer parameter The DLorJointTCIState may be set to provide one reference. The reference may be used to determine the uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter is for PUSCH, PUCCH, and SRS. It may be used for the following: That is, one reference may be provided to determine the uplink transmit space filter for PUSCH, PUCCH, and SRS. The TCI state may be DLorJointTCIState(TCIState). DLorJointTCIState is the DL / Joint TCI state, Alternatively, it may be called a Unified TCI state. One list may be dl-OrJoint-TCIStateList.

[0275] Terminal device 1 may have the upper-layer parameter UL-TCIState set. For example, terminal device 1 One list may be set in the higher-level parameter BWP-UplinkDedicated. One list may contain up to 64 upper-layer parameters UL-TCIState. One list may also contain up to 64 upper-layer parameters UL-TCIState. Each UL-TCIState ( Alternatively, the UL-TCIState setting may include parameters for setting one reference signal. For example, each UL-TCIState may include one parameter for setting one reference signal to determine PUSCH, PUCCH, and uplink transmit space filtering for part or all of the SRS. One list may be the upper layer parameter ul-TCI-StateList. i. The TCI state may also be UL-TCIState. UL-TCIState is UL TCI state, or unified This may also be referred to as a TCI state.

[0276] UL-TCIState may be a higher-layer parameter TCI-UL-State. UL-TCIState may be set by a 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] If DLorJointTCIState or UL-TCIState is set, terminal device 1 may send a PUSCH according to the spatial relation. For example, the spatial relation is one reference signal The relationship may also be based on the RS (Row Speed) number. For example, one reference signal may be the uplink transmit sky It may also be a reference signal for determining the inter-filter. One reference signal may be a reference signal set by qcl-Type where typeD is set in the “indicated TCI state”. The "specified TCI state" may be the specified DLorJointTCIState or the specified UL-TCIState. The Reference RS in the specified DLorJointTCIState may be the CSI-RS resource in the higher-level parameter NZP-CSI-RS-ResourceSet. The Reference RS in the specified UL-TCIState may be the CSI-RS resource in the NZP-CSI-RS-ResourceSet. This may also be the case. The indicated UL-TCIState is a TCI state, UL TCI state, or unspecified TCI state as indicated by DCI format 1_1 or DCI format 1_2. It may be a single TCI state. The indicated DLorJointTCIState (Indicated DLorJointTCIState) may be a TCI state, DL / Joint TCI state, or unified TCI state as 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) are one BWP of one component carrier It may be set in DLorJointTCIState or UL-TCIState if 1 If not present in one BWP, terminal device 1 may apply the DLorJointTCIState setting or the UL-TCIState setting from the reference BWP.

[0279] Terminal device 1 has both the first upper layer parameter and the second upper layer parameter set. You do not need to expect this. The first upper layer parameter may be any of TCI-State, SpatialRelationInfo, and PUCCH-SpatialRelationInfo. The second upper layer parameter The parameter may be either DLorJointTCIState or UL-TCIState. When a TCI-State is set in any component carrier in a certain list In addition, the second upper layer parameter does not need to be set for any component carrier within the same band in the given list. The given list is upper layer parameter simultaneousTCI-UpdateList1, upper layer parameter simultaneousTCI-UpdateList2, upper layer parameter This may be set by the parameter simultaneousSpatial-UpdatedList1 or the higher-level parameter simultaneousSpatial-UpdatedList2. If the first higher-level parameter is set, it is not expected that two TAs will be provided in one serving cell.

[0280] Terminal device 1 may receive an activation command. The code is used to map up to eight "TCI states, and one or both of a pair of TCI states" to code points in the DCI field 'Transmission Configuration Indication'. It may be done. A pair of TCI states consists of one TCI state for multiple downlink channels / signals (DL TCI state) and one TCI state for multiple uplink channels / signals (UL TCI state). , may be accompanied by. Multiple downlink Channels / signals are PDSCH, PDCCH, and CSI-RS It may be part or all of. Multiple uplink channels / signals are PUSCH, PUCCH, And, it may be part or all of the SRS. DCI (DCI format) is one or more It may consist of DCI fields. For example, DCI (DCI format) may consist of a TCI field ('Transmission Configuration Indication' field).

[0281] If the first set of one or more TCI state IDs is activated in the second set, The first set is suitable for the downlink BWP in the component carrier as indicated. It may be used. If the first set of one or more TCI state IDs is activated in the third set, the first set may be applied for the downlink BWP and uplink BWP in the indicated component carrier. The second set may be applied for one or more components A third set may be one or both of the component carrier and one or more downlink BWPs. A third set may be some or all of the component carrier, one or more downlink BWPs, and one or more uplink BWPs.

[0282] The activation command is one or both of DLorJointTCIState and UL-TCIState When mapping to the TCI code point (the code point of the DCI field 'Transmission Configuration Indication'), terminal device 1 may apply either or both of the indicated DLorJointTCIState and the indicated UL-TCIState.

[0283] Terminal device 1 provides the specified DLorJointTCIState or the specified UL-TCIState. You may receive DCI format 1_1 / 1_2. DCI format is downlink assignment It does not require an assignment. For example, if DCI format 1_1 / 1_2 does not involve a downlink assignment, terminal device 1 will know that CS-RNTI is used to scramble the CRC for DCI, that all RV (Redundancy version) values ​​are 1, and that all MCS values ​​are 1. It may also be assumed that NDI is 0, that all values ​​are set to 0 for FDRA type 0, and that all values ​​are set to 1 for FDRA type 1, or some or all of these.

[0284] Terminal device 1 may receive a DCI format including a TRP instruction field. The TRP instruction field selects one or more TCI states from one or more “indicated TCI states”. This may be done. The TCI state may be referred to as the “applied TCI state”. If one TCI state is selected, one TCI state may be applied to PDSCH, PUSCH, PUCCH, CSI-RS, or SRS scheduled by the DCI format. If two TCI states are selected If so, two TCI states may be applied to a 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 DCI.

[0285] N conf Individual TCI states may be set. For example, N conf The TCI states may be set in the wireless resource control layer. For example, N conf The TCI state may be set by higher-level parameters. conf Each of these TCI states is referred to as the “configured TCI state”. It's okay to do that. conf This can be an integer from 1 to 128. If the TCI state is a DL TCI state or a Joint TCI state, then N conf This can be an integer from 1 to 128. TCI state If it is in UL TCI state, then N conf This can be an integer from 1 to 64.

[0286] Nact The individual TCI states may be activated. For example, N act The number of TCI states is N conf This may be some or all of the TCI states. For example, N act Each TCI state corresponds to the media access control layer. It may be activated in N. act Each TCI state is activated by MAC CE. It's fine. act Each of these TCI states may also be referred to as an “activated TCI state.” act This can be an integer from 1 to 32.

[0287] N ind The number of TCI states may be specified. For example, N ind The number of TCI states is N act Individual TCI states It may be part or all of N. ind Each TCI state is indicated at the physical layer. It is also acceptable. For example, N ind Each TCI state may be indicated by a DCI. For example, N ind Each TCI state may be indicated by the TCI field in DCI. ind Each of these TCI states may also be referred to as the “referred TCI state.” The “referred TCI state” is The “indicated TCI condition” may apply to PDSCH, PDCCH, and CSI-RS. The “indicated TCI condition” may apply to PUSCH, PUCCH, and SRS. The “indicated TCI condition” may apply to PDSCH, PDCCH, CSI-RS, PUSCH, PUCCH, and SRS. N ind This can be an integer from 1 to 4.

[0288] N app Each TCI state may be indicated or applied. For example, N app The number of TCI states is N ind This may be some or all of the TCI states. For example, Napp The individual TCI states may be indicated at the physical layer. For example, N app Each TCI state may be indicated by a DCI. For example, N app Each TCI state is indicated by the TRP indication field in DCI. It's okay to do that. app Each of these TCI states may also be referred to as the “applicable TCI state”. app This can be 1 or 2.

[0289] Terminal device 1 may receive higher layer settings. Terminal device 1 is set to "TCI state". After it is determined, one of the "specified TCI states" is applied from the "set TCI state". Prior to this, 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 terminal device 1 has received the initial setting of multiple DLorJoint-TCIStates and before one of the configured TCI states is applied, 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] Terminal device 1 may receive higher layer settings. Terminal device 1 is set to "TCI state". After it is determined, one of the "specified TCI states" is applied from the "set TCI state". Before that, terminal device 1 applies the “instructed TCI state” to the first uplink transmit space filter for PUSCH, PUCCH, and SRS, and the second uplink transmit space filter It may be assumed that it is the same as, for example, terminal device 1 has multiple DLorJoint-TCIState, Alternatively, after receiving the first setting of multiple UL-TCIStates, and from the set TCI state 1 Before the specified TCI state is applied, terminal device 1 applies the specified TCI state. It may be assumed that the first uplink transmit spatial filter (UL TX spatial filter) for PUSCH, PUCCH, and SRS used is the same as the second uplink transmit spatial filter. The second uplink transmit space filter may be an uplink transmit space filter for PUSCH transmissions scheduled by random access response grants in the initial access procedure.

[0291] After terminal device 1 has received multiple DLorJoint-TCIState settings ("set TCI states"), and before one "instructed TCI state" is applied from the set TCI states, The DMRS of the PDSCH, DMRS of the PDCCH, and CSI-RS to which the indicated TCI state applies may be an SS / PBCH block or a CSI-RS resource and QCL. For example, an SS / PBCH block or a CSI-RS resource may be identified in a random access procedure initiated by a synchronized reconfiguration. For example, terminal device 1 sets the DLorJoint-TCIState with a synchronized reconfiguration. It may be received as part of a reconfiguration with sync.

[0292] Terminal device 1 has multiple DLorJoint-TCIState or multiple UL-TCIState settings ("Settings After receiving a “TCI state that is specified”, and from the set TCI state, one “TCI state that is specified”. Prior to the application of the specified TCI state, the first uplink transmit space filter for PUSCH, PUCCH, and SRS may be assumed to be the same as the second uplink transmit space filter. The second uplink transmit space filter is the uplink transmit space filter for PUSCH transmits scheduled by random access response grants in random access procedures initiated by synchronized reconfiguration. That's fine.

[0293] DLorJoint-TCIState may be used as the “instructed TCI state”. For example, terminal Device 1 may obtain the QCL assumption (QCL relationship, QCL) from the "configured TCI state" for the PDSCH DMRS, PDCCH DMRS, and CSI-RS to which the "configured TCI state" applies. The "configured TCI state" is applied to the PDSCH DMRS, PDCCH DMRS, and CSI-RS. Good. The “indicated TCI state” may apply to DMRS of PDSCH, DMRS of PDCCH, CSI-RS, PUSCH, PUCCH, and SRS.

[0294] UL-TCIState may be used as the “instructed TCI state”. For example, terminal device 1 is For PUSCH, PUCCH, and SRS, which apply the “instructed TCI state,” the uplink transmit space filter may be determined from the “configured TCI state.”

[0295] When terminal device 1 transmits the 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 that transmits a TCI state indication without a downlink assignment. The HARQ-ACK information may also be HARQ-ACK information corresponding to a PDSCH scheduled by a DCI that transmits a TCI state indication. The second indicated TCI state may be indicated before the first indicated TCI state. The first slot is the first slot of the first channel. It may be the first slot after the beamAppTime symbol from the subsequent OFDM symbol. BeamAppTime may be the number of OFDM symbols. BeamAppTime may be set by a higher-layer parameter. BeamAppTime may be determined by the terminal capability. The indicated TCI state may be the indicated DLorJointTCIState or the indicated UL-TCIState.

[0296] If the upper-level parameter PDCCH-Config contains two different values ​​for the CORESET Pool Index (or coresetPoolIndex), terminal device 1 may receive activation commands ("Activated TCI States") for each CORESET associated with the CORESET Pool Index. The activation commands may be used to map up to eight TCI states to code points in the DCI field 'Transmission Configuration Indication'. If a set of TCI state IDs is activated for one CORESET Pool Index, the "Activated TCI States" corresponding to that CORESET Pool Index are associated with one physical cell ID. It is also possible to use a different CORESET pool index from the one CORESET pool index. The corresponding “activated TCI state” may be associated with a physical cell ID different from that one physical cell ID. The activation command may be received as MAC CE. In one BWP, 1 or Multiple CORESETs may be configured. A single CORESET may correspond to a CORESET pool index of '0' or '1'.

[0297] DCI field 'TransmissionConfiguration Indication' (i.e., TCI field) A single code point may contain up to four TCI states. For example, up to four TCI states One of the states may be a Joint TCI state. One of the maximum four TCI states may be a DL TCI state. It may be in any state. One of the maximum four TCI states may be a UL TCI state. One code point in the DCI field 'Transmission Configuration Indication' may be two It may include a “TCI state pair.” A TCI state pair may be a pair of a DL TCI state and a UL TCI state. Terminal device 1 may receive an activation command. The activation command may be used to map up to eight combinations of four or fewer TCI states to code points in 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 code maps in the DCI field 'Transmission Configuration Indication'. Terminal device 1 does not expect to receive more than 8 TCI states in the activation command. Alternatively, terminal device 1 may receive more than 8 "TCI state pairs" in the activation command. You don't need to expect that.

[0298] When terminal device 1 transmits the first PUCCH in the first slot, the TCI state and code point The mapping with the input may be applied from the second slot. The first PUCCH is the first This may be accompanied by HARQ-ACK information. The first PUCCH may be transmitted in response to the first PDSCH. The first PDSCH may transmit an activation command.

[0299] If the first upper layer parameter is set, and the first time offset is greater than or equal to the first value, and terminal device 1 is the first setting of the TCI state (set After receiving the TCI state (which is to be activated), and after receiving the activation command (which is to be activated TCI state), Before being transmitted, the DMRS port of the PDSCH is connected to the SS / PBCH block and QCL with respect to QCL type A. This may also be the case. The first upper layer parameter may be set for a CORESET that schedules the PDSCH. The CORESET may schedule the PDSCH. The first time offset may be the offset between the reception of the DL DCI and the PDSCH. The first value may be timeDurationForQCL.

[0300] If the first upper-layer parameter is set, terminal device 1 may assume that the DCI format of the PDCCH transmitted in CORESET contains a TCI field. The higher-level parameter may be tci-PresentInDCI, which is set to 'enabled'. The first upper-layer parameter may be tci-PresentInDCI, which is set to 'enabled' for PDSCH or CORESET, which schedules multicast PDSCH. The first upper-layer parameter may also be tci-PresentDCI-1-2.

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

[0302] If a first terminal capability is indicated to terminal device 1, terminal device 1 may determine a spatial domain filter. The spatial domain filter may be used while performing applicable channel access procedures before UL transmission on the channel. If an SRI corresponding to UL transmission is indicated In this case, terminal device 1 may use the same spatial domain filter as the spatial domain filter associated with the instructed SRI. Terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive the DL reference signal associated with the instructed TCI state. For example, when a TCI state setting (a TCI state to be set) with DLorJointTCIState or UL-TCIState is set, terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive the DL reference signal associated with the instructed TCI state. The first terminal capability is '1'. It may also be a beamCorrespondenceWithoutUL-BeamSweeping.

[0303] When the first upper-level parameter is set and multiple (e.g., two) TCI states are indicated, the DMRS port of the PDSCH is DL-RS and QCL for the multiple (e.g., two) TCI states. This is also acceptable. Multiple TCI states may be indicated at one code point of the DCI field 'Transmission Configuration Indication' in the DCI that schedules the PDSCH. The first upper layer parameter may be sfnSchemePdsch. The first upper layer parameter may be sfnSchemePdsch with 'sfnSchemeA' set. The first upper layer parameter may be sfnSchemePdsch with 'sfnSchemeB' set. Two TCI states The second one does not require the inclusion of QCL parameters {Doppler shift, Doppler spread}. Good. When the first upper-level parameter is set, and multiple (e.g., two) TCI states are indicated, and the TRP indication field indicates a third or fourth indication. In this case, the DMRS port of the PDSCH may have multiple (for example, two) TCI states for DL-RS and QCL. The setting of the first upper layer parameters may also involve applying the SFN method for PDSCH.

[0304] Terminal device 1 may receive DMRS for PDSCH scheduled by PDCCH with DCI format. If two TCI states are indicated and terminal device 1 receives the DMRS and SS / PBCH block for PDSCH in the same OFDM symbol, then at least one for PDSCH The DMRS port and SS / PBCH block may be QCL with typeD('QCL-TypeD'). If the first upper layer parameter is set and multiple PDCCHs overlap in the time-frequency domain, different DMRS settings may not be expected, and two TCI states may not indicate a DMRS port within a single CDM group. The first upper layer parameter may be PDCCH-Config, which includes two different CORESET pool indices. The SS / PBCH block may belong to either group 1 or group 2. For example, group Group 1 may correspond to the first TAG ID or the second subTAG ID. Group 2 corresponds to the It may also support a second TAG ID, or a second subTAG ID.

[0305] On the downlink, a maximum of 16 or 32 HARQ Pros can be used in a single serving cell. Seth may be supported. The number of HARQ processes may be set by a higher-level parameter. If no higher-level parameter is set, the number of HARQ processes may be 8. stomach.

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

[0307] The upper-level parameters may include values ​​for two different CORESET pool indices. PDCCHs that schedule two PDSCHs (the first PDSCH and the second PDSCH) may be associated with CORESETs having different CORESET pool index values. The upper layer parameter may be PDCCH-Config. Terminal device 1 may receive the first PDSCH and the second PDSCH.

[0308] 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 is SI-RNTI, P-RNTI, blow The G-RNTI may be used for scheduling for docasting. Terminal device 1 may assume that the DMRS port of the second PDSCH is the second SS / PBCH block or the second CSI-RS resource and QCL with respect to the first QCL parameter. The second SS / PBCH block or the second CSI-RS resource may be used for RACH-related purposes. The second PDSCH is used with RA-RNTI and MSGB-RNTI. It may be scheduled. Terminal device 1 has a DMRS port for the first PDCCH order and a DMRS port for the third PDSCH, and a second SS / PBCH block with respect to the first QCL parameter, Alternatively, it may be assumed that there is a second CSI-RS resource and QCL. The third PDSCH may be scheduled in RA-RNTI for random access procedures triggered by the first PDCCH order. The first QCL parameters may include some or all of the Doppler shift, Doppler spread, average delay, delay spread, and spatial RX parameters.

[0309] Decoding PDCCH with CRC scrambled by CS-RNTI is performed at the upper layer. If this setting is used, terminal device 1 may receive a PDSCH without a corresponding PDCCH.

[0310] When the first upper layer parameter is set, terminal device 1 may receive multiple PDCCHs. The first upper layer parameter may be PDCCH-Config. This may include two different CORESET pool index values. Multiple PDCCHs are multiple The PDSCH may be scheduled. Multiple PDSCHs may or may not overlap in the time-frequency domain. If multiple PDSCHs are associated with different CORESETs, terminal device 1 may receive multiple PDSCHs simultaneously. Different CORESETs may have different CORESET pool index (coresetPoolIndex) values.

[0311] CORESET (upper layer parameter ControlResourceSet) is CORESET pool index (upper layer If the parameter coresetPoolIndex is not provided, terminal device 1 may assume that CORESET is assigned a CORESET pool index of 0. If two TAG IDs or two subTAG IDs are provided, CORESET may have a CORESET pool index.

[0312] The first physical cell ID associated with the first CORESET may be different from the second physical cell ID associated with the second CORESET. For example, via the activated TCI state, the first CORESET and the second CORESET may be associated with different physical cell IDs. It may also support different CORESET pool indexes.

[0313] If the PDCCH reception contains two candidate PDCCHs from the search region set, monitor one PDCCH. The monitoring occasion may be the union of PDCCH monitoring occasions for two PDCCH candidates. The start of PDCCH reception may also be the start of the first PDCCH candidate. Furthermore, the termination of PDCCH reception may also be the termination of a subsequent PDCCH candidate.

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

[0315] In each CORESET, at least the following may be provided: a CORESET index by a first upper-layer parameter, a QCL relationship (antenna port QCL) by a second upper-layer parameter, and an indication of whether a TCI field exists by a third upper-layer parameter. The first upper-level parameter may be controlResourceSetId. The second upper-level parameter may be TCI-State. The third upper-level parameter may be tci-PresentInDCI, or It may also be tci-PresentDCI-1-2.

[0316] If a value of 0 is provided for the search area ID, terminal device 1 will have a search opportunity for a PDCCH candidate. The search area ID may be determined as follows: The search area ID may also be the searchSpaceID. The search area ID may be included in PDCCH-Config or PDCCH-ConfigCommon.

[0317] If two TCI states are provided in one CORESET, terminal device 1 will provide one CORESET You may assume that the QCL information is indicated by both of the two TCI states for PDCCH reception. The two TCI states indicate the QCL information (QCL relationship) of the DMRS antenna port for PDCCH reception. You may do so.

[0318] If no TCI state setting is provided in one CORESET, or if there are two or more TCI states If initial settings are provided and no MAC CE activation command is received, terminal device 1 may assume that the DMRS antenna ports associated with PDCCH reception are the SS / PBCH block and QCL. The SS / PBCH block may be identified by terminal device 1 during the initial access procedure.

[0319] If, in a single CORESET, two or more TCI state settings are provided by reconfiguration with synch, and a MAC CE activation command is not received, terminal device 1 will determine that the DMRS antenna port associated with PDCCH reception is in the SS / PBCH block or CSI-RS block. It may be assumed that these are resources and QCLs. The SS / PBCH block or CSI-RS resource is identified by terminal device 1 in a random access procedure initiated by a synchronized reconfiguration. It's okay.

[0320] In a CORESET with index 0, if a TCI state (e.g., a unified TCI state) is provided and the unified TCI state is applied, terminal device 1 will use a DMRS antenna for first PDCCH reception. It may be assumed that the naport (DMRS port) and the DMRS antenna port for the first PDSCH reception are the reference signal and QCL indicated by the TCI state. The application of the Unified TCI state may be that followUnifiedTCIstate is set to 'enable'. The PDSCH reception is scheduled by the DCI format provided by the first PDCCH reception. It may be linked. The unified TCI state may also be DLorJoint-TCIState.

[0321] In a CORESET with index 0, if a TCI state (e.g., unified TCI state) is provided and the unified TCI state is not applied, terminal device 1 will perform a DMRS annealing for the first PDCCH reception. The tenaport (DMRS port) is activated by one or more reference signals and QCL depending on the TCI state. It's okay to have it.

[0322] In a CORESET with an index other than 0, if one TCI state is provided, 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 RS and QCL as set by the TCI state. The TCI state indicated by the MAC CE activation command may be the “Activated TCI state”.

[0323] If a unified TCI state is provided, PDCCH in one CORESET with an index other than 0 A DMRS antenna port for receiving and a DMRS antenna port for PDSCHs scheduled by the DCI format provided by the PDCCH reception are indicated The reference signal may be provided by a TCI state ("indicated TCI state") and QCL.

[0324] If multiple (e.g., two) unified TCI states are provided (or indicated), then index 0 and above In a single CORESET with an external connection, a DMRS antenna port for PDCCH reception and a DMRS antenna port for PDSCH scheduled by the DCI format provided by said PDCCH reception may be QCL and a reference signal provided by one or both of the indicated unified TCI states ("indicated TCI states").

[0325] When a unified TCI state is applied, PDCCH occurs in one CORESET with an index other than 0. A DMRS antenna port for receiving and a DMRS antenna port for PDSCHs scheduled by the DCI format provided by the PDCCH reception are indicated The reference signal may be provided by a TCI state ("indicated TCI state") and QCL.

[0326] In one BWP within one serving cell, a set of 10 or fewer search regions is provided. This may also be done. For each set of search domains, the first upper layer parameter determines the search domain set index, the second upper layer parameter determines the relationship between the search domain set and CORESET, and the third The search space set (search space set index) linked by the higher-level parameters may be determined to at least. The first higher-level parameter is searchSpaceId. This is also possible. The second upper layer parameter may be controlResourceSetId. In the first search domain set, the second search domain set index is determined by the third upper layer parameter. A third higher-level parameter may be provided. A third higher-level parameter may link the first set of search spaces with the second set of search spaces. The third higher-level parameter may be searchSpaceLinking. The provision of a third higher-level parameter may mean that search space linking is applied.

[0327] When the first search space set and the second search space set are linked, terminal device 1 may monitor according to each search space set in a monitoring opportunity in one slot. The count of PDCCH candidates corresponding to the first search space set and the second search space set may be 3. The CORESET pool index for the first CORESET associated with the first search space set may be different from the CORESET pool index for the second CORESET associated with the second search space set. Linking the first search space set and the second search space set may mean 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.

[0328] If the first search area set and the second search area set are linked, and the third search area set is not linked, terminal device 1 may monitor the first PDCCH candidate corresponding to the first search area set for the first DCI format, and the second search area The terminal device 1 may monitor a second PDCCH candidate corresponding to the region set. Alternatively, for the second DCI format, the terminal device 1 may monitor a third PDCCH candidate corresponding to the third search region set. Furthermore, in one CORESET, and for the same symbol in one slot... Then, the first PDCCH candidate corresponding to the first search region set, or the second search region set The second PDCCH candidate corresponding to the first set and the third PDCCH candidate corresponding to the third search region set may use the same set of CCEs and may undergo the same scrambling. The third PDCCH candidate corresponding to the third search region set is counted for monitoring. It is not necessary. Furthermore, the detected DCI format does not necessarily have to be assumed to be the first DCI format.

[0329] If the first search area set and the second search area set are linked, and the third search area set and the fourth search area set are linked, and the detected DCI format If the coreset sizes are the same, terminal device 1 may expect different CCEs or different scrambling in a single coreset.

[0330] When a terminal device monitors multiple PDCCHs in the first CORESET and the second CORESET, The first CORESET may correspond to a CSS set with the smallest index, or to a USS set with the smallest index. The second CORESET is the same as the first CORESET. It may have properties of type D. Repeats may be applied for PDCCH. The application of repeats for PDCCH is provided by two-QCLTypeDforPDCCHRepetition. It is acceptable to do so.

[0331] If the first search area set and the second search area set are linked, terminal device 1 may detect from the two PDCCH receptions that the one terminating later is in DCI format.

[0332] MAC PDU (MAC protocol data unit) is a byte-aligned (byte-aligned) file. A MAC SDU (MAC service data unit) may be a bit string of byte-aligned (i.e., a multiple of 8 bits) bit array. A MAC SDU may consist of bits from the first bit onward of a MAC PDU. A MAC CE may consist of bits from byte-aligned (i.e., a multiple of 8 bits) bit array. The MAC subheader may be a bit string (a multiple of 8 bits) of byte-aligned length (i.e., a bit string of 8 bits). Good. Each MAC subheader may be placed immediately before the corresponding MAC SDU, MAC CE, or padding.

[0333] A MAC PDU (MAC protocol data unit) may consist of one or more MAC subPDUs. Each MAC subPDU may consist of one MAC subheader. A subPDU may consist of one MAC subheader and one MAC SDU (Service Data Unit). Each MAC subPDU may consist of one MAC subheader and one MAC CE. Each MAC subPDU may consist of one MAC subheader and padding. The MAC SDU is variable. Each MAC subheader may correspond to one MAC SDU, one MAC CE, or padding. A single MAC PDU may correspond to one transport block. .

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

[0335] Figure 9 shows an example of activation command A according to one aspect of this embodiment. The Serving cell ID field identifies the serving cell to which the first MAC CE is applied. Child may be indicated. The BWP ID field may indicate the DL BWP to which MAC CE applies as the code point of the DCI's 'bandwidth part indicator field'. The first MAC CE is When applied to a set of multiple serving cells, the BWP ID field may be ignored. i The field “T” may indicate the activation / deactivation status of the TCI state, accompanied by the TCI state ID i. i Setting the field of “ to 1 may indicate that the TCI state associated with TCI state ID i is activated. i Setting the field to 1 may indicate that the TCI state with TCI state ID i maps to one code point in the DCI's 'Transmission Configuration Indication field'. i When the field is set to 0, the TCI state associated with TCI state ID i is deactivated. It may also be indicated that “T i The setting of the field " to 1 may indicate that a TCI state with TCI state ID i does not map to one code point in the DCI's 'Transmission Configuration Indication field', where i is the TCI state ID (or TCI-StateID). This is also acceptable. A TCI state may be accompanied by a TCI state ID. Maximum number of “Activated TCI states” It may be 8. The field of CORESET pool ID is the first mapping, CORESET pool The CORESET ID (ControlResourceSetId) is set by the CORESET pool index. Alternatively, it may be shown to be unique. The first mapping is “the activated TCI state”. And, “T i The code point of the DCI 'Transmission Configuration Indication' set by the field may also be mapped to the field of the CORESET pool ID. Setting this to 1 means that the first MAC CE is applied to downlink transmissions scheduled by a CORESET with a CORESET pool ID (CORESET pool index) of value 1. This may indicate that the CORESET pool ID field is set to 0, which may indicate that the first MAC CE is applied to downlink transmissions scheduled by a CORESET with a CORESET pool ID (CORESET pool index) of value 0. If the coresetPoolIndex is not set, the CORESET pool ID in the first MAC CE is The field may be ignored.

[0336] The second MAC CE may be activation command B. The second MAC CE may be a MAC CE for activation or deactivation of the TCI state for PDSCH (UE-specific PDSCH). The second MAC subheader may be a T for PDSCH. A MAC CE for activating / deactivating the CI state may be identified. For example, the second MAC subheader may be accompanied by a second LCID (Logical channel ID). The second LCID is an eLCID. This is also acceptable. For example, the value of the second LCID may be "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH".

[0337] Figure 10 shows an example of activation command B according to one aspect of this embodiment. i " of The field is the TCI status ID. i,2 You may also indicate whether an octet containing the character exists. For example, “C i If the field is set to 1, the TCI status ID i,2 An octet containing "C" may exist. For example, "C i If the field is set to 0, the TCI status ID i,2 An octet containing this may not exist. TCI state ID i,j The field may indicate a TCI state identified by a TCI State ID (TCI-StateId). i,j This may represent the j-th TCI state indicated for the i-th code point in the DCI's 'Transmission configuration indication' field. TCI State ID i,2 is “C i "This may be optional based on the field indication. i may be the index of the code point in the DCI'Transmission configuration indication' field. j is 1 or 2 It's okay to have it.

[0338] 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 state. The MAC CE for activation / deactivation of the unified TCI state is identified by the third MAC subheader. This is also acceptable. For example, the third MAC subheader may include the third LCID (Logical channel ID). This is also acceptable. The third LCID may be an eLCID. For example, the value of the third LCID may be "Unified TCI States Activation / Deactivation MAC CE".

[0339] Figure 11 shows an example of an activation command C according to one aspect of this embodiment. The DL BWP ID field may indicate one downlink BWP to which MAC CE is applied as one code point in the DCI'bandwidth part indicator' field. The UL BWP ID field is Apply MAC CE to one uplink BWP, DCI's 'bandwidth part indicator' feel It may also be indicated as one of the chord points of "P". i The field may indicate whether each TCI code point has multiple TCI states or one TCI state. Example For example, “P i "If 1 is set in the field, the i-th TCI code point is DL TCI state It may include both states and UL TCI states. For example, “P i "When 0 is set in the field" In addition, the i-th TCI code point may include either a DL TCI state or a UL TCI state. The field is where the TCI state ID in the same octet is joint(both DL and UL) / DL, Alternatively, it may indicate whether it is for 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 “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 considered reserved. 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 PDSCH, PDCCH, and CSI-RS. The UL TCI state is a TCI state that applies to some or all of PUSCH, PUCCH, and SRS. This is also acceptable. A Joint TCI state may represent both a DL TCI state and a UL TCI state. A DLorJointTCIState may be either a DL TCI state or a Joint TCI state. A UL-TCIState may be a UL TCI state. A DL TCI state may be a TCI state for DL. A Joint TCI state may be a TCI state for both DL and UL. A UL TCI state may be a TCI state for UL. This may also be the case. A TCI code point is a DCI's Transmission configuration indication. It can also be a code point for a field. In MAC CE, the “R” field is confirmed It may also be a reserved bit. The reserved bit may be set to 0.

[0340] The fourth MAC CE may be activation command D. The fifth MAC CE may be activation command E. The fourth MAC CE is either activation or deactivation of the unified TCI state. A MAC CE may be for deactivation. For example, a fourth MAC CE may be for activation or deactivation of an enhanced unified TCI state. A fifth MAC CE may be for activation or deactivation of a unified TCI state. For example, a fifth MAC CE may be for activation or deactivation of an enhanced unified TCI state. It may also be a MAC CE for deactivation. By the fourth MAC subheader MAC CEs for activation / deactivation of the unified TCI state may be identified. Fifth MAC sub The header may identify the MAC CE for activating / deactivating the unified TCI state. For example, the fourth MAC subheader may include the fourth LCID (Logical channel ID). If the fifth MAC subheader is, it may also include a fifth LCID (Logical channel ID). The fourth LCID may be an eLCID. The fifth LCID may also be an eLCID. For example, if the value of the fourth LCID is "Enhanced unified TCI States Activation / Deactivation MAC CE 1", This is also acceptable. For example, the value of the fifth LCID may be "Enhanced unified TCI States Activation / Deactivation MAC CE 2".

[0341] Figure 12 shows an example of an activation command D according to one aspect of this embodiment. Serving The Cell ID (Serving cell ID) field identifies the serving cell to which the fourth MAC CE applies. The DL BWP ID field may indicate one downlink BWP to which the fourth MAC CE applies. Link BWP to one code point in the DCI's 'bandwidth part indicator' field and The UL BWP ID field may indicate one uplink BWP to which the fourth MAC CE applies. Link BWP is one code point in the DCI's 'bandwidth part indicator' field. You may give instructions by saying "P i The field “P” may indicate whether each TCI code point has multiple TCI states or one TCI state. For example, “P i "There is 1 in the field If set, the i-th TCI code point may include both DL TCI states and UL TCI states. For example, “P i "If the field is set to 0, the i-th TCI code point This may include either the DL TCI state or the UL TCI state. i The field of “ is each TCI code The dot point may indicate whether it is a joint (both DL and UL) / DL, or for UL. For example, “D / U i If the field is set to 1, the i-th TCI code point may be for DL / joint. For example, “D / U i "If the field is set to 0, the i-th TCI code point may be for UL." jThe field “T” may indicate the activation / deactivation status of the TCI state, accompanied by the TCI state ID j. j " When the field is set to 1, the TCI state associated with TCI state ID j is activated. You may also indicate “T j The field of " being set to 1 means that the TCI state ID j is associated with the TCI The status is one code point in the DCI's 'Transmission Configuration Indication field'. You may also show that it maps to “T j Setting the field of “ to 0 may indicate that the TCI state associated with TCI state ID j is deactivated. j Setting the field to 1 may indicate that the TCI state with TCI state ID j does not map to one code point in the DCI's 'Transmission Configuration Indication field', where j is either a UL TCI state ID (UL-TCIState-Id) or a DL / Joint TCI state ID (DLorJoint-TCIState-Id). It may also be the case that the number of UL TCI state IDs is up to 64. The number of DL / Joint TCI state IDs is up to 128. j may be {0, ..., 63}. j may be {0, ..., 127 It may also be {0, ..., 191}. For example, the i-th TCI code point If it corresponds to the UL TCI state, then “T j The field may indicate the activation / deactivation status of the TCI state with TCI state ID j-128. For example, i If the eye's TCI code point corresponds to a DL TCI state or a Joint TCI state, then “T jThe field “T” may indicate the activation / deactivation status of a TCI state with TCI state ID j-64. For example, if the i-th TCI code point corresponds to a UL TCI state, “T” j The field being set to 1 means that the TCI with TCI status ID j-128 It may also indicate that a state is activated. For example, if the i-th TCI code point corresponds to the UL TCI state, “T j Setting the field " 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 a DL TCI state or a Joint TCI state, then "T j Setting the field to 1 may indicate that a TCI state with TCI state ID j-64 is activated. For example, if the i-th TCI code point is a DL TCI state, or a Joint TCI state. When dealing with a state, “T j The field " being set to 1 means TCI status ID j-64 It may also indicate that the associated TCI state is mapped to the i-th TCI code point. The field of CORESET pool ID is such that the second mapping is CORESET pool ID (CORESET pool index This indicates that it is unique to the CORESET ID (ControlResourceSetId) set in (kus). That's good too. The second mapping is “Activated TCI state” and “T i "By field The DCI 'Transmission Configuration Indication' code point to be set may also be mapped to the value 1. Setting the CORESET pool ID field to 1 means the value 1 Scheduled by CORESET with CORESET pool ID (CORESET pool index) This may indicate that MAC CE is applied to downlink or uplink transmissions being scheduled. Setting the CORESET pool ID field to 0 may indicate that MAC CE is applied to downlink or uplink transmissions scheduled by a CORESET with a CORESET pool ID (CORESET pool index) of value 0. CORESET pool If the index (coresetPoolIndex) is not set, the CORESET pool in the fourth MAC CE will not work. The ID field can be ignored.

[0342] Figure 13 shows an example of an activation command E according to one aspect of this embodiment. The CORESET pool ID field may be reserved. i,j "feel The code may indicate whether each TCI code point has multiple TCI states or one TCI state. For example, “P i,j "If 1 is set in the field, the i-th TCI code Even if the j-th TCI state at a given point is two (for example, a DL TCI state and a UL TCI state) Good. For example, “P i,j "If the field is set to 0, the i-th TCI code point The j-th TCI state in this case may be a single state (for example, a DL TCI state or a UL TCI state). Yes. “D / U j The field “D / U” may indicate whether the TCI state ID in the same octet is joint(both DL and UL) / DL or UL. j The field of " is the same oct The TCI status ID in the set indicates whether it is for joint (both DL and UL) / DL or UL. It is also acceptable to use "D / U j"If a field is set to 1, in the same octet The TCI status ID may also be for DL / joint. For example, “D / U j "If the field is set to 0, the TCI state ID in the same octet may be for UL. i,j The field may indicate a TCI state identified by a DL / Joint TCI State ID (TCI-StateId) or a UL TCI State ID (UL-TCIState-Id). j "The field is set to 1" If so, a 7-bit "TCI state ID" is used. i,j " may be used. j If the field is set to 0, the "TCI state ID" i,j The most significant bit of “ may be considered as reserved, and the remaining 6 bits may represent the UL-TCIState ID (UL TCI State ID, UL-TCIState-Id).

[0343] In Figure 13, j may correspond to the CORESET pool ID (CORESET pool index). For example, j=1 may correspond to CORESET pool ID (CORESET pool index)=0. For example, j=2 could correspond to CORESET pool ID (CORESET pool index)=1. For example, j=0 may correspond to CORESET pool ID (CORESET pool index)=0. j=1 may also correspond to CORESET pool ID (CORESET pool index)=1. Whether or not it corresponds to the T pool ID (CORESET pool index) is determined by the "J" field. It may be determined by the following. For example, if the "J" field is set to 1, j may correspond to the CORESET pool ID (CORESET pool index). For example, if the "J" field is set to 0 If set, j corresponds to the index of the TCI state in a single code point. It's fine. “P i,j The field indicates whether each TCI code point of the DCI associated with the CORESET pool ID corresponding to j has multiple TCI states or only one TCI state. Good. For example, “P i,j If the field is set to 1, then the i-th TCI code point of the DCI associated with the CORESET pool ID corresponding to j corresponds to both the DL TCI state and the UL TCI state. That's also good. For example, “P i,j If the field is set to 0, the corresponding CORESET pool The i-th TCI code point of the DCI associated with the ID may correspond to either the DL TCI state or the UL TCI state. The CORESET pool index (upper layer parameter coresetPoolIndex) is set. If not present, j does not need to correspond to a CORESET pool ID.

[0344] The activation command F may be MAC CE for TCI status indication for PDCCH. The transformation command F consists of a 5-bit serving cell ID, a 4-bit coreset ID, and a 7-bit TCI. It may consist of a state ID and a .

[0345] Activation command G may be MAC CE for TCI state indication for PDCCH. The activation command G may consist of a 5-bit serving cell ID, a 4-bit coreset ID, a 7-bit first TCI state ID, and a 7-bit second TCI state ID. If one or more coresets in a single BWP are set with different coreset pool index values, the activation command G may not be applied to one or more coresets. SFN is applied for PDCCH. If so, activation command G may be applied. SFN for PDCCH is applied. This may involve setting sfnSchemePdcch.

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

[0347] A UL slot may be a slot composed of UL symbols. A special slot may be a slot composed of UL symbols, flexible symbols, and DL symbols. A DL slot may be a slot composed of DL symbols.

[0348] The UL symbol may be an OFDM symbol set or indicated for the uplink in time-division duplexing. The UL symbol may be an OFDM symbol set or indicated for PUSCH, or PUCCH, PRACH, or SRS. The UL symbol may be provided by the upper-layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbol may also be provided by the upper-layer parameter tdd-UL-DL-ConfigurationDedicated. . UL slots may be provided by the higher-layer parameter tdd-UL-DL-ConfigurationCommon. UL slots may be provided by the higher-layer parameter tdd-UL-DL-ConfigurationDedicated Therefore, it may be provided.

[0349] The DL symbol may be an OFDM symbol set or indicated for the downlink in time-division duplexing. The DL symbol may be an OFDM symbol set or indicated for PDSCH or PDCCH. The DL symbol may have the upper layer parameter tdd-UL -DL-ConfigurationCommon may provide the DL symbol, which is a higher-layer parameter. The DL slot may be provided by tdd-UL-DL-ConfigurationDedicated. DL slots may also be provided by the higher-layer parameter tdd-UL-DL-ConfigurationCommon. good.

[0350] A flexible symbol may be an OFDM symbol within a certain period that is not set or indicated as a UL symbol or a DL symbol. The period may be the period given by the higher-level parameter dl-UL-TransmissionPeriodicity. Good. The flexible symbol is for PDSCH, PDCCH, PUSCH, PUCCH, or PRACH. This may be set to or indicated by an OFDM symbol.

[0351] The upper-level parameter tdd-UL-DL-ConfigurationCommon may be a parameter that sets each of one or more slots to either an UL slot, a DL slot, or a special slot. The upper-level parameter tdd-UL-DL-ConfigurationDedicated is tdd-UL-DL-ConfigurationCommon may be a common upper-layer parameter, while tdd-UL-DL-ConfigurationDedicated may be a dedicated upper-layer parameter.

[0352] Multiple TRPs (Transmission Reception Points, or Transmit / Receive Points) are used. It may be done. The base station device 3 may consist of multiple TRPs (Multi-TRP). The terminal device 1 may be scheduled by two TRPs in one serving cell. In Multi-TRP, either single-DCI or multi-DCI operating mode may be used. In Multi-TRP, uplink control may be completed at the MAC layer and physical layer. In Multi-TRP, MAC Downlink control may be completed at the layer and physical layer. In Single-DCI mode, terminal device 1 may be scheduled by the same DCI for two TRPs. In Multi-DCI mode, terminal device 1 may be scheduled by independent DCIs from each TRP. In Multi-TRP, each TRP may be identified by TRP information. That is, one TRP in Multi-TRP may be identified by one TRP piece of information. TRP information may be used to select one TRP.

[0353] Even if the TA offset (Timing advance offset) value is provided by the higher-level parameters, Good. The timing advance (TA) may be determined based on at least the TA offset. One TA offset may be provided for one serving cell. Two TA offsets may be provided for one serving cell. If no higher-level parameters are provided, terminal device 1 may determine the value of the TA offset. Terminal device 1 may determine the values ​​of two TA offsets for one serving cell. The value of the TA offset is N TA,offset This may also be the case. The upper layer parameter is n-TimingAdvanceOffset It may be possible. Determining the TA may also mean adjusting the uplink timing. In other words, the uplink timing may be referred to as TA.

[0354] If two uplink carriers are configured in one serving cell, one TA The offset value may be applied to two uplink carriers. If two TRPs (Transmission Reception Points) are set in one serving cell, one TA offset The value may be applied to two TRPs. Two TRPs are set in one serving cell. In this case, the values ​​of the two TA offsets may be applied to the two TRPs.

[0355] Terminal device 1 may adjust the uplink timing. For example, terminal device 1 may adjust the uplink timing in response to the reception of a TA command (Timing advance command). For example, in response to the reception of one TA command (Timing advance command) for one TAG (Timing advance group), terminal device 1 may adjust the uplink timing for PUSCH / SRS / PUCCH transmissions in all serving cells in one TAG. For example, in response to the reception of one TA command for one TAG, terminal device 1 adjusts the uplink timing for PUSCH / SRS / PUCCH transmissions in one or more serving cells belonging to one TAG. It is also possible to do so. For example, terminal device 1 is N TA,offet The uplink timing may be adjusted based on the value of N. TA,offset This may be the same for all serving cells in a single TAG. TA,offset This does not have to be the same for all serving cells in a single TAG. Also, terminal device 1 is N TA,offset The value of, and one or both of the TA commands. Based on this, the uplink timing may be adjusted. There is one uplink timing. This may be the same for all serving cells in the TAG. Uplink timing The link timing does not have to be the same for all serving cells in a single TAG. For example, the first uplink timing may be the same for a first portion of the serving cells in a single TAG. It may be the same. For example, the second uplink timing is the service in one TAG. The same may apply to the second part of the Gsell. All serving cells in a single TAG may be divided into a first part and a second part.

[0356] In response to the reception of a single TA command (Timing advance command) for a single subTAG, terminal device 1 may adjust the uplink timing for PUSCH / SRS / PUCCH transmission corresponding to a single subTAG (or subTAG ID). For example, in response to the reception of a single TA command for a single subTAG, terminal device 1 may adjust the uplink timing for one or more serving cells belonging to a single subTAG, The uplink timing for PUSCH / SRS / PUCCH transmission in TRP may be adjusted. TA,offset This may be the same for all serving cells in a single subTAG. The uplink timing is the same for all serving cells in a single subTAG. It is permissible. Two subTAGs may be used in a single serving cell.

[0357] Terminal device 1 may determine the uplink timing based on at least some or all of the TA command, TA offset, and TRP information. The first uplink timing and the second uplink timing may be determined. For example, the TRP (Transmission Reception Point) information identifies one of one or more TRPs. It may also be information for the purpose of [something]. For example, TRP information may be an index for identifying a single TRP. It may also be a combination. For example, one TRP may be determined based on TRP information. Example For example, TRP information may be information for identifying one or more TRPs. TRP information may be provided by higher-layer parameters. TRP information is provided in random access response TRP information may be included in the DCI format. TRP information may also be a CORESET pool index. TRP information may be associated with an index of a CORESET resource pool. For example, the first CORESET pool index may be associated with the first TRP, and the second CORESET pool index may be associated with the second TRP. The information may also be related to the TCI state. TRP information is a pool of TCI states. Alternatively, it may be associated with a pool index. The first one or more TCI states It may be associated with the pool index of the first TCI state. The second or more TCI states may be associated with the pool index of the second TCI state. The TRP information may be a TAG ID (subTAG ID). For example, the first TAG ID (subTAG ID) is: The first TRP may be related, and the second TAG ID (subTAG ID) may be related to the second TRP. .

[0358] The TAG ID may be used to identify a TAG or a subTAG.

[0359] Based on a timing adjustment indication for one TAG from the MCG. Then, the first uplink timing may be determined. Based on a timing adjustment instruction for one TAG from the SCG, the second uplink timing may be determined. Based on the timing adjustment instructions for these two TAGs, the first uplink timing and the second uplink timing may be determined.

[0360] TA commands may be modified based on subcarrier intervals. For example, between subcarriers In the interval setting μ, one TA command for one TAG changes the uplink timing. Further instructions may be given. For example, the uplink timing is 16*64*T c / 2 μ It may be changed by a multiple of . "*" may also be the multiplication operator.

[0361] The Timing Advance (TA) of the random access preamble may be 0.

[0362] TA commands may be included in the random access response. For example, one TAG (and The TA command for subTAG is a random action associated with one TAG (or subTAG). It may be included in the response. For example, one TA command related to one TRP piece of information is one The random access response in the random access procedure related to the TRP information is included It may also be sent as a MAC CE command. For example, the TA command may be an Absolute timing advance command MAC CE. Random access response, or TA command T in the case of an Absolute timing advance command MAC CE A For one TAG, N TA You may also specify the value of T. A This is an integer from 0 to 3846 It can also be a number. For example, N TA is, T A *16*64 / 2 μ It is also acceptable. TA This may relate to the subcarrier interval of an uplink transmission. For example, an uplink transmission may be an uplink transmission from terminal device 1. For example, an uplink transmission may be a random active It may also be the first uplink transmission after receiving a response. For example, an uplink transmission may be the first uplink transmission after receiving an absolute timing advance command MAC CE. A This may be an index value. Uplink transmission may be an uplink channel transmission. In a random access procedure, whether to receive an Absolute timing advance command MAC CE or a random access response may be determined by higher-layer parameters. For example, the random access procedure may be initiated (triggered) by a PDCCH order.

[0363] TA command T A For one TAG, the current N TA You can also instruct the system to adjust the value. For example, the TA command T A is, N TA,old From N TA,new You may instruct them to make adjustments to N. TA,new is, N TA,old +(T A -31)*16*64 / 2 μ It is also acceptable. For example, T A This can be an integer from 0 to 63.

[0364] If the terminal device has one or more active uplink BWPs, the TA command (TA Command) The value is also related to the maximum subcarrier spacing of one or more active uplink BWPs. Good. The TA command may also be a TA command in one TAG that includes the uplink BWP on two uplink carriers of one serving cell. For example, between the first subcarriers. N for one uphill link BWP with separation TA,newThe value may be rounded to match the timing advance granularity (TA) for one uplink BWP with an initial subcarrier interval. Rounding the value may also mean performing fractional part processing on the value. For example, while maintaining the timing advance accuracy requirements, N TA,new is, I don't mind being criticized.

[0365] N due to positive angle TA The adjustment is for uplink transmission for one TAG (Timing advance group). You may also instruct the timing (uplink timing) to advance. A negative value of N is used. TA The adjustment may also instruct a delay in the uplink transmission timing for one TAG.

[0366] If one TA command is received in the first slot n, the uplink transmission timing adjustment may be applied from the beginning of the second slot. The first slot n may be an uplink slot. The uplink slot is an uplink frame It may also be the corresponding slot. The second slot is n+k+1+2 μ *K offset Even Good. That is, the second slot is k+1+2 from the first slot n. μ *K offset It can be a slot after a slot. K offset k may be provided by higher layer parameters. ,ceil(N subframe,μ slot ·(N T,1 +N T,2 +N TA,max +0.5) / T sf ) may also be acceptable. N T,1 units This can also be in milliseconds. T,1This is the duration in milliseconds for the N1 symbol. This is also acceptable. The N1 symbol may correspond to the PDSCH processing time. T,2 This may be the duration in milliseconds of the N2 symbol. The N2 symbol may correspond to the PUSCH preparation time. TA,max This may also be the maximum TA value (timing advance value) in milliseconds. TA,max This may also be the maximum TA value that can be provided by the 12-bit TA command field. subframe,μ slot This could also be the number of slots in a single subframe. sf This can be 1 millisecond. sf teeth It may also be the duration of a subframe. offset is, K cell,offset -K UE,offset It is also acceptable. K cell,offset This may be provided by higher-level parameters. K UE,offset There is one It may also be provided by the MAC CE command. cell,offset K may be 0. UE,offset It may be 0. One or both of N1 and N2 may be determined in relation to the minimum subcarrier spacing (SCS). The minimum subcarrier spacing is set It may also be the smallest subcarrier spacing among all downlink BWPs and all uplink BWPs that are set. If μ=0, N1 may be 14. Slot n and N subframe,μ slot This may be determined in relation to the minimum subcarrier interval. TA,max This may be determined in relation to the minimum subcarrier interval. Slot n may be the last of one or more slots that overlap with the slots for PDSCH reception. In PDSCH reception, T TAIt is also possible to assume that = 0. In PDSCH, one TA command is received. It is also possible that a PDSCH containing one TA command is received. The PDSCH may provide one TA command.

[0367] If terminal device 1 changes the active uplink BWP, terminal device 1 may determine the TA command (TA command value) based on the subcarrier interval of the changed active uplink BWP. For example, if terminal device 1 changes the active uplink BWP between the time of receiving the TA command and the time of applying adjustments for uplink transmission timing, terminal device 1 will determine the new TA commands may be determined based on the subcarrier spacing of the active uplink BWP. After applying adjustments for uplink transmission timing, the active uplink BWP changes. If changed, terminal device 1 may assume the same absolute timing advance command value (absolute timing advance command MAC CE). That is, active uplink BWP change The first absolute timing advance command value prior to the change may be the same as the second absolute timing advance command value after the active uplink BWP change.

[0368] If the downlink timing is changed and the downlink timing is not corrected, terminal device 1 is N TA This may be changed. If the downlink timing is changed, and the downlink timing is partially corrected by uplink timing adjustment without a TA command, terminal device 1 is N TA This may be changed. Uplink timing adjustment may involve determining or changing the uplink timing.

[0369] If a single TA command causes two adjacent slots to overlap, the latter slot may be reduced. Also, if the beginning of the first slot is within X symbols of the end of the second slot If initiated within, the first slot may be reduced. The X symbol is a subcarrier. The interval and / or terminal capabilities may be determined based on at least one or both.

[0370] A TAG (Timing advance group) may be a group of one or more serving cells. One or more serving cells may be set up by RRC. A serving cell may use one TA value. One or more serving cells may use one Timing reference cells may be used. The PTAG (Primary TAG) may be a TAG containing a SpCell. The STAG (Secondary TAG) may be a TAG that does not contain a SpCell. This is also acceptable. One or more serving cells may use two TA values. One TAG may use two TA values. It may contain two subtags.

[0371] A subTAG may be a group of one or more serving cells. A subTAG may be a group of serving cells that use the same TA (TA value). For example, a subTAG may be associated with one TRP. For example, a subTAG may be associated with one TRP. Associated with subTAG A serving cell does not have to be associated with a TAG. For example, a subTAG may be set for one serving cell. For example, a serving cell associated with a subTAG is not associated with a TAG. They may be linked. A subTAG may be a group of one or more TRPs. A subTAG may be a group of TRPs that use the same TA (TA value). For example, a subTAG may be associated with one serving cell. A subTAG may be a group of TAs for one serving cell. i. Two subTAGs may be provided, configured, or determined within a single serving cell. A subTAG ID may be determined for each subTAG. A subTAG may be a type of TAG. That is, TAG and subTAG may be referred to as TAGs.

[0372] The RRC layer may configure one or more upper-layer parameters for uplink time alignment maintenance. For example, the RRC layer may configure a time alignment timer. For example, the time alignment timer may be configured by the upper-layer parameter timeAlignmentTimer. The time alignment timer may control a first time, which may be the time at which a MAC entity considers multiple serving cells to belong to a related TAG. For example, the time alignment timer may control the uplink It may also be time for time synchronization (alignment). That is, the time synchronization timer is running. The operation may involve time synchronization. Time synchronization may also involve the determination (or adjustment) of the uplink timing. In other words, the TA may perform time synchronization.

[0373] The RRC layer may configure one or more upper-layer parameters for the maintenance of multiple uplink time synchronizations. For example, the RRC layer may configure multiple time synchronization timers. At least one of the multiple time synchronization timers may be associated with subTAG. At least one of the synchronous timers may be associated with a TAG.

[0374] A time synchronization timer may correspond to a single subTAG. For example, the time synchronization timer may correspond to the time at which a MAC entity considers one or more serving cells to belong to a subTAG. You may also control the following. For example, a time synchronization timer may control the time at which a MAC entity considers one or more TRPs to belong to a subTAG.

[0375] A MAC entity may perform some or all of the processes from the first to the fourth. stomach.

[0376] In the first process, the TA command MAC CE (Timing advance command MAC CE) is received, Tsu, N TA If it is held in the indicated TAG, the MAC entity may apply a TA command for the indicated TAG. In the first process, a TA command MAC CE (Timing advance command MAC CE) is received, and N TA If held in the indicated TAG, the MAC entity starts or restarts the time synchronization timer associated with the indicated TA command. It is permissible to do so. The time synchronization timer may be a timeAlignmentTimer.

[0377] The second process is when the TA command receives a random access response. The second process may be the processing when received in a TA command message. The second process may be the processing when the message B (MSGB) is received. The second process may be the processing in a serving cell belonging to a single TAG (or subTAG). The second process may be the processing in a SpCell. In the second process, random access passes are used. If the Random Access Preamble is not selected from the Contention-Based Random Access (CBRA) preamble, the MAC entity will have one TAG (or subTAG). A TA command may be applied to start or restart a time-synchronized timer associated with a single TAG (or subTAG). The TA command may be received via a random access response.

[0378] In the second process, if the time synchronization timer associated with one TAG (or subTAG) is stopped (not running), the MAC entity may apply a TA command for that TAG (or subTAG) and start the time synchronization timer. Furthermore, if contention resolution does not complete successfully, the MAC entity may stop the time synchronization timer.

[0379] In the second process, if the time synchronization timer associated with one subTAG is stopped, the MAC entity may apply the TA command of the random access response in the first random access procedure and start the time synchronization timer. Furthermore, if the conflict resolution does not complete successfully, the MAC entity may stop the time synchronization timer. The first random access procedure was a random access procedure associated with one subTAG. This is also acceptable. The first random access procedure may be a random access procedure for obtaining TA.

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

[0381] In the third process, if an Absolute Timing Advance Command (TA) is received for a message A (MSGA) transmission containing a C-RNTI MAC CE, the MAC entity may apply the Absolute TA command for the Primary Tag (PTAG) and start or restart the time synchronization timer associated with the PTAG. If an Absolute TA command is received for a random access preamble transmission, the MAC entity may apply the Absolute TA command for the Tag or sub-Tagg. In this case, the time synchronization timer associated with the PTAG may not be started or restarted.

[0382] In the third process, an absolute Timing Advance Command associated with one subTAG sends either message A (MSGA) containing C-RNTI MAC CE, or message 1. When received, the MAC entity may apply an absolute TA command for one subTAG, and may start or restart a time synchronization timer associated with one subTAG.

[0383] The fourth process may be the process for when the time synchronization timer has expired. In the fourth process, the time synchronization timer is related to the PTAG (or the subTAG associated with the first TRP) When linked, the MAC entity performs some or all of the sub-operations from the first to the seventh sub-operations. This may be performed. The first sub-action may be to flush all HARQ buffers for all serving cells. The second sub-action may be to flush all HARQ buffers for all serving cells. The third sub-action may be to notify the RRC to release the PUCCH. The third sub-action may be to notify the RRC to release the SRS for all serving cells. The fourth sub-action may be to clear the configured downlink assignments and configured uplink grants. The fifth sub-action may be to clear the PUSCH resources for semi-persistent CSI reporting. This is also acceptable. The sixth sub-operation may be to consider all time synchronization timers as expired. The seventh sub-operation is N for all TAGs (or subTAGs). TA It may also mean maintaining the time synchronization timer when it is not running. In this case, the MAC entity is N TA It is not necessary to change this. In the fourth process, if the time synchronization timer is associated with STAG (or a subTAG associated with the second TRP), the MAC entity may perform some or all of the eighth to thirteenth suboperations. The eighth suboperation performs all HARQ buffers for serving cells belonging to this TAG (or this subTAG). This may also involve deleting (flushing). The ninth sub-action may involve notifying the RRC to release PUCCH for the serving cells belonging to this TAG (or this subTAG). The tenth sub-action may involve releasing PUCCH for the serving cells belonging to this TAG (or this subTAG). This may involve notifying the RRC to release an SRS for the eleventh sub-operation, which is the downlink set for the serving cells belonging to this TAG (or this sub-TAG). This involves removing (clearing) the link assignment and the configured uplink grant. Alternatively, the twelfth sub-operation is the serving cell belonging to this TAG (or this subTAG). Even if it involves removing (clearing) the PUSCH resource for quasi-static CSI reporting. Good. The thirteenth sub-operation is N of this TAG (or this subTAG). TA It could also mean maintaining it.

[0384] A HARQ buffer may store MAC PDUs for transmission. A may be associated with one HARQ process. One HARQ process may correspond to one HARQ process ID. Flushing a HARQ buffer may mean that the HARQ buffer becomes empty. A HARQ entity for one transport block When requesting an initial transmission (new transmission), the HARQ process uses the MAC PDU, as well as the associated MAC PDU. It can also be saved to a HARQ buffer.

[0385] Maximum uplink transmission timing difference If the MAC entity stops sending uplink transmissions for SCell because it has exceeded the limit, MAC E The NTP may consider a time synchronization timer to be expired when it stops. The time synchronization timer may be a time synchronization timer associated with SCell.

[0386] If the time synchronization timer has expired, the MAC entity will perform an uplink transmission. It is not necessary. If the time synchronization timer is not running, the MAC entity The uplink transmission does not have to be performed. This uplink transmission does not have to include a random access preamble transmission. This uplink transmission does not have to include a message A transmission. It's not necessary. This uplink transmission is an uplink transmission in one serving cell. This may also be the case. This uplink transmission may be an uplink transmission in one TRP. This time synchronization timer may be a time synchronization timer associated with the TAG to which one serving cell belongs. This time synchronization timer may be associated with the subTAG to which one serving cell belongs. This may be an associated time synchronization timer. This time synchronization timer may be an associated time synchronization timer associated with a subTAG to which one TRP belongs.

[0387] If a time synchronization timer associated with one subTAG has expired, MAC Ent. The IT performs uplink transmissions to one or more TRPs included in that one subTAG. It is not required. If the time synchronization timer associated with one subTAG has expired, the MAC entity does not need to perform the uplink transmission associated with that subTAG. This uplink transmission is either a random access preamble transmission or a message A transmission. It is not necessary to include both. For example, if a time synchronization timer associated with one TRP information has expired, the MAC entity will perform an uplink transmission associated with that TRP information. You don't have to.

[0388] If the time synchronization timer associated with PTAG is not working, the MAC entity will either In a serving cell, the MAC entity does not need to perform an uplink transmission. This uplink transmission does not include random access preamble transmission in SpCell. This is also acceptable. This uplink transmission does not necessarily have to include sending message A in SpCell.

[0389] A MAC PDU (Protocol Data Unit) may be a bit string sorted by one byte. A MAC PDU may also be a transport block. For example, a MAC PDU may consist of one or more MAC subPDUs. Each MAC subPDU is a single MAC sub. It may consist of a header. Each MAC subPDU has one MAC subheader and one MAC SDU (Service It may consist of a Data Unit. Each MAC subPDU may consist of one MAC subheader and one MAC CE (Control Element). Each MAC subPDU may consist of one MAC header and padding. Therefore, it may be constructed as follows. MAC SDU may be data from a higher layer. MAC SDU may be data to a higher layer.

[0390] A TA command may be a MAC CE. Alternatively, a TA command may be contained within a MAC CE. For example, a TA command may be contained within a TA command MAC CE. A TA command MAC CE may consist of a TAG ID and a TA command. A TAG ID is one of a TAG and one of a subTAG. Either one or both may be indicated. A TAG containing a SpCell may correspond to TAG ID 0. The TAG ID may be indicated by 2 bits. The TAG ID may indicate one subTAG. The TAG ID may indicate one TRP. The TA command is T A You may instruct T A T can be an integer from 0 to 63. A This may be used to control the amount of timing adjustment. Timing adjustment may be applied by a MAC entity. TA commands may be indicated in 6 bits. The TA command MAC CE is a MAC subheader with a certain LCID (Logical channel ID) It may be identified by Da. Some LCIDs may be LCIDs corresponding to index 61.

[0391] The TA command may be included in the absolute TA command MAC CE. The absolute TA command MAC CE may consist of a reserved bit and the TA command. The TA command has an index value T A You may instruct T A This may be used to control the amount of timing adjustment. The TA command may be indicated by 12 bits. The allocation bits may be 4 bits. The allocation bits may be set to the value 0. The absolute TA command MAC CE may consist of at least a TAG ID. The TAG ID may indicate one subTAG. The TAG ID may indicate one TRP. The absolute TA command MAC CE is , may be identified by a MAC subheader with an eLCID. The eLCID is an index It may also be an eLCID compatible with S316.

[0392] TA commands may be included in the random access response. For example, TA commands may be included in the MAC payload of the random access response. This is the index value T A You may instruct T A This may be used to control the amount of timing adjustment. The size of the TA command field may be 12 bits. The random access response may consist of a TA command, an uplink grant, and a Temporary C-RNTI. The uplink grant may indicate the resources to be used on the uplink. The uplink grant field may be 27 bits. The Temporary C-RNTI indicates a temporary ID to be used by the MAC entity during random access. This is also acceptable. The Temporary C-RNTI field may be 16 bits. The random access response may be MAC RAR. For example, the random access response may be fallbackRAR. The TA command may be included in message B (MSGB). For example, TA command The command may be included in the MAC payload of message B. The TA command may be included in successRAR. The random access response may also include TRP information. For example... Then, the TA corresponding to one TRP identified by the TRP information, the random access response This may also be indicated by TA commands included in the program.

[0393] Random access (or a random access procedure) is initiated by a MAC entity. Random access may be initiated by the PDCCH order (or PDCCH). Random access may be initiated by RRC. Random access in SCell may be initiated by the PDCCH order. Random access may also be triggered by MAC entities. Random access may be initiated by the PDCCH order. It may be triggered. Random access may be triggered by RRC.

[0394] For example, random access may be triggered (started) by an event. For example, an event may be initial access from the RRC_IDLE state. For example, an event may be the RRC connection re-establishment procedure. For example, an event may be the arrival of uplink or downlink data in the RRC_CONNECTED state when the uplink synchronization state is 'non-synchronized'. For example, one event may be the arrival of uplink data in the RRC_CONNECTED state when there is no PUCCH resource. For example, one event may be the failure of a scheduling request. For example, one event may be a response from RRC in response to a handover. It could be a quest. For example, an event could be an RRC connection resume. For example, an event could be establishing a time alignment. For example, an event could be establishing a time alignment for STAG. For example, an event could be establishing a time alignment for TRP. For example, an event may be a request for Other SI. For example, an event may be beam failure recovery. For example, one event could be the acquisition of a TA (Trial Access). Another event could be the acquisition of a Secondary TA. The event could also be the objective of a random access procedure.

[0395] Random access (random access type) may also be 4-step random access (4-step random access type). (P) may be a 2-step random access (2-step random access type) . Random access may support CBRA (Contention-based random access). That is, random access may be CBRA. Random access may support CFRA (Contention-free random access). That is, random access may be CFRA. For example, random access is a 4-step random access type. It may also be a CBRA. For example, random access may be a 4-step random access type CFRA. For example, random access may be a 2-step random access type CBRA. For example, random access may be a 2-step random access CFRA.

[0396] In a 4-step random access type CBRA, terminal device 1 receives message 1 (random). In a 2-step random access type CBRA, terminal device 1 may send message A (random access preamble and PUSCH payload) and receive message B (conflict resolution). In a 4-step random access type CFRA, terminal device 1 may assign a random access preamble. The terminal device 1 may receive, send a random access preamble, and receive a random access response. In a 2-step random access type CFRA, terminal device 1 sends a random access preamble. The system may receive a sespriamble and PUSCH assignment, send a random access preamble and PUSCH, and receive a random access response.

[0397] If a CFRA resource is not configured, RSRP (Reference signal received power) is used to select either a 2-step random access type or a 4-step random access type. A threshold may be used. 4-step random access type CFRA resource If the setting is configured, terminal device 1 will use a 4-step random access type random access If a 2-step random access type CFRA resource is configured, terminal device 1 may perform a 2-step random access type random access. stomach.

[0398] Message 1 may consist of a single preamble in PRACH. After sending Message 1, terminal device 1 receives one response (random accessless) within the configured window. You may monitor the response. CFRA uses a dedicated preamble. It may be assigned. In CFRA, in response to the receipt of a random access response, terminal device 1 The random access may be terminated. In CBRA, terminal device 1 may send message 3 in response to receiving a random access response. For example, terminal device 1 may send message 3. You can send message 3 using a grant (random access response grant). i. In CBRA, terminal device 1 may monitor message 4 (conflict resolution). Message 3 If contention resolution after transmission fails, terminal device 1 may send message 1.

[0399] Message A may include a preamble in PRACH. Message A may also include a payload in PUSCH. After sending Message A, terminal device 1 is configured... In CFRA, one response may be monitored within the window. In CFRA, a dedicated preamble and PUSCH resource may be allocated for sending message A. In CFRA, terminal device 1 may terminate random access upon receiving one response. In CBRA, If conflict resolution is successful, terminal device 1 may terminate random access. If a fallback indication is received in B, terminal device 1 You may send message 3 based on the fallback instruction and monitor the conflict resolution. If conflict resolution after sending message 3 is unsuccessful, terminal device 1 will send message A but Good. If a 2-step random access type random access is not completed, terminal device 1 may be configured to switch to a 4-step random access type CBRA.

[0400] Random access procedures may be initiated (triggered) by a PDCCH order. Random access procedures may be initiated (triggered) by MAC. Random access procedures may be initiated (triggered) by RRC. Random access procedures in SCells may be initiated by PDCCH order. Random access in cells related to additional PCI indexes The access procedure may be initiated by a PDCCH order.

[0401] In a MAC entity, only one random access may be running simultaneously. If a first random access is in progress and a second random access is triggered, terminal device 1 may continue the first random access. If it is in progress and a second random access is triggered, terminal device 1 may initiate a second random access.

[0402] For random access, RRC uses some or all of the top layer parameters from the first to the ninth layer. The part may be set. The first set of PRACH Occasions for sending Message 1 (Random Access Preamble) may be set by the first upper layer parameter. The first set may be used for Message A PRACH. The second set of PRACH Occasions for sending the Random Access Preamble for Message A may be set by the first upper layer parameter This may be set by a meter. That is, the first upper layer parameter may determine the available set of PRACH opportunities for sending a random access preamble. PRACH opportunities may also be referred to as RA opportunities. PRACH opportunities may also be referred to as RACH opportunities (RACH occasions).

[0403] Some or all of the first to ninth upper-layer parameters may be referred to as RACH settings. RACH settings may be configured in the upper-layer parameters SI-RequestConfig, ReconfigurationWithSync, BeamFailureRecoveryConfig, RACH-ConfigCommon, TwoTA-Config1-r18, and TwoTA-Config2-r18. RACH settings are configured in the upper-layer parameter SI-RequestConfig, The RACH configuration may be included in some or all of the upper-layer parameters ReconfigurationWithSync, BeamFailureRecoveryConfig, RACH-ConfigCommon, TwoTA-Config1-r18, and TwoTA-Config2-r18. RACH-ConfigGeneric is also acceptable.

[0404] The first upper-level parameter may be prach-ConfigurationIndex. The first upper-level parameter may be set in the configuration for obtaining the second TA (either or both of the upper-level parameters twoTA-Config1-r18 and twoTA-Config2-r18). Obtaining the second TA involves determining and providing two TAs (TAGs, or subTAGs) in one serving cell. Alternatively, it may be set.

[0405] The power of the random access preamble may be set by a third upper-layer parameter. For example, the power of the initial (first-transmission) random access preamble may be set by a third upper-layer parameter.

[0406] The RSRP threshold may be set by a fourth upper-level parameter. For example, the RSRP threshold may be for SS / PBCH block selection or CSI-RS selection. The RSRP threshold may be an RSRP threshold for selection between two uplink carriers, even if the two uplink carriers are NUL (Normal Uplink) and SUL (Supplementary Uplink). good.

[0407] The maximum number of transmissions of one or both of Message 1 and Message A may be set by a fifth upper-layer parameter. The transmission power of one or both of Message 1 and Message A may be changed with each transmission. For example, the power of one or both of Message 1 and Message A may be changed based on a sixth upper-layer parameter. The sixth upper-layer parameter may be the power ramping factor.

[0408] The random access preamble may be set by a seventh upper layer parameter. For example, the index of the random access preamble used in the PRACH opportunity. However, it may be set by a seventh upper layer parameter. The seventh upper layer parameter is 0 It may represent any of the values ​​from 6 to 63. The seventh upper layer parameter may be ra-PreambleIndex.

[0409] The number of SS / PBCH blocks mapped to each PRACH opportunity may be defined by the eighth upper layer parameter. The number of ampoules may be defined by the eighth upper layer parameter. The CBRA random access preamble may be a Contention-based Random Access Preamble. Sending either or both of Sage 1 and Message A is to Group A, or Gru A random access preamble corresponding to group B may be used. For example, terminal device 1 may perform message A transmission using random access preamble group A. For example, terminal device 1 may perform message A transmission using random access preamble group B. You may perform this action.

[0410] The ninth upper-layer parameter may define a PRACH opportunity associated with a single SS / PBCH block (SSB). MAC entities send a random access preamble in the PRACH opportunity. This is also acceptable. The ninth upper layer parameter may be ra-ssb-OccasionMaskIndex.

[0411] The first to twelfth variables (UE variables) may be used for random access procedures. The first variable may be PREAMBLE_INDEX. The second variable may be PREAMBLE_TRANSMISSION_COUNTER. The third variable may be PREAMBLE_POWER_RAMPING_COUNTER. It may be present. The fourth variable may also be PREAMBLE_POWER_RAMPING_STEP. The fifth variable The number may be PREAMBLE_RECEIVED_TARGET_POWER. The sixth variable may be PREAMBLE_BACKOFF. The seventh variable may be PCMAC. The eighth variable may be SCALING_FACTOR_BI. The ninth variable may be TEMPORARY_C-RNTI. The tenth variable may be RA_TYPE. The eleventh variable may be POWER_OFFSET_2STEP_RA. The twelfth variable may be MSGA_PREAMBLE_POWER_RAMPIPNG_STEP.

[0412] RA_TYPE may be set to 4-stepRA. For example, when a random access procedure is initiated by a PDCCH order, and the index of the random access preamble (ra-PreambleIndex) is provided by the PDCCH, and the index of the random access preamble If the dex is not 0b000000, RA_TYPE may be set to 4-stepRA. For example, SI If a random access procedure is initiated for a request, and a random access resource (RACH setting) is provided by the RRC for the SI request, RA_TYPE may be set to 4-step RA. If a random access procedure is initiated for beam fault recovery (or beam fault recovery for SpCell), and a CFRA resource corresponding to a beam fault recovery request for the 4-step random access type is provided, RA_TYPE A 4-step RA may be set for this. If a random access procedure is initiated, and the higher-level parameter rach-ConfigDedicated provides a CFRA resource for a 4-step random access type, then RA_TYPE may be set to 4-stepRA. For example, to obtain the second TA, a random access If the procedure is initiated, and to obtain the second TA, random access resources (for example) If a CFRA resource is provided, RA_TYPE may be set to 4-stepRA. A random access resource may be either a CFRA resource or a CBRA resource, or both. Providing a random access resource may mean setting the RACH configuration. Second TA acquisition means obtaining a second (or two) TA in a single serving cell. It is also possible to obtain this. If RA_TYPE is set to 4-stepRA, 4-step RA Random access of the random access type may be performed. RA_TYPE is set to 2-stepRA. If this occurs, a two-step random access type random access may be performed.

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

[0414] The first action may be performed if a random access procedure is initiated for beam failure recovery. The first action may also be performed if the beam failure recovery timer (beamFailureRecoveryTimer) is running or not set. The first action may be performed if contention-free Random Access Resources (CFRA resources) for beam fault recovery requests are provided by the RRC. The beam fault recovery request may be related to either the SSB or the CSI-RS. The first action is at least This may be done if another SSB, or at least one CSI-RS, is available. At least one SSB may have an RSRP (Reference Signal Received Power) exceeding the threshold. At least one CSI-RS may have an RSRP exceeding the threshold. In the first action, the MAC entity may select the first SSB. The first SSB is The first SSB may be an SSB included in the first set of reference signals. The first SSB may be an SSB with an RSRP exceeding a certain threshold. In the first operation, the MAC entity i may select a first CSI-RS. The first CSI-RS may be a CSI-RS included in the first reference signal set. The first CSI-RS may be a CSI-RS with an RSRP exceeding a certain threshold. The first reference signal set is defined by candidateBeamRSList. It may be set. If the first SSB is selected, the first random accessory is set to PREAMBLE_INDEX. A spriamble index (ra-PreambleIndex) may be set. The first random access preamble index may be the ra-PreambleIndex corresponding to the SSB selected from a set of random access preambles for beam fault recovery.

[0415] The second action may be performed if a random access preamble index (ra-PreambleIndex) is provided by PDCCH (PDCCH order). The second action may be performed if the random access preamble index is not 0b000000. In the second action, the MAC entity sets the random access preamble index to PREAMBLE_INDEX. You may set the jack. In the second operation, one SSB is indicated (signaled) by the PDCCH. It may also be used.

[0416] The second action may be performed if a random access preamble index (ra-PreambleIndex) is provided by PDCCH (PDCCH order). The second action may be performed if the random access preamble index is not 0b000000. The second action may be performed if PDCCH provides the first value. The second action may be performed if the first value is determined by PDCCH. In the second action, MAC entities The first value may be set to a second random access preamble index in PREAMBLE_INDEX. The second random access preamble index may be a random access preamble index for obtaining the second TA. The second random access preamble index may be a ra-PreambleIndex corresponding to the indicated SSB from the set of random access preambles for obtaining the second TA. The first value may identify a single RACH setting. The first value may identify a single upper-level parameter containing a RACH setting. The first value may be an additional PCI index, TAG ID, and TRP information.

[0417] The third action may be performed. In rach-ConfigDedicated, the CFRA related to SSB If a source is provided, the third action may be performed. The third action may be performed if at least one SSB is available. At least one SSB may be an SSB with an RSRP exceeding a certain threshold. In the third action, the MAC entity may select one SSB. One SSB may have an RSRP exceeding a certain threshold. In the third action, PREAMBLE_INDEX may be set to ra-PreambleIndex, which corresponds to the selected SSB.

[0418] A fourth action may be performed. If a random access procedure for an SI request is initiated, a fourth action may be performed. If a random access resource for an SI request is provided by the RRC, a fourth action may be performed. In the fourth action, If at least one SSB is available, the MAC entity may choose one SSB. i. At least one SSB may have an RSRP exceeding a certain threshold. One SSB may have an RSRP exceeding a certain threshold. In the fourth action, the MAC entity may select any SSB. In the fourth action, it is determined according to the upper layer parameter ra-PreambleStartIndex. From the random access preambles, one random access preamble corresponding to the selected SSB may be selected. In the fourth action, the selected random access preamble may be set in PREAMBLE_INDEX.

[0419] A fifth action may be performed. A fifth action may be performed for CBRA preamble selection. In the fifth action, the MAC entity may select one SSB. One SSB is This may be accompanied by RSRP exceeding a certain threshold. Also, in the fifth operation, the MAC entity is responsible You may choose the SSB of your choice.

[0420] The sixth action may be performed. The sixth action may be performed if a random access procedure for obtaining the second TA is initiated. The sixth action may be performed if the random access resources for obtaining the second TA are provided by the RRC. In the sixth action, the MAC entity may select one SSB. The SSB may have an RSRP exceeding a certain threshold. In the sixth action, any SSB may be selected. In the sixth action, a random access preamble index (ra-PreambleIndex) corresponding to the selected SSB may be set. The random access resources for obtaining the second TA may be determined in one or both of the upper layer parameters twoTA-Config1-r18 and twoTA-Config2-r18.

[0421] The random access preamble is related to the reference signal (either SSB or CSI-RS). This is also good. For example, the number of random access preambles per reference signal is good for the upper layers. It may be determined by Lameter.

[0422] If a random access procedure is initiated for an SI request and the first upper-layer parameter is set, the MAC entity may determine a first PRACH occasion. The first PRACH occasion may be related to the selected SSB. This may be determined based on a first restriction, which may be given by the upper-level parameter ra-ssb-OccasionMaskIndex. The first PRACH opportunity may be the next valid PRACH opportunity. The first upper-level parameter may be either or both of ra-AssociationPeriodIndex and si-RequestPeriod.

[0423] If RA_TYPE is set to 4-StepRA, then one of the first through sixth operations will occur. If SSB is selected, the MAC entity may determine a second PRACH opportunity. The selected SSB may be permitted by the first restriction. The selected SSB may be indicated by the PDCCH (PDCCH Order).

[0424] If RA_TYPE is set to 4-StepRA, then one of the first through sixth operations will occur. In the event that a CSI-RS is selected and there are no CFRA resources associated with the selected CSI-RS, the MAC entity may determine a third PRACH opportunity based on the SSB.

[0425] If RA_TYPE is set to 4-StepRA, then one of the first through sixth operations will occur. In this case, if CSI-RS is selected, the MAC entity corresponds to the selected CSI-RS. You may determine four PRACH opportunities.

[0426] Random access (random access procedure) is initiated in one serving cell. At that time, the MAC entity may flush the message 3 buffer, or flush the message A buffer, and select a carrier to perform random access. You may do this, determine the random access type, or perform a Random Access Resource selection procedure.

[0427] A MAC entity may randomly select one PRACH opportunity from among several PRACH opportunities.

[0428] A MAC entity may perform the procedure for sending a random access preamble.

[0429] The MAC entity powers each random access type based on a counter. The MAC entity may determine the PRACH opportunity to which the random access preamble is sent. The MAC entity then determines the selected PRACH opportunity. The physical layer may be instructed to send a random access preamble using PRACH. The RA-RNTI associated with the opportunity is an index of the leading OFDM symbol of the PRACH opportunity and one system The index may be calculated based on some or all of the index of the leading slot of the PRACH opportunity in the system frame, the index of the PRACH opportunity in the frequency domain, and the uplink carrier on which the random access preamble is transmitted.

[0430] The MAC entity is the first window from the end of sending the random access preamble. You may start this. The random access preamble may be a CFRA random access preamble (Contention-free Random Access Preamble). The random access preamble may be a CBRA random access preamble (Contention-based Random Access Preamble). The MAC entity uses PDCCH for random access responses. It may be monitored. For example, while the first window is operating, the MAC entity may monitor the PDCCH. The PDCCH may be the PDCCH in SpCell. Reception of PDCCH The notification may be received from the physical layer. The PDCCH transmission may be addressed to C-RNTI. If the CFRA random access preamble is transmitted by the MAC entity, the MAC entity may consider the random access to have been successfully completed.

[0431] A valid downlink assignment may be received in the PDCCH corresponding to RA-RNTI. The received transport block may be decoded. The random access response may contain a MAC subPDU. The MAC subPDU may be accompanied by a random access preamble ID. Based at least on the fact that the random access response contains a MAC subPDU, the MAC entity has successfully received the random access response. It can be considered as such.

[0432] A MAC entity may consider the receipt of a random access response to have been successful. Based at least on the fact that the reception of the random access response is considered successful, the MAC entity may consider the random access to have been successfully completed, instruct the higher layer to receive an ACK (acknowledgment), and apply the received TA command. For example, a MAC entity may process the value of an incoming UL grant. For example, a MAC entity may instruct the physical layer to process the incoming UL grant.

[0433] If the receipt of a random access response is considered successful, and one service When a random access preamble is sent in a ping cell, the MAC entity You may apply (process) a TA command for one serving cell. The receipt of a random access response is considered successful, and in one serving cell, The transmission of the dam access preamble and, at least based on this, the MAC entity The TA command may be applied to one serving cell. Random access Based at least on the fact that the response is considered to have been received successfully, the MAC entity A TA command may be applied for a single TRP. For example, a MAC PDU can be used as a TA command (for example) If it includes an absolute TA command (MAC CE), the MAC entity may process the TA command. For example, a MAC PDU may be included in a transport block. For example One or more MAC SDUs may be multiplexed into a transport block. For example, 1 Alternatively, multiple MAC SDUs are demultiplexed from the transport block. That's good too.

[0434] For MAC entities, the BFR (Beam Failure Recovery) procedure is implemented at RRC. Therefore, it may be set. The BFR procedure setting may include the RACH setting. The BFR procedure setting may also be the upper layer parameter BeamFailureRecoveryConfig. A MAC entity may trigger BFR based on the value of BFI_COUNTER. BFI_COUNTER is a beam fault candidate indicator This could be a counter for Beam Failure Instance Indication (BFR) triggered. If so, the first random access procedure may be initiated. The first random access procedure may be a random access procedure for beam fault recovery.

[0435] Terminal device 1 may receive upper-layer parameters. Terminal device 1 may initiate a random access procedure in response to receiving the upper-layer parameter RRCReconfiguration. For example, when the upper-layer parameter RRCReconfiguration is received in the upper-layer parameter nr-SCG, and the upper-layer parameter nr-SCG includes the upper-layer parameter reconfigurationWithSync. Terminal device 1 may initiate a second random access procedure in RRC. RRCReconfiguration may be received for NR SCG RRC Reconfiguration. The second random access procedure is random access for Reconfiguration with sync. Procedures are also acceptable.

[0436] For MAC entities, the procedure for obtaining the second TA may be configured by RRC. The configuration of the second TA acquisition procedure may include RACH configuration. The configuration of the second TA acquisition procedure may be either or both of TwoTA-Config1-r18 and TwoTA-Config2-r18. MAC entities are This may trigger the acquisition of a second TA. For example, the MAC entity may be associated with the subTAG. A second TA acquisition may be triggered based on the expiration of the first TA. Up to two subTAGs may be provided in one serving cell. The second TA acquisition may be triggered in one serving cell. This may be triggered to set up two TAs (TAGs). Based on the triggering of the acquisition of the second TA, a third random access procedure may be initiated. The third random access procedure may be a random access procedure for acquiring the second TA. TwoTA-Config1-r18 , and if either or both of TwoTA-Config2-r18 are provided, for obtaining the second TA The random access procedure may be initiated in MAC or RRC.

[0437] Before initiating random access (physical random access procedure), the physical layer may receive a set of SS / PBCH block indices from the upper layer and provide the upper layer with a set of RSRP measurements. The physical layer may provide the upper layer one or more parameters to the upper layer before initiating random access. Before initiating random access, the physical layer may instruct the upper layer to perform type 2 random access. Type 1 random access may be a 4-step random access type random access. Type 2 random access may be a 2-step random access type random access. Before initiating random access, the physical layer may provide the upper layer one or more parameters to the upper layer It may be received from the layer. One or more parameters may include setting PRACH transmit parameters. Setting PRACH transmit parameters may be RACH settings. PRACH transmit parameters may be PRACH preamble format for PRACH transmission, time resources, or frequency resources. One or more parameters determine the root sequence. The following parameters may be included. One or more parameters are part of the PRACH preamble sequence ( Parameters that determine the cyclic shift in the series of the DOM access preamble It may include one or more parameters. It may include TRP information. For example, one The random access preamble may be associated with a single TRP.

[0438] Random access reduces the number of messages sent in PRACH, message 1, message 2, etc. It may also include: Random access may include sending message 1 in PRACH, message 2, sending PUSCH scheduled by a Random access response uplink grant, and PDSCH for conflict resolution. Message 1 may be a random access preamble. Message 2 may be a random access response message (random access response). For example, message 2 may be a random access response accompanied by PDCCH / PDSCH. A random access procedure is referred to as random access. That's good too.

[0439] Random access may include at least sending message A and receiving message B. Random access may include sending message A, receiving message B, sending a PUSCH scheduled by a random access response grant, and conflict resolution. PDSCH for this purpose may include, and. Message A is a random access program in PRACH. It may also be a rambil and a PUSCH. Message B may also be a random access response. For example, Message B may be a random access response accompanied by PDCCH / PDSCH. The random access response grant may also be a fallback random access response grant.

[0440] When random access is initiated by a PDCCH order, PRACH transmission (random access A sessile transmission may have the same subcarrier interval as a PRACH transmission initiated by a higher layer. If two uplink carriers are configured in a serving cell, and terminal device 1 detects a PDCCH order, terminal device 1 may use the value of the UL / SUL instruction field from the detected PDCCH order to determine one uplink carrier for the PRACH transmission. If N TRPs are configured in a serving cell... If both terminal devices 1 and terminal device 1 detect a PDCCH order, terminal device 1 will determine one TRP for PRACH transmission by looking at one field (or field) of the detected PDCCH order. The value of the world may be used. In the random access procedure for obtaining the second TA, one field of the PDCCH order may include an additional PCI index.

[0441] Random access may be triggered by a higher layer or by the PDCCH order in response to a PRACH transmission request. The higher layer configuration for PRACH transmission may include some or all of the following: the PRACH transmission configuration, the preamble index (index of the random access preamble), the preamble SCS (subcarrier interval of the random access preamble), RA-RNTI, the PRACH resource, and TRP information.

[0442] Random access preambles may also be contention-based preambles. The dam access preamble may be a contention-free preamble. Valid PRACH The number of contention-based preambles per opportunity and per SS / PBCH block index may be set by higher-level parameters. PRACH opportunities may be enabled. For example, Based at least on the OFDM symbol set for time-division duplexing, the PRACH opportunity is It may be effective.

[0443] Terminal device 1 decodes DCI format 1_0 with CRC scrambled with RA-RNTI. It may attempt to do so. For example, in response to a PRACH transmission, terminal device 1 may attempt to decode DCI format 1_0 with a RA-RNTI scrambled CRC within a window. The window is opened based at least on the leading OFDM symbol of CORESET. It can also be used from the start.

[0444] Terminal device 1 detects DCI format 1_0 with CRC scrambled by RA-RNTI. Furthermore, based at least on the terminal device 1 receiving a transport block, Terminal device 1 may pass the transport block to the upper layer. For example, transport The PRACH may be received in a PDSCH within a window. The upper layer may parse the transport block corresponding to the Random access preamble identity (RAPID) associated with the PRACH transmission. When identifying RAPID in a response (random access response message), The upper layer may instruct the physical layer to ascend and grant a link grant (random access response grant). The random access response may be a random access response of a transport block. The random access response grant is a random access A response-boosting link grant is also acceptable.

[0445] Terminal device 1 displays DCI format 1_0 with CRC scrambled with RA-RNTI. If not detected within the window, or if the transport block in PDSCH is not windowed If it is not received internally, the upper layer may instruct the physical layer to send PRACH. If the upper layer does not identify the RAPID associated with sending PRACH, the upper layer will not send PRACH. The physical layer may be instructed to do the following. For example, terminal device 1 may instruct the last OFDM symbol of the window It may be expected that PRACH will be sent within a predetermined time from the last OFDM symbol received by PDSCH. Furthermore, terminal device 1 may be expected to send PRACH within a predetermined time from the last OFDM symbol received by PDSCH. Sending PRACH is equivalent to sending a random access preamble. That's fine.

[0446] A PDCCH order may trigger a CFRA (Contention-free random access procedure). For example, a PDCCH order may trigger a CFRA in a single SpCell. The commander may initiate PRACH transmission. Terminal device 1 is initiated by the PDCCH order. When attempting to detect DCI format 1_0 with CRC scrambled by RA-RNTI in response to a PRACH transmission, PDCCH and PDCCH containing DCI format 1_0 will be on the same DMRS antenna. It may be assumed that the port has QCL characteristics. The QCL characteristics may also be large-scale characteristics of the channel.

[0447] A random access response grant (random access response) is one or more. It may consist of fields. For example, one or more fields may be frequency hopping It may include a flag field. For example, one or more fields may be frequency range Includes a region resource allocation field (or a PUSCH frequency resource allocation field). That's fine too. For example, one or more fields could be time domain resource allocation fields. It may include a D (or PUSCH time resource allocation field). For example, one or more fields may include a TPC (Transmission power control) command field. For example, one or more fields may include a CSI request field. For example, one or more fields may include a field containing TRP information.

[0448] When the CRC of DCI format 1_0 is scrambled by C-RNTI, and the frequency range If all area resource allocation fields are "1", DCI format 1_0 is the first It may be used for random access procedures. The first random access procedure is PDCCH This may also be called an order-initiated random access procedure, i.e., DCI. The PDCCH into which format 1_0 is placed (mapped) may be in PDCCH order.

[0449] The DCI format in the PDCCH order may include a Random Access Preamble Index field. The Random Access Preamble Index may also be ra-PreambleIndex. The DCI format in the PDCCH order may include a UL / SUL indicator field. The UL / SUL indicator field may indicate a UL carrier. The DCI format in the PDCCH order may include an SS / PBCH index field. The SS / PBCH index field may indicate one SS / PBCH. One SS / PBCH is a RACH for PRACH transmission. It may be used to determine opportunities (PRACH opportunities). Random access preamble If the index values ​​are not all "0", the SS / PBCH index field may indicate one SS / PBCH. The DCI format in PDCCH order is PRACH mask index The PRACH Mask Index field may be included. The PRACH mask index field may indicate one RACH opportunity. One RACH opportunity may be associated with one SS / PBCH. If the values ​​of the random access preamble index are not all "0", the PRACH mask index field may indicate one RACH opportunity. In the PDCCH order The DCI format may include an Additional PCI Index field. The Additional PCI Index field points to the first higher-level parameter, including the RACH setting. It may be indicated. The additional PCI index field indicates one additional PCI index. It is also possible that one additional PCI index may be associated with the first upper-tier parameter, which includes the RACH setting. The first upper-tier parameter may be twoTA-Config1-r18. The level parameters may also be twoTA-Config2-r18.

[0450] PCI (Physical Cell ID) may also be called the physical cell ID. Additional PCI may be the physical cell ID for non-serving cells. The additional PCI index is It may be an index for identifying additional PCIs. The additional PCI index may be set by higher-level parameters. The additional PCI index may be indicated by the DCI field. The additional PCI index may also be used to indicate the physical cell ID. good.

[0451] DCI formats 1_0 / 1_1 / 1_2 may be used for PDSCH scheduling. The Bandwidth Part Indicator (BWP) field may be included in either or both of DCI Format 1_1 and DCI Format 1_2. The number of information bits constituting the BWP field may be determined based on the number of DL BWPs. The TPC command (TPC command for scheduled PUCCH) field may be included in either or both of DCI Format 1_1 and DCI Format 1_2. Second TPC command for scheduled The PUCCH) field is either DCI Format 1_1 or DCI Format 1_2 or It may be included in both. For example, if the upper-level parameter SecondTPCFieldDCI is set. The second TPC command (Second TPC command for scheduled PUCCH) field may be included in DCI format 1_1.

[0452] DCI Format 1_0, DCI Format 1_1, and DCI Format 1_2 are PDSCH It may also be a DCI format for scheduling. DCI format 1_0 may be used for scheduling PDSCH in a single downlink cell.

[0453] The antenna port(s) field may be included in DCI format 1_1 and DCI format 1_2. Information bits constituting the antenna port field. The number may be 4, 5, or 6 bits. Also, the antenna port field is configured The number of information bits may be 4, 5, 6, or 7 bits. Also, 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 a value may be any of values ​​1, 2, or 3. The number of CDM groups without data may refer to CDM group 0. A value of 2 indicates a CDM group without data. The number of groups may refer to CDM groups {0, 1}. The number of CDM groups with no data (value 3) may refer to CDM groups {0, 1, 2}.

[0454] The higher-level parameter dmrs-Type being 1 means that DMRS setting type 1 is set. It is acceptable. The higher-level parameter dmrs-Type being 2 means that DMRS setting type 2 is set. It may also be the case that the upper layer parameter maxLength is 1, which may mean that the maximum number of forward DMRS symbols is 1. This means that the maximum number of forward DMRS symbols may be 2 symbols. For example, The positional parameter maxLength being 1 means that a single symbol forward DMRS (forward DMRS single It may also be the case that the volt is set. For example, the upper layer parameter maxLength is 2. This may involve setting a single-symbol forward DMRS (forward DMRS symbol) or a double-symbol forward DMRS.

[0455] The number of DMRS ports may be the number of layers (number of transmitting layers) v. Antenna ports {p0,..., {pv-1}(antenna port value, antenna port number) may be the sum of the DMRS port (DMRS port value, DMRS port number) and 1000. For example, DMRS port 0 may correspond to antenna port p0=1000. For example, DMRS port 1 may correspond to antenna port p1=1001. For example, DMRS ports {0,1} may correspond to antenna ports {p0=1000,p1=1001}. For example, DMRS ports {2,3} may correspond to antenna ports {p2=1002,p3=1003}.

[0456] The TCI (Transmission configuration indication) field may be included in either or both of DCI format 1_1 and DCI format 1_2. For example, if higher-level parameters are set, the TCI (Transmission configuration indication) field may be DCI It may be included in either or both of Format 1_1 and DCI Format 1_2. Example For example, if the upper-level parameter tci-PresentInDCI is set, the TCI (Transmission configuration indication) field may be included in either 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 are indicated in the DCI format. This may be indicated by a field.

[0457] The DCI format 0_0 / 0_1 / 0_2 may be used for scheduling in PUSCH. The Bandwidth Part Indicator (BWP) 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 field may be determined based on the number of UL BWPs. The TPC command (TPC command for scheduled PUSCH) field may be included in either or both of DCI Format 0_1 ​​and DCI Format 0_2. Second TPC command for scheduled The PUSCH) field is either DCI format 0_1 ​​or DCI format 0_2 or It may be included in both. For example, if the upper-level parameter SecondTPCFieldDCI is set. The second TPC command (Second TPC command for scheduled PUSCH) field may be included in DCI format 1_1.

[0458] The SRS resource indicator field is in DCI format 0_1, and The SRS resource set indicator field may be included in either 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, the precoding information and layer count fields may relate to a first SRS resource set. If the SRS resource set indicator field indicates 1 ("01"), the SRS resource indicator field, the precoding information and layer count fields may relate to a second SRS resource set. If the SRS resource set indicator field indicates 2 ("10"), the SRS resource indicator field, the precoding information and layer count fields may relate to a first SRS resource set. Also, if the SRS resource set instruction field indicates 2 ("10"), the second SRS resource - Instruction field and the second “Precoding information and layer count field” (second The precoding information field of the SRS resource set may also relate to a second SRS resource set. If the SRS resource set instruction field indicates 3 ("11"), the SRS resource instruction field The first SRS resource set contains fields for pre-coding information and layer count. It may also relate to the following: If the SRS resource set instruction field indicates 3 ("11"), then the second SRS resource instruction field and the second "precoding information and layer count field "D" may also be related to the second SRS resource set.

[0459] Terminal device 1 performs uplink physical based on uplink timing (Timing Advance: TA) It transmits channels / signals (e.g., PUSCH, PUCCH, SRS). Also, multiple identical uplink timings may belong to one TAG or one subTAG. One TAG or one subTAG may be associated with one TAG ID, or may be identified by one TAG ID. Therefore, as a challenge, when terminal device 1 transmits an uplink physical channel / signal, 1 Two TAG IDs need to be indicated or determined. The present invention may be used as a means of solving the problem for determining TAG IDs when two uplink timings are provided in one serving cell.

[0460] Figure 14 shows an example of TCI state management according to one aspect of this embodiment. A black circle may represent a single TCI state.

[0461] One or more TCI states 1000 may be set by higher-level parameters. For example, one or more UL TCI states (UL-TCIState) may be set by higher-level parameters for each uplink BWP (BWP-UplinkDedicated). For example, one or more DL / Joint TCI states (DLorJointTCIState) may be set by higher-level parameters for each PDSCH configuration (PDSCH-Config). It is also possible that one TCI state may be associated with one TCI state ID. For example, one UL TCI state A state may be associated with a single UL TCI state ID (TCI-UL-State-Id, UL-TCIState-Id). For example, a single DL / Joint TCI state (TCI-state) may be associated with a single TCI state ID (TCI-stateId). i. One or more TCI states set by the higher-level parameters may be the set TCI state 1000.

[0462] One or more TCI states 1001 may be activated by MAC CE (e.g., activation command). PDSCH may transmit a first transport block. A block may be a single MAC PDU. A single MAC PDU may contain an activation command, or a MAC CE referred to as an activation command. For example, an activation command may be activation command D, or activation command E. One or more TCI states, and one or both of one or more “pairs of TCI states”, are one or more code points They may be mapped to one or more code points. For example, an activation command may map one or more TCI states, and one or both of a “pair of TCI states,” to one or more code points. Each TCI state, or each pair of TCI states, may be mapped to one code point. For example, each TCI state, or each pair of TCI states, may be mapped to a single code point by an activation command. The code points to be mapped may also be code points in the TCI field. The code points to which a TCI state, or a pair of TCI states, are mapped are in DCI format 1_1, Alternatively, it may be a code point of a TCI field in DCI format 1_2. A code point to which a TCI state, or a pair of TCI states, is mapped may be a code point of a TCI field in either DCI1040 or DCI1041. For example, DCI1040 is The activation command in the associated CORESET pool index 1080 maps the TCI state, or a pair of TCI states, to the code point of the TCI field in DCI 1040. Alternatively, a TCI state, or a pair of TCI states, may be mapped to a code point in the TCI field of DCI1041 by an activation command in the associated CORESET pool index 1081. TCI states activated by MAC CE (activation command) The state 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.

[0463] If the CORESET pool index (coresetPoolIndex) is not set in one or more CORESETs (ControlResourceSets), the activation command E may be used. When the coresetPoolIndex is set in one or more CORESETs (ControlResourceSets), activation command D or activation command E may be used. For example, in single-DCI mode, activation command E may be used. For example, in multi-DCI mode, activation command D may be used. For example, in both single-DCI and multi-DCI modes, activation command E may be used.

[0464] One or more TCI states 1002 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 TCI (Transmission configuration indication) field. The TCI field is 1 Alternatively, multiple (e.g., two or four) TCI states may be indicated. For example, one value in the TCI field may correspond to one code point in the TCI field. The TCI state indicated by the first DCI format may be indicated TCI state 1002. Indicated TCI state 1002 may be some or all of the UL TCI state, DL TCI state, and Joint TCI state. The UL TCI state may be the TCI state for PUSCH, PUCCH, and SRS. The DL TCI state may be the TCI state for PDSCH, PDCCH, and CSI-RS. The Joint TCI state is the TCI state for PUSCH, PUCCH, SRS, PDSCH, PDCCH, and CSI-RS. It's fine to act that way.

[0465] The number of TCI states 1002 to be indicated may be 4. For example, the number of TCI states 1002 to be indicated is: There may be a first pair consisting of a first UL TCI state and a first DL TCI state, and a second pair consisting of a second UL TCI state and a second DL TCI state. The first pair may also be related to a first TRP. The second pair may also be related to the second TRP.

[0466] The number of TCI states 1002 to be indicated may be 3. For example, the number of TCI states 1002 to be indicated is: The first pair consists of the first UL TCI state and the first DL TCI state, and the third DL / UL / Joint TCI state. It may exist. The first pair may be related to the first TRP, and the third DL / UL / Joint TCI state may be related to the second TRP. The first pair may be related to the second TRP, and the third DL / UL / Joint TCI state may be related to the first TRP.

[0467] The number of TCI states 1002 that are indicated may be 2. For example, the number of TCI states 1002 that are indicated may be: There 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.

[0468] The number of TCI states 1002 that are indicated may be 2. For example, the number of TCI states 1002 that are indicated may be: The first pair may be 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.

[0469] The number of TCI states 1002 that are indicated may be 1. For example, the number of TCI states 1002 that are indicated may be: The first DL / UL / Joint TCI state may also be. The first DL / UL / Joint is not related to TRP. This is also acceptable. The first DL / UL / Joint TCI state may be associated with the first TRP. The first DL / UL / Joint TCI state may be associated with the second TRP.

[0470] The indicated TCI state 1002 is N from the last OFDM symbol of PUCCH1060 or PUCCH1061. symb It may be applied from the first slot after the symbol. For example, the indicated TCI state 1002 This is the last OFDM symbol of PUCCH1060, which is instructed to be transmitted by DCI1040. symb Symbol It may be applied from the first slot after the first. For example, the indicated TCI state 1002 may be applied from the last OFDM symbol of PUCCH1061 which is indicated to be transmitted by DCI1041. symb It may be applied from the first slot after the symbol. The indicated TCI state 1002 may be applied to multiple channels / signals. symb This could also be BeamAppTime. For example, if DCI1040 is associated with CORESET pool index 1080, the indicated TCI state 1002 could be TCI state 1010. For example, if DCI1041 is associated with CORESET pool index 1081, the indicated TCI state 1002 could be TCI state 1011.

[0471] One or more of the TCI states 1002 may apply to the uplink channel (uplink physical channel) 1070. “TCI states 1002 that are indicated” apply to the uplink channel 1070. "This refers to one or more UL TCI states and one or both of one or more Joint TCI states. It may be the other way around. The “instructed TCI state” 1002 applied to the uplink channel 1070 is The “applicable TCI state” 1020 may also be the “applicable TCI state” for the uplink channel 1070.

[0472] One or more of the TCI states 1002 may apply to the uplink channel (uplink physical channel) 1071. The “indicated TCI states 1002” that apply to the uplink channel 1071. "This refers to one or more UL TCI states and one or both of one or more Joint TCI states. It may be the other way around. The “indicated TCI state” 1002 applied to the uplink channel 1071 is , or “Applicable TCI state” 1021. TCI state 1021 may be “Applicable TCI state” for uplink channel 1071.

[0473] The indicated TCI state 1002 may include at least TCI state 1010 and TCI state 1011. One or both of TCI state 1010 and TCI state 1011 may be applied to the uplink channel 1070. i. Either or both of TCI state 1010 and TCI state 1011 may be applied to the uplink channel 1071. Either or both of TCI state 1010 and TCI state 1011 applied to the uplink channel 1070 may be TCI state 1020. Either or both of TCI state 1010 and TCI state 1011 applied to the uplink channel 1071 may be TCI state 1021.

[0474] If DCI1042, which schedules transmission on uplink channel 1070, is associated with CORESET pool index 1080, or if PDCCH1032, to which DCI1042, which schedules transmission on uplink channel 1070, is mapped, is associated with CORESET pool index 1080. The TCI state 1010 may be applied to the uplink channel 1070. For example, the TCI state 1010 may be applied to the uplink channel 1070 as the “Applied TCI state” 1020. If DCI 1043, which schedules transmission on link channel 1071, is associated with CORESET pool index 1081, or if PDCCH 1033, to which DCI 1043, which schedules transmission on uplink channel 1071, is mapped, is associated with CORESET pool index 1081, then TCI state 1011 may be applied to uplink channel 1071. For example, TCI state 1011 is “Apply”. The TCI state "1021" may be applied to the uplink channel 1071. If DCI1042, which schedules transmission on channel 1070, is associated with CORESET pool index 1081, or if DCI1042, which schedules transmission on uplink channel 1070 If the PDCCH1032 to which is mapped is associated with CORESET pool index 1081, then TCI state 1011 may be applied to the uplink channel 1070. For example, TCI state 1011 may be applied to the uplink channel 1070 as “Applied TCI state” 1020. If DCI1043, which schedules the transmission of channel 1071, is associated with CORESET pool index 1080, or if DCI1043, which schedules the transmission of uplink channel 1071, is associated with M If the PDCCH1033 being selected is associated with CORESET pool index 1080, then TCI state 1010 is higher It may also be applied to the uplink channel 1071. For example, TCI state 1010 may be applied to the uplink channel 1071 as “Applicable TCI state” 1021.

[0475] Figure 15 shows an example of timeline management of TCI status according to one aspect of this embodiment. Terminal device 1 may receive PDCCH1030. Terminal device 1 may receive PDCCH1030 in which DCI1040 is placed. PDCCH1030 may be received in the first CORESET. The first CORESET may correspond to the CORESET pool index 1080. That is, PDCCH1030 and DCI1040 may be associated with the CORESET pool index 1080. DCI1040 in PDCCH1030 may include one or both of the first TCI field and the TRP indicator field. The first TCI field, or the activation command for the first TCI field, is in the CORESET pool It may also support the 1080-index. DCI1040 is PDSCH1050, or PDSCH1050 Reception may be scheduled. DCI1040 may instruct PDSCH1050 to receive. DCI1040 may instruct PDSCH1050 to transmit.

[0476] Terminal device 1 may receive PDSCH1050. For example, terminal device 1 may receive PDSCH1050 scheduled by DCI1040. The transport block transmitted by PDSCH1050 may include a first activation command. The first activation command is CORESET It may also support a pool index of 1080.

[0477] Terminal device 1 may transmit PUCCH1060. For example, terminal device 1 may transmit PUCCH1060 scheduled by DCI1040. PUCCH1060 may transmit HARQ-ACK. The UCI in PUCCH1060 may include HARQ-ACK information. PUCCH1060 may correspond to CORESET pool index 1080. From the last OFDM symbol of PUCCH1060, N symb TCI state 1010 may be applied later. TCI state 1010 may be one of the indicated TCI states 1002.

[0478] Terminal device 1 may receive PDCCH1031. Terminal device 1 may receive PDCCH1031 in which DCI1041 is located. PDCCH1031 may be received in a second CORESET. The second CORESET may correspond to the CORESET pool index 1081. That is, PDCCH1031 and DCI1041 may be associated with the CORESET pool index 1081. DCI1041 in PDCCH1031 may include one or both of the second TCI field and the TRP indicator field. The activation command for the second TCI field is CORESET It may also correspond to pool index 1081. DCI1041 is PDSCH1051, or PDSCH1051 Reception may be scheduled. DCI1041 may instruct PDSCH1051 to receive. DCI1041 may instruct PDSCH1051 to transmit.

[0479] Terminal device 1 may receive PDSCH1051. For example, terminal device 1 may receive PDSCH1051 scheduled by DCI1041. The transport block transmitted by PDSCH1051 may include a second activation command. The second activation command is CORESET It may also support pool index 1081.

[0480] Terminal device 1 may transmit PUCCH1061. For example, terminal device 1 may transmit PUCCH1061 scheduled by DCI1041. PUCCH1061 may transmit HARQ-ACK. The UCI in PUCCH1061 may include HARQ-ACK information. PUCCH1061 may correspond to CORESET pool index 1081. From the last OFDM symbol of PUCCH1061, N symbTCI state 1011 may be applied later. TCI state 1011 may be one of the indicated TCI states 1002.

[0481] Figure 16 shows an example of uplink channel transmission according to one aspect of this embodiment. Terminal device 1 may receive PDCCH1032. For example, terminal device 1 may receive PDCCH1032 on which DCI1042 is located. PDCCH1032 and DCI1042 may be associated with CORESET pool index 1080. For example, PDCCH1032 may be received in a CORESET on which CORESET pool index 1080 is set.

[0482] Terminal device 1 may transmit uplink channel 1070. The uplink channel may be PUSCH, PUCCH, or SRS. In some cases, the applicable TCI state 1020 may be determined based on the CORESET pool index corresponding to DCI 1042 (i.e., CORESET pool index 1080). For example, if PDCCH 1032 is received in a CORESET where CORESET pool index 1080 is set, The TCI state 1020 applied to the uplink channel 1070 may also be TCI state 1010. Although different from Figure 16, if PDCCH 1032 is received in a CORESET where CORESET pool index 1081 is set, the TCI state 1020 applied to the uplink channel 1070 will be TCI state 1011. That's fine.

[0483] If the uplink channel 1070 is a PUCCH, the applicable TCI state 1020 may be determined based on the higher-level parameters included in the PUCCH resource (e.g., CORESET pool index). For example, for the PUCCH resource indicated by DCI 1042, the CORESET pool index If S1080 is set, the TCI state 1020 applied to the uplink channel 1070 may be TCI state 1010. Although different from Figure 16, if CORESET pool index 1081 is set for the PUCCH resource indicated by DCI 1042, then it is applied to the uplink channel 1070. TCI state 1020 may also be TCI state 1011.

[0484] If the uplink channel 1070 is an SRS, then the upper layer parameters included in the SRS resource ( For example, based on a CORESET pool index, or an SRS resource set, The applicable TCI state 1020 may be determined. For example, if PDCCH 1032 is received in a CORESET where the CORESET pool index 1080 is set, the TCI state 1020 applied to the uplink channel 1070 may be TCI state 1010. For example, if the CORESET pool index 1080 is set for an SRS resource indicated by DCI 1042, the applicable TCI state 1020 for the uplink channel 1070 may be TCI state 1010. The TCI state 1020 used may also be TCI state 1010. Although it differs from Figure 16, let's assume CORESET In a CORESET where pool index 1081 is set, if PDCCH 1032 is received, the TCI state 1020 applied to the uplink channel 1070 may be TCI state 1011. Although different from Figure 16, if CORESET pool index 1081 is used for the SRS resource indicated by DCI 1042 If this is set, the TCI state 1020 applied to the uplink channel 1070 may also be TCI state 1011.

[0485] Terminal device 1 may receive PDCCH1033. For example, terminal device 1 may receive PDCCH1033 in which DCI1043 is located. PDCCH1033 and DCI1043 may be associated with CORESET pool index 1081. For example, PDCCH1033 may be received in a CORESET in which CORESET pool index 1081 is set.

[0486] Terminal device 1 may transmit uplink channel 1071. The uplink channel may be PUSCH, PUCCH, or SRS. In some cases, the applicable TCI state 1021 may be determined based on the CORESET pool index corresponding to DCI 1043 (i.e., CORESET pool index 1081). For example, if PDCCH 1033 is received in a CORESET where CORESET pool index 1081 is set, The TCI state 1021 applied to the uplink channel 1071 may also be TCI state 1011. Although different from Figure 16, if PDCCH 1033 is received in a CORESET where the CORESET pool index 1080 is set, the TCI state 1021 applied to the uplink channel 1071 may be TCI state 1010. That's fine.

[0487] If the uplink channel 1071 is PUCCH, the applicable TCI state 1021 may be determined based on the higher-level parameters (e.g., CORESET pool index) included in the PUCCH resource. For example, DCI 1043 indicates the CORESET pool index for the PUCCH resource. If S1081 is set, the TCI state 1021 applied to the uplink channel 1071 may also be TCI state 1011. Although different from Figure 16, if CORESET pool index 1080 is set for the PUCCH resource indicated by DCI 1043, then it is applied to the uplink channel 1071. TCI state 1021 may also be TCI state 1010.

[0488] If the uplink channel 1071 is an SRS, then the upper layer parameters included in the SRS resource ( For example, based on a CORESET pool index, or an SRS resource set, The TCI state 1021 that is applied may be determined. For example, if PDCCH 1033 is received in a CORESET where CORESET pool index 1081 is set, the TCI state 1021 applied to the uplink channel 1071 may be TCI state 1011. For example, the SRS resource indicated by DCI 1043 If CORESET pool index 1081 is set for this purpose, then the uplink channel 1071 is suitable. The TCI state 1021 used may also be TCI state 1011. Although it differs from Figure 16, let's assume CORESET In a CORESET where pool index 1080 is set, if PDCCH 1033 is received, the TCI state 1021 applied to the uplink channel 1071 may be TCI state 1010. Although different from Figure 16, if CORESET pool index 1080 is for the SRS resource indicated by DCI 1043 If this is set, the TCI state 1021 applied to the uplink channel 1071 may be TCI state 1010.

[0489] Terminal device 1 has either uplink channel 1070 or uplink channel 1071. The uplink timing 1090 (TA 1090) may be adjusted for both. For example, in response to receiving a TA command 1200 for TAG 1100, terminal device 1 may adjust the uplink timing 1090. The TA command 1200 may be received by a random access response or MAC CE. TAG 1100 may correspond to TAG ID 1300, that is, TAG ID 1300 may be an identifier for TAG 1100. TAG ID 1300 may be a subTAG ID. Terminal device 1 controls either or both of the uplink channels 1070 and 1071. For this reason, the uplink timing 1091 (TA 1091) may be adjusted. For example, TAG 1101 In response to receiving the TA command 1201, terminal device 1 adjusts the uplink timing 1091. It is also possible that the TA command 1201 is received by a random access response or by MAC CE. TAG 1101 may correspond to TAG ID 1301, that is, TAG ID 1301 may be an identifier for TAG 1101. TAG ID 1301 may be a subTAG ID. For example, TAG 1100 and TAG 1101 may be provided in one serving cell. For example, TAG ID 1300 and TAG ID 1301 may be set in one serving cell. For example, uplink timing 1090 and uplink timing 1091 may be used in one serving cell. You can stay.

[0490] One of the uplink timings 1090 and 1091 may be applied to the uplink channel 1070. Also, one of TAG 1100 and 1101 may correspond to the uplink channel 1070. One of the uplink timings 1090 and 1091 may be applied to the uplink channel 1071. Also, one of TAG 1100 and 1101 may correspond to the uplink channel 1071.

[0491] Means 1, 2, and 3 may be used to determine the uplink timing, TAG, or TAG ID applied to the uplink channel. Also, if terminal device 1 has a terminal capacity of 1400 These methods may be used differently depending on whether or not they have. Also, for terminal device 1 These methods may be used depending on whether the upper layer parameter 1500 or upper layer parameter 1600 is set.

[0492] In means 1, means 2, and means 3, which of TAG 1100 and TAG 1101 is the ascending ring Whether it applies to channel 1070 may be determined based at least on the TCI fields in one or both of DCI 1040 and DCI 1041.

[0493] In method 1, either TAG ID 1300 or TAG ID 1301 may be set for each of the one or more “Set TCI states” 1000. One of them may be set for a single TCI state. For example, in the upper-level parameter UL-TCIState or DLorJoint-TCIState, one of TAG ID 1100 and TAG ID 1101 may be set. It may be set. However, neither TAG ID 1100 nor TAG ID 1101 is required to be set in the higher-level parameter TCI-State.

[0494] In method 1, for the TCI state 1020 applied to the uplink channel 1070, TAG ID 1300 , and either TAG ID 1301 may be set. TAG ID 1300 for TCI state 1020 If set, the uplink timing 1090 and TAG 1100 may be applied to the uplink channel 1070. If TAG ID 1301 is set for TCI state 1020, the uplink timing 1091 and TAG 1101 may be applied to the uplink channel 1070.

[0495] In method 1, if terminal device 1 has a terminal capacity of 1400, or if terminal device 1 has a terminal capacity of 1400 When reporting, method 1 may be used. If terminal device 1 does not have terminal capability 1400, or does not report, it is expected that a TAG ID will be set for the TCI status. It is not necessary. Also, if terminal device 1 does not have terminal capacity 1400, or if it does not report If not applicable, the TAG ID set for the TCI status may be ignored.

[0496] In method 1, if the upper layer parameter 1500 is set, or if the upper layer parameter 1600 If it is not set, means 1 may be used. In addition, it is not necessary to expect that a TAG ID will be set for the TCI state. If Lameter 1600 is set, the TAG ID set for the TCI status may be ignored. .

[0497] In method 2, either TAG ID 1300 or TAG ID 1301 may be set for a single activation command. For example, TAG ID 1300 and TAG ID 1301 may be set for a single activation command. It may be determined by one CORESET pool index included in the hand. There may be a one-to-one correspondence between the TAG ID and the CORESET pool index. For example, CORESET pool index 1080 may correspond to uplink timing 1090, TAG 1100, and TAG ID 1300. CORESET pool index 1081 is linked to the uplink timing 1091, TAG 1101, and It may also support TAG ID 1301.

[0498] In method 2, if PDCCH 1032 is associated with CORESET pool index 1080, then some or all of the uplink timing 1090, TAG 1100, and TAG ID 1300 are associated with the uplink channel. This may also apply to 1070. In means 2, if PDCCH 1033 is associated with CORESET pool index 1081, then the uplink timing 1091, TAG 1101, and part of TAG ID 1301 The entire set may be applied to the uplink channel 1071.

[0499] In method 2, if terminal device 1 does not have terminal capability 1400, or if terminal device 1 does not report terminal capability 1400, method 2 may be used. In cases where, or when reporting, one CORESET pool index is related to two TAG IDs They may be linked. For example, a TCI state corresponding to CORESET pool index 1080 (e.g., one or more activated TCI states 1001) may be associated with two TAG IDs, two TAGs, and some or all of two uplink timings.

[0500] In method 2, method 2 may be used if the upper layer parameter 1500 is not set, or if the upper layer parameter 1600 is set. If the upper layer parameter 1500 is set, or if the upper layer parameter 1600 is not set, one CORESET pool index may be associated with two TAG IDs. For example, a TCI state (e.g., one or more activated TCI states 1001) corresponding to CORESET pool index 1080 may be associated with two TAG IDs, two TAGs, and some or all of two uplink timings.

[0501] In method 3, TAG ID 1300 corresponds to SSB group 1, and TAG ID 1301 corresponds to SSB group 2. For example, if TCI state 1020 corresponds to SSB group 1, the uplink channel 1070 to which TCI state 1020 applies may correspond to some or all of the uplink timing 1090, TAG 1100, and TAG ID 1300. For example, if TCI state 1021 corresponds to SSB group 2, the uplink channel 1071 to which TCI state 1021 applies may correspond to some or all of the uplink timing 1091 This may correspond to TAG 1101 and some or all of TAG ID 1301. The TCI state is one S Corresponding to an SB group may mean that the reference signal related to the QCL relationship provided by the TCI state is associated with one SSB group. For the TCI state, a higher-level parameter qcl-info may be set to one SSB group (or an ID that identifies one SSB group). The SSB group may be set by a higher-level parameter. For example, an SSB group may be set by a dedicated higher-level parameter for one serving. Therefore, based on the higher-level parameter, it may be determined that both TAG ID 1300 and TAG ID 1301 correspond to one SSB group, and that either TAG ID 1300 or TAG ID 1301 corresponds to one SSB group. For example, one SSB group may contain 32 SS / PBCH blocks.

[0502] In means 3, if terminal device 1 does not have terminal capability 1400 or does not report, TCI state 1010 may correspond to SSB group 1 and TCI state 1011 may correspond to SSB group 2. If terminal device 1 has terminal capability 1400 or reports, both TCI state 1010 and TCI state 1011 may correspond to SSB group 1 or SSB group 2.

[0503] In method 3, if the upper layer parameter 1500 is not set, or if the upper layer parameter 1600 is set, TCI state 1010 corresponds to SSB group 1, and TCI state 1011 corresponds to SSB group 2. This may also be supported. If upper layer parameter 1500 is set, or if the upper layer parameter is not set, both TCI state 1010 and TCI state 1011 are SSB group 1, or SSB group It may also be possible to support Loop 2.

[0504] Terminal capability 1400 refers to the ability to perform Dynamic Point Selection. The terminal capability 1400 may also be the capability to perform TRP switching in a CORESET corresponding to one CORESET pool index. The terminal capability 1400 may be the capability to perform TRP switching in a CORESET It may also be the ability to perform switching. Terminal capability 1400 may also be the ability to associate one beam information with one uplink timing, independently of CORESET or the CORESET pool index.

[0505] The upper layer parameter 1500 may be set when terminal capability 1400 is reported. The upper layer parameter 1500 may determine whether to apply dynamic point selection. The upper layer parameter 1600 may be a parameter that determines whether the PUSCH-MTRP method is applied. For example, the upper layer parameter 1500 determines whether the STxMP method is applied. It is also possible to apply cyclic mapping to PUSCH using upper-layer parameter 1500. It is also possible to apply sequential mapping to PUSCH using upper-layer parameter 1500. It is not necessary to expect that upper-layer parameters 1500 and 1600 will be set.

[0506] Terminal device 1 may receive the first PDCCH. The first DCI (DCI format) may be placed (mapped) to the first PDCCH. Terminal device 2 may receive the second PDCCH. The DCI (DCI format) may be placed (mapped) to the second PDCCH. Terminal device 1 may receive the PDSCH. The first DCI may schedule the reception of the PDSCH or the PDSCH. The first DCI may instruct the reception of the PDSCH. Terminal device 1 receives the uplink channel. You may transmit the Nell (uplink physical channel). The second DCI is the uplink channel. Alternatively, transmission on the uplink channel may be scheduled. The second DCI is uplink The terminal device 1 may instruct the transmission of the link channel. The terminal device 1 may receive the first PDCCH, the second PDCCH, and the PDSCH in that order.

[0507] The uplink channel may be one of PUSCH, PUCCH, or SRS.

[0508] The first CORESET pool index may be the first value. The second CORESET pool index may be the first value. That is, the first CORESET pool index The first and second CORESET pool indexes may be the same. The first CORESET pool index may relate to the first PDCCH, the first DCI, and some or all of the TCI fields in the first DCI. The second CORESET pool index may relate to one or both of the second PDCCH and the second DCI.

[0509] The first beam information may be indicated by the first DCI. For example, the first beam information The information may be indicated by the TCI field in the first DCI. The first beam information may be a TCI state. For example, the first beam information may be an indicated TCI state. The first beam information may be applied to the uplink channel. The first beam information may be used to determine the uplink transmit space filter of the uplink channel.

[0510] The first uplink timing (first TA) may be used for the uplink channel. For example, the first uplink timing may be adjusted for the uplink channel. The first uplink timing may correspond to the first TAG. The first TAG may correspond to the first TAG ID. The first TAG ID may be determined based on the TCI field. That's fine. For example, the first TAG ID may be determined or indicated based on the TCI field in the first DCI.

[0511] The second uplink timing (second TA) may correspond to the second TAG. The second TAG may correspond to the second TAG ID. The second TAG ID does not have to be indicated based on the TCI field in the first DCI. The first uplink timing and the second uplink timing may be provided in a single serving cell. Terminal device 1 provides a single serving cell In Guser, you may hold both the first TAG and the second TAG.

[0512] The code point in the TCI field relates to either or both of the first and second TAG IDs. They may be linked. For example, multiple second beam information at the code point of the TCI field The information may be related to one or both of the first and second TAG IDs. The second beam information may be a TCI state. For example, the second beam information may be an activated TCI state. That is, the first beam information may be determined from multiple second beam information values.

[0513] When terminal capabilities are reported, as means 1 or means 3, each of the TCI fields The code point may be associated with either the first TAG ID or the second TAG ID. If terminal capability is not reported, as a means 2, each code point in the TCI field may be associated with the first TAG ID. If terminal capability is not reported, it means that terminal device 1 does not have terminal capability. This may also be the case. The terminal capability may be 1400. The terminal capability may be the capability in which both the first uplink timing and the second uplink timing are used in one or more CORESETs corresponding to one CORESET pool index.

[0514] If the first upper-level parameter is set, or if the second upper-level parameter is not set, then, as means 1 or means 3, each code point in the TCI field is first It may be associated with either the first TAG ID or the second TAG ID. If the first upper-level parameter is not set, or if the second upper-level parameter is set, as means 2, each code point in the TCI field may be associated with the first TAG ID. The first upper-level parameter may be upper-level parameter 1500. The second upper-level parameter may be upper-level parameter 1600.

[0515] The first TAG ID may be determined based on the first CORESET pool index to which the TCI field is related. For example, if terminal capability is not reported, the first TAG ID is based on the TCI field. The field may be determined based on the first CORESET pool index to which it relates. For example, the first CORESET pool index may correspond to the first TAG ID. The second CORESET pool index may correspond to the second TAG ID.

[0516] The following describes various aspects of the apparatus according to one embodiment of this invention.

[0517] The programs that run on the base station device 3 and terminal device 1 according to the present invention may be programs that control the CPU (Central Processing Unit) and the like (programs that make the computer function) in order to realize the functions of the above embodiment according to the present invention. The information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing. The data is then stored in various types of ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and read, modified, and written by the CPU as needed.

[0518] Furthermore, the terminal device 1 and a part of the base station device 3 in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read by a computer system and executed.

[0519] Furthermore, the term "computer system" as used herein refers to the computer system built into terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. In addition, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into computer systems.

[0520] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory inside a computer system that acts as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0521] Furthermore, the base station device 3 in the above-described embodiment can also be realized as an assembly (device group) composed of multiple devices. Each device constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. The device group only needs to have a complete set of the functions or functional blocks of the base station device 3. In addition, the terminal device 1 related to the above-described embodiment can also communicate with the base station device as an assembly.

[0522] Furthermore, the base station device 3 in the above-described embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGen RAN, NR RAN). Also, the base station device 3 in the above-described embodiment may be eNodeB and / or gNB. It may possess some or all of the functions of the corresponding higher-level node.

[0523] Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiment may be implemented as LSIs, which are typically integrated circuits, or as chipsets. Each functional block of terminal device 1 and base station device 3 may be individually chipped, or some or all of them may be integrated into a single chip. Furthermore, the integrated circuit method is not limited to LSIs; dedicated circuits may also be used. Alternatively, it can be implemented with a general-purpose processor. Furthermore, advances in semiconductor technology may replace LSIs. If the technology for integrated circuit integration emerges, it will also be possible to use integrated circuits that utilize that technology.

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

[0525] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this 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 this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0526] 1 (1A, 1B, 1C) Terminal device 3 Base station equipment 10, 30 Wireless Transceiver Unit 10a, 30a Wireless 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 Wireless Resource Control Layer Processing Unit 91, 92, 93, 94 Search area set 300 Component Carrier 301 Primary Cell 302, 303 Secondary Cells Set of resource elements for 700 PSS Set of resource elements for 710, 711, 712, 713 PBCH and DMRS for PBCH Set of resource elements for 720 SSS 3000 points 3001, 3002 Resource Grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common Resource Block Sets 1000 TCI status to be set 1001 Activated TCI state 1002, 1010, 1011 Indicated TCI status 1020, 1021 Applicable TCI status 1030, 1031, 1032, 1033 PDCCH 1040, 1041, 1042, 1043 DCI 1050, 1051 PDSCH 1060, 1061 PUCCH 1070, 1071 Uplink Channel 1080, 1081 CORESET pool index 1090, 1091 Uplink Timing 1100, 1101 TAG 1200, 1201 TA command 1300, 1301 TAG ID 1400 terminal capacity 1500, 1600 Upper layer parameters

Claims

1. A receiving unit that receives a first PDCCH on which a first DCI is located, a second PDCCH on which a second DCI is located, and a PDSCH scheduled by the first DCI. Transmitter that transmits the uplink channel scheduled by the second DCI And, equipped with, The first beam information is indicated by the TCI field in the first DCI, The aforementioned first beam information is applied for the uplink channel, The first PDCCH and the second PDCCH are related to the first CORESET pool index, The first uplink timing for the uplink channel is determined by the first TAG ID. The first TAG ID is determined based on the TCI field. The code point of the TCI field is one of the first TAG ID and the second TAG ID. This corresponds to both. Terminal device.

2. If terminal capabilities are not reported, the code point corresponds to the first TAG ID. The terminal device according to claim 1.

3. When STxMP is applied for the aforementioned uplink channel, the code point is, The first TAG ID corresponds to The terminal device according to claim 1.

4. The terminal capability is such that in one or more CORESETs corresponding to the first CORESET pool index, both the first uplink timing and the second uplink timing are It is an ability that is used, Both the first upward link timing and the second upward link timing are one Provided in the serving cell The terminal device according to claim 2.

5. A transmitting unit that transmits a first PDCCH on which a first DCI is located, a second PDCCH on which a second DCI is located, and a PDSCH scheduled by the first DCI. The receiving unit receives the uplink channel scheduled by the second DCI. And, equipped with, The first beam information is indicated by the TCI field in the first DCI, The aforementioned first beam information is applied for the uplink channel, The first PDCCH and the second PDCCH are related to the first CORESET pool index, The first uplink timing for the uplink channel is determined by the first TAG ID. The first TAG ID is determined based on the TCI field. The code point of the TCI field is one of the first TAG ID and the second TAG ID. This corresponds to both. Base station equipment.

6. If terminal capabilities are not reported, the code point corresponds to the first TAG ID. The base station device according to claim 5.

7. When STxMP is applied for the aforementioned uplink channel, the code point is, The first TAG ID corresponds to The terminal device according to claim 5.

8. The terminal capability is such that in one or more CORESETs corresponding to the first CORESET pool index, both the first uplink timing and the second uplink timing are It is an ability that is used, Both the first upward link timing and the second upward link timing are one Provided in the serving cell The base station device according to claim 6.

Images