Base station, communication method and integrated circuit

Abstract

To achieve appropriate wireless communication processing according to required conditions.SOLUTION: A terminal includes a control circuit that determines at least one uplink signal to be transmitted in a certain transmission resource in the time domain among a plurality of uplink signals based on information on the priority of the plurality of uplink signals, and a transmission circuit that transmits the determined uplink signal in the transmission resource.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a base station, a communication method, and an integrated circuit. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has completed the Release 15 NR (New Radio access technology) specification for 5G (5th Generation mobile communication systems). NR supports functions that realize Ultra Reliable and Low Latency Communication (URLLC) in addition to high speed and large capacity, which are the basic requirements for enhanced Mobile Broadband (eMBB). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] RP-190726, “New WID: Physical Layer Enhancements for NR Ultra-Reliable and Low Latency Communication (URLLC),” Huawei, HiSilicon, RAN#83 [Non-patent document 2] RP-190728, “New WID: Support of NR Industrial Internet of Things (IoT),” Nokia, Nokia Shanghai Bell, RAN#83 [Non-patent document 3] 3GPP TS38.211 V15.6.0, “3GPP TSG-RAN NR Physical channels and modulation (Release 15),” June 2019.

Non-licensed Document 4

Non-licensed Document 5

Non-licensed Document 6

Non-licensed Document 7

Non-licensed Document 8

Non-licensed literature 9

Non-licensed literature 10

[0004] However, there is room for further consideration regarding appropriate wireless communication processing according to required conditions.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a base station, a communication method, and an integrated circuit that can perform appropriate wireless communication processing according to required conditions. [Means for solving the problem]

[0006] A terminal according to one embodiment of the present disclosure includes a control circuit that determines, based on information regarding the priorities of a plurality of uplink signals, at least one uplink signal to be transmitted in a certain transmission resource in the time domain from among the plurality of uplink signals, and a transmission circuit that transmits the determined uplink signal in the transmission resource.

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

[0008] According to an embodiment of the present disclosure, it is possible to realize appropriate wireless communication processing according to required conditions.

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of uplink signal combinations in a scenario where transmission resources overlap in uplink transmissions. [Figure 2] Block diagram showing an example of the configuration of a part of a terminal [Figure 3] Block diagram showing an example of the configuration of a base station [Figure 4] Block diagram showing an example of a terminal configuration [Figure 5] FIG. 1 shows an example of an instruction from the medium access control (MAC) layer to the PHY layer in a scheduling request (SR) transmission. [Figure 6] 1 is a flowchart showing an example of terminal operation according to terminal operation 1. [Figure 7] FIG. 10 is a diagram showing an example of an instruction from the MAC layer to the physical (PHY) layer related to terminal operation 1. [Figure 8] FIG. 1 is a diagram showing an example of correspondence between the priority of a logical channel and the priority of a scheduling request (SR) in a PHY layer. [Figure 9] FIG. 10 is a diagram showing an example of association between logical channels, logical channel priorities, and SR resource IDs. [Figure 10] FIG. 1 is a diagram showing an example of the association between logical channels, logical channel priorities, and SR resource IDs, and the priority of SRs. [Figure 11] An example of SchedulingRequestId IE [Figure 12] FIG. 10 is a diagram showing an example of an instruction from a gNB to a UE (PHY layer) related to terminal operation 1. [Figure 13] 1 is a flowchart showing an example of terminal operation according to terminal operation 1. [Figure 14] A diagram showing an example of the correspondence between priority indicators and logical channel priorities. [Figure 15] A diagram showing an example of the correspondence between priority indicators and logical channel priorities. [Figure 16] FIG. 10 is a diagram showing an example of an instruction from a gNB to a UE (PHY layer) related to terminal operation 1. [Figure 17] 1 is a flowchart showing an example of terminal operation according to terminal operation 1. [Figure 18] FIG. 1 is a diagram showing an example of correspondence between logical channel priorities and channel state information (CSI) priorities. [Figure 19] FIG. 10 is a diagram showing an example of an instruction from the MAC layer to the PHY layer related to terminal operation 1. [Figure 20] 1 is a flowchart showing an example of terminal operation according to terminal operation 1. [Figure 21] 10 is a flowchart showing an example of terminal operation according to terminal operation 2. [Figure 22] 10 is a flowchart showing an example of terminal operation relating to terminal operation 3. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0012] In NR, a terminal (also referred to as User Equipment (UE)) is assumed to support multiple services with different requirements (e.g., eMBB and URLLC). For example, in uplink transmissions from a terminal, transmission resources (in other words, uplink resources or transmission periods) for services with different requirements may overlap (or collide) in the time domain (see, for example, Non-Patent Documents 1 and 2).

[0013] Below, cases (also referred to as scenarios) in which transmission resources corresponding to services with different requirements in a terminal overlap in the time domain will be described.

[0014] <Scenario 1: UL control / control resource collision> A terminal transmits uplink control information (UCI) to a base station (also referred to as a gNB, for example) using an uplink control channel (for example, a PUCCH: Physical Uplink Control Channel). The UCI includes, for example, a response signal (for example, called an Acknowledgement / Negative Acknowledgement (ACK / NACK) or HARQ-ACK) indicating an error detection result of downlink data (for example, a PDSCH: Physical Downlink Shared Channel), downlink channel state information (for example, CSI: Channel State Information), and an uplink radio resource allocation request (for example, SR: Scheduling Request).

[0015] Furthermore, the terminal can transmit the CSI using an uplink data channel (for example, a Physical Uplink Shared Channel (PUSCH)).

[0016] In Scenario 1, UCIs for multiple services with different requirements may occur at the same time (e.g., simultaneously) in a terminal. In this case, resources allocated to the UCIs for the multiple services with different requirements may overlap in the time domain.

[0017] <Scenario 2:UL data / control resource collision> The terminal transmits uplink data to the base station using, for example, the PUSCH.

[0018] In Scenario 2, uplink data and UCI may occur at the same time (e.g., simultaneously) for services with different requirements in a terminal. In this case, resources allocated to uplink data and resources allocated to UCI may overlap in the time domain.

[0019] <Scenario 3: UL data / data resource collision> The terminal transmits uplink data to the base station using, for example, the PUSCH.

[0020] In Scenario 3, uplink data for multiple services with different requirements may occur at the same time (e.g., simultaneously) in the terminal. In this case, resources allocated to the uplink data for the multiple services with different requirements may overlap in the time domain.

[0021] Above, we have explained Scenarios 1 to 3.

[0022] Fig. 1 shows an example of combinations of uplink signals (e.g., 21 combinations not hatched in Fig. 1) in scenarios where overlapping of uplink transmission resources occurs (e.g., including Scenarios 1 to 3). Note that Fig. 1 shows two services (e.g., URLLC and eMBB) as examples of services having different requirements.

[0023] In the above-mentioned scenario, if a terminal has the capability to transmit signals of multiple channels simultaneously (e.g., simultaneous transmission of multiple PUCCHs or PUSCHs, or transmission of both PUCCHs and PUSCHs), the terminal may transmit signals for services with different requirements simultaneously without considering their impact on each other.

[0024] On the other hand, if the terminal does not have the capability to simultaneously transmit signals of multiple channels, the terminal transmits signals of some of the multiple channels (either one in the above-mentioned scenario) and does not transmit signals of the other channels (in other words, this is called dropping or not transmitting). Alternatively, the terminal controls the transmission power of the multiple channels.

[0025] There is room for discussion regarding terminal operation when the terminal does not have the capability to simultaneously transmit signals of multiple channels. For example, there is room for discussion regarding terminal operation based on a priority (also referred to as a priority level) for determining which uplink signal (e.g., uplink data or UCI) the terminal will transmit.

[0026] Hereinafter, as an example, the operation of a terminal in the case where multiple uplink transmissions in NR Release 15 overlap in the time domain will be described (see, for example, Non-Patent Document 3).

[0027] [1]: When the PUCCH resource for transmitting an SR and the PUCCH resource for transmitting an ACK / NACK from a terminal overlap in the time domain. <1-1> If the PUCCH resources configured for a terminal to transmit an ACK / NACK using PUCCH format 0 overlap in the time domain with the PUCCH resources configured for a terminal to transmit an SR, the terminal, for example, multiplexes the ACK / NACK and SR onto the PUCCH and transmits them.

[0028] At this time, the PUCCH resource onto which the ACK / NACK and the SR are multiplexed is determined based on, for example, the PUCCH resource allocated for transmitting the ACK / NACK (see, for example, Non-Patent Document 3 or 5).

[0029] <1-2> If the format of the PUCCH resource configured for a terminal to transmit an SR is PUCCH format 1, and the PUCCH resource configured for transmitting an ACK / NACK using PUCCH format 1 overlaps in the time domain with the PUCCH resource configured for the terminal to transmit an SR, the terminal, for example, multiplexes the ACK / NACK and SR into the PUCCH and transmits them.

[0030] At this time, for example, in the case of positive SR (in other words, with SR), the terminal transmits ACK / NACK using the PUCCH allocated to SR. On the other hand, for example, in the case of negative SR (in other words, without SR), the terminal transmits ACK / NACK using the PUCCH allocated to ACK / NACK. In this case, the base station determines whether SR is present (in other words, whether it is positive SR or negative SR) based on the PUCCH resource on which the ACK / NACK is actually transmitted (for example, see Non-Patent Document 5).

[0031] <1-3> If the format of the PUCCH resource configured for a terminal to transmit an SR is PUCCH format 0, and the PUCCH resource configured for transmitting an ACK / NACK using PUCCH format 1 overlaps in the time domain with the PUCCH resource configured for transmitting an SR, the terminal, for example, drops the transmission of the SR and transmits the ACK / NACK using the PUCCH resource allocated for the ACK / NACK (see, for example, non-patent document 5).

[0032] <1-4> If a PUCCH resource configured to transmit an ACK / NACK using any of PUCCH formats 2, 3, or 4 overlaps in the time domain with a PUCCH resource configured to transmit an SR, the terminal, for example, multiplexes the ACK / NACK and SR into the PUCCH and transmits them.

[0033] At this time, the PUCCH resource onto which the ACK / NACK and SRS are multiplexed is determined based on, for example, the PUCCH allocated for transmitting the ACK / NACK. Also, the terminal transmits, for example, a bit string in which a bit string indicating the presence or absence of an SR is added to the end of the ACK / NACK bit string, on the PUCCH (see, for example, Non-Patent Document 4 or 5).

[0034] [2]: When the PUCCH resource where the terminal transmits the SR overlaps with the PUCCH resource where the terminal transmits the CSI in the time domain. For example, the terminal multiplexes the CSI and SR into the PUCCH and transmits the multiplexed CSI and SR.

[0035] At this time, the PUCCH resource onto which the CSI and SR are multiplexed is determined based on, for example, the PUCCH resource allocated for transmitting the CSI. Also, the terminal transmits, on the PUCCH, a bit string in which a bit string indicating the presence or absence of an SR is added to the beginning of the CSI bit string (see, for example, Non-Patent Document 4 or 5).

[0036] [3] When the PUCCH resource for transmitting ACK / NACK and the PUCCH resource for transmitting CSI overlap in the time domain. In the terminal, for example, whether simultaneous transmission of ACK / NACK and CSI is possible is configured in advance by a parameter "simultaneousHARQ-ACK-CSI" of an upper layer. If "simultaneousHARQ-ACK-CSI" is configured to allow simultaneous transmission of ACK / NACK and CSI, the terminal, for example, multiplexes the ACK / NACK and CSI onto a PUCCH and transmits them. At this time, the PUCCH resource onto which the ACK / NACK and CSI are multiplexed is determined, for example, based on the PUCCH allocated for transmitting the ACK / NACK.

[0037] On the other hand, if "simultaneousHARQ-ACK-CSI" is configured to not allow simultaneous transmission of ACK / NACK and CSI, or if "simultaneousHARQ-ACK-CSI" is not configured, the terminal, for example, drops the transmission of CSI and transmits ACK / NACK using the PUCCH allocated to ACK / NACK (see, for example, Non-Patent Document 5).

[0038] [4]: When the PUCCH resource on which the terminal transmits SR and the PUSCH resource on which the terminal transmits uplink data overlap in the time domain For example, the terminal drops the SR transmission and transmits uplink data (see, for example, Non-Patent Document 5).

[0039] [5]: When the PUCCH resource in which the terminal transmits ACK / NACK or CSI overlaps with the PUSCH resource in which the terminal transmits uplink data in the time domain. For example, the terminal multiplexes ACK / NACK or CSI and uplink data into a PUSCH and transmits the multiplexed data.

[0040] At this time, the PUSCH in which ACK / NACK or CSI and uplink data are multiplexed is determined based on the PUSCH resources allocated for transmitting the uplink data (see, for example, Non-Patent Document 5).

[0041] The above describes the operation of a terminal when multiple uplink transmissions in NR Release 15 overlap in the time domain.

[0042] The terminal operation in the above-mentioned NR Release 15 does not sufficiently consider the terminal operation regarding uplink signals with different requirements.

[0043] For example, in the above-described terminal operation <1-3>, there may be a case where an opportunity to transmit an SR for URLLC traffic requiring high reliability or low latency in PUCCH format 0 overlaps in the time domain with PUCCH format 1 resources for transmitting ACK / NACK for eMBB traffic, which has a lower priority than the URLLC traffic. In this case, according to the above-described terminal operation <1-3>, the terminal drops the SR for the URLLC traffic (in other words, does not transmit the SR). Therefore, the terminal transmits the SR at the next transmission opportunity, which may increase the delay in URLLC, which requires low latency.

