Terminal device and base station device

Abstract

To provide a terminal device capable of performing SPS PDSCH receptions in different cycles.SOLUTION: A terminal device comprises a reception section for receiving a DCI format. A first high-order layer parameter determines a cycle of at least a first SPS PDSCH, and a second high-order layer parameter determines a cycle of at least a second SPS PDSCH cycle. The first SPS PDSCH is deactivated by the DCI format. The second SPS PDSCH is activated by the DCI format. The cycle of the first SPS PDSCH is different from the cycle of the second SPS PDSCH. The reception section receives the second SPS PDSCH based on the second high-order layer parameter.SELECTED DRAWING: Figure 11

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). rd This is being studied in the LTE Generation Partnership Project. In LTE, base station devices are also called eNodeBs (evolved NodeBs) and terminal devices are also called UEs (User Equipment). LTE is a cellular communication system in which areas covered by base station devices are arranged in multiple cell-like configurations. A single base station device may manage multiple serving cells.

[0003] 3GPP is currently studying the next-generation standard (NR: New Radio) to be proposed for IMT (International Mobile Telecommunication)-2020, a standard for next-generation mobile communication systems formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is expected to meet the requirements of 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] 3GPP is currently studying the extension of services supported by NR (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 [Non-patent document 3] “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #94-e, 6th - 17th December, 2021 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 including a receiving unit that receives a DCI format, wherein a first higher layer parameter determines a periodicity of at least a first SPS PDSCH, a second higher layer parameter determines a periodicity of at least a second SPS PDSCH, the first SPS PDSCH is deactivated by the DCI format, the second SPS PDSCH is activated by the DCI format, the periodicity of the first SPS PDSCH is different from the periodicity of the second SPS PDSCH, and the receiving unit receives the second SPS PDSCH based on the second higher layer parameter.

[0008] (2) A second aspect of the present invention is a base station device including a transmitter that transmits a DCI format, wherein a first higher layer parameter determines at least a periodicity of a first SPS PDSCH, a second higher layer parameter determines at least a periodicity of a second SPS PDSCH, the first SPS PDSCH is deactivated by the DCI format, the second SPS PDSCH is activated by the DCI format, the periodicity of the first SPS PDSCH is different from the periodicity of the second SPS PDSCH, and the transmitter transmits the second SPS PDSCH based on the second higher layer parameter.

[0009] (3) A third aspect of the present invention is a communication method used in a terminal device, comprising: receiving a DCI format; a first higher layer parameter determines a periodicity of at least a first SPS PDSCH; a second higher layer parameter determines a periodicity of at least a second SPS PDSCH; the first SPS PDSCH is deactivated by the DCI format; the second SPS PDSCH is activated by the DCI format; the periodicity of the first SPS PDSCH differs from the periodicity of the second SPS PDSCH; and the second SPS PDSCH is received based on the second higher layer parameter.

[0010] (4) Furthermore, a fourth aspect of the present invention is a communication method used in a base station device, comprising: transmitting a DCI format; a first higher layer parameter determines at least a periodicity of a first SPS PDSCH; a second higher layer parameter determines at least a periodicity of a second SPS PDSCH; the first SPS PDSCH is deactivated by the DCI format; the second SPS PDSCH is activated by the DCI format; the periodicity of the first SPS PDSCH is different from the periodicity of the second SPS PDSCH; and the second SPS PDSCH is transmitted based on the second higher layer parameter. [Effects 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 explanation of the drawings]

[0012] [Figure 1] 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. [Figure 2] 10 is an example showing the relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and a cyclic prefix (CP) setting according to one aspect of the present embodiment. [Figure 3] FIG. 10 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. [Figure 5] 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one 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 aspect of this embodiment. [Figure 8]FIG. 10 is a diagram illustrating an example of a monitoring opportunity for a set of search areas according to one aspect of the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating a flow for explaining an example of an SPS according to one aspect of this embodiment. [Figure 10] FIG. 9 is a diagram showing a detailed example of 906 according to one aspect of this embodiment. [Figure 11] 10A and 10B are diagrams illustrating examples of SPS PDSCH reception with different periods based on a PDCCH according to an aspect of the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[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. E modulo F may output the remainder when E is divided by F. exp(G) = e^G, where e is Napier's constant. H^I represents H to the Ith power. max(J,K) is a function that outputs the maximum value of J and K. Here, if J and K are equal, max(J,K) is a function that outputs J or K. min(L,M) is a function that outputs the maximum value of L and M. Here, when L and M are equal, min(L,M) is a function that outputs L or M. 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 Orthogonal Frequency Division Multiplexing (OFDM) is used. An OFDM symbol is a time domain unit of OFDM. The OFDM symbol includes at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal in baseband signal generation. In the downlink, at least Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) is used. In the uplink, either CP-OFDM or Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) is used. DFT-s-OFDM may be obtained by applying Transform precoding to CP-OFDM.

[0016] The OFDM symbol may be a name including a CP added to the OFDM symbol. In other words, a certain OFDM symbol may be configured to include the certain OFDM symbol and the CP added to the certain OFDM symbol.

[0017] Fig. 1 is a conceptual diagram of a wireless communication system according to one 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 will also be 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, or transmission / reception points). When the base station device 3 is configured with multiple transmission devices, the multiple transmission devices may be located at different positions.

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

[0020] A serving cell may be configured to include one or both of a downlink component carrier (downlink carrier) and one or both of an uplink component carrier (uplink carrier). A serving cell may be configured to include one or both of two or more downlink component carriers and two or more uplink component carriers. 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. Alternatively, 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 a certain 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 called 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 (for example, the parameter CarrierBandwidth). start,μ grid,x is a bandwidth configuration indicated by a parameter provided by the RRC layer (for example, the parameter OffsetToCarrier). The offset configuration and the bandwidth configuration are configurations used to configure an SCS-specific carrier.

[0026] The subcarrier spacing (SCS: SubCarrier Spacing) Δf for a certain subcarrier spacing setting μ 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 spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb 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 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is an extended cyclic prefix (CP), N slot 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 = 480 kHz. 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 a period of length T f The radio frame (system frame, frame) may be organized into T f =(Δf max N f / 100)·T s = 10 ms. A radio frame consists 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 is.

[0030] An OFDM symbol is a time domain unit of a communication system. For example, an OFDM symbol may be a time domain unit of CP-OFDM. Also, an OFDM symbol may be a time domain unit of DFT-s-OFDM.

[0031] A slot may consist of multiple OFDM symbols, for example, N consecutive OFDM symbols. slot symb For example, in the normal CP setting, N OFDM symbols may constitute one slot. slot symb = 14. 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 the subframe may be given. For example, slot index n μ s ranges from 0 to N in the subframe subframe,μ slot The number and index of slots included in the radio frame may be given for the subcarrier spacing setting μ. μ s,f ranges from 0 to N in the radio frame. frame,μ slot Integer values ​​in the range -1 to +1 may be given in ascending order.

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

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

[0035] 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 (the 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 the 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 the subcarrier spacing setting μ1. The resource grid 3001 is 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 ) is the offset to

[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 (the 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 the 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 ) is the offset to

[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 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 contains N subcarriers, subframe,μ symb Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The resource specified by is also called a resource element (RE).

[0044] Resource Block (RB) is N RB sc A resource block includes N consecutive subcarriers. A resource block is a collective term for 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 in ascending order starting from 0. 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 The subcarrier with 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 in ascending order starting from 0 in a given BWP. The index n of the physical resource block for a given subcarrier spacing configuration μ is μ PRB is n μ CRB =nμ PRB +N start,μ BWP,i where 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 a downlink carrier is also referred to as a downlink BWP. The BWP configured for an uplink component carrier is also referred to as an uplink BWP.

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

[0050] When the large-scale properties 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 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 beam parameters (spatial Rx parameters). The first and second antenna ports being QCL with respect to beam parameters may mean that a receive beam assumed by the receiver for the first antenna port is the same as (or corresponds to) a receive beam assumed by the receiver 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 may be performing communication using a plurality of aggregated serving cells. Also, carrier aggregation may be performing communication using a plurality of aggregated component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated downlink component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated uplink component carriers.

[0052] Fig. 5 is a schematic block diagram showing an example configuration 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 transceiver unit (physical layer processing unit) 30 and / or part or all of a higher layer processing unit 34. The radio transceiver unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and 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 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 part or all of a wireless receiver 30b. Here, the baseband unit included in the wireless transmitter 30a and the baseband unit included in the wireless receiver 30b may have the same or different device configurations. Furthermore, the RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may have the same or different device configurations. Furthermore, the antenna unit included in the wireless transmitter 30a and the antenna unit included in the wireless receiver 30b may have the same or different device configurations.

[0054] For example, the radio transmitting unit 30a may generate and transmit a PDSCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PBCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a synchronization signal baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDSCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a CSI-RS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a DL PTRS baseband signal.

[0055] For example, the radio receiving unit 30b may receive a PRACH. For example, the radio receiving unit 30b may receive and demodulate a PUCCH. The radio receiving unit 30b may receive and demodulate a PUSCH. For example, the radio receiving unit 30b may receive a PUCCH DMRS. For example, the radio receiving unit 30b may receive a PUSCH DMRS. For example, the radio receiving unit 30b may receive an UL PTRS. For example, the radio 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 on the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

[0057] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing.

[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 radio transceiver unit 30 (or the radio receiver unit 30b) performs processes such as demodulation and decoding. The radio transceiver unit 30 (or the radio receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The radio transceiver unit 30 (or the radio receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.

[0061] The RF unit 32 converts (down-converts) the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation and removes unnecessary frequency components. 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 a digital signal. The baseband unit 33 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

[0063] The baseband unit 33 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate OFDM symbols, adds CPs to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 33 outputs the converted analog signals 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 to control 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 may be any of a PCell (Primary cell), a PSCell (Primary SCG cell), and an SCell (Secondary Cell).

[0067] The PCell is a serving cell included in an MCG (Master Cell Group). The PCell is a cell on which an initial connection establishment procedure or a connection re-establishment procedure is performed by the terminal device 1 (the cell on which the procedure has been performed).

[0068] The PSCell is a serving cell included in an SCG (Secondary Cell Group). The PSCell is a serving cell to which the terminal device 1 performs random access.

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

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

[0071] One or more downlink BWPs may be 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 set 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 set 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 an 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 an 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 an 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 downlink control information. The downlink BWP switch may also 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 also 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 given 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. At any given time, one uplink BWP may be active for a serving cell.

[0079] Fig. 6 is a schematic block diagram showing an example configuration 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 one or all of a radio transmission / reception unit (physical layer processing unit) 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes at least an antenna unit 11, an RF unit 12, and part 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 part or all of a radio resource control layer processing unit 16.

[0080] The wireless transceiver 10 includes at least a wireless transmitter 10a and part or all of a wireless receiver 10b. Here, the baseband unit 13 included in the wireless transmitter 10a and the baseband unit 13 included in the wireless receiver 10b may have the same or different device configurations. The RF unit 12 included in the wireless transmitter 10a and the RF unit 12 included in the wireless receiver 10b may have the same or different device configurations. The antenna unit 11 included in the wireless transmitter 10a and the antenna unit 11 included in the wireless receiver 10b may have the same or different device configurations.

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

[0082] For example, the wireless receiver 10b may receive and demodulate a PDSCH. For example, the wireless receiver 10b may receive and demodulate a PDCCH. For example, the wireless receiver 10b may receive and demodulate a PBCH. For example, the wireless receiver 10b may receive a synchronization signal. For example, the wireless receiver 10b may receive a PDSCH DMRS. For example, the wireless receiver 10b may receive a PDCCH DMRS. For example, the wireless receiver 10b may receive a CSI-RS. For example, the wireless receiver 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 on the MAC layer, the integrated packet data 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 radio transceiver 10 (or the radio transmitter 10a) performs processes such as modulation and encoding. The radio transceiver 10 (or the radio transmitter 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting into a time-continuous signal) the uplink data, and transmits the physical signal to the base station device 3. The radio transceiver 10 (or the radio transmitter 10a) may allocate the physical signal to a certain BWP (active uplink BWP) and transmit the physical signal to the base station device 3.

[0087] The radio transceiver 10 (or the radio receiver 10b) performs processes such as demodulation and decoding. The radio transceiver 10 (or the radio receiver 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The radio transceiver 10 (or the radio receiver 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The radio transceiver 10 (radio receiver 10b) may perform a channel access procedure prior to transmitting the physical signal.

[0088] The RF unit 12 converts (down-converts) the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation 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 removes a portion corresponding to a cyclic prefix (CP) from the converted digital signal, and performs a fast Fourier transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

[0090] The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the uplink data to generate OFDM symbols, adds CPs to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 13 outputs the converted analog signals 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 to control 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 a downlink physical channel, a downlink physical signal, an uplink physical channel, and an uplink physical channel. The physical channel is a general term for a downlink physical channel and an uplink physical channel. The physical signal is a general term for a downlink physical signal and an 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] The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of channel state information (CSI), 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 indicate an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to the transport block. The ACK may indicate that the transport block has been decoded successfully. The NACK may indicate that the transport block has not been decoded successfully. The HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.

[0099] A transport block is a sequence of information bits delivered from a higher layer. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be delivered via an Uplink-Shared Channel (UL-SCH) in the transport layer.

[0100] The HARQ-ACK for a transport block may be referred to as the HARQ-ACK for a PDSCH. In this case, the "HARQ-ACK for a PDSCH" refers to the 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. When the scheduling request bit indicates a positive SR, this is also referred to as "a positive SR is transmitted." A positive SR may indicate that UL-SCH resources for the initial transmission are requested by the terminal device 1. A positive SR may indicate that a scheduling request is triggered by a higher layer. A positive SR may be transmitted when a scheduling request is indicated by a higher layer. When the scheduling request bit indicates a negative SR, this is also referred to as "a negative SR is transmitted." A negative SR may indicate that UL-SCH resources for the initial transmission are not requested by the terminal device 1. A negative SR may indicate that a scheduling request is not triggered by a higher layer. A 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 indicator related to the quality of a propagation path (e.g., propagation strength) or the quality of a physical channel, the PMI is an indicator related to a precoder, and the RI is an indicator related to a transmission rank (or the number of transmission layers).

[0104] The channel state information is an indicator related to 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 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 in a certain information format.

[0106] The PUSCH may be used to transmit one or both of a transport block and uplink control information. The transport block may be allocated to the PUSCH. The transport block delivered by the UL-SCH may be allocated to the PUSCH. The uplink control information may be allocated to the PUSCH. The terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are allocated. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are allocated.

[0107] The PRACH may be transmitted to convey a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The PRACH sequence x 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. ux u =exp(-jπui(i+1) / L RA ) where j is the imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, C 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 is an integer in the range of -1, 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 cyclically shifted C v , and the sequence index u for the PRACH sequence. An index may be assigned to 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 does not have to be used to transmit information generated in a higher layer. 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] The set of antenna ports for DMRSs for PUSCH (DMRSs related to PUSCH, DMRSs included in PUSCH, and DMRSs corresponding to PUSCH) may be determined based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for DMRSs for 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 equivalent to 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 a PUCCH and the transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format. One or both of the mapping of a PUCCH to resource elements and the mapping of a 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 a PUCCH may also mean transmitting a PUCCH and a 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] The PBCH may be transmitted to convey one or both of a Master Information Block (MIB) and physical layer control information. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters allocated to a Broadcast Control Channel (BCCH), which is a logical channel of the MAC layer. The BCCH is allocated to a BCH, which is a channel of the transport layer. The BCH may be mapped to the PBCH. The terminal device 1 may receive the PBCH allocated with the MIB and / or physical layer control information. The base station device 3 may transmit the PBCH allocated with the MIB and / or physical layer control information.

[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 to identify at least 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, a half radio frame may be configured to include five subframes. Alternatively, a half radio frame may be configured to include the first five subframes of ten subframes included in a radio frame. Alternatively, a half radio frame may be configured to include the last five subframes of ten subframes included in a radio frame.

[0122] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include 3 bits. The SS / PBCH block index bits may be configured with 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 from index 0 to 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 may be transmitted to convey downlink control information (DCI). The downlink control information may be mapped to the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is mapped. The base station device 3 may transmit the PDCCH in which the downlink control information is mapped.

[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 also be interpreted as a set of downlink control information set in a certain downlink control information format.

[0126] The downlink control information may be used to activate or deactivate Semi-Persisitent Scheduling (SPS). The downlink control information may be used to activate or deactivate a configured grant type 2.

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

[0128] DCI format 0_0 is used at least for scheduling a PUSCH allocated to a certain cell. DCI format 0_0 includes at least some or all of fields 1A to 1H. 1A) Identifier field for DCI formats 1B) Frequency domain resource assignment field 1C) Time domain resource assignment field 1D) Frequency hopping flag field 1E) MCS field (Modulation and Coding Scheme field) 1F) NDI field (New data indicator field) 1G) RV field (RV field: Redundancy version field) 1H) HARQ process number field

