Terminal, wireless communication method, and base station

Abstract

A terminal involved in one embodiment of the present disclosure includes: a receiving unit, which receives downlink control information for triggering feedback of a single-trigger HARQ-ACK; and a control unit, which, when performing the feedback of the HARQ-ACK based on the downlink information, controls the feedback using a common codebook for HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities.

Description

Technical Field

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. Background Art

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been standardized to further enhance the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Releases (Rel.) 8 and 9).

[0003] Successor systems of LTE (for example, also referred to as fifth-generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being studied.

[0004] Furthermore, conventional systems support a configuration in which a UE feeds back a delivery confirmation signal (HARQ-ACK, ACK / NACK, or A / N) for DL ​​data (eg, PDSCH), thereby controlling retransmission of the PDSCH.

[0005] Prior art literature

[0006] Non-patent literature

[0007] Non-Patent Document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0008] Problems to be solved by the invention

[0009] In future wireless communication systems (e.g., 5G, NR, etc.), it is envisioned that: for example, high speed and large capacity (e.g., enhanced mobile broadband (eMBB: enhanced Mobile Broad Band)), a large number of terminals (e.g., massive Machine Type Communication (mMTC), Internet of Things (IoT)), ultra-high reliability and low latency (e.g., ultra-reliable and low-latency communications (URLLC)), etc.), multiple business types (also called services, types, service types, communication types, or use cases, etc.) with different requirements (requirements) will coexist.

[0010] When a UE supports (or utilizes) multiple service types, it is also assumed that the HARQ-ACK codebook used in HARQ-ACK feedback is set for each service type. In addition, in future wireless communication systems, research is underway to allow the UE to provide HARQ-ACK feedback for multiple HARQ processes at once.

[0011] However, how to control HARQ-ACK feedback when supporting HARQ-ACK codebook configuration for each of multiple service types has not been fully studied.

[0012] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform HARQ-ACK feedback even when communicating using multiple service types.

[0013] Means for solving problems

[0014] A terminal involved in one embodiment of the present invention is characterized in that it comprises: a receiving unit for receiving downlink control information for triggering feedback of a single-triggered HARQ-ACK; and a control unit for controlling feedback of HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities using a common codebook when performing feedback of the HARQ-ACK based on the downlink information.

[0015] Effects of the Invention

[0016] According to one embodiment of the present disclosure, HARQ-ACK feedback can be appropriately performed even when communication is performed using multiple service types. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1This is a diagram showing an example of performing HARQ-ACK feedback for each service type.

[0018] Figure 2 This is a diagram showing an example of one-shot HARQ-ACK feedback control.

[0019] Figure 3 This is a diagram showing an example of one-shot HARQ-ACK feedback control according to the first example.

[0020] Figure 4 This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the first embodiment.

[0021] Figure 5 This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the first embodiment.

[0022] Figure 6 This is a diagram showing an example of one-shot HARQ-ACK feedback control according to the second example.

[0023] Figure 7A as well as Figure 7B This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the second example.

[0024] Figures 8A to 8C This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the second example.

[0025] Figures 9A to 9C This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the second example.

[0026] 10A to 10C This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the second example.

[0027] Figures 11A to 11C This is a diagram showing another example of one-shot HARQ-ACK feedback control according to the second example.

[0028] Figure 12 This is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.

[0029] Figure 13 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0030] Figure 14 This is a diagram showing an example of the configuration of a user terminal according to one embodiment.

[0031] Figure 15This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment. DETAILED DESCRIPTION

[0032] <Service (Business Type)>

[0033] Future wireless communication systems (e.g., NR) envision further sophistication of mobile broadband (e.g., enhanced mobile broadband (eMBB)), machine-type communications that enable a large number of simultaneous connections (e.g., massive machine-type communications (mMTC) and the Internet of Things (IoT)), and ultra-reliable and low-latency communications (e.g., ultra-reliable and low-latency communications (URLLC)). Service types (also referred to as types, services, service types, communication types, use cases, and the like) are envisioned. For example, URLLC requires lower latency and higher reliability than eMBB.

[0034] The service type may also be identified in the physical layer based on at least one of the following.

[0035] Logical channels with different priorities;

[0036] Modulation and Coding Scheme (MCS) table (MCS index table);

[0037] Channel Quality Indication (CQI) table;

[0038] DCI format;

[0039] Radio Network Temporary Identifier (RNTI: System Information - Radio Network Temporary Identifier)) used for scrambling (masking) of the CRC (Cyclic Redundancy Check) bits included in (added to) the DCI (DCI format);

[0040] RRC (Radio Resource Control) parameters;

[0041] Specific RNTI (e.g., RNTI for URLLC, MCS-C-RNTI, etc.);

[0042] Search space;

[0043] ·Specific fields within the DCI (e.g., newly added fields or reuse of existing fields).

[0044] Specifically, the service type of HARQ-ACK (or PUCCH) for PDSCH can also be determined based on at least one of the following.

[0045] The MCS index table used to determine at least one of the modulation order, target code rate, and transport block size (TBS) of the PDSCH (e.g., whether to use MCS index table 3);

[0046] The RNTI used for CRC scrambling of the DCI used to schedule the PDSCH (e.g., whether the CRC is scrambled by the C-RNTI or the MCS-C-RNTI);

[0047] Priority is set through higher layer signaling.

[0048] The service type may be associated with communication requirements (such as delay and error rate, and request conditions), data type (such as voice and data), and the like.

[0049] The difference between the requirements of URLLC and eMBB can be that the latency of URLLC is smaller than the latency of eMBB, or that the requirements of URLLC include reliability requirements.

[0050] For example, the requirements for the user (U) plane delay of eMBB may also include the case where the U-plane delay of the downlink is 4ms and the U-plane delay of the uplink is 4ms. On the other hand, the requirements for the U-plane delay of URLLC may also include the case where the U-plane delay of the downlink is 0.5ms and the U-plane delay of the uplink is 0.5ms. In addition, the requirements for the reliability of URLLC may also include the case where the error rate of 32 bytes is 10 in a U-plane delay of 1ms. -5 situation.

[0051] Furthermore, enhanced Ultra Reliable and Low Latency Communications (eURLLC) is being studied to improve the reliability of unicast data services. Hereinafter, URLLC and eURLLC will be referred to as URLLC when no distinction is made between them.

[0052] <Priority Setting>

[0053] In NR versions later than Rel. 16, studies are underway to assign multiple levels of priority (e.g., two levels) to specific signals or channels. For example, it is envisioned that different priorities may be assigned to each signal or channel corresponding to different service types (also known as services, service types, communication types, use cases, etc.) to control communications (e.g., transmission control in the event of a conflict). This allows for different priorities to be assigned to the same signal or channel, depending on the service type, etc., to control communications.

[0054] Priority can also be set for signals (e.g., UCI of HARQ-ACK, reference signals, etc.), channels (PDSCH, PUSCH, etc.), or HARQ-ACK codebooks. Priority can also be defined by a first priority (e.g., high) and a second priority (e.g., low) lower than the first priority. Alternatively, three or more priority levels may be set. Information related to priority can also be notified from the base station to the UE using at least one of higher layer signaling and DCI.

[0055] For example, priorities may be set for HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK for semi-persistent PDSCH (SPSPDSCH), and HARQ-ACK for SPS PDSCH release. Alternatively, priorities may be set for HARQ-ACK codebooks corresponding to these HARQ-ACKs. In addition, when setting priorities for PDSCH, the priority of PDSCH may be replaced with the priority of HARQ-ACK for the PDSCH.

[0056] In the event of a conflict between different UL signals / UL channels, the UE may also control UL transmission based on priority. For example, it may control the UE to perform high-priority UL transmissions while ignoring (e.g., dropping) low-priority UL transmissions. Alternatively, the transmission timing of low-priority UL transmissions may be altered (e.g., delayed or shifted).

[0057] The collision between different UL signals / UL channels refers to the situation where time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or it may also refer to the situation where transmission timings of different UL signals / UL channels overlap.

[0058] When priority is notified using DCI, whether a bit field for notifying priority (e.g., a priority indicator) is set in the DCI may be notified or set to the UE by the base station using higher layer signaling. In addition, when the DCI does not include a bit field for notifying priority, the UE may also determine that the priority of the PDSCH (or the HARQ-ACK corresponding to the PDSCH) scheduled by the DCI is a specific priority (e.g., low).

[0059] (HARQ-ACK codebook)

[0060] The UE may also use one PUCCH resource to send HARQ-ACK feedback using a HARQ-ACK codebook consisting of one or more bits of delivery confirmation information (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)). HARQ-ACK bits may also be referred to as HARQ-ACK information, HARQ-ACK information bits, etc.

[0061] Here, the HARQ-ACK codebook may also include HARQ-ACK bits in units of at least one of the time domain (e.g., time slot), frequency domain (e.g., component carrier (CC)), spatial domain (e.g., layer), transport block (TB), and code block group (CBG) constituting the TB. The HARQ-ACK codebook may also be simply referred to as a codebook.

