User equipment, scheduling node, method for user equipment, and method for scheduling node - Patents.com

Abstract

The present disclosure relates to a user equipment (UE). The UE comprises a transceiver and circuitry. In operation, the transceiver receives downlink control information (DCI) signaling. In operation, the circuitry obtains an indication from the DCI signaling, the indication indicating scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of: i) scheduling of repeated transmissions of the TBs M times, where M is equal to or greater than 1; ii) an interleaving pattern for the TBs; and iii) transmission gaps between the TBs.

Description

[Technical Field]

[0001] The present disclosure is directed to methods, devices, and articles in communication systems, such as 3GPP® communication systems.

[0002] TECHNICAL FIELD The present disclosure relates to transmitting and receiving signals in a communication system, and more particularly to methods and communication devices for such transmission and reception. [Background technology]

[0003] The 3rd Generation Partnership Project (3GPP) is developing technical specifications for next-generation cellular technology, also known as 5G, which operates in the frequency range up to 100 GHz and includes New Radio (NR) radio access technology (RAT). NR is the successor to technologies such as LTE (Long Term Evolution) and LTE-A (LTE Advanced).

[0004] In systems such as LTE and NR, further improvements and options may facilitate efficient operation of the communication system and certain devices associated with the system. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 v15.6.0 [Non-patent document 2] 3GPP TS 38.211 v16.0.0 [Non-patent document 3] 3GPP TS 38.211 v15.7.0 [Non-patent document 4] ITU-R M.2083 [Non-Patent Document 5] TR 38.913 [Non-patent document 6] TS 23.501 v16.1.0 [Non-Patent Document 7] TS 38.331 v15.8.0 [Non-patent document 8] TS 38.212 v16.0.0 [Non-Patent Document 9] 3GPP TS 38.213 version 16.0.0 [Non-Patent Document 10] TS 38.214 v16.0.0 [Non-Patent Document 11] 3GPP TS 38.331 v15.9.0 [Non-Patent Document 12] TS 38.212 v15.6.0 Summary of the Invention [Problem to be solved by the invention]

[0006] One non-limiting, exemplary embodiment is directed to providing efficient Downlink Control Information (DCI) scheduling of multiple transport blocks (TBs) in a wireless communication system. [Means for solving the problem]

[0007] In one embodiment, the technology disclosed herein features an apparatus (e.g., user equipment (UE)) that, in operation, includes a transceiver that receives downlink control information (DCI) signaling. The apparatus also, in operation, includes circuitry that obtains, from the DCI signaling, an indication indicative of scheduling of N transport blocks, where N is an integer greater than 1. The indication further indicates at least one of: i) scheduling of repeated transmissions of the TBs M times, where M is greater than or equal to 1; ii) an interleaving pattern for the TBs; and iii) transmission gaps between the TBs.

[0008] These comprehensive or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0010] In the following, exemplary embodiments are explained in more detail with reference to the attached drawings. [Figure 1] Diagram showing an example of a 3GPP NR system architecture [Figure 2] Schematic diagram showing the division of functions between NG-RAN and 5GC [Figure 3] Sequence diagram for RRC connection setup / reconfiguration procedures [Figure 4] Schematic diagram showing usage scenarios for high-speed, large-capacity (eMBB: enhanced Mobile Broadband), multiple simultaneous connections (mMTC: massive Machine Type Communications), and ultra-reliable and low latency (URLLC: Ultra Reliable and Low Latency Communications) [Figure 5] Block diagram showing an example of a 5G system architecture for non-roaming [Figure 6] A block diagram illustrating functional components of a base station and user equipment according to one embodiment. [Figure 7] A block diagram illustrating steps of an exemplary communication method for a UE and steps of an exemplary communication method for a base station. [Figure 8]Schematic diagram of an exemplary scheduling of transport blocks [Figure 9] Schematic diagram of an exemplary scheduling of transport blocks DETAILED DESCRIPTION OF THE INVENTION

[0011] <5G NR system architecture and protocol stack> 3GPP is working on the next release of fifth-generation cellular technology (also known simply as 5G), which includes 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 at the end of 2017, allowing for trials and commercial deployment of smartphones compliant with the 5G NR standard to proceed.

[0012] In particular, the overall system architecture assumes a Next Generation Radio Access Network (NG-RAN) comprising gNBs. The gNBs provide UE-side termination of the NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols. The gNBs are interconnected via an Xn interface. The gNBs are also connected to the Next Generation Core (NGC) via a Next Generation (NG) interface, more specifically to the Access and Mobility Management Function (AMF, e.g., a specific core entity that runs the AMF) via an NG-C interface, and to the User Plane Function (UPF, e.g., a specific core entity that runs the UPF) via an NG-U interface. The NG-RAN architecture is shown in Figure 1 (see, for example, Section 4 of Non-Patent Document 1).

[0013] The NR user plane protocol stack (see, for example, Section 4.4.1 of Non-Patent Document 1) includes a Packet Data Convergence Protocol (PDCP) sublayer, a Radio Link Control (RLC) sublayer, and a Medium Access Control (MAC) sublayer, which are terminated on the network side at the gNB. Furthermore, a new Access Stratum (AS) sublayer (Service Data Adaptation Protocol (SDAP)) is introduced above the PDCP sublayer (see, for example, Section 6.5 of 3GPP Non-Patent Document 1). NR also defines a control plane protocol stack (see, for example, Section 4.4.2 of Non-Patent Document 1). An overview of Layer 2 functions is described in Section 6 of Non-Patent Document 1. The functions of the PDCP sublayer, RLC sublayer, and MAC sublayer are described in Sections 6.4, 6.3, and 6.2 of Non-Patent Document 1, respectively. The functions of the RRC layer are listed in section 7 of Non-Patent Document 1.

[0014] For example, the MAC layer is responsible for multiplexing logical channels and scheduling and scheduling-related functions, including handling various numerologies.

[0015] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. It also maps 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 transmitting a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels are the Physical Random Access Channel (PRACH), the Physical Uplink Shared Channel (PUSCH), and the Physical Uplink Control Channel (PUCCH) in the uplink, and the Physical Downlink Shared Channel (PDSCH), the Physical Downlink Control Channel (PDCCH), and the Physical Broadcast Channel (PBCH) in the downlink.

[0016] NR use cases / deployment scenarios include enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine Type Communication (mMTC), which have diverse requirements for data rates, latency, and coverage. For example, eMBB requires support for peak data rates (20 Gbps downlink, 10 Gbps uplink) and effective (user-experienced) data rates approximately three times those offered by IMT-Advanced. Meanwhile, URLLC imposes more stringent requirements for ultra-low latency (user-plane latency of 0.5 ms for both UL and DL) and high reliability (1-10-5 within 1 ms). Finally, mMTC preferably requires high connection density (1 million devices per square kilometer in urban environments), wide coverage in adverse environments, and ultra-long battery life (15 years) for low-cost devices.

[0017] Therefore, OFDM numerology (e.g., subcarrier spacing, OFDM symbol length, cyclic prefix (CP) length, number of symbols per scheduling interval) suitable for one use case may not be valid for another use case. For example, low-latency services may preferably require a shorter symbol length (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (i.e., TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP length than scenarios with small delay spreads. To maintain similar CP overhead, the subcarrier spacing needs to be optimized accordingly. NR may support multiple values ​​of subcarrier spacing. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, ... are currently being considered. The symbol length Tu and subcarrier spacing Δf are directly related by the formula Δf = 1 / Tu. Similar to LTE systems, the term "resource element" can be used to denote the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0018] In the new wireless system 5G-NR, for each numerology 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 the frequency index in the frequency domain and the symbol position in the time domain (see Non-Patent Document 2, for example, Section 4). For example, uplink and downlink transmissions are organized into frames with a duration of 10 ms, and each frame consists of 10 subframes with a duration of 1 ms each. In the implementation of 5G NR, the number of consecutive OFDM symbols per subframe varies depending on the subcarrier spacing setting. For example, in the case of a 15 kHz subcarrier spacing, the subframe has 14 OFDM symbols (similar to an LTE-compliant implementation assuming a normal cyclic prefix). On the other hand, in the case of a 30 kHz subcarrier spacing, the subframe has two slots, and each slot is composed of 14 OFDM symbols.

[0019] Compared with LTE numerology (subcarrier spacing and symbol length), NR supports multiple different types of subcarrier spacings, which are labeled by the parameter μ (LTE has only a 15 kHz subcarrier spacing, which corresponds to μ = 0 in NR). The types of NR numerology are summarized in Non-Patent Document 3.

[0020] <Function Split between NG-RAN and 5GC> Figure 2 shows the function split between NG-RAN and 5GC. The NG-RAN logical nodes are gNB or ng-eNB. The 5GC includes logical nodes of AMF, UPF, and SMF.

[0021] Specifically, gNB and ng-eNB provide the following main functions. · Radio resource management functions such as radio bearer control, radio admission control, connection mobility control, and dynamic resource allocation (scheduling) to the UE in both the uplink and downlink IP header compression, encryption, and integrity protection of data AMF selection at UE attach time if routing to AMF cannot be determined from information provided by the UE Routing of user plane data towards UPF Routing of control plane information towards AMF Setting up and disconnecting connections Scheduling and sending paging messages Scheduling and transmission of system broadcast information (originating from AMF or OAM) Measurement and measurement reporting configuration for mobility and scheduling Transport-level packet marking in the uplink Session management Network slicing support QoS flow management and mapping to data radio bearers Support for UEs in RRC_INACTIVE state NAS message delivery function Radio access network sharing Dual Connectivity Close cooperation between NR and E-UTRA

[0022] The Access and Mobility Management Function (AMF) provides the following main functions: Termination of Non-Access Stratum (NAS) signaling NAS signaling security Access Stratum (AS) security control Core Network (CN) inter-node signaling for mobility between 3GPP access networks Idle mode UE reachability (including control and execution of paging retransmissions) ·Registration area management Support for intra-system and inter-system mobility Access authentication Access authorization, including roaming permission checks Mobility management control (subscription and policy) Network slicing support Session Management Function (SMF) selection

[0023] Furthermore, the User Plane Function (UPF) provides the following main functions: Anchor points for intra-RAT / inter-RAT mobility (when applicable) External PDU session points for interconnection with data networks Packet routing and forwarding Packet inspection and policy rule enforcement for the user plane Traffic usage reporting Uplink classifier to support routing of traffic flows to the data network Branch point supporting multi-homed PDU sessions User plane QoS processing such as packet filtering, gating, and UL / DL (uplink / downlink) rate enforcement Uplink traffic verification (SDF placement for QoS flows) Downlink packet buffering and downlink data notification triggering

[0024] Finally, the Session Management Function (SMF) provides the following main functions: Session management · IP address allocation and management for UE UPF selection and control ·Configuration of traffic steering in the user plane function (UPF) to route traffic to appropriate destinations ·Enforcement of control part policies and QoS ·Notification of downlink data

[0025] <RRC Connection Setup and Reconfiguration Procedures> Figure 3 shows a part of the interaction between the UE, the gNB, and the AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS part (see Non-Patent Document 1).

[0026] RRC is a higher layer signaling protocol used to configure the UE and the gNB. This transition specifically involves the AMF preparing UE context data (e.g., including PDU session context, security keys, UE radio capabilities, UE security capabilities, etc.) and sending it to the gNB along with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE. This operation is performed by the gNB sending a Security Mode Command message to the UE, and the UE responding with a Security Mode Complete message to the gNB. The gNB then sends an RRC Reconfiguration message to the UE, and upon receiving an RRC Reconfiguration Complete message from the UE, the gNB performs reconfiguration to set up Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). In the case of a signaling-only connection, SRB2 and DRB are not configured, so the steps related to RRC reconfiguration are omitted. Finally, the gNB notifies the AMF that the configuration procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0027] Therefore, the present disclosure provides a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.) including: a control circuit that, during operation, establishes a next generation (NG) connection with a gNodeB; and a transmitter that, during operation, transmits an initial context setup message to the gNodeB via the NG connection so that a signaling radio bearer between the gNodeB and a terminal (UE) is configured. Specifically, the gNodeB transmits Radio Resource Control (RRC) signaling, including a resource allocation configuration information element, to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.

