Base station, communication method and integrated circuit

Abstract

To achieve appropriate wireless communication processing according to required conditions.SOLUTION: A base station includes: a control circuit that generates first downstream control information that directs allocation of a first channel and second downstream control information that directs allocation of a second channel, the first downstream control information including a parameter indicating a priority value and the second downstream control information including no parameter; and a communication circuit that transmits or receives at least one signal of the first channel and the second channel based on the priority value. When the parameter indicates that the priority value is small, the control circuit determines that the first and second channels have the same priority value.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a communication method. [Background technology]

[0002] 3GPP (3rd Generation Partnership Project) has completed the Release 15 NR (New Radio access technology) specification formulation for the realization of 5th generation mobile communication systems (5G). NR supports functions that realize ultra-reliable and low latency communication (URLLC) in addition to high speed and large capacity, which are 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] R1-1905092, “Discussion on UCI enhancement for URLLC,” Panasonic, RAN1#96bis, April 2019 [Non-Patent Document 4] R1-1905094, “Discussion on scheduling / HARQ enhancement for URLLC,” Panasonic, RAN1#96bis, April 2019 [Non-Patent Document 5] 3GPP TS38.133 V15.5.0, “NR; Requirements for support of radio resource management (Release 15),” March 2019 Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is room for consideration regarding appropriate wireless communication processing in accordance with required conditions.

[0005] Non-limiting embodiments of the present disclosure contribute to providing a terminal and a communication method capable of implementing 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 a method of determining priorities of a first channel and a second channel, whose resource allocations overlap each other in the time domain, based on parameters related to control information indicating the allocation of each of the first channel and the second channel, and a communication circuit that transmits or receives a signal for at least one of the first channel and the second channel based on the priorities.

[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. Effect 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 description of the drawings]

[0010] [Figure 1] FIG. 1 shows an example (Scenario 1) where resources for services with different requirements overlap in the time domain. [Diagram 2] FIG. 1 shows an example (Scenario 2) where resources for services with different requirements overlap in the time domain. [Diagram 3] FIG. 1 shows an example (Scenario 3) where resources for services with different requirements overlap in the time domain. [Figure 4] FIG. 1 shows an example (Scenario 4) where resources for services with different requirements overlap in the time domain. [Diagram 5] FIG. 13 is a diagram showing an example in which CORESETs are set overlapping in the time domain; [Figure 6] Diagram showing an application example of transmit beamforming [Figure 7] FIG. 1 is a block diagram showing a configuration example of a portion of a terminal according to a first embodiment; [Figure 8]FIG. 1 is a block diagram showing a configuration example of a base station according to a first embodiment; [Figure 9] FIG. 1 is a block diagram showing a configuration example of a terminal according to a first embodiment; [Figure 10] A flowchart showing an example of the operation of the terminal according to the first embodiment. [Figure 11] FIG. 13 is a diagram showing an example of setting CORESET and channels according to the second embodiment. [Figure 12] FIG. 13 is a diagram showing an example of setting CORESET and channels according to the third embodiment. [Figure 13] A flowchart showing an example of the operation of a terminal according to the fourth embodiment. [Figure 14] A flowchart showing an example of the operation of a terminal according to the sixth embodiment. [Figure 15] A flowchart showing another example of the operation of the terminal according to the sixth embodiment. [Figure 16] FIG. 1 shows an example of carriers with different subcarrier spacing. [Figure 17] FIG. 13 is a diagram showing an example of time difference correction between carriers. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0012] In NR, a terminal (also called UE (User Equipment)) is assumed to support a plurality of services having different requirements (e.g., eMBB, URLLC, etc.). In this case, in the terminal, reception resources (in other words, downlink resources or reception periods) or transmission resources (in other words, uplink resources or transmission periods) for the services having different requirements may overlap in the time domain (see, for example, Non-Patent Documents 1 and 2).

[0013] Hereinafter, cases (also called scenarios, for example) in which transmission and reception resources corresponding to services having different requirements in a terminal overlap in the time domain will be described.

[0014] <Scenario 1:Intra-UE DL prioritization (DL data / data resource conflicts)> In Scenario 1, for example, as shown in FIG. 1, a terminal receives a data signal (e.g., a downlink data signal or a PDSCH: Physical Downlink Shared Channel) for a service having different requirements (eMBB and URLLC in FIG. 1) in the downlink.

[0015] At this time, resources are assigned to the downlink data signals for each service by different control information (e.g., downlink scheduling assignment information, also called DL assignment). The DL assignment may be included in a downlink control channel (e.g., PDCCH: Physical Downlink Control Channel), as shown in FIG. 1.

[0016] In FIG. 1, resources allocated to downlink data signals for each service (eg, PDSCH resources) overlap in the time domain.

[0017] <Scenario 2:Intra-UE UL prioritization (UL data / data resource collision)> In Scenario 2, for example, as shown in FIG. 2, a terminal transmits a data signal (e.g., an uplink data signal or a PUSCH (Physical Uplink Shared Channel)) for a service having different requirements (eMBB and URLLC in FIG. 2) in the uplink.

[0018] At this time, resources are allocated to the uplink data signal for each service according to different control information (for example, uplink resource allocation information, also called UL grant). The UL grant may be included in the PDCCH, for example, as shown in FIG.

[0019] In FIG. 2, resources allocated to uplink data signals for each service (eg, resources for PUSCH) overlap in the time domain.

[0020] <Scenario 3:Intra-UE UL prioritization (UL control / control resource collision)> In Scenario 3, in downlink retransmission control (e.g., Hybrid Automatic Repeat Request (HARQ)), the terminal transmits a response signal (e.g., ACK / NACK: Acknowledgement / Negative Acknowledgement) indicating an error detection result of a downlink data signal (e.g., PDSCH) to a base station (also referred to as a gNB).

[0021] For example, as shown in Fig. 3, in the downlink, the terminal receives data signals (e.g., PDSCHs) for services (eMBB and URLLC in Fig. 3) having different requirements. The terminal also transmits ACK / NACKs for each PDSCH to the base station using an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel).

[0022] At this time, resources are allocated to the downlink data signal for each service and the PUCCH corresponding to the downlink data signal according to different control information (for example, downlink scheduling assignment information or DL ​​assignment).

[0023] In FIG. 3, the resources allocated to the PUCCH for each service overlap in the time domain.

[0024] <Scenario 4:Intra-UE UL prioritization (UL data / control resource collision)> In Scenario 4, for example, as shown in FIG. 4, the terminal transmits, in the uplink, a data signal (e.g., PUSCH) for one (e.g., URLLC) of services having different requirements (e.g., eMBB and URLLC in FIG. 4), and a control signal (e.g., ACK / NACK for PDSCH) for the other (e.g., eMBB).

[0025] At this time, resources are assigned to the uplink data signal according to uplink resource assignment information (e.g., UL grant), and resources are assigned to the downlink data signal and the PUCCH corresponding to the downlink data signal according to different downlink scheduling assignment information (e.g., DL assignment).

[0026] In FIG. 4, resources allocated to uplink data signals (eg, resources of the PUSCH) and resources allocated to the PUCCH overlap in the time domain.

[0027] Above, we have explained Scenarios 1 to 4.

[0028] In the above scenario, if a terminal has the capability to simultaneously receive or transmit signals of multiple channels, the terminal can simultaneously receive or transmit signals for services with different requirements without considering their influence on each other.

[0029] On the other hand, if the terminal does not have the capability to simultaneously receive or transmit signals of multiple channels, the terminal receives or transmits some of the multiple channels (either one of them in the above-mentioned scenario), or controls the transmission power of the multiple channels if the multiple channels are uplink channels.

[0030] In this case, if the terminal cannot simultaneously receive or transmit signals of multiple channels, the terminal determines which channel to receive or transmit the signal of. In other words, the terminal can determine the priority of receiving or transmitting signals of multiple channels.

[0031] For example, one example of a method for determining the priority of a channel is based on the reception timing (in other words, the reception order) of downlink control information (for example, DCI: Downlink Control Information) including a DL assignment or a UL grant at a terminal.

[0032] In this method, for example, when a terminal sequentially receives DCI including allocation information (e.g., DL assignment or UL grant) for each channel (in other words, each service), the terminal determines that the priority of a channel assigned by a DCI received later (in other words, later) is higher than the priority of a channel assigned by a DCI received earlier (in other words, earlier).

