Communication device, scheduling node and method thereof, and integrated circuit

Abstract

The invention relates to a communication device, a scheduling node and a method thereof, and an integrated circuit. The communication device comprises: a transceiver for receiving downlink control information (DCI); and circuitry to obtain an indication from the DCI that references an entry of a Time Domain Resource Allocation (TDRA) table, where a quantity of data N is associated with a quantity of entries included in the TDRA table, N being an integer greater than 1.

Description

[0001] This application is a divisional application of the invention patent application with the application date of July 15, 2021, application number: 202180045679.4, and invention name: "User equipment, scheduling node, method for user equipment and method for scheduling node". Technical Field

[0002] The present disclosure is directed to methods, apparatus and articles in a communication system, such as a 3GPP communication system.

[0003] The present disclosure relates to the transmission and reception of signals in a communication system, and more particularly to methods and apparatus for such transmission and reception. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) is working on the technical specifications for the next generation of cellular technology, also known as fifth generation (5G), including the "New Radio" (NR) radio access technology (RAT) operating in the frequency range up to 100 GHz. NR is a follow-up to technologies such as Long Term Evolution (LTE) and LTE-Advanced (LTE-A).

[0005] For systems like LTE and NR, further improvements and options may contribute to the efficient operation of the communication system and the specific devices attached to the system. Summary of the Invention

[0006] One non-limiting and exemplary embodiment facilitates providing efficient downlink control information (DCI) scheduling of multiple transport blocks (TBs) in a wireless communication system.

[0007] In one embodiment, the technology disclosed herein is characterized by a communication device comprising: a transceiver that receives downlink control information (DCI); and a circuit that obtains an indication of an entry of a referenced time domain resource allocation (TDRA) table from the DCI, wherein a data quantity N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

[0008] In one embodiment, the technology disclosed herein is characterized by a scheduling device comprising: a circuit that generates downlink control information (DCI), wherein the DCI includes an indication of an entry referencing a time domain resource allocation (TDRA) table, wherein the amount of data N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1; and a transceiver that sends the DCI to a communication device.

[0009] In one embodiment, the technology disclosed herein is characterized by a method for a communication device, the method comprising the steps of: receiving downlink control information DCI; and obtaining an indication of an entry of a referenced time domain resource allocation TDRA table from the DCI, wherein the amount of data N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

[0010] In one embodiment, the technology disclosed herein is characterized by a method for scheduling a device, the method comprising the steps of: generating downlink control information DCI, wherein the DCI includes an indication of at least a reference to an entry of a time domain resource allocation TDRA table, wherein the amount of data N is associated with the number of entries included in the TDRA table, wherein N is an integer greater than 1; and sending the DCI to a communication device.

[0011] In one embodiment, the technology disclosed herein is characterized by an integrated circuit that controls a process of a communication device, the integrated circuit including a circuit that controls: receiving downlink control information DCI; and obtaining an indication of at least a referenced entry of a time domain resource allocation TDRA table from the DCI, wherein the amount of data N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

[0012] In one embodiment, the technology disclosed herein is characterized by an integrated circuit that controls a process of a scheduling device, the integrated circuit including a circuit that controls: generating downlink control information DCI, wherein the DCI includes an indication of an entry referencing a time domain resource allocation TDRA table, wherein the amount of data N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1; and sending the DCI to a communication device.

[0013] In one embodiment, the technology disclosed herein features an apparatus (e.g., user equipment (UE)). The apparatus includes a transceiver that receives downlink control information (DCI) signaling. The apparatus also includes circuitry that obtains, from the DCI signaling, an indication indicating a schedule of N transport blocks, where N is greater than 1. The indication further indicates at least one of: i) a schedule of M repetitions of a transport block (TB), where M is equal to or greater than one; ii) an interleaving pattern of the TBs; and iii) a transmission gap between the TBs.

[0014] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.

[0015] Additional benefits and advantages of the disclosed embodiments will become apparent from the description and drawings. Such benefits and / or advantages may be achieved individually by various embodiments and features of the description and drawings, and it is not necessary to provide all of these embodiments and features in order to achieve one or more such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Exemplary embodiments will be described in more detail below with reference to the accompanying drawings and figures.

[0017] Figure 1 An exemplary architecture of a 3GPP NR system is shown;

[0018] Figure 2 is a schematic diagram showing the functional division between NG-RAN and 5GC;

[0019] Figure 3 It is a sequence diagram of the RRC connection establishment / reconfiguration procedure;

[0020] Figure 4 is a schematic diagram illustrating usage scenarios of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC);

[0021] Figure 5 is a block diagram illustrating an exemplary 5G system architecture for non-roaming;

[0022] Figure 6 is a block diagram illustrating functional components of a base station and a user equipment according to an embodiment;

[0023] Figure 7 is a block diagram illustrating steps of an exemplary communication method for a UE and steps of an exemplary communication method for a base station;

[0024] Figure 8a is a diagram of an exemplary scheduling of two transport blocks with repetition and transmission gaps but no interleaving between TBs;

[0025] Figure 8b is a diagram of an exemplary scheduling of two transport blocks with repetition and interleaving but without a transmission gap;

[0026] Figure 8c is a diagram illustrating an exemplary schedule of four transport blocks without repetition, interleaving, and transmission gaps;

[0027] Figure 8d is a diagram of an exemplary scheduling of two transport blocks with a transmission gap between TBs but without repetition and interleaving; and

[0028] Figure 9is a diagram illustrating an exemplary scheduling of two transport blocks using a configured grant (CG) or semi-persistent scheduling (SPS) framework. DETAILED DESCRIPTION

[0029] 5G NR system architecture and protocol stack

[0030] 3GPP has been working on the next release of fifth-generation cellular technology, known as 5G, including the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed in late 2017, allowing for trials and commercial deployment of smartphones compliant with the 5G NR standard.

[0031] The overall system architecture utilizes the NG-RAN (Next Generation Radio Access Network) consisting of gNBs, which provide NG-Radio Access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations to the UE. The gNBs are interconnected via Xn interfaces. The gNBs are also connected to the Next Generation Core (NGC) via Next Generation (NG) interfaces. More specifically, the gNBs are connected to the Access and Mobility Management Function (AMF) (e.g., a core entity that implements the AMF) via the NG-C interface, and to the User Plane Function (UPF) (e.g., a core entity that implements the UPF) via the NG-U interface. Figure 1 The middle figure shows the NG-RAN architecture (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0032] The user plane protocol stack for NR (see, for example, 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol, see Section 6.4 of TS 38.300), the RLC (Radio Link Control, see Section 6.3 of TS 38.300), and the MAC (Medium Access Control, see Section 6.2 of TS 38.300) sublayers, which terminate in the gNB on the network side. Additionally, a new Access Stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced above PDCP (see, for example, subclause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, for example, TS 38.300, Section 4.4.2). An overview of Layer 2 functionality is provided in subclause 6 of TS 38.300. The functions of the PDCP, RLC, and MAC sublayers are listed in Sections 6.4, 6.3, and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in Subclause 7 of TS 38.300.

[0033] For example, the medium access control layer handles logical channel multiplexing, as well as scheduling and scheduling-related functions, including handling different parameter sets.

[0034] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. It also handles the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmission of a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) for uplink, and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) for downlink.

[0035] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), which have different requirements in terms of data rate, latency and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user experience data rates that are about three times that provided by advanced IMT. On the other hand, in the case of URLLC, ultra-low latency (0.5ms for user plane delay for UL and DL each) and high reliability (1-10 times within 1ms) are required. -5 Finally, mMTC may preferably require high connection density (1,000,000 devices / km in urban environments) 2 ), wide coverage in harsh environments, and extremely long battery life (15 years) for low-cost devices.

[0036] Therefore, an OFDM parameter set (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case may not be suitable for another use case. For example, low latency services may preferably require shorter symbol duration (and therefore larger subcarrier spacing) and / or fewer symbols per scheduling interval (also known as TTI) than mMTC services. In addition, deployment scenarios with large channel delay spread may preferably require longer CP duration than those with short delay spread. The subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one subcarrier spacing value. Correspondingly, subcarrier spacing of 15kHz, 30kHz, 60kHz... are currently under consideration. Symbol duration T u And the subcarrier spacing Δf is calculated by the formula Δf=1 / T u In a similar manner as in the LTE system, the term "resource element" may be used to refer to a minimum resource unit consisting of one subcarrier of one OFDM / SC-FDMA symbol length.

[0037] In the new radio system 5G-NR, for each parameter set and carrier, a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink, respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v16.0.0, e.g., Section 4). For example, downlink and uplink transmissions are organized into frames of 10 ms duration, each consisting of ten subframes of 1 ms duration each. In 5G NR implementations, the number of consecutive OFDM symbols per subframe depends on the subcarrier spacing configuration. For example, for a 15 kHz subcarrier spacing, a subframe has 14 OFDM symbols (similar to LTE-compliant implementations, assuming a normal cyclic prefix). On the other hand, for a 30 kHz subcarrier spacing, a subframe has two slots, each of which includes 14 OFDM symbols.

[0038] Compared to the LTE numerology (subcarrier spacing and symbol length), NR supports multiple different types of subcarrier spacing, marked by the parameter μ (in LTE, there is only a 15kHz subcarrier spacing, which corresponds to μ=0 in NR). The types of NR numerology are summarized in 3GPP TS 38.211, v15.7.0.

[0039] 5G NR functional division between NG-RAN and 5GC

[0040] Figure 2The figure shows the functional division between NG-RAN and 5GC. The NG-RAN logical node is the gNB or ng-eNB. The 5GC has the logical nodes AMF, UPF, and SMF.

[0041] Specifically, gNB and ng-eNB host the following key functions:

[0042] - Functions for radio resource management, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (scheduling);

[0043] -IP header compression, encryption and integrity protection of data;

[0044] - selection of the AMF at UE attach when the route to the AMF cannot be determined from the information provided by the UE;

[0045] - Routing user plane data towards UPF(s);

[0046] - Routing control plane information towards the AMF;

[0047] -Connection establishment and release;

[0048] - Scheduling and sending of paging messages;

[0049] - Scheduling and sending of system broadcast information (derived from AMF or OAM);

[0050] - Measurement and measurement reporting configuration for mobility and scheduling;

[0051] -Transmission level grouping marking in uplink;

[0052] -Session management;

[0053] - Network slicing support;

[0054] -QoS flow management and mapping to data radio bearers;

[0055] - Support for UEs in RRC_INACTIVE state;

[0056] -NAS message distribution function;

[0057] - Wireless access network sharing;

[0058] -Dual connectivity;

[0059] - Close interworking between NR and E-UTRA.

[0060] The Access and Mobility Management Function (AMF) hosts the following key functions:

[0061] -Non-access stratum, NAS, signaling terminal;

[0062] -NAS signaling security;

[0063] -Access layer, AS, security control;

[0064] - Inter-core network (CN) node signalling for mobility between 3GPP access networks;

[0065] - Idle mode UE reachability (including control and operation of paging retransmission);

[0066] -Registration area management;

[0067] -Support for intra-system and inter-system mobility;

[0068] -Access authorization;

[0069] -Access authorization, including verification of roaming rights;

[0070] - Mobility management control (subscription and policy);

[0071] - Network slicing support;

[0072] -Session Management Function, SMF, selection.

[0073] Additionally, the User Plane Function (UPF) hosts the following key functions:

[0074] - Anchor point for intra-RAT / inter-RAT mobility (when applicable);

[0075] - External PDU session points interconnected with the data network;

[0076] -Packet routing and forwarding;

[0077] - User plane portion for packet inspection and policy rule enforcement;

[0078] - Traffic usage reports;

[0079] - Uplink classifier that supports routing traffic flows to the data network;

[0080] -Support branch points for multi-homed PDU sessions;

[0081] - QoS handling for the user plane, such as packet filtering, gating, UL / DL rate enforcement;

[0082] - Uplink traffic verification (SDF to QoS flow mapping);

[0083] - Downlink packet buffering and downlink data notification triggering.

[0084] Finally, the session management function SMF hosts the following main functions:

[0085] -Session management;

[0086] -UE IP address allocation and management;

[0087] -UP selection and control;

[0088] -Configure traffic steering at the user plane function (UPF) to route traffic to the appropriate destination;

[0089] -Policy enforcement and QoS control;

[0090] -Downlink data notification.

[0091] RRC connection establishment and reconfiguration process

[0092] Figure 3 The figure shows some interactions between the UE, gNB and AMF (5GC entity) in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED for the NAS part (see TS 38.300 v15.6.0).

[0093] RRC is the higher-layer signaling (protocol) used for UE and gNB configuration. Specifically, the transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities) and sending it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security with the UE by sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. The gNB then performs reconfiguration to establish Signaling Radio Bearer 2 (SRB 2) and Data Radio Bearer(s) (DRBs) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete message from the UE in response. For signaling-only connections, the steps related to RRCReconfiguration are skipped because SRB 2 and DRBs are not established. Finally, the gNB notifies the AMF of the completion of the establishment procedure via an Initial Context Setup Response.

[0094] Therefore, the present disclosure provides a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.), which includes: a control circuit that establishes a next generation (NG) connection with a gNodeB; and a transmitter that sends an initial context setup message to the gNodeB via the NG connection to trigger the establishment of a signaling radio bearer between the gNodeB and a user equipment (UE). Specifically, the gNodeB sends radio resource control (RRC) signaling containing a resource allocation configuration information element to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0095] IMT usage scenarios in 2020 and beyond

[0096] Figure 4 The diagram illustrates some use cases for 5G NR. Within the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are being considered that envision supporting a wide range of services and applications for IMT-2020. The first phase of specifications for enhanced mobile broadband (eMBB) has been finalized. In addition to further expanding eMBB support, current and future work will involve standardization of ultra-reliable and low-latency communications (URLLC) and massive machine-type communications. Figure 4 Some examples of envisaged usage scenarios for IMT for 2020 and beyond are illustrated (see for example ITU-R M.2083 Figure 2 ).

[0097] URLLC use cases have stringent requirements on capabilities such as throughput, latency, and availability, and are envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, distribution automation in smart grids, transportation safety, etc. Ultra-reliability of URLLC is supported by identifying technologies that meet the requirements of TR 38.913. For NR URLLC in Release 15, the key requirements include a target user plane latency of 0.5ms for UL (uplink) and a target user plane latency of 0.5ms for DL (downlink). For a packet size of 32 bytes with a user plane latency of 1 millisecond, the general URLLC requirement for one transmission of a packet is a BLER (block error rate) of 1E-5.

[0098] From a physical layer perspective, reliability can be improved in a number of possible ways. Current scope for improving reliability involves defining separate CQI tables for URLLC, more compact DCI formats, PDCCH repetition, etc. However, as NR becomes more stable and developed, the scope for achieving ultra-reliability (a key requirement for NR URLLC) is likely to expand. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-security, and mission-critical applications.

[0099] In addition, technical enhancements to the NRURLLC target are aimed at improving latency and reliability. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, unlicensed (permitted by configuration) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means that the transmission for which resources have been allocated is stopped, and the allocated resources are used for another transmission that is requested later but has lower latency / higher priority. Accordingly, the transmission that has been granted is preempted by the later transmission. Preemption is applicable independently of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.

[0100] The mMTC (Massive Machine Type Communication) use case is characterized by a very large number of connected devices, often transmitting relatively low volumes of non-latency-sensitive data. Devices are required to be low-cost and have very long battery life. From the perspective of NR, utilizing very narrow bandwidth segments is a possible solution that (from the UE's perspective) conserves power and enables long battery life.

[0101] As mentioned above, the scope of reliability in NR is expected to become even broader. A key requirement for all use cases, but particularly essential for URLLC and mMTC, is high or ultra-reliability. Several mechanisms can be considered to improve reliability from both a radio and network perspective. Generally speaking, there are several key potential areas that can help improve reliability. These include compact control channel information, data / control channel repetition, and diversity in the frequency, time, and / or spatial domains. These areas apply to general reliability, regardless of the specific communication scenario.

[0102] For NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, transportation industry and power distribution. The more stringent requirements are higher reliability (up to 10 6level), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few microseconds (where this value can be one or a few microseconds, depending on the frequency range), and short latency on the order of 0.5 to 1 millisecond, specifically a target user plane latency of 0.5 milliseconds, depending on the use case.

[0103] In addition, for NR URLLC, some technical enhancements have been identified from the physical layer perspective. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements have also been identified. The term "mini-slot" refers to a Transmission Time Interval (TTI) that includes a smaller number of symbols than a slot (a slot includes 14 symbols).

[0104] QoS control

[0105] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows that require guaranteed bit rates (GBR QoS flows) and QoS flows that do not require guaranteed bit rates (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest QoS differentiation granularity within a PDU session. Within a PDU session, a QoS flow is identified by a QoS Flow ID (QFI) carried in the encapsulation header on the NG-U interface.

[0106] For each UE, 5GC establishes one or more PDU sessions. For example, as mentioned above Figure 3 As shown, for each UE, the NG-RAN sets up at least one data radio bearer (DRB) along with the PDU session, and can subsequently configure additional DRBs for the QoS flows of that PDU session (when to do so depends on the NG-RAN). The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0107] Figure 5 The 5G NR non-roaming reference architecture (see TS 23.501 v16.1.0, Section 4.23) is illustrated. Figure 4The application functions (AF) exemplarily described in the

[0015] section, such as external application servers hosting 5G services, interact with the 3GPP core network in order to provide services, such as supporting the impact of applications on traffic routing, accessing the network exposure function (NEF), or interacting with the policy framework for policy control (see Policy Control Function, PCF) (e.g., QoS control). Based on operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions interact with related network functions using an external exposure framework via the NEF.

[0108] Figure 5 Other functional units of the 5G architecture are shown, namely the Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN), such as operator services, Internet access or third-party services. All or part of the core network functions and application services can be deployed and run in a cloud computing environment.

[0109] Therefore, in the present disclosure, an application server (e.g., AF of a 5G architecture) is provided, which includes a transmitter and a control circuit, which sends a request including QoS requirements for at least one of URLLC, eMMB, and mMTC services to at least one function of a 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements, and the control circuit uses the established PDU session to perform the service.

[0110] RRC status (RRC_Connected, RRC_Inactive)

[0111] In LTE, the RRC state machine consists of only two states, the RRC idle state (mainly characterized by high power saving, UE autonomous mobility and no UE connectivity to the core network established) and the RRC connected state, in which the UE can send user plane data while mobility is controlled by the network to support lossless service continuity. Together with 5G NR, the LTE-related RRC state machine can also be extended to inactive states (see, for example, TS 38.331v15.8.0, Figure 4 .2.1-2), similar to NR 5G explained below.

[0112] RRC in NR 5G (see TS 38.331v15.8.0, Section 4) supports the following three states: RRC Idle, RRC Inactive, and RRC Connected. When an RRC connection has been established, the UE is in either the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, i.e., no RRC connection has been established, the UE is in the RRC_IDLE state. Figure 6 As illustrated, the following state transitions are possible:

[0113] From RRC_IDLE to RRC_CONNECTED, following, for example, the "Connection Setup" procedure;

[0114] From RRC_CONNECTED to RRC_IDLE, following, for example, the "Connection Release" procedure;

[0115] From RRC_CONNECTED to RRC_INACTIVE, following e.g. the “Release with pending connection” procedure;

[0116] From RRC_INACTIVE to RRC_CONNECTED, following, for example, the "connection restart" procedure;

[0117] From RRC_INACTIVE to RRC_IDLE (one-way), following e.g. "Connection Release"

[0118] program.

[0119] A new RRC state, RRC Inactive, is defined for 5G 3GPP's new radio technology to provide benefits in supporting a wider range of services, such as eMBB (enhanced mobile broadband), mMTC (massive machine type communication), and URLLC (ultra-reliable and low latency communication), which have very different requirements in terms of signaling, power saving, latency, etc. Therefore, the new RRC Inactive state should be designed to allow minimization of signaling, power consumption, and resource expenditure in the radio access network and the core network, while still allowing, for example, data migration to be initiated with low latency.

[0120] Bandwidth

[0121] NR systems will support a maximum channel bandwidth that is much wider than LTE's 20MHz (e.g., 100MHz). LTE also supports wideband communications via carrier aggregation (CA) of up to 20MHz component carriers. By defining a wider channel bandwidth in NR, frequency resources can be dynamically allocated via scheduling, which can be more efficient and flexible than LTE's carrier aggregation operation, where activation / deactivation is based on MAC control elements. Having a single wideband carrier also has advantages in terms of low control overhead, as it only requires single control signaling (carrier aggregation requires separate control signaling for each aggregated carrier).

[0122] In addition, like LTE, NR can also support aggregation of multiple carriers via carrier aggregation or dual connectivity.

[0123] Since UEs do not always demand high data rates, using wide bandwidths can lead to higher idle power consumption from both RF and baseband signal processing perspectives. In this regard, the newly developed concept of bandwidth fractions for NR provides a way to operate UEs with a bandwidth smaller than the configured channel bandwidth, thereby providing an energy-efficient solution despite supporting wideband operation. Such low-end terminals that cannot access the full bandwidth of NR can benefit from this.