[0129] The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. That is, the DCI format identification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format identification field included in DCI format 0_0 may indicate 0.

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

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

[0132] The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.

[0133] The NDI field may be used to indicate whether the data is new, for example, to determine whether a channel scheduled by a DCI format that includes the NDI field supports new data.

[0134] 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) allocated to the PUSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PUSCH.

[0135] DCI format 0_0 may not include fields used for CSI requests.

[0136] DCI format 0_0 may not include a carrier indicator field. That is, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated may be the same as the serving cell of the uplink component carrier on which the PDCCH including the DCI format 0_0 is allocated. By detecting DCI format 0_0 on a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_0 is allocated on the uplink component carrier of the serving cell.

[0137] DCI format 0_0 may not include a BWP field. Here, DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing an active uplink BWP. Based on detecting DCI format 0_0 used for scheduling a PUSCH, the terminal device 1 may recognize that the PUSCH will be transmitted without switching the active uplink BWP.

[0138] DCI format 0_1 ​​is used at least for scheduling a PUSCH allocated to a certain cell. DCI format 0_1 ​​includes at least some or all of fields 2A to 2K. 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 2I) NDI field (New data indicator field) 2J) RV field (RV field: Redundancy version field) 2K) HARQ process number field

[0139] The DCI format specific field included in DCI format 0_1 ​​may indicate 0.

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

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

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

[0143] The BWP field of 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 of 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.

[0144] The DCI format 0_1 ​​that does not include a BWP field may be a DCI format for scheduling a PUSCH without changing the 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.

[0145] If the DCI format 0_1 ​​includes a BWP field but the terminal device 1 does not support the BWP switching function by the DCI format 0_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it transmits the PUSCH 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 BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