[0028] <IMT usage scenarios from 2020 onwards> Figure 4 shows some use cases for 5G NR. The Third Generation Partnership Project NR (3GPP NR) is considering three use cases that are expected to support a wide variety of services and applications through IMT-2020. The first phase of specifications for enhanced mobile broadband (eMBB) has been completed. In addition to further expanding support for eMBB, current and future research is also underway on standardization of ultra-reliable and low-latency communications (URLLC) and massive machine-type communications (mMTC). Figure 4 shows examples of usage scenarios expected for IMT beyond 2020 (see, for example, Figure 2 in Non-Patent Document 4).

[0029] URLLC use cases have stringent performance requirements for throughput, latency, availability, etc., and are envisioned as one of the enablers of future vertical applications, such as wireless control of industrial production and manufacturing processes, remote medical surgery, smart grid power distribution automation, and road safety. URLLC's ultra-high reliability is supported by identifying technologies that meet the requirements set by [Non-Patent Document 5]. For NR URLLC in Release 15, a key requirement is a user plane latency target of 0.5 ms in the uplink (UL) and 0.5 ms in the downlink (DL). A typical URLLC requirement for a single packet transmission is a block error rate (BLER) of 1E-5 for a 32-byte packet size with a user plane latency of 1 ms.

[0030] From a physical layer perspective, there are various ways to improve reliability. Currently, possible ways to improve reliability include defining a separate CQI table for URLLC, a more compact DCI format, and PDCCH repetition. However, as NR becomes more stable and developed (relative to the primary requirement of NR URLLC), the range of possible ways to achieve ultra-high reliability may expand. Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0031] Additionally, NR URLLC targets technology enhancements for improved latency and reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means stopping a transmission that already has allocated resources and using those already allocated resources for another transmission that requires less latency or higher priority and is requested later. Therefore, a previously allowed transmission is preempted by a later transmission. Preemption can be applied regardless of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (e.g., eMBB). Technology enhancements for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0032] The mMTC (Massively Simultaneous Connections) use case is characterized by a very large number of connected devices, each transmitting relatively small amounts of data that are typically not sensitive to latency. These devices are required to be low cost and have very long battery life. From an NR perspective, using very narrow bandwidth portions is one way to save power and extend battery life for the UE.

[0033] As mentioned above, the scope of reliability improvement in NR is expected to be broader. One of the key requirements common to all cases, and especially for URLLC and mMTC, is high or ultra-high reliability. Several mechanisms can be considered to improve reliability from the radio and network perspectives. In general, there are several key areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency, time, and spatial domains. These areas are generally applicable to reliability improvement, regardless of the specific communication scenario.

[0034] For NR URLLC, additional use cases with more stringent requirements have been identified, such as factory automation, the transportation industry, and power distribution. The more stringent requirements include high reliability (up to level 10 -6 ), high availability, a packet size of up to 256 bytes, time synchronization up to about a few μs (which can be 1 μs or a few μs depending on the frequency range and a short delay of about 0.5 to 1 ms, e.g., a 0.5 ms delay in the target user plane).

[0035] Furthermore, in NR URLLC, several technical enhancements have been identified from the perspective of the physical layer. These include enhancements to the Physical Downlink Control Channel (PDCCH) related to compact DCI, repetition of the PDCCH, and increased monitoring of the PDCCH. Also, the enhancement of Uplink Control Information (UCI) is related to the enhancement of extended Hybrid Automatic Repeat Request (HARQ) and CSI feedback. Enhancements to the Physical Uplink Shared Channel (PUSCH) related to mini-slot level hopping and enhancements to retransmission / repetition have also been identified. A "mini-slot" represents a Transmission Time Interval (TTI) that contains a smaller number of symbols than a slot (a slot composed of 14 symbols).

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

[0037] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) for the PDU session; additional DRBs for the QoS flows of that PDU session can be configured later (when this is up to the NG-RAN), e.g., as described above with reference to Figure 3. The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and the 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and the NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0038] Figure 5 shows the non-roaming reference architecture for 5G NR (see Non-Patent Document 6, Section 4.23). As illustrated in Figure 4, application functions (AFs), such as external application servers hosting 5G services, interact with the 3GPP core network to provide services. For example, they access network exposure functions (NEFs) to support applications that affect traffic routing, and interact with a policy framework for policy control such as QoS control (see Policy Control Function (PCF)). Based on operator deployment, application functions that are deemed trusted by the operator can interact directly with the relevant network functions. Application functions that are not authorized by the operator to directly access network functions interact with the relevant network functions using an open framework via the NEF.

[0039] Figure 5 shows further functional units of the 5G architecture, namely the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), the Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and the Data Network (DN) (operator-provided services, internet access, third-party services, etc.). All or some of the core network functions and application services may be deployed and run on a cloud computing environment.

[0040] Therefore, in the present disclosure, in operation, in order to establish a PDU session including a radio bearer between a gNodeB and a UE according to QoS requirements, a transmitter that transmits a request including QoS requirements for at least one of URLLC, eMBB, and mMTC services to at least one of the functions of the 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.), and a control circuit that executes a service using the established PDU session in operation are provided in an application server (e.g., AF in the 5G architecture).

[0041] <RRC state (RRC_Connected, RRC_Inactive)> 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 connection to the core network established) and the RRC connected state where the UE can transmit user plane data while mobility is network-controlled to support seamless service continuity. In relation to 5G NR, the LTE-related RRC state machine can also be extended to the inactive state, similar to NR 5G described below (see, for example, Non-Patent Document 7, FIG. 4.2.1-2).

[0042] The RRC of NR 5G (see Non-Patent Document 7, Section 4) supports three states: RRC idle, RRC inactive, and RRC connected. When the RRC connection is established, the UE enters either the RRC_CONNECTED state or the RRC_INACTIVE state. Otherwise, i.e., when the RRC connection is not established, the UE is in the RRC_IDLE state. As shown in FIG. 6, the following state transitions can occur. · For example, from RRC_IDLE to RRC_CONNECTED according to the "connection establishment" procedure · For example, from RRC_CONNECTED to RRC_IDLE according to the "connection release" procedure<0For example, from RRC_CONNECTED to RRC_INACTIVE following the "connection release with suspend" procedure. For example, from RRC_INACTIVE to RRC_CONNECTED following the "connection resumption" procedure. For example, from RRC_INACTIVE to RRC_IDLE (one-way) following the "Connection Release" procedure

[0043] A new RRC state, RRC Inactive, is being defined for 5G 3GPP's new radio technologies to bring advantages in supporting a wider range of services such as eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications), and URLLC (Ultra-Reliable and Low-Latency Communications), which have significantly different requirements in terms of signaling, power saving, latency, etc. Therefore, the new RRC Inactive state must be designed to enable minimizing signaling, power consumption, and resource costs in the radio access network and core network, while still allowing low-latency initiation of data transfers, etc.

[0044] <Bandwidth part> The NR system supports a much wider maximum channel bandwidth (e.g., several hundred MHz) than LTE's 20 MHz. LTE also supports wideband communications through carrier aggregation (CA) of component carriers up to 20 MHz. Defining wider channel bandwidths in NR enables dynamic allocation of frequency resources through scheduling, which can be more efficient and flexible than LTE's carrier aggregation operation, whose activation / deactivation is based on MAC control elements. Having a single wideband carrier also benefits from lower control overhead, since only a single control signaling is required (as opposed to carrier aggregation, which requires separate control signaling for each aggregated carrier).