[0033] This is because when a channel assigned by a base station in a DCI (DL assignment or UL grant) that is first transmitted has a high priority, it is irrational to subsequently assign a lower priority channel to the resources of the higher priority channel in a redundant manner.

[0034] However, in the above-described method of determining priority, there is room for consideration of, for example, the following items (1), (2), and (3).

[0035] (1) In Scenario 4 (e.g., see FIG. 4), for example, the processing time taken by a terminal to generate a PUSCH (URLLC PUSCH in FIG. 4) is different from the processing time taken by a terminal to receive a PDSCH (eMBB PDSCH in FIG. 4), demodulate and decode the PDSCH, and generate a PUCCH including an ACK / NACK.

[0036] For this reason, when resources of PUSCH and PUCCH overlap in the time domain as in Scenario 4, the base station may not necessarily be able to transmit DCI corresponding to a high priority channel (e.g., URLLC channel) after DCI corresponding to a low priority channel (e.g., eMBB channel). Therefore, for example, in a terminal, DCI corresponding to a high priority channel may be received before DCI corresponding to a low priority channel, so that in a method in which channel priorities are determined based on the reception order of DCI, the terminal may not be able to appropriately determine channel priorities.

[0037] (2) In NR, a terminal receives DCI including at least one of DL assignment and UL grant from a base station. For example, a CORESET (Control Resource Set) and a search space are configured in the terminal for PDCCH, which is a control channel that transmits DCI. For example, the terminal monitors (in other words, blind decoding) a search space, which is the position of PDCCH candidates in the CORESET, and detects DCI addressed to the terminal. At this time, different CORESETs (or search spaces) may be configured in the terminal for services having different requirements. Also, for example, as shown in FIG. 5, at least some of the CORESETs configured for services having different requirements (eMBB and URLLC in FIG. 5) may be configured to overlap each other in the time domain.

[0038] In this case, when the terminal receives DCI corresponding to each service from each CORESET, it may not be able to determine which DCI was received last (in other words, which service has a higher priority). In other words, in the case of Fig. 5, it may not be possible to determine the priority between services (or channels) having different requirements (the method of determining the priority is unclear).

[0039] (3) In NR, for example, in high frequency bands of 6 GHz or more, the application of transmission beamforming in base stations is assumed. The application of transmission beamforming can ensure the communication distance and area between the base station and the terminal. For example, there is a configuration in which the base station transmits the PDCCH by sequentially switching beams within a slot (for example, also called beam sweeping). In addition, when beamforming is applied to the PDCCH, for example, as shown in FIG. 6, a CORESET (or search space) can be set for each beam (four beams in FIG. 6).

[0040] In this case, it is desirable that the CORESET (in other words, search space or PDCCH) to which the DCI is assigned is a CORESET corresponding to a beam appropriate for the terminal. For example, as shown in FIG. 6, among a plurality of resources in which a CORESET corresponding to each beam is respectively set in the time domain, a resource in which a CORESET corresponding to a beam appropriate for the terminal is set is assigned to the terminal. For this reason, the scheduling of the DCI in the time domain is restricted. Therefore, when beamforming is applied, the above-mentioned method of determining the priority based on the order of DCI may increase delay due to scheduling constraints.

[0041] Above, we have explained items (1), (2), and (3).

[0042] As another example of a method for determining the priority of a channel, Non-Patent Documents 3 and 4 disclose a method in which, for example, a base station notifies a terminal of information indicating the priority of a channel (hereinafter, also referred to as priority information or priority indication). The priority indication is notified, for example, by DL assignment or UL grant.

[0043] In Non-Patent Documents 3 and 4, for example, in the case of Scenario 4 (see, for example, FIG. 4) in which resources between PUSCH and PUCCH overlap in the time domain, the terminal determines which of PUSCH and PUCCH is to be prioritized based on the Priority indication included in the UL grant and DL assignment, respectively.

[0044] Also, in Non-Patent Documents 3 and 4, for example, in Scenarios 1, 2, and 3 (see, for example, Figs. 1, 2, and 3), the terminal sequentially receives DCI (including, for example, DL assignment or UL grant), and determines that the priority of a channel allocated by a DCI received later among the multiple DCIs is higher. Also, for example, when the DCI includes a Priority indication, the terminal does not assume that the priority of a channel allocated by a DCI received later among the multiple DCIs is set lower than the priority of a channel allocated by a DCI received earlier.

[0045] With these methods, even if channels transmitted or received by a terminal overlap in the time domain, the terminal can appropriately determine the priority between channels by the priority indication. However, this method does not consider the above items (2) and (3). For example, as in the above item (2), there is room to consider a method of determining the priority of channels in a case where resource areas (e.g., CORESET, search space, or PDCCH) including control information (e.g., DL assignment and UL grant) indicating the allocation of each of the channels overlapping in the time domain overlap in the time domain. Also, as in the above item (3), there is room to consider a method of determining the priority of channels in a case where a resource area (e.g., CORESET, search space, or PDCCH) including control information indicating the allocation of at least one of the channels overlapping in the time domain is, for example, a resource area in which a plurality of beams are respectively set.

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

[0047] Each embodiment will be described in detail below.

[0048] (Embodiment 1) [Communication system overview] The communication system according to each embodiment of the present disclosure includes a base station 100 and a terminal 200.

[0049] Fig. 7 is a block diagram showing a configuration example of a part of a terminal 200 according to an embodiment of the present disclosure. In the terminal 200 shown in Fig. 7, a control unit 205 (e.g., corresponding to a control circuit) determines a method of determining the priority of a first channel and a second channel, in which resource allocations overlap each other in the time domain, based on parameters related to control information (e.g., DCI) indicating the allocation of each of the first channel and the second channel. A receiving unit 201 and a transmitting unit 209 (e.g., corresponding to a communication circuit) receive or transmit a signal for at least one of the first channel and the second channel based on the priority.

[0050] [Base station configuration] Fig. 8 is a block diagram showing an example of the configuration of a base station 100 according to embodiment 1. In Fig. 8, 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.

[0051] Control section 101 determines information for DCI reception in terminal 200, and outputs, for example, the determined information to higher control signal generating section 102 and extraction section 109. The information for DCI reception may include, for example, CORESET, search space setting, and information related to the DCI field.

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

[0053] Furthermore, the control unit 101 determines information for terminal 200 to transmit an ACK / NACK for a downlink data signal, and outputs the determined information to the downlink control information generating unit 103 and the extracting unit 109. The information for transmitting an ACK / NACK may include, for example, information on a PUCCH resource.

[0054] In addition, the control unit 101 determines information (e.g., coding and modulation scheme and radio resource allocation) for the terminal 200 to transmit an uplink data signal, and outputs the determined information to the downlink control information generation unit 103, the extraction unit 109, and the decoding unit 111.

[0055] Furthermore, when the priority indication is applied, the control unit 101 determines the priorities of multiple channels (for example, PDSCH, PUSCH, or PUCCH) and outputs the determined priority information (for example, priority indication) to the downlink control information generating unit 103. Furthermore, the control unit 101 outputs the determined priority information to the extraction unit 109.

[0056] The upper layer control signal generating section 102 generates an upper layer control signal bit sequence based on the information inputted from the control section 101 , and outputs the upper layer control signal bit sequence to the encoding section 104 .

[0057] 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 with terminal-specific identification information. The terminal-specific identification information may be, for example, a Cell Radio Network Temporary Identifier (C-RNTI), a Modulation and Coding Scheme C-RNTI (MCS-C-RNTI), an RNTI introduced for URLLC, or another RNTI.

[0058] The encoding unit 104 encodes the downlink data signal, the bit string input from the higher control signal generating unit 102, or the DCI bit string input from the downlink control information generating unit 103, based on, for example, information input from the control unit 101 (for example, information regarding the coding rate), and outputs the encoded bit string to the modulation unit 105.

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

