User equipments, base stations and methods

Abstract

A user equipment (UE) is described. The UE may comprise reception circuitry configured to receive a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The UE may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The UE may also comprise transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH in N*K slot(s), wherein the N is equal to 1. The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

Description

[DESCRIPTION][Title of Invention]USER EQUIPMENTS, BASE STATIONS AND METHODS[Technical Field]

[0001] The present invention relates to a user equipment, a base station and a method. [Background Art]

[0002] In the 3rd Generation Partnership Project (3GPP), a radio access method and a radio network for cellular mobile communications (hereinafter, referred to as Long Term Evolution, or Evolved Universal Terrestrial Radio Access) have been studied. In LTE (Long Term Evolution), a base station device is also referred to as an evolved NodeB (eNodeB), and a terminal device is also referred to as a User Equipment (UE). LTE is a cellular communication system in which multiple areas are deployed in a cellular structure, with each of the multiple areas being covered by a base station device. A single base station device may manage multiple cells. Evolved Universal Terrestrial Radio Access is also referred as E-UTRA.

[0003] In the 3GPP, the next generation standard (New Radio: NR) has been studied in order to make a proposal to the International-Mobile-Telecommunication-2020 (IMT-2020) which is a standard for the next generation mobile communication system defined by the International Telecommunications Union (ITU). NR has been expected to satisfy a requirement considering three scenarios of enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC), in a single technology framework.

[0004] For 5G user equipment (UE), initial random access plays an important role in fulfilling the latency requirements. However, for some cell-edge UEs, delay may occurdue to the poor connectivity in the random access procedure. To extend the coverage of 5G service, techniques for enhanced coverage UEs are studied. For enhanced coverage UEs, physical random access channel (PRACH) resources should be well designed for UEs with different pathlosses values.[Brief Description of the Drawings]

[0005] Figure 1 is a conceptual diagram of a wireless communication system;

[0006] Figure 2 is an example showing the relationship between subcarrier-spacing configuration u, the number of OFDM symbols per slot Nslotsymb, and the CP configuration;

[0007] Figure 3 is a diagram showing an example of a method of configuring a resource grid;

[0008] Figure 4 is a diagram showing a configuration example of a resource grid 3001;

[0009] Figure 5 is a schematic block diagram showing a configuration example of the base station device;

[0010] Figure 6 is a schematic block diagram showing a configuration example of the terminal device;

[0011] Figure 7 is a diagram showing a configuration example of an SS / PBCH block;

[0012] Figure 8 is a diagram showing an example of the monitoring occasion of the search-space-set;

[0013] Figure 9 is a diagram illustrating an example of a contention-based random access procedure according to the embodiment of the present invention;

[0014] Figure 10 is a diagram illustrating an example of a procedure of XPUSCH repetition;

[0015] Figure 11 is a flowchart showing an example of Msg3 repetition applicability determination.

[0016] Figure 12 is a flowchart showing an example of XPUSCH repetition applicability determination.

[0017] Figure 13 is a flowchart showing an example of number of repetition determination of XPUSCH.

[0018] Figure 14 is an example of a higher-layer parameter configuring UE specific PUSCH configuration.

[0019] Figure 15 is an example of a higher-layer parameter provided via System information.

[0020] Figure 16 is an example of a higher-layer parameter to identify a feature of Random Access resources.[Description of Embodiments]

[0021] A user equipment (UE) is described. The UE may comprise reception circuitry configured to receive a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The UE may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The UE may also comprise transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1. The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0022] A*B may represent the multiplication of A and B.

[0023] A base station is described. The base station may comprise transmission circuitry configured to transmit a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The base station may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The base station may also comprise reception circuitry configured to receive a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1. The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0024] A method of a UE is described. The method may comprise receiving a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The method may also comprise determining a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The method may also comprise transmitting a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1. The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0025] The K may be determined to one value of a parameter list of system information of RRC message.

[0026] The K may be determined based on a code point which is provided by one or more bit(s) in Modulation and Coding Scheme (MCS) information field of the scheduling DO format 0_0 with CRC scrambled by C-RNTI if a first information is not provided in the first configuration and if the UE requested the repetitions.

[0027] The K may be determined based on a pre-determined table for the repetition.

[0028] floor (CX) may be a floor function for real number CX. For example, floor (CX) may be a function that provides the largest integer within a range that does not exceed the real number CX. ceil (DX) may be a ceiling function to a real number DX. For example, ceil (DX) may be a function that provides the smallest integer within the range not less than the real number DX. mod (EX, FX) may be a function that provides the remainder obtained by dividing EX by FX. mod (EX, FX) may be a function that provides a value which corresponds to the remainder of dividing EX by FX. It is exp (GX) = eAGX. Here, e is Napier number. (HX)A(IX) indicates IX to the power of HX.

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

[0030] The OFDM symbol may be a designation including a CP added to the OFDM symbol. That is, an OFDM symbol may be configured to include the OFDM symbol and a CP added to the OFDM symbol.

[0031] Figure 1 is a conceptual diagram of a wireless communication system. In Figure 1, the wireless communication system includes at least terminal device lA to 1C and a base station device 3 (BS # 3: Base station # 3). Hereinafter, the terminal devices 1A to 1C are also referred to as a terminal device 1 (UE # 1 : User Equipment # 1).

[0032] The base station device 3 may be configured to include one or more transmission devices (or transmission points, transmission devices, reception devices, transmission points, reception points). When the base station device 3 is configured by a plurality of transmission devices, each of the plurality of transmission devices may be arranged at a different position.

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

[0034] A serving cell may be configured to include at least one downlink component carrier (downlink carrier) and / or one uplink component carrier (uplink carrier). A serving cell may be configured to include at least two or more downlink component carriers and / or two or more uplink component carriers. A downlink component carrier and an uplink component carrier are also referred to as component carriers (carriers). The uplink component carrier can be used for sidelink communication.

[0035] For example, one resource grid may be provided for one component carrier. For example, one resource grid may be provided for one component carrier and a subcarrier-spacing configuration u. A subcarrier-spacing configuration u is also referredto as numerology. A resource grid includes subcarriers. The resource gridstarts from a common resource block with index Nstart=ugrid. The common resource block with the indexis also referred to as a reference point of the resource grid. The resource grid includes OFDM symbols. The subscript x indicates thetransmission direction and indicates either downlink or uplink. One resource grid is provided for an antenna port p, a subcarrier-spacing configuration u, and a transmission direction x. The resource grid may be applied to downlink, uplink and / or sidelink.

[0036] Resource grid is also referred to as carrier.

[0037] and are given based at least on an RRC parameter (e.g.referred to as RRC parameter CarrierBandwidth). The RRC parameter is used to define one or more SCS (SubCarrier-Spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. One component carrier may comprise one or more SCS specific carriers. The SCS specific carrier may be included in a system information block (SIB). For each SCS specific carrier, a subcarrier-spacing configuration u may be provided.

[0038] Figure 2 is an example showing the relationship between subcarrier-spacing configuration u, the number of OFDM symbols per slot Nslotsymb, and the CP configuration. In Figure 2A, for example, when the subcarrier-spacing configuration u is set to 2 and the CP configuration is set to normal CP (normal cyclic prefix),Further, in Figure 2B, for example, when the subcarrier-spacingconfiguration u is set to 2 and the CP configuration is set to an extended CP (extended cyclic prefix), The subcarrier-spacingconfiguration u may be applied to downlink, uplink and / or sidelink.

[0039] In the wireless communication system, a time unit Tcmay be used to represent the length of the time domain. The time unit = 480kHz. It is Nf = 4096. The constant k is is 15 kHz. Nf,ref is 2048.

[0040] Transmission of signals in the downlink and / or transmission of signals in the uplink and / or transmission of signals in the sidelink may be organized into radio frames (system frames, frames) of length Tf. It is Tf = (dfmax Nf / 100) * Ts= 10 ms. One radio frame is configured to include ten subframes. The subframe length is TSf = (dfmaxNf / 1000) Ts= 1 ms. The number of OFDM symbols per subframe is

[0041] For a subcarrier-spacing configuration u, the number of slots included in a subframe and indexes may be given. For example, slot index nusmay be given in ascending order with an integer value ranging from 0 to Nsubframe’usiot -1 in a subframe. For subcarrier-spacing configuration u, the number of slots included in a radio frame and indexes of slots included in the radio frame may be given. Also, the slot index n\ f may be given in ascending order with an integer value ranging from 0 to -1 in theradio frame. Consecutive Nslotsymb OFDM symbols may be included in one slot. It is

[0042] Figure 3 is a diagram showing an example of a method of configuring a resource grid. The horizontal axis in Figure 3 indicates frequency domain. Figure 3 shows a configuration example of a resource grid of subcarrier-spacing configuration u = ui in the component carrier 300 and a configuration example of a resource grid of subcarrierspacing configuration u = U2 in a component carrier. One or more subcarrier-spacing configuration may be set for a component carrier. Although it is assumed in Figure 3 thatui = U2-1, various aspects of this embodiment are not limited to the condition of m = U2- 1.

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

[0044] Point 3000 is an identifier for identifying a subcarrier. Point 3000 is also referred to as point A. The common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier-spacing configuration ui.

[0045] Among the common resource block-set 3100, the common resource block including the point 3000 (the block indicated by the upper right diagonal line in Figure 3) is also referred to as a reference point of the common resource block-set 3100. The reference point of the common resource block-set 3100 may be a common resource block with index 0 in the common resource block-set 3100.

[0046] The offset 3011 is an offset from the reference point of the common resource block-set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks which is relative to the subcarrierspacing configuration ui. The resource grid 3001 includescommon resource blocks starting from the reference point of the resource grid 3001.

[0047] The offset 3013 is an offset from the reference point of the resource grid 3001 to the reference point ) of the BWP (Bandwidth Part) 3003 of the index il .

[0048] Common resource block-set 3200 is a set of common resource blocks with respect to subcarrier-spacing configuration U2.

[0049] A common resource block including the point 3000 (a block indicated by an upper left diagonal line in Figure 3) in the common resource block-set 3200 is also referred to as a reference point of the common resource block-set 3200. The referencepoint of the common resource block-set 3200 may be a common resource block with index 0 in the common resource block-set 3200.

[0050] The offset 3012 is an offset from the reference point of the common resource block-set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks for subcarrier-spacing configuration u = U2. The resource grid 3002 includes Nslze=ugrid2,x common resource blocks starting from the reference point of the resource grid 3002.

[0051] The offset 3014 is an offset from the reference point of the resource grid 3002 to the reference point ) of the BWP 3004 with index i2.

