Terminal and radio communication method

Abstract

To provide a terminal and a radio communication method with which it is possible to efficiently and reliably execute an operation along with a preset scheduling in a simultaneous data transmission service to a plurality of specified or unspecified terminals.SOLUTION: In a data distribution intended for a plurality of terminals, the terminals receive a downlink data channel that is common to terminal groups. It is assumed that the terminal groups of the terminals are divided in a plurality of subgroups, and a preset scheduling of the downlink data channel is applied in units of the subgroups.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present disclosure relates to a terminal compatible with multicast / broadcast services and a wireless communication method.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is standardizing the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and is also promoting the standardization of the next generation called Beyond 5G, 5G Evolution or 6G.

[0003] In Release 17 of 3GPP, the target is a service (tentatively called MBS: Multicast and Broadcast Services) of simultaneously transmitting data (also called distribution) to a plurality of specific or unspecified terminals (User Equipment, UE) in NR (Non-Patent Document 1).

[0004] In MBS, for example, scheduling of a UE group targeted by a service and improvement of reliability (for example, feedback to a radio base station (gNB) of HARQ (Hybrid Automatic Repeat Request)) are being studied.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

Summary of the Invention

[0006] In MBS, the UE needs to efficiently and reliably perform operations associated with the activation / deactivation of semi-persistent (which may also be called semi-persistent) scheduling of the downlink data channel common to the UE group, specifically, the Physical Downlink Shared Channel (PDSCH).

[0007] Also, confirmation for the activation / deactivation of the scheduling needs to be reliably performed.

[0008] Therefore, the following disclosure is made in view of such a situation, and aims to provide a terminal and a wireless communication method that can efficiently and reliably perform operations associated with semi-persistent scheduling in a simultaneous data transmission service to a specific or unspecific plurality of terminals.

[0009] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (radio signal transceiver unit 210) that receives a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and a control unit (control unit 270) that assumes that the terminal group is divided into a plurality of sub-groups, and activation or deactivation of semi-persistent scheduling of the downlink data channel is applied in units of the sub-groups.

[0010] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (radio signal transceiver unit 210) that receives a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and a control unit (control unit 270) that assumes that feedback of an automatic repeat request in the downlink data channel is transmitted in different time regions for each terminal.

[0011] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (radio signal transceiver 210) that receives a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and a control unit (control unit 270) that applies both an affirmative response and a negative response as feedback of an automatic repeat request for activation or deactivation of semi-persistent scheduling of the downlink data channel.

[0012] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (radio signal transceiver 210) that receives a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and a control unit (control unit 270) that controls activation or deactivation of semi-persistent scheduling of the downlink data channel based on signaling common to the terminal group or signaling specific to the terminal.

[0013] One aspect of the present disclosure is a wireless communication method including receiving a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and assuming that activation or deactivation of semi-persistent scheduling of the downlink data channel is applied in units of the sub-groups when the terminal group is divided into a plurality of sub-groups.

[0014] One aspect of the present disclosure is a wireless communication method including receiving a downlink data channel common to a terminal group in data distribution for a plurality of terminals, and assuming that feedback of an automatic repeat request in the downlink data channel is transmitted in different time regions for each terminal.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

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

[0017] (1) Overall schematic configuration of the wireless communication system (1.1) System configuration example FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system compliant with 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] Note that the wireless communication system 10 may be a wireless communication system compliant with a scheme called Beyond 5G, 5G Evolution, or 6G.

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

[0020] Actually, NG-RAN20 includes a plurality of NG-RAN Nodes, specifically, gNBs (or ng-eNBs), and is connected to a core network (5GC, not shown) compliant with 5G. Note that NG-RAN20 and 5GC may simply be expressed as the "network".

[0021] gNB100 is a radio base station compliant with NR and performs wireless communication with UE200 according to NR. gNB100 and UE200 can support Massive MIMO that generates a more directive beam BM by controlling radio signals transmitted from a plurality of antenna elements, carrier aggregation (CA) that bundles and uses a plurality of component carriers (CC), and dual connectivity (DC) that simultaneously communicates between the UE and each of the plurality of 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 to 52.6 GHz In FR1, a sub-carrier spacing (SCS) of 15, 30, or 60 kHz is used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 has a higher frequency than FR1, and an SCS of 60 or 120 kHz (240 kHz may be included) is used, and a bandwidth (BW) of 50 to 400 MHz may be used.

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

[0025] Also, 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 a configuration example of a radio frame, subframe, and slot used in the wireless communication system 10.

[0027] As shown in FIG. 2, one slot is composed of 14 symbols, and the symbol period (and slot period) becomes shorter as the SCS increases (widens). Note that the number of symbols constituting one slot does not necessarily have to be 14 symbols (for example, 28, 56 symbols). Also, the number of slots per subframe may vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (for example, as shown in FIG. 2, 480 kHz, 960 kHz).

[0028] Note that the time direction (t) shown in FIG. 2 may also be referred to as the time domain, symbol period, or symbol time. Also, the frequency direction may be referred to as the frequency domain, resource block, resource block group, subcarrier, BWP (Bandwidth part), subchannel, common frequency resource, etc.

[0029] (1.2) Provision of MBS In the wireless communication system 10, Multicast and Broadcast Services (MBS) may be provided.

