Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives at least one of a first DCI and a second DCI; and a control unit that controls, at least based on the first DCI, a determination of a channel access type applied to monitoring and transmission of an uplink shared channel (CG-PUSCH) based on a set grant. For the first DCI and the second DCI, at least one of a field commonly or separately set for monitoring and a downlink feedback information (DFI) flag field, or for the second DCI, a field not set for monitoring and a downlink feedback information (DFI) flag field. According to one embodiment of the present disclosure, wireless communication in an NR-U system can be appropriately controlled.

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 a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized for the purpose of further high-speed data rates, low latency, etc. (Non-Patent Document 1). In addition, for the purpose of further large capacity and high performance of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) has been standardized.

[0003] Research is also being conducted on a successor system to LTE (for example, also referred to as the 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 and later, etc.).

[0004] Prior Art Documents

[0005] Non-Patent Documents

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

[0007] Problems to be Solved by the Invention

[0008] In future wireless communication systems (for example, also referred to as 5G, 5G+, New Radio (NR), 3GPP Rel. 16 and later, etc.), the use of an unlicensed band (which may also be referred to as an NR-Unlicensed (U) system) is being studied in the same way as in existing wireless communication systems (for example, before 3GPP Rel. 15).

[0009] In addition, in future wireless communication systems (e.g., also known as 5G, 5G+, New Radio (NR), 3GPP Rel. 16 and later, etc.), research is being conducted on downlink control information (DCI) formats (e.g., DCI format 0_2, 1_2) introduced for service types such as ultra-reliable and low-latency communications (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)).

[0010] However, research on whether to support an indication for the NR-U system through DCI formats for service types such as URLLC is insufficient.

[0011] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station capable of appropriately controlling wireless communication in an NR-U system.

[0012] Means for Solving the Problem

[0013] A terminal according to one aspect of the present disclosure is characterized by having: a receiving unit that receives at least one of a first DCI and a second DCI; and a control unit that controls, at least based on the first DCI, a determination of a channel access type applied to sensing and transmission of a configured grant-based physical uplink shared channel (CG-PUSCH). For the first DCI and the second DCI, at least one of a common or separately configured field for sensing and a downlink feedback information (DFI) flag field, or for the second DCI, a field not configured for sensing and a downlink feedback information (DFI) flag field.

[0014] Effects of the Invention

[0015] According to one aspect of the present disclosure, wireless communication in an NR-U system can be appropriately controlled. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 FIG. is an example showing the association between a channel access type and a CP extension.

[0017] Figure 2 FIG. is an example showing the association between a channel access type, a CP extension, and a CAPC.

[0018] Figure 3 FIG. is an example showing an initial transmission and a retransmission based on CG-DFI.

[0019] Figure 4This is a diagram showing an example of the payload of DCI corresponding to the bit length of the channel access - CP extension field.

[0020] Figure 5 This is a diagram showing an example of the payload of DCI corresponding to the bit length of the channel access - CP extension - APC field.

[0021] Figure 6 This is a diagram showing an example of the payload of DCI corresponding to the bit length of the HARQ - ACK bitmap field.

[0022] Figure 7 This is a diagram showing an example of the schematic structure of a wireless communication system according to an embodiment.

[0023] Figure 8 This is a diagram showing an example of the structure of a base station according to an embodiment.

[0024] Figure 9 This is a diagram showing an example of the structure of a user terminal according to an embodiment.

[0025] Figure 10 This is a diagram showing an example of the hardware structure of a base station and a user terminal according to an embodiment. Detailed Embodiments

[0026] (Service (Service Type))

[0027] In future wireless communication systems (e.g., NR), it is envisioned to further enhance mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), enable massive machine - type communications with a large number of simultaneous connections (e.g., massive Machine Type Communications (mMTC), Internet of Things (IoT)), ultra - reliable and low - latency communications (e.g., Ultra - Reliable and Low - Latency Communications (URLLC)), etc. (also referred to as types, services, service types, communication types, use cases, etc.). For example, in URLLC, lower latency and higher reliability than eMBB are required.

[0028] Service types can also be identified in the physical layer based on at least one of the following.

[0029] · Logical channels with different priorities

[0030] · Modulation and Coding Scheme (MCS) Table (MCS Index Table)

[0031] · Channel Quality Indication (CQI) Table

[0032] · DCI Format

[0033] · Used in the scrambling of the Cyclic Redundancy Check (CRC) bits included (appended) in the DCI (DCI Format) (Radio Network Temporary Identifier (System Information - Radio Network Temporary Identifier (RNTI)))

[0034] · RRC (Radio Resource Control) Parameters

[0035] · Specific RNTIs (e.g., RNTI for URLLC, MCS - C - RNTI, etc.)

[0036] · Search Space

[0037] · Specified Fields in DCI (e.g., newly added fields or reuse of existing fields)

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

[0039] · MCS Index Table used in the determination of 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)

[0040] · RNTI used in the CRC scrambling of the DCI for scheduling the PDSCH (e.g., which one of C - RNTI or MCS - C - RNTI is used for CRC scrambling)

[0041] · Priority set by higher - layer signaling

[0042] In the present disclosure, the high-layer signaling may also be any one of, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0043] For example, the MAC signaling may also use a MAC Control Element (MACCE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0044] The physical layer signaling may also be, for example, Downlink Control Information (DCI).

[0045] The service type may also be associated with communication requirements (requirements such as latency, error rate, request conditions), data categories (voice, data, etc.), and the like.

[0046] The difference between the requirements of URLLC and those of eMBB may also be that the latency of URLLC is less than that of eMBB, or that the requirements of URLLC include the requirement of reliability.

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

[0048] In addition, as enhanced Ultra Reliable and Low Latency Communications (eURLLC), the improvement of the reliability of services for unicast data has been mainly studied. Hereinafter, without distinguishing between URLLC and eURLLC, it is simply referred to as URLLC.

[0049] In NR after Rel.16, the study is underway to set priorities for specific signals or channels at multiple levels (e.g., two levels). For example, it is envisioned that different priorities are set for each of the signals or channels corresponding to different service types (also referred to as services, service types, communication types, use cases, etc.) to perform communication control (e.g., transmission control in case of conflicts, etc.). Thereby, for the same signal or channel, different priorities can be set according to the service type, etc. to control communication.

[0050] Priorities can also be set for signals (e.g., UCI such as HARQ-ACK, reference signals, etc.), channels (PDSCH, PUSCH, etc.), or HARQ-ACK codebooks, etc. Priorities can also be defined by a first priority (e.g., High) and a second priority lower than the first priority (e.g., Low). Alternatively, three or more types of priorities can also be set. Information related to priorities can also be notified from the base station to the UE using at least one of higher layer signaling and DCI.

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

[0052] In the case where different UL signals / UL channels conflict, the UE can also control UL transmission based on priorities. For example, control can also be performed to perform UL transmission with a higher priority without performing (e.g., discarding) UL transmission with a lower priority. Alternatively, the transmission timing of UL transmission with a lower priority can also be changed (e.g., postponed or shifted).

[0053] The conflict 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.

[0054] When the priority is notified by DCI, whether the bit field for notifying the priority (e.g., the priority indicator) is set in the DCI can also be notified or set to the UE by the base station using high-layer signaling. In addition, when the DCI does not include a bit field for notifying the priority, the UE can 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).

[0055] (Priority setting)

[0056] Furthermore, in NRs after Rel.16, it is being studied to set multiple levels (e.g., 2 levels) of priority for specific signals or channels. For example, it is envisioned that different priorities are set for each signal or channel corresponding to different business types (also known as services, service types, communication types, use cases, etc.) to perform communication control (e.g., transmission control in case of conflict, etc.). Thus, for the same signal or channel, different priorities can be set according to service types, etc. to control communication.

[0057] Priority can also be set for signals (e.g., UCI of HARQ-ACK, etc., 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) having a lower priority than the first priority. Alternatively, more than three types of priorities can also be set. Information related to priority can also be notified to the UE from the base station using at least one of high-layer signaling and DCI.

[0058] For example, priority 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, priority may be set for the HARQ-ACK codebook corresponding to these HARQ-ACKs. In addition, when setting priority for PDSCH, the priority of PDSCH may be replaced by the priority of HARQ-ACK for the PDSCH.

[0059] In addition, it can also be prioritized for PUSCH based on dynamic grants, PUSCH based on configured grants, etc.

[0060] In the case where different UL signals / UL channels conflict, the UE can also control UL transmissions based on the priority. For example, control can also be performed to perform UL transmissions with a higher priority without performing (e.g., discarding) UL transmissions with a lower priority. Alternatively, the transmission timing of UL transmissions with a lower priority can also be changed (e.g., postponed or shifted).

[0061] The conflict of different UL signals / UL channels means that the time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or it can also mean that the transmission timings of different UL signals / UL channels overlap.

