RU2784380C2 - Terminal and transmission method - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: communication terminal receives from a base station data of a control channel used for information transmission for assignment of an uplink signal. The control channel does not contain a field of SRS resource indicator (SRI) and does not indicate in a clear way a service type and a power control parameter. The terminal calculates transmission power, using the power control parameter, which is dynamically configured based on a given condition related to the control channel, and transmits the uplink signal, using calculated transmission power.

EFFECT: possibility of configuration of transmission power of an uplink channel without clear indication of a set of parameters of power control with a control channel.

32 cl, 16 dwg

Description

Technical field

The present invention relates to a terminal and a transmission method.

State of the art

[0002] In standardizing the 5th generation (5G) communication system, the 3rd Generation Partnership Project (3GPP) discussed a new radio access method (New Radio, NR), which is not necessarily backward compatible with the LTE/LTE-Advanced standards.

[0003] In NR, technical studies have been carried out aimed at ultra-reliable and low latency communications (URLC), which is one of the requirements of 5G. The URLLC must simultaneously satisfy the requirement of "high reliability" of a packet data error rate of 10 ^-5 or less for a packet data volume of 32 bytes (burst success rate of 99.999% or more) and "low latency" of 1 ms or less for radio interval (see, for example, non-patent literature (hereinafter referred to as NPL (Non-Patent Literature)) 1).

[0004] In order to meet the above requirements of URLLC, the possibility of transmitting, when transmitting the uplink channel (PUSCH: Physical Uplink Shared Channel (Physical Uplink Shared Channel)) URLLC data, URLLC data using high transmission power (for example, power boost) on compared to the uplink of other data (eg see NPL 2).

Link List

Non-Patent Literature

[0005]

NPL 1

3GPP Technical Report TR 38.913 Volume 14.3.0, Scenario and Requirements Studies for Next Generation Access Technologies (Edition 14) (2017-06)

NPL 2

R1-1803359, "Summary of Handling UL Multiplexing in Transmission with Different Reliability Requirements", video, February 2018

NPL 3

3GPP TS 38.213 Specification Volume 15.1.0, "NR; Physical Layer Procedures for Management (Edition 15)" (2018-03)

NPL 4

3GPP Specification TS 38.212 Volume 15.1.1, "NR; Channel Multiplexing and Coding (Edition 15)" (2018-04)

NPL 5

R1-1805630, "Brief description of section "7.2.2. Study on the Need for a New DCI Format", Huawei, April 2018

NPL 6

3GPP Specification TS 38.214 Volume 15.2.0, "NR; Physical Layer Procedures for Data (Edition 15)" (2018-06)

Disclosure of the essence of the invention

[0006] However, the transmission method of PUSCH URLLC has not yet been fully explored.

[0007] The non-limiting examples of the present invention contribute to providing a terminal and a transmission method that can transmit an uplink signal in an appropriate manner.

[0008] A terminal according to one example of the present invention comprises: a circuit that, during operation, configures a first power control parameter corresponding to a first service when a predetermined condition related to a control channel used in transmitting uplink assignment information is satisfied, and configures a second power control parameter corresponding to the second service when the predetermined condition is not satisfied; and a transmission scheme that, in operation, transmits the uplink signal using the transmission power calculated using the first power control parameter or the second power control parameter.

[0009] A transmission method according to one example of the present invention includes: configuring a first power control parameter corresponding to a first service when a predetermined condition related to a control channel used in transmitting uplink assignment information is satisfied, and configuring a second control parameter the power corresponding to the second service when the predetermined condition is not satisfied; and transmitting the uplink signal using the transmit power calculated using the first power control parameter or the second power control parameter.

[0010] It should be noted that these general or specific aspects may be implemented as a system, device, method, integrated circuit, computer program, storage medium, or any selective combination thereof.

[0011] According to one example of the present invention, an uplink signal can be properly transmitted.

[0012] Additional benefits and advantages of one general example of the present invention will become apparent from the description and drawings. Benefits and/or advantages may be separately obtained using the various embodiments and features presented in the description and drawings, which need not be provided all in order to obtain one or more of such benefits and/or advantages.

Brief description of the drawings

[0013]

On FIG. 1 is a diagram showing an example of a PC parameter set.

On FIG. 2 is a block diagram showing a configuration example of a terminal part according to Embodiment 1 of the invention.

On FIG. 3 is a block diagram showing a configuration example of a terminal according to Embodiment 1 of the invention.

On FIG. 4 is a block diagram showing a configuration example of a base station according to Embodiment 1 of the invention.

On FIG. 5 is a flowchart showing exemplary operations of a terminal and a base station according to Embodiment 1 of the invention.

On FIG. 6 is a diagram showing a configuration example of PC parameter set numbers A and B according to Embodiment 1 of the invention.

On FIG. 7A is a diagram showing an example of an MCS table for URLLC.

On FIG. 7B is a diagram showing an example of an eMBV MCS table.

On FIG. 7C is a diagram showing another example of an eMBV MCS table.

On FIG. 8 is a diagram showing a configuration example of PC parameter set numbers A and B according to Embodiment 1 of the invention.

On FIG. 9 is a diagram showing an example in which a radio resource is overlapped between URLLC and eMBV according to Embodiment 1 of the invention.

On FIG. 10 is a block diagram showing a configuration example of a terminal according to Embodiment 2 of the invention.

On FIG. 11 is a diagram showing a configuration example of PC parameter set numbers according to Embodiment 2 of the invention.

On FIG. 12 is a diagram showing another configuration example of PC parameter set numbers according to Embodiment 2 of the invention.

On FIG. 13 is a diagram showing another configuration example of PC parameter set numbers according to Embodiment 2 of the invention.

On FIG. 14 is a block diagram showing a configuration example of a terminal according to Embodiment 3 of the invention.

Implementation of the invention

[0014] The following describes in detail the embodiments of the present invention with reference to the accompanying drawings.

[0015] Transmission power control (TPC) PUSCH in the terminal (sometimes called the user equipment (User Equipment, UE)) for NR is performed, for example, in accordance with the following Equation 1 (see, for example, NPL 3) .

[one]

[0016] In Equation 1, P _PUSCH,f,c (i, j, qd, l) is the PUSCH transmit power [dBm] at carrier number "f", serving cell number "c", slot number "i", power control parameter set number "j" (power control, PC), reference signal (reference signal, RS) number "q _d " pathloss estimation (PL), and closed loop processing number "l"; P _CMAX,f,c (i) is the maximum transmit power [dBm] of the terminal at slot number i; P _{O_PUSCH,f,c} (j) is the target receive power [dBm] (parameter value) at PC parameter set number j; 2 ^μ ⋅M _RB,f,c ^PUSCH (i) is the PUSCH bandwidth [PRB] obtained by subcarrier spacing (SCS) normalization applied to PUSCH, with slot number i with SCS reference 15 kHz; α _f,c (j) is a weighting factor (parameter value) indicating the degree of compensation of the bandwidth loss at the number j of the PC parameter set; PL _f,c (q _d ) is the bandwidth loss [dB] measured by the terminal from RS at RS number q _d ; Δ _TF,f,c (i) is the offset [dB] depending on the modulation and coding scheme (MCS) of the transmitted data at slot number i; and f _f,c (i, l) is the amount of the closed loop data processing correction [dB] at the slot number i and the closed loop data process number l.

[0017] In Equation 1, P _{O_PUSCH,f,c} (j) and α _f,c (j) are called "PC parameter set". For example, as shown in FIG. 1, PC parameter set values for each PC parameter set number j are configured in advance from the base station (sometimes referred to as "eNB" or "gNB") to the terminal, for example, by specifying radio resource control (RRC).

[0018] The use, in URLLC upstream data transmission, of a set of PC parameters (P _{O_PUSCH,f,c} (j) and α _f,c (j)) corresponding to high transmission power compared to other types of service (e.g. eMBW ) to meet URLLC reliability requirements. For example, the possibility of transmitting URLLC data with high transmission power compared to eMBV data has been studied by applying power boost to the URLLC data.

[0019] PUSCH scheduling information (e.g., frequency resource allocation information, time resource allocation information or MCS, etc.) is called downlink control information (DCI) and is transmitted from the base station to the terminal using a physical downlink control channel (PDCCH). In addition, the PDCCH used to indicate PUSCH scheduling information is called "uplink grant (UL grant)".

[0020] In NR, two types of DCI format, "DCI format 0_0" and "DCI format 0_1", are defined as DCI format for UL permission (see, for example, NPL 4). The DCI 0_0 format is also referred to as the DCI "fallback" format. Because DCI format 0_0 does not include some of the information included in DCI format 0_1, DCI format 0_0 has a small payload size compared to DCI format 0_1.

[0021] In addition, a PDCCH (eg, UL grant) indicating scheduling information of URLLC data (sometimes referred to as PUSCH for URLLC) should also have high reliability and low latency that are equivalent to or better than the reliability and latency of URLLC data. Here, the smaller the payload size, the higher the coding efficiency becomes, thus improving the reliability. As such, the use of a DCI fallback format (eg, DCI format 0_0) in a DCI PDCCH format indicating URLLC data scheduling information has been studied (see, for example, NPL 5).

[0022] For example, DCI format 0_1 includes an SRS resource indicator (SRI) field. When using the DCI format 0_1 in the UL permission DCI format, you can specify the parameter set number j of the PC terminal using the SRI field. Therefore, the base station may indicate the URLLC PUSCH boost transmission to the terminal using the DCI 0_1 format. In other words, the base station can use the SRI field included in the DCI format 0_1 to explicitly indicate to the terminal the PC parameter set number j corresponding to the PC parameter set (P _{O_PUSCH,f,c} (j) and α _f,c (j)), appropriate for the PUSCH transmit power for URLLC.

[0023] On the other hand, the DCI fallback format (eg, DCI format 0_0) does not include an SRI field. When the SRI field is not included, that is, when a UL permission is used that does not include information explicitly indicating a PC parameter set number, for example, a fixed value of the PC parameter set (for example, a PC parameter set value j=0) is used.

[0024] In this case, since the fixed value of the PC parameter set is applied to the terminal regardless of the service type (also called traffic type) such as URLLC and eMBB, for example, the uplink transmission power suitable for the service type cannot be configured. For example, when the parameter value for eMBW is set to a fixed value of the PC parameter set, URLLC data scheduling will result in a lack of transmission power, and URLLC quality requirements cannot be satisfied. On the other hand, when the parameter value for URLLC is set to a fixed value of the PC parameter set, eMBV data scheduling will result in excessive transmission power, resulting in increased interference and fears of degrading system performance.

[0025] As described above, the method of indicating to the terminal to increase the PUSCH power for URLLC in a UL grant not including information that explicitly indicates, for example, a PC parameter set number, has not been fully discussed.

[0026] Therefore, in one example of the present invention, a method for properly configuring the transmission power of an uplink channel suitable for a type of service such as URLLC and eMBB, for example, will be described.

[0027] [Embodiment 1]

[Communication System Overview]

A communication system according to an embodiment of the present invention includes a terminal 100 and a base station 200. The terminal 100 transmits a PUSCH using a given transmit power based on the DCI included in the UL grant from the base station 200. The base station 200 transmits the UL grant to the terminal 100 and receives PUSCH from terminal 100.

