User equipment, base station, and method

Abstract

To provide a system and a method, capable of improving communication flexibility and efficiency in a next generation standard system.SOLUTION: A terminal device 1 comprises: a higher-layer processing unit 14 for acquiring a first RRC (radio resource control) parameter for indicating a transmission configuration and a second RRC parameter for indicating whether or not a transform precoding indicator field is included in a DCI (downlink control information) format; and a wireless transmission / reception unit 10 for receiving scheduling information on a PUSCH (physical uplink shared channel) and transmitting the PUSCH. When the first RRC parameter indicates a codebook and the second RRC parameter indicates that a transform precoding indicator field is included in a DCI, a DCI format including a first field with a maximum number of bits among one or more tables applied based on values of a third RRC parameter to a sixth RRC parameter and a transform precoder is monitored.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to user equipment, base stations, and methods. [Background technology]

[0002] The Third Generation Partnership Project (3GPP) is researching wireless access methods and wireless networks for cellular mobile communications (hereinafter referred to as Long Term Evolution or Evolutionary Universal Terrestrial Radio Access). In LTE (Long Term Evolution), base station equipment is also called Evolutionary NodeB (eNodeB), and terminal equipment is also called User Equipment (UE). LTE is a cellular communication system in which multiple areas are deployed in a cellular structure, and each of the multiple areas is covered by base station equipment. A single base station can manage multiple cells. Evolutionary Universal Terrestrial Radio Access is also called E-UTRA.

[0003] At 3GPP, the next-generation standard (NewRadio: NR) is being researched for proposal to International-Mobile-Telecommunication 2020 (IMT2020), the standard for next-generation mobile communication systems defined by the International Telecommunication Union (ITU). NR is envisioned to meet the requirements of considering three scenarios within a single technology framework: eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication).

[0004] For example, a wireless communication device can communicate with one or more devices using a communication structure. However, the flexibility and / or efficiency of the communication structure used may be limited. As will be discussed in this argument, systems and methods for improving the flexibility and / or efficiency of communication may be considered beneficial. [Brief explanation of the drawing]

[0005] [Figure 1] This is a conceptual diagram of a wireless communication system according to one aspect of this embodiment.

[0006] [Figure 2] This is an example showing the relationship between the subcarrier spacing configuration u, the number of OFDM symbols per slot Nslot symb, and the CP configuration according to one aspect of this embodiment.

[0007] [Figure 3] This figure shows an example of a method for configuring a resource grid according to one aspect of this embodiment.

[0008] [Figure 4] This figure shows an example configuration of a resource grid 3001 according to one aspect of this embodiment.

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

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

[0011] [Figure 7] This figure shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment.

[0012] [Figure 8]This figure shows an example of a monitoring opportunity for a search space set according to one aspect of this embodiment.

[0013] [Figure 9] This is an exemplary configuration of a frame structure according to one aspect of this embodiment.

[0014] [Figure 10] This is an exemplary configuration of a slot configuration according to one aspect of this embodiment.

[0015] [Figure 11] This is an exemplary configuration of the baseband section 13 in the wireless transmission section 10a according to one aspect of this embodiment.

[0016] [Figure 12] This is an exemplary configuration of an encoding device 12000 according to one aspect of this embodiment.

[0017] [Figure 13] This is an example of a bit selection procedure according to one aspect of this embodiment.

[0018] [Figure 14] This is an example of a circular buffer according to one aspect of this embodiment.

[0019] [Figure 15] This is an exemplary configuration of a processing timeline according to one aspect of this embodiment.

[0020] [Figure 16] This is an exemplary configuration of a processing timeline according to one aspect of this embodiment.

[0021] [Figure 17] This is an exemplary configuration of a third type of PUSCH transmission in multiple slots according to one aspect of this embodiment.

[0022] [Figure 18]This is an exemplary configuration of multiple instances of a third type of PUSCH transmission in multiple slots according to one aspect of this embodiment.

[0023] [Figure 19] This is an example of the UE method.

[0024] [Figure 20] This is an example of a base station method.

[0025] [Figure 21] This is an example of applicable PUSCH time domain resource allocation for the common search space and DCI format 0_0 within the UE-specific search space.

[0026] [Figure 22] This is an example of an applicable PUSCH time-domain resource allocation for DCI format 0_1 ​​in a UE-specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0027] [Figure 23] This is an example of an applicable PUSCH time-domain resource allocation for DCI format 0_2 in a UE-specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0028] [Figure 24] This is an example of the default PUSCH time domain resource allocation A for a typical CP.

[0029] [Figure 25] This is an example of a redundant version of a PUSCH transmission.

[0030] [Figure 26]This is an example of a table used for precoding information and the number of layer fields in DCI format 0_1 / 0_2.

[0031] [Figure 27] This is an example of a table used for precoding information and the number of layer fields in DCI format 0_1 / 0_2.

[0032] [Figure 28] This is an example of a table used for precoding information and the number of layer fields in DCI format 0_1 / 0_2.

[0033] [Figure 29] This is an example of a table used for the second precoding information field in DCI format 0_1 / 0_2.

[0034] [Figure 30] This is an example of a table used for the second precoding information field in DCI format 0_1 / 0_2.

[0035] [Figure 31] This is an example of a table used for the antenna port field in DCI format 0_1 / 0_2.

[0036] [Figure 32] This is an example of a table used for the antenna port field in DCI format 0_1 / 0_2. [Modes for carrying out the invention]

[0037] The User Equipment (UE) is described below. The UE may comprise: a higher-layer processing circuit configured to acquire at least a first RRC parameter indicating texConfig and a second RRC parameter indicating whether a conversion precoding indicator field is included in the DCI format; a receiving circuit configured to receive the DCI format for scheduling PUSCHs; and a transmitting circuit configured to transmit PUSCHs scheduled by the DCI format. If the first RRC parameter indicates invalidation and the second RRC parameter indicates that a conversion precoding indicator field is included in the DCI format, the receiving circuit is configured to monitor the DCI format including the values ​​of a third RRC parameter, a fourth RRC parameter, a fifth RRC parameter, a sixth RRC parameter, and a first DCI field having the maximum number of bits in one or more tables applied based on the conversion precoder.

[0038] A base station is described below. The base station may comprise: an upper-layer processing circuit configured to obtain at least a first RRC parameter indicating texConfig and a second RRC parameter indicating whether a conversion precoding indicator field is included in the DCI format; a transmitting circuit configured to transmit the DCI format for scheduling pushes; and a receiving circuit configured to receive pushes scheduled by the DCI format. If the first RRC parameter indicates invalidation and the second RRC parameter indicates that a conversion precoding indicator field is included in the DCI format, the transmitting circuit is configured to transmit the DCI format, which includes the values ​​of a third RRC parameter, a fourth RRC parameter, a fifth RRC parameter, a sixth RRC parameter, and a first DCI field having the maximum number of bits in one or more tables applied based on the conversion precoder.

[0039] A method for user equipment (UE) is described. This method may include: obtaining a first RRC parameter indicating at least texConfig and a second RRC parameter indicating whether a conversion precoding indicator field is included in the DCI format; receiving a DCI format for scheduling a PUSCH; sending a PUSCH scheduled by the DCI format; and monitoring a DCI format that includes the values ​​of a third, fourth, fifth, and sixth RRC parameter, and a first DCI field having the maximum number of bits in one or more tables applied based on a conversion precoder, if the first RRC parameter indicates a codebook and the second RRC parameter indicates that a conversion precoding indicator field is included in the DCI format.

[0040] "Configuring available slot-based counts (PUSCH repeat counts)" may also be referred to as "configuring a set of slot-based counts (PUSCH repeat counts) to be enabled," "enabling slot-based counts (PUSCH repeat counts)," or "enabling the RRC parameter AvailableSlotCounting."

[0041] The statement "Available slot-based count (PUSCH repeat count) is not configured" may also be expressed as "Disabled slot-based count (PUSCH repeat count) is configured," "Slot-based count (PUSCH repeat count) is disabled," "The RRC parameter indicating available slot-based count (PUSCH repeat count) is not configured," or "The RRC parameter AvailableSlotCounting is disabled."

[0042] floor(CX) can be the floor function of a real number CX. For example, floor(CX) can be a function that provides the largest integer within the range not exceeding the real number CX. ceil(DX) can be the ceiling function of a real number DX. For example, ceil(DX) can be a function that provides the smallest integer greater than or equal to the real number DX. mod(EX,FX) can be a function that provides the remainder obtained by dividing EX by FX. mod(EX,FX) can be a function that provides the value corresponding to the remainder obtained by dividing EX by FX. This is exp(GX)=e^GX, where e is Napier's number. (HX)^(IX) represents IX raised to the power of HX.

[0043] In a wireless communication system according to one aspect of this embodiment, at least OFDM (Orthogonal Frequency Division Multiplexing) is used. An OFDM symbol is a time-domain unit of OFDM. An OFDM symbol includes at least one subcarrier. An OFDM symbol is converted into a time-continuous signal in baseband signal generation. For downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) is used. For uplink, CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing) is used. DFT-s-OFDM can be given by applying a transformation precoding to CP-OFDM. CP-OFDM is OFDM using CP (CyclicPrefix).

[0044] Either DFT-s-OFDM or CP-OFDM may be given based on whether the transformation precoder (or transformation precoding) is enabled. If the transformation precoder (or transformation precoding) is enabled, DFT-s-OFDM may be given. CP-OFDM may be given if the transformation precoder (or transformation precoding) is disabled. For example, either an enabled or disabled transformation precoder for PUSCH may be indicated based on the RRC parameter transformPrecoder in PUSCH-Config or ConfiguredGrantConfig and / or msg3-transformPrecoder in RACH-ConfigCommon.

[0045] The RRC parameter transformPrecoder indicates the UE-specific selection of the transform precoder for PUSCH. If transformPrecoder is not present / configured, the UE applies the value of msg3-transformPrecoder to the transform precoder for PUSCH.

[0046] `msg3-transformPrecoder` indicates that the UE should enable the transformation precoder for Msg3 transmission. If `msg3-transformPrecoder` is provided / configured, the UE will enable the transformation precoder for Msg3 transmission. If `msg3-transformPrecoder` is not present / configured / provided, the UE will disable the transformation precoder for Msg3 transmission.

[0047] An OFDM symbol may be a specification that includes a CP (Component of Programming) added to an OFDM symbol. That is, an OFDM symbol may be configured to include an OFDM symbol and a CP added to an OFDM symbol.