[0044] Furthermore, in the terminal operation [4] described above, there may be a case where an opportunity to transmit an SR for URLLC traffic overlaps in the time domain with a PUSCH for transmitting uplink data for eMBB traffic. In this case, according to the terminal operation [4] described above, the terminal drops the SR for URLLC traffic (in other words, does not transmit the SR). Therefore, since the terminal transmits the SR at the next transmission opportunity, delay may increase in URLLC, which requires low delay.

[0045] Thus, in terminal operation in NR Release 15, uplink signals with different requirements may result in increased delay, for example, signals (e.g., SR) for URLLC traffic that require high reliability or low latency may not be transmitted.

[0046] Furthermore, for example, when a terminal multiplexes multiple UCIs onto a PUCCH and transmits them, or when a terminal multiplexes UCI onto a PUSCH and transmits them, the terminal can collectively transmit UCI and uplink data whose resources overlap in the time domain. In this case, for example, the terminal may multiplex UCI for URLLC traffic that requires high reliability or low latency onto a PUCCH or PUSCH for eMBB traffic that has a lower priority than the URLLC traffic and transmit the UCI. In this case, the resources and radio parameters allocated to the PUCCH or PUSCH onto which UCI is multiplexed may not satisfy the requirements of URLLC.

[0047] Furthermore, for example, when a terminal multiplexes UCI for eMBB traffic onto a PUCCH or PUSCH for URLLC traffic that requires high reliability or low latency and transmits the multiplexed UCI, the transmission characteristics of the PUCCH or PUSCH for URLLC traffic may be degraded due to the increase in the number of transmission bits caused by multiplexing UCI for eMBB traffic.

[0048] Therefore, in one embodiment of the present disclosure, the operation of a terminal when channels corresponding to services with different requirements overlap in the time domain will be described.

[0049] For example, in one embodiment of the present disclosure, in a scenario in which transmissions of uplink signals (e.g., UCI or uplink data) having different requirements overlap in the time domain, the terminal determines a priority of the uplink signal and transmits at least one of the UCI and the uplink data based on the priority.

[0050] For example, the terminal determines the priority of UCI or uplink data in the physical (PHY) layer. For example, when uplink signal transmissions overlap in the time domain, the terminal compares the priority of each UCI or uplink data in the PHY layer (also referred to as the physical layer) and preferentially transmits UCI or uplink data with a higher priority. Alternatively, the terminal may multiplex UCI with a lower priority into an uplink channel (e.g., PUCCH or PUSCH) that transmits an uplink signal with a higher priority, and transmit the multiplexed UCI.

[0051] According to one embodiment of the present disclosure, even when an uplink resource for transmitting a high-priority uplink signal such as URLLC overlaps with an uplink resource for transmitting a low-priority uplink signal such as eMBB in the time domain, the terminal can transmit UCI or uplink data while suppressing an increase in delay and a deterioration in transmission characteristics.

[0052] An embodiment of the present disclosure will be described in detail below.

[0053] [Communication System Overview] The communication system according to an embodiment of the present disclosure includes a base station 100 and a terminal 200.

[0054] 2 is a block diagram illustrating a configuration example of a portion of terminal 200 according to an embodiment of the present disclosure. In terminal 200 illustrated in FIG. 2, control unit 205 (e.g., corresponding to a control circuit) determines the priority of each of a first uplink signal and a second uplink signal, the resource allocations of which overlap in the time domain. Transmitting unit 209 (e.g., corresponding to a transmitting circuit) transmits at least one of the first uplink signal and the second uplink signal based on the priority.

[0055] [Base station configuration] 3 is a block diagram illustrating a configuration example of a base station 100 according to an embodiment of the present disclosure. In FIG. 3, the base station 100 includes a control unit 101, a higher control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0056] For example, the control unit 101 determines configuration information including higher layer parameters for the terminal 200 (for example, referred to as Radio Resource Control (RRC) configuration information), and outputs the determined RRC configuration information to the higher control signal generation unit 102 and extraction unit 109.

[0057] The RRC setting information may include, for example, information regarding the setting of logical channels (hereinafter referred to as logical channel setting information), information regarding the setting of SR resources (hereinafter referred to as SR resource setting information), information for DCI reception, information regarding the setting of ACK / NACK transmission (hereinafter referred to as ACK / NACK transmission setting information), information regarding the setting of CSI transmission (hereinafter referred to as CSI transmission setting information), and information regarding the setting of PUSCH transmission (hereinafter referred to as PUSCH transmission setting information).

[0058] Furthermore, the RRC configuration information may include, for example, information for determining the priority of an uplink signal (e.g., UCI and uplink data) in the PHY layer. The information for determining the priority of the uplink signal may include, for example, information on the association (described later) between the priority of a logical channel and the priority of the uplink signal in the PHY layer.

[0059] Furthermore, the control unit 101 determines information related to a downlink signal for transmitting downlink data (e.g., PDSCH), an upper control signal, or downlink control information (e.g., DCI). The information related to the downlink signal may include, for example, information such as a modulation and coding scheme (MCS) and radio resource allocation. The control unit 101 outputs the determined information to, for example, the encoding unit 104, the modulation unit 105, and the signal allocation unit 106. Furthermore, the control unit 101 outputs the information related to the downlink signal to the downlink control information generation unit 103.

[0060] Furthermore, the control unit 101 determines information for terminal 200 to transmit an ACK / NACK for downlink data, and outputs the determined information to the downlink control information generation unit 103 and the extraction unit 109. The information for transmitting the ACK / NACK may include, for example, information on PUCCH resources. The information for transmitting the ACK / NACK may also include, for example, information for determining the priority of the ACK / NACK in the PHY layer, which will be described later.

[0061] Furthermore, control section 101 may, for example, determine information for terminal 200 to transmit CSI, and output the determined information to downlink control information generation section 103 and extraction section 109. The information for transmitting CSI may include, for example, a flag for triggering CSI transmission or information on PUSCH resources.

[0062] Furthermore, the control unit 101 determines information for the terminal 200 to transmit uplink data, and outputs the determined information to the downlink control information generation unit 103, the extraction unit 109, and the decoding unit 111. The information for transmitting uplink data may include, for example, a coding and modulation scheme and radio resource allocation.

[0063] The higher control signal generating section 102 generates a higher layer control signal bit sequence based on information received as input from the control section 101 (for example, RRC setting information), and outputs the higher layer control signal bit sequence to the encoding section 104.

[0064] The downlink control information generating unit 103 generates a downlink control information (for example, DCI) bit string based on information input from the control unit 101, and outputs the generated DCI bit string to the encoding unit 104. Note that control information may be transmitted to multiple terminals. For this reason, the downlink control information generating unit 103 may scramble the PDCCH that transmits the DCI using identification information specific to the terminal. The identification information specific to the terminal may be, for example, any of information such as a C-RNTI (Cell Radio Network Temporary Identifier), an MCS-C-RNTI (Modulation and Coding Scheme C-RNTI), and an RNTI introduced for URLLC, or may be other information (for example, another RNTI).

[0065] The encoding unit 104 encodes downlink data (which may also be referred to as downlink UP data, for example), a bit string input from the higher control signal generating unit 102, or a DCI bit string input from the downlink control information generating unit 103, based on information input from the control unit 101 (for example, information related to the coding rate). The encoding unit 104 outputs the encoded bit string to the modulation unit 105.

[0066] The modulation unit 105 modulates the coded bit sequence input from the coding unit 104, for example, based on information input from the control unit 101 (for example, information regarding the modulation method), and outputs the modulated signal (for example, a symbol sequence) to the signal allocation unit 106.

[0067] The signal allocation unit 106 maps the symbol sequence (including, for example, downlink data or a control signal) input from the modulation unit 105 to the radio resource based on the information indicating the radio resource input from the control unit 101. The signal allocation unit 106 outputs the downlink signal onto which the signal has been mapped to the transmission unit 107.

[0068] Transmitting unit 107 performs a transmission waveform generation process such as Orthogonal Frequency Division Multiplexing (OFDM) on the signal input from signal allocating unit 106. In addition, in the case of OFDM transmission that adds a cyclic prefix (CP), transmitting unit 107 performs an Inverse Fast Fourier Transform (IFFT) process on the signal and adds a CP to the signal after IFFT. Transmitting unit 107 also performs RF processing such as D / A conversion and up-conversion on the signal, and transmits the radio signal to terminal 200 via an antenna.

[0069] The receiving unit 108 performs RF processing such as downconvert or A / D conversion on the uplink signal received from the terminal 200 via the antenna. In addition, in the case of OFDM transmission, the receiving unit 108 performs fast Fourier transform (FFT) processing on the received signal and outputs the resulting frequency domain signal to the extracting unit 109.

[0070] The extraction unit 109 determines information related to an uplink signal to be transmitted by the terminal 200 (for example, information related to an uplink signal with a high priority) based on information input from the control unit 101. Based on the determined information, the extraction unit 109 extracts, for example, a radio resource portion in which UCI or uplink data, or both, are transmitted from the received signal input from the receiving unit 108, and outputs the extracted radio resource portion to the demodulation unit 110.

[0071] The demodulation unit 110 demodulates at least one of the UCI and the uplink data based on the signal (radio resource portion) input from the extraction unit 109, and outputs the demodulation result to the decoding unit 111.

[0072] The decoding unit 111 performs error correction decoding on at least one of the UCI and the uplink data based on the information input from the control unit 101 and the demodulation result input from the demodulation unit 110, and obtains a decoded received bit sequence. Note that the decoding unit 111 does not need to perform error correction decoding on UCI that is transmitted without being subjected to error correction coding.

[0073] [Device configuration] Fig. 4 is a block diagram showing an example configuration of terminal 200 according to an embodiment of the present disclosure. For example, the configuration of terminal 200 shown in Fig. 4 is an example configuration of a PHY layer. In Fig. 4, terminal 200 includes receiving unit 201, extracting unit 202, demodulating unit 203, decoding unit 204, control unit 205, encoding unit 206, modulating unit 207, signal allocating unit 208, and transmitting unit 209.

[0074] The receiver 201 receives a downlink signal (for example, downlink data or downlink control information) from the base station 100 via an antenna, and performs RF processing such as downconvert or A / D conversion on the radio received signal to obtain a received signal (baseband signal). When receiving an OFDM signal, the receiver 201 performs FFT processing on the received signal to convert it into the frequency domain. The receiver 201 outputs the received signal to the extractor 202.

[0075] Based on the information on the radio resource of the downlink control information input from the control unit 205, the extraction unit 202 extracts a radio resource portion that may include downlink control information from the received signal input from the receiving unit 201, and outputs the extracted radio resource portion to the demodulation unit 203. Furthermore, based on the information on the radio resource of the data signal input from the control unit 205, the extraction unit 202 extracts a radio resource portion that includes downlink data, and outputs the extracted radio resource portion to the demodulation unit 203.

[0076] Demodulation section 203 demodulates the signal input from extraction section 202 and outputs the demodulation result to decoding section 204 .

[0077] The decoding unit 204 performs error correction decoding on the demodulation result input from the demodulation unit 203, and obtains, for example, downlink reception data, an upper layer control signal, or downlink control information. The decoding unit 204 outputs the upper layer control signal and the downlink control information to the control unit 205, and outputs the downlink reception data. The decoding unit 204 may also generate an ACK / NACK based on the decoding result of the downlink reception data. The ACK / NACK may be output to, for example, the coding unit 206.

[0078] The control unit 205 determines, for example, the priority of an uplink signal (e.g., UCI and uplink data) in the PHY layer. The control unit 205 may determine the priority of the uplink signal based on at least one of, for example, information on the priority of the uplink signal obtained from the MAC layer (also referred to as a MAC entity), information on the priority of the uplink signal included in the upper layer control signal input from the decoding unit 204, and information on the priority of the uplink signal (e.g., ACK / NACK) indicated in the downlink control information. Hereinafter, the process (or operation) of determining the priority of the uplink signal may be referred to, for example, as "terminal operation 1."

[0079] Furthermore, when transmissions of multiple uplink signals (in other words, transmission resources or transmission periods) overlap in the time domain, the control unit 205, for example, compares the priorities of the multiple uplink signals and determines the priorities among the multiple uplink signals based on the comparison results (hereinafter, this may be referred to as "terminal operation 2"). Furthermore, the control unit 205 determines the uplink signal to actually transmit based on the priorities among the multiple uplink signals (hereinafter, this may be referred to as "terminal operation 3"). The control unit 205 outputs the determination result to, for example, the coding unit 206, the modulation unit 207, and the signal allocation unit 208.

[0080] An example of terminal operation 1, terminal operation 2, and terminal operation 3 in the terminal 200 will be described later.

[0081] Furthermore, the control unit 205 may output, for example, information included in the higher layer control signal to the MAC layer. The information output to the MAC layer may include, for example, RRC configuration information and downlink control information.

[0082] Furthermore, the control unit 205 determines information related to the transmission of uplink signals and outputs the determined information to the encoding unit 206 and the signal allocation unit 208. Furthermore, the control unit 205 determines information related to the reception of downlink signals and outputs the determined information to the extraction unit 202.

