User equipment, base station and method

Abstract

A user equipment (UE) is described. The UE can include a higher layer processing circuitry configured to obtain at least a first RRC parameter for indicating whether a transform precoder is enabled and a second RRC parameter for indicating whether a transform precoding indicator field is included in a DCI format, a receiving circuitry configured to receive the DCI format for scheduling of a PUSCH, and a transmitting circuitry configured to transmit the PUSCH.

Description

Technical Field

[0001] This invention relates to user equipment, base stations, and methods. Background Technology

[0002] In the 3rd Generation Partnership Project (3GPP), radio access methods and radio networks for cellular mobile communications (hereinafter referred to as LTE or Evolved Universal Terrestrial Radio Access) have been studied. In LTE (Long Term Evolution), base station equipment is also called Evolved Node B (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, with each area covered by base station equipment. A single base station equipment can manage multiple cells. Evolved Universal Terrestrial Radio Access is also known as E-UTRA.

[0003] Within 3GPP, a next-generation standard (New Radio: NR) has been studied in order to propose a standard for next-generation mobile communication systems as defined by the International Telecommunication Union (ITU)—International Mobile Telecommunications 2020 (IMT-2020). NR is expected to meet the requirements of three scenarios within a single technology framework: enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0004] For example, a wireless communication device may use a communication structure to communicate with one or more devices. However, the communication structure used may only offer limited flexibility and / or efficiency. As this discussion illustrates, systems and methods that improve communication flexibility and / or efficiency may be advantageous. Attached Figure Description

[0005] Figure 1 This is a conceptual diagram of a wireless communication system according to an embodiment of the present disclosure; Figure 2 This illustrates the subcarrier spacing configuration u and the number of OFDM symbols N per time slot according to an embodiment of this disclosure. slot symb Examples of relationships and CP configurations; Figure 3 This is an illustration showing an example of a method for configuring a resource grid according to an embodiment of this disclosure; Figure 4 This is a diagram illustrating an example configuration of a resource grid 3001 according to an embodiment of this disclosure; Figure 5 This is a schematic block diagram illustrating a configuration example of base station equipment 3 according to an embodiment of the present disclosure; Figure 6This is a schematic block diagram illustrating a configuration example of terminal device 1 according to an embodiment of the present disclosure; Figure 7 This is a diagram illustrating an example configuration of the SS / PBCH block according to an embodiment of this disclosure; Figure 8 This is an illustration showing an example of the timing of monitoring the search space set according to an embodiment of this disclosure; Figure 9 This is an exemplary configuration of the frame structure according to an aspect of the embodiments of this disclosure; Figure 10 This is an exemplary configuration of time slot configuration according to an aspect of the embodiments of this disclosure; Figure 11 This is an exemplary configuration of the baseband unit 13 in the wireless transmission unit 10a according to an embodiment of the present disclosure; Figure 12 This is an exemplary configuration of encoder 12000 according to an aspect of the embodiments of this disclosure; Figure 13 This is an example of a bit selection procedure according to an aspect of the embodiments of this disclosure; Figure 14 This is an exemplary configuration of a cyclic buffer according to an aspect of the embodiments of this disclosure; Figure 15 This is an exemplary configuration of the processing timeline according to an aspect of the implementation of this disclosure; Figure 16 This is an exemplary configuration of the processing timeline according to an aspect of the implementation of this disclosure; Figure 17 This is an exemplary configuration of a third type of PUSCH transmission in multiple time slots according to an aspect of the present disclosure; Figure 18 This is an exemplary configuration of multiple instances of a third type of PUSCH transmission in multiple time slots according to an aspect of the present disclosure; Figure 19 Here is an example of a method used for UE; Figure 20 Here is an example of a method used for a base station; Figure 21 This is an example of the applicable PUSCH time-domain resource allocation for DCI format 0_0 in the public search space and the UE-specific search space; Figure 22 This is an example of applicable PUSCH time-domain resource allocation for DCI format 0_1 ​​scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI in a UE-specific search space. Figure 23This is an example of applicable PUSCH time-domain resource allocation for DCI format 0_2 scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI or SP-CSI-RNTI in a UE-specific search space. Figure 24 This is an example of the default PUSCH time-domain resource allocation A for a normal CP; and Figure 25 This is an example of a redundant version of the PUSCH transmission. Detailed Implementation

[0006] This invention describes a User Equipment (UE). The UE may include: a higher-layer processing circuit configured to acquire at least a first RRC parameter and a second RRC parameter, the first RRC parameter indicating whether a transform precoder is enabled, and the second RRC parameter indicating whether a transform precoder indicator field is included in a DCI format; a receiving circuit configured to receive the DCI format for PUSCH scheduling; and a transmission circuit configured to transmit the PUSCH scheduled by the DCI format, wherein, if the first RRC parameter indicates that the PUSCH is disabled and the second RRC parameter indicates that the transform precoder indicator field is included in the DCI format, the transmission circuit is configured to apply transform precoding based on the value of the transform precoder indicator field in the DCI format for the transmission of the PUSCH.

[0007] This invention describes a base station. The base station may include: a higher-layer processing circuit configured to provide at least a first RRC parameter and a second RRC parameter, the first RRC parameter indicating whether a transform precoder is enabled, and the second RRC parameter indicating whether a transform precoder indicator field is included in the DCI format; a transmission circuit configured to transmit the DCI format for PUSCH scheduling; and a receiving circuit configured to receive the PUSCH scheduled by the DCI format, wherein, if the first RRC parameter indicates that the PUSCH is disabled and the second RRC parameter indicates that the transform precoder indicator field is included in the DCI format, the transmission circuit is configured to transmit the DCI format including the transform precoder indicator field, and the receiving circuit is configured to receive the PUSCH with transform precoding applied based on the value of the transform precoder indicator field in the DCI format.

[0008] A method for a User Equipment (UE) is described. The method may include: acquiring at least a first RRC parameter and a second RRC parameter, the first RRC parameter indicating whether a transform precoder is enabled, and the second RRC parameter indicating whether a transform precoder indicator field is included in a DCI format; receiving the DCI format for scheduling a PUSCH; and transmitting the PUSCH scheduled by the DCI format, wherein, if the first RRC parameter indicates that the transform precoder is disabled and the second RRC parameter indicates that the transform precoder indicator field is included in the DCI format, transform precoding is applied for the transmission of the PUSCH based on the value of the transform precoder indicator field in the DCI format.

[0009] "Configured available slot-based counting (PUSCH repeat count)" can be expressed as "Configured to be enabled slot-based counting (PUSCH repeat count)" or "Slot-based counting (PUSCH repeat count) enabled" or "RRC parameter AvailableSlotCounting enabled".

[0010] "No available slot-based counting (PUSCH repeat count) is configured" can be expressed as "Slot-based counting (PUSCH repeat count) is configured to be disabled" or "Slot-based counting (PUSCH repeat count) is disabled" or "The RRC parameter used to indicate the available slot-based counting (PUSCH repeat count) is not configured" or "The RRC parameter AvailableSlotCounting is disabled".

[0011] `floor(CX)` can be the floor function for the real number CX. For example, `floor(CX)` can be a function that provides the largest integer not exceeding the range of the real number CX. `ceil(DX)` can be the ceiling function for the real number DX. For example, `ceil(DX)` can be a function that provides the smallest integer not less than the range of 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 of EX divided by FX. It is exp(GX) = e^GX. Here, e is the Napier constant. `(HX)^(IX)` indicates that IX is a power of HX.

[0012] In the wireless communication system according to an embodiment of this disclosure, at least OFDM (Orthogonal Frequency Division Multiplexing) is used. An OFDM symbol is a time-domain unit of OFDM. An OFDM symbol comprises at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal during baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) is used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-Extended Orthogonal Frequency Division Multiplexing) is used. DFT-s-OFDM can be given by applying transform precoding to CP-OFDM. CP-OFDM is OFDM using CP (Cyclic Prefix).

[0013] The output can be either DFT-s-OFDM or CP-OFDM based on whether a transform precoder (or transform precoding) is enabled. If a transform precoder (or transform precoding) is enabled, DFT-s-OFDM is given. If a transform precoder (or transform precoding) is disabled, CP-OFDM is given. For example, the enabled or disabled transform precoder for PUSCH can be indicated based on the RRC parameter `transformPrecoder` in PUSCH-Config or ConfiguredGrantConfig and / or the `msg3-transformPrecoder` parameter in RACH-ConfigCommon.

[0014] The RRC parameter `transformPrecoder` indicates the UE-specific selection of the transform precoder for the PUSCH. If `transformPrecoder` is absent or not configured, the UE applies the value of `msg3-transformPrecoder` to the transform precoder for the PUSCH.

[0015] The `msg3-transformPrecoder` directs the UE to enable the transformation precoder for Msg3 transmission. If `msg3-transformPrecoder` is provided / configured, the UE enables the transformation precoder for Msg3 transmission. If `msg3-transformPrecoder` is not present / not configured / not provided, the UE disables the transformation precoder for Msg3 transmission.

[0016] An OFDM symbol can be the name of a CP that is added to the OFDM symbol. In other words, an OFDM symbol can be configured to include both the OFDM symbol and the CP that is added to the OFDM symbol.