[0124] A bandwidth part (BWP) is a subset of a cell's total cell bandwidth, e.g., the positioning and number of contiguous physical resource blocks (PRBs). Bandwidth parts can be defined separately for uplink and downlink. Furthermore, each bandwidth part can be associated with a specific set of OFDM parameters, e.g., subcarrier spacing and cyclic prefix. Bandwidth adaptation is achieved, for example, by configuring a UE with one or more BWPs and informing the UE which of the configured BWPs is currently active.

[0125] For example, in 5G NR, a specific BWP is configured only for UEs in the RRC_Connected state. For example, in addition to the initial BWP (e.g., one for UL and one for DL, respectively), BWPs only exist for UEs in the connected state. To support the initial data exchange between the UE and the network, for example, during the process of moving the UE from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state, the initial DL BWP and the initial UL BWP are configured in the minimum SI.

[0126] Although a UE may be configured with more than one BWP (e.g., up to 4 BWPs per serving cell as currently defined for NR), a UE may only have one active DL BWP at a time.

[0127] Switching between configured BWPs can be achieved by means of downlink control information (DCI).

[0128] For a primary cell (PCell), the initial BWP is the BWP used for initial access, and the default BWP is the initial BWP unless another initial BWP is explicitly configured. For a secondary cell (SCell), an initial BWP is always explicitly configured, and a default BWP can also be configured. When a default BWP is configured for a serving cell, the expiration of the inactivity timer associated with that cell switches the active BWP to the default BWP.

[0129] Generally, it is envisaged that the downlink control information does not contain the BWP ID.

[0130] Downlink Control Information (DCI)

[0131] For example, PDCCH monitoring is performed by a UE to identify and receive information intended for the UE, such as control information and user traffic (eg, DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0132] The control information in the downlink (which may be referred to as downlink control information, DCI) in 5G NR has the same purpose as DCI in LTE, namely as a special set of control information for scheduling downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, many different DCI formats have been defined (see TS 38.212 v16.0.0 Section 7.3.1). The following table gives an overview.

[0133]

[0134]

[0135] The PDCCH search space is an area in the downlink resource grid (time-frequency resources) that can carry the PDCCH (DCI). In general, it is an area of radio resources used by a base station to send control information to one or more UEs in the downlink. The UE performs blind decoding on the entire search space in an attempt to find the PDCCH data (DCI). Conceptually, the search space concept in 5G NR is similar to that of LTE, although there are many differences in the details.

[0136] In 5G NR, PDCCH is sent in a radio resource area called a control resource set (CORESET). In LTE, the concept of CORESET does not exist explicitly. Instead, PDCCH in LTE uses the full carrier bandwidth (4 in the narrowest case) in the first 1-3 OFDM symbols. In contrast, CORESET in NR can appear anywhere within the timeslot and anywhere within the carrier frequency range, except for CORESETs outside its active bandwidth part (BWP) that the UE is not expected to handle. A CORESET is a set of physical radio resources (e.g., a specific area on the NR downlink resource grid) and a set of parameters used to carry PDCCH / DCI.

[0137] Accordingly, the UE uses the corresponding search space set to monitor the set of PDCCH candidates in one or more CORESETs on the active DL BWP on each activated serving cell configured with PDCCH monitoring, where monitoring implies decoding each PDCCH candidate according to the monitored DCI format (e.g., as defined in 3GPP TS 38.213 Version 16.0.0, sections 10 and 11).

[0138] In short, a search space can include multiple PDCCH candidates associated with the same aggregation level (e.g., where the PDCCH candidates differ with respect to the DCI format to be monitored). Conversely, a search space set can include multiple search spaces at different aggregation levels, but associated with the same CORESET. Unlike in LTE, where control channels span the entire carrier bandwidth, as described above, the bandwidth of a CORESET can be configured (for example) within the active DL frequency bandwidth part (BWP). In other words, the CORESET configuration defines the frequency resources of the search space set, and thus the frequency resources of the PDCCH candidates included in the search spaces in that set. The CORESET configuration also defines the duration of the search space set, which can be one to three OFDM symbols in length. The start time, on the other hand, is configured by the search space set configuration itself, i.e., at which OFDM symbol the UE begins monitoring the PDCCHs of the search spaces in that set. Combined, the configuration of the search space set and the CORESET provide an unambiguous definition of the UE's PDCCH monitoring requirements in both the frequency and time domains. Both CORESET and search space set configurations may be semi-statically configured via RRC signaling.

[0139] The first CORESET, CORESET 0, is provided by the Master Information Block (MIB) as part of the configuration of the initial bandwidth portion to enable the reception of the remaining system information and additional configuration information from the network. After connection establishment, multiple potentially overlapping CORESETs may be configured for the UE using RRC signaling.

[0140] The network can define a common control domain and a UE-specific control domain. In NR, the number of CORESETs is limited to 3 per BWP (including common and UE-specific CORESETs). When assuming, for example, that 4 BWPs are configured for each serving cell, the maximum number of CORESETs per serving cell will be 12. In general, the number of search spaces per BWP can be limited to (for example) 10 in current NR, resulting in a maximum number of search spaces per BWP of 40. Each search space is associated with a CORESET.

[0141] The common CORESET is shared by multiple UEs in a cell, so the network needs to take care of the alignment of the configuration with all UEs accordingly.The common CORESET can be used for random access, paging and system information.

[0142] In NR, flexible slot formats can be configured for UEs through cell-specific and / or UE-specific higher layer signaling in a semi-static downlink / uplink assignment manner, or through dynamic signaling, for example, via DCI format 2_0 in the Group Common PDCCH (GC-PDCCH). When dynamic signaling is configured, the UE monitors the GC-PDCCH (DCI format 2_0) carrying the dynamic slot format indication (SFI).

[0143] Typically, each BWP can be configured with one or more CORESETs (e.g., up to 3 CORESETs per BWP), including both common CORESETs and UE-specific CORESETs. Each CORESET can then have several search spaces, each with one or more PDCCH candidates that the UE can monitor.

[0144] Time Domain Scheduling in 5GNR

[0145] In the time domain, transmissions in 5G NR are organized into 10ms frames, each divided into 10 equally sized subframes of 1ms in length. A subframe is, in turn, divided into multiple slots, each consisting of 14 OFDM symbols. The duration of a slot, measured in milliseconds, depends on the numerology set. For example, with a 15kHz subcarrier spacing, an NR slot has the same structure as an LTE subframe with a normal cyclic prefix. The subframe in NR serves as a numerology-independent time reference, which is useful, especially when multiple numerologies are mixed on the same carrier, while the slot is the typical unit of dynamic scheduling.

[0146] In the following, the time domain resource allocation currently implemented in the 3GPP technical specifications will be presented. The following explanation is to be understood as a specific exemplary embodiment of time domain resource allocation and should not be understood as the only possible time domain resource allocation. On the contrary, the present disclosure and solution are applicable in a corresponding manner to different embodiments of time domain resource allocation that may be implemented in the future. For example, although the TDRA table below is based on specific parameters (e.g., 5 parameters), time domain resource allocation can also be based on a different number of parameters and / or different parameters.

[0147] Dynamically signaling the time domain allocation for data to be received or transmitted in the DCI is useful because the portion of the timeslot available for downlink reception or uplink transmission may vary from slot to slot due to the use of dynamic TDD or the amount of resources used for uplink control signaling. The timeslot in which the transmission occurs is signaled as part of the time domain allocation. While in many cases downlink data is transmitted in the same timeslot as the corresponding resource allocation, this is typically not the case for uplink transmissions.

[0148] When a UE is scheduled to receive PDSCH or transmit PUSCH via DCI, the Time Domain Resource Allocation (TDRA) field value of the DCI indicates the row index of the Time Domain Resource Allocation (TDRA) table. The term "table" is used herein because the TDRA entries are presented as tables in the corresponding 3GPP technical specifications, but it should be interpreted as a logical, rather than restrictive, term. Specifically, the present disclosure is not limited to any specific organization, and the TDRA table can be implemented in any manner as a set of parameters associated with respective entry indices.

[0149] For example, the row of the TDRA table indexed by the DCI defines several parameters that can be used to allocate radio resources in the time domain. In this example, the TDRA table can indicate the time slot offset K0 / K2, the start and length indicator SLIV, or directly indicate the starting symbol S and the allocation length l. In addition, the TDRA table can also indicate the PDSCH mapping type and dmrs-TypeA-Position assumed in PDSCH reception, which are not directly related to the scheduled time domain radio resources. The time domain allocation field in the DCI is used as an index to the table, and the actual time domain allocation is then obtained from the table. In such an exemplary embodiment, the DCI indication of the row of the TDRA table (a value of the row index) therefore corresponds to an indication of a combination of specific values of dmrs-TypeA-Position, PDSCH mapping type, K0 value, S value and / or L value.

[0150] There is one table for uplink scheduling grants and one table for downlink scheduling assignments. For example, 16 rows can be configured, each containing:

[0151] ● Slot offset (K0, K2), which is the time slot relative to the time slot in which the DCI is acquired. Currently, downlink slot offsets from 0 to 3 are possible, while for uplink, slot offsets from 0 to 7 can be used. The slot offset may also be referred to as PDCCH (including K0 / K2)

[0152] The gap (e.g., time gap or slot gap) between the time slot of the corresponding PDSCH (as multiple time slots) scheduled by the PDCCH.

[0153] ●The first OFDM symbol in the time slot in which data is transmitted.

[0154] ● The transmission duration in number of OFDM symbols in a slot. Not all start and length combinations fit into a slot. Therefore, the start and length are jointly coded to cover only valid combinations.

[0155] • For downlink, the PDSCH mapping type (ie DMRS positioning) is also part of the table. This provides greater flexibility than indicating the mapping type separately.

[0156] It is also possible to configure slot aggregation, which repeats the transmission of the same transport block over up to 8 slots.

[0157] The current 3GPP standard TS 38.214 v16.0.0 (e.g., Section 5.1.2 for DL and Section 6.1.2 for UL) deals with time domain scheduling and provides several default tables that can be used in the above aspects, for example, when there is no RRC configuration table (e.g., pdsch-ConfigCommon or pdsch-Config in either pdsch-TimeDomainAllocationList) available at the UE. Once these fields (e.g., pdsch-AllocationList) are defined in the RRC message, the fields called time domain resource allocation (e.g., in DCI 1_0 and DCI 1_1) determine which elements are used for each PDSCH scheduling.

[0158] In the following, the default PDSCH time domain resource allocation A for a general cyclic prefix is given.

[0159] Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation for general CP A

[0160]

[0161] It is obvious from this that in practice, when downlink scheduling of the same time slot is applied, the K0 value is always assumed to be 0.

