Terminal and communication method
The terminal postpones acknowledgement transmissions to resolve overlapping issues in SBFD systems, enhancing system efficiency by optimizing resource use in SBFD environments.
Patent Information
- Application Number
- JP2025019617
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-07
- Publication Date
- 2025-10-14
AI Technical Summary
In wireless communication systems, the transmission of Hybrid Automatic Repeat request Acknowledgement (HARQ-ACK) for Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) is hindered when its timing overlaps with Synchronization Signal Block (SSB) or Control Resource SET (CORESET) symbols, leading to reduced system utilization efficiency, and the use of subband non-overlapping full duplex (SBFD) complicates resource control for PUCCH transmission.
A terminal is designed to postpone the transmission of acknowledgement responses until the next available slot that does not overlap with conflicting resources, ensuring efficient use of SBFD symbols and non-SBFD symbols.
This approach enhances system utilization efficiency by avoiding conflicts and optimizing resource allocation in SBFD environments, thereby improving communication performance.
Smart Images

Figure 2025155883000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a terminal and a communication method. [Background technology]
[0002] 3GPP (registered trademark) has established specifications for the 5th generation mobile communication system (also known as 5G, New Radio (NR) or Next Generation (NG)), and is also working on specifications for the next generation mobile communication system, known as Beyond 5G, 5G Evolution, or 6G.
[0003] Release 18 discusses a duplexing scheme that enables simultaneous use of the downlink (DL) and uplink (UL) by utilizing multiple subbands that make up a time division duplexing (TDD) band. This duplexing scheme is called subband non-overlapping full duplex (SBFD). Note that symbols to which SBFD is applied may also be called SBFD symbols. In addition, in SBFD symbols, subbands used for DL may also be called DL subbands, and subbands used for UL may also be called UL subbands.
[0004] Furthermore, in preparation for Release 19, extensions regarding UL transmission and DL reception using SBFD symbols and non-SBFD symbols are being considered (Non-Patent Document 1). [Prior art documents] [Non-patent literature]
[0005] [Non-Patent Document 1] “New WID: Evolution of NR duplex operation: Subband full duplex (SBFD)”, RP-234035, 3GPP TSG RAN Meeting #102, 3GPP, December 11-15, 2023 [Non-patent document 2] 3GPP TS 38.214 V18.3.0 (2024-06) [Non-patent document 3] 3GPP TS 38.300 V18.2.0 (2024-06) [Non-patent document 4] 3GPP TS 38.331 V18.1.0 (2024-03) [Non-patent document 5] 3GPP TR 38.858 V18.1.0 (2024-03) [Non-patent document 6] 3GPP TR 38.213 V18.3.0 (2024-06) Summary of the Invention
[0006] When the transmission timing of a Hybrid Automatic Repeat request Acknowledgement (HARQ-ACK) for a Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) overlaps with the timing of a DL symbol, a Synchronization Signal Block (SSB) symbol, or a Control Resource SET (CORESET) #0 symbol, the transmission of the HARQ-ACK is stopped and the SPS-PDSCH corresponding to the HARQ-ACK is retransmitted, resulting in reduced system utilization efficiency. For this reason, a function that postpones the transmission timing of a HARQ-ACK for an SPS PDSCH until the next UL slot is supported as an SPS HARQ-ACK deferring function. It is assumed that the above-mentioned SBFD is also applied to this SPS PDSCH HARQ-ACK deferring function.
[0007] However, PUCCH (Physical Uplink Control Channel) resources within an SBFD symbol may or may not be usable for PUCCH transmission depending on whether they overlap with RBs (Resource Blocks) outside UL usable PRBs (Physical Resource Blocks). Therefore, in SPS HARQ-ACK postponement, resource control taking into account the UL usable PRBs remains an unresolved issue, and further study is required.
[0008] One aspect of the present disclosure is useful for a terminal that, when the transmission resource of the acknowledgement overlaps with other bandwidth resources, appropriately postpones the transmission of the acknowledgement until the next earliest transmission slot in which the transmission resource does not overlap with other resources.
[0009] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives a downlink signal configured by semi-static scheduling in either a first time unit in which the downlink and the uplink can be used simultaneously using multiple subbands that constitute a time division duplex band, or a second time unit in which either the downlink or the uplink can be used by applying the time division duplex band, and a control unit that controls the transmission of an acknowledgement response to the downlink signal, wherein if the transmission resource of the acknowledgement response overlaps with a resource outside the available subbands on the first time unit, the control unit postpones the transmission of the acknowledgement response until the next earliest transmission slot in which the transmission resource does not overlap with a resource on the first time unit or the second time unit. [Brief explanation of the drawings]
[0010] [Figure 1] 1 is a diagram illustrating an overall schematic configuration of a wireless communication system. [Figure 2] FIG. 1 illustrates frequency ranges used in wireless communication systems. [Figure 3] 1A to 1C are diagrams illustrating examples of the configuration of radio frames, subframes, slots, and symbols used in a radio communication system. [Figure 4A] FIG. 1 is a diagram illustrating an example of TDD settings defined up to Rel-16. [Figure 4B] FIG. 1 is a diagram illustrating an example of the configuration of SBFD. [Figure 5] FIG. 10 is a diagram illustrating an example of SBFD operation. [Figure 6A] FIG. 1 illustrates an example of an existing TDD configuration. [Figure 6B] A diagram showing an example of TDD including SBFD configuration. [Figure 7] A figure showing an example of SPS HARQ-ACK postponement operation in Rel-17 NR. [Figure 8] FIG. 1 is a diagram illustrating Configuration 1. [Figure 9] FIG. 10 is a diagram illustrating configuration 2. [Figure 10]FIG. 2 is a block diagram showing an example of the configuration of a base station. [Figure 11] FIG. 2 is a block diagram showing an example of the configuration of a terminal. [Figure 12] FIG. 2 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 13] FIG. 1 is a diagram illustrating an example of a configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION
[0011] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.
[0012] <Wireless communication system configuration> 1 is a wireless communication system conforming to a scheme called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.
[0013] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) by bundling them together, and Dual Connectivity (DC), which communicates with two base stations simultaneously. In this specification, "and / or" may be simply written as " / ".
[0014] As shown in FIG. 1, a wireless communication system 10 includes a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) constituting a Next Generation-Radio Access Network (NG-RAN) 20, and a terminal 200 (hereinafter also referred to as a user equipment (UE) 200) that performs wireless communication with the gNB 100. The NG-RAN 20 is connected to a core network (CN) (not shown). The CN is composed of multiple network functions (NFs). The NFs are, for example, an access and mobility management function (AMF) and a network data analytics function (NWDAF). The AMF performs, for example, registration of the UE 200. The NWDAF performs, for example, optimization of the CN. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1. The NG-RAN 20 and the CN may be simply referred to as a "network."
[0015] The gNB100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration having a distributed unit (DU) having a function for connecting to the UE200 and a central unit (CU) having a function for connecting to the network. In this case, the gNB100 may be read as a DU, a CU, or a DU and a CU. When read as a DU, the gNB100 may be called a gNB-DU. When read as a CU, the gNB100 may be called a gNB-CU. When read as a DU and a CU, the DU portion may be called a gNB-DU and the CU portion may be called a gNB-CU.
[0016] Furthermore, the wireless communication system 10 may support a plurality of frequency ranges (FRs). That is, as shown in FIG. 2, the wireless communication system 10 may support the following FRs: FR1: 410MHz~7.125GHz FR2-1: 24.25GHz~52.6GHz ·FR2-2: More than 52.6GHz~71GHz
[0017] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used, and in FR2-1, an SCS of 60 or 120 kHz (or 240 kHz) and a BW of 50 to 400 MHz may be used.
[0018] Note that SCS may be interpreted as numerology, which is defined in §5.1 of Non-Patent Document 3 and corresponds to one subcarrier interval in the frequency domain.
[0019] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.
[0020] Fig. 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in Fig. 3, one slot is made up of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.
[0021] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it may be 28 or 56 symbols, etc.) Furthermore, the number of slots per subframe may differ depending on the SCS.
[0022] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.
[0023] The wireless communication system 10 may support coverage enhancement (CE) that expands the coverage of a cell (or a physical channel) formed by the gNB 100. In coverage enhancement, a mechanism for increasing the success rate of reception of various physical channels, such as repetition of a physical random access channel (PRACH), may be provided.
[0024] For example, UE200 receives information related to the random access procedure from gNB100 as a downlink (DL) signal (e.g., SIB1 (System Information Block Type 1) etc.).
[0025] Furthermore, for example, the UE 200 transmits the PRACH as an UL signal to the gNB 100 using a RACH occasion, i.e., a RACH (transmission) opportunity (RO), which is a resource for transmitting a random access preamble. For example, the UE 200 repeats the PRACH as an UL signal to the gNB 100.
[0026] The UL signal may include, for example, a UL data signal and control information. For example, the UL signal may include information related to the processing capability of the UE 200 (e.g., UE capability). The UL signal may also include a reference signal.
[0027] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels may include a Physical Uplink Shared Channel (PUSCH), and the control channels may include a Physical Uplink Control Channel (PUCCH). For example, the UE 200 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel, and the PUCCH is an example of an uplink control channel. The shared channels may also be called data channels.
[0028] The reference signal included in the UL signal may include at least one of, for example, a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for positioning information. For example, reference signals such as the DMRS and PTRS are used to demodulate the UL data signal and are transmitted using the PUSCH.
[0029] Meanwhile, gNB100 transmits information related to the RACH procedure to UE200 as a DL signal (e.g., SIB1, etc.) in response to the operation of UE200.
[0030] Furthermore, for example, the gNB 100 receives, as an UL signal, a PRACH from the UE 200. For example, the gNB 100 receives, as an UL signal, a PRACH from the UE 200 in a repetition manner.
[0031] The channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channels may include a Physical Downlink Shared Channel (PDSCH), and the control channels may include a Physical Downlink Control Channel (PDCCH). For example, gNB100 transmits control information to UE200 using PDCCH and transmits DL data signals using PDSCH. Note that PDSCH is an example of a downlink shared channel, and PDCCH is an example of a downlink control channel. Note that PDCCH may be read by Downlink Control Information (DCI) transmitted in PDCCH, control information, etc.
[0032] The reference signals included in the DL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRSRS, and PRS for position information. For example, reference signals such as DMRS and PTRS are used for demodulating DL data signals and are transmitted using PDSCH.
[0033] [[ID=])]] Next, SBFD, CG (Configured Grant), codebook-based uplink transmission, non-codebook-based uplink transmission, and mTRP will be described.
[0034] <SBFD operation> Considering the transmission / reception time ratio (e.g., DL:UL=4:1) in Time Division Duplex (TDD) up to Rel-16, there may be cases where the number of transmission opportunities for UL signals / channels is fewer than the number of reception opportunities for DL signals / channels. In such cases, UE 200 cannot transmit UL signals / channels frequently, which raises concerns about transmission delays of important UL signals / channels. Furthermore, since there are fewer UL transmission opportunities compared to DL reception opportunities, there is also concern about signal / channel congestion during UL transmission opportunities. Furthermore, with TDD, the time resources available for transmitting UL signals / channels are limited, which limits the application of UL coverage extension techniques, such as repetition transmission.
[0035] In future wireless communication systems (for example, Rel-18 and later), the introduction of a time-frequency division duplexing method that combines TDD and frequency division duplexing (FDD) for UL and DL is being considered.
[0036] Examples of the time-frequency division duplexing method include XDD (Cross Division Duplex) and Subband Non-Overlapping Full Duplex (SBFD). XDD or SBFD may refer to a duplexing method that frequency-division multiplexes DL and UL within one component carrier (CC) in the TDD band (allowing DL and UL to be used simultaneously).
[0037] Figure 4A is a diagram showing an example of the TDD configuration defined up to Rel-16. In the example shown in Figure 4A, TDD slots or symbols are configured for a UE in a bandwidth such as one component carrier (CC) (which may also be called a cell or serving cell) or bandwidth portion (BWP).
[0038] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. This conventional TDD slot or symbol configuration does not ensure sufficient UL time resources, which can result in UL transmission delays and reduced coverage performance.
[0039] Fig. 4B is a diagram showing an example of the configuration of SBFD. In the example shown in Fig. 4B, within one component carrier (CC), resources used for DL reception and resources used for UL transmission overlap in time. With such a resource configuration, more UL resources can be secured, thereby improving resource utilization efficiency.
[0040] For example, as shown in the example of Figure 4B, both ends of the frequency domain may be set as DL resources, and UL resources may be sandwiched between these DL resources. This may prevent or mitigate cross link interference (CLI) with neighboring carriers. Also, a guard region may be set at the boundary between the DL resources and the UL resources.
[0041] Considering the complexity of handling self-interference, it may be considered that only the gNB 100 uses the DL resource and the UL resource simultaneously. That is, in radio resources where the DL and UL overlap in time, one UE 200 may use the DL resource and another UE 200 may use the UL resource.
[0042] Fig. 5 is a diagram showing an example of SBFD operation. In the example shown in Fig. 5, some of the DL resources of the TDD band are configured as UL resources, and the DL and UL are configured to partially overlap in the time domain.
[0043] In the example shown in FIG. 5, during the DL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) receives the DL channel / signal.
[0044] Furthermore, during a period in which DL and UL overlap in time, one UE 200 (UE1 in the example of FIG. 5) receives a DL channel / signal, and another UE 200 (UE2 in the example of FIG. 5) transmits a UL channel / signal. During this period, the gNB 100 performs simultaneous transmission and reception of DL and UL.
[0045] Furthermore, during the UL-only period, each of the multiple UEs 200 (UE1 and UE2 in FIG. 5) transmits a UL channel / signal.
[0046] In existing NR (e.g., those defined up to Rel-15 / 16 / 17), DL frequency resources and UL frequency resources in a UE carrier are configured as DL BWP and UL BWP, respectively. To switch DL / UL frequency resources to other DL / UL frequency resources, multiple BWP configurations and a BWP adaptation mechanism are required.
[0047] Figure 6A is a diagram showing an example of an existing TDD configuration. In Figure 6A, slots / symbols marked with "D" are DL slots / symbols, slots / symbols marked with "U" are UL slots / symbols, and slots / symbols marked with "F" are flexible (hereinafter also referred to as FL) slots / symbols. Note that similar notations may be used in the following figures.
[0048] In the existing NR, as shown in FIG. 6A, time resources (time units such as symbols and slots) in the TDD carrier for UE 200 are configured as at least one of DL, UL, and flexible (FL) in the TDD configuration.
[0049] Figure 6B is a diagram showing an example of an existing TDD configuration. In Figure 6B, slots / symbols or subbands marked with "D" are DL slots / symbols or DL subbands, and slots / symbols or subbands marked with "U" are UL slots / symbols or UL subbands. Note that similar notations may be used in the following figures.
[0050] As shown in FIG. 6B , the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL reception) on some frequency resources (subbands), and signaled or configured as DL (or UL) or for DL reception (or UL transmission) on other frequency resources (subbands). Alternatively, the SBFD symbol may be a symbol that is signaled or configured as UL (or DL) or for UL transmission (or DL reception) on a portion of frequency resources. Alternatively, the SBFD symbol may be a symbol that is signaled or configured as DL (or UL) or for DL reception (or UL transmission) on a portion of frequency resources.
[0051] Here, the time unit may be at the symbol level, slot / subslot level, or a group of symbols / slots / subslots, i.e., the SBFD time unit may be an SBFD symbol, a slot / subslot containing or overlapping an SBFD symbol, or a group of symbols / slots / subslots containing or overlapping an SBFD symbol.
[0052] A pure time unit may be a non-SBFD symbol (i.e., a symbol that is not an SBFD symbol, also called a non-SBFD symbol), a slot / sub-slot that does not contain or overlap an SBFD symbol, or a group of symbols / slots / sub-slots that do not contain or overlap an SBFD symbol, and may also be called a non-SBFD time unit.
[0053] As described above, SBFD may be applied to each slot / symbol. Note that each slot / symbol may be set to DL, UL, or Flexible (FL) that can be used as DL or UL, and then SBFD may be applied.
[0054] SBFD is a type of (full-duplex) duplexing scheme based on time division duplexing (TDD), enabling simultaneous use of multiple sub-bands that make up the TDD band. SBFD can be described as a duplexing scheme in which multiple sub-bands are specified within the TDD band, a duplexing scheme in which UL and DL are allocated non-overlapping in the frequency direction in the TDD time unit, or a duplexing scheme in which all two sub-bands are overlapped.
[0055] A symbol to which SBFD is applied is also called an SBFD symbol. "SBFD is applied" may be interpreted as SBFD being applied to at least a part of scheduling. In other words, a "symbol to which SBFD is applied" may be interpreted as a symbol to which SBFD is applied (SBFD symbol) in scheduling to which SBFD is applied. Also, a "time unit to which non-SBFD is applied" may be interpreted as a symbol to which SBFD is not applied (non-SBFD symbol) in scheduling to which SBFD is applied.
[0056] Furthermore, a UE that supports SBFD operation (SBFD-compatible UE) is referred to as an SBFD-aware UE or an SBFD-capable UE, and a UE that does not support SBFD operation is referred to as a legacy UE. For example, when SBFD is applied to a DL symbol, an SBFD-aware UE can recognize the UL subband (and DL subband) in this SBFD symbol, but a legacy UE recognizes this SBFD symbol as a normal DL symbol.
[0057] <SPS HARQ-ACK Deferring> In 3GPP, in Release 17, in order to improve system utilization efficiency, it was agreed to support the deferred transmission of HARQ-ACK (Hybrid Automatic Repeat request Acknowledgement) due to TDD collision for SPS (Semi-Persistent Scheduling) PDSCH.
[0058] When the transmission timing of HARQ-ACK for SPS PDSCH overlaps with the timing of DL symbols, SSB (Synchronization Signal Block) symbols, or CORESET (Control Resource SET) #0 symbols, the transmission of the HARQ-ACK is aborted, and the retransmission of the SPS-PDSCH corresponding to the HARQ-ACK is performed, resulting in a decrease in system utilization efficiency. To prevent this decrease in system utilization efficiency, the function of deferring the transmission timing of HARQ-ACK for SPS PDSCH until the next UL slot is supported as the SPS HARQ-ACK deferring function.
[0059] SPS HARQ-ACK Deferring Conditions: · Overlap with semi-static DL / SSB / CORESET #0 symbols · SPS HARQ-ACK deferring is valid in the SPS configuration The target slot / sub-slot is the first available slot / sub-slot where the determined PUCCH resource does not overlap with semi-static DL, SSB, or CORESET#0 symbols and satisfies the condition of "K1_max_def > K1+K_def". · K_def is the number of slots / sub-slots from the initial PUCCH slot to the target PUCCH slot. · K1_max_def is set for each SPS configuration index.
[0060] If a PUCCH using "SPS-PUCCH-AN-List-r16" or "n1PUCCH-AN" overlaps with a semi-static DL or SSB symbol, the SPS HARQ-ACK PUCCH (transmission of SPS HARQ-ACK) may be postponed.
[0061] Note that "SPS-PUCCH-AN-List-r16" is included in information (for example, PUCCH-Config) that sets PUCCH resource parameters for a terminal. "SPS-PUCCH-AN-List-r16" is an example of information that indicates a list of PUCCH resources for DL SPS HRQ-ACK. Also, "n1PUCCH-AN" is included in information (for example, SPS-Config) that is used to set DL semi-persistent transmission. "n1PUCCH-AN" is an example of information that indicates PUCCH HARQ resources for DL SPS.
[0062] The postponement of the SPS HARQ-ACK may be configured for each SPS configuration. The SPS-PDSCH is transmitted from the base station based on a period set by a higher layer. The SPS HARQ-ACK for the SPS PDSCH that can be postponed may be postponed.
[0063] A maximum deferral limitation may be set for each SPS configuration. For example, a condition may be set that "K1_max_def=K1+K_def" does not exceed a limit (e.g., maximum deferral limitation).
[0064] The slot in which the deferred SPS HARQ-ACK may be transmitted is called the target slot or the target PUCCH slot.
[0065] For example, the target slot is the first available slot in which the determined PUCCH resource does not overlap with invalid symbols (e.g., semi-static DL or SSB symbols). The determined PUCCH resource may correspond to the PUCCH resource used for transmitting the postponed SPS HARQ-ACK. Also, the first available slot may be the earliest slot in the time direction.
[0066] The target slot may be determined taking into consideration the multiplexing of SPS HARQ-ACK and dynamic HARQ-ACK.
[0067] After determining the target PUCCH slot, if the deferred SPS HARQ-ACK is not transmitted, the transmission of the deferred SPS HARQ-ACK bit may not be further deferred, in which case the deferred SPS HARQ-ACK bit may be dropped.
[0068] FIG. 7 is a diagram showing an example of postponement of SPS HARQ-ACK. The horizontal axis in FIG. 7 represents the time axis. Six slots are shown in FIG. 4 as an example. Note that, hereinafter, multiple slots may be referred to as the first slot, the second slot, etc., in order from the oldest slot (the left side of the figure). Each of the six slots is marked with "D" or "U." A slot marked with "D" indicates a DL slot, and a slot marked with "U" indicates a UL slot. The first slot includes SPS PDSCH#1.
[0069] Here, for example, a case will be described in which the postponement of SPS HARQ-ACK is enabled in the SPS configuration of SPS PDSCH#1, and the SPS HARQ-ACK for the SPS PDSCH can be transmitted in the second slot. Note that the fact that the SPS HARQ-ACK can be transmitted in the second slot may be equivalent to the information indicating the transmission slot of the SPS HARQ-ACK indicating transmission in the second slot. In this case, since the SPS HARQ-ACK overlaps with the semi-static DL in the second slot, the SPS HARQ-ACK PUCCH is postponed.
[0070] The slot in which the SPS HARQ-ACK for the SPS PDSCH can be transmitted (the second slot in FIG. 7) is specified by the parameter "K1." K1 indicates the offset from the data (e.g., SPS PDSCH) to the corresponding acknowledgment (e.g., SPS HARQ-ACK). In the case of FIG. 7, K1=1 is set for SPS PDSCH#1, indicating the second slot.
[0071] In the example of Figure 7, the fourth slot corresponds to the first available slot (target slot) that does not overlap with an invalid symbol (e.g., a semi-static DL or SSB symbol), so the HARQ-ACK bit (deferred HARQ-ACK bit) for SPS PDSCH#1 with SPS HARQ-ACK deferral enabled is transmitted in the target slot.
[0072] The conditions for the SPS HARQ-ACK postponement are defined as follows in §9.2.5.4 of Non-Patent Document 6:
[0073] (1)SPS HARQ-ACK postponement conditions "Overlap with the symbol indicated as the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, overlap with the symbol indicated as the SS / PBCH block by ssb-PositionsInBurst, or overlap with the symbol belonging to the CORESET associated with the Type0-PDCCH CSS set"
[0074] (2) Target slot / sub-slot determination condition "Not dropped due to overlap with high-priority PUSCH or PUCCH transmission, and does not overlap with any of the symbols indicated as the downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated, the symbols indicated as the SS / PBCH block by ssb-PositionsInBurst, or the symbols belonging to the CORESET associated with the Type0-PDCCH CSS set"
[0075] <Consideration of Duplex Extension for Rel-19> As described above, in Rel-18, studies have been conducted to enable the coexistence of downlink and uplink (full duplex, more specifically sub-band non-overlapping full duplex) on the gNB side within the conventional TDD band. Regarding SBFD, the impacts on specifications, performance evaluation results, implementation feasibility, and RF requirements are summarized in Non-Patent Document 5.
[0076] In Non-Patent Document 1, studies have been centered around the extension of sub-band non-overlapping full duplex (SBFD) operation on the gNB side within the TDD carrier. The objectives of the studies for Rel-19 are as follows. (1) Study on the specification of semi-static indication of the time position of SBFD subbands to UE in RRC_CONNECTED mode Indication of the time position of the SBFD subband in the SIB is not excluded (2) Study on the specification of semi-static indication of the frequency domain location of SBFD subbands to UE in RRC_CONNECTED mode Indication of the frequency domain location of SBFD subbands in the SIB is not excluded (3) Study on SBFD operation specifications to support random access of SBFD symbols by UE in RRC CONNECTED mode (4) Consider SBFD operation to support random access by UE in RRC_IDLE / INACTIVE mode and specify it if appropriate. ·Check whether standardization work will proceed in RAN#104 (5) Study on the specifications for the operation and procedures of SBFD-enabled UE (SBFD aware UE) transmission / reception and measurement of SBFD symbols and / or non-SBFD symbols. Transmit / receive operation in SBFD sub-bands configured for DL and / or flexible symbols as indicated by TDD-UL-DL-ConfigCommon UL transmission only in the UL sub-band DL reception only within DL sub-band (excluding CLI measurements by UE outside DL sub-band) Note: When flexible symbols are used, it is not expected that legacy uplink symbols will be converted to downlink / SBFD symbols. Enhanced resource allocation in the frequency domain for the following SBFD symbols: Frequency domain resource allocation for PDSCH / CSI-RS across two DL subbands in an SBFD symbol Handling misalignment of boundaries between SBFD subbands and resource block groups (RBGs), CSI report subbands, CSI-RS resources, and precoding resource block groups (PRGs) Enhancements for physical channels / signals and procedures spanning SBFD and non-SBFD symbols in different slots, where each transmission / reception within a slot includes either all SBFD symbols or all non-SBFD symbols, including: Resource allocation in the frequency domain when transmitting / receiving SBFD and non-SBFD symbols using different available frequency resources in different slots CSI reports for related CSI-RS instances occurring in both SBFD and non-SBFD symbols in different slots SRS, PUCCH and PUSCH configurations in SBFD and non-SBFD symbols (e.g., resources, frequency hopping parameters, UL power control parameters and / or beam / spatial relationships) Overlap processing between DL reception in DL sub-band and UL transmission in UL sub-band in SBFD symbols (6) Based on TR 38.858 (Non-Patent Document 5), the following is assumed: SBFD on the gNB side Half duplex operation on the UE side FR1 and FR2-1 SBFD operation option 4 (e.g., both the time and frequency location of the sub-bands for SBFD operation are known to the SBFD-capable UE) Coexistence of non-SBFD-capable UE (including legacy UE) and SBFD-capable UE in a cell where SBFD is operated on the gNB side SBFD method within a single DL and UL BWP pair with aligned center frequencies One UL subband for SBFD operation in SBFD symbols (excluding legacy UL symbols / slots) within a TDD carrier · The mechanism of SBFD operation needs to consider the coexistence of adjacent channels between two operators
[0077] <Transmission / reception spanning SBFD symbols and non-SBFD symbols> In §6.1.2 of Non-Patent Document 5, it is being examined whether to support transmission / reception spanning SBFD symbols and non-SBFD symbols.
[0078] Regarding UL transmission / DL reception spanning SBFD symbols and non-SBFD symbols in different slots (each transmission / reception within a slot is either all SBFD or all non-SBFD symbols), the following options are considered for SBFD-capable UEs. Option 1: Transmission / reception is restricted to only SBFD symbols or only non-SBFD symbols Option 2: Transmission / reception can be performed with SBFD symbols and non-SBFD symbols
[0079] UL transmission / DL reception spanning SBFD symbols and non-SBFD symbols includes the following information: · Repetition of PDSCH / PUSCH / PUCCH · SPS PDSCH / CG PUSCH (Configured Grant PUSCH) · TBoMS (Transport Block processing over Multiple Slots) · Multiple (several) PUSCH / PDSCH scheduled by a single DCI · Periodic / semi-persistent SRS / CSI-RS / PUCCH · PDCCH
[0080] Option 1 can be achieved by gNB configuration or scheduling such that all transmit / receive occasions are restricted to either SBFD symbols or non-SBFD symbols. Alternatively, Option 1 can be achieved by additional instructions or rules to determine which transmit / receive occasions are valid within one symbol type and invalid within other symbol types. The frequency resources, power control, and beam / spatial relationships for all transmit / receive occasions may be identical in Option 1 but may be different in Option 2. If different, additional work on the specifications may be required. Option 1 may / may not increase transmit / receive latency if transmit / receive in other symbol types is postponed, and may degrade performance if transmit / receive in other symbol types is dropped. Option 2 may / may not reduce transmit / receive latency and improve coverage.
[0081] <Terminology> The following explains the definitions of terms related to SBFD.
[0082] SBFD symbol: Symbol set in SBFD sub-band Non-SBFD symbols: Symbols that are not configured in the SBFD sub-bands DL (or semi-static D) symbol: A symbol indicated as DL by t-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated UL (or semi-static U) symbol: A symbol designated as UL by tdd-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated Flexible (or Semi-Static F, or Flexible) Symbol: A symbol designated as flexible by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigDedicated SBFD DL symbol: A symbol indicated as downlink (DL) by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which the SBFD subband is configured SBFD Flexible (FL) Symbol: A symbol indicated as flexible by the tdd-UL-DL-Configuration Common and / or tdd-UL-DL-Configuration Dedicated, in which SBFD sub-bands are configured.
[0083] <Agreement 1> At the 3GPP RAN1#117 meeting, it was agreed that whether transmission / reception in different slots is limited to one symbol type or is allowed by two symbol types is determined based on the configuration as follows:
[0084] For an SBFD-capable UE with UL transmissions and DL receptions spanning SBFD and non-SBFD symbols in different slots (each transmission / reception in a slot having either all SBFD symbols or all non-SBFD symbols), the SBFD-capable UE is provided with one of the following configurations: Configuration 1: Transmission / reception is restricted to either SBFD symbols only or non-SBFD symbols only (see Figure 8). Configuration 2: Transmission / reception can be performed using both SBFD and non-SBFD symbols (see Figure 9).
[0085] The granularity of the settings (for example, per UE, per channel / signal, etc.) has not yet been determined. It is also unclear whether support for setting 2 depends on the UE capability.
[0086] In UL transmission / DL reception for one slot, SBFD symbols and non-SBFD symbols are never mixed in one occasion, and one of the symbol types is always used for each transmission / reception within the slot. However, in UL transmission / DL reception where resources are periodically allocated, such as in repetition spanning multiple slots, an event may occur in which transmission / reception is performed using SBFD symbol types in some slots and non-SBFD symbols in other slots. In such cases, two options are supported: one option (Configuration 1) that enables only one of the symbol types for the entire transmission / reception spanning multiple slots, and another option (Configuration 2) that allows both symbol types to be mixed. Either configuration is set in the terminal.
[0087] For example, when configuration 1 is set for a terminal, if repetition is set for SBFD symbols, the repetition is valid only for SBFD symbols in that terminal, and when repetition is set for non-SBFD symbols, the repetition is valid only for non-SBFD symbols in that terminal. When configuration 2 is set for a terminal, it becomes possible to use both SBFD symbols and non-SBFD symbols in a certain repetition.
[0088] <Agreement 2> At the 3GPP RAN1#119 meeting, the following items (Agreements 2-1 to 2-3) were agreed upon. Agreement 2-1 states that an SBFD-capable UE can be configured with Configuration 2 for each UL / DL BWP. Agreement 2-2 also states that the valid symbol type of SPS PDSCH is determined based on the symbol type of the first SPS PDSCH associated with the activation DCI. Agreement 2-3 also states that under certain conditions, the UE will postpone / drop transmission / reception of invalid symbol types.
[0089] (Agreement 2-1) For SBFD-capable UEs, for UL transmissions and DL receptions that span SBFD and non-SBFD symbols in different slots (each transmission / reception within a slot may contain all SBFD symbols or all non-SBFD symbols), Support for configuration 2 depends on the UE's capabilities. Configuration 1 is the default capability. An SBFD-capable UE may be configured with Configuration 2 for each UL / DL BWP. · The DL BWP configuration applies to PDSCH reception within at least the DL BWP. The UL BWP configuration applies to PUCCH and PUSCH transmissions within the UL BWP. -For SRS (Sounding Reference Signal), only configuration 1 is applied.
[0090] (Agreement 2-2) For configuration 1: Transmission / reception is restricted to only SBFD symbols or only non-SBFD symbols. For Type 2 CG PUSCH and SPS PDSCH, the following options are limited: ·The valid symbol type of Type 2 CG PUSCH is determined based on the symbol type of the first CG PUSCH associated with the activation DCI. ·The valid symbol type of SPS PDSCH is determined based on the symbol type of the first SPS PDSCH associated with the activation DCI.
[0091] (Agreement 2-3) Update the following agreement in 3GPP RAN1#118 meeting. In the case of UL transmission and DL reception spanning SBFD symbols and non-SBFD symbols in different slots in Configuration 1 (each transmission / reception within a slot is either all SBFD or all non-SBFD symbols), For PUSCH repetition Type A that counts available slots, A-SRS that counts available slots, TBoMS, and PUCCH repetition, the UE defers transmission with an invalid symbol type. For CG PUSCH, SPS PDSCH, P / SP SRS, P / SP CSI-RS, P / SP PUCCH, SP-CSI on PUSCH that do not have TBoMS or PUSCH repetition Type A that counts available slots, PUSCH repetition Type A that does not count available slots, multi-PUSCH / PDSCH scheduled by a single DCI, and PDSCH repetition, transmission / reception with an invalid symbol type is dropped.
[0092] <SPS HARQ-ACK Delay Related Technology> The following describes related technologies for SPS HARQ-ACK deferring, which is relevant to the present disclosure. Under the following (a) SPS HARQ-ACK deferring condition, the UE determines the following (b) target slot / subslot and performs SPS HARQ-ACK deferring. The background technology is as described above in the section "SPS HARQ-ACK deferring."
[0093] (a) SPS HARQ-ACK deferring conditions If SPS HARQ-ACK postponement is enabled in the SPS configuration, the HARQ-ACK of the SPS configuration can be postponed in the following cases of Alt. (Alternative) 1-a to 4-a.
[0094] (Alt.1-a) If the SPS HARQ-ACK PUCCH overlaps with at least one semi-static DL symbol (whether SBFD or non-SBFD), SSB symbol, or Type-0 CORESET symbol
[0095] (Alt.2-a) If the SPS HARQ-ACK PUCCH overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol, or Type-0 CORESET symbol
[0096] (Alt.3-a) If the SPS HARQ-ACK PUCCH overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol, Type-0 CORESET symbol, or SBFD semi-static / dynamic DL symbol and / or SBFD semi-static / dynamic UL symbol (and / or SBFD semi-static / dynamic flexible symbol).
[0097] (Alt.4-a) If the SPS HARQ-ACK PUCCH overlaps with the DL subband in at least one non-SBFD semi-static DL symbol, SSB symbol, Type-0 CORESET symbol, or SBFD semi-static / dynamic DL symbol and / or SBFD semi-static / dynamic UL symbol (and / or SBFD semi-static / dynamic flexible symbol).
[0098] Here, among the above-mentioned Alt.1-a to Alt.4-a, different alternatives (Alt.) may be prioritized based on the method of indicating SBFD operation (and / or DL / UL subband allocation). For example, when SBFD operation (and / or DL / UL subband allocation) is configured by RRC, Alt.2-a or Alt.3-a may be applied. When SBFD operation (and / or DL / UL subband allocation) is dynamically indicated by DCI, Alt.1-a may be applied. Furthermore, the selection may be specified by a specification, semi-statically configured by RRC configuration or the like, dynamically notified by DCI notification or the like, or determined according to a rule. Furthermore, the application may be specified, configured, notified, or determined explicitly or implicitly.
[0099] (b) Determining the target slot / subslot As described above, when the HARQ-ACK for the SPS configuration is postponed, the UE may determine the first available slot / subslot as the target slot / subslot for the postponed transmission. Here, the target slot / subslot in which the SPS HARQ-ACK can be transmitted is the slot / subslot in which the determined PUCCH resource is first available and may be a slot that satisfies the following conditions Alt. 1-b to 4-b.
[0100] (Alt.1-b) Non-overlapping SPS HARQ-ACK PUCCH that overlaps at least one semi-static DL symbol (whether SBFD or non-SBFD), SSB symbol, or Type-0 CORESET symbol
[0101] (Alt.2-b) At least one non-SBFD semi-static DL symbol, SSB symbol, or Type -0 CORESET symbol must not overlap with the SPS HARQ-ACK PUCCH. (Alt.3-b)
[0102] Does not overlap with SPS HARQ-ACK PUCCH that overlaps with at least one non-SBFD semi-static DL symbol, SSB symbol, Type-0 CORESET symbol, or SBFD semi-static / dynamic DL symbol and / or SBFD semi-static / dynamic UL symbol (and / or SBFD semi-static / dynamic flexible symbol).
[0103] (Alt.4-b) Does not overlap with the SPS HARQ-ACK PUCCH that overlaps with the DL subband in at least one non-SBFD semi-static DL symbol, SSB symbol, Type-0 CORESET symbol, or SBFD semi-static / dynamic DL symbol and / or SBFD semi-static / dynamic UL symbol (and / or SBFD semi-static / dynamic flexible symbol).
[0104] As a variant, joint operation of SPS HARQ-ACK deferral and SBFD operations may not be supported, e.g., the UE may not assume / judge / determine / interpret that SPS HARQ-ACK deferral is enabled for an SPS configuration on a serving cell / bandwidth portion (BWP) while SBFD operation (and / or DL / UL subband allocation) is configured / signaled / enabled on the serving cell / BWP.
[0105] Also, as a variant, if SBFD operation (and / or DL / UL subband allocation) is configured / notified / enabled on the serving cell / BWP and SPS HARQ-ACK deferral operation is enabled for the SPS configuration on the serving cell / BWP, the UE may not perform the SPS HARQ-ACK deferral operation.
[0106] Note that which of the above-mentioned Alt.s to apply may be explicitly or implicitly specified by a specification, semi-statically configured by RRC, dynamically notified by DCI, or determined by a rule. For example, a parameter indicating which Alt.s to apply may be transmitted in at least one of RRC, DCI, and MAC CE (Medium Access Control Element).
[0107] (UE operation) In the related art, when a HARQ-ACK postponement condition is satisfied in a time-frequency division duplex operation such as an SBFD operation and a non-time-frequency division duplex operation such as a non-SBFD operation, the UE may enable a HARQ-ACK postponement operation and postpone transmission of an uplink control channel for the HARQ-ACK according to the postponement operation, where the HARQ-ACK may be an SPS HARQ-ACK and the uplink control channel may be a PUCCH.
[0108] Specifically, the UE may enable the HARQ-ACK postponement operation when the SPS HARQ-ACK overlaps with a semi-static downlink time unit, an SSB time unit, or a Type-0 CORESET time unit, regardless of whether the UE is operating in SBFD or non-SBFD mode. The UE may also enable the HARQ-ACK postponement operation when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, a synchronization signal block (SSB) time unit, or a Type-0 CORESET time unit. The UE may also enable the HARQ-ACK postponement operation when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, an SSB time unit, or a Type-0 CORESET time unit, or when the SPS HARQ-ACK overlaps with an SBFD semi-static / dynamic time unit. The UE may also enable the postponement operation of HARQ-ACK when the SPS HARQ-ACK overlaps with a non-SBFD semi-static downlink time unit, an SSB time unit, or a Type-0 CORESET time unit, or overlaps with a downlink subband in an SBFD semi-static / dynamic time unit.
[0109] (gNB operation) In the related art, a gNB may transmit a downlink data channel and receive an uplink control channel of a HARQ-ACK that has been postponed according to a postponement operation that is enabled when a HARQ-ACK postponement condition is satisfied in a time-frequency division duplex operation such as an SBFD operation and a non-time-frequency division duplex operation such as a non-SBFD operation for the downlink data channel, where the HARQ-ACK may be an SPS HARQ-ACK and the uplink control channel may be a PUCCH.
[0110] (UE Capability) Regarding the SPS HARQ-ACK enhancement for time-frequency division duplex operation such as the SBFD operation described above, UE capability information indicating whether the UE supports the SPS HARQ-ACK enhancement for time-frequency division duplex operation may be defined. Also, UE capability information regarding SPS HARQ-ACK transmission for time-frequency division duplex operation such as SBFD operation may be defined. Specifically, UE capability information indicating whether the UE supports SPS HARQ-ACK postponement for SBFD operation may be defined. If the UE supports the SPS HARQ-ACK enhancement for time-frequency division duplex operation, the UE may transmit UE capability information indicating support for the SPS HARQ-ACK enhancement for time-frequency division duplex operation to the gNB. Upon receiving the UE capability information, the gNB can receive the SPS HARQ-ACK from the UE in accordance with the SPS HARQ-ACK enhancement for time-frequency division duplex operation.
[0111] <Analysis> The above-mentioned SPS HARQ-ACK deferral-related technology proposes the impact of SBFD on SPS HARQ-ACK deferring. In this related technology, the bandwidth resource (UL available PRB (Physical Resource Block)) is not considered when determining the SPS HARQ-ACK deferral condition and the target slot / subslot. However, the PUCCH resource within the SBFD symbol may or may not be available for PUCCH transmission depending on whether it overlaps with an RB (Resource Block) outside the UL available PRB. Therefore, the following unresolved issue (1) regarding the bandwidth resource (UL available PRB) remains, and further study is required. Furthermore, for the HARQ-ACK PUCCH for the SPS PDSCH, study is also required on issue (2) regarding whether the HARQ-ACK is an SBFD symbol or a non-SBFD symbol. (1) Determine the SPS HARQ-ACK postponement conditions and target slots / subslots taking into account bandwidth resources (UL available PRBs). (2) Clarify whether the HARQ-ACK PUCCH for the SPS PDSCH of one SPS configuration is considered to be a transmission corresponding to Configuration 1 or Configuration 2.
[0112] Therefore, in the <Proposal> of this embodiment, a specific proposal for solving the above-mentioned (1) and (2) will be explained.
[0113] <Proposal Summary> As proposals in this embodiment, the following proposals 1 and 2 will be described. (Proposal 1) The HARQ-ACK for the SPS PDSCH of one SPS configuration is an independent PUCCH transmission. The HARQ-ACK for the SPS PDSCH in the SPS configuration can be an SBFD symbol or a non-SBFD symbol by default (not affected by Configuration 1 or Configuration 2). (Proposal 2) The HARQ-ACK for the SPS PDSCH of one SPS configuration is a related (series of) PUCCH transmissions. Whether the HARQ-ACK for the SPS PDSCH in the SPS configuration is an SBFD symbol or a non-SBFD symbol depends on Configuration 1 or Configuration 2.
[0114] <Proposal 1> The HARQ-ACK for the SPS PDSCH of one SPS configuration is an independent PUCCH transmission. The HARQ-ACK for the SPS PDSCH in the SPS configuration can be an SBFD symbol or a non-SBFD symbol by default (not affected by Configuration 1 or Configuration 2).
[0115] When SPS HARQ-ACK deferring is enabled, the deferral conditions and target slot / subslot of SPS HARQ-ACK depend on the UL available PRBs in the SBFD symbol, and the UE determines the next (1-b) slot / subslot to defer SPS HARQ-ACK under the following condition (1-a).
[0116] (1-a) SPS HARQ-ACK postponement condition When the SPS HARQ-ACK PUCCH resource overlaps with RBs outside the UL enabled PRBs in an SBFD symbol, overlaps with a non-SBFD DL symbol / SSB symbol, or overlaps with a (non-SBFD) Type-0 CORESET symbol
[0117] (1-b) Determining the target slot / subslot The earliest slot / subslot in which the determined PUCCH resource does not overlap with RBs outside the UL available PRBs in the SBFD symbol, does not overlap with non-SBFD DL symbols / SSB symbols, and does not overlap with (non-SBFD) Type-0 CORESET symbols.
[0118] It should be noted that the above-mentioned conditions (1-a) and (1-b) may be combined with alternatives of the related art (Alternatives 1-a to 4-a, 1-b to 4-b).
[0119] <Proposal 2> The HARQ-ACK for the SPS PDSCH of one SPS configuration is a related (series of) PUCCH transmissions. Whether the HARQ-ACK for the SPS PDSCH of the SPS configuration is an SBFD symbol or a non-SBFD symbol depends on Configuration 1 or Configuration 2.
[0120] [When configuration 1 is specified] When configuration 1 is specified, it is necessary to determine the valid symbol type of the SPS HARQ-ACK PUCCH depending on whether the SPS HARQ-ACK postponement is valid or not. Therefore, the following cases (2-1) to (2-3) will be explained respectively.
[0121] (2-1) Valid symbol types for SPS HARQ-ACK PUCCH The valid symbol type for the SPS HARQ-ACK PUCCH is determined based on the following Alt. 2-1-1 to 2-1-2.
[0122] (Alt.2-1-1) Valid symbol types are the same as the valid symbol types of the SPS PDSCH occasion in the SPS configuration. (Alt.2-1-2) Valid symbol types are separate / independent from the valid symbol types of the SPS PDSCH occasions in the SPS configuration.
[0123] (Setting or determining valid symbol types) In the above-mentioned Alt.2-1-2, if the valid symbol types of the SPS HARQ-ACK PUCCH are different / independent from the valid symbol types of the SPS PDSCH occasions in the SPS configuration, the UE / gNB (NW) configures or determines the valid symbol types of the SPS HARQ-ACK PUCCH based on the following Alt.2-1-2-1 to 2-1-2-2.
[0124] (Alt.2-1-2-1) Explicitly set by a parameter in the SPS configuration. (Alt. 2-1-2-2) Determined based on the symbol type of the HARQ-ACK PUCCH of the first SPS PDSCH occasion after activation (or the symbol type of the HARQ-ACK PUCCH corresponding to the activation DCI).
[0125] (2-2) Invalid symbol type when SPS HARQ-ACK deferral is not enabled If SPS HARQ-ACK postponement is not enabled and the SPS HARQ-ACK overlaps with an invalid symbol type, the UE shall process as follows: Alt. 2-2-1 to 2-2-2.
[0126] (Alt. 2-2-1) An SPS HARQ-ACK with an invalid symbol type is postponed to the next slot / subslot where the PUCCH resource determined for the SPS HARQ-ACK is of a valid symbol type. (Alt.2-2-2) SPS HARQ-ACKs with invalid symbol types are dropped.
[0127] (2-3) Impact of SPS HARQ-ACK postponement when SPS HARQ-ACK postponement is enabled When SPS HARQ-ACK postponement is enabled, the following cases of Alt. 2-3-1 to 2-3-2 will be explained.
[0128] (Alt.2-3-1) If the valid symbol type is SBFD If the valid symbol type is SBFD, the UE determines the next (2-3-1-b) slot / sub-slot to postpone SPS HARQ-ACK under the following condition (2-3-1-a).
[0129] (2-3-1-a) SPS HARQ-ACK postponement conditions If the determined PUCCH resource overlaps with (or is within) a non-SBFD symbol, or overlaps with an RB outside the UL available PRB within an SBFD symbol.
[0130] (2-3-1-b) Determining the target slot / sub-slot The earliest slot / subslot in which the determined PUCCH resource is within the SBFD symbol and does not overlap with RBs outside the UL available PRBs
[0131] (Alt.2-3-2) If the valid symbol type is not SBFD If the valid symbol type is not SBFD, the UE determines the next (2-3-2-a) slot / sub-slot to postpone SPS HARQ-ACK under the following condition (2-3-2-a).
[0132] (2-3-2-a) SPS HARQ-ACK postponement conditions If the determined PUCCH resource overlaps with (or is within) an SBFD symbol, or overlaps with a non-SBFD DL symbol, an SSB symbol, or a (non-SBFD) Type-0 CORESET symbol.
[0133] (2-3-2-b) Determining the target slot / sub-slot The earliest slot / subslot in which the determined PUCCH resource does not overlap with SBFD symbols and does not overlap with non-SBFD DL symbols, SSB symbols, or (non-SBFD) type-0 CORESET symbols.
[0134] If configuration 2 is provided, proposal 1 may be reused.
[0135] Regarding the above-mentioned condition (2-3), alternatives of the related art (Alt. 1-a to 4-a, 1-b to 4-b) may be combined.
[0136] (effect) As described above, according to Proposals 1 and 2, the UE determines the SPS HARQ-ACK postponement condition and the target slot / subslot assuming that the PUCCH resource in the SBFD symbol overlaps with an RB outside the UL available PRB, so that the UE can appropriately determine the SPS HARQ-ACK postponement operation. Furthermore, because it is clarified whether the HARQ-ACK for the SPS PDSCH of one SPS configuration is an independent PUCCH transmission or a related (series of) PUCCH transmission depending on the premise, it is possible to more clearly assume implementation constraints based on the specification.
[0137] <Variations of Proposals 1 and 2> (Combined with options) In Proposals 1 and 2 of the present disclosure, which proposal is applied or which option or alternative is used may be determined as follows. - Set by upper layer parameters Determined by related higher level parameters -Indicated in MAC CE or DCI Determined based on UE capabilities - Listed in the specifications - Determined based on the conditions stated in the specifications Determined by higher layer parameters / MAC CE / DCI configuration and reported UE capabilities (combination of the above decisions)
[0138] In Proposals 1 and 2 of this disclosure, multiple options, related art alternatives, and alternatives may be combined into one option / alternative. Also, throughout the proposals, the RS (reference signal) measured will be the QCL source RS in the active / indicated TCI state.
[0139] (Signal from NW to UE) In this disclosure, the UE may receive the following types of information from the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g., RRC messages / LPP (LTE propositioning protocol) messages) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) DCI DCI Field: Existing DCI field or newly introduced DCI field RNTI: DCI with CRC scrambled by the existing RNTI or the newly introduced RNTI DCI Format: Existing DCI format or newly introduced DCI format Combination of the above information
[0140] In the present disclosure, the UE may receive information from the network (NW) in the following periodic format: Option 1: Receive periodic updates Option 2: Semi-persistent reception of information (triggered by UE or gNB instructions) Option 3: Receiving information aperiodically (triggered by UE or gNB instructions)
[0141] In the present disclosure, the UE may receive information from the network (NW) as the following QCL rules: QCL Type A QCL Type B QCL Type C QCL Type D
[0142] In this disclosure, the QCL resource RS for each QCL type may be configured as follows: SSB (SS / PBCH Block) CSI-RS with / without repetition ·TRS(tracking reference signal) PDCCH / PDSCH DMRS
[0143] In the present disclosure, information from the network (NW) is set / indicated as follows: ·UE common / UE only Cell specific / Cell common Per UE / CC / BWP / band / cell / CG
[0144] (Signal from UE to NW) In this disclosure, the UE may report the following types of information to the network (NW): Also, throughout the proposal, the network (NW) may be referred to as a gNB. Information via higher layer signaling (e.g. RRC message / LPP message) MAC CE Subheader with new LCID in the subheader Extending an existing MAC CE (e.g., introducing a new octet) UCI UCI on PUCCH or PUSCH Combination of the above information
[0145] In the present disclosure, the UE may report information to the network (NW) in a periodic manner as follows: Option 1: Send information periodically Option 2: Semi-persistent information transmission (triggered by UE or gNB instruction) Option 3: Aperiodic information transmission (triggered by UE or gNB instruction)
[0146] <UE capability> The UE capability indicating the capability of the terminal may include the following information indicating the capability of the terminal. For example, the following new UE capability and report signaling (and RRC configuration) may be defined. Note that the information indicating the capability of the terminal may correspond to information defining the capability of the terminal. The UE may report the following information indicating the capabilities of the terminal to the gNB: ·Device capabilities for each proposal ·Ability to implement each option or combination of options in each proposal · Capabilities for each alternative or combination of alternatives in each proposal The UE may report information indicating the above terminal capabilities for each frequency to the gNB. · Capabilities for UE / FR1 / FR2 / FR2-1 / FR2-2 / FR3 / SCS / band / BC / FC / FSPC etc. The UE may report information indicating the above terminal capabilities for each cell to the gNB. Capabilities for each UE / cell / TDD / FDD, etc.
[0147] The above UE capabilities and the configuration of this proposal are closely related, and if the functions related to each option in each proposal depend on the UE capabilities, the gNB may select or enable the functions related to each option based on the capabilities reported by the UE.
[0148] Next, the configurations of the gNB100 and the UE200 will be described. Note that the configurations of the gNB100 and the UE200 described below are examples of functions related to the present embodiment. The gNB100 and the UE200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to the present embodiment.
[0149] <Base station configuration> Fig. 10 is a block diagram showing an example of the configuration of a base station 100 (gNodeB (gNB) 100) according to this embodiment. The gNB 100 includes, for example, a transmitter 101, a receiver 102, and a controller 103. The gNB 100 communicates with a UE 200 (see Fig. 11) by radio.
[0150] The transmitter 101 transmits a downlink (DL) signal to the UE 200. For example, under the control of the controller 103, the transmitter 101 transmits a DL signal (for example, the above-mentioned RRC, SIB, MAC CE, DCI, notification, confirmation, etc.).
[0151] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission by the UE 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.
[0152] The channels used for transmitting DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, the gNB 100 transmits downlink control information to the UE 200 using the PDCCH and transmits downlink data signals using the PDSCH.
[0153] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.
[0154] The receiver 102 receives an uplink (UL) signal transmitted from the UE 200. For example, under the control of the controller 103, the receiver 102 receives an UL signal (for example, the above-mentioned request, notification, etc.).
[0155] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.
[0156] The control unit 103 controls the communication operations of the gNB 100, including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102.
[0157] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.
[0158] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on a signal (e.g., data and control information, etc.) received from the UE 200 and / or data and control information, etc. acquired from an upper layer. Information on the allocated resources may be included in control information transmitted to the UE 200.
[0159] <Device configuration> 11 is a block diagram showing an example of the configuration of UE 200 according to the present embodiment. UE 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. UE 200 communicates with gNB 100 by radio, for example.
[0160] The transmitter 202 transmits an UL signal to the gNB 100. For example, the transmitter 202 transmits the UL signal under the control of the controller 203. For example, the transmitter 202 may transmit an MsgA PRACH in a valid MsgA RO determined by the controller 203, and may transmit an MsgA PUSCH in a valid MsgA PO determined by the controller 203.
[0161] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the UE 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.
[0162] The channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, the UE 200 transmits uplink control information to the gNB 100 using the PUCCH and transmits an uplink data signal using the PUSCH.
[0163] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).
[0164] The receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.
[0165] The control unit 203 controls the communication operations of the UE 200, including the reception processing in the reception unit 201 and the transmission processing in the transmission unit 202.
[0166] For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the higher layer.
[0167] For example, the control unit 203 controls transmission of information to be fed back to the gNB 100. The information to be fed back to the gNB 100 may include, for example, HARQ-ACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the gNB 100 may be included in UCI.
[0168] For example, the communication unit consisting of the receiving unit 201 or the receiving unit 201 and the transmitting unit 202 may receive a signal generated based on the SPS configuration. The communication unit consisting of the receiving unit 201 and the transmitting unit 202 transmits and receives all signals related to Proposals 1 and 2.
[0169] For example, the control unit 203 may control the transmission of an acknowledgement (HARQ-ACK) for a signal generated based on the SPS configuration, and if the transmission resource of the acknowledgement overlaps with other band resources, may control the transmission of the acknowledgement to be postponed until the next earliest transmission slot in which the transmission resource does not overlap with other resources. Furthermore, the control unit 203 may set and determine valid symbol types for the SPS HARQ-ACK PUCCH and the SPS PDSCH occasion of the SPS configuration. The control unit 203 is responsible for all the processes related to Proposals 1 and 2.
[0170] Here, the communication unit consisting of the receiving unit 201 and the transmitting unit 202 may transmit and receive signals whose transmission and / or reception symbol type is either an SBFD symbol type or a non-SBFD symbol type. The SBFD symbol type may be interpreted as a symbol type that can be used simultaneously for downlink and uplink by utilizing multiple subbands that make up a time division duplex band. The non-SBFD symbol type may be interpreted as a symbol type that can be used only for downlink or uplink in a time division duplex band.
[0171] The control unit 203 may determine the frequency resource of the uplink data channel in the time unit to which SBFD is applied, based on the frequency domain resource allocation (FDRA) and the offset value of the resource block of SBFD. Also, the control unit 203 may determine the offset value of the resource block of SBFD based on a plurality of LSB / MSB bits of the frequency domain resource allocation field of the downlink control information (DCI).
[0172] When inter-slot / intra-slot frequency hopping is enabled, the control unit 203 may determine the frequency resource of the uplink data channel in the time unit to which SBFD is applied based on the frequency domain resource allocation (FDRA) and an offset value. Also, the control unit 203 may determine the offset value based on the offset value of the resource block of SBFD and / or the frequency hopping offset value.
[0173] The control unit 203 may determine, for each RGB of FDRA Type 0, a corresponding RBG for the PUSCH occasion of the SBFD symbol.
[0174] With the above configuration, when a plurality of subbands constituting a time division duplex band are available, control unit 203 of UE 200 can appropriately set frequency resources for SBFD symbols in PUSCH transmission.
[0175] <Other> The items explained in Proposals 1 to 3 above may be combined as appropriate as long as no contradictions arise.
[0176] In the above, SBFD symbols and non-SBFD symbols may be read as SBFD slots and non-SBFD slots, respectively.
[0177] The configuredGrantConfig, pusch-Config, and activation DCI for the CG PUSCH, and the sps-Config and activation DCI for the SPS PDSCH, which are transmitted from a gNB (base station) to a UE (terminal), may be referred to as information about a periodic or semi-persistent signal or channel, etc. Configuration information about PDSCH repetition, etc., transmitted from a gNB to a UE may be referred to as information about a periodic or semi-persistent signal or channel, etc. Hereinafter, a UE may receive, from a gNB, information about a periodic or semi-persistent signal or channel, and information about a time unit (SBFD symbol, SBFD slot, etc.) in which multiple subbands constituting a time division duplex band can be used. <Hardware configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.
[0178] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0179] For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Figure 12 is a diagram showing an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The gNB 100 and UE 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0180] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the gNB100 and the UE200 may be configured to include one or more of the apparatuses shown in the figures, or may be configured to exclude some of the apparatuses.
[0181] Each function in gNB100 and UE200 is realized by loading specific software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication by communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.
[0182] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.
[0183] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the UE 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.
[0184] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.
[0185] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.
[0186] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.
[0187] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0188] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0189] Furthermore, the gNB 100 and the UE 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0190] <Information notification, signaling> The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0191] <Applicable systems> Embodiments described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable systems, and next generation systems extended, modified, created, or defined based on these. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.
[0192] <Processing procedures, etc.> The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0193] <Base station operation> In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.
[0194] <Input / output direction> Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input and output via multiple network nodes.
[0195] <Handling of input and output information> Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.
[0196] <Judgment method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0197] <Variations of form, etc.> Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0198] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0199] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0200] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0201] <Information, Signals> The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0202] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0203] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0204] <parameter, channel name> Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0205] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0206] <Base station> In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0207] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.
[0208] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
[0209] <Mobile station> In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0210] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0211] <Base station / mobile station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and devices mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
[0212] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal may be configured to have the functions of the base station described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0213] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.
[0214] Fig. 13 shows an example configuration of a vehicle 2001. As shown in Fig. 13, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0215] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
[0216] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0217] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0218] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.
[0219] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0220] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0221] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029, which are provided in the vehicle 2001.
[0222] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
[0223] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0224] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.
[0225] <Terminology and interpretation> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0226] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0227] <Reference signal> The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0228] <The meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0229] <"First", "Second"> As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0230] <Means> In the configuration of each of the above devices, the "means" may be replaced with "section", "circuit", "device", etc.
[0231] <Open format> In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.
[0232] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.
[0233] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, and specific windowing processing performed by a transceiver in the time domain.
[0234] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.
[0235] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0236] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0237] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
[0238] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.
[0239] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0240] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0241] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0242] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0243] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0244] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0245] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.
[0246] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0247] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0248] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0249] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0250] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0251] <Maximum transmission power> The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0252] <Article> In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0253] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Industrial Applicability]
[0254] One aspect of the present disclosure is useful in wireless communication systems. [Explanation of symbols]
[0255] 10. Wireless communication systems 20 NG-RAN 100 base stations (gNB) 200 User Equipment (UE) 101,202 Transmitter 102,201 Receiver 103,203 Control unit
Claims
1. a receiver that receives a downlink signal configured by semi-static scheduling in either a first time unit in which a downlink and an uplink can be simultaneously used by a plurality of subbands that constitute a time division duplex band, or a second time unit in which one of the downlink and the uplink can be used by applying the time division duplex band; a control unit that controls transmission of an acknowledgement response to the downstream signal; Equipped with When a transmission resource of the acknowledgement overlaps with a resource outside an available subband in the first time unit, the control unit postpones transmission of the acknowledgement until a next earliest transmission slot in which the transmission resource does not overlap with a resource in the first time unit or the second time unit. Terminal.
2. The downlink signal is a signal on a PDSCH (Physical Downlink Shared Channel) generated based on a configuration of SPS (Semi-Persistent Scheduling), The acknowledgment is a signal based on a Hybrid Automatic Repeat request Acknowledgement (HARQ-ACK). The terminal of claim 1.
3. The HARQ-ACK for the SPS PDSCH of one SPS configuration is an independent PUCCH (Physical Uplink Control Channel) transmission. The terminal according to claim 2.
4. The HARQ-ACK for the SPS PDSCH of one SPS configuration is a series of associated PUCCH (Physical Uplink Control Channel) transmissions. The terminal according to claim 2.
5. The device is receiving a downlink signal configured by semi-static scheduling in either a first time unit in which a downlink and an uplink can be simultaneously used by a plurality of subbands constituting a time division duplex band, or a second time unit in which one of the downlink and the uplink can be used by applying the time division duplex band; Controlling transmission of an acknowledgement response to the downstream signal; if a transmission resource for the acknowledgement overlaps with a resource outside the available subbands on the first time unit, postponing transmission of the acknowledgement until the next earliest transmission slot in which the transmission resource does not overlap with a resource on the first time unit or the second time unit. Communication method.