[0017] Figure 1 This is a conceptual diagram of a wireless communication system according to an embodiment of this disclosure. Figure 1In this context, the wireless communication system includes at least terminal devices 1A to 1C and base station device 3 (BS#3: base station #3). In the following text, terminal devices 1A to 1C are also referred to as terminal device 1 (UE#1: user equipment #1).

[0018] The base station device 3 can be configured to include one or more transmission devices (or transmission points, transmission devices, receiving devices, transmission points, receiving points). When the base station device 3 is configured with multiple transmission devices, each of the multiple transmission devices can be arranged in a different location.

[0019] Base station equipment 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 called a cell.

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

[0021] For example, a resource grid can be provided for a component carrier. For example, a resource grid can be provided for a component carrier and its subcarrier spacing configuration u. The subcarrier spacing configuration u is also called a parameter set. Resource grid N size,u grid,x N RB sc Subcarriers. The resource grid starts from index N. start,u grid It begins with a public resource block. It has index N. start,u grid The public resource blocks are also called the reference points of the resource grid. The resource grid includes N. subframe,u symb One OFDM symbol. The subscript x indicates the transmission direction and whether it is a downlink or uplink. A resource grid is provided for the antenna port p, subcarrier spacing configuration u, and transmission direction x.

[0022] Resource grids are also called carriers.

[0023] N is given at least based on the RRC parameter (e.g., called the RRC parameter CarrierBandwidth). size,u grid,x and N start,u gridThe RRC parameter is used to define one or more SCS (Subcarrier Spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. A component carrier may include one or more SCS specific carriers. SCS specific carriers may be included in the System Information Block (SIB). For each SCS specific carrier, a subcarrier spacing configuration u can be provided.

[0024] Figure 2 This illustrates the subcarrier spacing configuration u and the number N of OFDM symbols per time slot according to an embodiment of this disclosure. slot symb An example of the relationship between CP configuration. Figure 2 In A, 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. Furthermore, in Figure 2 In B, 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, N frame,u slot =40, N subframe,u slot =4.

[0025] In a wireless communication system according to an embodiment of this disclosure, the time unit T c It can be used to represent the length of time. The time unit is T. c For T c =1 / (df) max *N f ). It is df max =480kHz. Its value is Nf = 4096. The constant k is k = df max *N f / (df ref N f,ref ) = 64. df ref It is 15kHz. N f,ref The value is 2048.

[0026] Signal transmission in the downlink and / or uplink can be organized into lengths of T. f Radio frames (system frames, frames). It is a T f =(df max N f / 100)*T s= 10ms. A radio frame is configured to consist of ten subframes. The subframe length is T. sf =(df max Nf / 1000)T s = 1ms. The number of OFDM symbols in each subframe is N. subframe,u symb =N slot symb N subframe,u slot .

[0027] For the subcarrier spacing configuration u, the number and index of time slots included in the subframe can be given. For example, time slot index n u s It can be given in ascending order in the subframe, with values ​​from 0 to N. subframe,u slot Integer values ​​within the range of -1. For the subcarrier spacing configuration u, the number of time slots included in the radio frame and the index of the time slots included in the radio frame can be given. Additionally, the time slot index n... u s,f It can be given in ascending order in radio frames, having numbers from 0 to N. frame,u slot Integer values ​​within the range of -1. Consecutive N... slot symb One OFDM symbol can be included in one time slot. It is N slot symb =14.

[0028] Figure 3 This is an illustration of an example of a method for configuring a resource grid according to an embodiment of this disclosure. Figure 3 The horizontal axis in the diagram indicates the frequency domain. Figure 3 The subcarrier spacing configuration u = u in component carrier 300 is shown. i Examples of resource grid configurations, and examples of resource grid configurations with subcarrier spacing configuration u=u2 in component carriers. One or more subcarrier spacing configurations can be set for component carriers. Although in Figure 3 The assumption is u1 = u2-1, but the various aspects of this implementation scheme are not limited to the condition u1 = u2-1.

[0029] Component carrier 300 is a frequency band with a predetermined width in the frequency domain.

[0030] Point 3000 is an identifier used to identify the subcarrier. Point 3000 is also called point A. The Common Resource Block (CRB) set 3100 is a set of common resource blocks used for the subcarrier spacing configuration u1.

[0031] In the public resource block set 3100, point 3000 is included (by... Figure 3The public resource block (represented by the upper right slash in the block) is also called the reference point of the public resource block set 3100. The reference point of the public resource block set 3100 can be the public resource block with index 0 in the public resource block set 3100.

[0032] 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. Resource grid 3001 includes N starting from the reference point of resource grid 3001. size,u grid1,x A public resource block.

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

[0034] Common resource block set 3200 is a common resource block set concerning subcarrier spacing configuration u2.

[0035] Including point 3000 in the public resource block set 3200 (by... Figure 3 The public resource block (indicated by the upper left slash in the block) is also called the reference point of the public resource block set 3200. The reference point of the public resource block set 3200 can be the public resource block with index 0 in the public resource block set 3200.

[0036] 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 used for subcarrier spacing configuration u = u2. Resource grid 3002 includes N starting from the reference point of resource grid 3002. size,u grid2,x A public resource block.

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

[0038] Figure 4 This is an illustration showing an example configuration of a resource grid 3001 according to an embodiment of this disclosure. Figure 4 In the resource grid, the horizontal axis indicates the OFDM symbol index l sym And the vertical axis indicates the subcarrier index k sc Resource grid 3001 includes N size,u grid1, xN RBsc There are N subcarriers, and include N subframes,u symb One OFDM symbol. Indexed by subcarrier k in the resource grid. sc and OFDM symbol index l sym The specified resource is also called a resource element (RE).

[0039] Resource blocks (RBs) include N RB sc A contiguous subcarrier. A resource block is a common name for common resource blocks, physical resource blocks (PRBs), and virtual resource blocks (VRBs). It consists of N... RB sc =12.

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

[0041] The common resource blocks used for subcarrier spacing configuration u are indexed in ascending order, starting from 0, in the frequency domain. The common resource block with index 0 for subcarrier spacing configuration u includes point 3000 (or conflicts with, matches it). The index n of the common resource block relative to subcarrier spacing configuration u... u CRB Satisfying n u cRB =ceil(k sc / N RB sc The relationship is k. sc A subcarrier with a center frequency of 0 is a subcarrier whose center frequency is the same as that of the subcarrier corresponding to point 3000.

[0042] The physical resource blocks used for subcarrier spacing configuration u are indexed in the frequency domain of the BWP, starting from 0 and in ascending order. The index n of the physical resource block relative to the subcarrier spacing configuration u... u pRB Satisfying n u cRB =n u pRB +N start,u BWP,i The relationship. N start ,u BWP,i Indicates the reference point of the BWP with index i.

[0043] A BWP is defined as a subset of common resource blocks included in a resource grid. A BWP includes resources from reference point N. start ,u BWP,i The beginning of Nsize,u BWP,i A common resource block. The BWP of the downlink component carrier is also called the downlink BWP. The BWP of the uplink component carrier is also called the uplink BWP.

[0044] An antenna port is defined as the channel on which symbols are transmitted, which can be inferred from the channel on which another symbol is transmitted at the same antenna port. 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 cell. For example, a symbol may correspond to a resource element.

[0045] If the large-scale performance of a symbol-transmitted channel on one antenna port can be inferred from the symbol-transmitted channel on another antenna port, then the two antenna ports can be said to have a QCL (quasi-co-bit). This large-scale property includes one or more of the following: delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameter.

[0046] Carrier aggregation can enable communication using multiple aggregated serving cells. Carrier aggregation can also be communication using multiple aggregated link component carriers. Carrier aggregation can be communication using multiple aggregated downlink component carriers. Carrier aggregation can also be communication using multiple aggregated uplink component carriers.

[0047] Figure 5 This is a schematic block diagram illustrating an example configuration of base station equipment 3 according to an embodiment of this disclosure. Figure 5 As shown, the base station device 3 includes at least some or all of a wireless transmission / reception unit (physical layer processing unit) 30 and a higher layer processing unit 34. The wireless transmission / reception unit 30 includes at least some or all of an antenna unit 31, an RF unit 32 (radio frequency unit 32), and a baseband unit 33. The higher layer processing unit 34 includes at least some or all of a media access control layer processing unit 35 and a radio resource control (RRC) layer processing unit 36.

[0048] The wireless transmission / reception unit 30 includes at least some or all of the wireless transmission unit 30a and the wireless reception unit 30b. The configuration of the baseband unit 33 included in the wireless transmission unit 30a and the configuration of the baseband unit 33 included in the wireless reception unit 30b may be the same or different. The configuration of the RF unit 32 included in the wireless transmission unit 30a and the configuration of the RF unit 32 included in the wireless reception unit 30b may be the same or different. The configuration of the antenna unit 31 included in the wireless transmission unit 30a and the configuration of the antenna unit 31 included in the wireless reception unit 30b may be the same or different.

[0049] The higher-layer processing unit 34 provides downlink data (transmission blocks) to the wireless transmission / reception unit 30 (or the wireless transmission unit 30a). The higher-layer processing unit 34 performs processing at the Media Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and / or RRC layer.

[0050] The Media Access Control layer processing unit 35, which is included in the high-level processing unit 34, performs MAC layer processing.

[0051] The Radio Resource Control (RRC) layer processing unit 36, included in the higher-layer processing unit 34, performs RRC layer processing. The RRC layer processing unit 36 ​​manages various configuration information / parameters (RRC parameters) of the terminal device 1. The RRC layer processing unit 36 ​​configures the RRC parameters based on the RRC messages received from the terminal device 1.

[0052] The wireless transmission / reception unit 30 (or wireless transmission unit 30a) performs processes such as encoding and modulation. The wireless transmission / reception unit 30 (or wireless transmission unit 30a) generates a physical signal by encoding and modulating downlink data. The wireless transmission / reception unit 30 (or wireless transmission unit 30a) converts the OFDM symbols in the physical signal into a time-continuous signal, thereby converting it into a baseband signal. The wireless transmission / reception unit 30 (or wireless transmission unit 30a) transmits the baseband signal (or physical signal) to the terminal device 1 via radio frequency. The wireless transmission / reception unit 30 (or wireless transmission unit 30a) can arrange the baseband signal (or physical signal) on component carriers and transmit the baseband signal (or physical signal) to the terminal device 1.

[0053] The wireless transmission / reception unit 30 (or wireless reception unit 30b) performs processes such as demodulation and decoding. The wireless transmission / reception unit 30 (or wireless reception unit 30b) separates, demodulates, and decodes the received physical signals, and provides the decoded information to the higher-layer processing unit 34. The wireless transmission / reception unit 30 (or wireless reception unit 30b) can perform the channel access procedure before the transmission of the physical signals.

[0054] RF unit 32 demodulates the physical signal received via antenna unit 31 into a baseband signal (down-conversion) and / or removes additional frequency components. RF unit 32 provides the processed analog signal to baseband unit 33.

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

[0056] 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 into an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.

[0057] The RF unit 32 removes extra frequency components from the analog signal (a signal on radio frequency) input from the baseband unit 33, up-converts the analog signal into radio frequency, and transmits the signal via the antenna unit 31. The RF unit 32 may have the function of controlling the transmission power. The RF unit 32 is also called a transmission power control unit.

[0058] Terminal device 1 can be configured with at least one or more serving cells (or one or more component carriers, one or more downlink component carriers, and one or more uplink component carriers).

[0059] Each serving cell in the serving cell group for terminal device 1 can be any one of PCell (primary cell), PSCell (primary SCG cell), and SCell (secondary cell).

[0060] PCell is a serving cell included in MCG (Main Cell Group). PCell is the cell (implementing cell) in which terminal device 1 performs the initial connection establishment procedure or connection reconstruction procedure.

[0061] A PSCell is a serving cell included in an SCG (Secondary Cell Group). A PSCell is a serving cell for which random access is performed by terminal device 1 during a synchronized reconfiguration process.

[0062] SCell can be included in either MCG or SCG.

[0063] A serving cell group (cell group) is a name that includes at least an MCG and an SCG. A serving cell group may include 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 can operate via carrier aggregation.

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

[0065] In a set of one or more downlink BWPs used for a serving cell (or downlink component carrier), one downlink BWP can be set as an active downlink BWP (or can activate one downlink BWP). In a set of one or more uplink BWPs used for a serving cell (or uplink component carrier), one uplink BWP can be set as an active uplink BWP (or can activate one uplink BWP).

[0066] The active downlink BWP can receive PDSCH, PDCCH, and CSI-RS. Terminal device 1 can receive PDSCH, PDCCH, and CSI-RS in the active downlink BWP. The active uplink BWP can transmit PUCCH and PUSCH. Terminal device 1 can transmit PUCCH and PUSCH in the active uplink BWP. The active downlink BWP and active uplink BWP are also referred to as the active BWP.

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

[0068] Downlink BWP switching disables the active downlink BWP and activates one of the inactive downlink BWPs, excluding the active one. Downlink BWP switching can be controlled by the BWP field included in the downlink control information. Downlink BWP switching can be controlled based on higher-layer parameters.

[0069] Uplink BWP switching is used to deactivate the active uplink BWP and activate any inactive uplink BWPs other than the active one. Uplink BWP switching can be controlled by the BWP field included in the downlink control information. Uplink BWP switching can be controlled based on higher-layer parameters.

[0070] In the set of one or more downlink BWPs used for the serving cell, two or more downlink BWPs may not be set as active downlink BWPs. For the serving cell, one downlink BWP may be active at a specific time.

[0071] In the set of one or more uplink BWPs used for the serving cell, two or more uplink BWPs may not be set as active uplink BWPs. For the serving cell, one uplink BWP may be active at a specific time.

[0072] Figure 6 This is a schematic block diagram illustrating a configuration example of terminal device 1 according to an embodiment of the present disclosure. Figure 6 As shown, terminal device 1 includes at least some or all of a wireless transmission / reception unit (physical layer processing unit) 10 and a higher layer processing unit 14. The wireless transmission / reception unit 10 includes at least some or all of an antenna unit 11, an RF unit 12, and a baseband unit 13. The higher layer processing unit 14 includes at least some or all of a media access control layer processing unit 15 and a radio resource control layer processing unit 16.

[0073] The wireless transmission / reception unit 10 includes at least some or all of the wireless transmission unit 10a and the wireless reception unit 10b. The configuration of the baseband unit 13 included in the wireless transmission unit 10a and the configuration of the baseband unit 13 included in the wireless reception unit 10b may be the same or different. The configuration of the RF unit 12 included in the wireless transmission unit 10a and the configuration of the RF unit 12 included in the wireless reception unit 10b may be the same or different. The configuration of the antenna unit 11 included in the wireless transmission unit 10a and the configuration of the antenna unit 11 included in the wireless reception unit 10b may be the same or different.

[0074] The higher-layer processing unit 14 provides uplink data (transmission blocks) to the wireless transmission / reception unit 10 (or the wireless transmission unit 10a). The higher-layer processing unit 14 performs processing at the MAC layer, packet data integration protocol layer, radio link control layer, and / or RRC layer.

[0075] The Media Access Control Layer Processing Unit 15, which is included in the High-Level Processing Unit 14, performs MAC layer processing.

[0076] The Radio Resource Control (RRC) layer processing unit 16, included in the higher-layer processing unit 14, performs RRC layer processing. The RRC layer processing unit 16 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The RRC layer processing unit 16 configures the RRC parameters based on the RRC messages received from the base station device 3.

[0077] The wireless transmission / reception unit 10 (or wireless transmission unit 10a) performs processes such as encoding and modulation. The wireless transmission / reception unit 10 (or wireless transmission unit 10a) generates a physical signal by encoding and modulating uplink data. The wireless transmission / reception unit 10 (or wireless transmission unit 10a) converts the OFDM symbols in the physical signal into a time-continuous signal, thereby converting it into a baseband signal. The wireless transmission / reception unit 10 (or wireless transmission unit 10a) transmits the baseband signal (or physical signal) to the base station equipment 3 via radio frequency. The wireless transmission / reception unit 10 (or wireless transmission unit 10a) can arrange the baseband signal (or physical signal) on the BWP (active uplink BWP) and transmit the baseband signal (or physical signal) to the base station equipment 3.

[0078] The wireless transmission / reception unit 10 (or wireless reception unit 10b) performs processes such as demodulation and decoding. The wireless transmission / reception unit 10 (or wireless reception unit 10b) can receive physical signals in the BWP (Active Downlink BWP) of the serving cell. The wireless transmission / reception unit 10 (or wireless reception unit 10b) separates, demodulates, and decodes the received physical signals, and provides the decoded information to the higher-layer processing unit 14. The wireless transmission / reception unit 10 (or wireless reception unit 10b) can perform channel access procedures before the transmission of physical signals.

[0079] RF unit 12 demodulates the physical signal received via antenna unit 11 into a baseband signal (down-conversion) and / or removes additional frequency components. RF unit 12 provides the processed analog signal to baseband unit 13.

[0080] The baseband unit 13 converts the analog signal (signal on radio frequency) input from the RF unit 12 into a digital signal (baseband signal). The baseband unit 13 separates the portion corresponding to the CP from the digital signal, performs a fast Fourier transform on the digital signal with the CP removed, and provides the physical signal in the frequency domain.

[0081] 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 digital signals (baseband signals), and converts the digital signals into analog signals. Baseband unit 13 provides analog signals to RF unit 12.

[0082] RF unit 12 removes extra frequency components from the analog signal (signal on radio frequency) input from baseband unit 13, up-converts the analog signal to radio frequency, and transmits the signal via antenna unit 11. RF unit 12 may have the function of controlling transmission power. RF unit 12 is also called transmission power control unit.

[0083] The physical signal (signal) will be described below.

[0084] Physical signal is a general term encompassing downlink physical channel, uplink physical channel, and uplink physical channel. Physical channel is a general term encompassing both downlink and uplink physical channels.

[0085] The uplink physical channel may correspond to a set of resource elements carrying information and / or uplink control information originating from higher layers. The uplink physical channel may be a physical channel used in uplink component carriers. The uplink physical channel may be transmitted by terminal device 1. The uplink physical channel may be received by base station device 3. In a wireless communication system according to an embodiment of this disclosure, at least some or all of PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), and PRACH (Physical Random Access Channel) may be used.

[0086] PUCCH can be used to transmit uplink control information (UCI). A PUCCH can be sent to deliver (transmit, transmit) uplink control information. Uplink control information can be mapped to (or placed in) a PUCCH. Terminal device 1 can transmit a PUCCH containing uplink control information. Base station device 3 can receive a PUCCH containing uplink control information.

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

[0088] Channel state information is transmitted using channel state information bits or channel state information sequences. Scheduling requests are also called scheduling request bits or scheduling request sequences. HARQ-ACK information is also called HARQ-ACK information bits or HARQ-ACK information sequences.

[0089] HARQ-ACK information may include HARQ-ACK states corresponding to transport blocks (TB: Transport Block, MAC PDU: Media Access Control Protocol Data Unit, DL-SCH: Downlink Channel, UL-SCH: Uplink Channel, PDSCH: Physical Downlink Shared Channel, PUSCH: Physical Uplink Shared Channel). The HARQ-ACK state may indicate ACK (acknowledgment) or NACK (negative acknowledgment) corresponding to the transport block. ACK indicates that the transport block has been successfully decoded. NACK indicates that the transport block has not been successfully decoded. HARQ-ACK information may include a HARQ-ACK codebook, which includes one or more HARQ-ACK states (or HARQ-ACK bits).

[0090] For example, the correspondence between HARQ-ACK information and transport blocks can mean that HARQ-ACK information corresponds to PDSCH used for transport block transmission.

[0091] The HARQ-ACK status indicates either an ACK or NACK corresponding to a CBG (Code Block Group) included in a transport block.

[0092] A scheduling request can be used at least to request PUSCH (or UL-SCH) resources for a new transmission. A scheduling request can be used to indicate a positive or negative SR. The fact that a scheduling request indicates a positive SR is also called "sending a positive SR". A positive SR indicates that Terminal Device 1 is requesting PUSCH (or UL-SCH) resources for the initial transmission. A positive SR indicates that a higher layer will trigger a scheduling request. A positive SR can be sent when a higher layer commands the sending of a scheduling request. The fact that a scheduling request bit indicates a negative SR is also called "sending a negative SR". A negative SR indicates that Terminal Device 1 is not requesting PUSCH (or UL-SCH) resources for the initial transmission. A negative SR indicates that a higher layer has not triggered a scheduling request. A negative SR can be sent if a higher layer has not commanded the sending of a scheduling request.

[0093] Channel state information may include at least some or all of the following: Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). The CQI is an indicator related to channel quality (e.g., propagation quality) or physical channel quality, and the PMI is an indicator related to the precoder. The RI is an indicator related to the transmission class (or the number of transmission layers).

[0094] Channel state information can be provided based at least on receiving one or more physical signals (e.g., one or more CSI-RS) for channel measurement. Terminal device 1 can select the channel state information based at least on receiving one or more physical signals for channel measurement. Channel measurement may include interference measurement.

[0095] PUCCH can correspond to the PUCCH format. PUCCH can be a set of resource elements used to transmit the PUCCH format. PUCCH can include the PUCCH format. The PUCCH format can include UCI.

[0096] The PUSCH can be used to transmit uplink data (transmission blocks) and / or uplink control information. The PUSCH can be used to transmit uplink data (transmission blocks) and / or uplink control information corresponding to the UL-SCH. The PUSCH can be used to transmit uplink data (transmission blocks) and / or uplink control information. The PUSCH can be used to transmit uplink data (transmission blocks) and / or uplink control information corresponding to the UL-SCH. Uplink data (transmission blocks) can be arranged in the PUSCH. Uplink data (transmission blocks) corresponding to the UL-SCH can be arranged in the PUSCH. Uplink control information can be arranged in the PUSCH. Terminal device 1 can transmit a PUSCH containing uplink data (transmission blocks) and / or uplink control information. Base station device 3 can receive a PUSCH containing uplink data (transmission blocks) and / or uplink control information.

[0097] PRACH can be used to transmit random access preambles. The sequence X of the PRACH is... u,v (n) by X u,v (n)=X u (mod(n+C v ,L RA Definition. X u It can be a ZC sequence (Zadoff-Chu sequence). X u Can be made by X u =exp(-jpui(i+1) / L RA Definition: j is the hypothetical unit. p is the cycle ratio. C v This corresponds to the cyclic shift of PRACH.

[0098] L RA Corresponding to the length of PRACH. L RA It can be 839, 139, or another value. I is in the range 0 to L. RA Integers in the range -1. u is the sequence index of the PRACH. Terminal device 1 can transmit PRACH. Base station device 3 can receive PRACH.

[0099] For a given PRACH opportunity, 64 random access preambles are defined. At least a PRACH-based cyclic shift C... v The sequence index u of PRACH is used to specify (determine, give) the random access preamble.

[0100] The uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in higher layers. The uplink physical signal may be a physical signal used in uplink component carriers. Terminal device 1 may transmit the uplink physical signal. Base station device 3 may receive the uplink physical signal. In a radio communication system according to an embodiment of this disclosure, at least some or all of UL DMRS (Uplink Demodulation Reference Signal), SRS (Sound Reference Signal), and UL PTRS (Uplink Phase Tracking Reference Signal) may be used.

[0101] UL DMRS is the generic name for DMRS used for PUSCH and DMRS used for PUCCH.

[0102] A set of antenna ports for the DMRS used in the PUSCH (DMRS associated with the PUSCH, DMRS included in the PUSCH, and DMRS corresponding to the PUSCH) can be given based on a set of antenna ports for the PUSCH. That is, a set of antenna ports for the DMRS used in the PUSCH can be the same as a set of antenna ports for the PUSCH.

[0103] The transmission of PUSCH and the transmission of DMRS used for PUSCH can be indicated (or scheduled) by a DCI format. PUSCH and DMRS used for PUSCH can be collectively referred to as PUSCH. The transmission of PUSCH can be the transmission of both PUSCH and DMRS used for PUSCH.

[0104] PUSCH can be estimated from the DMRS used for PUSCH. In other words, the propagation path of PUSCH can be estimated from the DMRS used for PUSCH.

[0105] The set of antenna ports for the DMRS used for the PUCCH (DMRS associated with the PUCCH, DMRS included in the PUCCH, and DMRS corresponding to the PUCCH) may be the same as the set of antenna ports for the PUCCH.

[0106] The transmission of PUCCH and the transmission of DMRS for PUCCH can be indicated (or triggered) by a DCI format. The arrangement of PUCCH in a resource element (resource element mapping) and / or the arrangement of DMRS for PUCCH in a resource element can be provided by at least one PUCCH format. PUCCH and DMRS for PUCCH can be collectively referred to as PUCCH. The transmission of PUCCH can be the transmission of both PUCCH and DMRS for PUCCH.

[0107] PUCCH can be estimated from the DMRS used for PUCCH. In other words, the propagation path of PUCCH can be estimated from the DMRS used for PUCCH.

[0108] A downlink physical channel may correspond to a set of resource elements carrying information and / or downlink control information originating from higher layers. The downlink physical channel may be a physical channel used in downlink component carriers. Base station equipment 3 may transmit the downlink physical channel. Terminal equipment 1 may receive the downlink physical channel. In a wireless communication system according to an embodiment of this disclosure, at least some or all of PBCH (Physical Broadcast Channel), PDCCH (Physical Downlink Control Channel), and PDSCH (Physical Downlink Shared Channel) may be used.

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

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

[0111] Radio frame information is used to indicate radio frames in which PBCH is transmitted (including radio frames in time slots in which PBCH is transmitted). Radio frame information is represented by 4 bits. Radio frame information can be represented by 4 bits of a radio frame indicator. The radio frame indicator can include 10 bits. For example, the radio frame indicator can be used to identify radio frames from index 0 to index 1023.

[0112] Half-radio frame information is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of the radio frame in which the PBCH is transmitted. Here, a half-radio frame can be configured to include five subframes. A half-radio frame can be configured as the first five subframes of the ten subframes included in a radio frame. A half-radio frame can be configured as the last five subframes of the ten subframes included in a radio frame.

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

[0114] Subcarrier offset information is used to indicate subcarrier offset. Subcarrier offset information can be used to indicate the difference between the first subcarrier in which the PBCH is arranged and the first subcarrier in which the control resource set with index 0 is arranged.

[0115] The PDCCH can be used to transmit downlink control information (DCI). Downlink control information can be delivered via PDCCH. Downlink control information can be mapped to the PDCCH. Terminal device 1 can receive a PDCCH containing downlink control information. Base station device 3 can transmit a PDCCH containing downlink control information.

[0116] Downlink control information can correspond to the DCI format. Downlink control information can be included in the DCI format. Downlink control information can be arranged in each field of the DCI format.

[0117] DCI format is the common name for DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. Uplink DCI format is the common name for DCI format 0_0 and DCI format 0_1. Downlink DCI format is the common name for DCI format 1_0 and DCI format 1_1.

[0118] DCI format 0_0 is used at least for scheduling the cell's PUSCH (or PUSCH deployed on the cell). DCI format 0_0 includes at least some or all of fields 1A to 1E. 1A is the DCI format identification field (identifier field of the 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).

[0119] The frequency domain resource allocation field can be called the FDRA field or the FDRA information field.

[0120] The Time Domain Resource Allocation field can be called the TDRA field or the TDRA information field.

[0121] The DCI format identification field indicates whether the DCI format including this DCI format identification field is an uplink DCI format or a downlink DCI format. The DCI format identification field included in DCI format 0_0 can indicate 0 (or can indicate that DCI format 0_0 is an uplink DCI format).

[0122] The frequency domain resource allocation field included in DCI format 0_0 can be used to indicate at least the allocation (assignment) of frequency resources for PUSCH. The frequency domain resource allocation field included in DCI format 0_0 can be used at least to indicate the allocation (assignment) of frequency resources for PUSCH scheduled by DCI format 0_0.

[0123] The time-domain resource allocation field included in DCI format 0_0 can 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 can be used to indicate at least the allocation of time resources for PUSCH scheduled by DCI format 0_0.

[0124] The frequency hopping flag field can be used to indicate at least whether frequency hopping is applied to the PUSCH. The frequency hopping flag field can be used to indicate at least whether frequency hopping is applied to the PUSCH scheduled by DCI format 0_0.

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

[0126] DCI format 0_0 may not include fields used for CSI requests. In other words, DCI format 0_0 may not require a CSI request.

[0127] DCI format 0_0 may not include a carrier indicator field. Uplink component carriers on which PUSCH scheduled by DCI format 0_0 are arranged can be the same as uplink component carriers on which PDCCH including DCI format 0_0 is arranged.

[0128] DCI format 0_0 may not include the BWP field. The uplink BWP of a PUSCH scheduled by DCI format 0_0 can be the same as the uplink BWP of a PDCCH including DCI format 0_0.

[0129] DCI format 0_1 ​​is used at least for scheduling cell (or deploying on cell) PUSCH. DCI format 0_1 ​​includes at least some or all of fields 2A to 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.

[0130] The DCI format identification field included in DCI format 0_1 ​​can indicate 0 (or can indicate that DCI format 0_1 ​​is an uplink DCI format).

[0131] The frequency domain resource allocation field included in DCI format 0_1 ​​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 ​​can be used at least to indicate the allocation of frequency resources for PUSCH scheduled by DCI format.

[0132] The time-domain resource allocation field included in DCI format 0_1 ​​can be used to indicate at least the allocation of time resources for PUSCH. The time-domain resource allocation field included in DCI format 0_1 ​​can be used at least to indicate the allocation of time resources for PUSCH scheduled by DCI format 0_1.

[0133] The frequency hopping flag field can be used to indicate at least whether frequency hopping is applied to PUSCH scheduled by DCI format 0_1.

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

[0135] When DCI format 0_1 ​​includes a BWP field, the BWP field can be used to indicate an uplink BWP on which a PUSCH scheduled by DCI format 0_1 ​​is deployed. When DCI format 0_1 ​​does not include a BWP field, the uplink BWP on which a PUSCH is deployed can be an active uplink BWP. When the number of uplink BWPs in the uplink component carriers configured in terminal device 1 is two or more, the number of bits in the BWP field included in DCI format 0_1 ​​for scheduling PUSCHs deployed on the uplink component carriers can be one or more. When the number of uplink BWPs in the uplink component carriers configured in terminal device 1 is one, the number of bits in the BWP field included in DCI format 0_1 ​​for scheduling PUSCHs deployed on the uplink component carriers can be zero.

[0136] The CSI Request field is used at least to indicate a CSI report.

[0137] If DCI format 0_1 ​​includes a carrier indicator field, the carrier indicator field can be used to indicate the uplink component carrier (or serving cell) on which a PUSCH is arranged. When DCI format 0_1 ​​does not include a carrier indicator field, the serving cell on which a PUSCH is arranged can be the same as the serving cell on which a PDCCH including DCI format 0_1 ​​for scheduling the PUSCH is arranged. When the number of uplink component carriers (or the number of serving cells) in the serving cell group configured in terminal device 1 is two or more (when uplink carrier aggregation operates in the serving cell group), or when cross-carrier scheduling is configured for the serving cell group, the number of bits in the carrier indicator field included in DCI format 0_1 ​​for scheduling the PUSCH arranged on the serving cell group can be one or more (e.g., 3). When the number of uplink component carriers (or the number of serving cells) in the serving cell group configured in terminal device 1 is one (when uplink carrier aggregation is not operating in the serving cell group), or when cross-carrier scheduling is not configured for the serving cell group, the number of bits in the carrier indicator field included in the DCI format 0_1 ​​for scheduling PUSCHs arranged on the serving cell group can be zero.

[0138] DCI format 1_0 is used at least for scheduling the PDSCH (deployed on the cell). DCI format 1_0 includes at least some or all of fields 3A to 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.

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

[0140] The frequency domain resource allocation field included in DCI format 1_0 can be used to indicate the frequency resource allocation of PDSCHs at least.

[0141] The time-domain resource allocation field included in DCI format 1_0 can be used to indicate at least the time resource allocation of PDSCH. The time-domain resource allocation field included in DCI format 1_0 can be used to indicate at least the time resource allocation of PDSCH scheduled by DCI format 1_0.

[0142] The MCS field included in DCI format 1_0 can be used to indicate at least part or all of the modulation scheme and / or target coding rate of the PDSCH. The MCS field included in DCI format 1_0 can be used to indicate at least part or all of the modulation scheme and / or target coding rate of the PDSCH scheduled by DCI format 1_0. The transport block size (TBS) of the PDSCH can be given at least based on the target coding rate and part or all of the modulation scheme of the PDSCH.

[0143] The PDSCH-to-HARQ-feedback timing indicator field can be used to indicate at least the offset (K1) from a time slot that includes the last OFDM symbol of the PDSCH scheduled by DCI format 1_0 to another time slot that includes the first OFDM symbol of the PUCCH triggered by DCI format 1_0.

[0144] The PUCCH resource indicator field can be a field that indicates an index to any one or more PUCCH resources included in a PUCCH resource set used for PUCCH transmission. A PUCCH resource set may include one or more PUCCH resources. The PUCCH resource indicator field can trigger PUCCH transmission using at least the PUCCH resources indicated by the PUCCH resource indicator field.

[0145] DCI format 1_0 may not include a carrier indicator field. Downlink component carriers on which a PDSCH scheduled by DCI format 1_0 is arranged may be the same as downlink component carriers on which a PDCCH including DCI format 1_0 is arranged.

[0146] DCI format 1_0 may not include the BWP field. The downlink BWP of a PDSCH scheduled by DCI format 1_0 can be the same as the downlink BWP of a PDCCH including DCI format 1_0.

[0147] DCI format 1_1 is used at least for scheduling cell (or deploying on cell) PDSCH. DCI format 1_1 includes at least some or all of fields 4A to 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.

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

[0149] The frequency domain resource allocation field included in DCI format 1_1 can be used to indicate the frequency resource allocation of PDSCH at least. The frequency domain resource allocation field included in DCI format 1_0 can be used to indicate the frequency resource allocation of PDSCH scheduled by DCI format 1_1 at least.

[0150] The time-domain resource allocation field included in DCI format 1_1 can be used to indicate at least the time resource allocation of PDSCH. The time-domain resource allocation field included in DCI format 1_1 can be used to indicate at least the time resource allocation of PDSCH scheduled by DCI format 1_1.

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

[0152] When DCI format 1_1 includes the PDSCH-to-HARQ-feedback timing indicator field, the PDSCH-to-HARQ-feedback timing indicator field indicates the offset (K1) from the time slot containing the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another time slot containing the first OFDM symbol of the PUCCH triggered by DCI format 1_1. When DCI format 1_1 does not include the PDSCH-to-HARQ-feedback timing indicator field, the offset from the time slot containing the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another time slot containing the first OFDM symbol of the PUCCH triggered by DCI format 1_1 is identified by higher-layer parameters.

[0153] When DCI format 1_1 includes a BWP field, the BWP field can be used to indicate a downlink BWP on which a PDSCH scheduled by DCI format 1_1 is deployed. When DCI format 1_1 does not include a BWP field, the downlink BWP on which a PDSCH is deployed can be an active downlink BWP. When the number of downlink BWPs in the downlink component carriers configured in terminal device 1 is two or more, the number of bits in the BWP field included in DCI format 1_1 for scheduling the PDSCH deployed on the downlink component carriers can be one or more. When the number of downlink BWPs in the downlink component carriers configured in terminal device 1 is one, the number of bits in the BWP field included in DCI format 1_1 for scheduling the PDSCH deployed on the downlink component carriers can be zero.

[0154] If DCI format 1_1 includes a carrier indicator field, the carrier indicator field can be used to indicate the downlink component carrier (or serving cell) on which a PDSCH is arranged. When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier (or serving cell) on which a PDSCH is arranged can be the same as the downlink component carrier (or serving cell) on which a PDCCH including DCI format 1_1 for scheduling the PDSCH is arranged. When the number of downlink component carriers (or the number of serving cells) in the serving cell group configured in terminal device 1 is two or more (when downlink carrier aggregation is operating in the serving cell group), or when cross-carrier scheduling is configured for the serving cell group, the number of bits in the carrier indicator field included in DCI format 1_1 for scheduling the PDSCH arranged on the serving cell group can be one or more (e.g., 3). When the number of downlink component carriers (or the number of serving cells) in the serving cell group configured in terminal device 1 is one (when downlink carrier aggregation is not operating in the serving cell group), or when cross-carrier scheduling is not configured for the serving cell group, the number of bits in the carrier indicator field included in the DCI format 1_1 for scheduling the PDSCH arranged on the serving cell group can be zero.

[0155] The PDSCH can be used to transmit one or more transport blocks. The PDSCH can be used to transmit one or more transport blocks corresponding to the DL-SCH. The PDSCH can be used to transmit one or more transport blocks corresponding to the DL-SCH. One or more transport blocks can be arranged in the PDSCH. One or more transport blocks corresponding to the DL-SCH can be arranged in the PDSCH. Base station equipment 3 can transmit the PDSCH. Terminal equipment 1 can receive the PDSCH.

[0156] The downlink physical signal may correspond to a set of resource elements. The downlink physical signal may not carry information generated in higher layers. The downlink physical signal may be a physical signal used in downlink component carriers. The downlink physical signal may be transmitted by base station equipment 3. The downlink physical signal may be transmitted by terminal equipment 1. In a wireless communication system according to an embodiment of this disclosure, at least some or all of SS (synchronization signal), DL DMRS (downlink demodulation reference signal), CSI-RS (channel state information reference signal), and DL PTRS (downlink phase tracking reference signal) may be used.

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

[0158] Figure 7This is a diagram illustrating an example configuration of the SS / PBCH block according to an embodiment of this disclosure. Figure 7 In the middle, the horizontal axis indicates the time domain (OFDM symbol index l) sym The vertical axis indicates the frequency domain. Diagonal blocks indicate a set of resource elements for the PSS. Grid line blocks indicate a set of resource elements for the SSS. Additionally, blocks in the horizontal lines indicate a set of resource elements for the PBCH and a set of resource elements for the DMRS used in the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

[0159] like Figure 7 As shown, the SS / PBCH block includes the PSS, SSS, and PBCH. The SS / PBCH block comprises four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is allocated subcarriers 57 to 183 of the first OFDM symbol. The SSS is allocated subcarriers 57 to 183 of the third OFDM symbol. Subcarriers 1 to 56 of the first OFDM symbol can be set to zero. Subcarriers 184 to 240 of the first OFDM symbol can be set to zero. Subcarriers 49 to 56 of the third OFDM symbol can be set to zero. Subcarriers 184 to 192 of the third OFDM symbol can be set to zero. In the first to 240 subcarriers of the second OFDM symbol, the PBCH is allocated subcarriers that were not allocated to the DMRS used for the PBCH. In the first to 48 subcarriers of the third OFDM symbol, the PBCH is allocated subcarriers that were not allocated to the DMRS used for the PBCH. In subcarriers 193 to 240 of the third OFDM symbol, the PBCH was allocated subcarriers that were not allocated to the DMRS used for the PBCH. In subcarriers 1 to 240 of the fourth OFDM symbol, the PBCH was allocated subcarriers that were not allocated to the DMRS used for the PBCH.

[0160] The antenna ports of PSS, SSS, PBCH in the SS / PBCH block and the DMRS used for PBCH can be the same.

[0161] The PBCH can be estimated from the DMRS used for the PBCH. For the DM-RS used for the PBCH, the channel transmitted on the PBCH symbol at the antenna port can only be inferred from the channel transmitted on the DM-RS symbol at the antenna port if the two symbols are transmitted within the same SS / PBCH block in the same time slot and have the same SS / PBCH block index.

[0162] DL DMRS is the generic name for DMRS used in PBCH, DMRS used in PDSCH, and DMRS used in PDCCH.

[0163] A set of antenna ports for the DMRS used in the PDSCH (DMRS associated with the PDSCH, DMRS included in the PDSCH, and DMRS corresponding to the PDSCH) can be given based on a set of antenna ports for the PDSCH. The set of antenna ports for the DMRS used in the PDSCH can be the same as the set of antenna ports for the PDSCH.

[0164] The transmission of PDSCH and the transmission of DMRS used for PDSCH can be indicated (or scheduled) by a DCI format. PDSCH and DMRS used for PDSCH can be collectively referred to as PDSCH. Transmitting PDSCH can be either transmitting PDSCH or using DMRS used for PDSCH.

[0165] The PDSCH can be estimated from the DMRS used for the PDSCH. For the DM-RS associated with the PDSCH, the channel transmitted on one antenna port for the PDSCH symbol can be inferred from the channel transmitted on the other antenna port for the DM-RS symbol if the two symbols are in the same resource as the scheduled PDSCH, in the same time slot, and in the same PRG (Precoding Resource Group).

[0166] The antenna ports of the DMRS used for the PDCCH (DMRS associated with the PDCCH, DMRS included in the PDCCH, and DMRS corresponding to the PDCCH) can be the same as the antenna ports of the PDCCH.

[0167] The PDCCH can be estimated from the DMRS used for the PDCCH. For the DM-RS associated with the PDCCH, the channel transmitted on a symbol for the PDCCH on one antenna port can be inferred from the channel transmitted on another symbol for the DM-RS on the same antenna port, provided that the two symbols are within the same precoded resource (i.e., within the resource in the REG packet).

[0168] BCH (Broadcast Channel), UL-SCH (Uplink Channel), and DL-SCH (Downlink Channel) are transport channels. The channels used in the MAC layer are called transport channels. The unit of the 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 Repeat Request) control is performed for each transport block. A transport block is a unit of data delivered from the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords, and modulation processing is performed on each codeword.

[0169] One UL-SCH and one DL-SCH can be provided for each serving cell. The BCH can be provided to the PCell. Alternatively, the BCH can be omitted from the PSCell and SCell.

[0170] BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. BCCH is the channel used by the RRC layer to deliver MIB or system information. CCCH can be used to transmit common RRC messages among multiple terminal devices 1. CCCH can be used by terminal devices 1 that are not connected via RRC. DCCH can be used at least to transmit dedicated RRC messages to terminal device 1. DCCH can be used by terminal device 1 in RRC connection mode.

[0171] An RRC message includes one or more RRC parameters (information elements, higher-level parameters). For example, an RRC message may include a MIB. For example, an RRC message may include system information (SIB: System Information Block, MIB). SIB is a generic name for various types of SIBs (e.g., SIB1, SIB2). For example, an RRC message may include messages corresponding to a CCCH. For example, an RRC message may include messages corresponding to a DCCH. RRC message is a general term for both public and private RRC messages.

[0172] The BCCH in the logical channel can be mapped to the BCH or DL-SCH in the transport channel. The CCCH in the logical channel can be mapped to the DL-SCH or UL-SCH in the transport channel. The DCCH in the logical channel can be mapped to the DL-SCH or UL-SCH in the transport channel.

[0173] The UL-SCH in the transport channel can be mapped to the PUSCH in the physical channel. The DL-SCH in the transport channel can be mapped to the PDSCH in the physical channel. The BCH in the transport channel can be mapped to the PBCH in the physical channel.

[0174] High-level parameters are parameters included in RRC messages or MAC CE (Media Access Control Component). High-level parameters are generic names for information included in the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and MAC CE. If a high-level parameter is included in an RRC message, it may be referred to as an RRC parameter or RRC configuration.

[0175] Higher-layer parameters can be cell-specific or UE-specific. Cell-specific parameters include parameters that are common to all cells. UE-specific parameters include parameters that can be configured differently for each UE.

[0176] Base station equipment can indicate changes to cell-specific parameters through reconfiguration with random access. A UE can change cell-specific parameters before triggering random access. Base station equipment can indicate changes to UE-specific parameters with or without random access. A UE can change UE-specific parameters before or after random access.

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

[0178] Cell search is the process by which terminal device 1 synchronizes with cells in the time and / or frequency domains and detects physical cell identifiers. Terminal device 1 can detect physical cell IDs by performing time and / or frequency domain synchronization with cells through cell search.

[0179] The sequence of PSS should be given at least based on the physical cell ID. The sequence of SSS should be given at least based on the physical cell ID.

[0180] An SS / PBCH block candidate indicates a resource where transmission of an SS / PBCH block is possible. An SS / PBCH block can be transmitted at a resource indicated as an SS / PBCH block candidate. Base station device 3 can transmit an SS / PBCH block at an SS / PBCH block candidate. Terminal device 1 can receive (detect) an SS / PBCH block at an SS / PBCH block candidate.

[0181] A set of SS / PBCH block candidates in a half-radio frame is also called an SS burst set. An SS burst set is also called a transmission window, SS transmission window, or DRS transmission window (discovery reference signal transmission window). An SS burst set is a general name that includes at least a first SS burst set and a second SS burst set.

[0182] Base station device 3 transmits one or more indexed SS / PBCH blocks at a predetermined period. Terminal device 1 can detect at least one of the one or more indexed SS / PBCH blocks. Terminal device 1 can attempt to decode the PBCH included in the SS / PBCH block.

[0183] Random access is a process that includes at least some or all of messages 1, 2, 3 and 4.

[0184] Message 1 describes the process by which terminal device 1 transmits PRACH. Terminal device 1 transmits PRACH in a PRACH timing selected from one or more PRACH timings, based at least on the index of SS / PBCH block candidates detected according to cell search.

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

[0186] Message 3 (Msg 3) is the procedure for transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected during Message 2. The random access response grant is indicated by MAC CE and is included in the PDSCH scheduled by DCI format 1_0.

[0187] The PUSCH scheduled based on random access response permission is either message 3PUSCH or PUSCH. Message 3PUSCH contains a Contention Resolution Identifier (MAC CE). The Contention Resolution ID (MAC CE) includes the Contention Resolution ID.

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

[0189] Message 4 is an attempt to detect a DCI format 1_0 message with a CRC scrambled by a 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 conflict resolution ID.

[0190] Data communication is a general term used for both downlink and uplink communication.

[0191] In data communication, terminal device 1 attempts to detect (attempt to monitor PDCCH) in resources identified at least based on one or both of the control resource set and the search space set. This is also referred to as "terminal device 1 attempts to detect PDCCH in the control resource set," "terminal device 1 attempts to detect PDCCH in the search space set," "terminal device 1 attempts to detect PDCCH candidates in the control resource set," "terminal device 1 attempts to detect PDCCH candidates in the search space set," "terminal device 1 attempts to detect DCI format in the control resource set," or "terminal device 1 attempts to detect DCI format in the search space set." Monitoring PDCCH can be equivalent to monitoring the DCI format in PDCCH.

[0192] A control resource set is a set of resources configured by multiple resource blocks in a time slot and a predetermined number of OFDM symbols.

[0193] The resource set used for control resource set can be indicated by higher-level parameters. The number of OFDM symbols included in the control resource set can also be indicated by higher-level parameters.

[0194] PDCCH can also be called a PDCCH candidate.

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

[0196] The CSS set is a general name for the PDCCH common search space sets of types 0, 0a, 1, 2, and 3. The USS set can also be called the UE-specific PDCCH search space set.

[0197] A class 0 PDCCH public search space set can be used as a public search space set with index 0. A class 0 PDCCH public search space set can be a public search space set with index 0.

[0198] The search space set is associated with (and included in) the control resource set, corresponding to the control resource set. The index of the control resource set associated with the search space set can be indicated by high-level parameters.

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

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

[0201] Figure 8 This is an illustration showing an example of the timing of monitoring the search space set according to an embodiment of this disclosure. Figure 8 In this context, search space set 91 and search space set 92 are sets in the primary cell 301, search space set 93 is a set in the secondary cell 302, and search space set 94 is a set in the secondary cell 303.

[0202] exist Figure 8In the middle, the block indicated by the grid line indicates the search space set 91, the block indicated by the upper right diagonal line indicates the search space set 92, the block indicated by the upper left diagonal line indicates the search space set 93, and the block indicated by the horizontal line indicates the search space set 94.

[0203] exist Figure 8 In this configuration, the PDCCH monitoring period of search space set 91 is set to one time slot, the PDCCH monitoring offset of search space set 91 is set to zero time slots, 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 timing of search space set 91 corresponds to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each time slot.

[0204] exist Figure 8 In this configuration, the PDCCH monitoring period of search space set 92 is set to 2 time slots, the PDCCH monitoring offset of search space set 92 is set to 0 time slots, and the PDCCH monitoring pattern of search space set 92 is [1,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring timing of search space set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each even-numbered time slot.

[0205] exist Figure 8 In this configuration, the PDCCH monitoring period of search space set 93 is set to 2 time slots, the PDCCH monitoring offset of search space set 93 is set to 0 time slots, and the PDCCH monitoring pattern of search space set 93 is [0,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring timing of search space set 93 corresponds to the eighth OFDM symbol (OFDM symbol #8) in each even-numbered time slot.

[0206] exist Figure 8 In this configuration, the PDCCH monitoring period of search space set 94 is set to 2 time slots, the PDCCH monitoring offset of search space set 94 is set to 1 time slot, and the PDCCH monitoring pattern of search space set 94 is [1,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring timing of search space set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd-numbered time slot.

[0207] The Class 0 PDCCH public search space set can be used at least for DCI formats with cyclic redundancy check (CRC) sequences scrambled by SI-RNTI (System Information - Temporary Identifier for Radio Networks).

[0208] The 0a class PDCCH common search space set can be used at least for DCI formats with cyclic redundancy check sequences scrambled by SI-RNTI.

[0209] The Class 1 PDCCH public search space set can be used for DCI formats with CRC sequences scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​or TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0210] The Class 2 PDCCH public search space set can be used for DCI formats with CRC sequences scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

[0211] The three-class PDCCH public search space set can be used for DCI formats with CRC sequences scrambled by C-RNTI (Cell-Radio Network Temporary Identifier).

[0212] The UE-specific search space set can be used at least for DCI formats with CRC sequences scrambled by C-RNTI.

[0213] In downlink communication, terminal device 1 can detect the downlink DCI format. The detected downlink DCI format is used at least for PDSCH resource allocation. The detected downlink DCI format is also called downlink allocation. Terminal device 1 attempts to receive PDSCH. Based on the PUCCH resources indicated by the detected downlink DCI format, it can report the HARQ-ACK corresponding to the PDSCH (corresponding to the HARQ-ACK of the transport block included in the PDSCH) to base station device 3.

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

[0215] PUSCH transmissions can be dynamically scheduled via UL grants in the DCI, or the transmissions can correspond to grants with either Type 1 or Type 2 configurations. Type 1 granted PUSCH transmissions are semi-statically configured to operate upon receiving the higher-layer parameter `configuredGrantConfig`, which includes `rrc-ConfiguredUplinkGrant`, without detecting UL grants in the DCI. Upon receiving the higher-layer parameter `configuredGrantConfig`, which does not include `rrc-ConfiguredUplinkGrant`, Type 2 granted PUSCH transmissions are semi-persistently scheduled according to these procedures by effectively activating UL grants in the DCI. If `configuredGrantConfigToAddModList` is configured, more than one grant configuration with Type 1 and / or Type 2 grants can be active simultaneously on the active BWP of the serving cell.

[0216] This describes further details of resource allocation in the time domain for PUSCHs scheduled in DCI format. When the UE (Terminal Device 1) is scheduled to transmit a transport block and no CSI is reported, or when the UE is scheduled to transmit a transport block and CSI is reported on the PUSCH by the DCI, the DCI's "Time Domain Resource Allocation" field value m can provide a row index m+1 to the allocation table. The determination of the resource allocation table used can be predefined and / or defined in the RRC configuration. The index row of the resource allocation table can define the slot offset K2, the start and length indicators SLIV, or directly define the start symbol S and allocation length L, PUSCH mapping type, and repetition count (if the RRC parameter numberOfRepetitions exists in the resource allocation table) to be applied to PUSCH transmission. Note that the RRC parameter is a higher-level parameter.

[0217] For PUSCHs scheduled using DCI format 0_1, if the RRC parameter pusch-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 PUSCHs scheduled using DCI format 0_2, if the RRC parameter pusch-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 the time-domain resource allocation for PUSCHs scheduled using PDCCH.

[0218] For PUSCH repetition type A, the starting symbol S relative to the start of the time slot and the number L of consecutive symbols allocated to the PUSCH, counting from symbol S, can be determined based on the start and length indicators SLIV of the index row: if (L-1)≤7, then SLIV=14(L-1)+S, otherwise SLIV=14(14-L+1+(14-1-S), where 0 <L≤14-S。

[0219] For PUSCH repetition type A, when a PUSCH scheduled by DCI format 0_1 ​​or 0_2 is transmitted in a PDCCH with a CRC scrambled with C-RNTI, MCS-C-RNTI or CS-RNTI of NDI=1, the repetition number K can be determined as follows: if the RRC parameter numberOfRepetitions exists in the resource allocation table, then the repetition number K can be equal to numberOfRepetitions; otherwise, if the UE is configured with the RRC parameter pusch-AggregationFactor, then the repetition number K can be equal to pusch-AggregationFactor; otherwise, K=1.

[0220] If the UE does not have a coverage enhancement feature (e.g., available slot-based PUSCH repetition count) or if the UE does not have a coverage enhancement configuration (e.g., available slot-based PUSCH repetition count), the following can be applied. For PUSCH repetition type A, in the case of K>1, the same symbol allocation can be applied across K consecutive slots, and the PUSCH can be limited to a single transport layer. The UE can repeat TB across K consecutive slots, thereby applying the same symbol allocation in each slot. The redundant version to be applied at the nth transmission time of TB can be determined as follows, where n = 0, 1, ... K-1 can be determined as follows. For PUSCH repetition type A, PUSCH transmissions in slots of multi-slot PUSCH transmissions can be omitted based on conditions in at least and / or at most PUSCH priority-based procedures, slot configuration-based procedures, slot format-based procedures, and cancellation indication-based procedures. For example, if a time slot is available according to all the conditions defined in those procedures, then the time slot can be determined to be available, and / or if a time slot is unavailable according to at least one of the conditions defined in those procedures, then the time slot can be determined to be unavailable. K can be an integer.

[0221] If the UE has a coverage enhancement feature and / or if the UE has a coverage enhancement configuration, the following can be applied: For PUSCH repetition type A, in the case of K>1, the same symbol allocation can be applied across K available time slots (i.e., the first K time slots available for PUSCH transmission), and the PUSCH can be limited to a single transport layer. The UE can repeat TB across K consecutive time slots, thereby applying the same symbol allocation in each time slot. The K available time slots can be determined based on conditions in at least and / or at most procedures based on PUSCH priority, time slot configuration, time slot format, and cancellation indication. For example, if a time slot is available according to all the conditions defined in those procedures, the time slot can be determined to be available, and / or if a time slot is unavailable according to at least one of the conditions defined in those procedures, the time slot can be determined to be unavailable.

[0222] If the UE has a coverage enhancement feature and / or if the UE has a coverage enhancement configuration, the following can be applied. For PUSCH repetition type A, in the case of K>1, the same symbol allocation can be applied across K available time slots (i.e., the first K time slots available for PUSCH transmission), and the PUSCH can be limited to a single transport layer. The UE can repeat TB across K available time slots, thereby applying the same symbol allocation in each time slot. The K available time slots can be determined based on conditions in at least and / or at most the first RRC parameter. The first RRC parameter can be one or more of the following: 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 in slots of multi-slot PUSCH transmissions are omitted based on the conditions in at least and / or at most the second RRC parameter. The second RRC parameter can be one or more of the following: 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.

[0223] ConfiguredGrantConfig can be called ConfiguredGrantConfig.

[0224] ConfiguredGrantConfig can be called ConfiguredGrantConfig.

[0225] When PUSCH resource allocation is semi-statically configured via the high-level parameter configuredGrantConfig in the BWP-UplinkDedicated information element and PUSCH transport corresponds to the configured grant, the following high-level parameters are applied during transport.

[0226] For Class 1 PUSCH transports with configured authorization, unless otherwise specified, the following parameters are given in configuredGrantConfig, and corresponding to the determination of the PUSCH repetition type: if the higher-level parameter pusch-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.

[0227] The higher-level parameter `pusch-RepTypeIndicator` indicates whether the UE follows the behavior for PUSCH repetition type A or PUSCH repetition type B for the authorization configuration of Class 1 configuration. The value `pusch-RepTypeA` enables "PUSCH repetition type A", and the value `pusch-RepTypeB` enables "PUSCH repetition type B". The value `pusch-RepTypeB` is not configured simultaneously with `cg-nrofPUSCH-InSlot-r16` and `cg-nrofSlots-r16`.

[0228] For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rule of DCI format 0_0 on the UE-specific search space.

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

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

[0231] Further details are described regarding the time-domain resource allocation for PUSCHs with configured grants. For PUSCH transmissions with a Class 1 or Class 2 configuration, the (nominal) number of repetitions K can be provided by the index row in the time-domain resource allocation table to be applied to the transmitted transport block if numberOfRepetitions exists in the table; otherwise, K can be provided by the repK parameter configured by the higher layer. If the higher layer does not deliver a transport block for transmission on resources allocated for unauthorized uplink transmissions, the UE may disallow any transmission on resources configured by the RRC parameter configuredGrantConfig.

[0232] A set of allowed periodic Ps is defined in the RRC configuration. The RRC parameter cg-nrofSlots provides the number of consecutive time slots allocated within the configured grant period. The RRC parameter cg-nrofPUSCH-InSlot provides the number of consecutive PUSCH allocations within a time slot, where the first PUSCH allocation can be a Type 1 PUSCH transmission following the RRC parameter timeDomainAllocation, or a Type 2 PUSCH transmission based on the higher-level configuration of the MAC procedure and the UL grant received on the DCI. Remaining PUSCH allocations can have the same length and PUSCH mapping type and can be appended to previous allocations without any gaps. The same combination of start symbol and length, and PUSCH mapping type, can be repeated on consecutively allocated time slots.

[0233] The UE may not expect to be configured to have a duration for K repeated transmissions that is greater than the duration derived from the periodicity P. If the UE determines that for a transmission opportunity, the number of symbols available for PUSCH transmission in the time slot is less than the transmission duration L, the UE may not transmit the PUSCH in that transmission opportunity.

[0234] These procedures apply to PUSCH transmissions of type A repetition with a Class 1 or Class 2 configuration. The RRC parameter repK-RV defines the redundancy version mode to be applied to the repetition. If cg-RetransmissionTimer is provided, the UE determines the redundancy version for uplink transmissions with a configured grant. If the parameter repK-RV is not provided in configuredGrantConfig and cg-RetransmissionTimer is not provided, the redundancy version for uplink transmissions with a configured grant may have to be set to 0. If the parameter repK-RV is provided in configuredGrantConfig and cg-RetransmissionTimer is not provided, it is associated with the (mod(n-1,4)+1)th value in the configured RV sequence for the nth transmission opportunity (n = 1, 2, ..., K) in K repetitions. If the configured grant configuration is configured with startingFromRV0 set to "off", the initial transmission of the transport block may begin only at the first transmission opportunity in K repetitions. Otherwise, except for the last transmission opportunity when K≥8, the initial transmission of the transport block may begin at the first transmission opportunity in the K repetitions if the configured RV sequence is {0,2,3,1}; at any transmission opportunity associated with RV=0 in the K repetitions if the configured RV sequence is {0,3,0,3}; and / or at any transmission opportunity in the K repetitions if the configured RV sequence is {0,0,0,0}.

[0235] If the configured authorization configuration does not have startingFromRV0 set to "off", and if a slot-based count is configured, the initial transmission of a transport block can begin at the first transmission timing in K repetitions.

[0236] If the configured authorization configuration does not have startingFromRV0 set to "off", and if no available slot-based count is configured, the initial transmission of a transport block may, except for the last transmission opportunity when K>8, begin at the first transmission opportunity in the K repetitions if the configured RV sequence is {0,2,3,1}; begin at any transmission opportunity associated with RV=0 in the K repetitions if the configured RV sequence is {0,3,0,3}; and / or begin at any transmission opportunity in the K repetitions if the configured RV sequence is {0,0,0,0}.

[0237] If the configured authorization configuration does not have startingFromRV0 set to "off", and if a slot-based count is configured, the initial transmission of a transport block may, except for the last transmission opportunity when K>8, begin at the first transmission opportunity in the K repetitions if the configured RV sequence is {0,2,3,1}; begin at any transmission opportunity associated with RV=0 in the K repetitions if the configured RV sequence is {0,3,0,3}; and / or begin at any transmission opportunity in the K repetitions if the configured RV sequence is {0,0,0,0}.

[0238] If the configured authorization configuration does not have startingFromRV0 set to "off", and if no available slot-based count is configured, assuming the transmission timing for K repetitions is determined based on consecutive physical slots, the initial transmission of a transport block may, except for the last transmission timing when K>8, begin at the first transmission timing in the K repetitions if the configured RV sequence is {0,2,3,1}; begin at any transmission timing in the K repetitions associated with RV=0 if the configured RV sequence is {0,3,0,3}; and / or begin at any transmission timing in the K repetitions if the configured RV sequence is {0,0,0,0}.

[0239] For any RV sequence, repetition may have to terminate after K repetitions, or at the last transmission point of the K repetitions within period P, or at the start symbol of a repetition overlapping with a PUSCH having the same HARQ process scheduled by DCI format 0_0, 0_1, or 0_2, whichever arrives first. Additionally, if the UE receives a DCI format 0_1 ​​with a DFI flag provided and set to "1", and if the UE detects an ACK corresponding to the HARQ process for that transport block in that DCI, the UE may have to terminate the repetition of the transport block in the PUSCH transmission.

[0240] The UE does not expect to be configured to have a duration for K repeated transmissions that is greater than the duration derived from the periodicity P. If the UE determines that for a transmission opportunity, the number of symbols available for PUSCH transmission in the time slot is less than the transmission duration L, then the UE will not transmit PUSCH in that transmission opportunity.

[0241] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is enabled, the UE determines N*K time slots for PUSCH transmission of PUSCH repetition type A based on the RRC parameters tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst. If at least one symbol in a time slot, indicated by the index row of the resource allocation table used, 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-PositionsInBurst, then that time slot is not counted in the number of N*K time slots for PUSCH transmission of PUSCH repetition type A. Otherwise, the UE determines N*K consecutive time slots for PUSCH transmission of PUSCH repetition type A. For UEs with reduced half-duplex capability, and when AvailableSlotCounting is enabled, if at least one of the symbols in a slot, indicated by the index row of the resource allocation table used, overlaps with a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, then that slot is not counted in the number of N*K slots for PUSCH transmissions of PUSCH repetition type A.

[0242] For paired spectrum and SUL band, the UE determines N*K consecutive time slots for PUSCH transmission of PUSCH repetition type A, regardless of whether AvailableSlotCounting is enabled. For UEs with reduced half-duplex capability, and when AvailableSlotCounting is enabled, if at least one symbol in a time slot, indicated by the index row of the resource allocation table used, overlaps with a symbol of an SS / PBCH block with an index provided by ssb-PositionslnBurst, that time slot is not counted in the total number of N*K time slots for PUSCH transmission of PUSCH repetition type A.

[0243] For both Category 1 and Category 2 PUSCH transmissions with configured authorization, when K>1, for unpaired spectrum, if the RRC parameter AvailableSlotCounting is enabled, the UE may have to repeat the TB across N*K slots determined for PUSCH transmission, thus applying the same symbol allocation in each slot. Otherwise, the UE may have to repeat the TB across N*K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats the TB in the repK earliest consecutive transmission opportunity candidates within the same configuration.

[0244] For both Category 1 and Category 2 PUSCH transmissions with configured authorization, when K>1, for paired spectrum, regardless of whether AvailableSlotCounting is enabled, the UE may have to repeat TB across N*K consecutive time slots, thus applying the same symbol allocation in each time slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats TB in the repK earliest consecutive transmission opportunity candidates within the same configuration. Category 1 or Category 2 PUSCH transmissions with configured authorization in a time slot are omitted based on conditions in the UE procedure for reporting control information, the UE procedure for determining time slot configuration, and the UE procedure associated with cancellation indication.

[0245] If no available slot-based counting is configured [or for paired spectrum], for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat TB across K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats TB in the earliest consecutive transmission timing candidates within the same configuration repK.

[0246] If a slot-based count is configured [and for unpaired spectrum], for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat TB across the first K available slots, thus applying the same symbol allocation in each slot, where each available slot is a slot with the following symbols: UL symbols as described in the UE procedure for determining slot configuration, or flexible symbols as described in the UE procedure for determining slot configuration, i.e., non-SS / PBCH block symbols for PUSCH, and [ / or] consecutive UL symbols equal to or greater than the number of symbols used for PUSCH starting from the first symbol as described in the UE procedure for determining slot configuration, or flexible symbols as described in the UE procedure for determining slot configuration, i.e., non-SS / PBCH block symbols; unless the UE has set the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats TB in the repK earliest consecutive transmission opportunity candidates within the same configuration. Based on conditions in the UE procedure for reporting control information, the UE procedure for determining time slot configuration, and the UE procedure associated with the cancellation indication, PUSCH transmissions of type 1 or type 2 with configured authorization in the time slot are omitted. An SS / PBCH block symbol is a symbol of an SS / PBCH block that has a candidate SS / PBCH block index corresponding to the SS / PBCH block index indicated to the UE by ssb-PositionslnBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, as described in the UE synchronization procedure for cell search.

[0247] If no available slot-based counting is configured [or for paired spectrum], for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat TB across K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats TB in the earliest consecutive transmission timing candidates within the same configuration repK.

[0248] If a slot-based count is configured [and for unpaired spectrum], for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat the TB across the initial slot and the subsequent K-1 available slots, thus applying the same symbol allocation in each slot, where the initial slot is the slot with symbols defined during uplink transmissions that do not require dynamic authorization by the MAC entity, and each available slot is the slot with symbols as described in the UE procedure for determining the slot configuration, or as described in the UE procedure for determining the slot configuration. The flexible symbols described in the procedure, i.e., non-SS / PBCH block symbols, are used for PUSCH, and / or, as described in the UE procedure for determining slot configuration, a number of consecutive UL symbols equal to or greater than the number of symbols used for PUSCH starting from the first symbol, or as described in the UE procedure for determining slot configuration, i.e., non-SS / PBCH block symbols; unless the UE has set higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats TB in the earliest consecutive transmission opportunity candidates repK within the same configuration. Based on the conditions in the UE procedure for reporting control information, the UE procedure for determining slot configuration, and the UE procedure associated with cancellation indication, Class 1 or Class 2 PUSCH transmissions with configured authorization in the slot are omitted. An SS / PBCH block symbol is a symbol for an SS / PBCH block that has a candidate SS / PBCH block index corresponding to the SS / PBCH block index indicated to the UE by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, as described in the UE synchronization procedure for cell search.

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

[0250] The UE may not expect the initial time slot to be unavailable.

[0251] If no available slot-based counting is configured, or for paired spectrum, for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat TB across K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats TB in the earliest consecutive transmission opportunity candidates within the same configuration repK.

[0252] If slot-based counting is configured and for unpaired spectrum, for both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE may have to repeat TB across K available slots, thus applying the same symbol allocation in each slot, where each available slot is a slot with the following symbols: UL symbols as described in those procedures, or flexible symbols according to the conditions in those procedures, i.e., non-SS / PBCH block symbols for PUSCH, and / or consecutive UL symbols equal to or greater than the number of symbols used for PUSCH starting from the first symbol according to the conditions in those procedures, or flexible symbols according to the conditions in those procedures, i.e., non-SS / PBCH block symbols; unless the UE has set the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot, in which case the UE repeats TB in the earliest consecutive transmission opportunity candidates within the same configuration repK.

[0253] Based on the conditions in those procedures, PUSCH transmissions of type 1 or 2 with configured authorization in the time slot are omitted. Based on the conditions in those procedures, the SS / PBCH block symbol is the symbol of the SS / PBCH block with a candidate SS / PBCH block index corresponding to the SS / PBCH block index indicated to the UE by ssb-PositionsInBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon.

[0254] For both Type 1 and Type 2 PUSCH transmissions with configured authorization, when K > 1, the UE may have to repeat the TB across K consecutive time slots, thus applying the same symbol allocation in each time slot, unless the UE has the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats the TB in the earliest consecutive transmission opportunity candidates repK within the same configuration. Based on conditions in one or more RRC configurations, Type 1 or Type 2 PUSCH transmissions with configured authorization in a time slot may be omitted.

[0255] These procedures apply to PUSCH transfers of PUSCH repetition type B with authorization of type 1 or 2 configuration. For PUSCH transfers with authorization of type 1 or 2 configuration, nominal and actual repetitions are determined according to the procedures for PUSCH repetition type B, based on at least one of those procedures. The higher-level configuration parameter repK-RV defines the redundancy version mode to be applied to the repetition. If the parameter repK-RV is not provided in configuredGrantConfig, the redundancy version for each actual repetition with the configured authorization may have to be set to 0. Otherwise, for the nth transfer timing in all actual repetitions (including omitted actual repetitions) of K nominal repetitions, it is associated with the (mod(n-1,4)+1)th value in the configured RV sequence. If the configured authorization configuration is configured with startingFromRVO set to "off", the initial transfer of the transfer block may begin only at the first transfer timing in the actual repetition. Otherwise, except for the actual repetition within the last nominal repetition when K≥8, the initial transmission of the transport block may: begin at the first transmission opportunity in the actual repetition if the configured RV sequence is {0,2,3,1}; begin at any transmission opportunity in the actual repetition associated with RV=0 if the configured RV sequence is {0,3,0,3}; and / or begin at any transmission opportunity in the actual repetition if the configured RV sequence is {0,0,0,0}.

[0256] For any RV sequence, the repetition may have to terminate after K nominal repetitions, or at the last transmission opportunity of the K nominal repetitions within period P, or at 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 arrives first. The UE does not expect to be configured to have a duration for the K nominal repetition transmissions that is greater than the duration derived from periodicity P.

[0257] For PUSCH repetition type A (as determined by procedures defined in those procedures used for scheduling PUSCHs or those used for configuring PUSCHs), the UE is configured to perform frequency hopping by the RRC parameter frequencyHoppingDCI-0-1 in the pusch-Config (e.g., frequencyHoppingDCI-0-1-r16 and / or frequencyHoppingDCI-0-1-r17) for PUSCH transmissions scheduled by DCI format 0_1; and is configured to perform frequency hopping by frequencyHoppingDCI-0-2 in the pusch-Config for PUSCH transmissions scheduled by DCI format 0_1. Used for PUSCH transmissions scheduled by DCI format 0_2; and configured for frequency hopping by frequencyHopping provided in pusch-Config for PUSCH transmissions scheduled by DCI formats other than 0_2; and configured for frequency hopping by frequencyHopping provided in configuredGrantConfig for configured PUSCH transmissions; and configured for frequency hopping by frequencyHoppingPUSCH-RepTypeA provided in rrc-ConfiguredUplinkGrant for PUSCH transmissions in Class 1 configuration. One of two frequency hopping modes can be configured (intra-slot frequency hopping, suitable for single-slot and multi-slot PUSCH transmissions; and inter-slot frequency hopping, suitable for multi-slot PUSCH transmissions). A further frequency hopping mode (inter-repetition frequency hopping, suitable for multi-slot PUSCH transmissions) can be configured.

[0258] pusch-Config can also be called PUSCH-Config.

[0259] pusch-Config can also be called PUSCH-Config.

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

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

[0262] When `pusch-RepTypeIndicatorDCI-0-1` is set to either `pusch-RepTypeA` or `pusch-RepTypeB` with "inter-repetition frequency hopping", the RRC parameter `frequencyHoppingDCI-0-1-r17` indicates the frequency hopping scheme for DCI format 0_1. 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 this field is not present, inter-repetition frequency hopping is not configured for DCI format 0_1 ​​for the case of `pusch-RepTypeA`, and frequency hopping is not configured for DCI format 0_1 ​​for the case of `pusch-RepTypeB`. Alternatively, when `pusch-RepTypeIndicatorDCI-0-1` is set to `pusch-RepTypeA` with "inter-repetition frequency hopping" enabled, the RRC parameter `frequencyHoppingDCI-0-1-r17` can indicate the frequency hopping scheme for DCI format 0_1.

[0263] In the case of Class 2 resource allocation, the UE transmits PUSCH without frequency hopping.

[0264] In the case of Class 1 resource allocation, regardless of whether transform precoding is enabled for PUSCH transmissions, the UE may perform PUSCH frequency hopping if the frequency hopping field is set to 1 in the corresponding detected DCI format or in the random access response UL grant, or if the RRC parameter frequencyHoppingOffset is provided for Class 1 PUSCH transmissions with configured grants; otherwise, PUSCH frequency hopping is not performed. When frequency hopping is enabled for PUSCH, RE mappings are defined in those procedures.

[0265] For PUSCHs scheduled by RAR UL licenses, fallback RAR UL licenses, or DCI format 0_0 with a CRC scrambled by TC-RNTI, the frequency offset is obtained as described in those procedures. For PUSCHs scheduled by DCI format 0_0 / 0_1 or UL licenses based on a Class 2 configuration activated by DCI format 0_0 / 0_1, and for Class 1 resource allocations, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in the pusch-Config. For PUSCHs scheduled by DCI format 0_2 or UL licenses based on a Class 2 configuration activated by DCI format 0_2, and for Class 1 resource allocations, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in the pusch-Config. When the size of the active BWP is less than 50 PRBs, one of the offsets of the two higher-level configurations is indicated in the UL license. When the size of the active BWP is equal to or greater than 50 PRBs, one of the offsets of the four higher-level configurations is indicated in the UL license.

[0266] For UL-authorized PUSCHs based on Type 1 configuration, the frequency offset is provided by the RRC parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant. For PUSCH repetition type B (as determined according to procedures defined in those procedures used for scheduling PUSCHs or those used for configuring PUSCHs), the UE is configured to perform frequency hopping by the RRC parameter frequencyHoppingDCI-0-2 in push-Config for PUSCH transmissions scheduled by DCI format 0_2; configured to perform frequency hopping by frequencyHoppingDCI-0-1 provided in push-Config for PUSCH transmissions scheduled by DCI format 0_1; and configured to perform frequency hopping by frequencyHoppingPUSCH-RepTypeB provided in rrc-ConfiguredUplinkGrant for PUSCH transmissions in Type 1 configuration. The frequency hopping mode for PUSCH transmissions in Type 2 configuration 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.

[0267] In the case of Class 1 resource allocation, regardless of whether transform precoding is enabled for PUSCH transmission, 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 Class 1 authorized PUSCH transmissions with configuration; otherwise, PUSCH frequency hopping is not performed. When frequency hopping is enabled for PUSCH, RE mappings are defined in those procedures.

[0268] For PUSCHs scheduled by DCI format 0_1 ​​or UL-authorized PUSCHs based on a Class 2 configuration activated by DCI format 0_1, and for Class 1 resource allocations, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in the pusch-Config. For PUSCHs scheduled by DCI format 0_2 or UL-authorized PUSCHs based on a Class 2 configuration activated by DCI format 0_2, and for Class 1 resource allocations, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in the pusch-Config. When the size of the active BWP is less than 50 PRBs, one of the offsets of the two higher-level configurations is indicated in the UL authorization. When the size of the active BWP is equal to or greater than 50 PRBs, one of the offsets of the four higher-level configurations is indicated in the UL authorization.

[0269] For UL-licensed PUSCHs based on Class 1 configuration, the frequency offset is provided by the RRC parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.

[0270] In the case of inter-slot frequency hopping, the starting RB during time slot n^u_s follows the RB of inter-slot frequency hopping for PUSCH repetition type A, according to at least one condition defined in those procedures.

[0271] If the UE cannot have a coverage enhancement feature (e.g., available slot-based PUSCH repetition count) or if the UE does not have a coverage enhancement configuration (e.g., available slot-based PUSCH repetition count), then the following can be applied (i.e., the number of repetitions based on contiguous (or continuous or consecutive) slot counts). Alternatively or additionally, if the UE can have a coverage enhancement feature, and if the UE has a slot count type configuration (RRC configuration or RRC parameter indicating whether the number of repetitions is counted based on contiguous (or continuous) slots or based on available slots), which indicates that PUSCH repetitions are counted based on contiguous slots, then the following can be applied. For both Class 1 and Class 2 authorized PUSCH transmissions with configuration, when K>1, the UE may repeat TB across K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE may repeat TB in the repK earliest consecutive transmission opportunity candidates within the same configuration. For PUSCH repetition type A, one or two types of PUSCH transmissions with configured authorization in a time slot may be omitted based on conditions in at least and / or at most procedures based on PUSCH priority, time slot configuration, time slot format, and cancellation indication. For example, a time slot is determined to be available if it is available according to all the conditions defined in those procedures, and / or unavailable if it is unavailable according to at least one of the conditions defined in those procedures.

[0272] It should be noted that the above slot count type configuration may be referred to by different names. The presence of a slot count type configuration in the 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 the RRC configuration message may mean that the number of repetitions is counted based on connected slots. Additionally and / or alternatively, a slot count type configuration set to a first value (e.g., "connected") may mean that the number of repetitions is counted based on connected 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.

[0273] If the UE has a coverage enhancement feature and / or if the UE has a coverage enhancement configuration, the following can be applied (i.e., the number of repetitions counted based on available time slots). Alternatively or additionally, if the UE has a coverage enhancement feature and / or if the UE has a time slot counting type configuration that indicates that PUSCH repetitions are counted based on available time slots, the following can be applied. For both Class 1 and Class 2 authorized PUSCH transmissions with configuration, when K>1, the UE can repeat TB across K available time slots (i.e., the first K time slots available for PUSCH transmission), thereby applying the same symbol allocation in each time slot. The K available time slots can be determined based on conditions in at least and / or at most procedures based on PUSCH priority, time slot configuration, time slot format, and cancellation indication. For example, if a time slot is available according to all the conditions defined in those procedures, the time slot can be determined to be available, and / or if a time slot is unavailable according to at least one of the conditions defined in those procedures, the time slot can be determined to be unavailable.

[0274] The pattern of inter-slot frequency hopping based on available time slots can be determined based on the omission of PUSCH transmission.

[0275] The pattern of RV based on available time slots can be determined based on the omission of PUSCH transmission.

[0276] The pattern of slot counts based on available slots can be determined based on the omission of PUSCH transmissions.

[0277] This describes the procedure based on PUSCH priority. Unless otherwise stated, a PUSCH will be transmitted if it is scheduled by DCI or configured with a configured authorization.

[0278] PUSCH or PUCCH transmissions, including repetitions (if any), may have a priority index of 0 or 1. For configured authorized PUSCH transmissions, the UE may determine the priority index based on the RRC parameter phy-PriorityIndex (if provided). For PUCCH transmissions with HARQ-ACK information corresponding to SPS PDSCH receive or SPS PDSCH release, the UE may determine the priority index based on the RRC parameter harq-CodebookID (if provided). For PUCCH transmissions with SR, the UE may determine the corresponding priority via the RRC parameter phy-PriorityIndex (if any) in the RRC parameter SchedulingRequestResourceConfig. For PUSCH transmissions with semi-persistent CSI reports, the UE may determine the priority index based on 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 PUSCH or PUCCH transmissions, the priority index may be 0.

[0279] If, in an active DL BWP, the UE can monitor the detection of DCI formats 0_1 and 1_1, or DCI formats 0_2 and 1_2, by the PDCCH, a priority index can be provided by the priority indicator field. If the UE indicates the ability to monitor the detection of DCI formats 0_1 and 1_1, and DCI formats 0_2 and 1_2 by the PDCCH in an active DL BWP, DCI format 0_1 ​​or DCI format 0_2 can schedule PUSCH transmissions with any priority, and DCI format 1_1 or DCI format 1_2 can schedule PDSCH reception and trigger PUCCH transmissions with corresponding HARQ-ACK information with any priority.

[0280] When the UE determines that PUCCH and / or PUSCH transmissions (including repetitions, if any) with different priority indices overlap, the UE may first resolve the overlap of PUCCH and / or PUSCH transmissions with the lower priority index. Then: if a transmission of a first PUCCH with a higher priority index, scheduled by the DCI format in PDCCH reception, will overlap in time with a transmission of a second PUSCH or second PUCCH with a lower priority index, the UE may cancel the repetition of the second PUSCH or second PUCCH transmission before the first symbol overlapping with the first PUCCH transmission; if a transmission of a first PUSCH with a higher priority index, scheduled by the DCI format in PDCCH reception, will overlap in time with a transmission of a second PUCCH with a lower priority index, the UE may cancel the repetition of the second PUCCH transmission before the first symbol overlapping with the first PUSCH transmission. Overlap may be resolved before or after resolving the channel with the higher priority index (if any). The UE can anticipate that the transmission of the first PUCCH or the first PUSCH will not begin until T_(proc,2)+d_1 after the last symbol received by the corresponding PDCCH. Based on u and N_2, T_(proc,2) is the PUSCH preparation time for the corresponding UE's processing capability assuming d_2,1=0, and d_1 is determined by the reported UE capability.

[0281] If the slot counting type configuration indicates that the number of repetitions is counted based on contiguous slots, the above processing time requirement applies: the first PUSCH will not start before T_(proc,2)+d_1 after the last symbol received by the corresponding PDCCH. If the slot counting type configuration indicates that the number of repetitions is counted based on available slots, the processing time requirement can be relaxed. For example, the processing time requirement can be applied: the first PUSCH will not start before T_(proc,2)+d_1+d_x after the last symbol received by the corresponding PDCCH, where d_x is a positive value. d_x can be represented in symbolic units. In other words, if the number of repetitions of PUSCH repetition type A is counted based on contiguous slots, the processing time requirement applies: the first PUSCH will not start before T_(proc,2)+d_1 after the last symbol received by the corresponding PDCCH. If the number of repetitions of PUSCH repetition type A is counted based on available slots, the processing time requirement can be relaxed. Relaxing the processing time requirement may mean allowing a longer interval duration between the start of a PUSCH and the end of the corresponding PDCCH, where the processing time requirement may be the maximum processing time required to cancel a scheduled / configured / authorized PUSCH transmission.

[0282] If the UE is scheduled by the DCI format in the first PDCCH reception to transmit the first PUCCH or the first PUSCH with a higher priority index, which overlaps with the transmission of the second PUCCH or the second PUSCH with a lower priority index scheduled by the DCI format in the second PDCCH (if any), then T_(proc,2) can be based on the value of μ of the minimum SCS configuration corresponding to the first PDCCH, the second PDCCH, the first PUCCH or the first PUSCH and the second PUCCH or the second PUSCH. If the overlapping group includes the first PUCCH, and if the RRC parameter processingType2Enabled of the RRC parameter PDSCH-ServingCellConfig is set to enabled for the serving cell where the UE receives the first PDCCH, and for all serving cells where the UE receives the PDSCH corresponding to the second PUCCH, then for μ=0, N_2 is 5, for μ=1, N_2 is 5.5, and for μ=2, N_2 is 11; otherwise, if the RRC parameter PUSCH-ServingCellConfig's processingType2Enabled is set to enabled for the serving cell with the second PUSCH, then for μ=0, N_2 is 10, for μ=1, N_2 is 12, for μ=2, N_2 is 23, and for μ=3, N_2 is 36. If the overlapping group includes the first PUSCH, and if the processingType2Enabled of PUSCH-ServingCellConfig is set to enabled for serving cells with the first PUSCH and the second PUSCH, then for μ=0, N_2 is 5, for u=1, N_2 is 5.5, and for u=2, N_2 is 11; otherwise, if the processingType2Enabled of PDSCH-ServingCellConfig is set to enabled for all serving cells where the UE receives the PDSCH corresponding to the second PUCCH, then for μ=0, n_2 is 10, for μ=1, n_2 is 12, for μ=2, n_2 is 23, and for μ=3, n_2 is 36.

[0283] If the UE transmits the following channels, including duplicates (if any), the following overlaps will occur in time: a first PUCCH with a higher priority index and a second PUCCH or PUSCH with a lower priority index and an SR; or a configured grant PUSCH with a higher priority index and a PUCCH with a lower priority index; or a first PUCCH with a higher priority index, HARQ-ACK information only in response to PDSCH reception, and no corresponding PDCCH, and a second PUCCH with a lower priority index and SR and / or CSI; or a configured grant PUSCH with a lower priority index; or a PUSCH with a lower priority index, SP-CSI report, and no corresponding PDCCH; or a higher priority PUSCH with a lower priority index and an SR and / or CSI. If a PUSCH with a high priority index, an SP-CSI report, and no corresponding PDCCH, and a PUCCH with a lower priority index, an SR or CSI report, or a HARQ-ACK message that only responds to PDSCH reception, and no corresponding PDCCH; or an authorized PUSCH with a high priority index and a PUSCH with a lower priority index configured on the same serving cell, and if the repetition of the PUCCH / PUSCH transmission with the lower priority index overlaps with the PUCCH / PUSCH transmission with the high priority index in time, the UE may expect to cancel the repetition of the PUCCH / PUSCH transmission with the lower priority index before the first symbol overlapping with the PUCCH / PUSCH transmission with the higher priority index.

[0284] The UE may not expect to be scheduled to transmit a PUCCH or PUSCH with a lower priority index that overlaps in time with a PUCCH with a higher priority index, HARQ-ACK information that only responds to PDSCH reception, and which does not have a corresponding PDCCH. The UE may also not expect to be scheduled to transmit a PUCCH with a lower priority index that overlaps in time with a PUSCH with a higher priority index, SP-CSI report, and which does not have a corresponding PDCCH.

[0285] If the UE multiplexes the aperiodic CSI in the PUSCH, and the UE multiplexes the UCI including HARQ-ACK information in the PUCCH that overlaps with the PUSCH, and the timing conditions for overlapping PUCCH and PUSCH are met, then the UE can multiplex the HARQ-ACK information only in the PUSCH and not transmit the PUCCH.

[0286] If a UE transmits multiple PUSCHs in a time slot on the corresponding serving cell, including a first PUSCH scheduled by the DCI format and a second PUSCH configured by the corresponding RRC parameter ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE will reuse UCI in one of the multiple PUSCHs, and the multiple PUSCHs satisfy the UCI reuse condition, then the UE can reuse UCI in the PUSCH from the first PUSCH.

[0287] If a UE transmits multiple PUSCHs in a time slot on the corresponding serving cell, and the UE will reuse UCI in one of the multiple PUSCHs, and the UE does not reuse aperiodic CSI in any of the multiple PUSCHs, then the UE can reuse UCI in the PUSCH of the serving cell with the smallest RRC parameter ServCellIndex that satisfies the UCI reuse condition. If a UE transmits more than one PUSCH in a time slot on the serving cell with the smallest ServCellIndex that satisfies the UCI reuse condition, then the UE can reuse UCI in the earliest PUSCH that the UE transmits in the time slot.

[0288] If a UE transmits PUSCH on multiple time slots, and the UE will transmit a PUCCH with HARQ-ACK and / or CSI information on a single time slot, which overlaps with PUSCH transmissions in one or more of the multiple time slots, and the PUSCH transmissions in the one or more time slots satisfy the HARQ-ACK and / or CSI information multiplexing condition, then the UE can multiplex the HARQ-ACK and / or CSI information in the PUSCH transmissions in the one or more time slots. If the UE will transmit a single-slot PUCCH with HARQ-ACK and / or CSI information in a time slot without PUSCH transmission, then the UE may not multiplex the HARQ-ACK and / or CSI information in the PUSCH transmissions from the multiple time slots.

[0289] If PUSCH transmissions on the multiple time slots are scheduled using a DCI format that includes the DAI field, the value of the DAI field can be used to multiplex HARQ-ACK information in PUSCH transmissions in any of the multiple time slots in which the UE multiplexes HARQ-ACK information.

[0290] When a UE will multiplex HARQ-ACK information in a PUSCH transmission configured by the RRC parameter ConfiguredGrantConfig and including CG-UCI, 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 multiplex HARQ-ACK information in a PUCCH transmission or another PUSCH transmission.

[0291] If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be transmitted or multiplexed using UCI, then that time slot is considered usable for PUSCH transmission. If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be canceled, then that time slot is considered unusable for PUSCH transmission.

[0292] The procedure based on time slot configuration is described. If the PUSCH is scheduled by DCI or is configured with a configured authorization, the PUSCH will be transmitted unless otherwise specified.

[0293] If the UE is provided with the RRC parameter tdd-UL-DL-ConfigurationCommon, the UE can set the per-slot format (indicating which symbol type format, downlink symbol, uplink symbol, or flexible symbol, each symbol in the slot is) across multiple time slots, as indicated by tdd-UL-DL-ConfigurationCommon. If the UE is additionally provided with the RRC parameter tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-ConfigurationDedicated can override the flexible-only symbol configuration for each time slot across multiple time slots as provided by tdd-UL-DL-ConfigurationCommon.

[0294] For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in a set of symbols of a time slot, and if the UE does not detect a DCI format instructing the UE to transmit PUSCH, PUCCH, PRACH, or SRS in at least one symbol of that set of symbols in the time slot, then the UE receives PDCCH, PDSCH, CSI-RS, or DL ​​PRS; otherwise, the UE may not receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in that set of symbols of the time slot.

[0295] For operation on a single carrier in an unpaired spectrum, if the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH in a set of symbols within a time slot, and the UE detects a DCI format indicating that the UE will receive CSI-RS or PDSCH in a subset of symbols within that set of symbols, then: the following A), B), and C) may be applied. A) If the UE does not indicate the capability for partial cancellation, if the first symbol in the set occurs within T_(proc,2) relative to the last symbol of the CORESET in which the UE detects the DCI format, then the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in that set of symbols; otherwise, the UE cancels the actual repetition of PUCCH, PUSCH, or PUSCH or PRACH transmission in that set of symbols. B) If the UE indicates the capability for partial cancellation, then the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in the symbols within that set of symbols within T_(proc,2) relative to the last symbol of the CORESET in which the UE detects the DCI format. The UE cancels actual duplicate or PRACH transmissions of PUCCH or PUSCH or PUSCH in the remaining symbols of the symbol set. C) The UE does not expect to cancel SRS transmissions in symbols within a subset of symbols in which the last symbol of the CORESET in DCI format was detected by the UE within T_(proc,2). The UE cancels SRS transmissions in the remaining symbols of the symbol subset. T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capability assuming d_2,1=1, and μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH carrying DCI format and the SCS configuration of SRS, PUCCH, PUSCH or μ_r, where μ_r corresponds to the SCS configuration of PRACH if μ_r is 15kHz or higher; otherwise μ_r=0.

[0296] If the slot counting type configuration indicates that the number of repetitions is counted based on contiguous slots, the above processing time requirement can be applied: "If the first symbol in the group occurs within T_(proc,2) relative to the last symbol of the DCI format CORESET detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols." If the slot counting 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 group occurs within T_(proc,2)+d_x relative to the last symbol of the DCI format CORESET detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols; otherwise, the UE cancels the PUSCH transmission," where d_x is a positive value, can be applied. In other words, if the number of repetitions of PUSCH repetition type A is counted based on contiguous slots, the processing time requirement of T_(proc,2) can be applied. If the number of repetitions of PUSCH repetition type A is counted based on available slots, a longer processing time requirement can be applied.

[0297] For a time slot, a set of symbols is indicated to the UE as a downlink via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. When PUSCH, PUCCH, PRACH, or SRS overlaps with this set of symbols in the time slot, even if there is only partial overlap, the UE may not transmit PUSCH, PUCCH, PRACH, or SRS.

[0298] For a time slot, the UE may not expect to receive both the dedicated RRC parameters that configure the UE to transmit in that set of symbols in the time slot and the dedicated RRC parameters that configure the UE to receive in that set of symbols in the time slot.

[0299] For operation on a single carrier in an unpaired spectrum, for a set of symbols in a time slot for receiving an SS / PBCH block, indicated to the UE by the RRC parameter ssb-PositionsInBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, if the transmission would overlap with any symbol in that set of symbols and the UE does not transmit SRS in that set of symbols in the time slot, the UE may not transmit PUSCH, PUCCH, or PRACH in the time slot. When providing the UE with that set of symbols in the time slot, the UE may not expect that set of symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

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

[0301] If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be transmitted, then that time slot is considered available for PUSCH transmission. If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be canceled or not transmitted, then that time slot is considered unavailable for PUSCH transmission.

[0302] An example of the definition of T_(proc,2) is described. If, for a transport block, it includes a DM-RS as defined by the slot offset K2, and a PUSCH allocation start S and length L indicated by the "time-domain resource allocation" of the scheduling DCI, and including the effects of timing advance, the first uplink symbol in the PUSCH allocation is no earlier than symbol L2, where L2 is defined as the next uplink symbol after the end of reception of the last symbol of the PDCCH carrying the scheduling PUSCH of the DCI, where its CP start T_(proc,2), (T proc,2 =max((N2+d 2,1 +d2)(2048+144)·κ2 -μ ·T c +T ext +T switch ,d 2,2If the UE can transmit the transport block, then N2 is based on u for UE processing capabilities 1 and 2, respectively, where u corresponds to one of (μDL, μUL) generated using the maximum T_(proc,2), where μDL corresponds to the subcarrier spacing of the downlink PDCCH carrying the DCI of the scheduled PUSCH, and μUL corresponds to the subcarrier spacing of the uplink channel to which the PUSCH is to be transmitted, and the constant κ is 64. For operations with shared spectrum channel access, T_ext can be non-zero, otherwise T_ext = 0. If the first symbol of the PUSCH allocation consists only of DM-RS, then d2,1 = 0, otherwise d2,1 = 1. The time unit T_C = 1 / (Δf_"max"N_f), where Δf_"max" = 480 - 10^3 Hz and N_f = 4096. If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation also includes the effect of the timing difference between the component carriers. If the scheduling DCI triggers a BWP handover, then d2,2 equals the handover time; otherwise, d2,2 = 0. If a PUSCH with a higher priority index overlaps with a PUCCH with a lower priority index, then d2 for the PUSCH with the higher priority is set to be reported by the UE; otherwise, d2 = 0. For a UE supporting Capability 2 on a given cell, if the higher-layer parameter processingType2Enabled in PUSCH-ServingCellConfig is configured and set to "Enabled" for that cell, the processing time based on UE Capability 2 is applied. If a PUSCH indicated by the DCI overlaps with one or more PUCCH channels, the transport block is multiplexed; otherwise, the transport block is transmitted on the PUSCH indicated by the DCI. If an uplink handover gap is triggered, then T_switch equals the handover gap duration, and for a UE configured with the RRC parameter uplinkTxSwitchingOption set to "dualUL", for uplink carrier aggregation pUL = min(pUL,carrier1,pUL,carrier2), otherwise T_switch = 0. For PUSCH timing capability 1, the PUSCH preparation time N2 is 10, 12, 23, and 36 symbols for μ = 0, 1, 2, and 3, respectively. For PUSCH timing capability 2, the PUSCH preparation time N2 is 5, 5.5, and 11 symbols for μ = 0, 1, and 2 (for frequency range (FR) 1).

[0303] The procedure based on the time slot format is described. If the PUSCH is scheduled by DCI or is configured with a configured authorization, the PUSCH will be transmitted unless otherwise specified.

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

[0305] The SFI index field value in DCI format 2_0 can indicate to the UE the slot format of each slot in a plurality of slots for each DL BWP or each UL BWP, starting from the slot where the UE detects DCI format 2_0. The number of slots can be equal to or greater than the PDCCH monitoring periodicity of DCI format 2_0. The SFI index field may include a maxSFIindex digit, where maxSFIindex is the maximum value among the values ​​provided by the corresponding RRC parameter slotFormatCombinationId. The slot format can be identified by the corresponding format index as provided in the table, where each entry specifies a corresponding combination of “D”, “U”, and / or “F”, where “D” represents a downlink symbol, “U” represents an uplink symbol, and “F” represents a flexible symbol. Index 255 can instruct the UE to determine the slot format based on tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and based on the detected DCI format (if any).

[0306] For a set of symbols in a time slot, the UE may not expect to detect a DCI format 2_0 for the uplink of that set of symbols with an SFI index field value, and may not expect to detect a DCI format indicating that the UE receives PDSCH or CSI-RS in that set of symbols in the time slot.

[0307] For a set of symbols in a time slot, the UE may not expect to detect a DCI format 2_0 for downlink with an SFI index field value, and may not expect to detect a DCI format, RAR UL license, fallbackRAR UL license, or successRAR for PUSCH, PUCCH, PRACH, or SRS in that set of symbols in the time slot.

[0308] For a set of symbols in a time slot indicated as downlink / uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE may not expect to detect a set of symbols in the time slot with an SFI index field value indicating that the set of symbols in the time slot is uplink / downlink or flexible DCI format 2_0.

[0309] For a set of symbols indicated to the UE as a flexible time slot by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if any), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, and if the UE detects DCI format 2_0, which provides a time slot format value other than 255, at least the following A) through E) may be applied. A) If the SFI index field value in DCI format 2_0 indicates that the set of symbols for the time slot is flexible, and the UE detects DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, which instructs the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the set of symbols for the time slot, then the UE transmits PUSCH, PUCCH, PRACH, or SRS in the set of symbols for the time slot. B) If the SFI index field value in DCI format 2_0 indicates that the group of symbols in the time slot is flexible, and the UE does not detect a DCI format indicating that the UE receives PDSCH or CSI-RS, or the UE does not detect a DCI format indicating that the UE transmits PUSCH, PUCCH, PRACH, or SRS, RAR UL, fallbackRAR UL grant, or successRAR grant in the group of symbols in the time slot, then the UE will not transmit or receive in the group of symbols in the time slot. C) If the UE is configured by a higher layer to transmit PUCCH, PUSCH, or PRACH in the group of symbols in the time slot, then the UE will only transmit PUCCH, PUSCH, or PRACH in the time slot if the SFI index field value in DCI format 2_0 indicates that the group of symbols in the time slot is uplink. D) The UE does not expect to detect in DCI format 2_0 that the group of symbols indicating the time slot is a downlink SFI index field value, nor does it expect to detect DCI format, RAR UL license, fallbackRAR UL license, or successRAR indicating that the UE transmits SRS, PUSCH, PUCCH, or PRACH in one or more symbols of the group from the time slot. E) If the group of symbols in the time slot includes any repeating symbols corresponding to PUSCH transmissions activated (i.e., scheduled) by a UL Class 2 licensed PDCCH, the UE may not expect to detect in DCI format 2_0 that the group of symbols indicating the time slot is a downlink or flexible SFI index field value.

