Terminal, wireless communication method, base station and system

By employing tailored modulation and coding schemes, transmission power control, and separate HARQ-ACK codebooks, the wireless communication system addresses the challenge of diverse use cases in 5G and NR, optimizing performance for eMBB and URLLC.

JP7602570B2Active Publication Date: 2024-12-18NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023069232
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-04-20
Publication Date
2024-12-18
Estimated Expiration
2038-08-09

AI Technical Summary

Technical Problem

Future wireless communication systems, such as 5G and NR, face challenges in accommodating diverse use cases like eMBB and URLLC with different requirements, leading to insufficient performance for URLLC or excessive performance for eMBB due to common definitions in existing specifications.

Method used

The solution involves a terminal and wireless communication system that controls uplink and downlink transmissions and receptions using separate modulation and coding schemes, transmission power, HARQ-ACK codebooks, and other parameters tailored for each service type, such as eMBB and URLLC, through new MCS tables and RNTIs to optimize performance for each use case.

Benefits of technology

This approach allows for appropriate control of multiple use cases with different requirements, ensuring optimal performance for both eMBB and URLLC by independently managing transmission and reception conditions and parameters, thereby enhancing system efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007602570000005
    Figure 0007602570000005
  • Figure 0007602570000006
    Figure 0007602570000006
  • Figure 0007602570000007
    Figure 0007602570000007
Patent Text Reader

Abstract

To provide a terminal, a wireless communication method, a base station, and a system that prevent insufficient performance for URLLC or excessive performance for eMBB in transmission and reception operations for eMBB and URLLC for which many of the transmission and reception operations are commonly specified.SOLUTION: In a next-generation mobile communication system, a terminal (UE) includes: a receiving unit that receives downlink control information (DCI) for scheduling at least one of uplink (UL) transmission and downlink (DL) reception corresponding to different services, including modulation and coding scheme (MCS) fields; and a control unit that separately generates an acknowledgment signal (HARQ-ACK) codebook for the DL reception on he basis of the DCI for each HARQ-ACK transmission corresponding to the different service.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-A (LTE Advanced, LTE Rel. 10, 11, 12, 13) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (LTE Rel. 8, 9).

[0003] Successor systems to LTE (e.g., FRA (Future Radio Access), 5G (5th generation mobile communication system), 5G+ (plus), NR (New Radio), NX (New radio access), FX (Future generation radio access), LTE Rel. 14 or 15 or later, etc.) are also being considered.

[0004] In existing LTE systems (e.g., 3GPP Rel. 8-14), a user equipment (UE: User Equipment) controls reception of a physical downlink shared channel (e.g., PDSCH: Physical Downlink Shared Channel) based on downlink control information (DCI: Downlink Control Information, also called DL assignment, etc.) from a base station. Also, the UE controls transmission of a physical uplink shared channel (e.g., PUSCH: Physical Uplink Shared Channel) based on DCI (also called UL grant, etc.). The UE controls reception of the PDSCH (or transmission of the PUSCH) using a predetermined modulation and coding scheme (MCS: Modulation and Coding Scheme) table.

[0005] Furthermore, the UE transmits channel state information (CSI) using a predetermined channel quality indicator (CQI) table. [Prior art documents] [Non-patent literature]

[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 [Problem to be solved by the invention]

[0007] In future wireless communication systems (e.g., 5G (5th generation mobile communication system), NR (New Radio)), use cases such as enhanced mobile broadband (eMBB), massive machine type communications (mMTC) that realizes multiple simultaneous connections, and ultra-reliable and low-latency communications (URLLC) are expected. For example, URLLC requires higher latency reduction and higher reliability than eMBB.

[0008] In this way, various use cases (e.g., eMBB, URLLC, etc.) with different requirements are assumed in NR. However, in the specifications currently under consideration (e.g., Rel. 15), many of the transmission and reception operations of eMBB and URLLC are commonly specified. In this case, there is a risk that the performance will be insufficient for URLLC or excessive for eMBB.

[0009] The present disclosure has been made in consideration of such points, and one of its objectives is to provide a terminal, a wireless communication method, a base station, and a system that are capable of appropriately controlling each use case, even when multiple use cases with different requirements coexist in a wireless communication system. [Means for solving the problem]

[0010] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives downlink control information (DCI) including a modulation and coding scheme (MCS) field, the DCI including scheduling at least one of uplink (UL) transmission and downlink (DL) reception corresponding to different services; and a control unit that generates a delivery acknowledgement signal (HARQ-ACK) codebook for the DL reception based on the DCI separately for each HARQ-ACK transmission corresponding to the different services. The control unit controls a transmission power for each of the UL transmissions corresponding to the different services based on a value of a specific field in the DCI related to a transmission power of the UL transmission corresponding to the different services. The present invention is characterized by the above. Effect of the Invention

[0011] According to one aspect of the present disclosure, even when multiple use cases with different requirements coexist in a wireless communication system, it is possible to appropriately control each use case. [Brief description of the drawings]

[0012] [Figure 1] 1A and 1B are diagrams showing examples of MCS tables 1 and 2. [Diagram 2] FIG. 2 is a diagram showing an example of the MCS table 3. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing an example of transmission and reception control for each use case in this embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of an overall configuration of a base station according to an embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a functional configuration of a base station according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the overall configuration of a user terminal according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a functional configuration of a user terminal according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] In NR, it is expected that new MCS tables and CQI tables that are not specified in the existing LTE system will be introduced to support various use cases. The new tables may specify candidates (indexes) with lower coding rates than the existing tables.

[0014] In addition, when a new MCS table is introduced, a new RNTI (which may be called mcs-C-RNTI) may be used to specify the new MCS table. An example of an MCS table and an RNTI newly introduced in NR will be described below.

[0015] <MCSテーブル> In NR, it is considered to control at least one of the modulation scheme (or modulation order) and coding rate (modulation order / coding rate) of the physical shared channel scheduled by the DCI based on a predetermined field included in the DCI. For example, the UE controls the reception process of the PDSCH based on a modulation and coding scheme (MCS) field included in the DCI (e.g., DCI format 1_0, 1_1) that schedules the PDSCH.

[0016] Specifically, the UE receives the PDSCH based on a table (also called an MCS table) in which an MCS index, a modulation order, and a coding rate are defined in association with each other, and the MCS index specified by the DCI. Similarly, the UE transmits the PUSCH based on the MCS table and the MCS index specified by the DCI that schedules the PUSCH.

[0017] Each modulation order is a value corresponding to each modulation method. For example, the modulation order of QPSK (Quadrature Phase Shift Keying) is 2, the modulation order of 16QAM (Quadrature Amplitude Modulation) is 4, the modulation order of 64QAM is 6, and the modulation order of 256QAM is 8.

[0018] FIG. 1 is a diagram showing an example of an MCS table. Note that the values ​​in the MCS table shown in FIG. 1 are merely examples and are not limited to these. In addition, the MCS index (I MCS) may be omitted, and other items may be added.

[0019] In Fig. 1A, QPSK, 16QAM, and 64QAM are defined as modulation orders, and in Fig. 1B, QPSK, 16QAM, 64QAM, and 256QAM are defined as modulation orders. In Fig. 1A and Fig. 1B, the minimum coding rate (MCS index 0) is defined to be 120 (×1024).

[0020] The MCS table in Fig. 1A may be called MCS table 1 for PDSCH, 64QAM table, or qam64. The MCS table in Fig. 1B may be called MCS table 2 for PDSCH, 256QAM table, or qam256. The 64QAM table and 256QAM table shown in Fig. 1 are also specified in the existing LTE system.

[0021] In NR, cases where lower latency and higher reliability than in existing LTE systems are required (e.g., URLLC, etc.) are expected. To accommodate such cases, it is expected that a new MCS table different from the MCS table specified in the existing LTE system will be introduced.

[0022] An example of a new MCS table is shown in Fig. 2. Note that the values ​​in the MCS table shown in Fig. 2 are merely examples and are not limited to these. In Fig. 2, QPSK, 16QAM, and 64QAM are specified as modulation orders, and the minimum coding rate (MCS index 0) is defined to be 30 (x1024). The MCS table in Fig. 2 may be called MCS table 3 for PDSCH, a new MCS table, or qam64LowSE.

[0023] In this way, the new MCS table (MCS table 3) may be a table in which a coding rate (e.g., 30) lower than the minimum coding rate (e.g., 120) specified in the MCS tables (MCS table 1, MCS table 2) shown in Fig. 1 is specified. Alternatively, MCS table 3 may be a table in which a coding rate for the same MCS index is set lower than that of MCS table 1 or MCS table 2.

[0024] The UE may select an MCS table to be used for determining the modulation order / coding rate of the PDSCH based on at least one of the following conditions (1) to (3). (1) Whether or not a specific RNTI is set (2) Notification of information specifying the MCS table (MCS table information) (3) RNTI type applied to CRC scrambling of at least one of DCI (or PDCCH) and PDSCH

[0025] For example, assume that a predefined RNTI (which may be referred to as mcs-C-RNTI or new-RNTI) is not configured for a UE by a higher layer (e.g., RRC signaling). In this case, the UE may determine an MCS table to be applied based on MCS table information specified by a higher layer parameter (e.g., mcs-table).

[0026] The MCS table information may be information that specifies either MCS table 1, MCS table 2 (e.g., qam256), or MCS table 3 (e.g., qam64LowSE). Alternatively, the MCS table information may be information that specifies either MCS table 2 (e.g., qam256) or MCS table 3 (e.g., qam64LowSE).

[0027] When MCS table 2 is set, the UE applies MSC table 2 to control reception of the PDSCH.