[0062] In the case of scheduling shared channels with different priorities using DCI, it becomes a problem how to control the multiple DCI formats used in the scheduling of the shared channel and the priorities of the shared channels scheduled by the DCI. The shared channels with different priorities can also be PDSCHs with different HARQ-ACK priorities or PUSCHs with different priorities.

[0063] For example, consider using either an existing DCI format (e.g., DCI format 0_1 / 1_1) or a new DCI format (e.g., DCI format 0_2 / 1_2) supported in Rel.15 to control the scheduling of shared channels with different priorities. In the case where the UE is configured to monitor either the existing DCI format or the new DCI format, the existing DCI format or the new DCI format can also support the scheduling of both the first priority (or URLLC) and the second priority (or eMBB).

[0064] (HARQ process)

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

[0066] In a wireless communication system, data transmission is scheduling-based, and scheduling information for downlink (DL) data transmission is conveyed through downlink control information (DCI). For a HARQ process, a HARQ process number (HPN) is given. 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 numbers range from HPN0 to HPN15. The HARQ process number is also referred to as the HARQ process ID (HARQ process identifier).

[0067] 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) can also be referred to as a transport block (TB). A TB is a unit processed by the media access control (MAC) layer. The control of HARQ (retransmission) can be performed for each TB or for a code block group (CBG) containing one or more code blocks (CBs) within a TB.

[0068] The user terminal uses the PUCCH (physical uplink control channel) or the PUSCH, etc., to send information indicating a positive acknowledgement (ACK) / negative acknowledgement (NACK) of HARQ to the base station, and this ACK / NACK of HARQ indicates whether the decoding of the DL transport block received using the PDSCH is successful.

[0069] 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 can also correspond to one or more transport blocks (TB).

[0070] (Unlicensed band)

[0071] In an unlicensed band (e.g., 2.4 GHz band, 5 GHz band, 6 GHz band, etc.), it is envisaged that multiple systems such as, for example, a Wi-Fi system and a system supporting Licensed-Assisted Access (LAA) (LAA system) coexist. Therefore, it is considered necessary to avoid transmission conflicts and / or control interference between the multiple systems.

[0072] In the LAA of an existing LTE system (e.g., Rel. 13), before data transmission in an unlicensed band, a data transmission device performs listening, which confirms the presence or absence of transmissions from other devices (e.g., base stations, user terminals, Wi-Fi devices, etc.). This listening is also referred to as Listen Before Talk (LBT), Clear Channel Assessment (CCA), carrier sensing, channel sensing, sensing, channel access procedure, shared spectrum channel access procedure, Energy Detection (ED), etc.

[0073] The transmission device can be, for example, a base station (e.g., gNB: gNodeB) in the downlink (DL), and can also be a user terminal (e.g., User Equipment (UE)) in the uplink (UL). In addition, the receiving device that receives data from the transmission device can be, for example, a user terminal in the DL and a base station in the UL.

[0074] In the LAA of an existing LTE system, after it is detected in LBT that there is no transmission from other devices (idle state), the transmission device starts data transmission after a specific period (e.g., an immediate or backoff period).

[0075] 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, etc.). An NR system using an unlicensed band can also be referred to as an NR-Unlicensed (NR-U) system, an NR LAA system, etc.

[0076] Dual Connectivity (DC) between the authorized band and the unauthorized band, Stand-Alone (SA) of the unauthorized band, etc. can also be included in NR-U.

[0077] Nodes in NR-U (e.g., base stations, UEs) coexist with other systems or other operators. Therefore, after confirming that the channel is idle through LBT, transmission starts.

[0078] In NR-U, when the LBT result is idle, the 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 can also be referred to as the Channel Occupancy Time (COT).

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

[0080] (Channel access type)

[0081] In future wireless communication systems (e.g., NR after Rel.16), research is being conducted on UEs performing LBT based on multiple LBT types. The type of this LBT can also be referred to as the channel access type, channel access mode, shared channel access type, etc.

[0082] In NR after Rel.16, the channel access type can also be classified into any one of type 1, type 2A, type 2B, and type 2C. When a specific higher-layer parameter is provided (e.g., ChannelAccessMode-r16) and the specific higher-layer parameter is not set to a specific condition (e.g., ChannelAccessMode-r16 = semistatic), the UE can also perform uplink channel access operations based on any of the above channel access types.

[0083] The name of the channel access type is not limited to these. For example, the name of the channel access type can also be "Channel access type X" where X is represented by any combination of numbers, English letters, or both, or it can be other names.

[0084] Type 1 channel access can also be channel access with a variable transmission waiting time (Contention Window Size (CWS)) accompanied by random back-off. Type 1 channel access can also be a type of channel access used in a coexistence environment with other unlicensed bands (e.g., Wi-Fi).

[0085] In Type 1 channel access, the terminal (including terminals in other wireless communication standards) / gNB can also listen during a specific period before sending a signal. This specific period can also be composed of at least an extended period (which can also be called Defer duration, e.g., 43 μs) and a listening slot (e.g., 9 μs).

[0086] In Type 1 channel access, a specific counter (timer) is set for the terminal / gNB, and when this counter expires (the counter value = 0), the transmission of the signal can also be permitted.

[0087] This counter can also be decremented every time a listening slot (e.g., 9 μs) elapses. This counter set for the terminal / gNB can also stop during a specific period (the period during which the signal is transmitted) when the transmission of a signal by a terminal / gNB other than this terminal / gNB is detected (LBT busy). This counter can also be restarted after a specific period (the period during which the signal is transmitted).

[0088] When the counter values set for multiple terminals / gNBs become 0 at a certain moment and the transmissions of the signals of these multiple terminals / gNBs are repeated, the CWS of this terminal can also be extended.

[0089] Type 2A channel access can also be channel access without random back-off. In Type 2A channel access, the UE can also be set a first period (e.g., a 25 μs period (which can also be called a listening period (interval), gap, etc.)) including a period for listening, and listen during this period. The UE can also transmit a signal immediately after this period when it is LBT idle during this listening.

[0090] Type 2B channel access can also be channel access without random back-off. In Type 2B channel access, the UE can also be set a second period (e.g., a 16 μs period) including a period for listening, and listen during this period. The UE can also transmit a signal immediately after this period when it is LBT idle during this listening.

[0091] Type 2C channel access may also be channel access for which a first period or a second period (e.g., 16 μs) or less is set for the UE, but during which no monitoring is performed. The UE may also transmit a signal during a specific period (e.g., a period of up to 584 μs) immediately after the expiration of this period.

[0092] In order to control the period of monitoring in each type of channel access, a cyclic prefix (CP) extension may also be set. The CP extension may also be represented by a specific time corresponding to a CP extension index. When T TA is the timing advance, this specific time may also be at least one of 25 μs, 16 + T TA μs, 25 + T TA μs.

[0093] The UE may also receive information related to the above-mentioned channel access type and indication of CP extension (CP extension) based on at least one of higher layer signaling and physical layer signaling.

[0094] The UE may also receive information related to the channel access type and indication of CP extension included in a specific DCI format (e.g., DCI format 0_0 / 1_0 / 1_1). The information related to the channel access type and indication of CP extension may also be the ChannelAccess-CPext field included in DCI format 0_0. The ChannelAccess-CPext field included in DCI format 0_0 / 1_0 may also have a bit length of 2 bits. The ChannelAccess-CPext field included in DCI format 1_1 may also have a bit length that can be set from 0 to 4 bits.

[0095] Figure 1 is a diagram showing an example of the association between the channel access type and CP extension. Figure 1 In the example shown, the channel access type and CP extension respectively correspond to indices 0 to 3. The UE is notified of the value of the ChannelAccess-CPext field included in DCI format 0_0 / 1_0. The UE determines the index value corresponding to this field value, and determines the channel access type and CP extension corresponding to this index value based on Figure 1 the association as shown.

[0096] In addition, it may also be Figure 1 that the CP extension shown is represented by an index, and the CP extension value corresponding to this index is set. Furthermore, Figure 1 the association of is merely an example, and the association between the channel access type and CP extension is not limited to this.

[0097] In addition, when a specific high-layer parameter is set (for example, ul-dci-triggered-UL-ChannelAccess-CPext-CAPC-r16), the UE can also receive information related to the channel access type and the indication of CP extension included in DCI format 0_1. The information related to the channel access type and the indication of CP extension can also be the Channel Access Priority Classes (CAPC) (ChannelAccess-CPext-CAPC) field included in DCI format 0_1.

[0098] The ChannelAccess-CPext-CAPC field can also be a field that indicates CAPC for the UE. CAPC can also classify the channel access priority in a certain service type normalized by different 5G Quality of Service (QoS) indicators (5QI) into a specific number (for example, 4) of levels. The specific number can also be any integer other than 4.