[0162] In the following, the default PUSCH time domain resource allocation A for a general cyclic prefix is given.

[0163] Table 6.1.2.1.1-2: Default PUSCH time domain resource allocation for general CP A

[0164]

[0165] It is clear from this that the value of K2 in turn depends on the parameter j, which is given in the table below.

[0166] Table 6.1.2.1.1-4: Definition of j value

[0167] <![CDATA[μ PUSCH ]]> J 0 1 1 1 2 2 3 3

[0168] The parameter μPUSCH is the subcarrier spacing configuration of PUSCH.

[0169] As is apparent from the above, the PUSCH and PDSCH TDRA tables are based on common parameters such as PUSCH mapping type, K0 / K2 values, S values, and L values. K0 is the time slot offset between the scheduled PDCCH and the scheduled PDSCH, i.e., for DL scheduling. K2 is the time slot offset between the scheduled PDCCH and the scheduled PUSCH, i.e., for UL scheduling. The S value of the TDRA table may indicate the position of the starting symbol of the scheduled resource in the relevant time slot (the time slot is the time slot in which the scheduled resource will be received / sent, given by K0 / K2). The L value of the TDRA table may indicate the length of the PDSCH / PUSCH in terms of symbols / in units of symbols and / or the length of the scheduled resource in terms of symbols / in units of symbols.

[0170] In the following, examples of RRC-configured TDRA tables for PDSCH are provided, where the parameter K0 varies between 0 and 4 slots.

[0171]

[0172] Correspondingly, the RRC-configured TDRA table allows K0 values of up to 4 time slots, effectively allowing same-time slot as well as cross-time slot scheduling (ie, DCI and corresponding resource allocation in different time slots).

[0173] In the current 5G-specific exemplary embodiment, the configured TDRA table is signaled within the PDSCH-related configuration via RRC (e.g., information element PDSCH-Config of 3GPP TS 38.331 v15.9.0), which in turn may be within an information element attached to the bandwidth part ((BWP)-downlink specific). Therefore, if the TDRA table is configured by higher layers, the TDRA table may be BWP-specific. The communication device may use a default table or may apply a TDRA table configured by higher layers (referred to as pdsch-TimeDomainAllocationList in either pdsch-ConfigCommon or pdsch-Config). However, this is just one possible example of the interaction between NR's TDRA configuration and the BWP concept. The present invention does not presuppose the adoption of a BWP and is not limited to resource allocation using a TDRA table.

[0174] Downlink Control Channel (PDCCH) monitoring

[0175] Many functions operated by a UE involve monitoring of a downlink control channel (eg, PDCCH, see 3GPP TS 38.300 v15.6.0, section 5.2.3) to receive, for example, specific control information or data destined for the UE.

[0176] A non-exhaustive list of these features is given below:

[0177] -·Paging message monitoring function,

[0178] -·System information collection function,

[0179] - Signalling monitoring operations for discontinuous DRX functionality,

[0180] - Inactive monitoring operation for discontinuous DRX functionality,

[0181] - Random access response reception for random access function,

[0182] - Reordering function of the Packet Data Convergence Protocol (PDCP) layer.

[0183] As described above, PDCCH monitoring is performed by the UE in order to identify and receive information intended for the UE, such as control information and user traffic (eg, DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0184] The control information in the downlink (which may be referred to as downlink control information, DCI) in 5G NR has the same purpose as DCI in LTE, namely as a special set of control information for scheduling downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, many different DCI formats have been defined (see TS 38.212 v15.6.0 section 7.3.1).

[0185] The above-mentioned DCI formats represent predetermined formats in which respective information is formed and transmitted. Specifically, DCI formats 0_1 and 1_1 are used for scheduling PUSCH and PDSCH, respectively, in one cell.

[0186] Each of these functions' PDCCH monitoring serves a specific purpose and is therefore initiated to achieve the aforementioned purpose. PDCCH monitoring is typically controlled based on at least one timer operated by the UE. The purpose of the timer is to control PDCCH monitoring, for example, to limit the maximum amount of time a UE monitors PDCCH. For example, a UE may not need to monitor PDCCH indefinitely, but may stop monitoring after a period of time to save power.

[0187] As mentioned above, one of the purposes of DCI on the PDCCH is to dynamically schedule resources in the downlink, uplink, or even sidelink. Specifically, several DCI formats are provided to carry an indication of the resources (resource allocation, RA) allocated to a data channel for a specific user. Resource allocations can include specifications for resources in the frequency domain and / or time domain.

[0188] Terminals and base stations

[0189] In LTE and NR, a terminal or user terminal or user equipment is called a user equipment (UE). This can be a mobile device or communication device, such as a wireless phone, a smartphone, a tablet or a USB (Universal Serial Bus) stick with user equipment functionality. However, the term mobile device is not limited to this, and generally, a relay can also have the functionality of such a mobile device, and a mobile device can also work as a relay. For example, a mobile station or mobile node or user terminal or UE is a physical entity (physical node) within a communication network. In addition, a communication device can be a communication device of any machine type, such as an IoT device. A node can have several functional entities. A functional entity refers to a software or hardware module that implements and / or supplies a predetermined set of functions to other functional entities of the same or another node or network. A node can have one or more interfaces that attach the node to a communication facility or medium through which the node can communicate. Similarly, a network entity can have a logical interface that attaches the functional entity to the communication facility or medium, through which the network entity can communicate with other functional entities or corresponding nodes.

[0190] A base station is a network node, such as one that forms part of a network used to provide services to terminals. A base station is a network node or scheduling node that provides wireless access to terminals. Communication between terminals and base stations is generally standardized. In LTE and NR, the radio interface protocol stack includes the physical layer, the media access layer (MAC), and higher layers. In the control plane, the higher-layer protocol, the Radio Resource Control (RRC), is provided. Via RRC, the base station can control terminal configuration, and the terminal can communicate with the base station to perform control tasks such as connection and bearer establishment, modification, measurements, and other functions. The terminology used in LTE is eNB (or eNodeB), while 5G NR currently uses the term gNB. The terms "base station" or "radio base station" here refer to a physical entity in a communications network. Like a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or supplies a predetermined set of functions to other functional entities in the same or another node or network. The physical entity performs some control tasks for the communications device, including one or more of scheduling and configuration. Note that base station functionality and communications device functionality can also be integrated within a single device. For example, a mobile terminal can also perform base station functions for other terminals. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB.

[0191] Professional terms

[0192] Hereinafter, a UE, a base station, and procedures will be described for the new radio access technology envisioned for 5G mobile communication systems, but they can also be used in LTE mobile communication systems. Various embodiments and variations will also be explained. The above discussions and findings contribute to the following disclosure and, for example, may be based at least in part on the above discussions and findings.

[0193] In general, it should be noted that many assumptions have been made herein in order to explain the basic principles of the present disclosure in a clear and understandable manner. However, these assumptions should be understood as examples made herein for illustrative purposes only and should not limit the scope of the present disclosure.

[0194] In addition, some of the terms used below for procedures, entities, layers, etc. are closely related to the terminology used in LTE / LTE-A systems or in the current 3GPP 5G standardization, even though the specific terminology used in the context of the new radio access technology of the next 3GPP 5G communication system has not yet been fully determined or may eventually change. Therefore, the terminology may change in the future without affecting the functionality of the embodiments. As a result, those skilled in the art will recognize that, due to the lack of newer or ultimately agreed-upon terminology, the embodiments and their scope of protection should not be limited to the specific terminology used exemplarily herein, but should be understood more broadly based on the functions and concepts that form the basis of the functions and principles of the present disclosure.

[0195] Power saving potential

[0196] The inventors have identified the potential to save power at the UE and thus increase the battery life of the UE, particularly for reduced-capability NR devices (e.g., supporting Rel. 17). Specifically, in applicable use cases (e.g., delay tolerant), UE power consumption can be saved by: i) reducing PDCCH monitoring, e.g., by having a smaller number of blind decodes and / or CCE restrictions; ii) extending DRX in RRC inactive, idle, and / or connected states; and iii) relaxing RRM for fixed devices.

[0197] A potential way to save power at the UE could be to improve PDCCH monitoring and scheduling. Specifically, for UEs with frequent traffic in RRC connected mode, PDCCH alone still represents a large portion of the UE's power consumption. Therefore, since PDCCH-only slots without PDSCH / PUSCH scheduling may account for a large portion of the total power consumption, reducing the number of PDCCH-only slots can help significantly reduce the UE's power consumption. Power consumption can also be further reduced by utilizing the above-mentioned DCI to schedule repeated transmission and / or reception of one or more (or all) TBs scheduled by the above-mentioned DCI.

[0198] Note that multi-TB scheduling may be particularly suitable / effective when certain service requirements (e.g., throughput) must be met for certain UEs / services, and when the service type is not very latency sensitive. In this case, the gNB can perform scheduling prediction, which can allow for better use of the timeslots by scheduling more than one TB in multiple upcoming timeslots in one DCI.

[0199] For UEs with reduced capabilities, coverage restoration may also be an important aspect. Data channel scheduling with duplication may benefit coverage enhancement due to certain cost / complexity reductions (e.g., reduction in Rx / Tx antennas). Multi-TB scheduling may allow for further power reduction in interaction with PDCCH monitoring reduction / adaptation, as further explained below.

[0200] Example

[0201] The present disclosure provides techniques for multi-TB scheduling with and without repetitions, which can facilitate power savings for UEs. Specifically, the present disclosure addresses signaling support and framework design for multi-TB scheduling with and without repetitions. Specifically, the present disclosure provides a framework that enables dynamic multi-TB scheduling with and without repetitions.

[0202] Since the present disclosure involves scheduling, both the scheduled device (usually a communication device / transceiver device) and the scheduling device (usually a network node) are involved. Accordingly, the present disclosure provides a base station and a user equipment. Figure 6 As shown in FIG, a user equipment 610 and a base station 660 may communicate with each other via a wireless channel in a wireless communication system. For example, the user equipment may be an NR user equipment, and the base station may be a network node or a scheduling node, such as an NR gNB (specifically, a gNB in a non-terrestrial network (NTN) NR system).

[0203] The present disclosure also provides a system including a scheduled and a scheduling device, and corresponding methods and programs. An example of such a communication system is Figure 6 The communication system 600 may be a wireless communication system according to the 5G technical specifications, specifically an NR communication system. However, the present disclosure is not limited to 3GPP NR and may also be applied to other wireless or cellular systems, such as NTN.