[0048] Figure 1 is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. In Figure 1, the wireless communication system includes at least terminal devices 1A to 1C and a base station device 3 (BS#3: base station #3). Hereinafter, terminal devices 1A to 1C are also called terminal devices 1 (UE#1: user equipment #1).

[0049] The base station device 3 may be configured to include one or more transmitting devices (or transmitting point, transmitting device, receiving device, transmitting point, receiving point). If the base station device 3 is composed of multiple transmitting devices, each of the multiple transmitting devices may be located in a different position.

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

[0051] A serving cell may be configured to include at least one downlink component carrier (downlink carrier) and / or one uplink component carrier (uplink carrier). A serving cell may be configured to include at least two or more downlink component carriers and / or two or more uplink component carriers. Downlink component carriers and uplink component carriers are also referred to as component carriers (carriers).

[0052] For example, one resource grid may be provided for one component carrier. For example, one resource grid may be provided for one component carrier and a subcarrier spacing configuration u. The subcarrier spacing configuration u is also called numerology. The resource grid is N size,u grid,x N RB sc Includes subcarriers. The resource grid is index N. start,u grid Starts with a common resource block containing index N.start,u grid A common resource block having is also referred to as a reference point of a resource grid. The resource grid includes N subframe,u symb OFDM symbols. The subscript x indicates the transmission direction and indicates either downlink or uplink. One resource grid is provided for antenna port p, subcarrier spacing configuration u, and transmission direction x.

[0053] The resource grid is also referred to as a carrier.

[0054] N size,u grid,x and N start,u grid are given based on at least RRC parameters (e.g., referred to as the RRC parameter CarrierBandwidth). The RRC parameter is used to define one or more SCS (subcarrier spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. One component carrier may include one or more SCS specific carriers. The SCS specific carrier may be included in the system information block (SIB). For each SCS specific carrier, a subcarrier spacing configuration u may be provided.

[0055] FIG. 2 is an example showing the relationship between the subcarrier spacing configuration u, the number N of OFDM symbols per slot slot symb and the CP configuration according to one aspect of the present embodiment. In FIG. 2A, for example, when the subcarrier spacing configuration u is set to 2 and the CP configuration is set to normal CP (normal cyclic prefix), N slot symb = 14, N frame,u slot = 40, N subframe,u slot = 4. Further, in FIG. 2B, for example, when the subcarrier spacing configuration u is set to 2 and the CP configuration is set to extended CP (extended cyclic prefix), N slot symb = 12, Nframe,u slot =40, N subframe,u slot = 4

[0056] In a wireless communication system according to one aspect of this embodiment, the time unit T c The length of time can be represented using the time unit T. c is, T c = 1 / (df max * N f ) is df max Since it is 480kHz, Nf = 4096. The constant k is k = df max * N f / (df ref N f, ref) = 64, and df ref It is 15kHz. f,ref The value is 2048.

[0057] The transmission of a signal on the downlink and / or on the uplink is of length T f It can be organized into wireless frames (system frames, frames). f =(df max N f / 100) * T s = 10ms. One wireless frame is configured to contain 10 subframes. The subframe length is T sf =(df max N f / 1000)T s = 1ms. The number of OFDM symbols per subframe is N subframe,u symb =N slot symb N subframe,u slot That is the case.

[0058] In the case of a subcarrier spacing configuration u, the number of slots and their indices within the subframe may be given. For example, slot index n u sThis refers to 0 to N within the subframe. subframe,u slot The values ​​can be given in ascending order as integers in the range of -1. For a subcarrier spacing configuration u, the number of slots included in the radio frame and the indices of the slots included in the radio frame can be given. Also, the slot index n u s,f This is 0 to N within the wireless frame. frame,u slot The integers can be given in ascending order within the range of -1. (N consecutive integers) slot symb OFDM symbols can be contained in one slot. slot symb = 14

[0059] Figure 3 shows an example of a method for configuring a resource grid 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 subcarrier spacing configuration u=u1 and an example of a resource grid configuration with subcarrier spacing configuration u=u2 for a component carrier 300. One or more subcarrier spacing configurations can be set for the component carrier. In Figure 3, it is assumed that u1=u2-1, but various aspects of this embodiment are not limited to the condition u1=u2-1.

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

[0061] Point 3000 is an identifier for identifying a subcarrier. Point 3000 is also referred to as Point A. The Common Resource Block (CRB) set 3100 is a set of common resource blocks for the subcarrier spacing configuration u1.

[0062] Within the common resource block set 3100, the common resource block containing point 3000 (the block indicated by the upper right diagonal line 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 with index 0 within the common resource block set 3100.

[0063] 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 configuration u1. The resource grid 3001 starts from the reference point of the resource grid 3001. size,u grid1,x This is a common resource block.

[0064] Offset 3013 is the reference point (N) from the reference point of resource grid 3001 to the reference point of BWP (bandwidth portion) 3003 of index i1. start,u BWP,i1 This is an offset to ).

[0065] The common resource block set 3200 is a set of common resource blocks relating to the subcarrier spacing configuration u2.

[0066] The common resource block containing point 3000 in the common resource block set 3200 (the block indicated by the upper left diagonal line 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 be the common resource block with index 0 within the common resource block set 3200.

[0067] 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 indicated by the number of common resource blocks for the subcarrier spacing configuration u = u2. The resource grid 3002 starts from the reference point of the resource grid 3002 and contains N size,u grid2,x common resource blocks.

[0068] Offset 3014 is the offset from the reference point of the resource grid 3002 to the reference point (N start,u BWP,i2 ) of the BWP 3004 having the index i2.

[0069] FIG. 4 is a diagram showing a configuration example of the resource grid 3001 according to an aspect of the present embodiment. In the resource grid of FIG. 4, the horizontal axis represents the OFDM symbol index l sym and the vertical axis represents the subcarrier index k sc . The resource grid 3001 contains N size,u grid1,x N RB sc subcarriers and also contains N subframes,u symb OFDM symbols. The resource specified by the subcarrier index k sc and the OFDM symbol index 1 within the resource grid sym is also referred to as a resource element (RE).

[0070] A resource block (RB) contains N RB sc consecutive subcarriers. A resource block is a general term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). It is N RB sc = 12.

[0071] A resource block unit is a set of resources corresponding to one OFDM symbol within one resource block. That is, one resource block unit includes 12 resource elements corresponding to one OFDM symbol within one resource block.

[0072] The common resource blocks of subcarrier spacing configuration u are indexed in ascending order from 0 in the frequency domain within the set of common resource blocks. The common resource block with index 0 of subcarrier spacing configuration u includes (or collides with, coincides with) point 3000. The index n of the common resource block for subcarrier spacing configuration u u CRB is n u CRB =ceil(k sc / N RB sc ) and satisfies the relationship. k sc The subcarrier with k = 0 has the same center frequency as the center frequency of the subcarrier corresponding to point 3000.

[0073] The physical resource blocks for subcarrier spacing configuration u are indexed in ascending order from 0 in the frequency domain within the BWP. The index n of the physical resource block for subcarrier spacing configuration u u PRB is n u CRB =n u PRB +N start,u BWP,i and satisfies the relationship. N start,u BWP,i indicates the reference point of the BWP with index i.

[0074] The BWP is defined as a subset of the common resource blocks included in the resource grid. The BWP starts from the reference point N start,u BWP,i and has N size,u BWP,iIncludes common resource blocks. The BWP of a downlink component carrier is also called a downlink BWP. The BWP of an uplink component carrier is also called an uplink BWP.

[0075] An antenna port is defined such that the channel through which a symbol on the antenna port is transmitted can be inferred from the channel through which another symbol on the same antenna port is transmitted. For example, a channel may correspond to a physical channel. For example, a symbol may correspond to an OFDM symbol. For example, a symbol may correspond to a resource block unit. For example, a symbol may correspond to a resource element.

[0076] Two antenna ports are said to be QCL (Quasi Co-Located) if the large-scale characteristics of the channel through which symbols are transmitted on one antenna port can be inferred from the channel through which symbols are transmitted on the other antenna port. The large-scale characteristics include one or more of the following: delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters.

[0077] Carrier aggregation can be a form of communication that uses multiple aggregated serving cells. Carrier aggregation can be a form of communication that uses multiple aggregated component carriers. Carrier aggregation can be a form of communication that uses multiple aggregated downlink component carriers. Carrier aggregation can be a form of communication that uses multiple aggregated uplink component carriers.

[0078] Figure 5 is a schematic block diagram showing an example 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 part or all of the wireless transceiver unit (physical layer processing unit) 30 and the upper layer processing unit 34. The wireless transceiver unit 30 includes at least part or all of the antenna unit 31, the RF unit 32 (radio frequency unit 32), and the baseband 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 unit (RRC) layer processing unit 36.

[0079] The wireless transmitting / receiving unit 30 includes at least part or all of the wireless transmitting unit 30a and the wireless receiving unit 30b. The configuration of the baseband unit 33 included in the wireless transmitting unit 30a and the configuration of the baseband unit 33 included in the wireless receiving unit 30b may be the same or different. The configuration of the RF unit 32 included in the wireless transmitting unit 30a and the configuration of the RF unit 32 included in the wireless receiving unit 30b may be the same or different. The configuration of the antenna unit 31 included in the wireless transmitting unit 30a and the configuration of the antenna unit 31 included in the wireless receiving unit 30b may be the same or different.

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

[0081] The media access control layer processing unit 35, included in the upper layer processing unit 34, performs MAC layer processing.

[0082] The wireless resource control layer processing unit 36, included in the upper layer processing unit 34, performs RRC layer processing. The wireless resource control layer processing unit 36 ​​manages various configuration information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 36 ​​configures the RRC parameters based on the RRC messages received from the terminal device 1.

[0083] The wireless transceiver 30 (or wireless transmitter 30a) performs processing such as encoding and modulation. The wireless transceiver 30 (or wireless transmitter 30a) generates a physical signal by encoding and modulating downlink data. The wireless transceiver 30 (or wireless transmitter 30a) converts the OFDM symbols of the physical signal into a baseband signal by converting them into a time-continuous signal. The wireless transceiver 30 (or wireless transmitter 30a) transmits the baseband signal (or physical signal) to the terminal device 1 via the radio frequency. The wireless transceiver 30 (or wireless transmitter 30a) can place the baseband signal (or physical signal) on a component carrier and transmit the baseband signal (or physical signal) to the terminal device 1.

[0084] The wireless transceiver 30 (or wireless receiver 30b) performs processing such as demodulation and decoding. The wireless transceiver 30 (or wireless receiver 30b) separates, demodulates, and decodes the received physical signal and provides the decoded information to the upper layer processing unit 34. The wireless transceiver 30 (or wireless receiver 30b) can perform a channel access procedure before transmitting the physical signal.

[0085] The RF unit 32 demodulates (downconverts) the physical signal received via the antenna unit 31 into a baseband signal and / or removes extraneous frequency components. The RF unit 32 provides the processed analog signal to the baseband unit 33.

[0086] The baseband unit 33 converts the analog signal (radio frequency signal) input from the RF unit 32 into a digital signal (baseband signal). The baseband unit 33 separates the portion corresponding to the cyclic prefix (CP) from the digital signal. The baseband unit 33 performs a Fast Fourier Transform (FFT) on the digital signal from which the CP has been removed. The baseband unit 33 provides a physical signal in the frequency domain.

[0087] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the downlink data to generate OFDM symbols, adds CP to the generated OFDM symbols to generate a digital signal (baseband signal), and converts the digital signal to an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.

[0088] The RF unit 32 removes extraneous frequency components from the analog signal (radio frequency signal) input from the baseband unit 33, upconverts the analog signal to a radio frequency, and transmits it via the antenna unit 31. The RF unit 32 may have a function to control the transmission power. The RF unit 32 is also referred to as the transmission power control unit.

[0089] For terminal device 1, at least one serving cell (or one or more component carriers, one or more downlink component carriers, and one or more uplink component carriers) can be configured.

[0090] Each serving cell configured for terminal device 1 may be a PCell (primary cell), a PSCell (primary SCG cell), or a SCell (secondary cell).

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

[0092] PSCell is a serving cell included in the SCG (Secondary Cell Group). PSCell is a serving cell in which random access is performed by terminal device 1 in a synchronous reconfiguration procedure (synchronous reconfiguration).

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

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

[0095] One or more downlink BWPs can be configured for each serving cell (or each downlink component carrier). One or more uplink BWPs can be configured for each serving cell (or each uplink component carrier).

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

[0097] PDSCH, PDCCH, and CSI-RS can be received on the active downlink BWP. Terminal device 1 can receive PDSCH, PDCCH, and CSI-RS on the active downlink BWP. PUCCH and PUSCH can be transmitted on the active uplink BWP. Terminal device 1 can transmit PUCCH and PUSCH on the active uplink BWP. The active downlink BWP and active uplink BWP are also referred to as active BWPs.

[0098] PDSCH, PDCCH, and CSI-RS do not need to be received on downlink BWPs other than active downlink BWPs (inactive downlink BWPs). Terminal device 1 may not receive PDSCH, PDCCH, and CSI-RS on downlink BWPs other than active downlink BWPs. PUCCH and PUSCH do not need to be transmitted on uplink BWPs other than active uplink BWPs (inactive uplink BWPs). Terminal device 1 may not transmit PUCCH and PUSCH on uplink BWPs other than active uplink BWPs. Inactive downlink BWPs and inactive uplink BWPs are also referred to as inactive BWPs.

[0099] Downlink BWP switching involves deactivating the active downlink BWP and activating one of the inactive downlink BWPs other than the active one. Downlink BWP switching can be controlled by the BWP field included in the downlink control information. Downlink BWP switching can also be controlled based on higher-level parameters.

[0100] Uplink BWP switching is used to deactivate an active uplink BWP and any other active uplink BWPs. Uplink BWP switching can be controlled by the BWP field included in the downlink control information. Uplink BWP switching can also be controlled based on higher-level parameters.

[0101] In a serving cell, it is possible that two or more downlink BWPs are not configured as active downlink BWPs. For a serving cell, one downlink BWP may be active at a given time.

[0102] In a serving cell, it is possible that two or more uplink BWPs are not configured as active uplink BWPs. For a serving cell, one uplink BWP may be active at a given time.

[0103] Figure 6 is a schematic block diagram showing an example 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 part or all of the wireless transmission / reception unit (physical layer processing unit) 10 and the upper layer processing unit 14. The wireless transmission / reception unit 10 includes at least part or all of the antenna unit 11, RF unit 12, and baseband unit 13. The upper layer processing unit 14 includes at least part or all of the media access control layer processing unit 15 and the wireless resource control layer processing unit 16.

[0104] The wireless transmitting / receiving unit 10 includes at least part or all of the wireless transmitting unit 10a and the wireless receiving unit 10b. The configuration of the baseband unit 13 included in the wireless transmitting unit 10a and the configuration of the baseband unit 13 included in the wireless receiving unit 10b may be the same or different. The configuration of the RF unit 12 included in the wireless transmitting unit 10a and the RF unit 12 included in the wireless receiving unit 10b may be the same or different. The configuration of the antenna unit 11 included in the wireless transmitting unit 10a and the configuration of the antenna unit 11 included in the wireless receiving unit 10b may be the same or different.

[0105] The upper layer processing unit 14 provides uplink data (transport blocks) to the wireless transceiver unit 10 (or wireless transmitter unit 10a). The upper layer processing unit 14 performs processing at the MAC layer, packet data integration protocol layer, wireless link control layer, and / or RRC layer.

[0106] The media access control layer processing unit 15, included in the upper layer processing unit 14, performs MAC layer processing.

[0107] The wireless resource control layer processing unit 16, included in the upper layer processing unit 14, performs RRC layer processing. The wireless resource control layer processing unit 16 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 16 configures the RRC parameters based on the RRC messages received from the base station device 3.

[0108] The wireless transceiver unit 10 (or wireless transmitter unit 10a) performs processing such as encoding and modulation. The wireless transceiver unit 10 (or wireless transmitter unit 10a) generates a physical signal by encoding and modulating the uplink data. The wireless transceiver unit 10 (or wireless transmitter unit 10a) converts OFDM symbols in the physical signal into a baseband signal by converting them to a time-continuous signal. The wireless transceiver unit 10 (or wireless transmitter unit 10a) transmits the baseband signal (or physical signal) to the base station device 3 via the radio frequency. The wireless transceiver unit 10 (or wireless transmitter unit 10a) can place the baseband signal (or physical signal) on a BWP (Active Uplink BWP) and transmit the baseband signal (or physical signal) to the base station device 3.

[0109] The wireless transceiver 10 (or wireless receiver 10b) performs processing such as demodulation and decoding. The wireless transceiver 10 (or wireless receiver 10b) can receive physical signals in the serving cell's BWP (Active Downlink BWP). The wireless transceiver 10 (or wireless receiver 10b) separates, demodulates, and decodes the received physical signals and provides the decoded information to the upper layer processing unit 14. The wireless transceiver 10 (or wireless receiver 10b) can perform channel access procedures before transmitting physical signals.

[0110] The RF unit 12 demodulates (downconverts) the physical signal received via the antenna unit 11 into a baseband signal and / or removes extraneous frequency components. The RF unit 12 provides the processed analog signal to the baseband unit 13.

[0111] The baseband unit 13 converts the analog signal (signal on the radio frequency) input from the RF unit 12 into a digital signal (baseband signal). The baseband unit 13 separates the portion corresponding to CP from the digital signal, performs a Fast Fourier Transform on the digital signal from which CP has been removed, and provides a physical signal in the frequency domain.

[0112] The baseband unit 13 performs an inverse fast Fourier transform on the uplink data to generate OFDM symbols, adds CP to the generated OFDM symbols to generate a digital signal (baseband signal), and converts the digital signal to an analog signal. The baseband unit 13 provides the analog signal to the RF unit 12.

[0113] The RF unit 12 removes extraneous frequency components from the analog signal (radio frequency signal) input from the baseband unit 13, upconverts the analog signal to a radio frequency, and transmits it via the antenna unit 11. The RF unit 12 may have a function to control the transmission power. The RF unit 12 is also called the transmission power control unit.

[0114] The following explains physical signals (signals).

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

[0116] An uplink physical channel may correspond to a set of resource elements that carry information originating from a higher layer and / or uplink control information. An uplink physical channel may be a physical channel used by 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 PUCCH (physical uplink control channel), PUSCH (physical uplink sharing channel), and PRACH (physical random access channel) may be used.

[0117] A PUCCH may be used to transmit uplink control information (UCI). A PUCCH may be transmitted to distribute (transmit, propagate) uplink control information. Uplink control information may be mapped (or placed) in a PUCCH. Terminal device 1 may transmit a PUCCH in which uplink control information is placed. Base station device 3 may receive a PUCCH in which uplink control information is placed.

[0118] Uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of the following: channel status information (CSI), scheduling request (SR), and HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledges).

[0119] Channel status information is transmitted using 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.

[0120] HARQ-ACK information may include transport blocks (TB: Transport Block, MAC PDU: Media Access Control Protocol Data Unit, DL-SCH: Downlink Shared Channel, UL-SCH: Uplink Shared Channel, PDSCH: Physical Downlink Shared Channel, PUSCH: Physical Uplink Shared Channel). HARQ-ACK status may indicate an ACK (Acknowledgment) or NACK (Negative Response) corresponding to a transport block. An ACK may indicate that the transport block has been successfully decoded. A NACK may indicate that the transport block has not been successfully decoded. HARQ-ACK information may include a HARQ-ACK codebook containing one or more HARQ-ACK statuses (or HARQ-ACK bits).

[0121] For example, a correspondence between HARQ-ACK information and a transport block may mean that the HARQ-ACK information and PDSCH used to transmit a transport block correspond correspond.

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

[0123] A scheduling request may be used to request a PUSCH (or UL-SCH) resource for a new transmission. A scheduling request may be used to indicate either a positive SR or a negative SR. The fact that a scheduling request indicates a positive SR is also referred to as "a positive SR is sent." A positive SR may indicate that a PUSCH (or UL-SCH) resource for an initial transmission is requested by terminal device 1. A positive SR may indicate that a higher layer will trigger the scheduling request. A positive SR may be sent when a higher layer instructs to send a scheduling request. The fact that a scheduling request bit indicates a negative SR is also referred to as "a negative SR is sent." A negative SR may indicate that a PUSCH (or UL-SCH) resource for an initial transmission is not requested by terminal device 1. A negative SR may indicate that a higher layer will not trigger the scheduling request. A negative SR may be sent when a higher layer has not instructed to send a scheduling request.

[0124] Channel status information may include at least some or all of the following: Channel Quality Indicators (CQI), Precoder Matrix Indicators (PMI), and Rank Indicators (RI). CQI is an indicator related to channel quality (e.g., propagation quality) or physical channel quality; PMI is an indicator related to the precoder; and RI is an indicator related to the transmit rank (or number of transmit layers).

[0125] Channel status information may be provided based on at least the reception of one or more physical signals (e.g., one or more CSI-RS) used for channel measurement. Channel status information may be selected by terminal device 1 based on at least the reception of one or more physical signals used for channel measurement. Channel measurement may include interference measurement.

[0126] PUCCH may correspond to the PUCCH format. PUCCH may be a set of resource elements used to communicate the PUCCH format. PUCCH may contain the PUCCH format. The PUCCH format may contain UCI.

[0127] A PUSCH may be used to transmit uplink data (transport blocks) and / or uplink control information. A PUSCH may be used to transmit uplink data (transport blocks) corresponding to UL-SCH and / or uplink control information. A PUSCH may be used to transmit uplink data (transport blocks) and / or uplink control information. A PUSCH may be used to transmit uplink data (transport blocks) corresponding to UL-SCH and / or uplink control information. Uplink data (transport blocks) may be placed in a PUSCH. Uplink data (transport blocks) corresponding to UL-SCH may be placed in a PUSCH. Uplink control information may be placed in a PUSCH. Terminal device 1 can transmit a PUSCH in which uplink data (transport blocks) and / or uplink control information are placed. Base station device 3 can receive a PUSCH in which uplink data (transport blocks) and / or uplink control information are placed.

[0128] PRACH can be used to send a random access preamble. PRACH can be used to transmit a random access preamble. Sequence X of PRACH u, v(n) is X u,v (n) = X u (mod(n+C v ,L RA Defined by X u This could be a ZC sequence (Zadoff-Chu sequence). u X u =exp(-jpui(i+1) / L RAIt can be defined by ). j is the imaginary unit. p is pi. C v This corresponds to the cyclical shift of PRACH. RA This corresponds to the length of PRACH. RA i can be 839, 139, or another value. i is 0 to L RA It is an integer in the range of -1. u is the sequence index of PRACH. Terminal device 1 can transmit PRACH. Base station device 3 can receive PRACH.

[0129] Given a PRACH opportunity, 64 random access preambles are defined. Each random access preamble has at least the cyclic shift C of PRACH. v And it is specified (determined, given) based on the sequence index u of PRACH.

[0130] An uplink physical signal may correspond to a set of resource elements. An uplink physical signal may not carry information generated in higher layers. An uplink physical signal may be a physical signal used by an uplink component carrier. Terminal device 1 can transmit an uplink physical signal. Base station device 3 can receive an uplink physical signal. In a wireless communication system according to one aspect of this embodiment, at least some or all of ULDMRS (Uplink Demodulation Reference Signal), SRS (Sounding Reference Signal), and ULPTRS (Uplink Phase Tracking Reference Signal) may be used.

[0131] UL DMRS is a general term for DMRS in Pusch and DMRS in Pucch.

[0132] The set of antenna ports for DMRS for PUSCH (DMRS associated with PUSCH, DMRS contained in PUSCH, and DMRS corresponding to PUSCH) may be given based on the set of antenna ports for PUSCH. That is, the set of DMRS antenna ports for PUSCH may be the same as the set of antenna ports for PUSCH.

[0133] The transmission of PUSCH and the transmission of DMRS for PUSCH may be indicated (or scheduled) by a single DCI format. PUSCH and DMRS for PUSCH may be collectively referred to as PUSCH. The transmission of PUSCH may be the transmission of PUSCH and DMRS for PUSCH.

[0134] PUSCH can be estimated from DMRS for PUSCH. That is, the propagation path of PUSCH can be estimated from DMRS for PUSCH.

[0135] The set of antenna ports for DMRS for PUCCH (DMRS associated with PUCCH, DMRS contained in PUCCH, DMRS corresponding to PUCCH) may be identical to the set of antenna ports for PUCCH.

[0136] The transmission of a PUCCH and the transmission of a DMRS for a PUCCH may be indicated (or scheduled) by a single DCI format. The placement of a PUCCH in a resource element (resource element mapping) and / or the placement of a DMRS for a PUCCH within a resource element may be provided by at least one PUCCH format. PUCCH and DMRS for a PUCCH may be collectively referred to as PUCCH. The transmission of a PUCCH may be the transmission of a PUCCH and a DMRS for a PUCCH.

[0137] PUCCH can be estimated from DMRS for PUCCH. That is, the propagation path of PUCCH can be estimated from DMRS for PUCCH.

[0138] A downlink physical channel may correspond to a set of resource elements that carry information originating from higher layers and / or downlink control information. A downlink physical channel may be a physical channel used as a downlink component carrier. Base station device 3 can transmit downlink physical channels. Terminal device 1 can receive downlink physical channels. In a wireless communication system according to one aspect of this embodiment, at least some or all of PBCH (Physical Broadcast Channel), PDCCH (Physical Downlink Control Channel), and PDSCH (Physical Downlink Shared Channel) may be used.

[0139] A PBCH may be used to transmit a MIB (Master Information Block) and / or physical layer control information. Physical layer control information is a type of downlink control information. A PBCH may be transmitted to deliver the MIB and / or physical layer control information. A BCH can be mapped to (or correspond to) a PBCH. Terminal device 1 can receive a PBCH. Base station device 3 can transmit a PBCH. Physical layer control information is also referred to as the PBCH payload and timing-related PBCH payload. A MIB may contain one or more higher layer parameters.

[0140] The physical layer control information includes 8 bits. The physical layer control information may include at least some or all of 0A to 0D. 0A is the radio frame information. 0B is the half-radio frame information (half-system frame information). 0C is the SS / PBCH block index information. 0D is the subcarrier offset information.

[0141] Wireless frame information is used to indicate the wireless frame transmitted by the PBCH (the wireless frame containing the slot from which the PBCH is transmitted). Wireless frame information is represented by 4 bits. Wireless frame information can also be represented by 4 bits of a wireless frame indicator. A wireless frame indicator may contain 10 bits. For example, a wireless frame indicator may be used to identify wireless frames from index 0 to index 1023.

[0142] Half-radio frame information is used to indicate whether a PBCH is transmitted in the first five subframes or the second five subframes of the radio frame in which the PBCH is transmitted. Here, a half-radio frame may be configured to contain five subframes. A half-radio frame may consist of the first half of the ten subframes contained in the radio frame, which is five subframes. A half-radio frame may consist of the second half of the ten subframes contained in the radio frame, which is five subframes.

[0143] SS / PBCH block index information is used to indicate the SS / PBCH block index. SS / PBCH block index information can be represented by 3 bits. SS / PBCH block index information may consist of 3 bits of the SS / PBCH block index index. The SS / PBCH block index indicator may contain 6 bits. The SS / PBCH block index indicator can be used to identify SS / PBCH blocks from index 0 to index 63 (or index 0 to index 3, index 0 to index 7, index 0 to index 9, index 0 to index 19, etc.).

[0144] Subcarrier offset information is used to indicate the subcarrier offset. Subcarrier offset information can be used to indicate the difference between the first subcarrier where the PBCH is located and the first subcarrier where the control resource set with index 0 is located.

[0145] A PDCCH may be used to transmit downlink control information (DCI). A PDCCH may be transmitted to distribute downlink control information. Downlink control information may be mapped to a PDCCH. Terminal device 1 can receive a PDCCH in which downlink control information is placed. Base station device 3 can transmit a PDCCH in which downlink control information is placed.

[0146] Downlink control information may be compatible with the DCI format. Downlink control information may be included in the DCI format. Downlink control information may be placed in each field of the DCI format.

[0147] The DCI format is a general term encompassing DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. The uplink DCI format is a general term encompassing DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term encompassing DCI format 1_0 and DCI format 1_1.

[0148] DCI format 0_0 is used at least to schedule cell pushes (or pushes placed on cells). DCI format 0_0 includes at least some or all of fields 1A to 1E. 1A is the DCI format identification field (identifier field for DCI format). 1B is the frequency domain resource allocation field (FDRA field, FDRA information field). 1C is the time domain resource allocation field (TDRA field, TDRA information field). 1D is the frequency hopping flag field. 1E is the MCS field (Modulation-and-Coding-Scheme field).

[0149] The frequency domain resource allocation field may be referred to as the FDRA field or FDRA information field.

[0150] The time domain resource allocation field may be referred to as the TDRA field or TDRA information field.

[0151] The DCI format identifier field may indicate whether the DCI format containing the DCI format identifier field is an uplink DCI format or a downlink DCI format. The DCI format identifier field in DCI format 0_0 may show 0 (or may indicate that DCI format 0_0 is an uplink DCI format).

[0152] The frequency domain resource allocation field included in DCI format 0_0 can be used to indicate at least the allocation of frequency resources for PUSCH.

[0153] The time domain resource allocation field included in DCI format 0_0 may be used to indicate at least the allocation of time resources for PUSCH. The time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for PUSCH scheduled by DCI format 0_0.

[0154] The frequency hopping flag field may be used to indicate whether frequency hopping applies to a PUSCH. The frequency hopping flag field may be used to indicate whether frequency hopping applies to a PUSCH scheduled by DCI format 0_0.

[0155] The MCS field included in DCI format 0_0 may be used to indicate at least some or all of the modulation scheme and / or target coding rate for PUSCH. The transport block size (TBS) of PUSCH may be given based at least some or all of the target coding rate and the modulation scheme for PUSCH. The modulation scheme may include at least one of the modulation order, target coding rate, and spectral efficiency.

[0156] DCI format 0_0 does not necessarily have to include fields used in CSI requests. In other words, CSI may not be required by DCI format 0_0.

[0157] DCI format 0_0 does not have to include a carrier indicator field. An uplink component carrier on which a PUSCH scheduled by DCI format 0_0 is located may be the same as an uplink component carrier on which a PDCCH containing DCI format 0_0 is located.

[0158] DCI format 0_0 does not have to include a BWP field. The uplink BWP on which a PUSCH scheduled by DCI format 0_0 is located may be the same as the uplink BWP on which a PDCCH containing DCI format 0_0 is located.

[0159] DCI format 0_1 / 0_2 is used for scheduling PUSCH for (or placed on) a cell. DCI format 0_1 / 0_2 includes at least some or all of fields 2A-2H. 2A is the DCI format identification field. 2B is the frequency domain resource allocation field. 2C is the time domain resource allocation field. 2D is the frequency hopping flag field. 2E is the MCS field. 2F is the CSI request field. 2G is the BWP field. 2H is the carrier indicator field.

[0160] The DCI format identification field in DCI format 0_1 / 0_2 may indicate 0 (or may indicate that DCI format 0_1 / 0_2 is an uplink DCI format).

[0161] The frequency domain resource allocation field included in DCI format 0_1 / 0_2 can be used to indicate, at least, the allocation of frequency resources for PUSCH. The frequency domain resource allocation field included in DCI format 0_1 / 0_2 can be used to indicate the allocation of frequency resources for PUSCH scheduled by the DCI format.

[0162] The time domain resource allocation field included in DCI format 0_1 / 0_2 may be used to indicate the allocation of time resources for PUSCH, at least. The time domain resource allocation field included in DCI format 0_1 / 0_2 may be used to indicate the allocation of time resources for PUSCH scheduled by DCI format 0_1 / 0_2.

[0163] The frequency hopping flag field may be used to indicate whether frequency hopping applies to a PUSCH scheduled by DCI format 0_1 / 0_2.

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

[0165] If DCI format 0_1 ​​includes a BWP field, the BWP field may be used to indicate the uplink BWP on which the PUSCH scheduled by DCI format 0_1 ​​is located. If DCI format 0_1 / 0_2 does not include a BWP field, the uplink BWP on which the PUSCH is located may be the active uplink BWP. If there are two or more uplink BWPs configured within terminal device 1 in the uplink component carrier, the number of bits in the BWP field included in DCI format 0_1 / 0_2 used to schedule the PUSCH located on the uplink component carrier may be one or more. If there is one uplink BWP configured within terminal device 1 in the uplink component carrier, the number of bits in the BWP field included in DCI format 0_1 / 0_2 used to schedule the PUSCH located on the uplink component carrier may be zero.

[0166] The CSI request field is used at least to indicate a CSI report.

[0167] If the DCI format 0_1 / 0_2 includes a carrier indicator field, the carrier indicator field may be used to indicate the uplink component carrier (or serving cell) where the PUSCH is located. If the DCI format 0_1 / 0_2 does not include a carrier indicator field, the serving cell where the PUSCH is located may be the same serving cell where the PDCCH containing the DCI format 0_1 / 0_2 used for scheduling the PUSCH is located. If there are two or more uplink component carriers (or serving cells) configured within terminal device 1 in a serving cell group (when uplink carrier aggregation operates within a serving cell group), or if cross-carrier scheduling is configured for a serving cell group, the number of bits in the carrier indicator field contained in the DCI format 0_1 / 0_2 used for scheduling the PUSCH located in the serving cell group may be one or more (e.g., 3). If the number of uplink component carriers (or serving cells) configured within terminal device 1 in a serving cell group is 1 (or if uplink carrier aggregation is not operating within the serving cell group), or if cross-carrier scheduling is not configured for the serving cell group, the number of bits in the carrier indicator field included in DCI format 0_1 / 0_2 used for scheduling PUSCH placed in the serving cell group may be zero.

[0168] Furthermore, DCI format 0_1 / 0_2 may include one or more DCI fields, such as an SRS resource set indicator field, an SRS resource indicator field, a second SRS resource indicator field, a number of precoding information and layer fields, a second precoding information field, an antenna port field, a DMRS sequence initialization field, a PTRS / DMRS related field, and / or a second PTRS related field.

[0169] The number of bits of the SRS resource set indicator field can be determined as 0 or 2 bits based on one or more conditions. The number of bits of the DCI field can be 2 bits if txConfig is configured as "nonCodeBook", is configured by srs-ResourceSetToAddModListDCI-0-2, and there are two SRS resource sets associated with the usage of the "nonCodeBook" value, or if txConfig is configured as "codebook" and there are two SRS resource sets configured by srs-ResourceSetToAddModListDCI-0-2 and associated with the usage of the "codebook" value. Otherwise, the number of bits of the DCI field can be 0 bits.

[0170] The number of precoding information and layer fields can indicate the precoding information (i.e., TPMI value) and the number of layers for PUSCH transmission scheduled by DCI format 0_1 / 0_2.

[0171] The number of bits of the precoding information and the number of layers can be determined as 0, 1, 2, 3, 4, 5, 6, or more bits based on one or more conditions depending on whether the transform precoder is enabled or disabled, the number of antenna ports, the RRC parameter txConfig, ul-FullPowerTransmission, the maxRank and codebookSubset of DCI format 0_1, or the maxRankDCI-0-2 and codebookSubsetDCI-0-2 of DCI format 0_2.

[0172] For example, the number of bits in the precoding information and the number of layer fields may be 0 bits if the RRC parameter txConfig is configured to "nonCodebook". The number of bits in the DCI field may be 0 bits for one antenna port if the RRC parameter txConfig is configured to "codebook". The number of bits is 4, 5, or 6 bits for four antenna ports if the RRC parameter txConfig is configured to "codebook", the RRC parameter ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", and the conversion precoder is disabled, depending on the values ​​of the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2. The number of bits in the DCI field is 4 or 5 bits according to the value of the RRC parameter codebookSubset if there are 4 antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "MlpowerMode1", maxRank for DCI format 0_1 ​​or maxRank for DCI format 0_2 DCI-0-2 is configured to "2", and the conversion precoder is disabled. The number of bits in the DCI field is 4 or 6 bits according to the value of the RRC parameter codebookSubset for DCI format 0_1 ​​or codebookSubset for DCI format 0_2 DCI-0-2 if there are 4 antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank for DCI format 0_1 ​​or maxRank for DCI format 0_2 DCI-0-2 is configured to "3" or "4", and the conversion precoder is disabled.The number of bits in the DCI field can be 2, 4, or 5 bits, depending on whether the conversion precoder is enabled or disabled, and if txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or "fullpower", and if the four antenna ports are configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", as well as the values ​​of the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2. The number of bits in the DCI field can be 3 or 4 bits, depending on whether the conversion precoder is enabled or disabled, and the value of the RRC parameter codebookSubset for DCI format 0_1 ​​or codebookSubsetDCI-0-2 for DCI format 0_2, provided that there are 4 antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", and maxRank for DCI format 0_1 ​​or maxRankDCI-0-2 for DCI format 0_2 is configured to "1". The number of bits in the DCI field can be 2 or 4 bits, depending on the values ​​of the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2, when there are two antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", and the conversion precoder is disabled.The number of bits in the DCI field can be 2 bits if there are two antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", the conversion precoder is disabled, maxRank for DCI format 0_1 ​​or maxRankDCI-0-2 for DCI format 0_2 is configured to "2", and codebookSubset for DCI format 0_1 ​​or codebookSubsetDCI-0-2 for DCI format 0_2 is configured to "nonCoherent". The number of bits in the DCI field can be 1 or 3 bits, depending on whether the conversion precoder is enabled or disabled, and whether txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or "fullpower", and whether the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2, for two antenna ports. The number of bits in the DCI field can be 2 bits, depending on whether the conversion precoder is enabled or disabled, and the value of the RRC parameter codebookSubset for DCI format 0_1 ​​or codebookSubsetDCI-0-2 for DCI format 0_2, provided there are two antenna ports, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank for DCI format 0_1 ​​or maxRankDCI-0-2 for DCI format 0_2 is configured to "1".

[0173] Figures 26, 27, and 28 are examples of tables used for the number of precoding information and layer fields in DCI format 0_1 / 0_2, which are determined based on the values ​​of the RRC parameters txConfig, ul-FullPowerTransmission, maxRank, and / or codebookSubset, and / or the number of antenna ports, and / or whether the conversion precoder is enabled or disabled.

[0174] The number of bits used for precoding information and layer fields in DCI format 0_1 / 0_2 can be determined according to the table.

[0175] For the RRC parameter txConfig configured in "codebook", if ul-FullPowerTransmission is configured to "fullpowerMode2", and maxRank DCI-0-2 in DCI format 0_1 ​​and / or maxRankDCI-0-2 in DCI format 0_2 are configured to be greater than 2, and at least one SRS having four antenna ports is configured in the SRS resource set indicated by the SRS resource set indicator field if present, or otherwise in the SRS resource set with the usage set in "codebook", and if an SRS resource having two antenna ports is indicated via an SRI in the same SRS resource set, the relevant table may be used.

[0176] If different SRS resources with different numbers of antenna ports are configured for the RRC parameter txConfig configured in "codebook", the bit width is determined according to the maximum number of ports in the SRS resources among all configured SRS resources in the SRS resource set, with the usage set in "codebook". If the number of ports in the configured SRS resources in the set is less than the maximum number of ports in the SRS resources among the configured SRS resources, the most significant bit, set to "0", is inserted into the field.

[0177] txConfig can be used to indicate whether the UE uses codebook-based or non-codebook-based transmission. If txConfig is not present, the UE transmits PUSCH on one antenna port.

[0178] ul-FullPowerTransmission can be used to configure the UE in UL full power transmission mode.

[0179] maxRank and maxRankDCI-0-2 can be used to indicate a subset of PMIs addressed by TRI from 1 to ULmaxRank. The field maxRank applies to DCI format 0_1, and the field maxRankDCI-0-2 applies to DCI format 0_2.

[0180] The fields codebookSubset and codebookSubsetDCI-0-2 can be used to indicate a subset of the PMI addressed by the TPMI, where the PMI is supported by the UE with maximum coherence capability. The field codebookSubset applies to DCI format 0_1, and the field codebookSubsetDCI-0-2 applies to DCI format 0_2.

[0181] The second precoding information field may indicate the precoding information (i.e., TPMI value) and the number of layers for a PUSCH / SRS transmission scheduled according to DCI format 0_1 / 0_2.

[0182] The number of bits in the second precoding information field may be determined as 0, 1, 2, 3, 4, 5, 6, or more bits, based on one or more conditions including whether the conversion precoder is enabled or disabled, the number of antenna ports, the values ​​of the RRC parameters txConfig, ul-FullPowerTransmission, maxRank, and codebookSubset, and the values ​​of maxRank and codebookSubset for DCI format 0_1 ​​and maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2.

[0183] For example, the number of bits in the second precoding information field may be 0 if the SRS resource set indicator field does not exist. The number of bits in the DCI field may be 0 if the RRC parameter txConfig is configured to "nonCodebook". The number of bits in the DCI field may be 0 for one antenna port if the RRC parameter txConfig is configured to "codebook". The number of bits in the DCI field may be 3, 4, or 5 bits according to the values ​​of the RRC parameters maxRank and codebookSubset in DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubset in DCI format 0_2, according to the associated table where the number of layers and layer fields indicated by the precoding information is the same for four antenna ports, the SRS resource set indicator field exists, txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", and the conversion precoder is disabled. The number of bits in the DCI field can be 4 bits, according to the associated table where the number of layers and layer fields indicated by the precoding information for the four antenna ports are the same, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank in DCI format 0_1 ​​or maxRankDCI-0-2 in DCI format 0_2 is configured to "2", and if the conversion precoder is disabled, according to the value of the RRC parameter codebookSubset in DCI format 0_1 ​​or codebookSubsetDCI-0-2 in DCI format 0_2.The number of bits in the DCI field can be 4 bits according to the value of the RRC parameter codebookSubset or codebookSubsetDCI-0-2 in DCI format 0_1, if the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank is configured to "3" or "4", and the conversion precoder is disabled, according to the associated table where the number of layers and the number of layer fields indicated by the precoding information are the same for the four antenna ports. The number of bits in the DCI field can be 2, 4, or 5 bits, depending on the associated table where the number of layers and layer fields indicated by the precoding information are the same for the four antenna ports, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", the conversion precoder is either enabled or disabled, and the values ​​of the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2.The number of bits in the DCI field can be 3 or 4 bits, depending on the value of the RRC parameter codebookSubset in DCI format 0_1 ​​or codebookSubsetDCI-0-2 in DCI format 0_2, according to the associated table where the number of layers and layer fields indicated by the precoding information for the four antenna ports are the same, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank or maxRankDCI-0-2 in DCI format 0_1 ​​is configured to "1", the conversion precoder is either enabled or disabled, and the value of the RRC parameter codebookSubset in DCI format 0_1 ​​or codebookSubsetDCI-0-2 in DCI format 0_2. The number of bits in the DCI field can be 1 or 3 bits, according to the values ​​of the RRC parameters maxRank and codebookSubset in DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 in DCI format 0_2, according to the associated table where the number of layers and layer fields indicated by the precoding information is the same for the two antenna ports, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", and the conversion precoder is disabled.The number of bits in the DCI field can be 2 bits if, according to the associated table where the number of layers and layer fields indicated by the precoding information for the two antenna ports are the same, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", the conversion precoder is disabled, maxRank for DCI format 0_1 ​​or maxRankDCI-0-2 for DCI format 0_2 is configured to "2", and codebookSubset or codebookSubsetDCI-0-2 for DCI format 0_1 ​​is configured to "nonCoherent". The number of bits in the DCI field can be 1 or 3 bits, according to the associated table where the number of layers and layer fields indicated by the precoding information are the same for the two antenna ports, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is not configured, or is configured to "fullpowerMode2", or is configured to "fullpower", the conversion precoder is either enabled or disabled, and the values ​​of the RRC parameters maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2.The number of bits in the DCI field can be 2 bits, according to the associated table where the number of layers and layer fields indicated by the precoding information for the two antenna ports are the same, the SRS resource set indicator field is present, txConfig is configured to "codebook", ul-FullPowerTransmission is configured to "fullpowerMode1", maxRank in DCI format 0_1 ​​or maxRankDCI-0-2 in DCI format 0_2 is configured to "1", and if the conversion precoder is disabled, according to the value of the RRC parameter codebookSubset in DCI format 0_1 ​​or codebookSubsetDCI-0-2 in DCI format 0_2.

[0184] Figures 29 and 30 are examples (one or more) of tables used for the second precoding information field in DCI format 0_1 / 0_2, which are determined based on the values ​​of the RRC parameters txConfig, ul-FullPowerTransmission, maxRank, maxRankDCI-0-2, and / or codebookSubset, and / or the number of antenna ports, and / or whether the conversion precoder is enabled or disabled, the number of layers and layer fields indicated by the precoding information, and whether the SRS resource set indicator field exists.

[0185] The relevant table may be used if, for the RRC parameter txConfig configured in "codebook", ul-FullPowerTransmission is configured to "fullpowerMode2", the maxRank in DCI format 0_1 ​​and / or maxRankDCI-0-2 in DCI format 0_2 are configured to be greater than 2, at least one SRS having four antenna ports is configured within the SRS resource set indicated by the SRS resource set indicator field, and an SRS resource having two antenna ports is indicated via a second SRS within the same SRS resource set.

[0186] If different SRS resources with different numbers of antenna ports are configured for the RRC parameter txConfig configured in "codebook", the bit width is determined according to the maximum number of ports in the SRS resources among the configured SRS resources in the second SRS resource set with the usage set in "codebook" as defined in the relevant table. If the number of ports in the configured SRS resources in the set is less than the maximum number of ports in the SRS resources among the configured SRS resources, the most significant bit is inserted into the field with a value of "0".

[0187] The antenna port field may indicate the number of DMRSCDM groups (one or more), without the number of data and DMRS ports (one or more) and / or preload symbols.

[0188] The number of bits in the antenna port field can be determined as 2, 3, 4, 5, or more bits, based on whether the conversion precoder is enabled or disabled, and one or more conditions determined by the values ​​of the RRC parameters dmrs-Type, maxLength, txConfig, dmrs-UplinkTransformpreprecoded, and tp-pi2BPSK.

[0189] For example, the number of bits in the antenna port field can be 2 bits, as defined by the relevant table, when the transform precoder is enabled, dmrs-Type is configured to "1", and maxLength is configured to "1", except that both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured and π / 2BPSK is used. The number of bits in the DCI field can also be 2 bits, as defined by the relevant table, when the transform precoder is enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, π / 2BPSK is used, dmrs-Type is configured to "1", and maxLength is configured to "1". However, nSCID is the scrambling identity of the antenna port as defined by the DMRS sequence generation method for PUSCH when transform precoding is enabled. The number of bits in the DCI field can be 4 bits, as defined by the relevant table, when the transform precoder is enabled, dmrs-Type is configured to "1", and maxLength is configured to "2", except that both dmrs-UplinkTransformPrecoded and tp-pi2BPSK are configured and π / 2BPSK is used. The number of bits in the DCI field can be 4 bits, as defined by the relevant table, when the transform precoder is enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, π / 2BPSK is used, dmrs-Type is configured to "1", and maxLength is configured to "2". However, nSCID is the scrambling identity of the antenna port as defined by the DMRS sequence generation method for PUSCH when transform precoding is enabled.The number of bits in the DCI field can be 3 bits, as defined by the relevant table, when the conversion precoder is disabled, dmrs-Type is configured to 1, and maxLength is configured to 1, and the rank value is determined according to the SRS resource indicator field if the RRC parameter txConfig is configured to "nonCodebook", and according to the number of precoding information and layer fields if the RRC parameter txConfig is configured to "codebook". The number of bits in the DCI field can be 4 bits, as defined by the relevant table, when the conversion precoder is disabled, dmrs-Type is configured to "1", and maxLength is configured to "2", and the rank value is determined according to the SRS resource indicator field if the upper layer parameter txConfig is configured to "nonCodebook", and according to the number of precoding information and layer fields if the RRC parameter txConfig is configured to "codebook". The number of bits in the DCI field can be 4 bits, as defined by the relevant table, when the conversion precoder is disabled, dmrs-Type is configured to "2", and maxLength is configured to "1", and the rank value is determined according to the SRS resource indicator field if the RRC parameter txConfig is configured to "nonCodebook", and according to the number of precoding information and layer fields if the RRC parameter txConfig is configured to "codebook". The number of bits in the DCI field can be 5 bits, as defined by the relevant table, when the conversion precoder is disabled, dmrs-Type is configured to "2", and maxLength is configured to "2", and the rank value is determined according to the SRS resource indicator field if the RRC parameter txConfig is configured to "nonCodebook", and according to the number of precoding information and layer fields if the upper layer parameter txConfig is configured to "codebook".The number of CDM groups that do not contain the data of values 1, 2, and 3 in the related table refers to CDM groups {0}, {0,1}, and {0,1,2} respectively.

[0190] FIGS. 31 and 32 are examples (singular or plural) of tables used for the antenna port field in DCI format 0_1 / 0_2, which are determined based on, respectively, whether the values of the RRC parameters txConfig, maxLength, and / or dmrs-Type, whether dmrs-UplinkTransformPrecoding and / or tp-pi2BPSK is configured, and / or whether the transform precoder is enabled or disabled, the number of layers and the number of layer fields indicated by the precoding information, and whether the SRS resource set indicator field exists.

[0191] dmrs-Type can be used for the selection of the DMRS type used for UL. If dmrs-Type does not exist, the UE uses DMRS type 1.

[0192] maxLength can be used to indicate the maximum number of OFDM symbols for UL front-loaded DMRS. len1 corresponds to the value 1 and len2 corresponds to the value 2. If maxLength does not exist, the UE applies the value len1. When set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI.

[0193] dmrs-UplinkTransformPrecoding can be used to indicate whether low PAPR DMRS is used for PUSCH with pi / 2BPSK modulation. The network can configure this field only when tp-pi2BPSK is used within PUSCH-Config.

[0194] tp-pi2BPSK can be used to indicate whether the UE should enable pi / 2-BPSK in the conversion precoding if the field exists, and disable it otherwise.

[0195] The PTRS-DMRS related fields may indicate the DMRS port associated with ULPTRS port 0 and / or 1 or the actual ULPTRS port.

[0196] The number of bits in the PTRS-DMRS related fields may be determined based on one or more conditions, including whether PTRS-UplinkConfig is configured, the values ​​of mazNroPorts, the RRC parameter maxRank in DCI format 0_1, the maxRankDCI-0-2 in DCI format 0_2, the value of the SRS resource indicator field, and / or the number of precoding information and layer fields.

[0197] For example, the number of bits in the PTRS-DMRS related fields may be 0 if PTRS-UplinkConfig is not configured as either dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB, the conversion precoder is not disabled, the conversion precoder is disabled, or maxRank is configured as "1". The number of bits in the DCI field may otherwise be 2, and when one PT-RS port and two PT-RS ports are each configured by PTRS-Uplink's ConfigmaxNrofPorts, the associated table is used to indicate the association between the PTRS port(s) and DMRS port(s), with the DMRS port(s) being indicated by the Antenna Port field. When the SRS Resource Set Indicator field exists and maxRank > 2, this field indicates the association between the PTRS port(s) and DMRS port(s) corresponding to the SRS Resource Indicator field and / or the number of precoding information and layer fields in the associated table. When the SRS Resource Set Indicator field exists and maxRank is configured to "2", according to the relevant table, the MSB of this field indicates the association between the PTRS port(s) and DMRS port(s) corresponding to the SRS Resource Indicator field and / or the number of precoding information and layer fields, and the LSB of this field indicates the association between the PTRS port(s) and DMRS port(s) corresponding to the second SRS Resource Indicator field and / or the second precoding information field.

[0198] If the "Bandwidth Part Indicator" field exists for bandwidth parts other than the active bandwidth part and for the bandwidth part where the "PTRS-DMRS Related" field is indicated, but not for the active bandwidth part, the UE will infer that the "PTRS-DMRS Related" field does not exist for the specified bandwidth part.

[0199] The second PTRS-DMRS related field may indicate DMRS ports 0 and / or 1 associated with the ULPTRS port.

[0200] The number of bits in the second PTRS-DMRS related field may be 2 bits if the PTRS-DMRS related field and the SRS resource set indicator field exist and maxRank > 2. The number of bits in the DCI field may be 0 bits otherwise, and when one PT-RS port and two PT-RS ports are each configured by ConfigmaxNrofPorts of the PTRS-Uplink, the related table is used to indicate the association between the PTRS port(s) and DMRS port(s) corresponding to the second SRS source indicator field and / or the second precoding information field, with the DMRS port indicated by the antenna port field.

[0201] The DMRS sequence initialization field may indicate the value of the nSCID.

[0202] The number of bits in the DMRS sequence initialization field can be determined based on whether the conversion precoder is enabled or disabled. For example, the number of bits in the DCI field may be 0 if the conversion precoder is enabled. The number of bits in the DCI field may be 1 if the conversion precoder is disabled.

[0203] DCI format 1_0 is used at least for scheduling PDSCHs of cells (placed on cells). DCI format 1_0 includes at least some or all of fields 3A-3F. 3A is the DCI format identification field. 3B is the frequency domain resource allocation field. 3C is the time domain resource allocation field. 3D is the MCS field. 3E is the PDSCH-to-HARQ-feedback indicator field. 3F is the PUCCH resource indicator field.

[0204] The DCI format identification field included in DCI format 1_0 can indicate 1 (or indicate that DCI format 1_0 is a downlink DCI format).

[0205] The frequency domain resource allocation field included in DCI format 1_0 can be used to indicate the allocation of frequency resources for a PDSCH. The frequency domain resource allocation field included in DCI format 1_0 can be used to indicate the allocation of frequency resources for a PDSCH scheduled by DCI format 1_0.

[0206] The time domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of time resources for PDSCH, at least. The time domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of time resources for PDSCH scheduled by DCI format 1_0.

[0207] The MCS field included in DCI format 1_0 may be used to indicate at least some or all of the modulation scheme of the PDSCH and / or the target coding rate for the PDSCH. The transport block size (TBS) of the PDSCH may be given based at least some or all of the target coding rate and the modulation scheme for the PDSCH.

[0208] The PDSCH-to-HARQ feedback timing indicator field may be used to indicate at least the offset (K1) from the slot containing the first OFDM symbol of a PDSCH scheduled by DCI format 1_0, which is located in another slot containing the first OFDM symbol of a PUCCH triggered by DCI format 1_0.

[0209] The PUCCH resource indicator field may be a field that indicates the index of any one or more PUCCH resources included in a PUCCH resource set for PUCCH transmission. A PUCCH resource set may contain one or more PUCCH resources. The PUCCH resource indicator field can trigger a PUCCH transmission on PUCCH resources indicated at least based on the PUCCH resource indicator field.

[0210] DCI format 1_0 does not have to include a carrier indicator field. 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.

[0211] DCI format 1_0 does not have to include a BWP field. The downlink BWP where a PDSCH scheduled by DCI format 1_0 is located may be the same as the downlink BWP where a PDCCH containing DCI format 1_0 is located.

[0212] DCI format 1_1 is used for scheduling PDSCHs for (or placed on) cells. DCI format 1_1 includes at least some or all of fields 4A-4H. 4A is the DCI format identification field. 4B is the frequency domain resource allocation field. 4C is the time domain resource allocation field. 4D is the MCS field. 4E is the PDSCH-to-HARQ-feedback indicator field. 4F is the PUCCH resource indicator field. 4G is the BWP field. 4H is the carrier indicator field.

[0213] The DCI format identification field included in DCI format 1_1 can indicate 1 (or indicate that DCI format 1_1 is a downlink DCI format).

[0214] The frequency domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of frequency resources for PDSCHs, at a minimum. The frequency domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of frequency resources for PDSCHs scheduled by DCI format 1_1.

[0215] The time domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of time resources for PDSCH, at least. The time domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of time resources for PDSCH scheduled by DCI format 1_1.

[0216] The MCS field included in DCI format 1_1 may be used to indicate at least some or all of the modulation scheme and / or target coding rate for the PDSCH. The MCS field included in DCI format 1_1 may be used to indicate at least some or all of the modulation scheme and / or target coding rate for the PDSCH scheduled by DCI format 1_1.

[0217] If DCI format 1_1 includes a PDSCH-to-HARQ feedback timing indicator field, the PDSCH-to-HARQ feedback timing indicator field indicates the offset (K1) from the slot containing the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another slot containing the first OFDM symbol of the PUCCH triggered by DCI format 1_1. If DCI format 1_1 does not include a PDSCH-to-HARQ feedback timing indicator field, it is the offset from the slot containing the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another slot identified by the higher-level parameter where the first OFDM symbol of the PUCCH triggered by DCI format 1_1 is located.

[0218] If DCI format 1_1 includes a BWP field, the BWP field may be used to indicate the downlink BWP where the PDSCH scheduled by DCI format 1_1 is located. If DCI format 1_1 does not include a BWP field, the downlink BWP where the PDSCH is located may be the active downlink BWP. If there are two or more downlink BWPs configured within terminal device 1 in the downlink component carrier, the number of bits in the BWP field included in DCI format 1_1 used to schedule the PDSCH located on the downlink component carrier may be one or more. If there is one downlink BWP configured within terminal device 1 in the downlink component carrier, the number of bits in the BWP field included in DCI format 1_1 used to schedule the PDSCH located on the downlink component carrier may be zero.

[0219] If DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the downlink component carrier (or serving cell) where the PDSCH is located. If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier (or serving cell) where the PDSCH is located may be the same as the downlink component carrier (or serving cell) where the PDCCH is located, which includes the DCI format 1_1 used for scheduling the PDSCH. If there are two or more downlink component carriers (or serving cells) configured within terminal device 1 in a serving cell group (when downlink carrier aggregation operates within a serving cell group), or if cross-carrier scheduling is configured for a serving cell group, the number of bits in the carrier indicator field included in DCI format 1_1 used to schedule the PDSCH located in the serving cell group may be one or more (e.g., 3). If the number of downlink component carriers (or serving cells) configured within terminal device 1 in a serving cell group is 1 (or if downlink carrier aggregation does not operate within the serving cell group), or if cross-carrier scheduling is not configured for the serving cell group, the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling PDSCHs placed in the serving cell group may be zero.

[0220] A PDSCH may be used to transmit one or more transport blocks. A PDSCH may be used to transmit one or more transport blocks corresponding to a DL-SCH. One or more transport blocks can be transmitted using a PDSCH. A PDSCH may be used to transmit one or more transport blocks corresponding to a DL-SCH. One or more transport blocks may be placed within a PDSCH. One or more transport blocks corresponding to a DL-SCH may be placed within a PDSCH. Base station device 3 may transmit a PDSCH. Terminal device 1 can receive a PDSCH.

[0221] Downlink physical signals may correspond to a set of resource elements. Downlink physical signals cannot carry information generated in higher layers. Downlink physical signals may be physical signals used in downlink component carriers. Downlink physical signals may be transmitted by base station equipment 3. Downlink physical signals may be transmitted by terminal equipment 1. In a wireless communication system according to one aspect of this embodiment, at least some or all of SS (Synchronization Signal), DLDMRS (Downlink DeModulation Reference Signal), CSI-RS (Channel Status Information Reference Signal), and DL PTRS (Downlink Phase Tracking Reference Signal) may be used.

[0222] A synchronization signal may be used to synchronize at least terminal device 1 in the frequency domain and / or time domain of the downlink. The synchronization signal is a collective term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0223] Figure 7 shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In Figure 7, the horizontal axis represents the time domain (OFDM symbol index l symThe graph shows the frequency domain on the vertical axis. Shaded blocks represent sets of resource elements for PSS. Grid line blocks represent sets of resource elements for SSS. Horizontal line blocks also represent sets of resource elements for PBCH and sets of resource elements for DMRS for PBCH (DMRS related to PBCH, DMRS contained in PBCH, and DMRS corresponding to PBCH).

[0224] As shown in Figure 7, the SS / PBCH block contains PSS, SSS, and PBCH. The SS / PBCH block contains four consecutive OFDM symbols. The SS / PBCH block contains 240 subcarriers. PSS is assigned to subcarriers 57 through 183 in the first OFDM symbol. SSS is assigned to subcarriers 57 through 183 in the third OFDM symbol. 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. In subcarriers 1 through 240 of the second OFDM symbol, PBCH is assigned to subcarriers to which the PBCH DMRS is not assigned. In the third OFDM symbol, subcarriers 1-48, PBCH is assigned to a subcarrier that does not have a DMRS assigned to it. In the third OFDM symbol, subcarriers 193-240, PBCH is assigned to a subcarrier that does not have a DMRS assigned to it. In the fourth OFDM symbol, subcarriers 1-240, PBCH is assigned to a subcarrier that does not have a DMRS assigned to it.

[0225] The antenna ports for PSS, SSS, PBCH, and DMRS on the PBCH within the SS / PBCH block may be the same.

[0226] PBCH can be inferred from the DM-RS of PBCH. In the DM-RS of PBCH, the channel on which the PBCH symbol on the antenna port is transmitted can be inferred from the channel on which another DM-RS symbol on the antenna port is transmitted, using the same SS / PBCH block index, only if the two symbols are in the same SS / PBCH block where they are transmitted within the same slot.

[0227] DL DMRS is a general term for the DMRS of PBCH, PDSCH, and PDCCH.

[0228] The set of antenna ports for DMRS for a PDSCH (DMRS associated with the PDSCH, DMRS contained within the PDSCH, and DMRS corresponding to the PDSCH) may be given based on the set of antenna ports for the PDSCH. The set of antenna ports for DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

[0229] PDSCH transmissions and DMRS transmissions for PDSCH may be indicated (or scheduled) by a single DCI format. PDSCH and DMRS for PDSCH may be collectively referred to as PDSCH. A PDSCH transmission may be a PDSCH and DMRS transmission for PDSCH.

[0230] PDSCH can be inferred from DMRS for PDSCH. In the case of DMRS associated with PDSCH, the channel on which the PDSCH symbol is transmitted on one antenna port can be inferred from the channel on which the other DMRS symbol is transmitted on the antenna port, only if the two symbols are in the same slot, within the same PRG (Precoding Resource Group), and within the same resource as the scheduled PDSCH.

[0231] The antenna port for 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.

[0232] PDCCH can be inferred from the DMRS for PDCCH. For DMRS associated with PDCCH, the channel on which the PDCCH symbol is propagated on one antenna port can be inferred from the channel on which another symbol is propagated on the same antenna port, only if the two symbols are in a resource (i.e., a resource within a resource within a REG bundle) where the UE can assume that the UE is using the same precoding.

[0233] BCH (Broadcast Channel), UL-SCH (Uplink-Shared Channel), and DL-SCH (Downlink-Shared Channel) are transport channels. Channels used in the MAC layer are called transport channels. The unit of a transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU (Protocol Data Unit). In the MAC layer, HARQ (Hybrid Automatic Retransmission Request) control is performed for each transport block. A transport block is the unit of data delivered to the physical layer by the MAC layer. In the physical layer, transport blocks are mapped to codewords, and modulation processing is performed for each codeword.

[0234] One UL-SCH and one DL-SCH may be provided per serving cell. BCH may be provided to PCell. BCH may not be provided to PSCell and SCell.

[0235] BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. BCCH is an RRC layer channel used to distribute MIB or system information. CCCH may be used to transmit common RRC messages among multiple terminal devices 1. CCCH may be used for terminal devices 1 that are not connected by RRC. DCCH may be used to transmit dedicated RRC messages to terminal devices 1. DCCH may be used for terminal devices 1 that are in RRC connection mode.

[0236] An RRC message contains one or more RRC parameters (information elements, higher-level parameters). For example, an RRC message may contain an MIB. For example, an RRC message may contain system information (SIB: System Information Block, MIB). SIB is a general term for various types of SIBs (e.g., SIB1, SIB2). For example, an RRC message may contain a message corresponding to CCCH. For example, an RRC message may contain a message corresponding to DCCH. An RRC message is a general term for common RRC messages and dedicated RRC messages.

[0237] BCCH in a logical channel may be mapped to BCH or DL-SCH in a transport channel. DCCH in a logical channel may be mapped to DL-SCH or UL-SCH in a transport channel. DCCH in a logical channel may be mapped to DL-SCH or UL-SCH in a transport channel.

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

[0239] Higher-layer parameters are parameters included in RRC messages or MAC CEs (Medium Access Control Control Elements). Higher-layer parameters are a general term encompassing information included in MIBs, system information, messages corresponding to CCCHs, messages corresponding to DCCHs, and MAC CEs. When higher-layer parameters are included in an RRC message, they may be referred to as RRC parameters or RRC configurations.

[0240] Higher-level parameters can be cell-specific or UE-specific. Cell-specific parameters are those that include common configurations within a cell. UE-specific parameters are those that include configurations that may be configured differently for each UE.

[0241] Base station equipment may exhibit changes in cell-specific parameters due to reconfiguration via random access. UEs can modify cell-specific parameters before triggering random access. Base station equipment may exhibit changes in UE-specific parameters due to reconfiguration with or without random access. UEs can modify UE-specific parameters before or after random access.

[0242] The procedures performed by terminal device 1 include at least some or all of the following 5A to 5C: 5A is cell search; 5B is random access; and 5C is data communication.

[0243] Cell search is a procedure used by terminal device 1 to synchronize with cells in the time domain and / or frequency domain, and to detect physical cell identifiers. By performing a cell search, terminal device 1 can detect the physical cell ID by synchronizing with the cell in the time domain and / or frequency domain.

[0244] The PSS sequence is given based on at least the physical cell ID. The SSS sequence is given based on at least the physical cell ID.

[0245] SS / PBCH block candidates indicate resources where SS / PBCH block transmission may exist. SS / PBCH blocks can be transmitted on the resources indicated as SS / PBCH block candidates. Base station device 3 can transmit SS / PBCH blocks on SS / PBCH block candidates. Terminal device 1 can receive (detect) SS / PBCH blocks on SS / PBCH block candidates.

[0246] A set of SS / PBCH block candidates within a half-radio frame is also called an SS burst set. An SS burst set is also called a transmit window, SS transmit window, or DRS transmit window (Discovery Reference Signal transmission window). An SS burst set is a general term that includes at least a first SS burst set and a second SS burst set.

[0247] The base station device 3 transmits SS / PBCH blocks of one or more indices at predetermined intervals. The terminal device 1 can detect at least one SS / PBCH block from among the SS / PBCH blocks of one or more indices. The terminal device 1 can attempt to decode the PBCH contained in the SS / PBCH block.

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

[0249] Message 1 is the procedure for terminal device 1 to send a PRACH. Based on at least the index of the SS / PBCH block candidate detected based on the cell search, terminal device 1 sends a PRACH at one PRACH opportunity selected from one or more PRACH opportunities.

[0250] Message 2 describes the procedure by which terminal device 1 attempts to detect DCI format 1_0 using a Cyclic Redundancy Check (CRC) scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier). Terminal device 1 can attempt to detect DCI format 1_0 within the search space set.

[0251] Message 3 (Msg3) is a procedure for sending a PUSCH scheduled by a random access response grant contained in DCI format 1_0 detected in the Message 2 procedure. The random access response grant is indicated by the MAC CE contained in the PDSCH scheduled by DCI format 1_0.

[0252] A PUSCH scheduled based on a random access response grant is either message 3 PUSCH or PUSCH. Message 3 PUSCH includes a conflict resolution identifier MAC CE. The conflict resolution ID MAC CE includes a conflict resolution ID.

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

[0254] Message 4 is a procedure to attempt to detect DCI format 1_0 with a CRC scrambled by either C-RNTI (Cell-Radio Network Temporary Identifier) ​​or TC-RNTI. Terminal device 1 receives a PDSCH scheduled based on DCI format 1_0. The PDSCH may include a collision resolution ID.

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

[0256] In data communication, terminal device 1 attempts to detect (attempts to monitor, monitors PDCCH) a PDCCH within a resource identified based on at least one or all of the control resource set and the search space set. This is also referred to as "terminal device 1 attempts to detect a PDCCH in the control resource set," "terminal device 1 attempts to detect a PDCCH in the search space set," "terminal device 1 attempts to detect a candidate PDCCH in the search space set," "terminal device 1 attempts to detect a candidate PDCCH in the search space set," "terminal device 1 attempts to detect a DCI format in the control resource set," or "terminal device 1 attempts to detect a DCI format in the search space set." Monitoring a PDCCH may be equivalent to monitoring a DCI format within a PDCCH.

[0257] A control resource set is a set of resources consisting of a number of resource blocks and a predetermined number of OFDM symbols within each slot.

[0258] The set of resources for a control resource set may be indicated by a higher-level parameter. The number of OFDM symbols included in the control resource set may also be indicated by a higher-level parameter.

[0259] PDCCH can also be called PDCCH candidate.

[0260] A search space set is defined as a set of PDCCH candidates. A search space set can be a common search space (CSS) set or a UE-specific search space (USS) set.

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

[0262] A Type 0 PDCCH common search space set can be used as a common search space set having index 0.

[0263] A search space set is associated with (contained within, corresponding to) a control resource set. The index of the control resource set associated with the search space set may be indicated by a higher-level parameter.

[0264] For a search space set, some or all of 6A-6C may be indicated by at least higher-level parameters. 6A is the PDCCH monitoring period. 6B is the PDCCH monitoring pattern within the slot. 6C is the PDCCH monitoring offset.

[0265] A search space set monitoring opportunity may correspond to one or more OFDM symbols to which the first OFDM symbol of the control resource set associated with the search space set is assigned. A search space set monitoring opportunity may correspond to a resource identified by the first OFDM symbol of the control resource set associated with the search space set. A search space set monitoring opportunity is given based on at least some or all of the PDCCH monitoring periodicity, the PDCCH monitoring pattern within the slot, and the PDCCH monitoring offset.

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

[0267] In Figure 8, blocks indicated by grid lines represent search space set 91, blocks indicated by diagonal upper-right lines represent search space set 92, blocks indicated by diagonal upper-left lines represent search space set 93, and blocks indicated by horizontal lines represent search space set 94.

[0268] In Figure 8, the PDCCH monitoring periodicity of search space set 91 is set to 1 slot, the PDCCH monitoring offset of search space set 91 is set to 0 slot, and the PDCCH monitoring pattern of search space set 91 is [1,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunities of search space set 91 correspond to the 1st OFDM symbol (OFDM symbol #0) and the 8th OFDM symbol (OFDM symbol #7) in each slot.

[0269] In Figure 8, the PDCCH monitoring periodicity of search space set 92 is set to 2 slots, the PDCCH monitoring offset of search space set 92 is set to 0 slots, and the PDCCH monitoring pattern of search space set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunities of search space set 92 correspond to the leading OFDM symbol (OFDM symbol #0) in each of the even-numbered slots.

[0270] In Figure 8, the PDCCH monitoring periodicity of search space set 93 is set to 2 slots, the PDCCH monitoring offset of search space set 93 is set to 0 slots, and the PDCCH monitoring pattern of search space set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunities of search space set 93 correspond to the 8th OFDM symbol (OFDM symbol #8) in each of the even-numbered slots.

[0271] In Figure 8, the PDCCH monitoring periodicity of search space set 94 is set to 2 slots, the PDCCH monitoring offset of search space set 94 is set to 1 slot, and the PDCCH monitoring pattern of search space set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunities of search space set 94 correspond to the leading OFDM symbol (OFDM symbol #0) in each of the odd-numbered slots.

[0272] A Type 0 PDCCH common search space set can be used for DCI formats that have a cyclic redundancy check (CRC) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0273] A Type 0 PDCCH common search space set can be used for DCI formats having a cyclic redundancy check sequence scrambled by SI-RNTI.

[0274] A Type 1 PDCCH common search space set can be used for DCI formats having a CRC sequence scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​or a CRC sequence scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0275] The Type 2 PDCCH common search space set can be used for DCI formats that have a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

[0276] The Type 3 PDCCH common search space set can be used for DCI formats that have a CRC sequence scrambled by C-RNTI (Cell-Radio Network Temporary Identifier).

[0277] A UE-specific search space set may be used for DCI formats that have a CRC sequence scrambled by at least C-RNTI.

[0278] In downlink communication, terminal device 1 can detect the downlink DCI format. The detected downlink DCI format is used for at least PDSCH resource allocation. The detected downlink DCI format is also referred to as the downlink allocation. Terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resources indicated based on the detected downlink DCI format, the HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block contained in the PDSCH) may be reported to base station device 3.

[0279] In uplink communication, terminal device 1 can detect the uplink DCI format. The detected uplink DCI format is used at least for resource allocation in PUSCH. The detected uplink DCI format is also called the uplink grant. Terminal device 1 transmits PUSCH.

[0280] PUSCH transmissions (one or more) can be dynamically scheduled by UL grants within the DCI, or transmissions can correspond to configured grant types 1 or 2. PUSCH transmissions for configured grant type 1 are quasi-statically configured to operate upon receipt of higher-level parameters in configdGrantConfig, including rrc-ConfiguredUplinkGrant, without the detection of UL grants in the DCI. PUSCH transmissions for configured grant type 2 are semi-permanently scheduled by UL grants within a valid activated DCI according to their procedures (one or more) after receiving higher-level parameters configuredGrantConfig that do not include rrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList is configured, two or more configured grant configurations for configured grant type 1 and / or configured grant type 2 may be simultaneously active on the serving cell's active BWP.

[0281] Further details of resource allocation in the time domain of PUSCH scheduled by DCI format are described. When a UE (Terminal Device 1) is scheduled to send transport blocks but not CSI reports, or when a UE is scheduled by DCI to send transport blocks and CSI reports (one or more) on PUSCH, the DCI's "Time Domain Resource Allocation" field value m can provide row index m+1 to the allocated table. The determination of the resource allocation table to be used may be predefined and / or defined in the RRC configuration. The indexed row of the resource allocation table can define the slot set K2, the start and length indicator SLIV, or directly, the start symbol S and allocation length L to be applied to the PUSCH transmission, the PUSCH mapping type, and the number of repetitions (if the RRC parameter numberOfRepetitions exists in the resource allocation table). Note that RRC parameters are a kind of higher-level parameter.

[0282] For a PUSCH scheduled by DCI format 0_1, if the RRC parameter push-RepTypeIndicatorDCI-0-1 is set to "pUSCH-RepTypeB", the UE can apply the PUSCH repetition type B procedure when determining time-domain resource allocation. For a PUSCH scheduled by DCI format 0_2, if the RRC parameter push-RepTypeIndicatorDCI-0-2 is set to "pUSCH-RepTypeB", the UE can apply the PUSCH repetition type B procedure when determining time-domain resource allocation. Otherwise, the UE can apply the PUSCH repetition type A procedure when determining time-domain resource allocation for a PUSCH scheduled by PDCCH.

[0283] For a PUSCH repeat type A, the starting symbol S for the start of the slot, and the number of consecutive symbols L counted from the symbol S assigned to PUSCH, can be determined from the indexed row start and length indicator SLIV. If (L-1) ≤ 7, then SLIV = 14(L-1) + S; otherwise, SLIV = 14(14-L+1+(14-1-S), where 0 <L≦14-S。

[0284] When sending a PUSCH scheduled in DCI format 0_1 ​​or 0_2 with a PDCCH having a scrambled CRC of C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1 for PUSCH repetition type A, the number of repetitions K may be determined as follows: If the RRC parameter numberOfRepetitions exists in the resource allocation table, the number of repetitions K may be equal to numberOfRepetitions, else, if the UE is configured with the RRC parameter push-AggregationFactor, the number of repetitions K may be equal to push-AggregationFactor, otherwise K=1.

[0285] If the UE lacks the functionality of a specific coverage extension feature(single or multiple) (e.g., available slot-based PUSCH repetition count), or if the UE does not have a specific coverage extension configuration(single or multiple) (e.g., available slot-based PUSCH repetition count), the following may apply: For PUSCH repetition type A, in case K>1, the same symbol assignment may be applied across K consecutive slots, and the PUSCH may be limited to a single transmit layer. The UE can repeat a TB across K consecutive slots, applying the same symbol assignment to each slot. A redundant version (n=0, 1, ...K-1) applied to the nth transmit opportunity of a TB may be determined as described below. For PUSCH repetition type A, PUSCH transmits within slots of a multi-slot PUSCH transmit may be omitted according to at least and / or many conditions of the PUSCH priority-based procedure, slot configuration-based procedure, slot format-based procedure, and cancellation instruction-based procedure. For example, a slot can be determined to be available if it is available according to all the conditions defined in these procedures, and / or the slot can be determined to be unavailable if it is unavailable according to at least one of the conditions defined in those procedures. K can be an integer.

[0286] The following may apply if the UE has a specific coverage extension feature(single or multiple) and / or a specific coverage extension configuration(single or multiple): For PUSCH repeat type A, if K>1, the same symbol assignment can be applied across K available slots (i.e., the first K slots available for PUSCH transmission), and the PUSCH may be limited to a single transmission layer. The UE can repeat a TB across K consecutive slots, each applying the same symbol assignment. The K available slots may be determined according to the conditions of at least and / or more of the PUSCH priority-based procedure, slot configuration-based procedure, slot format-based procedure, and cancellation instruction-based procedure. For example, a slot can be determined to be available if it is available according to all the conditions defined in these procedures, and / or a slot can be determined to be unavailable if it is not available according to at least one of the conditions defined in those procedures.

[0287] The following may apply if the UE has the functionality of a certain coverage extension feature(single or multiple) and / or if the UE has a certain coverage extension configuration(single or multiple): For PUSCH repeat type A, if K>1, the same symbol assignment can be applied across K available slots (i.e., the first K slots available for PUSCH transmission), and PUSCH may be limited to a single transmission layer. The UE can repeat TB across K available slots, each with the same symbol assignment applied to it. The K available slots may be determined according to at least and / or conditions in the first RRC parameter. The first RRC parameter may be one or more of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, numberOfRepetitions, BandCombination-UplinkTxSwitch, repK, repK-RV,pusch-AggregationFactor, nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot, timeDomainAllocation,numberOfInvalidSymbolsForDL-UL-Switching, invalidSymbolPattern, and periodicityAndPattern. For PUSCH repetition type A, PUSCH transmissions within slots of multi-slot PUSCH transmissions are omitted according to at least and / or more conditions in the second RRC parameter.The second RRC parameter may be one or more of the following: tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, numberOfRepetitions, BandCombination-UplinkTxSwitch, repK, repK-RV, push-AggregationFactor, nrofSlots, configuredGrantConfig, cg-nrofSlots, cg-nrofPUSCH-InSlot, timeDomainAllocation, numberOfInvalidSymbolsForDL-UL-Switching, invalidSymbolPattern, and periodicityAndPattern.

[0288] `configuredGrantConfig` can refer to `ConfiguredGrantConfig`.

[0289] `configuredGrantConfig` can refer to `ConfiguredGrantConfig`.

[0290] If the PUSCH resource allocation is quasi-statically configured by the higher-level parameter configuredGrantConfig within the BWP-UplinkDedicated information element, and the PUSCH transmission corresponds to a configured grant, the following higher-level parameters will be applied to the transmission.

[0291] For Type 1 PUSCH transmissions with a configured grant, the following parameters are provided in configuredGrantConfig unless otherwise specified. Additionally, for determining the PUSCH repetition type, if the upper-level parameter push-RepTypeIndicator in rrc-ConfiguredUplinkGrant is configured and set to "pusch-RepTypeB", then PUSCH repetition type B is applied. Otherwise, PUSCH repetition type A is applied.

[0292] The upper-level parameter push-RepTypelndicator indicates whether the UE follows the behavior of PUSCH repeat type A or PUSCH repeat type B for each type 1 configured grant configuration. The value push-RepTypeA enables "PUSCH repeat type A", and the value push-RepTypeB enables "PUSCH repeat type B". The value push-RepTypeB cannot be configured simultaneously with cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16.

[0293] For PUSCH iteration type A, the selection of the time domain resource allocation table follows the rules of DCI format 0_0 for the UE-specific search space.

[0294] For PUSCH repetition type A, the selection of the time domain resource allocation table is as follows: If push-RepTypeIndicatorDCI-0-1 in push-Config is configured and set to "pusch-RepTypeA", then push-TimeDomainResourceAllocationListDCI-0-1 in push-Config is used. Otherwise, push-TimeDomainResourceAllocationListDCI-0-2 in push-Config is used. If neither push-RepTypeIndicatorDCI-0-1 nor push-RepTypeIndicatorDCI-0-2 in push-Config is set to "pusch-RepTypeA", then push-RepTypeIndicator in rrc-ConfiguredUplinkGrant is not expected to be configured to "pusch-RepTypeA".

[0295] For PUSCH repetition type B, the selection of the time domain resource allocation table is as follows: If push-RepTypeIndicatorDCI-0-1 in push-Config is configured and set to "pusch-RepTypeB", then push-TimeDomainResourceAllocationListDCI-0-1 in push-Config is used. Otherwise, push-TimeDomainResourceAllocationListDCI-0-2 in push-Config is used. If neither push-RepTypeIndicatorDCI-0-1 nor push-RepTypeIndicatorDCI-0-2 in push-Config is set to "pusch-RepTypeB", then push-RepTypeIndicator in rrc-ConfiguredUplinkGrant is not expected to be configured to "pusch-RepTypeB".

[0296] Further details of resource allocation in the time domain for PUSCH with configured grants are described below. For PUSCH transmissions with type 1 or type 2 configured grants, the (nominal) number of repetitions K applicable to the transmitted transport block may be provided by an indexed row in the time domain resource allocation table if numberOfReperitions exists in the table. Otherwise, K may be provided by the upper-tier configured parameter repK. The UE may not be allowed to transmit what is a resource configured by the RRC parameter configuredGrantConfig if the upper tier did not deliver the transport block to be transmitted with resources allocated to the uplink transmission without a grant.

[0297] The permitted set of periodicities P is defined in the RRC configuration. The RRC parameter cg-nrofSlots can provide the number of consecutive slots allocated within a configured grant period. The RRC parameter cg-nrofPUSCH-InSlot can provide the number of consecutive PUSCH allocations within a slot (where the first PUSCH allocation may follow the RRC parameter timeDomainAllocation for upper-layer configurations following a type 1 PUSCH transmission or MAC procedure, as well as a UL grant received in DCI for a type 2 PUSCH transmission, and the remaining PUSCH allocations may have the same length and PUSCH mapping type), and may be added following previous allocations without gaps. The same combination of start symbol, length, and PUSCH mapping type may be repeated across consecutively allocated slots.

[0298] The UE cannot be expected to consist of a transmission period of K repetitions that is longer than the period derived by the periodicity P. The UE may not transmit a PUSCH during a transmission opportunity if it determines that the number of symbols available for a PUSCH transmission in the slot is less than the transmission duration L.

[0299] The procedure applies to PUSCH transmissions of type A PUSCH repetitions with type 1 or type 2 configured grants. The RRC parameter repK-RV defines the redundant version pattern applied to the repetition. If cg-RetransmissionTimer is provided, the redundant version for uplink transmissions with configured grants is determined by the UE. If the parameter repK-RV is not provided in configuredGrantConfig and cg-RetransmissionTimer is not provided, the redundant version for uplink transmissions with configured grants may need to be set to 0. If the parameter repK-RV is not provided in configuredGrantConfig and cg-RetransmissionTimer is not provided, for the nth transmission opportunity (n=1, 2, ..., K) during K repetitions, it is associated with the (mod(n-1,4)1)th value in the configured RV sequence. If the configured grant configuration is configured with startingFromRV0 set to "off", the initial transmission of the transport block can only be initiated on the first transmission opportunity of K repetitions. Otherwise, the initial transmission of the transport block may start with the first transmission opportunity out of K repetitions if the configured RV sequence is {0,2,3,1}, with any of the K repetitions of transmission opportunities associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or with any of the K repetitions of transmission opportunities if the configured RV sequence is {0,0,0,0}, except for the last transmission opportunity if K≧8.

[0300] If the configured grant configuration is not configured with startingFromRV0 set to "off", and if an available slot-based count is configured, the initial transmission of the transport block may be initiated on the first transmission opportunity of K repetitions.

[0301] If the configured grant configuration is not set to "off" and a slot-based count of available slots is configured, the initial transmit of the transport block may start with the first transmit opportunity of K repetitions if the configured RV sequence is {0,2,3,1}, any of the K repetitions of transmit opportunities associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or any of the K repetitions of transmit opportunities if the configured RV sequence is {0,0,0,0}, except for the last transmit opportunity if K≧8.

[0302] If the configured grant configuration is not set to "off" and a slot-based count of available slots is configured, the initial transmit of the transport block may start with the first transmit opportunity of K repetitions if the configured RV sequence is {0,2,3,1}, any of the K repetitions of transmit opportunities associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or any of the K repetitions of transmit opportunities if the configured RV sequence is {0,0,0,0}, except for the last transmit opportunity if K≧8.

[0303] If the configured grant configuration is not set to "off" and the available slot-based count is not configured, the initial transmit of the transport block may start with any of the K transmit opportunities associated with RV=0, assuming that if the configured RV sequence is {0,2,3,1}, the first transmit opportunity out of K repetitions is determined based on consecutive physical slots, excluding the last transmit opportunity if K≧8, and / or if the configured RV sequence is {0,0,0,0}.

[0304] For any RV sequence, a repetition may need to terminate after sending K repetitions, or at the last transmission opportunity among the K repetitions within a period P, or after reaching the start symbol of a repetition that overlaps with a PUSCH having the same HARQ process scheduled by DCI format 0_0, 0_1, or 0_2, whichever comes first. Furthermore, if a UE is provided with DCI format 0_1 ​​with the DFI flag set to "1", and within this DCI the UE detects an ACK for the HARQ process corresponding to its transport block, the UE may need to terminate the repetition of the transport block in a PUSCH transmission.

[0305] The UE is not expected to consist of a transmission period of K repetitions that is longer than the period derived by the periodicity P. The UE will not transmit a PUSCH in a transmission opportunity if it determines that the number of symbols available for a PUSCH transmission in the slot is less than the transmission duration L.

[0306] For unpaired spectra, if the RRC parameter AvailableSlotCounting is enabled, the UE will perform N PUSCH transmissions of type A based on the RRC parameters tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst. * Determine the K slot. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot is provided, and if it overlaps with the DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or with the symbol of the SS / PBCH block having an index provided by ssb-PositionsInBurst, the slot is N for PUSCH transmission of PUSCH repeat type A.* The number of K slots is not counted. Otherwise, the UE will have N PUSCH transmissions of type A. * Determine K consecutive slots. In the case of reduced capacity half-duplex UE, if AvailableSlotCounting is enabled, if at least one of the symbols indicated in the indexed row of the used resource allocation table in the slot overlaps with a symbol in the SS / PBCH block having an index provided by ssb-PosionsInBurst, the slot is N for PUSCH transmission of PUSCH repetition type A. * It is not counted in the number of K slots.

[0307] For paired spectra and SUL bands, UE is N for PUSCH transmission of PUSCH repetition type A, regardless of whether AvailableSlotCounting is enabled or not. * Determine K consecutive slots. In the case of reduced capability half-duplex UE, if AvailableSlotCounting is enabled, if at least one of the symbols indicated by the indexed row in the used resource allocation table within the slot overlaps with a symbol in the SS / PBCH block having an index provided by ssb-Positionslnburst, then the slot is N for PUSCH transmission of PUSCH repeat type A. * It is not counted in the number of K slots.

[0308] For both Type 1 and Type 2 PUSCH transmissions with configured grants, for ampered spectra, if K > 1, and if the RRC parameter AvailableSlotCount is enabled, the UE determines N for PUSCH transmissions that apply the same symbol assignment within each slot. *It may be necessary to repeat TB across K slots. Otherwise, the UE applies the same symbol assignment to each slot unless the UE is provided with the higher-level parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat the TB across K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity candidate for repK within the same configuration.

[0309] For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE applies the same symbol assignment to each slot, regardless of whether AvailableSlotCount is enabled or not, unless the UE provides the higher-level parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat the TB over K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity of repK within the same configuration. A Type 1 or Type 2 PUSCH transmission with a configured grant in a slot is omitted according to the conditions in the UE procedure(s) for reporting control information, the UE procedure(s) for determining the slot configuration(s), and the UE procedure(s) associated with the cancellation instruction.

[0310] If no available slot-based count is configured (or in the case of paired spectrum), for both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE applies the same symbol assignment to each slot unless the UE is provided with the upper layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat the TB across K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity candidate of RepK within the same configuration.

[0311] If an available slot-based count is configured (for ampered spectrum), for both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may need to repeat the TB across the first K available slots, applying the same symbol assignment to each slot, in which case each available slot is either a UL symbol as described in the UE procedure(s) for determining the slot configuration(s), or a flexible symbol (i.e., SS / P for PUSCH) as described in the UE procedure(s) for determining the slot configuration(s). A slot having consecutive UL symbols (i.e., not BCH block symbols) and / or flexible symbols (i.e., starting from the first symbol and not more than the number of SS / PBCH block symbols for PUSCH) as described in the UE procedure(s) for determining the slot configuration(s), unless the UE is provided with the upper-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in this case the UE repeats the TB with the earliest consecutive transmission opportunity candidate for RepK in the same configuration. A type 1 or type 2 PUSCH transmission with a configured grant in the slot is omitted according to the conditions in the UE procedure(s) for reporting control information, the UE procedure(s) for determining the slot configuration(s), and the UE procedure(s) associated with the cancellation instruction. The SS / PBCH block symbol is the symbol for an SS / PBCH block that has a candidate SS / PBCH block index corresponding to the SS / PBCH block index shown to the UE by ssb-Positionslnburst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, as described in the UE synchronization procedure for searching for cells.

[0312] If no available slot-based count is configured (or in the case of paired spectrum), for both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE applies the same symbol assignment to each slot unless the UE is provided with the upper layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat the TB across K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity candidate of RepK within the same configuration.

[0313] If an available slot-based count is configured (for ampered spectrum), for both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may need to repeat the TB across the initial slot and the subsequent K-1 available slots, in which case the initial slot is a slot with symbols specified in the uplink transmission procedure(single or multiple) without dynamic grants by the MAC entity, and each of the available slots has UL symbols, or UE procedure(single or multiple) for determining slot configuration(single or multiple) A slot having flexible symbols (i.e., not SS / PBCH block symbols for PUSCH) as described in the single or multiple UE procedures for determining the slot configuration (single or multiple), and consecutive UL symbols as described in the single or multiple UE procedures for determining the slot configuration (single or multiple), or flexible symbols (i.e., starting from the first symbol and not more than the number of SS / PBCH block symbols for PUSCH) as described in the single or multiple UE procedures for determining the slot configuration (single or multiple), unless the UE is provided with the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in this case the UE repeats the TB with the earliest consecutive transmission opportunity candidate for RepK in the same configuration. A Type 1 or Type 2 PUSCH transmission with a configured grant in the slot is omitted according to the conditions in the single or multiple UE procedures for reporting control information, the single or multiple UE procedures for determining the slot configuration (single or multiple), and the UE procedures associated with the cancellation instruction.The SS / PBCH block symbol is the symbol for an SS / PBCH block that has a candidate SS / PBCH block index corresponding to the SS / PBCH block index shown to the UE by ssb-Positionslnburst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, as described in the UE synchronization procedure for searching for cells.

[0314] The MAC entity may be included in the media access control layer processing unit 15.

[0315] UE may not anticipate that the initial slot will be unavailable.

[0316] If no available slot-based counts are configured, or in the case of paired spectra, for both Type 1 and Type 2 PUSCH transmissions with configured grants, K > 1, unless the UE is provided with the upper layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, the UE applies the same symbol assignment to each slot. * It may be necessary to repeat the TB across K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity candidate of RepK within the same configuration.

[0317] If an available slot-based count is configured and is for ampered spectrum, then for both type 1 and type 2 PUSCH transmits with configured grants, if K > 1, the UE may need to repeat TB over K available slots, in which case each available slot is a slot having UL symbols as described in these procedures, or flexible symbols (i.e., not SS / PBCH block symbols for PUSCH) as per the conditions of these procedures, and / or consecutive UL symbols as per the conditions of these procedures, or flexible symbols (i.e., starting from the first symbol and not more than or equal to the number of symbols for PUSCH), and unless the UE is provided with the upper layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in this case the UE repeats TB at the earliest consecutive transmit opportunity candidate of RepK within the same configuration.

[0318] Type 1 or Type 2 PUSCH transmissions with configured grants in a slot are omitted in accordance with the conditions of these procedures. The SS / PBCH block symbol is the symbol of an SS / PBCH block having a candidate SS / PBCH block index corresponding to the SS / PBCH block index shown to the UE by the ssb-Positionslnburst in SIB1 or the ssb-PositionslnBurst in ServingCellConfigCommon, in accordance with the conditions of these procedures.

[0319] For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may need to repeat the TB over K consecutive slots, applying the same symbol assignment to each slot, unless the UE is provided with the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats the TB at the earliest consecutive transmission opportunity of repK within the same configuration. Type 1 or Type 2 PUSCH transmissions with configured grants in a slot are omitted according to the conditions of one or more RRC configurations.

[0320] The procedure applies to PUSCH transmissions of PUSCH repetition type B using a type 1 or type 2 configured grant. For PUSCH transmissions with a type 1 or type 2 configured grant, the nominal and actual repetitions are determined according to the PUSCH repetition type B procedure, according to at least one of those defined in these procedures. The upper-layer configuration parameter repK-RV defines the redundant version pattern applied to the repetitions. If the parameter repK-RV is not provided to configuredGrantConfig, the redundant version for each actual repetition with the configured grant may need to be set to 0. Otherwise, for the nth transmission opportunity of all actual repetitions (including omitted actual repetitions) of the K nominal repetitions, it is associated with the (mod(n-1,4)+1)th value in the configured RV sequence. If the configured grant configuration is set to "off" with startingFromRV0, the initial transmission of the transport block can only be initiated on the first transmission opportunity of the actual repetitions. Otherwise, the initial transmission of the transport block may, if K≧8, begin on the first transmission opportunity of an actual repeat if the configured RV sequence is {0,2,3,1}, except for the actual repeat in the last nominal repeat; if the configured RV sequence is {0,3,0,3}, begin on any transmission opportunity of an actual repeat associated with RV=0; and / or if the configured RV sequence is {0,0,0,0}, begin on any transmission opportunity of an actual repeat.

[0321] For any RV sequence, a repetition may need to end after sending K nominal repetitions, or at the last transmission opportunity between K nominal repetitions within period P, or after reaching the earlier of the start symbol of a repetition that overlaps with a PUSCH having the same HARQ process scheduled by DCI format 0_0, 0_1, or 0_2. The UE is not expected to consist of a period of transmissions of K nominal repetitions longer than the period derived by periodicity P.

[0322] For PUSCH repetition type A (as determined by following the procedures specified in these procedures for scheduled PUSCH or procedures for configured PUSCH), the UE is configured for frequency hopping by the RRC parameter frequencyHoppingDCI-0-1 in push-Config for PUSCH transmissions scheduled by DCI format 0_1 ​​(e.g., frequencyHoppingDCI-0-1-r16 and / or frequencyHoppingDCI-0-1-r17), by frequencyHoppingDCI-0-2 in push-Config for PUSCH transmissions scheduled by DCI format 0_2, by frequencyHopping provided to push-Config for PUSCH transmissions scheduled by DCI formats other than 0_2, by frequencyHopping provided to configuredGrantConfig for configured PUSCH transmissions, and by frequencyHoppingPUSCH-RepTypeA provided to rrc-ConfiguredUplinkGrant for type 1 configured PUSCH transmissions. One of two frequency hopping modes can be configured: intra-slot frequency hopping applicable to single-slot and multi-slot push transmits, and inter-slot frequency hopping applicable to multi-slot push transmits. Another frequency hopping mode can be configured: inter-repetition frequency hopping applicable to multi-slot push transmits.

[0323] push-Config may be referred to as PUSCH-Config.

[0324] pusch-Config may be referred to as PUSCH-Config.

[0325] The RRC parameter frequency hopping indicates that a value of intraSlot enables "intra-slot frequency hopping" and a value of interSlot enables "inter-slot frequency hopping". If the field is not present, frequency hopping is not configured for "pusch-RepTypeA". The field frequencyHopping applies to DCI formats 0_0 and 0_1 for "pusch-RepTypeA".

[0326] The RRC parameter frequencyHoppingDCI-0-1-r16 indicates the frequency hopping scheme for DCI format 0_1 ​​when push-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeB". The value interRepetition enables "inter-repetition frequency hopping", and the value interSlot enables "inter-slot frequency hopping". If the field is not present, frequency hopping is not configured for DCI format 0_1.

[0327] The RRC parameter frequencyHoppingDCI-0-1-r17 indicates the frequency hopping scheme for DCI format 0_1 ​​when push-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeA" or "pusch-RepTypeB" with "inter-repetition frequency hopping". The value interRepetition enables "inter-repetition frequency hopping", the value interSlot enables "inter-slot frequency hopping", and the value intraSlot enables "intra-slot frequency hopping". If the field does not exist, inter-repetition frequency hopping is not configured for DCI format 0_1 ​​with "pusch-RepTypeA", and frequency hopping is not configured for DCI format 0_1 ​​with "pusch-RepTypeB". Alternatively, the RRC parameter frequencyHoppingDCI-0-1-r17 may indicate a frequency hopping scheme in DCI format 0_1 ​​if push-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeA", which enables "frequency hopping between repetitions".

[0328] For resource allocation type 2, the UE sends a PUSCH without frequency hopping.

[0329] For resource allocation type 1, regardless of whether conversion precoding is enabled for PUSCH transmissions, the UE may perform PUSCH frequency hopping if the frequency hopping field in the corresponding detected DCI format or random access response UL grant is set to 1, or, in the case of type 1 PUSCH transmissions with a configured grant, if the RRC parameter frequencyHoppingOffset is provided; otherwise, PUSCH frequency hopping will not occur. Once frequency hopping is enabled for PUSCH, the RE mapping is defined in these steps.

[0330] For PUSCH scheduled by DCI format 0_0 with a RAR UL grant, fallbackRAR UL grant, or CRC scrambled by TC-RNTI, the frequency offset is obtained as described in these procedures. For PUSCH scheduled by DCI format 0_0 / 0_1, or for PUSCH for resource allocation type 1 based on a configured type 2 UL grant activated by DCI format 0_0 / 0_1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in push-Config. For PUSCH scheduled by DCI format 0_2, or for PUSCH activated by DCI format 0_2 and based on a configured type 2 UL grant for resource allocation type 1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in push-Config. If the size of the active BWP is less than 50PRB, one of the two upper-layer configuration offsets is indicated to the UL grant. If the size of the active BWP is 50PRB or larger, one of the four upper-layer configuration offsets is indicated in the UL grant.

[0331] For PUSCH based on a Type 1 configured UL grant, the frequency offset is provided by the RRC parameter frequencyHoppingOffset within rrc-ConfiguredUplinkGrant.

[0332] For PUSCH repetition type B (as determined by following the procedures specified in these procedures for scheduled PUSCH or procedures for configured PUSCH), the UE is configured for frequency hopping by the RRC parameter frequencyHoppingDCI-0-2 in push-Config for PUSCH transmissions scheduled by DCI format 0_2, by frequencyHoppingDCI-0-1 provided in push-Config for PUSCH transmissions scheduled by DCI format 0_1, and by frequencyHoppingPUSCH-RepTypeB provided in rrc-ConfiguredUplinkGrant for type 1 configured PUSCH transmissions. The frequency hopping mode for type 2 configured PUSCH transmissions follows the configuration of the activated DCI format. One of two frequency hopping modes (inter-repetition frequency hopping and inter-slot frequency hopping) can be configured.

[0333] For resource allocation type 1, regardless of whether conversion precoding is enabled for PUSCH transmissions, the UE may perform PUSCH frequency hopping if the frequency hopping field in the corresponding detected DCI format is set to 1, or if the RRC parameter frequencyHoppingPUSCH-RepTypeB is provided for type 1 PUSCH transmissions with configured grants; otherwise, PUSCH frequency hopping will not be performed. If frequency hopping is enabled for PUSCH, the RE mapping is defined in these steps.

[0334] For PUSCH scheduled by DCI format 0_1, or PUSCH for resource allocation type 1 based on a configured UL grant of type 2 activated by DCI format 0_1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in push-Config. For PUSCH scheduled by DCI format 0_2, or PUSCH activated by DCI format 0_2 and based on a configured UL grant of type 2 for resource allocation type 1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in push-Config. If the size of the active BWP is less than 50PRB, one of the two upper-layer configuration offsets is indicated in the UL grant. If the size of the active BWP is 50PRB or more, one of the four upper-layer configuration offsets is indicated in the UL grant.

[0335] For PUSCH based on a Type 1 configured UL grant, the frequency offset is provided by the RRC parameter frequencyHoppingOffset within rrc-ConfiguredUplinkGrant.

[0336] In the case of inter-slot frequency hopping, the start RB between slots nAu_s is followed by inter-slot frequency hopping of PUSCH receive type A according to at least one of the conditions defined in those procedures.

[0337] If the UE does not have the capability of a specific coverage extension feature(single or multiple) (e.g., available slot-based PUSCH repetition count), or if the UE does not have a specific coverage extension configuration(single or multiple) (e.g., available slot-based PUSCH repetition count), then the following may apply (i.e., the number of repetitions counted based on consecutive (or contiguous or consecutive) slots). Alternatively or additionally, if the UE has the capability of a specific coverage extension(single or multiple), and the UE has a slot count type configuration (RRC configuration or RRC parameter indicating whether the repetition count is counted based on consecutive (or consecutive) slots or based on available slots) indicating PUSCH repetitions counted based on consecutive slots, then the following may apply. For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may repeat the TB over K consecutive slots, applying the same symbol assignment to each slot unless the UE has provided the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE may repeat the TB at the earliest consecutive transmission opportunity for repK within the same configuration. A Type 1 or Type 2 PUSCH transmission with configured grants in a slot may be omitted according to conditions in at least and / or more of the PUSCH priority-based procedure, slot configuration-based procedure, slot format-based procedure, and cancellation-based procedure. For example, a slot may be determined to be available if it is available according to all the conditions defined in these procedures, and / or a slot may be determined to be unavailable if it is unavailable according to at least one of the conditions defined in those procedures.

[0338] It should be noted that the aforementioned slot count type configurations may be referred to by different names. The presence of a slot count type configuration in an RRC configuration message may mean that the number of repetitions is counted based on available slots, while the absence of a slot count type configuration in an RRC configuration message may mean that the number of repetitions is counted based on consecutive slots. Additionally and / or alternatively, a slot count type configuration set to a first value (e.g., consecutive) may mean that the number of repetitions is counted based on consecutive slots, while a slot count type configuration set to a second value (e.g., "available") may mean that the number of repetitions is counted based on available slots.

[0339] If the UE has the functionality of a specific coverage extension feature(single or multiple), and / or if the UE has a specific coverage extension configuration(single or multiple), the following (i.e., the number of repetitions counted based on available slots) may apply. Alternatively or additionally, if the UE has the functionality of a specific coverage extension feature(single or multiple), and the UE has a slot count type configuration indicating the PUSCH repetitions to be counted based on available slots, the following may apply. For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE can repeat the TB across K available slots (i.e., the first K slots available for the PUSCH transmission) applying the same symbol assignment to each slot. The K available slots may be determined according to the conditions of at least and / or more of the PUSCH priority-based procedure, slot configuration-based procedure, slot format-based procedure, and cancellation instruction-based procedure. For example, a slot can be determined to be available if it is available in accordance with all the conditions defined in these procedures, and / or a slot can be determined to be unavailable if it is unavailable in accordance with at least one of the conditions defined in those procedures.

[0340] The pattern of inter-slot frequency hopping based on available slots can be determined based on the omission of push transmissions.

[0341] The RV pattern based on available slots may be determined based on the omission of PUSCH transmission.

[0342] The pattern of slot counting based on available slots may be determined based on the omission of PUSCH transmissions.

[0343] This describes the priority-based procedure for PUSCH. Unless otherwise specified, PUSCH will be sent if it is scheduled by DCI or a PUSCH with a Confided Grant.

[0344] If present, a PUSCH or PUCCH transmission including repetitions may have a priority index of 0 or 1. For a configured grant PUSCH transmission, the UE can determine the priority index from the RRC parameter phy-Prioritylndex, if provided. For a PUCCH transmission with HARQ-ACK information corresponding to an SPS PDSCH reception or SPS PDSCH release, the UE can determine the priority index from the RRC parameter harq-CodebookID, if provided. For a PUCCH transmission with an SR, the UE can determine the corresponding priority from the RRC parameter phy-Prioritylndex in the RRC parameter SchedulingRequestResourceConfig, if present. For a PUSCH transmission with a semi-persistent CSI report, the UE can determine the priority index from the priority indicator field in the DCI format that activates the semi-persistent CSI report, if provided. If no priority index is provided to the UE for a PUSCH or PUCCH transmission, the priority index may be 0.

[0345] In an active DL BWP, if the UE can monitor PDCCH for the detection of either DCI format 0_1 ​​and DCI format 1_1, or DCI format 0_2 and DCI format 1_2, the priority index may be provided by the priority indicator field. If the UE demonstrates the ability to monitor PDCCH for the detection of DCI format 0_1 ​​and DCI format 1_1 and DCI format 0_2 and DCI format 1_2 in an active DL BWP, DCI format 0_1 ​​and DCI format 0_2 can schedule PUSCH transmissions of any priority, DCI format 1_1 or DCI format 1_2 can schedule PDSCH receptions, and can trigger PUCCH transmissions with corresponding HARQ-ACK information of any priority.

[0346] If a UE determines that there are duplicates of PUCCH and / or PUSCH transmissions with different priority indices, including repetitions, the UE can first resolve the duplicates of PUCCH and / or PUSCH transmissions with lower priority indices. Then, if a first PUCCH transmission with a higher priority index, scheduled by the DCI format in a PDCCH reception, temporally overlaps with a second PUSCH, or a repeat of a second PUCCH transmission with a lower priority index, the UE can cancel the second PUSCH or the repeat of the second PUCCH transmission before the first symbol that would overlap with the first PUCCH transmission. Similarly, if a first PUSCH transmission with a higher priority index, scheduled by the DCI format in a PDCCH reception, temporally overlaps with a repeat of a second PUCCH transmission with a lower priority index, the UE can cancel the repeat of the second PUCCH transmission before the first symbol that would overlap with the first PUSCH transmission. Overlaps, if any, may be applicable before or after resolving overlaps between channels of higher priority indices. The UE may assume that the transmission of the first PUCCH or first PUSCH does not begin after the last symbol of the corresponding PDCCH reception, but before T_(proc,2)+d_1. T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capacity assumed by d_2,1=0 based on p and N_2, where d_1 is determined by the reported UE capacity.

[0347] If the slot count type configuration indicates that the number of repetitions is counted based on consecutive slots, the above processing time requirement may apply that the first PUSCH does not start before T_(proc,2)+d_1 after the last symbol of the corresponding PDCCH reception. If the slot count type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement may be relaxed. For example, the processing time requirement may apply that the first PUSCH does not start before T_(proc,2)+d_1+d_x after the last symbol of the corresponding PDCCH reception, in which case d_x is a positive value. d_x can be expressed in units of symbols. In other words, if the number of repetitions of PUSCH repetition type A is counted based on consecutive slots, the processing time requirement may apply that the first PUSCH does not start before T_(proc,2)+d_1 after the last symbol of the corresponding PDCCH reception. If the number of repetitions of PUSCH repetition type A is counted based on available slots, the processing time requirement may be relaxed. Relaxing the processing time requirement may mean allowing a longer gap duration between the start of a PUSCH and the end of the corresponding PDCCH, in which case the processing time requirement may be the maximum processing time required to cancel a scheduled / configured / granted PUSCH transmission.

[0348] If a UE is scheduled by DCI format in the first PDCCH reception to send a first PUCCH with a higher priority index that overlaps with a second PUCCH or second PUSCH transmission with a lower priority index that is scheduled by DCI format in the second PDCCH, then T_(proc,2) can be based on the value of μ corresponding to the smallest SCS configuration among the first PDCCH, second PDCCH, first PUCCH, or first PUSCH, and the second PUCCH or second PUSCH. If the overlapping group includes the first PUCCH, and the RRC parameter processingType2Enabled of the RRC parameter PDSCH-ServingCellConfig is set to enable the serving cell in which the UE receives the first PDCCH and all serving cells in which the UE receives the PDSCH corresponding to the second PUCCH, then N_2 is 5 when μ=0, 5.5 when μ=1, and 11 when μ=2. Also, if the RRC parameter processingType2Enabled of the RRC parameter PUSCH-ServingCellConfig is set to enable the saving cell using the second PUSCH, then N_2 is 10 when μ=0, 12 when μ=1, 23 when μ=2, and 36 when μ=3. If the overlapping group includes the first PUSCH, and processingType2Enabled in PUSCH-ServingCellConfig is set to enable serving cells using the first and second PUSCH, then N_2 is 5 when μ=0, 5.5 when μ=1, and 11 when μ=2. Also, if processingType2Enabled in PDSCH-ServingCellConfig is set to enable for all serving cells where the UE receives a PDSCH corresponding to the second PUSCH, then N_2 is 10 when μ=0, 12 when μ=1, 23 when μ=2, and 36 when μ=3.

[0349] UE has, if any, a first PUCCH with a higher priority index and a second PUCCH or PUSCH with a lower priority index using SR, or a configured grant PUSCH with a higher priority index and a lower priority PUCCH, or a first PUCCH with a higher priority index and a second PUCCH with a lower priority index having HARQ-ACK information in response only to PDSCH reception without a corresponding PDCCH, or a configured grant PUSCH with a lower priority index having one or more SP-CSI reports without a corresponding PDCCH, or one or more SP-CSI reports without a corresponding PDCCH When transmitting the following channels, which include repetitions that will overlap in time with higher priority index PUSCHs and lower priority index PUCCHs with SR or CSI, or HARQ-ACK information corresponding only to PDSCH receptions that do not have a corresponding PDCCH, or higher priority index configured grant PUSCHs and lower priority index configured PUSCHs on the same serving cell, the UE may expect to cancel the repetition of PUCCH / PUSCH transmissions preceding the first symbol that overlaps with the higher priority index PUCCH / PUSCH transmission if the repetition of the lower priority index PUCCH / PUSCH transmission overlaps in time with the higher priority index PUCCH / PUSCH transmission.

[0350] A UE may not be expected to send a PUCCH or a PUSCH with a lower priority index that would overlap in time with a PUCCH with a higher priority index that has HARQ-ACK information only in response to a PDSCH reception that does not have a corresponding PDCCH. A UE may not be expected to be scheduled to send a PUCCH with a lower priority index that would overlap in time with a PUSCH with a higher priority index that has one or more SP-CSI reports that do not have a corresponding PDCCH.

[0351] If the UE multiplexes a non-periodic CSI with PUSCH, and the UE multiplexes a UCI containing HARQ-ACK information within a PUCCH that overlaps with PUSCH, and the timing conditions overlapping with PUCCH and PUSCH are met, the UE may multiplex only the HARQ-ACK information with PUSCH and not transmit PUCCH.

[0352] The UE sends multiple PUSCHs in a slot on each serving cell, including a first PUSCH and a second PUSCH scheduled in DCI format, each configured by the RRC parameter ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE multiplexes the UCI on one of the multiple PUSCHs. If the multiple PUSCHs satisfy the conditions for UCI multiplexing, the UE can multiplex the UCI from the first PUSCH to the second PUSCH.

[0353] If a UE sends multiple PUSCHs within a slot on each serving cell, and the UE multiplexes a UCI in one of the PUSCHs, and the UE does not multiplex a non-periodic CSI in any of the PUSCHs, then the UE can multiplex the UCI in the PUSCH of the serving cell that has the smallest RRC parameter ServCellIndex, as the UCI multiplexing conditions are met. If a UE sends two or more PUSCHs within a slot on a serving cell that has the smallest ServCellIndex that satisfies the UCI multiplexing conditions, then the UE can multiplex the UCI in the earliest PUSCH that the UE sends within the slot.

[0354] If a UE transmits a PUSCH through multiple slots, the UE transmits a PUCCH along with HARQ-ACK and / or CSI information across a single slot that overlaps with a PUSCH transmit in one or more of the multiple slots, and the PUSCH transmits in one or more slots satisfy the conditions for multiplexing HARQ-ACK and / or CSI information, the UE may multiplex HARQ-ACK and / or CSI information across the PUSCH transmits in one or more slots. If no UPUSCH transmits exist, and the UE does not transmit a single-slot PUCCH along with HARQ-ACK and / or CSI information in a slot, the UE may not multiplex HARQ-ACK and / or CSI information across the PUSCH transmits in slots from multiple slots.

[0355] If a push transmission across multiple slots is scheduled by a DCI format that includes a DAI field, the value of the DAI field may be applicable to the multiplexing of HARQ-ACK information in a push transmission in any slot from the multiple slots from which the UE multiplexes the HARQ-ACK information.

[0356] If the UE is to multiplex HARQ-ACK information in a PUSCH transmission that includes CG-UCI, as configured by the RRC parameter ConfiguredGrantConfig, the UE may multiplex HARQ-ACK information in the PUSCH transmission if the UE is provided with the RRC parameter cg-UCI-Multiplexing; otherwise, the UE will not transmit the PUSCH and will instead multiplex HARQ-ACK information in a PUSCH transmission or another PUSCH transmission.

[0357] A slot can be considered available for PUSCH transmission if it is determined that a PUSCH (or repeated PUSCH) is transmitted within the slot, or that a UCI (single or multiple) is being multiplexed. A slot can be considered unavailable for PUSCH transmission if it is determined that a PUSCH (or repeated PUSCH) within the slot is being canceled.

[0358] The procedure for slot configuration-based PUSCH is described below. If PUSCH is scheduled by DCI or a PUSCH with a configured grant, PUSCH will be sent unless otherwise specified.

[0359] If the UE provides the RRC parameter tdd-UL-DL-ConfigurationCommon, the UE can set the slot format for each slot over the number of slots indicated by tdd-UL-DL-ConfigurationCommon (a format indicating the types of symbols between downlink, uplink, and flexible symbols for each symbol within the slot). If the UE also provides the RRC parameter tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-ConfigurationDedicated can override only the flexible symbols for each slot over the number of slots provided by tdd-UL-DL-ConfigurationCommon.

[0360] In the case of operation on a single carrier in the ampered spectrum, if the UE is configured by the upper layer to receive PDCCH, or PDSCH, or CSI-RS, or DL ​​PRS in the set of symbols of the slot, the UE may receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS if it does not detect a DCI format that indicates to the UE to transmit PUSCH, PUCCH, PRACH, or SRS in at least one of the symbols of the set of symbols of the slot; otherwise, the UE may not receive PDCCH, or PDSCH, or CSI-RS, or DL ​​PRS in the set of symbols of the slot.

[0361] In the case of operation on a single carrier in the ampered spectrum, if the upper layer is configured to send SRS or PUCCH, or PUSCH or PRACH in a set of symbols in a slot, and the DCI format is detected in the UE to indicate to the UE that CSI-RS or PDSCH in a subset of symbols from the set of symbols, then the following A), B), and C) may apply: A) If the UE does not show the ability of partial cancellation, and the first symbol in the set occurs within T_(proc,2) for the last symbol in the CORESET in which the UE detects the DCI format, the UE does not expect to cancel the transmission of PUCCH, PUSCH or PRACH in the set of symbols. Otherwise, the UE cancels the PUCCH, PUSCH, or actual repetition of PUSCH or PRACH transmission in the set of symbols. B) If the UE demonstrates partial cancellation capability, the UE does not expect to cancel PUCCH, PUSCH, or PRACH transmissions from the set of symbols occurring in T_(proc,2) for the last symbol in the CORESET where the DCI format is detected. The UE cancels PUCCH, PUSCH, actual repetitions of PUSCH, or PRACH transmissions in the remaining symbols from the set of symbols. C) The UE does not expect to cancel SRS transmissions of symbols from the subset of symbols occurring in T_(proc,2) for the last symbol in the CORESET where the DCI format is detected. The UE cancels SRS transmissions in the remaining symbols from the subset of symbols. T_(proc,2) is the PUSCH preparation time of the corresponding UE processing capability, assuming that d_2,1=1, μ is the minimum SCS configuration between the SCS configuration of PDCCH carrying the DCI format and the SCS configuration of SRS, PUCCH, PUSCH, or μ_r, where μ_r corresponds to the SCS configuration of PRACH if it is 15kHz or higher, otherwise μ_r=0.