[0052] Figure 4 is a diagram showing a configuration example of a resource grid 3001. In the resource grid of Figure 4, the horizontal axis indicates OFDM symbol index lsym, and the vertical axis indicates the subcarrier index ksc. The resource grid 3001 includes subcarriers, and includes OFDM symbols. A resourcespecified by the subcarrier index kscand the OFDM symbol index lsymin a resource grid is also referred to as a resource element (RE).

[0053] A resource block (RB) includes c consecutive subcarriers. A resourceblock is a generic name of a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). It is

[0054] A resource block unit is a set of resources that corresponds to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements which corresponds to one OFDM symbol in one resource block.

[0055] Common resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a common resource block-set. The common resource block with index 0 for the subcarrier-spacing configuration u includes(or collides with, matches) the point 3000. The index nucRB of the common resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of UUCRB =The subcarrier with ksc = 0 is a subcarrier with the same center frequency as the center frequency of the subcarrier which corresponds to the point 3000.

[0056] Physical resource blocks for a subcarrier-spacing configuration u are indexed in ascending order from 0 in the frequency domain in a BWP. The index HUPRB of the physical resource block with respect to the subcarrier-spacing configuration u satisfies the relationship of indicates the reference pointof BWP with index i.

[0057] A BWP is defined as a subset of common resource blocks included in the resource grid. The BWP includes common resource blocks starting from thereference points A BWP for the downlink component carrier is also referredto as a downlink BWP. A BWP for the uplink component carrier is also referred to as an uplink BWP. A BWP for the sidelink is also referred to as a sidelink BWP.

[0058] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel. For example, the symbols may correspond to OFDM symbols. For example, the symbols may correspond to resource block units. For example, the symbols may correspond to resource elements.

[0059] Two antenna ports are said to be QCL (Quasi Co-Located) if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed.The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0060] Carrier aggregation may be communication using a plurality of aggregated serving cells. Carrier aggregation may be communication using a plurality of aggregated component carriers. Carrier aggregation may be communication using a plurality of aggregated downlink component carriers. Carrier aggregation may be communication using a plurality of aggregated uplink component carriers.

[0061] Figure 5 is a schematic block diagram showing a configuration example of the base station device 3. As shown in Figure 5, the base station device 3 includes at least a part or all of the wireless transmission / reception unit (physical layer processing unit) 30 and the higher-layer processing unit 34. The wireless transmission / reception unit 30 includes at least a part or all of the antenna unit 31 , the RF unit 32 (Radio Frequency unit 32), and the baseband unit 33. The higher-layer processing unit 34 includes at least a part or all of the medium access control layer processing unit 35 and the radio resource control (RRC) layer processing unit 36.

[0062] The wireless transmission / reception unit 30 includes at least a part of or all of a wireless transmission unit 30a and a 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.

[0063] The higher-layer processing unit 34 provides downlink data (a transport block) to the wireless transmission I reception unit 30 (or the wireless transmission unit 30a). The higher-layer processing unit 34 performs processing of a medium access control (MAC) layer, a packet data convergence protocol layer (PDCP layer), a radio link control layer (RLC layer) and / or an RRC layer.

[0064] The medium access control layer processing unit 35 included in the higher- layer processing unit 34 performs processing of the MAC layer.

[0065] The radio resource control layer processing unit 36 included in the higher- layer processing unit 34 performs the process of the RRC layer. The radio resource control layer processing unit 36 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 configures an RRC parameter based on the RRC message received from the terminal device 1.

[0066] The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) performs processing such as encoding and modulation. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) generates a physical signal by encoding and modulating the downlink data. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) converts OFDM symbols in the physical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) transmits the baseband signal (or the physical signal) to the terminal device 1 via radio frequency. The wireless transmission / reception unit 30 (or the wireless transmission unit 30a) may arrange the baseband signal (or the physical signal) on a component carrier and transmit the baseband signal (or the physical signal) to the terminal device 1.

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

[0068] The RF unit 32 demodulates the physical signal received via the antenna unit 31 into a baseband signal (down convert), and / or removes extra frequency components. The RF unit 32 provides the processed analog signal to the baseband unit 33.

[0069] The baseband unit 33 converts an analog signal (signals on radio frequency) input from the RF unit 32 into a digital signal (a baseband signal). The baseband unit 33 separates a portion which corresponds to CP (Cyclic Prefix) from the digital signal. The baseband unit 33 performs Fast Fourier Transformation (FFT) on the digital signal from which the CP has been removed. The baseband unit 33 provides the physical signal in the frequency domain.

[0070] The baseband unit 33 performs Inverse Fast Fourier Transformation (IFFT) on downlink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.

[0071] The RF unit 32 removes extra frequency components from the analog signal (signals on radio frequency) input from the baseband unit 33, up-converts the analog signal to a radio frequency, and transmits it via the antenna unit 31. The RF unit 32 mayhave a function of controlling transmission power. The RF unit 32 is also referred to as a transmission power control unit.

[0072] At least one or more serving cells (or one or more component carriers, one or more downlink component carriers, one or more uplink component carriers) may be configured for the terminal device 1.

[0073] Each of the serving cells set for the terminal device 1 may be any of PCell (Primary cell), PSCell (Primary SCG cell), and SCell (Secondary Cell).

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

[0075] A PSCell is a serving cell included in a SCG (Secondary Cell Group). A PSCell is a serving cell in which random-access is performed by the terminal device 1 in a reconfiguration procedure with synchronization (Reconfiguration with synchronization).

[0076] A SCell may be included in either an MCG or a SCG.

[0077] The serving cell group (cell group) is a designation including at least MCG and SCG. The 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 the serving cell group may be operated by carrier aggregation.

[0078] One or more downlink B WPs may be configured for each serving cell (or each downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or each uplink component carrier).

[0079] Among the one or more downlink BWPs set for the serving cell (or the downlink component carrier), one downlink BWP may be set as an active downlink BWP (or one downlink BWP may be activated). Among the one or more uplink BWPs set forthe serving cell (or the uplink component carrier), one uplink BWP may be set as an active uplink BWP (or one uplink BWP may be activated).

[0080] A PDSCH, a PDCCH, a C SI-RS and other physical downlink channels / signals may be received in the active downlink BWP. The terminal device 1 may receive the PDSCH, the PDCCH, and the CSI-RS in the active downlink BWP. Additionally, in some case, the terminal device 1 may receive the CSI-RS or other physical downlink channels / signals (e.g., Positioning RS (PRS)) in the downlink BWP that is not active or in the cell that is not a serving cell. A PUCCH, a PUSCH, an SRS and other physical uplink channels / signals may be sent on the active uplink BWP. The terminal device 1 may transmit the PUCCH, the PUSCH, the SRS and other physical uplink channels / signals in the active uplink BWP. Additionally, in some case, the terminal device 1 may receive the SRS or other physical uplink channels / signals (e.g., SRS for Positioning) in the uplink BWP that is not active or in the cell that is not a serving cell. The active downlink BWP and the active uplink BWP are also referred to as active BWP.

[0081] Downlink BWP switching deactivates an active downlink BWP and activates one of inactive downlink BWPs which are other than the active downlink BWP. The downlink BWP switching may be controlled by a BWP field included in a downlink control information. The downlink BWP switching may be controlled based on higher- layer parameters.

[0082] Uplink BWP switching is used to deactivate an active uplink BWP and activate any inactive uplink BWP which is other than the active uplink BWP. Uplink BWP switching may be controlled by a BWP field included in a downlink control information. The uplink BWP switching may be controlled based on higher-layer parameters.

[0083] Among the one or more downlink BWPs set 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 certain time.

[0084] Among the one or more uplink BWPs set 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 certain time.

[0085] The aforementioned procedures for Uplink BWP may be applicable to Sidelink BWP.

[0086] Figure 6 is a schematic block diagram showing a configuration example of the terminal device 1 (including target UE 4 and anchor UE 5 described later). As shown in Figure 6, the terminal device 1 includes at least a part or all of the wireless transmission I reception unit (physical layer processing unit) 10 and the higher-layer processing unit 14. The wireless transmission / reception unit 10 includes at least a part or all of the antenna unit 11, the RF unit 12, and the baseband unit 13. The higher-layer processing unit 14 includes at least a part or all of the medium access control layer processing unit 15 and the radio resource control layer processing unit 16.

[0087] The wireless transmission / reception unit 10 includes at least a part of or all of a wireless transmission unit 10a and a 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 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 wirelesstransmission unit 1 Oa and the configuration of the antenna unit 11 included in the wireless reception unit 10b may be the same or different.

[0088] The higher-layer processing unit 14 provides uplink or side link data (a transport block) to the wireless transmission / reception unit 10 (or the wireless transmission unit 10a). The higher-layer processing unit 14 performs processing of a MAC layer, a packet data integration protocol layer, a radio link control layer, and / or an RRC layer. The higher-layer processing unit 14 may also performs processing of a MAC layer, a packet data integration protocol layer, a radio link control layer, and / or an RRC layer for PC 5.

[0089] The medium access control layer processing unit 15 included in the higher- layer processing unit 14 performs processing of the MAC layer.

[0090] The radio resource control layer processing unit 16 included in the higher- layer processing unit 14 performs the process of the RRC layer and / or the PC5 RRC (PC5-RRC) process. The radio resource control layer processing unit 16 manages various configuration information / parameters (RRC parameters and / or PC5 RRC (PC5-RRC) parameters) of the terminal device 1. The radio resource control layer processing unit 16 configures RRC parameters based on the RRC message received from the base station device 3 and / or PC5 RRC parameters based on the PC5 RRC (PC5-RRC) message received from another terminal device.