[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 a large number of UEs 200 receive the same data simultaneously. In such a case, it is effective to use MBS rather than unicast.

[0031] Note that unicast may be interpreted as communication that is performed one-to-one between the network and a specific one UE 200 (the UE 200 specific identification information may be specified).

[0032] Multicast may be interpreted as communication that is performed one-to-multiple (a specific large number) between the network and a specific multiple UEs 200 (the multicast specific identification information may be specified). Note that the number of UEs 200 that receive the received multicast data may be one as a result.

[0033] Broadcast may be interpreted as communication that is performed one-to-unspecified multiple between the network and all UEs 200. The data to be multicast / broadcast may have the same content that is copied, but some content such as the header may be different. Also, the data to be multicast / broadcast may be transmitted (distributed) simultaneously, but strict simultaneity is not necessarily required, and propagation delay and / or processing delay within the RAN node may be included.

[0034] Note that the target UE 200 may be in any of the states of the radio resource control layer (RRC), i.e., idle state (RRC idle), connected state (RRC connected), or other states (for example, inactive state). The inactive state may be interpreted as a state in which some settings of the RRC are maintained.

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

[0036] · PTM Transmission Method 1: · For the MBS group of an RRC connected UE, group-common PDSCH is scheduled using a group-common PDCCH (Physical Downlink Control Channel).

[0037] · The CRC of the PDCCH and the PDSCH are scrambled by a group-common RNTI (Radio Network Temporary Identifier).

[0038] · PTM Transmission Method 2: · For the MBS group of an RRC connected UE, group-common PDSCH is scheduled using a UE-specific PDCCH.

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

[0040] · The PDSCH is scrambled by a group-common RNTI.

[0041] · PTP Transmission Method: · For an RRC connected UE, UE-specific PDSCH is scheduled using a UE-specific PDCCH.

[0042] ·The CRC of PDCCH and PDSCH are scrambled by UE-specific RNTI. That is, it may mean that MBS packets are transmitted by unicast.

[0043] Figure 3 shows a configuration example of PTM transmission mode 1 and PTM transmission mode 2. Note that UE-specific PDCCH / PDSCH can be identified by the target UE, but may not be identifiable by other UEs within the same MBS group. Group-common PDCCH / PDSCH are transmitted in the same time / frequency resource and can be identified by all UEs within the same MBS group. Also, the names of PTM transmission modes 1 and 2 are provisional names, and may be called by other names as long as the above-described operations are executed.

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

[0045] Also, in order to improve the reliability of MBS, the following two feedback methods are assumed for HARQ (Hybrid Automatic Repeat Request) feedback, specifically, HARQ feedback for multicast / broadcast PDSCH.

[0046] ·Option 1: Feedback of both ACK / NACK (ACK / NACK feedback) ·UEs that have successfully received and decoded the PDSCH transmit ACK. ·UEs that have failed to receive and decode the PDSCH transmit NACK. ·PUCCH (Physical Uplink Control Channel) resource configuration: PUCCH-Config can be configured for multicast. · PUCCH resource: Shared / orthogonal among UEs is determined by network configuration. · HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB determination algorithms defined in 3GPP TS38.213). · Multiplexing: Applicable to unicast or multicast. · Option 2: NACK-only feedback. · UEs that successfully receive and decode PDSCH do not send ACK (do not send responses). · UEs that fail to receive and decode PDSCH send NACK. · For a given UE, PUCCH resource configuration can be set separately for unicast or groupcast (multicast). Note that ACK may be called positive acknowledgement, and NACK may be called negative acknowledgement. HARQ may be called automatic repeat request.

[0047] Enabling / Disabling of Option 1 or Option 2 may apply the following.

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

[0049] · Adopt SPS group-common PDSCH · As UE capability, multiple SPS group-common PDSCH can be configured. ·HARQ feedback for the SPS group-common PDSCH is possible ·At least activation / deactivation by group-common PDCCH is possible Note that deactivation may be read as other synonymous terms such as release. For example, activation may be read as start, trigger, etc., and deactivation may be read as end, stop, etc.

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

[0051] Scheduling may be interpreted as a process of allocating resources for data transmission. In dynamic scheduling, all PDSCHs may be interpreted as a mechanism 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 transmission is scheduled by upper layer signaling such as RRC messages.

[0052] Also, with respect to the physical layer, there may be scheduling categories for time domain scheduling and frequency domain scheduling.

[0053] Also, multicast, groupcast, broadcast, and MBS may be read as each other. The multicast PDSCH and the PDSCH scrambled by the group-common RNTI may be read as each other.

[0054] Furthermore, the terms data and packet may be interchangeable with each other and may be interpreted as synonyms for terms such as signal and data unit. Also, transmission, reception, transmission, and distribution may be interchangeable with each other.

[0055] (2) Functional Block Configuration of the Wireless Communication System Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0056] FIG. 4 is a functional block configuration diagram of the gNB 100 and the UE 200. Hereinafter, the UE 200 will be described. As shown in FIG. 4, the UE 200 includes a radio signal transceiver 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 transceiver unit 260, and a control unit 270.

[0057] Note that in FIG. 4, only the main functional blocks related to the description of the embodiment are shown, and it should be noted that the UE 200 has other functional blocks (for example, a power supply unit, etc.). Also, FIG. 4 shows the functional block configuration of the UE 200 (gNB 100), and for the hardware configuration, refer to FIG. 9.

[0058] The radio signal transceiver unit 210 transmits and receives radio signals according to NR. The radio signal transceiver unit 210 supports Massive MIMO, CA using a plurality of CCs bundled together, and DC for simultaneously communicating between the UE and each of the two NG-RAN Nodes.

[0059] Also, the radio signal transceiver unit 210 supports MBS and can receive a downlink channel that is common to a terminal group in data distribution for a plurality of UEs 200. In the present embodiment, the radio signal transceiver unit 210 may constitute a receiving unit.