[0204] Figure 6 The figure shows a general, simplified and exemplary block diagram of a user equipment 610 (also referred to as a communication device) and a scheduling device 660, which is here exemplarily assumed to be located in a base station (network node) (e.g., an eNB or gNB). However, in general, in the case of a sidelink connection between two terminals, the scheduling device may also be a terminal. Furthermore, specifically with respect to the use cases of URLLC; eMBB and mMTC, the communication device 610 may also be a sensor device, a wearable device, or a connected vehicle, or a controller of an automated machine in an industrial plant. Furthermore, the communication device 610 is capable of acting as a relay between the base station 660 and another communication device (e.g., the present disclosure is not limited to a communication "terminal" or a user "terminal").

[0205] The UE and the eNB / gNB communicate with each other over a (wireless) physical channel 650 using their transceivers 620 (UE side) and 670 (base station side), respectively. The base station 660 and the terminal 610 together form a communication system 600. The communication system 600 may also include devices such as Figure 1 Other entities shown in .

[0206] like Figure 6 As shown in , in some embodiments, a user equipment (UE) 610 includes a transceiver 620 that receives downlink control information DCI signaling (also referred to as multi-TB scheduling DCI in this disclosure). The UE also includes circuits 630, 635 that obtain an indication from the DCI signaling. For example, the UE can obtain the indication from the DCI by parsing the DCI and / or extracting the above-mentioned indication from the DCI. The indication indicates the scheduling of N transport blocks TB, where N is an integer greater than 1. In addition, the indication indicates at least one of the following: i) scheduling of M repetitions of the TB, where M is equal to or greater than 1; ii) an interleaving pattern of the TB; and iii) a transmission gap between the TBs.

[0207] Likewise Figure 6 As shown in , in some embodiments, the base station 660 (or scheduling device 660) includes circuits 680 and 685. The circuits 680 and 685 generate downlink control information DCI signaling (also referred to as multi-TB scheduling DCI in this disclosure). The DCI signaling may include an indication indicating the scheduling of N transport blocks TB to the UE, where N is an integer greater than 1. In addition, the indication indicates at least one of the following: i) scheduling of M repetitions of the TB, where M is equal to or greater than 1; ii) the interleaving pattern of the TB; and iii) the transmission gap between the TBs. The base station 660 may also include a transceiver 670 that sends the DCI signaling to the UE.

[0208] The communication device 610 may include a transceiver 620 and a (processing) circuit 630, and the scheduling device 660 may include a transceiver 670 and a (processing) circuit 680. The transceiver 610 may in turn include and / or function as a receiver and / or transmitter. In other words, in the present disclosure, the term "transceiver" is used for hardware and software components that allow the communication device 610 or the respective base station 660 to send and / or receive radio signals via the wireless channel 650. Accordingly, a transceiver corresponds to a receiver, a transmitter, or a combination of a receiver and a transmitter. Generally, it is assumed that the base station and the communication device are capable of sending and receiving radio signals. However, in particular with respect to some applications of eMBB, mMTC, and URLLC (smart home, smart city, industrial automation, etc.), it is conceivable that devices such as sensors only receive signals. In addition, the term "circuitry" includes processing circuits formed by one or more processors or processing units, etc.

[0209] Circuits 630 and 680 (or processing circuits) can be one or more pieces of hardware, such as one or more processors or any LSI. There is an input / output point (or node) between the transceiver and the processing circuit, through which the processing circuit can control the transceiver, that is, control the receiver and / or transmitter and exchange receive / transmit data. As a transmitter and receiver, the transceiver may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit can perform control tasks, such as controlling the transceiver to transmit user data and control data provided by the processing circuit, and / or receiving user data and control data further processed by the processing circuit. The processing circuit can also be responsible for executing other processes, such as determination, decision, calculation, measurement, etc. The transmitter may be responsible for executing the transmission process and other related processes. The receiver may be responsible for executing the reception process and other related processes.

[0210] Corresponding to the above UE, a communication method performed by the UE is provided. Figure 7 As shown in , the method includes the step of receiving S 740 downlink control information DCI signaling (also referred to as multi-TB scheduling DCI in the present disclosure). In addition, the method includes the step of obtaining S750 an indication from the DCI signaling. For example, the indication can be obtained from the DCI by parsing the DCI and / or extracting the above indication from the DCI. The indication indicates the scheduling of N transport blocks TB, where N is an integer greater than 1. In addition, the indication indicates at least one of the following: scheduling of M repetitions of TB, where M is equal to or greater than 1; an interleaving pattern of the TB; and a transmission gap between TBs. As Figure 7 As further shown in , according to the scheduling of DCI / PDCCH, the UE may send S760 and / or receive the transport block scheduled by S760.

[0211] In addition, corresponding to the above-mentioned base station, a communication method performed by the base station is provided. Figure 7 As shown in , the method includes the step of generating S720 downlink control information DCI signaling (also referred to as multi-TB scheduling DCI in this disclosure). The DCI signaling includes an indication of the scheduling of N transport blocks TB to the user equipment UE, where N is an integer greater than 1. In addition, the indication indicates at least one of the following: i) the scheduling of M repetitions of the TB, where M is equal to or greater than 1; ii) the interleaving pattern of the TB; and iii) the transmission gap between the TBs. Finally, the method includes the step of sending S730 DCI signaling to the UE. Figure 7 As further shown in FIG, according to the scheduling of the DCI / PDCCH, the base station may receive S770 and / or send the transport block scheduled by S770.

[0212] like Figure 7 As illustrated in FIG, the base station method may further perform step S710, and the method for the base station may include the above-mentioned step S710. In step 710, which is performed before generating the multi-TB scheduling DCI in step S720, the base station performs allocation / scheduling of time domain resources for transmission and / or reception of N transport blocks. The scheduling may include the step of determining a scheduling step for indicating multiple (e.g., N>1) TBs to one or more UEs. Step 710 may generally be performed in conjunction with the scheduling of other transmission / reception resources for other UEs and taking into account the traffic conditions and quality of service requirements used by the one or more UEs.

[0213] It is also noted that any steps / operations described below may be performed or controlled by circuit 630 (on the UE side) and / or circuit 680 (on the base station side).

[0214] In the further description, the details and embodiments apply to each of the transceiver device, the scheduling device (or scheduling node), and the method, unless explicitly stated or the context indicates otherwise.

[0215] Multi-TB scheduling DCI

[0216] Generally speaking, a DCI can schedule multiple TBs. In other words, multi-TB transmissions, with or without duplication, are scheduled by a (single or one) DCI. This type of DCI is hereinafter referred to as multi-TB scheduling DCI. More specifically, a multi-TB scheduling DCI indicates the scheduling of multiple TBs (for the same UE). Similarly, the term "multi-TB scheduling" refers to scheduling multiple TBs to the same UE using a single (or one) DCI.

[0217] In general, the multi-TB scheduling DCI can further indicate to the above UE at least one of the following (one, two, three or even all four): i) the number of TBs N, ii) the number of repetitions M of TBs, iii) the transmission gap, and iv) the interleaving pattern.

[0218] In other words, the multi-TB scheduling DCI may include: i) an indication indicating the number of TBs N, ii) an indication indicating the number of TB repetitions M, iii) an indication indicating a transmission gap, and iv) an indication indicating an interleaving pattern. Note that the indication of the number of TBs N may implicitly indicate the scheduling of N TBs, and the indication of M repetitions may implicitly indicate the scheduling of M repetitions of the TB. More specifically, the indication of the number N in the multi-TB scheduling DCI may also indicate the scheduling of N TBs. In other words, the indication of the number N may be considered as a joint indication of the scheduling of the number N and N TBs. Similarly, the indication of the number M in the multi-TB scheduling DCI may also indicate the scheduling of M repetitions. In other words, the indication of the number M may be considered as a joint indication of the scheduling of the number M and M repetitions. Also note that the interleaving pattern may implicitly indicate the scheduling of N TBs, or the scheduling of M TB repetitions, or both.

[0219] In general, the indication indicating the scheduling of N TBs may jointly indicate the scheduling of N TBs and at least one of: ii) the scheduling of M repetitions; iii) the interleaving pattern; and iv) the transmission gap. Such joint indication may reduce overhead.

[0220] Multi-TB scheduling DCI scheduling

[0221] Generally speaking, the indication indicating the scheduling of N TBs may include an indication of the number N. In other words, the multi-TB scheduling DCI may generally include an indication of the number N of scheduled TBs. The indication of the number N may be explicit or implicit.

[0222] However, the present invention is not limited to this. That is, the scheduling of N TBs by a multi-TB scheduling DCI does not require that the multi-TB scheduling DCI include an explicit indication of the number N of scheduled TBs. In other words, the multi-TB scheduling DCI may or may not include an indication of the number N of scheduled TBs. For example, in some embodiments, the UE (e.g., its transceiver) receives radio resource control (RRC) signaling. In these embodiments, the UE (e.g., its processing circuitry) then obtains the indication of the number N of TBs from the received RRC signaling.

[0223] Likewise, an indication indicating scheduling of M repetitions of a TB may typically include an indication of the number M. In other words, a multi-TB scheduling DCI may typically include an indication of the number of repetitions M. The indication of the number of repetitions M may be explicit or implicit.

[0224] However, the present invention is not limited thereto. That is, the scheduling of M repetitions by a multi-TB scheduling DCI does not require that the multi-TB scheduling DCI include an explicit indication of the number M of scheduled TBs. In other words, the multi-TB scheduling DCI scheduling TB repetitions may or may not include an indication of the number M of repetitions of the scheduled TBs. Similar to the number N of TBs, the number M of repetitions may be indicated via RRC.

[0225] Typically, some multi-TB scheduling DCIs may explicitly indicate N and / or M, while for other multi-TB scheduling DCIs, it is implicitly understood that the current values of N and / or M apply (the last value of N / M is explicitly indicated by the multi-TB scheduling DCI). Alternatively or in addition, N and / or M may be configured via RRC, and the multi-TB scheduling DCI may indicate the scheduling of N transport blocks (and M repetitions, if applicable) simply by triggering (e.g., a one-bit field in the DCI). That is, the number of transport blocks N, the number of repetitions M, the interleaving pattern, and the transmission gap may be indicated by other means, such as by configuration via RRC.

[0226] In addition, multi-TB scheduling DCI can usually send / re-schedule resources for scheduling multiple TBs. It should also be noted that the scheduling of resources can be based on time slots (such as Figures 8a to 8d as well as Figure 9 ) or non-slot-based. In other words, the multi-TB scheduling DCI can be slot-based multi-TB scheduling, or it can be non-slot-based multi-TB scheduling. More specifically, slot-based scheduling refers to the scheduling of resources, in which all transmissions / repetitions of a TB are scheduled with a granularity of a slot. In other words, for each scheduled TB transmission / repetition, all time domain resources of one or more respective slots are used (for example, each transmission / repetition uses one or more entire / complete slots). On the other hand, non-slot-based scheduling refers to scheduling of time domain resources for a TB or its repetitions that is less than one slot, such as 1, 2, or several OFDM symbols. Specifically, non-slot-based scheduling can schedule multiple transmissions / repetitions of a TB in the same slot.