[0028] When a new MCS table (MCS table 3) is configured, the UE may determine the MCS table to be applied based on the search space type used for transmitting DCI. For example, even when a new MCS table is configured, the UE uses MCS table 1 when DCI (for example, DCI formats 0_0, 1_0) is transmitted in a common search space. On the other hand, when a new MCS table is configured and DCI (for example, DCI formats 0_0, 1_0, 0_1, 1_0) is transmitted in a UE-specific search space, the UE uses MCS table 3. Note that separate MCS tables may be configured for UL (PUSCH transmission) and DL (PDSCH reception).

[0029] Next, assume that a predetermined RNTI used to select an MCS table is configured for the UE by a higher layer (e.g., RRC signaling). In this case, the UE may determine an MCS table based on the RNTI type applied to CRC scrambling of at least one of the DCI (or PDCCH) and the PDSCH. For example, when the CRC of the PDSCH is scrambled with a predetermined RNTI, the UE receives the PDSCH using a new MCS table (MCS table 3).

[0030] For PDSCH transmitted by semi-persistent scheduling (DL-SPS), whether or not a new MCS table is set may be notified by higher layer parameters (e.g., mcs-Table). The setting of a new MCS table for DL-SPS may be set independently of PDSCH transmission based on DCI (grant-based DL scheduling).

[0031] It should be noted that the conditions for using the table shown in FIG. 1-2 are not limited to the above conditions.

[0032] In this way, NR supports new MCS tables with lower coding rates, assuming various use cases with different requirements (e.g., eMBB, URLLC, etc.). On the other hand, in specifications currently under consideration (e.g., Rel. 15), many of the transmission and reception operations of eMBB and URLLC are commonly specified. In this case, there is a risk that performance will be insufficient for URLLC, or excessive performance for eMBB.

[0033] Therefore, the inventors came up with the idea of ​​controlling at least one of a given UL transmission method and DL reception method by applying at least one of different transmission and reception conditions and parameters for each use case having different requirements (see FIG. 3).

[0034] For example, the UE selects transmission and reception conditions / parameters to be applied based on at least one of the MCS table type specified in the DCI, the RNTI type applied to the CRC scrambling of the DCI (or the PDCCH), and the resource type to be set. Although the number of transmission and reception conditions / parameters is two in FIG. 3, the present invention is not limited to this, and the number of transmission and reception conditions / parameters may be three or more. The parameters may be parameters to be applied to transmission and reception, and may be, for example, higher layer parameters.

[0035] Hereinafter, an embodiment according to the present disclosure will be described in detail. The aspects according to the present embodiment may be applied independently or in combination. In the following description, a first communication service (e.g., eMBB) and a second communication service (e.g., URLLC) are taken as examples of use cases with different requirements, but the use cases to which the present embodiment can be applied are not limited to these.

[0036] In this specification, at least one of DL and UL transmissions that apply a new MCS table (e.g., MCS table 3) may be assumed to be URLLC, or at least one of DL and UL transmissions that apply an existing MCS table (e.g., MCS table 1 or MCS table 2) may be assumed to be eMBB.

[0037] For example, the UE may assume that a UL or DL ​​channel scheduled or triggered by a DCI indicating a new MCS table is subject to URLLC, while a UL or DL ​​channel scheduled or triggered by a DCI indicating an existing MCS table is subject to eMBB. The UL channel may be a PUCCH or PUSCH, and the DL channel may be a PDSCH.

[0038] Alternatively, when the UE receives a CRC-scrambled DCI (or a PDCCH) with a predetermined RNTI, the UE may assume that URLLC is applied to the UL channel or DL ​​channel scheduled by the DCI. Alternatively, different DCI (e.g., DCI format) may be applied for URLLC and eMBB.

[0039] In the following description, the predetermined RNTI may be referred to as MCS-RNTI, mcs-C-RNTI, URLLC-RNTI, U-RNTI, Y-RNTI, New-RNTI, or X-RNTI. That is, in the following description, the predetermined RNTI may be read as at least one of MCS-RNTI, URLLC-RNTI, U-RNTI, Y-RNTI, and X-RNTI.

[0040] (First aspect) In the first aspect, the UL transmission power is separately controlled for the UL transmission of the first communication service (hereinafter also referred to as eMBB) and the UL transmission of the second communication service (hereinafter also referred to as URLLC). The UL transmission may be at least one of an uplink control channel (e.g., PUCCH) and an uplink shared channel (e.g., PUSCH).

[0041] First, the transmission power control of PUCCH and PUSCH will be described.

[0042] <Transmission Power Control for PUCCH> In NR, the transmission power of PUCCH is controlled based on the TPC command (also referred to as a value, an increment / decrement value, a correction value, etc.) indicated by the value of a predetermined field (also referred to as a TPC command field, a first field, etc.) in DCI.

[0043] For example, the transmission power (P PUCCH、b,f,c (i,q u ,q d ,l)) of PUCCH in the transmission occasion (also referred to as a transmission period, etc.) i of the BWP b of the carrier f of the cell c using the index l of the power control adjustment state may be represented by the following formula (1).

[0044] Here, whether the power control adjustment state has a plurality of states (e.g., two states) or a single state may be set by a higher layer parameter. Also, when a plurality of power control adjustment states are set, one of the plurality of power control adjustment states may be identified by the index l (e.g., l ∈ {0,1}). The power control adjustment state may be referred to as a PUCCH power control adjustment state, a first or second state, etc.

[0045] Also, the transmission occasion i of PUCCH is a predetermined period during which PUCCH is transmitted, and may be composed of, for example, one or more symbols, one or more slots, etc.

[0046]

number

[0047] In formula (1), P CMAX,f,c (i) is, for example, the transmission power (also called maximum transmission power, etc.) of the user terminal set for carrier f of cell c at transmission opportunity i. O_PUCCH,b,f,c (q u ) is, for example, a parameter related to the target received power set for BWP b of carrier f of cell c at transmission opportunity i (e.g., a parameter related to a transmit power offset, also referred to as a transmit power offset P0 or a target received power parameter, etc.).

[0048] M PUCCH RB,b,f,c (i) is the number of resource blocks (bandwidth) allocated to the PUCCH for transmission opportunity i in uplink BWP b of carrier f with cell c and subcarrier spacing μ. b,f,c (q d ) is, for example, the index q of the reference signal for the downlink BWP associated with the uplink BWP b of the carrier f of the cell c. d is the path loss calculated at the user terminal using

[0049] Δ F_PUCCH (F) is a higher layer parameter given for each PUCCH format. Δ TF,b,f,c (i) is the transmission power adjustment component (offset) for uplink BWP b of carrier f in cell c;

[0050] g b,f,c (i, l) is a value based on the TPC command of the power control adjustment state index l of the uplink BWP of carrier f of cell c and transmission opportunity i (e.g., an accumulated value of the TPC command). For example, the accumulated value of the TPC command may be expressed by Equation (2).

number

[0051] In Equation (2), δ PUCCH,b,f,c (i last , i, K PUCCH , l) may be, for example, the TPC command indicated by the TPC command field value in the DCI (e.g., DCI format 1_0 or 1_1) detected on the uplink BWP b of carrier f of cell c for transmission opportunity i after the previous PUCCH transmission opportunity i, or the TPC command indicated by the TPC command field value in the DCI (e.g., DCI format 2_2) having CRC parity bits scrambled by a specific RNTI (Radio Network Temporary Identifier) (e.g., TPC-PUCCH-RNTI).

[0052] Note that Equations (1) and (2) are merely illustrative and not limited thereto. The user equipment may control the transmission power of the PUCCH based on at least one parameter exemplified in Equations (1) and (2), additional parameters may be included, or some parameters may be omitted. Also, in the above Equations (1) and (2), the transmission power of the PUCCH is controlled for each BWP of a certain carrier of a certain cell, but this is not limiting. At least a part of the cell, carrier, BWP, and power control adjustment state may be omitted.

[0053] <Transmission Power Control for PUSCH> In NR, the transmission power of the PUSCH is controlled based on the TPC command (also referred to as a value, increment / decrement value, correction value, etc.) indicated by the value of a predetermined field (also referred to as the TPC command field, the first field, etc.) in the DCI.