[0091] The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) performs processing such as encoding and modulation. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) generates a physical signal by encoding and modulating the uplink data and / or sidelink data. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) converts OFDM symbols in thephysical signal to a baseband signal by conversion to a time-continuous signal. The wireless transmission I reception unit 10 (or the wireless transmission unit 10a) transmits the baseband signal (or the physical signal) to the base station device 3 or to another terminal device via radio frequency. The wireless transmission / reception unit 10 (or the wireless transmission unit 10a) may arrange the baseband signal (or the physical signal) on a BWP (active uplink BWP) and transmit the baseband signal (or the physical signal) to the base station device 3.

[0092] The wireless transmission / reception unit 10 (or the wireless reception unit 10b) performs processing such as demodulation and decoding. The wireless transmission / reception unit 10 (or the wireless reception unit 10b) may receive a physical signal in a BWP (active downlink BWP) of a serving cell and / or in a Sidelink BWP. The wireless transmission / reception unit 10 (or the wireless reception unit 10b) separates, demodulates and decodes the received physical signal, and provides the decoded information to the higher-layer processing unit 14. The wireless transmission I reception unit 10 (or the wireless reception unit 10b) may perform the channel access procedure prior to the transmission of the physical signal.

[0093] The wireless transmission / reception unit 10 may have a function to determine whether to change a number of transmissions of the multiple PRACH transmission for the retransmission. The wireless transmission / reception unit 10 may have a function to send higher layers a notification to suspend the power ramping counter in case the number of transmissions is determined to be changed. The wireless transmission / reception unit 10 may have a function to perform a PRACH retransmission.

[0094] The RF unit 12 demodulates the physical signal received via the antenna unit 11 into a baseband signal (down convert), and / or removes extra frequency components. The RF unit 12 provides the processed analog signal to the baseband unit 13.

[0095] The baseband unit 13 converts an analog signal (signals on radio frequency) input from the RF unit 12 into a digital signal (a baseband signal). The baseband unit 13 separates a portion which corresponds to CP from the digital signal, performs fast Fourier transformation on the digital signal from which the CP has been removed, and provides the physical signal in the frequency domain.

[0096] The baseband unit 13 performs inverse fast Fourier transformation on uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and convert the digital signal into an analog signal. The baseband unit 13 provides the analog signal to the RF unit 12.

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

[0098] The higher-layer processing unit 14 may have a function to determine whether to increment the ramping counter based on whether the notification is sent or not. The higher-layer processing unit 14 may have a function to determine a transmission power for the retransmission based on the power ramping counter. The higher-layer processing unit 14 may have a function to determine to perform a retransmission for a multiple PRACH transmission in case that a random access procedure is not completed after the multiple PRACH transmission.

[0099] Hereinafter, physical signals (signals) will be described.

[0100] Physical signal is a generic term for downlink physical channels, downlink physical signals, uplink physical channels, uplink physical signals, sidelink physical channels, and sidelink physical signals. The physical channel is a generic term for downlink physical channels, uplink physical channels and sidelink physical channels.

[0101] An uplink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and / or uplink control information. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by the terminal device 1. The uplink physical channel may be received by the base station device 3. In the wireless communication system according to one aspect of the present embodiment, at least part or all of PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) may be used.

[0102] A PUCCH may be used to transmit uplink control information (UCI). The PUCCH may be sent to deliver (transmission, convey) uplink control information. The uplink control information may be mapped to (or arranged in) the PUCCH. The terminal device 1 may transmit PUCCH in which uplink control information is arranged. The base station device 3 may receive the PUCCH in which the uplink control information is arranged.

[0103] Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes at least part or all of channel state information (CSI), scheduling request (SR), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).

[0104] Channel state information is conveyed by using channel state information bits or a channel state information sequence. Scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0105] HARQ-ACK information may include HARQ-ACK status which corresponds to a transport block (TB: Transport block, MAC PDU: Medium Access Control Protocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH: Uplink-Shared Channel, PDSCH: Physical Downlink Shared CHannel, PUSCH: Physical Uplink Shared CHannel). The HARQ-ACK status may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to the transport block. The ACK may indicate that the transport block has been successfully decoded. The NACK may indicate that the transport block has not been successfully decoded. The HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ-ACK status (or HARQ-ACK bits).

[0106] For example, the correspondence between the HARQ-ACK information and the transport block may mean that the HARQ-ACK information and the PDSCH used for transmission of the transport block correspond.

[0107] HARQ-ACK status may indicate ACK or NACK which correspond to one CBG (Code Block Group) included in the transport block.

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

[0109] The channel state information may include at least part or all of a channel quality indicator (CQI), a precoder matrix indicator (PMI), and a rank indicator (RI). CQI is an indicator related to channel quality (e.g., propagation quality) or physical channel quality, and PMI is an indicator related to a precoder. RI is an indicator related to transmission rank (or the number of transmission layers).

[0110] Channel state information may be provided at least based on receiving one or more physical signals (e.g., one or more CSI-RSs) used at least for channel measurement. The channel state information may be selected by the terminal device 1 at least based on receiving one or more physical signals used for channel measurement. Channel measurements may include interference measurements.

[0111] A PUCCH may correspond to a PUCCH format. A PUCCH may be a set of resource elements used to convey a PUCCH format. A PUCCH may include a PUCCH format. A PUCCH format may include UCI.

[0112] A PUSCH may be used to transmit uplink data (a transport block) and / or uplink control information. A PUSCH may be used to transmit uplink data (a transport block) corresponding to a UL-SCH and / or uplink control information. A PUSCH may be used to convey uplink data (a transport block) and / or uplink control information. APUSCH may be used to convey uplink data (a transport block) corresponding to a UL- SCH and / or uplink control information. Uplink data (a transport block) may be arranged in a PUSCH. Uplink data (a transport block) corresponding to UL-SCH may be arranged in a PUSCH. Uplink control information may be arranged to a PUSCH. The terminal device 1 may transmit a PUSCH in which uplink data (a transport block) and / or uplink control information is arranged. The base station device 3 may receive a PUSCH in which uplink data (a transport block) and / or uplink control information is arranged.

[0113] A PRACH may be used to transmit a random-access preamble. The PRACH may be used to convey a random-access preamble. The sequence xUj v(n) of the PRACH is defined by xUj v(n) = xu(mod (n + Cv, LRA)). The xumay be a ZC sequence (Zadoff- Chu sequence). The xumay be defined by xu= exp (-jpui (i + 1) / LRA). The j is an imaginary unit. The p is the circle ratio. The Cvcorresponds to cyclic shift of the PRACH. LRA corresponds to the length of the PRACH. The LRA may be 839 or 139 or another value. The i is an integer in the range of 0 to LRA-L The u is a sequence index for the PRACH. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH.

[0114] For a given PRACH opportunity, 64 random-access preambles are defined. The random-access preamble is specified (determined, given) at least based on the cyclic shift Cvof the PRACH and the sequence index u for the PRACH.

[0115] An uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in the higher-layer. The uplink physical signal may be a physical signal used in the uplink component carrier. The terminal device 1 may transmit an uplink physical signal. The base station device 3 may receive the uplink physical signal. In the radio communication system according to oneaspect of the present embodiment, at least a part or all of UL DMRS (UpLink Demodulation Reference Signal), SRS (Sounding Reference Signal), UL PTRS (UpLink Phase Tracking Reference Signal) may be used.

[0116] UL DMRS is a generic name of a DMRS for a PUSCH and a DMRS for a PUCCH.

[0117] A set of antenna ports of a DMRS for a PUSCH (a DMRS associated with a PUSCH, a DMRS included in a PUSCH, a DMRS which corresponds to a PUSCH) may be given based on a set of antenna ports for the PUSCH. That is, the set of DMRS antenna ports for the PUSCH may be the same as the set of antenna ports for the PUSCH.

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

[0119] A PUSCH may be estimated from a DMRS for the PUSCH. That is, propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

[0120] A set of antenna ports of a DMRS for a PUCCH (a DMRS associated with a PUCCH, a DMRS included in a PUCCH, a DMRS which corresponds to a PUCCH) may be identical to a set of antenna ports for the PUCCH.

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

[0122] A PUCCH may be estimated from a DMRS for the PUCCH. That is, propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

[0123] A downlink physical channel may correspond to a set of resource elements that carry information originating from the higher-layer and / or downlink control information. The downlink physical channel may be a physical channel used in the downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In the wireless communication system according to one aspect of the present embodiment, at least a part or all of PBCH (Physical Broadcast Channel), PDCCH (Physical Downlink Control Channel), and PDSCH (Physical Downlink Shared Channel) may be used.

[0124] The PBCH may be used to transmit a MIB (Master Information Block) and / or physical layer control information. The physical layer control information is a kind of downlink control information. The PBCH may be sent to deliver the MIB and / or the physical layer control information. A BCH may be mapped (or corresponding) to the PBCH. The terminal device 1 may receive the PBCH. The base station device 3 may transmit the PBCH. The physical layer control information is also referred to as a PBCH payload and a PBCH payload related to timing. The MIB may include one or more higher- layer parameters.

[0125] Physical layer control information includes 8 bits. The physical layer control information may include at least part or all of OA to 0D. The 0A is radio frame information. The OB is half radio frame information (half system frame information). The 0C is SS / PBCH block index information. The 0D is subcarrier offset information.

[0126] The radio frame information is used to indicate a radio frame in which the PBCH is transmitted (a radio frame including a slot in which the PBCH is transmitted). The radio frame information is represented by 4 bits. The radio frame information may be represented by 4 bits of a radio frame indicator. The radio frame indicator may include 10 bits. For example, the radio frame indicator may at least be used to identify a radio frame from index 0 to index 1023.

[0127] The half radio frame information is used to indicate whether the PBCH is transmitted in first five subframes or in second five subframes among radio frames in which the PBCH is transmitted. Here, the half radio frame may be configured to include five subframes. The half radio frame may be configured by five subframes of the first half of ten subframes included in the radio frame. The half radio frame may be configured by five subframes in the second half of ten subframes included in the radio frame.

[0128] The SS / PBCH block index information is used to indicate an SS / PBCH block index. The SS / PBCH block index information may be represented by 3 bits. The SS / PBCH block index information may consist of 3 bits of an SS / PBCH block index indicator. The SS / PBCH block index indicator may include 6 bits. The SS / PBCH block index indicator may at least be used to identify an SS / PBCH block 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.).