[0060] The wireless signal transceiver unit 210 can receive a downlink data channel (PDSCH) common to the terminal group, specifically, a group-common PDSCH (which may include an SPS group-common PDSCH). Also, the wireless signal transceiver unit 210 can receive a downlink control channel common to the terminal group, specifically, a group-common PDCCH.

[0061] The amplifier unit 220 is composed of a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the demodulation and modulation unit 230 to a predetermined power level. Also, the amplifier unit 220 amplifies the RF signal output from the wireless signal transceiver unit 210.

[0062] The demodulation and modulation unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (such as gNB100). In the demodulation and modulation unit 230, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) may be applied. Also, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0063] The control signal and reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0064] Specifically, the control signal and reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, for example, control signals of the radio resource control layer (RRC). Also, the control signal and reference signal processing unit 240 transmits various control signals to the gNB100 via a predetermined control channel.

[0065] The control signal / reference signal processing unit 240 executes processing using reference signals (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).

[0066] DMRS is a reference signal (pilot signal) known between the base station specific to each terminal and the terminal for estimating the fading channel used for data demodulation. PTRS is a reference signal specific to each terminal for the purpose of estimating phase noise, which is a problem in high frequency bands.

[0067] Note that the reference signals may include, in addition to DMRS and PTRS, Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

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

[0069] Also, the data channel includes PDSCH and PUSCH (Physical Uplink Shared Channel). Data may mean data transmitted via the data channel.

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

[0071] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into a predetermined size and performs channel coding on the divided data. Further, the encoding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0072] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmission / reception unit 260 performs the assembly / disassembly of PDU / SDU in a plurality of layers (such as Medium Access Control layer (MAC), Radio Link Control layer (RLC), and Packet Data Convergence Protocol layer (PDCP)). Further, the data transmission / reception unit 260 performs error correction and retransmission control of data based on Hybrid automatic repeat request (HARQ).

[0073] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 performs scheduling of the downlink channel related to MBS and control related to the HARQ feedback of the channel.

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

[0075] Regarding the SPS group-common PDSCH, it may be assumed that the terminal group is divided into a plurality of subgroups, and for each subgroup, SPS (i.e., activation / deactivation of semi-persistent scheduling) of the downlink data channel (PDSCH) for the terminal group is applied.

[0076] It may be assumed that the feedback of hybrid automatic repeat request (HARQ) in the downlink data channel, specifically, the feedback of HARQ for activation or deactivation of semi-persistent scheduling of the downlink data channel, is transmitted in different time regions for each UE200.

[0077] Specifically, it may be assumed that the slot (see Figure 2) used for HARQ feedback for activation / deactivation of the SPS group-common PDSCH is different for each UE200. Note that the slot may be changed to another unit in the time region such as a sub-slot, sub-frame, or symbol.

[0078] The control unit 270 may apply both an acknowledgment (ACK) and a negative acknowledgment (NACK) as feedback of hybrid automatic repeat request (HARQ) for activation or deactivation of semi-persistent scheduling (SPS) of the downlink data channel (PDSCH).

[0079] Specifically, the control unit 270 may use both ACK and NACK only for HARQ feedback for activation / deactivation of the SPS group-common PDSCH. On the other hand, for HARQ feedback for the SPS group-common PDSCH without PDCCH (SPS group-common PDSCH without PDCCH), the control unit 270 may use only NACK (NACK-only).

[0080] Alternatively, for the SPS group-common PDSCH and HARQ feedback for activation / deactivation of the SPS group-common PDSCH, both ACK and NACK may be used as a matter of course.

[0081] Also, for HARQ feedback for activation / deactivation of the SPS group-common PDSCH, only NACK (NACK-only) may be used.

[0082] The control unit 270 may execute activation / deactivation of the SPS group-common PDSCH at a layer higher than the physical (PHY) layer. For example, the control unit 270 may execute activation / deactivation in the MAC or RRC layer.

[0083] Also, the control unit 270 may execute confirmation for activation / deactivation of the SPS group-common PDSCH at a layer higher than the physical (PHY) layer. For example, the control unit 270 may execute confirmation in the MAC layer.

[0084] The control unit 270 may control activation or deactivation of semi-persistent scheduling (SPS) of the downlink data channel based on group common signaling common to the terminal group or UE-specific signaling specific to the UE 200.

[0085] Specifically, the control unit 270 may assume that the activation / deactivation of the SPS group-common PDSCH is executed by both group common signaling and UE-specific signaling. Alternatively, the control unit 270 may assume that the activation / deactivation is executed by at least one of group common signaling and UE-specific signaling.

[0086] Also, the gNB 100 can execute the scheduling of the downlink channels described above and the control related to HARQ.

[0087] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the scheduling of the downlink channels related to MBS and the operation related to the HARQ feedback of the channels will be described.

[0088] In MBS, it is possible to schedule the group-common PDSCH by the group-common PDCCH (see Figure 3). However, as described above, the activation / deactivation of SPS for the group-common PDSCH may be applied (such a group-common PDSCH may be called an SPS group-common PDSCH for convenience).

[0089] In such a case, it is necessary to consider the method of confirmation for activation / deactivation.

[0090] Figure 5 shows a sequence example of PDCCH, PDSCH, and HARQ feedback that provides an SPS scheme in MBS.

[0091] In 3GPP Release-15 (unicast SPS), although HARQ feedback can have the meaning of confirmation, if such a scheme is applied to MBS and it is assumed that ACK / NACK is always fed back, a large amount of PUCCH resources can only be used when available.

[0092] On the other hand, if only NACK feedback is used, the gNB cannot recognize which UE has a misdetection. Therefore, how to transmit HARQ ACK / NACK can be an issue.

[0093] Below, an efficient operation example regarding SPS of group-common PDSCH considering such issues will be described.