[0146] The CSI request field is used to indicate the reporting of CSI.

[0147] When DCI format 0_1 ​​includes a carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier on which a PUSCH is arranged. When DCI format 0_1 ​​does not include a carrier indicator field, the uplink component carrier on which a PUSCH is arranged may be the same as an uplink component carrier on which a PDCCH including DCI format 0_1 ​​used for scheduling the PUSCH is arranged. When the number of uplink component carriers configured in a 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 DCI format 0_1 ​​used for scheduling a 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 for a terminal device 1 in a certain serving cell group is 1 (when uplink carrier aggregation is not operated in a certain 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 certain 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 certain serving cell group).

[0148] DCI format 1_0 is used at least for scheduling a PDSCH allocated to a certain cell, and is configured to include at least some or all of 3A to 3I. 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 3G) NDI field (NDI field: New data indicator field) 3H) RV field (RV field: Redundancy version field) 3I) HARQ process number field

[0149] The DCI format specific field included in DCI format 1_0 may indicate 1.

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

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

[0152] 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 allocated to the PDSCH. The size of the transport block (TBS) allocated to the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.

[0153] The PDSCH_HARQ feedback timing indication field may be used to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.

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

[0155] DCI format 1_0 may not include a carrier indicator field. That is, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is arranged. The terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_0 is to be arranged on the downlink component carrier based on detecting DCI format 1_0 on the downlink component carrier.

[0156] DCI format 1_0 may not include a BWP field. Here, 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 it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_0 used for scheduling the PDSCH.

[0157] DCI format 1_1 is used at least for scheduling a PDSCH allocated to a certain cell. DCI format 1_1 includes at least some or all of 4A to 4L. 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 4J) NDI field (New data indicator field) 4K) RV field (RV field: Redundancy version field) 4L) HARQ process number field

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

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

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

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

[0162] 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 the slot containing the last OFDM symbol of the PDSCH to the slot containing 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 the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be specified by a parameter of a higher layer.

[0163] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.

[0164] The BWP field of 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, DCI format 1_1 may involve a change of the active downlink BWP. The terminal device 1 may recognize a downlink BWP in which a PUSCH is arranged by detecting DCI format 1_1 used for scheduling a PDSCH.

[0165] The DCI format 1_1 that does not include a BWP field may be a DCI format for scheduling a PDSCH without changing the active downlink BWP. The terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting the DCI format 1_1 that is used for scheduling a PDSCH and does not include a BWP field.

[0166] If the DCI format 1_1 includes a BWP field but the terminal device 1 does not support the BWP switching function by the DCI format 1_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for scheduling the PDSCH and includes a BWP field. Here, if the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

[0167] 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 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 for a terminal device 1 in a certain serving cell group is 1 (when downlink carrier aggregation is not operated in a certain 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 certain 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 certain serving cell group).

[0168] 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. A transport block may be allocated to the PDSCH. A transport block corresponding to the DL-SCH may be allocated to the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

[0169] 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 this embodiment, at least some or all of the following downlink physical signals may be used. ·Synchronization signal (SS) ·DL DMRS(DownLink DeModulation Reference Signal) ·CSI-RS(Channel State Information-Reference Signal) ·DL PTRS(DownLink Phase Tracking Reference Signal)

[0170] 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 PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal).

[0171] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym), where the vertical axis represents the frequency domain. Block 700 represents a set of resource elements for the PSS. Block 720 represents a set of resource elements for the SSS. Four blocks (blocks 710, 711, 712, and 713) represent 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).

[0172] As shown in FIG. 7, the SS / PBCH block includes a PSS, SSS, and PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is allocated to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is allocated to the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers in the first OFDM symbol may be set to zero. The 184th to 240th subcarriers in the first OFDM symbol may be set to zero. The 49th to 56th subcarriers in the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers in the third OFDM symbol may be set to zero. The PBCH is allocated to the 1st to 240th subcarriers in the second OFDM symbol, which are subcarriers where the DMRS for the PBCH is not allocated. 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.

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

[0174] The PBCH on which the 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 belongs.

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

[0176] The set of antenna ports for DMRSs for a PDSCH (DMRSs associated with a PDSCH, DMRSs included in a PDSCH, and DMRSs corresponding to a PDSCH) may be determined based on the set of antenna ports for the PDSCH, i.e., the set of antenna ports for DMRSs for a PDSCH may be the same as the set of antenna ports for the PDSCH.

[0177] 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 also mean transmitting the PDSCH and the DMRS for the PDSCH.

[0178] A propagation path of a PDSCH may be estimated from a DMRS for the PDSCH. If a set of resource elements carrying a certain PDSCH symbol and a set of resource elements carrying a DMRS symbol for the PDSCH are included in the same precoding resource group (PRG), the PDSCH carrying the PDSCH symbol for a certain antenna port may be estimated by the DMRS for the PDSCH.

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

[0180] 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 (or assumed to be applied) to a set of resource elements on which a certain PDCCH symbol is transmitted and a set of resource elements on which a DMRS symbol for the PDCCH is transmitted, the PDCCH on which a certain antenna port transmits a PDCCH symbol may be estimated by the DMRS for the PDCCH.

[0181] The BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels that define the relationship between physical layer channels and MAC layer channels (also called logical channels).

[0182] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, transport blocks carried on the BCH of the transport layer are delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, transport blocks carried on the UL-SCH of the transport layer are delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, transport blocks carried on the DL-SCH of the transport layer are delivered to the PDSCH of the physical layer.

[0183] One UL-SCH and one DL-SCH may be provided for each serving cell. The BCH may be provided for the PCell. The BCH does not necessarily have to be provided for the PSCell or SCell.

[0184] In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block.

[0185] The BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, the BCCH is a channel of the RRC layer used for transmitting MIB or system information. The CCCH (Common Control CHannel) may be used for transmitting an RRC message common to a plurality of terminal devices 1. Here, the CCCH may be used, for example, for a terminal device 1 that is not RRC connected. 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 example, for a terminal device 1 that is RRC connected.

[0186] Upper layer parameters common to multiple 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 configured.

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

[0188] Among certain upper layer parameters, upper layer parameters different from common upper layer parameters are also referred to as 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 configured. In other words, the dedicated RRC parameters are upper layer parameters that can provide unique settings for each of the terminal devices 1-A, 1-B, and 1-C.

[0189] The BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information other than MIB is delivered to the DL-SCH of the transport layer. The CCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the CCCH is delivered to the DL-SCH or UL-SCH. The DCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the DCCH is delivered to the DL-SCH or UL-SCH.

[0190] 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. An RRC message including a message corresponding to a DCCH is also referred to as a dedicated RRC message.

[0191] The upper layer parameters (parameters of the upper layer) are parameters included in RRC parameters or MAC CE (Medium Access Control Control Element). That is, the upper layer parameters are a general term for the parameters included in MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and MAC CE. The parameters included in MAC CE are transmitted by MAC CE (Control Element) commands.

[0192] 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

[0193] The cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in 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 the time domain and the frequency domain and detect a physical cell ID.

[0194] The sequence of PSSs is based at least on a physical cell ID. The sequence of SSSs is based at least on a physical cell ID.

[0195] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH block is permitted (possibly, reserved, configured, defined, possible).

[0196] The set of SS / PBCH block candidates in a half radio frame is also called the SS burst set. The SS burst set is also called the transmission window, SS transmission window, or DRS (Discovery Reference Signal) transmission window. The SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.

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

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

[0199] 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 at least on an index of an SS / PBCH block candidate detected based on a cell search. Each PRACH opportunity is defined based at least on resources in the time domain and the frequency domain.

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

[0201] A PDCCH including a DCI format with a CRC scrambled by the RNTI is also referred to as a PDCCH with RNTI, a PDCCH for RNTI, or a PDCCH addressed to RNTI.

[0202] The C-RNTI (Cell Radio Network Temporary Identifier) ​​may be used for dynamically scheduled unicast transmission. The dynamically scheduled unicast transmission may correspond to DL-SCH and UL-SCH. That is, the dynamically scheduled unicast transmission is either a PDSCH transmission or a PUSCH transmission. The terminal device 1 may receive (decode) a PDSCH based on detection of a PDCCH addressed to the C-RNTI including a downlink assignment. The terminal device 1 may transmit a PUSCH based on detection of a PDCCH addressed to the C-RNTI including an uplink grant.

[0203] A Configured Scheduling Radio Network Temporary Identifier (CS-RNTI) may be used for configured scheduled unicast transmissions. The CS-RNTI may be used for activating and deactivating configured scheduled unicast transmissions. The configured scheduled unicast transmissions may correspond to DL-SCH and UL-SCH. That is, the configured scheduled unicast transmissions are either PDSCH transmissions or PUSCH transmissions.

[0204] The configured and scheduled unicast transmissions may include downlink semi-persistent scheduling (SPS) and uplink configured grants.

[0205] 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 an RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including this 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 referred to as a random access response.

[0206] 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 DCI format 1_0.

[0207] 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 the contention resolution ID.

[0208] Message 3 PUSCH retransmissions are scheduled with DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

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

[0210] Data communication is a general term for downlink communication and uplink communication.

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

[0212] A control resource set is a set of resources consisting of a predetermined number of resource blocks and a predetermined number of OFDM symbols. In the frequency domain, a control resource set may be composed of contiguous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

