Terminal device and base station device
By implementing frequency hopping for PUSCH transmissions based on DCI or random access response grants with specific parameters, the communication efficiency of terminal and base station devices is enhanced, addressing the inefficiencies in existing LTE and NR systems for diverse communication scenarios.
Patent Information
- Application Number
- JP2021159397
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2021-09-29
- Publication Date
- 2024-11-13
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing radio access technologies in LTE and NR systems face challenges in efficiently managing communication methods for terminal and base station devices, particularly in scenarios requiring enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC), which are not adequately addressed by current standards.
The implementation of frequency hopping for PUSCH transmissions in terminal and base station devices, where the frequency hopping interval is determined by DCI or random access response grants, with specific parameters such as C-RNTI, CS-RNTI, or MCS-C-RNTI, to optimize communication efficiency.
This approach enhances communication efficiency by optimizing frequency hopping intervals, thereby improving the performance of terminal and base station devices in handling diverse communication scenarios, including eMBB, mMTC, and URLLC.
Smart Images

Figure 2024160191000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a terminal device and a base station device. [Background technology]
[0002] The radio access method and radio network for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is being developed by the Third Generation Partnership Project (3GPP: 3 rd The LTE standard is being considered in the LTE Generation Partnership Project. In LTE, a base station device is also called eNodeB (evolved NodeB), and a terminal device is also called UE (User Equipment). LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cell shapes. A single base station device may manage multiple serving cells.
[0003] In 3GPP, the International Telecommunication Union (ITU) The next-generation standard (NR: New Radio) is being studied to be proposed for IMT (International Mobile Telecommunication)-2020, the standard for the next-generation mobile communication system to be formulated (Non-Patent Document 1). NR is required to meet the requirements for three scenarios, eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication), within a single technology framework.
[0004] In 3GPP, the extension of services supported by NR is being considered (Non-Patent Document 2). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. [Non-Patent Document 2] “Release 17 package for RAN”, RP-193216, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #86, Sitges, Spain, 9th ― 12th December, 2019 Summary of the Invention [Problem to be solved by the invention]
[0006] The present invention provides a terminal device that performs efficient communication, a communication method used in the terminal device, a base station device that performs efficient communication, and a communication method used in the base station device. [Means for solving the problem]
[0007] (1) A first aspect of the present invention is a terminal device comprising: a receiving unit that receives a PDCCH including a DCI or a PDSCH including a random access response grant; and a transmitting unit that transmits a PUSCH, the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based on at least the DCI or the random access response grant, repeated transmission is instructed for the PUSCH, the transmission of the PUSCH is instructed by the DCI, and the D When the CI is accompanied by a CRC scrambled by the TC-RNTI, the frequency hopping interval corresponding to the frequency hopping is 1 slot, when the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot, and when the DCI indicates transmission of the PUSCH and the DCI is accompanied by at least a C-RNTI, and a CRC scrambled by either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by certain higher layer parameters.
[0008] (2) Also, a second aspect of the present invention is a base station device comprising: a transmitter that transmits a PDCCH including a DCI or a PDSCH including a random access response grant; and a receiver that receives a PUSCH, wherein the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based on at least the DCI or the random access response grant, repeated transmission is instructed for the PUSCH, transmission of the PUSCH is instructed by the DCI, and When the DCI is accompanied by a CRC scrambled by the TC-RNTI, the frequency hopping interval corresponding to the frequency hopping is 1 slot, when the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot, and when the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by at least a C-RNTI, and either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by a certain higher layer parameter.
[0009] (3) Also, a third aspect of the present invention is a communication method used in a terminal device, comprising: a step of receiving a PDCCH including a DCI or a PDSCH including a random access response grant; and a step of transmitting a PUSCH, wherein the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based at least on the DCI or the random access response grant, repeated transmission is instructed for the PUSCH, and transmission of the PUSCH is instructed by the DCI. When the DCI is accompanied by a CRC scrambled by a TC-RNTI, the frequency hopping interval corresponding to the frequency hopping is 1 slot, when the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot, and when the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by at least a C-RNTI, and either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by a certain higher layer parameter.
[0010] (4) Also, a fourth aspect of the present invention is a communication method used in a base station device, comprising: a step of transmitting a PDCCH including a DCI or a PDSCH including a random access response grant; and a step of receiving a PUSCH, wherein the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based on at least the DCI or the random access response grant, repeated transmission is instructed for the PUSCH, and transmission of the PUSCH is instructed by the DCI. When the DCI is accompanied by a CRC scrambled by a TC-RNTI, the frequency hopping interval corresponding to the frequency hopping is 1 slot, when the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot, and when the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by at least a C-RNTI, and either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by a certain higher layer parameter. Effect of the Invention
[0011] According to the present invention, the terminal device can perform communication efficiently, and the base station device can perform communication efficiently. [Brief description of the drawings]
[0012] [Figure 1] 1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. [Diagram 2] 1 is an example showing a relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and a cyclic prefix (CP) setting according to an aspect of the present embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. [Figure 4]FIG. 3 is a diagram illustrating an example of the configuration of a resource grid 3001 according to an aspect of the present embodiment. [Diagram 5] 2 is a schematic block diagram illustrating a configuration example of a base station device 3 according to an aspect of the present embodiment. FIG. [Figure 6] 1 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. [Figure 8] A diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. [Figure 9] 1A and 1B are diagrams illustrating examples of a set time domain window and an actual time domain window according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, an embodiment of the present invention will be described.
[0014] floor(C) may be a floor function for real number C. For example, floor(C) may be a function that outputs the largest integer not exceeding real number C. ceil(D) may be a ceiling function for real number D. For example, ceil(D) may be a function that outputs the smallest integer not below real number D. mod(E,F) may be a function that outputs the remainder when E is divided by F. mod(E,F) may be a function that outputs a value corresponding to the remainder when E is divided by F. exp(G)=e^G. Here, e is Napier's constant. H^I indicates H to the Ith power. max(J,K) is a function that outputs the maximum value of J and K. Here, max(J,K) is a function that outputs J or K when J and K are equal. min(L,M) is a function that outputs the maximum value of L and M. Here, min(L,M) is a function that outputs L or M when L and M are equal. round(N) is a function that outputs the integer value closest to N. “·” indicates multiplication.
[0015] In a wireless communication system according to an aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a unit of OFDM in the time domain. The OFDM symbol includes at least one or a plurality of subcarriers. The OFDM symbol is converted into a time-continuous signal in baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) is used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be provided by applying transform precoding to CP-OFDM.
[0016] The OFDM symbol may be a name including a CP added to the OFDM symbol, that is, a certain OFDM symbol may be configured to include the certain OFDM symbol and a CP added to the certain OFDM symbol.
[0017] Fig. 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. In Fig. 1, the wireless communication system includes at least terminal devices 1A to 1C and a base station device 3 (BS#3: Base station#3). Hereinafter, the terminal devices 1A to 1C are also referred to as terminal device 1 (UE#1: User Equipment#1).
[0018] The base station device 3 may be configured to include one or more transmission devices (or transmission points, transmission / reception devices, transmission / reception points). When the base station device 3 is configured with multiple transmission devices, each of the multiple transmission devices may be located at a different position.
[0019] The base station device 3 may provide one or more serving cells. The serving cell may be defined as a set of resources used for wireless communication. The serving cell may also be called a cell.
[0020] A serving cell may be configured to include one downlink component carrier (downlink carrier) and / or one uplink component carrier (uplink carrier). A serving cell may be configured to include two or more downlink component carriers and / or two or more uplink component carriers. Downlink component carriers and uplink component carriers are also collectively referred to as component carriers (carriers).
[0021] For example, one resource grid may be provided for each component carrier. Also, one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration μ, where the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be provided for a set of an antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x.
[0022] The resource grid is size,μ grid,x N RB sc where the resource grid includes common resource blocks N start,μ grid,x Also, common resource block N start,μ grid,x is also referred to as the reference point of the resource grid.
[0023] The resource grid is subframe,μ symbIt contains OFDM symbols.
[0024] The subscript x added to the resource grid related parameters indicates the transmission direction, for example, the subscript x may be used to indicate either the downlink or the uplink.
[0025] N size,μ grid,x is the offset setting indicated by a parameter provided by the RRC layer (e.g., the CarrierBandwidth parameter). start,μ grid,x is a bandwidth configuration indicated by a parameter provided by the RRC layer (eg, parameter OffsetToCarrier). The offset configuration and the bandwidth configuration are configurations used to configure an SCS-specific carrier.
[0026] Subcarrier spacing (SCS) for a certain subcarrier spacing setting μ )Δf is Δf=2 μ 15 kHz, where the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.
[0027] FIG. 2 shows a subcarrier interval setting μ and the number of OFDM symbols per slot N according to one embodiment of the present invention. slot symb , and CP (cyclic prefix) setting relationship In FIG. 2A, for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N slot symb =14, N frame,μ slot =40, N subframe,μ slot In FIG. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is the extended cyclic prefix (CP), Nslot symb =12, N frame,μ slot =40, N subframe,μ slot =4.
[0028] Time unit T c may be used to express a length in the time domain. c is T c =1 / (Δf max N f ) Δf max = 480kHz. f = 4096. The constant κ is κ = Δf max N f / (Δf ref N f,ref ) = 64. Δf ref is 15kHz. f,ref is 2048.
[0029] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be of length T f The radio frames (system frames, frames) may be organized into T f =(Δf max N f / 100)·T s = 10 ms. A radio frame is made up of 10 subframes. The length of a subframe is T sf =(Δf max N f / 1000)·T s = 1 ms. The number of OFDM symbols per subframe is N subframe,μ symb =N slot symb N subframe,μ slot It is.
[0030] An OFDM symbol is a unit of time domain for one communication method. For example, an OFDM symbol may be a unit of time domain for CP-OFDM. Also, an OFDM symbol may be a unit of time domain for DFT-s-OFDM.
[0031] A slot may consist of multiple OFDM symbols. For example, N consecutive slot symb One slot may be composed of N OFDM symbols. For example, in the normal CP setting, slot symb In addition, in the setting of the extended CP, N slot symb =12.
[0032] For a given subcarrier spacing setting μ, the number and index of slots contained in a subframe may be given. For example, slot index n μ s ranges from 0 to N in the subframe. subframe,μ slot For the subcarrier spacing setting μ, the number and index of slots included in the radio frame may be given. Also, the slot index n μ s,f ranges from 0 to N in the radio frame. frame,μ slot Integer values in the range -1 through increasing order may be given.
[0033] FIG. 3 is a diagram showing an example of a method for configuring a resource grid according to one aspect of the present embodiment. The horizontal axis in FIG. 3 indicates the frequency domain. FIG. 3 shows a configuration example of a resource grid with a subcarrier spacing μ1 in a component carrier 300, and a configuration example of a resource grid with a subcarrier spacing μ2 in the certain component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier. In FIG. 3, it is assumed that μ1=μ2-1, but various aspects of the present embodiment are not limited to the condition of μ1=μ2-1.
[0034] The component carrier 300 is a band having a predetermined width in the frequency domain.
[0035] The point 3000 is an identifier for identifying a certain subcarrier. Point 3000 is also referred to as point A. Common resource block (CRB) set 3100 is a set of common resource blocks for subcarrier spacing setting μ1.
[0036] In the common resource block set 3100, the common resource block including the point 3000 (a black block in the common resource block set 3100 in FIG. 3) is also called the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.
[0037] The offset 3011 is an offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks for a subcarrier spacing setting μ1. The resource grid 3001 is an N size,μ grid1,x It contains common resource blocks.
[0038] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N start,μ BWP,i1 )
[0039] Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting μ2.
[0040] In the common resource block set 3200, the common resource block including the point 3000 (a black block in the common resource block set 3200 in FIG. 3 ) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.
[0041] The offset 3012 is an offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing μ. The resource grid 3002 is N size,μ grid2,x It contains common resource blocks.
[0042] The offset 3014 is the distance from the reference point of the resource grid 3002 to the reference point of the BWP 3004 with index i2 (N start,μ BWP,i2 )
[0043] 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of FIG. 4, the horizontal axis represents the OFDM symbol index l sym and the vertical axis is the subcarrier index k sc The resource grid 3001 is size,μ grid1,x N RB sc It contains N subcarriers. subframe,μ symb Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The resource identified by , also called a resource element (RE).
[0044] A resource block (RB) is N RB sc A resource block includes a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). RB sc =12.
[0045] A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block, i.e., one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.
[0046] The common resource blocks for a given subcarrier spacing setting μ are indexed in a given common resource block set in the frequency domain starting from 0 in ascending order. The common resource block with index 0 for a given subcarrier spacing setting μ contains (or collides with, or coincides with) point 3000. The index n of the common resource block for a given subcarrier spacing setting μ μ CRB is n μ CRB =ceil(k sc / N RB sc ) relationship is satisfied. Here, k sc A subcarrier with a center frequency of 0 is a subcarrier having the same center frequency as the subcarrier corresponding to point 3000.
[0047] The physical resource blocks for a given subcarrier spacing configuration μ are indexed in the frequency domain starting from 0 in ascending order in a given BWP. μ PRB is nμ CRB =n μ PRB +N start,μ BWP,i Here, N start,μ BWP,i denotes the reference point of the BWP with index i.
[0048] A BWP is defined as a subset of common resource blocks contained in the resource grid. start,μ BWP,i Starting with N size,μ BWP,i The BWP configured for the downlink carrier is also called downlink BWP. The BWP configured for the uplink component carrier is also called uplink BWP.
[0049] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel, and the symbol may correspond to an OFDM symbol, and the symbol may correspond to a resource block unit, and the symbol may correspond to a resource element.
[0050] When the large scale properties of a channel through which a symbol is transmitted at one antenna port can be estimated from the channel through which a symbol is transmitted at another antenna port, the two antenna ports are said to be Quasi Co-Located (QCL). Here, the large scale properties may include at least long-range properties of the channel. The large scale properties may include at least some or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first antenna port and the second antenna port being QCL with respect to beam parameters may mean that a receiving beam assumed by the receiving side for the first antenna port is the same (or corresponds) as a receiving beam assumed by the receiving side for the second antenna port. The first antenna port and the second antenna port being QCLs in terms of beam parameters may mean that a transmission beam assumed by the receiving side for the first antenna port and a transmission beam assumed by the receiving side for the second antenna port are the same (or correspond to each other). The terminal device 1 may assume that the two antenna ports are QCLs if the large-scale characteristics of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port. The two antenna ports being QCLs may mean that the two antenna ports are assumed to be QCLs.
[0051] Carrier aggregation is the process of aggregating multiple serving The carrier aggregation may be a communication using a cell. Also, the carrier aggregation may be a communication using a plurality of aggregated component carriers. Also, the carrier aggregation may be a communication using a plurality of aggregated downlink component carriers. Also, the carrier aggregation may be a communication using a plurality of aggregated uplink component carriers.
[0052] Fig. 5 is a schematic block diagram showing a configuration example of a base station device 3 according to one aspect of the present embodiment. As shown in Fig. 5, the base station device 3 includes at least a radio transmission / reception unit (physical layer processing unit) 30 and / or a part or all of a higher layer processing unit 34. The radio transmission / reception unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and a part or all of a baseband unit 33. The higher layer processing unit 34 includes at least a medium access control layer processing unit 35 and a part or all of a radio resource control (RRC) layer processing unit 36.
[0053] The wireless transceiver 30 includes at least a wireless transmitter 30a and a part or all of a wireless receiver 30b. Here, the device configurations of the baseband unit included in the wireless transmitter 30a and the baseband unit included in the wireless receiver 30b may be the same or different. Furthermore, the device configurations of the RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may be the same or different. Furthermore, the device configurations of the antenna unit included in the wireless transmitter 30a and the antenna unit included in the wireless receiver 30b may be the same or different.
[0054] For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDSCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDCCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PBCH. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a synchronization signal. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDSCH DMRS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a PDCCH DMRS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a CSI-RS. For example, the wireless transmitting unit 30a may generate and transmit a baseband signal of a DL PTRS.
[0055] For example, the wireless receiving unit 30b may receive a PRACH. For example, the wireless receiving unit 30b may receive and demodulate a PUCCH. The wireless receiving unit 30b may receive and demodulate a PUSCH. For example, the wireless receiving unit 30b may receive a PUCCH DMRS. For example, the wireless receiving unit 30b may receive a PUSCH DMRS. For example, the wireless receiving unit 30b may receive a UL PTRS. For example, the wireless receiving unit 30b may receive an SRS.
[0056] The upper layer processing unit 34 outputs the downlink data (transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The upper layer processing unit 34 performs processing of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and an RRC layer.
[0057] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer.
[0058] The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 sets parameters based on an RRC message received from the terminal device 1.
[0059] The radio transceiver 30 (or the radio transmitter 30a) performs processes such as modulation and encoding. The radio transceiver 30 (or the radio transmitter 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting into a time-continuous signal) downlink data, and transmits the physical signal to the terminal device 1. The radio transceiver 30 (or the radio transmitter 30a) may allocate the physical signal to a certain component carrier and transmit the physical signal to the terminal device 1.
[0060] The wireless transceiver unit 30 (or the wireless receiver unit 30b) performs processes such as demodulation and decoding. The wireless transceiver unit 30 (or the wireless receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The wireless transceiver unit 30 (or the wireless receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.
[0061] The RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation (down-converts) and removes unnecessary frequencies. The RF unit 32 outputs the processed analog signal to the baseband unit.
[0062] The baseband unit 33 converts the analog signal input from the RF unit 32 into The baseband unit 33 converts the digital signal into a digital signal. The baseband unit 33 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, and converts the signal into a CP-removed signal. A Fast Fourier Transform (FFT) is performed on the signal to extract the frequency domain signal.
[0063] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32.
[0064] The RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. The RF unit 32 may also have a function of controlling transmission power. The RF unit 32 is also referred to as a transmission power control unit.
[0065] For the terminal device 1, one or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured.
[0066] Each of the serving cells configured for the terminal device 1 is a PCell (Primary cell The cell may be any one of a Primary SCG cell (PSCell), a Primary SCG cell (PSCell), and a Secondary Cell (SCell).
[0067] The PCell is a serving cell included in a Master Cell Group (MCG). ell executes an initial connection establishment procedure or a connection re-establishment procedure by the terminal device 1. This is the cell where the action is taken (the cell where the action was taken).
[0068] The PSCell is a serving cell included in a secondary cell group (SCG). The PSCell is a serving cell to which the terminal device 1 performs random access.
[0069] The SCell may be included in either the MCG or the SCG.
[0070] The term "serving cell group" (cell group) refers to at least the MCG and the SCG. The serving cell group may include one or more serving cells (or component carriers). The one or more serving cells (or component carriers) included in the serving cell group may be operated by carrier aggregation.
[0071] One or more downlink BWPs may be configured for each serving cell (or downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).
[0072] Of one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP may be configured as an active downlink BWP (or one downlink BWP may be activated). Of one or more uplink BWPs configured for a serving cell (or an uplink component carrier), one uplink BWP may be configured as an active uplink BWP (or one uplink BWP may be activated).
[0073] The PDSCH, PDCCH, and CSI-RS may be received in an active downlink BWP. The terminal device 1 may attempt to receive the PDSCH, PDCCH, and CSI-RS in the active downlink BWP. The PUCCH and PUSCH may be transmitted in an active uplink BWP. The terminal device 1 may transmit the PUCCH and PUSCH in the active uplink BWP. The active downlink BWP and the active uplink BWP are also collectively referred to as an active BWP.
[0074] The PDSCH, PDCCH, and CSI-RS may not be received in a downlink BWP (inactive downlink BWP) other than the active downlink BWP. The terminal device 1 may not attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP. The PUCCH and PUSCH may not be transmitted in an uplink BWP (inactive uplink BWP) that is not an active uplink BWP. The terminal device 1 may not transmit the PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are collectively referred to as the inactive BWP.
[0075] A downlink BWP switch is a procedure for deactivating one active downlink BWP of a serving cell and activating one of the inactive downlink BWPs of the serving cell. The downlink BWP switch may be controlled by a BWP field included in the downlink control information. The downlink BWP switch may be controlled based on higher layer parameters.
[0076] The uplink BWP switching is used to deactivate one active uplink BWP and activate any inactive uplink BWP other than the one active uplink BWP. The uplink BWP switching may be controlled by a BWP field included in the downlink control information. The uplink BWP switching may be controlled based on higher layer parameters.
[0077] Of one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs. For a serving cell, one downlink BWP may be active at a certain time.
[0078] Of one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. For a serving cell, one uplink BWP may be active at a given time.
[0079] Fig. 6 is a schematic block diagram showing a configuration example of a terminal device 1 according to one aspect of the present embodiment. As shown in Fig. 6, the terminal device 1 includes at least a radio transmission / reception unit (physical layer processing unit) 10 and one or all of an upper layer processing unit 14. The radio transmission / reception unit 10 includes at least an antenna unit 11, an RF unit 12, and some or all of a baseband unit 13. The upper layer processing unit 14 includes at least a medium access control layer processing unit 15 and some or all of a radio resource control layer processing unit 16.
[0080] The wireless transceiver 10 includes at least a wireless transmitter 10a and a part or all of a wireless receiver 10b. Here, the device configurations of the baseband unit 13 included in the wireless transmitter 10a and the baseband unit 13 included in the wireless receiver 10b may be the same or different. The device configurations of the RF unit 12 included in the wireless transmitter 10a and the RF unit 12 included in the wireless receiver 10b may be the same or different. The device configurations of the antenna unit 11 included in the wireless transmitter 10a and the antenna unit 11 included in the wireless receiver 10b may be the same or different.
[0081] For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PRACH. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUCCH. The radio transmission unit 10a may generate and transmit a baseband signal of a PUSCH. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUCCH DMRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a PUSCH DMRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of a UL PTRS. For example, the radio transmission unit 10a may generate and transmit a baseband signal of an SRS.
[0082] For example, the wireless receiver 10b may receive and demodulate the PDSCH. The wireless receiving unit 10b may receive and demodulate a PDCCH. For example, the wireless receiving unit 10b may receive and demodulate a PBCH. For example, the wireless receiving unit 10b may receive a synchronization signal. For example, the wireless receiving unit 10b may receive a PDSCH DMRS. For example, the wireless receiving unit 10b may receive a PDCCH DMRS. For example, the wireless receiving unit 10b may receive a CSI-RS. For example, the wireless receiving unit 10b may receive a DL PTRS.
[0083] The upper layer processing unit 14 outputs the uplink data (transport block) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 performs processing of the MAC layer, the packet data integration protocol layer, the radio link control layer, and the RRC layer.
[0084] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer.
[0085] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. The radio resource control layer processing unit 16 manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets the RRC parameters based on an RRC message received from the base station device 3.
[0086] The wireless transceiver 10 (or the wireless transmitter 10a) performs processes such as modulation and encoding. The wireless transceiver 10 (or the wireless transmitter 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits the physical signal to the base station device 3. The wireless transceiver 10 (or the wireless transmitter 10a) may place the physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.
[0087] The wireless transceiver unit 10 (or the wireless receiver unit 10b) performs processes such as demodulation and decoding. The wireless transceiver unit 10 (or the wireless receiver unit 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The wireless transceiver unit 10 (or the wireless receiver unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver unit 10 (wireless receiver unit 10b) may perform a channel access procedure prior to transmitting the physical signal.
[0088] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-converts) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13.
[0089] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 then subtracts a CP (Cyclic Prefix) from the converted digital signal. The corresponding portion is removed, and the signal from which the CP has been removed is subjected to a Fast Fourier Transform (FFT) to extract the signal in the frequency domain.
[0090] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, and The baseband unit 13 adds a CP to generate a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.
[0091] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 may also have a function of controlling transmission power. The RF unit 12 is also referred to as a transmission power control unit.
[0092] The physical signals (signals) will be explained below.
[0093] The physical signal is a general term for the downlink physical channel, the downlink physical signal, the uplink physical channel, and the uplink physical channel. The physical channel is a general term for the downlink physical channel and the uplink physical channel. The physical signal is a general term for the downlink physical signal and the uplink physical signal.
[0094] The uplink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by a terminal device 1. The uplink physical channel may be received by a base station device 3. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels may be used. ·PUCCH (Physical Uplink Control CHannel) ·PUSCH (Physical Uplink Shared CHannel) ·PRACH(Physical Random Access CHannel)
[0095] The PUCCH may be used to transmit uplink control information (UCI). The PUCCH may be transmitted to deliver, transmit, or convey the uplink control information. The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit the PUCCH in which the uplink control information is mapped. The base station device 3 may receive the PUCCH in which the uplink control information is mapped.
[0096] Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) is channel state information (CSI), schedule The SR includes at least a part or all of the Scheduling Request (SR) and Hybrid Automatic Repeat request ACKnowledgement (HARQ-ACK) information.
[0097] The channel state information is also referred to as a channel state information bit or a channel state information sequence. The scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. The HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.
[0098] The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). The HARQ-ACK may include an ACK (acknowledgement) or a NACK (negative-acknowledgement) corresponding to the transport block. ). The ACK may indicate that the decoding of the transport block has been successfully completed. The NACK may indicate that the decoding of the transport block has not been successfully completed. The HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ-ACK bits.
[0099] A transport block is a sequence of information bits delivered from higher layers. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be delivered via an UpLink-Shared CHannel (UL-SCH) in the transport layer.
[0100] HARQ-ACK for the transport block and HARQ- In this case, "HARQ-ACK for the PDSCH" refers to a HARQ-ACK for a transport block included in the PDSCH.
[0101] The HARQ-ACK may indicate an ACK or NACK corresponding to one Code Block Group (CBG) included in the transport block.
[0102] The scheduling request may be used at least to request UL-SCH resources for an initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. The scheduling request bit indicating a positive SR is also referred to as "a positive SR is transmitted". The positive SR may indicate that UL-SCH resources for an initial transmission are requested by the terminal device 1. The positive SR may indicate that a scheduling request is triggered by a higher layer. The positive SR may be transmitted when a scheduling request is indicated by a higher layer. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted". The negative SR may indicate that UL-SCH resources for an initial transmission are not requested by the terminal device 1. The negative SR may indicate that a scheduling request is not triggered by a higher layer. The negative SR may be transmitted when a scheduling request is not indicated by a higher layer.
[0103] The channel state information may include at least some or all of a Channel Quality Indicator (CQI), a Precoder Matrix Indicator (PMI), and a Rank Indicator (RI). The CQI is an index related to the quality of a propagation path (e.g., propagation strength) or the quality of a physical channel, and the PMI is an index related to a precoder. The RI is an index related to a transmission rank (or the number of transmission layers).
[0104] The channel state information is an indicator regarding the reception state of at least a physical signal (e.g., CSI-RS) used for channel measurement. The value of the channel state information may be determined by the terminal device 1 based on the reception state assumed by at least a physical signal used for channel measurement. The channel measurement may include an interference measurement.
[0105] The PUCCH may correspond to a PUCCH format. The PUCCH may be a set of resource elements used to convey the PUCCH format. The PUCCH may include a PUCCH format. The PUCCH may be transmitted with a certain PUCCH format. The PUCCH format may be interpreted as a format of information. The PUCCH format may also be interpreted as a set of information set to a certain information format.
[0106] The PUSCH may be used to transmit one or both of a transport block and uplink control information. The PUSCH may be used to transmit a transport block and uplink control information delivered by the UL-SCH. The transport block may be arranged in the PUSCH. The transport block delivered by the UL-SCH may be arranged in the PUSCH. The uplink control information may be arranged in the PUSCH. The terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are arranged. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are arranged.
[0107] The PRACH may be transmitted to carry a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. u,v (n) is x u,v (n)=x u (mod(n+C v ,L RA ) where x u is a ZC (Zadoff Chu) sequence. Also, x u x u =exp(-jπui(i+1) / L RA ), where j is the imaginary unit, and π is the ratio of the circumference of a circle to its circumference. v corresponds to the cyclic shift of the PRACH sequence. RA corresponds to the length of the PRACH sequence. RA is 839 or 139. Also, i ranges from 0 to L RA where u is an integer in the range of -1 to u, and u is the sequence index for the PRACH sequence.
[0108] For each PRACH opportunity, 64 random access preambles are defined. The random access preambles are the cyclic shifts of the PRACH sequence C v , and a sequence index u for the PRACH sequence. An index may be provided for each of the 64 identified random access preambles.
[0109] The uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not be used to transmit information generated in a higher layer. In addition, the uplink physical signal may be used to transmit information generated in a physical layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical signals may be used. ·UL DMRS(UpLink Demodulation Reference Signal) ·SRS(Sounding Reference Signal) ·UL PTRS(UpLink Phase Tracking Reference Signal)
[0110] UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.
[0111] A set of antenna ports of a DMRS for a PUSCH (a DMRS related to a PUSCH, a DMRS included in a PUSCH, a DMRS corresponding to a PUSCH) may be given based on a set of antenna ports for the PUSCH. For example, the set of antenna ports of a DMRS for a PUSCH may be the same as the set of antenna ports for the PUSCH.
[0112] The transmission of the PUSCH and the transmission of the DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as the PUSCH. Transmitting the PUSCH may be transmitting the PUSCH and the DMRS for the PUSCH.
[0113] The propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.
[0114] The set of antenna ports for DMRS for PUCCH (DMRS related to PUCCH, DMRS included in PUCCH, DMRS corresponding to PUCCH) may be the same as the set of antenna ports for PUCCH.
[0115] The transmission of the PUCCH and the transmission of the DMRS for the PUCCH may be indicated (or triggered) by one DCI format. One or both of the mapping of the PUCCH to resource elements and the mapping of the DMRS for the PUCCH to resource elements may be provided by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting the PUCCH may be transmitting the PUCCH and the DMRS for the PUCCH.
[0116] The propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.
[0117] The downlink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical channels may be used. ·PBCH(Physical Broadcast Channel) ·PDCCH (Physical Downlink Control Channel) ·PDSCH(Physical Downlink Shared Channel)
[0118] PBCH is a MIB (Master Information Block) and physical layer control information. The MIB may be transmitted to convey one or both of the physical layer control information and the MIB. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters arranged in a BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer. The BCCH is arranged in a BCH, which is a channel of the transport layer. The BCH may be arranged (mapped) in a PBCH. The terminal device 1 may receive a PBCH in which the MIB and one or both of the physical layer control information are arranged. The base station device 3 may transmit a PBCH in which the MIB and one or both of the physical layer control information are arranged.
[0119] For example, the physical layer control information may be configured with 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D. 0A) Radio frame bit 0B) Half radio frame (half system frame, half frame) bit 0C) SS / PBCH block index bit 0D) Subcarrier offset bit
[0120] The radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame bits include 4 bits. The radio frame bits may be configured by 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator may be used at least to identify radio frames with index 0 to index 1023.
[0121] The half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of a radio frame in which the PBCH is transmitted. Here, the half radio frame may be configured to include five subframes. Alternatively, the half radio frame may be configured to include the first five subframes of the ten subframes included in the radio frame. Alternatively, the half radio frame may be configured to include the last five subframes of the ten subframes included in the radio frame.
[0122] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include 3 bits. The SS / PBCH block index bits may consist of 3 bits of a 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used at least to identify SS / PBCH blocks with index 0 through index 63.
[0123] The subcarrier offset bit is used to indicate a subcarrier offset, which may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.
[0124] The PDCCH transmits downlink control information (DCI). The downlink control information may be transmitted to the base station apparatus 1 in order to receive the downlink control information. The downlink control information may be arranged in a PDCCH. The terminal apparatus 1 may receive the PDCCH in which the downlink control information is arranged. The base station apparatus 3 may transmit the PDCCH in which the downlink control information is arranged.
[0125] The downlink control information may be transmitted with a DCI format. The DCI format may be interpreted as a format of the downlink control information. The DCI format may be interpreted as a set of downlink control information set to a certain format of the downlink control information.
[0126] DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. The uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.
[0127] DCI format 0_0 is used at least for scheduling a PUSCH arranged in a certain cell. DCI format 0_0 includes at least a part or all of fields 1A to 1E. 1A) Identifier field for DCI formats 1B) Frequency domain resource assignment field field) 1C) Time domain resource assignment field ) 1D) Frequency hopping flag field 1E) MCS field (Modulation and Coding Scheme field)
[0128] The DCI format specification field may indicate whether the DCI format including the DCI format specification field is an uplink DCI format or a downlink DCI format. That is, the DCI format specification field may be included in each of the uplink DCI format and the downlink DCI format. Here, the DCI format specification field included in the DCI format 0_0 may indicate 0.
[0129] The frequency domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of frequency resources for the PUSCH.
[0130] The time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for the PUSCH.
[0131] The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.
[0132] The MCS field included in DCI format 0_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PUSCH. The target coding rate may be a target coding rate for a transport block allocated to the PUSCH. The size of the transport block (TBS: Transport Block Size) allocated to the PUSCH may be determined based on the target coding rate and the target coding rate of the PUSCH. The modulation scheme for the received signal may be determined based on one or both of the modulation schemes.
[0133] DCI format 0_0 may not include fields used for CSI requests.
[0134] DCI format 0_0 may not include a carrier indicator field. That is, a serving cell to which an uplink component carrier in which a PUSCH scheduled by DCI format 0_0 is arranged may be the same as a serving cell of an uplink component carrier in which a PDCCH including the DCI format 0_0 is arranged. Based on detecting DCI format 0_0 in a downlink component carrier of a serving cell, the terminal device 1 may recognize that a PUSCH scheduled by the DCI format 0_0 is arranged in an uplink component carrier of the serving cell.
[0135] The DCI format 0_0 may not include a BWP field. Here, the DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing an active uplink BWP. The terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting the DCI format 0_0 used for scheduling the PUSCH.
[0136] DCI format 0_1 is used at least for scheduling a PUSCH allocated to a certain cell. DCI format 0_1 includes at least a part or all of fields 2A to 2H. 2A) DCI format specific fields 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS Field 2F) CSI request field 2G) BWP field 2H) Carrier indicator field
[0137] The DCI format specific field included in DCI format 0_1 may indicate 0.
[0138] The frequency domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of frequency resources for the PUSCH.
[0139] The time domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of time resources for the PUSCH.
[0140] The MCS field included in DCI format 0_1 may be used to indicate at least some or all of the modulation scheme and / or the target coding rate for the PUSCH.
[0141] The BWP field of the DCI format 0_1 may be used to indicate an uplink BWP in which a PUSCH scheduled by the DCI format 0_1 is arranged. That is, the DCI format 0_1 may involve a change in the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting the DCI format 0_1 used for scheduling the PUSCH.
[0142] The DCI format 0_1 that does not include a BWP field may be a DCI format that schedules a PUSCH without changing an active uplink BWP. The terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting the DCI format D0_1 that is the DCI format 0_1 used for scheduling a PUSCH and does not include a BWP field.
[0143] If the DCI format 0_1 includes a BWP field, but the terminal device 1 does not support the function of switching the BWP by the DCI format 0_1, the BWP field may be ignored by the terminal device 1. That is, the terminal device 1 that does not support the function of switching the BWP may recognize that the PUSCH is transmitted without switching the active uplink BWP based on detecting the DCI format 0_1 that is used for scheduling the PUSCH and includes the BWP field. Here, if the terminal device 1 supports the function of switching the BWP, it may report that "the terminal device 1 supports the function of switching the BWP" in the function information reporting procedure of the RRC layer.
[0144] The CSI request field is used to indicate the reporting of CSI.
[0145] When the DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier on which the PUSCH is arranged. When the DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is arranged may be the same as the uplink component carrier on which the PDCCH including the DCI format 0_1 used for scheduling the PUSCH is arranged. When the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is two or more (when uplink carrier aggregation is operated in a certain serving cell group), the number of bits of the carrier indicator field included in the DCI format 0_1 used for scheduling the PUSCH arranged in the certain serving cell group may be one bit or more (for example, three bits). When the number of uplink component carriers configured in a terminal device 1 in a serving cell group is 1 (when uplink carrier aggregation is not operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 used for scheduling a PUSCH placed in the serving cell group may be 0 bits (or, the carrier indicator field may not be included in DCI format 0_1 used for scheduling a PUSCH placed in the serving cell group).
[0146] DCI format 1_0 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_0 includes at least a part or all of 3A to 3F. 3A) DCI format specific fields 3B) Frequency domain resource allocation field 3C) Time Domain Resource Allocation Field 3D) MCS field 3E) PDSCH_HARQ feedback timing indicator field 3F) PUCCH resource indicator field
[0147] The DCI format specific field included in DCI format 1_0 may indicate 1.
[0148] The frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of frequency resources for the PDSCH.
[0149] The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of time resources for the PDSCH.
[0150] The MCS field included in DCI format 1_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PDSCH. The target coding rate may be a target coding rate for a transport block arranged in the PDSCH. The size of the transport block (TBS) arranged in the PDSCH may be determined based on the target coding rate and the target coding rate of the PDSCH. The modulation scheme for the received signal may be determined based on one or both of the modulation schemes.
[0151] The PDSCH_HARQ feedback timing indication field may be used to indicate an offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.
[0152] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set. A PUCCH resource set may include one or more PUCCH resources.
[0153] DCI format 1_0 may not include a carrier indicator field. That is, a downlink component carrier on which a PDSCH scheduled by DCI format 1_0 is arranged may be the same as a downlink component carrier on which a PDCCH including the DCI format 1_0 is arranged. The terminal device 1 may recognize that a PDSCH scheduled by the DCI format 1_0 is arranged on a downlink component carrier based on detecting DCI format 1_0 in the downlink component carrier.
[0154] The DCI format 1_0 may not include a BWP field. Here, the DCI format 1_0 may be a DCI format for scheduling a PDSCH without changing an active downlink BWP. The terminal device 1 may recognize that the PDSCH is to be received without switching the active downlink BWP based on detecting the DCI format 1_0 used for scheduling the PDSCH.
[0155] DCI format 1_1 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_1 includes at least some or all of 4A to 4I. 4A) DCI format specific fields 4B) Frequency domain resource allocation field 4C) Time Domain Resource Allocation Field 4E) MCS Field 4F) PDSCH_HARQ feedback timing indication field 4G) PUCCH resource indication field 4H) BWP Field 4I) Career Indicator Field
[0156] The DCI format specific field included in DCI format 1_1 may indicate 1.
[0157] The frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of frequency resources for the PDSCH.
[0158] The time domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of time resources for the PDSCH.
[0159] The MCS field included in DCI format 1_1 may be used at least to indicate one or both of the modulation scheme and the target coding rate for the PDSCH.
[0160] If DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field, the PDSCH_HARQ feedback timing indication field may be used at least to indicate an offset from a slot including the last OFDM symbol of the PDSCH to a slot including the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, the offset from a slot including the last OFDM symbol of the PDSCH to a slot including the first OFDM symbol of the PUCCH may be specified by a higher layer parameter.
[0161] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.
[0162] The BWP field of the DCI format 1_1 may be used to indicate a downlink BWP in which a PDSCH scheduled by the DCI format 1_1 is arranged. That is, the DCI format 1_1 may involve a change in the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged based on detecting the DCI format 1_1 used for scheduling the PDSCH.
[0163] The DCI format 1_1 that does not include a BWP field may be a DCI format for scheduling a PDSCH without changing an active downlink BWP. The terminal device 1 detects the DCI format 1_1 that is used for scheduling a PDSCH and does not include a BWP field. Based on this, it may be recognized that the PDSCH is to be received without switching the active downlink BWP.
[0164] If the DCI format 1_1 includes a BWP field, but the terminal device 1 does not support the function of switching the BWP by the DCI format 1_1, the BWP field may be ignored by the terminal device 1. That is, the terminal device 1 that does not support the function of switching the BWP may recognize that the PDSCH is received without switching the active downlink BWP based on detecting the DCI format 1_1 that is used for scheduling the PDSCH and includes the BWP field. Here, if the terminal device 1 supports the function of switching the BWP, it may report that "the terminal device 1 supports the function of switching the BWP" in the function information reporting procedure of the RRC layer.
[0165] When DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate a downlink component carrier on which a PDSCH is arranged. When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which a PDSCH is arranged may be the same as a downlink component carrier on which a PDCCH including a DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink component carriers configured in a terminal device 1 in a certain serving cell group is two or more (when downlink carrier aggregation is operated in a certain serving cell group), the number of bits of the carrier indicator field included in DCI format 1_1 used for scheduling a PDSCH arranged in the certain serving cell group may be one bit or more (for example, three bits). When the number of downlink component carriers configured in a terminal device 1 in a serving cell group is 1 (when downlink carrier aggregation is not operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group).
[0166] The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block delivered by the DL-SCH. The PDSCH may be used to transmit a transport block. The transport block may be arranged in the PDSCH. A transport block corresponding to the DL-SCH may be arranged in the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.
[0167] The downlink physical signal may correspond to a set of resource elements. The downlink physical signal may not carry information generated in a higher layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical signals may be used. ·Synchronization signal (SS) ·DL DMRS(DownLink DeModulation Reference Signal) ·CSI-RS(Channel State Information-Reference Signal) ·DL PTRS(DownLink Phase Tracking Reference Signal)
[0168] The synchronization signal may be used by the terminal device 1 to synchronize one or both of the frequency domain and the time domain of the downlink. The synchronization signal is a general term for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).
[0169] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym), with the vertical axis indicating the frequency domain. Block 700 indicates a set of resource elements for the PSS. Block 720 indicates a set of resource elements for the SSS. Four blocks (blocks 710, 711, 712, and 713) indicate sets of resource elements for the PBCH and DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).
[0170] As shown in FIG. 7, the SS / PBCH block includes a PSS, an SSS, and a PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is arranged in the 57th to 183rd subcarriers of the first OFDM symbol. The SSS is arranged in the 57th to 183rd subcarriers of the third OFDM symbol. The 1st to 56th subcarriers of the first OFDM symbol may be set to zero. The 184th to 240th subcarriers of the first OFDM symbol may be set to zero. The 49th to 56th subcarriers of the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol may be set to zero. The PBCH is arranged in the 1st to 240th subcarriers of the second OFDM symbol, which are subcarriers in which the DMRS for the PBCH is not arranged. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated.
[0171] The antenna ports for the PSS, SSS, PBCH, and DMRS for the PBCH may be the same.
[0172] The PBCH on which a PBCH symbol is transmitted at a certain antenna port may be estimated by the DMRS for the PBCH that is placed in the slot to which the PBCH is mapped and is included in the SS / PBCH block to which the PBCH is included.
[0173] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.
[0174] A set of antenna ports of DMRS for PDSCH (DMRS related to PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) may be given based on the set of antenna ports for the PDSCH, i.e., the set of antenna ports of DMRS for PDSCH may be the same as the set of antenna ports for the PDSCH.
[0175] The transmission of the PDSCH and the transmission of the DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting the PDSCH may be transmitting the PDSCH and the DMRS for the PDSCH.
[0176] A propagation path of a PDSCH may be estimated from a DMRS for the PDSCH. If a set of resource elements on which a symbol of a certain PDSCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH on which a symbol of the PDSCH in a certain antenna port is transmitted may be estimated by the DMRS for the PDSCH.
[0177] The antenna port of the DMRS for the PDCCH (DMRS related to the PDCCH, DMRS included in the PDCCH, DMRS corresponding to the PDCCH) may be the same as the antenna port for the PDCCH.
[0178] A PDCCH may be estimated from a DMRS for the PDCCH. That is, a propagation path of a PDCCH may be estimated from a DMRS for the PDCCH. If the same precoder is applied (assumed to be applied, assumed to be applied) to a set of resource elements on which a symbol of a certain PDCCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDCCH is transmitted, a PDCCH on which a symbol of the PDCCH in a certain antenna port is transmitted may be estimated by the DMRS for the PDCCH.
[0179] The BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels. A port channel defines the relationship between a physical layer channel and a MAC layer channel (also called a logical channel).
[0180] The BCH of the transport layer is mapped to the PBCH of the physical layer, i.e., the transport block carried by the BCH of the transport layer is delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer, i.e., the transport block carried by the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer, i.e., the transport block carried by the DL-SCH of the transport layer is delivered to the PDSCH of the physical layer.
[0181] For each serving cell, one UL-SCH and one DL-SCH may be provided. The BCH may be provided for the PCell. The BCH does not have to be provided for the PSCell or SCell.
[0182] In the MAC layer, hybrid automatic repeat reQuest (HARQ) control is performed for each transport block.
[0183] BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), And DCCH (Dedicated Control CHannel) is a logical channel. For example, The BCCH is a channel of the RRC layer used to transmit the MIB or system information. Also, the CCCH (Common Control CHannel) may be used to transmit an RRC message common to a plurality of terminal devices 1. Here, the CCCH is, for example, For example, the DCCH may be used for a terminal device 1 that is not RRC connected. Furthermore, the DCCH (Dedicated Control CHannel) may be used at least for transmitting an RRC message dedicated to the terminal device 1. Here, the DCCH may be used for, for example, a terminal device 1 that is RRC connected.
[0184] The upper layer parameters common to a plurality of terminal devices 1 are also referred to as common upper layer parameters. Here, the common upper layer parameters may be defined as parameters specific to a serving cell. Here, the parameters specific to a serving cell may be parameters common to terminal devices (e.g., terminal devices 1-A, B, and C) in which the serving cell is set.
[0185] For example, the common upper layer parameters may be included in an RRC message delivered on the BCCH. For example, the common upper layer parameters may be included in an RRC message delivered on the DCCH.
[0186] Among certain upper layer parameters, upper layer parameters different from the common upper layer parameters are also called dedicated upper layer parameters. Here, the dedicated upper layer parameters can provide dedicated RRC parameters to the terminal device 1-A in which the serving cell is set. In other words, the dedicated RRC parameters are upper layer parameters that can provide unique settings for each of the terminal devices 1-A, B, and C.
[0187] The BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block including MIB information is delivered to the BCH of the transport layer. A transport block including system information other than MIB is delivered to the DL-SCH of the transport layer. A CCCH is mapped to the DL-SCH or UL-SCH. That is, a transport block mapped to a CCCH is delivered to the DL-SCH or UL-SCH. A DCCH is mapped to the DL-SCH or UL-SCH. That is, a transport block mapped to a DCCH is delivered to the DL-SCH or UL-SCH.
[0188] The RRC message includes one or more parameters managed in the RRC layer. Here, the parameters managed in the RRC layer are also referred to as RRC parameters. For example, the RRC message may include an MIB. The RRC message may also include system information. The RRC message may also include a message corresponding to a CCCH. The RRC message may also include a message corresponding to a DCCH. The RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.
[0189] The upper layer parameters are RRC parameters or parameters included in a Medium Access Control Element (MAC CE). The upper layer parameters are a general term for the parameters included in the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and MAC CE. The parameters included in MAC CE are sent by the MAC CE (Control Element) command. It is believed.
[0190] The procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C. 5A) Cell search 5B) Random access 5C) Data communication
[0191] The cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in terms of the time domain and the frequency domain and detect a physical cell identity. That is, the terminal device 1 may perform the cell search to synchronize with a certain cell in terms of the time domain and the frequency domain and detect a physical cell ID.
[0192] The sequence of the PSS is based at least on the physical cell ID. The sequence of the SSS is based at least on the physical cell ID.
[0193] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH block is permitted (possible, reserved, configured, defined, possible).
[0194] A set of SS / PBCH block candidates in a half radio frame is also called an SS burst set. The SS burst set is also called a transmission window, an SS transmission window, or a Discovery Reference Signal transmission window (DRS transmission window). The SS burst set is a general term including at least the first SS burst set and the second SS burst set.
[0195] The base station device 3 transmits SS / PBCH blocks of one or more indexes at a predetermined period. The terminal device 1 may detect at least one of the SS / PBCH blocks of the one or more indexes and attempt to decode the PBCH included in the SS / PBCH block.
[0196] Random access is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.
[0197] Message 1 is a procedure for transmitting a PRACH by a terminal device 1. The terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based on at least an index of an SS / PBCH block candidate detected based on a cell search. Each of the PRACH opportunities is defined based on at least resources in the time domain and the frequency domain.
[0198] The terminal device 1 transmits one random access preamble selected from among the PRACH opportunities corresponding to the index of the SS / PBCH block candidate from which the SS / PBCH block is detected.
[0199] Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including the DCI format in a control resource set given based on an MIB included in a PBCH included in an SS / PBCH block detected based on a cell search, and in resources indicated based on the setting of a search space set. Message 2 is also called a random access response.
[0200] Message 3 is a procedure for transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected by the procedure for message 2. Here, the random access response grant is indicated by a MAC CE included in a PDSCH scheduled by the DCI format 1_0.
[0201] The PUSCH scheduled based on the random access response grant is either a message 3 PUSCH or a PUSCH. The message 3 PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier (MAC CE) includes a contention resolution ID.
[0202] Message 3 PUSCH retransmissions are scheduled with DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).
[0203] Message 4 is the C-RNTI (Cell - Radio Network Temporary Identifier), or TC-RNTI. The terminal device 1 receives a PDSCH scheduled based on the DCI format 1_0. The PDSCH may include a collision resolution ID.
[0204] Data communication is a general term for downlink communication and uplink communication.
[0205] In data communication, the terminal device 1 attempts to detect the PDCCH in resources specified based on the control resource set and the search space set (monitors the PDCCH).
[0206] A control resource set is a set of resources consisting of a certain number of resource blocks and a certain number of OFDM symbols. In the frequency domain, a control resource set may consist of continuous resources (non-interleaved mapping) or distributed resources. The interleaver mapping may be implemented by using a
[0207] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter. The number of OFDM symbols constituting the control resource set may be indicated by a higher layer parameter.
[0208] The terminal device 1 attempts to detect a PDCCH in a search space set. Here, attempting to detect a PDCCH in a search space set may be attempting to detect a PDCCH candidate in a search space set, may be attempting to detect a DCI format in a search space set, may be attempting to detect a PDCCH in a control resource set, may be attempting to detect a PDCCH candidate in a control resource set, or may be attempting to detect a DCI format in a control resource set.
[0209] The search space set is defined as a set of PDCCH candidates. The search space set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. The terminal device 1 selects a type 0 PDCCH common search space set (Type0 PDCCH common search space set), Type 0a PDCCH common search space set The UE attempts to detect PDCCH candidates in some or all of the Type0a PDCCH common search space set, the Type1 PDCCH common search space set, the Type2 PDCCH common search space set, the Type3 PDCCH common search space set, and / or the UE-specific search space set.
[0210] The type 0 PDCCH common search space set is the 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.
[0211] The CSS set is a collective term for a type 0 PDCCH common search space set, a type 0a PDCCH common search space set, a type 1 PDCCH common search space set, a type 2 PDCCH common search space set, and a type 3 PDCCH common search space set. The USS set is also called a UE dedicated PDCCH search space set.
[0212] A search space set is associated with (contains, corresponds to) a control resource set. The index of the control resource set associated with the search space set may be indicated by a higher layer parameter.
[0213] For a given search area set, some or all of 6A to 6C may be indicated by at least higher layer parameters. 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 6C) PDCCH monitoring offset
[0214] A monitoring occasion for a certain search area set is defined as a monitoring occasion for the certain search area set. The monitoring opportunity for a search space set may correspond to an OFDM symbol in which a first OFDM symbol of an associated control resource set is located. The monitoring opportunity for a search space set may correspond to a resource of a control resource set starting from a first OFDM symbol of the control resource set associated with the search space set. The monitoring opportunity for the search space set is given based on at least some or all of a PDCCH monitoring interval, a PDCCH monitoring pattern in a slot, and a PDCCH monitoring offset.
[0215] 8 is a diagram showing an example of a monitoring opportunity of the search area set according to one aspect of the present embodiment. In FIG. 8, a search area set 91 and a search area set 92 are set in a primary cell 301, a search area set 93 is set in a secondary cell 302, and a search area set 94 is set in a secondary cell 303.
[0216] In Figure 8, the solid white blocks in primary cell 301 indicate search area set 91, the solid black blocks in primary cell 301 indicate search area set 92, the blocks in secondary cell 302 indicate search area set 93, and the blocks in secondary cell 303 indicate search area set 94.
[0217] The monitoring interval of the search area set 91 is set to 1 slot, and the monitoring The offset is set to 0 slot, and the monitoring pattern of the search area set 91 is [1,0 ,0,0,0,0,0,1,0,0,0,0,0,0,0]. The monitoring opportunities for search region set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each of the slots.
[0218] The monitoring interval of the search area set 92 is set to 2 slots, the monitoring offset of the search area set 92 is set to 0 slots, and the monitoring pattern of the search area set 92 is [1,0 ,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. The monitoring opportunity for search region set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.
[0219] The monitoring interval of the search area set 93 is set to 2 slots, the monitoring offset of the search area set 93 is set to 0 slots, and the monitoring pattern of the search area set 93 is [0,0 ,0,0,0,0,0,1,0,0,0,0,0,0,0]. The monitoring opportunity for search region set 93 corresponds to the eighth OFDM symbol (OFDM symbol #7) in each of the even slots.
[0220] The monitoring interval of the search area set 94 is set to 2 slots, the monitoring offset of the search area set 94 is set to 1 slot, and the monitoring pattern of the search area set 94 is [1,0 ,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. The monitoring opportunity for search region set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.
[0221] The Type 0 PDCCH common search space set may be used at least for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).
[0222] The Type 0a PDCCH common search space set may be used at least for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).
[0223] The Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and / or a CRC sequence scrambled by a Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).
[0224] A Type 2 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by a Paging-Radio Network Temporary Identifier (P-RNTI).
[0225] A Type 3 PDCCH common search space set may be used for a DCI format with a CRC sequence scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI).
[0226] The UE dedicated PDCCH search space set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.
[0227] In downlink communication, the terminal device 1 detects a downlink DCI format. The detected downlink DCI format is used at least for resource allocation of the PDSCH. The detected downlink DCI format is also called a downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, the terminal device 1 reports a HARQ-ACK corresponding to the PDSCH (a HARQ-ACK corresponding to a transport block included in the PDSCH) to the base station device 3.
[0228] In uplink communication, the terminal device 1 detects an uplink DCI format. The detected DCI format is used at least for resource allocation of a PUSCH. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.
[0229] In configured scheduling, an uplink grant for scheduling a PUSCH is configured for each transmission period of the PUSCH. When a PUSCH is scheduled by an uplink DCI format, part or all of the information indicated by the uplink DCI format may be indicated by an uplink grant configured in the case of configured scheduling.
[0230] Repetition transmission may be applied for the message 3 PUSCH. For example, the number of repetitions of the message 3 PUSCH scheduled by DCI format 0_0 with CRC scrambled based on the TC-RNTI may be determined based at least on the DCI format 0_0. For example, the number of repetitions of the message 3 PUSCH scheduled by a random access response grant may be determined based at least on the random access response grant. The number of repetitions may be the number of slots.
[0231] For example, the number of repetitions for message 3 PUSCH may be determined based at least on any of a first field, a second field, and a third field included in any of DCI format 0_0 and a random access response grant. The first field may be a time domain resource allocation field. The second field may be an MCS field. The third field may be a Transmission Power Control (TPC) command field.
[0232] It may be instructed to perform frequency hopping for a message 3 PUSCH to which repetitive transmission is applied. For example, the frequency hopping scheme corresponding to the frequency hopping may be inter-slot frequency hopping. Also, it may be instructed to perform frequency hopping for a message 3 PUSCH to which repetitive transmission is not applied. For example, the frequency hopping scheme corresponding to the frequency hopping may be intra-slot frequency hopping.
[0233] The medium access control layer processing unit 15 may implement a random access procedure. The random access procedure may be either a four-step random access procedure or a two-step random access procedure.
[0234] If the media access control layer processing unit 15 selects the four-step random access procedure, the media access control layer processing unit 15 may perform one or both of the following: random access preamble group selection and PRACH resource group selection.
[0235] The random access preamble group may be either the random access preamble group A or the random access preamble group B. The media access control layer processing unit 15 may select the random access preamble group based at least on the upper layer parameter ra-Msg3SizeGroupA. The ra-Msg3SizeGroupA may indicate a TBS threshold, and when transmitting a message 3 PUSCH including a TB smaller than the TBS threshold, the random access preamble group A may be selected.
[0236] One PRACH resource group may consist of one or more PRACH resources, and one PRACH resource group may consist of one or more PRACH opportunities.
[0237] The terminal device 1 requests application of repeated transmission to the PUSCH in message 3. The base station apparatus 3 may be notified of information indicating whether or not the PUSCH is to be repeated using the PRACH transmitted during the random access procedure. For example, the PRACH transmitted based on the first PRACH resource group may correspond to a request to apply the repetitive transmission to the message 3 PUSCH. Also, the PRACH transmitted based on the second PRACH resource group may correspond to not requesting to apply the repetitive transmission to the message 3 PUSCH.
[0238] That is, when the media access control layer processing unit 15 requests the application of repetitive transmission to the message 3 PUSCH, the media access control layer processing unit 15 may select the first PRACH resource group. Also, when the media access control layer processing unit 15 does not request the application of repetitive transmission to the message 3 PUSCH, the media access control layer processing unit 15 may select the second PRACH resource group.
[0239] In the random access procedure, whether or not the media access control layer processing unit 15 requests the application of repetitive transmission to the message 3 PUSCH may be determined based on one or both of a value of a reference signal received power (RSRP) of a downlink path loss reference and whether or not a random access preamble group B is configured for the first PRACH resource group. The media access control layer processing unit 15 may select a four-step random access procedure involving requesting the application of repetitive transmission to the message 3 PUSCH.
[0240] The downlink path loss reference may be either an SS / PBCH block or a CSI-RS, or may be an SS / PBCH block selected in a random access procedure.
[0241] The base station device 3 receives a message 2 based on the presence or absence of a request from the terminal device 1. Information included in the PDSCH (random access response grant) may be set.
[0242] When the reception of the message 2 is successfully completed, the media access control layer processing unit 15 may process the uplink grant (random access response grant) included in the random access response. In the process of the uplink grant, the physical layer processing unit 10 may be instructed to transmit the message 3 PUSCH.
[0243] PUSCH-Config may be a dedicated upper layer parameter. PUSCH-ConfigCommon may be a common upper layer parameter. PUSCH-Config may be set for each BWP for PUSCH transmission. PUSCH-Config may include a plurality of upper layer parameters related to PUSCH transmission. PUSCH-Config may be a UE-specific setting. For example, PUSCH-Config for the terminal device 1A, the terminal device 1B, and the terminal device 1C in one cell, or a plurality of upper layer parameters included in the PUSCH-Config may be different. PUSCH-ConfigCommon may be set for each BWP for PUSCH transmission. PUSCH-ConfigCommon may include a plurality of upper layer parameters related to PUSCH transmission. PUSCH-ConfigCommon may be a cell-specific setting. For example, PUSCH-ConfigCommon for the terminal device 1A, the terminal device 1B, and the terminal device 1C in one cell may be common. For example, PUSCH-ConfigCommon may be given by system information.
[0244] Repeated transmission is applied to PUSCH scheduled by DCI. In addition, repetition transmission may be applied to the PUSCH scheduled by the configured uplink grant. The PUSCH repetition type may be either PUSCH repetition type A or PUSCH repetition type B. The PUSCH repetition type may be configured by a higher layer parameter. The PUSCH repetition type may be based on the DCI format. For example, a first PUSCH repetition type for a PUSCH scheduled by DCI format 0_1 may be different from a second PUSCH repetition type for a PUSCH scheduled by DCI format 0_2.
[0245] The higher layer parameter numberOfRepetitions may be a parameter indicating the number of repetitions for PUSCH repetition transmission. In PUSCH repetition transmission corresponding to PUSCH repetition type A, the number of repetitions for the PUSCH repetition transmission may be determined by the value of the higher layer parameter numberOfRepetitions. In PUSCH repetition type A, the number of repetitions of the PUSCH, the transmission of which is indicated by the DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, may be equal to numberOfRepetitions in the resource allocation table, if numberOfRepetitions is present. In the case where one PUSCH-Time Domain Resource Allocation includes one or more PUSCH-Allocations, the higher layer parameter numberOfRepetitions may be set for each PUSCH-Allocation. In addition, the PUSCH-Time Domain Resource Allocation may be referred to as a resource allocation table.
[0246] The upper layer parameter pusch-AggregationFactor may be a parameter indicating the number of repetitions for PUSCH repetition transmission. In PUSCH repetition transmission corresponding to PUSCH repetition type A, the number of repetitions for the PUSCH repetition transmission may be determined by the value of the upper layer parameter pusch-AggregationFactor. In PUSCH repetition type A, the number of repetitions of the PUSCH, the transmission of which is instructed by the DCI format with the CRC scrambled by the C-RNTI and any of the MCS-C-RNTI and CS-RNTI, may be equal to the pusch-AggregationFactor when the pusch-AggregationFactor is set. The pusch-AggregationFactor may be set for the PUSCH-Config.
[0247] The number of repetitions corresponding to PUSCH repetition type A may be the number of slots for PUSCH repeated transmission. Also, one TB may be repeated in one or more slots. PUSCH repetitions transmitted in different slots may be subject to the same OFDM symbol allocation.
[0248] PUSCH repetition transmission corresponding to PUSCH repetition type B may be based on nominal repetition and actual repetition.
[0249] The higher layer parameters frequencyHopping, frequencyHoppingDCI-0-1, and frequencyHoppingDCI-0-2 may be parameters indicating a frequency hopping scheme for PUSCH. For example, a frequency hopping scheme corresponding to the frequency hopping for PUSCH may be set by frequencyHoppingDCI-0-2 in PUSCH-Config. Thus, a frequency hopping scheme corresponding to the frequency hopping for PUSCH may be set. Also, a frequency hopping scheme corresponding to the frequency hopping for PUSCH transmission set by frequencyHopping in configuredGrantConfig may be set. The frequency hopping scheme may be any of intra-slot frequency hopping, inter-slot frequency hopping, inter-repetition frequency hopping, and inter-bundle frequency hopping. Also, the frequency hopping interval corresponding to intra-slot frequency hopping may be within one slot. The frequency hopping interval corresponding to inter-slot frequency hopping may be one slot. The frequency hopping interval corresponding to inter-repetition frequency hopping may be based on nominal repetition. The frequency hopping interval corresponding to inter-bundle frequency hopping may be one or more slots. A bundle may be a time unit consisting of multiple slots. A bundle may be the number of slots corresponding to the frequency hopping interval.
[0250] For example, if a first higher layer parameter indicating a frequency hopping scheme for the PUSCH indicates inter-slot frequency hopping and a bundle is provided by a second higher layer parameter, inter-bundle frequency hopping may be applied to the PUSCH. For example, if the higher layer parameter indicating a frequency hopping scheme for the PUSCH indicates inter-bundle frequency hopping, inter-bundle frequency hopping may be applied to the PUSCH.
[0251] For example, the bundle may be provided by a higher layer parameter. For example, if the higher layer parameter indicates N, a bundle of N slots may be provided for the PUSCH to which inter-bundle frequency hopping is applied. The N may be an integer greater than 1. For example, if the higher layer parameter includes one value, the one value may be provided for one or both of the PUSCH to which inter-bundle frequency hopping is applied and the PUCCH. The one value may be an integer greater than 1. The one value may also be a window length of a time domain window to be set.
[0252] Whether to perform frequency hopping for a PUSCH whose transmission is instructed by the DCI format may be determined based at least on a value of a frequency hopping flag field included in a DCI format. Whether to perform frequency hopping for a PUSCH whose transmission is instructed by the random access response grant may be determined based at least on a value of a frequency hopping flag field included in a random access response grant. For example, frequency hopping for a PUSCH may be performed based at least on the value of the frequency hopping flag field being 1.
[0253] Intra-slot frequency hopping may be applied to PUSCH transmission in one or more slots. For example, intra-slot frequency hopping may be applied to PUSCH repeated transmission. For a PUSCH to which intra-slot frequency hopping is applied, the allocation of resource blocks may be switched for every one or more OFDM symbols. For example, for a PUSCH to which intra-slot frequency hopping is applied, the allocation of resource blocks may be the first hop or the second hop for every one or more OFDM symbols. In addition, when intra-slot frequency hopping is performed for the PUSCH, the first hop and the second hop may be switched every one or more OFDM symbols. The difference between the position of the first resource block of the first hop and the position of the first resource block of the second hop is RB offset RB offset may be set by a higher layer parameter. The one or more OFDM symbols may be within one slot. The one or more OFDM symbols may be The number of OFDM symbols for the PUSCH in one slot may be half. Intra-slot frequency hopping may be applied to the PUSCH corresponding to PUSCH repetition type A.
[0254] Inter-slot frequency hopping may be applied to PUSCH transmission in multiple slots. For PUSCH to which inter-slot frequency hopping is applied, the allocation of resource blocks may be switched for each slot. For example, inter-slot frequency hopping may be applied to PUSCH repeated transmission. Also, when inter-slot frequency hopping is performed for PUSCH, the allocation of resource blocks may be switched between the first hop and the second hop for each slot. For example, in a certain slot, slot index n μ s,f If n is an even number, the PUSCH transmission in a certain slot may correspond to the first hop. For example, in a certain slot, slot index n μ s,f If , the PUSCH transmission in a slot may correspond to a second hop. Inter-slot frequency hopping may be applied to a PUSCH corresponding to either PUSCH repetition type A or PUSCH repetition type B.
[0255] Inter-repetition frequency hopping may be applied to a PUSCH corresponding to PUSCH repetition type B. For a PUSCH to which inter-repetition frequency hopping is applied, the first hop and the second hop may be switched based on the nominal repetition.
[0256] Inter-bundle frequency hopping may be applied to PUSCH transmission in multiple slots. For example, inter-bundle frequency hopping may be applied to PUSCH repetition transmission. For PUSCH to which inter-bundle frequency hopping is applied, the arrangement of resource blocks may be switched for each bundle. Also, when inter-bundle frequency hopping is performed for PUSCH, the arrangement of resource blocks may be switched between the first hop and the second hop for each bundle. A bundle may be one or more slots. For example, a bundle may be determined by a higher layer parameter. For example, a bundle may be determined based on the number of repetitions. For example, a bundle may be composed of consecutive UL slots. For example, a bundle may be composed of a special slot and a UL slot. Inter-bundle frequency hopping may be applied to PUSCH corresponding to either PUSCH repetition type A or PUSCH repetition type B.
[0257] The UL slot may be a slot consisting of UL symbols. The special slot may be a slot consisting of UL symbols, flexible symbols, and DL symbols. The DL slot may be a slot consisting of DL symbols.
[0258] The UL symbol may be an OFDM symbol configured or indicated for the uplink in time division duplex. The UL symbol may be an OFDM symbol configured or indicated for the PUSCH, PUCCH, PRACH, or SRS. The UL symbol may be configured by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbol may be configured by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The UL slot may be configured by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL slot may be configured by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.
[0259] The DL symbol is a symbol that is configured or indicated for the downlink in time division duplex. The DL symbol may be an FDM symbol. The DL symbol may be an OFDM symbol configured or indicated for a PDSCH or a PDCCH. The DL symbol may be configured by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may be configured by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The DL slot may be configured by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL slot may be configured by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.
[0260] The flexible symbols may be OFDM symbols that are not configured or indicated as UL symbols or DL symbols among OFDM symbols in a certain period, which may be a period given by a higher layer parameter dl-UL-TransmissionPeriodicity. The flexible symbols may be OFDM symbols that are configured or indicated for PDSCH, PDCCH, PUSCH, PUCCH, or PRACH.
[0261] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter for setting a UL slot, a DL slot, or a special slot for each of one or more slots. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter for setting a UL symbol, a DL symbol, or a flexible symbol for each of the one or more slots. The tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. The tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.
[0262] The time domain window may indicate a time domain period. For example, the time domain window may be used for DMRS bundling. The terminal device 1 performing DMRS bundling may enable channel estimation using DMRS included in two or more PUSCHs in a period based on the time domain window. The terminal device 1 performing DMRS bundling may be expected to maintain one or both of phase continuity and power consistency between two PUSCHs in a period based on the time domain window. DMRS bundling may be referred to as joint channel estimation.
[0263] The time domain window may be a general term for a configured time domain window and an actual time domain window.
[0264] The configured time domain window may be composed of one or more consecutive slots. The configured time domain window may be configured by one or more higher layer parameters. For example, the one or more higher layer parameters may include one or more parameters that can enable the configured time domain window. For example, the one or more higher layer parameters may include one or more parameters that indicate a length of the configured time domain window. The length of the configured time domain window may be referred to as a window length. The configured time domain window may be composed of slots corresponding to the window length. The start position of the configured time domain window may be determined based on the first PUSCH of the PUSCH repeat transmission. For example, the start position of the configured time domain window may be the first slot of the PUSCH repeat transmission. For example, the start position of the configured time domain window may be determined based on the first PUSCH of the PUSCH repeat transmission. The start position of the time domain window may be the first slot in which a PUSCH to which PUSCH repetition type A is applied is transmitted. For example, the start position of the set time domain window may be the slot corresponding to the first transmission opportunity for a PUSCH to which PUSCH repetition type A is applied.
[0265] The window length may be determined based on a bundle. For example, the window length may be a bundle. For example, the window length may be used as a bundle for inter-bundle frequency hopping. For example, either the first hop or the second hop may correspond to a plurality of PUSCH transmissions in the set time domain window. The set time domain window and a part or both of the window length may be used for precoding. For example, the precoding applied to a plurality of PUSCH transmissions in the set time domain window may be the same. The set time domain window and a part or both of the window length may be used for terminal adjustment of the terminal device 1. For example, in the set time domain window, it is not necessary to correct a frequency synchronization error. For example, in the set time domain window, it is not necessary to correct a time timing synchronization error. For example, in the set time domain window, it is not necessary to make an adjustment related to the virtualization of an antenna. For example, in the set time domain window, it is not necessary to make an adjustment of an analog circuit controlled by a digital signal. For example, in the set time domain window, it is not necessary to make an adjustment of a high-frequency circuit. The adjustment of the high frequency circuit may include some or all of the following: changing the operating point of the power amplifier, changing the gain of the power amplifier, phase synchronization of the oscillator, phase adjustment of the two carrier waves, phase adjustment of the phase shifter, and stopping the power supply to the high frequency circuit.
[0266] The window length may have a maximum period determined. For example, the maximum period may be reported by the terminal device 1 to the base station device 3. For example, the maximum period may be the number of repetitions.
[0267] One or more window lengths may be configured in PUSCH-Config. Also, one or more window lengths may be configured in PUSCH-ConfigCommon. For example, one of the one or more window lengths may be determined based on a DCI format. For example, one of the one or more window lengths may be determined based on a time domain resource allocation field included in the DCI.
[0268] In Frequency Division Duplex, two or more configured time domain windows may be contiguous, for example, the last slot in a first configured time domain window may be contiguous with the first slot in a second configured time domain window.
[0269] In time division duplex, two or more configured time domain windows may be consecutive. Also, in time division duplex, two or more configured time domain windows may not be consecutive. For example, the start position of the configured time domain window may be determined based on at least one or both of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated. For example, the start position of the configured time domain window may not include a DL slot.
[0270] A first configured time domain window of the one or more configured time domain windows may end just before a DL slot. The time domain windows that are set except for the first set time domain among the domain windows may be aligned with the period given by dl-UL-TransmissionPeriodicity.
[0271] The configured time domain window may end based on a certain slot index. For example, n μ s,fIf is the first value, then μ s,f The configured time domain window may end at the end of a slot corresponding to n. The configured time domain window may be applied to a PUSCH transmitted in the slot. The first value may be 0. The first value may be configured by a higher layer parameter. The first value may be determined based on a certain period. For example, the certain period may be used for processing performed every certain period. The certain period may be an integer multiple of a window length of the configured time domain window. The first value may be determined by the certain period and an offset. Also, n μ s,f If is the second value, then μ s,f The time domain window may end at the end of the slot corresponding to the first value. The difference between the first value and the second value may be the certain period.
[0272] The last configured time domain window of the one or more configured time domain windows may end in a slot corresponding to the last PUSCH in the PUSCH repeated transmission.
[0273] One or more actual time domain windows may be determined in the configured time domain window. The multiple actual time domain windows may not be contiguous with each other. The terminal device 1 may be expected to maintain phase continuity and power consistency in the actual time domain window. The actual time domain window may consist of one or more slots. Also, the actual time domain window may consist of one or more OFDM symbols.
[0274] The actual time domain window may be determined based on events occurring within the configured time domain window. The actual time domain window may be determined based on slots or OFDM symbols corresponding to events in the configured time domain window. The actual time domain window may not include slots or OFDM symbols corresponding to events in the configured time domain window. For example, the events may include reception of a downlink physical channel and some or all of transmission of a high priority channel, slot format indication, frequency hopping, and cancellation indication.
[0275] For example, the slot or OFDM symbol corresponding to the event may be a slot or OFDM symbol where PUSCH repeated transmission is cancelled. For example, the slot corresponding to the event may be a DL slot. For example, the slot or OFDM symbol corresponding to the event may be a slot or OFDM symbol including a DL reception opportunity. For example, the slot or OFDM symbol corresponding to the event may be a slot or OFDM symbol where a high priority channel is transmitted. For example, the slot corresponding to the event may be a slot indicated as a DL slot or a special slot by the slot format indication. For example, the OFDM symbol corresponding to the event may be an OFDM symbol indicated as a DL symbol or a flexible symbol by the slot format indication. For example, the slot corresponding to the event may be the n-th slot associated with the second hop when the n-1-th slot is associated with the first hop. For example, the slot corresponding to the event may be the n-th slot associated with the first hop when the n-1-th slot is associated with the second hop. For example, the OFDM symbol corresponding to an event may be the nth OFDM symbol associated with the second hop when the n-1th OFDM symbol is associated with the first hop. For example, the OFDM symbol corresponding to an event may be the nth OFDM symbol associated with the first hop when the n-1th slot is associated with the second hop.
[0276] The actual time domain window may include OFDM symbols in which the PUSCH is not transmitted. For example, the actual time domain window may include 13 consecutive OFDM symbols, and the terminal device 1 may not transmit an uplink physical channel and an uplink physical signal in the 13 consecutive OFDM symbols.
[0277] The terminal device 1 may maintain phase continuity and transmission power consistency within an actual time domain window based on requirements for phase continuity and transmission power consistency. For example, in the actual time domain window, an uplink physical channel and two OFDM symbols on which an uplink physical signal is transmitted may correspond to the same antenna port. For example, the terminal device 1 may determine whether to transmit a first channel on which a symbol at an antenna port is transmitted so that the first channel can be estimated from a second channel on which other symbols at the antenna port are transmitted based on whether the first channel and the second channel are included in an actual time domain window. For example, when the first channel and the second channel are included in the actual time domain window, the terminal device 1 may transmit a first channel on which a symbol at an antenna port is transmitted so that the first channel can be estimated from the second channel on which other symbols at the antenna port are transmitted. Also, when the first channel and the second channel are not included in the certain actual time domain window, the terminal device 1 may not transmit the first channel through which the symbol at the certain antenna port is transmitted so that the first channel can be estimated from the second channel through which the other symbol at the certain antenna port is transmitted. Here, the first channel may be different from the second channel. Or, the first channel may be the same as the second channel. Also, the first channel may be a repetition of a third channel, and the second channel may be another repetition of the third channel. For example, the terminal device 1 may not change a parameter related to precoding for PUCCH and / or PUSCH in the actual time domain window. For example, the parameter related to precoding may be a precoding matrix for spatial multiplexing. Also, the parameter related to precoding may be an upper layer parameter txConfig. Also, the parameter related to precoding may be a TPMI (Transmitted Precoding Matrix Indicator).The TPMI may be given by a DCI format. Also, the parameter related to the precoding may be an SRS Resource Indicator (SRI). Also, the terminal device 1 may apply one precoding to the repetition of PUSCH in the actual time domain window. For example, power control may be performed for the first PUSCH in the actual time domain window. Also, power control may not be performed for one or more PUSCHs other than the first PUSCH in the actual time domain window. For example, a value of the TPC command field may be applied for the first PUSCH in the actual time domain window. Also, a value of the TPC command field may not be applied for one or more PUSCHs other than the first PUSCH in the actual time domain window. The TPC command field for PUSCH may be included in DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 2_2, DCI format 2_3, and part or all of the random access response grant. Also, the terminal device 1 may not perform frequency hopping for the repetition of PUSCH in the actual time domain window. Not performing the frequency hopping may mean that the repetition of the PUCCH in the actual time domain window is arranged at least in either the first hop or the second hop. The terminal device 1 may not perform beam switching on the PUSCH in the actual time domain window. The terminal device 1 may not change the setting of the modulation scheme for PUSCH transmission and the modulation order in the actual time domain window. The terminal device 1 may not change the index of the first resource block for PUSCH transmission and the number of resource blocks in the actual time domain window. One or more PUSCHs in the actual time domain window may correspond to the same time domain resource allocation. One or more PUSCHs in the actual time domain window may be applied with the same precoding.In addition, the same transmission power control may be applied to one or more PUSCHs in the actual time domain window. In addition, one or more PUSCHs in the actual time domain window may be at least arranged in the same resource block. In addition, between two non-consecutive PUSCHs in the actual time domain window, the terminal device 1 may transmit a baseband signal with an amplitude of 0.
[0278] 9 is a diagram showing an example of a time domain window set and an actual time domain window according to one embodiment of the present invention. In an uplink BWP in an uplink carrier, the terminal device 1 transmits a PUSCH 920 in a slot 910, a PUSCH 921 in a slot 911, a PUSCH 922 in a slot 912, a PUSCH 923 in a slot 913, a PUSCH 924 in a slot 914, a PUSCH 925 in a slot 915, and a PUSCH 927 in a slot 917. The PUSCH 920, the PUSCH 921, the PUSCH 922, and the PUSCH 923 are PUSCHs that start from a PRB 900. The PRB 900 may be the first hop. The PUSCH 924, the PUSCH 925, the PUSCH 926, and the PUSCH 927 start from a PRB 901. PRB 901 may be a second hop and may be different from PRB 900. PUSCH 920, PUSCH 921, PUSCH 922, PUSCH 923, PUSCH 924, PUSCH 925, PUSCH 926, and PUSCH 927 may be frequency hopped. PUSCH 926 may not be transmitted in slot 916. For example, PUSCH 926 may overlap with a high priority uplink channel. For example, the transmission of PUSCH 926 may be indicated to be canceled. For example, slot 916 may be a slot corresponding to an event.
[0279] 9, configured time domain window 930 includes PUSCH 920, PUSCH 921, PUSCH 922, and PUSCH 923. Configured time domain window 931 includes PUSCH 924, PUSCH 925, PUSCH 926, and PUSCH 927. Actual time domain window 940 may consist of slots or OFDM symbols included in configured time domain window 930. For example, actual time domain window 940 may be the same length as configured time domain window 930. Configured time domain window 931 may include actual time domain window 941 and actual time domain window 942. Time domain window 941 and actual time domain window 942 may not include PUSCH 926.
[0280] PUSCH 920, PUSCH 921, PUSCH 922, PUSCH 923, PUSCH 924, PUSCH 925, PUSCH 926, and PUSCH 927 may be PUSCH repeat transmissions. For example, the number of repetitions corresponding to the PUSCH repeat transmissions in FIG. 9 may be 8. For example, the PUSCH repeat transmissions in FIG. 9 may correspond to PUSCH repetition type A. PUSCH 926 may be dropped. The PUSCH repeats in FIG. 9 may be message 3 PUSCH repeat transmissions.
[0281] The frequency hopping in FIG. 9 may be inter-bundle frequency hopping. For example, the bundle may be 4 slots. For example, the bundle may be the same as the length of the configured time domain window 930. For example, the bundle may be the same as the length of the configured time domain window 931. The configured time domain window 930 may be configured by a higher layer parameter as a window length. The configured time domain window 931 may be configured by a higher layer parameter as a window length. The bundle may be configured by a higher layer parameter. For example, the bundle may be provided by a higher layer parameter including one value. For example, in FIG. 9, the one value may be 4. For example, if the one value is 8, the bundle may be composed of slot 910, slot 911, slot 912, slot 913, slot 914, slot 915, slot 916, and slot 917.
[0282] As a problem 1, a terminal device 1 that does not have a function of performing DMRS bundling for a message 3 PUSCH needs to switch whether or not to apply inter-bundle frequency hopping to a PUSCH. For example, the means 1 may be used to solve the problem 1. As a problem 2, a terminal device 1 that has a function of performing DMRS bundling for a message 3 PUSCH needs to be provided with higher layer parameters for a time domain window to be set from, for example, system information. For example, the means 2 may be used to solve the problem 2. Also, as a problem 3, a terminal device 1 that is configured for inter-bundle frequency hopping can be expected to improve communication efficiency by ensuring flexibility for a frequency hopping method. For example, the means 3 may be used to solve the problem 3.
[0283] In the means 1, the means 2, and the means 3, a dedicated higher layer parameter used to determine whether or not the frequency hopping scheme is inter-bundle frequency hopping may be provided. For example, in the means 1, the means 2, and the means 3, a dedicated higher layer parameter indicating whether or not the frequency hopping scheme is inter-bundle frequency hopping may be provided. Also, in the means 1, the means 2, and the means 3, a bundle for inter-bundle frequency hopping may be provided by the higher layer parameter.
[0284] Means 1 is explained in paragraphs 0285 to 0295.
[0285] In the means 1, the terminal device 1 may determine whether to apply inter-bundle frequency hopping to the scheduled PUSCH based at least on whether the PUSCH is a message 3 PUSCH. For example, if the PUSCH is a message 3 PUSCH, inter-slot frequency hopping may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH, inter-bundle frequency hopping may be applied to the PUSCH.
[0286] That is, if the PUSCH is not a message 3 PUSCH but is scheduled by a random access response grant, inter-slot frequency hopping may be applied to the PUSCH.
[0287] In addition, in another example, if the PUSCH is not a message 3 PUSCH but is scheduled by a random access response grant, inter-bundle frequency hopping may be applied to the PUSCH.
[0288] For example, if the PUSCH is a message 3 PUSCH and repetitive transmission is applied to the PUSCH, inter-slot frequency hopping may be applied to the PUSCH. For example, if the PUSCH is a message 3 PUSCH and repetitive transmission is not applied to the PUSCH, intra-slot frequency hopping may be applied to the PUSCH. For example, if the PUSCH is a message 3 PUSCH and repetitive transmission is not applied to the PUSCH, intra-slot frequency hopping may be applied to the PUSCH. If the PUSCH is not a PUSCH and repetition transmission is applied to the PUSCH, inter-bundle frequency hopping may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH and repetition is not applied to the PUSCH, intra-slot frequency hopping may be applied to the PUSCH.
[0289] For example, when the PUSCH is a message 3 PUSCH, repetitive transmission is applied to the PUSCH, and the value of the frequency hopping flag field included in either the random access response grant used for scheduling the PUSCH or the DCI is 1, inter-slot frequency hopping may be applied to the PUSCH. For example, when the PUSCH is a message 3 PUSCH, repetitive transmission is applied to the PUSCH, and the value of the frequency hopping flag field included in either the random access response grant used for scheduling the PUSCH or the DCI is 0, frequency hopping may not be applied to the PUSCH. For example, when the PUSCH is a message 3 PUSCH, repetitive transmission is not applied to the PUSCH, and the value of the frequency hopping flag field included in either the random access response grant used for scheduling the PUSCH or the DCI is 1, intra-slot frequency hopping may be applied to the PUSCH. For example, if the PUSCH is a message 3 PUSCH, repeated transmission is not applied to the PUSCH, and the value of the frequency hopping flag field included in either the random access response grant used for scheduling the PUSCH or the DCI is 0, frequency hopping may not be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH, repeated transmission is applied to the PUSCH, and the value of the frequency hopping flag field included in the DCI used for scheduling the PUSCH is 1, inter-bundle frequency hopping may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH, repeated transmission is applied to the PUSCH, and the value of the frequency hopping flag field included in the DCI used for scheduling the PUSCH is 0, frequency hopping may not be applied to the PUSCH.For example, if the PUSCH is not a message 3 PUSCH, repeated transmission is not applied to the PUSCH, and the value of the frequency hopping flag field included in the DCI used for scheduling the PUSCH is 1, intra-slot frequency hopping may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH, repeated transmission is not applied to the PUSCH, and the value of the frequency hopping flag field included in the DCI used for scheduling the PUSCH is 0, frequency hopping may not be applied to the PUSCH. The value of the frequency hopping flag field being 1 may mean that frequency hopping is applied to the PUSCH. The value of the frequency hopping flag field being 0 may mean that frequency hopping is not applied to the PUSCH.
[0290] In the means 1 and the means 2, the message 3 PUSCH may be applied with repeated transmission. For example, the PUSCH scheduled by the DCI with the CRC scrambled by the TC-RNTI may be applied with repeated transmission. For example, the number of repetitions may be determined at least based on the DCI. For example, the PUSCH scheduled by the random access response grant included in the PDSCH may be applied with repeated transmission. For example, the number of repetitions may be determined at least based on the random access response grant.
[0291] In the methods 1 and 2, frequency hopping is applied to the message 3 PUSCH. A message 3 PUSCH scheduled by a DCI or a random access response grant may perform frequency hopping based on the DCI or the random access response grant. For example, a message 3 PUSCH to which repetitive transmission is applied and frequency hopping is applied may apply inter-slot frequency hopping. For example, a message 3 PUSCH to which repetitive transmission is not applied and frequency hopping is applied may apply intra-slot frequency hopping.
[0292] In the means 1 and the means 2, the positions of the first resource blocks corresponding to the first hop and the second hop for the PUSCH of the message 3 and the RB offset In the means 1 and the means 2, one or both of the first resource block positions and the RB corresponding to the first hop and the second hop for the PUSCH of the message 3 are provided based on at least a common upper layer parameter. offset One or both of may be provided without being based on dedicated higher layer parameters.
[0293] In the means 1, one or both of the configured time domain window and the actual time domain window may be applied to the PUSCH scheduled by DCI with CRC scrambled by at least C-RNTI and any one of CS-RNTI and MCS-C-RNTI. For example, the PUSCH may perform inter-bundle frequency hopping. In frequency hopping for repeated transmission of the PUSCH, the number of slots corresponding to the frequency hopping interval may be determined by a higher layer parameter. The higher layer parameter may determine a window length for the configured time domain window.
[0294] For example, the number of slots corresponding to the frequency hopping interval may be determined by one higher layer parameter, which may be set for each PUSCH-Config.
[0295] For example, the number of slots corresponding to the frequency hopping interval may be determined by one higher layer parameter selected from a plurality of higher layer parameters. For example, the one higher layer parameter may be determined based on at least one of element 1 and element 2 of the plurality of higher layer parameters. Element 1 may be a DCI format corresponding to DCI that schedules a PUSCH to which frequency hopping is applied. Element 2 may be a time domain resource allocation field included in DCI that schedules a PUSCH to which frequency hopping is applied. For example, the plurality of higher layer parameters may be set for each PUSCH-Config.
[0296] In the means 1, one or both of the time domain window set for the repeated transmission of the message 3 PUSCH and the actual time domain window may not be applied. For example, the message 3 PUSCH may not perform inter-bundle frequency hopping. In the frequency hopping for the repeated transmission of the message 3 PUSCH, the number of slots corresponding to the frequency hopping interval may be 1.
[0297] Means 2 is explained in paragraphs 0298 to 0304.
[0298] In the means 2, the terminal device 1 may determine whether to apply a first upper layer parameter or a second upper layer parameter to a scheduled PUSCH based at least on whether the PUSCH is a message 3 PUSCH. The first upper layer parameter may be an upper layer parameter for a first configured time domain window. For example, the upper layer parameter for the first configured time domain window may indicate a first window length. The second upper layer parameter may be an upper layer parameter for a second configured time domain window. For example, the upper layer parameter for the second configured time domain window may indicate a second window length. For example, if the PUSCH is a message 3 PUSCH, the first upper layer parameter may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH, the second upper layer parameter may be applied to the PUSCH. The first upper layer parameter may be a common upper layer parameter. The second upper layer parameter may be a dedicated upper layer parameter.
[0299] For example, if the PUSCH is a message 3 PUSCH and repetition transmission is applied to the PUSCH, the first higher layer parameter may be applied to the PUSCH. For example, if the PUSCH is a message 3 PUSCH and repetition transmission is not applied to the PUSCH, both the first higher layer parameter and the second higher layer parameter may not be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH and repetition transmission is applied to the PUSCH, the second higher layer parameter may be applied to the PUSCH. For example, if the PUSCH is not a message 3 PUSCH and repetition is not applied to the PUSCH, both the first higher layer parameter and the second higher layer parameter may not be applied to the PUSCH.
[0300] For example, if the PUSCH is not a message 3 PUSCH but is scheduled by a random access response grant, inter-bundle frequency hopping may be applied to the PUSCH, and the first higher layer parameter may be applied to the PUSCH.
[0301] In the means 2, one or both of the configured time domain window and the actual time domain window may be applied to the PUSCH scheduled by the DCI with CRC scrambled by at least the C-RNTI and either the CS-RNTI or the MCS-C-RNTI. For example, the PUSCH may perform inter-bundle frequency hopping. In the frequency hopping for the repeated transmission of the PUSCH, the number of slots corresponding to the frequency hopping interval may be determined by a first higher layer parameter. The first higher layer parameter may determine a window length for the first configured time domain window.
[0302] For example, the first higher layer parameter may be determined based on at least one of element 1 and element 2 among the one or more higher layer parameters. Element 1 may be a DCI format corresponding to DCI scheduling a PUSCH to which frequency hopping is applied. Element 2 may be a time domain resource allocation field included in DCI scheduling a PUSCH to which frequency hopping is applied.
[0303] In the means 2, one or both of a configured time domain window and an actual time domain window for the repeated transmission of the message 3 PUSCH may be applied. For example, the message 3 PUSCH may perform inter-bundle frequency hopping. In the frequency hopping for the repeated transmission of the message 3 PUSCH, a number of slots corresponding to a frequency hopping interval may be determined by a second higher layer parameter. The second higher layer parameter may be different from the first higher layer parameter. The second higher layer parameter may determine a window length for the second configured time domain window.
[0304] For example, the second upper layer parameter may be element 1 of the one or more upper layer parameters; and may be determined based on at least one of element 1 and element 2. Element 1 may be a DCI format corresponding to a DCI that schedules a PUSCH to which frequency hopping is applied. Element 2 may be a time domain resource allocation field included in a DCI that schedules a PUSCH to which frequency hopping is applied.
[0305] Measure 3 is explained in paragraphs 0306 to 0316.
[0306] In the means 3, frequency hopping may be applied to the PUSCH repeat transmission. For example, inter-bundle frequency hopping may be applied to the PUSCH repeat transmission. In the frequency hopping for the PUSCH repeat transmission, the number of slots corresponding to the frequency hopping interval may be determined by a first higher layer parameter. That is, the bundle for the inter-bundle frequency hopping may be determined by the first higher layer parameter. Also, in the frequency hopping for the PUSCH repeat transmission, the frequency hopping scheme may be determined by a second higher layer parameter. The first higher layer parameter may be a dedicated higher layer parameter. The second higher layer parameter may be a dedicated higher layer parameter.
[0307] In the means 3, the first higher layer parameter may be different from the second higher layer parameter. For example, the first higher layer parameter may be set for each PUSCH-Config. For example, the second higher layer parameter may be determined based at least on element 1 among one or more higher layer parameters in the PUSCH-Config. Element 1 may be a DCI format corresponding to DCI that schedules a PUSCH to which frequency hopping is applied.
[0308] In the means 3, when the first higher layer parameter is set and the second higher layer parameter indicates intra-slot frequency hopping, the frequency hopping corresponding to the frequency hopping for the PUSCH may be intra-slot frequency hopping. Also, when the first higher layer parameter is set and the second higher layer parameter indicates inter-slot frequency hopping, the frequency hopping corresponding to the frequency hopping for the PUSCH may be inter-bundle frequency hopping. Also, when the first higher layer parameter is set and the second higher layer parameter indicates inter-bundle frequency hopping, the frequency hopping corresponding to the frequency hopping for the PUSCH may be inter-bundle frequency hopping.
[0309] In the means 3, when the first higher layer parameter is set and the second higher layer parameter indicates intra-slot frequency hopping, the frequency hopping interval corresponding to the frequency hopping for the PUSCH may be within one slot. Also, when the first higher layer parameter is set and the second higher layer parameter indicates inter-slot frequency hopping, the frequency hopping interval corresponding to the frequency hopping for the PUSCH may be determined by the first higher layer parameter. Also, when the first higher layer parameter is set and the second higher layer parameter indicates inter-bundle frequency hopping, the frequency hopping interval corresponding to the frequency hopping for the PUSCH may be determined by the first higher layer parameter.
[0310] In the means 3, when the frequency hopping interval determined by the first higher layer parameter is greater than one slot, the second higher layer parameter may not be expected to indicate intra-slot frequency hopping. Also, when the number of slots corresponding to the frequency hopping interval for PUSCH repeat transmission is set to a value greater than 1 by the first higher layer parameter, the terminal device 1 may not perform intra-slot frequency hopping for the PUSCH repeat transmission.
[0311] For example, the first higher layer parameter may be determined based on at least one of element 1 and element 2 among one or more higher layer parameters in the PUSCH-Config. Element 1 may be a DCI format corresponding to DCI that schedules a PUSCH to which frequency hopping is applied. Element 2 may be a time domain resource allocation field included in DCI that schedules a PUSCH to which frequency hopping is applied.
[0312] The first higher layer parameter may determine a window length for the time domain window to be configured.
[0313] In the means 3, the terminal device 1 may determine whether to apply a first higher layer parameter indicating a frequency hopping interval to the scheduled PUSCH based at least on a second higher layer parameter indicating a frequency hopping scheme of the PUSCH. For example, the first higher layer parameter may indicate a number of slots corresponding to a frequency hopping interval for the PUSCH. For example, if the second higher layer parameter indicates intra-slot frequency hopping, the first higher layer parameter may not be applied for frequency hopping of the PUSCH. For example, if the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping, the first higher layer parameter may be applied for frequency hopping of the PUSCH.
[0314] For example, when the second higher layer parameter indicates intra-slot frequency hopping, the first higher layer parameter may not be applied for the frequency hopping of the PUSCH, and the first higher layer parameter may be applied for the configured time domain window of the PUSCH. For example, when the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping, the first higher layer parameter may be applied for the frequency hopping of the PUSCH, and the first higher layer parameter may be applied for the configured time domain window of the PUSCH.
[0315] For example, when the second higher layer parameter indicates intra-slot frequency hopping and repetitive transmission is applied to the PUSCH, the first higher layer parameter may not be applied for the frequency hopping of the PUSCH repetition, and the first higher layer parameter may be applied for the configured time domain window of the PUSCH repetition. For example, when the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping and repetitive transmission is applied to the PUSCH, the first higher layer parameter may be applied for the frequency hopping of the PUSCH repetition, and the first higher layer parameter may be applied for the configured time domain window of the PUSCH repetition.
[0316] For example, when the second higher layer parameter indicates intra-slot frequency hopping and repetitive transmission is applied to the PUSCH, the first higher layer parameter may not be applied for frequency hopping of the PUSCH repetition, and a window length of a time domain window set for the PUSCH repetition transmission may be determined based on the first higher layer parameter. For example, when the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping and repetitive transmission is applied to the PUSCH, the first higher layer parameter may be applied for frequency hopping of the PUSCH repetition, and a window length of a time domain window set for the PUSCH repetition transmission may be determined based on the first higher layer parameter.
[0317] Various aspects of the device according to one aspect of this embodiment will be described below.
[0318] (1) In order to achieve the above object, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device, comprising: a receiving unit that receives a PDCCH including a DCI or a PDSCH including a random access response grant; and a transmitting unit that transmits a PUSCH, the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based on at least the DCI or the random access response grant, repeated transmission is instructed for the PUSCH, the transmission of the PUSCH is instructed by the DCI, and When the DCI includes a CRC scrambled by a TC-RNTI, a frequency hopping interval corresponding to the frequency hopping is one slot, when the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is one slot, and when the DCI indicates transmission of the PUSCH and includes a CRC scrambled by at least a C-RNTI, a CS-RNTI, or an MCS-C-RNTI, a number of slots for the frequency hopping interval is determined by a higher layer parameter. One or more higher layer parameters may be configured for the number of slots, and the higher layer parameter may be determined based at least on one of element 1 and element 2 of the one or more higher layer parameters, where element 1 may be a DCI format corresponding to the DCI, and element 2 may be a time domain resource allocation field included in the DCI. The higher layer parameter may determine a window length for a time domain window to be configured.
[0319] (2) A second aspect of the present invention is a terminal device comprising: a receiving unit that receives a PDCCH including a DCI or a PDSCH including a random access response grant; and a transmitting unit that transmits a PUSCH, the transmission of the PUSCH is instructed by the DCI or the random access response grant; a first higher layer parameter used to determine a window length of a first configured time domain window and a second higher layer parameter used to determine a window length of a second configured time domain window are provided; repeated transmission is applied to the PUSCH; the transmission of the PUSCH is instructed by the DCI; and A window length of the first configured time domain window is applied for the PUSCH if the DCI is accompanied by a CRC scrambled by a TC-RNTI, a window length of the first configured time domain window is applied for the PUSCH if the random access response grant indicates transmission of the PUSCH, and a window length of the second configured time domain window is applied for the PUSCH if the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by at least a C-RNTI, and any one of a CS-RNTI and an MCS-C-RNTI. The first upper layer parameter may be a common upper layer parameter, and the second upper layer parameter may be a dedicated upper layer parameter.
[0320] (3) A third aspect of the present invention is a terminal device comprising: a receiving unit that receives a PDCCH including a DCI instructing transmission of a PUSCH; and a transmitting unit that transmits the PUSCH, wherein frequency hopping for the PUSCH is performed based at least on the DCI, a number of slots for a frequency hopping interval corresponding to the frequency hopping is determined by a first higher layer parameter, a frequency hopping scheme corresponding to the frequency hopping is set by a second higher layer parameter different from the first higher layer parameter, and when the second higher layer parameter indicates intra-slot frequency hopping, the frequency hopping interval is within one slot, and when the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping, the frequency hopping interval is the number of slots. One or more higher layer parameters may be configured for the number of slots, and the first higher layer parameter may be determined based on at least one of element 1 and element 2 of the one or more higher layer parameters, where element 1 may be a DCI format corresponding to the DCI, and element 2 may be a time domain resource allocation field included in the DCI. If the second higher layer parameter indicates intra-slot frequency hopping, a window length of a configured time domain window for the PUSCH may be determined based on the first higher layer parameter, and if the second higher layer parameter indicates any of inter-slot frequency hopping and inter-bundle frequency hopping, the window length of the configured time domain window for the PUSCH may be determined based on the first higher layer parameter.
[0321] (4) A fourth aspect of the present invention is a terminal device, comprising: a receiving unit that receives a PDCCH including a DCI that instructs transmission of a PUSCH; and a transmitting unit that transmits the PUSCH, wherein frequency hopping for the PUSCH is performed based at least on the DCI, a number of slots for a frequency hopping interval corresponding to the frequency hopping is determined by a first higher layer parameter, a frequency hopping scheme corresponding to the frequency hopping is set by a second higher layer parameter different from the first higher layer parameter, and based on the number of slots for the frequency hopping interval being greater than 1, the second higher layer parameter is not expected to indicate intra-slot frequency hopping. One or more higher layer parameters may be set for the number of slots, and the first higher layer parameter may be determined based at least on either element 1 or element 2 of the one or more higher layer parameters, and the element 1 may be a DCI format corresponding to the DCI, and the element 2 may be a time domain resource allocation field included in the DCI. A window length of the configured time domain window for the PUSCH may be determined based on the first higher layer parameter.
[0322] (5) A fifth aspect of the present invention is a base station device, comprising: a transmitter that transmits a PDCCH including a DCI or a PDSCH including a random access response grant; and a receiver that receives a PUSCH, wherein the transmission of the PUSCH is instructed by the DCI or the random access response grant, frequency hopping for the PUSCH is performed based on at least the DCI or the random access response grant, the transmission of the PUSCH is instructed by the DCI, the DCI includes a CRC scrambled by a TC-RNTI, and the transmission of the PUSCH is instructed by the DCI. When the random access response grant indicates transmission of the PUSCH and repetitive transmission is applied to the transmission of the PUSCH, the frequency hopping interval corresponding to the frequency hopping is one slot, when the random access response grant indicates transmission of the PUSCH and repetitive transmission is applied to the transmission of the PUSCH, the frequency hopping interval is one slot, when the DCI includes at least a C-RNTI and a CRC scrambled by any one of CS-RNTI and MCS-C-RNTI and repetitive transmission is applied to the transmission of the PUSCH, the number of slots for the frequency hopping interval is determined by a certain higher layer parameter. One or more higher layer parameters may be configured for the number of slots, and the certain higher layer parameter may be determined based at least on any one of element 1 and element 2 of the one or more higher layer parameters, where the element 1 may be a DCI format corresponding to the DCI and the element 2 may be a time domain resource allocation field included in the DCI. The certain higher layer parameter may determine a window length for a time domain window to be configured.
[0323] (6) A sixth aspect of the present invention is a base station device, comprising: a transmission unit for transmitting a PDCCH including a DCI or a PDSCH including a random access response grant. and a receiving unit for receiving a PUSCH, wherein a transmission of the PUSCH is indicated by the DCI or the random access response grant, and a first higher layer parameter used to determine a window length of a first configured time domain window and a second higher layer parameter used to determine a window length of a second configured time domain window are provided, and when the DCI includes a CRC scrambled by a TC-RNTI and repetitive transmission is applied to the transmission of the PUSCH, the window length of the first configured time domain window for the PUSCH is determined. a window length of the first configured time domain window for the PUSCH is applied, if the transmission of the PUSCH is indicated by the random access response grant and repetition transmission is applied for the transmission of the PUSCH, a window length of the first configured time domain window for the PUSCH is applied, and if the DCI involves at least a C-RNTI and a CRC scrambled by any of a CS-RNTI and an MCS-C-RNTI and repetition transmission is applied for the transmission of the PUSCH, a window length of the second configured time domain window for the PUSCH is applied. The first upper layer parameter may be a common upper layer parameter, and the second upper layer parameter may be a dedicated upper layer parameter.
[0324] (7) A seventh aspect of the present invention is a base station device comprising: a receiving unit that transmits a PDCCH including a DCI that instructs transmission of a PUSCH; and a receiving unit that receives the PUSCH, wherein frequency hopping for the PUSCH is performed based at least on the DCI, a number of slots for a frequency hopping interval corresponding to the frequency hopping is determined by a first higher layer parameter, a frequency hopping scheme corresponding to the frequency hopping is set by a second higher layer parameter different from the first higher layer parameter, and when the second higher layer parameter indicates intra-slot frequency hopping, the frequency hopping interval is within one slot, and when the second higher layer parameter indicates either inter-slot frequency hopping or inter-bundle frequency hopping, the frequency hopping interval is the number of slots. One or more higher layer parameters may be configured for the number of slots, and the first higher layer parameter may be determined based on at least one of element 1 and element 2 of the one or more higher layer parameters, where element 1 may be a DCI format corresponding to the DCI, and element 2 may be a time domain resource allocation field included in the DCI. If the second higher layer parameter indicates intra-slot frequency hopping, a window length of a configured time domain window for the PUSCH may be determined based on the first higher layer parameter, and if the second higher layer parameter indicates any of inter-slot frequency hopping and inter-bundle frequency hopping, the window length of the configured time domain window for the PUSCH may be determined based on the first higher layer parameter.
[0325] (8) An eighth aspect of the present invention is a base station device, comprising: a transmitter that transmits a PDCCH including a DCI instructing transmission of a PUSCH; and a receiver that receives the PUSCH, wherein frequency hopping for the PUSCH is performed based at least on the DCI, a number of slots for a frequency hopping interval corresponding to the frequency hopping is determined by a first higher layer parameter, a frequency hopping scheme corresponding to the frequency hopping is set by a second higher layer parameter different from the first higher layer parameter, and based on the number of slots for the frequency hopping interval being greater than 1, the second higher layer parameter is not expected to indicate intra-slot frequency hopping. One or more higher layer parameters may be set for the number of slots, and the first higher layer parameter may be determined based at least on either element 1 or element 2 of the one or more higher layer parameters, and the element 1 may be a DCI format corresponding to the DCI, and the element 2 may be a time domain resource allocation field included in the DCI. A window length of the configured time domain window for the PUSCH may be determined based on the first higher layer parameter.
[0326] The base station device 3 and the program operating in the terminal device 1 according to the present invention control a CPU (Central Processing Unit) and the like so as to realize the functions of the above-mentioned embodiment according to the present invention. The information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then read and written to various ROMs such as Flash ROM (Read Only Memory) or HDD. D (Hard Disk Drive) and is read, modified, and written by the CPU as necessary. The inclusion takes place.
[0327] In addition, a part of the terminal device 1 and the base station device 3 in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to realize the control function.
[0328] The "computer system" here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as an OS and peripheral devices. Also, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system.
[0329] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that stores a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in such a case. The above program may be one that realizes part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.
[0330] Furthermore, the base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) consisting of a plurality of devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 according to the above-described embodiment. It is sufficient for the device group to have all of the functions or functional blocks of the base station device 3. Furthermore, the terminal device 1 according to the above-described embodiment can also communicate with the base station device as an aggregate.
[0331] In addition, the base station device 3 in the above-mentioned embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). In addition, the base station device 3 in the above-mentioned embodiment may have a part or all of the functions of an upper node for an eNodeB and / or a gNB.
[0332] In addition, some or all of the terminal device 1 and base station device 3 in the above-mentioned embodiment may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all of them may be integrated into a chip. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that replaces LSI appears due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.
[0333] In the above embodiment, a terminal device is described as an example of a communication device. However, the present invention is not limited to this, and can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.
[0334] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]
[0335] 1(1A, 1B, 1C) Terminal equipment 3 Base station equipment 10, 30 Radio transmitter / receiver 10a, 30a Wireless transmitter 10b, 30b Wireless receiver 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component Carriers 301 Primary Cell 302, 303 Secondary Cell A set of resource elements for 700 PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of Resource Elements for SSS 3000 points 3001, 3002 Resource Grid 3003, 3004 BWP 3011, 3012, 3013, 3014 offset 3100, 3200 common resource block set 900, 901 resource blocks 910, 911, 912, 913, 914, 915, 916, 917 Slots 920, 921, 922, 923, 924, 925, 926, 927 PUSCH 930, 931 Time domain window to be set 940, 941 Actual time domain window
Claims
1. A receiving unit that receives a PDCCH including a DCI or receives a PDSCH including a random access response grant; A transmission unit that transmits a PUSCH, The transmission of the PUSCH is indicated by the DCI or the random access response grant, performing frequency hopping for the PUSCH based at least on the DCI or the random access response grant; Repeated transmission is instructed for the PUSCH, When the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by a TC-RNTI, a frequency hopping interval corresponding to the frequency hopping is 1 slot; When the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot; When the DCI indicates transmission of the PUSCH and the DCI includes at least a C-RNTI and a CRC scrambled by either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by a higher layer parameter. Terminal device.
2. One or more higher layer parameters are configured for the number of slots; The certain upper layer parameter is determined based on at least one of an element 1 and an element 2 among the one or more upper layer parameters; The element 1 is a DCI format corresponding to the DCI, Element 2 is a time domain resource allocation field included in the DCI The terminal device according to claim 1 .
3. The certain higher layer parameter determines the window length for the time domain window to be configured. The terminal device according to claim 1 or 2.
4. A receiving unit that receives a PDCCH including a DCI or receives a PDSCH including a random access response grant; A transmission unit that transmits a PUSCH, The transmission of the PUSCH is indicated by the DCI or the random access response grant, A first higher layer parameter is provided for use in determining a window length of the first configured time domain window, and a second higher layer parameter is provided for use in determining a window length of the second configured time domain window, Repeated transmission is applied to the PUSCH, When the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by a TC-RNTI, a window length of the first configured time domain window is applied for the PUSCH; When the random access response grant indicates transmission of the PUSCH, a window length of the first configured time domain window is applied for the PUSCH; When the DCI indicates transmission of the PUSCH and the DCI includes at least a C-RNTI and a CRC scrambled by any one of a CS-RNTI and an MCS-C-RNTI, the second configured time period for the PUSCH is set. The window length of the region window is applied. Terminal device.
5. the first upper layer parameter is a common upper layer parameter; The second higher layer parameter is a dedicated higher layer parameter. The terminal device according to claim 4.
6. A transmitter for transmitting a PDCCH including a DCI or a PDSCH including a random access response grant; A receiving unit for receiving a PUSCH, The transmission of the PUSCH is indicated by the DCI or the random access response grant, performing frequency hopping for the PUSCH based at least on the DCI or the random access response grant; Repeated transmission is instructed for the PUSCH, When the DCI indicates transmission of the PUSCH and the DCI is accompanied by a CRC scrambled by a TC-RNTI, a frequency hopping interval corresponding to the frequency hopping is 1 slot; When the random access response grant indicates transmission of the PUSCH, the frequency hopping interval is 1 slot; When the DCI indicates transmission of the PUSCH and the DCI includes at least a C-RNTI and a CRC scrambled by either a CS-RNTI or an MCS-C-RNTI, the number of slots for the frequency hopping interval is determined by a higher layer parameter. Base station equipment.
7. One or more higher layer parameters are configured for the number of slots; The certain upper layer parameter is determined based on at least one of an element 1 and an element 2 among the one or more upper layer parameters; The element 1 is a DCI format corresponding to the DCI, Element 2 is a time domain resource allocation field included in the DCI The base station device according to claim 6.
8. The certain higher layer parameter determines the window length for the time domain window to be configured. The base station device according to claim 6 or 7.