[0129] The subcarrier offset information is used to indicate subcarrier offset. The subcarrier offset information may 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.

[0130] A PDCCH may be used to transmit downlink control information (DCI). A PDCCH may be transmitted to deliver downlink control information. Downlink control information may be mapped to a PDCCH. The terminal device 1 may receive a PDCCH in which downlink control information is arranged. The base station device 3 may transmit the PDCCH in which the downlink control information is arranged.

[0131] Downlink control information may correspond to a DCI format. Downlink control information may be included in a DCI format. Downlink control information may be arranged in each field of a DCI format.

[0132] DCI format is a generic name for DCI format 0_0, DCI format 0 1, DCI format l_0, and DCI format 1_1. Uplink DCI format is a generic name of the DCI format 0_0 and the DCI format 0 1. Downlink DCI format is a generic name of the DCI format l_0 and the DCI format 1_1.

[0133] A PDSCH may be used to transmit one or more transport blocks. A PDSCH may be used to transmit one or more transport blocks which corresponds to a DL-SCH. A PDSCH may be used to convey one or more transport blocks. A PDSCH may be used to convey one or more transport blocks which corresponds to a DL-SCH. One or more transport blocks may be arranged in a PDSCH. One or more transport blocks which corresponds to a DL-SCH may be arranged in a PDSCH. The base station device 3 may transmit a PDSCH. The terminal device 1 may receive the PDSCH.

[0134] Downlink physical signals may correspond to a set of resource elements. The downlink physical signals may not carry the information generated in the higher-layer. The downlink physical signals may be physical signals used in the downlink component carrier. A downlink physical signal may be transmitted by the base station device 3. The downlink physical signal may be transmitted by the terminal device 1. In the wirelesscommunication system according to one aspect of the present embodiment, at least a part or all of an SS (Synchronization signal), DLDMRS (DownLink DeModulation Reference Signal), CSI-RS (Channel State Information-Reference Signal), and DL PTRS (DownLink Phase Tracking Reference Signal) may be used.

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

[0136] Figure 7 is a diagram showing a configuration example of an SS / PBCH block. In Figure 7, the horizontal axis indicates time domain (OFDM symbol index lsym), and the vertical axis indicates frequency domain. The shaded blocks indicate a set of resource elements for a PSS. The blocks of grid lines indicate a set of resource elements for an SSS. Also, the blocks in the horizontal line indicate a set of resource elements for a PBCH and a set of resource elements for a DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, DMRS which corresponds to the PBCH).

[0137] As shown in Figure 7, the SS / PBCH block includes a PSS, an SSS, and a PBCH. The SS / PBCH block includes 4 consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is allocated to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is allocated to the 57th to 183rd subcarriers in the third OFDM symbol. The first to 56th subcarriers of the first OFDM symbol may be set to zero. The 184th to 240th subcarriers of the first OFDM symbol may be set to zero. The 49th to 56th subcarriers of the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol may be set to zero. In the first to 240th subcarriers of the second OFDM symbol, the PBCH is allocated to subcarriers in which the DMRSfor the PBCH is not allocated. In the first to 48th subcarriers of the third OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. In the 193rd to 240th subcarriers of the third OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. In the first to 240th subcarriers of the 4th OFDM symbol, the PBCH is allocated to subcarriers in which the DMRS for the PBCH is not allocated. The SS / PBCH is also referred to as SSB.

[0138] The antenna ports of a PSS, an SSS, a PBCH, and a DMRS for the PBCH in an SS / PBCH block may be identical.

[0139] A PBCH may be estimated from a DMRS for the PBCH. For the DM-RS for the PBCH, the channel over which a symbol for the PBCH on an antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within a SS / PBCH block transmitted within the same slot, and with the same SS / PBCH block index.

[0140] DL DMRS is a generic name of DMRS for a PBCH, DMRS for a PDSCH, and DMRS for a PDCCH.

[0141] A set of antenna ports for a DMRS for a PDSCH (a DMRS associated with a PDSCH, a DMRS included in a PDSCH, a DMRS which corresponds to a PDSCH) may be given based on the set of antenna ports for the PDSCH. The set of antenna ports for the DMRS for the PDSCH may be the same as the set of antenna ports for the PDSCH.

[0142] Transmission of a PDSCH and transmission of a DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as PDSCH. Transmitting a PDSCH may be transmitting a PDSCH and a DMRS for the PDSCH.

[0143] A PDSCH may be estimated from a DMRS for the PDSCH. For a DM-RS associated with a PDSCH, the channel over which a symbol for the PDSCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the antenna port is conveyed only if the two symbols are within the same resource as the scheduled PDSCH, in the same slot, and in the same PRG (Precoding Resource Group).

[0144] Antenna ports for a DMRS for a PDCCH (a DMRS associated with a PDCCH, a DMRS included in a PDCCH, a DMRS which corresponds to a PDCCH) may be the same as an antenna port for the PDCCH.

[0145] A PDCCH may be estimated from a DMRS for the PDCCH. For a DM-RS associated with a PDCCH, the channel over which a symbol for the PDCCH on one antenna port is conveyed can be inferred from the channel over which another symbol for the DM-RS on the same antenna port is conveyed only if the two symbols are within resources for which the UE may assume the same precoding being used (i.e. within resources in a REG bundle).

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

[0147] One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be given to PCell. BCH may not be given to PSCell and SCell.

[0148] A BCCH (Broadcast Control CHannel), a CCCH (Common Control CHannel), and a DCCH (Dedicated Control CHannel) are logical channels. The BCCH is a channel of the RRC layer used to deliver MIB or system information. The CCCH may be used to transmit a common RRC message in a plurality of terminal devices 1. The CCCH may be used for the terminal device 1 which is not connected by RRC. The DCCH may be used at least to transmit a dedicated RRC message to the terminal device 1. The DCCH may be used for the terminal device 1 that is in RRC-connected mode.

[0149] The RRC message includes one or more RRC parameters (information elements, higher layer parameters). For example, the RRC message may include a MIB. For example, the RRC message may include system information (SIB: System Information Block, MIB). SIB is a generic name for various type of SIBs (e.g., SIB1, SIB2). For example, the RRC message may include a message which corresponds to a CCCH. For example, the RRC message may include a message which corresponds to a DCCH. RRC message is a general term for common RRC message and dedicated RRC message.

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

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

[0152] A higher-layer parameter is a parameter included in an RRC message or a MAC CE (Medium Access Control Control Element). The higher-layer parameter is a generic name of information included in a MIB, system information, a message which corresponds to CCCH, a message which corresponds to DCCH, and a MAC CE. A higher- layer parameter may be referred to as an RRC parameter or an RRC configuration if the higher-layer parameter is the parameter included in the RRC message.

[0153] A higher-layer parameter may be a cell-specific parameter or a UE-specific parameter. A cell-specific parameter is a parameter including a common configuration in a cell. A UE-specific parameter is a parameter including a configuration that may be configured differently for each UE.

[0154] The base station device may indicate change of cell-specific parameters by reconfiguration with random-access. The UE may change cell-specific parameters before triggering random-access. The base station device may indicate change of UE-specific parameters by reconfiguration with or without random-access. The UE may change UE- specific parameters before or after random-access.

[0155] The procedure performed by the terminal device 1 includes at least a part or all of the following 5Ato 5C. The 5A is cell search. The 5B is random-access. The 5C is data communication.

[0156] The cell search is a procedure used by the terminal device 1 to synchronize with a cell in the time domain and / or the frequency domain and to detect a physical cell identity. The terminal device 1 may detect the physical cell ID by performing synchronization of time domain and / or frequency domain with a cell by the cell search.

[0157] A sequence of a PS S is given based at least on a physical cell ID. A sequence of an SSS is given based at least on the physical cell ID.

[0158] An SS / PBCH block candidate indicates a resource for which transmission of the SS / PBCH block may exist. An SS / PBCH block may be transmitted at a resource indicated as the SS / PBCH block candidate. The base station device 3 may transmit an SS / PBCH block at an SS / PBCH block candidate. The terminal device 1 may receive (detect) the SS / PBCH block at the SS / PBCH block candidate.

[0159] A set of SS / PBCH block candidates in a half radio frame is also referred to as an SS-burst-set. The SS-burst-set is also referred to as a transmission window, a SS transmission window, or a DRS transmission window (Discovery Reference Signal transmission window). The SS-burst-set is a generic name that includes at least a first SS- burst-set and a second SS-burst-set.

[0160] The base station device 3 transmits SS / PBCH blocks of one or more indexes at a predetermined cycle. The terminal device 1 may detect an SS / PBCH block of at least one of the SS / PBCH blocks of the one or more indexes. The terminal device 1 may attempt to decode the PBCH included in the SS / PBCH block.

[0161] The random-access is a procedure including at least a part or all of message 1 , message 2, message 3, and message 4.

[0162] The message 1 (Msgl, Msg 1) is a procedure in which the terminal device 1 transmits a PRACH. The terminal device 1 transmits the PRACH in one PRACH occasion (RACH occasion, RO) selected from among one or more PRACH occasions based on at least the index of the SS / PBCH block candidate detected based on the cell search. Alternatively, Msgl is information to indicate a Random Access preamble in one or more RO(s) to the base station 3 from the terminal device 1.

[0163] The message 2 (Msg2, Msg 2) is a procedure in which the terminal device 1 attempts to detect a DCI format l_0 with CRC (Cyclic Redundancy Check) scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier). The terminal device 1 may attempt to detect the DCI format l_0 in a search-space-set. Alternatively, Msg2 is information contained in PDSCH scheduled by the DCI format 1 0 with CRC (Cyclic Redundancy Check) scrambled by an RA-RNTI. The Msg 2 can be referred to as Random Access Response (RAR).

[0164] The message 3 (Msg3, Msg 3) is a procedure for transmitting a PUSCH scheduled by a random-access response grant (RAR UL grant) included detected in the message 2 procedure. The RAR UL grant is indicated by the MAC CE included in the PDSCH scheduled by the DCI format l_0. Alternatively, the Msg3 is information contained in PUSCH scheduled by RAR or DCI format 0 0 with CRC scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

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

[0166] Retransmission of the message 3 PUSCH is scheduled by DCI format 0_0 with CRC scrambled by a TC-RNTI.