[0054] ​​For example, when a UE transmits a PUSCH on a BWP b of a carrier f of a cell c using a parameter set (open loop parameter set) having an index j and a power control adjustment state index l, the transmission power (P PUSCH、b,f,c (i,j,q d , l) may be expressed by the following formula (3).

[0055] Here, the power control adjustment state may be configured to have multiple states (e.g., two states) or a single state by a higher layer parameter. In addition, when multiple power control adjustment states are configured, one of the multiple power control adjustment states may be identified by an index l (e.g., l∈{0,1}). The power control adjustment state may be called a PUSCH power control adjustment state, a first or second state, etc.

[0056] Furthermore, the PUSCH transmission opportunity i is a predetermined period during which the PUSCH is transmitted, and may be composed of, for example, one or more symbols, one or more slots, or the like.

[0057]

number

[0058] In equation (3), P CMAX,f,c(i) is, for example, the transmission power (also called maximum transmission power, etc.) of the user terminal set for carrier f of cell c at transmission opportunity i. O_PUSCH,b,f,c (j) is, for example, a parameter related to a target received power set for BWP b of carrier f of cell c at transmission opportunity i (for example, a parameter related to a transmission power offset, also referred to as a transmission power offset P0, a target received power parameter, etc.).

[0059] M PUSCH RB,b,f,c(i) is the number of resource blocks (bandwidth) allocated to the PUSCH for transmission opportunity i in uplink BWP b of carrier f with cell c and subcarrier spacing μ. b,f,c (j) is a value provided by a higher layer parameter (e.g., also called msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0060] PL b,f,c (q d ) is, for example, the index q of the reference signal for the downlink BWP associated with the uplink BWP b of the carrier f of the cell c. d is the path loss (path loss compensation) calculated at the user terminal using

[0061] Δ TF,b,f,c (i) is a transmission power adjustment component (offset, transmission format compensation) for uplink BWP b of carrier f in cell c.

[0062] f b,f,c (i, l) is a value based on the TPC command of the power control adjustment state index l of the uplink BWP of carrier f of cell c and transmission opportunity i (e.g., an accumulated value of the TPC command, a value by closed loop). For example, the accumulated value of the TPC command may be expressed by Equation (4).

number

[0063] In formula (4), δ PUSCH,b,f,c (i last ,i,K PUSCH , l) is, for example, the previous PUSCH transmission opportunity i lastThe TPC command may be a TPC command indicated by a TPC command field value in a DCI (e.g., DCI format 0_0 or 0_1) detected in an uplink BWP b of carrier f of cell c for a subsequent transmission opportunity i, or a TPC command indicated by a TPC command field value in a DCI (e.g., DCI format 2_2) having CRC parity bits scrambled with a specific RNTI (Radio Network Temporary Identifier) ​​(e.g., TPC-PUSCH-RNTI) (CRC-scrambled).

[0064] Note that formulas (3) and (4) are merely examples and are not limited thereto. The user terminal only needs to control the transmission power of the PUSCH based on at least one parameter exemplified in formulas (3) and (4), and additional parameters may be included or some parameters may be omitted. In addition, in the above formulas (3) and (4), the transmission power of the PUSCH is controlled for each BWP of a certain carrier of a certain cell, but this is not limited thereto. At least some of the cell, carrier, BWP, and power control adjustment state may be omitted.

[0065] In this way, in the UL transmission power control of the PUCCH and the transmission power control of the PUSCH, the UL transmission power is controlled by accumulating the TPC commands notified from the base station (eg, the above formula (2), formula (4), etc.).

[0066] The UE may control the TPC commands for eMBB and the TPC commands for URLLC separately (or independently). For example, the UE performs accumulation of TPC commands separately for eMBB and URLLC. That is, the accumulation of TPC commands for eMBB (e.g., g b,f,c (i,l), f b,f,c (i,l)) etc. are applied in the UL transmission of eMBB, and accumulation of TPC commands for URLLC etc. are applied in the UL transmission of URLLC.

[0067] Furthermore, whether or not to apply the method of separately storing TPC commands for each communication service may be set in the UE from the base station using higher layer signaling (for example, Separate TPC command).

[0068] Assume that a method for storing TPC commands separately for each communication service is set, and UL transmission corresponding to URLLC is instructed. The UL transmission may be PUCCH or PUSCH. In this case, the UE stores the TPC commands notified for the UL transmission corresponding to URLLC independently.

[0069] The case where UL transmission corresponding to URLLC is instructed may be at least one of the cases where a new MCS table (e.g., MCS table 3) is specified by DCI, where CRC-scrambled DCI is received with a specified RNTI, and where URLLC resources set in higher layer parameters are specified by DCI.

[0070] When PUCCH transmission corresponding to URLLC is instructed, the UE applies the formula (g URLLC b,f,c In addition, when PUSCH transmission corresponding to URLLC is instructed, the UE accumulates TPC commands based on the formula (f URLLC b,f,c The TPC is accumulated based on (i,l).

[0071] In other cases (e.g., when UL transmission corresponding to URLLC is not indicated), the UE applies the formula (g eMBB b,f,c In addition, when PUSCH transmission corresponding to eMBB is instructed, the UE separately accumulates the TPC command for eMBB based on the formula (f eMBB b,f,cThe TPC for eMBB is accumulated separately based on (i,l).

[0072] In addition, when a TPC command is notified by DCI that does not schedule (or trigger) DL or UL, the UE uses the TPC command as the accumulated TPC command value for URLLC (g URLLC b,f,c (i,l), or f URLLC b,f,c (i,l)) and the cumulative value of the TPC command for eMBB (g eMBB b,f,c (i,l), or f eMBB b,f,c In this case, when the UL transmission power for all services is changed, control can be performed using one DCI.

[0073] Alternatively, when a TPC command is notified by a DCI that does not schedule (or trigger) DL or UL, the UE may control to add the TPC command to either the accumulated value of TPC commands for URLLC or the accumulated value of TPC commands for eMBB. In this case, the UE may determine which communication service's TPC command to accumulate based on the RNTI or higher layer parameters applied to the DCI.

[0074] In this way, by independently controlling the application (eg, accumulation) of TPC commands for each communication service (or for each service having different requirements), it is possible to set an appropriate transmission power for each communication service.

[0075] (Second aspect) In the second aspect, the transmission processing of HARQ-ACK (e.g., codebook generation, etc.) is controlled separately for UL transmission of a first communication service (hereinafter also referred to as eMBB) and HARQ-ACK transmission of a second communication service (hereinafter also referred to as URLLC).

[0076] <HARQ-ACKコードブック> In NR, it is assumed that the UE determines the HARQ-ACK codebook (which may also be called the HARQ-ACK size) semi-statically or dynamically. The base station may notify the UE of information indicating the method of determining the HARQ-ACK codebook, for example, information indicating whether the HARQ-ACK codebook is semi-static or dynamic, by higher layer signaling for each component carrier, each cell group (CG), each PUCCH group, or each user terminal.

[0077] The HARQ-ACK codebook may be interpreted as a PDSCH HARQ-ACK codebook, a HARQ-ACK codebook size, the number of HARQ-ACK bits, or the like.

[0078] The UE may determine (generate) a HARQ-ACK information bit based on the determined HARQ-ACK codebook for each component carrier, each cell group, each PUCCH group, or each user terminal, and may transmit the generated HARQ-ACK using at least one of the uplink control channel (PUCCH) or the uplink shared channel (PUSCH).

[0079] If the UE is configured to semi-statically determine a HARQ-ACK codebook or is configured with a semi-static HARQ-ACK codebook, the HARQ-ACK codebook determination may be referred to as Type 1 HARQ-ACK codebook determination. If the UE is configured to dynamically determine a HARQ-ACK codebook or is configured with a dynamic HARQ-ACK codebook, the HARQ-ACK codebook determination may be referred to as Type 2 HARQ-ACK codebook determination.

[0080] The type 1 HARQ-ACK codebook and the semi-static HARQ-ACK codebook may be interchangeable, and the type 2 HARQ-ACK codebook and the dynamic HARQ-ACK codebook may be interchangeable.

[0081] In the type 1 HARQ-ACK codebook determination, the UE may determine the number of HARQ-ACK bits, etc. based on the configuration set by higher layer signaling. The set configuration may include, for example, the maximum or minimum number of DL (Downlink) transmissions, e.g., PDSCHs, to be scheduled over a range associated with the feedback timing of the HARQ-ACK.

[0082] The range is also called a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc. The bundling window may correspond to at least one range of space, time, and frequency.

[0083] In determining the type 2 HARQ-ACK codebook, the UE may determine the number of HARQ-ACK bits based on the bit string of a Downlink Assignment Index (DAI) field included in downlink control information, for example, a DL assignment. The DAI field may indicate at least one of a total DAI and a counter DAI.

[0084] The UE and the base station may separately (or independently) control the HARQ-ACK codebook to be applied to the HARQ-ACK transmission of eMBB and the HARQ-ACK codebook to be applied to the HARQ-ACK transmission of URLLC.

[0085] For example, the base station sets a HARQ-ACK codebook to be applied to the HARQ-ACK transmission of eMBB and a HARQ-ACK codebook to be applied to the HARQ-ACK transmission of URLLC separately. For example, the HARQ-ACK codebook to be applied to the HARQ-ACK transmission of eMBB may be type 1, and the HARQ-ACK codebook to be applied to the HARQ-ACK transmission of URLLC may be type 2.

[0086] The UE generates a HARQ-ACK codebook to be applied to the HARQ-ACK transmission of eMBB and a HARQ-ACK codebook to be applied to the HARQ-ACK transmission of URLLC separately.

[0087] Furthermore, whether or not to apply the method of generating a HARQ-ACK codebook separately for each communication service may be set in the UE from the base station using higher layer signaling (for example, SeparateHARQ-ACKcodebook).

[0088] Assume that a method of generating (or setting) a HARQ-ACK codebook separately for each communication service is set. When a UE receives a PDSCH, the UE transmits a HARQ-ACK for the PDSCH. In this case, the UE transmits the HARQ-ACK in a slot (or a PUCCH resource, a symbol, etc.) designated by a DCI or the like that schedules the PDSCH. The UE also generates a HARQ-ACK codebook in consideration of the HARQ-ACK to be transmitted in the same slot (or a PUCCH resource, a symbol, etc.).

[0089] In this case, when the UE receives a PDSCH corresponding to URLLC, the UE generates a HARQ-ACK codebook for URLLC and transmits a HARQ-ACK. On the other hand, when the UE receives a PDSCH corresponding to eMBB, the UE generates a HARQ-ACK codebook for eMBB and transmits a HARQ-ACK.

[0090] The UE may determine the communication service corresponding to the HARQ-ACK based on at least one of the MCS table (MCS table 3 / MCS table 1 or 2) specified in the DCI scheduling the PDSCH, the RNTI (predetermined RNTI / C-RNTI) used for CRC scrambling of the DCI scheduling the PDSCH, and the resources (URLLC resources / eMBB resources) specified by the DCI scheduling the PDSCH.

[0091] For example, if the transmission of HARQ-ACKs corresponding to PDSCHs for multiple URLLCs is specified to use the same slot, the same symbol (or overlapping symbols), or the same PUCCH resource, the UE generates a HARQ-ACK codebook for URLLC.

[0092] In addition, if the transmission of HARQ-ACKs corresponding to PDSCHs for multiple eMBBs is specified to use the same slot, the same symbol (or overlapping symbols), or the same PUCCH resource, the UE generates a HARQ-ACK codebook for eMBB.

[0093] There may be a case where the slots (or PUCCH resources, symbols, etc.) for transmitting the HARQ-ACK for the PDSCH for eMBB and the HARQ-ACK for the PDSCH for URLLC overlap. In this case, the UE may generate a different HARQ-ACK codebook and select a different resource (e.g., a PUCCH resource) for transmission.

[0094] In this way, by independently controlling the generation of the HARQ-ACK codebook for each communication service (or for each service having different requirements), it is possible to perform appropriate HARQ-ACK transmission for each communication service.

[0095] (Third aspect) In the third aspect, a demodulation reference signal (e.g., DMRS) applied to a first communication service (hereinafter also referred to as eMBB) and a configuration of a DMRS applied to a second communication service (hereinafter also referred to as URLLC) are controlled separately. The configuration of the DMRS may be called a DMRS arrangement or a DM-RS setting.

[0096] In NR, the resource (RE: Resource Element) mapping pattern of the DMRS used for the shared channel (PUSCH, PDSCH) is determined by the DMRS type. The UE may be configured with the DMRS configuration type for each channel from the base station using higher layer signaling.

[0097] The DMRS type is information indicating a mapping pattern of the DMRS to resource elements (REs). In Type 1, the DMRS is mapped based on the first symbol of the slot, whereas in Type 2, the DMRS is mapped based on the start symbol scheduled in the PDSCH. The DMRS type may be indicated by a higher layer parameter (e.g., "dmrs-Type" included in "DMRS-DownlinkConfig").

[0098] The UE may determine that the DL(UL) DMRS is, for example, type 2 if an RRC information element for DL(UL) ("dmrs-Type" information element) is set, and type 1 if it is not set.

[0099] Furthermore, the number (or the number and location) of DMRSs for a shared channel may be determined depending on the presence or absence of an additional DMRS. As information indicating the number or location of the additional DMRS, location information of the additional DMRS indicating the location of the DMRS to be additionally mapped may be notified to the UE from the base station. The location information of the additional DMRS may be indicated by a higher layer parameter (e.g., "dmrs-AdditionalPosition" included in "DMRS-DownlinkConfig").

[0100] The UE and the base station may separately configure a DMRS configuration to be used for an eMBB shared channel, etc., and a DMRS configuration to be used for a URLLC shared channel, etc. The separately configured DMRS configuration may be, for example, at least one of the DMRS type, the number, and the location.

[0101] For example, the base station configures the DMRS configuration of eMBB and the DMRS configuration of URLLC in the UE separately using higher layers. For example, the base station configures the DMRS configuration of eMBB in the UE using a predetermined higher layer parameter (e.g., DMRS-DownlinkConfig or DMRS-UplinkConfig). The base station may also configure the DMRS configuration of URLLC in the UE using a higher layer parameter different from the predetermined higher layer parameter or another information element included in the predetermined higher layer parameter.

[0102] Furthermore, whether or not to apply the method of separately configuring the DMRS configuration for each communication service may be configured in the UE from the base station using higher layer signaling (eg, SeparateDMRSconfig).

[0103] When a method for setting the DMRS configuration separately for each communication service is set, the UE separately controls the DMRS configuration to be applied for transmission and reception for URLLC and the DMRS configuration to be applied for transmission and reception for eMBB, based on the DMRS configuration for each communication service set by the base station.

[0104] The UE may select the DMRS configuration to apply based on at least one of the MCS table (MCS table 3 / MCS table 1 or 2) specified in the DCI that schedules the shared channel, the RNTI (predetermined RNTI / C-RNTI) used for CRC scrambling of the DCI that schedules the shared channel, and the resources (URLLC resources / eMBB resources) specified by the DCI that schedules the shared channel.

[0105] For example, if the shared channel corresponds to eMBB (e.g., MCS table 1 or 2, a predetermined RNTI is not applied, or URLLC resources are not configured), the UE applies the DMRS configuration set by a first higher layer parameter (e.g., DMRS-DownlinkConfig or DMRS-UplinkConfig). On the other hand, if the shared channel corresponds to URLLC (e.g., MCS table 3, a predetermined RNTI is applied, or URLLC resources are configured), the UE applies the DMRS configuration set by a second higher layer parameter different from the first higher layer parameter.

[0106] In this way, by independently controlling the DMRS configuration for each communication service (or for each service having different requirements), appropriate transmission and reception can be performed for each communication service.

[0107] (Fourth aspect) In the fourth aspect, a Phase-Tracking Reference Signal (PTRS) for phase noise compensation applied to a first communication service (hereinafter also referred to as eMBB) and a configuration of a PTRS (also referred to as a PT-RS setting) applied to a second communication service (hereinafter also referred to as URLLC) are controlled separately. The configuration of the PTRS may be called a PTRS arrangement or a PT-RS setting.

[0108] In NR, a base station (e.g., a gNB) transmits a Phase Tracking Reference Signal (PTRS) in the downlink. The base station may transmit the PTRS by mapping it, for example, in one subcarrier, continuously or non-continuously in the time direction. The base station may transmit the PTRS in at least a part of a period (slot, symbol, etc.) during which a downlink shared channel (PDSCH) is transmitted. The PTRS transmitted by the base station may be referred to as DL PTRS.

[0109] Furthermore, the UE transmits a phase tracking reference signal (PTRS) in the uplink. The UE may transmit the PTRS by mapping it, for example, contiguously or non-contiguously in the time direction in one subcarrier. The UE may transmit the PTRS in at least a part of a period (slot, symbol, etc.) in which an uplink shared channel (PUSCH: Physical Uplink Shared Channel) is transmitted. The PTRS transmitted by the UE may be called an UL PTRS. Hereinafter, the UL PTRS will be simply called a PTRS.

[0110] The UE may determine whether there is a PTRS in the uplink based on the configuration of higher layer signaling (e.g., the presence or absence of a PTRS-UplinkConfig information element). The UE may assume that a PTRS is present in a resource block for a PUSCH. The base station may determine a phase noise based on the PTRS transmitted from the UE and correct the phase error of the received signal.

[0111] The UE and the base station may separately configure a PTRS configuration to be used for eMBB and a PTRS configuration to be used for URLLC. The separately configured PTRS configuration may be, for example, at least one of time / frequency-domain density and whether or not a PTRS is configured. For example, the time / frequency-domain density of one PTRS (e.g., for URLLC) may be configured to be higher than the time / frequency-domain density of the other PTRS (e.g., for eMBB). Alternatively, a configuration may be used in which one PTRS (e.g., for URLLC) is configured and the other PTRS (e.g., for eMBB) is not configured.

[0112] The base station may set the PTRS configuration of eMBB and the PTRS configuration of URLLC in the UE separately by using higher layers. For example, the base station sets the PTRS configuration of eMBB in the UE by using a predetermined higher layer parameter (e.g., PTRS-DownlinkConfig or PTRS-UplinkConfig). The base station may also set the PTRS configuration of URLLC in the UE by using a higher layer parameter different from the predetermined higher layer parameter or another information element included in the predetermined higher layer parameter.

[0113] In addition, whether or not to apply the method of separately configuring the PTRS configuration for each communication service may be configured in the UE from the base station using higher layer signaling (for example, SeparatePTRSconfig).

[0114] When a method of configuring PTRS separately for each communication service is set, the UE separately controls the PTRS configuration to be used for URLLC and the PTRS configuration to be used for eMBB based on the PTRS configuration for each communication service set by the base station.

[0115] The UE may select the PTRS configuration to apply based on at least one of the MCS table (MCS table 3 / MCS table 1 or 2) specified in the DCI that schedules the shared channel, the RNTI (predetermined RNTI / C-RNTI) used for CRC scrambling of the DCI that schedules the shared channel, and the resources (URLLC resources / eMBB resources) specified by the DCI that schedules the shared channel.

[0116] For example, when URLLC is supported (e.g., MCS Table 3, application of a specific RNTI, or configuration of URLLC resources), the UE may control transmission or reception of the PTRS depending on whether or not a specific higher layer parameter for URLLC is configured. The specific higher layer parameter may be, for example, "URLLCphaseTrackingRS" included in "DMRS-DownlinkConfig" or "DMRS-UplinkConfig", or "phaseTrackingRS" included in "URLLC-DMRS-DownlinkConfig" or "URLLC-DMRS-UplinkConfig". If the specific higher layer parameter is not configured, the UE may control not to transmit or receive the PTRS.

[0117] In addition, when a specific upper layer parameter for URLLC is set, the UE controls the transmission or reception of PTRS based on an upper layer parameter different from the upper layer parameter used to notify the PTRS configuration of eMBB (e.g., PTRS-DownlinkConfig or PTRS-UplinkConfig, or frequencyDensity, timeDensity, etc. included in PTRS-DownlinkConfig or PTRS-UplinkConfig).

[0118] Furthermore, when eMBB is supported (for example, MCS table 1 or 2, a specific RNTI is not applied, or eMBB resources are configured), the UE may control transmission or reception of the PTRS depending on whether a specific higher layer parameter for eMBB is configured. The specific higher layer parameter for eMBB may be, for example, "phaseTrackingRS" included in "DMRS-DownlinkConfig" or "DMRS-UplinkConfig". If the specific higher layer parameter is not configured, the UE may control not to transmit or receive the PTRS.

[0119] When specific upper layer parameters for eMBB are configured, the UE controls the transmission or reception of PTRS based on the upper layer parameters (e.g., PTRS-DownlinkConfig or PTRS-UplinkConfig) used to notify the PTRS configuration of eMBB.

[0120] In this way, by independently controlling the PTRS configuration for each communication service (or for each service with different requirements), appropriate transmission and reception can be performed for each communication service.

[0121] (Fifth aspect) In the fifth aspect, a PUCCH resource set for a first communication service (hereinafter also referred to as eMBB) and a PUCCH resource set for a second communication service (hereinafter also referred to as URLLC) are controlled separately. Note that the PUCCH resource may be read as a PUCCH resource set.

[0122] <PUCCHリソース> In NR, a set of one or more resources for PUCCH (PUCCH resources) may be configured by higher layer signaling.

[0123] For example, a set including one or more PUCCH resources (PUCCH resource set) may be configured by higher layer signaling for each partial band (bandwidth part (BWP)) configured within a CC.

[0124] Furthermore, each PUCCH resource in the PUCCH resource set configured by higher layer signaling may be associated with each value of a predetermined field in DCI (also referred to as a PUCCH resource indicator / indication (PRI) field, an ACK / NACK resource indicator (ARI) field, an ACK / NACK resource offset (ARO) field, a second field, etc.). The DCI may be a DCI (DL assignment, DCI format 1_0 or 1_1) used for scheduling the PDSCH.

[0125] The UE determines the PUCCH resource used for transmitting the UCI based on the value of the PRI field in the DCI. The PRI field may be x bits (e.g., x=3). If the PUCCH resource set includes 2 to the power of x (e.g., 8 if x=3) or less PUCCH resources, the user terminal may determine the PUCCH resource associated with the value of the PRI field for transmitting the UCI.

[0126] On the other hand, if the PUCCH resource set includes more than 2 to the power of x (e.g., 8 if x = 3), the user terminal PRI In addition to the PUCCH resource allocation (also referred to as PRI, ARI, ARO, etc.), other parameters may be used to determine the PUCCH resource for transmitting the UCI. The other parameters may include at least one of the following: The number of control channel elements (CCEs) in a control resource set (CORESET) p for receiving a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel) that transmits DCI including a PRI field (N CCE,p ) The index (nCCE,p , CCE Index)

[0127] Each PUCCH resource may include at least one of the following: the number of symbols allocated to the PUCCH, a starting index of the symbols, a resource block (also called a physical resource block (PRB)) allocated to the PUCCH, a starting index of the resource block, whether or not frequency hopping is applied within the slot, and a starting index of the PRB of the second hop when frequency hopping is applied.

[0128] Furthermore, each PUCCH resource may be associated with the above PUCCH format and may include resources specific to the associated PUCCH format (eg, initial cyclic shift of PF0, OCC in the time domain of PF1, OCC length of PF4, OCC index, etc.).

[0129] The UE and the base station may separately configure the PUCCH resource (or the PUCCH resource set) to be used for eMBB and the PUCCH resource (or the PUCCH resource set) to be used for URLLC.

[0130] For example, the base station configures the PUCCH resource for eMBB and the PUCCH resource for URLLC in the UE separately using the higher layer. For example, the base station configures the PUCCH resource for eMBB in the UE using a predetermined higher layer parameter (for example, PUCCH-ResourceSet included in PUCCH-Config, or eMBB-PUCCH included in PUCCH-Resource). The base station may also configure the PUCCH resource for URLLC in the UE using a higher layer parameter different from the predetermined higher layer parameter (for example, URLLC-PUCCH included in PUCCH-Resource), or another information element included in the predetermined higher layer parameter.

[0131] Furthermore, whether or not to apply the method of separately configuring PUCCH resources for each communication service may be configured in the UE from the base station using higher layer signaling (eg, SeparatePUCCHresourceSet).

[0132] When a method of setting the DMRS configuration separately for each communication service is set, the UE separately controls the PUCCH resources to be applied to PUCCH transmission for URLLC and the PUCCH resources to be applied to PUCCH transmission for eMBB based on the PUCCH resource configuration for each communication service set by the base station.

[0133] The UE may select an applicable PUCCH resource based on at least one of the MCS table (MCS table 3 / MCS table 1 or 2) specified in the DCI scheduling the shared channel, the RNTI (predetermined RNTI / C-RNTI) used for CRC scrambling of the DCI scheduling the shared channel, and the resource (URLLC resource / eMBB resource) specified by the DCI scheduling the shared channel.

[0134] For example, when transmitting a PUCCH corresponding to URLLC (e.g., MCS table 3, applying a predetermined RNTI, or setting a URLLC resource), the UE applies a PUCCH resource set by a higher layer parameter different from the predetermined higher layer parameter for eMBB. On the other hand, when transmitting a PUCCH corresponding to eMBB, the UE applies a DMRS configuration set by the predetermined higher layer parameter.

[0135] In addition, the PUCCH resource set may not be set for each communication service, but each PUCCH resource may be set for each communication service. In this case, the UE may select and use a predetermined PUCCH resource from the PUCCH resource set set based on the applicable communication service.

[0136] In this way, by independently controlling the PUCCH resources for each communication service (or for each service having different requirements), it is possible to flexibly set the PUCCH resources for each communication service.

[0137] (Sixth aspect) In the sixth aspect, the number of repeat transmissions set for the first communication service (hereinafter also referred to as eMBB) and the number of repeat transmissions set for the second communication service (hereinafter also referred to as URLLC) are controlled separately. The number of repeat transmissions may be called a repeat factor.

[0138] In NR, repetition of transmission of at least one of a channel and a signal (channel / signal) is being considered. The channel / signal is, for example, a PDSCH, a PDCCH, a PUSCH, a PUCCH, a DL-RS, an uplink reference signal (UL-RS), etc., but is not limited thereto.

[0139] The number of repetitions is also referred to as a repetition factor K or an aggregation factor K. For example, the repetition factor K may be selected from a number of preset values ​​(e.g., 2, 4, 8, etc.). The n-th repetition may also be referred to as an n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K−1).

[0140] For example, the UE may receive information indicating the repetition factor K through higher layer signaling. The UE detects the DCI that schedules the PDSCH that is repeatedly transmitted in a serving cell or a partial band (bandwidth part (BWP)) in the serving cell.

[0141] The UE may detect the DCI by monitoring a CORESET (a set of one or more search spaces (SS sets) associated with the CORESET or PDCCH candidates constituting the SS set) configured in the DL BWP. The UE receives the PDSCH in K consecutive slots after a predetermined period from the slot in which the DCI is detected.

[0142] Specifically, the UE controls a reception process (e.g., at least one of reception, demapping, demodulation, and decoding) of a PDSCH or a transmission process (e.g., at least one of transmission, mapping, modulation, and coding) of a PUSCH in K consecutive slots based on at least one of the following field values ​​(or information indicated by the field value) in the DCI: Allocation of time domain resources (e.g. starting symbol, number of symbols in each slot, etc.); Allocation of frequency domain resources (e.g., a certain number of resource blocks (RBs) and a certain number of resource block groups (RBGs)), Modulation and Coding Scheme (MCS) index, Demodulation Reference Signal (DMRS) configuration, · State of the Transmission Configuration Indication (TCI) (TCI-state).

[0143] The UE controls reception of the PDSCH in each slot, assuming that the time domain resources, the same frequency domain resources, the MCS index, and the DMRS configurations allocated to the PDSCH are the same among K consecutive slots that are semi-statically set by higher layer signaling. That is, the user terminal assumes that the above field values ​​in a single DCI are applied to all K consecutive slots.

[0144] The UE and the base station may set a repetition factor to be applied to the UL channel or DL ​​channel of eMBB and a repetition factor to be applied to the UL channel or DL ​​channel of URLLC separately. The UL channel may be at least one of PUSCH and PUCCH, and the DL channel may be at least one of PDSCH and PDCCH. For example, the number of candidates for the number of repetition transmissions to be predefined and the maximum value of the number of repetition transmissions may be predefined in the specifications separately for each communication service.

[0145] For example, the base station sets the repetition factor for eMBB and the repetition factor for URLLC in the UE separately by using the upper layer. For example, the base station sets the repetition factor for eMBB in the UE by using a predetermined upper layer parameter (e.g., repK, pucch-Repetition-F1-3-4, or pusch-RepetitionMultiSlots). The base station may also set the repetition factor for URLLC in the UE by using an upper layer parameter different from the predetermined upper layer parameter, or by using another information element included in the predetermined upper layer parameter.

[0146] Furthermore, whether or not to apply the method of separately setting the repetition factor for each communication service may be set from the base station to the UE by using higher layer signaling (for example, SeparatePUCCHresourceSet).

[0147] When a method for setting the repetition factor separately for each communication service (or for each channel type of communication service) is configured, the UE controls the repetition factor to be applied to URLLC and the repetition factor to be applied to eMBB separately based on the repetition factor for each communication service set by the base station.

[0148] The UE may select the repetition factor to be applied based on at least one of the MCS table (MCS table 3 / MCS table 1 or 2) specified in the DCI, the RNTI (predetermined RNTI / C-RNTI) used for CRC scrambling of the DCI, and the resources (URLLC resources / eMBB resources) specified by the DCI that schedules the shared channel.

[0149] For example, if MCS table 1 or 2 is specified in the DCI, if a predefined RNTI is not applied to the DCI, or if a URLLC resource is not specified, the UE applies the repetition factor set in the first higher layer parameter, whereas if MCS table 3 is specified in the DCI, if a predefined RNTI is applied to the DCI, or if a URLLC resource is specified, the UE applies the repetition factor set in the second higher layer parameter.

[0150] In this way, the UE controls the transmission or reception operations shown in the above first to sixth aspects separately for each communication service type (or MCS table type, RNTI type, resource type to be set, etc.). For example, the UE may apply conditions set by different upper layer parameters for each communication service type.

[0151] In this way, by independently controlling the repetition factor for each communication service (or for each service having different requirements), it is possible to flexibly control the repetition transmission for each communication service.

[0152] (Wireless communication system) A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using at least one of the wireless communication methods described in the above embodiments or a combination of these methods.

[0153] 4 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. In the wireless communication system 1, carrier aggregation (CA) and / or dual connectivity (DC) can be applied, in which a plurality of basic frequency blocks (component carriers) are integrated into one unit, the system bandwidth (e.g., 20 MHz) of the LTE system.

[0154] The wireless communication system 1 may be referred to as LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), NR (New Radio), FRA (Future Radio Access), New-RAT (Radio Access Technology), etc., or may be referred to as a system that realizes these.

[0155] In addition, the wireless communication system 1 may support dual connectivity between multiple RATs (Radio Access Technologies) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE and NR (EN-DC: E-UTRA-NR Dual Connectivity) in which an LTE (E-UTRA) base station (eNB) is the master node (MN) and an NR base station (gNB) is the secondary node (SN), and dual connectivity between NR and LTE (NE-DC: NR-E-UTRA Dual Connectivity) in which an NR base station (gNB) is the MN and an LTE (E-UTRA) base station (eNB) is the SN.

[0156] The wireless communication system 1 includes a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged within the macrocell C1 and form small cells C2 that are narrower than the macrocell C1. User terminals 20 are arranged in the macrocell C1 and each small cell C2. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure.

[0157] The user terminal 20 can be connected to both the base station 11 and the base station 12. It is assumed that the user terminal 20 uses the macro cell C1 and the small cell C2 simultaneously using CA or DC. The user terminal 20 may also apply CA or DC using multiple cells (CCs) (for example, five or fewer CCs, six or more CCs).

[0158] Communication between the user terminal 20 and the base station 11 can be performed using a carrier (also called an existing carrier, legacy carrier, etc.) with a relatively low frequency band (e.g., 2 GHz) and narrow bandwidth. On the other hand, a carrier with a relatively high frequency band (e.g., 3.5 GHz, 5 GHz, etc.) and wide bandwidth may be used between the user terminal 20 and the base station 12, or the same carrier as between the user terminal 20 and the base station 11 may be used. Note that the configuration of the frequency bands used by each base station is not limited to this.

[0159] Furthermore, the user terminal 20 can communicate in each cell using time division duplex (TDD) and / or frequency division duplex (FDD). Furthermore, a single numerology may be applied in each cell (carrier), or multiple different numerologies may be applied.

[0160] Numerology may be a communication parameter applied to the transmission and / or reception of a signal and / or channel, and may refer to at least one of, for example, subcarrier spacing, bandwidth, symbol length, cyclic prefix length, subframe length, TTI length, number of symbols per TTI, radio frame structure, a particular filtering operation performed by the transceiver in the frequency domain, a particular windowing operation performed by the transceiver in the time domain, etc.

[0161] For example, for a given physical channel, if the subcarrier spacing of constituent OFDM symbols is different and / or if the number of OFDM symbols is different, the numerologies may be said to be different.

[0162] The base station 11 and the base station 12 (or the two base stations 12) may be connected by wire (for example, optical fiber conforming to CPRI (Common Public Radio Interface), X2 interface, etc.) or wirelessly.

[0163] The base station 11 and each base station 12 are connected to a higher station device 30, and are connected to a core network 40 via the higher station device 30. The higher station device 30 includes, but is not limited to, an access gateway device, a radio network controller (RNC), a mobility management entity (MME), and the like. Each base station 12 may be connected to the higher station device 30 via the base station 11.

[0164] The base station 11 is a base station having a relatively wide coverage, and may be called a macro base station, an aggregation node, an eNB (eNodeB), a transmission / reception point, etc. The base station 12 is a base station having a local coverage, and may be called a small base station, a micro base station, a pico base station, a femto base station, a HeNB (Home eNodeB), an RRH (Remote Radio Head), a transmission / reception point, etc. Hereinafter, when the base stations 11 and 12 are not distinguished from each other, they are collectively called the base station 10.

[0165] Each user terminal 20 is a terminal compatible with various communication methods such as LTE and LTE-A, and may include not only a mobile communication terminal (mobile station) but also a fixed communication terminal (fixed station).

[0166] In the wireless communication system 1, as a wireless access scheme, Orthogonal Frequency Division Multiple Access (OFDMA) is applied to the downlink, and Single Carrier Frequency Division Multiple Access (SC-FDMA) and / or OFDMA is applied to the uplink.

[0167] OFDMA is a multi-carrier transmission method that divides a frequency band into multiple narrow frequency bands (subcarriers) and maps data to each subcarrier for communication. SC-FDMA is a single-carrier transmission method that divides the system bandwidth into bands consisting of one or consecutive resource blocks for each terminal, and reduces interference between terminals by having multiple terminals use different bands. Note that the uplink and downlink wireless access methods are not limited to the combination of these, and other wireless access methods may be used.

[0168] In the wireless communication system 1, a downlink shared channel (PDSCH: Physical Downlink Shared Channel) shared by each user terminal 20, a broadcast channel (PBCH: Physical Broadcast Channel), a downlink L1 / L2 control channel, etc. are used as downlink channels. User data, upper layer control information, SIB (System Information Block), etc. are transmitted by the PDSCH. Furthermore, MIB (Master Information Block) is transmitted by the PBCH.

[0169] The downlink L1 / L2 control channel includes at least one of a downlink control channel (PDCCH (Physical Downlink Control Channel) and / or EPDCCH (Enhanced Physical Downlink Control Channel)), PCFICH (Physical Control Format Indicator Channel), and PHICH (Physical Hybrid-ARQ Indicator Channel). Downlink control information (DCI: Downlink Control Information) including scheduling information of PDSCH and / or PUSCH, etc. are transmitted by the PDCCH.

[0170] Note that scheduling information may be notified by DCI. For example, DCI for scheduling DL data reception may be called DL assignment, and DCI for scheduling UL data transmission may be called UL grant.

[0171] The number of OFDM symbols used for the PDCCH is transmitted by the PCFICH. The PHICH transmits delivery confirmation information (e.g., retransmission control information, also called HARQ-ACK, ACK / NACK, etc.) of the HARQ (Hybrid Automatic Repeat reQuest) for the PUSCH. The EPDCCH is frequency division multiplexed with the PDSCH (Downlink Shared Data Channel) and is used for transmitting DCI, etc., like the PDCCH.

[0172] In the wireless communication system 1, as uplink channels, an uplink shared channel (PUSCH: Physical Uplink Shared Channel) shared by each user terminal 20, an uplink control channel (PUCCH: Physical Uplink Control Channel), a random access channel (PRACH: Physical Random Access Channel), etc. are used. The PUSCH transmits user data, higher layer control information, etc. Furthermore, the PUCCH transmits downlink radio link quality information (CQI: Channel Quality Indicator), delivery acknowledgement information, scheduling request (SR: Scheduling Request), etc. The PRACH transmits a random access preamble for establishing a connection with a cell.

[0173] In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), etc. are transmitted as downlink reference signals. In addition, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. are transmitted as uplink reference signals. Note that the DMRS may be called a user equipment specific reference signal (UE-specific Reference Signal). In addition, the reference signals to be transmitted are not limited to these.

[0174] <Base station> 5 is a diagram showing an example of the overall configuration of a base station according to an embodiment. The base station 10 includes a plurality of transmitting / receiving antennas 101, an amplifier unit 102, a transmitting / receiving unit 103, a baseband signal processing unit 104, a call processing unit 105, and a transmission path interface 106. Note that the base station 10 may be configured to include one or more of each of the transmitting / receiving antennas 101, the amplifier unit 102, and the transmitting / receiving unit 103.

[0175] User data to be transmitted from the base station 10 to the user terminal 20 on the downlink is input from the higher-level station device 30 to the baseband signal processing unit 104 via the transmission path interface 106 .

[0176] In the baseband signal processing unit 104, transmission processes such as Packet Data Convergence Protocol (PDCP) layer processing, user data division and joining, Radio Link Control (RLC) layer transmission processes such as RLC retransmission control, Medium Access Control (MAC) retransmission control (e.g., HARQ transmission process), scheduling, transmission format selection, channel coding, Inverse Fast Fourier Transform (IFFT) processing, and precoding processing are performed on the user data, and the data is transferred to the transceiver unit 103. In addition, transmission processes such as channel coding and inverse fast Fourier transform are also performed on the downlink control signal, and the data is transferred to the transceiver unit 103.

[0177] The transmitting / receiving unit 103 converts the baseband signal output from the baseband signal processing unit 104 after precoding for each antenna into a radio frequency band and transmits the converted signal. The radio frequency signal frequency-converted by the transmitting / receiving unit 103 is amplified by the amplifier unit 102 and transmitted from the transmitting / receiving antenna 101. The transmitting / receiving unit 103 can be configured from a transmitter / receiver, a transmitting / receiving circuit, or a transmitting / receiving device that are explained based on a common understanding in the technical field to which the present disclosure relates. Note that the transmitting / receiving unit 103 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit.

[0178] On the other hand, for an uplink signal, a radio frequency signal received by the transmitting / receiving antenna 101 is amplified by the amplifier unit 102. The transmitting / receiving unit 103 receives the uplink signal amplified by the amplifier unit 102. The transmitting / receiving unit 103 frequency-converts the received signal to a baseband signal and outputs the signal to the baseband signal processing unit 104.

[0179] The baseband signal processing unit 104 performs Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing, error correction decoding, MAC retransmission control reception processing, and RLC layer and PDCP layer reception processing on the user data included in the input uplink signal, and transfers the data to the higher level station device 30 via a transmission path interface 106. The call processing unit 105 performs call processing (setting, releasing, etc.) of communication channels, status management of the base station 10, management of wireless resources, etc.

[0180] The transmission line interface 106 transmits and receives signals to and from the higher-level station device 30 via a predetermined interface. The transmission line interface 106 may also transmit and receive signals (backhaul signaling) to and from other base stations 10 via an inter-base station interface (for example, an optical fiber conforming to CPRI (Common Public Radio Interface), an X2 interface).

[0181] The transmitting / receiving unit 103 may further include an analog beam forming unit that performs analog beam forming. The analog beam forming unit may be configured with an analog beam forming circuit (e.g., a phase shifter, a phase shift circuit) or an analog beam forming device (e.g., a phase shifter) that is explained based on a common understanding in the technical field to which the present disclosure relates. The transmitting / receiving antenna 101 may be configured with, for example, an array antenna. The transmitting / receiving unit 103 may be configured to be able to apply single BF, multi BF, etc.

[0182] The transceiver 103 may transmit a signal using a transmission beam and may receive a signal using a reception beam. The transceiver 103 may transmit and / or receive a signal using a predetermined beam determined by the control unit 301.

[0183] The transmitting / receiving unit 103 may receive from the user terminal 20 and / or transmit to the user terminal 20 various pieces of information described in the above embodiments.

[0184] For example, the transceiver 103 receives a UL signal or channel transmitted using at least one of a first modulation and coding scheme (MCS) table and a second MCS table in which a coding rate lower than the minimum coding rate defined in the first MCS table is defined. The transceiver 103 may also transmit downlink control information including information on the MCS table.

[0185] 6 is a diagram showing an example of a functional configuration of a base station according to an embodiment. Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication.

[0186] The baseband signal processing unit 104 includes at least a control unit (scheduler) 301, a transmission signal generating unit 302, a mapping unit 303, a reception signal processing unit 304, and a measurement unit 305. Note that these components only need to be included in the base station 10, and some or all of the components do not necessarily need to be included in the baseband signal processing unit 104.

[0187] The control unit (scheduler) 301 performs overall control of the base station 10. The control unit 301 can be configured from a controller, a control circuit, or a control device that is described based on common understanding in the technical field to which the present disclosure relates.

[0188] The control unit 301 controls, for example, signal generation in the transmission signal generation unit 302, signal allocation in the mapping unit 303, etc. The control unit 301 also controls signal reception processing in the reception signal processing unit 304, signal measurement in the measurement unit 305, etc.

[0189] The control unit 301 controls the scheduling (e.g., resource allocation) of system information, downlink data signals (e.g., signals transmitted on PDSCH), and downlink control signals (e.g., signals transmitted on PDCCH and / or EPDCCH, such as delivery acknowledgement information). In addition, the control unit 301 controls the generation of downlink control signals, downlink data signals, etc., based on the result of determining whether or not retransmission control is required for uplink data signals.

[0190] The control unit 301 controls the scheduling of synchronization signals (for example, PSS / SSS), downlink reference signals (for example, CRS, CSI-RS, DMRS), and the like.

[0191] The control unit 301 may control the formation of a transmission beam and / or a reception beam using a digital BF (e.g., precoding) by the baseband signal processing unit 104 and / or an analog BF (e.g., phase rotation) by the transceiver unit 103.

[0192] The control unit 301 controls the transmission or reception operations shown in the first to sixth aspects separately for each communication service type (or MCS table type, RNTI type, resource type to be set, etc.). For example, different upper layer parameters may be set for each communication service type.

[0193] The transmission signal generating unit 302 generates downlink signals (downlink control signals, downlink data signals, downlink reference signals, etc.) based on instructions from the control unit 301, and outputs the generated downlink signals to the mapping unit 303. The transmission signal generating unit 302 can be configured from a signal generator, a signal generating circuit, or a signal generating device described based on common understanding in the technical field related to the present disclosure.

[0194] The transmission signal generating unit 302 generates a DL assignment for notifying allocation information of downlink data and / or a UL grant for notifying allocation information of uplink data, for example, based on an instruction from the control unit 301. Both the DL assignment and the UL grant are DCI and follow the DCI format. In addition, the downlink data signal is subjected to coding processing, modulation processing, etc. according to a coding rate, a modulation method, etc. determined based on channel state information (CSI) from each user terminal 20, etc.

[0195] The mapping unit 303 maps the downlink signal generated by the transmission signal generating unit 302 to a predetermined radio resource based on an instruction from the control unit 301, and outputs the mapped signal to the transmitting / receiving unit 103. The mapping unit 303 can be configured from a mapper, a mapping circuit, or a mapping device described based on a common understanding in the technical field related to the present disclosure.

[0196] The received signal processing unit 304 performs reception processing (e.g., demapping, demodulation, decoding, etc.) on the received signal input from the transmitting / receiving unit 103. Here, the received signal is, for example, an uplink signal (uplink control signal, uplink data signal, uplink reference signal, etc.) transmitted from the user terminal 20. The received signal processing unit 304 can be configured with a signal processor, a signal processing circuit, or a signal processing device described based on common understanding in the technical field related to the present disclosure.

[0197] The received signal processing unit 304 outputs information decoded by the receiving process to the control unit 301. For example, when a PUCCH including an HARQ-ACK is received, the received signal processing unit 304 outputs the HARQ-ACK to the control unit 301. In addition, the received signal processing unit 304 outputs the received signal and / or the signal after the receiving process to the measurement unit 305.

[0198] The measurement unit 305 performs measurements on the received signal. The measurement unit 305 can be configured with a measurement instrument, a measurement circuit, or a measurement device described based on common understanding in the technical field to which the present disclosure relates.

[0199] For example, the measurement unit 305 may perform RRM (Radio Resource Management) measurement, CSI (Channel State Information) measurement, etc., based on the received signal. The measurement unit 305 may measure received power (e.g., RSRP (Reference Signal Received Power)), received quality (e.g., RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio), SNR (Signal to Noise Ratio)), signal strength (e.g., RSSI (Received Signal Strength Indicator)), propagation path information (e.g., CSI), etc. The measurement result may be output to the control unit 301.

[0200] <User device> 7 is a diagram showing an example of the overall configuration of a user terminal according to an embodiment. The user terminal 20 includes a plurality of transmitting / receiving antennas 201, an amplifier unit 202, a transmitting / receiving unit 203, a baseband signal processing unit 204, and an application unit 205. Note that the user terminal 20 may be configured to include one or more of each of the transmitting / receiving antennas 201, the amplifier unit 202, and the transmitting / receiving unit 203.

[0201] The radio frequency signal received by the transmitting / receiving antenna 201 is amplified by the amplifier unit 202. The transmitting / receiving unit 203 receives the downlink signal amplified by the amplifier unit 202. The transmitting / receiving unit 203 frequency-converts the received signal to a baseband signal and outputs the signal to the baseband signal processing unit 204. The transmitting / receiving unit 203 can be configured from a transmitter / receiver, a transmitting / receiving circuit, or a transmitting / receiving device that are explained based on a common understanding in the technical field to which the present disclosure relates. Note that the transmitting / receiving unit 203 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit.

[0202] The baseband signal processing unit 204 performs FFT processing, error correction decoding, retransmission control reception processing, etc. on the input baseband signal. Downlink user data is transferred to the application unit 205. The application unit 205 performs processing related to layers higher than the physical layer and the MAC layer, etc. Among the downlink data, broadcast information may also be transferred to the application unit 205.

[0203] On the other hand, uplink user data is input from the application unit 205 to the baseband signal processing unit 204. The baseband signal processing unit 204 performs transmission processing for retransmission control (for example, transmission processing for HARQ), channel coding, precoding, Discrete Fourier Transform (DFT) processing, IFFT processing, and the like, and transfers the data to the transceiver unit 203.

[0204] The transmitting / receiving unit 203 converts the baseband signal output from the baseband signal processing unit 204 into a radio frequency band and transmits it. The radio frequency signal frequency-converted by the transmitting / receiving unit 203 is amplified by the amplifier unit 202 and transmitted from the transmitting / receiving antenna 201.

[0205] The transmitting / receiving unit 203 may further include an analog beam forming unit that performs analog beam forming. The analog beam forming unit may be configured with an analog beam forming circuit (e.g., a phase shifter, a phase shift circuit) or an analog beam forming device (e.g., a phase shifter) that is explained based on a common understanding in the technical field related to the present disclosure. The transmitting / receiving antenna 201 may be configured with, for example, an array antenna. The transmitting / receiving unit 203 may be configured to be able to apply single BF, multi-BF, etc.

[0206] The transceiver 203 performs UL transmission or DL ​​reception using at least one of a first modulation and coding scheme (MCS) table and a second MCS table in which a coding rate lower than the minimum coding rate defined in the first MCS table is defined.

[0207] 8 is a diagram showing an example of a functional configuration of a user terminal according to an embodiment. Note that in this example, functional blocks of the characteristic parts of the embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication.

[0208] The baseband signal processing unit 204 of the user terminal 20 includes at least a control unit 401, a transmission signal generating unit 402, a mapping unit 403, a reception signal processing unit 404, and a measurement unit 405. Note that these components only need to be included in the user terminal 20, and some or all of the components do not necessarily need to be included in the baseband signal processing unit 204.

[0209] The control unit 401 performs overall control of the user terminal 20. The control unit 401 can be configured from a controller, a control circuit, or a control device that is described based on common understanding in the technical field to which the present disclosure relates.

[0210] The control unit 401 controls, for example, signal generation in the transmission signal generation unit 402, signal allocation in the mapping unit 403, etc. The control unit 401 also controls signal reception processing in the reception signal processing unit 404, signal measurement in the measurement unit 405, etc.

[0211] The control unit 401 acquires the downlink control signal and the downlink data signal transmitted from the base station 10 from the received signal processing unit 404. The control unit 401 controls the generation of the uplink control signal and / or the uplink data signal based on the result of judging whether or not retransmission control is required for the downlink control signal and / or the downlink data signal.

[0212] The control unit 401 may control the formation of a transmission beam and / or a reception beam using a digital BF (e.g., precoding) by the baseband signal processing unit 204 and / or an analog BF (e.g., phase rotation) by the transceiver unit 203.

[0213] Furthermore, control unit 401 separately controls the transmission conditions / parameters for UL transmission and the reception conditions / parameters for DL ​​reception according to the type of MCS table to be applied.

[0214] For example, the control unit 401 may separately control the accumulation of transmission power control commands depending on the type of the applied MCS table. Also, the control unit 401 may separately generate codebooks used for transmitting acknowledgement signals depending on the type of the applied MCS table. Also, the control unit 401 may separately control the arrangement of reference signals depending on the type of the applied MCS table. Also, the control unit 401 may control the selection of resources for the uplink control channel depending on the type of the applied MCS table. Also, the control unit 401 may separately control the number of repetitions of UL transmission depending on the type of the applied MCS table.

[0215] Furthermore, the control unit 401 controls the transmission or reception operations shown in the above first to sixth aspects separately for each communication service type (or MCS table type, RNTI type, resource type to be set, etc.). For example, conditions set by different upper layer parameters for each communication service type may be applied.

[0216] The transmission signal generating unit 402 generates uplink signals (uplink control signals, uplink data signals, uplink reference signals, etc.) based on instructions from the control unit 401, and outputs the signals to the mapping unit 403. The transmission signal generating unit 402 can be configured from a signal generator, a signal generating circuit, or a signal generating device that is described based on common understanding in the technical field related to the present disclosure.

[0217] The transmission signal generating unit 402 generates uplink control signals related to acknowledgement information, channel state information (CSI), etc., based on, for example, an instruction from the control unit 401. The transmission signal generating unit 402 also generates uplink data signals based on an instruction from the control unit 401. For example, when a downlink control signal notified from the base station 10 includes an UL grant, the transmission signal generating unit 402 is instructed by the control unit 401 to generate an uplink data signal.

[0218] The mapping unit 403 maps the uplink signal generated by the transmission signal generating unit 402 to a radio resource based on an instruction from the control unit 401, and outputs the result to the transceiver unit 203. The mapping unit 403 can be configured from a mapper, a mapping circuit, or a mapping device that is described based on common understanding in the technical field related to the present disclosure.

[0219] The received signal processing unit 404 performs reception processing (e.g., demapping, demodulation, decoding, etc.) on the received signal input from the transmitting / receiving unit 203. Here, the received signal is, for example, a downlink signal (downlink control signal, downlink data signal, downlink reference signal, etc.) transmitted from the base station 10. The received signal processing unit 404 can be configured from a signal processor, a signal processing circuit, or a signal processing device described based on common understanding in the technical field related to the present disclosure. Also, the received signal processing unit 404 can configure a receiving unit related to the present disclosure.

[0220] The received signal processing unit 404 outputs information decoded by the receiving process to the control unit 401. The received signal processing unit 404 outputs, for example, broadcast information, system information, RRC signaling, DCI, and the like to the control unit 401. In addition, the received signal processing unit 404 outputs the received signal and / or the signal after the receiving process to the measurement unit 405.

[0221] The measurement unit 405 performs measurements on the received signal. The measurement unit 405 can be configured with a measurement instrument, a measurement circuit, or a measurement device described based on common understanding in the technical field to which the present disclosure relates.

[0222] For example, the measurement unit 405 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measurement unit 405 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 401. The transmission / reception unit 203 may transmit BFRQ, PBFRQ, etc. to the base station 10.

[0223] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0224] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function may be called a transmitting unit / section, a transmitter, etc. In either case, as described above, the implementation method is not particularly limited.