[0094] (3.1) Operation example 1 In this operation example, the terminal group (UE group) targeted by the SPS group-common PDSCH is divided into a plurality of sub-groups. Activation / deactivation of SPS may be executed in units of the divided sub-groups.

[0095] Figure 6 shows a configuration example of the terminal group and sub-groups according to operation example 1. As shown in Figure 6, the terminal group (UE Group of SPS group-common PDSCH) may be divided into a plurality of sub-groups. The number of sub-groups and the number of UEs included in each sub-group may not be particularly limited. As shown in Figure 6, activation / deactivation (release) of SPS may be executed in units of the divided sub-groups. UE200 may assume such activation / deactivation of SPS for each sub-group.

[0096] The SPS group-common PDSCH for which activation / deactivation (release) is performed may be the SPS group-common PDSCH for the terminal group (i.e., the terminal group before being divided into sub-groups), or may be the Group-common PDCCH / PDSCH related to the G-RNTI.

[0097] The sub-group may be defined in association with a specific G (Group)-RNTI. The G-RNTI is an RNTI associated with the terminal group and may be called by another name. Also, an RNTI generated based on a specific G-RNTI (for example, which may be called sub-G-RNTI) may be used, but the name is not limited to this. The G-RNTI may be the RNTI related to the Group-common PDCCH / PDSCH (the same applies hereinafter).

[0098] The G-RNTI may be used for MBS group-common PDCCH CRC scrambling and / or PDSCH data scrambling. The G-RNTI may be set by control information of a higher layer (for example, RRC).

[0099] For HARQ feedback for activation / deactivation of SPS in sub-group units, ACK / NACK feedback may be used. In this case, dedicated PUCCH resources for activation / deactivation in sub-group units may be set.

[0100] Activation of SPS in sub-group units may not involve PDSCH reception. In this case, the slot for HARQ feedback may be determined based on the activation reception timing in sub-group units.

[0101] According to this operation example, since activation / deactivation is performed in units of sub-groups that are finer (smaller) than the terminal group, the amount of PUCCH resources used at one time can be reduced. As a result, failures of activation / deactivation can be detected more reliably and easily. On the other hand, by performing the transmission of group-common PDSCH in units of larger terminal groups, the number of PDSCH transmissions can be reduced compared to the case of performing it in units of sub-groups.

[0102] (3.2) Operation Example 2 In this operation example, the slot for performing HARQ feedback for the activation / deactivation of SPS group-common PDSCH may be different for each UE.

[0103] Specifically, in the PDCCH related to (used for) the activation / deactivation of SPS group-common PDSCH, different slot offsets for each UE (that is, the time-domain offset from the PDSCH (or PDCCH) to the PUCCH) may be notified.

[0104] More specifically, in the DCI format related to the activation / deactivation of SPS group-common PDSCH, a field related to HARQ feedback may be defined or set.

[0105] The DCI including the said field may be CRC scrambled by the G-RNTI, or may be scrambled by an RNTI generated based on the G-RNTI. Also, the said field may be the PDSCH-to-HARQ_feedback timing indicator field (defined in 3GPP TS38.213), or may be the HARQ feedback timing indicator field.

[0106] The number of the fields may be set by the control information of the upper layer. Also, different fields may be defined or set for each UE, and the UE may determine the HARQ feedback slot based on the field associated with the UE. In this case, among the multiple fields, which field (e.g., which number) is used for the timing indication of the HARQ feedback of the UE may be set by the upper layer or determined according to a predetermined rule (e.g., using the field with the number obtained by performing a remainder operation (mod operation) on the C (cell)-RNTI by the number of the fields). Among the multiple fields, the values of the fields not associated with the UE may be ignored (not used for determining the HARQ feedback timing).

