Terminal and wireless communication method

Abstract

This terminal receives downlink control information, and in data distribution directed toward a plurality of terminals, determines an automatic-repeat-request feedback method, on the basis of information related to priority pertaining to the downlink control information.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method that support multicast / broadcast services. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 17 targets simultaneous data transmission (also called distribution) services (provisional name: MBS: Multicast and Broadcast Services) in NR to multiple specified or unspecified terminals (User Equipment, UE) (Non-Patent Document 1).

[0004] In MBS, for example, studies are underway on scheduling of UE groups that are the subject of services, and improving reliability (for example, feedback of HARQ (Hybrid Automatic Repeat Request) to radio base stations (gNBs)). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 Summary of the Invention

[0006] In the HARQ of MBS, it is assumed that a method of feeding back both ACK / NACK (ACK / NACK feedback) and a method of feeding back only NACK (NACK-only feedback) will be applied.

[0007] However, there is a problem in that the UE cannot select an appropriate method, such as which method to apply and how to apply it, for example, whether to basically fix it to one of the methods (semi-statically) or dynamically switch between both methods.

[0008] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal and a wireless communication method that can appropriately use ACK / NACK feedback and NACK-only feedback.

[0009] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that determines a method of feedback of an automatic repeat request in a downlink channel based on information regarding the priority of the downlink control information in data distribution to multiple terminals.

[0010] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that determines a method of feedback of an automatic repeat request based on information about an uplink control channel related to the downlink control information in data distribution to multiple terminals.

[0011] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that determines a method of feedback of an automatic repeat request based on the format of the downlink control information, settings related to reception of the downlink control information, or the automatic repeat request process, in data distribution to multiple terminals.

[0012] One aspect of the present disclosure is a terminal (UE200) that includes a transmitter (data transmitter / receiver 260) that transmits feedback of an automatic repeat request, and a control unit (control unit 270) that does not assume multiplexing of feedback information of different methods when different methods are applied to feedback of an automatic repeat request on a downlink channel in data distribution to multiple terminals.

[0013] One aspect of the present disclosure is a wireless communication method including the steps of receiving downlink control information and, in data distribution to multiple terminals, determining a method of feedback of an automatic repeat request in a downlink channel based on information regarding the priority associated with the downlink control information.

[0014] One aspect of the present disclosure is a wireless communication method including: receiving downlink control information; and determining, in data distribution to multiple terminals, a method of feedback of an automatic repeat request in a downlink channel based on information about an uplink control channel related to the downlink control information. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of PTM transmission method 1 and PTM transmission method 2. In FIG. [Figure 4]Figure 4 is a functional block diagram of gNB100 and UE200. [Figure 5] FIG. 5 is a diagram showing an example of a sequence of PDCCH, PDSCH and HARQ feedback in MBS. [Figure 6] FIG. 6 is a diagram showing an example of correspondence between priority indicators and HARQ feedback according to operation example 1-1 and operation example 1-2. [Figure 7] FIG. 7 is a diagram showing an example of a DCI field (item) according to operation example 2-0. [Figure 8] FIG. 8 is a diagram showing an example of a condition in which multiplexing of HARQ feedbacks of different schemes is permitted according to operation example 4-2. [Figure 9] FIG. 9 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0017] (1) Overall configuration of the wireless communication system (1.1) System configuration example 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a plurality of terminals 200 (User Equipment 200, hereinafter, UE 200).

[0018] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0019] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

[0020] The NG-RAN 20 actually includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0021] The gNB 100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO, which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.

[0022] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows:

[0023] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0024] Furthermore, the wireless communication system 10 may also support a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support a frequency band exceeding 52.6 GHz up to 114.25 GHz. The wireless communication system 10 may also support a frequency band between FR1 and FR2.

[0025] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied. Furthermore, DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0026] FIG. 2 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.

[0027] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 symbols (e.g., 28 or 56 symbols). The number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz as shown in Figure 2).

[0028] The time direction (t) shown in Fig. 2 may be called a time domain, a symbol period, or a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a resource block group, a subcarrier, a BWP (Bandwidth part), a subchannel, a common frequency resource, etc.

[0029] (1.2) Provision of MBS The wireless communication system 10 may provide multicast and broadcast services (MBS).

[0030] For example, in a stadium or a hall, it is assumed that a large number of UEs 200 are located within a certain geographical area and receive the same data simultaneously. In such a case, it is effective to use MBS instead of unicast.

[0031] Note that unicast may be interpreted as one-to-one communication with the network, in which a specific UE 200 is designated (identification information unique to the UE 200 may be designated).