[0099] The ChannelAccess-CPext-CAPC field can also have a bit length that can be set from 0 to 6 bits. When the number of entries in a specific high-layer parameter (for example, ULDCI-triggered-UL-ChannelAccess-CPext-CAPC-List-r16) is I, the bit length can also be Ceil(log 2 (I)) bits. In addition, Ceil(X) in the present disclosure can also refer to the ceiling function of X.

[0100] Figure 2 FIG. is an example showing the association of the channel access type, CP extension, and CAPC. Figure 2 In the example of, for each index, the channel access type, CP extension, and CAPC correspond. When a specific high-layer parameter is set (for example, ul-dci-triggered-UL-ChannelAccess-CPext-CAPC-r16), the UE is notified of the value of the ChannelAccess-CPext-CAPC field included in DCI format 0_1. The UE determines the index value corresponding to the field value and based on Figure 2 the association as shown, determines the channel access type, CP extension, and CAPC corresponding to the index value.

[0101] In addition, Figure 2The CP extension and the CAPC shown can also be represented by an index respectively, and a CP extension value and a 5QI number corresponding to the index can be set. In addition, Figure 2 The association of Figure 2 is just an example, and the association of the channel access type, the CP extension, and the CAPC is not limited to this.

[0102] (DFI flag field)

[0103] In a future wireless communication system (e.g., NR after Rel.16), the UE can also receive information related to the retransmission of a signal / channel (e.g., Physical Uplink Shared Channel (PUSCH), Uplink Control Information (UCI)) included in a specific DCI format (e.g., DCI format 0_1). The UE can also control the retransmission of the signal / channel based on the information related to the retransmission.

[0104] The information related to the retransmission of the signal / channel can also be a Downlink Feedback Information (DFI) flag field.

[0105] The DFI flag field can also have a bit length of 0 or 1 bit. The UE can also be set to monitor the DCI format 0_1 scrambled by a Cell-Specific Radio Network Temporary Identifier (CS-RNTI). When accessing a shared spectrum channel in a certain cell, the DFI flag field can also have a bit length of 1 bit. In other cases, the bit length of the DFI flag field can be 0 bit.

[0106] When the DFI flag field has a bit length of 1 bit, when the value of the DFI flag field is 1, activation of the transmission of a Type 2 Configured Grant (CG) can also be indicated for the UE. In addition, when the DFI flag field has a bit length of 1 bit, when the value of the DFI flag field is 0, CG-DFI can also be indicated for the UE.

[0107] It can also be that when CG-DFI is indicated for the UE, the remaining bits constituting the DCI format 0_1 are determined. Specifically, it can be that when CG-DFI is indicated for the UE, the remaining bits constituting the DCI format 0_1 include a HARQ-ACK bitmap field and a Transmission Power Control (TPC) command (TPC command for scheduled PUSCH) field for the scheduled PUSCH. The TPC command field can also have a bit length of 2 bits.

[0108] The HARQ-ACK bitmap field may also have a bit length of 16 bits. It may also correspond to the HARQ process index (HPN) in ascending order from the most significant bit (MSB) to the least significant bit (LSB) of the HARQ-ACK bitmap. Additionally, in the present disclosure, the MSB and LSB may also be interchanged. When the value of the HARQ-ACK bitmap field is 1, ACK may also be indicated for the corresponding PUSCH / UCI of the HPN. When the value of the HARQ-ACK bitmap field is 0, NACK may also be indicated for the corresponding PUSCH / UCI of the HPN.

[0109] The UE may also send UCI in the configured grant-based PUSCH (CG-PUSCH). This UCI may also be referred to as the configured grant-based UCI (CG-UCI). This CG-UCI may also be sent in the NR-U system.

[0110] The CG-UCI may also include specific fields. The specific fields may be at least one of a HARQ process number (HPN) field, a redundancy version (RV) field, a new data indicator (NDI) field, and a channel occupancy time (COT) sharing information field.

[0111] The HPN field may also have a bit length of 4 bits. The RV field may also have a bit length of 2 bits. The NDI field may also have a bit length of 1 bit.

[0112] It may also be that when the COT sharing information field is configured with specific higher layer parameters (e.g., ULtoDL-CO-SharingED-Threshold-r16) and other higher layer parameters (e.g., cg-COT-SharingList-r16), and the number of configured combinations in the other higher layer parameters (e.g., cg-COT-SharingList-r16) is set to C, it has a bit length of Ceil(log 2 (C)) bits.

[0113] Furthermore, the COT sharing information field may have a bit length of 1 bit when it is not configured with specific higher layer parameters (e.g., ULtoDL-CO-SharingED-Threshold-r16) and is configured with other higher layer parameters (e.g., cg-COT-SharingList-r16). In cases other than the above two cases, the COT sharing information field may be 0 bits.

[0114] Figure 3 It is a diagram showing an example of the initial transmission and retransmission based on CG-DFI. Figure 3In the example, the UE transmits CG-UCI#0 via CG-PUSCH#0 and CG-UCI#1 via CG-PUSCH#1 to the gNB, respectively.

[0115] Next, regarding the ACK / NACK indicating the reception processing results for at least CG-UCI#0 and CG-UCI#1, the gNB notifies the UE through the HARQ-ACK bitmap field included in the DCI indicating CG-DFI. At this time, the gNB notifies the UE of the information indicating ACK for CG-UCI#0 and the information indicating NACK for CG-UCI#1, respectively.

[0116] Next, the UE performs retransmission of CG-PUSCH based on the value of the HARQ-ACK bitmap field included in the DCI received from the gNB. Figure 3 In the example, the UE transmits CG-UCI#3 via CG-PUSCH#3 and retransmits CG-UCI#1 via CG-PUSCH#4 to the gNB. At this time, the NDI of CG-UCI#3 is toggled (the value changes to 1), and the NDI of the retransmitted CG-UCI#1 is not toggled (the value remains 0). In addition, Figure 3 In the example, the RV value (2) set for the retransmitted CG-UCI is different from the value (0) of the initial CG-UCI, but the RV values corresponding to the initial CG-UCI and the retransmitted CG-UCI can be either the same value or different values.

[0117] (DCI format for URLLC)

[0118] After Rel.16, DCI formats introduced for service types such as ultra-reliable and low-latency communications (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)) are being studied. This DCI format can also be referred to as DCI format 0_2 or DCI format 1_2. DCI format 0_2 can also be a DCI (UL grant) for scheduling PUSCH. DCI format 1_2 can also be a DCI (DL assignment) for scheduling PDSCH.

[0119] The name of the new DCI format is not limited to this. For example, the name of the new DCI format for scheduling PDSCH and PUSCH can also replace the "2" in the above DCI format 1_2 and DCI format 0_2 with any character string other than "0" and "1", or it can be other names.

[0120] DCI format 0_2 and DCI format 1_2 may also be DCI formats in which a part of the payload is restricted compared to existing DCI formats (e.g., DCI formats 0_1, 1_1).

[0121] Specifically, DCI format 0_2 and DCI format 1_2 may also not allow transmission and reception based on code block groups. In addition, the redundancy version (RV) field included in DCI format 0_2 and DCI format 1_2 may be set to 0 to 2 bits. In addition, the HARQ process number field included in DCI format 0_2 and DCI format 1_2 may be set to 0 to 4 bits. In addition, the sounding reference signal (SRS) request field included in DCI format 0_2 and DCI format 1_2 may be set to 0 to 3 bits.

[0122] In addition, the PUCCH resource indicator field and the transmit configuration indicator (TCI) field included in DCI format 1_2 may be set to 0 to 3 bits. In addition, the carrier indicator field included in DCI format 0_2 and DCI format 1_2 may be set to 0 to 3 bits.

[0123] In this way, by making it possible to set the number of bits of each field included in DCI format 0_2 and DCI format 1_2 to be smaller than that of existing DCI formats (e.g., DCI formats 0_0, 0_1, 1_0, 1_1), the payload (size) of the DCI format can be reduced, and the reliability of communication can be improved.

[0124] However, there has been no sufficient study on whether the DCI formats used in the NR-U system are supported by the DCI formats for URLLC.

[0125] Specifically, in the case of using the DCI format for URLLC for the DCI formats used in the NR-U system, there has been no sufficient study on which field included in the supported DCI or what number of bits to set for a specific field included in the DCI. In addition, in the case of using the DCI format for URLLC for the DCI formats used in the NR-U system, there has been no sufficient study on how to indicate CG-DFI / type 2 CG-PUSCH to the UE when the DFI flag field is not included in the DCI format for URLLC.

[0126] In such a situation where the research is insufficient, there is a concern about a decrease in throughput or a deterioration in communication quality when operating service types such as URLLC in the NR-U system.

[0127] Therefore, the inventors of the present invention have come up with an appropriate method for constructing DCI in the case of applying service types such as URLLC in the NR-U system.

[0128] Hereinafter, embodiments related to the present disclosure will be described in detail with reference to the drawings. The wireless communication methods related to the respective embodiments can be applied separately or in combination.