[0213] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter, and the number of OFDM symbols constituting the control resource set may be indicated by a higher layer parameter.

[0214] 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 the search space set, may be attempting to detect a DCI format in the search space set, may be attempting to detect a PDCCH in a control resource set, may be attempting to detect a PDCCH candidate in the control resource set, or may be attempting to detect a DCI format in the control resource set.

[0215] 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 attempts to detect PDCCH candidates in some or all of a Type 0 PDCCH common search space set, a Type 0a PDCCH common search space set, a Type 1 PDCCH common search space set, a Type 2 PDCCH common search space set, a Type 3 PDCCH common search space set, and / or a UE-specific search space set.

[0216] The Type 0 PDCCH common search space set may be used as the common search space set with index 0. The Type 0 PDCCH common search space set may be the common search space set with index 0.

[0217] 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-specific PDCCH search space set.

[0218] A search space set is associated with (contained in, 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.

[0219] 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

[0220] A monitoring occasion for a search space set may correspond to an OFDM symbol in which a first OFDM symbol of a control resource set associated with the search space set is located. A monitoring occasion for a search space set may correspond to resources of a control resource set starting from a first OFDM symbol of the control resource set associated with the search space set. The monitoring occasion for the search space set is determined based on at least some or all of a PDCCH monitoring interval, a PDCCH monitoring pattern within a slot, and a PDCCH monitoring offset.

[0221] 8 is a diagram illustrating an example of a monitoring opportunity for a search area set according to one aspect of the present embodiment. In FIG. 8, search area set 91 and search area set 92 are set in primary cell 301, search area set 93 is set in secondary cell 302, and search area set 94 is set in secondary cell 303.

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

[0223] The monitoring interval of search area set 91 is set to 1 slot, the monitoring offset of search area set 91 is set to 0 slot, and the monitoring pattern of search area set 91 is set to [1,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunities for search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0224] The monitoring interval of search area set 92 is set to 2 slots, the monitoring offset of search area set 92 is set to 0 slots, and the monitoring pattern of search area set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.

[0225] The monitoring interval of search area set 93 is set to 2 slots, the monitoring offset of search area set 93 is set to 0 slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0], i.e., the monitoring opportunity for search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.

[0226] The monitoring interval of search area set 94 is set to 2 slots, the monitoring offset of search area set 94 is set to 1 slot, and the monitoring pattern of search area set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.

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

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

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

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

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

[0232] The UE dedicated PDCCH search space set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.

[0233] In downlink communication, the terminal device 1 detects a downlink DCI format. The detected downlink DCI format is used at least for PDSCH resource allocation. The detected downlink DCI format is also referred to as 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.

[0234] In uplink communication, the terminal device 1 detects an uplink DCI format. The detected DCI format is used at least for PUSCH resource allocation. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.

[0235] In configured scheduling (configured grant), 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, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured in the case of configured scheduling.

[0236] Repeated transmission may be applied to a PUSCH scheduled by DCI. Also, repeated transmission may be applied to a PUSCH scheduled by a 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.

[0237] The number of repetitions for PUSCH repeat transmission may be configured by a higher layer parameter. For example, the higher layer parameter numberOfRepetitions may be a parameter including the number of repetitions for PUSCH repeat transmission. In PUSCH repeat transmission corresponding to PUSCH repetition type A, the number of repetitions for the PUSCH repeat transmission may be determined by the value of the higher layer parameter numberOfRepetitions. In PUSCH repetition type A, the number of repetitions for a PUSCH whose transmission is indicated by a DCI format including a CRC scrambled by C-RNTI and either MCS-C-RNTI or CS-RNTI may be equal to numberOfRepetitions if the numberOfRepetitions is present in the resource allocation table. When one PUSCH-TimeDomainResourceAllocation includes one or more PUSCH-Allocations, the higher layer parameter numberOfRepetitions may be configured for each PUSCH-Allocation. Furthermore, the PUSCH-TimeDomainResourceAllocation may be referred to as a resource allocation table.

[0238] The higher layer parameter pusch-AggregationFactor may be a parameter indicating the number of repetitions for PUSCH repeat transmission. In PUSCH repeat transmission corresponding to PUSCH repetition type A, the number of repetitions for the PUSCH repeat transmission may be determined by the value of the higher layer parameter pusch-AggregationFactor. In PUSCH repetition type A, the number of repetitions of a PUSCH whose transmission is indicated by a DCI format including a CRC scrambled by C-RNTI and either MCS-C-RNTI or CS-RNTI may be equal to pusch-AggregationFactor if pusch-AggregationFactor is configured. pusch-AggregationFactor may be configured for PUSCH-Config.

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

[0240] 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 PUSCH, PUCCH, PRACH, or SRS. The UL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The UL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.

[0241] The DL symbol may be an OFDM symbol configured or indicated for downlink in time division duplex. The DL symbol may be an OFDM symbol configured or indicated for PDSCH or PDCCH. The DL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The DL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.

[0242] A flexible symbol may be an OFDM symbol within a period that is not configured or indicated as an UL symbol or DL ​​symbol. The period may be a period given by the higher layer parameter dl-UL-TransmissionPeriodicity. The flexible symbol may be an OFDM symbol configured or indicated for a PDSCH, PDCCH, PUSCH, PUCCH, or PRACH.

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

[0244] The MAC entity may include one HARQ entity in each serving cell. Each HARQ entity may manage one or more HARQ processes. Each HARQ process may be associated with a HARQ process identifier. The HARQ entity may direct HARQ information and TBs received on the DL-SCH to the corresponding HARQ process. The corresponding HARQ process may be the HARQ process corresponding to the HARQ process ID included in the HARQ information.

[0245] A number of HARQ processes may be provided for each HARQ entity. For example, each HARQ process may be parallel. A dedicated broadcast HARQ process may be used for the BCCH.

[0246] An HARQ process may support one TB. For example, an HARQ process may be used for one TB. For example, an HARQ process may correspond to one TB. If the physical layer is not configured for downlink spatial multiplexing, an HARQ process may support one TB. An HARQ process may support one or two TBs. For example, an HARQ process may correspond to one or two TBs. If the physical layer is configured for downlink spatial multiplexing, an HARQ process may support one or two TBs.

[0247] A higher layer parameter may provide the number of TB transmissions. For example, the higher layer parameter may provide the number of TB transmissions in a bundle of downlink assignments. The bundling operation may depend on the HARQ entity. The same HARQ process may be invoked for each transmission that is part of the same bundle. The bundling operation may depend on the HARQ entity to invoke the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, a certain number of HARQ retransmissions may be performed. The certain number may be the value of the higher layer parameter pdsch-AggregationFactor minus 1.

[0248] The MAC entity may assign TB and HARQ information to an HARQ process. For example, if a downlink assignment is indicated, the MAC entity may assign TB and HARQ information to an HARQ process. The HARQ process may be indicated by the HARQ information. The HARQ information may be associated with a TB. For example, the HARQ information may indicate a TBS for the TB. The TB may be received from the physical layer. For example, if a downlink assignment is indicated for a broadcast HARQ process, the MAC entity may assign the received TB to a broadcast HARQ process.

[0249] The HARQ information may be HARQ information for any of DL-SCH, UL-SCH, and SL-SCH, and may be composed of some or all of a New Data Indicator (NDI), a Transport Block Size (TBS), a Redundancy Version (RV), and a HARQ process ID.

[0250] A transmission may occur corresponding to a HARQ process. For example, when a transmission occurs in a HARQ process, one or two TBs and HARQ information may be received from the HARQ entity. The HARQ process may assume that a transmission is a new transmission. For example, if the NDI is toggled, the HARQ process may assume that a transmission is a new transmission. For example, if the NDI is toggled for a TB compared to the value of the previously received transmission corresponding to the TB, the HARQ process may assume that a transmission is a new transmission. For example, if the HARQ process is at least equal to the broadcast process, the HARQ process may assume that a transmission is a new transmission. For example, if there is no previous NDI for a TB, the HARQ process corresponding to the TB may assume that a transmission is a new transmission. A new transmission may be a first transmission. If a transmission is not a new transmission, the transmission may be a retransmission. For example, if the NDI is not toggled, the transmission may be a retransmission.

[0251] If a transmission is a new transmission, the MAC entity may attempt to decode the received data. If a transmission is a retransmission, the MAC entity may instruct the physical layer to combine the received data with the data in the soft buffer. The MAC entity may also attempt to decode the combined data. The data may correspond to a TB. The soft buffer may correspond to a TB. The HARQ process may be equivalent to a broadcast process. If decoding of the data is successful, the MAC entity may transmit the decoded data (e.g., a MAC PDU) to an upper layer. If decoding of the data fails, the MAC entity may instruct the physical layer to place the data in the soft buffer. The MAC entity may instruct the physical layer to generate acknowledgments for the data. The MAC entity may ignore the NDI. For example, the NDI may be received in all downlink assignments. For downlink assignments, the PDCCH may be included. The PDCCH may correspond to a Temporary C-RNTI (TC-RNTI). For example, when determining whether the NDI in the PDCCH corresponding to the C-RNTI is toggled, the MAC entity may ignore the NDI in the PDCCH corresponding to the TC-RNTI. A toggled NDI may mean that the NDI is toggled compared to the value in the previous transmission.