[0032] Multicast may be interpreted as one-to-many (specified many) communication with a network, specifying a specific number of UEs 200 (identification information for multicast may be specified). Note that the number of UEs 200 receiving the received multicast data may ultimately be one.

[0033] Broadcasting may be interpreted as one-to-one communication between the network and all UEs 200. The multicast / broadcast data may be identical copies of the data, but some parts of the data, such as the header, may be different. The multicast / broadcast data may be transmitted (distributed) simultaneously, but strict simultaneity is not necessarily required, and propagation delays and / or processing delays within the RAN node may be included.

[0034] The target UE 200 may be in a radio resource control (RRC) layer state of an idle state (RRC idle), a connected state (RRC connected), or another state (e.g., an inactive state). The inactive state may be interpreted as a state in which some RRC settings are maintained.

[0035] In MBS, the following three methods are assumed for scheduling multicast / broadcast PDSCH (Physical Downlink Shared Channel, which may also be called MBS PDSCH), specifically, scheduling MBS packets (which may also be read as data). Note that RRC connected UE may also be read as RRC idle UE or RRC inactive UE.

[0036] ·PTM transmission method 1 (PTM-1): · For the MBS group of RRC connected UEs, the group-common PDSCH is scheduled using the group-common PDCCH (Physical Downlink Control Channel).

[0037] The CRC of the PDCCH and the PDSCH are scrambled by a group-common RNTI (which may also be called a Radio Network Temporary Identifier, G-RNTI).

[0038] ·PTM transmission method 2 (PTM-2): · For the MBS group of RRC connected UE, the group-common PDSCH is scheduled using the UE-specific PDCCH.

[0039] The PDCCH CRC is scrambled by the UE-specific RNTI.

[0040] The PDSCH is scrambled using the group-common RNTI.

[0041] ·PTP transmission method: For RRC connected UEs, UE-specific PDSCH is scheduled using UE-specific PDCCH.

[0042] The CRC of the PDCCH and the PDSCH are scrambled by a UE-specific RNTI, which may mean that the MBS packet is transmitted by unicast.

[0043] Figure 3 shows configuration examples of PTM transmission method 1 and PTM transmission method 2. Note that the UE-specific PDCCH / PDSCH can be identified by the target UE, but does not need to be identified by other UEs in the same MBS group. The group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group. The names of PTM transmission methods 1 and 2 are tentative, and they may be called by different names as long as the above-mentioned operations are performed.

[0044] Note that in point-to-point (PTP) delivery, the RAN node may deliver individual copies of the MBS data packet over the air to individual UEs, and in point-to-multipoint (PTM) delivery, the RAN node may deliver a single copy of the MBS data packet over the air to a set of UEs.

[0045] Furthermore, in order to improve the reliability of MBS, the following two feedback methods are envisaged for HARQ (Hybrid Automatic repeat request) feedback, specifically, HARQ feedback for multicast / broadcast PDSCH.

[0046] Option 1: Feedback both ACK and NACK (ACK / NACK feedback) UE that successfully receives and decodes PDSCH sends ACK · UEs that fail to receive and decode PDSCH send NACK PUCCH (Physical Uplink Control Channel) resource configuration: PUCCH-Config can be configured for multicast. PUCCH resources: shared / orthogonal between UEs, depending on network configuration HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) Multiplexing: Unicast or multicast can be applied Option 2: NACK-only feedback · UE that successfully receives and decodes PDSCH does not send ACK (does not send a response) · UEs that fail to receive and decode PDSCH send NACK For a given UE, PUCCH resource configuration can be configured separately via unicast or groupcast (multicast) Note that ACK may be called a positive acknowledgement, and NACK may be called a negative acknowledgement. HARQ may be called an automatic repeat request.

[0047] To enable or disable option 1 or option 2, one of the following may be applied:

[0048] RRC and Downlink Control Information (DCI) RRC only Furthermore, the following is assumed for SPS (Semi-persistent Scheduling) of multicast / broadcast PDSCH.

[0049] -SPS group-common PDSCH (also called group common SPS PDSCH) is used Multiple SPS group-common PDSCHs can be configured as UE capabilities. HARQ feedback for SPS group-common PDSCH is possible Activation / deactivation is possible via at least the group-common PDCCH (downlink control channel) Note that deactivation may be interpreted as another synonymous term such as release. For example, activation may be interpreted as start, start, trigger, etc., and deactivation may be interpreted as end, stop, etc.

[0050] SPS is a scheduling method used in contrast to dynamic scheduling, and may also be called semi-fixed, semi-persistent, or semi-persistent scheduling, and may also be interpreted as Configured Scheduling (CS).