[0083] Encoding section 206 encodes the uplink data, SR, CSI, or ACK / NACK for the downlink data based on the information input from control section 205, and outputs the encoded bit string to modulation section 207. Note that terminal 200 may transmit UCI (for example, SR or ACK / NACK) without performing error correction coding in encoding section 206.

[0084] Modulation section 207 modulates the coded bit sequence input from coding section 206 based on information input from control section 205 , and outputs the modulated signal (symbol sequence) to signal allocation section 208 .

[0085] The signal allocation unit 208 maps the signal input from the modulation unit 207 to radio resources based on information input from the control unit 205, and outputs the uplink signal onto which the signal has been mapped to the transmission unit 209.

[0086] Transmitting unit 209 generates a transmission signal waveform, such as OFDM, for the signal input from signal allocating unit 208. Furthermore, in the case of OFDM transmission using a CP, transmitting unit 209 performs IFFT processing on the signal and adds a CP to the signal after IFFT. Alternatively, in the case of generating a single-carrier waveform, transmitting unit 209 may have a DFT (Discrete Fourier Transform) unit added after modulating unit 207 or before signal allocating unit 208 (not shown). Furthermore, transmitting unit 209 performs RF processing, such as D / A conversion and up-conversion, on the transmission signal, and transmits the radio signal to base station 100 via an antenna.

[0087] [Example of Operation of Base Station 100 and Terminal 200] An example of the operation of base station 100 and terminal 200 having the above configuration will be described.

[0088] Below, the terminal operation 1, terminal operation 2, and terminal operation 3 of the terminal 200 described above will be explained respectively.

[0089] [Terminal operation 1] In terminal operation 1, terminal 200 determines the priority of an uplink signal (for example, UCI or uplink data) in the PHY layer.

[0090] Hereinafter, as an example, a method for determining the priority of UCI such as SR, ACK / NACK, and CSI, and uplink data (for example, PUSCH) in the PHY layer will be described.

[0091] <Terminal Operation 1:SR> An example of a method for determining the priority in the PHY layer of an SR transmitted by terminal 200 will be described.

[0092] SR is UCI that is transmitted when terminal 200 requests allocation of resources for transmitting uplink data to base station 100 (in other words, requests transmission on UL-SCH), for example.

[0093] Terminal 200 has a function of reporting the status of a transmission buffer corresponding to a logical channel for uplink data, for example, in the MAC layer. The function of reporting the status of a transmission buffer is sometimes called a "Buffer Status Report (BSR)."

[0094] When the transmission of a BSR is triggered and radio resources (e.g., PUSCH) for transmitting the BSR are not allocated to terminal 200, for example, as shown in FIG. 5, in terminal 200, the MAC layer instructs the PHY layer to transmit the SR using PUCCH (for example, see Non-Patent Document 6).

[0095] The terminal 200 (for example, the PHY layer) may determine the priority of the SR instructed to be transmitted by the MAC layer using the method described below.

[0096] FIG. 6 is a flowchart showing an example of an operation regarding a terminal operation 1 for determining the priority of an SR.

[0097] For example, terminal 200 acquires (in other words, receives) RRC configuration information from base station 100 (S111). The RRC configuration information may include, for example, SR resource configuration information and logical channel configuration information.

[0098] Terminal 200, for example, acquires information relating to the association between SR priorities of the PHY layer and logical channel priorities (S112). Information relating to the association between SR priorities of the PHY layer and logical channel priorities may be included in, for example, RRC configuration information or may be predefined in a standard. Furthermore, for example, when the number of SR priorities in the PHY layer (in other words, the number of candidates) is the same as the number of logical channel priorities (in other words, the number of candidates), and the priorities of other uplink signals are compared based on the priority of the logical channel, terminal 200 may omit the process of S112.

[0099] The terminal 200 (for example, the MAC layer) triggers the transmission of an SR (in other words, the transmission of a BSR) (S113).

[0100] Terminal 200 determines the priority of the SR in the PHY layer (S114). For example, terminal 200 may determine the priority of the SR based on the priority of the logical channel corresponding to the uplink data. For example, terminal 200 may determine the priority of the SR associated with the priority of the logical channel that triggered the SR in the association between the SR priority in the PHY layer and the priority of the logical channel.

[0101] Next, an example of a method for determining the priority of SR in the PHY layer will be described.

[0102] (Determination method 1: hereinafter referred to as "Terminal Operation SR-1") In terminal operation SR-1, terminal 200 (for example, MAC layer) determines the priority of the SR based on the priority of the logical channel that triggered the SR (or BSR).

[0103] Terminal 200 may obtain information regarding the priority of each logical channel from, for example, RRC configuration information (see, for example, Non-Patent Document 7). In terminal operation SR-1, for example, the priority of a logical channel may use "priority," which is a parameter set in "LogicalChannelConfig IE (Information Element)" in Non-Patent Document 7.

[0104] As shown in Fig. 7, when the MAC layer of terminal 200 triggers an SR (in other words, instructs transmission of an SR), it instructs the PHY layer to transmit an SR using a PUCCH. At this time, as shown in Fig. 7, for example, information indicating the priority of the logical channel that triggered the SR may be notified from the MAC layer to the PHY layer. For example, terminal 200 (PHY layer) may determine the priority of the SR based on the priority of the logical channel that triggered the SR.

[0105] According to the terminal operation SR-1, the terminal 200 can uniquely determine the priority of the SR in the PHY layer based on the priority of the logical channel that triggered the SR.

[0106] In NR, for example, multiple logical channels may correspond to one SR setting (or SR resource). Even in this case, for example, the priority of the logical channel that triggered SR is directly notified from the MAC layer to the PHY layer, so the PHY layer can uniquely determine the SR priority.

[0107] Note that the priority of a logical channel does not have to be notified from the MAC layer to the PHY layer. In this case, for example, terminal 200 may uniquely associate a logical channel (or the priority of the logical channel) with an SR setting (SR resource). Then, terminal 200 may determine the SR priority in the PHY layer based on the priority of the logical channel associated with the SR setting. In this case, for example, it is sufficient that the number of logical channels and the number of SR settings (SR resources) are the same.

[0108] Although the case where information regarding the priority of a logical channel is transmitted from the MAC layer to the PHY layer has been described, this is not limiting. For example, terminal 200 may determine the priority of an SR based on the priority of a logical channel in the MAC layer. Then, the information regarding the priority of the SR may be transmitted from the MAC layer to the PHY layer.

[0109] (Variations of terminal operation SR-1) In NR Release 15, for example, the number of priorities that can be set for a logical channel (in other words, the number of candidates) is 16. For example, the priority of a logical channel is any of 1 to 16, with priority 1 being the highest priority and the priorities decreasing in order (see, for example, Non-Patent Document 7).

[0110] In terminal operation SR-1, terminal 200 may set the priority of the logical channel notified from the MAC layer to the priority of the SR in the PHY layer. In this case, the number of priorities of the logical channel (in other words, the number of candidates) may be the same as the number of priorities of the SR in the PHY layer (in other words, the number of candidates).

[0111] However, the number of SR priorities (in other words, the granularity) at the PHY layer may be different from the number of logical channel priorities.

[0112] For example, the number of SR priorities in the PHY layer may be less than the number of logical channel priorities. Fig. 8 shows an example of association between logical channel priorities and SR priorities in the PHY layer when the number of SR priorities in the PHY layer is less than the number of logical channel priorities. The association between logical channel priorities and SR priorities in the PHY layer may be specified in advance in a standard, for example, or may be set from base station 100 to terminal 200 by RRC. Also, in the example of Fig. 8, the number of SR priorities in the PHY layer is set to 4 (any of 1 to 4), but the number of SR priorities is not limited to 4 and may be another number.

[0113] The number of SR priorities in the PHY layer can be reduced by reducing the number of SR priorities compared to the priorities of logical channels. By reducing the number of SR priorities, it is possible to reduce the overhead of control signals, for example, in priority comparison with ACK / NACK, which will be described later.

[0114] The number of SR priorities in the PHY layer may be greater than the number of logical channel priorities.

[0115] (Determination method 2: hereafter referred to as "Terminal Operation SR-2") In terminal operation SR-2, similar to terminal operation SR-1, terminal 200 (for example, MAC layer) determines the priority of the SR based on the priority of the logical channel that triggered the SR (or BSR).

[0116] Terminal 200 may obtain information regarding the priority of each logical channel from, for example, RRC settings (see, for example, Non-Patent Document 7). In terminal operation SR-2, terminal 200 determines the priority of an SR, for example, based on the priority of a logical channel associated with information regarding resources used for transmitting an SR (for example, an SR resource ID). For example, terminal 200 may determine the priority of an SR in the PHY layer based on "priority," which is a parameter regarding the priority of a logical channel set in "LogicalChannelConfig IE" in Non-Patent Document 7, and "schedulingRequestId," which is a parameter regarding an SR set in "LogicalChannelConfig IE" and "SchedulingRequestResourceConfig IE."

[0117] For example, in terminal 200, when triggering an SR, the MAC layer instructs the PHY layer to transmit the SR using the PUCCH, as shown in Fig. 5. At this time, the MAC layer instructs the PHY layer about an SR resource (for example, SchedulingRequestResourceConfig IE) for transmitting the SR (not shown).

[0118] The terminal 200 (for example, the PHY layer) identifies an "SR resource ID (for example, schedulingRequestId)" corresponding to an SR resource based on the SR resource instructed from the MAC layer. Furthermore, the terminal 200 (for example, the PHY layer) identifies a logical channel to which the SR resource ID of the SR resource instructed from the MAC layer is assigned and the priority of the logical channel based on, for example, the "LogicalChannelConfig IE." Then, the terminal 200 (for example, the PHY layer) may determine the priority of the SR in the PHY layer based on, for example, the priority of the identified logical channel.

[0119] FIG. 9 shows an example of the correspondence between logical channels (for example, logical channel numbers), logical channel priorities, and SR resource IDs related to terminal operation SR-2.

[0120] For example, terminal 200 identifies a logical channel associated with an SR resource ID corresponding to an SR resource instructed from the MAC layer and the priority of the logical channel based on Fig. 9. Then, terminal 200 may determine the priority of the SR based on the priority of the identified logical channel based on Fig. 9.

[0121] In terminal operation SR-2, terminal 200 (e.g., PHY layer) can identify the SR resource and the priority of the logical channel corresponding to the SR resource by obtaining the logical channel setting (e.g., the logical channel number and priority shown in FIG. 9) and the SR resource setting (e.g., the SR resource ID shown in FIG. 9) from the RRC setting.

[0122] In terminal operation SR-2, terminal 200 can determine the priority of SR based on the priority of the identified logical channel without notification of information related to priority from the MAC layer to the PHY layer. In other words, terminal 200 can determine the priority of SR based on the SR resource indicated from the MAC layer to the PHY layer, so there is no need to notify the logical channel that triggered SR (e.g., the priority of the logical channel) every time SR is triggered, as in terminal operation SR-1, for example.

[0123] (Variation 1 of terminal operation SR-2 (hereinafter referred to as terminal operation SR2-1)) In NR, for example, multiple logical channels may correspond to one SR setting (or SR resource). In this case, for example, in terminal 200, information on different priorities of multiple logical channels corresponding to one SR setting may be reported from the MAC layer to the PHY layer.

[0124] In terminal operation SR2-1, when one SR setting (or SR resource) corresponds to multiple logical channels, terminal 200 (e.g., PHY layer) may determine the priority of the SR in the PHY layer based on the priority of one of the multiple logical channels corresponding to the triggered SR resource.

[0125] For example, the terminal 200 may determine the priority of SR in the PHY layer based on the priority of the logical channel with the highest priority among a plurality of logical channels corresponding to the triggered SR resource.

[0126] Fig. 10 shows an example of the correspondence between logical channels, logical channel priorities, and SR resource IDs for terminal operation SR2-1, and the SR priorities in the PHY layer. In Fig. 10, the SR priorities in the PHY layer are determined based on the priority of the logical channel with the highest priority among multiple logical channels. For example, if logical channels with logical channel numbers 9 to 14 correspond to one SR setting (SR resource ID = 2), terminal 200 determines the SR priority based on the higher priority 9 of the priorities 9 and 10 corresponding to logical channel numbers 9 to 14. The same applies to the other logical channel numbers shown in Fig. 10.

[0127] In addition, in the terminal operation SR2-1, the method of determining the priority of the SR in the PHY layer is not limited to a method based on the priority of the logical channel with the highest priority among multiple logical channels. For example, the priority of the SR may be determined based on the priority of any one of multiple logical channels. For example, if the priority of the SR is determined based on the priority of the logical channel with the highest priority among multiple logical channels, for example, in terminal operation 2 or 3 described below, the SR is likely to be assigned a higher priority than other uplink signals (for example, ACK / NACK, CSI, or uplink data).

[0128] According to the terminal operation SR2-1, even when one SR setting corresponds to multiple logical channels, the terminal 200 can uniquely determine the priority of the SR in the PHY layer based on the logical channel corresponding to the SR setting (for example, an SR resource ID).

[0129] (Variation 2 of terminal operation SR-2 (hereinafter referred to as terminal operation SR2-2)) For example, similar to terminal operation SR-1 or a variation of terminal operation SR-1, terminal 200 may set the priority of the logical channel notified from the MAC layer to the priority of the SR in the PHY layer. Alternatively, the number of priorities of the SR in the PHY layer (in other words, the granularity) may be different from the number of priorities of the logical channel.