[0129] In the present disclosure, "A / B" can also be replaced with at least one of A and B, and "A / B / C" can also be replaced with at least one of A, B, and C.

[0130] In the present disclosure, an index, an ID, an indicator, a resource ID, etc. can also be replaced with each other.

[0131] In the present disclosure, the first DCI format, DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, the DCI format for eMBB, the DCI format for scheduling the PDSCH for eMBB, the DCI format not including a priority indicator field, the DCI format not including a priority indicator field for scheduling the PDSCH, the existing DCI format, the DCI format of Rel.15 can also be replaced with each other.

[0132] In the present disclosure, the second DCI format, DCI format 0_2, DCI format 1_2, the DCI format for URLLC, the DCI format for scheduling the PDSCH for URLLC, the DCI format including a priority indicator field, the DCI format including a priority indicator field for scheduling the PDSCH, the new DCI format can also be replaced with each other.

[0133] In the present disclosure, at least one of the NR-U field, the specific field, the channel access - CP extension field, and the channel access - CP extension - CAPC field can also be replaced with a field for listening, a field for channel access type, a field for channel access type and CP extension, a field having a size set depending on a high - layer parameter for listening.

[0134] In addition, in the present disclosure, the NR-U field, the specific field, the downlink feedback information flag field, the field for setting the grant DFI, the field for the PUSCH based on the set grant, the field for setting the grant retransmission, the field having a size set depending on a high - layer parameter for setting the grant DFI can also be replaced with each other.

[0135] (Wireless Communication Method)

[0136] <First Embodiment>

[0137] In the first embodiment, the NR-U specific field included in the second DCI format (e.g., at least one of DCI format 0_2 and DCI format 1_2) will be described.

[0138] [Channel access - CP extension field]

[0139] The second DCI format (e.g., at least one of DCI format 0_2 and DCI format 1_2) may also include a channel access - CP extension field. In other words, the UE may also assume that the channel access - CP extension field is included in the second DCI format and perform PDCCH reception / monitoring.

[0140] In addition, when a specific higher layer parameter (RRC parameter) is set for the UE, the second DCI format may also include a channel access - CP extension field. When a specific higher layer parameter (RRC parameter) is not set for the UE, the second DCI format may not include a channel access - CP extension field. In other words, when a specific higher layer parameter is set for the UE, it may also be set such that the channel access - CP extension field is included in the second DCI format and perform PDCCH reception / monitoring.

[0141] In the present disclosure, the specific higher layer parameter may also be set commonly for the second DCI format (e.g., DCI format 0_2) used in UL transmission scheduling, etc. and the second DCI format (e.g., DCI format 1_2) used in DL transmission scheduling, etc. Thereby, an increase in the overhead of the higher layer parameter can be suppressed. Alternatively, the specific higher layer parameter may be set separately for DCI format 0_2 and DCI format 1_2. Thereby, the number of fields / bits included in the DCI used in UL transmission control and the DCI used in DL transmission control can be flexibly controlled.

[0142] In addition, the second DCI format may not include a channel access - CP extension field. In other words, the UE may also assume that the channel access - CP extension field is not included in the second DCI format and perform PDCCH reception / monitoring.

[0143] [Channel access - CP extension - CAPC field]

[0144] The second DCI format (e.g., DCI format 0_2) may also include a channel access - CP extension - CAPC field. In other words, the UE may also assume that the channel access - CP extension - CAPC field is included in the second DCI format and perform PDCCH reception / monitoring.

[0145] In addition, when specific higher-layer parameters (RRC parameters) are set for the UE, the second DCI format may also include a Channel Access - CP Extension - APC field. When specific higher-layer parameters (RRC parameters) are not set for the UE, the second DCI format may not include the Channel Access - CP Extension - APC field. In other words, when specific higher-layer parameters are set for the UE, it can also be assumed that the second DCI format includes the Channel Access - CP Extension - APC field, and the UE can perform PDCCH reception / monitoring.

[0146] In addition, the second DCI format may not include the Channel Access - CP Extension - APC field. In other words, it can also be assumed that the second DCI format does not include the Channel Access - CP Extension - APC field, and the UE can perform PDCCH reception / monitoring.

[0147] [DFI flag field]

[0148] The second DCI format (e.g., DCI format 0_2) may also include a DFI flag field. In other words, it can also be assumed that the second DCI format includes the DFI flag field, and the UE can perform PDCCH reception / monitoring.

[0149] In addition, when specific higher-layer parameters (RRC parameters) are set for the UE, the second DCI format may also include the DFI flag field. In addition, when specific higher-layer parameters are not set for the UE, the second DCI format may not include the DFI flag field. In other words, when specific higher-layer parameters are set for the UE, it can also be assumed that the second DCI format includes the DFI flag, and the UE can perform PDCCH reception / monitoring.

[0150] In addition, the second DCI format may not include the DFI flag. In other words, it can also be assumed that the second DCI format does not include the DFI flag field, and the UE can perform PDCCH reception / monitoring.

[0151] According to the first embodiment above, the fields included in at least one of DCI format 0_2 and DCI format 1_2 can be appropriately configured, enabling more reliable communication.

[0152] <Second Embodiment>

[0153] In the second embodiment, when the second DCI format is used in the NR-U system and an NR-U field is included in the second DCI format, the number of bits of the field is described. The number of bits of the NR-U field included in the second DCI format may also follow at least one of the following Embodiments 2-1 to 2-4.

[0154] [Embodiment 2-1]

[0155] The bit length of the channel access - CP extension field included in the second DCI format (e.g., at least one of DCI format 0_2 and DCI format 1_2) can also be a bit length that can be set to a specific length (e.g., 0 to 4 bits) through a specific higher layer parameter. The bit length of this specific length can also be supported to be the same as the bit length that can be set for the channel access - CP extension field included in the first DCI format (DCI format 0_0 / 0_1 / 1_1).

[0156] In addition, the bit length of the channel access - CP extension field included in the second DCI format can also be a single fixed value (e.g., 1 or 2). Accordingly, the overhead of RRC signaling for the UE can be reduced.

[0157] When the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value (e.g., 1), the channel access type indicated for the UE can also be limited. In other words, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the UE can also determine the channel access type according to the association (table) indicated by only one or more specific channel access types.

[0158] For example, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the channel access type indicated for the UE can also be limited to a specific type combination (e.g., type 1 channel access and type 2C channel access). In other words, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the UE can also determine the channel access type according to the association indicated by only type 1 channel access and type 2C channel access. Accordingly, the UE can communicate appropriately even in a coexistence environment with other wireless communication standards (e.g., Wi-Fi).

[0159] In addition, for example, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the channel access type indicated for the UE can also be limited to another specific type combination (e.g., type 2A channel access and type 2C channel access). In other words, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the UE can also determine the channel access type according to the association indicated by only type 2A channel access and type 2C channel access. Accordingly, the UE can determine the channel access type suitable for low - latency communication and can perform highly reliable communication.

[0160] In addition, for example, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the channel access type indicated for the UE can also be limited to a specific type (e.g., type 2C channel access). In other words, when the bit length of the channel access - CP extension field included in the second DCI format is a first fixed value, the UE can also determine the channel access type based on the association indicated by the type 2C channel access corresponding only to different CP extension indices. Accordingly, the UE can determine the channel access type suitable for low - latency communication and can perform highly reliable communication.

[0161] In addition, when the bit length of the channel access - CP extension field included in the second DCI format is a second fixed value (e.g., 2), the UE can also determine the channel access type based on the association (table) used for the first DCI format.

[0162] In addition, when the bit length of the channel access - CP extension field included in the second DCI format is a second fixed value, the UE can also determine the channel access type based on the association including the combination of the channel access type and the CP extension index that is not included in the first DCI format. Accordingly, the UE communication in NR - U can be controlled more flexibly.

[0163] Figure 4 It is a diagram showing an example of the DCI payload corresponding to the bit length of the channel access - CP extension field. Figure 4 Above shows the DCI payload when the channel access - CP extension field included in the first DCI format (e.g., DCI format 0_0 / 0_1 / 1_1) has a bit length of 4 bits. Figure 4 Below shows the DCI payload when the channel access - CP extension field included in the second DCI format (e.g., DCI format 0_2 / 1_2) has a bit length of 2 bits.

[0164] As Figure 4 shown in the example, by making the bit length of the channel access - CP extension field included in the second DCI format (e.g., DCI format 0_2 / 1_2) a fixed value (here, 2 bits), the DCI payload can be made smaller than that of the first DCI format (e.g., DCI format 0_0 / 0_1 / 1_1).

[0165] [Embodiment 2 - 2]

[0166] The bit length of the channel access - CP extension - CAPC field included in the second DCI format (e.g., DCI format 0_2) can also be set to a specific length (e.g., 0 to 6 bits) of bits through a specific high - layer parameter. The bit length of this specific length can also be supported to be the same as the bit length that can be set for the channel access - CP extension field included in the first DCI format.