[0051] Scheduling may be interpreted as a process of allocating resources for transmitting data. Dynamic scheduling may be interpreted as a mechanism in which all PDSCHs are scheduled by DCI (e.g., DCI 1_0, DCI 1_1, or DCI 1_2). SPS may be interpreted as a mechanism in which PDSCH transmissions are scheduled by higher layer signaling, such as RRC messages.

[0052] Note that multicast SPS PDSCH reception may refer to group common SPS PDSCH reception, may be an SPS PDSCH received by multiple terminals, or may be SPS PDSCH reception associated with a G-RNTI or G-CS-RNTI (i.e., an RNTI associated with multiple terminals). Also, multicast may be read as broadcast.

[0053] For the physical layer, there may be scheduling categories of time domain scheduling and frequency domain scheduling.

[0054] Furthermore, multicast, groupcast, broadcast, and MBS may be interchangeable. Multicast PDSCH and PDSCH scrambled with a group-common RNTI may be interchangeable.

[0055] Furthermore, the terms data and packet may be read interchangeably and may be interpreted as synonymous with terms such as signal, data unit, etc. Also, send, receive, transmit, and deliver may be read interchangeably.

[0056] (2) Functional block configuration of wireless communication system Next, a description will be given of the functional block configuration of the wireless communication system 10. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0057] Fig. 4 is a functional block diagram of the gNB 100 and the UE 200. The following describes the UE 200. As shown in Fig. 4, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0058] It should be noted that Fig. 4 shows only the main functional blocks relevant to the description of the embodiment, and that the UE 200 has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 shows the functional block configuration of the UE 200 (gNB 100), and for the hardware configuration, please refer to Fig. 9.

[0059] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0060] The radio signal transmitting / receiving unit 210 supports MBS, and can receive a downlink channel that is common to a terminal group (group common) in data distribution to multiple UEs 200.

[0061] Furthermore, the radio signal transmitting and receiving unit 210 can receive a downlink data channel (PDSCH) in MBS, that is, data distribution to multiple terminals.

[0062] Specifically, the radio signal transmitting and receiving unit 210 can receive a group-common PDSCH (which may include an SPS group-common PDSCH), which is a downlink data channel (PDSCH) common to a terminal group.

[0063] Furthermore, the radio signal transmitting and receiving unit 210 can receive a downlink control channel common to a terminal group, specifically a group-common PDCCH, and can receive a downlink control channel specific to a terminal, specifically a UE-specific PDCCH.

[0064] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0065] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).

[0066] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0067] Specifically, the control signal / reference signal processor 240 receives various control signals, such as control signals (messages) of the radio resource control layer (RRC), transmitted from the gNB 100 via a predetermined control channel. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0068] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0069] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0070] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0071] The channels include a control channel and a data channel. The control channels may include a PDCCH, a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0072] Furthermore, the data channel includes a PDSCH, a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel.

[0073] In this embodiment, the control signal and reference signal processor 240 may configure a receiver that receives downlink control information (DCI). Also, the control signal and reference signal processor 240 may receive, in RRC, a message indicating the enabling or disabling of a function instructed by DCI to enable or disable HARQ feedback.

[0074] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0075] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0076] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ). Specifically, the data transmitter / receiver 260 can transmit HARQ (Automatic Repeat Request) feedback. In this embodiment, the data transmitter / receiver 260 may constitute a transmitter.

[0077] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 executes control related to scheduling of downlink channels for MBSs and HARQ feedback of the channels.

[0078] The control unit 270 executes control corresponding to the scheduling of a downlink data channel that is common to a terminal group (group common) in the MBS, that is, data delivery to a plurality of UEs 200. Specifically, the control unit 270 can execute control corresponding to the scheduling of a group-common PDCCH and a group-common PDSCH.

[0079] Control unit 270 may assume that, for the SPS group-common PDSCH, activation / deactivation of SPS, that is, semi-static scheduling, of the downlink data channel (PDSCH) for the terminal group is applied on a terminal group basis.

[0080] Furthermore, the control unit 270 may determine a feedback scheme of HARQ (Automatic Repeat Request) in a downlink channel for data distribution to multiple terminals, i.e., for an MBS. Specifically, the control unit 270 may determine a feedback scheme of HARQ in a PDSCH (specifically, an MBS PDSCH) based on a priority field included in a DCI (Downlink Control Information) for an MBS. The HARQ feedback scheme may mean ACK / NACK feedback or NACK-only feedback.

[0081] Control unit 270 may apply either ACK / NACK feedback or NACK-only feedback to the MBS PDSCH based on the contents of information (which may be read as a field or signal, etc.) related to priority among the fields included in the DCI.