[0062] In addition, the number of bits (size) included in the HARQ-ACK codebook may be semi-statically or dynamically determined. A HARQ-ACK codebook whose size is semi-statically determined is also referred to as a semi-static HARQ-ACK codebook, a Type 1 HARQ-ACK codebook, etc. A HARQ-ACK codebook whose size is dynamically determined is also referred to as a dynamic HARQ-ACK codebook, a Type 2 HARQ-ACK codebook, etc.

[0063] Whether to use the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook may be configured for the UE using a higher layer parameter (eg, pdsch-HARQ-ACK-Codebook).

[0064] In the case of a type 1 HARQ-ACK codebook, the UE may also feed back HARQ-ACK bits for PDSCH candidates (or PDSCH opportunities) corresponding to a specific range (e.g., a range set based on higher-layer parameters) regardless of whether PDSCH is scheduled or not.

[0065] The specific range may also be determined based on at least one of a specific period (e.g., a set of a specific number of opportunities (occasions) for candidate PDSCH reception, or a specific number of monitoring occasions (monitoring occasions) of PDCCH), the number of CCs configured or activated for the UE, the number of TBs (number of layers or rank), the number of CBGs per TB, and the presence or absence of spatial bundling applications. The specific range is also referred to as a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, etc.

[0066] In the Type 1 HARQ-ACK codebook, even if no PDSCH is scheduled for the UE, the UE reserves a HARQ-ACK bit for that PDSCH within a specific range. If the UE determines that the PDSCH is not actually scheduled, it can feedback this bit as a NACK bit.

[0067] On the other hand, in the case of type 2 HARQ-ACK codebook, the UE may also feed back the scheduled HARQ-ACK bits for the PDSCH within the above-mentioned specific range.

[0068] Specifically, the UE may also determine the number of bits of the Type 2 HARQ-ACK codebook based on a specific field in the DCI (e.g., the DL allocation index (Downlink Assignment Indicator (Index) (DAI)) field). The DAI field may also include a counter DAI (C-DAI) and a total DAI (T-DAI).

[0069] C-DAI can also represent the counter value of downlink transmissions (PDSCH, data, TB) scheduled during a specific period. For example, the C-DAI in the DCI that schedules data during the specific period can also represent the number counted initially in the frequency domain (e.g., CC) and then in the time domain during the specific period. For example, C-DAI can also be equivalent to the following value: for one or more DCIs included in a specific period, the value obtained by counting PDSCH receptions or SPS releases in ascending order of serving cell indexes and then in ascending order of PDCCH monitoring opportunities.

[0070] T-DAI may also indicate the total value (total number) of data scheduled within a specific period. For example, T-DAI within the DCI for data scheduled at a certain time unit (e.g., a PDCCH monitoring opportunity) within the specific period may also indicate the total number of data scheduled up to that time unit (also referred to as a point, timing, etc.) within the specific period.

[0071] In addition, the HARQ-ACK codebook is being separately set for different service types (or PDSCH or HARQ-ACK with different priorities) (see Figure 1 ). That is, in order to support multiple service types (or multiple priorities), it is considered to simultaneously construct multiple HARQ-ACK codebooks. For example, a first HARQ-ACK codebook (CB#1) corresponding to URLLC (e.g., first priority) and a second HARQ-ACK codebook (CB#2) corresponding to eMBB (e.g., second priority) may also be constructed.

[0072] In this case, the first PUCCH configuration parameter corresponding to the first HARQ-ACK codebook (e.g., PUCCH configuration or PUCCH configuration parameters) and the second PUCCH configuration parameter corresponding to the second HARQ-ACK codebook may also be supported or configured separately. The PUCCH configuration parameter may also be at least one of the PUCCH resource (or PUCCH resource set) used in HARQ-ACK transmission, the PUCCH transmission timing (e.g., K1 set), the maximum coding rate (e.g., max-code rate), and the PUCCH transmission power.

[0073] In this case, the first PUCCH setting information may be applied to HARQ-ACK feedback for URLLC, and the second PUCCH setting information may be applied to HARQ-ACK feedback for eMBB.

[0074] <Unauthorized Zone>

[0075] In unlicensed bands (e.g., 2.4 GHz band, 5 GHz band, 6 GHz band, etc.), it is envisioned that multiple systems, such as Wi-Fi systems and systems supporting Licensed-Assisted Access (LAA) (LAA systems), will coexist, and therefore conflict avoidance and / or interference control of transmissions between these multiple systems is considered necessary.

[0076] In the LAA of the existing LTE system (e.g., Rel. 13), the data sending device performs monitoring (Listen Before Talk (LBT)), Clear Channel Assessment (CCA)), carrier sensing, channel detection, sensing, and channel access procedure) to confirm whether there are any other devices (e.g., base stations, user terminals, Wi-Fi devices, etc.) sending data in the unlicensed band.

[0077] The transmitting device may be, for example, a base station (e.g., gNB: gNodeB) in the downlink (DL) or a user terminal (e.g., User Equipment (UE)) in the uplink (UL). Furthermore, the receiving device that receives data from the transmitting device may be, for example, a user terminal in the DL or a base station in the UL.

[0078] In the existing LAA of the LTE system, the transmitting device starts data transmission after a specific period (for example, immediately thereafter or during a backoff period) from when it detects that no other device is transmitting (idle state) in the LBT.

[0079] The use of unlicensed bands is also being studied in future wireless communication systems (e.g., also known as 5G, 5G+, New Radio (NR), 3GPP Rel.15 and later). NR systems using unlicensed bands may also be referred to as NR-Unlicensed (U) systems, NR LAA systems, etc.

[0080] Dual Connectivity (DC) between the licensed band and the unlicensed band, Stand-Alone (SA) in the unlicensed band, etc. may also be included in NR-U.

[0081] For coexistence with other systems or other operators, nodes (e.g., base stations, UEs) in NR-U start transmission after confirming that the channel is idle through LBT.

[0082] In NR-U, when the LBT result is idle, a base station (e.g., gNB) or UE obtains a transmission opportunity (TxOP) and performs transmission. When the LBT result is busy (LBT-busy), the base station or UE does not perform transmission. The time of the transmission opportunity is called the channel occupancy time (COT).

[0083] In addition, LBT-idle can also be replaced by LBT success. LBT-busy can also be replaced by LBT failure.

[0084] <HARQ process>

[0085] For a UE configured with carrier aggregation (CA) or dual connectivity (DC), there can also be an independent HARQ entity per cell (CC) or cell group (CG). The HARQ entity can also manage multiple HARQ processes in parallel.

[0086] In a wireless communication system, data transmission is based on scheduling, and the scheduling information for downlink (DL) data transmission is carried through downlink control information (DCI). Figure 1 It is a diagram showing an example of the relationship among the HARQ entity, HARQ process, and DCI. For the HARQ process, a HARQ process number (HPN) is assigned. The DCI contains a 4-bit HARQ process number field indicating the HARQ process number used in the current data transmission. The HARQ entity manages multiple (up to 16) HARQ processes in parallel. That is, the HARQ process number ranges from HPN0 to HPN15. The HARQ process number is also called the HARQ process ID (HARQ process identifier).

[0087] The unit for transmitting uplink (UL) data in the Physical Uplink Shared Channel (PUSCH) and the unit for transmitting DL data in the Physical Downlink Shared Channel (PDSCH) are also called Transport Blocks (TBs). TBs are units processed by the Media Access Control (MAC) layer. HARQ (retransmission) control can be performed for each TB or for a Code Block Group (CBG) containing one or more Code Blocks (CBs) within a TB.

[0088] The user terminal uses PUCCH (Physical Uplink Control Channel) or PUSCH to send information indicating HARQ positive acknowledgement (ACK) / negative acknowledgement (NACK) to the base station. The HARQ positive acknowledgement / negative acknowledgement indicates whether the decoding of the DL transport block received using PDSCH is successful.

[0089] In the physical layer, when multiple UL data or multiple DL data are not spatially multiplexed, a single HARQ process corresponds to one transport block (TB). In the physical layer, when multiple UL data or multiple DL data are spatially multiplexed, a single HARQ process may also correspond to one or more transport blocks (TBs).

[0090] One-Shot HARQ-ACK Feedback

[0091] Research is underway after Rel.16: In order to provide a transmission opportunity for HARQ-ACK feedback due to LBT failure in the UE or PUCCH detection error in the base station, request or trigger the feedback of the HARQ-ACK codebook containing all HARQ-ACK processes to the UE (see Figure 2 ). The HARQ-ACK process (e.g., DL HARQ-ACK process) may also be HARQ-ACK in all CCs configured for the UE in the PUCCH group.

[0092] exist Figure 2, it shows the situation where HARQ-ACK processes #0, #2, and #4 are fed back according to the request for single-trigger HARQ-ACK feedback.