[0227] It should also be noted that in this disclosure, statements such as "DCI scheduling," "DCI indicating scheduling," and "DCI including an indication indicating scheduling" may be used interchangeably. Furthermore, statements such as "scheduling transmission of multiple TBs," "scheduling transmission and / or reception of multiple TBs," and "scheduling multiple TBs" may be used interchangeably.

[0228] Also note that the scheduling of N TBs (and M repetitions, if applicable) can be scheduling of transmissions in the uplink (UL, such as PUSCH) or downlink (DL, such as PDSCH). In other words, the TBs scheduled by the multi-TB scheduling DCI can be scheduled for transmission or reception by the UE (and, correspondingly, for reception or transmission by the base station). In other words, unless explicitly stated otherwise, the term "transmission" refers to transmission by the UE or transmission by the base station, and the term "reception" refers to reception by the UE or reception by the base station.

[0229] In addition, it is noted that the resources to be used for scheduling the transmission / reception of N TBs (and M repetitions, if applicable) may or may not be indicated (explicitly or implicitly) by the above-mentioned multi-TB scheduling DCI. For example, using the SPS / CG framework, the above-mentioned resources can be indicated via RRC.

[0230] Transport Block (TB) and Repetition

[0231] Typically, N TBs may carry mutually different data.

[0232] Note that the term "transport block" may also be replaced by the term "codeword", specifically as used, for example, in the context of MIMO. More specifically, the term codeword is currently commonly used in MIMO to describe one or more codewords, each of which may be scheduled and then mapped to one or more / multiple spatial layers. As far as channel coding and modulation are concerned, the operation is indistinguishable for transport blocks and codewords as far as the present invention is concerned. In other words, the present disclosure also enables the scheduling of multiple codewords by providing a multi-codeword scheduling DCI that works in a similar manner to the multi-TB scheduling DCI (the term "transport block" is replaced by the term "codeword").

[0233] Typically, each of the M repetitions can carry the same data as the corresponding TB in the N TBs. In other words, each of the M repetitions can correspond to one of the N TBs scheduled by the multi-TB scheduling DCI. The TB and the repetition corresponding to the above TB can typically carry the same data. However, the TB and the corresponding repetition are not necessarily exactly the same. For example, the above-mentioned same data can be encoded differently in the TB and the corresponding repetition. That is, the repetition of the TB can be a different redundancy version (RV) of the above-mentioned TB. Typically, M can be a number greater than or equal to 1, where the number of repetitions M of 1 can mean / indicate that (only) one transmission is scheduled for one TB, or can mean / indicate that (only) one transmission of each TB is scheduled (i.e., the first transmission of each TB is counted as one of the repetitions of the above-mentioned TB). In other words, M=1 can indicate that no repetition is scheduled. In other words, the terms "transmission" and "repetition" can be used interchangeably here. It should also be noted that in the present disclosure, the term "further repetition" refers to (one or more) transmissions of a TB in addition to the first transmission of the TB.

[0234] It should also be noted that the number of repetitions, M, may be the total number of repetitions / transmissions scheduled by the multi-TB scheduling DCI. However, the present invention is not limited to this, as the multi-TB scheduling DCI may schedule M repetitions for each of the N scheduled transport blocks (for a total of N times M repetitions). Alternatively, the DCI may schedule M repetitions for only one (e.g., the first) or some TBs (every second, etc.), and may transmit other TBs only once. In general, the multi-TB scheduling DCI may indicate a different number of repetitions for each scheduled TB.

[0235] It should also be noted that the repetitions and transmissions mentioned in the present disclosure may be nominal repetitions / transmissions or actual repetitions / transmissions. Nominal repetitions and actual repetitions are concepts introduced in Rel.16NR for PUSCH repetition type B, which are explained in detail in TS38.214, Sec 6.1.2.1. More specifically, nominal repetitions / transmissions are configured / scheduled / indicated as intended repetitions / transmissions based on configured / scheduled / indicated resources. However, typically, some OFDM symbols assigned to nominal repetitions may be invalid and / or the nominal repetitions may cross the boundaries of the time slot, which may destroy the above-mentioned nominal repetitions. Accordingly, the nominal repetitions / transmissions may be further divided by the time slot boundaries or invalid OFDM symbols, and then therefore consist of one or more actual repetitions.

[0236] The indication in the multi-TB scheduling DCI can be an explicit indication (e.g., a bit field in the DCI for indicating the number N of TBs and / or the number M of repetitions), or, for example, a joint indication with an entry in, for example, a TDRA table (such a TDRA table can contain multiple entries specifying different combinations of TBs and numbers of repetitions).

[0237] Sending gap

[0238] Typically, a multi-TB scheduling DCI may indicate (e.g., include) a transmission gap. Here, a transmission gap refers to the gap in time (e.g., measured in time slots or OFDM symbols) between consecutive transmissions and / or further repetitions of a TB. In other words, a transmission gap refers to the time period (resources in the time domain) between two consecutive transmissions. Two consecutive transmissions / repetitions are two transmissions / repetitions between which the multi-TB scheduling DCI does not schedule another transmission / repetition of one of the N scheduled TBs.

[0239] Now refer to Figure 8c and Figure 8d Explain this further.

[0240] Specifically, Figure 8c An example of scheduling multiple TBs without sending gaps is shown. Figure 8c In the first time slot of a LTE-LTE, a PDCCH containing a multi-TB scheduling DCI is transmitted by the base station and / or received by the UE. This multi-TB scheduling DCI schedules four TBs in the third through sixth time slots, respectively. In other words, the multi-TB scheduling DCI schedules four TBs, with no transmission gaps between the four scheduled TBs. In other words, the four TBs are scheduled for transmission in immediately consecutive time slots.

[0241] Figure 8d An example of scheduling of multiple TBs with transmission gaps is shown. Figure 8c As shown in FIG, multi-TB scheduling DCI is transmitted in the first time slot. Specifically, starting from the third time slot, four TBs are scheduled every other time slot. That is, the first to fourth TBs are scheduled for transmission in time slots #3, #5, #7, and #9, respectively. In other words, four TBs are scheduled to be transmitted in one time slot between consecutive TBs.

[0242] Also note that, in general, different / multiple transmission gaps may be indicated by a multi-TB scheduling DCI. For example, a first transmission gap may apply to two consecutive first transmissions of a TB, a second gap may apply to two consecutive further repetitions, a third gap may apply to the first transmission and consecutive further repetitions of a TB, and / or a fourth gap may apply to further repetitions and consecutive transmissions of a TB.

[0243] Interleaved Mode

[0244] Typically, the interleaving pattern used to interleave two or more TBs scheduled by a multi-TB scheduling DCI can be selected from a set of predefined and / or predetermined interleaving patterns. In other words, one (e.g., which one) of the multiple predefined and / or predetermined interleaving patterns can be indicated by the multi-TB scheduling DCI. For example, these interleaving patterns can be configured via RRC signaling or defined in the standard.

[0245] The number of TBs (N) and / or the number of repetitions (M) can be implicitly indicated by the interleaving pattern. In other words, each interleaving pattern can be associated with N TBs and / or M repetitions. That is, by indicating the interleaving pattern, the multi-TB scheduling DCI implicitly indicates the associated number of TBs (N) and / or the associated number of repetitions (M). Similarly, the transmission gap can be fixed by the interleaving pattern, i.e., the interleaving pattern can be associated with a specific transmission gap. These associations can generally be fixed or dynamic, for example, configurable via RRC.

[0246] However, the present invention is not limited thereto. Typically, a multi-TB scheduling DCI may include an explicit indication of a transmission gap, which may be determined and set by the base station independently of the interleaving pattern indicated in the DCI, thereby increasing scheduling flexibility. The indication may be an explicit indication (e.g., a bit field in the DCI for indicating the gap), or a joint indication of, for example, the interleaving pattern, by reference to an entry in a TDRA table (such a TDRA table may contain multiple entries specifying the same interleaving pattern for different transmission gaps) and, for example, the interleaving pattern.

[0247] Typically, the interleaving mode may be selected from, but not limited to, two or more predefined interleaving modes, such as the TB priority mode and the RV priority mode described further below. In other words, the indication indicating interleaving in the multi-TB scheduling DCI may indicate which of the two or more predefined interleaving modes will be used for the scheduled TB (and the scheduled further repetitions, if applicable).

[0248] Now refer to Figures 8a to 8d Some exemplary interleaving patterns are described.

[0249] Figure 8a TB scheduling with repetition according to "TB priority mode" is shown, according to which the transmission of TBs (including repetitions) is not interleaved. That is, Figure 8a The figure shows the interleaving pattern of trivial interleaving of TB. The TB priority interleaving pattern can be schematically written as

[0250] {TB0_RV0,TB0_RV2,TB0_RV3,TB0_RV1,TB1_RV0,TB1_RV2,TB1_RV3,

[0251] TB1_RV1},

[0252] The expression before "_" indicates the transport block, and the expression after "_" indicates the redundancy version. More specifically, Figure 8a As shown in , the transmission of two TBs is scheduled by a multi-TB scheduling DCI. In addition, for each of the above two TBs, 4 repetitions are scheduled. Therefore, each of the two scheduled TBs is transmitted four times (and may be encoded differently in the above four times). The transmission of the first TB is first scheduled in time slots three to six. Specifically, a "0" redundant version is transmitted in the third time slot, a "2" redundant version is transmitted in the fourth time slot, a "3" redundant version is transmitted in the fifth time slot, and a "1" redundant version is transmitted in the third time slot. Figure 8a In the example shown in , there is a transmission gap of one time slot after the first TB is transmitted. After the transmission of the first TB and the transmission gap, the transmission of the second TB is scheduled in time slots 8 to 11. The redundant versions of the second TB are transmitted in the same order as the redundant versions of the first TB.

[0253] Typically, in TB-priority mode, transmissions (including repetitions) of TBs may be performed continuously (e.g., in consecutive time slots), i.e., without another scheduled transmission / repetition of a TB in between. Typically, there may or may not be transmission gaps between TB transmissions. Furthermore, there may or may not be transmission gaps between the last transmission of one TB and the first transmission of another TB. Some or all of these transmission gaps may be identical or different from one another.

[0254] TB priority mode can allow high reliability and low latency for the first TB to be sent. Utilizing the TB priority option can be particularly beneficial if the first TB has significantly higher priority and performance requirements than the second TB (and other TBs, if applicable).