[0082] The DCI is not particularly limited as long as it is a scheduling DCI, but specifically, it may be a DCI (or a DCI format) that schedules an MBS PDSCH, and may be a field that indicates a priority related to HARQ among the fields included in the DCI. For example, the field may be called a priority indicator field, or may be another field related to an indication of priority. Alternatively, it may not be a field in the DCI, but may be predetermined information related to the DCI.

[0083] The control unit 270 may select ACK / NACK feedback when the priority is high, and may select NACK-only feedback when the priority is low. Alternatively, the control unit 270 may assume ACK / NACK feedback or NACK-only feedback for each value of the Priority indicator field. Note that, when the Priority indicator field is not included in the DCI, the control unit 270 may assume that ACK / NACK feedback or NACK-only feedback is specified by the DCI or an RRC parameter.

[0084] Furthermore, in the MBS, the control unit 270 may determine the HARQ feedback method for the downlink channel based on information related to the PUCCH (uplink control channel) included in the DCI.

[0085] Specifically, the control unit 270 may determine ACK / NACK feedback or NACK-only feedback corresponding to MBS PDSCH reception based on a field (signal) related to determining the slot / resource to which the PUCCH is allocated, among the fields of the DCI (or DCI format) that schedules the MBS PDSCH.

[0086] Furthermore, in the MBS, the control unit 270 may determine the HARQ feedback method for the downlink channel based on the DCI format, settings related to DCI reception, or the HARQ process.

[0087] Specifically, the control unit 270 may assume different DCI formats for ACK / NACK feedback and NACK-only feedback regarding HARQ feedback.

[0088] In addition, settings related to receiving DCI may include, for example, an RNTI (Radio Network Temporary Identifier) ​​that scrambles the CRC (Cyclic Redundancy Checksum) of the DCI, a control resource set (CORESET) or search space that transmits the DCI, and PDSCH resources notified by the DCI.

[0089] CORESET may be interpreted as a set of physical resources (specifically, a specific region on the DL resource grid) and parameters used to transmit the PDCCH (including DCI). The settings related to DCI reception may include other settings required for receiving the DCI. The HARQ process may typically be an HARQ process number, but may also be other information (e.g., redundancy version (RV), codebook (CB) number, etc.) that can directly or indirectly identify the HARQ process.

[0090] Furthermore, when the control unit 270 receives a plurality of TBs and the HARQ feedback methods for the respective TBs are different, the control unit 270 may perform an operation related to multiplexing the corresponding HARQ-ACK bits and transmit them.

[0091] Note that control unit 270 does not need to assume that HARQ-ACK bits of different schemes are multiplexed onto the same channel. Furthermore, when control unit 270 receives a plurality of transport blocks (TBs) and the HARQ feedback schemes for the TBs are different, if a predetermined condition is satisfied for the HARQ feedback of the different schemes, control unit 270 may multiplex the HARQ-ACK bits of the different schemes onto the same channel as a predetermined value and execute HARQ feedback.

[0092] Alternatively, when the control unit 270 receives multiple TBs and the HARQ feedback methods for the respective TBs are different, if a predetermined condition is satisfied for the different HARQ feedback methods, the control unit 270 may determine the HARQ feedback method based on information related to a predetermined DCI, multiplex the HARQ-ACK bits corresponding to the multiple TBs onto the same channel, and perform HARQ feedback.

[0093] In addition, when the control unit 270 receives multiple TBs and the HARQ feedback methods for each of the TBs are different, if a predetermined condition is satisfied for the HARQ feedback of the different methods, the control unit 270 may drop the feedback of one of the methods and send only the feedback of the other method.

[0094] In addition, gNB100 can perform the above-mentioned downlink channel scheduling and control related to HARQ.

[0095] (3) Operation of the wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the operation relating to scheduling of a downlink channel for an MBS and HARQ feedback of that channel.

[0096] 5 shows an example of a sequence of PDCCH, PDSCH, and HARQ feedback in MBS. As shown in FIG. 5, PDCCH (which may include DCI) and PDSCH may be transmitted by unicast or multicast (broadcast). UE 200 may also transmit HARQ feedback (ACK / NACK) for the channel (transport block (TB) received via the channel).

[0097] 5, it appears that both a unicast PDSCH and a multicast PDSCH are transmitted after one PDCCH / DCI, but either a unicast PDSCH or a multicast PDSCH may be transmitted after one PDCCH / DCI. In other words, one PDCCH / DCI may schedule either a unicast PDSCH or a multicast PDSCH.