[0093] Feedback that includes HARQ-ACK (or HARQ-ACK codebook) for all HARQ-ACK processes in all CCs may also be referred to as single-shot HARQ-ACK feedback. Single-shot HARQ-ACK feedback may also be notified from the base station to the UE using a specific DCI format. The specific DCI format may also be a UE-specific DCI format (e.g., DCI format 1_1).

[0094] A UE that is requested or triggered to perform single-shot HARQ-ACK feedback may also use the PUCCH to feed back a codebook containing multiple (eg, all) HARQ-ACK processes in each configured CC.

[0095] In this way, it is assumed that one-shot HARQ-ACK feedback is introduced. One-shot HARQ-ACK feedback may also be referred to as one-time HARQ-ACK feedback, single HARQ-ACK feedback, or one-shot HARQ-ACK.

[0096] However, when single-trigger HARQ-ACK feedback is applied, how to control the transmission (e.g., PUCCH transmission) of HARQ-ACK for different service types (e.g., HARQ-ACK for eMBB, HARQ-ACK for URLLC) becomes a problem.

[0097] For example, when the UE feeds back one HARQ-ACK codebook based on a request or trigger for single-shot HARQ-ACK feedback notified via a certain DCI, how to control the HARQ-ACK included in the HARQ-ACK codebook becomes a problem.

[0098] The inventors of the present invention studied how to apply or control single-shot HARQ-ACK feedback when HARQ-ACK transmission (or HARQ-ACK codebook) is supported for each of multiple service types (or priorities), and came up with this embodiment.

[0099] The following describes the embodiments of the present disclosure in detail with reference to the accompanying drawings. Each of the following methods can be applied individually or in combination. Furthermore, the following embodiments can be applied in both the licensed band and the unlicensed band.

[0100] In the following description, the first priority (High) and the second priority (Low) are used as examples for explanation, but the number and types of priorities are not limited thereto. Three or more types of priorities (or levels) may also be applied. Furthermore, the priority set for each signal or channel may also be set to the UE via higher-layer signaling, etc.

[0101] In the following description, eMBB and URLLC are used as examples of multiple service types, but the types and number of service types are not limited to these. Furthermore, service types can also be set in association with priorities. Furthermore, in the following description, HARQ-ACK feedback based on a single-shot HARQ-ACK feedback request is used as an example, but this embodiment is not limited to this. For example, this embodiment can also be applied to HARQ-ACK feedback other than single-shot HARQ-ACK feedback.

[0102] (First Method)

[0103] In the first method, the case where the UE requests single-trigger HARQ-ACK feedback and uses one (or a common) HARQ-ACK codebook to send HARQ-ACKs corresponding to different service types (for example, Re-Tx HARQ-ACK) is described.

[0104] The network (e.g., a base station) may also use at least one of DCI and higher layer signaling to indicate to the UE a request or trigger for single-shot HARQ-ACK feedback. For example, the UE may also determine whether single-shot HARQ-ACK feedback is available based on the value of a specific field (e.g., a single-shot HARQ-ACK request field) included in a specific DCI format.

[0105] The specific DCI format may be a DCI format used for PDSCH scheduling (eg, at least one of DCI formats 1_0, 1_1, and 1_2). In addition, whether the DCI includes a specific field may be notified or configured from the base station to the UE using higher layer signaling.

[0106] A UE that is requested (or triggered) to provide feedback for a single-shot HARQ-ACK may also include one or more HARQ-ACKs in a single (or common) HARQ-ACK codebook (CB) for feedback. The HARQ-ACKs included in a HARQ-ACK codebook may also be HARQ-ACKs corresponding to a specific HARQ-ACK process (or a specific HARQ-ACK process number).

[0107] The specific HARQ-ACK process may be, for example, a HARQ-ACK process corresponding to a PDSCH scheduled for the UE. In addition, when multiple CCs (or cells) are configured for the UE, the HARQ-ACKs corresponding to the HARQ-ACK processes in the multiple CCs may be included in one HARQ-ACK codebook.

[0108] Even when the HARQ-ACK corresponding to a specific HARQ-ACK process corresponds to different service types or different priorities, the UE can use one HARQ-ACK codebook for HARQ-ACK feedback (see Figure 3 ).

[0109] exist Figure 3 , shows a situation where the HARQ-ACK for the PDSCH of eMBB (or, the second priority) and the HARQ-ACK for the PDSCH of URLLC (or, the first priority) cannot be sent (or is received incorrectly in the base station), and then the UE is requested to single-trigger HARQ-ACK feedback.

[0110] Here, the case where the PUCCH (or PUCCH resources) used for HARQ-ACK transmission of PDSCH for eMBB and the PUCCH used for HARQ-ACK transmission of PDSCH for URLLC are separately configured is shown. The PUCCH of each service type can also be specified or configured by scheduling the DCI (for example, the PUCCH resource indication field) of the PDSCH of each service type.

[0111] Before receiving a single-shot HARQ-ACK feedback request, the UE transmits HARQ-ACK for each service type using the configured PUCCH resources. Upon receiving a single-shot HARQ-ACK feedback request, the UE controls the HARQ-ACK for both the eMBB PDSCH and the URLLC PDSCH using a single HARQ-ACK codebook.

[0112] The HARQ-ACK codebook used in the one-shot HARQ-ACK feedback may be a HARQ-ACK codebook configured in consideration of HARQ-ACK for multiple service types (e.g., CCs used for transmission of each service type, the number of HARQ-ACK processes applied, etc.).

[0113] In addition, in the case of applying multiple HARQ-ACK codebook types with different service types (for example, semi-static HARQ-ACK codebook (type 1) and dynamic HARQ-ACK codebook (type 2)), either type can be selected. Either a specific codebook type (for example, type 1) can be selected, or a codebook type corresponding to a specific service type can be selected. Alternatively, the applied codebook type can either be predefined in the specification or be notified to the UE from the base station using DCI and higher layer signaling.

[0114] <Determination of PUCCH resources>

[0115] In the case of using one HARQ-ACK codebook to transmit HARQ-ACKs corresponding to different service types, the UE can also determine the PUCCH setting parameters (or, PUCCH parameters) used in the transmission of HARQ-ACK based on specific conditions. The PUCCH setting parameters (for example, PUCCH configuration parameter) can also be at least one of the PUCCH resources (or, PUCCH resource set) applied in the transmission of HARQ-ACK, the transmission timing of the PUCCH (for example, K1 set), the maximum coding rate (for example, max-code rate), and the transmission power of the PUCCH.

[0116] The UE can also use at least one of the following Option 1-1 to Option 1-3 to determine the PUCCH setting parameters used in HARQ-ACK feedback.

[0117] [Option 1-1]

[0118] The UE can also apply the PUCCH setting parameters corresponding to the HARQ-ACK of a specific service type (see Figure 4 ). In Figure 4 , it shows the case where for the HARQ-ACK for URLLC PDSCH (hereinafter, also referred to as HARQ-ACK for URLLC), the first PUCCH setting parameter (here, the first PUCCH resource set) is set, and for the HARQ-ACK for eMBB, the second PUCCH setting parameter (here, the second PUCCH resource set) is set.

[0119] The first PUCCH resource set can also be set by at least one of the DCI and higher layer signaling used to schedule the URLLC PDSCH. In addition, the second PUCCH resource set can also be set by at least one of the DCI and higher layer signaling used to schedule the eMBB PDSCH.

[0120] The UE may also control the UE to always use the first PUCCH resource when sending a codebook containing URLLC HARQ-ACK and eMBB HARQ-ACK via a single-trigger HARQ-ACK feedback request (option 1-1-1). Thus, a PUCCH resource configured with high reliability and low latency can be used as the PUCCH resource for HARQ-ACK feedback.

[0121] Alternatively, control may be performed so that, when a codebook including HARQ-ACK for URLLC and HARQ-ACK for eMBB is transmitted using a one-shot HARQ-ACK feedback request, the second PUCCH resource is always used (option 1-1-2).

[0122] [Option 1-2]

[0123] The UE may also determine the PUCCH (or PUCCH configuration parameters) to be applied in the one-shot HARQ-ACK feedback based on the notification from the base station.

[0124] For example, which PUCCH configuration parameter to apply among the PUCCH configuration parameters configured for each service type may be notified from the base station or configured to the UE using higher layer signaling (option 1-2-1).

[0125] Alternatively, which of the PUCCH configuration parameters set for each service type is to be applied may be indicated from the base station to the UE using DCI (option 1-2-2). The DCI used in the notification may also be a DCI (or PDCCH) for a single-trigger HARQ-ACK feedback request (see Figure 5 ).