[0107] FIG. 7 shows an example of an indication of HARQ feedback according to Operation Example 2. As shown in FIG. 7, the DCI field may include a plurality of HARQ feedback timing indicators. Here, an example is shown in which a specific UE is instructed to determine the HARQ feedback timing according to the field of the second HARQ feedback timing indicator (#2).

[0108] The above operations may be applied to each of a plurality of UEs instead of each UE. For example, when a subgroup of UEs is defined, different fields may be defined or set for each subgroup, and the UE may determine the HARQ feedback slot based on the field associated with the UE. Also in this case, as described above, which field (e.g., which number) is used for the timing indication of the HARQ feedback of the UE may be set by the upper layer or determined according to a predetermined rule. Also, among the multiple fields, the values of the fields not associated with the UE may be ignored (see FIG. 7).

[0109] Also, a time domain offset (which may also be referred to as a time offset) for HARQ feedback for activation / deactivation of the SPS group-common PDSCH may be set. The time offset may be an offset of slots from the PDSCH (or PDCCH) to the PUCCH, but is not limited thereto. As described above, it may be in units of sub-slots, sub-frames, frames, or symbols, etc.

[0110] The offset of the slot included in the PDCCH related to activation / deactivation of the SPS group-common PDSCH may not be used for the HARQ feedback. That is, except for activation / deactivation of the SPS group-common PDSCH, it may or may not be used for HARQ feedback transmission for reception of the SPS group-common PDSCH.

[0111] Also, a plurality of slot offset values may be set for each UE, and in a field included in the PDCCH related to activation / deactivation of the SPS group-common PDSCH, an identifier (index) associated with the slot offset may be specified. That is, even in DCI format 1_0, the slot offset may be set for each UE and associated with the index, and the index may be indicated by the DCI.

[0112] Also, the HARQ feedback timing may be determined by adding or subtracting a time offset (slot, sub-slot, sub-frame, frame, or symbol number) set by a higher layer to the slot number (which may also be a sub-slot, sub-frame, frame, or symbol) of the HARQ feedback timing indicated using at least one field related to HARQ feedback. If the time offset is not set, the HARQ feedback timing may be determined with time offset = 0.

[0113] This operation example may be applied not only to the activation / deactivation of the SPS group-common PDSCH but also to the HARQ feedback for any group-common PDCCH. For example, when only DCI format 1_0 is used for MBS, at least one time offset for HARQ feedback may be set, for example, by a higher layer, and one of the indexes associated with the set time offset may be indicated by DCI. In this case, the flexibility of resource allocation for HARQ feedback for the group-common PDCCH is improved.

[0114] (3.3) Operation Example 3 In this operation example, the HARQ feedback for the activation / deactivation of the SPS group-common PDSCH is always ACK / NACK feedback, and the HARQ feedback for the SPS group-common PDSCH without PDCCH (i.e., the SPS group-common PDSCH that does not correspond to activation / deactivation) may be executed by NACK-only.

[0115] FIG. 8 shows a sequence example of PDCCH, PDSCH, and HARQ feedback according to Operation Example 3. As shown on the left side of FIG. 8, for HARQ feedback for activation / deactivation of SPS group-common PDSCH with PDCCH, both ACK and NACK may be transmitted. On the other hand, as shown on the right side of FIG. 8, for HARQ feedback for SPS group-common PDSCH without PDCCH (SPS group-common PDSCH without PDCCH), only NACK may be transmitted.

[0116] That is, even for an SPS group-common PDSCH for which NACK-only feedback is configured or indicated, HARQ feedback for activation / deactivation may be performed by ACK / NACK feedback.

[0117] In this case, a PUCCH resource dedicated to ACK / NACK feedback for activation / deactivation may be configured.

[0118] Also, when only the PUCCH resource / resource set related to NACK-only feedback is configured for HARQ feedback for group-common PDSCH, any of the following may be executed.

[0119] · The UE may determine a PUCCH resource related to ACK / NACK feedback based on the PUCCH resource / resource set related to NACK-only feedback and perform ACK / NACK feedback for activation / deactivation.

[0120] For example, in the case of PUCCH Format (PF) 0 (short format), the PUCCH resource for NACK based feedback is used in the case of NACK, and the ACK resource may be derived by setting the CS index to +6 in the PUCCH resource for NACK based feedback.

[0121] In the case of PF1 (long format), for both ACK / NACK cases, it may be transmitted by PF1 using the PUCCH resource for NACK based feedback. In PF1, ACK / NACK may be modulated by BPSK (Binary Phase Shift Keying) / QPSK (Quadrature Phase shift Keying) and transmitted.

[0122] · The UE may perform HARQ feedback on the activation / deactivation of the SPS group-common PDSCH using the PUCCH resource / resource set for the unicast PDSCH.

[0123] Also, in this operation example, the HARQ feedback on the SPS group-common PDSCH and its activation / deactivation may necessarily be performed by both ACK / NACK feedbacks. That is, NACK-only feedback may not be performed.

[0124] Specifically, for HARQ feedback for group-common PDSCH, a PUCCH resource / resource set related to ACK / NACK feedback and a PUCCH resource / resource set related to NACK-only feedback may be configured. In this case, HARQ feedback for SPS group-common PDSCH and its activation / deactivation may be transmitted using the PUCCH resource / resource set related to ACK / NACK feedback.

[0125] Alternatively, when only a PUCCH resource / resource set related to NACK-only feedback is configured for HARQ feedback for group-common PDSCH, any of the following may be performed.

[0126] · Based on the PUCCH resource / resource set related to NACK-only feedback, a PUCCH resource related to ACK / NACK feedback may be determined and ACK / NACK feedback may be performed.

[0127] For example, if it is PF0, the PUCCH resource for NACK based feedback may be used in the case of NACK, and the ACK resource may be derived by setting CS index +6 in the PUCCH resource for NACK based feedback. If it is PF1, for both ACK and NACK cases, they may be transmitted by PF1 using the PUCCH resource for NACK based feedback. In PF1, ACK / NACK may be modulated with BPSK / QPSK and transmitted.

[0128] · The UE may perform HARQ feedback for SPS group-common PDSCH using the PUCCH resource / resource set for unicast PDSCH.

[0129] (3.4) Operation Example 4 In this operation example, the activation / deactivation of the SPS group-common PDSCH may be performed at a layer higher than the physical (PHY) layer.

[0130] For example, the activation / deactivation may be performed by a MAC CE (Control Element). Specifically, the activation / deactivation may be notified by a MAC CE included in the group-common PDSCH. In this case, the group-common PDSCH may mean the first SPS group-common PDSCH reception.

[0131] The CRC (Cyclic Redundancy Checksum) of the PDCCH corresponding to the group-common PDSCH that notifies the activation / deactivation may be scrambled by the G-RNTI or may be scrambled by the RNTI for the SPS group-common PDSCH.

[0132] Regarding the HARQ feedback for the activation / deactivation, any of the methods described above may be applied.

[0133] Alternatively, the activation / deactivation of the SPS group-common PDSCH may be notified by a MAC CE included in the unicast PDSCH. In this case, the offset from the unicast PDSCH to the first SPS group-common PDSCH reception resource may be notified.

[0134] Alternatively, the activation / deactivation of the SPS group-common PDSCH may be notified by RRC signaling.

[0135] Specifically, the activation / deactivation of the SPS group-common PDSCH may be set by unicast signaling of the RRC layer, and the activation / deactivation may be notified. Confirmation may be performed by a completion report for the provision of RRC parameters.

[0136] Alternatively, the activation / deactivation of the SPS group-common PDSCH may be notified by system information (SIB) including multicast information.

[0137] (3.5) Operation Example 5 In this operation example, confirmation for the activation / deactivation of the SPS group-common PDSCH may be performed at a layer higher than the physical (PHY) layer.

[0138] For example, a confirmation MAC CE for the SPS group-common PDSCH may be defined, and the confirmation MAC CE may be transmitted in response to the reception of the activation / deactivation of the SPS group-common PDSCH.

[0139] Alternatively, it may be that the UE that has received the activation / deactivation of the SPS group-common PDSCH must transmit the MAC CE in the earliest PUSCH resource after such reception. That is, if the MAC CE is not transmitted, the gNB may assume that the UE that did not transmit (was unable to transmit) has not received the activation / deactivation of the SPS group-common PDSCH. In this case, it may be applied only when NACK-only feedback is configured or indicated.

[0140] (3.6) Operation Example 6 In this operation example, the activation / deactivation of the SPS group-common PDSCH may be performed by both group-common signaling and UE-specific signaling.

[0141] Situations (scenarios) where such signaling is applied include, for example, when a UE that could not perform activation / deactivation by group-common signaling receives activation / deactivation by UE-specific signaling, or when a new UE joins a UE group of an SPS group-common PDSCH for which activation has already been completed and transmission has started, and the new UE performs reception of the SPS group-common PDSCH.

[0142] In this operation example, the activation / deactivation of the SPS group-common PDSCH may be performed by the UE-specific PDCCH.

[0143] Specifically, when the CRC of the UE-specific PDCCH is scrambled by a predetermined RNTI, the PDCCH may be determined as the activation / deactivation of the SPS group-common PDSCH.

[0144] Or, when it has the same DCI field value as the activation / deactivation of the UE-specific SPS PDSCH, the UE-specific PDCCH may be determined as the activation / deactivation of the SPS group-common PDSCH.

[0145] Or, when a predetermined field of the DCI has a predetermined value, the UE-specific PDCCH may be determined as the activation / deactivation of the SPS group-common PDSCH. The predetermined field is, for example, the PDSCH-to-HARQ_feedback timing indicator, the PUCCH resource indicator, the ZP (Zero power) CSI-RS trigger, etc.

[0146] Or, the PDSCH resource indicated in the UE-specific PDCCH may be recognized as the SPS group-common PDSCH.

[0147] (3.7) Operation Example 7 In this operation example, the HARQ feedback for the activation / deactivation of the SPS group-common PDSCH may be performed by ACK-only feedback.

[0148] Specifically, in ACK-only feedback, the UE may operate as follows.

[0149] ·UE that has successfully received and decoded the PDSCH transmits an ACK ·UEs that failed in PDSCH reception and decoding do not transmit anything Also, a PUCCH resource / resource set for ACK-only feedback may be separately configured, or a PUCCH resource / resource set for ACK / NACK feedback or a PUCCH resource / resource set for NACK-only feedback may be used.

[0150] Note that this operation example may be applied to HARQ feedback of not only activation / deactivation of SPS group-common PDSCH but also group-common PDSCH other than SPS group-common PDSCH, specifically, group-common PDSCH to which SPS is not applied.

[0151] (3.8) Modification example The above-described operation examples 1 to 7 may be combined and applied comprehensively as long as there is no contradiction. Also, as described above, terms indicating a time domain such as a slot may be read as other terms indicating a time domain such as a sub-slot.

[0152] Also, the CRC of the PDCCH / DCI related to the activation / deactivation of the SPS group-common PDSCH may be scrambled by the G-RNTI.

[0153] The above-described operation examples were related to MBS targeting simultaneous transmission (delivery) to multiple UEs. However, the UEs targeted by MBS do not necessarily have to be multiple all the time. If an operation according to MBS, such as using group-common PDSCH, is being executed, it may include cases where a specific or unspecified number of UEs are substantially regarded as one, and may not be multiple.

[0154] (4) Function and effect According to the above-described embodiments, the following operational effects can be obtained. Specifically, according to UE200 (and gNB100) related to operation examples 1 to 7, activation / deactivation of group-common PDSCH, specifically SPS group-common PDSCH, can be performed normally. That is, gNB100 (the network) can grasp the misdetection of DCI in UE200. Also, gNB100 can appropriately control resources related to HARQ feedback (including activation / deactivation of SPS group-common PDSCH).

[0155] gNB100 and UE200 can efficiently and reliably execute operations associated with semi-persistent scheduling (SPS) in simultaneous data transmission services (MBS) to a specific or unspecified plurality of UE200.

[0156] In this embodiment, it can be assumed that for SPS group-common PDSCH, the terminal group is divided into a plurality of sub-groups, and SPS of the downlink data channel (PDSCH) is applied in units of sub-groups. Therefore, failure of activation / deactivation of SPS group-common PDSCH can be detected more reliably and easily. Also, by performing transmission of group-common PDSCH in units of a large terminal group, the number of PDSCH transmissions can be reduced compared to the case of performing it in units of sub-groups.

[0157] In this embodiment, it may be assumed that HARQ feedback for activation / deactivation of SPS group-common PDSCH is transmitted in different time regions (such as slots) for each UE200. Therefore, while using SPS group-common PDSCH, reliable HARQ feedback for each UE200 can be provided.

[0158] In this embodiment, the UE 200 may apply both an acknowledgment (ACK) and a negative acknowledgment (NACK) as HARQ feedback for activation / deactivation of the SPS group-common PDSCH. Thereby, while utilizing the SPS group-common PDSCH, it is possible to provide detailed HARQ feedback for each UE 200.

[0159] In this embodiment, the UE 200 may control the activation / deactivation of the SPS group-common PDSCH based on group common signaling common to the terminal group or UE-specific signaling specific to the UE 200. For this reason, the activation / deactivation of the SPS group-common PDSCH can be controlled more reliably.

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

[0161] For example, in the above-described embodiment, the names PDCCH and PDSCH are used as the downlink channels, but any other name may be used as long as it is a downlink control channel or a downlink data channel (which may be a shared channel).

[0162] Also, in the above description, configure, activate, update, indicate, enable, specify, select may be read as each other. Similarly, link, associate, correspond, map may be read as each other, and allocate, assign, monitor, map may also be read as each other.

[0163] Furthermore, specific, dedicated, UE-specific, UE-dedicated may be read as each other. Similarly, common, shared, group-common, UE-common, UE-shared may be read as each other.

[0164] Also, the block configuration diagram (Figure 4) used in the description of the above embodiments shows blocks of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the realization method of each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (for example, using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0165] Functions include, but are not limited to, judgment, decision-making, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection determination, establishment, comparison, assumption, expectation, regarded as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), assigning, etc. For example, a functional block (component) that enables transmission is referred to as a transmitting unit or a transmitter. As described above, the implementation method is not particularly limited.