[0362] If the slot count type configuration indicates that the number of repetitions is counted based on consecutive slots, the above processing time requirement may apply: "If the first symbol in the set occurs within T_(proc,2) for the last symbol in the CORESET where the UE detects the DCI format, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission." If the slot count type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement can be relaxed. For example, "If the first symbol in the set occurs within T_(proc,2)+d_x for the last symbol in the CORESET where the UE detects the DCI format, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission" may apply, in which case d_x is a positive value. In other words, if the number of repetitions of PUSCH repetition type A is counted based on consecutive slots, the processing time requirement of T_(proc,2) may apply. If the number of repetitions for PUSCH repetition type A is counted based on the available slots, longer processing time requirements may apply.

[0363] For a set of symbols for a slot indicated to the UE as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE may not send PUSCH, PUCCH, PRACH, or SRS if the PUSCH, PUCCH, PRACH, or SRS overlaps, even partially, with the set of symbols for the slot.

[0364] For a set of slot symbols indicated to the UE as flexible by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, the UE may not expect to receive any dedicated RRC parameters from the UE in the set of slot symbols that constitute transmission, nor any dedicated RRC parameters that constitute reception by the UE in the set of slot symbols.

[0365] For operation on a single carrier in the ampered spectrum, for a set of symbols in a slot indicated to the UE by the RRC parameter ssb-PositionsInBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, for receiving an SS / PBCH block, the UE may not transmit PUSCH, PUCCH, or PRACH in the slot if the transmit overlaps with any symbol from the set of symbols, and the UE may not transmit SRS in the set of symbols in the slot. The UE may not expect the set of symbols in the slot to be indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided to the UE.