[0310] If the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH in a set of symbols of a time slot, and the UE detects DCI format 2_0 with a time slot format value other than 255, indicating that a subset of symbols from that set of symbols is a downlink or flexible time slot format, or the UE detects a DCI format indicating that the UE receives CSI-RS or PDSCH in a subset of symbols of that set of symbols, then the following A), B), and C) may be applied. A) If the UE does not indicate the capability of partial cancellation, if the first symbol in the set occurs within T_(proc,2) relative to the last symbol of the CORESET in which the UE detects the DCI format, then the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in that set of symbols; otherwise, the UE cancels the actual duplication of PUCCH, PUSCH, or PUSCH or PRACH transmission in that set of symbols. B) If the UE indicates the capability of partial cancellation, the UE does not expect to cancel the transmission of PUCCH, PUSCH, or PRACH in the symbols of the group of symbols within T_(proc,2) relative to the last symbol of the CORESET in DCI format where the UE detects it. The UE cancels the actual repetition of PUCCH, PUSCH, or PUSCH or PRACH transmission in the remaining symbols of the group of symbols. C) The UE does not expect to cancel the transmission of SRS in the symbols of the subset of symbols within T_(proc,2) relative to the last symbol of the CORESET in DCI format where the UE detects it. The UE cancels the transmission of SRS in the remaining symbols of the subset of symbols. T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capability assuming d_2,1=1, and μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH carrying DCI format and the SCS configuration of SRS, PUCCH, PUSCH or μ_r, where μ_r corresponds to the SCS configuration of PRACH if μ_r is 15kHz or higher; otherwise μ_r=0.