[0167] In addition, the bit length of the channel access - CP extension - CAPC field included in the second DCI format can also be set, through a specific high - layer parameter, to be less than the bit length of the channel access - CP extension - CAPC field included in the first DCI format. The bit length that can be set can also be a specific length (e.g., 0 to 4 bits) of bits.

[0168] In this way, by setting the bit length of this field to be less than the bit length of the channel access - CP extension - CAPC field included in the first DCI format, the payload size of the DCI format can be made smaller.

[0169] In addition, the bit length of the channel access - CP extension - CAPC field included in the second DCI format can also be a single fixed value (e.g., 1 or 2). Accordingly, the overhead of the RRC signaling for the UE can be reduced.

[0170] Figure 5 is a diagram showing an example of the DCI payload corresponding to the bit length of the channel access - CP extension - CAPC field. Figure 5 Above shows the DCI payload when the channel access - CP extension - CAPC field included in the first DCI format (e.g., DCI format 0_0 / 0_1 / 1_1) has a bit length of 6 bits. Figure 5 Below shows the DCI payload when the channel access - CP extension field included in the second DCI format (e.g., DCI format 0_2 / 1_2) has a bit length of 2 bits.

[0171] As Figure 5 shown in the example, by making the bit length of the channel access - CP extension - CAPC field included in the second DCI format (e.g., DCI format 0_2 / 1_2) a fixed value (here 2 bits), the DCI payload can be made smaller compared to the first DCI format (e.g., DCI format 0_0 / 0_1 / 1_1).

[0172] [Embodiment 2 - 3]

[0173] For the second DCI format (e.g., DCI format 0_2), whether to include the channel access - CP extension field or the channel access - CP extension - CAPC field included in the first DCI format (DCI format 0_1) can also be determined based on the setting of specific higher - layer parameters.

[0174] For example, when specific higher - layer parameters (RRC parameters) are set, the channel access - CP extension - CAPC field can also be included in the second DCI format. In other words, when specific higher - layer parameters are set, the UE can also assume that the channel access - CP extension - CAPC field is included in the second DCI format and perform PDCCH reception / monitoring. In this case, the channel access - CP extension field may not be included in the second DCI format. Or, in this case, the channel access - CP extension field may also be included in the second DCI format.

[0175] On the other hand, when no specific higher - layer parameters are set, the channel access - CP extension field can also be included in the second DCI format. In other words, when no specific higher - layer parameters are set, the UE can also assume that the channel access - CP extension field is included in the second DCI format and perform PDCCH reception / monitoring. In this case, the channel access - CP extension - CAPC field may not be included in the second DCI format. Or, in this case, the channel access - CP extension - CAPC field may also be included in the second DCI format.

[0176] In addition, for example, when specific higher - layer parameters (RRC parameters) are set, the channel access - CP extension field can also be included in the second DCI format. In other words, when specific higher - layer parameters are set, the UE can also assume that the channel access - CP extension field is included in the second DCI format and perform PDCCH reception / monitoring. In this case, the channel access - CP extension - CAPC field may not be included in the second DCI format. Or, in this case, the channel access - CP extension - CAPC field may also be included in the second DCI format.

[0177] On the other hand, when no specific higher - layer parameters (RRC parameters) are set, the channel access - CP extension - CAPC field can also be included in the second DCI format. In other words, when no specific higher - layer parameters are set, the UE can also assume that the channel access - CP extension - CAPC field is included in the second DCI format and perform PDCCH reception / monitoring. In this case, the channel access - CP extension field may not be included in the second DCI format. Or, in this case, the channel access - CP extension field may also be included in the second DCI format.

[0178] In addition, the bit length of the channel access - CP extension field or the bit length of the channel access - CP extension - CAPC field included in the second DCI format may also be applied to the number of bits described in the above - mentioned Embodiments 2 - 1 and 2 - 2.

[0179] [Embodiment 2 - 4]

[0180] The bit length of the DFI flag field included in the second DCI format (e.g., DCI format 0_2) may also be a bit length that can be set to a specific length (e.g., 0 or 1 bit) through a specific higher - layer parameter. The bit length of this specific length may also be supported to be the same as the bit length that can be set for the DFI flag field included in the first DCI format (DCI format 0_1).

[0181] The bit length of the HARQ - ACK bitmap field included in the second DCI format may also be a bit length that can be set to a specific length (e.g., 0 to 16 bits) through a specific higher - layer parameter. The bit length of this specific length may also be supported to be the same as the bit length that can be set for the HARQ - ACK bitmap field included in the first DCI format.

[0182] The bit length of the HARQ - ACK bitmap field included in the second DCI format may also be set to be less than the bit length of the HARQ - ACK bitmap field included in the first DCI format through a specific higher - layer parameter. The settable bit length may also be a bit length of a specific length (e.g., 0 to 4 bits).

[0183] In this case, the payload of the second DCI format can be set to be less than the payload of the first DCI format. Specifically, when the CG - DFI is indicated to the UE through the second DCI format, the payload of this second DCI format can be set to be less than the payload of the first DCI format. In addition, when the CG - DFI is not indicated to the UE through the second DCI format, it can be made at least 1 bit smaller than when the bit length of the HARQ - ACK bitmap field is a fixed value.

[0184] In addition, the case where the bit length of the HARQ - ACK bitmap field is 0 bit may also refer to the case where the CG - DFI is not indicated to the UE. Specifically, the case where the CG - DFI is not indicated may also refer to at least one of the cases where the CG - PUSCH in Rel.15 is transmitted or the PUSCH is transmitted dynamically.

[0185] In addition, the bit length of the HARQ-ACK bitmap field included in the second DCI format may also be a single fixed value (e.g., 1 or 2). Accordingly, the overhead of RRC signaling for the UE can be reduced.

[0186] Figure 6 It is a diagram showing an example of the DCI payload corresponding to the bit length of the HARQ-ACK bitmap field. Figure 6 Above shows the DCI payload when the HARQ-ACK bitmap field included in the first DCI format (e.g., DCI format 0_0 / 0_1 / 1_1) has a bit length of 16 bits. Figure 6 Below shows the DCI payload when the HARQ-ACK bitmap field included in the second DCI format (e.g., DCI format 0_2 / 1_2) has a bit length of 4 bits.

[0187] As Figure 6 As shown in the example of, by setting the bit length of the channel access - CP extension - CAPC field included in the second DCI format (e.g., DCI format 0_2 / 1_2) to be less than that of the first DCI format, the DCI payload can be made smaller than that of the first DCI format.

[0188] As described above, according to the second embodiment, when the DCI format for URLLC is used in the NR-U system, the bit numbers of the fields for the NR-U system can be appropriately set, and reliable communication can be performed preferably.

[0189] <Third Embodiment>

[0190] In the third embodiment, a method for indicating the CG-DFI to the UE when the second DCI format is used in the NR-U system and the field for CG-DFI is not included in the second DCI format (e.g., DCI format 0_2) will be described.

[0191] When the DFI flag field is not included in the second DCI format, the UE can also receive the indication of the CG-DFI based on the combination of multiple fields included in the first DCI, and control the transmission of the CG-PUSCH / CG-UCI.

[0192] When the DFI flag field is not included in the second DCI format, the UE can also use the DCI used in the activation / deactivation PDCCH validation of the type 2 CG-PUSCH to receive the indication of the CG-DFI.

[0193] In the case of receiving an indication of CG-DFI by using the DCI used in the active PDCCH verification of type 2 CG-PUSCH in the UE, the HARQ-ACK bitmap field included in the DCI may also have a bit length of 16 bits. In addition, the TPC command field included in the DCI may also have a bit length of 2 bits. In addition, the values of the HPN field and the RV field included in the DCI may also be 0. The values of the fields other than the fields included in the above DCI may also be 0.

[0194] In addition, in the case of receiving an indication of CG-DFI by using the DCI used in the deactive PDCCH verification of type 2 CG-PUSCH in the UE, the HARQ-ACK bitmap field included in the DCI may also have a bit length of 16 bits. In addition, the TPC command field included in the DCI may also have a bit length of 2 bits. In addition, the values of the HPN field and the RV field included in the DCI may also be 0.

[0195] In the case of receiving an indication of CG-DFI by using the DCI used in the active / deactive PDCCH verification in the UE for type 2 CG-PUSCH, the UE may also use the same DCI to receive an indication of the activation / deactivation of type 2 CG-PUSCH and CG-DFI.

[0196] In addition, in the case of receiving an indication of CG-DFI by using the DCI used in the active / deactive PDCCH verification in the UE for type 2 CG-PUSCH, the UE may also be assumed to receive the DCI only for the indication of CG-DFI.

[0197] As described above, according to the third embodiment, even when the field for CG-DFI is not included in the second DCI format (for example, DCI format 0_2), CG-DFI can be appropriately indicated to the UE.

[0198] (Wireless communication system)