[0366] If a UE is scheduled by DCI format to send PUSCH across multiple slots, the UE may not send PUSCH in a slot if tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates that for a slot from multiple slots, at least one symbol from the set of symbols for which the UE is scheduled to send PUSCH in the slot is a downlink symbol.

[0367] If it is determined that a PUSCH (or repeated PUSCH) within a slot will be transmitted, the slot can be considered available for transmitting a PUSCH. If it is determined that a PUSCH (or repeated PUSCH) within a slot will be canceled or not transmitted, the slot can be considered unavailable for transmitting a PUSCH.

[0368] An example of the definition of T_(proc,2) is given. The first uplink symbol in the PUSCH allocation of a transport block, including DM-RS, is defined by the slot set K2, the start S and length L of the PUSCH allocation indicated by the "Time Domain Resource Allocation" of the scheduling DCI, and includes the effect of timing advance, if the first uplink symbol in the PUSCH allocation of the transport block is symbol L2 or later (where L2 is the end of receiving the last symbol of the PDCCH carrying the DCI scheduling the PUSCH), then T_(proc,2)(T proc,2 =max((N2+d 2,1 +d2)(2048+144) . κ2 -μ. T c +T ext +T switch d 2,2)) defined as the next uplink symbol having its CP to initiate a transport block, the UE can transmit a transport block. N2 is based on the μ of the UE processing capabilities 1 and 2, where u corresponds to one of (μDL, μUL) as a result of the maximum T_(proc,2), μDL corresponds to the subcarrier interval of the downlink from which the PDCCH carrying the DCI scheduling the PUSCH is transmitted, μUL corresponds to the subcarrier interval of the uplink channel from which the PUSCH is transmitted, and the constant k is 64. In the case of operation with shared spectral channel access, T_ext can be a non-zero value, otherwise T_ext can be 0. If the first symbol of the PUSCH assignment consists only of DM-RS, then d2,1=0, otherwise d2,1=1. The time unit T_C=l / (Δf_"max"N_f), in this case Δf_"max"=480·10^3Hz and N_f=4096. If the UE consists of multiple active component carriers, the first uplink symbol of the PUSCH assignment further includes the effect of timing differences between component carriers. If the scheduling DCI triggers a switch on the BWP, d2,2 is equal to the switching time; otherwise, d2,2=0. If a PUSCH with a higher priority index overlaps with a PUCCH with a lower priority index, d2 for the higher priority PUSCH is set as reported by the UE; otherwise, d2=0. For a UE supporting capability 2 in a given cell, the processing time according to the UE processing capability 2 applies if the upper-layer parameter processingType2Enabled in PUSCH-ServingCellConfig is configured for the cell and set to "enabled". If a PUSCH indicated by the DCI overlaps with one or more PUCCH channels, the transport block is multiplexed; otherwise, the transport block is sent over the PUSCH indicated by the DCI.If the uplink switching gap is triggered, T_switch is equal to the switching gap period and is for the UE configured with the RRC parameter uplinkTxSwitchingOption set to "dualUL" for uplink carrier aggregation μUL=min(μUL,carrier1,μUL,carrier2); otherwise, T_switch is equal to 0. For push preparation times of push timing capability 1, push preparation times N2 are 10, 12, 23, and 36 symbols for μ=0, 1, 2, and 3, respectively. For push preparation times of push timing capability 2, push preparation times N2 are 5, 5.5, and 11 symbols for μ=0, 1, and 2 (for frequency range (FR) 1), respectively.