[0130] For example, the number of SR priorities in the PHY layer may be less than the number of logical channel priorities. The association between the logical channel priorities and the SR priorities in the PHY layer may be, for example, defined in advance in a standard, or may be set from base station 100 to terminal 200 by RRC.

[0131] The number of SR priorities in the PHY layer can be reduced by reducing the number of SR priorities compared to the priorities of logical channels. By reducing the number of SR priorities, it is possible to reduce the overhead of control signals, for example, in priority comparison with ACK / NACK, which will be described later.

[0132] (Determination method 3: hereafter referred to as "Terminal Operation SR-3") In terminal operation SR-3, terminal 200 obtains information on the association between SR resource configuration and SR priority in the PHY layer from the RRC configuration.

[0133] For example, a parameter indicating the priority of SR in the PHY layer may be added to the SchedulingRequestId IE in Non-Patent Document 7. Fig. 11 shows an example of the SchedulingRequestId IE in terminal operation SR-3. As shown in Fig. 11, for example, a parameter (in other words, a field) "priority" indicating the priority of SR is added to the SchedulingRequestId IE.

[0134] For example, in terminal 200, when triggering an SR, the MAC layer instructs the PHY layer to transmit an SR using the PUCCH, as shown in Fig. 5. At this time, the MAC layer instructs the PHY layer about an SR resource for transmitting the SR.

[0135] Terminal 200 (for example, PHY layer) identifies an SR resource ID (for example, SchedulingRequestId) corresponding to the SR resource based on the SR resource indicated by the MAC layer. Furthermore, terminal 200 (for example, PHY layer) determines the priority of the SR corresponding to the identified SR resource ID (for example, priority shown in FIG. 11) based on the RRC configuration (for example, SchedulingRequestId IE).

[0136] According to terminal operation SR-3, terminal 200 (for example, PHY layer) can uniquely determine the priority in the PHY layer based on the SR resources indicated in the RRC configuration.

[0137] Furthermore, according to the terminal operation SR-3, the priority of the SR resource in the PHY layer is set regardless of the priority of the logical channel. Therefore, for example, the number of SR priorities in the PHY layer may not be the same as the number of logical channel priorities. Furthermore, there is no need for a standard or RRC setting for setting the correspondence between the SR priority and the logical channel priority.

[0138] An example of a method for determining the priority of SR in the PHY layer has been described above.

[0139] <Terminal Operation 1: ACK / NACK> Next, an example of a method for determining the priority in the PHY layer of an ACK / NACK transmitted by terminal 200 will be described.

[0140] The ACK / NACK is, for example, a UCI indicating the result of error detection of downlink data (DL-SCH) transmitted on the PDSCH. In other words, the ACK / NACK is a response signal to the downlink data.

[0141] For example, the terminal obtains information about the logical channel of the downlink data transmitted by the DL-SCH (for example, including the priority of the logical channel) by decoding the PDSCH. For example, the terminal may determine the priority of ACK / NACK in the PHY layer based on the information about the priority of the logical channel. However, in this case, there is room for considering the following two points.

[0142] First, if the PDSCH cannot be decoded correctly, the terminal cannot obtain information about the priority of the logical channel. Therefore, the terminal can use information about the priority of the logical channel when transmitting an ACK (in other words, no error in the DL-SCH), but cannot use information about the priority of the logical channel when transmitting a NACK.

[0143] The second is that information about the logical channel of downlink data is included in a MAC Control Element (MAC CE), and a processing delay occurs when the terminal decodes the MAC CE and acquires the information in the MAC CE. Generally, the processing delay when the terminal decodes the MAC CE and acquires the information in the MAC CE is larger than the processing delay when the terminal decodes the PDSCH and generates and transmits an ACK / NACK for the PDSCH.

[0144] Furthermore, for example, Non-Patent Documents 8 and 9 disclose that a base station introduces priority indication, which includes information about priority in DL assignment (or DCI) for scheduling a PDSCH and notifies the terminal. However, in NR Release 15, the number of priorities that can be set for logical channels is 16, and the overhead of DCI increases when the priority of a logical channel is included in the PDSCH and notified.

[0145] In addition, in NR Release 16, to support services with different requirements (e.g., eMBB and URLLC), HARQ codebooks (e.g., ACK / NACK bit sequences) for transmitting ACK / NACK may be generated separately for each service. In this case, information indicating which HARQ codebook the PDSCH transmitted to the terminal corresponds to may be included in DL assignment (or DCI) and notified to the terminal from the base station.

[0146] For example, the terminal may determine the priority of an ACK / NACK based on the notification of the HARQ codebook. In other words, the base station may notify the priority of an ACK / NACK by utilizing (or reusing) the notification of the HARQ codebook. However, it is expected that the maximum number of HARQ codebooks generated separately for each service will be limited. For example, the maximum number of HARQ codebooks may be a number (e.g., 2) less than the number of logical channel priorities (e.g., 16). Therefore, it is difficult to notify the priority of logical channels included in the PDSCH by including it in DCI.

[0147] In an embodiment of the present disclosure, terminal 200 determines the priority of an ACK / NACK, for example, based on downlink control information (e.g., DL assignment or DCI) notified from base station 100. For example, as shown in Fig. 12, terminal 200 determines the priority of an ACK / NACK in the PHY layer based on information included in DL assignment (or DCI) that schedules downlink data (e.g., PDSCH) corresponding to the ACK / NACK or a parameter of the DCI.

[0148] In this case, the granularity of the information (e.g., referred to as priority information) for determining the priority of an ACK / NACK notified by information included in a DL assignment (or DCI) or parameters of the DCI may be greater than the number of priorities of a logical channel (or other UCI such as SR). For example, if the number of priorities of a logical channel is 16 levels, the granularity (in other words, the number of candidates) of the information for determining the priority of an ACK / NACK notified by information included in a DL assignment (or DCI) or parameters of the DCI may be a value corresponding to a number less than 16.

[0149] For example, terminal 200 may determine the priority of ACK / NACK in the PHY layer based on the correspondence between information included in DL assignment (or DCI) or information for determining the priority of ACK / NACK that can be notified by parameters of DCI and the priority of the logical channel (or other UCI such as SR) corresponding to the downlink data (logical channel priority).

[0150] FIG. 13 is a flowchart showing an example of an operation regarding a terminal operation 1 for determining the priority of an ACK / NACK.

[0151] Terminal 200 acquires, for example, information relating to the association between information for determining the priority of ACK / NACK (priority information) and the priority of logical channels (S121). The information relating to the association between information for determining the priority of ACK / NACK and the priority of logical channels may be set in terminal 200 by base station 100 via RRC, or may be specified in advance in a standard.

[0152] Terminal 200 receives DCI from base station 100, for example, and acquires resource allocation information included in DL assignment included in the DCI and information for determining the priority of ACK / NACK (priority information) (S122).

[0153] Terminal 200 receives a PDSCH signal (in other words, DL-SCH or downlink data) allocated by DCI based on the acquired resource allocation information, for example (S123). Terminal 200 then decodes the received PDSCH and generates an ACK / NACK (S124).

[0154] Terminal 200 determines, for example, the priority of an ACK / NACK in the PHY layer (S125). For example, terminal 200 determines the priority of a logical channel corresponding to information for determining the priority of an ACK / NACK included in the DCI, based on the association between information for determining the priority of an ACK / NACK and the priority of the logical channel. Terminal 200 may then determine the priority of the ACK / NACK based on the determined priority of the logical channel.

[0155] In FIG. 13, the process of S125 (processing for determining the priority of ACK / NACK in the PHY layer) may be performed before the process of S123 (receiving PDSCH) or the process of S124 (generating ACK / NACK).

[0156] According to an embodiment of the present disclosure, terminal 200 can determine the priority of an ACK / NACK for a PDSCH based on information notified by DCI, thereby suppressing, for example, an increase in processing delay for decoding MAC CE. Furthermore, terminal 200 can determine the priority of an ACK / NACK by receiving DCI. In other words, terminal 200 can determine the priority of an ACK / NACK (for example, the priority of a logical channel) even when it cannot correctly decode a PDSCH (for example, when transmitting a NACK).

[0157] Next, as an example, a method of associating information (priority information) for determining the priority of ACK / NACK that can be notified by DL assignment (or DCI) with the priority of a logical channel (or other UCI such as SR) will be described.

[0158] (Method 1: hereafter referred to as "Terminal Behavior ACK / NACK-1") In terminal operation ACK / NACK-1, the association between information for determining the priority of ACK / NACK and the priority of logical channels is set in terminal 200 by base station 100, for example, by RRC.

[0159] FIG. 14 shows an example of the correspondence between information for determining the priority of ACK / NACK and the priority of logical channels.

[0160] In FIG. 14, information (for example, priority indicator) relating to the priority of ACK / NACK (in other words, PDSCH) is notified to terminal 200 by one bit of DCI.

[0161] For example, in one example of the RRC configuration (configuration 1), information "0" regarding the priority notified by the DCI is associated with a logical channel priority of "1", and information "1" regarding the priority notified by the DCI is associated with a logical channel priority of "10". In another example of the RRC configuration (configuration 2), information "0" regarding the priority notified by the DCI is associated with a logical channel priority of "8", and information "1" regarding the priority notified by the DCI is associated with a logical channel priority of "16". Note that the RRC configuration is not limited to the example shown in FIG. 14. For example, the number of bits of the information regarding the priority notified by the DCI may be 2 or more.

[0162] For example, terminal 200 (PHY layer) identifies the priority of the logical channel corresponding to the information on the priority of the ACK / NACK included in the DCI based on the association between the information on the priority of the ACK / NACK and the priority of the logical channel (see, for example, FIG. 14). Then, terminal 200 determines the priority of the ACK / NACK in the PHY layer based on the identified priority of the logical channel.

[0163] In terminal operation ACK / NACK-1, terminal 200 determines the priority of an ACK / NACK based on, for example, one bit of DCI notification, so no processing delay occurs for decoding MAC CE. Furthermore, in terminal operation ACK / NACK-1, the amount of information related to the priority notified by DCI (one bit in FIG. 14) can be reduced compared to the number of logical channel priorities (for example, 16, four bits), and an increase in DCI overhead can be suppressed. Furthermore, in terminal operation ACK / NACK-1, base station 100 can flexibly set, for each terminal 200, an association between information for determining the priority of an ACK / NACK and the priority of a logical channel by RRC configuration.

[0164] In addition, the information associated with the information for determining the priority of ACK / NACK that can be notified by DL assignment (or DCI) is not limited to the priority of the logical channel, but may also be, for example, the priority of SR in the PHY layer or the priority of other signals.

[0165] (Method 2: hereafter referred to as "Terminal Behavior ACK / NACK-2") In the terminal operation ACK / NACK-2, the correspondence between the information for determining the priority of ACK / NACK and the priority of the logical channel is set in advance in the standard, for example.

[0166] For example, when information relating to the priority of ACK / NACK (in other words, PDSCH) is notified to terminal 200 by one bit of DCI, the correspondence between the priority information "0" notified by DCI and the logical channel priority "1", and the correspondence between the priority information "1" notified by DCI and the logical channel priority "10" may be determined in advance in the standard. Note that the correspondence between the priority information notified by DCI and the logical channel priority is not limited to the above example, and other correspondences may be used.

[0167] In terminal operation ACK / NACK-2, RRC settings relating to the correspondence between information for determining the priority of ACK / NACK and the priority of logical channels are not required, so signaling overhead relating to RRC settings can be reduced.

[0168] An example of the association between information for determining the priority of ACK / NACK and the priority of logical channels has been described above.

[0169] Note that information for determining the priority of ACK / NACK is not limited to, for example, explicit information included in DL assignment (or DCI) as described above, and may be implicitly notified by, for example, DCI parameters. For example, the information for determining the priority of ACK / NACK may be implicitly notified by at least one of differences in DCI format, differences in RNTI, DCI parameters, search space of PDCCH transmitting DCI or parameters of CORESET (Control Resource Set), and configuration information.

[0170] (Terminal Operation 1: ACK / NACK Variation 1) The information included in the DL assignment (or DCI) or the information for determining the priority of the ACK / NACK that can be notified by the parameters of the DCI may be associated with the priorities of multiple logical channels (or other UCI such as SR).

[0171] FIG. 15 shows an example of the correspondence between information for determining the priority of ACK / NACK and the priority of logical channels.

[0172] In Fig. 15, for example, priority information "0" notified by DCI is associated with priority set 2, which includes logical channel priorities 2 to 7. Also in Fig. 15, priority information "1" notified by DCI is associated with priority set 3, which includes logical channel priorities 8 to 15.

[0173] 15, for example, priority set 1 including logical channel priority 1 corresponds to a priority higher than any of the ACK / NACK priorities. Also, in FIG. 15, for example, priority set 4 including logical channel priority 16 corresponds to a priority lower than any of the ACK / NACK priorities.

[0174] In this way, the priorities of the logical channels may be grouped into a plurality of priority sets, including a priority set associated with the priorities of the ACK / NACKs. Note that the logical channels included in the priority sets are not limited to the example shown in FIG.

[0175] By grouping the priorities of logical channels, for example, terminal 200 can easily set other uplink signals (e.g., SR, CSI, or uplink data) different from ACK / NACK to the same priority as ACK / NACK. For example, in FIG. 15, if the priority of an uplink signal different from ACK / NACK is within the range of logical channel priorities 2 to 7 (e.g., priority set 2), terminal 200 determines that the priorities of ACK / NACK and other uplink signals are the same. By making it easier to set the same priority for ACK / NACK and other uplink signals, terminal 200 can easily multiplex and transmit multiple uplink signals, for example, when determining an uplink signal to actually transmit in terminal operation 3.