[0255] Figure 8b FIG2 shows a TB scheduling with repetition according to the “RV priority mode”, according to which the transmission of TBs (including repetitions) is interleaved. The TB priority interleaving mode can be schematically written as {TB0_RV0,TB1_RV0,TB0_RV2,TB1_RV2,TB0_RV3,TB1_RV3,TB0_RV1,

[0256] TB1_RV1}.

[0257] More specifically, Figure 8bAs shown in , the transmission of two TBs is scheduled by a multi-TB scheduling DCI. In addition, for each of the two TBs, four repetitions are scheduled. Therefore, each of the two scheduled TBs is transmitted four times (possibly encoded differently in the four times).

[0258] Starting from the third time slot (time slots #3, #5, #7, and #9), the transmission of the first TB is scheduled in every other time slot. The transmission of the second TB is scheduled in every other time slot starting from the fourth time slot (time slots #4, #6, #8, and #10). In other words, the transmission of the first and second time slots is interleaved.

[0259] In the first transmission of each TB (in time slots #3 and #4), the "0" redundant version of the respective TB is transmitted; in the second transmission of each TB, i.e., the first further repetition, the "2" redundant version of the respective TB is transmitted (in time slots #5 and #6); in the third transmission of each TB (in time slots #7 and #8), the "3" redundant version of the respective TB is transmitted; and, in the fourth transmission of each TB (in time slots #9 and #10), the "1" redundant version of the respective TB is transmitted. Figure 8b In the example shown in , the TB and further repetitions are sent with no gaps between them.

[0260] Typically, in RV-first mode, between two transmissions of a TB, there may be (eg, one) transmission of each other scheduled TB. Redundancy versions of different TBs may be transmitted in the same order (which may be specified by the RV-first mode).

[0261] RV priority mode can allow for increased time diversity, which can allow for improved reliability, especially in situations where frequency diversity is low. Typically, in RV priority mode, transmission / repetition of TBs can be performed continuously (e.g., in consecutive time slots), i.e., there are no gaps between transmissions / repetitions. However, there may also be gaps between transmissions / repetitions, which can further increase time diversity.

[0262] Figure 8c and Figure 8d Other examples of non-repetitive interleaving patterns are shown, where TBs are scheduled without gaps and with gaps, respectively. They have been explained above when illustrating the transmission gaps between TBs.

[0263] Note also that time domain interleaving can also be used for interleaved multiple access (IDMA) to increase capacity.

[0264] Combined Instructions and TDRA Form

[0265] Typically, a multi-TB scheduling DCI may jointly indicate to the UE one, more, or all of the following: i) the number of TBs, ii) the number of repetitions, iii) the transmission gap, and iv) the interleaving pattern. In other words, the indication in the multi-TB scheduling DCI may be a joint indication of the scheduling of N TBs and one or more of the previous points i) through iv).

[0266] For example, such a joint indication may be a parameter in the DCI or a field in the DCI. The joint indication may also be a reference to an entry in the time domain resource allocation TDRA table. Specifically, the joint indication may be an indication of an index (e.g., a row index) of an entry (e.g., a row) in the TDRA table. In other words, the joint indication may be indicated by a TDRA table to which columns corresponding to one or more of the above parameters i) to vi) have been added. In other words, the TDRA table signaling framework may be enhanced to support multi-TB scheduling, for example, by extending the existing TDRA table with additional entries / rows / columns.

[0267] An exemplary TDRA table for multi-TB scheduling is shown below.

[0268]

[0269] As illustrated in the above exemplary table, the TDRA table for multi-TB scheduling may include (corresponding to the last four rows in the above exemplary table, respectively):

[0270] i) a row specifying or indicating the number N of TBs for one or more (or even each) row index;

[0271] ii) specifying or indicating for one or more (or even each) row index the row to be repeated a number of times M;

[0272] iii) specifying or indicating for one or more (or even each) row index the row in which the gap is to be sent; and / or

[0273] iv) One or more (or even each) row index specifies or indicates a row of an interleaving pattern.

[0274] In other words, for each row index, one or more parameters mentioned in points i) to iv) above can be defined. If a row does not (explicitly) specify a row index (in the example table above, corresponding to the "NA" entries in the last four rows), a predefined or default value can be used. For example, some interleaving patterns may be associated with a default transmission gap.

[0275] Specifically, the row index may be indicated by an indication in the multi-DCI scheduling DCI. That is, the row index may be a joint indication in the multi-DCI scheduling DCI indicating the scheduling of N TBs and one or more of parameters i) to iv).

[0276] The use of joint indication of multiple parameters (e.g., number of TBs, number of repetitions M, interleaving pattern, and transmission gap) can facilitate scheduling of multiple TBs with no or minimal additional DCI overhead. In addition, joint indication based on, for example, a TDRA table can allow flexible allocation of time / frequency domain resources for transmission / reception of multiple TBs through a single DCI.

[0277] Also note that the TDRA tables supporting multi-TB scheduling can be configured / associated with a certain search space (SS) set or bandwidth part (BWP). That is, there may be one or more TDRA tables supporting multi-TB scheduling and one or more TDRA tables not supporting multi-TB scheduling.

[0278] Configured Grant (CG) and Semi-Persistent Scheduling (SPS) framework

[0279] Typically, a UE (e.g., a processing circuit thereof) may obtain an indication of activating configured grant (CG) or semi-persistent scheduling (SPS) from a multi-TB scheduling DCI. For example, an indication indicating the scheduling of N TBs may be an indication of activating CG / SPS. After obtaining an indication of activating CG / SPS, the circuit may activate CG or SPS according to the above indication. CG or SPS may indicate multiple transmission opportunities. The circuit may deactivate CG or SPS after N transmission opportunities starting from receiving the above-mentioned multi-TB scheduling DCI. Note that SPS and CG (specifically "type 2" CG) may be used to implement multi-TB scheduling in DL and UL, respectively.

[0280] That is, CG / SPS can be enhanced to enable multi-TB scheduling with or without repetition. Specifically, in this case, the multi-TB scheduling DCI can be just a trigger (e.g., a one-bit field in the multi-TB scheduling DCI). That is, the number of transport blocks N, the number of repetitions M, the interleaving pattern and the transmission gap can be indicated by other means, for example, they can be signaled through CG / SPS in an RRC configuration. However, the present invention is not limited to this, because the interleaving pattern and / or the transmission gap may or may not be indicated by the multi-TB scheduling DCI that activates CG / SPS.

[0281] Typically, multiple transmission opportunities (e.g., time resources) can be configured by RRC (e.g., using the CG / SPS framework). A portion of the multiple transmission opportunities can be selected by the control information of the CG / SPS triggered DCI. The remaining portion of the multiple transmission opportunities is released. For example, the CG / SPSDCI may include an explicit indication of the transmission opportunities to be selected from the configured transmission opportunities for the transmission / reception of the scheduled TBs (and further repetitions, if applicable). If there is only a trigger flag in the CG / SPSDCI, the number N of scheduled TBs and / or the number of transmission opportunities can be configured via RRC for the triggered CG / SPS configuration.

[0282] The number of transport blocks N indicated by the DCI triggered by CG / SPS

[0283] Typically, the number of TBs N may be indicated in the DCI triggering / activating the CG / SPS. That is, the control information of the multi-TB scheduling DCI (e.g., an indication indicating the scheduling of N TBs) may be or include the number of TBs N. In this case, the UE may automatically release the CG / SPS after N transmission opportunities or after N actual transmissions of the TBs. Alternatively, the UE may automatically release the CG / SPS after a number of transmission opportunities equal to / corresponding to the number of scheduled transmissions including repetitions, or after actually transmitting / receiving scheduled TBs including repetitions. Specifically, the UE / base station may not use all transmissions / repetitions scheduled by the DCI triggering / activating the CG / SPS to actually transmit the TBs / repetitions. The number of transport blocks N indicated / configured by the RRC

[0284] Typically, as described above, the number N of transport blocks may be indicated via RRC.

[0285] Specifically, in a certain CG / SPS configuration, the number N of TBs or timers can be configured by RRC. In the case of using a timer, the timer can (for example) start from the transmission of the first TB, or alternatively, can start from the transmission of multi-DCI scheduled DCI. If the CG / SPS configuration is triggered, it will automatically release / terminate the periodic transmission after the timer expires or the number of TBs transmitted. In other words, multiple CG / SPS configurations can be configured, and the CG / SPS that triggers the DCI can explicitly or implicitly indicate one of the configured CG / SPS configurations. For example, the CG / SPS that triggers the DCI can trigger the CG / SPS, whose time domain resources include the time slot in which the CG / SPS that triggers the DCI is sent. As a further example, if more than one CG / SPS configuration includes a time slot in which a CG / SPS triggering DCI is sent, the CG / SPS with a lower index or higher priority will be triggered. For example, the index and / or priority can be RRC configured in the CG / SPS configuration.