[0225] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 9 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0226] In the following description, the term "apparatus" may be replaced with a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0227] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

[0228] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0229] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned baseband signal processing unit 104 (204), call processing unit 105, etc. may be realized by the processor 1001.

[0230] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 401 of the user terminal 20 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and other functional blocks may be realized in a similar manner.

[0231] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

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

[0233] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission / reception antenna 101 (201), amplifier unit 102 (202), transmission / reception unit 103 (203), transmission line interface 106, etc. may be realized by the communication device 1004. The transmission / reception unit 103 may be implemented as a transmission unit 103a and a reception unit 103b that are physically or logically separated.

[0234] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED (Light Emitting Diode) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one (e.g., a touch panel).

[0235] 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 configured using a single bus, or may be configured using different buses between each device.

[0236] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0237] (Modification) In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Also, the signal may be a message. The reference signal may be abbreviated as RS (Reference Signal) and may be called a pilot, pilot signal, etc. depending on the applied standard. Also, the component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0238] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0239] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The numerology may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0240] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. Also, a slot may be a time unit based on numerology.

[0241] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0242] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be read as interchangeable with each other.

[0243] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, a minislot, or the like, instead of a subframe.

[0244] Here, 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 frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0245] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0246] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0247] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0248] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0250] In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0251] Note that one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0252] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0253] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0254] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0255] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0256] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0257] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0258] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH (Physical Uplink Control Channel), PDCCH (Physical Downlink Control Channel), etc.) and information elements may be identified by any suitable names, and the various names assigned to these various channels and information elements are not limiting in any way.