[0176] (Terminal behavior 1: ACK / NACK variation 2) The information contained in the DL assignment (or DCI) or the information for determining the priority of the ACK / NACK that can be notified in the parameters of the DCI may not correspond to any level of priority of the logical channel (or other UCI such as SR).

[0177] For example, information "0" regarding the priority of ACK / NACK notified by DCI may be associated with a level lower than logical channel priority 1 and higher than logical channel priority 2. Note that this setting of the priority of ACK / NACK is just an example, and the priority of ACK / NACK may be another value.

[0178] This priority setting enables terminal 200 to differentiate the priorities between ACK / NACK and other uplink signals different from ACK / NACK. Therefore, terminal 200 can clearly distinguish the priorities among multiple uplink signals, for example, when determining the uplink signal to actually transmit in terminal operation 3. For example, terminal 200 can easily apply the "prioritization" operation of dropping a low-priority signal and transmitting a high-priority signal, thereby simplifying the processing of terminal 200.

[0179] <Terminal Operation 1: CSI> Next, an example of a method for determining the priority in the PHY layer of CSI transmitted by terminal 200 will be described.

[0180] The CSI is, for example, UCI indicating downlink channel state information.

[0181] Terminal 200 determines the priority of CSI in the PHY layer in association with the priority of a logical channel (or other UCI such as SR), for example, as shown in Fig. 16. The association between the priority of a logical channel and the priority of CSI may be configured in terminal 200 in advance by RRC, or may be specified in advance in a standard.

[0182] For example, information regarding the association between CSI priority and logical channel priority "10" may be configured from base station 100 to terminal 200 by RRC. Note that the logical channel priority associated with CSI priority is not limited to "10" and may be another priority. Base station 100 may flexibly configure the association between CSI priority and logical channel priority for each terminal 200 by, for example, RRC configuration.

[0183] Alternatively, the priority of CSI may be predefined in a standard. For example, the priority of CSI may be associated with a logical channel priority of "10." Alternatively, the priority of CSI may be set to the lowest priority among the logical channels. Predefined CSI priority in a standard eliminates the need for RRC configuration, thereby reducing signaling overhead related to RRC configuration.

[0184] FIG. 17 is a flowchart showing an example of an operation regarding terminal operation 1 for determining the priority of CSI.

[0185] Terminal 200 acquires, for example, information relating to the association between the priority of CSI and the priority of logical channels (S131). The information relating to the association between the priority of CSI and the priority of logical channels may be configured in terminal 200 by base station 100 via RRC, or may be specified in advance in a standard.

[0186] Terminal 200, for example, triggers transmission of CSI (S132).

[0187] Terminal 200 determines, for example, the priority of CSI in the PHY layer (S133). For example, terminal 200 may determine the priority of CSI based on the association between the priority of CSI and the priority of a logical channel.

[0188] In FIG. 17, the order of the process of S132 (triggering CSI transmission) and the process of S133 (determining the priority of CSI in the PHY layer) may be reversed.

[0189] According to an embodiment of the present disclosure, terminal 200 may determine the priority of CSI in the PHY layer. By determining the priority of CSI, terminal 200 may compare the priority between CSI and logical channels (or other UCI such as SR).

[0190] (Terminal Operation 1: CSI Variation 1) The priority of a CSI may be associated with the priorities of multiple logical channels (or other UCIs such as SRs).

[0191] FIG. 18 shows an example of the association between the priority of CSI and the priority of logical channels.

[0192] In Fig. 18, for example, priority set 1 including logical channel priorities 1 to 7 corresponds to a higher priority than the CSI priority. Also in Fig. 18, for example, priority set 2 including logical channel priorities 8 to 15 corresponds to the same priority as the CSI priority. Also in Fig. 18, for example, priority set 3 including logical channel priority 16 corresponds to a lower priority than the CSI priority.

[0193] In this way, the priorities of the logical channels may be grouped into a plurality of priority sets including priority sets corresponding to the priorities of the CSI. Note that the logical channels included in the priority sets are not limited to the example shown in FIG.

[0194] By grouping the priorities of logical channels, for example, terminal 200 can easily set other uplink signals different from CSI (for example, SR, ACK / NACK, or uplink data) to the same priority as CSI. For example, in FIG. 18, if the priority of an uplink signal different from CSI is within the range of logical channel priorities 8 to 15 (for example, priority set 2), terminal 200 determines that the priorities of CSI and other uplink signals are the same. By making it easier to set the same priority for CSI and other uplink signals, terminal 200 can easily multiplex and transmit multiple uplink signals, for example, when determining an uplink signal to actually transmit in terminal operation 3.

[0195] (Terminal Operation 1: CSI Variation 2) The priority of the CSI may not match any level of priority of the logical channel (or other UCI such as SR).

[0196] For example, the priority of CSI may be set to a level lower than logical channel priority 7 and higher than logical channel priority 8. Note that this setting of CSI priority is just an example, and the priority of CSI may be set to another value.

[0197] This priority setting enables terminal 200 to differentiate the priorities between CSI and other uplink signals different from the CSI. Thus, terminal 200 can clearly distinguish the priorities among multiple uplink signals, for example, when determining an uplink signal to actually transmit in terminal operation 3. For example, terminal 200 can easily apply the "prioritization" operation of dropping a low-priority signal and transmitting a high-priority signal, thereby simplifying the processing of terminal 200.

[0198] (Terminal Operation 1: CSI Variation 3) In the above example, a case where one priority is set for CSI has been described, but multiple priorities may be set for CSI.

[0199] For example, multiple priorities may be set for CSI depending on the type of CSI or the type of services and traffic with different requirements. For example, the priority of CSI may differ depending on the type of CSI report, such as periodic CSI, semi-persistent CSI, and aperiodic CSI.

[0200] <Terminal Operation 1: Uplink Data> Next, an example of a method for determining the priority in the PHY layer of uplink data transmitted by terminal 200 will be described.

[0201] For example, terminal 200 has a function of mapping transmission data corresponding to logical channels to transport channels in the MAC layer. For example, when uplink data to be transmitted exists at the time of receiving an uplink grant, the MAC layer generates a transport block (TB) according to the uplink grant and instructs the PHY layer to transmit the uplink data (see, for example, Non-Patent Document 6).

[0202] At this time, terminal 200 (for example, PHY layer) may determine the priority of the uplink data (TB) instructed to be transmitted by the MAC layer based on the following method.

[0203] For example, terminal 200 (e.g., MAC layer) may determine the priority of uplink data (TB) based on the priority of the logical channel that triggered TB. Terminal 200 may obtain information regarding the priority of each logical channel, for example, from RRC configuration information (see, for example, Non-Patent Document 7). For example, for the priority of a logical channel, "priority," which is a parameter related to priority set in "LogicalChannelConfig IE" in Non-Patent Document 7, may be used.

[0204] As shown in Fig. 19, in terminal 200, when TB is triggered, the MAC layer instructs the PHY layer to transmit uplink data. At this time, for example, information regarding the priority of the logical channel that triggered TB may be notified from the MAC layer to the PHY layer, as shown in Fig. 19. For example, terminal 200 (PHY layer) may determine the priority of the uplink signal based on the priority of the logical channel that triggered TB.

[0205] Furthermore, a TB may include data corresponding to, for example, multiple logical channels. In this case, for example, any one of the priorities of the logical channels that triggered the TB may be notified from the MAC layer to the PHY layer. For example, among the priorities of the logical channels that triggered the TB, the priority of the logical channel with the highest priority may be notified from the MAC layer to the PHY layer, or the priority of the logical channel with the lowest priority may be notified from the MAC layer to the PHY layer.

[0206] FIG. 20 is a flowchart showing an example of an operation regarding a terminal operation 1 for determining the priority of uplink data.

[0207] Terminal 200, for example, acquires information relating to the association between the priority of uplink data (for example, PUSCH) in the PHY layer and the priority of logical channels (S141). The information relating to the association between the priority of uplink data and the priority of logical channels may be configured in terminal 200 by base station 100 via RRC, or may be specified in advance in a standard.

[0208] For example, the terminal 200 receives an uplink grant from the base station 100 and acquires resource allocation information for uplink data (S142).

[0209] Terminal 200 generates uplink data (PUSCH) based on, for example, the acquired resource allocation information (S143).

[0210] Terminal 200, for example, determines the priority of uplink data in the PHY layer (S144). For example, terminal 200 may determine the priority of uplink data based on the priority of the logical channel that triggered TB, based on the association between the priority of uplink data and the priority of the logical channel.

[0211] For example, terminal 200 may set the priority of the logical channel notified from the MAC layer to the PHY layer to the priority of the uplink data in the PHY layer.

[0212] Furthermore, for example, terminal 200 may differentiate the number of priorities of uplink data in the PHY layer (in other words, granularity) from the number of priorities of logical channels. In this case, the priorities of uplink data in the PHY layer may be determined in association with the priorities of logical channels. The association between the priorities of uplink data and the priorities of logical channels may be configured in terminal 200 by RRC, for example, or may be specified in advance in a standard.

[0213] In addition, in Figure 20, for example, if the number of priorities of uplink data in the PHY layer is the same as the number of priorities of logical channels, and the priorities of other uplink signals are compared based on the priority of the logical channels, terminal 200 may omit the processing of S141.

[0214] According to one embodiment of the present disclosure, for example, the priority of the uplink data determined from the priority of the logical channel that triggered the TB is notified from the MAC layer to the PHY layer, so that the PHY layer can uniquely determine the priority of the uplink data.

[0215] The above explains terminal operation 1.

[0216] [Terminal operation 2] In terminal operation 2, when the transmission of multiple uplink signals (UCI or uplink data) overlaps in the time domain, the terminal 200 determines the priority among the multiple uplink signals based on the priority of each uplink signal in the PHY layer determined in terminal operation 1.

[0217] FIG. 21 is a flowchart showing an example of terminal operation 2 in the terminal 200.

[0218] Terminal 200, for example, determines whether transmissions of multiple uplink signals (for example, UCI or uplink data) overlap in the time domain (S201). If transmissions of multiple uplink signals do not overlap in the time domain (S201: No), terminal 200 ends terminal operation 2 (for example, the processing in FIG. 21).

[0219] If transmissions of multiple uplink signals overlap in the time domain (S201: Yes), terminal 200 compares the priorities of the multiple uplink signals based on, for example, the priorities of the respective uplink signals in the PHY layer determined in terminal operation 1 (S202). Then, terminal 200 determines the priorities (for example, magnitude relationship or whether the uplink signals have the same priority) between the uplink signals based on the comparison result of the priorities between the multiple uplink signals (S203).

[0220] Here, for example, the number of priorities for each of SR, ACK / NACK, CSI, and uplink data in the PHY layer may be the same as the number of priorities for logical channels. In this case, terminal 200 may compare the priorities of each of SR, ACK / NACK, CSI, and uplink data based on the priority of the logical channel. For example, in terminal operation 1, if the priority of SR in the PHY layer corresponds to logical channel priority 1 and the priority of ACK / NACK in the PHY layer corresponds to logical channel priority 2, terminal 200 can determine that the priority of SR is higher than the priority of ACK / NACK.

[0221] Alternatively, for example, the number of priorities in the PHY layer for at least one of SR, ACK / NACK, CSI, and uplink data may be different from the number of priorities for logical channels. In this case, terminal 200 may compare the priorities of SR, ACK / NACK, CSI, and uplink data in the PHY layer based on a criterion different from the priority of logical channels. In the criterion in the PHY layer, the priority of the uplink signal may be determined in association with, for example, the priority of the logical channel. The association between the priority of the uplink signal and the priority of the logical channel may be notified from base station 100 to terminal 200 by, for example, RRC, or may be specified in advance in a standard.

[0222] Furthermore, the number of priorities for SR, ACK / NACK, CSI, and uplink data in the PHY layer may be the same or different. When the number of priorities differs between UCIs or between UCIs and uplink data, the association between the different numbers of priorities may be configured in terminal 200 by, for example, RRC, or may be specified in advance in a standard.

[0223] According to one embodiment of the present disclosure, terminal 200 can determine the priority between different UCIs or data based on the priority of each UCI and uplink data in the PHY layer, even when transmissions of multiple uplink signals (e.g., UCIs or uplink data) overlap in the time domain.

[0224] (Variation 1 of Terminal Operation 2) In the above-described terminal operation 1, as an example, a case has been described in which each of the priorities of ACK / NACK and CSI is associated with the priorities of multiple logical channels (or other UCI) (see, for example, FIGS. 15 and 18). In this case, for example, in terminal operation 2, terminal 200 may compare one of the priorities of multiple logical channels associated with the priorities of ACK / NACK or CSI with the priorities of other uplink signals. For example, in FIG. 15, when notified by priority indicator="0", terminal 200 may set priority 2, the highest of the priorities 2 to 7 of the logical channels corresponding to priority indicator="0", as the priority of ACK / NACK, and compare it with the priorities of other uplink signals.

[0225] Among the priorities of multiple logical channels associated with the priority of UCI in the PHY layer, the priority that serves as the reference (in other words, the object of comparison) in the PHY is not limited to the highest priority, but may be any one of the priorities.