[0060] The signal allocation unit 106 maps the symbol sequence (including, for example, a downlink data signal 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.

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

[0062] 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 FFT (Fast Fourier Transform) processing on the received signal and outputs the obtained frequency domain signal to the extracting unit 109.

[0063] The extraction unit 109 determines information related to the channel of the signal transmitted by the terminal 200 (e.g., information related to a channel with a high priority) based on the information input from the control unit 101. The extraction unit 109 extracts, based on the determined information, a radio resource portion in which, for example, an uplink data signal or an ACK / NACK signal, 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.

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

[0065] The decoding unit 111 performs error correction decoding of at least one of the uplink data signal and the ACK / NACK signal 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.

[0066] [Device configuration] Fig. 9 is a block diagram showing an example configuration of terminal 200 according to this embodiment. In Fig. 9, terminal 200 has receiving section 201, extracting section 202, demodulating section 203, decoding section 204, control section 205, encoding section 206, modulating section 207, signal allocation section 208, and transmitting section 209.

[0067] The receiver 201 receives a downlink signal (e.g., a downlink data signal 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 wireless 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 the received signal into the frequency domain. The receiver 201 outputs the received signal to the extractor 202.

[0068] Based on information relating to the radio resource of the downlink control information input from the control unit 205, the extraction unit 202 extracts a radio resource portion including the 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. Also, based on information relating to the radio resource of the data signal input from the control unit 205, the extraction unit 202 extracts a radio resource portion including the downlink data signal, and outputs the extracted radio resource portion to the demodulation unit 203.

[0069] In addition, for example, in Scenario 1 (in other words, when a downlink data signal is received; see FIG. 1 for example), the extraction unit 202 extracts the downlink data signal from the received signal based on information regarding priority input from the control unit 205.

[0070] Demodulation section 203 demodulates the signal inputted from extraction section 202 and outputs the demodulated result to decoding section 204 .

[0071] The decoder 204 performs error correction decoding on the demodulation result input from the demodulator 203 to obtain, for example, downlink reception data, a higher layer control signal, or downlink control information. The decoder 204 outputs the higher layer control signal and the downlink control information to the controller 205, and outputs the downlink reception data.

[0072] The control unit 205 determines the priority of the channel based on, for example, information for DCI reception included in the upper layer control signal input from the decoding unit 204 (for example, information on CORESET, search space setting, or DCI field) and radio resource allocation information indicated in the downlink control information. The control unit 205 outputs information on the determined priority to the extraction unit 202 (for example, in the case of Scenario 1), and to the encoding unit 206 and the signal allocation unit (for example, in the case of Scenarios 2, 3, and 4). An example of a method for determining the priority of the channel will be described later.

[0073] Furthermore, the control unit 205 determines information regarding the transmission of an uplink signal, and outputs the determined information to the encoding unit 206 and the signal allocation unit 208. Furthermore, the control unit 205 determines information regarding the reception of a downlink signal, and outputs the determined information to the extraction unit 202.

[0074] The encoding unit 206 encodes the uplink data signal or an ACK / NACK signal for the downlink data signal based on the information input from the control unit 205 , and outputs the encoded bit string to the modulation unit 207 .

[0075] The modulation unit 207 modulates the coded bit sequence inputted from the coding unit 206 and outputs the modulated signal (symbol sequence) to the signal allocation unit 208 .

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

[0077] Furthermore, the signal allocation unit 208 determines an uplink channel for outputting a signal to the transmission unit 209 based on information regarding priority input from the control unit 205, for example, in the cases of Scenarios 2, 3, and 4 (in other words, when transmitting an uplink signal. See, for example, FIG. 2, FIG. 3, or FIG. 4).

[0078] 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 add a DFT (Discrete Fourier Transform) unit 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.

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

[0080] FIG. 10 shows an example of a flow of transmission and reception processing of terminal 200 according to this embodiment.

[0081] 10, terminal 200 receives DCI including a DL assignment or a UL grant from base station 100 (ST101). In FIG 10, as an example, terminal 200 receives DCI #1 and DCI #2, each of which corresponds to a service having different requirements.

[0082] For example, a CORESET and a search space are configured in terminal 200 in PDCCH, which is a control channel through which DCI is transmitted. Terminal 200, for example, monitors a search space, which is the position of PDCCH candidates in CORESET, and detects DCI addressed to terminal 200. Also, different CORESETs (or search spaces) may be configured for services having different requirements. Also, for example, as shown in FIG. 5, CORESETs corresponding to services having different requirements may be configured to overlap in the time domain. Thus, terminal 200 detects DCI#1 and DCI#2, for example, in different CORESETs (or search spaces).

[0083] Terminal 200 acquires resource allocation information indicating channel resources allocated to terminal 200 based on a DL assignment or UL grant included in each of detected DCI#1 and DCI#2 (ST102).

[0084] Terminal 200 determines, based on the acquired resource allocation information, for example, whether or not the relationship between allocated resources of channels (for example, PDSCH, PUSCH, or PUCCH) corresponding to services having different requirements corresponds to any of the above-mentioned Scenario 1, 2, 3, or 4 (ST103). In other words, terminal 200 determines whether or not allocated resources of channels corresponding to services having different requirements overlap in the time domain.

[0085] If the situation corresponds to any one of Scenario 1, 2, 3, or 4 (ST103: Yes), the terminal 200 judges whether or not a certain condition is satisfied (ST104).

[0086] The condition in embodiment 1 (hereinafter referred to as "Condition A") is a case where resource areas (e.g., CORESET, search space, or PDCCH; hereinafter, CORESET will be described as an example) including DCI#1 and DCI#2 received (in other words, detected) by terminal 200 are set to overlap in the time domain.

[0087] When Condition A is satisfied, that is, when CORESETs including DCI#1 and DCI#2 are set to overlap in the time domain (ST104: Yes), terminal 200 determines a channel to prioritize transmission or reception (in other words, channel priority) based on priority information (Priority indication) included in each DCI (ST105). In other words, when Condition A is satisfied, terminal 200 does not determine channel priority for DCI#1 and DCI#2 based on the timing (or order) at which they are received (or detected). For example, when Condition A is satisfied, terminal 200 may determine that the timing at which each DCI is received is the same.

[0088] In this way, when the CORESETs including DCI#1 and DCI#2 overlap in the time domain, terminal 200 selects a method of determining the priority of the channel according to the Priority indication. Here, as an example of the Priority indication, a priority indicated by one bit (e.g., 0 or 1) of the DCI may be set.

[0089] For example, in the Priority indication, "1" may indicate high priority and "0" may indicate low priority. For example, in DCI#1 and DCI#2 for services having different requirements, when the Priority indication of DCI#1 is 1 and the Priority indication of DCI#2 is 0, terminal 200 determines that the channel allocated by DCI#1 has a higher priority than the channel allocated by DCI#2. On the other hand, when the Priority indication of DCI#1 is 0 and the Priority indication of DCI#2 is 1, terminal 200 determines that the channel allocated by DCI#2 has a higher priority than the channel allocated by DCI#1.

[0090] The number of bits of the Priority indication is not limited to 1 bit, and may be multiple bits. Furthermore, the correspondence between the value of the Priority indication (for example, 0 and 1) and the priority level is not limited to the above example. Furthermore, the above example of the Priority indication can be applied to other embodiments.

[0091] 10, when Condition A is not satisfied, for example, when CORESETs including DCI#1 and DCI#2 are set without overlapping in the time domain (ST104: No), terminal 200 determines the channel priority for DCI#1 and DCI#2 based on the order of reception (or detection) (ST106). For example, terminal 200 determines that the priority of the channel assigned by the later received DCI out of DCI#1 and DCI#2 is higher than the priority of the channel assigned by the earlier received DCI.

[0092] In this way, when the CORESETs including DCI#1 and DCI#2 do not overlap in the time domain, terminal 200 selects a method of determining channel priorities according to the reception order of DCI.

[0093] Terminal 200 receives or transmits a signal of a channel allocated by at least one of DCIs DCI#1 and DCI#2 based on the resource allocation information of each channel and the determined priority of each channel (ST107).

[0094] On the other hand, if the processing in ST103 does not correspond to any of Scenarios 1, 2, 3, and 4 (ST103: No), that is, if the allocated resources of channels corresponding to services having different requirements do not overlap in the time domain, terminal 200 receives or transmits signals of channels allocated by DCI#1 and DCI#2 based on the resource allocation information of each channel (ST108).

[0095] As described above, in this embodiment, terminal 200 determines a method for determining the priority of channels in which resource allocations overlap in the time domain (e.g., a first channel corresponding to URLLC and a second channel corresponding to eMBB) based on information indicating resources such as a CORESET, search space, or PDCCH corresponding to DCI indicating the allocation of each of the first channel and the second channel (in other words, parameters related to control information).

[0096] For example, in this embodiment, terminal 200 selects either a priority determination method based on a priority indication (e.g., a first determination method) or a priority determination method based on the receiving order of DCI (e.g., a second determination method) based on whether or not CORESETs corresponding to DCIs corresponding to services having different requirements overlap in the time domain.

[0097] As a result, when CORESETs including multiple DCIs are not overlappingly set in the time domain, terminal 200 can appropriately determine the priority of channels based on the order of reception of each DCI. In other words, terminal 200 can more easily determine the priority of channels without notification such as a priority indication.

[0098] Furthermore, when CORESETs each including multiple DCIs are configured to overlap in the time domain, terminal 200 can clearly determine a prioritized channel based on the priority indication, even when the reception timings of the DCIs are similar, for example.

[0099] Therefore, according to this embodiment, even when channels corresponding to services having different requirements overlap in the time domain and CORESETs (or search spaces or PDCCHs) including control information indicating the allocation of each of the channels overlapping in the time domain overlap in the time domain, terminal 200 can appropriately determine the priority of the channels and transmit and receive signals of channels according to the priority. As a result, this embodiment can realize appropriate wireless communication processing according to the requirements.

[0100] In the first embodiment, when terminal 200 receives (or detects) DCI, if CORESETs (or search spaces or PDCCHs) including each DCI are set to overlap in the time domain, terminal 200 determines a prioritized channel based on the Priority indication notified by the DCI. Here, for example, in the DCI introduced for URLLC, the control information notified by the DCI can be flexibly set. Therefore, for example, in the DCI introduced for URLLC, it is also possible to set whether or not there is a Priority indication.

[0101] Therefore, for example, when CORESET (or search space or PDCCH) is set to overlap in the time domain, base station 100 may include Priority indication in DCI and transmit it. In other words, when CORESET (or search space or PDCCH) does not overlap in the time domain, base station 100 does not include Priority indication in DCI. Thereby, for example, when terminal 200 does not determine the priority of the channel based on Priority indication, it is possible to reduce the DCI size.

[0102] (Embodiment 2) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0103] In this embodiment, the base station 100 applies transmission beamforming. For example, as shown in Fig. 11, multiple CORESETs (or search spaces) can be set within X consecutive OFDM symbols in a slot. For example, in Fig. 11, four CORESETs corresponding to four different beams (Beam 1, Beam 2, Beam 3, and Beam 4) are set.

[0104] A flow of transmission and reception processing of terminal 200 according to the present embodiment is, for example, similar to that of embodiment 1 (see, for example, FIG. 10). In the present embodiment, the processing of ST 104 shown in FIG. 10 is different from that of embodiment 1.

[0105] In ST104 shown in FIG. 10, terminal 200 determines whether or not a certain condition is satisfied (ST104).

[0106] The condition in the second embodiment (hereinafter referred to as "Condition B") is a case where a resource area (e.g., CORESET, search space, or PDCCH; hereinafter, CORESET will be described as an example) including at least one of DCI#1 and DCI#2 received (in other words, detected) by terminal 200 is one of multiple CORESETs set within X consecutive OFDM symbols in a slot. In other words, Condition B is a case where at least one of DCI#1 and DCI#2 is placed in any of multiple CORESETs set within X OFDM symbols.

[0107] When Condition B is satisfied, that is, when a CORESET including at least one of DCI#1 and DCI#2 is one of multiple CORESETs set within X OFDM symbols (ST104: Yes), terminal 200 determines a channel to prioritize transmission or reception (in other words, channel priority) based on priority information (Priority indication) included in each DCI (ST105). In other words, when Condition B is satisfied, terminal 200 does not determine channel priority for DCI#1 and DCI#2 based on the timing (or order) at which they are received (or detected). For example, when Condition B is satisfied, terminal 200 may determine that the timing at which each DCI is received is the same.

[0108] In this manner, when at least one of DCI#1 and DCI#2 is arranged in any one of the CORESETs set within X OFDM symbols, terminal 200 selects a method for determining channel priority according to the Priority indication.

[0109] On the other hand, if Condition B is not satisfied, for example if the CORESET including DCI#1 and DCI#2 is not one of the multiple CORESETs set within X OFDM symbols (ST104: No), terminal 200 determines the channel priority for DCI#1 and DCI#2 based on the order of reception (or detection) (ST106). For example, terminal 200 determines that the priority of the channel assigned by the later received DCI, of DCI#1 and DCI#2, is higher than the priority of the channel assigned by the earlier received DCI.

[0110] In this way, when at least one of DCI#1 and DCI#2 is not placed in any one of the CORESETs set within X OFDM symbols, terminal 200 selects a method of determining channel priority according to the reception order of DCI.

[0111] For example, in FIG. 11, the PDCCH including the DCI for URLLC is allocated to a resource earlier in the time domain than the PDCCH including the DCI for eMBB. Therefore, if terminal 200 determines the priority of the channel based on the reception order of DCI, the priority of the channel allocated by the DCI for eMBB is set higher than the priority of the channel allocated by the DCI for URLLC. However, as described above, in FIG. 11, transmission beamforming (e.g., Beams 1 to 4) is applied to the DCI for URLLC, and the PDCCH including the DCI for URLLC is arranged in a CORESET associated with an appropriate beam (Beam 2 in FIG. 11) for the PDCCH. In this way, when Condition B is satisfied, the scheduling in the time domain is restricted for the DCI (or PDCCH) to which transmission beamforming is applied.

[0112] In contrast, in the present embodiment, when Condition B is satisfied, for example, when beamforming is applied to DCI (or PDCCH), terminal 200 can appropriately determine the priority of a channel based on the Priority indication, regardless of the timing of receiving (or detecting) the DCI. For example, in FIG. 11, based on the Priority indication, the priority of a channel allocated by the DCI for URLLC may be set higher than the priority of a channel allocated by the DCI for eMBB.

[0113] As described above, in this embodiment, terminal 200 determines a method for determining the priority of channels (e.g., a first channel corresponding to URLLC and a second channel corresponding to eMBB) in which resource allocation overlaps in the time domain, based on information (e.g., X OFDM symbols) indicating resources corresponding to multiple beams that can be set in DCI.

[0114] For example, in this embodiment, terminal 200 selects either a priority determination method based on a priority indication or a priority determination method based on a reception order of DCI, based on whether at least one of DCI corresponding to a service having different requirements is placed in a CORESET corresponding to each of multiple beams.

[0115] As a result, according to the present embodiment, even when channels corresponding to services having different requirements overlap in the time domain and the application of beamforming limits the time domain scheduling of DCI, terminal 200 can appropriately determine the priority of the channel and transmit / receive signals of the channel according to the priority. As a result, in the present embodiment, appropriate wireless communication processing according to the requirements can be realized.

[0116] In this embodiment, X symbols may be set within the range of the number of symbols in a slot (for example, 14 symbols). The value of X may be a value determined by a standard, or may be statically set by a cell-specific, group-specific, or terminal-specific higher layer signal.

[0117] Also, for example, in URLLC, the introduction of a time unit shorter than a slot (for example, also called a subslot) is being considered. For example, a subslot may be a time unit consisting of seven symbols (not limited to seven symbols). For example, the slot described in the present embodiment may be replaced with a subslot.

[0118] (Embodiment 3) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0119] In this embodiment, the base station 100 applies transmission beamforming. For example, as shown in FIG. 12, a plurality of resource regions (for example, CORESET, search space, or PDCCH. In the following, CORESET will be described as an example) with different spatial reception parameters can be set. The spatial reception parameters may be called, for example, QCL (Quasi Co-Location)-TypeD. Different QCL-TypeD indicates, for example, different beam settings. For example, in FIG. 12, four CORESETs corresponding to four types of spatial reception parameters (for example, Beam 1, Beam 2, Beam 3, and Beam 4, respectively) are set.