[0028] FIG. 2 is a block diagram showing the configuration of a portion of a terminal 100 according to an embodiment of the present invention. In terminal 100 shown in FIG. 2, the PC parameter controller 104 configures the first power control parameter corresponding to the first service (eg, URLLC) when a predetermined condition related to the control channel (eg, UL grant) used in transmitting the uplink assignment is satisfied, and configures the second power control parameter. , corresponding to the second service (eg, eMBV) when the specified condition is not satisfied. The transmitter 109 transmits the uplink signal using the transmit power calculated using the first power control parameter or the second power control parameter.

[0029] [Terminal Configuration 100]

FIG. 3 is a block diagram showing a configuration example of a terminal 100 according to the present embodiment.

[0030] The terminal 100 shown in FIG. 3 includes an antenna 101, a receiver 102, a demodulator/decoder 103, a PC parameter controller 104, a transmit power calculator 105, a data generator 106, an encoder/modulator 107, a resource allocator 108, and a transmitter 109.

[0031] The receiver 102 receives, through the antenna 101, a signal transmitted from the base station 200, performs reception processing such as down-conversion or analog-to-digital conversion (ADC) of the received signal, and outputs the received signal after the reception processing to the demodulator/decoder 103 .

[0032] The demodulator/decoder 103 demodulates and decodes the received signal input from the receiver 102, extracts (receives) the UL grant (PDCCH or NR-PDCCH) addressed to the terminal 100 from the decoding results, and decodes the PUSCH scheduling DCI included in the extracted UL approval. The demodulator/decoder 103 outputs the decoded DCI to the PC parameter controller 104, the transmit power calculator 105, the encoder/modulator 107, and the resource allocator 108 .

[0033] The DCI includes, for example, frequency resource information, time resource information, MCS, transmission power information, payload size, DCI scrambling sequence, retransmission control information, TPC command information, and the like. Here, the UL grant transmitted from the base station 200 to the terminal 100 uses a DCI format having a small payload size. A DCI format having a small payload size may be a DCI format having a payload size equal to or smaller than the DCI format 0_0 size, for example. In other words, the UL grant transmitted from the base station 200 to the terminal 100 does not contain information explicitly indicating the number j of the PC parameter set.

[0034] It should be noted that the DCIs including all parts of the control information need not be indicated to the terminal 100 at the same time. For example, some DCI may be indicated to terminal 100 as general cell information or as quasi-static indication information. In addition, some DCI is defined in the specifications, such as general system information, and may not be indicated from base station 200 to terminal 100.

[0035] The PC parameter controller 104 determines the PC parameter set number j applied to the scheduled PUSCH using the DCI input from the demodulator/decoder 103.

The PC parameter controller 104 outputs the determined PC parameter set number to the transmit power calculator 105 .

[0036] For example, when a predetermined condition is satisfied with respect to the UL grant used in transmitting PUSCH scheduling information (assignment information), the PC parameter controller 104 determines that the PUSCH scheduled by the UL grant is the PUSCH for URLLC. When the PC parameter controller 104 determines that the PUSCH scheduled by the UL grant is the URLLC PUSCH, the PC parameter controller 104 configures the PC parameter set number j=A that corresponds to the URLLC. On the other hand, when the predetermined condition is not satisfied with respect to the UL grant, the PC parameter controller 104 determines that the PUSCH scheduled by this UL grant is a PUSCH for a service type other than URLLC. When the PC parameter controller 104 determines that the PUSCH scheduled by the UL grant is a PUSCH for a service type other than URLLC, the PC parameter controller 104 configures a PC parameter set number j=B that corresponds to a service type other than URLLC (for example, eMBV).

[0037] In addition, the PC parameter set table (see, for example, FIG. 1) is configured in advance from the base station 200 to the terminal 100. In addition, a parameter value corresponding to a transmission power value suggesting URLLC is configured in the PC parameter set, corresponding to the number j=A, and the parameter value corresponding to the transmission power value suggesting a service type other than URLLC (eg, eMBB) is configured in the PC parameter set corresponding to the number j=B. In other words, the transmit power value calculated using the PC parameter set corresponding to the number j=A is larger than the transmit power value calculated using the PC parameter set corresponding to the number j=B.

[0038] In addition, the method for selecting the PC parameter set number in the PC parameter controller 104 will be described later in detail.

[0039] The transmit power calculator 105 calculates a PUSCH transmit power value at slot number i using an updated value (control value such as +1 dB, -1 dB, etc.) of the closed loop data processing correction value included in the DCI inputted from the demodulator/decoder 103 and with the PC parameter set number j inputted from the PC parameter controller 104, for example, in accordance with Equation 1. The transmit power calculator 105 outputs the calculated PUSCH transmit power to the transmitter 109.

[0040] In addition, the transmit power calculator 105 may apply a predetermined fixed value (for example, q _d =0, l=0) when the PL evaluation number qd RS and the closed loop processing number l, which are parameters other than the slot number i and the PC parameter set number j, as shown in Equation 1, are not explicitly indicated by the PC parameter controller 104 . On the other hand, when the PL evaluation number qd RS and the closed loop processing number l are explicitly specified by the PC parameter controller 104, the transmission power calculator 105 configures the values indicated by the PC parameter controller 104 .

[0041] The data generator 106 generates data transmitted by the terminal 100 and outputs the generated transmission data to the encoder/modulator 107.

[0042] The encoder/modulator 107 encodes and modulates the transmission data input from the data generator 106 based on the DCI input from the demodulator/decoder 103, and outputs the modulated data signal to the resource allocator 108.

[0043] The resource allocator 108 assigns the modulated data signal input from the encoder/modulator 107 to a given radio resource (eg, frequency resource and time resource) based on the DCI input from the demodulator/decoder 103. The resource allocator 108 outputs the signal after the resource allocation to transmitter 109.

[0044] The transmitter 109 performs transmission processing such as digital-to-analog conversion (DAC) and upconversion for the signal input from the resource allocator 108. The transmitter 109 transmits the signal after transmission processing to the base station 200 via the antenna 101 using the transmission power value input from the transmission power calculator 105 .

[0045] [Base station configuration 200]

FIG. 4 is a block diagram showing a configuration example of a base station 200 according to the present embodiment.

[0046] The base station 200 shown in FIG. 4 includes a scheduler 201, a control information generator 202, an encoder/modulator 203, a transmitter 204, an antenna 205, a receiver 206, and a demodulator/decoder 207.

Scheduler 201 determines radio resource allocation information (eg, frequency resource allocation information, time resource allocation information, MCS, transmission power information, etc.) for the PUSCH of terminal 100. For example, scheduler 201 may determine radio resource allocation information on based on the quality information indicated from the terminal 100 at a given timing. The scheduler 201 outputs the given radio resource allocation information and the corresponding service type (eg, URLLC or eMBV) to the control information generator 202 .

[0048] The control information generator 202 generates a UL grant including the DCI indicated to the terminal 100 based on the radio resource allocation and type of service information input from the scheduler 201. The control information generator 202 outputs the generated UL grant to the encoder/modulator 203. Here, the UL grant is, for example, a DCI fallback format with a small payload size (eg, DCI format 0_0), and the UL grant does not contain information that explicitly indicates a PC parameter set number.

[0049] The encoder/modulator 203 encodes and modulates the UL grant input from the control information generator 202 and outputs the modulated UL grant to the transmitter 204.

[0050] The transmitter 204 performs transmission processing such as DAC, upconversion, and amplification of the signal input from the encoder/modulator 203, and transmits the signal after the transmission processing to the terminal 100 via the antenna 205.

[0051] The receiver 206 performs receive processing, such as downconversion or ADC, on the PUSCH transmitted from terminal 100 that was received through antenna 205, and outputs the received signal after receiving processing to demodulator/decoder 207.

[0052] The demodulator/decoder 207 demodulates and decodes the received signal input from the receiver 206 and obtains the received data from the terminal 100.

[0053] [Operation of base station and terminal 200]

The following describes in detail the operation of the terminal 100 and the base station 200 having the above-described configurations.

[0054] FIG. 5 is a flowchart showing exemplary operations of terminal 100 (FIG. 3) and base station 200 (FIG. 4).

[0055] The base station 200 determines the radio resource allocation information regarding the uplink signal (eg, PUSCH) for the terminal 100 and generates a DCI (ST101). The base station 200 transmits the UL grant containing the generated DCI to the terminal 100 (ST102).

[0056] The terminal 100 calculates the transmission power of the PUSCH based on the radio resource allocation data indicated by the DCI included in the UL grant from the base station 200 (ST103). At this time, the terminal 100 determines the PC parameter set number j for calculating the PUSCH transmission power of the URLLC according to whether the predetermined condition related to the UL grant is satisfied.

[0057] The terminal 100 transmits the PUSCH to the base station 200 using the calculated transmit power (ST104).

[0058] [PC Parameter Set Selection Method]

The following describes a method for selecting a PC parameter set in the PC parameter controller 104 of the terminal 100.

[0059] When the predetermined condition relating to the UL grant (details are described below) is satisfied, the PC parameter controller 104 of the terminal 100 determines that the UL grant from the base station 200 (see, for example, ST102 in FIG. 5) is a UL grant for URLLC data scheduling, and configures a PC parameter set value corresponding to PC parameter set number j=A, which corresponds to the URLLC.

[0060] On the other hand, when the predetermined condition related to the UL grant is not satisfied, the PC parameter controller 104 of the terminal 100 determines that the UL grant from the base station 200 is a UL grant for scheduling data of a different service type other than URLLC, and configures the value of the PC option set corresponding to the number j=B of the PC option set, which corresponds to a service type other than URLLC.

[0061] The transmit power calculator 105 of the terminal 100 calculates the transmit power of the PUSCH using the configured PC parameter set number j, for example, in accordance with Equation 1.

[0062] The following describes examples of a "predetermined condition" for determining whether a UL grant is a UL grant for scheduling URLLC data.

[0063] [Example 1: UL Grant Payload Size]

In Example 1, the predetermined condition is that the payload size of the DCI format used in the UL resolution is different from the predetermined size. Or, in Example 1, the predetermined condition is that the payload size of the DCI format used in the UL resolution is less than the predetermined size.

[0064] As described above, the smaller the UL grant payload size for scheduling URLLC data, the higher the coding efficiency becomes, thus improving reliability. Therefore, it can be considered that the UL permission used for URLLC scheduling is configured with a format having a small payload size.

[0065] For example, in Example 1, when the payload size of the DCI format used in the UL grant from the base station 200 is different from or less than the specified size, the PC parameter controller 104 determines that this UL grant is a UL grant for URLLC scheduling. . In other words, when the payload size of the DCI format is different from or smaller than the predetermined size, the PC parameter controller 104 determines that the PUSCH scheduled by the UL grant is a URLLC PUSCH (URLLC PUSCH).

[0066] For example, when the payload size of the UL grant detected by the terminal 100 differs from the payload sizes of both the DCI 0_0 format and the DCI 0_1 format prescribed in the UL grant for PUSCH assuming eMBC, the PC parameter controller 104 may determine that it is the UL grant is a UL grant for PUSCH scheduling for URLLC.