[0369] This describes the slot format-based procedure. If a PUSCH is scheduled by a DCI or a PUSCH with a configured grant, the PUSCH will be sent unless otherwise specified.

[0370] This procedure may be applied to serving cells included in a set of serving cells configured in the UE by the RRC parameters slotFormatCombToAddModList and slotFormatCombToReleaseList, availableRB-SetsToAddModList and availableRB-SetsToRelease, switchTriggerToAddModList and switchTriggerToReleaseList, or co-DurationsPerCellToAddModList and co-DurationsPerCellToReleaseList.

[0371] The SFI index field value of DCI format 2_0 can indicate to the UE the slot format of each slot within the number of slots in each DL BWP or each UL BWP, starting from the slot where the UE detects DCI format 2_0. The number of slots may be equal to or greater than the PDCCH monitoring periodicity of DCI format 2_0. The SFI index field may include a maxSFIindex bit where maxSFIindex is the maximum value of the value provided by the corresponding RRC parameter slotFormatCombinationId. The slot format may be identified by the corresponding format index provided in a table where each entry specifies the respective combination of "D", "U", and / or "F", where "D" indicates a downlink symbol, "U" indicates an uplink symbol, and "F" indicates a flexible symbol. Index 255 may indicate that the UE can determine the slot format of a slot based on tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and, if any, based on the detected DCI format.

[0372] In the case of a set of slot symbols, the UE may not expect to detect a DCI format 2_0 with an SFI index field indicating the set of slot symbols as an uplink, nor to detect a DCI format indicating to the UE that it will receive PDSCH or CSI-RS within the set of slot symbols.

[0373] In the case of a set of symbols in a slot, the UE may not expect to find a DCI format 2_0 with an SFI index field value indicating the set of symbols in the slot as a downlink, nor will it expect to find a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE that PUSCH, PUCCH, PRACH, or SRS be sent within the set of symbols in the slot.

[0374] For a set of symbols for a slot indicated as downlink / uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE may not expect to find a DCI format 2_0 with SFI index field values ​​indicating the set of symbols for the slot as uplink / downlink or flexible, respectively.

[0375] If provided, for a set of symbols for a slot that is indicated to the UE as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, if the UE finds a DCI format 2_0 that provides a slot format using a slot format other than 255, then at least A) to E) below may apply. A) If the SFI index field value of DCI format 2_0 indicates that the set of symbols for a slot is flexible, and the UE finds a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that indicates to the UE to send PUSCH, PUCCH, PRACH, or SRS within the set of symbols for the slot, the UE sends PUSCH, PUCCH, PRACH, or SRS within the set of symbols for the slot. B) If the SFI index field value in DCI format 2_0 indicates that the set of symbols in the slot is flexible and the UE does not detect a DCI format that indicates the UE should receive PDSCH or CSI-RS, or if the UE does not detect a DCI format, RAR UL, fallbackRAR UL grant, or successRAR grant that indicates the UE should transmit PUSCH, PUCCH, PRACH, or SRS within the set of symbols in the slot, the UE will not transmit or receive within the set of symbols in the slot. C) If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH within the set of symbols in the slot, the UE will transmit PUCCH, PUSCH, or PRACH within that slot only if the SFI index field value in DCI format 2_0 indicates that the set of symbols in the slot is uplink.D) The UE does not expect to detect the SFI index field value in DCI format 2_0 indicating the set of symbols in the slot as downlink, nor to detect the DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR indicating to the UE that SRS, PUSCH, PUCCH, or PRACH will be sent from the set of symbols in the slot with one or more symbols. E) The UE does not expect to detect the SFI index field value in DCI format 2_0 indicating the set of symbols in the slot as downlink or flexible if the set of symbols in the slot contains symbols corresponding to any repetition of a PUSCH transmission activated (i.e., scheduled) by the UL type 2 grant PDCCH.

[0376] If the upper layer is configured to send SRS, or PUCCH, or PUSCH, or PRACH within a set of symbols in a slot, and the UE detects a DCI format 2_0 with a slot format value other than 255 indicating a slot format having a subset of symbols from a set of symbols as downlink or flexible, or if the UE detects a DCI format indicating to the UE that it will receive CSI-RS or PDSCH within a subset of symbols from a set of symbols, then the following A), B), and C) apply: A) If the UE does not demonstrate the ability of partialCancellation, the UE does not expect to cancel the transmission of PUCCH, or PUSCH, or PRACH within a set of symbols if the first symbol in the set occurs within T_(proc,2) for the last symbol in the CORESET for which the UE detects the DCI format. Otherwise, the UE cancels the actual repetition of PUCCH, or PUSCH, or PUSCH, or PRACH transmission within a set of symbols. B) If the UE demonstrates partial cancellation capability, the UE does not expect to cancel PUCCH, PUSCH, or PRACH transmissions from the set of symbols occurring in T_(proc,2) for the last symbol in the CORESET where the DCI format is detected. The UE cancels PUCCH, PUSCH, actual repetitions of PUSCH, or PRACH transmissions in the remaining symbols from the set of symbols. C) The UE does not expect to cancel SRS transmissions of symbols from the subset of symbols occurring in T_(proc,2) for the last symbol in the CORESET where the DCI format is detected. The UE cancels SRS transmissions in the remaining symbols from the subset of symbols.T_(proc,2) is the PUSCH preparation time of the corresponding UE processing capability, assuming that d_2,1=1, μ is the minimum SCS configuration between the SCS configuration of PDCCH carrying the DCI format and the SCS configuration of SRS, PUCCH, PUSCH, or μ_r, where μ_r corresponds to the SCS configuration of PRACH if it is 15kHz or higher, otherwise μ_r=0.

[0377] If the slot count type configuration indicates that the number of repetitions is counted based on consecutive slots, the above processing time requirement may apply: "If the first symbol in the set occurs within T_(proc,2) for the last symbol in the CORESET where the UE detects the DCI format, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission." If the slot count type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement can be relaxed. For example, "If the first symbol in the set occurs within T_(proc,2)+d_x for the last symbol in the CORESET where the UE detects the DCI format, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission" may apply, in which case d_x is a positive value. In other words, if the number of repetitions of PUSCH repetition type A is counted based on consecutive slots, the processing time requirement of T_(proc,2) may apply. If the number of repetitions for PUSCH repetition type A is counted based on the available slots, longer processing time requirements may apply.

[0378] If the UE does not detect an SFI index field value in DCI format 2_0 indicating that the set of symbols in a slot is flexible or uplink, and the UE does not detect a DCI format indicating to the UE that it is sending SRS, PUSCH, PUCCH, or PRACH within the set of symbols, the UE may assume that the flexible symbols in the CORESET configured for the UE for PDCCH monitoring are downlink symbols.

[0379] If provided, for a set of symbols for a slot indicated as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, and the UE does not find DCI format 2_0 which provides the slot format for the slot, then at least A) below may be applied: A) If the UE receives the corresponding instruction by DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, the UE sends PUSCH, PUCCH, PRACH, or SRS within the set of symbols for the slot.

[0380] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH within a set of symbols in a slot, and the UE is not provided with the RRC parameter enableConfiguredUL, then A) and B) below may apply. A) The UE does not transmit PUCCH, PUSCH, or PRACH within a slot, and does not transmit SRS from the set of symbols in the slot if it starts from a symbol after a PUSCH preparation time T_(proc,2) after the last symbol of the CORESET configured to monitor PDCCH in DCI format 2_0, assuming d_2,1=1 after the last symbol of the corresponding PUSCH timing capability. μ, if 15kHz or higher, corresponds to the minimum SCS configuration between the SCS configuration of PDCCH carrying DCI format 2_0 and the SCS configuration of SRS, PUCCH, PUSCH, or μ_r, and μ_r corresponds to the SCS configuration of PRACH, otherwise μ_r=0. B) The UE does not assume that the transmission of symbols of SRS, or PUCCH, or PUSCH, or PRACH in a symbol will be canceled from the set of symbols in the slot, assuming d_2,1=1 after the last symbol of the CORESET configured to monitor the PDCCH in DCI format 2_0, if present, after the PUSCH preparation time T_(proc,2) for the corresponding PUSCH timing capability. μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH carrying DCI format 2_0 and the SCS configuration of SRS, PUCCH, PUSCH, or μ_r if 15kHz or higher, and μ_r corresponds to the SCS configuration of PRACH, otherwise μ_r=0.

[0381] If the slot count type configuration indicates that the number of repetitions is counted based on consecutive slots, the above processing time requirement may apply: "If the first symbol in the set occurs within T_(proc,2) for the last symbol in the CORESET that the UE monitors DCI format 2_0, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission." If the slot count type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement can be relaxed. For example, "If the first symbol in the set occurs within T_(proc,2)+d_x for the last symbol in the CORESET that monitors DCI format 2_0, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission" may apply, in which case the UE expects d_x to be a positive value. In other words, if the number of repetitions of PUSCH repetition type A is counted based on consecutive slots, the processing time requirement of T_(proc,2) may apply. If the number of repetitions for PUSCH repetition type A is counted based on the available slots, longer processing time requirements may apply.

[0382] If the UE is configured by the upper layer to send SRS, PUCCH, PUSCH, or PRACH within the set of symbols in the slot, and the UE is provided with enableConfiguredUL, then the UE may send SRS, PUCCH, PUSCH, or PRACH, respectively.

[0383] If it is determined that a PUSCH (or repeated PUSCH) within a slot will be transmitted, the slot may be considered available for PUSCH transmission. If it is determined that a PUSCH (or repeated PUSCH) within a slot will be canceled or not transmitted, or if at least one symbol for the PUSCH within the slot is determined to be a downlink symbol, the slot may be considered unavailable for PUSCH transmission.

[0384] This describes the procedure based on cancellation instructions. If a PUSCH is scheduled by a DCI or a PUSCH with a Confided Grant, the PUSCH will be sent unless otherwise specified.

[0385] If the UE provides the RRC parameter UplinkCancellation, the UE may provide a search space set for monitoring the first PDCCH candidate at the CCE aggregation level of the L_CI CCE for detecting DCI format 2_4 using the CI-RNTI provided by ci-RNTI in one or more serving cells.

[0386] For a serving cell having an associated field in DCI format 2_4, the field may be denoted by: N_"CI" (number of bits provided by RRC parameter ci-PayloadSize); B_"CI" (number of PRBs provided by RRC parameter frequencyRegionforCI within RRC parameter timeFrequencyRegion); T_"CI" (number of symbols provided by RRC parameter timeDurationforCI within RRC parameter timeFrequencyRegion, excluding symbols for receiving SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, if the PDCCH monitoring periodicity of the search space having DCI format 2_4 is one slot and there are two or more PDCCH monitoring opportunities in the slot, or equal to the PDCCH monitoring periodicity); otherwise, G_"CI" (number of partitions of symbols provided by RRC parameter timeGranularityforCI within RRC parameter timeFrequencyRegion).

[0387] Instructions for a serving cell in DCI format 2_4 may be applicable to push or SRS transmissions on the serving cell. If a push or SRS transmission is scheduled in DCI format, instructions in DCI format 2_4 may be applicable to a push or SRS transmission only if the last symbol of the PDCCH reception providing the DCI format is earlier than the first symbol of the PDCCH reception providing DCI format 2_4. In the case of a serving cell, the UE can determine that the first symbol of the T_CI symbol is the first symbol T'_(proc,2) after the end of the PDCCH reception where the UE detects DCI format 2_4, where T'_(proc,2) is obtained from T_(proc,2) of PUSCH processing capacity 2 assuming d_2,1=d_offset2^(-μ_UL) / 2^(-μ), where d_offset is given by the RRC parameter delta_Offset, and μ is the minimum SCS configuration between the SCS configuration of the PDCCH and the minimum SCS configuration μ_UL provided in the RRC parameter scs-SpecificCarrierList of FrequencyInfoUL or FrequencyInfoUL-SIB. The UE may not assume that it cancels the PUSCH or SRS transmission prior to the corresponding symbol, which is T_(proc,2) assuming d_2,1=0 after the last symbol of the CORESET where the UE detects DCI format 2_4.