[0226] (Variation 2 of Terminal Operation 2) In addition, cases in which transmissions of multiple uplink signals overlap in the time domain include, for example, cases in which multiple UCIs overlap in the time domain and the resources of both or one of the multiple UCIs overlap with the resources of uplink data in the time domain.

[0227] In this case, for example, terminal 200 first compares the priorities between UCIs and determines the UCI to be transmitted by terminal operation 3, which will be described later. Next, when the resource of the determined UCI and the resource of the uplink data overlap in the time domain, terminal 200 may compare the priorities between the UCI and the uplink data and determine the uplink signal to actually transmit by terminal operation 3, which will be described later.

[0228] The uplink signal actually transmitted by terminal 200 may be generated by applying, for example, a method of dropping a low-priority signal and transmitting a high-priority signal (e.g., also referred to as "prioritization"), or a method of multiplexing and transmitting multiple uplink signals in one channel (e.g., PUCCH or PUSCH) (e.g., "multiplexing"). In other words, as a result of terminal operation 2 and terminal operation 3 between UCIs, multiple uplink signals may be multiplexed in the uplink signal actually transmitted by terminal 200. In this case, the priority of the UCI compared with the uplink data in terminal 200 may be the priority of the UCI with the highest priority among the multiplexed UCIs, or may be another priority.

[0229] Furthermore, the processing of terminal 200 is not limited to the processing of comparing the priorities of UCIs and uplink data after comparing the priorities between UCIs, as described above. For example, when multiple UCIs overlap in the time domain and resources of both or one of the multiple UCIs overlap with resources of uplink data in the time domain, terminal 200 may compare the priorities of the multiple UCIs and the uplink data (for example, compare them collectively) to determine the uplink signal to actually transmit.

[0230] The above explains terminal operation 2.

[0231] [Terminal operation 3] In terminal operation 3, the terminal 200 determines an uplink signal to actually transmit based on the priorities among the multiple uplink signals determined in terminal operation 2.

[0232] FIG. 22 is a flowchart showing an example of terminal operation 3 in the terminal 200.

[0233] For example, terminal 200 determines whether transmissions of multiple uplink signals (for example, UCI or uplink data) overlap in the time domain (S301). If transmissions of multiple uplink signals do not overlap in the time domain (S301: No), terminal 200 performs processing of S304, which will be described later.

[0234] If the transmission of multiple uplink signals overlaps in the time domain (S301: Yes), the terminal 200 determines the uplink signal to actually transmit based on, for example, the priority among the multiple uplink signals determined in terminal operation 2 (S302).

[0235] The terminal 200 generates an uplink signal to be actually transmitted (S303). The uplink signal to be actually transmitted by the terminal 200 may be generated by applying prioritization or multiplexing, for example.

[0236] Then, the terminal 200 transmits the generated uplink signal (S304).

[0237] For example, the following methods (either of Options 1 to 3) regarding prioritization and multiplexing can be applied.

[0238] <option 1> When the priorities in the PHY layer between the target uplink signals are different, terminal 200 determines not to transmit (in other words, drop) the uplink signal with the lower priority among the multiple uplink signals. For example, terminal 200 drops the signal with the lower priority among two uplink signals with different priorities and transmits the signal with the higher priority.

[0239] On the other hand, if the target uplink signals have the same priority in the PHY layer, terminal 200 may apply, for example, the terminal operation in NR Release 15 described above (see, for example, Non-Patent Document 5).

[0240] According to Option 1, when resources for transmitting UCI (e.g., SR, ACK / NACK, or CSI) or uplink data having a higher priority compared to other services such as URLLC overlap in the time domain with other uplink transmissions (e.g., UCI or uplink data), terminal 200 can actually transmit the uplink signal having a higher priority.

[0241] < / option> <option 2> If the priorities in the PHY layer between the target uplink signals are different, terminal 200 drops the signal with the lower priority and transmits the signal with the higher priority, as in Option 1.

[0242] Furthermore, if the target uplink signals have the same priority in the PHY layer, one of the multiple uplink signals is determined not to be transmitted (in other words, dropped). For example, terminal 200 drops one of the two uplink signals having the same priority and transmits the other signal.

[0243] According to Option 2, even if the uplink signals have the same priority in the PHY layer, the terminal 200 transmits one uplink signal without multiplexing multiple uplink signals, thereby simplifying the processing of the terminal 200.

[0244] < / option> <option 3> When terminal 200 transmits UCI or uplink data with a high priority and satisfies a condition, terminal 200 multiplexes UCI or uplink data with a low priority onto a channel for transmitting UCI or uplink data with a high priority, and transmits the multiplexed data. For example, terminal 200 multiplexes two uplink signals into a transmission resource for transmitting an uplink signal with a higher priority out of two uplink signals with different priorities.

[0245] The condition for multiplexing and transmitting a plurality of uplink signals may be, for example, when there is a surplus of uplink resources (for example, when the amount of resources or the surplus of resources is equal to or greater than a threshold), or may be other conditions.

[0246] According to Option 3, when there are spare resources, the terminal 200 can multiplex and transmit as many uplink signals as possible, thereby improving resource utilization efficiency (in other words, transmission efficiency).

[0247] In other words, when there are not enough resources, terminal 200 can, for example, transmit some uplink signals and drop other uplink signals without multiplexing multiple uplink signals. By not multiplexing multiple uplink signals, it is possible to suppress degradation of transmission efficiency caused by, for example, transmitting URLLC traffic using resources corresponding to eMBB (in other words, resources that do not satisfy the requirements of URLLC). Furthermore, it is possible to suppress degradation of transmission efficiency caused by multiplexing UCI for eMBB traffic in resources corresponding to URLLC.

[0248] Below, an example of terminal operation 3 (including, for example, Options 1 to 3) will be described in each scenario in which transmissions of multiple uplink signals (SR, ACK / NACK, CSI, and uplink data) overlap in the time domain.

[0249] [SR vs ACK / NACK] When the transmission resource of the SR (e.g., PUCCH) and the transmission resource of the ACK / NACK (e.g., PUCCH) overlap in the time domain, the terminal 200, for example, determines the priority of the triggered SR in the PHY layer and the priority of the ACK / NACK based on terminal operation 1, and compares the priorities of the SR and ACK / NACK in the PHY layer based on terminal operation 2.

[0250] Then, based on the comparison result of the priorities of SR and ACK / NACK, terminal 200 determines the signal to actually transmit by one of the following methods in terminal operation 3.

[0251] < / option> <option 1> If the PHY layer priorities of the SR and the ACK / NACK are different, terminal 200 drops (in other words, does not transmit) the SR or ACK / NACK with a lower priority and transmits the ACK / NACK or SR with a higher priority. On the other hand, if the PHY layer priorities of the SR and the ACK / NACK are the same, terminal 200 may apply the terminal operation of NR Release 15 described above (for example, see Non-Patent Document 5).

[0252] < / option> <option 2> If the priorities of the SR and ACK / NACK in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or ACK / NACK with the lower priority and transmits the ACK / NACK or SR with the higher priority. On the other hand, if the priorities of the SR and ACK / NACK in the PHY layer are the same, terminal 200 may apply either of the following methods, Option 2-1 and Option 2-2.

[0253] Option 2-1: Terminal 200 drops the SR and transmits an ACK / NACK. For example, if a weighted priority is placed on the downlink compared to the uplink, the operation of Option 2-1 can make the priority of the ACK / NACK corresponding to the downlink data higher than the priority of the SR corresponding to the uplink data.

[0254] Option 2-2: Terminal 200 drops the ACK / NACK and transmits an SR. For example, if priority is weighted to the uplink compared to the downlink, the operation of Option 2-2 can make the priority of the SR corresponding to the uplink data higher than the priority of the ACK / NACK corresponding to the downlink data.

[0255] < / option> <option 3> If the priorities of the SR and the ACK / NACK in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or ACK / NACK with the lower priority, and transmits the ACK / NACK or SR with the higher priority.

[0256] On the other hand, if the SR and the ACK / NACK have the same priority in the PHY layer, terminal 200 may multiplex the SR and the ACK / NACK into the PUCCH and transmit the multiplexed SR and the ACK / NACK under certain conditions.

[0257] The condition for multiplexing an SR and an ACK / NACK may be, for example, a condition using information included in a DL assignment (or DCI) or information for determining the priority of an ACK / NACK that can be notified by a DCI parameter (for example, priority information). For example, if the priority of an ACK / NACK corresponds to information "0" for determining the priority of an ACK / NACK notified by a DCI, terminal 200 may multiplex the SR and the ACK / NACK into a PUCCH and transmit the multiplexed ACK / NACK. On the other hand, for example, if the priority of an ACK / NACK corresponds to information "1" for determining the priority of an ACK / NACK notified by a DCI, terminal 200 may drop the ACK / NACK.

[0258] Conversely, terminal 200 may, for example, drop the SR when the priority level of the ACK / NACK corresponds to information "0" for determining the priority of the ACK / NACK notified by DCI, and may multiplex the SR and ACK / NACK into a PUCCH and transmit them when the priority level of the ACK / NACK corresponds to information "1" for determining the priority of the ACK / NACK notified by DCI.

[0259] The conditions for multiplexing an SR, an ACK / NACK, and a PUCCH for transmission are not limited to those described above. The conditions may be conditions that utilize information such as the transmission timing of the PUCCH that transmits the SR or the ACK / NACK, the number of transmission symbols of the PUCCH, and the maximum value of the coding rate set for the PUCCH.

[0260] Furthermore, terminal 200 may switch whether or not to perform multiplex transmission of SR and ACK / NACK based on the setting (in other words, an instruction) of base station 100.

[0261] < / option> <option 4> When the transmission resource of SR (e.g., PUCCH) and the transmission resource of ACK / NACK (e.g., PUCCH) overlap in the time domain, not only Option 1, Option 2, and Option 3 described above, but also Option 4 described below may be applied.

[0262] In Option 4, terminal 200 may prioritize between SR and ACK / NACK based on, for example, parameters of transmission resources for SR and ACK / NACK in the PHY layer.

[0263] For example, if the SR and ACK / NACK have different priorities in the PHY layer, terminal 200 drops (in other words, does not transmit) the SR or ACK / NACK with a lower priority and transmits the ACK / NACK or SR with a higher priority.

[0264] On the other hand, when the priorities of SR and ACK / NACK in the PHY layer are the same, terminal 200 may further prioritize SR and ACK / NACK based on parameters of the transmission resources of SR or ACK / NACK in the PHY layer. The parameter used for the priority ranking may be, for example, at least one of the PUCCH format, the number of PUCCH symbols, and the SR period. For example, among PUCCH formats, a Short PUCCH may be set to a higher priority than a Long PUCCH. Also, for example, a smaller number of PUCCH symbols may be set to a higher priority. Also, when the SR period is shorter than a threshold, a higher priority may be set than when the SR period is equal to or greater than the threshold. Note that the parameters used for the priority ranking are not limited to these parameters and may be other parameters.

[0265] Option 4 allows the terminal 200 to more clearly distinguish the priority between SR and ACK / NACK.

[0266] [SR vs ACK / NACK Variation 1] In NR Release 15, for example, as described above, if a PUCCH resource configured for transmitting an SR using PUCCH format 0 overlaps with a PUCCH resource configured for transmitting an ACK / NACK using PUCCH format 1 in the time domain, the terminal drops the transmission of the SR and transmits the ACK / NACK using the PUCCH allocated for the ACK / NACK.

[0267] In terminal operation 3, in this case, terminal 200 may apply terminal operation different from NR Release 15.

[0268] For example, if the ACK / NACK is a NACK, terminal 200 may drop the transmission of the NACK and transmit an SR. On the other hand, if the ACK / NACK is an ACK, terminal 200 may multiplex and transmit the SR and ACK. Base station 100 can determine the SR and ACK / NACK (ACK or NACK) based on the PUCCH resource where the signal was detected (for example, a parameter such as the amount of cyclic shift).

[0269] According to variation 1, even if a PUCCH resource configured for transmitting an SR using PUCCH format 0 overlaps in the time domain with a PUCCH resource configured for transmitting an ACK / NACK using PUCCH format 1, terminal 200 can transmit the SR without dropping it. By transmitting the SR, it is possible to reduce delays in uplink data, for example.

[0270] [SR vs ACK / NACK Variation 2] In NR Release 15, for example, as described above, if a PUCCH resource configured for transmitting an SR using PUCCH format 0 overlaps with a PUCCH resource configured for transmitting an ACK / NACK using PUCCH format 1 in the time domain, the terminal drops the transmission of the SR and transmits the ACK / NACK using the PUCCH allocated for the ACK / NACK.

[0271] In terminal operation 3, in this case, terminal 200 may apply terminal operation different from NR Release 15.

[0272] For example, terminal 200 may use ACK / NACK to modulate some of the subcarriers of PUCCH format 0, which transmits an SR consisting of 12 subcarriers, and transmit the modulated subcarriers. Base station 100 may use, for example, subcarriers that are not modulated by ACK / NACK as demodulation reference signals, perform channel estimation, and then demodulate the subcarriers modulated by ACK / NACK.

[0273] According to Variation 2, even if the transmission resource for SR and the transmission resource for ACK / NACK overlap in the time domain, terminal 200 can transmit both the SR and the ACK / NACK by modulating subcarriers by the ACK / NACK in the PUCCH resource set for transmitting the SR using PUCCH format 0. Thus, terminal 200 can transmit the SR without dropping it, thereby reducing delays in uplink data, for example.