[0098] Furthermore, as shown in FIG. 5, it is assumed that ACK / NACK feedback and NACK-only feedback are also applied to HARQ feedback for MBS, and the feedback result by ACK / NACK feedback and the feedback result by NACK-only feedback may be switched as appropriate.

[0099] In the case where both ACK / NACK feedback and NACK-only feedback are applied in MBS, a specific method is required, such as whether to change both methods to semi-static or dynamic.

[0100] An example of operation regarding such a decision on ACK / NACK feedback and NACK-only feedback (which may include switching, changing, and multiplexing of both feedback results) will be described below.

[0101] (3.1) Example 1 In this operation example, HARQ feedback = {ACK / NACK feedback, NACK-only feedback} corresponding to MBS PDSCH reception may be specified (this may also be read as determined, selected, etc.) based on a signal related to Priority among fields in the DCI or DCI format that schedules the MBS PDSCH.

[0102] Specifically, the UE 200 may operate in accordance with operation examples 1-0 to 1-6.

[0103] (Operation Example 1-0): The signal related to priority may be the priority indicator field in the DCI, or may be another field related to the indication of priority. The priority indicated by the priority indicator field or another field related to the priority indication may be the priority of the HARQ feedback or PUCCH (hereinafter referred to as HARQ feedback / PUCCH) corresponding to the scheduled PDSCH.

[0104] Based on such a priority, HARQ feedback={ACK / NACK feedback, NACK-only feedback} corresponding to MBS PDSCH reception may be specified by at least one of the methods in the following operation examples 1-1 to 1-4.

[0105] (Example 1-1): When the priority is high (e.g., priority indicator = 1), ACK / NACK feedback is used. (Example 1-2): When the priority is low (e.g., priority indicator = 0), NACK-only feedback is used. Fig. 6 shows an example of the correspondence between the priority indicator and HARQ feedback according to operation example 1-1 and operation example 1-2. As shown in Fig. 6, when the priority indicator = 1, ACK / NACK feedback may be used, and when the priority indicator = 0, NACK-only feedback may be used.

[0106] (Operation example 1-3): HARQ feedback = {ACK / NACK feedback, NACK-only feedback} is set for each priority indicator value. (Operation Example 1-4): For each priority indicator value (at least for either 0 or 1), it is set whether or not the HARQ feedback method is instructed by DCI. The indication may be given by any of the following:

[0107] A field (e.g., 1 bit) defined for indicating the HARQ feedback scheme C (Cell) - Field already present in the DCI format scrambled by RNTI DCI format RNTI scrambling the CRC of the DCI CORESET / Search Space to transmit DCI PDSCH resources (time / frequency / code / space) signaled by DCI PUCCH resources (time / frequency / code / space) notified by DCI (Operation Example 1-5): If the DCI scheduling the MBS PDSCH does not include a priority indicator field, the {ACK / NACK feedback, NACK-only feedback} set by the RRC parameters may be applied. If {ACK / NACK feedback, NACK-only feedback} is not set by the RRC parameters, a predetermined value, specifically, a method defined by default may be used (for example, ACK / NACK feedback or NACK-only feedback).

[0108] (Operation Example 1-6): If the DCI that schedules the MBS PDSCH does not include a priority indicator field, {ACK / NACK feedback, NACK-only feedback} may be determined based on the priority of the HARQ feedback / PUCCH configured by the RRC parameters. If the priority is not set by an RRC parameter, it may be a predetermined value (for example, ACK / NACK feedback or NACK-only feedback).

[0109] According to this operation example, it is possible to appropriately determine the HARQ feedback method depending on the priority.