[0286] Figure 9 The figure shows the automatic release when scheduling multiple TBs using the CG / SPS framework. Note that the interleaving pattern, transmission gap, and number N and M are the same as Figure 8a Therefore, the same description will not be repeated. Figure 9 As shown in , the CG / SPS is automatically released / deactivated after the last scheduled transmission of a TB (including scheduled repetitions). That is, after sending the "1" redundant version of the second TB (i.e., after time slot #11, #1 is the time slot in which the CG / SPS that triggered the DCI was sent).

[0287] Using CG / SPS to schedule multiple TBs with a single DCI may be a simple and effective solution because it uses the existing SPS / CG framework. Specifically, this approach can reduce the number of parameters that must be introduced into the standard, thus having less impact on the specification. In addition, compared to the current SPS / CG framework, using CG / SPS for multi-TB scheduling can enable the gNB to complete the scheduling of multiple TBs by using only one DCI, rather than by using two DCIs (one for activating and one for deactivating SPS / CG). This can allow the UE to not monitor the PDCCH for SPS / CG deactivation, which can further save PDCCH monitoring power consumption.

[0288] In general, a physical downlink control channel PDCCH monitoring UE operation may be adapted according to the number N of TBs scheduled by DCI.

[0289] In general, multi-TB scheduling can allow for further power savings by adapting accordingly. More specifically, multi-TB scheduling can allow for scheduling the same number of resources and / or TBs with fewer DCIs. Therefore, as more resources are scheduled to a UE at once, PDCCH monitoring can be adapted to multi-TB scheduling. This adaptation of PDCCH monitoring operations / behavior can help further reduce the UE's own power consumption, but can also be used to provide more scheduling opportunities for other UEs.

[0290] For example, multiple parameter sets of "monitoringSlotPeriodicityAndOffset" and "monitoringSymbolsWithinSlot" can be configured. On the other hand, a single-TB scheduling DCI can trigger the UE to switch to the PDCCH monitoring timing specified by the first parameter set; and a multi-TB scheduling DCI can trigger the UE to switch to the PDCCH monitoring timing specified by the second parameter set. If the UE is already using the first parameter set when receiving the single-TB scheduling DCI, it can continue to use the first parameter set. Similarly, if the UE is already using the second parameter set when receiving the multi-TB scheduling DCI, it can continue to use the second parameter set.

[0291] In other words, when receiving single-TB scheduling DCI and / or when receiving multi-TB scheduling DCI, the UE can re-evaluate which of the two or more parameter sets it should use, or more generally, re-evaluate its PDCCH monitoring behavior. Typically, one or both of the multi-TB scheduling DCI and the single-TB scheduling DCI can trigger parameter set adaptation / re-evaluation.

[0292] In other words, when a UE receives DCI, it (or its processing circuitry) can determine whether to change its PDCCH monitoring operation. This decision can be based on whether the DCI is single-TB scheduling DCI or multi-TB scheduling DCI. However, this decision can depend on (e.g., take into account) further criteria such as battery status, expected traffic volume, etc.

[0293] For example, if the above-mentioned DCI is a single TB scheduling DCI, the UE may determine to monitor the first PDCCH candidate set. On the other hand, if the above-mentioned DCI is a multi-TB scheduling DCI, the UE may determine to monitor the second PDCCH candidate set. In other words, the UE may determine whether to monitor the first PDCCH candidate set or the second PDCCH candidate set. The second PDCCH candidate set may be smaller than the first PDCCH candidate set. Alternatively or additionally, when the above-mentioned DCI is a multi-TB scheduling DCI, the UE may determine to monitor its PDCCH less frequently than when the above-mentioned DCI is a single TB scheduling DCI. The UE may monitor a reduced number of PDCCH candidates, or perform monitoring at a lower frequency within a predetermined time period, and / or perform monitoring at a lower frequency until another DCI is received (specifically, until a single TB scheduling DCI is received). Specifically, when a multi-TB scheduling DCI is received, the UE may even determine to completely stop PDDCH monitoring within a predetermined time period.

[0294] It should also be noted that the embodiments of the present disclosure are also applicable and beneficial to relatively long round-trip time (RTT) scenarios, such as non-terrestrial networks (NTN) above 52.6 GHz, where the number of HARQ process IDs is small compared to the RTT, that is

[0295] slot_length x "the number of HARQ process IDs" < RTT, because a single DCI can schedule multiple time slots with a single HARQ process ID.

[0296] Further aspect

[0297] According to a first aspect, a user equipment UE is provided. The UE includes a transceiver and a circuit. The transceiver receives downlink control information DCI signaling. The circuit obtains an indication from the DCI signaling. The indication indicates the scheduling of N transport blocks TB, where N is an integer greater than 1; and at least one of the following: i) the scheduling of M repetitions of the TB, where M is equal to or greater than 1; ii) the interleaving pattern of the TB; and iii) the transmission gap between the TBs.

[0298] According to a second aspect provided in addition to the first aspect, the N TBs carry mutually different data, and / or each of the M repetitions carries the same data as the corresponding TB among the N TBs. [[ID=

[13]

[0299] According to a third aspect provided in addition to the first or second aspect, the indication indicating the scheduling of the N TBs can jointly indicate the scheduling of the N TBs and at least one of the following: i) the scheduling of the M repetitions; ii) the interleaving pattern; and iii) the transmission gap.

[0300] According to a fourth aspect provided in addition to the third aspect, the joint indication can be one of the following: i) a parameter in the DCI or a field in the DCI; and ii) a reference to an entry in a time domain resource allocation TDRA table.

[0301] According to a fifth aspect provided in addition to one of the first to fourth aspects, the indication indicating the scheduling of the N TBs can include an indication of the quantity N.

[0302] According to a sixth aspect provided in addition to one of the first to fifth aspects, the transceiver receives radio resource control RRC signaling; and the circuit obtains an indication indicating the quantity N of the TBs from the RRC signaling.

[0303] According to a seventh aspect provided in addition to one of the fifth or sixth aspects, when the circuit obtains an indication of an activated configured grant CG or semi-persistent scheduling SPS from the DCI, where the CG or SPS indicates multiple transmission opportunities, the circuit deactivates the CG or SPS after N transmission opportunities starting from receiving the DCI.

[0304] According to an eighth aspect provided in addition to one of the first to seventh aspects, when the transceiver receives DCI, the circuit adapts a physical downlink control channel PDCCH to monitor an operation of the UE according to the number N of TBs scheduled by the DCI.

[0305] According to a ninth aspect, a scheduling device is provided. The scheduling device includes circuitry and a transceiver. The circuitry generates downlink control information (DCI) signaling, where the DCI signaling includes an indication indicating to a user equipment (UE) the scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of the following: i) scheduling of M repetitions of the TBs, where M is equal to or greater than 1; ii) an interleaving pattern for the TBs; and iii) a transmission gap between the TBs. The transceiver transmits the DCI signaling to the UE.

[0306] According to a tenth aspect, a method for a user equipment (UE) is provided. The method includes the steps of receiving downlink control information (DCI) signaling and obtaining an indication from the DCI signaling. The indication indicates a schedule of N transport blocks (TBs), where N is an integer greater than 1, and at least one of: i) a schedule of M repetitions of the TBs, where M is equal to or greater than 1; ii) an interleaving pattern of the TBs; and iii) a transmission gap between the TBs.

[0307] According to an eleventh aspect, a method for scheduling a device is provided. The method includes generating downlink control information (DCI) signaling and transmitting the DCI signaling to a user equipment (UE). The DCI signaling includes an indication indicating to the UE the scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of: i) scheduling of M repetitions of the TBs, where M is equal to or greater than 1; ii) an interleaving pattern for the TBs; and iii) a transmission gap between the TBs.

[0308] Hardware and software implementations of the present disclosure

[0309] The present disclosure can be implemented by software, hardware, or a combination of software and hardware. Each functional block used in the description of each of the above embodiments can be partially or completely implemented by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSIs. The LSI can be formed by a chip alone, or a chip can be formed to include some or all functional blocks. The LSI can include data inputs and outputs coupled thereto. Depending on the degree of integration, the LSI here can be referred to as an IC, a system LSI, a super LSI, or an ultra LSI. However, the technology for implementing the integrated circuit is not limited to the LSI and can be implemented by using a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after manufacturing the LSI, or a reconfigurable processor in which the connections and settings of the circuit units placed in the LSI can be reconfigured, can be used. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces the LSI due to advances in semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate the functional blocks. Biotechnology can also be applied.

[0310] The present disclosure may be implemented by any type of device, apparatus, or system having a communication function, which is referred to as a communication device.

[0311] The communication device may include a transceiver and processing / control circuits. The transceiver may include and / or function as a receiver and a transmitter. As a transmitter and a receiver, the transceiver may include an RF (radio frequency) module including an amplifier, an RF modulator / demodulator, etc., and one or more antennas.

[0312] Some non-limiting examples of such communication devices include phones (e.g., cellular (mobile) phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital cameras / camcorders), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

[0313] Communication devices are not limited to portable or movable, and may also include any kind of non-portable or fixed apparatus, equipment, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other “things” in an “Internet of Things (IoT)” network.

[0314] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.

[0315] The communication apparatus may include a device, such as a controller or sensor, coupled to a communication device that performs the communication functions described in the present disclosure. For example, the communication apparatus may include a controller or sensor that generates control signals or data signals used by the communication device that performs the communication functions of the communication apparatus.

[0316] Communication devices may also include infrastructure such as base stations, access points, and any other devices, equipment, or systems that communicate with or control devices such as the non-limiting examples above.

[0317] In addition, various embodiments may also be implemented as software modules that are executed by a processor or directly in hardware. A combination of software modules and hardware is also possible. The software modules may be stored on any type of computer-readable storage medium. Specifically, according to another embodiment, a non-transitory computer-readable recording medium is provided. The recording medium stores a program that, when executed by one or more processors, causes the one or more processors to perform the steps of the method according to the present disclosure.

[0318] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, flash memory or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Similarly, any connection is properly referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves are used to send instructions from a website, server or other remote source, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals or other temporary media, but rather point to non-temporary tangible storage media. Disks and optical disks used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and blue-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media.

[0319] It should also be noted that individual features of different embodiments may be used individually or in any combination to form the subject of another embodiment. Those skilled in the art will appreciate that various variations and / or modifications may be made to the present disclosure as shown in the specific embodiments. Therefore, the embodiments presented are to be considered in all respects as illustrative and not restrictive.

Claims

1. A communication device, comprising: A transceiver, receiving downlink control information DCI; and circuitry, obtaining an indication referencing an entry of a time domain resource allocation TDRA table from the DCI, The data quantity N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

2. The communication device according to claim 1, wherein The communication determines, based on the indication, at least one of: the number of repetitions of the data, M, where M is equal to or greater than 1; and The time slot offset for data transmission.

3. The communication device according to claim 2, wherein: The indication jointly indicates N data and at least one of the following: M repetitions; and The time slot offset for data transmission. The communication device according to claim 1 , wherein The transceiver receives an indication including a data quantity N from radio resource control RRC signaling. The communication device according to claim 1 , wherein: The circuit monitors a physical downlink control channel (PDCCH) according to the amount N of data.

6. A scheduling device comprising: A circuit generates downlink control information (DCI), wherein the DCI includes an indication referencing an entry of a time domain resource allocation (TDRA) table, wherein the number of data N is associated with the number of entries included in the TDRA table, N being an integer greater than 1; and The transceiver sends the DCI to the communication device.

7. A method for a communication device, the method comprising the steps of: receiving downlink control information DCI; as well as Obtaining an indication of an entry referencing a time domain resource allocation TDRA table from the DCI, The data quantity N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

8. A method for scheduling equipment, the method comprising the following steps: generating downlink control information DCI, wherein the DCI comprises an indication referencing at least an entry of a time domain resource allocation TDRA table, wherein the number of data N is associated with the number of entries included in the TDRA table, wherein N is an integer greater than 1; and The DCI is sent to a communication device.

9. An integrated circuit for controlling a process of a communication device, the integrated circuit comprising a circuit for controlling: receiving downlink control information DCI; and Obtaining from the DCI an indication referencing at least an entry of a time domain resource allocation TDRA table, The data quantity N is associated with the number of entries included in the TDRA table, and N is an integer greater than 1.

10. An integrated circuit for controlling a process of a scheduling device, the integrated circuit comprising circuitry for controlling: Generate downlink control information DCI, where The DCI includes an indication referencing an entry of a time domain resource allocation TDRA table, wherein the number of data N is associated with the number of entries included in the TDRA table, N being an integer greater than 1; and The DCI is sent to a communication device.

Images