[0166] Furthermore, the above-described gNB 100 and UE 200 may function as a computer that performs the processing of the wireless communication method of the present disclosure. FIG. 9 is a diagram showing an example of the hardware configuration of the apparatus. As shown in FIG. 9, the apparatus 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, and a bus 1007, etc.

[0167] In the following description, the term "apparatus" can be read as a circuit, device, unit, etc. The hardware configuration of the apparatus may be configured to include one or more of each apparatus shown in the figure, or may be configured without including some apparatuses.

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

[0169] In addition, each function in the device is realized by causing a predetermined software (program) to be loaded onto hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs operations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0170] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.

[0171] In addition, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program for causing a computer to execute at least a part of the operations described in the above embodiments is used. Further, the above various processes 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. Note that the program may be transmitted from a network via a telecommunication line.

[0172] The memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 can store a program (program code), software module, etc. that can execute the method according to an embodiment of the present disclosure.

[0173] The storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, optical discs such as Compact Disc ROM (CD-ROM), hard disk drives, flexible disks, magneto-optical disks (e.g., compact discs, digital versatile discs, Blu-ray (registered trademark) discs), smart cards, flash memories (e.g., cards, sticks, key drives), floppy (registered trademark) disks, magnetic strips, etc. The 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 media including at least one of the memory 1002 and the storage 1003.