[0259] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0260] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via a plurality of network nodes.

[0261] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0262] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.

[0263] The physical layer signaling may be called L1 / L2 (Layer 1 / Layer 2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc. The MAC signaling may be notified by using a MAC control element (MAC CE (Control Element)), for example.

[0264] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0265] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

[0266] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0267] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0268] As used in this disclosure, the terms "system" and "network" may be used interchangeably.

[0269] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0270] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0271] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be partitioned 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 (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0272] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0273] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0274] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0275] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0276] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0277] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. In a network including one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, an MME (Mobility Management Entity) and an S-GW (Serving-Gateway)), or a combination thereof.

[0278] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0279] Each aspect / embodiment described in the present disclosure may be applied to a system using LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (registered trademark) (Global System for Mobile communications), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable wireless communication method, or a next-generation system extended based on these. In addition, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0280] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0281] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0282] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, and the like.

[0283] A "determining" may also be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

[0284] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0285] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

[0286] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0287] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

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

[0289] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0290] In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0291] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiving unit for receiving downlink control information (DCI) for scheduling uplink (UL) transmissions and / or downlink (DL) receptions corresponding to different services, the DCI including a modulation and coding scheme (MCS) field; A control unit that generates a delivery acknowledgement signal (HARQ-ACK) codebook for the DL reception separately for each HARQ-ACK transmission corresponding to the different services based on the DCI, The control unit controls the transmission power for each UL transmission corresponding to the different services based on a value of a specific field in the DCI relating to the transmission power of the UL transmission corresponding to the different services.