[0388] If the slot count type configuration indicates that the number of repetitions is counted based on consecutive slots, the above processing time requirement may apply: "If the first symbol in the set occurs within T'_(proc,2) for the last symbol of the PDCCH in which the UE detects DCI format 2_4, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission." If the slot count type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement can be relaxed. For example, "If the first symbol in the set occurs within T'_(proc,2)+d_x for the last symbol of the PDCCH in which the UE detects DCI format 2_4, the UE does not expect to cancel the PUSCH transmission in the set of symbols; otherwise, the UE cancels the PUSCH transmission" may apply, in which case d_x is a positive value. In other words, if the number of repetitions of PUSCH repetition type A is counted based on consecutive slots, the processing time requirement of T'_(proc,2) may apply. If the number of repetitions for PUSCH repetition type A is counted based on the available slots, longer processing time requirements may apply.

[0389] A UE that detects the DCI format 2_4 of a serving cell may cancel a PUSCH transmission (including a PUSCH transmission with repeat type A), or an actual repeat of a PUSCH transmission, or an SRS transmission on the serving cell, if the transmission is a PUSCH with priority 0, provided the UE is provided with the RRC parameter uplinkCancellationPriority, and the group of symbols from T_"CI" symbols has at least one bit value "1" in the corresponding set of N_BI bits in DCI format 2_4 and includes symbols of a PUSCH transmission or an SRS transmission (repeating), and the group of PRBs from B_"CI" PRB has the corresponding bit value "1" in the corresponding set of bits in DCI format 2_4 and includes a PUSCH transmission or an SRS transmission (repeating), or if the PUSCH transmission is of repeat type B, then the UE may cancel a PUSCH transmission (including a PUSCH transmission with repeat type A), or an actual repeat of a PUSCH transmission, or an SRS transmission on the serving cell. The cancellation of a PUSCH transmission (repeating) may include all symbols from the earliest symbol of the PUSCH transmission (repeating) that are in the group of symbols having the corresponding bit value "1" in DCI format 2_4. Cancellation of an SRS transmission may only include symbols that are in one or more groups of symbols that have a corresponding bit value of "1" in DCI format 2_4.

[0390] If a UE cancels a PUSCH or SRS transmission based on instructions in DCI format 2_4, the UE cannot expect to be scheduled by the second DCI format to transmit the PUSCH or SRS via a symbol containing the symbol of the canceled PUSCH or SRS transmission. The last symbol of a PDCCH reception providing the second DCI format is delayed compared to the first symbol of a PDCCH reception providing DCI format 2_4.

[0391] If it is determined that a PUSCH (or repeated PUSCH) within a slot will be transmitted, the slot can be considered available for transmitting a PUSCH. If it is determined that a PUSCH (or repeated PUSCH) within a slot will be canceled or not transmitted, the slot can be considered unavailable for transmitting a PUSCH.

[0392] When the number of repetitions is counted based on the available slots, several sub-options may exist regarding the consideration of conditions in PUSCH priority-based procedures, slot configuration-based procedures, slot format-based procedures, and cancel instruction-based procedures. Conditions in slot configuration procedures may always be applicable. Whether conditions in other procedures are applicable may depend on the specific RRC configuration.

[0393] The first sub-option is to have a single slot count type configuration that is applicable to all conditions. More specifically, if the slot count type configuration indicates that the number of repetitions is counted based on the available slots, and the available slot type configuration (e.g., an RRC configuration or RRC parameter indicating whether the available slots are determined based solely on a quasi-static configuration or on both a quasi-static configuration and dynamic signaling; this configuration may or may not be identical to the slot count type configuration) indicates that dynamic signaling is used to determine the available slots, then the available slots may be determined according to all conditions for which the corresponding RRC configuration is provided. For example, the conditions in a PUSCH priority-based procedure may be applicable if a phy-Prioritylndex or prioritylndicatorDCI is provided, but the conditions in a PUSCH priority-based procedure may not be applicable if a phy-Prioritylndex or prioritylndicatorDCI (a procedure for determining whether a PUSCH is sent based on its priority index) is not provided. The conditions for a slot format-based procedure may be applicable if SlotFormatCombinationsPerCell (i.e., an RRC parameter / configuration that triggers a slot format-based procedure (a procedure that determines whether or not a PUSCH is sent based on the slot format)) is provided, but the conditions for a slot format-based procedure may not be applicable if SlotFormatCombinationsPerCell is not provided. The conditions for a cancellation indicator-based procedure may be applicable if UplinkCancellation (i.e., an RRC parameter / configuration that triggers a cancellation indicator-based procedure (a procedure that determines whether or not a PUSCH is sent based on the cancellation indicator)) is provided, but the conditions for a cancellation indicator-based procedure may not be applicable if UplinkCancellation is not provided.

[0394] If, by the first sub-option, the UE has the functionality of a particular coverage extension feature(single or multiple), and / or the UE has a particular coverage extension configuration(single or multiple), then, alternatively or additionally, the UE may be provided with a slot count type configuration indicating that PUSCH repetitions are counted based on available slots, and / or the UE has an available slot count type configuration indicating that dynamic signaling is used to determine available slots, then the following may apply: For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may repeat the TB across K available slots (i.e., a first K slots available for the PUSCH transmission) applying the same symbol assignment to each slot. The K available slots may be determined according to the conditions of a slot configuration-based procedure, as well as a PUSCH priority-based procedure, a slot format-based procedure, and a cancel instruction-based procedure.

[0395] If the first sub-option means that the UE has the functionality of a particular coverage extension feature(single or multiple), and / or the UE has a particular coverage extension configuration(single or multiple), then, alternatively or additionally, the UE may be provided with a slot count type configuration indicating that PUSCH repetitions are counted based on available slots, and / or the UE may have an available slot count type configuration indicating that only quasi-static configurations are used to determine available slots, then the following may apply: For both Type 1 and Type 2 PUSCH transmissions with configured grants, if K > 1, the UE may repeat the TB across K available slots (i.e., the first K slots available for the PUSCH transmission) applying the same symbol assignment to each slot. The K available slots may be determined according to the conditions of a slot configuration-based procedure, without referring to the conditions of a PUSCH priority-based procedure, a slot format-based procedure, and a cancel instruction-based procedure.

[0396] A second sub-option is to have several slot count type configurations, each applicable to the conditions in their respective procedures. More specifically, if the available slot type configuration for a PUSCH priority-based procedure indicates that PUSCH priority-based send / cancel is used to determine the available slots, then the available slots may be determined according to the PUSCH priority-based procedure. Similarly, if the available slot type configuration for a slot format-based procedure indicates that slot format-based send / cancel is used to determine the available slots, then the available slots may be determined according to the slot format-based procedure. If the available slot type configuration for a cancel instruction-based procedure indicates that cancel instruction-based send / cancel is used to determine the available slots, then the available slots may be determined according to the cancel instruction-based procedure. For example, the conditions in a PUSCH priority-based procedure may be applicable if phy-Prioritylndex or prioritylndicatorDCI is provided, and if an available slot type configuration for a PUSCH priority-based procedure indicating the use of a PUSCH priority-based procedure is provided, but the conditions in a PUSCH priority-based procedure may not otherwise be applicable. The conditions for a slot format-based procedure may apply if SlotFormatCombinationsPerCell is provided and available slot type configurations for a slot format-based procedure indicating the use of a slot format-based procedure are provided, but the conditions for a slot format-based procedure may not apply otherwise. The conditions for a cancel instruction-based procedure may also apply if UplinkCancelling is provided and available slot type configurations for a cancel instruction-based procedure indicating the use of a cancel instruction-based procedure are provided, but the conditions for a cancel instruction-based procedure may not apply otherwise. Any combination of the above may also apply.For example, if available slot type configurations are provided for PUSCH priority-based procedures and for slot format-based procedures, and if available slot type configurations are not provided for cancel instruction-based procedures, the available slots may be determined based on the conditions of the slot configuration-based procedure and the conditions in the PUSCH priority-based procedure and the slot format-based procedure, but the conditions according to the cancel instruction-based procedure are not referenced for determining the available slots.

[0397] A second sub-option allows the following to apply if the UE has the functionality of a particular coverage extension feature(single or multiple) and / or if the UE has a particular coverage extension configuration(single or multiple), alternatively or additionally, if the UE has a slot count type configuration indicating that PUSCH repetitions are counted based on available slots, and if the UE has at least one of the available slot type configurations for PUSCH priority-based procedures, slot format-based procedures and cancel instruction-based procedures: For both type 1 and type 2 PUSCH transmissions with configured grants, if K>1, the UE can repeat the TB across K available slots (i.e., a first K slots available for the PUSCH transmission) applying the same symbol assignment to each slot. The K available slots may be determined according to the conditions of the slot configuration-based procedure, if available slot type configurations for PUSCH priority-based procedures, slot format-based procedures, or cancel instruction-based procedures are provided, and additionally, according to the conditions of the PUSCH priority-based procedure, slot format-based procedure, and cancel instruction-based procedure.

[0398] If only quasi-static configuration is used to determine available slots, and / or if any dynamic signaling is not used to determine available slots, the UE determines K slots for a PUSCH transmission that begin with a slot shown to the UE for the PUSCH transmission, having A) UL symbols or flexible symbols that are not SS / PBCH block symbols as described in the slot configuration procedure, and B) consecutive UL symbols or flexible symbols that are not SS / PBCH block symbols, starting with a first symbol, and the number of first symbols and symbols in the slot being greater than or equal to the number of symbols that may be provided in the PUSCH time-domain resource allocation information.

[0399] Note that the aforementioned configurations of available slot types may be referred to by different names. The presence of an available slot type configuration in an RRC configuration message may mean that conditions in both the slot configuration procedure and other procedures (one or more) are used to determine the available slots, while the absence of an available slot type configuration in an RRC configuration message may mean that conditions in the slot configuration procedure, rather than other procedures (one or more), are used to determine the available slots. Additionally and / or alternatively, an available slot type configuration set to a first value (e.g., "quasi-static") may mean that conditions in the slot configuration procedure, rather than other procedures (one or more), are used to determine the available slots, while an available slot type configuration set to a second value (e.g., "dynamic") may mean that conditions in both the slot configuration procedure and other procedures (one or more) are used to determine the available slots.

[0400] Figure 9 shows an exemplary configuration of a frame structure according to one aspect of this embodiment. In Figure 9, the horizontal axis represents the time domain. In the time domain, slots are numbered in ascending order starting from Slot#n (the slot with index n). Each line in the time domain indicates a slot boundary. 9001 represents the downlink domain. 9002 represents the flexible domain. 9003 represents the uplink domain.

[0401] The region indicated by 9000 includes the set of regions 9001, 9002, and 9003. Region 9000 may be configured based on a slot configuration. For example, a slot configuration may include at least a downlink region, a flexible region, and an uplink region. For example, a slot configuration may be configured to begin at one UL-to-DL switching point. Furthermore, a slot configuration may be configured to end at another UL-to-DL switching point. For example, a UL-to-DL switching point may be the point where the uplink region ends and the downlink region begins.

[0402] For example, a slot configuration can be repeated in the time domain. In Figure 9, a slot configuration containing three downlink slots, one special slot, and one uplink slot is repeated. Domain 9000 is an instance of the slot configuration starting with Slot#n, and domain 9010 is an instance of the slot configuration starting with Slot#n+5. In Figure 9, the repeating cycle of the slot configuration is 5 slots.

[0403] 9011 indicates the downlink region. Furthermore, 9012 indicates the flexible region. Furthermore, 9013 indicates the uplink region.

[0404] For example, a slot configuration can be represented by a combination of "D", "U", and "S". "D" indicates that the slot is a downlink slot. A downlink slot is a slot that has a downlink region. In Figure 9, Slot#n, Slot#n+1, Slot#n+2, Slot#n+5, Slot#n+6, and Slot#n+7 are downlink slots.

[0405] The letter "U" indicates that the slot is an uplink slot. An uplink slot is a slot that has an uplink area. In Figure 9, Slot#n+4 and Slot#n+9 are uplink slots.

[0406] The letter "S" indicates a special slot. A special slot is one that has at least two of the following: downlink area, flexible area, and uplink area. In Figure 9, Slot#n+3 and Slot#n+8 are special slots.

[0407] In Figure 9, the slot configuration may also be referred to as "DDDSU." "DDDSU" means that the slot configuration includes three downlink slots, one special slot, and one uplink slot.

[0408] The configuration of a special slot can be represented by "XDYFZU," where X is the number of downlink symbols, Y is the number of flexible symbols, and Z is the number of uplink symbols. For example, "10D2F2U" indicates that the special slot contains 10 downlink symbols, 2 flexible symbols, and 2 uplink symbols.

[0409] Downlink symbols are OFDM symbols within the downlink domain. Flexible symbols are OFDM symbols within the flexible domain. Uplink symbols are OFDM symbols within the uplink domain.

[0410] Slot configuration can be provided by RRC parameters. For example, slot configuration can be configured by common parameters included in system information such as SIB1. These common parameters are sometimes also referred to as tdd-UL-DL-ConfigurationCommon.

[0411] For example, terminal device 1 configures the reference subcarrier interval u from common parameters. refAnd the first TDD pattern can be determined. The first TDD pattern includes one or more of T1 to T5. T1 is the configuration period P in milliseconds provided by referenceSubcarrierSpacing. T2 is the number of slots d indicating consecutive downlink slots provided by nrofDownlinkSlots. slots T3 is the number of consecutive downlink symbols d provided by nrofDownlinkSymbols. sym T4 is the number of consecutive uplink slots provided by nrofUplinkSlots. slots T5 is the number of consecutive uplink symbols provided by nrofUplinkSymbols. sym That is the case.

[0412] Figure 10 shows an exemplary configuration of a slot configuration according to one aspect of this embodiment. In Figure 10, the horizontal axis represents the time domain. In the time domain, slots are numbered in ascending order starting from Slot#n (the slot with index n). Each line in the time domain indicates a slot boundary. 10000 represents the slot configuration. In the slot configuration, the first d is shown by region 10001. slots The 2 slots are configured as downlink slots. In the slot configuration, the last u indicated by region 10002 slots =1 slot is configured as an uplink slot. In the slot configuration, index n+d is indicated by region 10003. slots The first d starting from the first OFDM symbol in the slot having sym OFDM symbols are configured as downlink symbols. In the slot configuration, as indicated by region 10004, index n+Su slots The last u before the first OFDM symbol in the slot having symOFDM symbols are configured as uplink symbols. In a slot configuration, the remaining OFDM symbols that are not designated as either downlink or uplink regions, as indicated by region 1005, are flexible symbols.

[0413] The slot configuration can be modified by UE-specific parameters. These UE-specific parameters may also be referred to as tdd-UL-DL-CoifigurationDedicated.

[0414] If UE-specific parameters are provided to terminal device 1, these parameters can modify (or reconfigure) the slot configuration provided by common parameters. For example, UE-specific parameters can modify (or reconfigure) the flexible area in the slot configuration.

[0415] For example, terminal device 1 can determine a list containing a set of slot reconfigurations based on UE-specific parameters. Each slot reconfiguration in the set may be provided with at least one or both of the slot index and an instruction for the slot's TDD pattern. The instruction can be one of the following: "all DL", "all UL", and "explicit". If "all DL" is indicated for a slot, the slot configuration within the slot is reconfigured as a downlink area. If "all UL" is indicated for a slot, the slot configuration within the slot is reconfigured as an uplink area. If "explicit" is indicated for a slot, the slot configuration within the slot is reconfigured by the explicit instruction corresponding to "explicit". The instruction "explicit" corresponds to information indicating the TDD pattern within the slot. This information includes information indicating the number of downlink symbols starting from the beginning of the slot and information indicating the number of uplink symbols ending at the end of the slot. The remaining OFDM symbols between the downlink and uplink symbols are flexible symbols.

[0416] Terminal device 1 can receive physical signals if it is configured by the upper layer or indicated by the DCI format to receive physical signals in the downlink region.

[0417] If terminal device 1 is configured by the upper layer to transmit physical signals in the uplink area, or is indicated by the DCI format, then terminal device 1 can transmit physical signals.

[0418] If monitoring of DCI format 2_0 is not configured by the upper layer, terminal device 1 can receive physical signals if the DCI format indicates that terminal device 1 is scheduled to receive physical channels in the downlink or flexible region.

[0419] If monitoring of DCI format 2_0 is not configured by a higher layer, terminal device 1 may transmit a physical signal if the DCI format indicates that terminal device 1 is scheduled to transmit the physical signal in the uplink area or the flexible area.

[0420] If monitoring of DCI format 2_0 is configured by a higher layer, terminal device 1 can determine whether or not to receive a physical signal, at least based on the instructions in DCI format 2_0.

[0421] If monitoring of DCI format 2_0 is configured by a higher layer, terminal device 1 can decide whether or not to transmit a physical signal, at least based on the instructions in DCI format 2_0.

[0422] The configuration for monitoring DCI format 2_0 may include at least one of S1 to S3. S1 is the identifier of the serving cell. S2 is information indicating the bit position of the field of the slot format indicator index. S3 is a set of slot format combinations, where each slot format combination may include one or more slot formats. Each slot format combination may include the index of the slot format indicator. Each slot format may indicate a TDD pattern in the slot. For example, slot format #0 indicates that all OFDM symbols in the slot are downlink symbols. For example, slot format #1 indicates that all OFDM symbols in the slot are uplink symbols. For example, one slot format indicates that the first nine OFDM symbols in the slot are downlink symbols, the next three OFDM symbols in the slot are flexible symbols, and the remaining two OFDM symbols are uplink symbols. For example, one slot format indicates that terminal device 1 interprets DCI format 2_0 monitoring as not being configured. Other TDD patterns in the slot are not excluded.

[0423] When terminal device 1 detects DCI format 2_0 in the first slot, terminal device 1 applies the combination of slot formats indicated through the index of the slot format indicator in DCI format 2_0. For example, the combination of slot formats may be applied to slots starting from the first slot.

[0424] The behavior of a PUSCH transmission can be controlled based on instructions in DCI format 2_0, at least. For example, a PUSCH transmission may be a repetition of a PUSCH instance defined within a slot.

[0425] A PUSCH instance can be a unit of baseband signal generation, where baseband signal generation may be performed by the baseband unit 13.

[0426] Figure 11 shows an exemplary configuration of the baseband section 13 within the wireless transmission unit 10a according to one aspect of this embodiment. The baseband section 13 may include at least some or all of the following: an encoding device 12000, a scrambler 11001, a modulator 11002, a layer mapper 11003, a conversion precoder 11004, a precoder 11005, a resource element mapper 11006, and a time-continuous signal generator 11007.

[0427] A transport block may be provided to the encoding device 12000 from a higher layer. For example, a transport block may be provided to the encoding device 12000 from the MAC layer processing unit 15 via UL-SCH. The encoding device 12000 processes the transport block into a sequence b of encoded bits. The sequence of encoded bits may be provided to the scrambler 11001. An element in position k of sequence b may be denoted as b(k). Position k is 0 to M bit It lies within the range of -1. Position k is represented by an integer. M bit This represents the length of sequence b.

[0428] For example, the scrambler 11001 can scramble a sequence of encoded bits b by using a pseudo-random code c. For example, element b(k) can be scrambled by element c(k) at position k of the pseudo-random code c. For example, the scrambler 11001 can scramble b a By calculating (k) = mod(b(k) + c(k), 2), the sequence b a It can output b. a (k) is sequence b a This is the element at position k. If the baseband section 13 does not include the scrambler 11001, the sequence b of the encoded bits is b a It can be entered into.

[0429] The pseudo-random code c may be a sequence of bits generated by the scrambler 11001. For example, the pseudo-random code c may be generated by an equation having an initialization variable. The initialization variable can determine or control the output from the equation. The initialization variable may be determined at least based on the RNTI used to schedule uplink transmissions that propagate the transport block.

[0430] For example, modulator 11002 controls sequence b a Modulation can be performed to generate a sequence d of complex-valued symbols. The element at position j of sequence d is called d(j). Position j is 0 to M symb It is within the range of -1. Position j is represented by an integer. M symb This represents the length of sequence d. If the baseband section 13 does not include the modulator 12002, the sequence ba of encoded bits may be input to d.

[0431] For example, the modulation could be 2 / pi BPSK (Binary Phase Shift Keying), QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM.

[0432] For example, the layer mapper 11003 can perform layer mapping on sequence d. After layer mapping, each has a length M. layer symb An Nv sequence containing N is generated. v N is the number of layers in the PUSCH model. v v in the sequence th The sequence is x (v) It is called sequence x. (v) The element at position h is x (v) It is called (h). Position h is 0 to M layer symb It is within the range of -1. The position h is represented by an integer. Number Nv If is 1, the layer mapper 11003 may not perform layer mapping. If layer mapping is not performed in sequence d, sequence d is x (0) It can be entered into.

[0433] For example, the conversion precoder 11004 converts the precode to sequence x (v) Execute to sequence y (v) It can generate the following. The conversion precoding is sequence x (v) If not executed, sequence x (v) is sequence y (v) It can be entered into.

[0434] For example, precoder 11005 is sequence y (v) Precoding can be performed, and after precoding, each will have a length M layer symb tactN p A sequence is generated. N p This is the number of antenna ports for the pusher. p p in the sequence th The sequence is z (p) It is called sequence z. (p) The element at position h is z (p) It is called (h). Number N p If the value is 1, the precoder 11005 may not perform precoding. Precoding is performed on sequence y (v) If not executed, sequence y (v) is, z (p) It can be entered into.

[0435] For example, resource element mapper 11006 can perform RE mapping. In RE mapping, the element group z(h) = [z (0) (h),...,z (Np-1) (h)] is mapped to a resource element.

[0436] For example, the time-continuous signal generator 11007 can perform time-continuous signal generation based on the content within a resource element. The content within the resource element is determined based on RE mapping. The time-continuous signal generated by the time-continuous signal generator 11007 is provided to the RF unit 12.

[0437] The baseband section 33 may include corresponding components for receiving PUSCH as the baseband section 13.

[0438] Figure 12 shows an exemplary configuration of an encoding device 12000 according to one aspect of this embodiment. The encoding device 12000 may include at least some or all of the following: a CRC addition unit 12001, a CB segmentation unit 12002, an encoding unit 12003, a rate matching unit 12004, and a multiplexing unit 12005.

[0439] For example, a transport block input to the encoding device 12000 is input to the CRC addition unit 12001. In the CRC addition unit 12001, a CRC sequence is added to the transport block. The bit sequence after the addition of the CRC sequence is input to the code block segmentation unit 12002. If no CRC sequence is added to the transport block, the transport block is input to the code block segmentation unit 12002.

[0440] For example, a sequence input to the code block segmentation unit 12002 is segmented into multiple code blocks if the sequence length is greater than a certain value. If the sequence is segmented into multiple code blocks, a CRC sequence is added to each code block. Each code block after the addition of the CRC sequence is input to the encoding unit 12003. If the sequence is not segmented into multiple code blocks, a single code block is input to the encoding unit 12003. If the sequence is not segmented into multiple code blocks, no CRC sequence is added to the single code block. If the sequence is not segmented into multiple code blocks, a single code block without a CRC sequence is input to the encoding unit 12003.