[0067] Or, when the payload size of the UL grant detected by the terminal 100 is less than the payload size of the DCI 0_0 format corresponding to the DCI fallback format prescribed in the UL grant for PUSCH assuming eMBB, the PC parameter controller 104 may determine that this is a UL grant. is a UL permission to schedule PUSCH for URLLC.

[0068] When it is determined that the UL grant is a UL grant for scheduling PUSCH for URLLC, the PC parameter controller 104 selects the PC parameter set specified by the PC parameter set number j=A that corresponds to the URLLC.

[0069] On the other hand, when the payload size of the UL grant detected by the terminal 100 is equal to the payload size of DCI format 0_0 or DCI format 0_1, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than from URLLC (eg PUSCH for eMBV). When it is determined that the UL grant is a UL grant for scheduling service type data other than URLLC, the PC parameter controller 104 selects the PC parameter set specified by PC parameter set number j=B that corresponds to the service type other than URLLC.

[0070] As described above, in Example 1, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 according to the payload size of the DCI format used in the UL grant.

[0071] [Example 2: Scrambling sequence used in UL authorization]

In Example 2, the predetermined condition is that the scrambling sequence used in the UL grant is different from the predetermined sequence.

[0072] For example, when the terminal-specific scrambling sequence used in the DCI format of the UL grant differs from the given terminal-specific sequence, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling URLLC data. In other words, when the terminal-specific scrambling sequence used in the DCI format of the UL grant differs from the given terminal-specific sequence, the PC parameter controller 104 determines that the PUSCH scheduled by this UL grant is a URLLC PUSCH (URLLC PUSCH).

[0073] For example, in the DCI 0_0 format or the DCI 0_1 format prescribed in the UL grant for PUSCH assuming eMBV, a Cell-Radio Network Temporary Identifier (C-RNTI) or a configured Radio Network Temporary Identifier (Configured Scheduling) is used. -RNTI, CS-RNTI) and the like for a terminal specific scrambling sequence.

[0074] For example, when the scrambling sequence used in the UL grant detected by the terminal 100 is different from C-RNTI or CS-RNTI, the PC parameter controller 104 determines that this UL grant is a UL grant for URLLC PUSCH scheduling, and selects the set PC parameter set number j=A of the PC parameter set that corresponds to the URLLC.

[0075] On the other hand, when the scrambling sequence used in the UL grant detected by the terminal 100 is C-RNTI or CS-RNTI, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than from URLLC, and selects the PC parameter set identified by PC parameter set number j=B, which corresponds to a service type other than URLLC.

[0076] As described above, in Example 2, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 according to the scrambling sequence of the DCI format used in the UL authorization.

[0077] [Example 3: UL resolution after transmission of a Scheduling Request (SR) for URLLC]

In Example 3, the predetermined condition is that the UL grant is a UL grant received upon transmission of a scheduling request for URLLC (SR for URLLC) from terminal 100.

[0078] Here, "UL received after transmission of SR for URLLC" may be the UL granted within a given period XI [character] after transmission of the SR for URLLC, or may be the UL granted first after transmission of the SR for URLLC, e.g. .

[0079] In addition, the SR for URLLC may be explicitly indicated for URLLC, for example, when the SR resource is configured by the base station 200. In addition, an SR transmission that occurs during eMBV data transmission and has a high urgency or priority may be defined as transmit SR for URLLC. Or the radio resource for transmitting the SR for URLLC may be defined in the specifications. Or, when the resource cycle of the SR configured by the base station 200 is less than or equal to the predetermined value X2 [symbol], the SR for URLLC may be determined as the SR for URLLC for which low delay is requested.

[0080] For example, when a UL grant is received after transmitting an SR for URLLC, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling PUSCH for URLLC, and selects the PC parameter set specified by PC parameter set number j=A, which matches URLLC.

[0081] On the other hand, when a UL grant not satisfying the above predetermined condition is received after the transmission of the SR for URLLC, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than URLLC, and selects a set of parameters PC, identified by number j=B of the PC parameter set, which corresponds to a service type other than URLLC.

[0082] As described above, in Example 3, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 according to whether a UL grant corresponding to a predetermined condition is received after transmitting an SR for URLLC.

[0083] In addition, the values of the aforementioned threshold values X1 and X2 may be prescribed in advance in the specifications, or may be configured from the base station 200 to the terminal 100.

[0084] [Example 4: UL grant indicating retransmission in uplink transmission without grant] In Example 4, the predetermined condition is that UL grant indicates retransmission in uplink transmission without grant (hereinafter referred to as just "transfer without permission").

[0085] "Ungranted transmission" is a transmission method in which the radio resource (scheduling information) used in the initial transmission of the uplink signal is configured in advance from the base station 200 to the terminal 100. In the unauthorized transmission, when data is transmitted that should be transmitted, the terminal 100 transmits transmission data using a radio resource that is provided in advance.

[0086] According to the non-grant transmission, it is possible to shorten the time from generation of transmission data in the terminal 100 to PUSCH scheduling by granting the UL from the base station 200 after the transmission of the SR to the base station 200. Therefore, it is assumed that the non-grant transmission is used in the initial transmission for URLLC , which requires a small delay.

[0087] In addition, retransmission without permission is indicated by UL permission.

[0088] For example, when a UL grant is received to indicate retransmission without a grant, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling PUSCH for URLLC, and selects the PC parameter set specified by PC parameter set number j=A, which matches the URLLC. It should be noted that the PC parameter controller 104 may determine whether this is a retransmission in a non-grant transmission, for example, based on the value of the New data indicator (NDI) field in the UL grant.

[0089] On the other hand, when the non-grant transmission is not applicable, or when the UL grant for indicating retransmission without grant is not received, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than URLLC, and selects the PC option set identified by PC option set number j=B that corresponds to a service type other than URLLC.

[0090] As described above, in Example 4, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 according to whether the UL grant specifies retransmission in the case of unauthorized transmission.

[0091] In addition, the non-granted transmission resource for URLLC and the non-granted transmission resource for a service type other than URLLC (eg, eMBB) may differ from each other between the configuration performed by the base station 200 and the designation in the specification.

[0092] For example, in uplink transmission using the non-grant transmission resource, the terminal 100 may use the value of the PC parameter set for non-grant transmission, which is configured in advance from the base station 200 (a fixed value independent of the PC parameter set (see, for example, FIG. 1) used in uplink transmission based on UL approval). In addition, when an ungranted transfer resource for URLLC is defined, a distinction can be made between the value of the PC parameter set in the upstream using the ungranted transfer resource for URLLC and the value of the PC parameter set in the upstream using the ungranted transfer resource for the service type, other than URLLC.

[0093] This allows appropriate uplink power control to be performed on the initial URLLC transmission using the transmission resource without permission.

[0094] In addition, the UL grant to indicate retransmission without grant may be scrambled, for example, using CS-RNTI. In this case, when the detected UL grant is scrambled with the CS-RNTI, terminal 100 may determine that the PUSCH scheduled with that UL grant is for the URLLC.

[0095] [Example 5: Transmission Timing or Number of PUSCH Transmission Symbols Specified by UL Grant]

In Example 5, the predetermined condition is that the period of time from when terminal 100 receives the UL grant to when it transmits an uplink signal is within the predetermined time. Or, the predetermined condition is that the number of uplink transmission symbols indicated by the UL grant is less than or equal to the predetermined value.

[0096] The UL grant contains information about temporary resources (eg, time domain resource assignment field, etc.). The time resource information includes the time from receiving the UL grant to transmitting the PUSCH (eg, PUSCH preparation time, also referred to as N ₂ ) or the number of symbols (or slot length) of the PUSCH. In URLLC scheduling, the PUSCH preparation time or character length is likely to be configured to be short compared to other service type to meet low latency requirements.

[0097] For example, when the PUSCH preparation time indicated by the UL grant is less than or equal to X3 [character], the PC parameter controller 104 determines that this UL grant is a UL grant for PUSCH scheduling for URLLC, and selects the PC parameter set specified by j =A parameter set PC. [0097] On the other hand, when the PUSCH preparation time indicated by the UL grant is greater than X3 [character], the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than URLLC, and selects the PC parameter set , defined by the number j=B of the PC parameter set.

[0098] Or, when the number of PUSCH symbols indicated by the UL grant is less than or equal to X4 [character], the PC parameter controller 104 determines that this UL grant is a UL grant for PUSCH scheduling for URLLC, and selects the PC parameter set specified by number j =A parameter set PC. [0098] On the other hand, when the number of PUSCH symbols indicated by the UL grant is greater than X4 [character], the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than URLLC, and selects the PC parameter set , defined by the number j=B of the PC parameter set.

[0099] As described above, in Example 5, the PC parameter set number is implicitly indicated from base station 200 to terminal 100 according to the transmission timing (or number of transmission symbols) of the PUSCH indicated by the UL grant.

[0100] [Example 6: UL authorization detection loop]

In Example 6, the predetermined condition is that the UL grant detection cycle in the terminal 100 is less than or equal to the predetermined value.

[0101] In each DCI format including a UL grant, a given discovery cycle for each terminal 100 is configured with the base station 200. When scheduling URLLC data, it is likely that a shorter discovery cycle is configured for the UL grant to meet low latency requirements.

[0102] For example, when the UL grant discovery cycle is less than or equal to X5 [symbol], the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling PUSCH for URLLC, and selects the PC parameter set specified by parameter set number j=A PC.

[0097] On the other hand, when the UL grant discovery cycle is greater than X5 [symbol], the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling service type data other than URLLC, and selects the PC parameter set specified by number j =In PC parameter set.

[0104] As described above, in Example 6, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 in accordance with the UL grant discovery cycle.

[0105] [Example 7: Modulation and coding scheme (MCS) table used in UL authorization]

In Example 7, the predetermined condition is that the MCS table used in the UL grant is different from the predetermined MCS table.

[0106] In NR, "URLLC MCS table" and "eMBV MCS table" are defined in the MCS table (MCS template table uniquely corresponding to the MCS number) used in the UL grant to indicate the MCS (coding rate and modulation scheme) to the terminal.

[0107] An example of an MCS table for URLLC is shown in FIG. 7A, and an example of an eMBV MCS table is shown in FIG. 7B and 7C (for example, see NPL 6). The MCS table for URLLC shown in FIG. 7A does not have 256QAM (modulation order Qm=8) included in the eMBV MCS table shown in FIG. 7C and includes an MCS whose coding rate is lower than the eMBV MCS table shown in FIG. 7B and 7C (in other words, MCS with lower spectral efficiency).

[0108] For example, which MCS table used by the terminal 100 is predetermined by a terminal-specific scrambling sequence (eg, RNTI) used in the DCI format or a search space that is a PDCCH allocation resource.

[0109] For example, when the MCS table used in the UL grant is the URLLC MCS table, the PC parameter controller 104 determines that this UL grant is a UL grant for scheduling URLLC data. In other words, when the MCS table used in the UL grant is the URLLC MCS table, the PC parameter controller 104 determines that the PUSCH scheduled by this UL grant is the URLLC PUSCH (URLLC PUSCH).