[0126] In this case, a specific field of the DCI for the single-trigger HARQ-ACK feedback request can also be used to specify specific PUCCH setting parameters. The specific field can be a field for notifying priority (for example, a priority indicator field) or a re-set field. For example, when the bit value of the specific field is "1", the UE applies the PUCCH setting parameters corresponding to the HARQ-ACK for URLLC (for example, the first PUCCH resource) (see Figure 5 ). When the bit value of the specific field is "0", the UE applies the PUCCH setting parameters corresponding to the HARQ-ACK for eMBB (for example, the second PUCCH resource).

[0127] When the DCI for a single-trigger HARQ-ACK feedback request does not contain a specific field, the UE may also select the PUCCH configuration parameters corresponding to the HARQ-ACK for a specific service type. The specific service type may be pre-defined in the specification or notified or configured to the UE by the base station through higher layer signaling.

[0128] [Options 1-3]

[0129] The UE may also combine and apply PUCCH configuration parameters corresponding to each service type. For example, the UE may combine and apply a portion of the PUCCH configuration parameters corresponding to HARQ-ACK for URLLC (e.g., PUCCH resource set, maximum coding rate) and a portion of the PUCCH configuration parameters corresponding to HARQ-ACK for eMBB (e.g., PUCCH power idiom, K1 set).

[0130] The PUCCH configuration parameters selected for each service type may be pre-defined in the specification, or may be notified or configured to the UE from the base station through higher layer signaling or the like.

[0131] Alternatively, at least one of the PUCCH configuration information used in the single-shot HARQ-ACK feedback may be reset via at least one of DCI (e.g., DCI used in the single-shot HARQ-ACK feedback request) and higher-layer signaling. In this case, the PUCCH configuration parameters can be flexibly set for the HARQ-ACK codebook containing multiple service types.

[0132] (Second Method)

[0133] In the second method, the UE's request for single-trigger HARQ-ACK feedback is based on the situation where different HARQ-ACK codebooks (or PUCCH setting parameters) are used according to different service types (or priorities) to send HARQ-ACK corresponding to each service type.

[0134] The base station may also use at least one of DCI and higher layer signaling to indicate a request or trigger for single-trigger HARQ-ACK feedback to the UE. For example, the UE may also determine whether single-trigger HARQ-ACK feedback is available based on the value of a specific field (e.g., a single-trigger HARQ-ACK request field) included in a specific DCI format.

[0135] The specific DCI format may be a DCI format used for PDSCH scheduling (eg, at least one of DCI formats 1_0, 1_1, and 1_2). In addition, whether the DCI includes a specific field may be notified or configured to the UE by the base station using higher layer signaling.

[0136] A UE for which single-trigger HARQ-ACK feedback is requested (or triggered) may also provide feedback using a different HARQ-ACK codebook (CB) for each service type (or priority). In addition, single-trigger HARQ-ACK feedback may also be requested (or triggered) separately for each service type. In this case, the UE may also apply different PUCCH configuration parameters (e.g., PUCCH resources) to the HARQ-ACK of each service type for which a single-trigger HARQ-ACK feedback request is separately notified.

[0137] For example, a HARQ-ACK codebook containing only HARQ-ACK for eMBB may also be reported in the PUCCH resources for eMBB. Furthermore, a HARQ-ACK codebook containing only HARQ-ACK for URLLC may also be reported in the PUCCH resources for URLLC.

[0138] Figure 6 It shows the situation where HARQ-ACK for PDSCH of eMBB (or, second priority) and HARQ-ACK for PDSCH of URLLC (or, first priority) cannot be sent (or reception error in the base station), and then the UE is requested to single-trigger HARQ-ACK feedback.

[0139] Before receiving a single-shot HARQ-ACK feedback request, the UE performs HARQ-ACK feedback using the PUCCH resources configured for each service type. Upon receiving a single-shot HARQ-ACK feedback request, the UE uses a different HARQ-ACK codebook (and PUCCH resources) for each service type to separately control HARQ-ACK feedback for the eMBB PDSCH and HARQ-ACK for the URLLC PDSCH.

[0140] Furthermore, the DCI requesting the one-shot HARQ-ACK feedback may be transmitted separately for each service type, or one-shot HARQ-ACK feedback may be performed for multiple service types based on one DCI.

[0141] In the case where the HARQ-ACK codebook for single-trigger HARQ-ACK feedback contains HARQ-ACKs for a specific service type, the PUCCH resources corresponding to the specific service type are applied in the same way as before receiving the single-trigger HARQ-ACK feedback request.

[0142] The correspondence (or mapping) between the request for single-trigger HARQ-ACK feedback or the triggering DCI (request / triggering DCI) and the HARQ-ACK bits can also be determined based on a specific field of the DCI (see Figure 7A , Figure 7B ). The specific field can also be a field for notifying the priority (e.g., the Priority Indicator field).

[0143] Through the request / triggering DCI, the service type for which single-trigger HARQ-ACK feedback is to be performed is specified based on the field for indicating the single-trigger HARQ-ACK request (e.g., One-shot HARQ-ACK request) and the specific field. On the other hand, through the DCI used in the scheduling of the PDSCH, the service type for which HARQ-ACK feedback is to be performed is specified based on the specific field. Additionally, it can also be that the field for indicating the single-trigger HARQ-ACK request (e.g., One-shot HARQ-ACK request) is not included in the structure by the DCI used in the scheduling of the PDSCH (see Figure 7A , Figure 7B ).

[0144] <Determination of HARQ-ACK codebook>

[0145] In the case where, according to the single-trigger HARQ-ACK feedback request, different HARQ-ACK codebooks are used to transmit the HARQ-ACKs corresponding to each service type, the UE can also apply at least one of the following Options 2-1 to Option 2-4.

[0146] [Option 2-1]

[0147] Here, it is assumed that the HARQ-ACK process numbers and CCs assigned to the UE are dynamically scheduled (or applied) for multiple service types. That is, it is assumed that the same HARQ-ACK process numbers and CCs can be applied to multiple service types. In addition, it is assumed that the HARQ-ACK codebook size is set semi-statically based on the number of CCs and the number of HARQ-ACK processes, etc. [[ID=2⑧]]

[0148] The HARQ-ACK codebook (or single-shot HARQ-ACK feedback) may also be requested or specified based on the DCI. The HARQ-ACK codebook may also be a structure containing all HARQ-ACK process numbers in the CC configured for the UE. In addition, the UE may also determine the structure of the HARQ-ACK codebook based on the DCI (request / trigger DCI) requesting single-shot HARQ-ACK feedback (or HARQ-ACK codebook) (see Figure 8A ).

[0149] exist Figure 8A , shows a scenario where two CCs (CC#1 and CC#2) are configured for a UE supporting eMBB and URLLC, and eight HARQ-ACK processes can be configured for each CC. Here, the PDSCH for eMBB (corresponding to HARQ-ACK process #1) is scheduled in CC#1, and the PDSCH for eMBB (corresponding to HARQ-ACK process #3) and two PDSCHs for URLLC (corresponding to HARQ-ACK processes #5 and #6) are scheduled in CC#2.

[0150] The UE may also determine the service type (or priority) to which single-shot HARQ-ACK feedback is applied based on a specific field of the DCI (e.g., priority indicator) when single-shot HARQ-ACK feedback is requested through request / trigger DCI (e.g., one-shot HARQ-ACK request = 1).

[0151] For example, when the request / trigger DCI corresponds to the first priority for URLLC (e.g., high HARQ-ACK priority), the UE may also report the HARQ-ACK for URLLC as a valid HARQ-ACK value (or include it in the codebook). In this case, the HARQ-ACK for URLLC may also be mapped to a specific position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see Figure 8B ).