[0110] (3.1') Example 1' In this operation example, {ACK / NACK feedback, NACK-only feedback} may be determined based on the priority of HARQ feedback / PUCCH set by an RRC parameter or defined in advance.

[0111] Specifically, the UE 200 may operate in accordance with operation examples 1'-1 and 1'-2.

[0112] (Operation Example 1'-1): Priority may be set for each specified parameter For example, a priority may be set for each CORESET index, CORESET pool index, and SS (Synchronization Signal) index.

[0113] (Operation Example 1'-2): Priority may be defined to be determined based on a predetermined rule. In this case, Priority does not have to be explicitly set. For example, it may be a rule based on the CORESET index, CORESET pool index, or SS index. Specifically, it may be a CORESET index for multicast or a CORESET index for unicast. Or it may be both indexes.

[0114] Also, it may be a CORESET pool index for multicast or a CORESET pool index for unicast, or it may be an index for both.

[0115] If the above-mentioned priority is not set by an RRC parameter, a default method may be used (for example, ACK / NACK feedback or NACK-only feedback). The priority may be a layer 1 (L1) priority or a layer 2 (L2) priority (logical channel priority).

[0116] (3.2) Example 2 In this operation example, HARQ feedback = {ACK / NACK feedback, NACK-only feedback} corresponding to MBS PDSCH reception may be specified based on a signal related to PUCCH slot / resource determination among fields in the DCI or DCI format that schedules the MBS PDSCH.

[0117] Specifically, the UE 200 may operate in accordance with operation examples 2-0 to 2-2.

[0118] (Operation Example 2-0): The signal related to PUCCH slot / resource determination may be at least one of specific fields of DCI, or may be another field related to an instruction for PUCCH slot / resource determination. 7 shows an example of a DCI field (item) according to operation example 2-0. As shown in FIG. 7, UE 200 may determine the HARQ feedback method corresponding to MBS PDSCH reception based on the content of at least one of the PUCCH resource indicator and the PDSCH-to-HARQ_feedback timing indicator fields.

[0119] The PUCCH resource indicator and the PDSCH-to-HARQ_feedback timing indicator are specified in 3GPP TS38.213.

[0120] (Operation Example 2-1): If the slot to which the PUCCH is allocated is a predetermined slot (or has a slot offset), a predetermined value (for example, ACK / NACK feedback or NACK-only feedback) may be used. The predetermined slot may be set in advance, or may be set each time by DCI, RRC, or the like.

[0121] (Operation Example 2-2): If the resource to which the PUCCH is allocated is a predetermined resource, a predetermined value (for example, ACK / NACK feedback or NACK-only feedback) may be used. The predetermined resource may be set in advance, or may be set each time by DCI, RRC, or the like.

[0122] In addition, a predetermined value may be associated with a PUCCH resource, a PUCCH resource set, or a PUCCH format (PF), and the associated predetermined value may be applied by specifying a PUCCH resource (by DCI, RRC parameter, or CCE (Control channel element) index) or determining a PUCCH resource set.

[0123] According to this operation example, the HARQ feedback method can be flexibly switched depending on the situation.

[0124] (3.3) Example 3 In this operation example, HARQ feedback = {ACK / NACK feedback, NACK-only feedback} corresponding to MBS PDSCH reception may be specified based on at least one of the signals or information related to DCI reception that schedules MBS PDSCH, such as the DCI format, settings related to DCI reception, or the HARQ process.

[0125] Specifically, the UE 200 may operate in accordance with operation examples 3-1 to 3-5.

[0126] (Example 3-1): DCI format ACK / NACK feedback and NACK-only feedback may be specified by different DCI formats. That is, ACK / NACK feedback and NACK-only feedback may be specified by separate DCI formats. In this case, the DCI format used may not be particularly limited, but DCI 1_0, DCI 1_1, DCI 1_2, or a new DCI format may be used.

[0127] UE 200 may perform ACK / NACK feedback for an MBS PDSCH scheduled in a predetermined DCI format, and may perform NACK-only feedback for an MBS PDSCH scheduled in a DCI format other than the predetermined one.

[0128] Alternatively, the above-mentioned formats may be distinguished by payload size or by a format indicator.

[0129] (Operation example 3-2): RNTI scrambling the CRC of DCI G1-RNTI may be defined as a group-common RNTI and may be used for scheduling Group-common PDSCH with ACK / NACK feedback. Also, G2-RNTI may be defined as a group-common RNTI and may be used for scheduling Group-common PDSCH with NACK-only feedback.

[0130] (Example 3-3): CORESET / search space for sending DCI (Operation example 3-4): PDSCH resources (time / frequency / code / space) notified by DCI (Example 3-5): HARQ process number Note that the association with the HARQ feedback scheme in each of the above-described operation examples may be defined in advance, or may be set by parameters of a higher layer such as RRC.

[0131] It is expected that the appropriate HARQ feedback scheme depends on the reliability requirement for the traffic. According to this operation example, it is possible to select the HARQ feedback scheme based on parameters that may differ for each traffic.

[0132] (3.4) Example 4 In this operation example, HARQ-ACK bits (feedback results) relating to two types of HARQ feedback methods (ACK / NACK feedback, NACK-only feedback) corresponding to MBS PDSCH reception may be multiplexed.

[0133] Specifically, the UE 200 may operate in accordance with operation examples 4-1 to 4-5.

[0134] (Example 4-1): It is not necessary to assume that HARQ-ACK bits of different methods are multiplexed on the same channel. For example, the UE 200 may not assume that the feedback resources for the HARQ-ACK bits of different schemes are configured / instructed to be performed in the same slot (or sub-slot), and the UE 200 may not assume that the feedback resources for the HARQ-ACK bits of different schemes are overlapped.

[0135] (Operation Example 4-2): When multiple TBs are received and the HARQ feedback methods for each TB are different (for example, when ACK / NACK feedback is specified for some of the multiple TBs and NACK-only feedback is specified for the rest), if specific conditions for the HARQ feedback of different methods are met, the HARQ-ACK bits of different methods may be multiplexed onto the same channel as a predetermined value, and HARQ feedback may be performed. That is, when the predetermined value indicates ACK / NACK feedback, all the multiplexed bits may be generated as ACK / NACK feedback. Note that the predetermined value here may be ACK / NACK feedback or NACK-only feedback. Furthermore, the PUCCH resource / resource set may be determined by a parameter associated with the predetermined value.

[0136] "When specific conditions for HARQ feedback of different methods are met" may be specified in multiple cases in terms of resources for the feedback, etc.

[0137] FIG. 8 shows an example of a condition in which multiplexing of HARQ feedbacks of different schemes is permitted according to operation example 4-2.

[0138] "When specific conditions for HARQ feedback of different schemes are satisfied" may mean that at least one of the conditions 1 to 6 shown in Fig. 8 is satisfied. However, it may also be based on a combination of multiple conditions.

[0139] (Operation Example 4-3): When multiple TBs are received and the HARQ feedback methods for each TB are different (for example, ACK / NACK feedback is specified for some of the multiple TBs and NACK-only feedback is specified for the rest), if a predetermined condition is satisfied for the different HARQ feedback methods, the HARQ feedback method may be determined based on information related to predetermined DCI, and the HARQ-ACK bits corresponding to the multiple TBs may be multiplexed and transmitted on the same channel. That is, when the HARQ feedback scheme for a certain DCI is ACK / NACK feedback, all the bits to be multiplexed may be generated as ACK / NACK feedback.

[0140] The predetermined DCI may be the last DCI in the time and frequency domain among the DCIs corresponding to the bits to be multiplexed. The last DCI may mean the last DCI format specified in 3GPP TS38.213 or the like. For example, it may be a DCI determined by the following, and the parameter name may be different.

[0141] a last DCI format among the DCI formats that have a value of a PDSCH-to-HARQ_feedback timing indicator field, if present, or a value of dl- DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, indicating a same slot for the PUCCH transmission, that the UE detects and for which the UE transmits corresponding HARQ-ACK information in the PUCCH where, for PUCCH resource determination, detected DCI formats are first indexed in an ascending order across serving cells indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes. Additionally, the PUCCH resource / resource set may be determined by parameters associated with the HARQ feedback scheme for a given DCI.

[0142] (Operation Example 4-4): When multiple TBs are received and the HARQ feedback methods for each TB are different (for example, when ACK / NACK feedback is specified for some of the multiple TBs and NACK-only feedback is specified for the rest), if a predetermined condition is met for the HARQ feedback of the different methods, the feedback of one of the methods may be dropped and only the feedback of the other method may be sent. For example, bits relating to NACK-only feedback may be dropped, or bits relating to ACK / NACK feedback may be dropped.

[0143] (Operation Example 4-5): At least two of Operation Examples 4-1 to 4-4 may be switched by a predetermined method. For example, the switching may be performed by a setting using an RRC parameter, or may be performed by an instruction using DCI or MAC-CE (Control Element).

[0144] According to this operation example, when bits of both feedback methods are multiplexed, it is possible to continue to satisfy the quality of HARQ operation expected by the network. On the other hand, when bits of both feedback methods are not multiplexed, it is possible to avoid complex processing in UE 200, which can contribute to load reduction.

[0145] This operation example may be applied in combination with other operation examples described above. In this case, for example, in operation examples 1 to 3, the operation when multiplexing and / or priority processing of PUCCH resources related to different HARQ feedback schemes is required becomes clear, and UE 200 can appropriately perform HARQ feedback.

[0146] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained. Specifically, in the MBS, the UE 200 can determine the HARQ feedback method for the MBS PDSCH based on a field related to priority included in the DCI. Also, in the MBS, the UE 200 may determine the HARQ feedback method for the downlink channel based on a field related to PUCCH (uplink control channel) included in the DCI.

[0147] In the MBS, the UE 200 may determine the HARQ feedback method in the downlink channel based on the DCI format, the DCI reception setting, or the HARQ process. In addition, the UE 200 may assume that, in the MBS, different methods are applied to the HARQ feedback in the downlink channel when certain conditions are met, and multiplex the feedback results.

[0148] Therefore, even when both the ACK / NACK feedback and NACK-only feedback methods are applied in MBS, the UE 200 can appropriately use the ACK / NACK feedback and the NACK-only feedback.

[0149] (5) Other embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments and that various modifications and improvements are possible.

[0150] For example, in the above-described embodiment, the names PDCCH and PDSCH are used as downlink channels, but the downlink control channel or downlink data channel (which may be a shared channel) may be called by another name.

[0151] Also, in the above description, "configure," "activate," "update," "indicate," "enable," "specify," and "select" may be interchangeable. Similarly, "link," "associate," "correspond," and "map" may be interchangeable, and "allocate," "assign," "monitor," and "map" may also be interchangeable.

[0152] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0153] Furthermore, the block diagram (FIG. 4) used in the description of the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0154] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0155] Furthermore, the gNB 100 and UE 200 described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 9 is a diagram showing an example of the hardware configuration of the device. As shown in Figure 9, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0156] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0157] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0158] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0159] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0160] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0161] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0162] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0163] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0164] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0165] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0166] Furthermore, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

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