[0110] For example, when the MCS table used in the UL grant detected by the terminal 100 is the MCS table for URLLC, the PC parameter controller 104 determines that this UL grant is a UL grant for URLLC PUSCH scheduling, and selects the PC parameter set determined by number j=A of the PC parameter set that corresponds to the URLLC.

[0111] On the other hand, when the MCS table used in the UL grant detected by the terminal 100 is an eMBB MCS table (or an MCS table other than the URLLC MCS table), the PC parameter controller 104 determines that this UL grant is a UL for scheduling service type data other than URLLC. When it is determined that the UL grant is a UL grant for scheduling service type data other than URLLC, the PC parameter controller 104 selects the PC parameter set specified by PC parameter set number j=B that corresponds to the service type other than URLLC.

[0112] As described above, in Example 7, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 100 in accordance with the MCS table of the DCI format used in the UL authorization.

[0113] Examples of a "predetermined condition" for determining that a UL grant is a grant that schedules URLLC data have been described above.

[0114] It should be noted that a plurality of predetermined conditions described in Examples 1-7 can be combined.

[0115] [Example configuration of number j=A, B of PC parameter set]

Next, an example of setting the numbers j=A and B of the PC parameter set configured in the PC parameter controller 104 will be described.

[0116] For example, the transmission power of the URLLC PUSCH is at least configured to be greater than the transmission power of the PUSCH of a service type other than URLLC (eg, eMBB).

[0117] For example, in Equation 1, the PUSCH transmit power P _PUSCH,f,c (i, j, qd, l) is likely to increase as the target PC parameter set receive power P _{O_PUSCH,f,c} (j) increases. . In addition, the PUSCH transmission power _PUSCH,f,c (i, j, qd, l) is likely to increase as the weighting factor α _f,c (j) representing the degree of compensation for the bandwidth loss of the PC parameter set, since the value of the bandwidth loss will be more easily reflected in the power _PUSCH,f,c (i, j, qd, l) of the PUSCH transmission.

[0118] In addition, as shown in FIG. 6, for example, the smallest number 0 of the number j of the PC parameter set (any of j equal to 0 to J-1) can be set to the value (B=0) of the PC parameter set of a service type other than URLLC (for example, for eMBV) , for example, and the largest number J-1 of the number j of the PC parameter set can be set to the value of the PC parameter set (A=J-1) for URLLC. As shown in FIG. 6, P _{O_PUSCH,f,c} (0) = -80 dBm and α _f,c (0)=0.6 in case of PC parameter set number j=0, and P _{O_PUSCH,f,c} (J-1) = -50 dBm and α _f,c (J-1)=1.0 in case of the number j=J-1 of the PC parameter set. Therefore, the PUSCH transmission power _PUSCH,f,c (i, j, qd, l) when PC parameter set number j=J-1 is configured is likely to be larger than the PUSCH power _PUSCH,f,c (i, j , qd, l) PUSCH transmission when PC parameter set number j=0 is configured.

[0119] It should be noted that the case in which the PC parameter set number A is set to the maximum value J-1 of the j number, and the PC parameter set number B is set to the minimum value 0 of the j number, is described in FIG. 6, but PC parameter set numbers A and B are not limited to these values. For example, PC parameter set number B may be configured to have a greater value than PC parameter set number A.

[0120] Or, the URLLC PC parameter set number A can be set as the PC parameter set number (=B+Δ) obtained by adding the specified offset Δ to the PC parameter set number B for a service type other than URLLC (e.g., eMBB) .

[0121] Or, the value (P _{O_PUSCH,f,c} (B)+Δ) of the PC parameter set obtained by adding the specified offset Δ [dB] to the value of the PC parameter set of a service type other than URLLC (eg, eMBV) may be used as the value (P _{O_PUSCH,f,c} (A)) of the PC option set for URLLC. In other words, it can be P _{O_PUSCH,f,c} (A)=P _{O_PUSCH,f,c} (B)+Δ.

[0122] In addition, in the case where the terminal 100 performs transmission and reception with multiple Transmission/Reception Points (TRP), the PC parameter set number A for URLLC and the PC parameter set number B for the service type other than URLLCs can be defined for each TRP. FIG. 8 shows an example of configuring PC parameter set values for each TRP. FIG. 8, for TRP #0, PC parameter set number j=J-2 is configured as a PC parameter set value for URLLC, and PC parameter set number j=0 is configured as a PC parameter set value for a service type other than URLLC, for example. Similarly, for TRP #1, PC parameter set number j=J-1 is configured as a PC parameter set value for URLLC, and PC parameter set number j=1 is configured as a PC parameter set value for a service type other than URLLC.

[0123] Different TRPs have very different propagation conditions such as bandwidth loss and the like. Thus, as shown in FIG. 8, it is possible to define and select sets of PC parameters suitable for the respective TRPs. As a result, terminal 100 can appropriately configure the transmit power of the PUSCH for each TRP.

[0124] It should be noted that the PC parameter set configuration for each TRP shown in FIG. 8 is just an example and is not limited thereto, and the URLLC PUSCH transmit power may at least be configured to be higher than the non-URLC service type PUSCH transmit power for each TRP. For example, depending on the distribution environment of TRP #0 and TRP #1, the value of the PC parameter set for URLLC with respect to TRP #0 may be configured to be lower than the value of the PC parameter set of the service type other than URLLC.

[0125] In addition, in the case where the base station 200 having a plurality of antenna panels with different layout environments (in other words, different Quaisi-colocation (QCL)) communicates with the terminal 100, the PC parameter set number A for URLLC and number B of the non-URLLC type of service parameter set PC may be determined for each antenna panel in the same manner as when a plurality of TRPs communicate with the terminal 100 (see, for example, FIG. 8).

[0126] In addition, the TRP number and the antenna panel number may be determined based on the transmission resource of the control channel (for example, called the Control Resource Set (CORESET)) in which, for example, the control channel (for example, PDCCH) is configured received by terminal 100.

[0127] The configuration of the numbers j=A and B of the PC parameter set is described above.

[0128] In addition, the correspondence relationship between the PC parameter set number j and the PC parameter set (eg, P _{O_PUSCH,f,c} (j) and α _f,c (j)) is not limited to the example shown in FIG. 6. For example, in FIG. 6 shows the case where P _{O_PUSCH,f,c} (j) and α _f,c (j) increase as the PC parameter set number j increases (in other words, the case when P _{O_PUSCH,f,c} (j) and α _{f, c} (j) are sorted in ascending order). However, the value of P _{O_PUSCH,f,c} (j) or α _f,c (j) need not increase as the number j of the PC parameter set increases.

[0129] As described above, in the present embodiment, terminal 100 configures a PC parameter set (power control parameter) corresponding to URLLC when a predetermined condition related to UL permission is satisfied, and configures a PC parameter set corresponding to a service type other than URLLC, when the specified condition is not satisfied. Then, the terminal 100 transmits the uplink signal using the transmit power calculated using the configured PC parameter set.

[0130] As a result, a parameter (e.g., a PC parameter set) of transmit power control (e.g., power up) PUSCH for URLLC from base station 200 to terminal 100 can be implicitly specified. Therefore, even in a UL grant that contains no information (or field ) explicitly indicating the PC parameter set number, it is possible to properly configure the uplink transmission power suitable for the service type such as URLLC and eMBB and the like. In addition, since it is not necessary to add new information to the UL grant, an increase in PDCCH overhead can be prevented.

[0131] Thus, according to the present embodiment, the terminal 100 can appropriately transmit an uplink signal using the transmission power of the uplink channel according to the type of service.

[0132] In this case, a low delay is required for uplink URLLC data transmission. Therefore, as shown in FIG. 9, URLLC data (URLLC PUSCH) may be scheduled on a radio resource that has already been assigned to another terminal for eMBB data (eMBB PUSCH). In addition, allocation of a wideband radio resource has been studied in URLLC to take advantage of frequency diversity. Thus, it is assumed that a portion of the radio resource (eg, time resource or frequency resource) overlaps between the URLLC and the eMBW.

[0133] As described above, according to the present embodiment, the terminal 100 can, in the uplink transmission of URLLC data, properly configure the uplink power with which the URLLC data can be decoded in the base station 200 even if part or all of the radio resource for the uplink transmission overlaps ( overlaps) between eMBV data and URLLC data from different terminals (eg, UE#0 and UE#1 in FIG. 9). Therefore, the requirements of low latency and high reliability for URLLC can be met.

[0134] [Embodiment 2]

In the present embodiment, a method for configuring transmission power of PUSCH is described when uplink control information for URLLC (hereinafter referred to as uplink control information (Uplink Control Information, UCI)) is transmitted on PUSCH (also referred to as "collated UCI").

[0135] For example, when the transmission timing of the PUCCH, which is the uplink channel for transmitting the UCI, overlaps with the transmission timing of the PUSCH, the terminal multiplexes the UCI with the Uplink Packed Channel (UL-SCH: Uplink Data Information) and transmits it on the PUSCH (which also called "co-located UCI") to prevent an increase in the Peak to Average Power Ratio (PAPR) when transmitting with multiple carriers.

[0136] In this case, when the terminal transmits on the PUSCH the UCI required to provide the same high quality as the URLLC data (hereinafter referred to as "URLLC UCI"), a power increase may be required to satisfy the UCI quality. In other words, when the UCI for URLLC is transmitted on the PUSCH at the terminal, a power increase may be required compared to when a service type other than URLLC (eg, eMBB) is transmitted. In addition, as a UCI for URLLC, for example, acknowledgment/negative acknowledgment (ACK/NACK) information for URLLC data or channel state information (hereinafter referred to as CSI, Channel State Information) for a target Block Error Rate , BLER) for URLLC (e.g. BLER=10E-5), etc. (details are described below).

[0137] However, PUSCH transmission power control is defined either with or without UCI. Therefore, when the SRI field is not included, as in the case of the DCI fallback format (e.g., DCI format 0_0), that is, when a UL grant is used that does not contain information explicitly indicating a PC parameter set number, the PUSCH transmit power is determined regardless of the presence or no UCI for URLLC. For this reason, the terminal may not be able to appropriately increase the transmission power of the PUSCH including the UCI. For example, even when the terminal transmits data for eMBB and UCI for PUSCH on one PUSCH, the same transmission power is used as when transmitting data for eMBB alone (in other words, when data for eMBB is transmitted without UCI). Therefore, the UCI for PUSCH may have insufficient transmit power and may not meet the URLLC quality requirements.

[0138] Thus, in the present embodiment, a method is described for appropriately increasing the transmit power of a PUSCH including a UCI (specifically, a UCI for URLLC) by selecting a PC parameter set.

[0139] The communication system according to the present embodiment includes a terminal 300 (see FIG. 10, which is described below) and a base station 200 (see FIG. 4, for example).

[0140] [300 Terminal Configuration]

FIG. 10 is a block diagram showing a configuration example of a terminal 300 according to the present embodiment. FIG. 10, the same components as those of the terminal 100 (FIG. 3) of Embodiment 1 are assigned the same reference numerals and their descriptions are omitted. In particular, in the terminal 300 shown in FIG. 10 to terminal 100 shown in FIG. 3, the UCI generator 301, the encoder/modulator 302, and the multiplexer 303 are added, and the operation of the PC parameter controller 304 is different.