[0152] Figure 8B An example of a HARQ-ACK codebook (CB#1) corresponding to URLLC is shown. The UE includes HARQ-ACK for URLLC (here, HARQ-ACK processes #5 and #6 of CC#2) in CB#1 as a valid HARQ-ACK value.

[0153] Alternatively, a configuration may be employed in which the UE does not report HARQ-ACK processes for eMBB or other unscheduled HARQ-ACK processes as valid HARQ-ACKs. The UE may also report HARQ-ACK values ​​that are not reported as valid HARQ-ACKs as fixed values ​​(e.g., either NACK or ACK). Furthermore, the position of each HARQ-ACK process within the codebook may be determined based on at least one of the HARQ-ACK process number and the CC index.

[0154] exist Figure 8B , it shows the situation where the UE treats the HARQ-ACK for eMBB (here, HARQ-ACK process #1 of CC#1 and HARQ-ACK process #3 of CC#2) as a non-valid HARQ-ACK value (here, NACK) and includes it in CB#1.

[0155] When the request / trigger DCI corresponds to the second priority level for eMBB (e.g., low HARQ-ACK priority), the UE may also report the HARQ-ACK for eMBB as a valid HARQ-ACK value (or include it in the codebook). In this case, the HARQ-ACK for eMBB may also be mapped to a specific position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see Figure 8C ).

[0156] Figure 8C An example of a HARQ-ACK codebook (CB#2) for eMBB is shown. The UE includes HARQ-ACK for eMBB (here, HARQ-ACK process #1 for CC#1 and HARQ-ACK process #3 for CC#2) as a valid HARQ-ACK value in CB#2.

[0157] On the other hand, it can also be a structure as follows: the UE does not report the HARQ-ACK process used for URLLC or other HARQ-ACK processes that are not scheduled as valid HARQ-ACK. Figure 8B , shows the situation where the UE includes the HARQ-ACK for URLLC (here, HARQ-ACK processes #5 and #6 of CC#2) as a non-valid HARQ-ACK value (here, NACK) in CB#2.

[0158] By this means, even when the HARQ-ACK process number and CC configured for the UE are dynamically scheduled for multiple service types, it is possible to appropriately configure the HARQ-ACK codebook corresponding to each service type.

[0159] [Option 2-2]

[0160] Here, it is assumed that the PDSCH corresponding to each service type is scheduled in different frequency domains (for example, different CCs). In other words, it is assumed that one of the PDSCH for eMBB and the PDSCH for URLLC is scheduled in a certain CC (for example, CC#1), and the other of the PDSCH for eMBB and URLLC is scheduled in another CC (for example, CC#2).

[0161] Which service type's PDSCH is scheduled in each CC (the association between CC and service type) can be pre-defined in the specification, or can be notified or set to the UE from the base station through higher layer signaling, etc., or can be notified to the UE through request / trigger DCI.

[0162] exist Figure 9A , it is shown that for a UE supporting eMBB and URLLC, two CCs (CC#1 and CC#2) are configured, and eight HARQ-ACK processes can be configured for each CC. In addition, it is shown that the PDSCH for eMBB is scheduled in CC#1, and the PDSCH for URLLC is scheduled in CC#2. Here, it is shown that two PDSCHs for eMBB (corresponding to HARQ-ACK processes #1 and #3) are scheduled in CC#1, and two PDSCHs for URLLC (corresponding to HARQ-ACK processes #5 and #6) are scheduled in CC#2.

[0163] The HARQ-ACK codebook for eMBB (or single-shot HARQ-ACK feedback) may also be requested or specified via the DCI for eMBB. The HARQ-ACK codebook may also include a structure that contains all HARQ-ACK processes corresponding to the eMBB CC. On the other hand, the HARQ-ACK codebook for URLLC (or single-shot HARQ-ACK feedback) may also be requested or specified via the DCI for URLLC. The HARQ-ACK codebook may also include a structure that contains all HARQ-ACK processes corresponding to the URLLC CC.

[0164] The UE may also determine the service type (or priority) to which single-shot HARQ-ACK feedback is applied based on a specific field of the DCI (e.g., priority indicator) when single-shot HARQ-ACK feedback is requested through request / trigger DCI (e.g., one-shot HARQ-ACK request = 1).

[0165] For example, when the request / trigger DCI corresponds to the first priority for URLLC (e.g., high HARQ-ACK priority), the UE may also report the HARQ-ACK for URLLC as a valid HARQ-ACK value. In this case, the HARQ-ACK for URLLC may also be mapped to a specific position in the codebook based on at least one of the HARQ-ACK process number and the CC index of the scheduled URLLC (see Figure 9B ).

[0166] Figure 9B An example of a HARQ-ACK codebook (CB#1) corresponding to URLLC is shown. The HARQ-ACK codebook size can also be determined based on the number of CCs scheduled for URLLC (here, 1 (CC#2)) and the number of HARQ-ACK processes supported in that CC (here, 8 (#0 to #7)). The UE can also include the HARQ-ACK for URLLC (here, HARQ-ACK processes #5 and #6 of CC#2) as a valid HARQ-ACK value in CB#1.

[0167] When the request / trigger DCI corresponds to the second priority level for eMBB (e.g., low HARQ-ACK priority), the UE may also report the HARQ-ACK for eMBB as a valid HARQ-ACK value. In this case, the HARQ-ACK for eMBB may also be mapped to a specific position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see Figure 9C ).

[0168] Figure 9CAn example of a HARQ-ACK codebook (CB#2) for eMBB is shown. The HARQ-ACK codebook size can also be determined based on the number of CCs in which eMBB is scheduled (here, 1 (CC#1)) and the number of HARQ-ACK processes supported in that CC (here, 8 (#0 to #7)). The UE can also include HARQ-ACK for eMBB (here, HARQ-ACK processes #1 and #3 of CC#1) as a valid HARQ-ACK value in CB#2.

[0169] By limiting the CCs in which PDSCHs are scheduled for each service type in this manner, the codebook size can be reduced even when the codebook applied to HARQ-ACK feedback is semi-statically determined (for example, the number of CCs and the number of HARQ-ACK processes).

[0170] [Option 2-3]

[0171] Here, it is assumed that the HARQ-ACK process number set for each CC is associated with the service type (or grouped according to the service type). In other words, in a certain CC, a first HARQ-ACK process group (one or more HARQ-ACK process numbers) may be set for eMBB, and a second HARQ-ACK process group (e.g., another HARQ-ACK process number) may be set for URLLC. The HARQ-ACK process group may also be referred to as a HARQ-ACK process set.

[0172] For example, an odd-numbered HARQ-ACK process number may be set to the service type of one party (e.g., eMBB), and an even-numbered HARQ-ACK process number may be set to the service type of the other party (e.g., URLLC). In addition, the number of HARQ-ACK process numbers associated with each service type may be set to be equal or to be set to more than one service type (e.g., URLLC).

[0173] Furthermore, the HARQ-ACK process number associated with each service type may be defined in the specification or may be notified from the base station to the UE using at least one of higher layer signaling and DCI (e.g., request / trigger DCI). Furthermore, the HARQ-ACK process number corresponding to each service type may be set differently for each CC, or the HARQ-ACK process number corresponding to the service type may be set commonly across multiple CCs.

[0174] The PDSCH corresponding to each service type scheduled to the UE may also apply only the HARQ-ACK process number within the HARQ-ACK process group (HARQ-ACK process set / group) set to the service type.

[0175] exist Figure 10A , it is shown that for eMBB and URLLC UEs, two CCs (CC#1 and CC#2) are set, and 8 HARQ-ACK processes can be set in CC#1, and 4 HARQ-ACK processes can be set in CC#2.

[0176] Furthermore, the diagram shows that in CC#1, a first HARQ-ACK process group {#0, #2, #4, #6} is configured for URLLC, and a second HARQ-ACK process group {#1, #3, #5, #7} is configured for eMBB. Furthermore, the diagram shows that two PDSCHs for eMBB (corresponding to HARQ-ACK processes #1 and #3) and a PDSCH for URLLC (HARQ-ACK process #6) are scheduled in CC#1, while a PDSCH for URLLC (corresponding to HARQ-ACK process #2) is scheduled in CC#2.

[0177] The HARQ-ACK codebook for eMBB (or single-shot HARQ-ACK feedback) may also be requested or specified via the DCI for eMBB. The HARQ-ACK codebook may also be a structure of the HARQ-ACK process included in the HARQ-ACK process group for eMBB in the CC configured for the UE. On the other hand, the HARQ-ACK codebook for URLLC (or single-shot HARQ-ACK feedback) may also be requested or specified via the DCI for URLLC. The HARQ-ACK codebook may also be a structure of the HARQ-ACK process included in the HARQ-ACK process group for URLLC in the CC configured for the UE.

[0178] The UE may also determine the service type (or priority) to which single-shot HARQ-ACK feedback is applied based on a specific field of the DCI (e.g., priority indicator) when single-shot HARQ-ACK feedback is requested through request / trigger DCI (e.g., one-shot HARQ-ACK request = 1).

[0179] For example, when the request / trigger DCI corresponds to the first priority for URLLC (e.g., high HARQ-ACK priority), the UE may also report the HARQ-ACK for URLLC as a valid HARQ-ACK value. In this case, the HARQ-ACK for URLLC may also be mapped to a specific position in the codebook based on at least one of the CC index and the HARQ-ACK process number set to the UE (see Figure 10B ).

[0180] Figure 10B An example of a HARQ-ACK codebook (CB#1) corresponding to URLLC is shown. The HARQ-ACK codebook size can also be determined based on the number of CCs configured for the UE (here, 2) and the number of HARQ-ACK processes included in the HARQ-ACK process group for URLLC in each CC (here, 4 in CC#1 and 2 in CC#2). The UE includes the HARQ-ACK for URLLC (here, HARQ-ACK process #6 in CC#1 and HARQ-ACK process #2 in CC#2) as a valid HARQ-ACK value in CB#1.

[0181] In the case where the request / trigger DCI corresponds to the second priority level for eMBB (e.g., low HARQ-ACK priority), the UE may also report the HARQ-ACK for eMBB as a valid HARQ-ACK value. In this case, the HARQ-ACK for eMBB may also be mapped to a specific position in the codebook based on at least one of the CC index and the HARQ-ACK process number set to the UE (see Figure 10C ).

[0182] Figure 10C An example of a HARQ-ACK codebook (CB#2) for eMBB is shown. The HARQ-ACK codebook size may also be determined based on the number of CCs configured for the UE (here, 2) and the number of HARQ-ACK processes included in the HARQ-ACK process group for eMBB in each CC (here, 4 in CC#1 and 2 in CC#2). The UE may also include HARQ-ACK for eMBB (here, HARQ-ACK processes #1 and #3 in CC#1) as a valid HARQ-ACK value in CB#2.

[0183] By associating different HARQ-ACK process numbers with multiple service types in this manner, the codebook size can be reduced even when the codebook applied to HARQ-ACK feedback is semi-statically determined (e.g., the number of CCs and the number of HARQ-ACK processes).

[0184] [Options 2-4]

[0185] Here, we assume that the HARQ-ACK process number and CC assigned to the UE are dynamically scheduled for multiple service types. In other words, we assume that the same HARQ-ACK process number and CC can be applied to multiple service types. Furthermore, we assume that the HARQ-ACK codebook size is dynamically configured based on the scheduled PDSCH.

[0186] In this case, the UE can also control HARQ-ACK feedback (e.g., HARQ-ACK codebook generation) based on the counter DAI and total DAI included in the DCI. For example, the HARQ-ACK codebook size is determined based on the total DAI included in the request / trigger DCI, and the position of the HARQ-ACK in the codebook is determined based on the counter DAI included in the DAI used to schedule the PDSCH (see Figure 11A ).

[0187] exist Figure 11A In the DCI for scheduling PDSCH (#1) for eMBB, a counter DAI (=1) and a total DAI (=1) are included. In addition, a counter DAI (=1) and a total DAI (=1) are included in the DCI for scheduling PDSCH (#2) for URLLC, and a counter DAI (=2) and a total DAI (=2) are included in the DCI for scheduling PDSCH (#3).

[0188] When the UE receives a request / trigger DCI for requesting single-trigger HARQ-ACK feedback for URLLC, it includes the HARQ-ACK for URLLC (here, #2 and #3) in the codebook for URLLC (CB#1) based on the request / trigger DCI (see Figure 11B ). The codebook size of CB#1 may also be determined based on the total DAI included in the request / trigger DCI.

[0189] In addition, the position of the HARQ-ACK corresponding to each PDSCH in the codebook can also be determined based on the counter DAI included in the DCI used to schedule the PDSCH. Here, the HARQ-ACK corresponding to PDSCH #2 with a smaller counter DAI value is mapped to position #0, and the HARQ-ACK corresponding to PDSCH #3 is mapped to position #1.

[0190] When the UE receives a request / trigger DCI for requesting a single-shot HARQ-ACK feedback for eMBB, the UE includes the HARQ-ACK for eMBB (here, #1) in the codebook for eMBB (CB#2) based on the request / trigger DCI (see Figure 11C ). The codebook size of CB#2 may also be determined based on the total DAI included in the request / trigger DCI.

[0191] Furthermore, the position of the HARQ-ACK corresponding to each PDSCH in the codebook may also be determined based on the counter DAI included in the DCI for scheduling the PDSCH. Here, the case where the HARQ-ACK corresponding to PDSCH #1 is mapped to position #0 is shown.

[0192] In addition, the above description shows the case where the codebook size for single-shot HARQ-ACK feedback is determined based on the total DAI included in the request / trigger DCI, but the present invention is not limited to this. For example, the codebook size may also be determined based on the total DAI included in the last DCI used to schedule the PDSCH of each service type.

[0193] In addition, in the second embodiment, the HARQ-ACK codebook applied to the one-shot HARQ-ACK feedback is described, but the HARQ-ACK codebook can also be applied to HARQ-ACK feedback performed before the one-shot HARQ-ACK feedback request.

[0194] <Changes>

[0195] The single-shot HARQ-ACK feedback described in the first embodiment and the single-shot HARQ-ACK feedback described in the second embodiment may also be combined (eg, switched) for application.

[0196] For example, whether single-shot HARQ-ACK feedback includes multiple service types (eMBB and URLLC) may be notified from the base station to the UE using at least one of higher layer signaling and L1 signaling. The L1 signaling may also be DCI (eg, request / trigger DCI).

[0197] When notified via L1 signaling, a new field or an existing field may be used to specify whether single-shot HARQ-ACK feedback supports a structure containing multiple service types. A specific bit field (e.g., a 2-bit field) may also be set in the request / trigger DCI to notify information related to the service type to which single-shot HARQ-ACK feedback (or one HARQ-ACK codebook) is applied.

[0198] For example, it can also indicate that when a specific bit field is "00", single-trigger HARQ-ACCK feedback supports multiple service types, when it is "01", single-trigger HARQ-ACK feedback only includes eMBB, and when it is "10", single-trigger HARQ-ACK feedback only includes URLLC.

[0199] (Wireless Communication System)

[0200] The following describes a configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above-described embodiments of the present disclosure.

[0201] Figure 12 This figure shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may also be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP) or the fifth generation mobile communication system New Radio (5G NR).

[0202] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0203] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0204] The wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) where both MN and SN are NR base stations (gNB)).

[0205] The wireless communication system 1 may also include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are narrower than the macrocell C1. User terminals 20 may also be located within at least one of the cells. The arrangement and number of cells and user terminals 20 are not limited to those shown in the figure. Hereinafter, when not distinguishing between base stations 11 and 12, they are collectively referred to as base stations 10.

[0206] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0207] Each CC may also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may also be included in FR1, and the small cell C2 may also be included in FR2. For example, FR1 may be a frequency band below 6 GHz (below 6 GHz (sub-6 GHz)), and FR2 may be a frequency band higher than 24 GHz (above 24 GHz (above-24 GHz)). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to this. For example, FR1 may also be equivalent to a frequency band higher than FR2.

[0208] Furthermore, in each CC, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD).

[0209] Multiple base stations 10 may also be connected via wired (e.g., optical fiber based on Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11, which is equivalent to the upper station, may also be referred to as an Integrated Access Backhaul (IAB) donor, and the base station 12, which is equivalent to the relay station, may also be referred to as an IAB node.

[0210] The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The core network 30 may also include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0211] The user terminal 20 may also be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0212] In the wireless communication system 1, a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used.

[0213] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be applied to the UL and DL radio access schemes.

[0214] As downlink channels, the wireless communication system 1 may use a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20), a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc.

[0215] In addition, as uplink channels, the wireless communication system 1 can also use an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20), an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc.

[0216] The PDSCH is used to transmit user data, higher-layer control information, and system information blocks (SIBs). The PUSCH can also be used to transmit user data, higher-layer control information, and the Master Information Block (MIB). The PBCH can also be used to transmit the Master Information Block (MIB).

[0217] The lower layer control information may also be transmitted via the PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

[0218] In addition, the DCI that schedules the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI that schedules the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be replaced by DL data, and the PUSCH may also be replaced by UL data.

[0219] In PDCCH detection, a control resource set (CORESET) and a search space can also be used. A CORESET corresponds to the resources for searching for DCI. A search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space settings.

[0220] A search space may also correspond to PDCCH candidates that correspond to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. In addition, the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc., used in this disclosure, may be used interchangeably.

[0221] Uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.), and a scheduling request (SR) may also be transmitted via the PUCCH. A random access preamble used to establish a connection with a cell may also be transmitted via the PRACH.

[0222] In the present disclosure, downlink, uplink, etc. may be expressed without the word "link." Furthermore, various channels may be expressed without the word "physical" at the beginning.

[0223] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may also be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may also be transmitted.

[0224] For example, a synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SSs (PSS, SSS) and PBCHs (and DMRS for PBCHs) may also be referred to as an SS / PBCH block or an SS block (SSB). Furthermore, SSs and SSBs may also be referred to as reference signals.

[0225] In addition, as an uplink reference signal (UL-RS), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. can also be transmitted in the wireless communication system 1. In addition, DMRS can also be called a user terminal specific reference signal (UE-specific Reference Signal).

[0226] (Base Station)

[0227] Figure 13This figure shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface (transmission line interface) 140. Furthermore, more than one of each of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission path interface 140 may be provided.

[0228] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also assumed that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may be omitted.

[0229] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on the common knowledge in the technical field to which this disclosure relates.

[0230] The control unit 110 may also control signal generation, scheduling (e.g., resource allocation, mapping), etc. It may also control transmission, reception, and measurement using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. The control unit 110 may also generate data, control information, sequences, etc. to be transmitted as signals, and forward them to the transceiver unit 120. The control unit 110 may also perform call processing (setting up, releasing, etc.) for communication channels, manage the status of the base station 10, and manage radio resources.

[0231] The transceiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter (phase shifter), a measurement circuit, a transceiver circuit, and the like, which are described based on the common knowledge in the technical field involved in this disclosure.

[0232] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0233] The transmitting and receiving antenna 130 can be formed of an antenna described based on the common knowledge in the technical field to which this disclosure relates, such as an array antenna.