[0120] In this embodiment, for example, as shown in FIG. 12, a set of CORESETs having different QCL-Type D is defined.

[0121] A flow of transmission and reception processing of terminal 200 according to the present embodiment is, for example, similar to that of embodiment 1 (see, for example, FIG. 10). In the present embodiment, the processing of ST 104 shown in FIG. 10 is different from that of embodiment 1.

[0122] In ST104 shown in FIG. 10, terminal 200 determines whether or not a certain condition is satisfied (ST104).

[0123] The condition in the third embodiment (hereinafter referred to as "Condition C") is a case where a CORESET including at least one of DCI#1 and DCI#2 received (in other words, detected) by terminal 200 is included in the above-mentioned collection of CORESETs. In other words, Condition C is a case where at least one of DCI#1 and DCI#2 is placed in a CORESET within the collection of CORESETs.

[0124] When Condition C is satisfied, that is, when a CORESET including at least one of DCI#1 and DCI#2 is included in the CORESET group (ST104: Yes), terminal 200 determines a channel to prioritize transmission or reception (in other words, channel priority) based on priority information (Priority indication) included in each DCI (ST105). In other words, when Condition C is satisfied, terminal 200 does not determine channel priority for DCI#1 and DCI#2 based on the timing (or order) at which they were received (or detected). For example, when Condition C is satisfied, terminal 200 may determine that the timing at which each DCI was received is the same.