[0311] If the slot counting type configuration indicates that the number of repetitions is counted based on contiguous slots, the above processing time requirement can be applied: "If the first symbol in the group occurs within T_(proc,2) relative to the last symbol of the DCI format CORESET detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols." If the slot counting 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 group occurs within T_(proc,2)+d_x relative to the last symbol of the DCI format CORESET detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols; otherwise, the UE cancels the PUSCH transmission," where d_x is a positive value, can be applied. In other words, if the number of repetitions of PUSCH repetition type A is counted based on contiguous slots, the processing time requirement of T_(proc,2) can be applied. If the number of repetitions of PUSCH repetition type A is counted based on available slots, a longer processing time requirement can be applied.

[0312] The UE may assume that if the UE does not detect the SFI index field value of the group of symbols indicating the time slot in DCI format 2_0 as flexible or uplink, and the UE does not detect the DCI format indicating that the UE transmits SRS, PUSCH, PUCCH or PRACH in the group of symbols, then the flexible symbol in the CORESET configured for the UE for PDCCH monitoring is a downlink symbol.

[0313] For a set of symbols indicated as flexible time slots by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if any), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, and if the UE does not detect DCI format 2_0 providing a time slot format for the time slot, at least the following A) may be applied: A) If the UE receives the corresponding indication via DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, the UE transmits PUSCH, PUCCH, PRACH, or SRS in that set of symbols for the time slot.