[0252] The SPS may be configured (or provided) by higher layer parameters. The SPS may be configured by the RRC layer for each BWP in one serving cell. For example, the SPS may be provided by the RRC layer for each BWP in one serving cell. Multiple downlink assignments may be configured and activated in one BWP. The activation and deactivation of the SPS may be independent among multiple serving cells. For example, when a first SPS in a first serving cell is activated, a second SPS in a second serving cell may be activated or deactivated.

[0253] Activation of SPS may mean that a configured downlink assignment is activated. Activation of SPS may mean that a configured downlink assignment is activated. Activation of SPS may mean that SPS activation is indicated. Activation of SPS may mean that a configured downlink assignment is started (or resumed, or stored). Activation of SPS may mean that verification of an activated PDCCH is achieved. Activation of SPS may mean that a special field in a DCI format has a specific value and verification of the DCI format is achieved. Activation of SPS may mean that an SPS PDSCH is activated. Activation of SPS may mean that a PDSCH is activated.

[0254] Deactivation of SPS may be deactivation of a configured downlink assignment. Deactivation of SPS may be deactivation of a configured downlink assignment. Deactivation of SPS may be indicating SPS deactivation. Deactivation of SPS may be clearing or releasing a configured downlink assignment. Deactivation of SPS may be verification of a deactivated PDCCH. Deactivation of SPS may be verification of a special field in a DCI format having a specific value and verification of the DCI format. Deactivation of SPS may be deactivation of an SPS PDSCH. Deactivation of SPS may be deactivation of a PDSCH.

[0255] The configured downlink assignment may be a downlink SPS assignment. The configured downlink assignment may be a downlink assignment for an SPS PDSCH.

[0256] The SPS PDSCH may be a PDSCH without a corresponding PDCCH. The SPS PDSCH may be a PDSCH without a corresponding PDCCH transmission. The SPS PDSCH may be an activated PDSCH. The PDSCH may be received without a corresponding PDCCH transmission. The SPS PDSCH may be a PDSCH scheduled by a configured downlink assignment. The SPS PDSCH may be a PDSCH whose transmission is instructed by a configured downlink assignment. The SPS PDSCH may be a PDSCH using the higher layer parameter sps-Config. The SPS PDSCH may be a PDSCH activated by DCI format 1_1 or DCI format 1_2. The SPS PDSCH may be a PDSCH scheduled using sps-Config without a corresponding PDCCH transmission. The SPS PDSCH may be a PDSCH activated by DCI format 4_2. The SPS PDSCH may be a PDSCH with SPS.

[0257] The SPS PDSCH configuration may be a higher layer parameter SPS-Config. The SPS PDSCH configuration may be a configuration for the SPS.

[0258] The periodicity for the SPS PDSCH may be the periodicity in the SPS PDSCH configuration. The periodicity for the SPS PDSCH may be the periodicity of the configured downlink assignment. The periodicity for the SPS PDSCH may be the periodicity for the SPS. The periodicity for the SPS PDSCH may be the higher layer parameter periodicity or the value of the higher layer parameter periodicity. The periodicity for the SPS PDSCH may be a value provided in the DCI format.

[0259] In SPS, one downlink assignment may be provided by the PDCCH, one downlink assignment may be stored based on physical layer signaling indicating activation, and one downlink assignment may be cleared based on physical layer signaling indicating deactivation.

[0260] For the SPS, one or more higher layer parameters may be configured. For example, the one or more higher layer parameters may include some or all of the following higher layer parameters. Furthermore, one SPS configuration may include some or all of the following higher layer parameters. Furthermore, an SPS PDSCH configuration may include some or all of the following higher layer parameters. cs-RNTI ·nrofHAQR-processes harq-ProcID-Offset periodicity

[0261] The higher layer parameter cs-RNTI may be the value of the RNTI for configured scheduling in the downlink and / or uplink. The cs-RNTI may be used for activation, deactivation, and retransmission.

[0262] The number of HARQ processes for the SPS may be provided by a higher layer parameter. For example, the higher layer parameter nrofHARQ-processes may provide the number of HARQ processes configured for the SPS. The HARQ processes may be managed by an HARQ entity. The terminal device 1 may allocate transport blocks and HARQ information received from the physical layer to HARQ processes indicated by the HARQ information.

[0263] An offset for the HARQ process ID may be provided by a higher layer parameter. For example, an offset used in deriving the HARQ process ID may be provided by a higher layer parameter. An offset for the HARQ process for SPS may be determined by a higher layer parameter. The higher layer parameter may be harq-ProcID-Offset.

[0264] The periodicity of the downlink assignment configured for the SPS may be configured by a higher layer parameter. The periodicity for the SPS may be configured by a higher layer parameter. The periodicity for the SPS PDSCH may be configured by a higher layer parameter. The periodicity of the downlink assignment configured may be configured by a higher layer parameter. "Configured by a higher layer parameter" may mean "provided by a higher layer parameter." "Configured by a higher layer parameter" may mean "determined based on a higher layer parameter." The periodicity may be based on a subcarrier spacing. The periodicity may be provided using the unit millisecond. The periodicity may be provided using a frame rate (FPS: Frames per second). The periodicity may be provided using the reciprocal of the frame rate. The periodicity may be an integer. The periodicity may be a real number. The periodicity may be equal to or less than 10 milliseconds. The periodicity may be updated by a DCI format. The periodicity may be indicated by a DCI format. The higher layer parameter may be an upper layer parameter periodicity.

[0265] The configuration for the SPS (or the PDSCH SPS configuration) may be indexed. One or more SPS configurations may be provided. The index of one or more SPS configurations may be configured by a higher layer parameter. The higher layer parameter may be sps-ConfigIndex. The higher layer parameter may be referred to as an SPS PDSCH configuration index.

[0266] After the downlink assignment for SPS is configured, the first downlink assignment may occur in a first slot. The first slot may be determined based on one or more factors, such as the number of slots in one radio frame (N frame,μ slot ). One or more elements may include a system frame number. One or more elements may include a slot number (slot index) in one radio frame. One or more elements may include a periodicity for SPS. One or more elements may include a higher layer parameter periodicity. Also, a second downlink assignment may occur in the second slot. The second slot is positioned at periodicity×N from the first slot. frame,μ slot The PDSCH transmitted by the second downlink assignment may be a retransmission of the PDSCH transmitted by the first downlink assignment.

[0267] The downlink assignment may be provided by the PDCCH. Alternatively, the downlink assignment may be received in the PDCCH. The downlink assignment may indicate that a DL-SCH is to be transmitted at one MAC entity. The downlink assignment may indicate that there is a transmission at the DL-SCL at the MAC entity. The downlink assignment may provide HARQ information.

[0268] The MAC entity may have any of the C-RNTI, Temporary C-RNTI, and CS-RNTI. The MAC entity may determine whether to consider the NDI to be toggled at each PDCCH occasion. A downlink assignment may be received on the PDCCH. The PDCCH may be the C-RNTI of the MAC entity or the PDCCH for the Temporary C-RNTI. A downlink assignment may be a downlink assignment for one PDCCH occasion and one serving cell. If a downlink assignment is the first downlink assignment for the Temporary C-RNTI, the MAC entity may consider the NDI to be toggled. If some or all of Condition 1, Condition 2, and Condition 3 are met, the MAC entity may consider the NDI to be toggled. If some or all of Condition 1, Condition 2, and Condition 3 are met, the MAC entity may not consider the value of the NDI. Condition 1 may be that a downlink assignment corresponds to the C-RNTI of the MAC entity. Condition 2 may be that the previous downlink assignment is a downlink assignment received for the MAC entity of the CS-RNT. Condition 3 may be that the previous downlink assignment is a downlink assignment to be configured. The previous downlink assignment may be indicated to the HARQ entity of the same HARQ process. The MAC entity may indicate the existence of a downlink assignment to the HARQ entity. The MAC entity may convey HARQ information to the HARQ entity.

[0269] The PDCCH may also be a PDCCH for the CS-RNTI of the MAC entity. If the NDI in the received HARQ information is 1, the MAC entity may consider that the NDI of a certain HARQ process is not toggled. Furthermore, the MAC entity may indicate the presence of a certain downlink assignment and the HARQ information to the HARQ entity. If the NDI in the received HARQ information is 0, the MAC entity may determine whether the PDCCH (or PDCCH contents) indicates SPS activation or SPS deactivation. If the PDCCH indicates SPS activation, the MAC entity may store the certain downlink assignment and the HARQ information as the configured downlink assignment. Furthermore, the MAC entity may start (or resume) the configured downlink assignment.

[0270] Furthermore, if the PDCCH indicates SPS deactivation, the MAC entity may clear the configured downlink assignment. Additionally, if the timeAlignmentTimer is running, the MAC entity may indicate a positive acknowledgment for SPS deactivation to the physical layer. The timeAlignmentTimer may control the period during which the MAC entity considers one or more serving cells, which may belong to the associated TAG. HARQ feedback may be transmitted in the one or more serving cells.

[0271] The MAC entity may perform the following operations for a serving cell and a configured downlink assignment. For example, if the first PDSCH period of a configured downlink assignment does not overlap with the second PDSCH period of a downlink assignment received on the PDCCH, the MAC entity may instruct the physical layer to receive a transport block (TB) on the DL-SCH according to the configured downlink assignment in the first PDSCH period. The MAC entity may then transmit the transport block to the HARQ entity. The MAC entity may then set the HARQ process ID to the HARQ process ID associated with the first PDSCH period. The MAC entity may then consider the NDI bit corresponding to the HARQ process to be toggled. The MAC entity may then indicate the existence of the configured downlink assignment to the HARQ entity and deliver stored HARQ information to the HARQ entity. The configured downlink assignment may be activated. Considering the NDI bit to be toggled may be considering the NDI to be toggled.