[0125] In this way, when at least one of DCI#1 and DCI#2 is placed in any one of the resources (e.g., a set of CORESETs) corresponding to multiple QCL-Type Ds, terminal 200 selects a method for determining the channel priority according to the Priority indication.

[0126] On the other hand, if Condition C is not satisfied, for example, if the CORESET including DCI#1 and DCI#2 is not included in the CORESET group (ST104: No), terminal 200 determines the channel priority for DCI#1 and DCI#2 based on the order of reception (or detection) (ST106). For example, terminal 200 determines that the priority of the channel assigned by the later received DCI, of DCI#1 and DCI#2, is higher than the priority of the channel assigned by the earlier received DCI.

[0127] In this way, when at least one of DCI#1 and DCI#2 is not placed in any one of the resources (e.g., a set of CORESETs) corresponding to multiple QCL-TypeDs, terminal 200 selects a method of determining the channel priority according to the reception order of DCI.

[0128] For example, in FIG. 12, the PDCCH including the DCI for URLLC is allocated to a resource earlier in the time domain than the PDCCH including the DCI for eMBB. Therefore, if terminal 200 determines the priority of the channel based on the reception order of DCI, the priority of the channel allocated by the DCI for eMBB is set higher than the priority of the channel allocated by the DCI for URLLC. However, in FIG. 12, transmission beamforming (e.g., Beams 1 to 4) is applied to the DCI for URLLC, and the PDCCH including the DCI for URLLC is placed in a CORESET associated with an appropriate QCL-TypeD (spatial reception parameter) for the PDCCH. In this way, when Condition C is satisfied, the scheduling in the time domain is restricted for the DCI (or PDCCH) to which transmission beamforming is applied.

[0129] In contrast, in the present embodiment, when Condition C is satisfied, for example, when beamforming is applied to DCI (or PDCCH), terminal 200 can appropriately determine the priority of a channel based on the Priority indication, regardless of the timing of receiving (or detecting) the DCI. For example, in FIG. 12, based on the Priority indication, the priority of a channel allocated by a DCI for URLLC may be set higher than the priority of a channel allocated by a DCI for eMBB.

[0130] Thus, in this embodiment, terminal 200 determines a method for determining the priority of channels (e.g., a first channel corresponding to URLLC and a second channel corresponding to eMBB) in which resource allocation overlaps in the time domain, based on information (e.g., a set of CORESETs) indicating resources corresponding to multiple spatial parameters (e.g., QCL-TypeD) that can be set in DCI.

[0131] For example, in this embodiment, terminal 200 selects either a priority determination method based on a priority indication or a priority determination method based on the reception order of DCI, based on whether at least one of DCI corresponding to a service having different requirements is placed in a CORESET in the above set.

[0132] As a result, according to the present embodiment, even when channels corresponding to services having different requirements overlap in the time domain and the application of beamforming limits the time domain scheduling of DCI, terminal 200 can appropriately determine the priority of the channel and transmit / receive signals of the channel according to the priority. As a result, in the present embodiment, appropriate wireless communication processing according to the requirements can be realized.

[0133] In this embodiment, as a method of setting a set of CORESETs to which different QCL-TypeDs are set, for example, a set including the number of a CORESET or a search space may be set by a higher layer signal. Also, a time interval for a set of CORESETs may be introduced, and CORESETs (or search spaces or PDCCHs) to which different QCL-TypeDs are set that are included in the time interval may be regarded as one set. The time interval may be, for example, one slot, or may have a time length different from one slot.

[0134] Also, for example, in URLLC, the introduction of a time unit shorter than a slot (for example, also called a subslot) is being considered. For example, a subslot may be a time unit consisting of seven symbols (not limited to seven symbols). For example, the slot described in the present embodiment may be replaced with a subslot.

[0135] (Embodiment 4) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0136] In this embodiment, for example, when terminal 200 receives (or detects) DCI, if the resource areas (e.g., CORESET, search space, or PDCCH; hereinafter, CORESET will be described as an example) including each DCI are configured to overlap in the time domain (in other words, in the case of Condition A), a "reference timing" is introduced to determine the priority of the channel.

[0137] The reference timing may be, for example, the first symbol position or the last symbol position in the CORESET setting.

[0138] Fig. 13 shows an example of a flow related to transmission and reception processing of terminal 200 according to the present embodiment. Note that in Fig. 13, the same processes as those in embodiment 1 (e.g., Fig. 10) are given the same reference numerals, and the description thereof will be omitted. For example, in Fig. 13, the process of ST201 differs from that in embodiment 1 (e.g., the process of ST105 in Fig. 10).

[0139] 13, when Condition A is satisfied, that is, when CORESETs including DCI#1 and DCI#2 are set to overlap in the time domain (ST104: Yes), terminal 200 determines a channel to prioritize transmission or reception (in other words, channel priority) based on the reference timing corresponding to the CORESET including each DCI (ST201). For example, terminal 200 determines that, of DCI#1 and DCI#2, the channel assigned by the DCI whose reference timing is later in the time domain has a higher priority.

[0140] In this way, when the CORESETs containing DCI#1 and DCI#2 overlap in the time domain, terminal 200 selects a method for determining the channel priority based on information regarding the positions in the time domain of the resources corresponding to DCI#1 and DCI#2 (e.g., CORESET, search space, or PDCCH).

[0141] On the other hand, if the CORESETs including DCI#1 and DCI#2 do not overlap in the time domain, terminal 200 selects a method of determining channel priorities according to the reception order of DCI (ST106 in FIG. 13).

[0142] As described above, in this embodiment, terminal 200 determines a method for determining the priority of channels in which resource allocations overlap in the time domain (e.g., a first channel corresponding to URLLC and a second channel corresponding to eMBB) based on information indicating resources such as a CORESET, search space, or PDCCH corresponding to DCI indicating the allocation of each of the first channel and the second channel (in other words, parameters related to control information).

[0143] For example, in this embodiment, terminal 200 selects either a priority determination method based on the reference timing of the CORESET corresponding to each DCI, or a priority determination method based on the reception order of DCI, based on whether or not CORESETs corresponding to DCIs corresponding to services having different requirements overlap in the time domain.

[0144] As a result, when CORESETs including multiple DCIs do not overlap in the time domain, terminal 200 can appropriately determine the priority of channels based on the reception order of each DCI. Also, even when CORESETs including multiple DCIs overlap in the time domain, terminal 200 can clearly determine a prioritized channel based on the reference timing of CORESET. In other words, terminal 200 can more easily determine the priority of channels without notification from base station 100.

[0145] Therefore, according to this embodiment, even if channels corresponding to services having different requirements overlap in the time domain, terminal 200 can appropriately determine the priority of the channels and transmit and receive signals of the channels according to the priority. As a result, this embodiment can realize appropriate wireless communication processing according to the requirements.

[0146] (Variation of the fourth embodiment) The parameter that determines the priority of a channel is not limited to a reference timing (eg, a position in the time domain of a resource region that includes DCI).

[0147] When multiple resource regions (e.g., CORESET, search space, or PDCCH; CORESET will be described here as an example) are configured to overlap in the time domain, the first symbol position (or the last symbol position) in each CORESET configuration may be set to the same position, for example, as shown in Fig. 5. Thus, for example, the time length or number of symbols in the CORESET configuration (in other words, the length of the CORESET in the time domain) may be set as a parameter for determining the priority of the channel.