[0141] The UCI generator 301 generates UCI (uplink control information such as ACK/NACK or CSI, etc.) transmitted by the terminal 300, and outputs the generated UCI to the encoder/modulator 302. In addition, the UCI generator 301 outputs information related to the transmitted UCI to the PC parameter controller 304 .

[0142] The encoder/modulator 302 encodes and modulates the UCI input from the UCI generator 301 based on the DCI input from the demodulator/decoder 103, and outputs the modulated UCI signal to the multiplexer 303.

[0143] The multiplexer 303 multiplexes the UCI signal input from the encoder/modulator 302 and the modulated data signal input from the encoder/modulator 107, and outputs the multiplexed data signal to the resource allocator 108. The multiplexer 303 may puncture some of the Resource Elements (REs) of the data signal and place the UCI signal in the punctured portion, for example, as a method of multiplexing the UCI and the data signal. Or, the multiplexer 303 may take into account the RE size of the UCI signal in advance and determine (rate match) the RE size of the data signal.

[0144] The PC parameter controller 304 determines the PC parameter set number j applied to the scheduled PUSCH using the DCI input from the demodulator/decoder 103 and the UCI related information input from the UCI generator 301. The PC parameter controller 304 outputs the determined PC parameter set number to the transmit power calculator 105 .

[0145] [Base Station Configuration]

Since the base station according to the present embodiment has the same basic configuration as the base station 200 according to Embodiment 1, it will be described with reference to FIG. 4. It should be noted that the decoded reception data at the base station 200 according to the present embodiment includes the UCI in addition to the data from the terminal 300 (see FIG. 10).

[0146] Further, this application describes examples of "predetermined condition" for adapting the increase in transmission power by changing the set of PC parameters in relation to PUSCH, including (multiplexing or overlapping) UCI (in particular, UCI for URLLC).

[0147] [Example 1: Enabling ACK/NACK on PDSCH (downlink data channel) for URLLC]

In Example 1, the predetermined condition is that the UCI included in the PUSCH scheduled by the UL grant is an ACK/NACK (answer signal) for the PDSCH for the URLLC. It can be considered that ACK/NACK for PDSCH for URLLC is required to provide low latency and high reliability, similar to PDSCH for URLLC.

[0148] In addition, when the scrambling sequence (eg, RNTI) used in DCI for PDSCH scheduling differs from the specified sequence (eg, C-RNTI or CS-RNTI for PDSCH scheduling for eMBB), terminal 300 may determine that this PDSCH is the PDSCH for URLLC. For example, when the scrambling sequence used in DCI for PDSCH scheduling is the RNTI for URLLC, terminal 300 may determine that this PDSCH is the PDSCH for URLLC.

[0149] Or, when using the MCS table for URLLC in DCI to schedule a PDSCH, terminal 300 may determine that this PDSCH is the PDSCH for URLLC.

[0150] For example, when an ACK/NACK for PDSCH for URLLC is included in the PUSCH scheduled by the UL grant detected by the terminal 300, the PC parameter controller 304 determines that this UL grant is a UL grant for PUSCH scheduling that contains the UCI for URLLC, and selects the PC option set specified by the PC option set number j=A that corresponds to the URLLC.

[0151] On the other hand, when the PDSCH ACK/NACK for URLLC is not included in the PUSCH scheduled by the UL grant detected by the terminal 300, the PC parameter controller 304 determines that this UL grant is a UL grant for PUSCH scheduling that does not contain UCI for URLLC, and selects the PC option set identified by PC option set number j=B, which corresponds to a service type other than URLLC.

[0152] As described above, in Example 1, the PC parameter set number is implicitly indicated from base station 200 to terminal 300 according to whether ACK/NACK for PDSCH for URLLC in PUSCH scheduled by UL grant is included.

[0153] [Example 2: ACK/NACK when the time interval from PDSCH reception to ACK/NACK transmission does not exceed a predetermined threshold]

In Example 2, the predetermined condition is that the UCI included in the PUSCH scheduled by the UL grant is an ACK/NACK when the time interval from PDSCH reception to ACK/NACK transmission (sometimes referred to as N1 [symbol], for example) is less than or equal to the set threshold X6 [character]. For example, N1 is included in DCI for PDSCH scheduling.

[0154] In other words, the predetermined condition is that the time period N1 [symbol] from the time the terminal 300 receives the PDSCH to the time the terminal 300 transmits a UCI containing an ACK/NACK for that PDSCH is within the predetermined time X6.

[0155] When N1 is short (in other words, in the case of N1≤X6), terminal 300 may determine that the UCI included in the UL scheduled PUSCH is the UCI for URLLC that requires low delay.

[0156] For example, when a short N1 ACK/NACK (ACK/NACK where N1≤X6) is included in the PUSCH scheduled by the UL grant detected by the terminal 300, the PC parameter controller 304 determines that this UL grant is a UL grant for scheduling a PUSCH that contains the UCI for the URLLC, and selects the PC parameter set specified by the PC parameter set number j=A that corresponds to the URLLC.

[0157] On the other hand, in a case other than the above (for example, when ACK/NACK with long N1 (ACK/NACK where N1>X6) is included in PUSCH), the PC parameter controller 304 determines that this UL grant is a UL for PUSCH scheduling that does not contain the UCI for URLLC and selects the PC Parameter Set number j=B of the PC Parameter Set that corresponds to a service type other than URLLC.

[0158] As described above, in Example 2, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 300 according to whether a short N1 ACK/NACK is included in the PUSCH scheduled by the UL grant.

[0159] [Example 3: CSI calculated with a target BLER not exceeding a given threshold]

In Example 3, the predetermined condition is that the UCI included in the PUSCH scheduled by the UL grant is the CSI calculated with a target error rate (eg, BLER) that is less than or equal to the predetermined threshold value X7.

[0160] The target BLER used in the calculation of the CSI is configured in advance from the base station 300 to the terminal 200. The terminal 300 may determine that the CSI calculated with a low target BLER less than or equal to the X7 threshold is the UCI for URLLC.

[0161] For example, when a CSI calculated with a target BLER (eg, target BLER=10E-5) less than or equal to a predetermined threshold X7 is included in the PUSCH scheduled by the UL grant detected by the terminal 300, the PC parameter controller 304 determines that this UL grant is a UL grant for PUSCH scheduling that contains the UCI for the URLLC, and selects the PC parameter set number j=A of the PC parameter set that corresponds to the URLLC.

[0162] On the other hand, in a case other than the above (for example, when the CSI calculated with the target BLER (eg, target BLER=10E-1) exceeding the predetermined threshold value X7 is included in PUSCH), the PC parameter controller 304 determines that this UL grant is a UL grant for PUSCH scheduling that does not contain a UCI for URLLC, and selects a PC parameter set identified by PC parameter set number j=B that corresponds to a service type other than URLLC.

[0163] As described above, in Example 3, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 300 according to whether the PUSH scheduled by the UL grant includes a CSI calculated with a target BLER less than or equal to the specified threshold value X7.

[0164] [Example 4: enabling ACK/NACK in PDSCH for eMBV]

In Example 4, the predetermined condition is that the UCI included in the PUSCH scheduled by the UL grant is an ACK/NACK for the eMBV PDSCH. Thus, the condition is opposite to the condition (being ACK/NACK for PDSCH for URLLC) from Example 1 according to the present embodiment.

[0165] For example, when scheduling a service having a lower priority of low delay and a higher priority of high reliability, the base station 200 may be considered to perform control such that the total error rate obtained by multiplying the respective PDSCH and ACK/NACK error rates , for this PDSCH becomes a given quality.

[0166] For example, a case has been described where the total error rate (a value obtained by multiplying the respective error rates) of the PDSCH and ACK/NACK becomes a constant value (eg, 10E-6). In this case, the base station 200 performs control such that the PDSCH error rate becomes 10E-1 (PDSCH equivalent quality for eMBB) and the ACK/NACK error rate becomes 10E-5 (URLC equivalent UCI quality), for example. Or, the base station 200 controls such that the PDSCH error rate becomes 10E-5 (PDSCH equivalent quality for URLLC) and the ACK/NACK error rate becomes 10E-1 (UCI equivalent quality for eMBB).

[0167] In other words, the ACK/NACK for the PDSCH whose error rate is controlled at 10E-1 (PDSCH for eMBB) is the UCI for the URLLC whose error rate is controlled at 10E-5. On the other hand, ACK/NACK for PDSCH whose error rate is controlled at 10E-5 (PDSCH for URLLC) is the UCI for eMBB whose error rate is controlled at 10E-1.

[0168] Therefore, when the base station 200 performs such control as described above, for example, when the ACK/NACK for PDSCH for eMBV is included in the PUSCH scheduled by the UL grant detected by the terminal 300, the PC parameter controller 304 determines that this grant is UL is a UL grant for PUSCH scheduling that contains a UCI for URLLC (ACK/NACK) and selects a PC parameter set specified by PC parameter set number j=A that corresponds to the URLLC.

[0169] On the other hand, in a case other than the above, the PC parameter controller 304 determines that this UL grant is a UL grant for scheduling a PUSCH that does not contain a UCI for URLLC (eg, a PUSCH containing a UCI for eMBB), and selects PC option set, identified by PC option set number j=B, which corresponds to a service type other than URLLC.

[0170] As described above, in Example 4, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 300 according to whether ACK/NACK for the eMBB PDSCH is included in the PUSCH scheduled by the UL grant.

[0171] It should be noted that although the PC parameter set value control method is switched between Examples 1 and 4 according to the present embodiment, the appropriate control method can be selected in accordance with the scheduling method adopted by the base station 200.

[0172] [Example 5: Number of REs required for UCI for URLLC reaches upper limit]

In Example 5, the predetermined condition is that the UCI for URLLC applicable to any of Examples 1-4 according to the present embodiment is included (combined) in the PUSCH scheduled by the UL grant, and the number of REs required for this UCI for URLLC , reaches the upper limit of the number of REs that can be placed in PUSCH.

[0173] In NR, in the case of ACK/NACK, the number of UCI REs that can be placed in the PUSCH is determined, for example, in accordance with the following Equation 2.

[2]

[0174] Here, Q' _ACK is the number of RE (called the actual number of RE) ACK/NACK actually transmitted on PUSCH, O _ACK is the number of ACK/NACK bits, L _ACK is the number of Cyclic Redundancy Check bits , CRC), β _offset ^PUSCH is an ACK/NACK coding rate correction factor (parameter) for data (UL-SCH), ΣM _SC ^UCI (l) (where l is 0 to N _symb,all ^PUSCH -1) is the number of REs used in PUSCH transmission, and ΣK _r (where r is 0 to C _UL-SCH -1) is the number of data bits (UL-SCH) transmitted on the PUSCH. In addition, a represents the ratio of the number of RE UCIs (ACK/NACK) transmitted on the PUSCH. In other words, α is a parameter for defining an upper limit on the number of UCI REs to ensure the quality of the UL-SCH.

[0175] Here, the left side of the Min function of Equation 2 (let Q'' _ACK as in the following Equation 3) represents the number of REs (called the required number of REs) used in PUSCH transmission to obtain the quality required for ACK/NACK.

[3]