[0314] If the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH in that group of symbols in a time slot, and the UE is not provided with the RRC parameter enableConfiguredUL, then the following A) and B) may apply. A) The UE does not transmit PUCCH, PUSCH, or PRACH in the time slot, and does not transmit SRS in some symbols from that group of symbols in the time slot, if any, the symbols begin after the last symbol of the CORESET of DCI format 2_0 in which the UE is configured to monitor the PDCCH, after the PUSCH preparation time T_(proc,2) for the corresponding PUSCH timing capability assuming d_2,l=1, and μ 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, where if μ_r is 15kHz or higher, then μ_r corresponds to the SCS configuration of PRACH; otherwise, μ_r=0. B) The UE does not expect to cancel the transmission of SRS, PUCCH, PUSCH, or PRACH in some symbols of this group of symbols from the time slot, if any, the symbols begin after the last symbol of the CORESET of DCI format 2_0 in which the UE is configured to monitor the PDCCH, and before the symbol after the PUSCH preparation time T_(proc,2) for the corresponding PUSCH timing capability assuming d_2,1=1, and μ 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, where if μ_r is 15kHz or higher, μ_r corresponds to the SCS configuration of PRACH; otherwise μ_r=0.

[0315] If the slot counting type configuration indicates that the number of repetitions is counted based on contiguous slots, the above processing time requirement can be applied: "If the first symbol in the group occurs within T_(proc,2) relative to the last symbol of the CORESET of DCI format 2_0 monitored by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols." If the slot counting 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 group occurs within T_(proc,2)+d_x relative to the last symbol of the CORESET of DCI format 2_0 monitored by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols; otherwise, the UE cancels the PUSCH transmission," where d_x is a positive value, can be applied. In other words, if the number of repetitions of PUSCH repetition type A is counted based on contiguous slots, the processing time requirement of T_(proc,2) can be applied. If the number of repetitions of PUSCH repetition type A is counted based on available slots, a longer processing time requirement can be applied.

[0316] If the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH in that group of symbols of a time slot, and the UE is provided with enableConfiguredUL, then the UE may transmit SRS, PUCCH, PUSCH, or PRACH respectively.

[0317] If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be transmitted, then the time slot is considered available for PUSCH transmission. If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be canceled or not transmitted, or if at least one symbol in the time slot used for PUSCH is determined to be a downlink symbol, then the time slot is considered unavailable for PUSCH transmission.

[0318] The procedure based on the cancellation instruction is described. If the PUSCH is scheduled by DCI or is configured with a configured authorization, the PUSCH will be transmitted unless otherwise stated.

[0319] If the UE is provided with the RRC parameter UplinkCancellation, then in one or more serving cells, the UE may be provided with a search space set for monitoring first PDCCH candidates, wherein the CCE aggregation level of the search space set is L_CI CCE, for detecting DCI format 2_4 with CI-RNTI provided by ci-RNTI.

[0320] For a serving cell with an associated field in DCI format 2_4, this field can be represented as: N_"CI", the number of bits, provided by the RRC parameter ci-PayloadSize; B_"CI", the number of PRBs, provided by the RRC parameter frequencyRegionforCI in the RRC parameter timeFrequencyRegion; T_"CI", the number of symbols from multiple symbols excluding those used to receive SS / PBCH blocks and DL symbols indicated by tdd-UL-DL-ConfigurationCommon, provided by the RRC parameter timeDurationforCI in the RRC parameter timeFrequencyRegion if the PDCCH monitoring periodicity of the search space set of DCI format 2_4 is one time slot and there are more than one PDCCH monitoring opportunity in the time slot, otherwise it is equal to the PDCCH monitoring periodicity; and G_"CI", the number of times T_"CI" symbols are divided, provided by the RRC parameter timeGranularityforCI in the RRC parameter timeFrequencyRegion.

[0321] The indications for the serving cell via DCI format 2_4 may be applied to PUSCH or SRS transmissions on the serving cell. If a PUSCH or SRS transmission is scheduled by DCI format, the indications of DCI format 2_4 may be applied to the PUSCH or SRS transmission only if the last symbol of a PDCCH reception provided by DCI format is earlier than the first symbol of a PDCCH reception provided by DCI format 2_4. For the serving cell, the UE can determine that the first symbol among T_CI symbols is the first symbol after T'_(proc,2) from which the UE detects the end of the reception of a PDCCH of DCI format 2_4, where T'_(proc,2) is derived from T_(proc,2) for a PUSCH processing capability 2 with the assumption d_2,1 = d_offset·2^(-μ_UL) / 2^(-μ), where d_offset is provided 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 scs-SpecificCarrierList of the RRC parameter FrequencyInfoUL or FrequencyInfoUL-SIB. The UE may not expect to cancel PUSCH transmission or SRS transmission before the corresponding symbol of T_(proc,2) with the assumption d_2,1 = 0 after the last symbol of the CORESET of DCI format 2_4.

[0322] If the slot counting type configuration indicates that the number of repetitions is counted based on contiguous slots, the above processing time requirement can be applied: "If the first symbol in the group occurs within T'_(proc,2) relative to the last symbol of the PDCCH of DCI format 2_4 detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols." If the slot counting 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 group occurs within T'_(proc,2)+d_x relative to the last symbol of the PDCCH of DCI format 2_4 detected by the UE, the UE does not expect to cancel the transmission of PUSCH in that group of symbols; otherwise, the UE cancels the PUSCH transmission," where d_x is a positive value, can be applied. In other words, if the number of repetitions of PUSCH repetition type A is counted based on contiguous slots, the processing time requirement of T'_(proc,2) can be applied. If the number of repetitions of PUSCH repetition type A is counted based on available slots, a longer processing time requirement can be applied.

[0323] If the UE is provided with the RRC parameter uplinkCancellationPriority, a set of symbols from T_"CI" symbols that have at least one bit value "1" in the corresponding set of N_BI bits in DCI format 2_4, and includes symbols of PUSCH transmission (which repeats) or SRS transmission; and a set of PRBs from B_"CI" PRBs that have a corresponding bit value "1" in the corresponding set of bits in DCI format 2_4, and include PUSCH transmission (which repeats) or SRS transmission, if the PUSCH transmission has repetition type B, then the UE detecting DCI format 2_4 for the serving cell can cancel the PUSCH transmission (including PUSCH transmission with repetition type A) or the actual repetition of the PUSCH transmission, or if correspondingly, if the transmission is a PUSCH with priority 0, then the SRS transmission on the serving cell can be canceled. Cancellation of PUSCH transmission (which repeats) can include all symbols from the set of symbols with a corresponding bit value "1" in DCI format 2_4 from the earliest symbol of the PUSCH transmission (which repeats). Cancellation of SRS transmission may be included only in symbols that have a corresponding bit value "1" in DCI format 2_4 within one or more symbol groups.

[0324] If the UE cancels a PUSCH or SRS transmission based on the indication of DCI format 2_4, the UE may not expect to be scheduled by the second DCI format to transmit PUSCH or SRS on symbols that include the canceled PUSCH or SRS transmission, wherein the last symbol of PDCCH reception provided by the second DCI format is later than the first symbol of PDCCH reception provided by DCI format 2_4.

[0325] If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be transmitted, then that time slot is considered available for PUSCH transmission. If a PUSCH (or a repeat of a PUSCH) in a time slot is determined to be canceled or not transmitted, then that time slot is considered unavailable for PUSCH transmission.

[0326] When counting repetitions based on available time slots, several sub-options may exist, taking into account conditions in procedures based on PUSCH priority, time slot configuration, time slot format, and cancellation indication. Conditions in the time slot configuration procedure always apply. Whether conditions in other procedures apply may depend on the specific RRC configuration.

[0327] The first sub-option is a single slot count type configuration applicable to all conditions. More specifically, if the slot count type configuration indicates that the number of repetitions is counted based on available slots, and if the available slot type configuration (indicating whether the available slots are determined based solely on a semi-static configuration or on both semi-static configuration and dynamic signaling, which may or may not be the same as the slot count type configuration) indicates that dynamic signaling is used to determine available slots, then available slots can be determined based on all conditions of the corresponding RRC configuration provided. For example, if phy-PriorityIndex or priorityIndicatorDCI is provided, conditions in a PUSCH priority-based procedure are applicable, while if phy-PriorityIndex or priorityIndicatorDCI is not provided, conditions in a PUSCH priority-based procedure (a procedure for determining whether to transmit PUSCH based on the PUSCH priority index) may not be applicable. If SlotFormatCombinationsPerCell (i.e., the RRC parameter / configuration that triggers the slot-format-based procedure (the procedure that determines whether to transmit the PUSCH based on the slot format)) is provided, the conditions in the slot-format-based procedure are applicable; otherwise, the conditions in the slot-format-based procedure may not be applicable. Similarly, if UplinkCancellation (i.e., the RRC parameter / configuration that triggers the cancellation indicator-based procedure (the procedure that determines whether to transmit the PUSCH based on the cancellation indicator) is provided, the conditions in the cancellation indicator-based procedure are applicable; otherwise, the conditions in the cancellation indicator-based procedure may not be applicable.

[0328] Using the first sub-option, if the UE has a coverage enhancement feature and / or if the UE is configured with a coverage enhancement feature, alternatively or additionally, if the UE is configured with a slot counting type configuration indicating that PUSCH repetitions are counted based on available slots and / or if the UE is configured with an available slot type configuration indicating that dynamic signaling is used to determine available slots, the following can be applied. For both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE can repeat TB across K available slots (i.e., the first K slots available for PUSCH transmission), thereby applying the same symbol allocation in each slot. The K available slots can be determined based on conditions in the slot configuration-based procedure and additionally in the PUSCH priority-based procedure, the slot format-based procedure, and the cancellation indication-based procedure.

[0329] Using the first sub-option, if the UE has a coverage enhancement feature and / or if the UE is configured with a coverage enhancement feature, alternatively or additionally, if the UE is configured with a slot counting type configuration indicating that PUSCH repetitions are counted based on available slots and / or if the UE is configured with an available slot type configuration indicating that only semi-static configuration is used to determine available slots, then the following can be applied. For both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE can repeat TB across K available slots (i.e., the first K slots available for PUSCH transmission), thereby applying the same symbol allocation in each slot. The K available slots can be determined based on conditions in the slot configuration-based procedure, but without reference to conditions in the PUSCH priority-based procedure, the slot format-based procedure, and the cancellation indication-based procedure.

[0330] The second sub-option has several slot count type configurations, each applicable to conditions in the corresponding procedure. More specifically, if the available slot type configuration for a PUSCH priority-based procedure indicates that PUSCH priority-based transmission / cancellation is used to determine available slots, then available slots can 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 transmission / cancellation is used to determine available slots, then available slots can be determined according to the slot format-based procedure. If the available slot type configuration for a cancellation indication-based procedure indicates that cancellation indication-based transmission / cancellation is used to determine available slots, then available slots can be determined according to the cancellation indication-based procedure. For example, if phy-PriorityIndex or priorityIndicatorDCI is provided, and additionally if an available slot type configuration for a PUSCH priority-based procedure is provided indicating the use of a PUSCH priority-based procedure, then conditions in the PUSCH priority-based procedure are applicable; otherwise, conditions in the PUSCH priority-based procedure may not be applicable. If `SlotFormatCombinationsPerCell` is provided, and additionally if a configuration of available slot types for a slot-format-based procedure is provided indicating the use of a slot-format-based procedure, then the conditions in the slot-format-based procedure are applicable; otherwise, the conditions in the slot-format-based procedure may not apply. If `UplinkCancellation` is provided, and additionally if a configuration of available slot types for a cancellation-indication-based procedure is provided indicating the use of a cancellation-indication-based procedure, then the conditions in the cancellation-indication-based procedure are applicable; otherwise, the conditions in the cancellation-indication-based procedure may not apply. Any combination of the above may also be applied. For example, if a configuration of available slot types for a PUSCH priority-based procedure is provided, and if a configuration of available slot types for a slot-format-based procedure is provided, but not for a cancellation-indication-based procedure, then available slots can be determined based on the slot-configured procedure and also based on the conditions in the PUSCH priority-based procedure and the slot-format-based procedure; however, the conditions based on the cancellation-indication-based procedure are not relevant to determining available slots.

[0331] Using the second sub-option, if the UE is able to have a certain coverage enhancement feature and / or if the UE is configured with a certain coverage enhancement feature, alternatively or additionally, if the UE is configured with a slot counting type configuration indicating that PUSCH repetitions are counted based on available slots, and if the UE is configured with at least one of an available slot type configuration for a procedure based on PUSCH priority, a procedure based on slot format, and a procedure based on cancellation indication, then the following can be applied: For both Class 1 and Class 2 PUSCH transmissions with configured authorization, when K>1, the UE can repeat TB across K available slots (i.e., the first K slots available for PUSCH transmission), thereby applying the same symbol allocation in each slot. K available time slots can be determined based on conditions in the time slot-based configuration procedure, and if available time slot type configurations for the PUSCH priority-based procedure, the time slot format-based procedure, or the cancellation indication-based procedure are provided accordingly, K available time slots can also be determined based on conditions in the PUSCH priority-based procedure, the time slot format-based procedure, and the cancellation indication-based procedure.

[0332] If only semi-static configuration is used to determine available time slots and / or no dynamic signaling is used to determine available time slots, the UE determines K time slots for PUSCH transmission, starting from the time slot instructing the UE to perform PUSCH transmission, and having A) UL symbols as described in the time slot configuration procedure, or flexible symbols of non-SS / PBCH block symbols; and B) consecutive UL symbols, or flexible symbols of non-SS / PBCH block symbols, starting from the first symbol as described in the time slot configuration procedure, equal to or greater than the number of symbols in the time slot and the number of symbols in the time slot that can be provided by time-domain resource allocation information for PUSCH.