[0272] The HARQ process ID for the configured downlink assignment may be determined based on Equation 1. The HARQ process ID for the SPS may be determined based on Equation 1. P1 is the number of slots in one radio frame (N frame,μ slot ) P2 may be configured by a higher layer parameter. For example, P2 may be configured by the higher layer parameter periodicity. P3 may be configured by a higher layer parameter. For example, P3 may be configured by the higher layer parameter nrofHARQ-Processes. CURRENT_slot may correspond to the slot where DL transmission starts. For example, CURRENT_slot may correspond to the SFN and N frame,μ slotand the slot index.

[0273]

number

[0274] The HARQ process ID for the configured downlink assignment may be determined based on Equation 2. The HARQ process ID for the SPS may be determined based on Equation 2. P1, P2, and P3 in Equation 2 may be the same as P1, P2, and P3 in Equation 1, respectively. P4 may be set by a higher layer parameter. For example, P4 may be the higher layer parameter harq-ProcId-Offset.

[0275]

number

[0276] The SPS of this embodiment will be described below. Fig. 9 is a diagram showing a flow for explaining an example of the SPS in this embodiment. The processing in Fig. 9 may be executed by the radio resource control layer processing unit 16 or the MAC entity (MAC layer) of the terminal device 1.

[0277] In 900, the terminal device 1 receives a downlink assignment for the SPS, configures or stores the downlink assignment for the SPS, and proceeds to 902. The configured or stored downlink assignment is also referred to as a configured downlink assignment. The terminal device 1 may receive the downlink assignment for the SPS using a PDCCH addressed to the CS-RNTI.

[0278] After the downlink assignment is set for SPS, in 902, the terminal device 1 sequentially assumes that the Nth downlink assignment occurs in the downlink slot that satisfies the following equation 3, and proceeds to 904.

[0279]

number

[0280] N SFN is the SFN (System Frame Number), which is the number of the radio frame. slot is the slot number in the radio frame. SFN_start_SPS and N slot_start_SPS is the SFN and slot of the first transmission of the PDSCH from which the configured downlink assignment begins. periodicity_SPS is a parameter configured by the RRC, and is the periodicity of the configured downlink assignment for SPS. The configured downlink assignment may be implicitly reused according to the periodicity defined by the RRC.

[0281] In 904, the terminal device 1 determines whether the PDSCH period of the downlink assignment to be set overlaps with the PDSCH period of the downlink assignment received on the PDCCH. If the terminal device 1 determines in 904 that the PDSCH period of the downlink assignment to be set does not overlap with the PDSCH period of the downlink assignment received on the PDCCH, the terminal device 1 proceeds to 906. If the terminal device 1 determines in 904 that the PDSCH period of the downlink assignment to be set overlaps with the PDSCH period of the downlink assignment received on the PDCCH, the terminal device 1 proceeds to 908.

[0282] At 906, the terminal device 1 attempts to decode the transport block received during the PDSCH period of the downlink assignment to be set. That is, if at 904 the terminal device 1 determines that the PDSCH period of the downlink assignment to be set overlaps with the PDSCH period of the downlink assignment received on the PDCCH, the terminal device 1 does not need to attempt to decode the transport block in the PDSCH corresponding to the downlink assignment to be set. That is, if the terminal device 1 cannot find a PDCCH addressed to the C-RNTI, downlink transmission according to the downlink assignment to be set is assumed. Also, if the terminal device 1 finds a PDCCH (downlink assignment) addressed to the C-RNTI, the assignment of the PDCCH (downlink assignment) addressed to the C-RNTI overwrites the downlink assignment to be set.

[0283] FIG. 10 is a diagram showing a detailed example of 906 of this embodiment. 906 may include some or all of 906a to 906g. The terminal device 1 may sequentially execute the processes starting from 906a. In 906a, the terminal device 1 may instruct the physical layer to receive a transport block on the DL-SCH according to the configured downlink assignment during the PDSCH period of the configured downlink assignment, and may pass the transport block to the HARQ entity. In 906b, the terminal device 1 may set the HARQ process ID to the HARQ process ID associated with the PDSCH period. The HARQ process ID associated with the PDSCH period may be given based at least on the number of the slot including the PDSCH period. In 906c, the terminal device 1 considers the NDI bit to be toggled. In 906d, the terminal device 1 indicates the existence of the configured downlink assignment to the HARQ entity, and passes HARQ information to the HARQ entity.

[0284] 906e may be processed by an HARQ entity included in the MAC entity of the terminal device 1. The HARQ entity manages the HARQ process. In 906e, the terminal device 1 may allocate the transport block and HARQ information received from the physical layer to the HARQ process indicated by the HARQ information.

[0285] Steps 906f and 906g may be processed by the HARQ process of terminal device 1. At step 906f, terminal device 1 attempts to decode the received transport block. At step 906g, terminal device 1 instructs the physical layer to generate a HARQ-ACK for the data in the transport block.

[0286] In 908, the terminal device 1 determines whether deactivation (release) of SPS has been instructed. If in 908 the terminal device 1 determines that deactivation (release) of SPS has been instructed, the terminal device 1 proceeds to 910 and clears the downlink assignment to be set. If in 908 the terminal device 1 determines that deactivation (release) of SPS has not been instructed, the terminal device 1 proceeds to 902.

[0287] In each serving cell, one or more PDSCHs may be transmitted without a corresponding PDCCH transmission. If a first one or more PDSCHs without a corresponding PDCCH are present in one slot, the terminal device 1 may receive a second one or more PDSCHs based on some or all of Order 0, Order 1, Order 2, and Order 3. The second one or more PDSCHs may be some or all of the first one or more PDSCHs. The second one or more PDSCHs may be one or more PDSCHs after resolving overlap with OFDM symbols in a slot designated as UL (UL slot). Order 0 may mean that j is set to 0. j may be the number of PDSCHs selected for decoding. Q may be a set of activated PDSCHs. An activated PDSCH may be a PDSCH without a corresponding PDCCH transmission in one slot. Order 1 may mean that the terminal device 1 receives one PDSCH. One PDSCH may have the lowest index among one or more indexes in set Q. The one or more indexes may be indexes set by a higher layer parameter. The one or more indexes may be indexes set by a higher layer parameter sps-ConfigIndex. Furthermore, Order 1 may be setting j to j+1. Furthermore, Order 1 may be designating one received PDSCH as a survivor PDSCH. Order 2 may be removing the surviving PDSCH in Order 1 and PDSCHs that overlap with the surviving PDSCH in Order 1 from Set Q. Order 3 may be repeating Order 1 and Order 2 until Set Q is empty. Furthermore, Order 3 may be repeating Order 1 and Order 2 until j is equal to the first number. The first number may be the number of PDSCHs (or unicast / multicast PDSCHs) in one slot.

[0288] The terminal device 1 may validate the PDCCH for SPS. Validating the PDCCH may be validating the DCI format. For example, the terminal device 1 may validate the PDCCH to schedule activation or deactivation (release). For example, the terminal device 1 may validate the PDCCH to simultaneously schedule activation and deactivation. The PDCCH may be a downlink SPS assignment PDCCH. If the CRC of the DCI format is scrambled with the CS-RNTI, the terminal device 1 may validate the PDCCH. The DCI format may be mapped to the PDCCH. If a New Data Indicator (NDI) field in the DCI format is set to 0, the terminal device 1 may validate the PDCCH. If a DFI flag field in the DCI format is set to 0, the terminal device 1 may validate the PDCCH. In case of validation for scheduling activation and if there is a PDSCH_HARQ feedback timing indication field in the DCI format, the PDSCH_HARQ feedback timing indication field may not provide an applicable value from the higher layer parameter dl-DataToUl-Ack-r16.

[0289] Verification of the DCI format may be achieved when one configuration (e.g., SPS-Config) is provided for the SPS PDSCH and when one or more fields in the DCI format are set to specific values. The one or more fields may be some or all of the HARQ process number field, the RV field, the MCS field, and the frequency domain resource allocation field. The one or more fields may be referred to as special fields. For example, verification of an activated PDCCH may be achieved when all values ​​in the HARQ process number field are zero and all values ​​in the RV field are zero. Verification of an activated PDCCH may be achieved when the PDCCH indicates SPS activation. For example, verification of a deactivated PDCCH may be achieved when all values ​​in the HARQ process number field are zero, all values ​​in the RV field are zero, all values ​​in the MCS field are one, and the frequency allocation field is all zeros or all ones. Verification of a deactivated PDCCH may be achieved when the PDCCH indicates SPS deactivation. Achieving verification of the PDCCH may also be achieving verification of the DCI format.

[0290] When multiple configurations (e.g., multiple SPS-Configs) are provided for the SPS PDSCH, the value of the HARQ Process Number field may indicate activation for the SPS PDSCH configuration having the first same value (or index). The first same value may be provided by a higher layer parameter. For example, the higher layer parameter may be sps-ConfigIndex. That is, verification of the PDCCH (or DCI format) may be performed for one or more configurations for the SPS PDSCH. The one or more configurations may have the first same value. Verification of the DCI format may be achieved when one or more fields in the DCI format are set to specific values. The one or more fields may be some or all of the RV field, MCS field, and frequency domain resource allocation field. The one or more fields may be referred to as a special field. For example, verification of the activated PDCCH may be achieved when the values ​​of the RV field are all 0. For example, verification of a released PDCCH may be achieved when the values ​​of the RV field are all 0s, the values ​​of the MCS field are all 1s, and the values ​​of the frequency domain resource allocation field are all 0s or all 1s. Achieving verification of the PDCCH may also mean achieving verification of the DCI format.