2. The terminal according to claim 1, characterized in that the control unit controls a demodulation reference signal (DMRS) configuration to be applied to at least one of the UL transmission and the DL reception corresponding to the different services separately for each UL transmission or each DL reception.

3. The terminal according to claim 1 , wherein the control unit separately controls configuration of physical uplink control channel (PUCCH) resources corresponding to the different services.

4. The terminal according to claim 1, characterized in that the control unit controls the number of repetitions applied to at least one of the UL transmission and the DL reception corresponding to the different services separately for each UL transmission or each DL reception.

5. The terminal according to claim 1 , characterized in that at least one of the different services corresponds to highly reliable and low latency communication (URLLC).

6. receiving downlink control information (DCI) scheduling uplink (UL) transmissions and / or downlink (DL) receptions corresponding to different services, the DCI including a modulation and coding scheme (MCS) field; generating a delivery acknowledgement signal (HARQ-ACK) codebook for the DL reception separately for each HARQ-ACK transmission corresponding to the different services based on the DCI; A wireless communication method for a terminal, comprising: a step of controlling a transmission power for each UL transmission corresponding to the different service based on a value of a specific field in the DCI relating to the transmission power of the UL transmission corresponding to the different service.

7. a transmitter for transmitting downlink control information (DCI) for scheduling uplink (UL) transmissions and / or downlink (DL) receptions corresponding to different services, the DCI including a modulation and coding scheme (MCS) field; A control unit that sets a delivery acknowledgement signal (HARQ-ACK) codebook for the DL reception separately for each HARQ-ACK transmission corresponding to the different services by the DCI, The base station is characterized in that the control unit controls the transmission power for each UL transmission corresponding to the different services using the value of the specific field in the DCI regarding the transmission power of the UL transmission corresponding to the different services.

8. A system having a terminal and a base station, The terminal includes a receiving unit for receiving downlink control information (DCI) for scheduling at least one of uplink (UL) transmission and downlink (DL) reception corresponding to different services, the DCI including a modulation and coding scheme (MCS) field; A control unit that generates a delivery acknowledgement signal (HARQ-ACK) codebook for the DL reception separately for each HARQ-ACK transmission corresponding to the different services based on the DCI, The control unit of the terminal controls a transmission power for each of the UL transmissions corresponding to the different services based on a value of a specific field in the DCI related to a transmission power of the UL transmission corresponding to the different services; The base station includes a transmitter for transmitting the DCI; A control unit that sets the HARQ-ACK codebook separately for each HARQ-ACK transmission by the DCI, The system is characterized in that the control unit of the base station controls the transmission power for each UL transmission corresponding to the different services using the value of the specific field in the DCI regarding the transmission power of the UL transmission corresponding to the different services.

Citation Information

Patent Citations

  • Method and radio node for enabling use of higher order modulation in wireless communication with user equipment

    JP2016535521A

  • Interference cancellation and suppression for multiuser multiple-input / multiple-output (mimo) communications

    JP2017539127A