[0333] It should be noted that the above-mentioned available time slot type configurations may be referred to by different names. The presence of an available time slot type configuration in the RRC configuration message means that conditions in the time slot configuration procedure and other procedures are used to determine available time slots, while the absence of an available time slot type configuration in the RRC configuration message means that conditions in the time slot configuration procedure are used, but conditions in other procedures are not used to determine available time slots. Additionally and / or alternatively, an available time slot type configuration set to a first value (e.g., "semi-static") means that conditions in the time slot configuration procedure are used, but conditions in other procedures are not used to determine available time slots, while an available time slot type configuration set to a second value (e.g., "dynamic") means that conditions in the time slot configuration procedure and other procedures are used to determine available time slots.

[0334] Figure 9 This is an exemplary configuration of the frame structure according to aspects of the embodiments of this disclosure. Figure 9In the diagram, the horizontal axis indicates the time domain. Within the time domain, time slots are numbered in ascending order from time slot #n (the time slot with index n). Each row in the time domain indicates a time slot boundary. 9001 indicates the downlink region. 9002 indicates the flexible region. 9003 indicates the uplink region.

[0335] The area indicated by 9000 includes a set of areas 9001, 9002, and 9003. Area 9000 can be configured based on time slot configuration. For example, time slot configuration may include at least a downlink area, a flexible area, and an uplink area. For example, time slot configuration may be configured such that the time slot configuration begins at a UL to DL handover point. Furthermore, time slot configuration may be configured such that the time slot configuration ends at another UL to DL handover point. For example, the UL to DL handover point may be the point where the uplink area ends and the downlink area begins.

[0336] For example, time slot configurations can be repeated in the time domain. Figure 9 The configuration repeats, including three downlink time slots, one special time slot, and one uplink time slot. Region 9000 is an instance of a time slot configuration starting at time slot #n, and Region 9010 is an instance of a time slot configuration starting at time slot #n+5. Figure 9 In this configuration, the repeating cycle of the time slot configuration is 5 time slots.

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

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

[0339] "U" indicates that the time slot is an uplink time slot. An uplink time slot is a time slot with an uplink region. Figure 9 In the table, time slots #n+4 and #n+9 are uplink time slots.

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

[0341] exist Figure 9 In this context, the time slot configuration can also be referred to as "DDDSU". "DDDSU" means that the time slot configuration includes 3 downlink time slots, 1 special time slot and 1 uplink time slot.

[0342] The configuration of a special time slot can be represented by "XDYFZU". Here, 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 time slot includes 10 downlink symbols, 2 flexible symbols, and 2 uplink symbols.

[0343] Downlink symbols are OFDM symbols within the downlink area. Flexible symbols are OFDM symbols within the flexible area. Uplink symbols are OFDM symbols within the uplink area.

[0344] Time slot configuration can be provided by RRC parameters. For example, time slot configuration can be provided by common parameters included in system information such as SIB1. Common parameters can also be referred to as tdd-UL-DL-ConfigurationCommon.

[0345] For example, terminal device 1 can determine the reference subcarrier spacing configuration u based on common parameters. ref The first TDD pattern includes one or more of T1 through T5. T1 is the configuration period P provided by referenceSubcarrierSpacing, in milliseconds. 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 .

[0346] Figure 10 This is an exemplary configuration of time slot configuration according to aspects of the embodiments of this disclosure. Figure 10 In the diagram, the horizontal axis indicates the time domain. Within the time domain, time slots are numbered in ascending order from time slot #n (the time slot with index n). Each row in the time domain indicates a time slot boundary. 10000 indicates the time slot configuration. In the time slot configuration, the first d, as indicated by region 10001, represent the... slots = Two time slots are configured as downlink time slots. In the time slot configuration, as indicated by area 10002, the last u slots = 1 time slot is configured as an uplink time slot. In the time slot configuration, as indicated in area 10003, in the slot with index n+d slots The first d starting from the first OFDM symbol in the time slot symOne OFDM symbol is configured as a downlink symbol. In the time slot configuration, as indicated in region 10004, in the slot with index n+Su slots The last u before the first OFDM symbol in the time slot sym One OFDM symbol is configured as an uplink symbol. In the time slot configuration, the remaining OFDM symbols not indicated as downlink or uplink areas, as indicated by area 1005, are flexible symbols.

[0347] The time slot configuration can be modified by UE-specific parameters. These UE-specific parameters are also known as tdd-UL-DL-CoifigurationDedicated.

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

[0349] For example, terminal device 1 can determine a list including a set of time slot reconfigurations via UE-specific parameters. In each time slot reconfiguration within this set, at least one or both of a time slot index and an indication of the time slot's TDD pattern can be provided. This indication can indicate one of "All DL", "All UL", and "Explicit". When "All DL" is indicated for a time slot, the time slot configuration within the time slot is reconfigured as a downlink area. When "All UL" is indicated for a time slot, the time slot configuration within the time slot is reconfigured as an uplink area. When "Explicit" is indicated for a time slot, the time slot configuration within the time slot is reconfigured by an explicit indication corresponding to "Explicit". The "Explicit" indication corresponds to information indicating the TDD pattern within the time slot. This information includes information indicating the number of downlink symbols starting at the beginning of the time slot and information indicating the number of uplink symbols ending at the end of the time slot. The remaining OFDM symbols between the downlink and uplink symbols are flexible symbols.

[0350] If terminal device 1 is configured by a higher layer or indicated by the DCI format to receive physical signals in the downlink area, then terminal device 1 can receive physical signals.

[0351] If terminal device 1 is configured by a higher layer or indicated by the DCI format to transmit physical signals in the uplink area, then terminal device 1 may transmit physical signals.

[0352] If terminal device 1 is indicated by the DCI format 2_0 of the scheduling physical channel to receive in the downlink area or flexible area when the monitoring of the higher layer is not configured, terminal device 1 may receive physical signals.

[0353] If the terminal device 1 is not configured with DCI format 2_0 for monitoring at higher levels, and the terminal device 1 is indicated by the DCI format of the scheduled physical signal to be transmitted in the uplink area or flexible area, then the terminal device 1 may transmit physical signals.

[0354] With DCI format 2_0 monitoring configured at the higher level, terminal device 1 can determine whether to receive physical signals based at least on the indications in DCI format 2_0.

[0355] With DCI format 2_0 monitoring configured at the higher level, terminal device 1 can determine whether to transmit physical signals based at least on the indications in DCI format 2_0.

[0356] The configuration for monitoring DCI format 2_0 may include at least one or more of S1 to S3. S1 is the identifier of the serving cell. S2 is information indicating the bit positions of a field used for the index of the slot format indicator. S3 is a set of slot format combinations. Here, each slot format combination may include one or more slot formats. Each of the slot format combinations may include an index of the slot format indicator. Each slot format may indicate a TDD pattern within 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, a slot format indicates that the first 9 OFDM symbols in the slot are downlink symbols, the next 3 OFDM symbols in the slot are flexible symbols, and the remaining 2 OFDM symbols are uplink symbols. For example, a slot format instructs terminal device 1 to interpret the monitoring as if DCI format 2_0 were not configured. Other TDD patterns within the slot are not excluded.

[0357] When terminal device 1 detects DCI format 2_0 in the first time slot, terminal device 1 applies the time slot format combination indicated by the index of the time slot format indicator in DCI format 2_0. For example, the time slot format combination can be applied to the time slot starting at the first time slot.

[0358] The behavior of PUSCH transmissions can be controlled, at least based on the instructions in DCI format 2_0. For example, a PUSCH transmission can be a repetition of a PUSCH instance, where the PUSCH instance is confined to a time slot.

[0359] A PUSCH instance can be a unit for baseband signal generation. Here, baseband signal generation can be performed by baseband unit 13.

[0360] Figure 11This is an exemplary configuration of the baseband unit 13 in the wireless transmission unit 10a according to an embodiment of the present disclosure. The baseband unit 13 may include at least some or all of the following: encoder 12000, scrambler 11001, modulator 11002, layer mapper 11003, transform pre-encoder 11004, pre-encoder 11005, resource element mapper 11006, and time continuous signal generator 11007.

[0361] A transport block can be provided to encoder 12000 from a higher layer. For example, a transport block can be provided to encoder 12000 from MAC layer processing unit 15 via UL-SCH. Encoder 12000 processes the transport block into a sequence b of coded bits. The sequence of coded bits can be provided to scrambler 11001. The element at position k in sequence b can be called b(k). Position k is between 0 and M. bit The range is -1. Position k is represented by an integer. M bit This represents the length of sequence b.

[0362] For example, scrambler 11001 can scramble the sequence of coded bits b using 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, scrambler 11001 can compute b... a (k) = mod(b(k) + c(k), 2) Output sequence b a b a (k) is the sequence b a The element at position k. In the absence of scrambler 11001 in baseband unit 13, the sequence b of coded bits can be input to b. a .

[0363] The pseudo-random code c can be a sequence of bits generated by scrambler 11001. For example, the pseudo-random code c can be generated by an equation with initialization variables. The initialization variables can determine or control the output from the equation. The initialization variables can be determined at least based on the RNTI used to schedule the transmission of the uplink transport block.

[0364] For example, modulator 11002 can perform operations on sequence b a The modulation generates a sequence d containing complex-valued symbols. The element at position j in sequence d is called d(j). Position j ranges from 0 to M. symb The range is -1. Position j is represented by an integer. M symb This represents the length of sequence d. In the case where baseband unit 13 does not include modulator 11002, the sequence b of encoded bits... a You can enter d.

[0365] For example, the modulation can be 2 / pi BPSK (binary phase shift keying), QPSK (quadrature phase shift keying), 16QAM (quadrature amplitude modulation), 64QAM or 256QAM.

[0366] For example, layer mapper 11003 can perform layer mapping on sequence d. After layer mapping, sequences of length M are generated. layer symb N v N sequences. v N is the number of layers used for PUSCH. v The v-th sequence in a sequence is called x. (v) Sequence x (v) The element at position h is called x (v) (h).

[0367] Position h is between 0 and M layer symb The range is -1. Position h is represented by an integer. In the quantity N... v When the value is 1, layer mapper 11003 may not perform layer mapping. Without performing layer mapping on sequence d, sequence d can be input to x. (0) .

[0368] For example, the transform precoder 11004 can process sequence x (v) Perform transform precoding and generate sequence y (v) Without sequence x (v) When performing transform precoding, sequence x (v) Input can be given to sequence y (v) .

[0369] For example, the pre-encoder 11005 can process the sequence y (v) Perform precoding. After precoding, generate each with a length M. layer symb N p N sequences. p N is the number of antenna ports used for PUSCH. p The p-th sequence in the sequence is called z. (p) Sequence z (p) The element at position h is called z. (p) (h). In quantity N p When the value is 1, the precoder 11005 may not perform precoding. This applies to sequences y... (v) When precoding is performed, sequence y (v) You can input z (p) .