[0045] Also, like LTE, NR may support aggregation of multiple carriers via carrier aggregation or dual connectivity.

[0046] Because UEs do not always require high data rates, using a wide bandwidth can result in high idle power consumption in terms of both RF and baseband signal processing. In this regard, the newly developed bandwidth part concept for NR offers a means to operate UEs at bandwidths narrower than the configured channel bandwidth, thereby providing an energy-efficient solution while supporting wideband operation. This can be beneficial for low-end terminals that cannot access the full NR bandwidth.

[0047] A bandwidth part (BWP) is a subset of the total cell bandwidth of a cell, e.g., the location and number of contiguous physical resource blocks (PRBs). It can be defined separately for uplink and downlink. Furthermore, each bandwidth part can be associated with a specific OFDM numerology, e.g., subcarrier spacing and cyclic prefix. For example, bandwidth adaptation is achieved by configuring BWP(s) in the UE and informing the UE which of the configured BWPs is currently active.

[0048] Illustratively, in 5G NR, a specific BWP is configured only for a UE in the RRC_Connected state. For example, other than an initial BWP (e.g., one for UL and one for DL), a BWP exists only for a UE in the connected state. To support initial data exchange between the UE and the network, such as during the process of transitioning 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 with minimum SI.

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

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

[0051] 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), the initial BWP is always explicitly configured, and a default BWP may also be configured. If a default BWP is configured for the serving cell, the active BWP is switched to the default BWP when the inactivity timer associated with that cell expires.

[0052] Typically, it is assumed that the downlink control information does not include the BWP ID.

[0053] <Downlink Control Information (DCI)> 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).

[0054] Downlink control information (which may be referred to as downlink control information DCI) has the same purpose in 5G NR as DCI in LTE, i.e., it is a set of special control information that schedules downlink data channels (such as PDSCH) or uplink data channels (such as PUSCH). In 5G NR, there are several different predefined DCI formats (see 3GPP TS 26.110, section 7.3.1). An overview is given in the table below. [Table 1]

[0055] The PDCCH search space is an area in the downlink resource grid (time-frequency resources) where the PDCCH (DCI) can be carried. Roughly speaking, the radio resource region is used by the base station to transmit control information in the downlink to one or more UEs. The UE performs blind decoding over the entire search space to try to find the PDCCH data (DCI). Conceptually, the concept of search space in 5G NR is similar to that of search space in LTE, although there are many differences in the details.

[0056] In 5G NR, the PDCCH is transmitted in a radio resource region called the control resource set (CORESET). The concept of a CORESET does not explicitly exist in LTE. Instead, the LTE PDCCH uses the entire carrier bandwidth in the first one to three OFDM symbols (four in the narrowest case). In contrast, the NR CORESET can exist anywhere within a slot and anywhere within the carrier's frequency range, but a UE is not expected to handle a CORESET outside its active bandwidth part (BWP). 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 the PDCCH / DCI.

[0057] Thus, the UE monitors a set of PDCCH candidates in one or more CORESETs on the active DL BWP for each activated serving cell for which PDCCH monitoring is configured using the corresponding search space set, where monitoring means decoding each PDCCH candidate according to the monitored DCI format, e.g. as defined in 3GPP TS 23.2013, sections 10 and 11.

[0058] Briefly, a search space may include multiple PDCCH candidates associated with the same aggregation level (e.g., the PDCCH candidates differ in terms of the DCI format they monitor). A search space set may include multiple search spaces with different aggregation levels but associated with the same CORESET. Unlike LTE, where the control channel spans the entire carrier bandwidth, as described above, the bandwidth of the CORESET may 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, consequently, the PDCCH candidates of the search spaces included in the set. The CORESET configuration also defines the duration of the search space set, which may be one to three OFDM symbols. Meanwhile, the start time is configured by the search space set configuration itself, e.g., the OFDM symbol from which the UE starts monitoring the PDCCHs of the search spaces of the set. In combination, the search space set configuration and the CORESET configuration provide a clear definition of the UE's PDCCH monitoring requirements in the frequency and time domains. The configuration of both the CORESET and the search space set can be configured semi-statically via RRC signaling.

[0059] The first CORESET, CORESET0, is provided as part of the initial bandwidth part configuration by the master information block (MIB), allowing the UE to receive the remaining system information and additional configuration information from the network. After connection setup, multiple, possibly overlapping CORESETs can be configured into the UE using RRC signaling.

[0060] The network may define a common control region and a UE-specific control region. In NR, the number of CORESETs is limited to three per BWP, including both common and UE-specific CORESETs. Assuming, for example, that four BWPs are configurable for each serving cell, the maximum number of CORESETs per serving cell is 12. In general, the number of search spaces per BWP can be limited to, for example, 10, as in current NR, resulting in a maximum number of 40 search spaces per BWP. Each search space is associated with a CORESET.

[0061] Since the common CORESET is shared by multiple UEs in a cell, the network must correspondingly support coordination with all UEs for this configuration. The common CORESET can be used for random access, paging, and system information.

[0062] In NR, flexible slot formats can be configured for UEs by cell- and / or UE-specific higher layer signaling in a semi-static downlink / uplink allocation scheme, or by dynamic signaling, such as 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) which carries a dynamic slot format indication (SFI).

[0063] In general, one or more CORESETs including both common CORESETs and UE-specific CORESETs may be configured for each BWP (e.g., up to three CORESETs per BWP), and each CORESET may have multiple search spaces, each of which has one or more PDCCH candidates that the UE can monitor.

[0064] <Time domain scheduling in 5G NR> In the time domain, 5G NR transmissions are organized into frames of 10 ms in length, each divided into 10 equally sized subframes of 1 ms in length. Subframes are then divided into slots of 14 OFDM symbols each. The duration of a slot in milliseconds varies depending on the numerology. Thus, for example, for a 15 kHz subcarrier spacing, an NR slot has the same structure as an LTE subframe with a regular cyclic prefix. The NR subframe serves as a numerology-independent time reference, which is particularly useful when multiple numerologies are mixed on the same carrier, whereas a slot is the typical unit of dynamic scheduling.

[0065] The following describes time domain resource allocation currently implemented in 3GPP technical specifications. The following description should be understood as a specific exemplary implementation of time domain resource allocation, and not as the only possible time domain resource allocation. Rather, the present disclosure and solutions are applied in a manner that corresponds to different implementations of time domain resource allocation that may be implemented in the future. For example, although the following TDRA table is based on specific parameters (e.g., five parameters), the time domain resource allocation may also be based on a different number of parameters and / or different parameters.

[0066] The time domain allocation for received or transmitted data is dynamically signaled in the DCI, which is useful in that the fraction of a slot available for downlink reception or uplink transmission can vary from slot to slot as a result of dynamic TDD use or the amount of resources used for uplink control signaling. The slot in which the transmission occurs is signaled as part of the time domain allocation. Downlink data is often transmitted in the same slot as the corresponding resource allocation, but this is often not the case for uplink transmission.

[0067] When a UE is scheduled to receive a PDSCH or transmit a PUSCH by a DCI, the Time Domain Resource Assignment (TDRA) field value of the DCI indicates a row index of a time-domain resource allocation (TDRA) table. Because TDRA entries are presented as a table in the corresponding 3GPP technical specifications, the term "table" is used herein, but this should be interpreted as a logical and rather non-limiting term. In particular, the present disclosure is not limited to any particular organization, and the TDRA table may be implemented in any manner as a set of parameters associated with each entry index.

[0068] For example, a row of the TDRA table indexed by the DCI defines several parameters that can be used for allocating radio resources in the time domain. In the current example, the TDRA table may indicate the slot offset K0 / K2, the start and length indicator SLIV (start and length indicator), or directly the start symbol S and the allocation length L. Furthermore, the TDRA table may also indicate the PDSCH mapping type assumed for PDSCH reception and the dmrs-TypeA-Position parameter, which is not directly related to the scheduled time-domain radio resources. The time-domain allocation field of the DCI is used as an index into this table, from which the actual time-domain allocation is obtained. Thus, in such an exemplary implementation, a DCI indication of a row of the TDRA table (one value of the row index) corresponds to an indication of a specific combination of values ​​of the dmrs-TypeA-Position, PDSCH mapping type, K0 value, S value, and / or L value.

[0069] There is one table for uplink scheduling grants and one table for downlink scheduling assignments. For example, 16 rows can be configured, each row containing: Slot offset (K0, K2), which is the slot relative to the slot where the DCI is acquired. Currently, downlink slot offsets of 0 to 3 are possible, and uplink slot offsets of 0 to 7 can be used. The slot offset can also be referred to as the gap (e.g., time gap or slot gap) in terms of the number of slots between the slot of the PDCCH (including K0 / K2) and the slot of the corresponding PDSCH scheduled by the PDCCH. The first OFDM symbol in the slot in which data is transmitted. Duration of the transmission in number of OFDM symbols in a slot. Not all combinations of start and length fit into one slot, so start and length are coded together to cover only valid combinations. For downlink, the PDSCH mapping type, i.e., DMRS position, is also part of the table, which provides more flexibility than if the mapping type were indicated separately.

[0070] It is also possible to configure slot aggregation, i.e. transmission in which the same transport block is repeated for up to 8 slots.

[0071] The current 3GPP standard, 3GPP TS 2.0, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.1 ...1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3

[0072] Below is the default PDSCH time domain resource allocation A for normal cyclic prefix. [Table 2]

[0073] As can be seen from this table, the K0 value is always assumed to be 0, and indeed same-slot downlink scheduling is applied.

[0074] Below is the default PUSCH time domain resource allocation A for normal cyclic prefix. [Table 3]

[0075] As is evident from this table, the K2 value in turn depends on the parameter j, as shown in the table below. [Table 4]