[0148] Terminal 200 may set higher the priority of a channel assigned by DCI transmitted in a CORESET having a shorter time length or number of symbols in the CORESET. For example, in the example shown in Fig. 5, the time length of the CORESET for URLLC is shorter than the time length of the CORESET for eMBB. Therefore, in the example shown in Fig. 5, the priority of a channel assigned by DCI transmitted in the CORESET for URLLC may be set higher than the priority of a channel assigned by DCI transmitted in the CORESET for eMBB.

[0149] Furthermore, the parameters that determine the priority of a channel may include both the reference timing and the time length of the CORESET (for example, the number of symbols).

[0150] For example, when terminal 200 receives (or detects) DCI, if CORESETs including each DCI are set overlapping in the time domain, terminal 200 first determines the priority of the channel based on the reference timing. In this case, terminal 200 may determine that the priority of a channel assigned by a DCI with a shorter time length (or number of symbols) of CORESET is higher if the reference timings (or priorities) are the same.

[0151] Alternatively, when terminal 200 receives (or detects) DCI, if CORESETs including each DCI are set overlapping in the time domain, terminal 200 first determines the priority of the channel based on the time length of the CORESET. In this case, terminal 200 may determine that the priority of the channel allocated by the DCI with the later reference timing is higher if the time lengths (or priorities) are the same.

[0152] (Embodiment 5) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0153] As described above, for example, a CORESET or a search space is configured for a PDCCH that is a control channel that transmits DCI in terminal 200. Terminal 200 monitors a search space that is a position of PDCCH candidates in the CORESET, and detects DCI addressed to terminal 200. Also, different CORESETs (or search spaces or PDCCHs) can be configured in terminal 200 for services having different requirements.

[0154] In this embodiment, multiple CORESETS are prohibited from being configured to overlap in the time domain for terminal 200. In other words, multiple CORESETS are configured in terminal 200 without overlapping in the time domain.

[0155] According to this embodiment, when terminal 200 receives (or detects) DCI, CORESETs (or search spaces or PDCCHs) including each DCI are not configured to overlap in the time domain, so terminal 200 can receive each DCI sequentially. Therefore, terminal 200 can determine the priority of channels allocated by each DCI, for example, based on the reception timing of the DCI (in other words, the reception order). For example, terminal 200 can clearly distinguish the reception timing of each DCI, and can clearly determine the prioritized channel, because CORESETs are not configured to overlap in the time domain.

[0156] Therefore, according to this embodiment, even if channels corresponding to services having different requirements overlap in the time domain, terminal 200 can appropriately determine the priority of the channels and transmit and receive signals of the channels according to the priority. As a result, this embodiment can realize appropriate wireless communication processing according to the requirements.

[0157] (Embodiment 6) A base station and a terminal according to the present embodiment have basic configurations in common with base station 100 and terminal 200 according to the first embodiment, and therefore will be described with reference to FIGS.

[0158] For example, in each of the first to third embodiments, under a certain condition (eg, Condition A, B, or C), terminal 200 determines the priority of a channel based on a priority indication notified by DCI.