[0291] For example, if the HARQ process number field indicates a first HARQ process ID, DCI format verification may be achieved for a first SPS PDSCH configuration (or an SPS PDSCH and a configured downlink assignment) corresponding to the first HARQ process ID and a second SPS PDSCH configuration (or an SPS PDSCH and a configured downlink assignment) corresponding to the first HARQ process ID. The HARQ process number field may be used to determine the HARQ process ID. The HARQ process ID for the SPS PDSCH may be the HARQ process ID for the configured downlink assignment. Correspondence of the HARQ process ID to the SPS PDSCH may mean that the HARQ process ID corresponds to the SPS PDSCH configuration. Correspondence of the HARQ process ID to the SPS PDSCH may mean that the HARQ process ID corresponds to the downlink assignment to which the HARQ process ID is configured.

[0292] If multiple SPS PDSCH configurations (e.g., multiple SPS-Configs) are provided, and if the higher layer parameter sps-ConfigDeactivationStateList is provided, the value of the HARQ Process Number field may indicate a corresponding entry to schedule deactivation of the first one or more SPS PDSCH configurations. That is, the corresponding entry may identify the first one or more SPS PDSCHs from the multiple SPS PDSCH configurations. If multiple SPS PDSCH configurations are provided, and the higher layer parameter sps-ConfigDeactivationStateList is not provided, the value of the HARQ Process Number field may indicate deactivation for the SPS PDSCH configuration having the value provided by sps-ConfigIndex if the values ​​of the RV field are all zeros, the values ​​of the MCS field are all ones, and the values ​​of the Frequency Domain Resource Allocation field are all zeros or all ones. Verification of the DCI format (or deactivated PDCCH) may be achieved.

[0293] Achieving either verification of an activated PDCCH or verification of a deactivated PDCCH may be considered to be achievement of PDCCH verification (or DCI format verification). If the verification is achieved, the information in the DCI format may be regarded as valid activation or valid release of the SPS. If the verification is not achieved, the terminal device 1 may discard all information in the DCI format.

[0294] As a problem, a parameter in the SPS PDSCH configuration (e.g., a period for SPS) needs to be dynamically changed according to traffic and jitter in order to perform communication efficiently. For example, means 1 and means 2 may be used to solve the problem.

[0295] 11 is a diagram illustrating an example of SPS PDSCH reception with different cycles based on a PDCCH according to one aspect of the present embodiment. In FIG. 11, a PDSCH 1100 may be received, a PDSCH 1101 may be received, a PDSCH 1102 may be received, or a PDSCH 1103 may be received. Also, a PDCCH 1110 may be received. The PDSCH 1100, the PDSCH 1101, the PDSCH 1102, and the PDSCH 1103 may be SPS PDSCHs. That is, the PDSCH 1100 may be the SPS PDSCH 1100, the PDSCH 1101 may be the SPS PDSCH 1101, the PDSCH 1102 may be the SPS PDSCH 1102, and the PDSCH 1103 may be the SPS PDSCH 1103. The cycle 1120 may be different from the cycle 1121. PDSCH 1101 may be received 1120 periods after the end of PDSCH 1100. PDSCH 1101 may be received 1120 periods after PDSCH 1100. PDSCH 1102 may be received 1121 periods after the end of PDSCH 1102. PDSCH 1103 may be received 1121 periods after PDSCH 1102. Periods 1120 and 1121 may be P2 in Equation 1. Periods 1120 and 1121 may be N in Equation 3. periodicity_SPS may be.

[0296] 11, the HARQ process IDs for PDSCH 1100, PDSCH 1101, PDSCH 1102, and PDSCH 1103 may be the same, and the HARQ process IDs for PDSCH 1100 and PDSCH 1101 may be different from the HARQ process IDs for PDSCH 1102 and PDSCH 1103.

[0297] 11, the PDCCH 1110 may be a PDCCH for the PDSCH 1102. For example, the PDCCH 1110 may correspond to the PDSCH 1102.

[0298] In the means 1, downlink assignments configured for the PDSCH 1100 and the PDSCH 1101 may be deactivated by the PDCCH 1110 (or the DCI format in the PDCCH 1110). The PDSCH 1100 and the PDSCH 1101 may be deactivated by the PDCCH 1110 (or the DCI format in the PDCCH 1110). In the means 1, downlink assignments configured for the PDSCH 1102 and the PDSCH 1103 may be activated by the PDCCH 1110 (or the DCI format in the PDCCH 1110). The PDSCH 1102 and the PDSCH 1103 may be activated by the PDCCH 1110 (or the DCI format in the PDCCH 1110).

[0299] In the first means, the PDSCH 1100 and the PDSCH 1101 may correspond to a first configured downlink assignment. The PDSCH 1100 and the PDSCH 1101 may correspond to a first SPS PDSCH configuration. The PDSCH 1102 and the PDSCH 1103 may correspond to a second configured downlink assignment. The PDSCH 1102 and the PDSCH 1103 may correspond to a second SPS PDSCH configuration. The first SPS PDSCH configuration may be different from the second SPS PDSCH configuration. For example, the periodicity in the first SPS PDSCH configuration may be different from the periodicity in the second SPS PDSCH configuration. For example, the index in the first SPS PDSCH configuration may be different from the index in the second SPS PDSCH configuration. The periodicity in the first SPS PDSCH configuration may be period 1120. The periodicity in the second SPS PDSCH configuration may be period 1121.

[0300] In means 1, at time 1130, PDSCH 1100 and PDSCH 1101 may be activated, and PDSCH 1102 and PDSCH 1103 may be deactivated. At time 1131, PDSCH 1100 and PDSCH 1101 may be deactivated, and PDSCH 1102 and PDSCH 1103 may be activated.

[0301] In the first means, the CRC of the DCI format in the PDCCH 1110 may be scrambled by the CS-RNTI. Alternatively, the CRC of the DCI format in the PDCCH 1110 may not be scrambled by the CS-RNTI.

[0302] The means 1 may achieve verification of the PDCCH 1110 (or a DCI format in the PDCCH 1110). For example, verification of an activated and deactivated PDCCH 1110 may be achieved. For example, when a specific field in the DCI format in the PDCCH 1110 has a specific value, verification of the DCI format corresponding to the activated and deactivated PDCCH 1110 may be achieved.

[0303] In the means 1, the PDCCH 1110 (or content of the PDCCH 1110) may indicate SPS activation and SPS deactivation. For example, the PDCCH 1110 (or content of the PDCCH 1110) may indicate activation of a first SPS and deactivation of a second SPS. When activation of the first SPS is indicated, the first MAC entity may store a configured downlink assignment corresponding to the first SPS. When deactivation of the second SPS is indicated, the first MAC entity may clear a configured downlink assignment corresponding to the second SPS. In the means 1, when NDI in the HARQ information is 0, it may be determined whether the PDCCH 1110 (or content of the PDCCH 1110) indicates SPS activation and / or SPS deactivation.

[0304] In the means 1, a plurality of SPS PDSCH configurations may be provided. A first higher layer parameter may be configured in a first SPS PDSCH configuration. A second higher layer parameter may be configured in a second SPS PDSCH configuration. The first higher layer parameter may determine a periodicity of the first SPS PDSCH. The second higher layer parameter may determine a periodicity of the second SPS PDSCH. An SPS PDSCH configuration index in the first SPS PDSCH configuration may be different from an SPS PDSCH configuration index in the second SPS PDSCH configuration.

[0305] The means 1 may receive a PDCCH in which a DCI format is configured. A first SPS PDSCH may be activated based at least on the PDCCH (or the DCI format). A second SPS PDSCH may be deactivated based at least on the PDCCH (or the DCI format). A periodicity of the first SPS PDSCH may be different from a periodicity of the second SPS PDSCH.

[0306] In the first means, HARQ-ACK information does not need to be provided in response to deactivation of the SPS PDSCH.

[0307] In the means 1, a first higher layer parameter may determine a periodicity of at least a first SPS PDSCH. A second higher layer parameter may determine a periodicity of at least a second SPS PDSCH. The first SPS PDSCH may be deactivated by a DCI format. The second SPS PDSCH may be activated by the DCI format. The periodicity of the first SPS PDSCH may be different from the periodicity of the second SPS PDSCH. The second SPS PDSCH may be received, or the first SPS PDSCH may not be received, based on the second higher layer parameter.

[0308] In the means 1, an SPS PDSCH configuration index corresponding to the first SPS PDSCH or the second SPS PDSCH may be indicated based on at least one DCI field included in the DCI format. For example, in the means 1, verification of the DCI format may not be achieved.

[0309] In the means 2, the downlink assignments configured for the PDSCH 1100 and the PDSCH 1101 by the PDCCH 1110 (or the DCI format in the PDCCH 1110) may not be deactivated. The PDSCH 1100 and the PDSCH 1101 may not be deactivated by the PDCCH 1110 (or the DCI format in the PDCCH 1110). In the means 2, the downlink assignments configured for the PDSCH 1102 and the PDSCH 1103 may be activated by the PDCCH 1110 (or the DCI format in the PDCCH 1110). The PDSCH 1102 and the PDSCH 1103 may be activated by the PDCCH 1110 (or the DCI format in the PDCCH 1110).