[0174] The communication device 1004 is hardware (a transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc.

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

[0176] The input device 1005 is an input device that receives external input (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs external output (for example, a display, a speaker, an LED lamp, etc.). Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

[0177] Also, 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 for each device.

[0178] 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), a Field Programmable Gate Array (FPGA), etc., 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 hardware components.

[0179] Also, the notification of information is not limited to the aspects / embodiments described in this disclosure, and other methods may be used. For example, the notification of information may be implemented by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper 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. Also, 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, etc.

[0180] Each aspect / embodiment described in this disclosure may be applied to at least one of systems using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 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), other suitable systems, and next-generation systems extended based thereon. Also, a plurality of systems may be combined (e.g., a combination of at least one of LTE and LTE-A and 5G) and applied.

[0181] The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be reordered as long as there is no contradiction. For example, for the methods described in this disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0182] Specific operations assumed to be performed by a base station in this disclosure may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal can clearly be performed by at least one of the base station and other network nodes other than the base station (for example, but not limited to, an MME or an S-GW, etc.). Although the case where there is one other network node other than the base station is exemplified above, a combination of a plurality of other network nodes (for example, an MME and an S-GW) may also be possible.

[0183] Information, signals (such as information) can be output from an upper layer (or a lower layer) to a lower layer (or an upper layer). They may also be input and output via a plurality of network nodes.

[0184] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information can be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to other devices.

[0185] The determination may be made based on a value represented by 1 bit (0 or 1), may be made based on a Boolean value (true or false), or may be made by comparing numerical values (for example, comparing with a predetermined value).

[0186] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to being explicitly performed, and may be performed implicitly (for example, by not performing the notification of the predetermined information).

[0187] Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by some other name.

[0188] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

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

[0190] In addition, for the terms described in the present disclosure and the terms necessary for understanding the present disclosure, they 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). Also, the signal may be a message. Also, a component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

[0191] The terms "system" and "network" used in the present disclosure are used interchangeably.

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

[0193] The names used for the above-described parameters are not limiting names in any respect. Furthermore, mathematical formulas and the like using these parameters may be different from those explicitly disclosed in the present disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0194] In the present 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", "component carrier", etc. may be used interchangeably. The base station may also be referred to by terms such as macro cell, small cell, femto cell, pico cell, etc.

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

[0196] The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services within this coverage.

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

[0198] 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 term.