[0076] The parameter μPUSCH is a setting for the subcarrier spacing of the PUSCH.

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

[0078] An example of a TDRA table configured by RRC for PDSCH is shown below, where the parameter K0 varies between 0 and 4 slots. [Table 5]

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

[0080] In a current 5G-specific example implementation, the configured TDRA table is signaled within the PDSCH-related configuration via RRC (e.g., the information element PDSCH-Config in Non-Patent Document 11), which in turn may be within the information element related to the bandwidth part ((BWP)-DownlinkDedicated). Therefore, if the TDRA table is configured at a higher layer, the TDRA table may be BWP-specific. The communication device may use a default table or apply a TDRA table configured at a higher layer (called pdsch-TimeDomainAllocationList in either pdsch-ConfigCommon or pdsch-Config). However, this is only one possible example of the interaction between the TDRA configuration and the BWP concept in NR. The present invention does not assume the use of BWP and is not limited to resource allocation using the TDRA table.

[0081] <PDCCH downlink control channel (PDCCH) monitoring> Many functions performed by a UE include monitoring a downlink control channel (eg, PDCCH, see 3GPP TS 23.110.2, section 5.2.3) to receive, for example, specific control information or data intended for the UE.

[0082] A non-exhaustive list of these features is given below. Paging message monitoring function - System information acquisition function Signaling monitoring operation for Discontinued Reception (DRX) function Inactivity monitoring for discontinuous reception (DRX) function -Random access response reception for random access function Packet Data Convergence Protocol (PDCP) layer reordering function

[0083] As mentioned above, PDCCH monitoring is performed by a UE to identify and receive information intended for the UE, such as control information and user traffic (e.g., DCI on the PDCCH and user data on the PDSCH indicated by the PDCCH).

[0084] Downlink control information (which may be referred to as downlink control information (DCI)) has the same purpose in 5G NR as DCI in LTE, i.e., it is a set of special control information that schedules a downlink data channel (such as a PDSCH) or an uplink data channel (such as a PUSCH). In 5G NR, there are several different predefined DCI formats (see 3GPP TS 26.110, section 7.3.1).

[0085] The DCI format indicates a predetermined format in which each piece of information is formed and transmitted. Specifically, DCI formats 0_1 and 1_1 are used to schedule the PUSCH and PDSCH in one cell, respectively.

[0086] Each of these functions, PDCCH monitoring, serves a specific purpose and is therefore initiated towards its end. PDCCH monitoring is typically controlled based on at least one timer operated by the UE. The timer has the purpose of controlling PDCCH monitoring, for example, limiting the maximum time that the UE monitors the PDCCH. For example, the UE may not monitor the PDCCH indefinitely, but may stop monitoring after a period of time to allow power to be saved.

[0087] As mentioned above, one of the purposes of DCI on the PDCCH is dynamic scheduling of resources in the downlink, uplink, and even sidelink. Specifically, several formats of DCI are provided to carry an indication of resources allocated to a data channel of a particular user (resource allocation, RA). Resource allocation may include specifying resources in the frequency domain and / or the time domain.

[0088] <Terminals and base stations> In LTE and NR, a terminal, user terminal, or user device is called user equipment (UE). It can be a mobile device or communication device, such as a wireless phone, smartphone, tablet computer, or USB (Universal Serial Bus) stick, that has user equipment functionality. However, the term mobile device is not limited thereto; in general, a relay can also have such mobile device functionality and can also function as a relay. For example, a mobile station, mobile node, or user terminal or UE is a physical entity (physical node) in a communication network. Furthermore, a communication device can be any machine-type communication device, such as an IoT device. A node can have multiple functional entities. A functional entity refers to a software or hardware module that implements a given set of functions and / or provides a given set of functions to other functional entities of the same or other nodes or networks. A node may have one or more interfaces that connect the node to communication facilities or media over which the node can communicate. Similarly, a network entity may have logical interfaces that connect functional entities to communication facilities or media over which it can communicate with other functional entities or corresponding nodes.

[0089] A base station is a network node that forms part of a network that provides services to, for example, terminals. A base station is a network node or scheduling node that provides wireless access to terminals. Communication between terminals and base stations is typically standardized. In LTE and NR, the wireless interface protocol stack includes a physical layer, a medium access layer (MAC), and higher layers. The control plane provides a radio resource control protocol, which is a higher layer protocol. Through RRC, the base station can control the configuration of terminals, and terminals can communicate with the base station to perform control tasks such as establishing and modifying connections and bearers, measurements, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB. The term "base station" or "radio base station" herein refers to a physical entity in a communication network. Similar to a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements a predetermined set of functions and / or provides a predetermined set of functions to other functional entities of the same or other nodes or networks. The physical entity performs several control tasks for communication devices, including one or more of scheduling and configuration. Note that the base station functionality and communication device functionality may be integrated within a single device. For example, a mobile terminal may also implement the base station functionality for other terminals. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB.

[0090] <Terminology> The following describes UEs, base stations, and procedures for a new radio access technology intended for 5G mobile communication systems, but which may also be used in LTE mobile communication systems. Different implementations and variations are also described. The following disclosure is facilitated by, and may be based, for example, at least in part on, the above discussion and discoveries.

[0091] It should be noted that, overall, many assumptions are made herein to enable the principles underlying the present disclosure to be explained in a clear and understandable manner, however, these assumptions should be understood as merely examples made herein for illustrative purposes and should not limit the scope of the present disclosure.

[0092] Furthermore, although some of the terms used below, such as procedures, entities, and layers, are closely related to those used in the LTE / LTE-A system or the current 3GPP 5G standardization, the specific terms used in the context of the new radio access technology of the upcoming 3GPP 5G communication system have not yet been fully determined and may eventually change. Therefore, the terms may change in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art will recognize that the scope of the embodiments and their protection should not be limited to the specific terms used illustratively herein due to the absence of newer or ultimately agreed-upon terms, but should be more broadly understood in terms of the functions and concepts underlying the functions and principles of the present disclosure.

[0093] <Possibility of power saving> The inventors have identified the possibility of saving power in the UE and thereby extending UE battery life, especially for reduced capability NR devices (e.g., those corresponding to Release 17). Specifically, UE power consumption can be saved in applicable use cases (e.g., delay tolerance) by i) reducing PDCCH monitoring, such as by reducing the 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.

[0094] One way to save UE power is to improve PDCCH monitoring and scheduling. Specifically, for UEs in RRC CONNECTED mode with heavy traffic, PDCCH-only still accounts for a large portion of UE power consumption. Therefore, since PDCCH-only slots without PDSCH / PUSCH scheduling can account for a large portion of total power consumption, reducing the number of PDCCH-only slots can help significantly reduce UE power consumption. Further power consumption reductions can be achieved by scheduling repeated transmissions and / or receptions of one or more (or all) of the TBs scheduled by the DCI with the DCI.

[0095] It should be noted that scheduling multiple TBs may be particularly suitable / efficient for less delay-sensitive service types when specific service requirements such as throughput need to be met for a particular UE / service. In such cases, the gNB may perform scheduling prediction, which may enable better slot utilization by scheduling two or more TBs in one DCI into subsequent slots.

[0096] For light-capability UEs, coverage recovery may also be an important aspect. Data channel scheduling with repetition may be beneficial for improving coverage, as certain cost / complexity reductions are made, such as reduced Rx / Tx antennas. Scheduling multiple TBs may allow for further power consumption reductions in interaction with reduced / adapted PDCCH monitoring, as explained further below.

[0097] <Embodiment> The present disclosure provides techniques for multiple TB scheduling with or without repeat transmission that may facilitate UE power saving. Specifically, the present disclosure addresses signaling support and framework design for multiple TB scheduling with or without repeat transmission. In particular, the present disclosure provides a framework that may enable dynamic multiple TB scheduling with or without repeat transmission.

[0098] The present disclosure relates to scheduling involving both entities: a scheduled device (typically a communication device / transceiver device) and a scheduling device (typically a network node). Accordingly, the present disclosure provides a base station and a user equipment (UE). As shown in FIG. 6, a user equipment 610 and a base station 660 may communicate with each other via a radio channel in a wireless communication system. For example, the UE may be an NR user equipment (NR) and the base station may be a network node or scheduling node, such as an NR gNB, particularly a gNB in ​​a Non-Terrestrial Network (NTN) NR system.

[0099] The present disclosure further provides a system including a scheduled device and a scheduling device, as well as corresponding methods and programs. An example of such a communication system is shown in FIG. 6. The communication system 600 may be a wireless communication system conforming to 5G technical specifications, particularly an NR communication system. However, the present disclosure is not limited to 3GPP NR and may be applied to other wireless or cellular systems, such as NTN.

[0100] FIG. 6 illustrates a general, simplified, and exemplary block diagram of a user equipment 610 (also referred to as a “communication device,” “terminal,” or “UE”) and a scheduling device 660, illustratively assumed here to be located in a base station (network node) such as an eNB or gNB. However, in general, the scheduling device may be a terminal in the case of a sidelink connection between two terminals. Also, particularly with regard to URLLC, eMBB, and mMTC use cases, the communication device 610 may be a sensor device, a wearable device, or a controller of a connected vehicle or automated machine in a factory. Furthermore, the communication device 610 may be capable of acting as a relay between the base station 660 and other communication devices (e.g., the present disclosure is not limited to a communication “terminal” or a user “terminal”).

[0101] The UE and eNB / gNB communicate with each other over a (wireless) physical channel 650 using their transceiver 620 (UE side) and transceiver 670 (base station side), respectively. The base station 660 and the terminal 610 together form a communication system 600. The communication system 600 may further include other entities as shown in FIG.