[0167] The message 4 (Msg4, Msg 4) is a procedure that attempts to detect a DCI format l_0 with CRC scrambled by either a C-RNTI (Cell-Radio Network Temporary Identifier) or a TC-RNTI. The terminal device 1 receives a PDSCH scheduled based on the DCI format l_0. The PDSCH may include a collision resolution ID. Alternatively,the Msg4 is information contained in PDSCH scheduled by DO format l_0 scheduled by C-RNTI or TC-RNTI.

[0168] The terminal device 1 may transmit PUSCH scheduled by DCI format 0_0

[0169] The message 5 (Msg5, Msg 5) is a procedure that attempts to detect a DCI format 0__0 with CRC scrambled by either a C-RNTI (Cell-Radio Network Temporary Identifier). The terminal device 1 transmits a PUSCH scheduled based on the DCI format 0_0. The PUSCH may include a UE capability. Alternatively, the Msg5 is information contained in PDSCH scheduled by DCI format 0_0 with CRC scrambled by C-RNTI.

[0170] In this embodiment, all of PDSCH scheduled by DCI format 0_0 scrambled by C-RNTI (not only the PUSCH including UE capability) can be referred to as Msg5.

[0171] Data communication is a generic term for downlink communication and uplink communication.

[0172] In data communication, the terminal device 1 attempts to detect a PDCCH (attempts to monitor a PDCCH, monitors a PDCCH) in a resource identified at least based on one or all of a control resource set and a search-space-set. It’s also called as “the terminal device 1 attempts to detect a PDCCH in a control resource set”, “the terminal device 1 attempts to detect a PDCCH in a search-space-set”, “the terminal device 1 attempts to detect a PDCCH candidate in a control resource set”, “the terminal device 1 attempts to detect a PDCCH candidate in a search-space-sef ’, “the terminal device 1 attempts to detect a DCI format in a control resource set”, or “the terminal device 1 attempts to detect a DCI format in a search-space-sef ’. Monitoring a PDCCH may be equivalent as monitoring a DCI format in the PDCCH.

[0173] The control resource set is a set of resources configured by the number of resource blocks and a predetermined number of OFDM symbols in a slot.

[0174] The set of resources for the control resource set may be indicated by higher- layer parameters. The number of OFDM symbols included in the control resource set may be indicated by higher-layer parameters.

[0175] A PDCCH may be also called as a PDCCH candidate.

[0176] A search-space-set is defined as a set of PDCCH candidates. A search-space- set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

[0177] The CSS set is a generic name of a type-0 PDCCH common search-space-set, a type-Oa PDCCH common search-space-set, a type-1 PDCCH common search-space-set, a type-2 PDCCH common search-space-set, and a type-3 PDCCH common search-space- set. The USS set may be also called as UE-specific PDCCH search-space-set.

[0178] The type-0 PDCCH common search-space-set may be used as a common search-space-set with index 0. The type-0 PDCCH common search-space-set may be a common search-space-set with index 0.

[0179] A search-space-set is associated with (included in, corresponding to) a control resource set. The index of the control resource set associated with the search-space-set may be indicated by higher-layer parameters.

[0180] For a search-space-set, a part or all of 6 A to 6C may be indicated at least by higher-layer parameters. The 6A is PDCCH monitoring period. The 6B is PDCCH monitoring pattern within a slot. The 6C is PDCCH monitoring offset.

[0181] A monitoring occasion of a search-space-set may correspond to one or more OFDM symbols in which the first OFDM symbol of the control resource set associated with the search-space-set is allocated. A monitoring occasion of a search-space-set may correspond to resources identified by the first OFDM symbol of the control resource set associated with the search-space-set. A monitoring occasion of a search-space-set is givenbased at least on a part or all of PDCCH monitoring periodicity, PDCCH monitoring pattern within a slot, and PDCCH monitoring offset.

[0182] Figure 8 is a diagram showing an example of the monitoring occasion of the search-space-set. In Figure 8, the search-space-set 91 and the search-space-set 92 are sets in the primary cell 301, the search-space-set 93 is a set in the secondary cell 302, and the search-space-set 94 is a set in the secondary cell 303.

[0183] In Figure 8, 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.

[0184] In Figure 8, the PDCCH monitoring periodicity for the search-space-set 91 is set to 1 slot, the PDCCH monitoring offset for the search-space-set 91 is set to 0 slot, and the PDCCH monitoring pattern for the search-space-set 91 is [1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is, the monitoring occasion of the search-space-set 91 corresponds to the first OFDM symbol (OFDM symbol # 0) and the eighth OFDM symbol (OFDM symbol # 7) in each of the slots.

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

[0186] In Figure 8, the PDCCH monitoring periodicity for the search-space-set 93 is set to 2 slots, the PDCCH monitoring offset for the search-space-set 93 is set to 0 slots, and the PDCCH monitoring pattern for the search-space-set 93 is [0, 0, 0, 0, 0, 0, 0, 1, 0,0, 0, 0, 0, 0]. That is, the monitoring occasion of the search-space-set 93 corresponds to the eighth OFDM symbol (OFDM symbol # 8) in each of the even slots.

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

[0188] The type-0 PDCCH common search-space-set may be at least used for a DCI format with a cyclic redundancy check (CRC) sequence scrambled by an SI-RNTI (System Information-Radio Network Temporary Identifier).

[0189] The type-Oa PDCCH common search-space-set may be used at least for a DCI format with a cyclic redundancy check sequence scrambled by an SI-RNTI.

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

[0191] The type-2 PDCCH common search-space-set may be used for a DCI format with a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

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

[0193] The UE-specific search-space-set may be used at least for a DCI format with a CRC sequence scrambled by a C-RNTI.

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

[0195] In uplink communication, the terminal device 1 may detect an uplink DCI format. The detected uplink DCI format is at least used for resource assignment for a PUSCH. The detected uplink DCI format is also referred to as uplink grant. The terminal device 1 transmits the PUSCH.

[0196] PUSCH transmission(s) can be dynamically scheduled by an UL grant in a DCI, or the transmission can correspond to a configured grant Type 1 or Type 2. The configured grant Type 1 PUSCH transmission is semi-statically configured to operate upon the reception of higher layer parameter of configuredGrantConfig including rrc- ConfiguredUplinkGrant without the detection of an UL grant in a DCI. The configured grant Type 2 PUSCH transmission is semi-persistently scheduled by an UL grant in a valid activation DCI according to those procedure(s) after the reception of higher layer parameter configuredGrantConfig not including rrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList is configured, more than one configured grant configuration of configured grant Type 1 and / or configured grant Type 2 may be active at the same time on an active BWP of a serving cell.

[0197] The random access procedure may include a contention-based random access (CBRA) procedure and a contention-free random access (CFRA) procedure.

[0198] The random access procedure is initiated by a PDCCH order, by the MAC entity itself, or by RRC. There is only one random access procedure ongoing at any point in time in a MAC entity. The random access procedure on an SCell shall only be initiated by a PDCCH order.

[0199] The random access procedure may have two random access (RA) type which are 2-step RA type and 4-step RA type.

[0200] Following higher-layer parameters for the random access procedure may be configured by RRC. For example, the parameters are provided in the system information by base station 3.

[0201] prach-Configurationlndex indicates the available set of PRACH occasions for the transmission of the random access preamble for Msgl. These are also applicable to the MsgA PRACH if the PRACH occasions are shared between 2-step and 4-step RA types.

[0202] msgA-PRACH-Configurationlndex indicates the available set of PRACH occasions for the transmission of the random access preamble for MsgA in 2-step RA type.

[0203] preambleReceivedTargetPower indicates initial random access preamble power for 4-step RA type.

[0204] msgA-PreambleReceivedTargetP wer indicates initial random access preamble power for 2-step RA type.

[0205] rsrp-ThresholdSSB indicates an RSRP threshold for the selection of the SSB for 4-step RA type.

[0206] rsrp-ThresholdCSI-RS indicates an RSRP threshold for the selection of C SIRS for 4-step RAtype.

[0207] msgA-RSRP-ThresholdSSB indicates an RSRP threshold for the selection of the SSB for 2-step RA type.

[0208] msgA-RSRP -Threshold indicates an RSRP threshold for selection between 2- step RA type and 4-step RA type when both 2-step and 4-step RA type random access resources are configured in the UL BWP.

[0209] msgA-TransMax indicates the maximum number of MsgA transmissions when both 4-step and 2-step RA type Random Access Resources are configured.

[0210] power RampingStep indicates the power-ramping factor.

[0211] msgA-PreamblePowerRampingStep indicates the power ramping factor for MsgA preamble.

[0212] ra-Preamblelndex indicates a random access preamble;

[0213] ra-ssb-OccasionMasklndex defines PRACH occasion(s) associated with an SSB in which the MAC entity may transmit a random access preamble.

[0214] ra-OccasionList defines PRACH occasion(s) associated with a CSI-RS in which the MAC entity may transmit a random access preamble.

[0215] startPreambleForThisPartition indicates the first preamble associated with the set of random access resources applicable to the Random Access procedure.

[0216] preambleTransMax indicates the maximum number of random access preamble transmission.

[0217] ssb-perRACH-OccasionAndCB-PreamblesPerSSB defines the number of SSBs mapped to each PRACH occasion for 4-step RA type and the number of contentionbased Random Access Preambles mapped to each SSB.

[0218] msgA-CB-PreamblesPerSSB-PerSharedRO defines the number of contentionbased Random Access Preambles for 2-step RA type mapped to each SSB when the PRACH occasions are shared between 2-step and 4-step RA types.

[0219] msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB defines the number of SSBs mapped to each PRACH occasion for 2-step RA type and the number of contention-based Random Access Preambles mapped to each SSB.

[0220] numberOJPreamblesForThisPartition indicates the number of consecutive preambles associated with the set of random access resources applicable to the random access procedure.

[0221] ra-ResponseWindow indicates the time window to monitor RA response(s).

[0222] ra-ContentionResolutionTimer indicates the Contention Resolution Timer

[0223] totalNumberOfRA-Preambles indicates total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request).

[0224] The terminal device 1 may use following variables for the random access procedure.

[0225] PREAMBLE_TRANSMISSION_COUNTER is used to count the number of attempts of a preamble transmission.

[0226] PREAMBLE POWER RAMPING COUNTER is used to count the number of power ramping which increase the transmission power of the preamble transmission.

[0227] PREAMBLE POWER RAMPING STEP is used to storage the step size of power ramping.

[0228] PREAMBLE_RECEFVED_TARGET_POWER is used to storage the received target power of a preamble transmission.

[0229] TEMPORARY C-RNTI is used to storage the temporary C-RNTI.

[0230] RA TYPE is used to storage the RA type.

[0231] MSGA_PREAMBLE_POWER_RAMPING_STEP is used to storage the step size of power ramping for 2-step RA.

[0232] A user equipment (UE) is described. The UE may comprise reception circuitry configured to receive a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The UE may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The UE may also comprise transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1 (i.e. the TB is transmitted K slot(s)). The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition. The N may be the factor of transmission of Transport Block over Multiple Slots.

[0233] The reception circuitry comprised in the UE may be the Wireless transmission / reception unit 10 in Figure 6. The processing circuitry comprised in the UE may be the Higher-layer processing unit 14 in Figure 6. The transmission circuitry comprised in the UE may be the Wireless transmission / reception unit 10 in Figure 6.

[0234] A base station is described. The base station may comprise transmission circuitry configured to transmit a first configuration of Physical Uplink Shared Channel(PUSCH) including first information. The base station may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The base station may also comprise reception circuitry configured to receive a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1 (i.e. the TB is received K slot(s)). The K may be determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0235] The transmission circuitry comprised in the base station may be the Wireless transmission / reception unit 30 in Figure 5. The processing circuitry comprised in the base station may be the Higher-layer processing unit 34 in Figure 5. The reception circuitry comprised in the UE may be the Wireless transmission / reception unit 30 in Figure 5.

[0236] A user equipment (UE) is described. The UE may comprise reception circuitry configured to receive a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The UE may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The UE may also comprise transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH in N*K slot(s), wherein the N equal to 1 (i.e. the TB is transmitted K slot(s)). The UE may also comprise transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH inN*K slot(s). The N may be equal to 1. The K may be larger than 1 if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0237] A base station is described. The base station may comprise transmission circuitry configured to transmit a first configuration of Physical Uplink Shared Channel (PUSCH) including first information. The base station may also comprise processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DO) format 0J) with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI). The base station may also comprise reception circuitry configured to receive a Transport Block (TB) of the PUSCH in N*K slot(s). The N may be equal to 1 (i.e. the TB is received K slot(s)). The K may be larger than 1 if the first information is not provided and if the UE requests the repetition. The K may be determined to 1 if the first information is provided. The K may be determined to 1 if the UE does not request the repetition.

