Terminal and wireless communication method
The proposed solution allows terminals to configure HARQ feedback for MBS and unicast PDSCHs based on terminal capabilities and RRC parameters, addressing the challenge of multiplexing methods in MBS, enhancing communication reliability and efficiency.
Patent Information
- Application Number
- JP2023520603
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-05-10
- Publication Date
- 2025-07-01
- Estimated Expiration
- 2041-05-10
AI Technical Summary
Existing 3GPP standards face challenges in configuring appropriate Hybrid Automatic Repeat Request (HARQ) feedback for Multicast and Broadcast Services (MBS) due to the inability to handle time-division multiplexing (TDM) and frequency-division multiplexing (FDM) scenarios, where multiple PDSCHs cannot be overlapped in the same symbol, complicating the determination of HARQ-ACK codebook configuration.
A terminal and wireless communication method that determines HARQ feedback configuration based on terminal capabilities or radio resource control layer parameters, allowing simultaneous reception of multicast and unicast PDSCHs within the same time domain under specific conditions, irrespective of multiplexing methods.
Enables appropriate HARQ feedback configuration for MBS and unicast PDSCHs, ensuring reliable communication quality by adapting to different multiplexing scenarios, thereby improving the efficiency of multicast and broadcast services.
Smart Images

Figure 0007701440000001 
Figure 0007701440000002 
Figure 0007701440000003
Abstract
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 advancing 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 specific or unspecified plurality of 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] For HARQ of MBS, a method of feeding back both ACK and NACK (ACK / NACK feedback) is applied, and support for the determination algorithm of the HARQ-ACK codebook (CB) (type-1 and type-2, defined in 3GPP TS38.213) is assumed.
[0007] Also, the PDSCH for MBS (Physical Downlink Shared Channel, MBS PDSCH) and the PDSCH specific to a particular UE (Unicast PDSCH) can be time-division multiplexed (TDM) or frequency-division multiplexed (FDM). In this case, the configuration of the HARQ-ACK CB also differs depending on the difference in the multiplexing method of TDM or FDM.
[0008] However, the HARQ-ACK CB is premised on the fact that in a specific cell (the same cell), multiple PDSCHs cannot be overlapped and assigned to the same symbol. It functions in the case of TDM, but may not function in the case of FDM. For this reason, it may be difficult for the UE to determine an appropriate HARQ-ACK CB configuration.
[0009] Therefore, the following disclosure is made in view of such a situation, and aims to provide a terminal and a radio communication method that can configure appropriate HARQ feedback regardless of the multiplexing method between the MBS PDSCH and the Unicast PDSCH.
[0010] One aspect of the present disclosure is a terminal (UE200) including a transmission unit (data transceiver unit 260) that transmits feedback of an automatic repeat request, and a control unit (control unit 270) that determines a configuration of the feedback of a first downlink data channel common to a terminal group and the feedback of a second downlink data channel specific to the terminal based on terminal capabilities or parameters of a radio resource control layer.
[0011] One aspect of the present disclosure is a terminal (UE200) including a transmission unit (data transmission / reception unit 260) that transmits feedback of an automatic repeat request, and a control unit (control unit 270) that assumes that a first downlink data channel common to a terminal group and a second downlink data channel specific to a terminal are received within the same time domain only when a specific condition is satisfied in the same cell.
[0012] One aspect of the present disclosure is a wireless communication method including a step of transmitting feedback of an automatic repeat request, and a step of determining a configuration of the feedback of the first downlink data channel common to a terminal group and the feedback of the second downlink data channel specific to a terminal based on terminal capabilities or parameters of a radio resource control layer.
[0013] One aspect of the present disclosure is a wireless communication method including a step of transmitting feedback of an automatic repeat request, and a step of assuming that a first downlink data channel common to a terminal group and a second downlink data channel specific to a terminal are received within the same time domain only when a specific condition is satisfied in the same cell.
Brief Description of Drawings
[0014]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Embodiments for Carrying Out the Invention
[0015] 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.
[0016] (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 according 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).
[0017] Note that the wireless communication system 10 may also be a wireless communication system according to a system called Beyond 5G, 5G Evolution, or 6G.
[0018] 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.
[0019] NG-RAN20 actually 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 "network".
[0020] 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 wireless signals transmitted from a plurality of antenna elements, Carrier Aggregation (CA) that bundles and uses a plurality of Component Carriers (CCs), and Dual Connectivity (DC) that enables simultaneous communication between the UE and each of a plurality of NG-RAN Nodes.
[0021] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows.
[0022] ·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 is at 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.
[0023] 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.
[0024] 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).
[0025] Figure 2 shows a configuration example of a radio frame, a sub-frame, and a slot used in the wireless communication system 10.
[0026] As shown in Figure 2, one slot is composed of 14 symbols, and as the SCS increases (widens), the symbol period (and slot period) becomes shorter. 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 sub-frame may vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (for example, as shown in Figure 2, 480 kHz, 960 kHz).
[0027] Note that the time direction (t) shown in Figure 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, sub-carrier, BWP (Bandwidth part), sub-channel, common frequency resource, etc.
[0028] (1.2) Provision of MBS In the wireless communication system 10, Multicast and Broadcast Services (MBS) may be provided.
[0029] For example, in a stadium or a hall, etc., 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 more effective to use MBS rather than unicast.
[0030] 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).
[0031] Multicast may be interpreted as communication that is performed one-to-multiple (a specific large number) between the network and a specific plurality of UEs 200 (the identification information for multicast may be specified). Note that the number of UEs 200 that receive the received multicast data may be one as a result.
[0032] Broadcast may be interpreted as communication that is performed one-to-indeterminate large number between the network and all UEs 200. The data that is multicast / broadcast may have the same copied content, but some content such as headers may be different. Also, the data that is 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, etc. may be included.
[0033] 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.
[0034] In MBS, the following three methods are assumed for the scheduling of multicast / broadcast Physical Downlink Shared Channel (PDSCH), 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.
[0035] · PTM Transmission Method 1 (PTM-1): · For the MBS group of RRC connected UEs, group-common Physical Downlink Control Channel (PDCCH) is used to schedule group-common PDSCH.
[0036] · The CRC of the PDCCH and the PDSCH are scrambled by a group-common Radio Network Temporary Identifier (which may be called G-RNTI).
[0037] · PTM Transmission Method 2 (PTM-2): · For the MBS group of RRC connected UEs, UE-specific PDCCH is used to schedule group-common PDSCH.
[0038] · The CRC of the PDCCH is scrambled by UE-specific RNTI.
[0039] · The PDSCH is scrambled by group-common RNTI.
[0040] · PTP Transmission Method: · For RRC connected UEs, UE-specific PDCCH is used to schedule UE-specific PDSCH.
[0041] · The CRC of PDCCH and PDSCH are scrambled by UE-specific RNTI. That is, it may mean that MBS packets are transmitted by unicast.
[0042] 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 it does not have to 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 as long as the above-described operations are executed, they may be called by other names.
[0043] In addition, 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.
[0044] 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.
[0045] · Option 1: Feedback of both ACK / NACK (ACK / NACK feedback) · UEs that have successfully received and decoded PDSCH transmit ACK. · UEs that have failed to receive and decode 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.
[0046] Activation and deactivation of Option 1 or Option 2 may apply to any of the following.
[0047] · RRC and downlink control information (DCI: Downlink Control Information) · RRC only Also, for SPS (Semi-persistent Scheduling) of multicast / broadcast PDSCH, the following is assumed.
[0048] · Adopt SPS group-common PDSCH (may also be called group common SPS PDSCH) · As UE capability, multiple SPS group-common PDSCH can be configured ·HARQ feedback for the SPS group-common PDSCH is possible ·Activation / deactivation by at least group-common PDCCH (downlink control channel) is possible Note that deactivation may be read as other synonymous terms such as release. For example, activation may be read as start-up, start, trigger, etc., and deactivation may be read as end, stop, etc.
[0049] 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).
[0050] Scheduling may be interpreted as a process of allocating resources for transmitting data. In dynamic scheduling, it 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 transmission is scheduled by upper layer signaling such as an RRC message.
[0051] Note that Multicast SPS PDSCH reception may mean group common SPS PDSCH reception, may be an SPS PDSCH received by multiple terminals, or may be an 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.
[0052] Regarding 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 of data and packet may be read as each other, and may be interpreted as synonyms for terms such as signal and data unit. Also, transmission, reception, transmission, and delivery may be read as 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. 10.
[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 that bundles a plurality of CCs for use, and DC that simultaneously communicates between the UE and each of the two NG-RAN Nodes.
[0059] The wireless signal transceiver unit 210 supports MBS and can receive a downlink channel that is common to a terminal group in data distribution to a plurality of UEs 200.
[0060] Also, the wireless signal transceiver unit 210 can receive a downlink data channel (PDSCH) in MBS, that is, in data distribution to a plurality of terminals.
[0061] Specifically, the wireless signal transceiver 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.
[0062] Also, the wireless signal transceiver 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.
[0063] 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.
[0064] 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).
[0065] The control signal and reference signal processing unit 240 executes 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.
[0066] Specifically, the control signal and reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, control signals (messages) of the radio resource control layer (RRC). Also, the control signal and reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.
[0067] The control signal and reference signal processing unit 240 executes processing using reference signals (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).
[0068] DMRS is a reference signal (pilot signal) known between the base station and the terminal specific to each 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 that is a problem in a high frequency band.
[0069] Note that in addition to DMRS and PTRS, the reference signal may include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for position information.
[0070] In addition, the channels include a control channel and a data channel. The control channel 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)), and a Physical Broadcast Channel (PBCH), etc.
[0071] In addition, the data channel includes a PDSCH, a PUSCH (Physical Uplink Shared Channel), etc. The data may mean the data transmitted via the data channel.
[0072] In this embodiment, the control signal / reference signal processing unit 240 may constitute a receiving unit that receives downlink control information (DCI). Further, the control signal / reference signal processing unit 240 may receive, in RRC, a message indicating activation or deactivation of a function in which activation or deactivation of HARQ feedback is indicated by DCI.
[0073] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding, etc. for each predetermined communication destination (gNB100 or another gNB).
[0074] Specifically, the encoding / decoding unit 250 splits the data output from the data transmission / reception unit 260 into a predetermined size and performs channel coding on the split data. Further, the encoding / decoding unit 250 decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.
[0075] 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 Media Access Control layer (MAC), Radio Link Control layer (RLC), and Packet Data Convergence Protocol layer (PDCP)).
[0076] Also, the data transmission / reception unit 260 performs error correction and retransmission control of data based on Hybrid automatic repeat request (HARQ). Specifically, the data transmission / reception unit 260 can transmit the feedback of HARQ (Automatic Repeat reQuest). In the present embodiment, the data transmission / reception unit 260 may constitute a transmission unit.
[0077] The control unit 270 controls each functional block constituting the UE 200. In particular, in the present embodiment, the control unit 270 performs scheduling of the downlink channel related to MBS and control related to the HARQ feedback of the channel.
[0078] 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 a plurality of UEs 200, that is, in MBS. Specifically, the control unit 270 can perform control corresponding to the scheduling of group-common PDCCH and group-common PDSCH.
[0079] Regarding the SPS group-common PDSCH, the control unit 270 may assume that the activation / deactivation of SPS, that is, semi-persistent scheduling, of the downlink data channel (PDSCH) for the terminal group is applied in units of the terminal group.
[0080] In addition, the control unit 270 can set the configuration of a codebook (which may be read as a bit string, etc.) related to HARQ feedback for MBS. Specifically, the control unit 270 can change or determine the configuration of the type-1 HARQ-ACK CB (codebook) based on specific conditions.
[0081] Note that, as described above, type-1 and type-2 are defined for the HARQ-ACK CB determination algorithm. The main difference between type-1 and type-2 is that type-1 configures the HARQ-ACK CB in a semi-static manner, while type-2 configures the HARQ-ACK CB in a dynamic manner.
[0082] In the case of the type-1 HARQ-ACK CB, the control unit 270 may feedback HARQ-ACK bits corresponding to the predetermined range regardless of whether PDSCH scheduling is present within the predetermined range (for example, a range set based on upper layer parameters).
[0083] The predetermined range may be determined based on at least one of a predetermined period (for example, a set of a predetermined number of opportunities for candidate PDSCH reception, or a predetermined number of monitoring occasions m of PDCCH), the number of Component carriers set or activated in the UE200, the number of Transport blocks (TBs) (number of layers or rank), the number of Code block groups per TB, and the application of spatial bundling. The predetermined range is also called a HARQ-ACK bundling window, a HARQ feedback window, a bundling window, a feedback window, etc.
[0084] For example, the control unit 270 may determine the configuration of the HARQ feedback for the PDSCH related to MBS (which may be referred to as MBS PDSCH) and the HARQ feedback for the terminal-specific PDSCH based on the UE capability of the UE 200.
[0085] Specifically, the control unit 270 may determine the configuration of the HARQ feedback for the PDSCH (which may be referred to as the first downlink data channel) that is common to the UE group (terminal group) and the HARQ feedback for the terminal-specific PDSCH (the second downlink data channel). The terminal-specific PDSCH may be referred to as Unicast PDSCH.
[0086] Examples of the UE capability used for determining the configuration of the HARQ-ACK CB include, for example, the function of simultaneously receiving the Unicast PDSCH and the MBS PDSCH in the same symbol (frequency division multiplexing (FDM)) in a certain cell.
[0087] However, it is not necessary to be limited to such a capability as long as it is information that can explicitly or implicitly indicate the simultaneous reception of the Unicast PDSCH and the MBS PDSCH. That is, the control unit 270 may determine the configuration based on whether the MBS PDSCH (the first downlink data channel) and the Unicast PDSCH (the second downlink data channel) can be received within the same time domain (that is, whether they are set to be received within the same time domain) in the same cell.
[0088] In addition, the control unit 270 may determine the configuration of the HARQ feedback for the MBS PDSCH and the HARQ feedback for the Unicast PDSCH, specifically, the configuration of the HARQ-ACK CB, based on the parameters of the radio resource control layer (RRC) instead of the UE capability.
[0089] For example, the control unit 270 may determine the configuration of the HARQ-ACK CB based on whether a predetermined parameter in the RRC is set. The predetermined parameter is not limited, but for example, it may be sufficient to indicate whether FDM between Unicast PDSCH and MBS PDSCH is applied (or whether TDM is not applied).
[0090] Alternatively, the control unit 270 may determine the configuration of the HARQ-ACK CB based on the content of the value indicated by the RRC parameter. For example, the content may be sufficient to indicate that FDM (or TDM) between Unicast PDSCH and MBS PDSCH is applied.
[0091] In addition, the control unit 270 may interpret that the possibility that Unicast PDSCH and MBS PDSCH are received at the timing of the same symbol in a certain cell is limited when a predetermined condition is satisfied.
[0092] In other words, the control unit 270 may assume that in the same cell, only when a specific condition is satisfied, MBS PDSCH and Unicast PDSCH are received within the same time domain.
[0093] Note that the control unit 270 may assume that it is limited to the case where the HARQ-ACK bit for a certain MBS PDSCH and the HARQ-ACK bit for a certain Unicast PDSCH correspond to different HARQ-ACK bits of the type-1 HARQ-ACK CB.
[0094] In addition, gNB100 can execute the scheduling of the downlink channel and the control related to HARQ described above.
[0095] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation regarding the scheduling of the downlink channel related to the MBS and the HARQ feedback of the channel will be described.
[0096] FIG. 5 shows an example sequence of PDCCH, PDSCH, and HARQ feedback in the MBS. As shown in FIG. 5, the PDCCH (which may include DCI) and the PDSCH may be transmitted by unicast or multicast (broadcast). Also, the UE 200 may transmit HARQ feedback (ACK / NACK) for the transport block (TB) received via the channel.
[0097] Note that in FIG. 5, it appears that both the unicast PDSCH and the multicast PDSCH are transmitted after one PDCCH / DCI, but either the unicast PDSCH or the multicast PDSCH may be transmitted after one PDCCH / DCI. That is, one PDCCH / DCI may schedule either the unicast PDSCH or the multicast PDSCH.
[0098] Also, as shown in FIG. 5, in the HARQ feedback of the MBS, the HARQ-ACK CB may be configured as described above. Regarding the configuration of the HARQ-ACK CB, it is assumed that the type-1 HARQ-ACK CB is generated by concatenating (union) the PDSCH Time Domain Resource Allocation (TDRA) table / set.
[0099] The type-1 HARQ-ACK CB is semi-static as described above and may be interpreted as the HARQ-ACK bits corresponding to the actual and potential PDSCH receptions. The type-1 HARQ-ACK CB is a method based on the premise that multiple PDSCHs do not overlap on the same symbol in a certain cell.
[0100] The type-1 HARQ-ACK CB functions when MBS PDSCH and Unicast PDSCH are TDM, but does not function when MBS PDSCH and Unicast PDSCH are FDM, so another method is required.
[0101] FIG. 6 shows an example of constructing a type-1 HARQ-ACK CB by concatenating PDSCH TDRA tables / sets. In FIG. 6, it shows that PDSCHs with the same alphabet are represented by the same HARQ-ACK bits.
[0102] As described above, the following two configuration methods may be assumed for the type-1 HARQ-ACK CB.
[0103] · (i) Configuration method when MBS PDSCH and Unicast PDSCH are multiplexed by TDM in a certain cell (which may be interpreted as the same cell) · (ii) Configuration method when MBS PDSCH and Unicast PDSCH are multiplexed by FDM in a certain cell (which may be interpreted as the same cell) (i) may be a method of generating the CB in the same way as in the case of unicast alone based on the union of TDRA tables / sets. This method may be applied to all slots. Also, it may be applied limited to the slots in which both Unicast PDSCH and MBS PDSCH can be transmitted.
[0104] (ii) may be a method of generating the CB in a different way from the case of unicast alone, either without or based on the union of TDRA tables / sets. In this case, the CB may be generated by any of the following methods.
[0105] · (Option 1): Generate the CB for Unicast PDSCH over all slots and the CB for MBS PDSCH over all slots, and finally concatenate them ·(Option 2): Generate and concatenate the codeblocks (CBs) for Unicast PDSCH and the CBs for MBS PDSCH in each slot, and repeat this for all slots. ·(Option 3): Split Unicast PDSCH and MBS PDSCH into Start and Length Indicator Value (SLIV) groups (for example, A, B, and C in Figure 6 correspond to each SLIV group), and in each SLIV group, generate and concatenate the CBs for Unicast PDSCH and the CBs for MBS PDSCH, and repeat this for all SLIV groups in all slots.
[0106] (3.1) Operation Example 1 In this operation example, the method of configuring the type-1 HARQ-ACK codeblock may be changed based on predetermined conditions. Note that the method of configuring the type-1 HARQ-ACK codeblock may use (i) or (ii) described above.
[0107] Specifically, UE200 may operate according to Operation Examples 1-1 to 1-4.
[0108] ·(Operation Example 1-1): A predetermined UE capability is a predetermined value. For example, in a certain cell, it may be a UE capability indicating whether it supports the function of simultaneously receiving Unicast PDSCH and MBS PDSCH on the same symbol (which may be read as other time-domain expressions and may be interpreted as corresponding to FDM).
[0109] If this function is supported, (i) is applied, and if it is not supported, (ii) may be applied.
[0110] According to such an operation example, in a UE that does not support FDM, excessive bit number feedback can be avoided.
[0111] ·(Operation Example 1-2): A predetermined RRC parameter is set. For example, it may be an RRC parameter indicating whether to execute (ii). When the RRC parameter is set, (i) may be applied, and when it is not set, (ii) may be applied.
[0112] According to such an operation example, the network can appropriately control the UE 200 so as to satisfy the required communication quality.
[0113] ·(Operation Example 1-3): A predetermined RRC parameter is a predetermined value For example, it may be an RRC parameter directly indicating (i) or (ii). Also according to such an operation example, the network can appropriately control the UE 200 so as to satisfy the required communication quality.
[0114] ·(Operation Example 1-4): Regarding the setting related to the allocation of PDSCH, it is a setting in which a case where Unicast PDSCH and MBS PDSCH are simultaneously received (FDM) on the same symbol in a certain cell may occur FIG. 7 shows a configuration example of a type-1 HARQ-ACK CB according to Operation Example 1 (when Unicast PDSCH and MBS PDSCH are FDM). FIG. 8 shows a configuration example of a type-1 HARQ-ACK CB according to Operation Example 1 (when Unicast PDSCH and MBS PDSCH are TDM).
[0115] For example, for PDSCH candidates in the TDRA table / set, when there is a possibility that they may be allocated to the same symbol in a certain cell, (ii), that is, the configuration method in the case where Unicast PDSCH and MBS PDSCH are FDM, may be applied.
[0116] On the other hand, for PDSCH candidates in the TDRA table / set, when there is no possibility that they are allocated to the same symbol in a certain cell, (i), that is, the case where Unicast PDSCH and MBS PDSCH are TDM, may be applied.
[0117] Also, for the candidates of the indication in the PDSCH-to-HARQ_feedback timing indicator field of DCI, if they may be scheduled in the same slot in a certain cell, (i) or (ii) may be applicable.
[0118] Alternatively, for the candidates of the indication in the PDSCH-to-HARQ_feedback timing indicator field, if they are not likely to be scheduled in the same slot in a certain cell, (ii) may be applicable.
[0119] According to this operation example, an appropriate multiplexing method can be selected based on whether the FDM case can actually occur.
[0120] (3.2) Operation Example 2 The possibility that MBS PDSCH and Unicast PDSCH are received on the same symbol in a certain cell may be limited when a predetermined condition is satisfied.
[0121] Specifically, UE200 may operate according to Operation Example 2-1.
[0122] ·(Operation Example 2-1): Limited to the case where the HARQ-ACK bits for a certain MBS PDSCH and the HARQ-ACK bits for a certain Unicast PDSCH correspond to different HARQ-ACK bits of a type-1 HARQ-ACK CB For example, it may be limited to the case where the HARQ-ACK CB is configured according to the configuration method of (i) and corresponds to different HARQ-ACK bits.
[0123] FIG. 9 shows a configuration example of a type-1 HARQ-ACK CB according to Operation Example 2. The configuration example shown in FIG. 9 is the same as the configuration example shown in FIG. 6.
[0124] For example, when receiving a Unicast PDSCH corresponding to "A" (SLIV group) in FIG. 9, it may be assumed that an MBS PDSCH corresponding to "B" can be received simultaneously, but an MBS PDSCH corresponding to "A" cannot be received simultaneously.
[0125] According to this operation example, in the case of TDM / FDM, the same HARQ-ACK CB configuration method can be applied.
[0126] (4) Operations and Effects According to the above-described embodiments, the following operations and effects can be obtained. Specifically, the UE 200 can determine the configuration of the HARQ feedback of the MBS PDSCH (first downlink data channel) and the HARQ feedback of the Unicast PDSCH (second downlink data channel) based on the terminal capabilities or RRC parameters.
[0127] Also, it can be assumed that in the same cell, the MBS PDSCH and the Unicast PDSCH are received within the same time domain only when specific conditions are satisfied.
[0128] Therefore, even when the configuration of the HARQ-ACK CB differs due to the difference in the multiplexing method between TDM or FDM, the UE 200 can configure an appropriate HARQ feedback regardless of the multiplexing method between the MBS PDSCH and the Unicast PDSCH.
[0129] Also, in this embodiment, the UE 200 may determine the configuration of the type-1 HARQ-ACK CB based on whether the MBS PDSCH and the Unicast PDSCH are received within the same time domain in the same cell. Therefore, an appropriate type-1 HARQ-ACK CB can be configured according to the states of the MBS PDSCH and the Unicast PDSCH.
[0130] (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.
[0131] For example, in the above-described embodiments, the names PDCCH and PDSCH are used as the downlink channels. However, as long as they are downlink control channels or downlink data channels (which may be shared channels), they may be called by other names.
[0132] In addition, in the above description, configure, activate, update, indicate, enable, specify, select may be mutually interchanged. Similarly, link, associate, correspond, map may be mutually interchanged, and allocate, assign, monitor, map may also be mutually interchanged.
[0133] Furthermore, specific, dedicated, UE-specific, UE-dedicated may be mutually interchanged. Similarly, common, shared, group-common, UE-common, UE-shared may be mutually interchanged.
[0134] In addition, the block diagram (FIG. 4) used in the description of the above-described embodiments shows blocks of functional units. These functional blocks (constituent parts) are realized by any combination of at least one of hardware and software. Also, the method of realizing 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 connected (for example, using wired, wireless, etc.), 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.
[0135] Functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (constituent part) that functions as transmission is referred to as a transmitting unit or a transmitter. In any case, as described above, the realization method is not particularly limited.
[0136] 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. 10 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 10, 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, and the like.
[0137] In the following description, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the device may be configured to include one or more of each device shown in the figure, or may be configured without including some of the devices.
[0138] 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.
[0139] Also, each function in the device is realized by loading a predetermined software (program) 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, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.
[0140] The processor 1001 controls the entire computer by operating, for example, an operating system. 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, etc.
[0141] Also, 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 the 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 mounted by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.
[0142] The memory 1002 is a computer-readable recording medium and may be constituted by 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, a cache, a main memory (main storage device), etc. The memory 1002 can store a program (program code), a software module, etc. that can execute the method according to an embodiment of the present disclosure.
[0143] The storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital versatile disc, a Blu-ray (registered trademark) disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The storage 1003 may also be referred to as an auxiliary storage device. The above-described 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.
[0144] 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.
[0145] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
[0146] 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).
[0147] 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.
[0148] 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.
[0149] Also, the notification of information is not limited to the aspects / embodiments described in the present 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 combinations 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.
[0150] Each aspect / embodiment described in the present 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, etc.) and applied.
[0151] 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, regarding 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.
[0152] 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.
[0153] 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.
[0154] 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.
[0155] The determination may be made by a value represented by 1 bit (0 or 1), or by a Boolean value (true or false), or by a numerical comparison (for example, comparison with a predetermined value).
[0156] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched and used during execution. Also, 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).
[0157] Software should be broadly interpreted 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.
[0158] 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 cables, optical fiber cables, twisted pairs, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwaves, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.
[0159] 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., 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.
[0160] In addition, with regard to the terms described in this disclosure and the terms necessary for understanding this 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, a signal may be a message. Further, a component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.
[0161] The terms "system" and "network" used in this disclosure are used interchangeably.
[0162] Also, the information, parameters, etc. described in this 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.
[0163] The names used for the above-described parameters are not limiting names in any way. Furthermore, the mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in this 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 way.
[0164] 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", and "component carrier" may be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0165] A base station can accommodate one or more (e.g., three) cells (also referred to as 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 these smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0166] 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.
[0167] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.
[0168] 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.
[0169] At least one of the base station and the mobile station may also be referred to as a transmitting device, receiving device, 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.
[0170] 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 the 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).
[0171] 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 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 does not depend on numerology.
[0172] Numerology may be communication parameters applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier 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.
[0173] A slot may be composed of one or more symbols (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.
[0174] 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 referred to as 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 referred to as PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as PDSCH (or PUSCH) mapping type B.
[0175] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units when transmitting a signal. Different names corresponding to each of them may also be used.
[0176] For example, one sub-frame may be referred to as a transmission time interval (TTI), or a plurality of consecutive sub-frames may be referred to as TTI, or one slot or one mini-slot may be referred to as 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 referred to as a slot, mini-slot, etc. instead of a sub-frame.
[0177] Here, TTI refers to, for example, the minimum time unit of 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 units of TTI. Note that the definition of TTI is not limited to this.
[0178] 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 and link adaptation. When the TTI is given, the time interval (e.g., the number of symbols) in which the actual transport block, codeword, etc. are mapped may be shorter than the TTI.
[0179] Note that when 1 slot or 1 mini-slot is called a TTI, 1 or more TTIs (i.e., 1 or more slots or 1 or more mini-slots) may be the minimum time unit of scheduling. Also, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
[0180] 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 a 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.
[0181] 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 a long TTI and a TTI length of 1 ms or more.
[0182] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and in the frequency domain, it may include one or a plurality of consecutive subcarriers. 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.
[0183] Also, the time domain of the RB may include one or more symbols, and may have 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.
[0184] Note that one or more RBs may be referred to as Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.
[0185] Also, the resource block may be composed of one or more resource elements (RE). For example, 1 RE may be a radio resource area of 1 sub-carrier and 1 symbol.
[0186] The Bandwidth Part (BWP) (which may also be called partial bandwidth, etc.) may represent a subset of consecutive common resource blocks 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.
[0187] 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 1 carrier for the UE.
[0188] 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".
[0189] 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.
[0190] 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.
[0191] The reference signal can also be abbreviated as Reference Signal (RS) and may be called a Pilot depending on the applicable standard.
[0192] 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".
[0193] In the configuration of each of the above devices, the "means" may be replaced with a "section", "circuit", "device", etc.
[0194] Any reference in this disclosure to elements using terms such as "first", "second", etc. does not generally limit the quantity or order of those elements. These terms may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not mean that only two elements can be employed there, or that the first element must precede the second element in any way.
[0195] In this 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 this disclosure is not intended to be an exclusive disjunction.
[0196] In this disclosure, for example, when articles are added by translation, as in the case of a, an and the in English, this disclosure may include that the nouns following these articles are in the plural form.
[0197] As used in this disclosure, the terms "determining" and "deciding" may encompass a wide variety of actions. "Determining" and "deciding" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching 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" through some action. Also, "determining (deciding)" may be read as "assuming", "expecting", "considering", etc.
[0198] In this disclosure, the term "A and B are different" 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 be interpreted in the same way as "different".
[0199] Although the present disclosure has been described in detail above, it is apparent 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 as modifications and variations 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
[0200] 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 first method for generating a codebook for automatic repeat request feedback based on the union of time domain resource allocation for a first downlink data channel in multicast and time domain resource allocation for a second downlink data channel in unicast, and a codebook for automatic repeat request feedback of the first downlink data channel, and a second method for generating a codebook by combining the codebooks for automatic repeat request feedback of the second downlink data channel after generating them respectively, and a control unit that determines which method to use for feedback transmission based on parameters of the radio resource control layer, A transmission unit that transmits an automatic repeat request feedback for reception of the first downlink data channel and an automatic repeat request feedback for reception of the second downlink data channel based on the determination, A terminal comprising the same.
2. The terminal according to claim 1, wherein the control unit determines to use the second method when receiving the parameter indicating that the first downlink data channel and the second downlink data channel are frequency division multiplexed.
3. The terminal according to claim 1, wherein the transmission unit transmits capability information indicating that the first downlink data channel and the second downlink data channel can be received in the same time domain.
4. A step of determining which of a first method for generating a codebook for automatic repeat request feedback based on the union of time domain resource allocation for a first downlink data channel in multicast and time domain resource allocation for a second downlink data channel in unicast, and a codebook for automatic repeat request feedback of the first downlink data channel, and a second method for generating a codebook by combining the codebooks for automatic repeat request feedback of the second downlink data channel after generating them respectively, to use for feedback transmission based on parameters of the radio resource control layer, A step of transmitting an automatic repeat request feedback for reception by the first downlink data channel and an automatic repeat request feedback for reception of the second downlink data channel based on the determination, A communication method for a terminal including the same.
5. A communication system including a base station and a terminal, The base station is, A transmission unit that performs transmission by a first downlink data channel in multicast and transmission by a second downlink data channel in unicast is provided. The terminal Based on the union of the time domain resource allocation for the first downlink data channel and the time domain resource allocation for the second downlink data channel, a first method of generating a codebook for automatic repeat request feedback, the codebook for automatic repeat request feedback of the first downlink data channel, and the codebook for automatic repeat request feedback of the second downlink data channel are generated respectively, and then a control unit that determines which of the second methods of combining to generate a codebook is used for feedback transmission based on the parameters of the radio resource control layer, Based on the determination, a transmission unit that transmits an automatic repeat request feedback for reception by the first downlink data channel and an automatic repeat request feedback for reception by the second downlink data channel, Comprising Communication system.
Citation Information
Patent Citations
Feedback for multicast and broadcast messages
US20210111835A1
Cited By
Time domain resource allocation for multicast broadcast service
US12538316B2