[0102] As shown in FIG. 6, in some embodiments, a user equipment (UE) 610 comprises a transceiver 620 that, upon operation, receives downlink control information (DCI) signaling (also referred to in this disclosure as multi-TB scheduling DCI). The UE further comprises circuitry 630, 635 that, upon operation, obtains an indication from the DCI signaling. For example, the UE may obtain the indication from the DCI by parsing the DCI and / or by extracting the indication from the DCI. The indication indicates scheduling of N transport blocks (TBs), where N is an integer greater than 1. Furthermore, the indication indicates at least one of i) scheduling of repeated transmissions of M TBs, where M is greater than or equal to 1, ii) an interleaving pattern for the TBs, and iii) a transmission gap between the TBs.

[0103] Also shown in FIG. 6 , in some embodiments, the base station 660 (scheduling device 660) comprises circuits 680, 685. In operation, the circuits 680, 685 generate downlink control information (DCI) signaling (also referred to in this disclosure as multi-TB scheduling DCI). The DCI signaling may include an indication to the UE of scheduling N transport blocks (TBs), where N is an integer greater than 1. Furthermore, the indication may indicate at least one of: i) scheduling of repeated transmissions of the TBs M times, where M is greater than or equal to 1; ii) an interleaving pattern for the TBs; and iii) transmission gaps between the TBs. The base station 660 may further comprise a transceiver 670, which transmits the DCI signaling to the UE.

[0104] 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 620, in turn, may include and / or function as a receiver and / or a transmitter. In other words, in this disclosure, the term “transceiver” is used to refer to hardware and software components that enable the communication device 610 or the base station 660 to transmit and / or receive wireless signals over the wireless channel 650. Thus, a transceiver corresponds to a receiver, a transmitter, or a combination of a receiver and a transmitter. Typically, base stations and communication devices are assumed to be capable of both transmitting and receiving wireless signals. However, for some applications (e.g., smart homes, smart cities, industrial automation), particularly for eMBB, mMTC, and URLLC, devices such as sensors may only receive signals. Furthermore, the term “circuit” includes processing circuits formed by one or more processors or processing units.

[0105] The circuits 630, 680 (or processing circuits) may be one or more hardware components, such as one or more processors or any LSI. Between the transceiver and the processing circuit, there are input / output points (or nodes) through which the processing circuit, in operation, can control the transceiver, i.e., control the receiver and / or transmitter, and exchange receive / transmit data. The transceiver may include an RF (radio frequency) front end, including one or more antennas, amplifiers, RF modulators / demodulators, etc., as a transmitter and receiver. The processing circuit may perform control tasks, such as transmitting user data and control data provided by the processing circuit and / or controlling the transceiver to receive user data and control data that are further processed by the processing circuit. The processing circuit may also be responsible for performing other processing, such as decisions, judgments, calculations, and measurements. The transmitter may be responsible for performing transmission processing and other related processing. The receiver may be responsible for performing reception processing and other related processing.

[0106] Corresponding to the above-described UE, a communication method executed by the UE is provided. As shown in FIG. 7, the method includes step S740 of receiving downlink control information (DCI) signaling (also referred to as multi-TB scheduling DCI in this disclosure). Furthermore, the method includes step S750 of obtaining an indication from the DCI signaling. For example, the indication may be obtained from the DCI by parsing the DCI and / or extracting the indication from the DCI. The indication indicates scheduling of N transport blocks (TBs), where N is an integer greater than 1. Furthermore, the indication indicates at least one of scheduling repeated transmission of M TBs, where M is equal to or greater than 1, an interleaving pattern for the TBs, and a transmission gap between the TBs. Furthermore, as shown in FIG. 7, the UE may transmit (S760) and / or receive (S760) the scheduled transport blocks according to the scheduling of the DCI / PDCCH.

[0107] Further, a communication method performed by the base station is provided corresponding to the above-mentioned base station. As shown in FIG. 7, the method includes a step S720 of generating downlink control information (DCI) signaling (also referred to as multi-TB scheduling DCI in the present disclosure). The DCI signaling may include an indication to a user equipment (UE) of scheduling of N transport blocks (TBs), where N is an integer greater than 1. Furthermore, the indication may indicate at least one of i) scheduling of repeated transmission of M TBs, where M is equal to or greater than 1, ii) an interleaving pattern of the TBs, and iii) transmission gaps between the TBs. Finally, the method includes a step S730 of transmitting the DCI signaling to the UE. Furthermore, as shown in FIG. 7, the base station may receive (S770) and / or transmit (S770) the scheduled transport blocks according to the scheduling of the DCI / PDCCH.

[0108] As shown in FIG. 7, the base station method may perform or may include step S710. In step S710, which occurs before the generation of multi-TB scheduling DCI in step S720, the base station allocates / schedules time domain resources for transmission and / or reception of N transport blocks. This scheduling may include determining to indicate scheduling of multiple (e.g., N>1) TBs to one or more UEs. Step 710 may generally be performed taking into account traffic conditions and quality of service requirements used by one or more UEs, in conjunction with scheduling of resources for other transmission / reception of other UEs.

[0109] It should be noted that any of the steps / actions described below may be performed or controlled by circuitry 630 (UE side) and / or circuitry 680 (base station side).

[0110] In the further description, details and embodiments apply to each of the transceiver device, the scheduling device (or scheduling node), and the method, unless an explicit description or the context dictates otherwise.

[0111] <Multi-TB Scheduling DCI> In general, a DCI may schedule multiple TBs. In other words, multiple TB transmissions with or without repeated transmissions are scheduled by a (single or one) DCI. Hereinafter, such a DCI is also referred to as a multi-TB scheduling DCI. More specifically, a multi-TB scheduling DCI indicates the scheduling of multiple TBs (to the same UE). Similarly, the term "multi-TB scheduling" refers to the scheduling of multiple TBs by a single (or one) DCI to the same UE.

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

[0113] In other words, the multi-TB scheduling DCI may include i) an indication indicating the number N of TBs, ii) an indication indicating the number M of repeated transmissions of the TBs, iii) an indication indicating a transmission gap, and iv) an indication indicating an interleaving pattern. Note that an indication of the number N of TBs may implicitly indicate the scheduling of N TBs, and an indication of M repeated transmissions may implicitly indicate the scheduling of M repeated transmissions of a TB. More specifically, an 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 is considered to be a joint indication of the number N and the scheduling of the N TBs. Similarly, an indication of the number M in the multi-TB scheduling DCI may also indicate the scheduling of M repeated transmissions. In other words, the indication of the number M is considered to be a joint indication of the number M and the scheduling of M repeated transmissions. Note that the interleaving pattern may implicitly indicate the scheduling of N TBs and / or the scheduling of M repeated transmissions of a TB.

[0114] In general, an indication of scheduling of N TBs may jointly indicate the scheduling of the N TBs and at least one of: i) scheduling of M repeated transmissions, ii) an interleaving pattern, and iii) a transmission gap. Such joint indication may reduce overhead.

[0115] <Multi-TB Scheduling DCI Scheduling> In general, an indication of scheduling N TBs may include an indication of the number N. In other words, a 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.

[0116] However, the present invention is not limited in this respect. That is, 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) is configured to receive Radio Resource Control (RRC) signaling. In these embodiments, the UE (e.g., its processing circuitry) then, in operation, obtains an indication of the number N of TBs from the received RRC signaling.

[0117] Similarly, an indication of scheduling M repeat transmissions of a TB may generally include an indication of the number M. In other words, a multi-TB scheduling DCI may generally include an indication of the number M of repeat transmissions. The indication of the number M of repeat transmissions may be explicit or implicit.

[0118] However, the present invention is not limited thereto. That is, scheduling of M repeated transmissions 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, a multi-TB scheduling DCI that schedules repeated transmissions of TBs may or may not include an indication of the number M of repeated transmissions of the scheduled TBs. Similar to the number N of TBs, the number M of repeated transmissions may be indicated via RRC.

[0119] In general, 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 (the last value of N / M explicitly indicated by the multi-TB scheduling DCI) apply. Alternatively or additionally, 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 repeat transmissions, if applicable) solely by a trigger (e.g., a one-bit field in the DCI). That is, the number of transport blocks N, the number of repeat transmissions M, the interleaving pattern, and the transmission gap may be indicated by other means, e.g., configured by RRC.

[0120] Furthermore, the multi-TB scheduling DCI may generally schedule resources for scheduled transmissions / repeated transmissions of multiple TBs. The resource scheduling may be slot-based (as shown in FIGS. 8a-8d and 9) or non-slot-based. In other words, the multi-TB scheduling DCI may be slot-based multi-TB scheduling or non-slot-based multi-TB scheduling. More specifically, slot-based scheduling refers to resource scheduling in which all transmissions / repeated transmissions of a TB are scheduled at slot granularity. In other words, for each scheduled TB transmission / repeated transmission, all time domain resources of one or more respective slots are used (e.g., each transmission / repeated transmission uses one or more entire slots). On the other hand, non-slot-based scheduling refers to scheduling in which the time domain resources scheduled for a TB or its repeated transmissions are less than one slot, e.g., one, two, or several OFDM symbols. Specifically, non-slot-based scheduling may schedule multiple transmissions / repeated transmissions of a TB in the same slot.

[0121] It should be noted that in this disclosure, terms such as "the DCI schedules," "the DCI indicates scheduling," and "the DCI includes an indication indicating scheduling" are used synonymously. Furthermore, terms such as "schedules the transmission of multiple TBs," "schedules the transmission and / or reception of multiple TBs," and "schedules multiple TBs" are used synonymously.

[0122] Furthermore, the scheduling of the N TBs (and M repeated transmissions, if applicable) may be scheduling of transmissions on the uplink (UL, e.g., PUSCH) or downlink (DL, e.g., PDSCH). In other words, the TBs scheduled by the multi-TB scheduling DCI may be scheduled for transmission or reception by the UE (and correspondingly for reception or transmission by the base station). In other words, unless otherwise specified, 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.