[0199] Hereinafter, the structure of a wireless communication system according to an embodiment of the present disclosure will be described. In this wireless communication system, any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof is used for communication.

[0200] Figure 7It is a diagram showing an example of the schematic structure of a wireless communication system according to an 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), the 5th generation mobile communication system New Radio (5G NR), and the like.

[0201] In addition, the wireless communication system 1 may also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (RATs). MR-DC may 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 (NE-DC)), and the like.

[0202] In EN-DC, the base station (eNB) of LTE (E-UTRA) is the Master Node (MN), and the base station (gNB) of NR is the Secondary Node (SN). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

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

[0204] The wireless communication system 1 may also include: a base station 11 that forms a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a - 12c) that is disposed within the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration, quantity, etc. of each cell and the user terminal 20 are not limited to the manner shown in the figure. Hereinafter, without distinguishing between the base stations 11 and 12, they are collectively referred to as the base station 10.

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

[0206] Each CC may also be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a 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 of 6 GHz or less (sub - 6 GHz), and FR2 may be a frequency band higher than 24 GHz (above - 24 GHz). Additionally, the frequency bands, definitions, etc. of FR1 and FR2 are not limited thereto. For example, FR1 may correspond to a frequency band higher than FR2.

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

[0208] The multiple base stations (e.g., RRH) 10 may also be connected by wire (e.g., an optical fiber based on the Common Public Radio Interface (CPRI), the X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 that is equivalent to the upper - level station may also be referred to as an Integrated Access Backhaul (IAB) donor, and the base station 12 that is equivalent to a relay station may also be referred to as an IAB node.

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

[0210] User terminal 20 can also be a terminal that supports at least one of communication methods such as LTE, LTE-A, 5G, etc.

[0211] In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the Downlink (DL) and the Uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. can also be used.

[0212] The wireless access method can also be referred to as a waveform. Additionally, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of the UL and DL.

[0213] In the wireless communication system 1, as a downlink channel, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. that are shared among the respective user terminals 20 can also be used.

[0214] In addition, in the wireless communication system 1, as the uplink channel, the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), uplink control channel (Physical Uplink Control Channel (PUCCH)), random access channel (Physical Random Access Channel (PRACH)), etc., which are shared by each user terminal 20, can also be used.

[0215] User data, high-layer control information, System Information Block (SIB), etc. are transmitted through the PDSCH. User data, high-layer control information, etc. can also be transmitted through the PUSCH. In addition, the Master Information Block (MIB) can be transmitted through the PBCH.

[0216] Low-layer control information can also be transmitted through the PDCCH. The low-layer control information can also include, for example, downlink control information (Downlink Control Information (DCI)), and the downlink control information includes scheduling information of at least one of the PDSCH and the PUSCH.

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

[0218] In the detection of the PDCCH, the Control Resource Set (CORESET) and the search space can also be utilized. The CORESET corresponds to the resource for searching for the DCI. The search space corresponds to the search area and search method of the PDCCH candidates. One CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a certain search space based on the search space setting.

[0219] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. Additionally, in the present disclosure, "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. may also be used interchangeably.