[0168] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0169] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0170] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0171] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0172] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0173] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0174] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0175] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

[0179] Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0180] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

[0182] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0183] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0184] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0185] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

[0187] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

[0189] Furthermore, a base station in the present disclosure may be interpreted as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be interpreted as a side channel (or side link).

[0190] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0191] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

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

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

[0194] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

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

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

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

[0198] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

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

[0202] The time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each TTI, subframe, etc. may be composed of one or more resource blocks.

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

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

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

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

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

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

[0209] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0210] The reference signal may also be abbreviated as Reference Signal (RS), and may also be called a pilot depending on the applicable standard.

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

[0212] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

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

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

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

[0216] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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

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

[0219] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus

Claims

1. A data distribution system for a plurality of terminals, comprising: a receiving unit that receives downlink control information for scheduling reception of first data and downlink control information for scheduling reception of second data; a control unit that applies a first HARQ feedback scheme to a first HARQ feedback for the first data and applies a second HARQ feedback scheme different from the first HARQ feedback scheme to a second HARQ feedback for the second data; a transmitter that, when the first HARQ feedback and the second HARQ feedback overlap, multiplexes bits of the first HARQ feedback and bits of the second HARQ feedback onto the same channel using the first HARQ feedback scheme and transmits the HARQ feedback; A terminal comprising:

2. The terminal described in claim 1, wherein the control unit applies a feedback method that transmits both positive and negative responses as the first HARQ feedback method, and applies a feedback method that transmits only negative responses as the second HARQ feedback method.

3. The terminal described in claim 1, wherein the control unit applies a feedback method that transmits both a positive response and a negative response to a first HARQ feedback for the first data scheduled by downlink control information using a first group common RNTI, and applies a feedback method that transmits only a negative response to a second HARQ feedback for the second data scheduled by downlink control information using a second group common RNTI.

4. A terminal as described in claim 1, wherein, when a feedback method that transmits both positive and negative responses is applied as the first HARQ feedback method and a feedback method that transmits only negative responses is applied as the second HARQ feedback method, the transmitting unit transmits the HARQ feedback multiplexed on the same channel using resources associated with the first HARQ feedback method.

5. In data distribution to a plurality of terminals, a step of receiving downlink control information for scheduling reception of first data and downlink control information for scheduling reception of second data; applying a first HARQ feedback scheme to a first HARQ feedback for the first data and applying a second HARQ feedback scheme different from the first HARQ feedback scheme to a second HARQ feedback for the second data; and when the first HARQ feedback and the second HARQ feedback overlap, multiplexing bits of the first HARQ feedback and bits of the second HARQ feedback onto the same channel using the first HARQ feedback scheme to transmit HARQ feedback.

6. A communication system for distributing data to multiple terminals, the communication system includes a base station and the terminal; The base station a transmitter that transmits downlink control information that schedules transmission of the first data and downlink control information that schedules transmission of the second data; a receiving unit configured to receive a first HARQ feedback for the first data and a second HARQ feedback for the second data; The terminal a receiving unit that receives the downlink control information that schedules the transmission of the first data and the downlink control information that schedules the transmission of the second data; a control unit that applies a first HARQ feedback scheme to the first HARQ feedback for the first data and applies a second HARQ feedback scheme different from the first HARQ feedback scheme to the second HARQ feedback for the second data; a transmitting unit that, when the first HARQ feedback and the second HARQ feedback overlap, multiplexes bits of the first HARQ feedback and bits of the second HARQ feedback onto the same channel using the first HARQ feedback scheme and transmits HARQ feedback.

Images