[0234] The transmitting and receiving unit 120 may also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the aforementioned uplink channel, uplink reference signal, etc.

[0235] The transmitting and receiving unit 120 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmit beam and a receive beam.

[0236] The sending and receiving unit 120 (sending processing unit 1211) can also perform processing on the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (for example, RLC retransmission control), the Medium Access Control (MAC) layer (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 110 to generate a bit string to be sent.

[0237] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0238] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0239] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received by the transmitting and receiving antenna 130 .

[0240] The transmitting and receiving unit 120 (receiving processing unit 1212) can also apply receiving processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0241] The transmitting and receiving unit 120 (measuring unit 123) may also perform measurements related to the received signal. For example, the measuring unit 123 may also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc. based on the received signal. The measuring unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ)), signal to interference plus noise ratio (SINR), signal to noise ratio (SNR)), signal strength (e.g., received signal strength indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 110.

[0242] The transmission path interface 140 can also send and receive signals (return signaling) between the devices included in the core network 30, other base stations 10, etc., and can also obtain and transmit user data (user plane data) and control plane data for the user terminal 20.

[0243] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be constituted by at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0244] The transmitting and receiving unit 120 may also transmit downlink control information for triggering feedback of one-shot HARQ-ACK.

[0245] When HARQ-ACK feedback is performed based on downlink information, the control unit 110 may also control the reception of a codebook containing HARQ-ACKs corresponding to multiple service types or HARQ-ACKs of different priorities. Alternatively, when HARQ-ACK feedback is performed based on downlink information, the control unit 110 may also control the reception of codebooks containing HARQ-ACKs corresponding to multiple service types or HARQ-ACKs of different priorities.