[0220] Uplink control information (Uplink Control Information (UCI)) including at least one of channel state information (Channel State Information (CSI)), delivery confirmation information (e.g., which may also be referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (Scheduling Request (SR)) may also be transmitted via PUCCH. A random access preamble for establishing a connection with a cell may also be transmitted via PRACH.

[0221] Additionally, in the present disclosure, the downlink, uplink, etc. may also be expressed without "link". Further, it may also be expressed as not having "Physical" at the beginning of various channels.

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

[0223] The synchronization signal may also be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may also be referred to as an SS / PBCH block, an SS block (SS Block (SSB)), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

[0224] In addition, in the wireless communication system 1, as an Uplink Reference Signal (UL-RS), a reference signal for measurement (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may also be transmitted. In addition, DMRS may also be referred to as a UE-specific Reference Signal.

[0225] (Base station)

[0226] Figure 8 FIG. is an example showing the structure of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission path interface (transmission line interface) 140. In addition, one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140 may be provided respectively.

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

[0228] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc. that can be explained based on the common knowledge in the technical field related to the present disclosure.

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

[0230] The transmission and reception 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 transmission and reception unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission and reception circuit, etc. described based on common knowledge in the technical field related to the present disclosure.

[0231] The transmission and reception unit 120 can be configured as an integrated transmission and reception unit, or can be composed of a transmission unit and a reception unit. The transmission unit can also be composed of the transmission processing unit 1211 and the RF unit 122. The reception unit can also be composed of the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

[0232] The transmission and reception antenna 130 can be composed of an antenna described based on common knowledge in the technical field related to the present disclosure, such as an array antenna, etc.

[0233] The transmission and reception unit 120 can also transmit the above-mentioned downlink channels, synchronization signals, downlink reference signals, etc. The transmission and reception unit 120 can also receive the above-mentioned uplink channels, uplink reference signals, etc.

[0234] The transmission and reception unit 120 can also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of a transmission beam and a reception beam.

[0235] The transmission / reception unit 120 (transmission processing unit 1211) can also perform processing at the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0236] The transmission / reception unit 120 (transmission processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal.

[0237] The transmission / reception unit 120 (RF unit 122) can also perform modulation to the radio frequency band, filter processing, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmission / reception antenna 130.

[0238] On the other hand, the transmission / reception unit 120 (RF unit 122) can also perform amplification, filter processing, demodulation to the baseband signal, etc. on the radio frequency band signal received through the transmission / reception antenna 130.

[0239] The transmission / reception unit 120 (reception processing unit 1212) can also perform reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc. on the obtained baseband signal, and obtain user data, etc.

[0240] The transmitting and receiving unit 120 (measurement unit 123) may also perform measurements related to the received signal. For example, the measurement unit 123 may also perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may also perform measurements on 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.

[0241] The transmission path interface 140 may also transmit and receive signals (backhaul signaling) between the device included in the core network 30, other base stations 10, etc., and may also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0243] It may also be that the transmitting and receiving unit 120 transmits at least one of the first DCI and the second DCI. It may also be that the control unit 110 controls the reception of the uplink signal to which the channel access type determined based on the above first DCI is applied and the reception of the configured grant-based physical uplink shared channel (CG-PUSCH) transmitted based on the above first DCI. For the above first DCI and the above second DCI, at least one of the fields set for monitoring publicly or separately and the downlink feedback information (DFI) flag field may be set, or for the above second DCI, the fields not set for monitoring and the downlink feedback information (DFI) flag field may not be set (the first embodiment).

[0244] (User Terminal)

[0245] Figure 9 This is a diagram showing an example of the structure of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. Additionally, one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may be provided respectively.

[0246] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it can also be assumed that the user terminal 20 also has other functional blocks required for wireless communication. A part of the processing of each unit described below may also be omitted.

[0247] The control unit 210 implements overall control of the user terminal 20. The control unit 210 can be composed of a controller, a control circuit, etc. that can be explained based on common knowledge in the technical field related to this disclosure.

[0248] 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 / reception unit 220 and the transmission / 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 / reception unit 220.

[0249] The transmission / reception unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmission / reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc. that can be explained based on common knowledge in the technical field related to this disclosure.

[0250] The transmission / reception unit 220 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of the transmission processing unit 2211 and the RF unit 222. The reception unit may be composed of the reception processing unit 2212, the RF unit 222, and the measurement unit 223.

[0251] The transmission / reception antenna 230 can be composed of an antenna that can be explained based on common knowledge in the technical field related to this disclosure, such as an array antenna.

[0252] The transmission / reception unit 220 may also receive the above-mentioned downlink channels, synchronization signals, downlink reference signals, etc. The transmission / reception unit 220 may also transmit the above-mentioned uplink channels, uplink reference signals, etc.

[0253] The transmission / reception unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of a transmission beam and a reception beam.

[0254] The transmission / reception unit 220 (transmission processing unit 2211) may also perform, for example, PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210 to generate a bit string to be transmitted.

[0255] The transmission / reception unit 220 (transmission processing unit 2211) may also perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (if necessary), IFFT processing, precoding, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal.

[0256] In addition, regarding whether to apply DFT processing, it may also be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when the transform precoding is active (enabled), the transmission / reception unit 220 (transmission processing unit 2211) may also perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using the DFT-s-OFDM waveform. In other cases, the transmission / reception unit 220 (transmission processing unit 2211) may not perform DFT processing as the above-mentioned transmission processing.

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

[0258] On the other hand, the transmission / reception unit 220 (RF unit 222) may also perform amplification, filter processing, demodulation to a baseband signal, etc. on the radio frequency band signal received through the transmission / reception antenna 230.

[0259] The transmission / reception unit 220 (reception processing unit 2212) may also perform reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc. on the obtained baseband signal to obtain user data, etc.

[0260] The transmitting and receiving unit 220 (measurement unit 223) may also perform measurements related to the received signal. For example, the measurement unit 223 may also perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may also perform measurements on 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.

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

[0262] The transmitting and receiving unit 220 may also receive at least one of the first DCI and the second DCI. The control unit 210 may also control the determination of the channel access type applied to the monitoring and the transmission of the uplink shared channel (CG-PUSCH) based on the set grant, at least based on the first DCI. For the first DCI and the second DCI, at least one of the fields set publicly or separately for monitoring and the downlink feedback information (DFI) flag field may be used, or for the second DCI, the fields not set for monitoring and the downlink feedback information (DFI) flag field (first embodiment).

[0263] It may also be that, when a specific high-layer parameter is set, the bit length of the field for monitoring included in the second DCI is set to be less than the bit length of the field for monitoring included in the first DCI (second embodiment).

[0264] It may also be that the field for monitoring includes a field indicating the channel access type and the cyclic prefix extension and a field indicating the channel access type, the cyclic prefix extension, and the channel access priority level (first and second embodiments).

[0265] It may also be that, when the DFI flag field is not set in the second DCI, the control unit 210 controls the transmission of the CG-PUSCH based on the combination of multiple fields included in the first DCI (third embodiment).

[0266] (Hardware Structure)

[0267] In addition, the block diagrams used in the description of the above embodiments illustrate blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. Furthermore, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented by a single device physically or logically combined, or can be implemented by two or more physically or logically separated devices directly or indirectly (e.g., by wire, wireless, etc.) connected with these multiple devices. The functional block can also be implemented by combining the above single device or the above multiple devices with software.

[0268] Here, in terms of functions, there are judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, broadcasting, notification, communication, forwarding, configuration (setting), reconfiguration (resetting), allocation (mapping), assignment, etc., but are not limited to these. For example, a functional block (structural unit) that implements the transmission function may also be referred to as a transmitting unit, a transmitter, etc. Any one of them is as described above, and the implementation method is not particularly limited.

[0269] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure can also function as a computer that performs the processing of the wireless communication method of the present disclosure. Figure 10 It is a diagram showing an example of the hardware structure of a base station and a user terminal according to an embodiment. The above base station 10 and user terminal 20 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, etc.

[0270] In addition, in the present disclosure, terms such as device, circuit, equipment, section, unit, etc. can be replaced with each other. The hardware structure of the base station 10 and the user terminal 20 can be configured to include one or more of each device shown in the figure, or can be configured not to include some devices.

[0271] For example, only one processor 1001 is illustrated, but there may be multiple processors. In addition, the processing may be performed by one processor, or may be performed by two or more processors simultaneously, sequentially, or by other means. Further, the processor 1001 may also be implemented by one or more chips.

[0272] Regarding each function in the base station 10 and the user terminal 20, for example, by reading a specific software (program) into hardware such as the processor 1001 and the memory 1002, the processor 1001 performs arithmetic operations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage device 1003, thereby implementing the function.

[0273] The processor 1001 operates the operating system, for example, to control the entire computer. The processor 1001 may also be constituted by a central processing unit (Central Processing Unit (CPU)) including an interface with peripheral devices, a control device, an arithmetic device, registers, etc. For example, at least a part of the above control unit 110 (210), transmission / reception unit 120 (220), etc. may also be implemented by the processor 1001.

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

[0275] The memory 1002 may also be a computer-readable recording medium, for example, constituted by at least one of a read-only memory (Read Only Memory (ROM)), an erasable programmable read-only memory (Erasable Programmable ROM (EPROM)), an electrically erasable programmable read-only memory (Electrically EPROM (EEPROM)), a random access memory (Random Access Memory (RAM)), and other appropriate storage media. 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 a program (program code), software module, etc. executable for implementing the wireless communication method according to an embodiment of the present disclosure.

[0276] The storage device 1003 may also be a computer-readable recording medium, which is constituted by at least one of, for example, a flexible disc, a floppy (registered trademark) disk, an optical disk (such as a compact disc (Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray (registered trademark) disc), a removable disc, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. The storage device 1003 may also be referred to as an auxiliary storage device.

[0277] The communication device 1004 is hardware (a transmitting and receiving device) for performing inter-computer communication via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. In order to implement at least one of, for example, 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, etc. For example, the above-mentioned transmitting and receiving unit 120 (220), transmitting and receiving antenna 130 (230), etc. may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated and implemented by a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0278] The input device 1005 is an input device (such as a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside. The output device 1006 is an output device (such as a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. In addition, the input device 1005 and the output device 1006 may also be of an integrated structure (such as a touch panel).

[0279] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be constituted by a single bus or by different buses between each device.

[0280] In addition, the base station 10 and the 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), and a field programmable gate array (FPGA). The hardware may also be used to implement part or all of each functional block. For example, the processor 1001 may also be implemented by at least one of these hardware components.

[0281] (Variant example)

[0282] Furthermore, 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, a channel, a symbol, and a signal (signal or signaling) may also be replaced with each other. In addition, a signal may also be a message. A reference signal can also be abbreviated as RS and may also be referred to as a pilot, a pilot signal, etc. according to the applied standard. In addition, a component carrier (CC) may also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

[0283] A radio frame may also be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the radio frame may also be referred to as a subframe. Further, a subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) independent of the numerology.

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

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

[0286] A time slot can also contain multiple mini-slots. Each mini-slot can also be composed of one or more symbols in the time domain. In addition, a mini-slot can also be referred to as a sub-slot. A mini-slot can also be composed of a smaller number of symbols than a time slot. A Physical Downlink Shared Channel (PDSCH) (or Physical Uplink Shared Channel (PUSCH)) transmitted in a time unit larger than a mini-slot can also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot can also be referred to as PDSCH (PUSCH) mapping type B.

[0287] A radio frame, a sub-frame, a time slot, a mini-slot, and a symbol all represent time units when transmitting signals. A radio frame, a sub-frame, a time slot, a mini-slot, and a symbol can also use their respective other names. In addition, time units such as frames, sub-frames, time slots, mini-slots, and symbols in this disclosure can also be replaced with each other.

[0288] For example, a sub-frame can also be referred to as a Transmission Time Interval (TTI), multiple consecutive sub-frames can also be referred to as a TTI, and a time slot or a mini-slot can also be referred to as a TTI. That is, at least one of a sub-frame and a TTI can be a sub-frame (1 ms) in the existing Long Term Evolution (LTE), can also be a period shorter than 1 ms (for example, 1 - 13 symbols), and can also be a period longer than 1 ms. In addition, the unit representing a TTI can also not be referred to as a sub-frame, but can be referred to as a time slot, a mini-slot, etc.

[0289] Here, a TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as the frequency bandwidth and transmission power that can be used in each user terminal) to each user terminal in units of TTI. In addition, the definition of a TTI is not limited to this.

[0290] A TTI can also be the transmission time unit of a data packet (transmission block), a code block, a codeword, etc. that has undergone channel coding, and can also become a processing unit for scheduling, link adaptation, etc. In addition, when a TTI is given, the actual time interval (such as the number of symbols) for mapping a transmission block, a code block, a codeword, etc. can also be shorter than the TTI.

[0291] In addition, when a time slot or a mini-slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-slot) can also be the minimum time unit for scheduling. In addition, the number of time slots (mini-slots) that constitute the minimum time unit for this scheduling can also be controlled.

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

[0293] In addition, a long TTI (e.g., normal TTI, subframe, etc.) can also be replaced with a TTI having a time length exceeding 1 ms, and a short TTI (e.g., shortened TTI, etc.) can also be replaced with a TTI having a TTI length less than that of the long TTI and 1 ms or more.

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

[0295] In addition, the RB can also include one or more symbols in the time domain, and can also be the length of one time slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. can also be composed of one or more resource blocks respectively.

[0296] In addition, one or more RBs can also be referred to as physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc.

[0297] In addition, a resource block can also be composed of one or more resource elements (REs). For example, one RE can also be a radio resource area of one subcarrier and one symbol.

[0298] A Bandwidth Part (BWP) (which may also be referred to as partial bandwidth, etc.) may also represent a subset of consecutive common RBs (common resource blocks) used by a certain parameter set in a certain carrier. Here, the common RBs may also be determined by the indexes of the RBs based on the common reference point of the carrier. The PRBs may also be defined in a certain BWP and be numbered additionally within that BWP.

[0299] A BWP may also include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may also be set within one carrier.

[0300] At least one of the set BWPs may also be active, and the UE may not assume to transmit and receive specific signals / channels outside the active BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be replaced with "BWP".

[0301] In addition, the structures such as the above-mentioned radio frames, subframes, time slots, mini-slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-slots included in a time slot, the symbols and the number of RBs included in a time slot or mini-slot, the number of subcarriers included in an RB, and the number of symbols, symbol length, Cyclic Prefix (CP) length, etc. within a TTI can be changed in various ways.