[0199] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves unmanned (e.g., a drone, a self-driving car, etc.), or a robot (humanoid or unmanned). Note that at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0200] Also, the base station in the present disclosure may be read as a mobile station (user terminal, the same hereinafter). For example, for a configuration in which communication between the base station and the mobile station is replaced with communication between a plurality of mobile stations (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the base station may be configured as those of the mobile station. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel (or sidelink).

[0201] Similarly, the mobile station in the present disclosure may be read as a base station. In this case, the functions of the mobile station may be configured as those of the base station. A wireless 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 sub-frame. A sub-frame may further be composed of one or more slots in the time domain. A sub-frame may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

[0202] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of sub-carrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

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

[0204] The slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, the mini-slot may be called a sub-slot. The mini-slot may be composed of a smaller number of symbols than the slot. The PDSCH (or PUSCH) transmitted in a time unit larger than the mini-slot may be called PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be called PDSCH (or PUSCH) mapping type B.

[0205] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units when transmitting signals. Different names corresponding to each of them may be used.

[0206] For example, one sub-frame may be called a transmission time interval (TTI), or a plurality of consecutive sub-frames may be called TTI, or one slot or one mini-slot may be called TTI. That is, at least one of the sub-frame and TTI may be the sub-frame (1 ms) in the existing LTE, or a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing TTI may be called a slot, mini-slot, etc. instead of a sub-frame.

[0207] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

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

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

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

[0211] Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and not less than 1 ms.

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

[0213] Also, the time domain of the RB may include one or more symbols, and may be the length of 1 slot, 1 mini-slot, 1 sub-frame, or 1 TTI. 1 TTI, 1 sub-frame, etc. may each be composed of one or more resource blocks.

[0214] Note that one or more RBs may be referred to as physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc.

[0215] Also, the resource block may be composed of one or more resource elements (REs). For example, 1 RE may be a radio resource area of 1 sub-carrier and 1 symbol.

[0216] The bandwidth part (BWP) (which may also be called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. The PRB is defined in a certain BWP and may be numbered within the BWP.

[0217] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be set within one carrier for the UE.

[0218] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0219] The structures such as the above-described radio frames, sub-frames, slots, mini-slots, and symbols are merely exemplary. For example, the number of sub-frames included in a radio frame, the number of slots per sub-frame or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, Cyclic Prefix (CP) length, etc. within a TTI can be variously changed.

[0220] The terms "connected" and "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and can include the presence of one or more intermediate elements between two elements "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed". As used in this disclosure, two elements can be considered to be "connected" or "coupled" to each other using at least one of one or more electric wires, cables, and printed electrical connections, and also, as some non-limiting and non-exhaustive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (both visible and invisible) region.

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

[0222] As used in this disclosure, the description "based on" does not mean "based only on" unless otherwise specified. In other words, the description "based on" means both "based only on" and "based at least on".

[0223] In the configuration of each of the above-described apparatuses, the "means" may be replaced with a "section", "circuit", "device", or the like.

[0224] In the present disclosure, any reference to elements using designations such as "first", "second", etc. does not generally limit the quantity or order of those elements. These designations may be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements may be employed there, or that the first element must precede the second element in any form.

[0225] In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, like the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0226] In the present disclosure, for example, when articles are added by translation, like a, an, and the in English, the present disclosure may include that the nouns following these articles are in the plural form.

[0227] As used herein, the terms "determining" and "deciding" may encompass a wide variety of operations. "Determining" and "deciding" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or other data structure), ascertaining, and considering something as having been "determined" or "decided". "Determining" and "deciding" may also include receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, accessing (e.g., accessing data in a memory), and considering something as having been "determined" or "decided". "Determining" and "deciding" may further include resolving, selecting, choosing, establishing, comparing, etc., and considering something as having been "determined" or "decided". That is, "determining" and "deciding" may include considering something as having been determined or decided by performing some operation. Also, "determining (deciding)" may be construed as "assuming", "expecting", "considering", etc.

[0228] As used herein, the term "A is different from B" may mean that "A and B are different from each other". Note that the term may also mean that "A and B are each different from C". Terms such as "separated", "coupled", etc. may also be construed in the same manner as "different".

[0229] As described in detail above, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and changed 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 for illustrative purposes only and does not have any limiting meaning for the present disclosure.

Explanation of Signs

[0230] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Wireless signal transceiver 220 Amplifier section 230 Modulation / demodulation section 240 Control signal / reference signal processing section 250 Encoding / decoding section 260 Data transceiver 270 Control section 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims

1. A receiving unit that receives a downlink data channel common to a terminal group that is semi-fixedly scheduled in data distribution to a plurality of terminals; A terminal comprising a control unit that performs feedback using a feedback method that applies both positive acknowledgment and negative acknowledgment to the deactivation of semi-static scheduling of the downlink data channel.

2. In data distribution to a plurality of terminals, receiving a downlink data channel common to a terminal group that is semi-fixedly scheduled; A communication method for a terminal, comprising: a step of performing feedback using a feedback method that applies both positive and negative acknowledgements to the deactivation of semi-static scheduling of the downlink data channel.

3. A transmitter that transmits a common downlink data channel to a terminal group that is semi-fixedly scheduled in data distribution to a plurality of terminals; A base station comprising a receiver for receiving feedback from the terminal using a feedback method that applies both positive and negative acknowledgements to deactivation of semi-static scheduling of the downlink data channel.

4. A communication system including a base station and a plurality of terminals, The base station, A transmission unit that transmits a common downlink data channel to a terminal group that is semi-fixedly scheduled in data distribution to a plurality of terminals; a receiving unit for receiving feedback from the terminal using a feedback method that applies both positive and negative acknowledgements to deactivation of semi-static scheduling of the downlink data channel; The terminal includes: a receiving unit for receiving the downlink data channel; A communication system comprising a control unit that performs feedback using the feedback method in response to deactivation of semi-static scheduling of the downlink data channel.

5. A receiving unit for receiving a downlink data channel common to a terminal group that is semi-fixedly scheduled in data distribution to a plurality of terminals; A terminal comprising a control unit that performs feedback using a feedback method that applies both positive and negative acknowledgements to a downlink control channel that activates semi-static scheduling of the downlink data channel, and performs feedback using a feedback method that applies only negative acknowledgements to the downlink data channel that does not involve the downlink control channel.

Images