[0441] For example, a code block with index r (code block #r) input to the encoding unit 12003 is encoded by LDPC coding such as QC-LDPC (Quasi-Cyclic Low Density Parity Check) coding. The index r is in the range of 0 to C-1. C is the number of code blocks determined by the code block segmentation unit 12002. The encoded bits d of code block #r after LDPC coding. r This is input to the rate matching unit 12004.

[0442] For example, the rate matching unit 12004 executes a bit selection procedure. In the bit selection procedure, the encoded bits d of the code block r are selected. r However, length N cb It is written to the circular buffer.

[0443] Figure 13 shows an example of a bit selection procedure according to one aspect of this embodiment. In the bit selection procedure, two values ​​k and j are set to 0 in step 0. Next, in step 1, the rate matching unit 12004 checks whether the value k is smaller than the rate matching output sequence length Er. r If the value k is less than the rate matching output sequence length E r If the result is smaller than the specified value, the rate matching unit 12004 terminates the bit selection procedure.

[0444] Here, the rate-matching output sequence length E r This represents the number of bits available for transmission of code block #r. For example, the rate-matched output sequence length E of code block #r. r At least, the modulation order Q m This can be calculated based on some or all of the number of layers Nv, C', and G of PUSCH. For example, the rate-matched output sequence length E of code block r. r is, E r =N L Q m floor(G / (N L Q m C')) or E r =N L Q m ceil(G / (N L Q m It can be calculated by C').

[0445] Here, the number C' represents the number of code blocks. The number G represents the number of bits available for sending the UL-SCH. For example, the number G could represent the number of bits available for sending the UL-SCH in a PUSCH instance.

[0446] In step 2, the rate matching unit 12004 is d r (mod(k0+j,N cb ))but <null>Check whether it is not. d r (mod(k0+j,N cb ))but <null>Otherwise, the rate matching unit 12004 proceeds to step 3. r (mod(k0+j,N cb ))but <null>If so, the rate matching unit 12004 proceeds to step 5.

[0447] Here, "dr(mod(k0+j,Ncb)) is <null>"is" is <null>ga d r (mod(k0+j,N cb This means that it is set to ). If the element corresponds to the filter bit for LDPC encoding, <null>is, d r It can be set to some elements.

[0448] Here, d r The element at position k is d r It is referred to as (k).

[0449] In step 3, the rate matching unit 12004 is d r (mod(k0+j,N cb Set the value inside )) to e(k). Sequence e is a rate-matching output sequence. The k-th element of sequence e is called e(k).

[0450] Here, k0 represents the starting point of the circular buffer.

[0451] In step 4, the rate matching unit 12004 increments the value k by 1.

[0452] Step 5 is a sign that Step 2 is complete.

[0453] In step 6, the rate matching unit 12004 increments the value j by 1.

[0454] Step 7 is a sign that Step 1 is complete. The rate matching unit 12004 returns to Step 1.

[0455] Figure 14 shows an example of a circular buffer according to one aspect of this embodiment. In a circular buffer, the encoded bit d r The coordinates are mapped clockwise from the position indicated by RV0. Encoded bit d r Since it includes systemic bits and subsequent parity bits, the systemic bits are mapped starting from the position indicated by RV0, and the parity bits are mapped starting from the end of the systemic bits. The area indicated by the upper right diagonal line is filled with systemic bits. The area indicated by the grid lines is filled with parity bits.

[0456] In the bit selection procedure, the bits in the circular buffer have a length E r The bits are read from the starting point k0. The bits read from the circular buffer are written to the rate-matching output sequence e.

[0457] The starting point k0 is determined based on the redundant version indicated or determined by the redundant version field in the uplink DCI format for dynamic scheduling.

[0458] For example, the starting point k0 may be determined based on the identification of the redundant version and instance. For example, if one DCI format schedules repeated PUSCH, terminal device 1 can send multiple instances. For each instance, the starting point k0 may be determined. For example, if eight instances (instance #0, instance #1, instance #2, instance #3, instance #4, instance #5, instance #6, instance #7) are scheduled in one DCI format, the starting point k0 may be determined eight times.

[0459] For example, a sequence of RVs (redundant versions) may be provided to terminal device 1. If a sequence of RVs is provided, the RVs are assigned to each instance in multiple instances based on the sequence. For example, a sequence of length N. s If a sequence [0, 2, 3, 1] is provided, then (mod(N, N) in the sequence s )+1) th The value is n th It can be assigned to an instance. th The starting point k0 of the instance is n th This can be determined based on the RV allocated for the instance.

[0460] Figure 15 is an exemplary configuration of a first type of repetition of PUSCH scheduled by DCI format in multiple slots according to one aspect of this embodiment. In Figure 15, 15000 represents a PDCCH having DCI format that schedules PUSCH in a first type of repetition. Assume that the first type of repetition is scheduled in the slot starting at Slot#n+3 in Figure 15. 15001 represents an instance of PUSCH in Slot#n+3, where the value S is the starting OFDM symbol index in the slot for instance 15001, and the value L is the length of instance 15001 in terms of the number of OFDM symbols. Six instances, indicated by 15002-15007, follow instance 15001. Each instance is mapped within the slot. In Figure 15, the number of repetitions is K. rep Assume that it is 7.

[0461] The TDRA field in the DCI format can provide values ​​S and L.

[0462] In Figure 15, S applies to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within a slot. In Figure 15, L applies to all instances of PUSCH. For example, all instances apply the same length with respect to the number of OFDM symbols.

[0463] In the first type of iteration, multiple instances of PUSCH are created starting from a slot determined by the DCI format used to schedule PUSCH. rep It can be assigned to consecutive slots. For example, if the DCI format for scheduling a PUSCH includes a TDRA field, the TDRA field can provide a value K for determining the starting slot of the PUSCH. For example, the value K is in units of slots. For example, terminal device 1 can determine the starting slot as Slot#(n+K) if a PDCCH containing a DCI format is detected at Slot#n. If the DCI format does not include a TDRA field, the value K can be provided by the RRC layer via an RRC parameter.

[0464] A sequence of RVs for a first type of repetition may be provided to terminal device 1. For example, the sequence may be provided by the RRC layer via RRC parameters. When a sequence of RVs is provided for a first type of repetition, the sequence contains (mod(n,N s )+1) th The value is n th It can be assigned to an instance. Here, the index can be provided to each instance of PUSCH in ascending order in the time domain.

[0465] In the first type of iteration, if an instance overlaps with a downlink symbol determined by the slot configuration, the instance may be omitted (or dropped, canceled, or not sent).

[0466] In the first type of iteration, if an instance overlaps with a downlink symbol determined by the slot format, the transmission of the instance may be omitted.

[0467] In the first type of iteration, if an instance overlaps with another uplink signal having a higher priority than the PUSCH, the transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH having a higher priority than the PUSCH. For example, the priority of a PUSCH may be provided by the DCI format used to schedule the PUSCH.

[0468] Figure 16 shows an exemplary configuration of a second type of repetition of PUSCH scheduled by DCI format in multiple slots according to one aspect of this embodiment. In Figure 16, 16000 represents a PDCCH having DCI format that schedules PUSCH in a second type of repetition. It is assumed that the second type of repetition is scheduled in a slot starting at Slot#n+3. 16001 represents an instance of PUSCH in Slot#n+3, where the value S is the starting OFDM symbol index in the instance's slot, and the value L is the length of the instance in terms of the number of OFDM symbols. Three instances, represented by 16002-16004, follow instance 16001. Each instance is mapped within a slot. In Figure 16, the number of repetitions is K. rep It is 4.

[0469] In Figure 16, S applies to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within a slot. In Figure 16, L applies to all instances of PUSCH. For example, all instances apply the same length with respect to the number of OFDM symbols.

[0470] In the second type of iteration, multiple instances of PUSCH are scheduled starting from a slot determined by the DCI format used to schedule PUSCH. rep It can be assigned to consecutive available slots. For example, if the DCI format for scheduling a PUSCH includes a TDRA field, the TDRA field may provide a value K for determining the starting slot of the PUSCH. For example, the value K is in units of slots. For example, terminal device 1 may determine the starting slot as Slot#(n+K). If the DCI format does not include a TDRA field, the value K may be provided by the RRC layer via an RRC parameter.

[0471] In the second type of repetition, K rep Consecutive available slots may be determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols assigned to the instances within the slot does not overlap with any downlink symbols determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols determined by values ​​S and L within the slot does not overlap with any downlink symbols determined by the slot configuration. Values ​​S and L may be provided by the TDRA field in the DCI format. In Figure 16, Slot#n+3 is available in the second type of repetition because the set of OFDM symbols assigned to instance 16001 does not overlap with 9001. In other words, Slot#n+3 is available in the second type of repetition because each OFDM symbol assigned to instance 16001 overlaps with 9002 or 9003. In Figure 16, Slot#n+4 is available in the second type of repetition because the set of OFDM symbols assigned to instance 16002 does not overlap with 9001. In other words, Slot#n+4 is available for a second type of repetition because each OFDM symbol assigned to instance 16002 overlaps with 9003. In Figure 16, Slot#n+5 is not available for a second type of repetition because the set of OFDM symbols determined by values ​​S and L overlaps with 9011. In other words, Slot#n+5 is not available for a second type of repetition because some of the OFDM symbols determined by values ​​S and L do not overlap with 9002 or 9003.

[0472] The RV sequence may be provided to terminal device 1 for a second type of repetition. For example, the sequence may be provided by the RRC layer via RRC parameters. When the RV sequence is provided for a second type of repetition, the sequence contains (mod(n,N s The value of the )+1)th is n It can be assigned to the nth instance. Here, the index can be provided to each instance of PUSCH in ascending order in the time domain.

[0473] For example, a first sequence of RV and a second sequence of RV may be provided to terminal device 1. For example, the first sequence may be used for a first type of repetition. For example, the second sequence may be used for a second type of repetition.

[0474] For example, a first sequence may be provided by an RRC layer via a first RRC parameter. For example, a second sequence may be provided by an RRC layer via a second RRC parameter different from the first RRC parameter.

[0475] In the second type of iteration, if an instance overlaps with a downlink symbol determined by the slot configuration, the transmission of the instance may be omitted. On the other hand, in the second type of iteration, collision handling with downlink symbols by the slot configuration is K rep Since this is already done in the procedure for determining consecutive available slots, there may be no overlaps between downlink symbols and instances determined by the slot configuration. Therefore, in the case of the second type of iteration, the transmission of instances may not be omitted based on the slot configuration. For example, in the case of the second type of iteration, terminal device 1 may not determine whether or not an instance is omitted based on the slot configuration. For example, terminal device 1 may not perform the process of determining whether or not an instance is omitted based on the slot configuration.

[0476] In the second type of iteration, if the downlink symbol and instance determined by the slot format overlap, the transmission of the instance may be omitted.

[0477] In the second type of iteration, if an instance overlaps with another uplink signal that has a higher priority than the PUSCH, the transmission of the instance may be omitted. For example, the uplink signal may be a second PUSCH that has a higher priority than the PUSCH. For example, the priority of a PUSCH may be provided by the DCI format used to schedule the PUSCH.

[0478] The third type of repetition is K rep Let's assume =3 and explain using Figure 16.

[0479] In the third type of iteration, multiple instances of PUSCH can be assigned to consecutive available slots, starting with the slot determined by the DCI format used to schedule PUSCH.

[0480] In the third type of iteration, consecutive available slots may be determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols assigned to the instances within the slot does not overlap with any downlink symbols determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols determined by the values ​​S and L provided by TDRA in the DCI format within the slot does not overlap with any downlink symbols determined by the slot configuration. In Figure 16, Slot#n+3 is available in the third type of iteration because the set of OFDM symbols assigned to instance 16001 does not overlap with 9001. In other words, Slot#n+3 is available in the third type of iteration because each OFDM symbol assigned to instance 16001 overlaps with 9002 or 9003. In Figure 16, Slot#n+4 is available in the third type of iteration because the set of OFDM symbols assigned to instance 16002 does not overlap with 9001. In other words, Slot#n+4 is available in the third type of iteration because each OFDM symbol assigned to instance 16002 overlaps with 9003. In Figure 16, Slot#n+5 is not available in the third type of iteration because the set of OFDM symbols determined by values ​​S and L overlaps with 9011. In other words, Slot#n+5 is not available in the third type of iteration because some of the OFDM symbols determined by values ​​S and L do not overlap with 9002 or 9003.

[0481] The RV sequence may be provided to terminal device 1 for a third type of repetition. For example, the sequence may be provided by the RRC layer via RRC parameters. When the RV sequence is provided for a third type of repetition, the sequence contains (mod(n,N s The )+1)th value can be assigned to the nth instance. For example, the first sequence of RV and the third sequence of RV can be provided to terminal device 1. For example, the first sequence can be used for a first type of repetition. For example, the third sequence can be used for a third type of repetition.

[0482] For example, a first sequence may be provided by the RRC layer via a first RRC parameter. For example, a third sequence may be provided by the RRC layer via a third RRC parameter different from the first RRC parameter.

[0483] In the third type of iteration, if an instance overlaps with a downlink symbol determined by the slot configuration, the transmission of the instance may be omitted. On the other hand, in the third type of iteration, collision handling with downlink symbols by the slot configuration may have already been performed in the procedure for determining consecutive available slots, so there may be no instances where an instance overlaps with a downlink symbol determined by the slot configuration. Therefore, in the third type of iteration, the transmission of an instance may not be omitted based on the slot configuration. For example, in the third type of iteration, terminal device 1 may not decide whether or not to omit an instance based on the slot configuration. For example, terminal device 1 may not perform the process of deciding whether or not to omit an instance based on the slot configuration.

[0484] In the third type of iteration, if the downlink symbol and instance determined by the slot format overlap, the transmission of the instance may be omitted.

[0485] In a third type of iteration, if an instance overlaps with another uplink signal having a higher priority than the PUSCH, the transmission of the instance may be omitted. For example, the uplink signal could be a second PUSCH having a higher priority than the PUSCH. For example, the priority of a PUSCH may be provided by the DCI format used to schedule the PUSCH.

[0486] In the third type of repetition, the first K rep The instance is determined for PUSCH transmission. For example, if the instance is not omitted, the terminal device will have instances 16001, 16002, and 16003 as the first K rep It can be determined as an instance. For example, if instance 16002 is omitted due to a collision with a high-priority signal, the terminal device will determine that instances 16001, 16003, and 16004 are the first K rep Determined as an instance. For example, if instance 16003 is omitted due to a collision with a high-priority signal, the terminal device will determine instances 16001, 16002, and 16004 as the first K rep Determine it as an instance.

[0487] The fourth type of repetition is K rep Let's assume =3 and explain using Figure 16.

[0488] In the fourth type of iteration, multiple instances of PUSCH can be allocated on consecutively available slots, starting with the slot determined by the DCI format used to schedule PUSCH.

[0489] In the fourth type of iteration, consecutively available slots may be determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols assigned to the instances within the slot does not overlap with any downlink symbols determined by the slot configuration. For example, a slot may be available if the set of OFDM symbols determined by the values ​​S and L provided by TDRA in the DCI format within the slot does not overlap with any downlink symbols determined by the slot configuration. In Figure 16, Slot#n+3 is available in the fourth type of iteration because the set of OFDM symbols assigned to instance 16001 does not overlap with 9001. In other words, Slot#n+3 is available in the fourth type of iteration because each OFDM symbol assigned to instance 16001 overlaps with 9002 or 9003. In Figure 16, Slot#n+4 is available in the fourth type of iteration because the set of OFDM symbols assigned to instance 16002 does not overlap with 9001. In other words, Slot#n+4 is available in the fourth type of iteration because each OFDM symbol assigned to instance 16002 overlaps with 9003. In Figure 16, Slot#n+5 is not available in the fourth type of iteration because the set of OFDM symbols determined by values ​​S and L overlaps with 9011. In other words, Slot#n+5 is not available in the fourth type of iteration because some of the OFDM symbols determined by values ​​S and L do not overlap with 9002 or 9003.

[0490] Before determining the RV for each instance, terminal device 1 can determine whether one or more instances are omitted. For example, if no instances are omitted, terminal device determines that instances 16001, 16002, and 16003 are the first K rep It can be determined as an instance. For example, if instance 16002 is omitted due to a collision with a high-priority signal, the terminal device will determine that instances 16001, 16003, and 16004 are the first K rep Determined as an instance. For example, if instance 16003 is omitted due to a collision with a high-priority signal, the terminal device will determine instances 16001, 16002, and 16004 as the first K rep Determine it as an instance.

[0491] The RV sequence may be provided to terminal device 1 for a fourth type of repetition. For example, the sequence may be provided by the RRC layer via RRC parameters. When the RV sequence is provided for a fourth type of repetition, the sequence contains (mod(n,N s The value of the )+1)th is the first K rep It can be assigned to the nth instance within an instance. For example, the first sequence of RV and the fourth sequence of RV may be provided to terminal device 1. For example, the first sequence may be used for a first type of repetition. For example, the fourth sequence may be used for a fourth type of repetition.

[0492] For example, a first sequence may be provided by the RRC layer via a first RRC parameter. For example, a fourth sequence may be provided by the RRC layer via a fourth RRC parameter different from the first RRC parameter.

[0493] In the fourth type of iteration, if an instance overlaps with a downlink symbol determined by the slot configuration, the transmission of the instance may be omitted. On the other hand, in the fourth type of iteration, collision handling with downlink symbols based on the slot configuration may have already been performed in the procedure for determining continuously available slots, so there may be no instances where an instance overlaps with a downlink symbol determined by the slot configuration. Therefore, in the fourth type of iteration, the transmission of an instance may not be omitted based on the slot configuration. For example, in the case of the fourth type of iteration, terminal device 1 may not decide whether or not to omit an instance based on the slot configuration. For example, terminal device 1 may not perform the process of deciding whether or not to omit an instance based on the slot configuration.

[0494] In the fourth type of iteration, if an instance overlaps with a downlink symbol determined by the slot format, the transmission of the instance may be omitted.

[0495] In the fourth type of iteration, if an instance overlaps with another uplink signal having a higher priority than the PUSCH, the transmission of the instance may be omitted. For example, the uplink signal could be a second PUSCH having a higher priority than the PUSCH. For example, the priority of a PUSCH may be provided by the DCI format used to schedule the PUSCH.

[0496] In the fourth type of repetition, the first K rep The instance is sent for PUSCH transmission.

[0497] Figure 17 is an exemplary configuration of a first type of repetition of PUSCH having a configured grant in multiple slots according to one aspect of this embodiment. In Figure 17, 17010 indicates the period of the configured grant. 17011 indicates the period of the configured grant. Periods 17010 and 17011 are configured periodically. The configured grant occurs at the start OFDM symbol of period 17010. If the configured grant occurs within the start OFDM symbol of period 17010, then the first type of repetition is scheduled in a slot beginning at Slot#n+3, where Slot#n+3 is assumed to contain the start OFDM symbol. 17001 indicates an instance of PUSCH at Slot#n+3, where the value S indicates the start OFDM symbol index in the slot for instance 17001, and the value L indicates the length with respect to the number of OFDM symbols for instance 17001. The five instances indicated by 17002-17006 follow instance 17001. Each instance is mapped into a slot. In Figure 17, the number of repetitions is K. rep It is assumed to be 6.

[0498] Here, PUSCH is associated with period 17010. Additionally, PUSCH is associated with instances 17001 through 17006.

[0499] For example, values ​​S and L may be provided by the RRC layer via RRC parameters. For example, values ​​S and L may be provided by TDRA fields in the DCI format that activate the configured grant operation.

[0500] 17007 represents another instance of PUSCH. Instance 17007 is not part of a repetition of PUSCH in period 17010. Instance 17007 is the first instance of another PUSCH in period 17011. Here, a period can define a time opportunity that includes a number of repetitions of a single PUSCH. For example, if two instances are in different periods, the two instances are associated with different PUSCHs.

[0501] Here, another PUSCH is associated with period 17011. Another PUSCH is associated with instances 17001-17006.

[0502] A PUSCH that has instances occurring within a period is associated with the period. A PUSCH is associated with an instance.

[0503] In Figure 17, S applies to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within a slot. In Figure 17, L applies to all instances of PUSCH. For example, all instances apply the same length with respect to the number of OFDM symbols.

[0504] In the first type of iteration, multiple instances of PUSCH are placed in consecutive slots K, starting from the slot containing the OFDM symbol that marks the beginning of the period. rep It can be assigned to

[0505] Figure 18 is an exemplary configuration of a second type of iteration of PUSCH having a configured grant in multiple slots according to one aspect of this embodiment. In Figure 18, 18001 represents an instance of PUSCH in Slot #n+3, where the value S indicates the starting OFDM symbol index in the instance's slot, and the value L indicates the length of the instance in terms of the number of OFDM symbols. Two instances, indicated by 18002 and 18003, follow instance 18001. Each instance is mapped within a slot.

[0506] In Figure 18, the number of repetitions is K. rep It is assumed that it is 4. On the other hand, instance 18004 is not associated with PUSCH. Instance 18004 is the first instance associated with another PUSCH within period 17011.

[0507] For example, in the case of the second type of repetition, the set of PUSCH instances associated with the period is several K. rep And it can be determined based on the period. For example, if an instance of PUSCH is outside the period associated with PUSCH, the instance may be excluded from the set of instances of PUSCH. For example, K rep This indicates the maximum number of instances for PUSCH, and the number of instances is several tens of thousands. rep Instances are mapped within the time period so as not to exceed it.

[0508] In Figure 18, the value S is applied to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within the slot. In Figure 18, the value L is applied to all instances of PUSCH. For example, all instances apply the same length with respect to the number of OFDM symbols.

[0509] In the second type of iteration, multiple instances of PUSCH may be assigned to consecutive available slots, starting with the slot containing the start OFDM symbol for the period associated with PUSCH.

[0510] The third type of repetition is K rep Let's assume =4 and explain using Figure 18.

[0511] In the third type of iteration, multiple instances of PUSCH may be assigned to consecutive available slots, starting with the slot containing the start OFDM symbol for the period associated with PUSCH.

[0512] For example, in the case of the third type of repetition, the set of PUSCH instances associated with the period is several K. rep And it can be determined based on the period. For example, if an instance of PUSCH is outside the period associated with PUSCH, the instance may be excluded from the set of instances of PUSCH. For example, K rep This indicates the maximum number of instances for PUSCH, and the number of instances is several tens of thousands. rep Instances are mapped within the time period so as not to exceed it.

[0513] The fourth type of repetition is K rep Let's assume =4 and explain using Figure 16.

[0514] In the fourth type of iteration, multiple instances of PUSCH may be assigned to consecutive available slots, starting with the slot containing the OFDM symbol for the period associated with PUSCH.

[0515] Figure 19 shows an example of a method for the UE. This method may include obtaining a first RRC parameter (step 1901) and sending PUSCH in multiple slots (step 1902). If the first RRC parameter is set to a first value, the conditions in the slot formatting procedure may not be used to determine the multiple slots. If the first RRC parameter is set to a second value, the conditions in the slot formatting procedure may be used to determine the multiple slots.

[0516] Figure 20 shows an example of a method for a base station. This method may include transmitting a first RRC parameter (step 2001) and receiving PUSCH on multiple slots (step 2002). If the first RRC parameter is set to a first value, the conditions in the slot formatting procedure may not be used to determine the multiple slots. If the first RRC parameter is set to a second value, the conditions in the slot formatting procedure may be used to determine the multiple slots.

[0517] There are two types of transmissions without dynamic grants. One is configured grant type 1, where the uplink grant is provided by the RRC and stored as a configured uplink grant; the other is configured grant type 2, where the uplink grant is provided by the PDCCH and stored or cleared as a configured uplink grant based on L1 signaling indicating the activation or deactivation of the configured uplink grant. Types 1 and 2 are configured by the RRC of the serving cell per BWP. Multiple configurations can be active simultaneously within the same BWP. In the case of type 2, activation and deactivation are independent between serving cells. For the same BWP, a MAC entity can be configured in both type 1 and type 2.

[0518] The RRC configures the following parameters when a configured grant type 1 is configured: cs-RNTI is used to determine the CS-RNTI for retransmission. Periodicity is used to determine the periodicity of the configured grant type 1. timeDomainOffset is used to determine the resource offset in the time domain with respect to SFN=timeReferenceSFN. timeDomainAllocation is used to determine the allocation of the configured uplink grant in the time domain, including startSymbolAndLength (i.e., SLIV) or startSymbol. nrofHARQ-Processes is used to determine the number of HARQ processes for the configured grant. harq-ProcID-Offset is used to determine the offset of the HARQ processes for the configured grant to operate with shared spectral channel access. harq-ProcID-Offset2 is used to determine the offset of the HARQ processes for the configured grant. timeReferenceSFN is used to determine the SFN used to determine the resource offset in the time domain. The UE uses the nearest SFN in the indicated number that precedes the reception of the configured grant configuration.

[0519] RRC configures the following parameters when a configured grant type 2 is configured: cs-RNTI is used to determine the CS-RNTI for retransmission. Periodicity is used to determine the periodicity of the configured grant type 2. nrofHARQ-Processes is used to determine the number of HARQ processes of the configured grant. harq-ProcID-Offset is used to determine the offset of the HARQ processes of the configured grant for operation with shared spectral channel access. harq-ProcID-Offset2 is used to determine the offset of the HARQ processes of the configured grant.

[0520] RRC configures the following parameters when configured uplink grant retransmission is configured: cg-RetransmissionTimer is used to determine the duration after a configured grant (re)transmission of a HARQ process when the UE does not need to autonomously retransmit the HARQ process.

[0521] When the upper layer configures a configured grant type 1 for the serving cell's BWP, the MAC entity may need to initialize or reinitialize the configured uplink grant so that it recurs periodically to start with a symbol according to timeDomainOffset, timeReferenceSFN, and S (derived from SLIV or provided by startSymbol), and to start with a symbol according to timeDomainOffset, timeReferenceSFN, and S (derived from SLIV or provided by startSymbol).

[0522] After an uplink grant is configured for configured grant type 1, the MAC entity may need to sequentially consider that Nth (N>=0) uplink grants occur with symbols of the form [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot).

[0523] After an uplink grant is configured for configured grant type 2, the MAC entity may need to sequentially consider that Nth (N>=0) uplink grants occur with symbols of the form [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFNstart time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slotstart time x numberOfSymbolsPerSlot + symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot).

[0524] If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for a configured grant type 1 or type 2, the MAC entity may need to consider that uplink grants will occur in those additional PUSCH allocations specified in the UE procedure(s) to send PUSCHs in resource allocations for uplink transmissions that have configured grants.

[0525] If the available slot-based count is configured for configured grant type 1, the MAC entity may need to consider that the Nth (N>=0) uplink grant occurs in the symbol of [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity)modulo(1024 × numberOfSlotsPerFrame x numberOfSymbolsPerSlot), or in the first symbol of the first available slot specified in the UE procedure(s) associated with the transport block repetition for uplink transmission of PUSCH repetition type A in a post-symbol configured grant.

[0526] If the available slot-based count is configured for configured grant type 2, the MAC entity may need to consider that the Nth (N>=0) uplink grant occurs in the symbol of [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFNstart time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slotstart time x numberOfSymbolsPerSlot + symbolstart time) + N × periodicity] modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot), or in the first symbol of the first available slot specified in the UE procedure(s) associated with the transport block repetition for uplink transmission of PUSCH repetition type A in a post-symbol configured grant.

[0527] The SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, of the first transmission opportunity of PUSCH when the configured uplink grant is (re)initialized.

[0528] For SFNs that are not aligned across carriers within a cell group, the SFNs of the relevant serving cells are used to calculate the occurrence of configured uplink grants.

[0529] When a configured uplink grant is released by an upper layer, it may be necessary to release all corresponding configurations and clear all corresponding uplink grants.

[0530] A MAC entity may need to instruct the multiplexing and assembly procedure to generate a multiple entry configured grant confirmation MAC CE if at least one configured uplink grant confirmation has been triggered and not canceled, and the MAC entity has UL resources allocated for a new transmission, and in this MAC entity, at least one configured uplink grant is configured by configuredGrantConfigToAddModList. Furthermore, the MAC entity may need to instruct the multiplexing and assembly procedure to generate a configured grant confirmation MAC CE. Alternatively, the MAC entity may need to cancel all triggered configured uplink grant confirmations (one or more).

[0531] For Configured Grant Type 2, the MAC entity may need to clear the configured uplink grant(s) immediately after the first transmission of a Configured Grant Confirmation MAC CE or a Configured Grant Confirmation MAC CE with multiple entries, confirming the deactivation of the configured uplink grant(s).

[0532] Retransmission uses a configured uplink grant addressed to CS-RNTI, a received uplink grant, or a repetition of an uplink grant with a configured cg-RetransmissionTimer.

[0533] The MAC entity includes a HARQ entity for each serving cell that has configured uplinks (including if configured with a supplementaryUplink), and it maintains several parallel HARQ processes.

[0534] The number of parallel UL HARQ processes per HARQ entity is specified by the physical layer procedure of the data.

[0535] Each HARQ process supports one TB.

[0536] Each HARQ process is associated with a HARQ process identifier. HARQ process identifier 0 is used for UL transmissions with UL grants in RA responses or for UL transmissions for MSGA payloads.

[0537] When a single DCI is used to schedule multiple pushes, the UE is allowed to internally map the TB(s) generated in the event of an LBT failure(s)(s)(s) to different HARQ processes, i.e., the UE can send new TBs in any HARQ process within a grant that indicates new transmissions to the same TBS, same RV, and NDI.

[0538] The maximum number of TB transmissions in a bundle of dynamic grants or configured grants is given by REPETITION_NUMBER. For dynamic grants, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in the UE procedure associated with the resource allocation in the time domain. For configured grants, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in the UE procedure(s) for sending a PUSCH using the resource allocation for uplink transmissions with configured grants.

[0539] If REPETITION_NUMBER > 1, then after the first send in the bundle, at most REPETITION_NUMBER-1 HARQ retransmissions will continue within the bundle. For both dynamic grants and configured uplink grants, the bundling behavior relies on the HARQ entity to invoke the same HARQ process for each send that is part of the same bundle. Within a bundle, HARQ retransmissions are triggered without waiting for feedback from previous sends according to REPETITION_NUMBER for dynamic grants or configured uplink grants, unless terminated when specified in the UE procedure to send a PUSCH. Each send within a bundle is a separate uplink grant delivered to the HARQ entity.

[0540] The K available slots can be configured based on REPETITION_NUMBER.

[0541] If the UE is configured with the upper-level parameter push-TimeDomainAllocationListForMultiPUSCH, the UE is not assumed to be configured with push-AggregationFactor.

[0542] Figure 21 shows an example of a table of applicable PUSCH time domain resource allocations for the common search space and DCI format 0_0 in the UE-specific search space.

[0543] Figure 22 shows an example of an applicable PUSCH time-domain resource allocation table for DCI format 0_1 ​​in a UE-specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0544] Figure 23 shows an example of a PUSCH time-domain resource allocation table applicable to DCI format 0_2 in a UE-specific search space scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI.

[0545] Figure 24 shows an example of a table for the default PUSCH time domain resource allocation A for a typical CP. The subcarrier interval specific value j is used to determine K2 for a typical CP, in relation to Figure 24.

[0546] Figures 21, 22, and 23 define which PUSCH time-domain resource allocation configuration is applied. Figures 21, 22, and 23 are used to determine the resource allocation table used for PUSCH.

[0547] If a UE is scheduled to send a PUSCH with one or more CSI reports on the DCI using the "CSI Request" field without a transport block, the "Time Domain Resource Allocation" field value m on the DCI provides row index m+1 to the allocated table, as defined in Figures 21, 22, 23, and 24.

[0548] For a PUSCH repeat type A, the starting symbol S for the start of the slot, and the number of consecutive symbols L counted from the symbol S assigned to PUSCH, are determined from the indexed row start and length indicator SLIV.

[0549] For a PUSCH repeat type B, the starting symbol S for the start of the slot and the number of consecutive symbols L counted from the symbol S assigned to PUSCH are provided by the startSymbol and length of the indexed row in the resource allocation table, respectively.

[0550] For a PUSCH iteration of type A, the PUSCH mapping type is set to type A or type B as defined by the mapping to pre-recording and physical resources, as given by the indexed row.

[0551] For PUSCH repeat type B, the PUSCH mapping type is set to type B.

[0552] For PUSCH repetition type A, when sending a PUSCH scheduled by DCI format 0_1 ​​or 0_2 in a PDCCH having a CRC scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, if numberOfRepetitions exists in the resource allocation table, the number of repetitions K is determined as follows: if the number of repetitions K is equal to numberOfRepetitions, if the UE consists of push-AggregationFactor, then the number of repetitions K is equal to push-AggregationFactor, otherwise K=1. The number of slots used for TBS determination N is equal to 1.

[0553] For ampered spectra, if the RRC parameter AvailableSlotCounting is enabled, the UE will determine the number of PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2 based on the RRC parameters tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated and ssb-PositionsInBurst and TDRA information field values ​​in DCI format 0_1 ​​or 0_2. * Determine the K slot. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or with a symbol of an SS / PBCH block having an index provided by ssb-PositionsInBurst, then the slot is N for PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2. * The number of K slots is not counted. Otherwise, the UE will count N for PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2 based on the TDRA information field value in DCI format 0_1 ​​or 0_2. * Determine the K consecutive slots.

[0554] As explained above, there are two counting methods: one is the available slot count (also called the count based on available slots), and the other is the physical slot count (also called the count based on consecutive slots, consecutive slot count, or regular / normal / legacy count). In the available slot count, the N slots after the slot determined by slot offset K2 are counted. * The earliest available slot for K may be determined as the slot for PUSCH transmission. In this case, if at least one of the symbols indicated by the indexed row in the resource allocation table used within the slot (i.e., the symbols indicated by the TDRA field) overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or a symbol of an SS / PBCH block with an index provided by ssb-PositionslnBurst, the slot is not counted as an available slot. The physical slot count starts with the slot determined by slot offset K2. * A K-sequence slot may be designated as a slot for PUSCH transmission, regardless of whether it overlaps with DL symbols or SS / PBCH block symbols. Note that actual transmissions within a slot designated for PUSCH may or may not be further dropped in response to collisions with other channels and / or signals.