[0274] [SR vs ACK / NACK Variation 3] When a transmission resource (eg, PUCCH) for an SR and a transmission resource (eg, PUCCH) for an ACK / NACK overlap in the time domain, terminal 200 may apply a terminal behavior of dropping either the SR or the ACK / NACK.

[0275] When an SR is dropped, terminal 200 waits until the next SR transmission timing to transmit the SR, which may cause a delay in the uplink.

[0276] Furthermore, if an ACK / NACK is dropped, base station 100 cannot identify the reception result (error detection result) of the PDSCH at terminal 200. In this case, base station 100 retransmits the PDSCH, which reduces resource utilization efficiency.

[0277] Therefore, in Variation 3, an example of the operation of terminal 200 and base station 100 that takes into consideration the delay in SR transmission or resource utilization efficiency when either SR or ACK / NACK is dropped will be described.

[0278] <Variation 3-1> When the transmission resource of the SR (for example, PUCCH) and the transmission resource of the ACK / NACK (for example, PUCCH) overlap in the time domain, terminal 200 drops the transmission of the SR and transmits the ACK / NACK. In this case, base station 100 may determine that an SR is to be transmitted from terminal 200 and may allocate, for example, an uplink resource for transmitting a BSR to terminal 200.

[0279] When terminal 200 actually drops the SR transmission, it transmits a BSR and uplink data in the uplink resource allocated by base station 100. On the other hand, when terminal 200 does not actually drop the SR transmission (for example, when no SR transmission occurs), it may transmit, for example, a padding BSR in the uplink resource allocated by base station 100.

[0280] In variation 3-1, even if terminal 200 actually drops the transmission of an SR, terminal 200 can transmit a BSR without waiting for the next SR transmission timing to transmit an SR, thereby reducing delay.

[0281] <Variation 3-2> When an SR transmission resource (e.g., PUCCH) and an ACK / NACK transmission resource (e.g., PUCCH) overlap in the time domain, terminal 200 drops the SR transmission and transmits an ACK / NACK. In this case, in terminal 200, the PHY layer may notify the MAC layer that the SR has been dropped. By notifying the MAC layer that the SR has been dropped, terminal 200 can recognize that the SR that it instructed the PHY layer to transmit will not actually be transmitted.

[0282] <Variation 3-3> If the transmission resource of the SR (for example, PUCCH) and the transmission resource of the ACK / NACK (for example, PUCCH) overlap in the time domain, terminal 200 drops the transmission of the ACK / NACK and transmits the SR. In this case, base station 100 may determine that decoding of the ACK / NACK from terminal 200 has failed, and may request terminal 200 to retransmit the ACK / NACK.

[0283] According to variation 3-3, base station 100 requests retransmission of ACK / NACK without retransmitting PDSCH, thereby making it possible to suppress a decrease in resource utilization efficiency.

[0284] [SR vs CSI] When a transmission resource of an SR (e.g., a PUCCH) and a transmission resource of a CSI (e.g., a PUCCH or a PUSCH) overlap in the time domain, terminal 200, for example, determines the priority of the triggered SR in the PHY layer and the priority of the CSI based on terminal operation 1, and compares the priorities of the SR and the CSI in the PHY layer based on terminal operation 2.

[0285] Then, based on the comparison result of the priorities of the SR and CSI, terminal 200 determines the signal to actually transmit by one of the following methods in terminal operation 3.

[0286] < / option> <option 1> When the priorities of the SR and CSI in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or CSI with lower priority and transmits the CSI or SR with higher priority. On the other hand, when the priorities of the SR and CSI in the PHY layer are the same, terminal 200 may apply the terminal operation of NR Release 15 described above (for example, see Non-Patent Document 5).

[0287] < / option><option 2> If the priorities of the SR and CSI in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or CSI with lower priority and transmits the CSI or SR with higher priority. On the other hand, if the priorities of the SR and CSI in the PHY layer are the same, terminal 200 may apply either of the following methods, Option 2-1 and Option 2-2.

[0288] Option 2-1: Terminal 200 drops the SR and transmits the CSI. For example, if a weighted priority is placed on the downlink compared to the uplink, the operation of Option 2-1 can make the priority of the CSI corresponding to the downlink data higher than the priority of the SR corresponding to the uplink data.

[0289] Option 2-2: Terminal 200 drops the CSI and transmits an SR. For example, if the uplink is given more priority than the downlink, the operation of Option 2-2 can make the priority of the SR corresponding to the uplink data higher than the priority of the CSI corresponding to the downlink data.

[0290] < / option> <option 3> If the priorities of the SR and CSI in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or CSI with lower priority, and transmits the CSI or SR with higher priority.

[0291] On the other hand, when the SR and CSI have the same priority in the PHY layer, terminal 200 may multiplex and transmit the SR and CSI under certain conditions.

[0292] The condition for multiplexing SR and CSI may be, for example, a condition that uses information on the priority of CSI when the CSI has multiple priorities (e.g., CSI priority 1 and CSI priority 2). For example, terminal 200 may multiplex and transmit SR and CSI when the CSI priority corresponds to CSI priority 1, and may drop the CSI when the CSI priority corresponds to CSI priority 2.

[0293] Conversely, terminal 200 may drop the SR when the CSI priority corresponds to CSI priority 1, and may multiplex and transmit the SR and CSI when the CSI priority corresponds to CSI priority 2.

[0294] The conditions for multiplexing and transmitting SR and CSI on PUCCH are not limited to those described above. The conditions may be conditions that utilize information such as the transmission timing of the PUCCH that transmits SR or CSI, the number of transmission symbols of the PUCCH, the transmission period, and the maximum value of the coding rate set for the PUCCH.

[0295] Furthermore, terminal 200 may switch whether or not to perform multiplex transmission of SR and CSI based on a setting (in other words, an instruction) from base station 100.

[0296] [SR vs PUSCH] When the transmission resource of the SR (e.g., PUCCH) and the transmission resource of the uplink data (e.g., PUSCH) overlap in the time domain, the terminal 200, for example, determines the priority of the triggered SR in the PHY layer and the priority of the PUSCH based on the terminal operation 1, and compares the priorities of the SR and the PUSCH in the PHY layer based on the terminal operation 2.

[0297] Then, terminal 200 determines the signal to actually transmit by the following method in terminal operation 3 based on the comparison result of the priorities of SR and PUSCH.

[0298] < / option> <option 1> If the priorities of the SR and PUSCH in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the SR or PUSCH with lower priority and transmits the PUSCH or SR with higher priority. On the other hand, if the priorities of the SR and PUSCH in the PHY layer are the same, terminal 200 may apply the terminal operation of NR Release 15 described above (for example, see Non-Patent Document 5).

[0299] [SR vs PUSCH variations] When a transmission resource of an SR (eg, a PUCCH) and a transmission resource of uplink data (eg, a PUSCH) overlap in the time domain, terminal 200 may apply a terminal behavior of dropping the SR.

[0300] When an SR is dropped, terminal 200 waits until the next SR transmission timing to transmit the SR, which may cause a delay in the uplink.

[0301] Therefore, in this variation, an example of the operation of terminal 200 and base station 100 that takes into consideration the delay in SR transmission when an SR is dropped will be described.

[0302] <SR vs PUSCHのバリエーション1-1> When a transmission resource for an SR (for example, a PUCCH) overlaps with the PUCCH in the time domain, terminal 200 drops the transmission of the SR and transmits a PUSCH signal. In this case, base station 100 may determine that an SR is to be transmitted from terminal 200, and may allocate, for example, an uplink resource for transmitting a BSR to terminal 200.

[0303] When terminal 200 actually drops the SR transmission, it transmits a BSR and uplink data in the uplink resource allocated by base station 100. On the other hand, when terminal 200 does not actually drop the SR transmission (for example, when no SR transmission occurs), it may transmit, for example, a padding BSR in the uplink resource allocated by base station 100.

[0304] In variation 1-1, even if terminal 200 actually drops the transmission of an SR, terminal 200 can transmit a BSR without waiting for the next SR transmission timing to transmit an SR, thereby reducing delay.

[0305] <SR vs PUSCHのバリエーション1-2> When an SR transmission resource (for example, a PUCCH) and a PUSCH overlap in the time domain, terminal 200 drops the transmission of the SR and transmits a PUSCH. In this case, in terminal 200, the PHY layer may notify the MAC layer that the SR has been dropped. By notifying the MAC layer that the SR has been dropped, terminal 200 can recognize that the SR that it has instructed the PHY layer to transmit will not actually be transmitted.

[0306] [ACK / NACK vs CSI] When the transmission resource of the ACK / NACK (e.g., PUCCH) and the transmission resource of the CSI (e.g., PUCCH or PUSCH) overlap in the time domain, the terminal 200 determines, for example, the priority of the ACK / NACK in the PHY layer and the priority of the CSI based on the terminal operation 1, and compares the priorities of the ACK / NACK and the CSI in the PHY layer based on the terminal operation 2.

[0307] Then, based on the comparison result of the priorities of ACK / NACK and CSI, terminal 200 determines the signal to actually transmit by one of the following methods in terminal operation 3.

[0308] < / option> <option 1> When the PHY layer priorities of the ACK / NACK and the CSI are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or CSI with a lower priority and transmits the CSI or ACK / NACK with a higher priority. On the other hand, when the PHY layer priorities of the ACK / NACK and the CSI are the same, terminal 200 may apply the terminal operation of NR Release 15 described above (for example, see Non-Patent Document 5).

[0309] < / option> <option 2> If the priorities of the ACK / NACK and CSI in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or CSI with a lower priority and transmits the CSI or ACK / NACK with a higher priority. On the other hand, if the priorities of the ACK / NACK and CSI in the PHY layer are the same, terminal 200 may apply either of the following methods, Option 2-1 and Option 2-2.

[0310] Option 2-1: Terminal 200 drops the ACK / NACK and transmits the CSI. Option 2-2: Terminal 200 drops the CSI and transmits an ACK / NACK.

[0311] < / option> <option 3> If the priorities of the ACK / NACK and CSI in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or CSI with lower priority and transmits the CSI or ACK / NACK with higher priority.

[0312] On the other hand, if the ACK / NACK and CSI have the same priority in the PHY layer, terminal 200 may multiplex and transmit the ACK / NACK and CSI under certain conditions.

[0313] The condition for multiplexing an ACK / NACK and CSI may be, for example, a condition using information included in a DL assignment (or DCI) or information for determining the priority of an ACK / NACK that can be notified by a parameter of the DCI (for example, priority information). For example, if the priority of the ACK / NACK corresponds to information "0" for determining the priority of the ACK / NACK notified by the DCI, terminal 200 may multiplex the ACK / NACK and CSI on a PUCCH and transmit the multiplexed ACK / NACK. On the other hand, for example, if the priority level of the ACK / NACK corresponds to information "1" for determining the priority of the ACK / NACK notified by the DCI, terminal 200 may drop the ACK / NACK.

[0314] Conversely, terminal 200 may, for example, drop CSI when the priority level of the ACK / NACK corresponds to information "0" for determining the priority of the ACK / NACK notified by DCI, and may multiplex the ACK / NACK and CSI onto a PUCCH and transmit them when the priority level of the ACK / NACK corresponds to information "1" for determining the priority of the ACK / NACK notified by DCI.

[0315] The conditions for multiplexing an ACK / NACK and CSI onto a PUCCH and transmitting the multiplexed ACK / NACK are not limited to those described above. The conditions may be conditions that utilize information such as the transmission timing of the PUCCH that transmits the ACK / NACK or CSI, the number of transmission symbols of the PUCCH, and the maximum value of the coding rate set for the PUCCH.

[0316] Furthermore, terminal 200 may switch whether or not to perform multiplex transmission of ACK / NACK and CSI based on a setting (in other words, an instruction) from base station 100.

[0317] [ACK / NACK vs PUSCH] When the transmission resource of ACK / NACK (e.g., PUCCH) and the transmission resource of uplink data (e.g., PUSCH) overlap in the time domain, terminal 200 determines, for example, the priority of ACK / NACK in the PHY layer and the priority of PUSCH based on terminal operation 1, and compares the priorities of ACK / NACK and PUSCH in the PHY layer based on terminal operation 2.

[0318] Then, based on the comparison result of the priorities of ACK / NACK and PUSCH, terminal 200 determines the signal to actually transmit by one of the following methods in terminal operation 3.

[0319] < / option> <option 1> If the priorities of the ACK / NACK and the PUSCH in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or PUSCH with a lower priority and transmits the PUSCH or ACK / NACK with a higher priority. On the other hand, if the priorities of the ACK / NACK and the PUSCH in the PHY layer are the same, terminal 200 may apply the terminal operation of NR Release 15 described above (for example, see Non-Patent Document 5).

[0320] < / option> <option 2> If the priorities of the ACK / NACK and the PUSCH in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or PUSCH with a lower priority and transmits the PUSCH or ACK / NACK with a higher priority. On the other hand, if the priorities of the ACK / NACK and the PUSCH in the PHY layer are the same, terminal 200 may apply either of the following methods, Option 2-1 and Option 2-2.

[0321] Option 2-1: Terminal 200 drops the ACK / NACK and transmits a PUSCH. For example, if the uplink is given more priority than the downlink, the operation of Option 2-1 can make the priority of the uplink data (PUSCH) higher than the priority of the ACK / NACK corresponding to the downlink data.