[0238]

[0239] When the random access procedure is initiated on a serving cell, the terminal device 1 (can be MAC entity of the terminal device 1) sets the PREAMBLE TRANSMISSION COUNTER to 1 and sets the PREAMBLE POWER RAMPING COUNTER to 1.

[0240] When the terminal device 1 performs 4-step RA procedure (RA TYPE is set to 4-stepRA), the terminal device 1 set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep which is higher layer parameter provided by RRC.

[0241] Figure 9 is a diagram illustrating an example of a contention-based random access (CBRA) procedure of the terminal device 1 according to the present embodiment.

[0242] In 901, the terminal device 1 transmits a random access preamble to the base station device (BS) 3 via a PRACH. The transmitted random access preamble may be referred to as a message 1 (Msgl, Msg 1). The transmission of the random access preamble will also be referred to as PRACH transmission. The random access preamble is configured to notify information to the BS 3 using one sequence among a plurality of sequences. For example, 64 types (the numbers of random access preamble indexes range from 1 to 64) of sequences are prepared. In a case that 64 types of sequences are prepared, it is possible to indicate 6-bit information (which may be ra-Preamblelndex or a preamble index) for the BS 3. The information may be indicated as a random access preamble identifier (Random Access Preamble Identifier, RAPID).

[0243] In 902, the base station 3 transmits a Random Access Response (RAR) to the terminal device 1 via a PDSCH scheduled by DCI format 0_0 with CRC scrambled by RA-RNTI. The RAR may include RAPID, Timing Advance Command, RAR Uplink grant (RAR UL grant), and Temporary C-RNTI (TC-RNTI). The BS 3 may indicate RAPID that recognized in Msgl. The Timing Advance Command is for terminal device 1 to adjust Uplink timing relative to Downlink timing. The RAR UL grant includes the scheduling information for UE to receive Msg3. The TC-RNTI may be used for receiving DCI format 0_0 scheduling Msg3 re-transmission and receiving DCI format l_0 scheduling Msg4.

[0244] In 903, the terminal device 1 may transmit a PUSCH that may include UE identity. The UE identity may be used for contention resolution

[0245] In 904, the base station 3 may transmit a PDSCH that may include contention resolution.

[0246] In 905, the terminal device 1 may transmit PUSCH that may include UE capability. The PUSCH may be scheduled by DCI format 0_0 with CRC scrambled by C- RNTI. Hereafter, PUSCH scheduled by DCI format 0_0 with CRC scrambled by C-RNTI can be referred to as “XPUSCH”. Hereafter, XPUSCH repetition is explained.

[0247] The System Information (SI) may include msg3 -Repetitions that may indicate, if present, signalling of Msg3 repetition is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type.

[0248] The System Information (SI) may include PUSCH_DCI_ 0_0_C-RNTI- Repetitions that may indicate, if present, signalling of repetition of XPUSCH is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type. This parameter can be referred to as msg5- Repetitions (1601).

[0249] The SI may include BWP -UplinkCommon. BWP -UplinkCommon may be used to configure the common parameters of an uplink BWP. They are "cell specific" and the network may ensure the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell may be also provided via system information (SI). For all other serving cells, the network may provide the common parameters via dedicated signalling. BWP -UplinkCommon may include following parameters.

[0250] numberOjMsg3-RepetitionsList may be the number of repetitions for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. This field may be only applicable when the UE selects Random Accessresources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication may be configured in the BWP -UplinkCommon, the UE may apply the values {nl, n2, n3, n4}.

[0251] rsrp-ThresholdMsg3 may be threshold used by the UE for determining whether to select resources indicating Msg3 repetition in this BWP. The field may be mandatory if both set(s) of Random Access resources with MSG3 repetition indication and set(s) of Random Access resources without MSG3 repetition indication are configured in the BWP. It may be absent otherwise.

[0252] number OfMsg5-RepetitionsList may be the number of repetitions for XPUSCH. This field may be only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with Msg5 repetition indication may be configured in the BWP -UplinkCommon, the UE may apply the pre-determined values.

[0253] rsrp-ThresholdMsg5 may be threshold used by the UE for determining whether to select resources indicating Msg5 repetition in this BWP. The field may be mandatory if both set(s) of Random Access resources with Msg5 repetition indication and set(s) of Random Access resources without Msg5 repetition indication are configured in the BWP. It may be absent otherwise.

[0254] numberOfPUSCHJ CI_0_0_C-RNTI-RepetitionsList may be the number of repetitions for XPUSCH (1501). This field may be only applicable when the UE selects Random Access resources indicating XPUSCH repetition in this BWP. If this field is absent when the set(s) of Random Access resources with XPUSCH repetition indication may be configured in the BWP -UplinkCommon, the UE may apply the pre-determined values.

[0255] rsrp-ThresholdPUSCH_DCI O O_C-RNTI may be threshold used by the UE for determining whether to select resources indicating XPUSCH repetition in this BWP (1502). The field may be mandatory if both set(s) of Random Access resources with XPUSCH repetition indication and set(s) of Random Access resources without XPUSCH repetition indication are configured in the BWP. It may be absent otherwise.

[0256] UE specific PUSCH configuration can be referred to as dedicated PUSCH configuration.

[0257] Dedicated PUSCH configuration is used to configure the UE specific PUSCH parameters applicable to a particular BWP. Some examples of dedicated PUSCH configuration are listed below.

[0258] pusch-AggregationFactor may be number of repetitions for data. If the field is absent the UE may apply the value 1.

[0259] pusch-TimeDomainAllocationList may be list of time domain allocations for timing of UL assignment to UL data (PUSCH-TimeDomainResourceAllocation). The field pusch-TimeDomainAllocationList may apply to DCI formats 0_0 or DCI format 0_l when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured.

[0260] PUSCH-TimeDomainResourceAllocation may include a parameter for PUSCH allocation and PUSCH-Allocation.

[0261] PUSCH-Allocation may include number OfRepetitions. numberOfRepetitions may be number of repetitions for DCI format 0_l / 0_2.

[0262] enablingPUSCH_DCI_0_0_C-RNTI-Repetition may indicate that XPUSCH repetition is applied. If dedicated PUSCH configuration is provided and if this field is absent, the XPUSCH repetition is not applied.

[0263] disablingPUSCH_DCI_0_0_C-RNTI-Repetition may indicate that XPUSCH repetition is not applied (1401). If dedicated PUSCH configuration is not provided or if this field is absent, the XPUSCH repetition is applied.

[0264] Aggregation of multiple slots with TB repetition for Msg3 transmission may be supported on both NUL and SUL, applicable to CBRA with 4-step RA type. If configured, the UE may request Msg3 repetition via separate RACH resources when the RSRP of DL path-loss reference is lower than a configured threshold. BWP configured with RACH resources solely for Msg3 repetition is also supported without the need to consider the RSRP of DL path-loss reference by the UE.

[0265] Aggregation of multiple slots with TB repetition for Msg5 transmission may be supported on both NUL and SUL, applicable to CBRA with 4-step RA type. If configured, the UE may request Msg5 repetition via separate RACH resources when the RSRP of DL path-loss reference is lower than a configured threshold. BWP configured with RACH resources solely for Msg5 repetition is also supported without the need to consider the RSRP of DL path-loss reference by the UE.

[0266] Aggregation of multiple slots with TB repetition for XPUSCH may be supported on both NUL and SUL, applicable to CBRA with 4-step RAtype. If configured, the UE may request XPUSCH repetition via separate RACH resources when the RSRP of DL path-loss reference is lower than a configured threshold. BWP configured with RACH resources solely for XPUSCH repetition is also supported without the need to consider the RSRP of DL path-loss reference by the UE.