[0302] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, may also be represented by relative values with respect to a specific value, and may also be represented by corresponding other information. For example, radio resources may also be indicated by specific indexes.

[0303] In the present disclosure, the names used for parameters, etc. are not restrictive names in all aspects. Furthermore, the mathematical formulas, etc. using these parameters may also be different from those clearly disclosed in the present disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names. Therefore, the various names assigned to these various channels and information elements are not restrictive names in all aspects.

[0304] The information, signals, etc. described in the present disclosure may also be represented by any one of various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0305] In addition, 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.

[0306] The information, signals, etc. that are input and output can be stored in a specific location (e.g., a memory), or can be managed using a management table. The information, signals, etc. that are input and output can be overwritten, updated, or appended. The information, signals, etc. that are output can also be deleted. The information, signals, etc. that are input can also be sent to other devices.

[0307] The notification of information is not limited to the methods / embodiments described in this disclosure, and other methods can also be used. For example, the notification of information in this disclosure can also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), higher 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.

[0308] In addition, physical layer signaling can 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 can also be referred to as an RRC message, and can also be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration (RRC Connection Re - setup) message, etc. In addition, MAC signaling can, for example, also be notified using a MAC Control Element (MAC CE).

[0309] In addition, the notification of specific information (e.g., the notification of "is X") is not limited to explicit notification, and can also be performed implicitly (e.g., by not performing the notification of the specific information, or by the notification of other information).

[0310] The determination can be made by a value represented by one bit (0 or 1), by a true / false value (Boolean value) represented by true or false, or by a comparison of numerical values (e.g., comparison with a specific value).

[0311] Software, whether referred to as software, firmware, middleware, micro-code, hardware description language, or by any other name, should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, processes, functions, etc.

[0312] In addition, software, instructions, information, etc. can also be transmitted and received via a transmission medium. For example, in the case of transmitting software from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included in the definition of the transmission medium.

[0313] Terms such as "system" and "network" used in the present disclosure can be used interchangeably. "Network" can also represent a device (e.g., a base station) included in the network.

[0314] In the present disclosure, terms such as "precoding", "precoder", "weights (precoding weights)", "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", "panel", etc. can be used interchangeably.

[0315] In the present disclosure, terms such as "Base Station (BS)", "radio 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", "component carrier", etc. can be used interchangeably. There are also cases where terms such as macro cell, small cell, femto cell, pico cell, etc. are used to refer to the base station.

[0316] A base station can accommodate one or more (e.g., three) cells. When the base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services within the coverage range.

[0317] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "user device (User Equipment (UE))", "terminal", etc. can be used interchangeably.

[0318] There are also cases where the mobile station is referred to by 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.

[0319] At least one of the base station and the mobile station may also be referred to as a transmitting device, receiving device, wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), may also be a moving body that moves in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), and may also be a robot (humanoid or non-humanoid). In addition, at least one of the base station and the mobile station 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.

[0320] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, for a structure in which communication between a base station and a user terminal is replaced by communication between multiple user terminals (e.g., may also be referred to as Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), the various methods / embodiments of the present disclosure may also be applied. In this case, it may also be a structure in which 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 (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may also be replaced by a side channel.

[0321] Similarly, the user terminal in the present disclosure may also be replaced by a base station. In this case, it may also be a structure in which the base station 10 has the functions of the above-mentioned user terminal 20.

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

[0323] Each mode / embodiment described in the present disclosure can be used alone, in combination, or switched during execution. In addition, the processing procedures, sequences, flowcharts, etc. of each mode / embodiment described in the present disclosure can be rearranged as long as there is no contradiction. For example, for the methods described in the present disclosure, elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0324] Each mode / embodiment described in the present disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the fourth generation mobile communication system (4G), the fifth 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.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems using other appropriate wireless communication methods, next-generation systems extended based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G, etc.) for application.

[0325] The description "based on" used in the present disclosure does not mean "only based on" unless otherwise specified. In other words, the description "based on" means both "only based on" and "at least based on".

[0326] Any reference to elements using designations such as "first", "second", etc. used in the present disclosure does not comprehensively limit the quantity or order of these elements. These designations can be used in the present disclosure as a convenient method for distinguishing between two or more elements. Therefore, the reference to the first and second elements does not mean that only two elements can be adopted, or that the first element must take precedence over the second element in a certain form.

[0327] The term "determining" as used in this disclosure encompasses diverse operations. For example, "determining" can also include cases where judging, calculating, computing, processing, deriving, investigating, looking up (searching, inquiring) (such as searching in a table, database, or other data structure), ascertaining, etc. are considered as performing "determining".

[0328] In addition, "determining" can also include cases where receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, accessing (e.g., accessing data in a memory), etc. are considered as performing "determining".

[0329] Furthermore, "determining" can also include cases where resolving, selecting, choosing, establishing, comparing, etc. are considered as performing "determining". That is to say, "determining" can also include cases where certain operations are considered as performing "determining".

[0330] In addition, "determining" can also be replaced by "assuming", "expecting", "considering", etc.

[0331] The terms "connected" and "coupled" as used in this disclosure, or all their variations, denote all direct or indirect connections or couplings between two or more elements, and can include the situation where there is one or more intermediate elements between the two elements that are "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination of them. For example, "connected" can also be replaced by "access".

[0332] In the present disclosure, in the case of connecting two elements, it can be considered that one or more electric wires, cables, printed electrical connections, etc. are used, and electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, optical (both visible and invisible) region, etc. is used as several non-limiting and non-exclusive examples to "connect" or "combine" with each other.

[0333] In the present disclosure, a term such as "A is different from B" can also mean "A and B are different from each other". In addition, this term can also mean "A and B are each different from C". Terms such as "separate" and "combine" can also be interpreted as "different" in the same way.

[0334] In the present disclosure, when using "include", "including", and their variants, these terms, like the term "comprising", have an inclusive meaning. Furthermore, the term "or" used in the present disclosure does not mean exclusive or.

[0335] In the present disclosure, for example, in the case where articles are added by translation such as a, an, and the in English, the present disclosure may also include cases where the nouns following these articles are in the plural form.

[0336] As described above, the invention related to the present disclosure has been described in detail. However, for those skilled in the art, the invention related to the present disclosure is clearly not limited to the embodiments described in the present disclosure. The invention related to the present disclosure can be implemented in the form of modifications and changes without departing from the gist and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not have any restrictive meaning with respect to the invention related to the present disclosure.

Claims

1. A terminal, comprising: a receiving unit that receives at least one of first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) and second DCI for scheduling a physical uplink shared channel (PUSCH); and a control unit that controls at least one of the following: a determination of a channel access type and a cyclic prefix extension based on a first field included in the first DCI, and a determination of a channel access type, a cyclic prefix extension, and a channel access priority level based on a second field included in the second DCI, wherein the first DCI is DCI format 1_2 and the second DCI is DCI format 0_2.

2. The terminal according to claim 1, wherein, the DCI format 1_2 and the DCI format 0_2 are DCI formats for ultra-reliable and low-latency communication (URLLC).

3. The terminal according to claim 1, wherein, when a specific higher-layer parameter is set, the bit length of the first field is any one of 1 to 4 bits, and when the specific higher-layer parameter is not set, the bit length of the first field is 0 bit.

4. The terminal according to claim 1, wherein, when a specific higher-layer parameter is set, the bit length of the second field is any one of 1 to 6 bits, and when the specific higher-layer parameter is not set, the bit length of the second field is 0 bit.

5. A wireless communication method for a terminal, comprising the following steps: receiving at least one of first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) and second DCI for scheduling a physical uplink shared channel (PUSCH); and controlling at least one of the following steps: a determination of a channel access type and a cyclic prefix extension based on a first field included in the first DCI, and a determination of a channel access type, a cyclic prefix extension, and a channel access priority level based on a second field included in the second DCI, wherein the first DCI is DCI format 1_2 and the second DCI is DCI format 0_2.

6. A base station, comprising: a transmitting unit that transmits at least one of first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) and second DCI for scheduling a physical uplink shared channel (PUSCH); and a control unit that controls at least one of the following: a determination of a channel access type and a cyclic prefix extension based on a first field included in the first DCI, and a determination of a channel access type, a cyclic prefix extension, and a channel access priority level using a second field included in the second DCI, wherein the first DCI is DCI format 1_2 and the second DCI is DCI format 0_2.

7. A system having a base station and a terminal, wherein, the base station has: a transmitting unit that transmits at least one of first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) and second DCI for scheduling a physical uplink shared channel (PUSCH), the terminal has: A receiving unit that receives at least one of the first DCI and the second DCI; and A control unit that controls at least one of the following: a decision on a channel access type and a cyclic prefix extension based on a first field included in the first DCI, and a decision on a channel access type, a cyclic prefix extension, and a channel access priority level based on a second field included in the second DCI, The first DCI is DCI format 1_2, and the second DCI is DCI format 0_2.

Images