[0322] Option 2-2: Terminal 200 drops the PUSCH and transmits an ACK / NACK. For example, if a higher priority is placed on the downlink compared to the uplink, the operation of Option 2-2 can make the priority of the ACK / NACK corresponding to the downlink data higher than the priority of the uplink data (PUSCH).

[0323] < / option> <option 3> If the priorities of the ACK / NACK and the PUSCH in the PHY layer are different, terminal 200 drops (in other words, does not transmit) the ACK / NACK or PUSCH with lower priority, and transmits the PUSCH or ACK / NACK with higher priority.

[0324] On the other hand, if the ACK / NACK and PUSCH have the same priority in the PHY layer, terminal 200 may multiplex and transmit the ACK / NACK and PUSCH under certain conditions.

[0325] The condition for multiplexing an ACK / NACK and a PUSCH may be, for example, a condition using information included in a DL assignment (or DCI) or information for determining the priority of an ACK / NACK that can be notified by a DCI parameter (for example, priority information). For example, if the priority of an ACK / NACK corresponds to information "0" for determining the priority of an ACK / NACK notified by a DCI, terminal 200 may multiplex the ACK / NACK and a PUSCH onto a PUCCH and transmit the multiplexed ACK / NACK. On the other hand, for example, if the priority level of an ACK / NACK corresponds to information "1" for determining the priority of an ACK / NACK notified by a DCI, terminal 200 may drop the ACK / NACK.

[0326] Conversely, terminal 200 may, for example, drop the PUSCH when the priority level of the ACK / NACK corresponds to information "0" for determining the priority of the ACK / NACK notified by DCI, and may multiplex the ACK / NACK and PUSCH onto a PUCCH and transmit the PUSCH when the priority level of the ACK / NACK corresponds to information "1" for determining the priority of the ACK / NACK notified by DCI.

[0327] The conditions for multiplexing an ACK / NACK and a PUSCH onto a PUCCH and transmitting the multiplexed ACK / NACK and PUSCH are not limited to those described above. The conditions may be conditions that use information such as the transmission timing for transmitting the ACK / NACK or PUSCH, the number of transmission symbols for the PUCCH or PUSCH, or the maximum value of the coding rate set for the PUSCH.

[0328] Furthermore, terminal 200 may switch whether or not to perform multiplex transmission of ACK / NACK and PUSCH based on a setting (in other words, an instruction) from base station 100.

[0329] The above has described examples of terminal operation 3 in each scenario in which transmissions of multiple uplink signals (SR, ACK / NACK, CSI, and uplink data) overlap in the time domain.

[0330] In addition, when the transmission resource of CSI (e.g., PUCCH or PUSCH) and the transmission resource of uplink data (e.g., PUSCH) overlap in the time domain, the terminal operation may be the same as the terminal operation of [ACK / NACK vs PUSCH] described above, except that ACK / NACK is replaced with CSI.

[0331] Furthermore, the above-described terminal operation 3 may also be applied to a case where the transmission resources of multiple uplink signals (e.g., SR and SR, ACK / NACK and ACK / NACK, CSI and CSI, or PUSCH and PUSCH) of the same uplink signal type (e.g., UCI type or uplink data) overlap in the time domain. For example, different priorities may be set for the same multiple uplink signals depending on services with different requirements (e.g., URLLC and eMBB). Terminal 200 may determine the uplink signal to actually transmit, for example, based on the priorities in the PHY layer of the same multiple uplinks whose transmission resources overlap in the time domain.

[0332] The above explains terminal operation 3.

[0333] Thus, in this embodiment, terminal 200 determines at least one uplink signal from among multiple uplink signals to transmit in a certain transmission resource in the time domain based on information regarding the priority of multiple uplink signals (e.g., priority in the PHY layer), and transmits the determined uplink signal in the transmission resource.

[0334] By the transmission process based on priority, even when the transmission resources of multiple uplink signals overlap in the time domain, terminal 200 can determine the uplink signal to actually transmit based on the priority of each of the multiple uplink signals. For example, terminal 200 can preferentially transmit an uplink signal with a higher priority (e.g., a signal corresponding to URLLC), thereby suppressing an increase in delay. Therefore, according to one embodiment of the present disclosure, it is possible to realize appropriate wireless communication process according to required conditions.

[0335] An embodiment of the present disclosure has been described above.

[0336] (Other embodiments) (1) As a result of the above-described terminal operations 1, 2, and 3, the uplink signal actually transmitted by terminal 200 may be, for example, a single signal (e.g., UCI or data), multiple UCIs, or UCI and data may be multiplexed.

[0337] In addition, before the terminal 200 eliminates overlap in the time domain of multiple uplink signals transmitted by the terminal 200 and actually transmits the uplink signal, the terminal 200 may receive information from the base station 100 regarding a resource collision with an uplink signal intended for another terminal, and may drop the transmission of the uplink signal (see, for example, non-patent document 10).

[0338] At this time, terminal 200 may be notified of, for example, information regarding the priority of the uplink signal intended for other terminals together with information regarding resource conflict with the uplink signal intended for other terminals from base station 100. In this case, terminal 200 may compare the priority of the uplink signal that terminal 200 plans to transmit with the priority of the uplink signal to be transmitted by other terminals notified by base station 100, and determine whether or not to transmit the uplink signal in terminal 200.

[0339] For example, the priority of the uplink signal of the terminal 200 when compared with information regarding the priority of uplink signals for other terminals notified by the base station 100 may be the highest priority among the multiplexed UCI or data, or may be another priority.

[0340] (2) In one embodiment of the present disclosure, the downlink control channel, the downlink data channel, the uplink control channel, and the uplink data channel are not limited to PDCCH, PDSCH, PUCCH, and PUSCH, respectively, and may be control channels with other names.

[0341] (3) Services with different requirements are not limited to eMBB and URLLC, but may be other services.

[0342] (4) The parameters shown in one embodiment of the present disclosure, such as the number of logical channel priorities and the number of uplink signal priorities in the PHY layer, are merely examples and are not limited to these values and may be other values.

[0343] The present disclosure can be realized by software, hardware, or software in conjunction with hardware. Each functional block described in the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit. Each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. An LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the level of integration, an LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI. The integration method is not limited to LSIs; it may also be realized by dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a field programmable gate array (FPGA), which can be programmed after LSI fabrication, or a reconfigurable processor, which allows the connections and settings of circuit cells within an LSI to be reconfigured, may also be used. The present disclosure may be realized as digital or analog processing. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology is also a possibility.

[0344] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a wireless transceiver and processing / control circuitry. The wireless transceiver may include a receiver and a transmitter, or both functions. The wireless transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0345] Communications equipment is not limited to portable or mobile equipment, but also includes non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (such as appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0346] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

[0347] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0348] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

[0349] A terminal according to one embodiment of the present disclosure includes a control circuit that determines, based on information regarding the priorities of a plurality of uplink signals, at least one uplink signal to be transmitted in a certain transmission resource in the time domain from among the plurality of uplink signals, and a transmission circuit that transmits the determined uplink signal in the transmission resource.

[0350] In one embodiment of the present disclosure, at least one of the plurality of uplink signals is a scheduling request for uplink data, and the information regarding the priority is based on the priority of a logical channel corresponding to the uplink data.

[0351] In one embodiment of the present disclosure, when the control circuit instructs the physical layer to transmit the scheduling request, it notifies the physical layer of information indicating the priority of the logical channel corresponding to the uplink data in the medium access control (MAC) layer.

[0352] In one embodiment of the present disclosure, the priority of the logical channel is associated with information regarding a resource used for transmitting the scheduling request.

[0353] In one embodiment of the present disclosure, the number of candidates for the priority of the uplink signal is different from the number of candidates for the priority of the logical channel.

[0354] In one embodiment of the present disclosure, at least one of the plurality of uplink signals is a scheduling request for uplink data, and the information regarding the priority is based on a resource used to transmit the scheduling request.

[0355] In one embodiment of the present disclosure, at least one of the plurality of uplink signals is a response signal corresponding to downlink data, and the information regarding the priority is based on downlink control information.

[0356] In one embodiment of the present disclosure, the information regarding the priority is based on a correspondence between a parameter in the control information and a priority of a logical channel corresponding to the downlink data.

[0357] In one embodiment of the present disclosure, the number of candidates for the priority of the uplink signal is less than the number of candidates for the priority of the logical channel.

[0358] In one embodiment of the present disclosure, at least one of the plurality of uplink signals is a signal including information indicating a downlink channel condition, and the information regarding the priority is received by a higher layer signal or is predefined.

[0359] In one embodiment of the present disclosure, at least one of the plurality of uplink signals is uplink data, and the information regarding the priority is based on the priority of a logical channel corresponding to the uplink data.

[0360] In one embodiment of the present disclosure, the control circuit determines not to transmit the uplink signal with a lower priority out of the first uplink signal and the second uplink signal with different priorities.

[0361] In one embodiment of the present disclosure, the control circuit determines not to transmit one of the first uplink signal and the second uplink signal having the same priority.

[0362] In one embodiment of the present disclosure, the transmitting circuit multiplexes the first uplink signal and the second uplink signal into the transmission resource for transmitting the uplink signal with the higher priority among the first uplink signal and the second uplink signal having different priorities.

[0363] In a transmission method according to one embodiment of the present disclosure, a terminal determines at least one uplink signal to be transmitted in a certain transmission resource in the time domain from among a plurality of uplink signals based on information regarding the priorities of the plurality of uplink signals, and transmits the determined uplink signal in the transmission resource.

[0364] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2019-130424, filed on July 12, 2019, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0365] An embodiment of the present disclosure is useful in a mobile communication system. [Explanation of symbols]

[0366] 100 base stations 101,205 Control section 102 Upper control signal generation unit 103 Downlink control information generation unit 104,206 Encoding section 105,207 Modulation section 106,208 Signal allocation section 107,209 Transmitter 108,201 Receiver 109,202 Extraction part 110,203 Demodulation section 111,204 Decoding section 200 devices< / option>

Claims

1. a control circuit for allocating a plurality of uplink signals to a resource in the time domain; a receiving circuit that receives at least one uplink signal among the plurality of uplink signals, the at least one uplink signal being determined based on information regarding the priorities of the plurality of uplink signals; Equipped with the control circuit sets a higher priority value in a physical layer for a scheduling request for uplink data, which is one of the plurality of uplink signals, and sets a lower priority value for a response signal, which is the other of the plurality of uplink signals, by downlink control information; the receiving circuit, when reception of one of the plurality of uplink signals overlaps with reception of the other of the plurality of uplink signals in a time domain, stops reception of the other of the plurality of uplink signals; the control circuit sets the number of priorities of the scheduling request to be smaller than the number of priorities of the logical channel corresponding to the uplink data; Base station.

2. one uplink signal among the plurality of uplink signals is a scheduling request for uplink data; The control circuit indicates information regarding the priority of the one uplink signal by a higher layer signal. The base station of claim 1.

3. The higher layer signal includes information regarding the resource of the one uplink signal. The base station according to claim 2.

4. one of the plurality of uplink signals is a scheduling request; the other of the plurality of uplink signals is a response signal to which the same priority value as that of the scheduling request is set, the receiving circuit receives at least one of the plurality of uplink signals when reception of the one of the plurality of uplink signals overlaps with reception of the other of the plurality of uplink signals in a time domain; The base station of claim 1.

5. Allocating a resource in the time domain for transmission of a plurality of uplink signals; receiving at least one uplink signal among the plurality of uplink signals, the at least one uplink signal being determined based on information regarding the priority of the plurality of uplink signals; a physical layer setting a higher priority value for a scheduling request for uplink data, which is one of the plurality of uplink signals, and a downlink control information setting a lower priority value for a response signal, which is the other of the plurality of uplink signals; When reception of one of the plurality of uplink signals overlaps with reception of another of the plurality of uplink signals in a time domain, reception of the other of the plurality of uplink signals is stopped; setting the number of priorities of the scheduling request to be smaller than the number of priorities of the logical channel corresponding to the uplink data; Communication method.

6. one uplink signal among the plurality of uplink signals is a scheduling request for uplink data; Indicating information regarding the priority of the one uplink signal by a higher layer signal; The communication method according to claim 5.

7. The higher layer signal includes information regarding the resource of the one uplink signal. The communication method according to claim 6.

8. one of the plurality of uplink signals is a scheduling request; the other of the plurality of uplink signals is a response signal to which the same priority value as that of the scheduling request is set, When reception of one of the plurality of uplink signals overlaps in a time domain with reception of another of the plurality of uplink signals, at least the other of the plurality of uplink signals is received. The communication method according to claim 5.

9. an allocation process for allocating a plurality of uplink signal transmissions to a certain resource in the time domain; receiving at least one uplink signal among the plurality of uplink signals, the at least one uplink signal being determined based on information about the priorities of the plurality of uplink signals; the allocation process includes setting a higher priority value in a physical layer for a scheduling request for uplink data, which is one of the plurality of uplink signals, and setting a lower priority value for a response signal, which is the other of the plurality of uplink signals, by downlink control information; When reception of one of the plurality of uplink signals overlaps with reception of another of the plurality of uplink signals in a time domain, the reception process stops reception of the other of the plurality of uplink signals; the allocation process sets the number of priorities of the scheduling request to be smaller than the number of priorities of the logical channel corresponding to the uplink data. Integrated circuit.

Images