[0267] PUSCH repetition type A is a procedure that the terminal device 1 repeat transmission of the TB across the K consecutive slots applying the same symbol allocation in each slot, where K is an integer number equal to or larger than 1.

[0268] Hereafter, the method to perform Msg3 repetition, Msg5 repetition and XPUSCH repetition (1003) is described.

[0269] For PUSCH repetition Type A, when transmitting PUSCH scheduled by DCI format 0_l or 0_2 in PDCCH with CRC scrambled with C-RNTI, MCS-C-RNTI, or CS- RNTI withNDI=l, the number of repetitions K may be determined as,- if numberOfRepetitions is present in the resource allocation table, the number of repetitions K is equal to numberOfRepetitions-,- elseif the UE is configured with pusch-AggregationFactor, the number of repetitions K is equal to pusch-AggregationFactor,'- otherwise K=l.A UE can be provided in BWP -UplinkCommon a set of numbers of repetitions for a PUSCH transmission with PUSCH repetition Type A that is scheduled by a RAR UL grant or by a DCI format 0_0 with CRC scrambled by a TC-RNTI. If the UE requests repetitions for the PUSCH transmission, the UE may transmit the PUSCH over N_"PUSCH"A"repeat" slots, where NJ'PUSCH"A"repeat" may be indicated by the 2 MSBs of the MCS field in the RAR UL grant or in the DCI format 0_0 from a set of four values provided by numberOfMsg3-RepetitionsList or from {1, 2, 3, 4} if numberOfMsg3-RepetitionsList is not provided. The UE may determine an MCS for the PUSCH transmission by the 2 LSBs of the MCS field in the RAR UL grant or by the 3 LSBs of the MCS field in the DCI format 0 0. For unpaired spectrum operation, the UE may determine the N_"PUSCH"A"repeat" slots as the first N_"PUSCH"A"repeat" slots starting from slot n+k_2+A where a repetition of the PUSCH transmission does not include a symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon orindicated as a symbol of an SS / PBCH block with index provided by ssb-PositionsInBurst. This repetition can be called as message 3 repetition (Msg3 repetition).

[0270] For PUSCH repetition type A, when transmiting PUSCH scheduled by RAR UL grant, the 2 MSBs of the MCS information field of the RAR UL grant may provide a codepoint to determine the number of repetitions K according to a pre-determined table, based on whether or not the higher layer parameter number OfMsg3-RepetitionsList provided by a System Information is configured. The number of slots used for TBS determination N may be equal to 1.This repetition procedure can be referred to as Msg3 repetition.

[0271] For PUSCH repetition type A, when transmiting PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the 2 MSBs of the MCS information field of the DCI format 0_0 with CRC scrambled by TC-RNTI may provide a codepoint to determine the number of repetitions K according to a pre-determined table, based on whether or not the higher layer parameter numberOJMsg3-RepetitionsList provided by a System Information is configured. The number of slots used for TBS determination N may be equal to 1.This repetition procedure can also be referred to as Msg3 repetition.

[0272] For PUSCH repetition type A, when transmitting XPUSCH,- if the UE requests repetitions for XPUSCH transmission, the terminal device 1 may determine the number of repetitions for XPUSCH repetition. The number of slots used for TBS determination N may be equal to 1.- otherwise, K=l.This repetition procedure can be called as XPUSCH repetition.

[0273] For PUSCH repetition type A, when transmitting XPUSCH,- if disablingMsg5Repetition in a dedicated PUSCH configuration is not provided (1301) and if the UE requests repetitions for XPUSCH transmission (1302), the terminal device1 may determine the number of repetitions for XPUSCH repetition (1303). The number of slots used for TBS determination N may be equal to 1.- otherwise, K=1 (1304).This repetition procedure can be referred to as XPUSCH repetition.

[0274] For PUSCH repetition type A, when transmitting XPUSCH,- if enablingMsg5Repetition in a dedicated PUSCH configuration is provided and if the UE requests repetitions for XPUSCH transmission, the terminal device 1 may determine the number of repetitions for XPUSCH repetition. The number of slots used for TBS determination N may be equal to 1.- otherwise, K=l.This repetition procedure can be referred to as XPUSCH repetition.

[0275] For PUSCH repetition type A, when transmitting XPUSCH,- if either a dedicated PUSCH configuration is not provided or the dedicated PUSCH configuration is provided and an enablingMsgS Repetition in the dedicated PUSCH configuration is provided and if the UE requests repetitions for XPUSCH transmission, the terminal device 1 may determine the number of repetitions for XPUSCH repetition. The number of slots used for TBS determination N may be equal to 1.- otherwise, K=l.This repetition procedure can be referred to as XPUSCH repetition.

[0276] For PUSCH repetition type A, when transmitting XPUSCH,- if dedicated PUSCH configuration is not provided and if the UE requests repetitions forXPUSCH transmission, the terminal device 1 may determine the number of repetitions for XPUSCH repetition. The number of slots used for TBS determination N may be equal to 1.- otherwise, K=1.This repetition procedure can be referred to as XPUSCH repetition.

[0277] Hereafter, the method of the number of repetitions determination (1002) for XPUSCH is described.

[0278] The terminal device 1 may determine the number of repetitions by one value of a list provided by higher layer parameter. Alternatively, the higher layer parameter may provide only one number of the repetitions.

[0279] The terminal device 1 may detect a DCI format 0_0 with CRC scrambled by C-RNTI. One of the plurality fields in the DCI format 0_0 may provide a codepoint to determine the number of repetitions K according to a pre-determined table, based on whether or not the higher layer parameter numberOfPUSCH_DCI_0_0_C-RNTI- RepetitionsList is configured.

[0280] One or more bit(s) of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0281] One or more MSB(s) of the MCS information field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0282] One or more LSB(s) of the MCS information field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0283] One or more MSB(s) of the HARQ process number field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0284] One or more LSB(s) of the HARQ process number field of the DCI format 0 0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0285] One or more bit(s) of the Channel Access CPext field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0286] One or more bit(s) of the TPC command field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0287] The UL / SUL field of the DCI format 0_0 with CRC scrambled by C-RNTI may provide a codepoint to determine the number of repetitions K.

[0288] The pre-determined table for Msg3 repetition or PUSCH repetition may indicate the mapping between list of number of repetitions configured by a system information in RRC message and the codepoint provided by the DCI indication.

[0289] For determination of the number of repetitions, the Msg3 repetition and the PUSCH repetition may refer different pre-determined table each other.

[0290] For determination of the number of repetitions, the Msg3 repetition and the PUSCH repetition may refer same pre-determined table each other.

[0291] Hereafter, the procedure of repetition request for Msg3 repetition and repetition request for XPUSCH repetition (1001) is described.

[0292] The MAC entity of the terminal device 1 may, if the B WP selected for RandomAccess procedure is configured with both set(s) of Random Access resources with msg3- Repetitions set to true and set(s) of Random Access resources without msg3-Repetitions set to true and the RSRP of the downlink pathloss reference is less than rsrp- ThresholdMsg3 (1101) or if the BWP selected for Random Access procedure is only configured with the set(s) of Random Access resources with msg3 -Repetitions set to true, assume Msg3 repetition is applicable for the current Random Access procedure (1102). Otherwise, the MAC entity shall Msg3 repetition is not applicable for the current Random Access procedure (1103).

[0293] Furthermore, if the BWP selected for Random Access procedure is configured with both set(s) of Random Access resources with msg5 -Repetitions set to true and set(s) of Random Access resources without msg5 -Repetitions set to true and the RSRP of the downlink pathloss reference is less than rsrp-ThresholdPUSCH_DCI 0_0_C-RNTI (1201) or if the BWP selected for Random Access procedure is only configured with the set(s) of Random Access resources with msg5 -Repetitions set to true, the MAC entity may assume XPUSCH repetition is also applicable for the current Random Access procedure (1202). Otherwise, the MAC entity shall XPUSCH repetition is not applicable for the current Random Access procedure (1203).

[0294] The value of rsrp-ThresholdPUSCH_DCI_0_0_C-RNTI may be always less than rsrp-ThresholdMsg3.

[0295] rsrp-ThresholdP USCH_DCI_0_0_C-RNTI may be indicated by relative value .

[0296] The MAC entity of the terminal device 1 may, if neither contention-free Random Access Resources nor Random Access Resources for SI request have been provided for this Random Access procedure and one or more of the features includingRedCap and / or Slicing and / or SDT and / or Msg3 repetition is applicable for this Random Access procedure, and if there is one set of Random Access resources available which can be used for indicating all features triggering this Random Access procedure, select this set of Random Access resources for this Random Access procedure.

[0297] The MAC entity of the terminal device 1 may, if neither contention-free Random Access Resources nor Random Access Resources for SI request have been provided for this Random Access procedure and one or more of the features including RedCap and / or Slicing and / or SDT and / or Msg3 repetition is applicable for this Random Access procedure, and if there are one or more sets of Random Access resources available that are configured with indication(s) for a subset of all features triggering this Random Access procedure, select this set of Random Access resources for this Random Access procedure.

[0298] The terminal device 1 may transmit PRACH on the selected set of Random Access resources in this Random Access procedure.

[0299] The terminal device 1 may request the XPUSCH repetition by using MAC sub-header or LCID in PUSCH scheduled by RAR UL grant or DCI 0_0 with CRC scrambled by TC-RNTI.

[0300] If terminal device 1 requests XPUSCH repetition, the terminal device 1 may transmit PUSCH scheduled by RAR UL grant or DCI 0_0 with CRC scrambled by TC- RNTI with LCID associated with XPUSCH repetition. Alternatively, if terminal device 1 requests XPUSCH repetition, the terminal device 1 may transmit PUSCH scheduled by RAR UL grant or DCI 0_0 with CRC scrambled by TC-RNTI with one or more MAC sub-header bit(s) indicating XPUSCH repetition.

[0301] For each Msg 1 transmission procedure, the terminal device 1 determines whether to increment the PREAMBLE POWER RAMPING COUNTER or not. In case that PREAMBLE_TRANSMISSION_COUNTER is greater than one (i.e. the Msg 1 procedure is a retransmission of PRACH), and in case that the notification of suspending power ramping counter has not been received from lower layers (can be physical layer control unit 10 of the terminal device 1), and if SSB or CSI-RS selected is not changed from the selection in the last random access preamble transmission, the terminal device 1 increment PREAMBLE_POWER_RAMPING_COUNTER by 1. For the increment, any other condition can be applied.