[0555] For an ampered spectrum, if the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without a transport block by the "CSI Request" field on the DCI, then the UE will send N PUSCH repetitions of type A scheduled by DCI format 0_1 ​​or 0_2 based on the TDRA information field value in DCI format 0_1 ​​or 0_2. * It is possible to determine the number of consecutive K-slots.

[0556] For an ampered spectrum, if the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without a transport block by the "CSI Request" field on the DCI, then the UE will send N PUSCH repetitions of type A scheduled by DCI format 0_1 ​​or 0_2 with a transport block based on the TDRA information field value in DCI format 0_1 ​​or 0_2. * It is possible to determine the number of consecutive K-slots.

[0557] For ampered spectra, if the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without a transport block by the "CSI Request" field on the DCI, then the UE will send N PUSCH repetitions of type A scheduled by DCI format 0_1 ​​or 0_2 based on the TDRA information field value in DCI format 0_1 ​​or 0_2. * It is possible to determine the number of consecutive K-slots.

[0558] For ampered spectra, if the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without a transport block by the "CSI Request" field on the DCI, then the UE will send a PUSCH with a transport block of type A PUSCH repetition scheduled by DCI format 0_1 ​​or 0_2 based on the TDRA information field value in DCI format 0_1 ​​or 0_2. * It is possible to determine the number of consecutive K-slots.

[0559] For an ampered spectrum, if the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without transport via the "CSI Request" field on the DCI, then the UE will send N PUSCH transmissions of type A PUSCH repetitions scheduled by DCI format 0_1 ​​or 0_2 based on the RRC parameters tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and TDRA information field values ​​in DCI format 0_1 ​​or 0_2. * A K slot can be determined. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or with a symbol of an SS / PBCH block having an index provided by ssb-PositionsInBurst, then the slot is N for PUSCH transmissions having a transport block of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2. * The number of K slots may not be counted.

[0560] For ampered spectra, if the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to send a PUSCH with a CSI report (one or more) without transport via the "CSI Request" field on the DCI, the UE will send N PUSCH transmissions of type A PUSCH repetitions scheduled by DCI format 0_1 ​​or 0_2 based on the RRC parameters tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and TDRA information field values ​​in DCI format 0_1 ​​or 0_2. * A K slot can be determined. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or with a symbol of an SS / PBCH block having an index provided by ssb-PositionsInBurst, then the slot is N for PUSCH transmissions having a transport block of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2. * The number of K slots may not be counted.

[0561] For ampered spectra, the UE performs N for push transmission of TB processing across multiple slots scheduled by DCI format 0_1 ​​or 0_2, based on the tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, ssb-PositionsInBurst, and TDRA information field values ​​within DCI format 0_1 ​​or 0_2. * Determine the K slot. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or with a symbol of an SS / PBCH block having an index provided by ssb-PositionsInBurst, then the slot is for PUSCH transmission of TB processing across multiple slots. * It is not counted in the number of K slots.

[0562] For the ampered spectrum, the UE determines the N for PUSCH transmission of PUSCH repetition type A scheduled by the RAR UL grant, based on the TDRA information field values ​​in tdd-UL-DL-ConfigurationCommon and ssb-PositionsInBurst and RAR UL grant. * Determine the K slot. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon, if provided, or with a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, then the slot is N for PUSCH transmission of PUSCH repetition type A scheduled by RAR UL grant. * It is not counted in the number of K slots.

[0563] For the ampered spectrum, the UE schedules PUSCH transmissions of type A PUSCH repetitions, scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI, based on the TDRA information field value in DCI which schedules tdd-UL-DL-ConfigurationCommon and ssb-PositionslnBurst and PUSCH. * Determine the K slot. If at least one of the symbols indicated by the indexed row of the resource allocation table used in the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon, if provided, or with a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, then the slot is N for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_0 scrambled by TC-RNTI. * It is not counted in the number of K slots.

[0564] For paired spectra and SUL bands, the UE, regardless of whether the RRC parameter AvailableSlotCounting is enabled, based on the TDRA information field value in DCI format 0_1 ​​or 0_2, determines N for PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, or for PUSCH transmissions of TB processing across multiple slots scheduled by DCI format 0_1 ​​or 0_2. * Determines K consecutive slots. In the case of reduced capacity half-duplex UE, if the RRC parameter AvailableSlotCounting is enabled, and at least one of the symbols indicated by the indexed row in the used resource allocation table within the slot overlaps with a symbol in the SS / PBCH block having an index provided by ssb-Positionslnburst, then the slot is for PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, or for PUSCH transmissions of TB processing across multiple slots scheduled by DCI format 0_1 ​​or 0_2. * It is not counted in the number of K slots.

[0565] For paired spectra and SUL bands, the UE, based on the TDRA information field value in the RAR UL grant, will send N PUSCH repetitions of type A PUSCH transmissions scheduled by the RAR UL grant. * Determine the K consecutive slots.

[0566] For paired spectra and SUL bands, the UE schedules PUSCH transmissions of type A PUSCH repetitions in DCI format 0_0 with CRC scrambled by TC-RNTI, based on the TDDA information field value in DCI that schedules PUSCH. * Determine the K consecutive slots.

[0567] The RRC parameter AvailableSlotCounting is enabled, and the UE performs a push or N TB process on multiple slots. * The UE will send a PUSCH repeat type A on slot K, and the UE will send a PUSCH or N for TB processing on multiple slots according to the UE procedure(s) that reports control information, the UE procedure(s) associated with the slot configuration, and the UE procedure(s) associated with the cancellation instruction. * If a PUSCH repeat type A is not sent from slot K, the UE will be N * The number of consecutive slots is counted by the number of K consecutive slots.

[0568] For PUSCH repetition type A, if K > 1, if PUSCH is scheduled by DCI format 0_1 ​​or 0_2, if the RRC parameter AvailableSlotCounting is enabled, N is determined for PUSCH transmission. * The same symbol assignment is applied across K slots, and PUSCH is limited to a single transmit layer. UE is determined for PUSCH transmission. * The TB needs to be repeated across K slots, and the same symbol assignment can be applied to each slot. Otherwise, the same symbol assignment will be N * Applied across K consecutive slots, PUSCH is limited to a single transmit layer. UE applies the same symbol assignment to each slot. * It may be necessary to repeat the TB across K consecutive slots. If PUSCH is scheduled by DCI format 0_0 with a CRC scrambled by RAR UL Grant or TC-RNTI, then N is determined for PUSCH transmission. * The same symbol assignment is applied across K slots, and PUSCH is limited to a single transmit layer. UE is determined for PUSCH transmission. * The TB needs to be repeated across K slots, and the same symbol assignment can be applied to each slot.

[0569] For ampered spectra, for TB processing across multiple slots, and for push transmission, N is determined. * The same symbol assignment is applied across K slots, and PUSCH is limited to a single transmit layer. The UE is determined for PUSCH transmission. * It is necessary to transmit TB across K slots, and the same symbol assignment can be applied to each slot. For paired spectra or auxiliary uplink bands, the same symbol assignment can be applied to N slots. * Applied across K consecutive slots, PUSCH is limited to a single transmit layer. UE applies the same symbol assignment in each slot. * It may be necessary to transmit TB across K consecutive slots.

[0570] For PUSCH transmissions scheduled by DCI format 0_1, 0_2, or 0_0 with CRC scrambled by TC-RNTI, a redundant version (n=0, 1, ..., N) is applied to the nth transmission opportunity of the TB. * K-1) is determined according to Figure 25.

[0571] A redundant version (n=0, 1, ..., N) applied to the nth transmission opportunity of a TB for a PUSCH repetition type A PUSCH transmission scheduled by a RAR UL grant. * K-1) is determined according to the first row of Figure 25.

[0572] For PUSCH repetition type A and TB processing across multiple slots, PUSCH transmissions within a slot of a multi-slot PUSCH transmission are omitted according to the conditions in the UE procedure(s) for reporting control information, the UE procedure(s) associated with the slot configuration, and the UE procedure(s) associated with the cancellation instruction.

[0573] For a PUSCH repeat type B, after determining the invalid symbols(s) for sending a PUSCH repeat type B for each of the K nominal repeats, the remaining symbols are considered potentially valid symbols for sending a PUSCH repeat type B. If the number of potentially valid symbols for sending a PUSCH repeat type B is greater than zero for the nominal repeats, the nominal repeats consist of one or more actual repeats, each actual repeat consisting of a contiguous set of all potentially valid symbols that can be used to send a PUSCH repeat type B in the slot. Actual repeats for a single symbol are omitted except when L=1. Actual repeats are omitted according to conditions in UE procedures(s) for reporting control information, UE procedures(s) associated with slot configuration, and UE procedures(s) associated with cancellation instructions. The UE may need to repeat the TB across actual repeats. The redundant version applied to the nth actual repeat (with a count including the omitted actual repeats) is determined according to Figure 25, where N=1.

[0574] When a UE schedules a non-periodic CSI report(s) or activates a semi-persistent CSI report(s) on a PUSCH without a transport block via the "CSI Request" field on the DCI for a PUSCH repeat type B, the nominal number of repeats is assumed to always be 1, regardless of the value of numberOfReperitions. When a UE is scheduled to send a PUSCH repeat type B without a transport block and with a non-periodic or semi-persistent CSI report(s) via the "CSI Request" field on the DCI, the first nominal repeat is assumed to be the same as the first actual repeat. For PUSCH repetition type B that carries a semi-persistent CSI report without a corresponding PDCCH after being activated by the "CSI Request" field on the DCI, the first nominal repetition is omitted if it is not the same as the first actual repetition; otherwise, the first nominal repetition is omitted according to the conditions in the UE procedure(s) for reporting control information, the UE procedure associated with slot configuration, and the UE procedure(s) associated with cancellation instructions.

[0575] For a PUSCH repeat type B, if the UE schedules the PUSCH to send a transport block and a non-periodic CSI report(s) via the "CSI Request" field on the DCI, the CSI report(s) will be multiplexed only in the first actual repeat. The UE does not assume that the first actual repeat has a single symbol duration.

[0576] If the push-TimeDomainAllocationListForMultiPUSCH in push-Config contains rows indicating resource allocations for 2 to 8 consecutive PUSCHs, K2 indicates the slot where the UE should send the first PUSCH of multiple PUSCHs. Each PUSCH has a distinct SLIV and mapping type. The number of scheduled PUSCHs is signaled by the number of valid SLIVs indicated in the rows of push-TimeDomainAllocationListForMultiPUSCH, which are signaled in DCI format 0_1.

[0577] For push-TimeDomainAllocationListForMultiPUSCH-r17 within push-Config, each PUSCH has a separate SLIV, mapping type, and K2. The number of scheduled PUSCHs is signaled by the number of SLIVs indicated in the row of push-TimeDomainAllocationListForMultiPUSCH-r17, which is signaled in DCI format 0_1.

[0578] For both Type 1 and Type 2 PUSCH transmissions with configured grants, when K > 1, and for ampered spectra, if the RRC parameter AvailableSlotCount is enabled, the UE determines N for PUSCH transmissions that apply the same symbol assignment within each slot. * It may be necessary to repeat TB across K slots. A slot is not counted in the number of NK slots if at least one of the symbols indicated by the indexed row in the used resource allocation table within the slot overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided, or with a symbol of an SS / PBCH block with an index provided by ssb-PositionslnBurst. Otherwise, the UE applies the same symbol allocation to each slot unless the UE is provided with the higher-tier parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat the TB across K consecutive slots, in which case the UE repeats the TB at the earliest consecutive transmission opportunity candidate for repK within the same configuration.

[0579] For both Type 1 and Type 2 PUSCH transmissions with configured grants, when K > 1, the UE applies the same symbol assignment to each slot for paired spectra, regardless of whether AvailableSlotCount is enabled, unless the UE provides the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot. * It may be necessary to repeat TB across K consecutive slots, in which case the UE repeats TB at the earliest consecutive transmission opportunity of repK within the same configuration. If the RRC parameter AvailableSlotCounting is enabled, for a reduced-capacity half-duplex UE, if at least one of the symbols indicated by the indexed row in the used resource allocation table within a slot overlaps with a symbol in an SS / PBCH block with an index provided by ssb-PositionslnBurst, the slot is N * It is not counted in the number of K slots.

[0580] Type 1 or Type 2 PUSCH transmissions with configured grants in a slot are omitted according to the conditions of the UE procedure(s) for reporting control information, the UE procedure(s) associated with slot configuration, and the UE procedure(s) associated with cancellation instructions.

[0581] For PUSCH without UL-SCH and / or PUSCH with only CSI, N=1 and K=1 can be assumed using the procedure described above. The UE and base station in this case will be explained.

[0582] The UE may include upper-layer processing circuitry configured to acquire at least a first RRC parameter to indicate whether the available slot count is valid or invalid. The first RRC parameter is named AvailableSlotCounting. Possible values ​​for the first RRC parameter may be "valid" and "invalid". The UE may also include receiving circuitry configured to receive a DCI format (e.g., DCI format 0_1 ​​or DCI format 0_2) for scheduling PUSCHs. This may also be described as the receiving circuitry being able to monitor and detect PDCCHs carrying the DCI format. The UE may also include transmitting circuitry configured to transmit PUSCHs on one or more slots scheduled by the DCI format. The UE may transmit PUSCHs upon detection of PDCCHs using the DCI format that schedules the PUSCHs.

[0583] A base station communicating with a UE may include a function associated with a function on the UE side and may perform processes associated with processes on the UE side. The base station (also referred to as a gNB) may include upper-layer processing circuitry configured to transmit at least a first RRC parameter to indicate whether the available slot count is valid. The base station may also include transmitting circuitry configured to transmit a DCI format (e.g., DCI format 0_1 ​​or DCI format 0_2) for scheduling PUSCHs. This may also be described as the transmitting circuitry being able to transmit a PDCCH carrying the DCI format. The base station may also include receiving circuitry configured to receive PUSCHs in one or more slots scheduled by the DCI format. The base station may monitor and receive PUSCHs when transmitting a PDCCH using the DCI format that schedules the PUSCHs.

[0584] The DCI format may include multiple information fields. These information fields may include a Time-Domain Resource Allocation field (also known as the TDRA (Time-Domain Resource Allocation) field). These information fields may include a CSI request field. These information fields may include a UL-SCH indicator field. Trigger states can be initiated using the CSI request field in the DCI. If all bits of the CSI request field in the DCI are set to zero, no CSI is requested. Each of the other values ​​in the CSI request field in the DCI corresponds to and may indicate a respective trigger state. Each trigger state may include a list of associated CSI-ReportConfigs indicating the channel's resource set ID and optionally the resource set ID for interference. A value of "1" set in the UL-SCH indicator field may indicate that the UL-SCH is transmitted over PUSCH, and a value of "0" in the UL-SCH indicator field may indicate that the UL-SCH is not transmitted over PUSCH. In other words, a value of "1" set in the UL-SCH indicator field may indicate that at least one transport block is included in PUSCH, while a value of "0" set in the UL-SCH indicator field may indicate that no transport block is included in PUSCH. The value of the UL-SCH indicator field may only be set to "0" if the trigger condition is initiated using the CSI request field in DCI, except in the case of no CSI request.

[0585] If the first RRC parameter indicates that the available slot count is valid and that PUSCH is transmitted in ampered spectrum, the UE can determine, based on a metric, whether to use the available slot count. The metric may be whether or not the transport block is included in the PUSCH. For example, if the transport block is included in the PUSCH, the available slot count is used; if the transport block is not included in the PUSCH, the physical slot count is used. In other words, based on whether or not the transport block is included in the PUSCH, the UE can determine whether or not a first slot in which at least one of the symbols indicated by the TDRA field overlaps with a DL symbol or a symbol in an SS / PBCH block is not counted as a second slot for transmitting the PUSCH. For example, if the transport block is included in the PUSCH, the first slot is not counted as a second slot; if the transport block is not included in the PUSCH, the first slot is counted as a second slot.

[0586] Alternatively or additionally, the metric may be whether the value of the UL-SCH index field is set to "1" or "0". For example, if the value of the UL-SCH index field in DCI is set to "1", the available slot count is used, and if the value of the UL-SCH index field in DCI is set to "0", the physical slot count is used.

[0587] Alternatively or additionally, the metric could be whether the value of the CSI Request field indicates a different trigger state without a CSI Request. For example, if the value of the CSI Request field indicates a different trigger state other than no CSI Request, the available slot count is used; if the value of the CSI Request field indicates a state corresponding to no CSI Request, the physical slot count is used.

[0588] Alternatively or additionally, the metric could be whether the PUSCH is for CSI only or not. For example, if the PUSCH is not for CSI only, the available slot count is used, and if the PUSCH is for CSI only, the physical slot count is used.

[0589] These methods could lead to the unification of the processing of push transmissions for CSIs with and without the AvailableSlotCounting configuration, and thus reduce the complexity of processing for aperiodic CSI reports.

[0590] If the upper-layer processing circuit does not obtain a first RRC parameter indicating that the available slot count is enabled, the UE can always use the physical slot count. In other words, if the upper-layer processing circuit does not obtain a first RRC parameter indicating that the available slot count is enabled, the UE can determine that the first slot is counted as the second slot, regardless of whether the transport block is included in the PUSCH. If the PUSCH is transmitted in a paired spectrum, the UE can always use the physical slot count. In other words, if the PUSCH is transmitted in a paired spectrum, the UE can determine that the first slot is counted as the second slot, regardless of whether the transport block is included in the PUSCH.

[0591] Alternatively, if the first RRC parameter indicates that the available slot count is valid and that the PUSCH is transmitted in an ampered spectrum, the UE can use the available slot count to determine the slot for transmitting a PUSCH with a periodic CSI report without a transport block. This is the same as in the case of transmitting a PUSCH with a transport block and a periodic CSI report, or in the case of multi-slot transmission of a PUSCH with a transport block.

[0592] This method could lead to the unification of the processing of available slot counts for push transmissions with transport blocks and push transmissions with only CSIs, and thus the complexity of processing related to slot counts can be reduced.

[0593] Further details of the UE procedure(s) for applying conversion precoding to PUSCH are described.

[0594] In the case of a PUSCH scheduled by a RAR UL grant, or a PUSCH scheduled by a fallbackRAR UL grant, or a PUSCH scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI, the UE shall consider the transform precoding to be either "enabled" or "disabled" according to the configured parameter msg3-transformPrecoder.

[0595] In the case of MsgA PUSCH, the UE shall consider the transformation precoding to be either "enabled" or "disabled" according to the higher-level configured parameter msgA-TransformPrecoder. If the RRC parameter msgA-TransformPrecoder is not configured, the UE shall consider the transformation precoding to be either "enabled" or "disabled" according to the RRC parameter msg3-transformPrecoder.

[0596] The RRC parameter msgA-TransformPrecoder indicates whether the UE enables or disables the transformation precoder for MsgA transmission.

[0597] In the case of a PUSCH transmission scheduled with a CS-RNTI, C-RNTI, or PDCCH having a CRC scrambled with MCS-C-RNTI or SP-CSI-RNTI having NDI=1, if a DCI with a scheduling grant is received in DCI format 0_0, the UE shall consider the transformation precoding to be either enabled or disabled in the case of this PUSCH transmission, according to the RRC parameter msg3-transformPrecoder.

[0598] For a PUSCH transmission scheduled with a CS-RNTI, C-RNTI, or PDCCH having a scrambled CRC with NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is configured with the RRC parameter transformPrecoder in push-Config, the UE shall, for this PUSCH transmission, either enable or disable transform precoding according to this parameter (i.e., the configured transformPrecoder).

[0599] For PUSCH transmissions scheduled with a PDCCH having a CRC scrambled with CS-RNTI, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI having NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is configured with the RRC parameter transformPrecoder and dynamicSwitchingTransformPrecoder set to "disabled" in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the RRC parameter transformPrecoder.

[0600] The statement "DCI with a scheduling grant was not received in DCI format 0_0" could mean "DCI with a scheduling grant was received in a DCI format other than DCI format 0_0." Alternatively, "DCI with a scheduling grant was not received in DCI format 0_0" could mean "the scheduling grant was received in configured grant format."

[0601] The RRC parameter dynamicSwitchingTransformPrecoder indicates whether the "Transform Precoding Indicator" field is included in DCI format 0_1 / 0_2. The "Transform Precoding Indicator" field is used to indicate whether the transform precoder is enabled.

[0602] The RRC parameter dynamicSwitchingTransformPrecoder can be configured as a common parameter for different DCI formats.

[0603] The RRC parameter dynamicSwitchingTransformPrecoder can be configured for DCI format 0_1 ​​and DCI format 0_2, respectively. In other words, an RRC parameter dynamicSwitchingTransformPrecoder can be configured for each DCI format. If the UE is configured with an RRC parameter dynamicSwitchingTransformPrecoder for each DCI format, the UE can assume that the "Transform Precoding Indicator" field may be included in the corresponding DCI format(s).

[0604] If the RRC parameter dynamicSwitchingTransformPrecoder indicates that it is "enabled," the "Transform Precoding Indicator" field may be included in DCI format 0_1 / 0_2. If the RRC parameter dynamicSwitchingTransformPrecoder indicates that it is "disabled," the "Transform Precoding Indicator" field may not be included in DCI format 0_1 / 0_2.

[0605] If the RRC parameter dynamicSwitchingTransformPrecoder is configured, the UE can assume that the "Transform Precoding Indicator" field may contain DCI format 0_1 / 0_2. The RRC parameter dynamicSwitchingTransformPrecoder may indicate that the "Transform Precoding Indicator" field, if provided, contains DCI format 0_1 / 0_2.

[0606] If the RRC parameter dynamicSwitchingTransformPrecoder is not configured or is absent, the UE may assume that the "Transform Precoding Indicator" field may not contain DCI format 0_1 / 0_2.

[0607] For PUSCH transmissions scheduled with a PDCCH having a CRC scrambled with CS-RNTI, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI having NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is configured with the RRC parameter transformPrecoder, dynamicSwitchingTransformPrecoder set to "Enabled" in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the DCI "Transform Precoding Indicator" field.

[0608] Alternatively, in the case of a PUSCH transmission scheduled with a CS-RNTI, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI having NDI=1 and a CRC scrambled with PDCCH, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is configured with the RRC parameter transformPrecoder and dynamicSwitchingTransformPrecoder set to "Enabled" in push-Config, the UE shall, for this PUSCH transmission, consider the transform precoding to be either enabled or disabled according to the DCI "Transform Precoding Indicator" field, regardless of the value of transformPrecoder.

[0609] Alternatively, in the case of a PUSCH transmission scheduled with a CS-RNTI, C-RNTI, or PDCCH having a scrambled CRC with NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is configured with the RRC parameter transformPrecoder set to "Enabled" and dynamicSwitchingTransformPrecoder set to "Enabled" in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the DCI "Transform Precoding Indicator" field.

[0610] UE can assume that the DCI "Conversion Precoding Indicator" field is not included in DCI Format 0_0.

[0611] For PUSCH transmissions scheduled with a CS-RNTI, C-RNTI, or PDCCH having a scrambled CRC with NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is not configured with the RRC parameter transformPrecoder in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission according to the RRC parameter msg3-transformPrecoder.

[0612] For PUSCH transmissions scheduled with a PDCCH having a CRC scrambled with CS-RNTI, C-RNTI, or MCS-C-RNTI or SP-CSI-RNTI having NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is not configured with the RRC parameter transformPrecoder and dynamicSwitchingTransformPrecoder set to "enabled" in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the higher-layer configured parameter msg3-transformPrecoder.

[0613] For PUSCH transmissions scheduled with a CS-RNTI, C-RNTI, or PDCCH having a CRC scrambled with MCS-C-RNTI or SP-CSI-RNTI having NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, and the UE is not configured with the RRC parameter transformPrecoder in push-Config and dynamicSwitchingTransformPrecoder in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the higher-layer configured parameter msg3-transformPrecoder.

[0614] For PUSCH transmissions scheduled with a CS-RNTI, C-RNTI, or PDCCH having a scrambled CRC with NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder, or if the UE is configured with dynamicSwitchingTransformPrecoder set to "disabled" in push-Config, the UE shall consider the transform precoding to be either enabled or disabled for this PUSCH transmission, according to the RRC parameter msg3-transformPrecoder.

[0615] For PUSCH transmissions scheduled with a CS-RNTI, C-RNTI, or PDCCH having a scrambled CRC with NDI=1, if the DCI with the scheduling grant is not received in DCI format 0_0, if the UE is not configured with transformPrecoder for the RRC parameter in push-Config, or if the UE is configured with dynamicSwitchingTransformPrecoder for the RRC parameter set to "Enabled" in push-Config, the UE shall consider transform precoding to be either enabled or disabled for this PUSCH transmission, according to the DCI "Transform Precoding Indicator" field.

[0616] The characteristics of the DCI "Transform Precoding Indicator" field can be achieved by using DCI fields other than the "Transform Precoding Indicator" field. In other words, if the UE is configured with the RRC parameter dynamicSwitchingTransformPrecoder set to "Enabled" in push-Config, the first value of the first DCI field may indicate that the transform precoder is enabled, and the second value of the first DCI field may indicate that the transform precoder is disabled. The UE can assume that the value(s) of the first DCI field included in the DCI format are associated with whether or not the transform precoder is enabled.

[0617] If the base station provides the RRC parameter dynamicSwitchingTransformPrecoder, which is set to "enabled" in push-Config, the first value of the first DCI field may be set to indicate that the transform precoder is enabled, and the second value of the first DCI field may be set to indicate that the transform precoder is disabled.

[0618] For a push transmission with a configured grant, if the UE is configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE shall consider the enabled or disabled transform precoder for this push transmission according to this parameter.

[0619] For a push transmission with a configured grant, if the UE is configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE shall consider the enabled or disabled transform precoder for this push transmission according to the higher-layer configured parameter msg3-transformPrecoder.

[0620] Here, "dynamicSwitchingTransformPrecoder is configured" can mean the same thing as "dynamicSwitchingTransformPrecoder is configured with 'enabled' enabled." Also, "dynamicSwitchingTransformPrecoder is not configured" can mean the same thing as "dynamicSwitchingTransformPrecoder is configured with 'disabled' enabled."

[0621] If the UE can apply conversion precoding based on a first DCI field indicating whether the conversion precoder is enabled or disabled, and the UE is configured with a first RRC parameter indicating that DCI formats 0_1 and / or 0_2 contain the first DCI field, the UE can assume the number of bits for each of one or more DCI fields based on whether the first DCI field is included in the DCI format(s), and based on that assumption, monitor the DCI format(s). For example, the number of bits for each of the precoding information, the second precoding information field, the antenna port field, the PTRS-DMRS related field, the second PTRS related field, and / or the DMRS sequence initialization field may be determined based on whether the UE is configured with a first RRC parameter indicating that DCI formats 0_1 and / or 0_2 contain the first DCI field.

[0622] For example, if the configured RRC parameter dynamicSwitchingTransformPrecode indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2 (i.e., corresponds to DCI format), then the table to which the DCI size (i.e., number of bits) and / or one or more DCI fields other than the transform precoding indicator field are applied may be determined. One of the one or more DCI fields may be the number of precoding information and layer fields. One of the one or more DCI fields may be a second precoding information field. One of the one or more DCI fields may be an antenna port field. One of the one or more DCI fields may be a PTRS-DMRS related field. One of the one or more DCI fields may be a second PTRS-DMRS related field. One of the one or more DCI fields may be a DMRS sequence initialization field. The UE may monitor the DCI fields(s) based on assumptions. The base station can set the DCI size (number of bits) for each DCI field if the RRC parameter dynamicSwitchingTransformPrecoder indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2.

[0623] In other words, the DCI size of each associated DCI field may be determined / assumed based on whether the dynamicSwitchingTransformPrecoder of the configured RRC parameter indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2.

[0624] For example, if the configured RRC parameter dynamicSwitchingTransformPrecoder indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2, the number of bits and layer fields of the precoding information may be one or more bits, according to a table applied by considering whether the transform precoder is enabled or disabled, based on the RRC parameters txConfig, ul-FullPowerTransmission, maxRank and codebookSubset for DCI format 0_1 ​​or maxRankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2, and the number of antenna ports.

[0625] For example, if the configured RRC parameter dynamicSwitchingTransformPrecoder indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2, the number of bits in the second precoding information field may be one or more bits, according to a table applied by considering whether the transform precoder is enabled or disabled, based on the RRC parameters txConfig, ul-FullPowerTransmission, the values ​​of maxRank and codebookSubset for DCI format 0_1 ​​or maRrankDCI-0-2 and codebookSubsetDCI-0-2 for DCI format 0_2, the number of antenna ports, and the number of the same layers and layer fields indicated by the precoding information.

[0626] For example, if the configured RRC parameter dynamicSwitchingTransformPrecoder indicates that the transform precoding indicator field is included in DCI format 0_1 ​​and / or DCI format 0_2, the number of bits in the antenna port fiel...

Images