[0123] Note that the resources used for transmission / reception of the N TBs (and M repeated transmissions, if applicable) to be scheduled may or may not be indicated (explicitly or implicitly) by the multi-TB scheduling DCI, e.g., via RRC using the SPS / CG framework.

[0124] <Transport Block (TB) and Repeated Transmission> In general, the N TBs may carry different data from each other.

[0125] It should be noted that the term "transport block" may also be replaced with the term "codeword," particularly when used 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 can be scheduled and mapped to one or more / multiple spatial layers. In terms of channel coding and modulation, no distinction is made between the operations for transport blocks and codewords as far as the present invention is concerned. In other words, the present disclosure also enables scheduling of multiple codewords by providing a multi-codeword scheduling DCI (with the term "transport block" replaced with the term "codeword") that functions similarly to a multi-TB scheduling DCI.

[0126] In general, each of the M repeated transmissions may carry the same data as a corresponding TB among the N TBs. In other words, each of the M repeated transmissions may correspond to one of the N TBs scheduled by the multi-TB scheduling DCI. A TB and its corresponding repeated transmission may generally carry the same data. However, the TB and the corresponding repeated transmission are not necessarily identical. For example, the same data may be coded differently in the TB and the corresponding repeated transmission. That is, the repeated transmission of a TB may be a different redundancy version (RV) of that TB. In general, M may be a number equal to or greater than 1, and the number of repeated transmissions M equal to 1 may mean / indicate that (only) one transmission is scheduled for one of the TBs, or that (only) one transmission of each TB is scheduled (i.e., the first transmission of each TB is counted as one of the repeated transmissions of that TB). In other words, M=1 may indicate that no repeated transmissions are scheduled. In other words, the terms "transmission" and "repeated transmission" are used synonymously herein. It should be noted that in this disclosure, the term "further repeated transmission" refers to transmission(s) of a TB other than the first transmission of the TB.

[0127] Note that the number of repeat transmissions M may be the repeat transmission / total of transmissions scheduled by the multi-TB scheduling DCI. However, the present invention is not limited thereto, because the multi-TB scheduling DCI may schedule M repeat transmissions of each of the N scheduled transport blocks (a total of N×M repeat transmissions). Alternatively, the DCI may schedule M repeat transmissions for only one (e.g., the first) or some (e.g., every other) of the TBs, and transmit the other TBs only once. In general, the multi-TB scheduling DCI may indicate a different number of repeat transmissions for each scheduled TB.

[0128] It should be noted that the repeat transmissions and transmissions referred to in this disclosure may be nominal repeat transmissions / transmissions or actual repeat transmissions / transmissions. Nominal repeat transmissions and actual repeat transmissions are concepts introduced in Release 16NR for PUSCH repeat transmission type B and are described in detail in 3GPP TS 26.10, Section 6.1.2.1. More specifically, a nominal repeat transmission / transmission is one that is intentionally configured / scheduled / indicated based on configured / scheduled / indicated resources. However, in general, some of the OFDM symbols allocated to a nominal repeat transmission may be invalid, or the nominal repeat transmission may cross a slot boundary, resulting in the nominal repeat transmission being interrupted. As a result, the nominal repeat transmission / transmission may be further divided by the slot boundary or invalid OFDM symbols, resulting in one or more actual repeat transmissions.

[0129] The indication in the multi-TB scheduling DCI may be an explicit indication (e.g., a bit field in the DCI to indicate the number of TBs N and / or the number of repeated transmissions M) or an integrated indication, such as by an entry in a TDRA table (such a TDRA table may contain multiple entries specifying different combinations of TBs and number of repeated transmissions).

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

[0131] This is now further explained with reference to Figures 8c and 8d.

[0132] Specifically, Figure 8c shows an example of scheduling multiple TBs without transmission gaps. As can be seen, in the first slot of Figure 8c, a PDCCH including a multi-TB scheduling DCI is transmitted by the base station and / or received by the UE. The multi-TB scheduling DCI schedules four TBs in the third to sixth slots, respectively. In other words, the multi-TB scheduling DCI schedules four TBs such that there is no transmission gap between the four scheduled TBs. That is, the four TBs are scheduled to be transmitted in consecutive slots.

[0133] Figure 8d shows an example of scheduling multiple TBs with transmission gaps. Similar to Figure 8c, the multi-TB scheduling DCI is transmitted in the first slot. Specifically, starting from the third slot, four TBs are scheduled every other slot. That is, the first to fourth TBs are scheduled to be transmitted in slots #3, #5, #7, and #9, respectively. That is, the four TBs are scheduled with a transmission gap of one slot between consecutive TBs.

[0134] It should be noted that in general, different / multiple transmission gaps may be indicated by the multi-TB scheduling DCI, e.g., a first transmission gap may apply to two consecutive first transmissions of a TB, a second gap may apply to two consecutive further repeated transmissions of a TB, a third gap may apply to the first transmission of a TB and the subsequent further repeated transmissions, and / or a fourth gap may apply to the further repeated transmissions and the subsequent transmissions of a TB.

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

[0136] The number of TBs N and / or the number of repeated transmissions M may be implicitly indicated by the interleaving pattern. In other words, each interleaving pattern may be associated with the number of TBs N and / or the number of repeated transmissions M. That is, by indicating an interleaving pattern, the multi-TB scheduling DCI implicitly indicates the number of associated TBs N and / or the number of associated repeated transmissions M. Similarly, the transmission gaps may be fixed by the interleaving pattern, i.e., the interleaving pattern may be associated with a specific transmission gap. These associations may be generally fixed or dynamic, e.g., configurable via RRC.

[0137] However, the present invention is not limited thereto. In general, a multi-TB scheduling DCI may include an explicit indication of a transmission gap that the base station can determine and configure independently of the interleaving pattern indicated in the DCI, thereby increasing scheduling flexibility. This indication may be an explicit indication (e.g., a bit field in the DCI to indicate the gap) or a joint indication with the interleaving pattern, etc., referring to an entry in a TDRA table (such a TDRA table may contain multiple entries of the same interleaving pattern specifying different transmission gaps).

[0138] In general, the interleaving pattern may be selected from two or more predefined interleaving patterns, such as, but not limited to, a TB priority pattern and an RV priority pattern, as further described below. In other words, an indication in the multi-TB scheduling DCI indicating interleaving may indicate which of two or more predefined interleaving patterns is used for the scheduled TB (and scheduled further repeat transmissions, if applicable).

[0139] Some exemplary interleaving patterns will now be described with reference to Figures 8a to 8d.

[0140] Figure 8a shows TB scheduling with repeat transmissions according to a "TB priority pattern" in which TB transmissions (including repeat transmissions) are not interleaved. That is, Figure 8a shows an interleaving pattern with trivial interleaving of TBs. The TB priority interleaving pattern can be roughly described as follows: {TB0_RV0, TB0_RV2, TB0_RV3, TB0_RV1, TB1_RV0, TB1_RV2, TB1_RV3, TB1_RV1}

[0141] Here, the notation before "_" indicates a transport block, and the notation after "_" indicates a redundancy version. More specifically, as also shown in Figure 8a, the multi-TB scheduling DCI schedules the transmission of two TBs. Furthermore, for each of these two TBs, four repeated transmissions are scheduled. Therefore, each of the two scheduled TBs is transmitted four times (possibly coded differently). The transmission of the first TB is first scheduled in slots 3 to 6. Specifically, a redundancy version of "0" is transmitted in the third slot, a redundancy version of "2" is transmitted in the fourth slot, a redundancy version of "3" is transmitted in the fifth slot, and a redundancy version of "1" is transmitted in the third slot. In the example shown in Figure 8a, there is a one-slot transmission gap after the transmission of the first TB. After the transmission of the first TB and the transmission gap, the transmission of the second TB is scheduled in slots 8 to 11. The redundancy versions of the second TB are transmitted in the same order as the redundancy versions of the first TB.

[0142] Generally, in a TB priority pattern, TB transmissions (including repeat transmissions) may be performed consecutively (e.g., in consecutive slots), i.e., without any other scheduled TB transmissions / repeated transmissions between them. Generally, there may or may not be transmission gaps between TB transmissions. Furthermore, there may or may not be a transmission gap between the last transmission of one TB and the first transmission of another TB. Some or all of these transmission gaps may be the same or different from each other.

[0143] The TB priority pattern may enable high reliability and low latency in the transmission of the first TB. Utilizing the TB priority option may be particularly beneficial when the first TB has significantly higher priority and performance requirements than the second TB (and further TBs, if applicable).

[0144] 8b shows TB scheduling with repeat transmissions according to an "RV priority pattern" in which TB transmissions (including repeat transmissions) are interleaved. The RV priority interleaving pattern can be roughly described as follows: {TB0_RV0, TB1_RV0, TB0_RV2, TB1_RV2, TB0_RV3, TB1_RV3, TB0_RV1, TB1_RV1}

[0145] More specifically, as also shown in Figure 8b, the multi-TB scheduling DCI schedules the transmission of two TBs. Furthermore, for each of these two TBs, four repeated transmissions are scheduled. Thus, each of the two scheduled TBs is transmitted four times (possibly coded differently).