[0302] To determine the transmission power of the random access preamble, the terminal device 1 set the PREAMBLE RECEIVED TARGET POWER to preambleReceivedTargetPower + DELTA_PREAMBLE +(PREAMBLE_POWER_RAMPING_COUNTER - 1) *PREAMBLE POWER RAMPING STEP + POWER_OFFSET_2STEPJRA wherein preambleReceivedTargetPower is the higher layer parameter signaled by RRC, DELTA PREAMBLE is the variable which is determined based on a format used for the PRACH, and POWER_OFFSET_2STEP_RA is the power offset variable which is applied when RA_TYPE is switched from 2-stepRA to 4-stepRA during this random access procedure.

[0303] The MAC entity (MAC layer processing unit 15) of the terminal device 1 instruct the physical layer (physical layer control unit 10 of the terminal device 1) to transmit the random access preamble using the PREAMBLE RECEIVED TARGET POWER.

[0304] The physical layer of the terminal device 1 determines a transmission power for a PRACH, on active UL BWP of a carrier of a serving cell based on DL RS for servingcell as PPRACH = min{PCMAX, PREAMBLE RECEIVED TARGETJ’OWER + PL}, wherein PCMAX is the UE configured maximum output power, and PL is a pathloss for the active UL BWP of the carrier based on the DL RS associated with the PRACH transmission on the active DL BWP of the serving cell.

[0305] Physical Random Access procedure may be triggered upon request of a PRACH transmission by higher layers or by a PDCCH order. A configuration by higher layers for a PRACH transmission may include a configuration for PRACH transmission and a preamble index.

[0306] In response to a PRACH transmission, the terminal device 1 may attempt to detect a DCI format l_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers. The window may start at the first symbol of the earliest CORESET the terminal device 1 is configured to receive PDCCH for Typel- PDCCH CSS set, that is at least one symbol, after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Typel-PDCCH CSS set as defined.

[0307] The terminal device 1 which receives a PDSCH of Msg4 may transmit multiple PUCCHs for HARQ-ACK (can be referred to as Msg4 HARQ-ACK repetition or PUCCH repetition for Msg4 HARQ-ACK) corresponding to the PDSCH of Msg4.

[0308] The Msg3 repetition may help to increase the probability of detecting PUSCH for Msg3 at a base station 3.

[0309] The XPUSCH repetition may help to increase the probability of detecting XPUSCH at a base station 3.

[0310] The downlink pathloss reference may be an SS block which is detected by the terminal device 1. The set of Random Access resources may be the set of random accesspreambles and / or the set of time / frequency resources for transmitting a PRACH (can be referred to as RACH occasion). The set of Random Access resources used for indicating Msg4 HARQ-ACK repetition can be configured by higher layer. The set of Random Access resources used for indicating Msg4 HARQ-ACK repetition are separated resources from a set of Random Access resources that are not associated with Msg4 HARQ-ACK repetition.

[0311] Figure 17 is an example of FeatureCombinationPreambles which associates a set of preambles with a feature combination. FeatureCombinationPreambles may include featureCombination, startPreambleForThisPartition, numberOfPreamblesPerSSB- ForThisPartition, ssb-SharedRO-Masklndex, and rsrp-ThresholdSSB .

[0312] featureCombination is a parameter which indicates which combination of features that the preambles indicated by this parameter are associated with. The terminal device 1 ignores a RACH resource defined by this FeatureCombinationPreambles if any feature within the featureCombination is not supported by the UE or has an unknown value.

[0313] If msg3-Repetitions is present in featureCombination, the parameter indicates that signalling of Msg3 repetition is part of this feature combination.

[0314] If msg5-Repetitions is present in featureCombination, the parameter indicates that signalling of XPUSCH repetition is part of this feature combination.

[0315] startPreambleForThisPartition is a parameter which defines the first preamble associated with the feature combination.

[0316] numberOfPreamblesPerSSB-ForThisPartition is a parameter which determines how many consecutive preambles are associated to the feature combination starting from the starting preamble(s) per SSB.

[0317] ssb-SharedRO-Masklndex is a parameter which indicates a subset of ROs where preambles are allocated for this feature combination.

[0318] Each of a program running on the base station device and the terminal device according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) and the like, such that the program causes a computer to operate in such a manner as to realize the functions of the above-described embodiment according to the present invention. The information handled in these devices is transitorily stored in a Random-Access-Memory (RAM) while being processed. Thereafter, the information is stored in various types of Read-Only-Memory (ROM) such as a Flash ROM and a Hard- Disk-Drive (HDD), and when necessary, is read by the CPU to be modified or rewritten.

[0319] Note that the terminal device 1 and the base station device 3 according to the above-described embodiment may be partially achieved by a computer. In this case, this configuration may be realized by recording a program for realizing such control functions on a computer-readable recording medium and causing a computer system to read the program recorded on the recording medium for execution.

[0320] Note that it is assumed that the "computer system" mentioned here refers to a computer system built into the terminal device 1 or the base station device 3, and the computer system includes an OS and hardware components such as a peripheral device. Furthermore, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, and the like, and a storage device built into the computer system such as a hard disk.

[0321] Moreover, the "computer-readable recording medium" may include a medium that dynamically retains a program for a short period of time, such as a communication line that is used to transmit the program over a network such as the Internet or over acommunication line such as a telephone line, and may also include a medium that retains a program for a fixed period of time, such as a volatile memory within the computer system for functioning as a server or a client in such a case. Furthermore, the program may be configured to realize some of the functions described above, and also may be configured to be capable of realizing the functions described above in combination with a program already recorded in the computer system.

[0322] Furthermore, the base station device 3 according to the above-described embodiment may be achieved as an aggregation (an device group) including multiple devices. Each of the devices configuring such an device group may include some or all of the functions or the functional blocks of the base station device 3 according to the above-described embodiment. The device group may include each general function or each functional block of the base station device 3. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as the aggregation.

[0323] Furthermore, the base station device 3 according to the above-described embodiment may serve as an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) and / or NG-RAN (Next Gen RAN, NR-RAN). Furthermore, the base station device 3 according to the above-described embodiment may have some or all of the functions of a node higher than an eNodeB or the gNB.

[0324] Furthermore, some or all portions of each of the terminal device 1 and the base station device 3 according to the above-described embodiment may be typically achieved as an LSI which is an integrated circuit or may be achieved as a chip set. The functional blocks of each of the terminal device 1 and the base station device 3 may be individually achieved as a chip, or some or all of the functional blocks may be integrated into a chip.Furthermore, a circuit integration technique is not limited to the LSI, and may be realized with a dedicated circuit or a general-purpose processor. Furthermore, in a case that with advances in semiconductor technology, a circuit integration technology with which an LSI is replaced appears, it is also possible to use an integrated circuit based on the technology.

[0325] Furthermore, according to the above-described embodiment, the terminal device has been described as an example of a communication device, but the present invention is not limited to such a terminal device, and is applicable to a terminal device or a communication device of a fixed-type or a stationary-type electronic device installed indoors or outdoors, for example, such as an Audio-Video (AV) device, a kitchen device, a cleaning or washing machine, an air-conditioning device, office equipment, a vending machine, and other household devices.

[0326] Furthermore, according to the above-described embodiment, the words / parameters described by Italic may be RRC parameter, higher layer parameter, PC5-RRC parameter and / or preconfigured parameter.

[0327] The embodiments of the present invention have been described in detail above referring to the drawings, but the specific configuration is not limited to the embodiments and includes, for example, an amendment to a design that falls within the scope that does not depart from the gist of the present invention. Furthermore, various modifications are possible within the scope of one aspect of the present invention defined by claims, and embodiments that are made by suitably combining technical means disclosed according to the different embodiments are also included in the technical scope of the present invention. Furthermore, a configuration in which constituent elements, described in therespective embodiments and having mutually the same effects, are substituted for one another is also included in the technical scope of the present invention.

Claims

[CLAIMS]1. A user equipment (UE) comprising: reception circuitry configured to receive a first configuration of Physical Uplink Shared Channel (PUSCH) including first information; and processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI); and transmission circuitry configured to transmit a Transport Block (TB) of the PUSCH in N*K slot(s), wherein the N is equal to 1; wherein the K is determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition, the K is determined to 1 if the first information is provided, and the K is determined to 1 if the UE does not request the repetition.

2. The UE according to the claim 1 : wherein the K is determined based on a code point which is provided by one or more bit(s) in Modulation and Coding Scheme (MCS) information field of a scheduling DCI format 0 0 with CRC scrambled by C-RNTI if a first information is not provided in the first configuration and if the UE requested the repetitions.

3. A base station comprising: transmission circuitry configured to transmit a first configuration of Physical Uplink Shared Channel (PUSCH) including first information; and processing circuitry configured to determine a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI); and reception circuitry configured to receive a Transport Block (TB) of the PUSCH in N*K slot(s), wherein the N is equal to 1; wherein the K is determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition,the K is determined to 1 if the first information is provided, and the K is determined to 1 if the UE does not request the repetition.

4. Abase station according to the claim 3: wherein the K is determined based on a code point which is provided by one or more bit(s) in Modulation and Coding Scheme (MCS) information field of a scheduling DCI format 0_0 with CRC scrambled by C-RNTI if a first information is not provided in the first configuration and if the UE requested the repetitions.

5. A method for a user equipment (UE) comprising: receiving a first configuration of Physical Uplink Shared Channel (PUSCH) including first information; and determining a number of repetition(s), K, for a PUSCH scheduled by Downlink Control Information (DCI) format 0_0 with Cyclic Redundancy Check (CRC) scrambled by Cell Radio Network Temporary Identifier (C-RNTI); and transmitting a Transport Block (TB) of the PUSCH in N*K slot(s), wherein the N is equal to 1 ; wherein the K is determined from multiple candidates of number of repetitions if the first information is not provided and if the UE requests the repetition, the K is determined to 1 if the first information is provided, and the K is determined to 1 if the UE does not request the repetition.

Images