[0246] (User Terminal)

[0247] Figure 14 This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0248] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, but it is also assumed that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may be omitted.

[0249] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on the common knowledge in the technical field to which this disclosure relates.

[0250] The control unit 210 may also control signal generation, mapping, etc. The control unit 210 may also control transmission, reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 may also generate data, control information, sequences, etc. to be transmitted as signals and forward them to the transmission and reception unit 220.

[0251] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on the common knowledge in the technical field involved in this disclosure.

[0252] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit or may be composed of a transmitting unit and a receiving unit. The transmitting unit may also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0253] The transmitting and receiving antenna 230 can be formed of an antenna described based on the common knowledge in the technical field to which this disclosure relates, such as an array antenna.

[0254] The transmitting and receiving unit 220 may also receive the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the aforementioned uplink channel, uplink reference signal, etc.

[0255] The transmitting and receiving unit 220 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

[0256] The sending and receiving unit 220 (sending processing unit 2211) can also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 210 to generate a bit string to be sent.

[0257] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0258] In addition, whether or not to apply DFT processing may also be based on the transform precoding setting. For a certain channel (e.g., PUSCH), if transform precoding is activated (enabled), the transmitting / receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the aforementioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transmitting / receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the aforementioned transmission processing without performing DFT processing.

[0259] The transmitting and receiving unit 220 (RF unit 222 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 230 .

[0260] On the other hand, the transmitting and receiving unit 220 (RF unit 222 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received by the transmitting and receiving antenna 230 .

[0261] The transmitting and receiving unit 220 (receiving processing unit 2212) can also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0262] The transmitting and receiving unit 220 (measuring unit 223) may also perform measurements related to received signals. For example, the measuring unit 223 may also perform RRM measurements, CSI measurements, etc. based on the received signals. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 210.

[0263] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0264] The transmitting and receiving unit 220 receives downlink control information for triggering feedback of one-shot HARQ-ACK.

[0265] When HARQ-ACK feedback is performed based on downlink information, the control unit 210 may also control feedback using a common codebook for HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities. HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities may also be triggered simultaneously by downlink control information.

[0266] The control unit 210 may also determine the uplink shared channel to be used in the HARQ-ACK feedback based on the configuration information of the uplink control channel configured for a specific service type or a specific priority. Alternatively, the control unit 210 may also determine the uplink shared channel to be used in the HARQ-ACK feedback based on the downlink control information.

[0267] Alternatively, when HARQ-ACK feedback is performed based on downlink information, the control unit 210 may also control feedback using different codebooks for HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities. HARQ-ACKs corresponding to multiple service types or HARQ-ACKs with different priorities may also be triggered separately by downlink control information.

[0268] For HARQ-ACKs of multiple service types or HARQ-ACKs of different priorities, at least one of a common HARQ-ACK process number and a common component carrier may also be applied. For HARQ-ACKs of multiple service types or HARQ-ACKs of different priorities, at least one of different HARQ-ACK process numbers and different component carriers may also be applied.

[0269] (Hardware Structure)

[0270] In addition, the block diagrams used in the description of the above embodiments show blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented by a device that is physically or logically combined, or two or more physically or logically separated devices can be directly or indirectly connected (for example, by wired, wireless, etc.) and implemented by these multiple devices. The functional block can also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0271] Here, the functions include judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that implements a sending function may also be referred to as a transmitting unit, a transmitter, etc. Any of them are as described above, and the implementation method is not particularly limited.

[0272] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 15This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and user terminal 20 described above can also 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, and the like.

[0273] In addition, in this disclosure, the terms such as device, circuit, equipment, section, and unit are interchangeable. The hardware structure of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

[0274] For example, although only one processor 1001 is shown, multiple processors may be provided. Furthermore, processing may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, processor 1001 may be implemented using more than one chip.

[0275] Regarding the various functions in the base station 10 and the user terminal 20, for example, they are achieved by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0276] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, at least a portion of the aforementioned control unit 110 (210) and the transmitting and receiving unit 120 (220) may also be implemented by the processor 1001.

[0277] In addition, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and performs various processes based on them. As a program, a program that causes a computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks can also be implemented similarly.

[0278] The memory 1002 may also be a computer-readable recording medium, for example, composed of 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), or other appropriate storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store executable programs (program code), software modules, etc. for implementing the wireless communication method according to an embodiment of the present disclosure.

[0279] The storage 1003 may also be a computer-readable recording medium, such as a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc ROM (CD-ROM)), etc.), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, or a key drive), a magnetic stripe, a database, a server, or other appropriate storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0280] The communication device 1004 is hardware (a transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like. To implement at least one of frequency division duplex (FDD) and time division duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like. For example, the aforementioned transmitting and receiving unit 120 (220) and the transmitting and receiving antenna 130 (230) may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated from the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0281] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, light emitting diode (LED) lamp, etc.). Alternatively, the input device 1005 and the output device 1006 may be integrated (e.g., a touch panel).

[0282] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0283] Furthermore, the base station 10 and user terminal 20 may also 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 may use this hardware to implement part or all of each functional block. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0284] (Variation)

[0285] In addition, the terms described in this disclosure and the terms required for understanding this disclosure may also be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be replaced with each other. In addition, a signal may also be a message. A reference signal may also be referred to as RS, or may be referred to as a pilot, pilot signal, etc. depending on the applied standard. In addition, a component carrier (CC) may also be referred to as a cell, frequency carrier, carrier frequency, etc.

[0286] A radio frame can also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) that is independent of the parameter set (numerology).

[0287] Here, a parameter set may also refer to communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set may also represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0288] A time slot may also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Furthermore, a time slot may also be a time unit based on a parameter set.

[0289] A time slot may also contain multiple mini-slots. Each mini-slot may also consist of one or more symbols in the time domain. Furthermore, a mini-slot may also be referred to as a sub-slot. A mini-slot may also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-slots may also be referred to as PDSCH (PUSCH) mapping type B.

[0290] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-time slots, and symbols may also be referred to by their respective equivalents. Furthermore, the terms frame, subframe, time slot, mini-time slot, and symbol may be used interchangeably in this disclosure.

[0291] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. In other words, at least one of the subframe and the TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. In addition, the unit representing the TTI can also be called a time slot, a mini-time slot, etc. instead of a subframe.

[0292] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the frequency bandwidth and transmit power available to each user terminal) in TTI units. The definition of TTI is not limited to this.

[0293] The TTI may also be a unit of time for transmitting channel-coded data packets (transport blocks), code blocks, code words, etc., and may also be a unit of processing for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which the transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

[0294] Furthermore, when a time slot or a mini-time slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-time slots) may also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit for scheduling may also be controlled.

[0295] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini-slot, a subslot, a time slot, etc.

[0296] In addition, long TTI (for example, normal TTI, subframe, etc.) can also be replaced by TTI with a time length exceeding 1ms, and short TTI (for example, shortened TTI, etc.) can also be replaced by TTI with a TTI length smaller than long TTI and greater than 1ms.