[0146] The transmission of the first TB is scheduled every other slot (slots #3, #5, #7, and #9) starting from the third slot. The transmission of the second TB is scheduled every other slot (slots #4, #6, #8, and #10) starting from the fourth slot. That is, the transmissions of the first and second slots are interleaved.

[0147] In the first transmission of each TB (slots #3 and #4), a redundancy version of "0" of the respective TB is transmitted; in the second transmission of each TB, i.e., the first further repeat transmission (slots #5 and #6), a redundancy version of "2" of the respective TB is transmitted; in the third transmission of each TB (slots #7 and #8), a redundancy version of "3" of the respective TB is transmitted; and in the fourth transmission of each TB (slots #9 and #10), a redundancy version of "1" of the respective TB is transmitted. In the example shown in Figure 8b, the TBs and further repeat transmissions are transmitted without any gaps between them.

[0148] In general, in an RV priority pattern, between two transmissions of a TB, there may be (e.g., one) transmission of a TB that is scheduled to be transmitted together. Redundancy versions of different TBs may be transmitted in the same order (which may be specified by the RV priority pattern).

[0149] The RV priority pattern can increase time diversity, which can increase reliability, especially in situations where frequency diversity is low. Generally, in the RV priority pattern, TB transmissions / repeated transmissions may be performed consecutively (e.g., in consecutive slots), i.e., without gaps between transmissions / repeated transmissions. However, gaps may exist between transmissions / repeated transmissions, which can further increase time diversity.

[0150] Figures 8c and 8d show further examples of interleaving patterns without repeated transmissions, where TBs are scheduled without gaps and with gaps, respectively, as already described above when describing transmission gaps between TBs.

[0151] It should be noted that time domain interleaving can also be used in interleave-division multiple-access (IDMA) to increase capacity.

[0152] <Consolidated Indication and TDRA Table> In general, the 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 repeated transmissions, 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 above points i) to iv).

[0153] For example, such an integration indication may be a parameter in the DCI or a field in the DCI. The integration indication may also refer to an entry in a time domain resource allocation (TDRA) table. Specifically, the integration indication may be an indication of an index (e.g., a row index) pointing to an entry (e.g., a row) in the TDRA table. That is, the integration indication may be indicated by a TDRA table with additional columns corresponding to one or more of the above parameters i) to vi). In other words, the TDRA table signaling framework may be enhanced to accommodate scheduling of multiple TBs, for example by extending an existing TDRA table with additional entries / rows / columns.

[0154] An example of a TDRA table for scheduling multiple TBs is shown below. [Table 6]

[0155] As shown in the example table above, a TDRA table for scheduling multiple TBs may include the following (corresponding to the last four rows of the example table above, respectively): i) for one or more (even each) row indexes, a row identifying or indicating the number N of TBs; ii) a row that identifies or indicates, for one or more (even each) row index, the number M of repeat transmissions; iii) for one or more (and even each) row index, a row identifying or indicating a transmission gap; and / or iv) A row that identifies or indicates an interleaving pattern for one or more (and even each) row index.

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

[0157] Specifically, the row index may be indicated by an indication in the multi-TB scheduling DCI, i.e., the row index may be an integrated indication in the multi-TB scheduling DCI indicating the scheduling of N TBs and one or more of parameters i) to iv).

[0158] The use of a joint indication of multiple parameters (e.g., the number of multiple TBs, the number of repeated transmissions M, the interleaving pattern, and the transmission gap) may enable scheduling of multiple TBs with no or minimal additional DCI overhead. Furthermore, the joint indication based on a TDRA table or the like may enable flexible allocation of time / frequency domain resources for transmission / reception of multiple TBs by a single DCI.

[0159] It should be noted that a TDRA table supporting multiple TB scheduling may be configured with / associated with a specific Search Space (SS) set or Bandwidth Part (BWP), i.e., there may be one or more TDRA tables supporting multiple TB scheduling and one or more TDRA tables not supporting multiple TB scheduling.

[0160] Configuration Grant (CG) and Semi-Persistent Scheduling (SPS) Framework In general, a UE (e.g., its processing circuitry) may, during operation, obtain an indication to activate a configuration grant (CG) or semi-persistent scheduling (SPS) from a multi-TB scheduling DCI. For example, an indication indicating scheduling of N TBs may be an indication to activate a CG / SPS. After obtaining the indication to activate a CG / SPS, the circuitry may, during operation, activate the CG or SPS according to the indication. The CG or SPS may indicate multiple transmission opportunities. The circuitry may, during operation, deactivate the CG or SPS after N transmission opportunities starting from receiving the multi-TB scheduling DCI. Note that the SPS and CG (especially "Type 2" CG) may be used to enable scheduling of multiple TBs in the DL and UL, respectively.

[0161] That is, the CG / SPS may be enhanced to enable scheduling of multiple TBs with or without repeat transmissions. In particular, in this case, the multi-TB scheduling DCI may simply be 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 repeat transmissions M, the interleaving pattern, and the transmission gap may be indicated by other means, for example, signaled in the RRC configuration by the CG / SPS. However, the present invention is not limited thereto, since the interleaving pattern and / or the transmission gap may or may not be indicated by the multi-TB scheduling DCI that activates the CG / SPS.

[0162] Generally, multiple transmission opportunities (e.g., time resources) can be configured in RRC (e.g., using the CG / SPS framework). Some of the multiple transmission opportunities may be selected by the control information of the CG / SPS trigger DCI. The remainder of some of the multiple transmission opportunities are released. For example, the CG / SPS DCI may include an explicit indication of the transmission opportunity selected from the configured transmission opportunities for the transmission / reception of the scheduled TB (and additional retransmissions if applicable). If there is only a trigger flag in the CG / SPS DCI, the number N of the scheduled TBs and / or the number of transmission opportunities may be configured via RRC for the triggered CG / SPS setting.

[0163] <The number N of transport blocks indicated by the CG / SPS trigger DCI> Generally, the number N of TBs can be indicated by the DCI that triggers / activates 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 N of TBs. In this case, the UE may automatically release CG / SPS after N transmission opportunities or after the actual transmission of the TBs N times. Alternatively, the UE may automatically release CG / SPS after the number of transmission opportunities equal to / corresponding to the number of scheduled transmissions including retransmissions, or after actually transmitting / receiving the scheduled TBs including retransmissions. Specifically, the UE / base station does not have to use all of the transmissions / retransmissions scheduled by the DCI that triggers / activates CG / SPS for actually transmitting the TB / retransmissions.

[0164] <The number N of transport blocks indicated / set by RRC> Generally, as already described above, the number N of transport blocks may be indicated via RRC.

[0165] Specifically, within a particular CG / SPS configuration, the number of TBs N or a timer may be configured by RRC. If a timer is used, the timer may start, for example, from the transmission of the first TB or from the transmission of the multi-TB scheduling DCI. If a CG / SPS configuration is triggered, periodic transmission is automatically released / terminated after the timer expires or after the number of TBs is transmitted. In other words, multiple CG / SPS configurations may be configured, and a CG / SPS trigger DCI may explicitly or implicitly indicate one of the configured CG / SPS configurations. For example, a CG / SPS trigger DCI may trigger that CG / SPS, and its time domain resource includes the slot in which the CG / SPS trigger DCI is transmitted. As a further example, if two or more CG / SPS configurations include the slot in which the CG / SPS trigger DCI is transmitted, the CG / SPS with a lower index or higher priority is triggered. The index and / or priority may be configured by RRC for the CG / SPS configuration, for example.

[0166] Figure 9 illustrates the automatic release when scheduling multiple TBs using the CG / SPS framework. Note that the interleaving pattern, transmission gaps, and numbers N and M are the same as in Figure 8a. Therefore, the same description will not be repeated. As shown in Figure 9, the CG / SPS is automatically released / deactivated after the transmission of the last scheduled TB (including scheduled repeat transmissions), i.e., after the transmission of the redundant version of "1" of the second TB (i.e., after slot #11, where #1 is the slot for transmitting the CG / SPS trigger DCI).

[0167] Scheduling multiple TBs with a single DCI using CG / SPS may be a simple and efficient solution because it uses the existing SPS / CG framework. Specifically, this approach may reduce the number of parameters that need to be introduced into the standard, thereby reducing the impact on the specifications. Furthermore, in contrast to the current SPS / CG framework, using CG / SPS for scheduling multiple TBs may enable the gNB to complete the scheduling of multiple TBs using only one DCI, rather than using two DCIs (one for SPS / CG activation and one for deactivation). This may eliminate the need for the UE to monitor the PDCCH for SPS / CG deactivation, thereby further saving power consumption for PDCCH monitoring.

[0168] In general, the PDCCH (Physical Downlink Control Channel) monitoring behavior of a UE may be adapted depending on the number N of TBs scheduled by the DCI.

[0169] In general, scheduling multiple TBs may enable further power savings by adapting accordingly. More specifically, scheduling multiple TBs may enable scheduling the same amount of resources and / or TBs with less DCI. Thus, PDCCH monitoring may be adapted to scheduling multiple TBs because more resources are scheduled to the UE at once. Such adaptation of PDCCH monitoring behavior may facilitate further reducing the UE's own power consumption, but may also be used to provide more scheduling opportunities to other UEs.

[0170] For example, multiple sets of the parameters "monitoringSlotPeriodicityAndOffset" and "monitoringSymbolsWithinSlot" can be configured. Meanwhile, a single-TB scheduling DCI may cause the UE to switch to a PDCCH monitoring opportunity specified by a first set of parameters, and a multi-TB scheduling DCI may cause the UE to switch to a PDCCH monitoring opportunity specified by a second set of parameters. If the UE is already using the first set of parameters when it receives the single-TB scheduling DCI, it may continue to use the first set of parameters. Similarly, if the UE is already using the second set of parameters when it receives the multi-TB scheduling DCI, it may continue to use the second set of parameters.

[0171] In other words, when receiving a single TB scheduling DCI and / or a multi-TB scheduling DCI, the UE may re-evaluate which of the two or more sets of parameters to use, or more generally, re-evaluate its PDCCH monitoring behavior. In general, one or both of the multi-TB scheduling DCI and the single TB scheduling DCI may trigger an adaptation / re-evaluation of the parameter sets.

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

[0173] For example, if the DCI is a single-TB scheduling DCI, the UE may determine to monitor a first set of PDCCH candidates. On the other hand, if the DCI is a multi-TB scheduling DCI, the UE may determine to monitor a second set of PDCCH candidates. In other words, the UE may determine whether to monitor the first or second set of PDCCH candidates. The second set of PDCCH candidates may be smaller than the first set of PDCCH candidates. Alternatively or additionally, the UE may determine to monitor the PDCCH less frequently when the DCI is a multi-TB scheduling DCI compared to when the DCI is a single-TB scheduling DCI. The UE may monitor a reduced number of PDCCH candidates or may perform monitoring less frequently for a predetermined period and / or until it receives another DCI (specifically, until it receives a single-TB scheduling DCI). Specifically, if it receives a multi-TB scheduling DCI, the UE may even decide to completely stop PDCCH monitoring for a predetermined period.

[0174] It should be noted that the embodiments of the present disclosure are applicable to scenarios with relatively long round trip times (RTT), for example, where the number of HARQ process IDs is small compared to the RTT, i.e., slot_length x "number of HARQ process IDs" <RTT This is also applicable and beneficial to non-terrestrial networks (NTNs) above 52.6 GHz because one DCI can schedule multiple slots with a single HARQ process ID.

[0175] Further Aspects According to a first aspect, there is provided a user equipment (UE). The UE comprises a transceiver and circuitry. In operation, the transceiver receives downlink control information (DCI) signaling. In operation, the circuitry obtains an indication from the DCI signaling. The indication indicates scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of: i) scheduling of repeated transmissions of the TBs M times, where M is equal to or greater than 1; ii) an interleaving pattern for the TBs; and iii) transmission gaps between the TBs.