[0310] In the second means, the PDSCH 1100 and the PDSCH 1101 may correspond to a first configured downlink assignment. The PDSCH 1100 and the PDSCH 1101 may correspond to a first SPS PDSCH configuration. The PDSCH 1102 and the PDSCH 1103 may correspond to a second configured downlink assignment. The PDSCH 1102 and the PDSCH 1103 may correspond to a second SPS PDSCH configuration. The first SPS PDSCH configuration may be the same as the second SPS PDSCH configuration. For example, the periodicity in the first SPS PDSCH configuration may be the same as the periodicity in the second SPS PDSCH configuration. For example, the index in the first SPS PDSCH configuration may be the same as the index in the second SPS PDSCH configuration. The periodicity in the first SPS PDSCH configuration may be period 1120. The period in the second SPS PDSCH configuration may or may not be period 1121. In the second means, period 1120 and period 221 may be different.

[0311] In means 2, at time 1130, PDSCH 1100 and PDSCH 1101 may be activated, and PDSCH 1102 and PDSCH 1103 may be activated or deactivated. At time 1131, PDSCH 1100 and PDSCH 1101 may not be deactivated, and PDSCH 1102 and PDSCH 1103 may be activated.

[0312] In the means 2, the CRC of the DCI format in the PDCCH 1110 may be scrambled by the CS-RNTI. Also, the CRC of the DCI format in the PDCCH 1110 does not have to be scrambled by the CS-RNTI.

[0313] In the means 2, verification of the PDCCH 1110 (or the DCI format in the PDCCH 1110) may be achieved. For example, verification of an activated PDCCH 1110 may be achieved. For example, if a specific field in the DCI format in the PDCCH 1110 has a specific value, verification of the DCI format corresponding to activation may be achieved.

[0314] In the second means, the SPS PDSCH configuration indexes corresponding to the PDSCH 1100, the PDSCH 1101, the PDSCH 1102, and the PDSCH 1103 may be the same.

[0315] In the means 2, the PDCCH 1110 (or the content of the PDCCH 1110) may indicate SPS activation. For example, the PDCCH 1110 (or the content of the PDCCH 1110) may indicate activation of a first SPS. When activation of the first SPS is indicated, the first MAC entity may store a configured downlink assignment corresponding to the first SPS. In the means 2, when NDI in the HARQ information is 0, it may be determined whether the PDCCH 1110 (or the content of the PDCCH 1110) indicates SPS activation or SPS deactivation.

[0316] In the means 2, the period 1121 may be determined by the PDCCH 1110 (or the DCI format of the PDCCH 1110). For example, the period 1120 may be updated to the period 1121 by the PDCCH 1110 (or the DCI format of the PDCCH 1110). For example, the period of the SPS PDSCH may be determined by the PDCCH 1110 (or the DCI format of the PDCCH 1110). For example, the period of the downlink assignment to be set corresponding to the PDSCH 1102 may be determined by the PDCCH 1110 (or the DCI format of the PDCCH 1110). For example, the period of the SPS PDSCH corresponding to the PDSCH 1102 may be determined by the PDCCH 1110 (or the DCI format of the PDCCH 1110).

[0317] The means 2 may provide one or more SPS PDSCH configurations. A first higher layer parameter may be configured in the first SPS PDSCH configuration. A second higher layer parameter may be configured in the second SPS PDSCH configuration. The first higher layer parameter may determine a periodicity of the first SPS PDSCH. The second higher layer parameter may not determine a periodicity of the second SPS PDSCH. The first SPS PDSCH configuration and the second SPS PDSCH configuration may be the same. The first higher layer parameter may be the same as the second higher layer parameter. The periodicity of the second SPS PDSCH may be indicated by a DCI format. An SPS PDSCH configuration index in the first SPS PDSCH configuration may be the same as an SPS PDSCH configuration index in the second SPS PDSCH configuration.

[0318] The means 2 may receive a PDCCH in which a DCI format is configured. The first SPS PDSCH may be activated based at least on the PDCCH (or the DCI format). The second SPS PDSCH may be deactivated based at least on the PDCCH (or the DCI format). The periodicity of the first SPS PDSCH may be different from the periodicity of the second SPS PDSCH.

[0319] In the means 2, a first periodicity of the SPS PDSCH may be determined based at least on a certain higher layer parameter. A second periodicity of the SPS PDSCH may be determined based at least on a DCI format. The SPS PDSCH may be received based on the second periodicity. The first periodicity may be different from the second periodicity. Two periods of the SPS PDSCH may be provided.

[0320] Various aspects of the device according to one aspect of this embodiment will be described below.

[0321] (1) In order to achieve the above object, aspects of the present invention provide the following measures: That is, a first aspect of the present invention is a terminal device including a receiver that receives a DCI format, wherein a first higher layer parameter determines a periodicity of at least a first SPS PDSCH, a second higher layer parameter determines a periodicity of at least a second SPS PDSCH, the first SPS PDSCH is deactivated by the DCI format and the second SPS PDSCH is activated by the DCI format, the periodicity of the first SPS PDSCH is different from the periodicity of the second SPS PDSCH, and the receiver receives the second SPS PDSCH based on the second higher layer parameter.

[0322] (2) A second aspect of the present invention is a terminal device including a receiving unit that receives a DCI format, wherein a first period of an SPS PDSCH is determined based at least on a certain upper layer parameter, and a second period of the SPS PDSCH is determined based at least on the DCI format, and the receiving unit receives the SPS PDSCH based on the second period.

[0323] (3) A third aspect of the present invention is a base station device including a transmitter that transmits a DCI format, wherein a first higher layer parameter determines a periodicity of at least a first SPS PDSCH, a second higher layer parameter determines a periodicity of at least a second SPS PDSCH, the first SPS PDSCH is deactivated by the DCI format, the second SPS PDSCH is activated by the DCI format, the periodicity of the first SPS PDSCH is different from the periodicity of the second SPS PDSCH, and the transmitter transmits the second SPS PDSCH based on the second higher layer parameter.

[0324] (4) A fourth aspect of the present invention is a base station device including a transmitter that transmits a DCI format, wherein a first period of an SPS PDSCH is determined based at least on a certain upper layer parameter, a second period of the SPS PDSCH is determined based at least on the DCI format, and the transmitter transmits the SPS PDSCH based on the second period.

[0325] The programs operating in the base station device 3 and terminal device 1 according to the present invention may be programs (programs that cause a computer to function) that control a CPU (Central Processing Unit) or the like so as to realize the functions of the above-described embodiments according to the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.

[0326] Note that the terminal device 1 and part of the base station device 3 in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize the function.

[0327] The term "computer system" used 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 term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system.

[0328] 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, or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

[0329] Furthermore, the base station device 3 in the above-described embodiment can also be realized as a collection (device group) consisting of multiple 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 a collection.

[0330] Furthermore, the base station device 3 in the above-described embodiments may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or an NG-RAN (NextGen RAN, NR RAN). Furthermore, the base station device 3 in the above-described embodiments may have some or all of the functions of an upper node for an eNodeB and / or a gNB.

[0331] Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chipset. 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. Furthermore, the integrated circuit method is not limited to LSI, and may be realized using a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.

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

[0333] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications 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 substituted with elements that achieve the same effect are also included. [Explanation of symbols]

[0334] 1(1A, 1B, 1C) Terminal equipment 3 Base station equipment 10, 30 Radio transmitter / receiver 10a, 30a Radio 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 Medium 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 700 Set of resource elements for 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 1100, 1101, 1102, 1103 PDSCH 1110 PDCCH 1120, 1121 period 1130, 1131 hours

Claims

1. a receiving unit for receiving a DCI format; The first higher layer parameter determines a periodicity of at least the first SPS PDSCH; The second higher layer parameter determines a periodicity of at least the second SPS PDSCH; the first SPS PDSCH is deactivated by the DCI format; the second SPS PDSCH is activated by the DCI format; The DCI format indicates one HARQ process ID; the HARQ process ID corresponds to both the first SPS PDSCH and the second SPS PDSCH; a period of the first SPS PDSCH is different from a period of the second SPS PDSCH; The receiving unit receives the second SPS PDSCH based on the second higher layer parameter. Terminal device.

2. An SPS PDSCH configuration index corresponding to the first SPS PDSCH or the second SPS PDSCH is indicated based on at least one DCI field included in the DCI format. The terminal device according to claim 1 .

3. a transmitter for transmitting a DCI format; The first higher layer parameter determines a periodicity of at least the first SPS PDSCH; The second higher layer parameter determines a periodicity of at least the second SPS PDSCH; the first SPS PDSCH is deactivated by the DCI format; the second SPS PDSCH is activated by the DCI format; The DCI format indicates one HARQ process ID; the HARQ process ID corresponds to both the first SPS PDSCH and the second SPS PDSCH; a period of the first SPS PDSCH is different from a period of the second SPS PDSCH; The transmitter transmits the second SPS PDSCH based on the second higher layer parameter. Base station equipment.

4. An SPS PDSCH configuration index corresponding to the first SPS PDSCH or the second SPS PDSCH is indicated based on at least one DCI field included in the DCI format. The base station device according to claim 3 .

Images