[0370] For example, resource element mapper 11006 can perform RE mapping. In RE mapping, a set of elements z(h) = [z (0) (h),…,z (Np-1) [(h)] is mapped to a resource element.

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

[0372] The baseband unit 33 may include corresponding components for receiving PUSCH, such as baseband unit 13.

[0373] Figure 12 This is an exemplary configuration of encoder 12000 according to an aspect of the present disclosure. Encoder 12000 may include at least some or all of CRC addition unit 12001, CB segmentation unit 12002, encoding unit 12003, rate matching unit 12004, and multiplexing unit 12005.

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

[0375] For example, if the sequence length exceeds a certain value, the sequence input to the code block segmentation unit 12002 is segmented into multiple code blocks. When the sequence is segmented into multiple code blocks, a CRC sequence is added to each code block. Each code block after the CRC sequence is added 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, a CRC sequence is not added to a 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.

[0376] For example, a code block with index r (code block #r) input to encoding unit 12003 is encoded using LDPC encoding, such as QC-LDPC (quasi-cyclic low-density parity check) encoding. The index r is in the range of 0 to C-1. C is the number of code blocks determined in code block segmentation unit 12002. The encoded bits d of code block #r after LDPC encoding are... rIt is input to the rate matching unit 12004.

[0377] For example, the rate matching unit 12004 executes a bit selection procedure. In the bit selection procedure, the encoded bit d of code block r... r The length written is N cb In the circular buffer.

[0378] Figure 13 This is an example of a bit selection procedure according to an embodiment of the present disclosure. In the bit selection procedure, two values ​​k and j are set to 0, as in step 0. Next, in step 1, the rate matching unit 12004 checks whether the value k is less than the rate matching output sequence length E. r If the value k is less than the rate-matched output sequence length E r Then the rate matching unit 12004 proceeds to step 2. If the value k is not less than the length E of the rate matching output sequence. r Then the rate matching unit 12004 terminates the bit selection procedure.

[0379] Here, the rate-matched output sequence length E r This indicates the number of available bits for transmission of code block #r. For example, the rate of code block #r matches the output sequence length E. r It can be calculated based on at least some or all of the following: modulation order Q m The number of layers N used for PUSCH v The numbers C' and G. For example, the rate of code block r matches the output sequence length E. r It can be calculated as: 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 C')).

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

[0381] In step 2, the rate matching unit 12004 verifies d. r (mod(k0+j,N cb Is it not? <null>If d r (mod(k0+j,N cb ))No <null>Then the rate matching unit 12004 proceeds to step 3. If d r (mod(k0+j,N cb ))for <null>Then the rate matching unit 12004 proceeds to step 5.

[0382] Here, "d r (mod(k0+j,N cb ))for <null>"means for" <null>Set to d r (mod(k0+j,N cb When the element corresponds to the padding bits used for LDPC encoding, it can be... <null>Set to d r Some elements.

[0383] Here, in d r The element at position k is called d r (k).

[0384] In step 3, the rate matching unit 12004 will d r (mod(k0+j,N cb The value in )) is set to e(k). Sequence e is the rate-matched output sequence. The element at position k in sequence e is called e(k).

[0385] Here, k o This indicates the starting point of the circular buffer.

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

[0387] Step 5 marks the end of Step 2.

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

[0389] Step 7 marks the end of Step 1. Rate matching unit 12004 returns to Step 1.

[0390] Figure 14 This is an exemplary configuration of a circular buffer according to an embodiment of this disclosure. In the circular buffer, the encoded bit d... r Clockwise mapping begins at the position indicated by RV0. Due to the encoding bit d... r The system consists of system bits, followed by parity bits. Mapping begins at the position indicated by RV0, and mapping begins at the end of the system bits. The region indicated by the upper right slant line is filled with system bits. The region indicated by the lattice lines is filled with parity bits.

[0391] In the bit selection procedure, bits in the circular buffer are read starting from point k0, with a length of E. r The bits read from the circular buffer are written into the rate-matched output sequence e.

[0392] The starting point k is determined based on the redundancy version indicated or determined by the redundancy version field in the uplink DCI format used for dynamic scheduling. o .

[0393] For example, the starting point k can be determined based on the identification of redundant versions and instances. o For example, in the case of repeated PUSCH scheduling in a DCI format, terminal device 1 can transmit multiple instances. For each instance, a starting point k0 can be determined. For example, in the case of 8 instances (instance #0, instance #1, instance #2, instance #3, instance #4, instance #5, instance #6, instance #?) in a DCI format scheduling, 8 starting points k can be determined. o .

[0394] For example, an RV (Redundant Version) sequence can be provided to terminal device 1. When an RV sequence is provided, an RV is assigned to each of multiple instances based on that sequence. For example, when providing a sequence of length N... s Given the sequence [0,2,3,1], the (mod(n,N)th digit of the sequence... s (+1) values ​​can be assigned to the nth instance. The starting point k of the nth instance can be determined based on the RV assigned to it. o .

[0395] Figure 15 This is an exemplary configuration of a first type of repetition of PUSCH scheduled in DCI format across multiple time slots according to an embodiment of this disclosure. Figure 15 In the diagram, 15000 indicates a PDCCH with DCI format, which schedules a PUSCH with first-type repeating. Assuming in... Figure 15 The first type of repetition is scheduled in the time slot starting at time slot #n+3. 15001 indicates an instance of PUSCH in time slot #n+3. Here, the value S indicates the starting OFDM symbol index within the time slot used for instance 15001. Furthermore, the value L indicates the length in terms of the number of OFDM symbols used for instance 15001. Instance 15001 is followed by six instances indicated by 15002 to 15007. Each instance is mapped within a time slot. Figure 15 In this case, assume the number of repetitions is K. rep It is 7.

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

[0397] exist Figure 15 In this context, S is applied to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within the time slot. Figure 15 In this context, L is applied to all instances of PUSCH. For example, all instances apply the same length in terms of the number of OFDM symbols.

[0398] In the first type of repetition, K can begin at the time slot determined by the DCI format of the scheduling PUSCH. rep Multiple instances of PUSCH are allocated across consecutive time slots. For example, if the DCI format for scheduling PUSCH includes a TDRA field, the TDRA field can provide a value K for determining the starting time slot of the PUSCH. For example, the value K is in time slots. For example, if a PDCCH including the DCI format is detected in time slot #n, terminal device 1 can determine the starting time slot as time slot #(n+K). If the DCI format does not include TDRA, the value K can be provided by the RRC layer through RRC parameters.

[0399] A first-type repeating RV sequence can be provided to terminal device 1. For example, the sequence can be provided by the RRC layer via RRC parameters. In the case of providing an RV sequence for the first-type repeating, the (mod(n,N))th RV sequence... s ()+1) values ​​can be assigned to the nth instance. Here, an index can be provided to each instance of PUSCH in ascending order in the time domain.

[0400] For Type 1 duplication, if an instance overlaps with a downlink symbol determined by the time slot configuration, the transmission of that instance may be omitted (or discarded, canceled, or not transmitted).

[0401] For the first type of repetition, the transmission of that instance may be omitted if the instance overlaps with a downlink symbol determined by the time slot format.

[0402] For Type 1 duplication, if an instance overlaps with another uplink signal having a higher priority than the current PUSCH, the transmission of that instance can be omitted. For example, the uplink signal could be a second PUSCH with a higher priority than the current PUSCH. The priority of the PUSCH could be provided by the DCI format that schedules the PUSCH.

[0403] Figure 16 This is an exemplary configuration of a second type of repetition of PUSCHs scheduled in a DCI format across multiple time slots according to an embodiment of this disclosure. Figure 16 In this context, 16000 indicates a PDCCH with DCI format, which schedules a PUSCH with second-type repetition. Assume second-type repetition is scheduled in a time slot starting at time slot #n+3. 16001 indicates an instance of PUSCH in time slot #n+3. Here, the value S indicates the starting OFDM symbol index within the time slot used for this instance. Furthermore, the value L indicates the length in terms of the number of OFDM symbols used for this instance. Instance 16001 follows the three instances indicated by 16002 to 16004. Each instance is mapped within a time slot. Figure 16 In this case, assume the number of repetitions is K. rep It is 4.

[0404] exist Figure 16 In this context, S is applied to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within the time slot. Figure 16 In this context, L is applied to all instances of PUSCH. For example, all instances apply the same length in terms of the number of OFDM symbols.

[0405] In the second type of repetition, K can begin at the time slot determined by the DCI format of the scheduling PUSCH. rep Multiple instances of PUSCH are allocated across consecutive available time slots. For example, if the DCI format for scheduling PUSCH includes a TDRA field, the TDRA field can provide a value K for determining the starting time slot of the PUSCH. For example, the value K is in time slots. For example, in the case where terminal device 1 can determine the starting time slot as time slot #(n+K). If the DCI format does not include TDRA, the value K can be provided by the RRC layer through RRC parameters.

[0406] In the second type of repetition, K can be determined by the time slot configuration. rep A time slot is available in consecutive slots. For example, a time slot is available if the set of OFDM symbols allocated to an instance in the time slot does not overlap with any downlink symbols determined by the time slot configuration. For example, a time slot is available if the set of OFDM symbols determined by values ​​S and L in the time slot does not overlap with any downlink symbols determined by the time slot configuration. Values ​​S and L can be provided by the TDRA field in the DCI format. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16001 does not overlap with 9001, time slot #n+3 can be used for type II repetition. In other words, because each OFDM symbol allocated to instance 16001 overlaps with either 9002 or 9003, time slot #n+3 can be used for type II repetition. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16002 does not overlap with 9001, time slot #n+4 can be used for type II repetition. In other words, because each OFDM symbol allocated to instance 16002 overlaps with 9003, time slot #n+4 can be used for type II repetition. Figure 16 In this context, because a set of OFDM symbols determined by values ​​S and L overlaps with 9011, time slot #n+5 cannot be used for type 2 repetition. In other words, because a set of OFDM symbols determined by values ​​S and L does not overlap with 9002 or 9003, time slot #n+5 cannot be used for type 2 repetition.

[0407] An RV sequence for the second type of repetition can be provided to terminal device 1. For example, the sequence can be provided by the RRC layer via RRC parameters. In the case of providing an RV sequence for the second type of repetition, the (mod(n,N))th RV sequence... s ()+1) values ​​can be assigned to the nth instance. Here, an index can be provided to each instance of PUSCH in ascending order in the time domain.

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

[0409] For example, a first sequence can be provided by an RRC layer using a first RRC parameter. Alternatively, a second sequence can be provided by an RRC layer using a second RRC parameter that is different from the first RRC parameter.

[0410] For the second type of duplication, if the instance overlaps with a downlink symbol determined by the time slot configuration, the transmission of that instance can be omitted. On the other hand, for the second type of duplication, since K may already be determined... rep The process of handling conflicts with downlink symbols configured by the time slots within a series of consecutive available time slots may not result in any instances overlapping with downlink symbols determined by the time slot configuration. Therefore, for Type II duplication, it may not be possible to omit the transmission of that instance based on the time slot configuration. For example, for Type II duplication, terminal device 1 may not be able to determine whether to omit the instance based on the time slot configuration. For example, terminal device 1 may not perform the process of determining whether to omit the instance based on the time slot configuration.

[0411] For the second type of repetition, the transmission of that instance may be omitted if the instance overlaps with a downlink symbol determined by the time slot format.

[0412] For type 2 duplication, if an instance overlaps with another uplink signal having a higher priority than the current PUSCH, the transmission of that instance can be omitted. For example, the uplink signal could be a second PUSCH with a higher priority than the current PUSCH. The priority of the PUSCH could be provided by the DCI format that schedules it.

[0413] use Figure 16 The hypothesis K is described rep =3 is the third type of repetition.

[0414] In the third type of repetition, multiple instances of PUSCH can be allocated on consecutive available time slots starting at the time slot determined by the DCI format of the scheduling PUSCH.

[0415] In type 3 repetition, consecutively available time slots can be determined by time slot configuration. For example, a time slot is available if a set of OFDM symbols allocated to an instance within that time slot does not overlap with any downlink symbols determined by the time slot configuration. For example, a time slot is available if a set of OFDM symbols determined by the values ​​S and L provided by the TDRA field in the DCI format does not overlap with any downlink symbols determined by the time slot configuration. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16001 does not overlap with 9001, time slot #n+3 can be used for type 3 repetition. In other words, because each OFDM symbol allocated to instance 16001 overlaps with either 9002 or 9003, time slot #n+3 can be used for type 3 repetition. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16002 does not overlap with 9001, time slot #n+4 can be used for type 3 repetition. In other words, because each OFDM symbol allocated to instance 16002 overlaps with 9003, time slot #n+4 can be used for type 3 repetition. Figure 16 In this context, because a set of OFDM symbols determined by values ​​S and L overlaps with 9011, time slot #n+5 cannot be used for type 3 repetition. In other words, because a set of OFDM symbols determined by values ​​S and L does not overlap with 9002 or 9003, time slot #n+5 cannot be used for type 3 repetition.

[0416] An RV sequence for third-type repetition can be provided to terminal device 1. For example, the sequence can be provided by the RRC layer via RRC parameters. In the case of providing an RV sequence for third-type repetition, the (mod(n,N))th RV sequence... s (1)+1) values ​​can be assigned to the nth instance. For example, a first RV sequence and a third RV sequence 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.

[0417] For example, a first sequence can be provided by an RRC layer using a first RRC parameter. Alternatively, a third sequence can be provided by an RRC layer using a third RRC parameter that is different from the first RRC parameter.

[0418] For type 3 duplication, if an instance overlaps with a downlink symbol determined by the time slot configuration, the transmission of that instance can be omitted. On the other hand, for type 3 duplication, since conflict resolution with the downlink symbol determined by the time slot configuration may have already been completed in the procedure for determining consecutive available time slots, there may not be a situation where an instance overlaps with a downlink symbol determined by the time slot configuration. Therefore, for type 3 duplication, it may not be possible to omit the transmission of that instance based on the time slot configuration. For example, for type 3 duplication, terminal device 1 may not be able to determine whether to omit the instance based on the time slot configuration. For example, terminal device 1 may not perform the procedure for determining whether to omit the instance based on the time slot configuration.

[0419] For the third type of repetition, the transmission of that instance may be omitted if the instance overlaps with a downlink symbol determined by the time slot format.

[0420] For type 3 duplication, if an instance overlaps with another uplink signal having a higher priority than the current PUSCH, the transmission of that instance can be omitted. For example, the uplink signal could be a second PUSCH with a higher priority than the current PUSCH. The priority of the PUSCH could be provided by the DCI format that schedules it.

[0421] For the third type of repetition, determine the first K. rep Each instance is used for PUSCH transmission. For example, without any instances being omitted, the terminal device can determine instances 16001, 16002, and 16003 as the first K. rep Examples. For instance, if instance 16002 is omitted due to a conflict with a high-priority signal, the terminal device determines instances 16001, 16003, and 16004 as the top K. rep Examples. For instance, if instance 16003 is omitted due to a conflict with a high-priority signal, the terminal device determines instances 16001, 16002, and 16004 as the top K. rep One example.

[0422] use Figure 16 The hypothesis K is described rep =3 is the fourth type of repetition.

[0423] In the fourth type of repetition, multiple instances of PUSCH can be allocated on consecutive available time slots starting at the time slot determined by the DCI format of the scheduling PUSCH.

[0424] In Type IV repetition, consecutively available time slots can be determined by time slot configuration. For example, a time slot is available if a set of OFDM symbols allocated to an instance within that time slot does not overlap with any downlink symbols determined by the time slot configuration. For example, a time slot is available if a set of OFDM symbols determined by the values ​​S and L provided by the TDRA field in the DCI format does not overlap with any downlink symbols determined by the time slot configuration. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16001 does not overlap with 9001, time slot #n+3 can be used for type four repetition. In other words, because each OFDM symbol allocated to instance 16001 overlaps with either 9002 or 9003, time slot #n+3 can be used for type four repetition. Figure 16 In this context, because the set of OFDM symbols allocated to instance 16002 does not overlap with 9001, time slot #n+4 can be used for fourth-type repetition. In other words, because each OFDM symbol allocated to instance 16002 overlaps with 9003, time slot #n+4 can be used for fourth-type repetition. Figure 16 In this context, because a set of OFDM symbols determined by values ​​S and L overlaps with 9011, time slot #n+5 cannot be used for type 4 repetition. In other words, because a set of OFDM symbols determined by values ​​S and L does not overlap with 9002 or 9003, time slot #n+5 cannot be used for type 4 repetition.

[0425] Before determining the RV for each instance, terminal device 1 may determine whether one or more instances are omitted. For example, if no instances are omitted, terminal device 1 may determine that instances 16001, 16002, and 16003 are among the top K. rep Examples. For instance, if instance 16002 is omitted due to a conflict with a high-priority signal, the terminal device determines instances 16001, 16003, and 16004 as the top K. rep Examples. For instance, if instance 16003 is omitted due to a conflict with a high-priority signal, the terminal device determines instances 16001, 16002, and 16004 as the top K. rep One example.

[0426] An RV sequence for fourth-type repetition can be provided to terminal device 1. For example, the sequence can be provided by the RRC layer via RRC parameters. In the case of providing an RV sequence for fourth-type repetition, the (mod(n,N))th RV sequence... s (+1) values ​​can be assigned to the first K rep The nth instance in a set of instances. For example, a first RV sequence and a fourth RV sequence can be provided to terminal device 1. For example, the first sequence can be used for a first type of repetition. For example, the fourth sequence can be used for a fourth type of repetition.

[0427] For example, a first sequence can be provided by an RRC layer using a first RRC parameter. Alternatively, a fourth sequence can be provided by an RRC layer using a fourth RRC parameter that is different from the first RRC parameter.

[0428] For Type 4 duplication, if an instance overlaps with a downlink symbol determined by the time slot configuration, the transmission of that instance can be omitted. On the other hand, for Type 4 duplication, since conflict resolution with the downlink symbol determined by the time slot configuration may have already been completed in the procedure for determining consecutive available time slots, there may not be a situation where an instance overlaps with a downlink symbol determined by the time slot configuration. Therefore, for Type 4 duplication, it may not be possible to omit the transmission of that instance based on the time slot configuration. For example, for Type 4 duplication, terminal device 1 may not be able to determine whether to omit the instance based on the time slot configuration. For example, terminal device 1 may not perform the procedure for determining whether to omit the instance based on the time slot configuration.

[0429] For the fourth type of repetition, the transmission of that instance may be omitted if the instance overlaps with a downlink symbol determined by the time slot format.

[0430] For type 4 repetition, if an instance overlaps with another uplink signal having a higher priority than the current PUSCH, the transmission of that instance can be omitted. For example, the uplink signal could be a second PUSCH with a higher priority than the current PUSCH. The priority of the PUSCH could be provided by the DCI format that schedules the PUSCH.

[0431] For the fourth type of repetition, K is transmitted before... rep One instance is used for PUSCH transport.

[0432] Figure 17 This is an exemplary configuration of a first type of repeating authorized PUSCH in multiple time slots according to aspects of this disclosure. Figure 17 In the diagram, 17010 indicates the period of the configured authorization. 17011 indicates the period of the configured authorization. Periods 17010 and 17011 are configured periodically. The configured authorization occurs in the starting OFDM symbol of period 17010. In the case where the configured authorization occurs in the starting OFDM symbol of period 17010, it is assumed that the first type of repetition is scheduled in the time slot starting at time slot #n+3, where time slot #n+3 includes the starting OFDM symbol. 17001 indicates an instance of PUSCH in time slot #n+3. Here, the value S indicates the starting OFDM symbol index within the time slot used for instance 17001. Furthermore, the value L indicates the length in terms of the number of OFDM symbols used for instance 17001. Instance 17001 follows the five instances indicated by 17002 to 17006. Each instance is mapped within a time slot. Figure 17 In this case, assume the number of repetitions is K. rep It is 6.

[0433] Here, PUSCH is associated with period 17010. Furthermore, PUSCH is associated with instances 17001 through 17006.

[0434] For example, values ​​S and L can be provided by the RRC layer via RRC parameters. Alternatively, values ​​S and L can be provided by the TDRA field in the DCI format of the authorization operation for activation configuration.

[0435] 17007 indicates an instance of another PUSCH. Instance 17007 is not part of a repetition of PUSCH within period 17010. Instance 17007 is the first instance of another PUSCH within period 17011. Here, a period can define the timing of including the number of repetitions of a single PUSCH. For example, if two instances are included in different periods, then these two instances are associated with different PUSCHs.

[0436] Here, another PUSCH is associated with period 17011. In addition, another PUSCH is associated with instances 17001 to 17006.

[0437] A PUSCH with instances occurring within a period is associated with that period. PUSCHs are associated with these instances.

[0438] exist Figure 17 In this context, S is applied to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within the time slot. Figure 17 In this context, L is applied to all instances of PUSCH. For example, all instances apply the same length in terms of the number of OFDM symbols.

[0439] In the first type of repetition, K can begin at the time slot of the initial OFDM symbol that includes the period. rep Multiple instances of PUSCH are allocated on consecutive time slots.

[0440] Figure 18 This is an exemplary configuration of a second type of repeating authorized PUSCH with configuration in multiple time slots according to aspects of the embodiments of this disclosure. Figure 18 In this context, 18001 indicates an instance of PUSCH in time slot #n+3. Here, the value S indicates the starting OFDM symbol index within the time slot used for this instance. Furthermore, the value L indicates the length in terms of the number of OFDM symbols used for this instance. Following the two instances indicated by 18002 and 18003 is instance 18001. Each instance is mapped within a time slot.

[0441] exist Figure 18 In this case, assume the number of repetitions is K. rep Yes, it is 4. On the other hand, instance 18004 is not associated with a PUSCH. Instance 18004 is the first instance associated with another PUSCH within period 17011.

[0442] For example, for the second type of repetition, it can be based on the quantity K. rep The period is used to determine a set of instances of PUSCH associated with that period. For example, if an instance of PUSCH exceeds the period associated with that PUSCH, that instance can be excluded from that set of instances of PUSCH. For example, K rep This indicates the maximum number of instances of PUSCH, and the instance mapping within the period ensures that the number of instances does not exceed the number K. rep .

[0443] exist Figure 18 In this context, the value S is applied to all instances of PUSCH. For example, all instances apply the same starting OFDM symbol index within the time slot. Figure 18 In this context, the value L is applied to all instances of PUSCH. For example, all instances apply the same length in terms of the number of OFDM symbols.

[0444] In the second type of repetition, multiple instances of PUSCH can be allocated on consecutive available time slots, starting at the time slot of the starting OFDM symbol of the period associated with PUSCH.

[0445] use Figure 18 The hypothesis K is described rep =4 is the third type of repetition.

[0446] In the third type of repetition, multiple instances of PUSCH can be allocated on consecutive available time slots, starting at the time slot of the starting OFDM symbol of the period associated with PUSCH.

[0447] For example, for the third type of repetition, it can be based on the quantity K. rep The period is used to determine a set of instances of PUSCH associated with that period. For example, if an instance of PUSCH exceeds the period associated with that PUSCH, that instance can be excluded from that set of instances of PUSCH. For example, K rep This indicates the maximum number of instances of PUSCH, and the instance mapping within the period ensures that the number of instances does not exceed the number K. rep .

[0448] use Figure 16 The hypothesis K is described rep =4, the fourth type of repetition.

[0449] In the fourth type of repetition, multiple instances of PUSCH can be allocated on consecutive available time slots, starting at the time slot of the starting OFDM symbol of the period associated with PUSCH.

[0450] Figure 19 An example of a method for a UE is shown. The method may include obtaining a first RRC parameter (step 1901) and transmitting PUSCH in multiple time slots (step 1902). If the first RRC parameter is set to a first value, the conditions in the time slot formatting procedure may not be used to determine multiple time slots. If the first RRC parameter is set to a second value, the conditions in the time slot formatting procedure can be used to determine multiple time slots.

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

[0452] There are two types of transports without dynamic grants. One is Type 1 granted grants, where the uplink grant is provided by the RRC and stored as a configured uplink grant; the other is Type 2 granted grants, where the uplink grant is provided by the PDCCH and stored as a configured uplink grant or cleared based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and Type 2 are configured by the RRC of the serving cell for each BWP. Multiple configurations can be active simultaneously within the same BWP. For Type 2, activation and deactivation are independent between serving cells. For the same BWP, a MAC entity can be configured with both Type 1 and Type 2.

[0453] When a Class 1 grant is configured, the RRC configures the following parameters: `cs-RNTI` is used to determine the CS-RNTI used for retransmission. `periodicity` is used to determine the periodicity of the Class 1 grant. `timeDomainOffset` is used to determine the offset of the resource relative to the time domain SFN = `timeReferenceSFN`. `timeDomainAllocation` is used to determine the allocation of uplink grants for the time domain configuration containing `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 configuration grant for operations utilizing shared spectrum 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, which is used to determine the offset of the resource in the time domain. The UE uses the SFN closest to the indicated number before receiving the configured grant configuration.

[0454] When Class 2 license configuration is configured, the RRC configuration uses the following parameters: `cs-RNTI` determines the CS-RNTI used for retransmission; `periodicity` determines the periodicity of the Class 2 license; `nrofHARQ-Processes` determines the number of HARQ processes configured for the license; `harq-ProcID-Offset` determines the offset of the configured licensed HARQ processes for operations utilizing shared spectrum channel access; and `harq-ProcID-Offset2` determines the offset of the configured licensed HARQ processes.

[0455] When retransmission on configured uplink grant is configured, RRC configures the following parameters. cg-RetransmissionTimer is used to determine the duration after the configured grant (re)transmission of the HARQ process when the UE may be unable to retransmit the HARQ process independently.

[0456] When granting an uplink grant for a BWP configured by an upper layer for the serving cell, the MAC entity may have to store the uplink grant provided by the upper layer as an uplink grant configured for the indicated BWP for the serving cell, and initialize or reinitialize the configured uplink grant according to timeDomainOffset, timeReferenceSFN, and S (derived from SLIV or provided by startSymbol) to start in the symbol and retransmit periodically.

[0457] After granting uplink authorization for a Class 1 configuration, the MAC entity may have to sequentially consider the Nth (N≥0) uplink authorization occurring in the symbol described below, for which [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in the frame×numberOfSymbolsPerSlot)+number of symbols in the slot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

[0458] After granting uplink authorization for Class 2 configurations, the MAC entity may have to sequentially consider the Nth (N≥0) uplink authorization occurring in the symbol described below, for which [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in the frame×numberOfSymbolsPerSlot)+number of symbols in the slot]=[(SFNstart time×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstart time×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity]modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

[0459] If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for authorization in a Type 1 or Type 2 configuration, the MAC entity may have to consider uplink authorization occurring in those additional PUSCH allocations as specified in the UE procedure in order to utilize resource allocation for uplink transmissions with configured authorization to transmit the PUSCH.

[0460] If available slot-based counting is configured for Class 1 authorization, the MAC entity may have to consider that the Nth (N≥0) uplink authorization occurs in the first symbol of the first available slot as specified in the UE procedure, which is associated with a transport block repetition of an uplink transmission of PUSCH repetition type A with a configured authorization at or after the symbol described below, for that symbol [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in the frame×numberOfSymbolsPerSlot)+number of symbols in the slot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

[0461] If available slot-based counting is configured for Class 2 configuration grants, the MAC entity may have to consider that the Nth (N≥0) uplink grant occurs in the first symbol of the first available slot as specified in the UE procedure, which is associated with a transport block repetition of an uplink transmission of PUSCH repetition type A with a configured grant at or after the symbol described below, for that symbol [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in the frame×numberOfSymbolsPerSlot)+number of symbols in the slot]=[(SFNstart time×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstart time×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity]modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot).

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

[0463] In the case of unaligned SFNs across carriers in a cell group, the SFN of the relevant serving cell is used to calculate the occurrence of configured uplink grants.

[0464] When the configured uplink license is released by the upper layer, it may be necessary to release all corresponding configurations and clear all corresponding uplink licenses.

[0465] If at least one configured uplink grant acknowledgment has been triggered and not cancelled, and if the MAC entity has allocated UL resources for the new transport, and if at least one configured uplink grant in the MAC entity is configured by `configuredGrantConfigToAddModList`, then the MAC entity may have to instruct the multiplexer and assembler to generate multiple configured grant acknowledgment MAC CEs. Alternatively, the MAC entity may have to instruct the multiplexer and assembler to generate configured grant acknowledgment MAC CEs. Or, the MAC entity may have to cancel all triggered configured uplink grant acknowledgments.

[0466] For Class 2 configuration authorizations, the MAC entity may need to clear the configured uplink authorization immediately after the first transmission of the configuration authorization confirmation MAC CE or multiple configuration authorization confirmation MAC CEs.

[0467] Retransmissions use the configured uplink grant for duplicates or uplink grants addressed to the CS-RNTI or configured uplink grants with cg-RetransmissionTimer.

[0468] The MAC entity includes a HARQ entity for each serving cell with a configured uplink (including when it is configured with a supplementary uplink), which maintains multiple parallel HARQ processes.

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

[0470] Each HARQ process supports one TB.

[0471] Each HARQ process is associated with a HARQ process identifier. HARQ process identifier 0 is used for UL transfers with UL authorization in the RA response or for UL transfers targeting the MSGA payload.

[0472] When a single DCI is used to schedule multiple PUSCHs, it allows the UE to map generated TBs within different HARQ processes in the event of an LBT failure. That is, the UE can transmit a new TB on any HARQ process with the same TBS, the same RV, and the NDI indicating the new transmission.

[0473] The maximum number of TBs transmitted within a dynamically granted or configured grant packet is given by REPETITION_NUMBER. For dynamically granted grants, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in the UE procedure associated with 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, to utilize resource allocation for uplink transmissions with configured grants to transmit PUSCH.

[0474] If REPETITION_NUMBER > 1, after the first transmission within the packet, a subsequent REPETITION_NUMBER-1 HARQ retransmission occurs within the packet. For dynamically granted and configured uplink grants, the packetization operation relies on the HARQ entity to invoke the same HARQ process for each transmission that is part of the same packet. Within the packet, HARQ retransmissions are triggered based on the REPETITION_NUMBER used for dynamically granted or configured uplink grants without waiting for feedback from previous transmissions, unless they terminate as specified in the UE procedure for transmitting PUSCH. Each transmission within the packet is a separate uplink grant delivered to the HARQ entity.

[0475] K available time slots can be configured based on REPETITION_NUMBER.

[0476] If the UE is configured with the higher-level parameter pusch-TimeDomainAllocationListForMultiPUSCH, then the UE does not expect to be configured with pusch-AggregationFactor.

[0477] Figure 21 An example table of applicable PUSCH time-domain resource allocations for DCI format 0_0 in the public search space and UE-specific search space is shown.

[0478] Figure 22 An example table of applicable PUSCH time-domain resource allocations for DCI format 0_1 ​​scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI is shown for a UE-specific search space.

[0479] Figure 23 An example table of applicable PUSCH time-domain resource allocations for DCI format 0_2 scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or SP-CSI-RNTI is shown for a UE-specific search space.

[0480] Figure 24 An example table of the default PUSCH time-domain resource allocation A for a normal CP is shown. Combined with... Figure 24 For a normal CP, a specific value j of the subcarrier spacing is used to determine K2.

[0481] Figure 21 , Figure 22 and Figure 23 This specifies which PUSCH time-domain resource allocation configuration should be applied. Figure 21 , Figure 22 and Figure 23 Used to determine the resource allocation table to be used for PUSCH.

[0482] When the UE is scheduled to transmit a PUSCH that has no transport block but has a CSI report provided by the "CSI Request" field on the DCI, the DCI's "Time Domain Resource Allocation" field value m is as follows: Figure 21 , Figure 22 , Figure 23 and Figure 24 The allocation table defined in the document provides row index m+1.

[0483] For PUSCH repetition type A, the starting symbol S relative to the start of the time slot and the number L of consecutive symbols assigned to the PUSCH, counting from symbol S, are determined based on the start and length indicator SLIV of the index row.

[0484] For PUSCH repetition type B, the starting symbol S relative to the start of the time slot and the number of consecutive symbols L allocated to the PUSCH, counting from symbol S, are provided by startSymbol and the length of the index row of the resource allocation table, respectively.

[0485] For PUSCH repeating type A, the PUSCH mapping type is set to type A or type B, as defined in Precoding, and mapped to the physical resource as given by the index row.

[0486] For PUSCH repeating type B, the PUSCH mapping type is set to type B.

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

[0488] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is enabled, the UE determines N*K slots for PUSCH transmissions with 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, as well as the TDRA information field value in DCI format 0_1 ​​or 0_2. If at least one symbol in a slot, indicated by the index row of the resource allocation table used, 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-PositionsInBurst, then that slot is not counted in the number of N*K slots for PUSCH transmissions with PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2. Otherwise, the UE determines the N*K consecutive time slots for PUSCH transmissions with 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.

[0489] As described above, there are two counting methods: available slot counting (also known as available slot-based counting) and physical slot counting (also known as consecutive slot counting, consecutive slot counting, or regular / normal / traditional counting). In available slot counting, the N*K earliest available slots no earlier than the slot determined by slot offset K2 can be identified as slots for PUSCH transmission, wherein a slot is not counted as an available slot if at least one of the symbols in the slot indicated by the index row of the resource allocation table used (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. In physical timeslot counting, N*K consecutive timeslots starting with the timeslot determined by timeslot offset K2 can be identified as timeslots for PUSCH transmission, regardless of whether they overlap with DL symbols or SS / PBCH block symbols. It should be noted that, depending on conflicts with other channels and / or signals, actual transmissions within the timeslots identified for PUSCH may or may not be further discarded.

[0490] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K consecutive time slots for PUSCH transmission with 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.

[0491] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K consecutive time slots for PUSCH transmission of a transport block with 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.

[0492] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K consecutive time slots for PUSCH transmission with 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.

[0493] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K consecutive time slots for PUSCH transmission of a transport block with 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.

[0494] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is enabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K slots for PUSCH transmission with 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, as well as the TDRA information field value in DCI format 0_1 ​​or 0_2. If at least one of the symbols in a time slot, indicated by the index row of the resource allocation table used, 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-PositionsInBurst, then that time slot may not be counted in the number of N*K time slots for PUSCH transmission of a transport block with PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2.

[0495] For unpaired spectrum, when the RRC parameter AvailableSlotCounting is disabled and the UE is scheduled to transmit a PUSCH with no transport block but a CSI report provided by the "CSI Request" field on the DCI, the UE can determine the N*K slots for PUSCH transmission with 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, as well as the TDRA information field value in DCI format 0_1 ​​or 0_2. If at least one of the symbols in a time slot, indicated by the index row of the resource allocation table used, 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-PositionsInBurst, then that time slot may not be counted in the number of N*K time slots for PUSCH transmission of a transport block with PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2.

[0496] For unpaired spectrum, the UE determines N*K time slots for PUSCH transmissions with TB processing on multiple time slots based on the values ​​of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst, as well as the TDRA information field values ​​in DCI format 0_1 ​​or 0_2. If at least one of the symbols in a time slot, indicated by the index row of the resource allocation table used, 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-PositionsInBurst, then that time slot is not counted in the number of N*K time slots for PUSCH transmissions with TB processing on multiple time slots.

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

[0498] For unpaired spectrum, the UE determines the N*K time slots for PUSCH transmissions with PUSCH repetition type A scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, based on the values ​​of the TDRA information field in tdd-UL-DL-ConfigurationCommon and ssb-PositionslnBurst and the DCI that schedules the PUSCH. If at least one symbol in a time slot, indicated by the index row of the resource allocation table used, overlaps with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon (if provided) or a symbol of an SS / PBCH block with an index provided by ssb-PositionsInBurst, then that time slot is not counted in the number of N*K time slots for PUSCH transmissions with PUSCH repetition type A scheduled by DCI format 0_0 with TC-RNTI scrambled by TC-RNTI.

[0499] For paired spectrum and SUL band, regardless of whether the RRC parameter AvailableSlotCounting is enabled, the UE determines the N*K consecutive time slots for PUSCH transmissions with PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, or for PUSCH transmissions with TB processing on multiple time slots scheduled by DCI format 0_1 ​​or 0_2, based on the TDRA information field value in DCI format 0_1 ​​or 0_2. For UEs with reduced half-duplex capability, and when the RRC parameter AvailableSlotCounting is enabled, if at least one of the symbols in a slot, indicated by the index row of the resource allocation table used, overlaps with a symbol of an SS / PBCH block with an index provided by ssb-PositionslnBurst, then that slot is not counted in the number of slots used for PUSCH transmissions with PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, or for PUSCH transmissions with TB processing on multiple slots scheduled by DCI format 0_1 ​​or 0_2.

[0500] For paired spectrum and SUL band, the UE determines N*K consecutive time slots for PUSCH transmissions with PUSCH repetition type A scheduled by the RAR UL grant based on the TDRA information field value in the RAR UL grant.

[0501] For paired spectrum and SUL band, the UE determines the N*K consecutive time slots for PUSCH transmission with PUSCH repetition type A, scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, based on the TDRA information field value in the DCI of the scheduled PUSCH.

[0502] If the RRC parameter AvailableSlotCounting is enabled, and the UE will transmit TB processing on multiple slots or PUSCH with PUSCH repetition type A on N*K slots, and the UE will not transmit TB processing on multiple slots or PUSCH with PUSCH repetition type A on slots from N*K slots, then the UE will count these slots in the total number of N*K slots according to the UE procedure for reporting control information, the UE procedure associated with slot configuration, and the UE procedure associated with cancellation indication.

[0503] For PUSCH repetition type A, if K>1 and the PUSCH is scheduled by DCI format 0_1 ​​or 0_2, and if the RRC parameter AvailableSlotCounting is enabled, the same symbol allocation is applied across the N*K slots determined for PUSCH transmission, and the PUSCH is limited to a single transport layer. The UE may have to repeat TB across the N*K slots determined for PUSCH transmission, thus applying the same symbol allocation in each slot. Otherwise, the same symbol allocation is applied across N*K consecutive slots, and the PUSCH is limited to a single transport layer. The UE may have to repeat TB across N*K consecutive slots, thus applying the same symbol allocation in each slot. Additionally, if the PUSCH is scheduled by RAR UL-licensed scheduling or by DCI format 0_0 with a CRC scrambled by TC-RNTI, the same symbol allocation is applied across the N*K slots determined for PUSCH transmission, and the PUSCH is limited to a single transport layer. The UE may have to repeat the TB across N*K time slots determined for PUSCH transmission, thus applying the same symbol allocation in each time slot.

[0504] For TB processing across multiple time slots, for unpaired spectrum, the same symbol allocation is applied across N*K time slots determined for PUSCH transmission, and the PUSCH is limited to a single transport layer. The UE may have to transmit the TB across the N*K time slots determined for PUSCH transmission, thus applying the same symbol allocation in each time slot. For paired spectrum or supplemental uplink bands, the same symbol allocation is applied across N*K consecutive time slots, and the PUSCH is limited to a single transport layer. The UE may have to transmit the TB across N*K consecutive time slots, thus applying the same symbol allocation in each time slot.

[0505] For PUSCH transmissions scheduled by DCI format 0_1, 0_2, or 0_0 with CRC scrambled by TC-RNTI, according to Figure 25 Determine the redundant version to be applied at the nth transmission time of TB, where n = 0, l, ... N*K-1.

[0506] For PUSCH transmissions with PUSCH repetition type A that are scheduled by RAR UL authorization, according to Figure 25 The first line determines the redundant version to be applied at the nth transmission time of TB, where n = 0, l, ... N*K-1.

[0507] For PUSCH repetition type A and TB processing on multiple time slots, PUSCH transmission in the time slot of multi-time slot PUSCH transmission is omitted based on the conditions in the UE procedure for reporting control information, the UE procedure associated with time slot configuration, and the UE procedure associated with cancellation indication.

[0508] For PUSCH repetition type B, after determining invalid symbols for each repetition in K nominal repetitions for PUSCH repetition type B transmission, the remaining symbols are considered potentially valid symbols for PUSCH repetition type B transmission. If, for a nominal repetition, the number of potentially valid symbols for PUSCH repetition type B transmission is greater than zero, the nominal repetition consists of one or more actual repetitions, where each actual repetition consists of a consecutive set of all potentially valid symbols available for PUSCH repetition type B transmission within the time slot. Actual repetitions with a single symbol are omitted except in the case where L=1. Actual repetitions are omitted based on conditions in the UE procedure for reporting control information, the UE procedure associated with time slot configuration, and the UE procedure associated with cancellation indication. The UE may have to repeat TB across actual repetitions. Figure 25 Determine the redundant version to be applied to the Nth actual repetition (with a count including omitted actual repetitions), where N = 1.

[0509] For PUSCH repetition type B, when the UE receives a DCI and schedules an aperiodic CSI report via the "CSI Report" field on the DCI or activates a semi-persistent CSI report on a PUSCH without a transport block, the nominal repetition count is always assumed to be 1, regardless of the value of numberOfRepetitions. When the UE is scheduled to transmit a PUSCH repetition type B without a transport block and with an aperiodic or semi-persistent CSI report provided by the "CSI Request" field on the DCI, the first nominal repetition is expected to be the same as the first actual repetition. For PUSCH repetition type B, which carries a semi-persistent CSI report on a PUSCH after activation via the "CSI Request" field on the DCI without a corresponding PDCCH, if the first nominal repetition differs from the first actual repetition, the first nominal repetition is omitted; otherwise, the first nominal repetition is omitted based on conditions in the UE procedure for reporting control information, the UE procedure associated with time slot configuration, and the UE procedure associated with cancellation indication.

[0510] For PUSCH repetition type B, when the UE is scheduled to transmit transport blocks and aperiodic CSI reports provided on the PUSCH by the "CSI Request" field on the DCI, the CSI reports are multiplexed only on the first actual repetition. The UE does not expect the first actual repetition to have a single symbol duration.

[0511] If the `pusch-TimeDomainAllocationListForMultiPUSCH` in the `pusch-Config` contains a line indicating resource allocation for two to eight contiguous PUSCHs, K2 indicates the time slot of the first PUSCH in which the UE may have to transmit multiple PUSCHs. Each PUSCH has a separate SLIV and mapping type. The number of scheduled PUSCHs is signaled as the number of valid SLIVs indicated in the line of `pusch-TimeDomainAllocationListForMultiPUSCH`, signaled in DCI format 0_1.

[0512] For pushch-TimeDomainAllocationListForMultiPUSCH-rl7 in pushch-Config, each PUSCH has a separate SLIV, mapping type, and K2. The number of scheduled PUSCHs is signaled as the number of SLIVs indicated in the line of pushch-TimeDomainAllocationListForMultiPUSCH-r17, signaled in DCI format 0_1.

[0513] For both Category 1 and Category 2 PUSCH transmissions with configured authorization, when K>1, for unpaired spectrum, if the RRC parameter AvailableSlotCounting is enabled, the UE may have to repeat the TB across the N*K slots determined for PUSCH transmission, thus applying the same symbol allocation in each slot. If at least one of the symbols in a slot, indicated by the index row of the resource allocation table used, 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, then that slot is not counted in the total number of N*K slots. Otherwise, the UE may have to repeat the TB across N*K consecutive time slots, thus applying the same symbol allocation in each time slot, unless the UE has the higher-layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats the TB in the earliest consecutive transmission opportunity candidates within the same configuration repK.

[0514] For both Category 1 and Category 2 PUSCH transmissions with configured authorization, when K>1, for paired spectrum, regardless of whether AvailableSlotCounting is enabled, the UE may have to repeat the TB across N*K consecutive slots, thus applying the same symbol allocation in each slot, unless the UE has the RRC parameters cg-nrofSlots and cg-nrofPUSCH-InSlot set, in which case the UE repeats the TB in the repK earliest consecutive transmission opportunity candidates within the same configuration. If the RRC parameter AvailableSlotCounting is enabled, and in the case of a UE with reduced half-duplex capability, if at least one symbol in a slot, indicated by the index row of the resource allocation table used, overlaps with a symbol of an SS / PBCH block with an index provided by ssb-PositionslnBurst, then that slot is not counted in the total number of N*K slots.

[0515] Based on the conditions in the UE procedure for reporting control information, the UE procedure associated with time slot configuration, and the UE procedure associated with cancellation indication, omitting Class 1 or Class 2 PUSCH transmissions with configured authorization in the time slot.

[0516] For PUSCHs without UL-SCH and / or PUSCHs with only CSI, it can be assumed in the foregoing procedure that N=1 and K=1. The UE and base station for this case are described.

[0517] The UE may include higher-layer processing circuitry configured to acquire at least a first RRC parameter indicating whether available slot counting is enabled. The first RRC parameter may be named AvailableSlotCounting. Possible values ​​for the first RRC parameter may be "enabled" and "disabled". 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 PUSCH scheduling. This can also be described as the receiving circuitry monitoring and detecting PDCCHs carrying a DCI format. The UE may also include transmission circuitry configured to transmit PUSCHs in one or more slots scheduled by the DCI format. The UE may transmit a PUSCH upon detecting a PDCCH with a DCI format that is scheduled for PUSCH.

[0518] A base station communicating with a UE may include functional units associated with functional units on the UE side and may execute procedures associated with procedures on the UE side. The base station (also referred to as a gNB) may include higher-layer processing circuitry configured to transmit at least a first RRC parameter indicating whether available time slot counting is enabled. The base station may also include transmission circuitry configured to transmit a DCI format (e.g., DCI format 0_1 ​​or DCI format 0_2) for PUSCH scheduling. This can also be described as the transmission circuitry transmitting a PDCCH carrying a DCI format. The base station may also include receiving circuitry configured to receive PUSCH in one or more time slots scheduled by the DCI format. The base station may monitor and receive PUSCH while transmitting a DCI format PDCCH with scheduled PUSCH.

[0519] The DCI format may include multiple information fields. These multiple information fields may include a Time Domain Resource Allocation (TDRA) field. These multiple information fields may include a CSI Request field. These multiple information fields may include a UL-SCH Indicator field. A trigger state can be initiated using the CSI Request field in the DCI. When all bits of the CSI Request field in the DCI are set to zero, no CSI is requested. Each of the other values ​​of the CSI Request field in the DCI corresponds to and indicates the corresponding trigger state. Each trigger state may contain a list of associated CSI-ReportConfigs, which indicates the resource set ID used for the channel and optionally for interference. A value of "1" set in the UL-SCH Indicator field indicates that UL-SCH is transmitted on the PUSCH, and a value of "0" in the UL-SCH Indicator field indicates that UL-SCH is not transmitted on the PUSCH. In other words, a value of "1" set in the UL-SCH indicator field indicates that at least one transport block will be included in the PUSCH, and a value of "0" set in the UL-SCH indicator field indicates that no transport block will be included in the PUSCH. The value of the UL-SCH indicator field can be set to "0" only in the triggering state other than when there is no CSI request initialized using the CSI request field in the DCI.

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

[0521] Alternatively or additionally, the metric can be set to either "1" or "0" for the UL-SCH index field. For example, if the UL-SCH index field in the DCI is set to "1", the available slot count is used; if the UL-SCH index field in the DCI is set to "0", the physical slot count is used.

[0522] Alternatively or additionally, the metric may be whether the value of the CSI Request field indicates an event state other than no CSI request. For example, if the value of the CSI Request field indicates an event state other than no CSI request, the available slot count is used, and if the value of the CSI Request field indicates a state corresponding to no CSI request, the physical slot count is used.

[0523] Alternatively or additionally, the metric could be whether PUSCH is used solely for CSI. For example, if PUSCH is used for more than just CSI, the available slot count is used, and if PUSCH is used solely for CSI, the physical slot count is used.

[0524] These methods enable consistent processing of PUSCH transports used solely for CSI, with and without AvailableSlotCounting configuration, and thus reduce processing complexity in non-periodic CSI reporting.

[0525] If the higher-layer processing circuitry does not acquire the first RRC parameter indicating that available time slot counting is enabled, the UE can always use physical time slot counting. In other words, if the higher-layer processing circuitry does not acquire the first RRC parameter indicating that available time slot counting is enabled, the UE can determine that the first time slot is counted as the second time slot, regardless of whether a transport block is included on the PUSCH. If the PUSCH is transmitted in a paired spectrum, the UE can always use physical time slot counting. In other words, if the PUSCH is transmitted in a paired spectrum, the UE can determine that the first time slot is counted as the second time slot, regardless of whether a transport block is included on the PUSCH.

[0526] Alternatively, if the first RRC parameter indicates that available slot counting is enabled and the PUSCH is transmitted in an unpaired spectrum, the UE can use available slot counting to determine the slots for transmitting a PUSCH that has no transport block and has aperiodic CSI reports. The same applies to transmissions of PUSCHs with transport blocks and aperiodic CSI reports, or to multi-slot transmissions of PUSCHs with transport blocks.

[0527] This method enables consistent processing of available slot counts for PUSCH transmissions with transport blocks and PUSCH transmissions for CSI only, and thus reduces the processing complexity in terms of slot counts.

[0528] More details are described regarding the UE procedure for applying transform precoding on the PUSCH.

[0529] For PUSCHs scheduled by RAR UL license, or PUSCHs scheduled by fallbackRAR license, or PUSCHs scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the UE should consider "enabling" or "disabling" transform precoding based on the parameter msg3-transformPrecoder configured by the higher layer.

[0530] For MsgA PUSCH, the UE should consider "enabling" or "disabling" transform precoding based on the parameter msgA-TransformPrecoder configured by the higher layer. If the RRC parameter msgA-TransformPrecoder is not configured, the UE should consider "enabling" or "disabling" transform precoding based on the RRC parameter msg3-transformPrecoder.

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

[0532] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is received using DCI format 0_0, the UE should consider enabling or disabling transform precoding for that PUSCH transmission based on the RRC parameter msg3-transformPrecoder.

[0533] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI with NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is configured with the RRC parameter transformPrecoder in pusch-Config, then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on that parameter (i.e., the configured transformPrecoder).

[0534] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI with NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is configured with the RRC parameter transformPrecoder and dynamicSwitchingTransformPrecoder in pusch-Config is set to "Disabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the RRC parameter transformPrecoder.

[0535] "DCI with scheduling authority not received using DCI format 0_0" can mean "DCI with scheduling authority received using a DCI format other than DCI format 0_0". "DCI with scheduling authority not received using DCI format 0_0" can also mean "Scheduling authority received using the configured authority".

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

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

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

[0539] If the RRC parameter dynamicSwitchingTransformPrecoder indicates "Enabled", the "Transform Precoder Indicator" field may be included in DCI format 0_1 / 0_2. If the RRC parameter dynamicSwitchingTransformPrecoder indicates "Disabled", the "Transform Precoder Indicator" field may not be included in DCI format 0_1 / 0_2.

[0540] If the RRC parameter dynamicSwitchingTransformPrecoder is configured, the UE may assume that the "Transform Precoding Indicator" field may be included in DCI format 0_1 / 0_2. The RRC parameter dynamicSwitchingTransformPrecoder may indicate that the "Transform Precoding Indicator" field is included in DCI format 0_1 / 0_2 (if provided).

[0541] If the RRC parameter dynamicSwitchingTransformPrecoder is not configured or does not exist, the UE may assume that the "Transform Precoder Indicator" field may not be included in DCI format 0_1 / 0_2.

[0542] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE has the RRC parameter transformPrecoder configured and dynamicSwitchingTransformPrecoder in pusch-Config is set to "Enabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the DCI "Transform Precoding Indicator" field.

[0543] Alternatively, for a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI of NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE has the RRC parameter transformPrecoder configured and dynamicSwitchingTransformPrecoder in pusch-Config is set to "Enabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the DCI "Transform Precoding Indicator" field, regardless of the value of transformPrecoder.

[0544] Alternatively, for a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is configured with the RRC parameter transformPrecoder set to "Enabled" and dynamicSwitchingTransformPrecoder in pusch-Config set to "Enabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the DCI "Transform Precoding Indicator" field.

[0545] The UE may assume that the DCI "Transform Precoding Indicator" field is not included in DCI format 0_0.

[0546] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is not configured with the RRC parameter transformPrecoder in pusch-Config, the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the RRC parameter msg3-transformPrecoder.

[0547] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is not configured with the RRC parameter transformPrecoder and dynamicSwitchingTransformPrecoder in pusch-Config is set to "Enabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the higher-layer parameter msg3-transformPrecoder.

[0548] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE is not configured with the RRC parameters transformPrecoder and dynamicSwitchingTransformPrecoder in pusch-Config, the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the higher-layer parameter msg3-transformPrecoder.

[0549] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI using NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder and if the UE has dynamicSwitchingTransformPrecoder set to "disabled" in pusch-Config, then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the RRC parameter msg3-transformPrecoder.

[0550] For a PUSCH transmission scheduled by a PDCCH with a CRC scrambled with CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI of NDI=1, if a DCI with scheduling authority is not received using DCI format 0_0, and if the UE does not have the RRC parameter transformPrecoder configured in push-Config and if the UE has dynamicSwitchingTransformPrecoder configured in push-Config to be "Enabled", then the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the DCI "Transform Precoding Indicator" field.

[0551] The characteristics of the DCI "Transform Precoder Indicator" field can be implemented by using DCI fields other than the "Transform Precoder Indicator" field. In other words, if the UE is configured with the RRC parameter dynamicSwitchingTransformPrecoder set to "Enabled" in pusch-Config, then the first value of the first DCI field can indicate that the transform precoder is enabled, and the second value of the first DCI field can indicate that the transform precoder is disabled. The UE can assume that the value of the first DCI field included in the DCI format is associated with whether the transform precoder is enabled.

[0552] If the base station provides the RRC parameter dynamicSwitchingTransformPrecoder in pusch-Config to be set to "Enabled", then the first value of the first DCI field can be set to indicate that the transform precoder is enabled, and the second value of the first DCI field can be set to indicate that the transform precoder is disabled.

[0553] For PUSCH transports with configured grants, if the UE is configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE should consider enabling or disabling transform precoding for the PUSCH transport based on this parameter.

[0554] For PUSCH transmissions with configured grants, if the UE is not configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE should consider enabling or disabling transform precoding for the PUSCH transmission based on the parameter msg3-transformPrecoder configured by the higher layer.

[0555] Here, "dynamicSwitchingTransformPrecoder configured" can have the same meaning as "dynamicSwitchingTransformPrecoder configured as 'enabled'". And "dynamicSwitchingTransformPrecoder not configured" can have the same meaning as "dynamicSwitchingTransformPrecoder configured as 'disabled'".

[0556] Each program running on base station equipment and terminal equipment according to aspects of the invention may be a program that controls a central processing unit (CPU) or the like, causing the program to cause the computer to operate in a manner that implements the functions described above according to the invention. Information processed in these devices is temporarily stored in random access memory (RAM) while being processed. Subsequently, this information is stored in various types of read-only memory (ROM) such as flash ROM and hard disk drive (HDD), and is read by the CPU as needed for modification or rewriting.

[0557] It should be noted that the terminal device 1 and base station device 3 according to the above implementation scheme can be partially implemented by a computer. In this case, the configuration can be implemented by recording the program for implementing such control functions on a computer-readable recording medium, and enabling the computer system to read the program recorded on the recording medium for execution.

[0558] It should be noted that the "computer system" mentioned here refers to the computer system built into terminal device 1 or base station device 3, and that the computer system includes an operating system and hardware components such as peripheral devices. Furthermore, "computer-readable recording media" refers to portable media such as floppy disks, magneto-optical disks, ROMs, CD-ROMs, etc., as well as storage devices built into the computer system such as hard disks.

[0559] Furthermore, "computer-readable recording medium" can include media that dynamically retain programs for short periods of time, such as communication lines for transmitting programs via networks (such as the Internet) or communication lines (such as telephone lines), and can also include media that retain programs for fixed periods of time, such as volatile memory within a computer system, in which case the computer system operates as a server or client. In addition, the program can be configured to perform some of the functions described above, and can also be configured to perform these functions in conjunction with programs already recorded in the computer system.

[0560] Furthermore, the base station device 3 according to the above embodiment can be implemented as an aggregation (device group) comprising multiple devices. Each device configured in such a device group may include some or all of the functions or function blocks of the base station device 3 according to the above embodiment. The device group may include each general function or each function block of the base station device 3. In addition, the terminal device 1 according to the above embodiment can also communicate with the base station device as an aggregation.

[0561] Furthermore, the base station equipment 3 according to the above embodiments can be used as an evolved universal terrestrial radio access network (E-UTRAN) and / or NG-RAN (Next Generation RAN, NR-RAN). Additionally, the base station equipment 3 according to the above embodiments can have some or all of the functions of a node above the eNodeB or gNB.

[0562] Furthermore, some or all of the components of each of the terminal device 1 and the base station device 3 according to the above embodiments can typically be implemented as an LSI (which is an integrated circuit) or as a chipset. Functional blocks of each of the terminal device 1 and the base station device 3 can be implemented as individual chips, or some or all of the functional blocks can be integrated into a chip. Moreover, circuit integration technology is not limited to LSI and can be implemented using dedicated circuits or general-purpose processors. Furthermore, in cases where alternative circuit integration technologies to LSI emerge with advancements in semiconductor technology, integrated circuits based on such technologies can also be used.

[0563] Furthermore, according to the above embodiments, the terminal device has been described as an example of a communication device, but the present invention is not limited to such terminal devices, and is applicable to terminal devices or communication devices of fixed or fixed electronic devices installed indoors or outdoors, such as audio-visual (AV) devices, kitchen appliances, cleaning machines or washing machines, air conditioning equipment, office equipment, vending machines and other household appliances.

[0564] Embodiments of the invention have been described in detail above with reference to the accompanying drawings; however, specific configurations are not limited to these embodiments and include, for example, modifications to designs that fall within the scope of the spirit of the invention. Furthermore, various modifications are possible within the scope of one aspect of the invention as defined by the claims, and embodiments obtained by appropriately combining the technical means disclosed according to different embodiments are also included within the technical scope of the invention. Moreover, configurations in which constituent elements described in the respective embodiments and having the same effect as each other are substituted for one another are also included within the technical scope of the invention.< / null> < / null> < / null> < / null> < / null> < / null>

Claims

1. A user equipment (UE), the user equipment comprising: A higher-layer processing circuit is configured to acquire at least a first Radio Resource Control (RRC) parameter and a second RRC parameter, wherein the first RRC parameter indicates whether a transform precoder is enabled, and the second RRC parameter indicates whether the downlink control information (DCI) format includes a transform precoder indicator field. A receiving circuit, configured to receive the DCI format for scheduling of the Physical Uplink Shared Channel (PUSCH), and A transmission circuit configured to transmit the PUSCH scheduled by the DCI format. in When the second RRC parameter indicates that the transform precoding indicator field is included in the DCI format, the transmission circuit is configured to apply transform precoding based on the value of the transform precoding indicator field in the DCI format for the transmission of the PUSCH.

2. A base station, the base station comprising: A higher-layer processing circuit is configured to provide at least a first Radio Resource Control (RRC) parameter and a second RRC parameter, wherein the first RRC parameter indicates whether a transform precoder is enabled, and the second RRC parameter indicates whether the downlink control information (DCI) format includes a transform precoder indicator field. Transmission circuitry, configured to transmit the DCI format for scheduling of the Physical Uplink Shared Channel (PUSCH), and A receiving circuit configured to receive the PUSCH scheduled by the DCI format. in When the second RRC parameter indicates that the transform precoding indicator field is included in the DCI format, the transmission circuit is configured to transmit the DCI format including the transform precoding indicator field, and the receiving circuit is configured to receive the PUSCH with transform precoding applied based on the value of the transform precoding indicator field in the DCI format.

3. A method for a user equipment (UE), the method comprising: At least a first Radio Resource Control (RRC) parameter and a second RRC parameter are obtained. The first RRC parameter indicates whether a transformation precoder is enabled, and the second RRC parameter indicates whether the downlink control information (DCI) format includes a transformation precoder indicator field. Receive the DCI format for PUSCH scheduling, and The transmission of the PUSCH is scheduled by the DCI format. in When the second RRC parameter indicates that the transform precoding indicator field is included in the DCI format, transform precoding is applied based on the value of the transform precoding indicator field in the DCI format for the transmission of the PUSCH.

Images