[0176] According to a second aspect provided in addition to the first aspect, the N TBs carry different data from each other and / or each of the M repeated transmissions carries the same data as a corresponding TB among the N TBs.

[0177] According to a third aspect provided in addition to the first or second aspect, the indication indicating the scheduling of the N TBs may jointly indicate the scheduling of the N TBs and at least one of the scheduling of the M repeated transmissions, the interleaving pattern, and the transmission gap.

[0178] According to a fourth aspect provided in addition to the third aspect, the integration indication may be one of a parameter in the DCI or a field in the DCI and a reference to an entry in a time domain resource allocation (TDRA) table.

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

[0180] According to a sixth aspect provided in addition to one of the first to fifth aspects, the transceiver, when operating, receives radio resource control (RRC) signaling, and the circuit, when operating, obtains an indication of the number N of TBs from the RRC signaling.

[0181] According to a seventh aspect provided in addition to one of the fifth or sixth aspects, when the circuit, in operation, receives from the DCI an indication to activate a configuration grant (CG) or semi-persistent scheduling (SPS) indicating multiple transmission opportunities, the circuit, in operation, deactivates the CG or the SPS after N transmission opportunities starting from receiving the DCI.

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

[0183] According to a ninth aspect, there is provided a scheduling device. The scheduling device includes a circuit and a transceiver. In operation, the circuit generates downlink control information (DCI) signaling, the DCI signaling including an indication to the UE of scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of: i) scheduling of repeated transmissions of the TBs M times, where M is equal to or greater than 1; ii) an interleaving pattern for the TBs; and iii) transmission gaps between the TBs. In operation, the transceiver transmits the DCI signaling to the user equipment (UE).

[0184] According to a tenth aspect, there is provided a method for a user equipment (UE), the method comprising: receiving downlink control information (DCI) signaling; and obtaining an indication from the DCI signaling, the indication indicating at least one of scheduling of N transport blocks (TBs), where N is an integer greater than 1, and scheduling of M repeated transmissions of the TBs, where M is equal to or greater than 1, an interleaving pattern for the TBs, and a transmission gap between the TBs.

[0185] According to an eleventh aspect, there is provided a method for a scheduling node, the method comprising: generating downlink control information (DCI) signaling; and transmitting the DCI signaling to a user equipment (UE), the DCI signaling including indications to the UE of scheduling of N transport blocks (TBs), where N is an integer greater than 1, and at least one of scheduling of M repeated transmissions of the TBs, where M is equal to or greater than 1, an interleaving pattern for the TBs, and transmission gaps between the TBs.

[0186] Hardware and Software Implementations of the Disclosure The present disclosure may be realized by software, hardware, or software interlocked with hardware. Each functional block used in the description of each embodiment above may be partially or entirely realized by an LSI (Large Scale Integration) such as an integrated circuit (IC), and each process described in each embodiment may be partially or entirely controlled by the same LSI or a combination of LSIs. The LSI may be formed as an individual chip, or a single chip may be formed to include some or all of the functional blocks. The LSI may also include data input / output devices coupled thereto. Here, LSI may be referred to as an IC, system LSI, super LSI, or ultra LSI depending on the degree of integration. However, the technology for realizing an integrated circuit is not limited to LSI, and may be realized using dedicated circuits, general-purpose processors, or application-specific processors. Furthermore, a field programmable gate array (FPGA), which allows reconfiguration of the connections and settings of circuit cells arranged within the LSI or a reconfigurable processor that can be programmed after fabrication, may also be used. The present disclosure may be realized as digital processing or analog processing. As a result of advances in semiconductor technology and other derivative technologies, if future integrated circuit technologies replace LSI, functional blocks can be integrated using future integrated circuit technologies. Biotechnology is also applicable.

[0187] The present disclosure may be implemented by any type of apparatus, device or system having communication capabilities, referred to as a communications apparatus.

[0188] A communication device may include a transceiver and processing / control circuitry. The transceiver may include and / or function as a receiver and a transmitter. The transceiver as a transmitter and receiver may include a Radio Frequency (RF) module including an amplifier, an RF modulator / demodulator, etc., and one or more antennas.

[0189] Some non-limiting examples of such communication devices include telephones (e.g., mobile (cell) phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), 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 remote medical) devices, and vehicles (e.g., automobiles, airplanes, ships) that provide communication capabilities, and various combinations thereof.

[0190] The communications apparatus is not limited to being portable or mobile, but may include any type of apparatus, device or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines and any other "thing" in an "Internet of Things (IoT)" network.

[0191] Communications may include, for example, exchanging data via cellular systems, wireless LAN systems, satellite systems, and the like, as well as various combinations thereof.

[0192] A communications apparatus may include devices such as a controller or a sensor coupled to the communications device to perform the communications functions described in this disclosure. For example, a communications apparatus may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications apparatus.

[0193] Communications equipment may also include infrastructure facilities such as base stations, access points, and any other equipment, device, or system that communicates with or controls equipment such as those in the above non-limiting examples.

[0194] Furthermore, various embodiments may also be implemented using software modules executed by a processor or directly in hardware. A combination of software modules and hardware implementation may also be possible. The software modules may be stored in any type of computer-readable storage medium. Specifically, according to another implementation, a non-transitory computer-readable storage medium is provided. The storage 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.

[0195] By way of example, and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but instead cover non-transitory tangible storage media. As used herein, disk and disc as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically while discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0196] It should be noted that individual features of different embodiments may be the subject of other embodiments, individually or in any combination. As shown in the specific embodiments, it will be understood by those skilled in the art that numerous variations and / or modifications may be made to the present disclosure. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive.

Claims

1. a transceiver configured, in operation, to receive downlink control information (DCI) signaling; a circuit for, during operation, obtaining an indication from the DCI signaling; A user equipment (UE) comprising: The indication is scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; indicates, the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. User Equipment (UE).

2. The N TBs carry different data; and / or each of the M repeated transmissions carries the same data as a corresponding one of the N TBs; 2. A user equipment (UE) according to claim 1.

3. In operation, the transceiver receives radio resource control (RRC) signaling before receiving the DCI signaling; and in operation, the circuitry obtains a second indication from the RRC signaling indicating the number N of TBs.

2. A user equipment (UE) according to claim 1.

4. When the circuitry, in operation, obtains from the DCI signaling an indication to activate a configuration grant (CG) or semi-persistent scheduling (SPS) indicating multiple transmission opportunities, the circuitry, in operation, deactivates the CG or the SPS after N transmission opportunities starting from receiving the DCI signaling.

4. A user equipment (UE) according to claim 3.

5. In operation, the circuitry performs a physical downlink control channel (PDCCH) monitoring operation for the UE in response to the number N of TBs.

2. A user equipment (UE) according to claim 1.

6. a circuit for generating downlink control information (DCI) signaling in operation; a transceiver configured to, in operation, transmit the DCI signaling to a user equipment (UE); A scheduling device comprising: The DCI signaling may include: scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; Including an indication of the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. Scheduling device.

7. receiving downlink control information (DCI) signaling; obtaining an indication from the DCI signaling; 1. A method for a user equipment (UE), comprising: The indication is scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; indicates, the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. method.

8. generating downlink control information (DCI) signaling; transmitting the DCI signaling to a user equipment (UE); A method for a scheduling device, comprising: The DCI signaling may include: scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; Including an indication of the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. method.

9. 1. An integrated circuit that, in operation, controls processing of a user equipment (UE), comprising: The process comprises: receiving downlink control information (DCI) signaling; obtaining an indication from the DCI signaling; The indication is scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; indicates, the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. Integrated circuit.

10. an integrated circuit that, in operation, controls the operation of a scheduling apparatus, The process comprises: generating downlink control information (DCI) signaling; transmitting the DCI signaling to a user equipment (UE); The DCI signaling may include: scheduling N transport blocks (TBs), where N is an integer greater than 1; a transmission gap between the TBs; scheduling M repeated transmissions of said TB, where M is 1 or greater; At least one of the interleaving patterns of the TB; Including an indication of the indication is a reference to at least one entry in a time domain resource allocation (TDRA) list; The number N of TBs is related to the number of the at least one entry in the TDRA list. Integrated circuit.

Images