[0159] Here, there may be cases where the priorities of channels that are allocated to terminal 200 in a time domain in an overlapping manner become the same. For example, a case where "1" indicates a high priority and "0" indicates a low priority in the Priority indication will be described. In this case, in DCIs (DCI#1 and DCI#2) for services having different requirements, if the Priority indications of both DCI#1 and DCI#2 are the same value of 1 or 0, terminal 200 determines that the priorities of the channels allocated by DCI#1 and DCI#2 are the same.

[0160] Alternatively, channels that are allocated to terminal 200 in a time domain that overlap each other may include a channel that is allocated by a DCI that does not include a priority indication.

[0161] For example, when terminal 200 supports services having a plurality of different requirements (e.g., eMBB and URLLC), a DCI including a Priority indication (in other words, a newly introduced DCI) may be configured for URLLC. On the other hand, a DCI not including a Priority indication (in other words, an existing NR DCI) may be configured for eMBB. In this case, a case may occur in which a DCI that allocates at least one channel among channels for services having a plurality of different requirements does not include a Priority indication.

[0162] In this embodiment, a method for determining the priority of channels in these cases will be described.

[0163] Hereinafter, operation example 1 and operation example 2 of terminal 200 in this embodiment will be described respectively.

[0164] <Example 1> In operation example 1, an operation example of terminal 200 in the case where channels having the same priority overlap in the time domain will be described.

[0165] Fig. 14 shows an example of a flow of transmission and reception processing of terminal 200 according to this embodiment. In Fig. 14, the same processes as those in embodiment 1 (e.g., Fig. 10) or embodiment 4 (e.g., Fig. 13) are denoted by the same reference numerals, and the description thereof will be omitted.

[0166] In FIG. 14, when a certain condition (for example, Condition A, Condition B or Condition C) is satisfied (ST104: Yes), terminal 200 determines a channel to prioritize transmission or reception on, based on a Priority indication included in each DCI (ST105).

[0167] Here, terminal 200 determines whether the priorities determined for each channel based on the Priority indication notified by each DCI are the same (ST301). In other words, terminal 200 determines whether the priority of the channel can be clearly determined by the processing of ST105. If the Priority indications notified by each DCI are not the same (ST301: No), terminal 200 performs the processing of ST107.

[0168] On the other hand, if the priority indication notified by each DCI is the same (ST301: Yes), terminal 200 determines the channel priority based on the position in the time domain (e.g., reference timing, or time length (or number of symbols)) of the resources (e.g., CORESET, search space, or PDCCH) corresponding to each DCI, as in embodiment 4 (ST201).

[0169] In other words, when the priority determined for each channel based on the Priority indication is the same as in any of the first to third embodiments, as shown in FIG. 14, terminal 200 may proceed to a priority determination process based on the reference timing as in the fourth embodiment.

[0170] Fig. 15 shows another example of the flow of transmission and reception processing of terminal 200 according to the present embodiment. In Fig. 15, the same processes as those in Fig. 14 are denoted by the same reference numerals, and the description thereof will be omitted.

[0171] For example, in FIG. 15, the operation in the case where the priority determined for each channel based on the Priority indication notified by each DCI is the same (ST301: Yes) differs from the operation shown in FIG.

[0172] 15, when the Priority indication (priority) notified by each DCI is the same (ST301: Yes), terminal 200 determines which of Condition B, Condition C, and Condition A is satisfied (ST401). In other words, terminal 200 determines whether CORESETs (or search spaces or PDCCHs) corresponding to the respective DCIs overlap in the time domain.

[0173] When CORESETs (or search spaces or PDCCHs) corresponding to the respective DCIs overlap in the time domain, for example in the case of Condition A (ST401: Yes), terminal 200 may determine the priority of the channels based on the reference timing (ST201), for example, as in embodiment 4. In other words, when the priorities of the channels determined based on the priority indication are the same as in any of embodiments 1 to 3, and when CORESETs (or search spaces or PDCCHs) including the respective DCIs are set to overlap in the time domain, terminal 200 may proceed to a priority determination process based on the reference timing as in embodiment 4.

[0174] On the other hand, in FIG. 15, if the CORESETs (or search spaces or PDCCHs) corresponding to the respective DCIs do not overlap in the time domain, for example, in the case of Condition B or Condition C (ST401: No), terminal 200 may determine the priority of the channels based on, for example, the order in which the DCIs are received.

[0175] <Example 2> In the second operation example, an operation example of terminal 200 in a case where a Priority indication is not included in DCI that allocates at least one channel among channels for a service having a plurality of different requirement conditions will be described.

[0176] For example, terminal 200 receives (or detects) DCIs (eg, DCI#1 and DCI#2) for services having different requirements.

[0177] At this time, there may be a case where one of DCI#1 and DCI#2 (for example, DCI#1) includes a Priority indication, and the other DCI (for example, DCI#2) does not include a Priority indication.

[0178] In this case, terminal 200 may determine that, for example, if the Priority indication of DCI#1 is 1 (e.g., indicating high priority), the priority of the channel allocated by DCI#1 is higher than the priority of the channel allocated by DCI#2.

[0179] On the other hand, for example, when the Priority indication of DCI#1 is 0 (for example, when indicating a low priority), terminal 200 may determine that the priority of the channel allocated by DCI#2 is higher than the priority of the channel allocated by DCI#1. Alternatively, terminal 200 may determine that the priorities of the channels allocated by DCI#1 and DCI#2 are the same in this case.

[0180] Furthermore, when neither DCI#1 nor DCI#2 includes a priority indication, terminal 200 may determine that the priorities of the channels allocated by DCI#1 and DCI#2 are the same.

[0181] If terminal 200 determines that the priorities of the channels allocated by DCI #1 and DCI #2 are the same, terminal 200 may perform the operation shown in FIG. 14 or FIG. 15, for example, as described above.

[0182] Operation example 1 and operation example 2 have been described above.

[0183] In this way, according to the present embodiment, even when the priorities of channels determined by the Priority indication are the same, or even when the Priority indication is not included in at least one of the multiple DCIs notified to terminal 200, terminal 200 can appropriately determine the priority of the channel and transmit / receive a signal of the channel according to the priority. As a result, in the present embodiment, it is possible to realize appropriate wireless communication processing according to the required conditions.

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

[0185] (Other embodiments) (1) In NR, for example, carrier aggregation is supported.

[0186] Carrier aggregation allows, for example, operation in which a carrier for transmitting a PDCCH and a carrier for transmitting a PDSCH allocated by the PDCCH are different (for example, called "cross-carrier scheduling").

[0187] Furthermore, in carrier aggregation, for example, cross-carrier scheduling between carriers having different numerologies (in other words, subcarrier spacing (SCS)) is supported.

[0188] FIG. 16 shows an example of cross-carrier scheduling between carriers having different numerologies.

[0189] In the example shown in FIG. 16, a CORESET (or search space or PDCCH) with the same number of symbols (e.g., 3 symbols) is set for both carriers (e.g., Carrier 1 with SCS=15 kHz and Carrier 2 with SCS=30 kHz). As shown in FIG. 16, even if the number of symbols of the CORESET (or search space or PDCCH) is the same, the CORESET length (time length) is different between carriers with different numerologies. In FIG. 16, the time length of the CORESET (e.g., 3 symbols) in Carrier 2 is shorter than the time length of the CORESET (e.g., 3 symbols) in Carrier 1.

[0190] Here, the situation of two CORESETs shown in Fig. 16 corresponds to, for example, a situation in which a plurality of CORESETs shown in Fig. 5 are set to overlap in the time domain. Thus, for example, in cross-carrier scheduling between carriers having different numerologies, when PDSCHs scheduled from each carrier overlap in the time domain within the same carrier, terminal 200 may operate based on at least one of, for example, the first embodiment, the fourth embodiment, and the sixth embodiment.

[0191] (2) In NR, for example, carrier aggregation is supported. In inter-band carrier aggregation in NR, for example, the terminal 200 allows a case where there is a reception slot timing difference (in other words, a time difference) between different carriers (see, for example, Non-Patent Document 5). For example, in Frequency Range 1 (FR1, for example, 6 GHz or less), a reception slot timing difference of up to 33 us is allowed.

[0192] For example, when the terminal 200 determines the channel priority at the reception timing of DCI, if there is a reception slot timing difference between carriers, as shown in FIG. 17, instead of the reception timing of DCI in absolute time, after correcting the reception slot timing difference (in other words, the time difference) to align the reception slot timings, the reception timing of DCI may be determined.

[0193] (3) In each of the above-described embodiments, the method by which the terminal 200 determines the channel priority when channels (in other words, reception resources or transmission resources) for services having different requirement conditions overlap in the time domain has been described.

[0194] After determining the channel priority, the terminal 200 may perform the following operations, for example, in the above-described scenarios (each of Scenario 1 to 4).

[0195] <Scenario 1 (see, for example, FIG. 1)> When the terminal 200 cannot receive (or perform demodulation and decoding processing) multiple PDSCHs simultaneously, the terminal 200 receives (or performs demodulation and decoding processing) the PDSCH with the highest priority. On the other hand, the terminal 200 does not perform the reception (or demodulation and decoding processing) of the PDSCH with the lowest priority. Further, the terminal 200 may generate a NACK for the PDSCH with the lowest priority for which reception (or demodulation and decoding processing) is not performed and feedback it to the base station 100.

[0196] <Scenario 2 (see, for example, FIG. 2)> When the terminal 200 cannot simultaneously transmit multiple PUSCHs, the terminal 200 transmits the PUSCH with a higher priority and does not transmit the PUSCH with a lower priority.

[0197] Alternatively, even if the terminal 200 can simultaneously transmit multiple PUSCHs, when the total transmission power exceeds the maximum transmission power, the transmission power of the PUSCH with a lower priority may be controlled (scaled).

[0198] <Scenario 3 (see, for example, FIG. 3)> When the terminal 200 cannot simultaneously transmit multiple PUCCHs, the terminal 200 transmits the PUCCH including ACK / NACK for a channel with a higher priority. On the other hand, the terminal 200 may drop (in other words, not transmit) the ACK / NACK for a channel with a lower priority.

[0199] Alternatively, the terminal 200 may multiplex the ACK / NACK for a channel with a lower priority onto the ACK / NACK for a channel with a higher priority and transmit each ACK / NACK in one PUCCH. At this time, the terminal 200 may multiplex the ACK / NACK for a channel with a higher priority onto the PUCCH in order. Also, when there is room in the resources set for the PUCCH, the terminal 200 may multiplex the ACK / NACK for a channel with a lower priority onto the PUCCH.

[0200] Alternatively, even if the terminal 200 can simultaneously transmit multiple PUCCHs, when the total transmission power exceeds the maximum transmission power, the transmission power of the PUCCH with a lower priority may be controlled (scaled).

[0201] <Scenario 4 (see, for example, FIG. 4)> When the terminal 200 cannot simultaneously transmit PUSCH and PUCCH, the terminal 200 may transmit the channel with a higher priority (PUSCH or PUCCH) and drop (in other words, not transmit) the channel with a lower priority (PUSCH or PUCCH).

[0202] Alternatively, terminal 200 may multiplex ACK / NACK onto a PUSCH and transmit the same.

[0203] Alternatively, if terminal 200 can simultaneously transmit a plurality of PUSCHs and PUCCHs, but the sum of the transmission power exceeds the maximum transmission power, the transmission power of a low priority channel (PUSCH or PUCCH) may be controlled (scaled).

[0204] (4) A priority indication is not limited to cases where it is explicitly indicated by DCI, but may also be indicated implicitly.

[0205] For example, the priority indication may be implicitly notified by the DCI format, the RNTI, or the search space, and terminal 200 may determine the priority of the channel based on the DCI format, the RNTI, or the search space.

[0206] For example, in the case of a DCI format, when terminal 200 receives DCI of a DCI format introduced for URLLC, terminal 200 may determine that the priority of a channel allocated by the DCI is higher than the priority of channels allocated by DCI of other DCI formats.

[0207] Also, for example, in the case of RNTI, if the detected RNTI is different from the C-RNTI, for example, if it is the MCS-C-RNTI introduced for URLLC in Rel. 15 or an RNTI newly introduced for URLLC, terminal 200 may determine that the priority of the channel assigned by the corresponding DCI is higher than the priority of channels assigned by other DCIs.

[0208] Furthermore, in the case of a search space, terminal 200 may determine the priority of a channel allocated by a DCI based on a search space number set in the search space in which the DCI is detected.

[0209] By implicitly reporting priority indication (eg, channel priority), the amount of signaling can be reduced.

[0210] Note that the method of implicitly notifying the priority indication is not limited to these. For example, it is sufficient that a parameter that enables terminal 200 to determine the priority of a channel (for example, eMBB and URLLC) is associated with the priority of the channel.

[0211] (5) In each of the above embodiments, the downlink control channel, the downlink data channel, the uplink control channel, and the uplink data channel are not limited to the PDCCH, the PDSCH, the PUCCH, and the PUSCH, respectively, and may be control channels with other names.

[0212] (6) The unit of time resource is not limited to the time resource (eg, slot or subslot) described in each of the above embodiments, and may be another time resource unit (eg, subframe or frame, etc.).

[0213] (7) The services having different requirements are not limited to eMBB and URLLC, but may be other services.

[0214] The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiment may be realized partially or entirely as an LSI, which is an integrated circuit, and each process described in the above embodiment may be controlled partially or entirely by one LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of one chip to include some or all of the functional blocks. The LSI may have input and output data. Depending on the degree of integration, the LSI may be called an IC, a system LSI, a super LSI, or an ultra LSI. The method of integration is not limited to LSI, and may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, a field programmable gate array (FPGA) that can be programmed after LSI manufacture, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells inside the LSI may be used. The present disclosure may be realized as digital processing or analog processing. Furthermore, if an integrated circuit technology that can replace LSI appears due to the progress of semiconductor technology or a different derived technology, it is natural that such technology may be used to integrate the functional blocks. The application of biotechnology, etc. is also a possibility.

[0215] The present disclosure may be implemented in any type of apparatus, device, or system having a communication function (collectively referred to as a communication apparatus). The communication apparatus may include a radio transceiver and processing / control circuitry. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio 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, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices, etc.), game consoles, digital book readers, telehealth and telemedicine devices, communication-enabled vehicles or mobile conveyances (e.g., cars, airplanes, boats, etc.), and combinations of the above devices.

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

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

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

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

[0220] A terminal according to one embodiment of the present disclosure includes a control circuit that determines a method of determining priorities of a first channel and a second channel, whose resource allocations overlap each other in the time domain, based on parameters related to control information indicating the allocation of each of the first channel and the second channel, and a communication circuit that transmits or receives a signal for at least one of the first channel and the second channel based on the priorities.

[0221] In a terminal according to one embodiment of the present disclosure, the control circuit selects, based on the parameter, either a first determination method for determining the priority according to notification information indicating the priority received from a base station, or a second determination method for determining the priority according to a receiving order of the control information.

[0222] In a terminal according to one embodiment of the present disclosure, the parameters include information indicating resources corresponding to the control information, and the control circuit selects the first determination method when the resources corresponding to the control information overlap in the time domain.

[0223] In a terminal according to an embodiment of the present disclosure, the control circuit selects the second determination method when resources corresponding to the control information do not overlap in a time domain.

[0224] In a terminal according to one embodiment of the present disclosure, the parameters include information indicating resources corresponding to a plurality of beams that can be set in the control information, and the control circuit selects the first determination method when at least one of the control information is placed in any one of the resources corresponding to the plurality of beams.

[0225] In a terminal according to one embodiment of the present disclosure, the control circuit selects the second determination method when at least one of the control information is not placed in any one of the resources corresponding to each of the multiple beams.

[0226] In a terminal according to one embodiment of the present disclosure, the parameters include information indicating resources corresponding to a plurality of spatial parameters that can be set in the control information, and the control circuit selects the first determination method when at least one of the control information is placed in any one of the resources corresponding to the plurality of spatial parameters.

[0227] In a terminal according to one embodiment of the present disclosure, the control circuit selects the second determination method when at least one of the control information is not placed in any one of the resources corresponding to each of the plurality of spatial parameters.

[0228] In a terminal according to one embodiment of the present disclosure, the parameters include information indicating resources corresponding to the control information, and when the resources corresponding to the control information overlap in the time domain, the control circuit determines the priority based on information regarding at least one of the positions and lengths in the time domain of the resources corresponding to each of the control information.

[0229] In a terminal according to an embodiment of the present disclosure, when resources corresponding to the control information do not overlap in a time domain, the control circuit determines the priority based on a reception order of the control information.

[0230] In a terminal according to one embodiment of the present disclosure, when the priorities determined for the first channel and the second channel are identical, the control circuit determines the priorities based on information regarding at least one of the positions and lengths in the time domain of resources corresponding to each of the control information.

[0231] In a terminal according to one embodiment of the present disclosure, when the priorities determined for the first channel and the second channel are identical and when the resources corresponding to each of the control information overlap in the time domain, the control circuit determines the priority based on information regarding at least one of the position and length in the time domain of the resources corresponding to each of the control information.

[0232] In a terminal according to one embodiment of the present disclosure, when the priorities determined for the first channel and the second channel are identical and when the resources corresponding to each of the control information do not overlap in the time domain, the control circuit determines the priority based on the order of reception of the control information.

[0233] A communication method according to one embodiment of the present disclosure determines a method for determining the priority of a first channel and a second channel, whose resource allocations overlap each other in the time domain, based on parameters related to control information indicating the allocation of each of the first channel and the second channel, and transmits or receives a signal for at least one of the first channel and the second channel based on the priority.

[0234] The disclosures of the specification, drawings and abstract contained in the U.S. provisional application no. 62 / 839,128 filed on April 26, 2019, and the Japanese application no. 2019-089057 filed on May 9, 2019 are incorporated herein by reference in their entirety. [Industrial Applicability]

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

[0236] 100 base stations 101,205 Control section 102 Upper control signal generation unit 103 Downlink control information generator 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 terminals

Claims

1. a control circuit that generates first downlink control information instructing allocation of a first channel and second downlink control information instructing allocation of a second channel, the first downlink control information including a parameter indicating a priority value, and the second downlink control information not including the parameter; a communication circuit for transmitting or receiving a signal on at least one of the first channel and the second channel based on the priority value; if the parameter indicates that the priority value is smaller, the control circuit determines that the priority values ​​of the first channel and the second channel are the same; Base station.

2. when a transmission of the first channel having a higher priority value overlaps on a time axis with a transmission of the second channel having a lower priority value, the communication circuit receives the first channel. The base station according to claim 1 .

3. the communication circuit receives the first channel when the parameter indicates that the priority is high and transmission of the first channel overlaps in time with transmission of the second channel; The base station according to claim 1 .

4. When the first downlink control information and the second downlink control information do not include a parameter indicating the priority value, the control circuit determines that the priority values ​​of the first channel and the second channel are the same. The base station according to claim 1 .

5. the first channel is a physical uplink shared channel, and the second channel is a physical uplink control channel; when a transmission of the first channel having a higher priority value overlaps on a time axis with a transmission of the second channel having a lower priority value, the communication circuit receives the first channel. The base station according to claim 1 .

6. the first channel and the second channel are physical uplink control channels; when a transmission of the first channel having a higher priority value overlaps on a time axis with a transmission of the second channel having a lower priority value, the communication circuit receives the first channel. The base station according to claim 1 .

7. notifying at least one of the priority values ​​of the first channel and the second channel by one bit of the first downlink control information or the second downlink control information; The base station according to claim 1 .

8. The base station is generating first downlink control information instructing allocation of a first channel and second downlink control information instructing allocation of a second channel, the first downlink control information including a parameter indicating a priority value and the second downlink control information not including the parameter; Transmitting or receiving at least one signal on the first channel and the second channel based on the priority value; if the parameter indicates that the priority value is smaller, determining that the priority values ​​of the first channel and the second channel are the same; Communication methods.

9. receiving the first channel when the transmission of the first channel having a larger priority value overlaps on a time axis with the transmission of the second channel having a smaller priority value; The communication method according to claim 8.

10. the first downlink control information includes a parameter indicating a value of the priority, and the second downlink control information does not include the parameter; receiving the first channel if the parameter indicates that the priority value is large and transmission of the first channel overlaps in time with transmission of the second channel; The communication method according to claim 8.

11. if the first downlink control information and the second downlink control information do not include a parameter indicating the priority value, it is determined that the priority values ​​of the first channel and the second channel are the same; The communication method according to claim 8.

12. the first channel is a physical uplink shared channel, and the second channel is a physical uplink control channel; receiving the first channel when the transmission of the first channel having a larger priority value overlaps on a time axis with the transmission of the second channel having a smaller priority value; The communication method according to claim 8.

13. the first channel and the second channel are physical uplink control channels; When the transmission of the first channel having a larger priority value overlaps on a time axis with the transmission of the second channel having a smaller priority value, the first channel is received. The communication method according to claim 8.

14. notifying at least one of the priority values ​​of the first channel and the second channel by one bit of the first downlink control information or the second downlink control information; The communication method according to claim 8.

15. generating first downlink control information instructing allocation of a first channel and second downlink control information instructing allocation of a second channel, the first downlink control information including a parameter indicating a priority value and the second downlink control information not including the parameter; transmitting or receiving signals on at least one of the first channel and the second channel based on the priority value; if the parameter indicates that the priority value is small, in the process of determining the priority value, it is determined that the priority values ​​of the first channel and the second channel are the same; Integrated circuits.

Images