[0297] A resource block (RB) is a unit of resource allocation in the time and frequency domains. In the frequency domain, it may also include one or more consecutive subcarriers (subcarriers). The number of subcarriers included in an RB may be the same regardless of the parameter set, for example, it may be 12. The number of subcarriers included in an RB may also be determined based on the parameter set.

[0298] In addition, an RB may also include one or more symbols in the time domain, and may also be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks.

[0299] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

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

[0301] A Bandwidth Part (BWP) (also referred to as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a carrier. Common RBs can also be identified by their index relative to the common reference point of the carrier. PRBs can also be defined within a BWP and assigned a number within that BWP.

[0302] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured within one carrier.

[0303] At least one of the configured BWPs may be activated, and the UE may not assume that it will transmit or receive specific signals / channels outside of the activated BWP. In addition, the terms "cell," "carrier," and the like in this disclosure may be replaced with "BWP."

[0304] The above-mentioned structures of radio frames, subframes, slots, mini-slots, and symbols are merely examples. For example, various modifications may be made to the number of subframes in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots within a slot, the number of symbols and RBs within a slot or mini-slot, the number of subcarriers within an RB, the number of symbols within a TTI, the symbol length, and the cyclic prefix (CP) length.

[0305] Furthermore, the information and parameters described in this disclosure may be expressed as absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may be indicated by specific indexes.

[0306] In this disclosure, the names used for parameters, etc., are not intended to be limiting in any respect. Furthermore, the mathematical formulas for these parameters, etc., may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can 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 respect.

[0307] Information, signals, and the like described in this disclosure may also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like that may be referred to throughout the foregoing description may also be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0308] Furthermore, information, signals, etc. can be output in at least one of the following directions: from a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0309] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or appended. Output information, signals, etc. may also be deleted. Input information, signals, etc. may also be sent to other devices.

[0310] The notification of information is not limited to the methods / implementations described in the present disclosure, and may also be performed by other methods. For example, the notification of information in the present disclosure may also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI))), uplink control information (Uplink Control Information (UCI))), high-layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB)), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0311] In addition, physical layer signaling may also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as RRC message, for example, RRC Connection Setup message, RRC Connection Reconfiguration message, etc. In addition, MAC signaling may also be notified using MAC Control Element (CE), for example.

[0312] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0313] The determination can be made by a value represented by a bit (0 or 1), a true or false value (Boolean value) represented by true (true) or false (false), or by comparison of numerical values ​​(for example, comparison with a specific value).

[0314] Whether software is called software, firmware, middleware, microcode, hardware description language, or other names, it should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, program, sub-program, software module, application, software application, software package, routine, sub-routine, object, executable file, execution thread, procedure, function, etc.

[0315] Furthermore, software, instructions, information, and the like may also be transmitted and received via a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and a wireless technology (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0316] The terms "system" and "network" used in this disclosure can be used interchangeably. "Network" may also refer to devices included in the network (eg, base stations).

[0317] In the present disclosure, terms such as "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)" "Transmission Configuration Indication state (TCI state)", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.

[0318] In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP))", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" are used interchangeably. In some cases, a base station may be referred to as a macro cell, small cell, femto cell, or pico cell.

[0319] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entire coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within that coverage area.

[0320] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (UE)”, and “terminal” can be used interchangeably.

[0321] A mobile station may also be referred to 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, hand set, user agent, mobile client, client, or several other appropriate terms.

[0322] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, at least one of the base station and the mobile station may also be a device mounted on a mobile object, a mobile object itself, etc. The mobile object may be a vehicle (e.g., a vehicle, an aircraft, etc.), a mobile object that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) device such as a sensor.

[0323] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by communication between multiple user terminals (for example, which may also be referred to as device-to-device (D2D)), vehicle-to-everything (V2X), etc.). In this case, it may also be configured such that the user terminal 20 has the functions of the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be replaced by terms corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may also be replaced by side channels.

[0324] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0325] In the present disclosure, actions are assumed to be performed by a base station, and sometimes, depending on the circumstances, by its upper node. Obviously, in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME)), a Serving-Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0326] The various methods / implementations described in this disclosure may be used individually or in combination, and may be switched between them during execution. Furthermore, the processing procedures, sequences, flow charts, and the like of the various methods / implementations described in this disclosure may be reversed as long as they do not conflict. For example, the elements of various steps described in this disclosure are presented in an illustrative order, but are not limited to the specific order presented.

[0327] The various modes and embodiments described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems using other appropriate wireless communication methods, and next-generation systems based on these. In addition, multiple systems can also be combined for application (for example, LTE or LTE-A, combined with 5G, etc.).

[0328] The phrase “based on” used in this disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0329] Any reference to an element using the designations "first," "second," etc., as used in this disclosure, does not necessarily limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and a second element does not necessarily imply that only two elements may be used, or that the first element must in some way take precedence over the second element.

[0330] The term "determining" as used in this disclosure may encompass a variety of actions. For example, "determining" may also be considered as "judging," calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or other data structure), ascertaining, etc.

[0331] In addition, "judgment (decision)" can also be regarded as a situation of "judgment (decision)" on receiving (for example, receiving information), transmitting (for example, sending information), input (input), output (output), accessing (for example, accessing data in a memory), etc.

[0332] In addition, "judgment (decision)" can also be regarded as a situation in which "judgment (decision)" is made on resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can also be regarded as a situation in which "judgment (decision)" is made on some actions.

[0333] In addition, “judgment (decision)” can also be replaced by “assuming (assuming)”, “expecting (expecting)”, “considering (considering)” and so on.

[0334] As used in this disclosure, the terms "connected," "coupled," and all variations thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between the two elements being "connected" or "coupled." The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be replaced by "access."

[0335] In the present disclosure, when two elements are connected, it can be considered that they are "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region, etc. as several non-limiting and non-inclusive examples.

[0336] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other." Alternatively, the term may also mean "A and B are each different from C." Terms such as "separate" and "bound" may also be interpreted in the same way as "different."

[0337] In this disclosure, when the terms "include," "including," and variations thereof are used, these terms, like the term "comprising," have an inclusive meaning. Furthermore, the term "or" used in this disclosure does not mean an exclusive OR.

[0338] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure may also include a case where the noun following the article is in a plural form.

[0339] While the inventions disclosed herein have been described in detail above, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The inventions disclosed herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the claims. Therefore, the descriptions in this disclosure are for illustrative purposes only and are not intended to limit the inventions disclosed herein in any way.

Claims

1. A terminal, characterized in that: have: a receiving unit, receiving downlink control information (DCI) and higher layer signaling including a specific field for triggering single-trigger HARQ-ACK feedback including all HARQ-ACK processes in all configured component carriers; as well as A control unit, when performing feedback of the HARQ-ACK based on the DCI, controls feedback using a common codebook for HARQ-ACKs with different priorities, The DCI format of the DCI is a terminal-specific DCI format, The higher layer signaling notifies whether the DCI contains the specific field, HARQ-ACKs with different priorities are triggered simultaneously by the DCI. The HARQ-ACK with a low priority among the HARQ-ACKs with different priorities has its transmission timing delayed. The control unit determines an uplink shared channel to be used for feedback of the HARQ-ACK based on configuration information of an uplink control channel configured for a specific priority level.

2. The terminal according to claim 1, wherein The control unit determines an uplink shared channel to be used in the HARQ-ACK feedback based on the DCI.

3. A wireless communication method, characterized in that: have: receiving downlink control information (DCI) and higher layer signaling including a specific field for triggering single-shot HARQ-ACK feedback for all HARQ-ACK processes in all configured component carriers; In a case where the HARQ-ACK feedback is performed based on the DCI, a step of controlling feedback using a common codebook for HARQ-ACKs with different priorities; as well as The step of determining an uplink shared channel to be used for feedback of the HARQ-ACK based on configuration information of an uplink control channel configured for a specific priority level, The DCI format of the DCI is a terminal-specific DCI format, The higher layer signaling notifies whether the DCI contains the specific field, HARQ-ACKs with different priorities are triggered simultaneously by the DCI. Among the HARQ-ACKs with different priorities, the transmission timing of the HARQ-ACK with a lower priority is delayed.

4. A base station, characterized in that: a transmitting unit, transmitting downlink control information DCI and higher layer signaling including a specific field, wherein the specific field is used to trigger single-trigger HARQ-ACK feedback including all HARQ-ACK processes in all configured component carriers; as well as a control unit that, when feedback of the HARQ-ACK is performed based on the DCI, controls reception of codebooks including HARQ-ACKs having different priorities; The DCI is sent using a terminal-specific DCI format. The higher layer signaling notifies whether the DCI contains the specific field, HARQ-ACKs with different priorities are triggered simultaneously by the DCI. The HARQ-ACK with a low priority among the HARQ-ACKs with different priorities has its transmission timing delayed. The uplink shared channel used in the HARQ-ACK feedback is determined based on the configuration information of the uplink control channel configured for a specific priority.

Images