[0176] When the number of REs (required number of REs) required for the UCI for URLLC reaches the upper limit, that is, when the number of REs is limited to α to Q' _ACK <Q'' _ACK , the terminal 300 cannot locate the UCI containing the specified number RE, to meet the required quality in PUSCH.

[0177] Therefore, when the number of REs required for the UCI for URLLC reaches the upper limit of the number of REs that can be placed in the PUSCH (i.e., in the case of Q' _ACK <Q'' _ACK ), the PC parameter controller 304 selects a PC parameter set defined by the PC parameter set number j=A that corresponds to the URLLC, to improve the quality of the UCI for the URLLC.

[0178] On the other hand, when the number of REs required for the UCI for URLLC has not reached the upper limit of the number of REs that can be placed in the PUSCH (i.e., in the case of Q' _ACK ≥Q'' _ACK ), the controller 304 The PC Parameter Set determines that there is no need for power up and selects the PC Parameter Set identified by PC Parameter Set Number j=B, which corresponds to a service type other than URLLC.

[0179] As described above, in Example 5, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 300 according to whether the number of REs required for the UCI for the URLLC included in the PUSH scheduled by the UL grant reaches the upper a limit on the number of REs that can be placed in PUSCH.

[0180] In addition, the terminal 300 performs the same data processing as described above even when the UCI for URLLC is CSI (more specifically, CSI-1 (CSI Part 1) and CSI-2 (CSI Part 2). That is, when the number of CSI REs to be placed in the PUSCH is limited to a, the terminal 300 selects the PC parameter set number j=A of the PC parameter set that corresponds to the URLLC to improve the quality of the UCI for the URLLC.

[0181] [Example 6: The number of UCI REs including the UCI for URLLC is greater than the predetermined ratio]

In Example 6, the predetermined condition is that the UCI for URLLC applicable to any of Examples 1 to 4 according to the present embodiment is included in the PUSCH scheduled by UL grant, and the number of UCI REs including the UCI for URLLC is greater than given ratio in general PUSCH

[0182] For example, terminal 300 performs power up in PUSH when the condition presented in the following Equation 4 is satisfied.

[four]

[0183] Here, Q'ACK, Q'CSI-1 and Q'CSI-2 represent the RE number (actual RE number) of ACK/NACK, CSI part 1 and CSI part 2 that are actually transmitted on the PUSCH, respectively. In addition, ΣM _SC ^UCI (l) (where l is 0 to N _symb,all ^PUSCH -1) is the number of REs used in PUSCH transmission, and γ is the upper limit factor of the number of UCI REs (total UCI including in ACK/NACK and CSI) containing the UCI for the URLLC carried on the PUSCH. For example, when the ratio of the RE number of UCI to the RE number of the total PUSCH exceeds this factor γ, it is assumed that the UCI is more dominant than the UL-SCH in the PUSCH.

[0184] For example, when the total required number of REs for the UCI including the UCI for URLLC reaches the upper limit, that is, when the condition of Equation 4 is met, the PC parameter controller 304 determines that the UCI is dominant over the UL-SCH in the PUSCH , and selects the PC option set specified by the PC option set number j=A that matches the URLLC.

[0185] On the other hand, when the total required number of REs for the UCI including the UCI for URLLC does not reach the upper limit, that is, when the condition of Equation 4 is not met, the PC parameter controller 304 determines that the UL-SCH is dominant over with UCI in PUSCH, and selects the PC Parameter Set identified by PC Parameter Set Number j=B, which corresponds to a service type other than URLLC.

[0186] As described above, in Example 6, the PC parameter set number is implicitly indicated from the base station 200 to the terminal 300 according to whether the UCI is dominant over the UL-SCH in the PUSCH.

[0187] It should be noted that δ, which is an upper limit (number of REs) of the number of RE UCIs transmitted on the PUSCH, can be determined as in the following Equation 5. That is, when the condition of Equation 5 is met, the terminal 300 determines that the UCI is dominant over UL-SCH in PUSCH and selects the PC parameter set number j=A of the PC parameter set that corresponds to the URLLC. As a result, effects similar to those of control using the γ factor shown in Equation 4 can be obtained.

[5]

[0188] Described above are examples of "predetermined condition" for adapting transmission power increase by changing the PC parameter set with respect to a PUSCH containing a UCI.

[0189] It should be noted that a plurality of predetermined conditions described in Examples 1-6 can be combined.

[0190] [PC Parameter Set Selection Method]

The following describes a method for selecting a PC parameter set when the UCI is set to PUSH in the PC parameter controller 304 of the terminal 300.

[0191] [Example 1: Selecting a PC Parameter Set for Each UCI Type from UCI for URLLC]

In Example 1, the PC parameter controller 304 selects a PC parameter set for each UCI type from the UCI for URLLC (eg, ACK/NACK, CSI part 1 or CSI part 2, etc.).

[0192] For example, as shown in FIG. 11, when the UCI type is CSI (CSI part 1 or CSI part 2), the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-2 that corresponds to the URLLC. In addition, when the UCI type is ACK/NACK, the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-1 that corresponds to the URLLC.

[0193] As a result, it is possible to increase the ACK/NACK transmission power, which is considered to have a large impact on the packet transmission delay time compared to CSI.

[0194] In addition, the CSI part 1 includes a wideband CQI or rank indicator, and the CSI part 2 includes a subband CQI. Part 1 of the CSI is considered important information that is often used in base station planning as compared to Part 2 of the CSI. Therefore, the PC parameter controller 304 can determine the PC parameter set such that high transmit power is configured when CSI part 1 is enabled as UCI for URLLC, compared to when only CSI part 2 is enabled as UCI.

[0195] For example, when the CSI part 1 is included in the UCI, the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-2 (e.g., P _{O_PUSCH,f,c} (j) = -60 dBm, α _f,c (j)=0.9). In addition, when only the CSI part 2 is included in the UCI, the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-3 (for example, P _{O_PUSCH,f,c} (j) = -55 dBm, α _{f ,c} (j)=0.9).

[0196] As a result, it is possible to adjust the appropriate transmission power according to the importance of the CSI information.

[0197] [Example 2: Selecting a PC Parameter Set According to the Number of UCI Bits Including UCI for URLLC]

In Example 2, the PC parameter controller 304 selects the PC parameter set according to the number of UCI bits including the UCI for URLLC.

[0198] For example, as shown in FIG. 12, when the number of UCI bits including the URLLC UCI is less than or equal to the predetermined threshold X8 [bit], the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-2 that corresponds to the URLLC. In addition, when the number of UCI bits including the URLLC UCI is greater than the predetermined threshold value X8 [bit], the PC parameter controller 304 selects the PC parameter set specified by the PC parameter set number j=J-1 that corresponds to the URLLC.

[0199] As a result, the transmission power of the PUSCH can be increased as the number of UCI bits increases, that is, as the UCI becomes more dominant in the entire PUSCH.

[0200] [Example 3: Selecting a PC Parameter Set According to a Combination of UL-SCH and UCI Service Types for URLLC]

In Example 3, the PC parameter controller 304 selects the PC parameter set according to the combinations of UL-SCH and UCI service types for URLLC.

[0201] As shown in FIG. 13, there are four combinations of UL-SCH (PUSCH) and UCI for URLLC. FIG. 13, (1) shows the pattern in which the UCI for eMBB is transmitted on the PUSCH for eMBB, (2) shows the pattern in which the UCI for URLLC is transmitted on the PUSCH for URLLC, (3) shows the pattern in which the UCI for URLLC is transmitted on PUSCH for eMBB, and (4) shows the pattern in which the UCI for eMBB is transmitted on the PUSCH for URLLC.

[0202] For example, as in Option 1 shown in FIG. 13, the PC parameter controller 304 may select the PC parameter set specified by the PC parameter set number j=A that corresponds to URLLC in the case of a combination in which at least one of UCI for URLLC and PUSCH for URLLC is included (combination (2), (3) or (4) in FIG. 13). On the other hand, as in Option 1 shown in FIG. 13, the PC parameter controller 304 may select the PC parameter set specified by the PC parameter set number j=B that corresponds to URLLC in the case of a combination in which none of UCI for URLLC and PUSCH for URLLC are included (combination (1) in FIG. 13).

[0203] Or, as in Option 2 in FIG. 13, the PC parameter controller 304 may select the PC parameter set according to the respective combinations. In Option 2 in FIG. 13, the PC parameter controller 304 selects the PC parameter set specified by PC parameter set number j=B, which corresponds to eMBV, in the case of combination (1), and selects the PC parameter sets specified by j=A1 to A3, which corresponds to URLLC, in case of combination (2) - (4), respectively.

[0204] For example, as shown in Option 2 in FIG. 13, when the UCI quality for URLLC takes precedence over the PUSCH quality for URLLC, the PC parameter controller 304 configures the PC parameter set in which the transmission power is increased in the order (2)>(3)>(4). Note that the PC parameter set configuration method is not limited to the example shown in FIG. 13. For example, when the PUSCH quality for URLLC takes precedence over the UCI quality for URLLC, the PC parameter controller 304 may configure a PC parameter set in which transmission power is increased in the order (2)>(4)>(3).

[0205] As a result, the terminal 300 can configure the transmission power according to the combination of UL-SCH (PUSCH) and UCI service types for URLLC.

[0206] The PC parameter set selection method is described above. Note that the values (for example, j=0, J-3, J-2, or J-1) of the PC parameter set configured in FIG. 11-13 are one example, and other values may be used.

[0207] As described above, in the present embodiment, the terminal 300 configures the PC parameter set (power control parameter) corresponding to the URLLC when a predetermined condition related to the UCI for the URLLC included in the PUSCH scheduled by the UL grant is satisfied, and configures the set PC parameters corresponding to a service type other than URLLC when the specified condition is not satisfied. Then, the terminal 300 transmits the uplink signal using the transmit power calculated using the configured PC parameter set.

[0208] As a result, in the present embodiment, the terminal 300 can control the transmit power of the PUSCH according to the presence or absence of the UCI for URLLC, so that an appropriate power boost can be performed on the transmit power of the PUSCH including the UCI (specifically, the UCI for URLLC ).

[0209] In addition, when at least one UCI for URLLC satisfying the predetermined condition of Examples 1-4 as described above is included in the UCI included and transmitted on the PUSCH, the terminal 300 may select the PC parameter set specified by the number j=A the PC parameter set that matches the URLLC, regardless of other information included in that UCI.

[0210] In addition, when the UCI for URLLC satisfying the predetermined condition as described above is included in the PUSCH for eMBV scheduled by DCI (for example, DCI format 0_0 or DCI format 0_1 scrambled with C-RNTI or CS-RNTI ), the terminal 300 may select the PC parameter set specified by the PC parameter set number j=A that corresponds to the URLLC, even in the case of PUSCH for eMBB.

[0211] In addition, the present embodiment can be similarly applied to the transmit power configuration method when the UCI for URLLC is transmitted on the PUSCH, where the transmission is performed without permission.

[0212] In addition, when changing the PC parameter set, the terminal 300 does not need to change the number of UCI REs placed in the PUSCH. That is, the terminal 300 does not need to change the parameter (α, β _offset ^PUSCH ) to calculate the number of RE (coding rate) UCI. Therefore, the terminal 300 can configure the transmission power according to the quality requirements of the UCI by simply controlling the change of the PC parameter set.

[0213] Or, the terminal 300 may change the number of UCI REs placed on the PUSCH with a change in the PC parameter set. In this case, the terminal 300 separately configures a parameter used in the calculation of the UCI code rate according to the PC parameter set, or changes the code rate calculation in view of the increase or decrease in transmission power due to the PC parameter set. As a result, the terminal 300 can more appropriately configure the transmission power according to the quality requirements of the UCI by controlling the change in the PC parameter set and the change in the calculation of the UCI coding rate.

[0214] [Embodiment 3]

In the present embodiment, a method for configuring the uplink transmission power of PUSCH in UCI transmission for URLLC no PUSCH is described similarly to Embodiment 2 of the invention.

[0215] In the present embodiment, a method has been described for appropriately increasing the power with respect to the transmission power of a PUSCH containing a UCI (specifically, the UCI for URLLC) by fixing the PC parameter set regardless of the service type and by introducing a UCI-dependent power adjustment parameter into the power equation transmission (see, for example, Equation 1).

[0216] The communication system according to the present embodiment includes a terminal 400 (see FIG. 14, which is described below) and a base station 200 (see FIG. 4, for example).

[0217] [Terminal 400 configuration]

FIG. 14 is a block diagram showing a configuration example of a terminal 400 according to the present embodiment. FIG. 14, the same components as those of the terminal 100 (FIG. 3) of Embodiment 1 or the terminal 300 (FIG. 10) of Embodiment 2 are assigned the same reference numbers and their descriptions are omitted. In particular, in the terminal 400 shown in FIG. 14, the operations of the UCI generator 401 and the transmit power calculator 402 differ from the terminal 300 shown in FIG. ten.

[0218] The PC parameter controller 104 performs the same data processing as in Embodiment 1. [0144] The PC parameter controller 104 determines the PC parameter set number j applied to the scheduled PUSCH using the DCI input from the demodulator/decoder 103 regardless of the presence or absence of a UCI.

[0219] The UCI generator 401 generates the UCI transmitted by the terminal 400 and outputs the generated UCI to the encoder/modulator 302. In addition, the UCI generator 401 outputs information related to the transmitted UCI to the transmit power calculator 402.

[0220] The transmit power calculator 402 calculates the transmit power of the PUSCH using the PC parameter set number j configured in the PC parameter controller 104 in accordance with Equation 6, for example. In Equation 6, ΔUCI (UCI dependent power control parameter [dB]) is added to Equation 1.

[6]

[0221] [Base Station Configuration]

Since the base station according to the present embodiment has the same basic configuration as the base station 200 according to Embodiment 1 or Embodiment 2, it will be described with reference to FIG. 4. It should be noted that the decoded reception data at the base station 200 according to the present embodiment includes the UCI in addition to the uplink data from the terminal 400 (see FIG. 14).

[0222] The following describes examples of a method for increasing transmission power using a UCI-dependent power adjustment parameter ΔUCI with respect to a PUSCH containing a UCI.

[0223] ΔUCI is calculated, for example, as shown in the following Equation 7.

[7]

[0224] Here, Q''UCI is the number of REs (required number of REs) of UCIs transmitted on the PUSCH to improve the quality required for the UCI. In particular, Q''UCI is the total number of REs of the respective required numbers of ACK/NACK REs, CSI Part 1 and CSI Part 2 (Q''ACK, Q''CSI-1 and Q''CSI-2) as shown in Equation 8.

[eight]

[0225] In addition, in Equation 7, Q'UCI is the number of REs (actual number of REs) of UCIs actually transmitted on the PUSCH. In particular, Q'UCI is the total number of REs of the respective actual numbers of ACK/NACK REs, CSI Part 1 and CSI Part 2 (Q'ACK, Q'CSI-1 and Q'CSI-2), as shown in Equation 9.

[9]

[0226] Therefore, even when the number of UCI REs to satisfy the quality required for the UCI cannot be placed on the PUSCH (in the case of Q' _UCI (actual number of RE) <Q'' _UCI (required number of RE)), the terminal 400 may apply power increase according to insufficient amount of RE by applying ΔUCI Δ _UCI . For example, the smaller the Q' _UCI for the Q'' _UCI , the larger the Δ _UCI , and the transmit power calculator 402 configures a higher transmit power for the PUSCH.

[0227] As a result, in the present embodiment, the transmission power of the PUSCH can be controlled according to the UCI for URLLC, so that a corresponding power boost can be performed on the transmission power of the PUSCH including the UCI (specifically, the UCI for URLLC).

[0228] In addition, in the present embodiment, when terminal 400 does not transmit UCI on PUSCH, Δ _UCI may not be applicable (Δ _UCI = 0 [dB]) in Equation 6.

[0229] In addition, the present embodiment can be similarly applied to the transmission power configuration method when the UCI for URLLC is transmitted on the PUSCH, where transmission is performed without permission.

[0230] In addition, in the present embodiment, _ΔUCI can only be applied when UCI for URLLC is enabled, and _ΔUCI may not be applicable ( _ΔUCI =0 [dB]) when UCI for URLLC is not enabled. Or, Δ _UCI can be applied regardless of the UCI service type (regardless of UCI for URLLC and UCI for eMBB).

[0231] The embodiments of the present invention have been described above.

[0232] (1) The type of service or type of traffic (eg, information indicating either URLLC or eMBV) may be included in a UL permit. In this case, the base station 200 can easily indicate to the terminal 100 the PUSCH service type that has been scheduled using the UL grant, and the terminal 100 can transmit data on the PUSCH using the PC parameter set appropriate for the service type.

[0233] (2) In the above embodiment, the case where the PC parameter set (eg, PC parameter set number j) is changed in accordance with a predetermined condition related to UL granting is described. However, in the present embodiment, a PC parameter other than PC parameter set number j (eg, PL evaluation number q _d RS, closed loop process number l) can be changed according to a predetermined condition related to UL authorization.

[0234] For example, another closed loop processing (number l) may be configured between the URLLC and the eMBV according to a predetermined condition related to the UL grant. In addition, a different closed-loop data processing correction value can be configured between the URLLC and the eMBV according to a predetermined condition related to the UL authorization. For example, when the DCI closed loop processing correction value contains 2 bits (4 patterns), a larger correction value can be applied in URLLC than in eMBV, for example, {+3, -1, 0,+1} for eMBV and {+6, -2, 0,+2} for URLLC. In this case, the terminal 100 may perform closed loop power control in accordance with the quality requirements for the type of service. In addition, the parameter configured in accordance with the predetermined condition related to UL permission is not limited to the closed loop processing and may be another parameter.

[0235] (3) In the above embodiment, PUSCH transmission power control has been described. However, an embodiment of the present invention can also be applied to an uplink channel other than PUSCH (eg, a Physical Uplink Control Channel (PUCCH).

[0236] PUCCH transmission power control is performed, for example, according to the following Equation 10 (see, for example, NPL 3).

[ten]

[0237] In Equation 10, P _PUCCH,b,f,c (i, qu, qd, l) is the PUCCH transmit power [dBm] at UL BWP part number "b", carrier number "f" , a serving cell number "c", a slot number "i", a PC parameter number "qu", a PL evaluation RS number "qd", and a closed loop processing number "l". P _{O_PUCCH,b,f,c} (q _u ) is the target receive power [dBm] (parameter value) at PC parameter number qu. 2μ⋅M _RB,b,f,c ^PUCCH (i) is the PUSCH bandwidth [PRB] obtained by SCS normalization applied to PUSCH at slot number i with 15 kHz SCS affinity PL _b,f,c ( q _d ) is the bandwidth loss [dB] measured by the terminal from RS at RS number q _d . _{ΔF_PUCCH} (F) is an offset [dB] depending on the PUCCH format. Δ _TF,b,f,c (i) is an offset [dB] dependent on the MCS of data transmitted at slot number i. g _b,f,c (i, l) is the closed loop processing correction value [dB] at slot number i and closed loop process number l.

[0238] For example, with respect to the PUCCH for transmitting ACK/NACK to the downlink data channel (PDSCH: Physical Downlink Shared Channel), the PC parameter number q _u can be indicated from the base station 200 to the terminal 100 using the information MAC-CE PDSCH (particularly PUCCH spatial relationship information). However, with respect to the PUCCH, there is no accompanying PDSCH to perform the SR transmission, so there is no explicit indication of the value of the PC parameter from the base station 200 to the terminal 100.

[0239] With regard to such a PUCCH transmission where there is no explicit indication of the value of the PC parameter, the terminal 100 may switch the value of the PC parameter (for example, the number q _u of the PC parameter) according to a predetermined condition related to the UL grant, similarly to the above-described embodiment. For example, a PC parameter value corresponding to a large transmission power value compared to SR transmission of a service type other than URLLC may be configured for a PUCCH that performs SR transmission for URLLC. As a result, the SR for URLLC can be transmitted with high quality, and URLLC requirements can be met. Thus, the same effects as for PUSCH transmission can be obtained for PUCCH transmission.

[0240] (4) In the present embodiment, a service type having various requirements such as reliability or low latency and the like (in other words, service, traffic type, logical channel type, use case or use case) is not limited by URLLC or eMVV. For example, one embodiment of the present invention can be applied to mMTC transmission and similar effects can be obtained.

[0241] (5) The present invention may be implemented by software, hardware, or software in cooperation with hardware. Each functional block used in the description of each embodiment described above may be partially or wholly implemented by a third-level integration (LSI) integrated circuit, such as an integrated circuit, and each process described in each embodiment may be partially or wholly controlled. the same LSI or a combination of LSIs. An LSI may be individually configured as a chip, or a single chip may be configured to include some or all of the functional blocks. An LSI may include its associated inputs and outputs. The LSI in this application may be referred to as integrated circuit (IC), system LSI, super-LSI or ultra-LSI depending on the difference in the degree of integration. However, the implementation method of the integrated circuit is not limited to LSI, and may be implemented using a dedicated circuit, a general purpose processor, or a special purpose processor. In addition, a field-programmable gate array (FPGA) can be used, which can be programmed after the manufacture of the LSI, or a reconfigurable processor, in which the connections and settings of circuit cells located inside the LSI can be reconfigured. The present invention may be implemented as digital data processing or analog data processing. If future integrated circuit technology replaces LSI as a result of the development of semiconductor technology or other derivative technology, functional blocks can be integrated using future integrated circuit technology. In addition, biotechnology may be applied.

[0242] The present invention may be implemented in any type of instrument, apparatus, and system, each provided with a communication function (collectively referred to as "communication devices"). Non-limiting examples of communication devices include telephones (e.g., portable phones and smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, and notebooks), cameras (e.g., digital still cameras/camcorders), digital players (e.g. , digital audio/video players), wearable devices (such as wearable cameras, smartwatches, and tracking devices), game consoles, digital book readers, telehealth devices (prescribing drugs based on remote medical monitoring), vehicles or transportation with the function communications (for example, cars, aircraft and ships), as well as a combination of the above devices of various types.

[0243] Communication devices are not limited to portable or mobile devices, and thus include non-portable or fixed devices, appliances, and systems of any type, such as smart home devices (e.g., home appliances, lighting equipment, smart meters, or measuring instruments, and control panels), vending machines, and the Internet of Things ("IoT"; all "things" that can exist on networks).

[0244] In addition to transmitting data via cellular systems, wireless LAN systems, satellite communication systems, and/or the like, communication includes transmitting data via a combination of these systems.

[0245] In addition, communication devices include devices, such as controllers or sensors, to be coupled or associated with a communication device that performs the communication functions described in the present invention. For example, controllers or sensors are included, each of which is configured to generate a control signal and/or a data signal used by a communication device that performs communication device communication functions.

[0246] In addition, communication devices include infrastructure equipment that communicates with the aforementioned non-restrictive devices of various types or that controls these non-restrictive devices of various types, such as base stations, access points, devices of any other kinds, devices and systems.

[0247] The terminal according to the present invention comprises: a circuit that, during operation, configures a first power control parameter corresponding to a first service when a predetermined condition related to a control channel used in transmitting uplink assignment information is satisfied, and configures a second parameter power control corresponding to the second service when the predetermined condition is not satisfied; and a transmission scheme that, in operation, transmits the uplink signal using the transmission power calculated using the first power control parameter or the second power control parameter.

[0248] In the terminal proposed in accordance with the present invention, the predetermined condition is that the payload size of the format used for the control channel is different from the predetermined size.

[0249] In the terminal proposed in accordance with the present invention, the predetermined condition is that the payload size of the format used for the control channel is less than the predetermined size.

[0250] In the terminal proposed in accordance with the present invention, the predetermined condition is that the scrambling sequence used for the control channel is different from the predetermined sequence.

[0251] In the terminal proposed in accordance with the present invention, the predetermined condition is that the control channel is a control channel received at the terminal within a predetermined time period after a signal requesting the first service scheduling is transmitted from the terminal.

[0252] In the terminal proposed in accordance with the present invention, the predetermined condition is that the control channel is the control channel that the terminal receives first after transmitting a signal requesting the scheduling of the first service from the terminal.

[0253] In the terminal proposed in accordance with the present invention, the predetermined condition is that the control channel indicates that the resource to use in the initial uplink transmission is a retransmission in a preconfigured transmission method.

[0254] In the terminal proposed in accordance with the present invention, the predetermined condition is that the time period until the terminal transmits an uplink signal after the terminal receives the control channel is within the predetermined time.

[0255] In the terminal proposed in accordance with the present invention, the predetermined condition is that the number of uplink transmission symbols indicated in the control channel is less than or equal to the predetermined value.

[0256] In the terminal proposed in accordance with the present invention, the predetermined condition is that the control channel detection period in the terminal is less than or equal to the predetermined value.

[0257] In the terminal proposed in accordance with the present invention, the predetermined condition is that the modulation index and coding scheme table used in the control channel is different from the predetermined table.

[0258] In the terminal proposed in accordance with the present invention, the predetermined condition is that the uplink control information included in the uplink signal is a response signal to the downlink data of the first service.

[0259] In the terminal proposed in accordance with the present invention, the predetermined condition is that the time period until the terminal transmits an uplink signal including a response signal to the downlink data after the terminal receives the downlink data is in within the specified time.

[0260] In the terminal proposed in accordance with the present invention, the predetermined condition is that the uplink control information included in the uplink signal is channel state information calculated using a target error rate that is less than or equal to a predetermined threshold value.

[0261] In the terminal proposed in accordance with the present invention, the total error rate of the downlink data and the downlink data response signal is constant, and the predetermined condition is that the uplink control information included in the uplink signal is the response signal to the downstream data of the second service.

[0262] In the terminal proposed in accordance with the present invention, the predetermined condition is that the amount of uplink control information resources included in the uplink signal is equal to or greater than the predetermined threshold.

[0262] In the terminal proposed in accordance with the present invention, the predetermined condition is that the ratio of the resource amount of the uplink control information included in the uplink signal to the resource amount of the entire uplink signal is greater than the predetermined threshold.

[0264] In the terminal proposed in accordance with the present invention, the transmit power calculated using the first power control parameter is greater than the transmit power calculated using the second power control parameter.

[0265] A transmission method proposed in accordance with the present invention includes: configuring a first power control parameter corresponding to a first service when a predetermined condition related to a control channel used in transmitting uplink signal assignment information is satisfied, and configuring a second parameter power control corresponding to the second service when the predetermined condition is not satisfied; and transmitting the uplink signal using the transmit power calculated using the first power control parameter or the second power control parameter.

[0266] Japanese Patent Application No. 2018-090120, filed on May 8, 2018, and Japanese Patent Application No. 2018-135011, filed on July 18, 2018, each of which includes a description, drawings, and an abstract, are fully incorporated herein. application by reference.

Industrial Applicability

[0267] One embodiment of the present invention is useful in mobile communication systems.

List of reference positions

[0268]

100, 300, 400 Terminal

101, 205 Antenna

102, 206 Receiver

103, 207 Demodulator/Decoder

104, 304 PC parameter controller

105, 402 Transmission power calculator

106 Data Generator

107, 203, 302 Encoder/modulator

108 Resource allocator

109, 204 Transmitter

200 base station

201 Scheduler

202 Control information generator

301, 401 UCI generator

303 Multiplexer

Claims (52)

1. Communication terminal, containing: a receiver that, during operation, receives data of a control channel used to transmit information for assigning an uplink signal and does not include an SRS Resource Indicator (SRI) field and does not explicitly indicate the type of service and the power control parameter; and a circuit that, during operation, calculates a transmission power using a power control parameter that is dynamically configured based on a predetermined condition related to the control channel; and a transmitter that, during operation, transmits an uplink signal using the computed transmit power. 2. The terminal of claim 1, wherein said predetermined condition is that the payload size of the format to be used for the control channel is different from the predetermined size. 3. The terminal of claim 1, wherein said predetermined condition is that the payload size of the format to be used for the control channel is less than the predetermined size. 4. The terminal of claim 1, wherein said predetermined condition is that the scrambling sequence to be used for the control channel is different from the predetermined sequence. 5. The terminal of claim 1, wherein said predetermined condition is that the control channel is a control channel received at the terminal within a predetermined period of time after the terminal transmits a signal requesting scheduling of ultra-reliable low latency communication (URLLC). 6. The terminal of claim 1, wherein said predetermined condition is that the control channel is the control channel that the terminal receives first after transmitting a signal requesting URLLC scheduling from the terminal. 7. The terminal of claim 1, wherein said predetermined condition is that the control channel indicates that the resource to use in the initial transmission of the uplink signal is a retransmission in a preconfigured transmission method. 8. The terminal of claim 1, wherein said predetermined condition is that the time period until the terminal transmits an uplink signal after the terminal receives the control channel is within the predetermined time. 9. The terminal of claim 1, wherein said predetermined condition is that the number of uplink transmission symbols specified in the control channel is less than or equal to a predetermined value. 10. The terminal of claim 1, wherein said predetermined condition is that the control channel detection period in the terminal is less than or equal to a predetermined value. 11. The terminal of claim 1, wherein said predetermined condition is that the modulation and coding scheme table to be used in the control channel is different from the predetermined table. 12. The terminal of claim 1, wherein said predetermined condition is that the period of time until the terminal transmits an uplink signal including a response signal to downlink data after the terminal has received the downlink data is within a predetermined time . 13. The terminal of claim 1, wherein at least two power control parameters are provided and one of them is set based on said predetermined condition. 14. The terminal of claim 1, wherein the type of service includes one of ultra-reliable low latency communications (URLLC) and eMBB. 15. Base station, comprising: a transmitter that, during operation, transmits data of a control channel used in transmitting information for assigning an uplink signal, and does not include an SRS Resource Indicator (SRI) field, and does not explicitly indicate the type of service and the power control parameter; and a receiver that, during operation, receives an uplink signal transmitted using a transmit power that is calculated using a power control parameter, wherein said power control parameter is set dynamically based on a predetermined condition related to the control channel. 16. The base station of claim 15, wherein said predetermined condition is that the payload size of the format used for the control channel is different from the predetermined size. 17. The base station of claim 15, wherein said predetermined condition is that the payload size of the format used for the control channel is less than the predetermined size. 18. The base station of claim 15, wherein said predetermined condition is that the scrambling sequence used for the control channel is different from the predetermined sequence. 19. The base station of claim 15, wherein said predetermined condition is that the control channel is a control channel received at the terminal within a predetermined period of time after a signal requesting URLLC scheduling is transmitted from the terminal. 20. The base station of claim 15, wherein said predetermined condition is that the control channel is the control channel that the terminal first receives after transmitting a signal requesting URLLC scheduling from the terminal. 21. The base station of claim 15, wherein said predetermined condition is that the control channel indicates that the resource to use in the initial uplink transmission is a retransmission in a preconfigured transmission method. 22. The base station of claim 15, wherein said predetermined condition is that the time period until the terminal transmits an uplink signal after the terminal receives the control channel is within the predetermined time. 23. The base station of claim 15, wherein said predetermined condition is that the number of uplink transmission symbols specified in the control channel is less than or equal to a predetermined value. 24. The base station of claim 15, wherein said predetermined condition is that the terminal control channel acquisition period is less than or equal to a predetermined value. 25. The base station of claim 15, wherein said predetermined condition is that the modulation and coding scheme table used in the control channel is different from the predetermined table. 26. The base station of claim 15, wherein said predetermined condition is that the time period until the terminal transmits an uplink signal including a response signal to downlink data after the terminal receives the downlink data is within specified time. 27. The base station of claim 15, wherein at least two power control parameters are provided and one of them is set based on a predetermined condition. 28. The base station of claim 15, wherein the type of service includes one of ultra-reliable low latency communications (URLLC) and eMBB. 29. The method of communication, including: receiving control channel data used for transmitting information for uplink assignment and not containing an SRS Resource Indicator (SRI) field, and not explicitly specifying the type of service and power control parameter; calculating transmission power using a power control parameter that is dynamically configured based on a predetermined condition related to the control channel; and transmitting the uplink signal using the computed transmit power. 30. Communication method, including: transmitting data of a control channel used for transmitting information for assigning an uplink signal, and not containing an SRS Resource Indicator (SRI) field, and not explicitly indicating the type of service and the power control parameter; receiving an uplink signal transmitted using a transmit power that is calculated using a power control parameter, wherein said power control parameter is set dynamically based on a predetermined condition related to the control channel. 31. Integrated circuit control process, which includes the following steps: receiving data of a control channel used for transmitting information for assigning an uplink signal and not containing an SRS Resource Indicator (SRI) field and not explicitly indicating a service type and a power control parameter; calculating transmission power using a power control parameter that is dynamically configured based on a determined condition related to the control channel; and transmitting the uplink signal using the computed transmit power. 32. Integrated circuit control process, which includes the following steps: transmitting data of a control channel used for transmitting information for assigning an uplink signal, and not containing an SRS Resource Indicator (SRI) field, and not explicitly indicating the type of service and the power control parameter; and receiving an uplink signal transmitted using a transmit power that is calculated using a power control parameter, wherein said power control parameter is set dynamically based on a predetermined condition related to the control channel.

Images