User equipment and method for receiving data

Abstract

The invention provides user equipment and a method for receiving data. The user equipment includes: a transceiver receiving data after receiving scheduling information; and circuitry to determine that a limit is not applied to the TDRA table in accordance with the minimum scheduling gap, using a default time domain resource allocation TDRA.

Description

[0001] This application is a divisional application of the invention patent application with the application date of September 28, 2020, application number: 202080069672.1, and invention name: "Apparatus and method for cross-time slot scheduling adaptation". Technical Field

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

[0003] Currently, the 3rd Generation Partnership Project (3GPP) is working on the technical specifications for the next generation of cellular technology, also known as the fifth generation (5G).

[0004] One goal is to provide a single technical framework that addresses all use cases, requirements, and deployment scenarios (e.g., see Section 6 of TR 38.913 Version 15.0.0), including at least enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). For example, eMBB deployment scenarios may include indoor hotspots, dense urban areas, suburban areas, urban macro sites, and highways; URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis, and treatment), real-time control of vehicles, and wide-area monitoring and control systems for smart grids; mMTC deployment scenarios may include scenarios with a large number of devices (such as smart wearables and sensor networks) with non-time-critical data transmission. Services eMBB and URLLC are similar in that they both require very wide bandwidth, but the difference is that URLLC services may preferably require ultra-low latency.

[0005] The second goal is to achieve forward compatibility. Backward compatibility to Long Term Evolution (LTE, LTE-A) cellular systems is not required, which facilitates the introduction of completely new system designs and / or novel features. Summary of the invention

[0006] One non-limiting and exemplary embodiment facilitates providing improved procedures that facilitate conserving UE power, including procedures involving cross-slot scheduling.

[0007] In an embodiment, the technology disclosed herein features a user equipment, including: a transceiver that receives data after receiving scheduling information; and a circuit that determines not to apply restrictions to the TDRA table based on a minimum scheduling gap when using a default time domain resource allocation TDRA.

[0008] In an embodiment, the technology disclosed herein features a method for receiving data, the method comprising: determining not to apply restrictions to a TDRA table according to a minimum scheduling gap when using a default time domain resource allocation TDRA; and receiving data after receiving scheduling information.

[0009] In an embodiment, the technology disclosed herein features a transceiver device that includes a transceiver that receives data after receiving a scheduling grant; and a circuit that determines whether to apply restrictions to a time domain resource allocation TDRA table based on a minimum scheduling gap, wherein the determination includes a determination of whether a common TDRA table is configured.

[0010] In an embodiment, the technology disclosed herein features a transceiver device that includes a transceiver that transmits data after receiving a scheduling grant; and a circuit that determines whether to apply a restriction to a time domain resource allocation TDRA table based on a minimum scheduling gap, wherein the TDRA table includes multiple entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, the scheduling gap indicator indicating a gap between reception of the scheduling grant and scheduled resources, and the determination includes comparing the minimum scheduling gap and the scheduling gap included in the TDRA table.

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

[0012] Additional benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually by various embodiments and features of the specification and drawings, and various embodiments and features do not need to be fully provided in order to obtain one or more of such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings and figures.

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

[0015] Figure 2 is a schematic diagram showing the division of functions between NG-RAN and 5GC;

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

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

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

[0019] Figure 6 is a schematic diagram showing an exemplary TDRA table;

[0020] Figure 7 is a schematic diagram showing cross-time slot scheduling;

[0021] Figure 8 is a block diagram showing a transceiver device and a scheduling device;

[0022] Fig. 9 is a diagram illustrating exemplary limitations of an exemplary TDRA table according to a minimum scheduling gap. DETAILED DESCRIPTION

[0023] 5G NR system architecture and protocol stack

[0024] 3GPP has been working on the next version of 5th generation cellular technology, or 5G for short, including the development of new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which allowed trials and commercial deployment of smartphones compliant with the 5G NR standard to continue.

[0025] Among other things, the overall system architecture assumes that the NG-RAN (Next Generation Radio Access Network) including the gNBs provides NG Radio Access User Plane (SDAP / PDCP / RLC / MAC / PHY) and Control Plane (RRC) protocol terminations to the UE. The gNBs are connected to each other via Xn interfaces. The gNBs are also connected to the NGC (Next Generation Core) via Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g. a specific core entity that implements the AMF) via the NG-C interface, and to the UPF (User Plane Function) (e.g. a specific core entity that implements the UPF) via the NG-U interface. Figure 1 The NG-RAN architecture is shown in (see, for example, 3GPP TS 38.300 v15.6.0 section 4).

[0026] A variety of different deployment scenarios can be supported (see, e.g., 3GPP TR 38.801 v14.0.0). For example, a non-centralized deployment scenario is shown herein (see, e.g., Section 5.2 of TR 38.801; a centralized deployment is shown in Section 5.4) where base stations supporting 5G NR can be deployed. The new eNB for NR 5G may be exemplarily referred to as a gNB. The eLTE eNB is an evolution of the eNB that supports connections to the EPC (Evolved Packet Core) and the NGC (Next Generation Core).

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

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

[0029] 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 handles the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for the transmission of a specific transport channel, and each transport channel is mapped to a corresponding physical channel. One physical channel is the PRACH (Physical Random Access Channel) used for random access.

[0030] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), which have diverse requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user-experienced data rates that are three times higher than those provided by International Mobile Telecommunications-Advanced (IMT-Advanced). On the other hand, in the case of URLLC, there are requirements for ultra-low latency (0.5ms for user plane latency for UL and DL each) and high reliability (1-10 Mbps within 1ms). -5 ) puts forward more stringent requirements. Finally, mMTC may preferably require high connection density (1,000,000 devices / km in an urban environment) 2 ), large coverage in harsh environments, and extremely long battery life for low-cost devices (15 years).

[0031] Therefore, an OFDM parameter set (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is applicable to one use case may not be applicable to another use case. For example, a low-latency service may preferably require a shorter symbol duration (and therefore a larger subcarrier spacing) and / or fewer symbols per scheduling interval (also known as TTI) than an mMTC service. In addition, a deployment scenario with a large channel delay spread may preferably require a longer CP duration than a scenario with a small delay spread. The subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one subcarrier spacing value. Correspondingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, ... are currently being considered. The symbol duration Tu and the subcarrier spacing Δf are directly related by the formula Δf=1 / Tu. In a similar manner as in LTE systems, the term "resource element" can be used to represent the smallest resource unit consisting of one subcarrier for the length of one OFDM / SC-FDMA symbol.

[0032] In the new radio system 5G-NR, for each numerology set and carrier, a resource grid of subcarriers and OFDM symbols is defined for uplink and downlink respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211 v15.6.0).

[0033] Division of 5G NR functions between NG-RAN and 5GC

[0034] Figure 2The division of functions between NG-RAN and 5GC is shown. The NG-RAN logical node is gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF.

[0035] Specifically, gNB and ng-eNB host the following main functions:

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

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

[0038] - Selection of the AMF at UE attach when the route to the AMF cannot be determined based on the information provided by the UE;

[0039] - Routing of user plane data towards UPF;

[0040] - Routing of control plane information towards the AMF;

[0041] -Connection establishment and release;

[0042] - Scheduling and transmission of paging messages;

[0043] - Scheduling and transmission of system broadcast information (originating from AMF or OAM);

[0044] -Mobility and scheduling measurements and measurement reporting configuration;

[0045] -Transport level packet marking in uplink;

[0046] -Session management;

[0047] - Network slicing support;

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

[0049] -Support UE in RRC_INACTIVE state;

[0050] -NAS message distribution function;

[0051] - Radio access network sharing;

[0052] -Dual connection;

[0053] - Tight interworking between NR and E-UTRA.

[0054] The access and mobility management function (AMF) has the following main functions:

[0055] - Non-Access Stratum (NAS) signalling termination;

[0056] -NAS signaling security;

[0057] -Access layer (AS) security control;

[0058] - Core Network (CN) inter-node signalling for mobility between 3GPP access networks;

[0059] - Idle mode UE reachability (including control and execution of paging retransmissions);

[0060] -Registration area management;

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

[0062] -Access authentication;

[0063] -Access authorization, including roaming permission checks;

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

[0065] - Network slicing support;

[0066] -Session Management Function (SMF) selection.

[0067] In addition, the User Plane Function (UPF) has the following main functions:

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

[0069] - External PDU session points interconnected to the data network;

[0070] -Packet routing & forwarding;

[0071] -Packet inspection and user plane part of policy rule enforcement;

[0072] -Business volume usage report;

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

[0074] -Support branching points for multi-host PDU sessions;

[0075] - QoS processing in the user plane, such as packet filtering, gating, UL / DL rate enforcement;

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

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

[0078] Finally, the Session Management Function (SMF) has the following main functions:

[0079] -Session management;

[0080] -UE IP address allocation and management;

[0081] -Selection and control of UP function;

[0082] -Configure traffic steering at the User Plane Function (UPF) to route traffic to the correct destination;

[0083] -Control some policy enforcement and QoS;

[0084] - Downlink data notification.

[0085] RRC connection establishment and reconfiguration procedures

[0086] Figure 3 Some interactions between the UE, gNB and AMF (5GC entity) are shown for the NAS part in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED (see TS 38.300v15.6.0).

[0087] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. Specifically, the transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities, and UE security capabilities, etc.) and sending it to the gNB along with the INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. Afterwards, the gNB performs reconfiguration to establish Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB) by sending an RRCReconfiguration message to the UE and the gNB receiving an RRCReconfigurationComplete message from the UE as a response. For a signaling-only connection, the steps related to RRCReconfiguration are skipped as SRB2 and DRB are not established. Finally, the gNB notifies the AMF that the establishment process is complete with the INITIALCONTEXT SETUP RESPONSE.

[0088] Therefore, in the present disclosure, an entity (e.g., AMF, SMF, etc.) of a fifth generation core (5GC) is provided, which includes a control circuit for establishing a next generation (NG) connection with a gNodeB, and a transmitter, which sends an initial context establishment message to the gNodeB via the NG connection to cause a signaling radio bearer to be established between the gNodeB and a user equipment (UE). Specifically, the gNodeB sends a radio resource control (RRC) signaling containing a resource allocation configuration information element to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0089] IMT usage scenarios in 2020 and beyond

[0090] Figure 4 Some use cases for 5G NR are shown. In the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are being considered that have been envisioned to support the wide variety of services and applications of IMT-2020. The specifications for enhanced mobile broadband (eMBB) Phase 1 have been completed. In addition to further extending eMBB support, current and future work will involve the standardization of ultra-reliable low-latency communications (URLLC) and massive machine-type communications. Figure 4 Some examples of envisaged usage scenarios for IMT for 2020 and beyond are shown.

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

[0092] From RAN1's ​​perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability includes defining a separate CQI table for URLLC, more compact DCI formats, repeated PDCCH, etc. However, as NR becomes more stable and developed, the scope can be expanded to achieve ultra-reliability (a key requirement for NR URLLC). Specific use cases for NR URLLC in Release 15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0093] In addition, the technical enhancements targeted by NR URLLC are aimed at latency improvement and reliability improvement. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, grant-free (configured grant) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means that the transmission for which resources have been allocated is stopped, and the allocated resources are used for another transmission requested later but with lower latency / higher priority requirements. Therefore, the already authorized transmission is preempted by the later transmission. Preemption is applicable independently of the specific service type. For example, a transmission of service type A (URLLC) can be preempted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table with a target BLER of 1E-5.

[0094] The mMTC (massive machine type communications) use case is characterized by a very large number of connected devices that typically send relatively small amounts of non-latency sensitive data. The devices need to be low cost and have very long battery life. Utilizing very narrow bandwidth portions is a possible solution from the NR point of view, which saves power and extends battery life from the UE point of view.

[0095] As mentioned above, the scope of reliability in NR is expected to become wider. High reliability or ultra-reliability is a key requirement for all situations and is particularly necessary for URLLC and mMTC. From a radio perspective and a network perspective, some mechanisms can be considered to improve reliability. In general, there are some key potential areas that can help improve reliability. Among these areas are compact control channel information, data / control channel repetition, and diversity in frequency, time and / or space domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0096] For NR URLLC, further use cases have been identified with more stringent requirements, such as factory automation, transportation and power distribution. The more stringent requirements are higher reliability (up to 10 -6 The main features of the technology are high-speed cellular networks, high-speed wireless communications (LTE), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few μs (where this value can be one μs or a few μs, depending on the frequency range), and short latencies on the order of 0.5 to 1 ms, in particular a target user plane latency of 0.5 ms, depending on the use case.

[0097] Furthermore, for NR URLLC, several technical enhancements from a physical layer perspective have been identified. Among these are PDCCH enhancements related to compact DCI, PDCCH (Physical Downlink Control Channel) repetition, increased PDCCH monitoring. Furthermore, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements are also identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a slot (a slot including fourteen symbols).

[0098] QoS Control

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

[0100] 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) together with the PDU Session, and may subsequently configure additional DRBs for the QoS flows of that PDU Session (when to do so is up to the NG-RAN), e.g. as referenced above Figure 3 As shown in Figure 1. NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in UE and NG-RAN associate UL and DL QoS flows with DRBs.

[0101] Figure 5 The 5G NR non-roaming reference architecture is shown (see TS 23.501 v16.1.0 section 4.23). Figure 4 The application function (AF) described in the example (e.g., an external application server hosting 5G services) interacts with the 3GPP core network to provide services, such as supporting the impact of applications on traffic routing, accessing the network exposure function (NEF), or interacting with the policy framework for policy control (see Policy Control Function (PCF)) for example, QoS control. Based on the operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that are not allowed by the operator to directly access network functions interact with related network functions using an external exposure framework via NEF.

[0102] Figure 5 Other functional units of the 5G architecture are shown, 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), such as operator services, Internet access or third-party services.

[0103] In LTE and NR, a terminal refers to a user equipment (UE). This can be a mobile device such as a wireless phone, a smart phone, a tablet computer, or a USB (Universal Serial Bus) stick that has the functionality of a user equipment. However, the term mobile device is not limited to this, and generally, a relay can also have the functionality of such a mobile device, and a mobile device can also work as a relay.

[0104] Downlink control channel monitoring, PDCCH, DCI

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

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

[0107] Paging message monitoring function,

[0108] System information collection function,

[0109] Signaling monitoring operation of the Disconnect Receive (DRX) function,

[0110] Inactivity monitoring operation of the Disconnect Receive (DRX) function,

[0111] · Random access response reception of the random access function,

[0112] · Reordering function of the Packet Data Convergence Protocol (PDCP) layer.

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

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

[0115] The DCI format represents a predetermined format in which corresponding information is formed and sent. Specifically, DCI formats 0_1 and 1_1 are used to schedule PUSCH and PDSCH in a cell, respectively.

[0116] Power saving enhancement

[0117] It is critical to study UE power consumption to ensure that UE power efficiency for 5G NR UEs can be better than that for LTE, and to identify and adopt techniques and designs for improvement. 3GPP is currently studying how to save UE power considering latency and performance in NR systems. For example, power saving signals / channels / procedures are used to trigger adaptation of UE power consumption characteristics. This may involve reducing UE power consumption associated with UE paging procedures.

[0118] Cross-slot scheduling

[0119] Cross-slot scheduling has been envisioned in 3GPP RAN1 study items (SI) and work items (WI) because it can promote power savings. One of the main goals is to specify a process for cross-slot scheduling so that communication devices can take advantage of power saving techniques. The present disclosure provides a more efficient cross-scheduling framework that promotes options for power savings for some communication devices.

[0120] For scheduling purposes, a communication device such as a user equipment (UE) may be informed in downlink control information (DCI), which is received by the UE in a physical downlink control channel (PDCCH), of the resources on which it (i.e., the UE itself) will send / receive data. For example, in the case where the UE is to receive data, the DCI may include a corresponding indication of resources in a physical downlink shared channel (PDSCH), and / or in the case where the UE is to send data, the DCI may include a corresponding indication of resources in a physical uplink shared channel (PUSCH). Such an indication may indicate the location of the resource in the frequency domain and / or time domain, and / or may indicate the length in symbols, as described in more detail below. In addition to this, the DCI may provide further transmission parameters, such as modulation and coding scheme (MCS) beamforming / precoding or other multiple output multiple input (MIMO) parameters. The PDCCH is transmitted to the communication device from a transmitter in a network (access) node such as a base station. In order to receive the PDCCH, the communication device usually has to monitor certain resources called search space or CORESET (control resource set). Monitoring means blind decoding to find out if there is control information directed to the monitoring communication device. This is achieved for example by providing (by the scheduling node) a cyclic redundancy check for the control information, which is scrambled with the identity of the communication device to which the control information is directed.

[0121] In LTE, the concept of CORESET is not explicitly proposed. Instead, downlink control signaling in LTE uses the full carrier bandwidth. This is called a control region in LTE. A more flexible structure is used in NR.

[0122] CORESET is a set of physical resources (i.e., a specific area on the NR downlink resource grid) and a set of parameters for carrying PDCCH / DCI. It is equivalent to the LTE PDCCH area (the first 1, 2, 3, 4 OFDM symbols in a subframe). However, in the LTE PDCCH area, the PDCCH always extends across the entire channel bandwidth, while the NR CORESET area is limited to a specific area in the frequency domain.

[0123] A CORESET may appear anywhere within a timeslot and anywhere in the frequency range of a carrier. However, a device is not expected to process a CORESET outside of its active BWP.

[0124] The first CORESET (CORESET 0) is provided by the Master Information Block (MIB) as part of the configuration of the initial BWP to be able to receive system information and additional configuration information from the network. After the connection is established, in addition to using RRC signaling, a device can be configured with multiple, possibly overlapping CORESETs.

[0125] The network can define a common control region and a UE-specific control region. In NR, the number of CORESETs is limited to 3 per BWP, including both common and UE-specific CORESETs. A common CORESET is shared by multiple UEs in a cell, so for this configuration, the network takes care to align with all UEs.

[0126] Each search space is a set of control channel elements at different aggregation levels, and there is a mapping between CORESETs and search spaces. A CORESET may have multiple search spaces in which a UE attempts blind decoding.

[0127] For example, as specified in Release 15 (NR), scheduling timing (e.g., scheduling for the above-mentioned resources) can be indicated within the DCI by using a time domain resource allocation (TDRA) table. Specifically, the UE can be informed of the allocated resources by indicating an entry (typically a row in the table) of the TDRA table in the DCI, for example, by signaling the entry (row) index. The term "table" is used as a logical term in this document because the TDRA entry can be generalized to the table in the standard specification. However, it is noted that the present disclosure is not limited to any particular physical storage organization, and the TDRA table can be implemented in any way as a collection of entries associated with corresponding entry indices.

[0128] Figure 6 is a schematic diagram showing an exemplary TDRA table. The TDRA table includes columns specifying row indices, which mark entries (rows of the table) including values ​​for each column. In this exemplary TDRA table, there are columns specifying dmrs-TypeA-Position, columns specifying PDSCH mapping types, columns specifying K0 values ​​(ie, scheduling gaps), columns specifying S values, and / or columns specifying L values. The DCI indication of a row of the TDRA table (a value of the row index) therefore corresponds to an indication of a combination of specific values ​​of dmrs-TypeA-Position, PDSCH mapping type, K0 value, S value, and / or L value.

[0129] In this example, DMRS-TypeA-Position is a parameter related to the location of the demodulation reference signal. This parameter is specified by another signaling parameter. Based on whether the parameter value is 2 or 3, the row index refers to a slightly different time domain resource allocation. The parameters DMRS-TypeA-Position and PDSCH mapping type are of no further importance to this disclosure; details can be found in the NR standard specifications. Typically, the TDRA table may include a reference Figure 6For this exemplary downlink TDRA table, the actual resource allocation is provided by parameters K0, S and L. In NR, there is a set of TDRA tables for downlink resource allocation, Figure 6 The TDRA table is one of them. In addition, there is a set of TDRA tables for uplink resource allocation, which is different from the set of downlink tables. In the case of the uplink TDRA table, the three parameters that specify the resource allocation (resource grant) are K2, S and L. Note that the present disclosure can be easily used for NRs including the currently defined tables, but is not limited to them. It can also be applied to the sidelink; it can be applied to different tables and even to resource allocations organized (signaled) in a different way.

[0130] The K0 value indicated in the DCI by the TDRA table row index indicates the gap between the time slot of the PDCCH and the time slot of the PDSCH in terms of time slots. Here, the time slot of the PDCCH is the time slot in which the DCI indicating the corresponding K0 is received, hereinafter also referred to as a scheduling time slot or a time slot carrying scheduling information or a time slot carrying a scheduling authorization. In addition, the time slot of the PDSCH may be a time slot (or the first / starting time slot) in which the scheduled resources are located, for example, a time slot in which data is to be sent / received. In other words, K0 may indicate the relative position (in the time domain) of the time slot including the resources scheduled for reception / transmission relative to a reference time slot, and the reference time slot may be the time slot of the DCI indicating the K0. More specifically, K0 may indicate the size or relative position of the gap in terms of time slots / in units of time slots. Note that a specific value of K0 (for example, in Figure 3 The value zero in the case of the table shown) may indicate that there is no gap and that the resource on which data is to be sent / received is located in the same slot as the DCI indicating K0. Furthermore, this is merely an example, and in general, the scheduling gap may be indicated as including or excluding the first slot (PDCCH) slot and / or the slot where the allocated resources start (the first PDSCH slot, also referred to as a resource slot or a scheduling slot). In general, the scheduling gap (denoted as K0 for downlink and K2 for uplink in NR) specifies the gap (time interval) between the scheduled resources and the scheduled resources.

[0131] In this disclosure, the terms "time slot" and "time slot" are generally used interchangeably. Generally, in this disclosure, a time slot refers to a time domain resource. In the case of NR, the time interval corresponding to a time slot depends on a parameter set, which is a combination of symbol duration, subcarrier spacing and cyclic prefix. A time slot consists of a specified number of symbols, which can be one or more. A specified number of time slots forms a subframe, and multiple subframes can form a radio frame. The term "specified" refers to the fact that both the UE and the gNB are aware of it. This can be achieved by signaling such a configuration in advance (i.e., before starting the scheduling process or together with the scheduling process), some parameters of the resources provided by the system may also be fixed and given by the standard.

[0132] Note further that the case of UL grants in DCI is similar to the case of DL grants described above. However, the scheduled resources are in PUSCH (instead of PDSCH), and the number indicating the gap is usually expressed as K2 (instead of K0). In this disclosure, K will be used to refer to any of K0, K2, or K for other types of links (such as sidelinks).

[0133] Furthermore, the S value indicated in the DCI may indicate the position of the starting symbol of the scheduled resource in the relevant time slot (which is the time slot in which the scheduled resource is to be received / transmitted, given by K0 / K2).

[0134] Finally, the L value indicated in the DCI may indicate the length of the PDSCH / PUSCH in symbols / symbols and / or the length of the scheduled resources in symbols / symbols. Figure 3 All entries in the TDRA table specify a K0 value of zero, but typically the TDRA table includes entries with different (integer) K0 values. For example, one entry of the TDRA table may correspond to a K0 value of 1, while another entry of the same TDRA table may correspond to a K0 value of 2. The possibility of non-zero K values ​​allows cross-slot scheduling, which refers to the case where the DCI that schedules a resource and the corresponding resource scheduled in the DCI are located in different time slots. In general, cross-slot scheduling can facilitate providing several advantages in terms of power savings.

[0135] For example, cross-slot scheduling can save power by relaxing the PDCCH processing timeline, for example, because the UE may not be required to decode the PDCCH as quickly as in the same-slot scheduling case (where the DCI that schedules the resources and the corresponding resources scheduled in the DCI are located in the same slot). In addition, cross-slot scheduling can allow for late PDSCH buffering. Unlike same-slot scheduling, in the case of cross-slot scheduling, the UE may not have to buffer all symbols after receiving the PDCCH until it decodes the PDCCH and realizes where the scheduled resources are actually located.

[0136] Specifically, when the UE knows the minimum (scheduled) gap between the PDCCH and the scheduled PDSCH, i.e., knows the minimum K that can be indicated in the DCI / PDCCH, the UE can skip PDSCH buffering in at least the current slot (e.g., the slot in which the PDCCH is received) and the next K-1 slots. In addition, the cross-slot scheduling potential can allow more micro-sleep cycles in the time interval, especially when the PDCCH is not scheduled until the scheduled resources are received.

[0137] This is Figure 7 It is shown in Figure 7 is a schematic diagram illustrating cross-slot scheduling, which shows the case where the minimum K value is 2 (more precisely, K0 = 2 in the figure). If the UE knows the minimum K, it does not need to monitor the PDCCH during the remaining time slots #n+2 and time slots #n+3, nor does it need to perform measurements during these time slots, nor does it need to buffer received data (PDSCH). The UE may choose to enter micro-sleep during the remainder of time slots #n+2 and / or time slots #n+3 in order to save power. However, please note that not all UEs must implement and / or adopt power saving. The provision of K increases the flexibility and opportunity for power saving, but it is not specified.

[0138] Figure 7 is an example based on the current NR specification. It shows a specific case where the PDCCH is transmitted in the entire first BWP, but resources are scheduled only in a subset of the physical resource blocks (PRBs) of the bandwidth part (BWP). Note that Figure 7 It can also be applied to the case where the BWP concept is not adopted, that is, the entire bandwidth is always allocable. A PRB refers to a resource unit with a predetermined number of subcarriers and a certain number of symbols of a certain parameter set.

[0139] In the current Release 15 NR, the TDRA table for each configuration is signaled within the configuration (PDSCH-Config) related to the PDSCH on the RRC layer, which may be within a specific container belonging to a bandwidth part ((BWP)-downlink dedicated). Therefore, if the TDRA table is a higher layer configuration, the TDRA table may be BWP specific. For example, a communication device such as a UE may use a default table, or may apply a higher layer configured pdsch-time domain allocation list (pdsch-TimeDomainAllocationList) in pdsch-ConfigCommon or pdsch-Config. However, this is only one possible detailed example of the interaction between the TDRA configuration and the BWP concept of NR. The present invention does not presuppose the adoption of a BWP and is not limited to resource allocation using a TDRA table.

[0140] RRC (Radio Resource Control) signaling is used by gNB (gNodeB, an exemplary name for a base station in NR corresponding to eNodeB (enhanced NodeB) of LTE (Long Term Evolution)) to semi-statically or statically configure the parameters of the radio access bearers and other parameters in the communication equipment (UE). As defined in clause 4.4.5 of TS 38.211 V15.0.0 (2017-12), a bandwidth part (or carrier bandwidth part) is a contiguous set of physical resource blocks as defined in clause 4.4.4.3 selected from a contiguous subset of common resource blocks defined in clause 4.4.4.2 for a given parameter set on a given carrier. In the specification TS 38.211 V15.0.0 it is defined that a UE can be configured with up to four carrier bandwidth parts in the downlink, where a single downlink carrier bandwidth part is active at a given time. The UE is not expected to receive PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), CSI-RS (Downlink Reference Signal for Channel State Information Estimation) or TRS (Tracking Reference Signal for fine time and frequency tracking of the channel) outside the active bandwidth part.

[0141] It is further defined in the specification that a UE can be configured with up to four carrier bandwidth parts in the uplink, where a single uplink carrier bandwidth part is active at a given time. If the UE is configured with a supplementary uplink, the UE can also be configured with up to four carrier bandwidth parts in the supplementary uplink, where a single supplementary uplink carrier bandwidth part is active at a given time. The UE should not send PUSCH or PUCCH outside the active bandwidth part. The parameter set is defined by the subcarrier spacing and the cyclic prefix (CP). A resource block is typically defined as 12 consecutive subcarriers in the frequency domain. Physical resource blocks (PRBs) are numbered within a BWP, and the PRB numbering of a BWP starts from 0.

[0142] The size of the BWP can vary from a minimum of 1 PRB to the maximum system bandwidth size. Currently, for each DL (downlink) and UL (uplink), up to four BWPs can be configured through higher layer parameters, with a single active downlink and uplink BWP in a given TTI (transmission time interval). However, the present disclosure is not limited to the case where a UE is configured with a maximum of four bandwidth parts as defined in TS 38.211. The number of bandwidth parts can be greater than 4 in the uplink and / or downlink. For example, a UE can be configured with 8 BWPs.

[0143] The TTI (Transmission Time Interval) determines the timing granularity of the scheduling assignments. One TTI is the time interval during which a given signal is mapped to the physical layer. The TTI length can vary from 14 symbols (slot-based scheduling) to a maximum of 2 symbols (non-slot-based scheduling). Downlink and uplink transmissions are specified to be organized into frames (10ms duration) consisting of 10 subframes (1ms duration). In slot-based transmissions, the subframes are in turn divided into slots, the number of slots is defined by the parameter set / subcarrier spacing, and the specified values ​​range between 10 slots for a subcarrier spacing of 15 kHz to 320 slots for a subcarrier spacing of 240kHz. The number of OFDM symbols per slot is 14 for a normal cyclic prefix and 12 for an extended cyclic prefix (see 3GPP TS 38.211 V15.0.0 (2017-12) sections 4.1 (General frame structure), 4.2 (Parameter sets), 4.3.1 (Frames and subframes) and 4.3.2 (Slots)). However, transmissions may also be non-slot based. In non-slot based communications, the minimum length of a TTI may be 2 OFDM symbols. The BWP concept in NR will allow a relatively small active bandwidth to be dynamically configured for smaller data packets, which allows power saving for the UE, since with a smaller active BWP the UE needs to monitor fewer frequencies or use fewer frequencies for transmission.

[0144] The active bandwidth portion of the user equipment (e.g., the portion of the bandwidth that the UE uses to send and receive signals in a TTI) can switch between configured BWPs. For example, the active BWP can be switched to a larger BWP according to current needs, or to save battery power of the UE, the active BWP can be switched to a smaller BWP. This is possible by dynamically indicating in the DCI the active BWP to be used in the next TTI. DCI transmits downlink and uplink scheduling information (e.g., resource assignments and / or grants), requests for aperiodic CQI reports, or uplink power control commands for one cell and one RNTI. DCI coding includes information element multiplexing, CRC (cyclic redundancy check) attachment, channel coding, and rate matching. DCI carries transmission parameters such as MCS, redundancy version, or HARQ process number. DCI consists of several fields (e.g., bit fields / bitmaps) carrying different types of control information or control parameters. The base station sending the DCI and the UE receiving the DCI know the location of a certain parameter and the number of bits encoding the corresponding parameter. However, this switching of the active BWP increases latency because the UE needs to decode the DCI and then start hardware tuning to the new active BWP.

[0145] In current NR discussions, a minimum scheduling gap, i.e., the minimum applicable value of K0 (or K2) for the active downlink (DL) (or uplink (UL)) bandwidth portion, may be indicated from the gNB to the UE in order to be able to benefit from power savings.

[0146] The minimum applicable value may be assigned directly.One of one or more preconfigured or predetermined values ​​may be indicated explicitly or implicitly.

[0147] When selecting an entry of a DL or UL TDRA table, the indicated minimum applicable value may be applied by excluding invalid TDRA entries or reinterpreting the selected K0 (K2) value.

[0148] In case a minimum applicable value of K0 (K2) is indicated for an active DL (UL) BWP, the UE may not expect entries in the TDRA table with K0 (K2) values ​​less than the indicated minimum applicable value, or consider TDRA entries with K0 (K2) values ​​less than the indicated minimum applicable value to be invalid.

[0149] According to current 3GPP discussions, DCI formats 0_1 / 1_1 will support an additional field with 1 bit to support cross-slot scheduling adaptation, thereby allowing power savings in BR. Specifically, one or both of the minimum K0 / K2 values ​​for limiting the TDRA table are configured by RRC. In the case of configuring one value, a 1-bit indication in the DCI indicates whether the restriction of the TDRA table according to the configured minimum K0 / K2 value is to be applied. In the case of configuring two values, a 1-bit indication indicates which of the two configured values ​​is to be used for the TDRA table restriction.

[0150] In the UE-specific search space and any search space not associated with CORESET 0, and when the UE is configured with a UE-specific TDRA table, a valid entry is selected and used according to the indicated minimum K0 / K2 value (ie, the indicated scheduling gap).

[0151] However, for common search spaces not associated with CORESET 0, applying the minimum value of K0 / K2 in cross-slot scheduling may bring some difficulties. Some possible problems are explained below.

[0152] Specifically, in the common search space, when the UE is scheduled by UE-specific DCI or when no UE-specific TDRA table is configured, it remains an open question whether the UE should apply restrictions according to the indicated minimum K0 / K2 value.

[0153] In a simple method of handling the situation, the UE cannot use the configured common TDRA table to restrict any entry of the TDRA table of the common search space. However, not applying the restriction will result in a reduction in power saving capability. In addition, always applying the restriction according to the indicated minimum scheduling gap may cause scheduling losses.

[0154] To address these issues, the present invention provides various embodiments described below that facilitate determining whether to apply cross-slot adaptation based on information about certain conditions. These conditions may include whether a common TDRA table is configured, a comparison result between an indicated minimum scheduling gap and a scheduling gap included in the TDRA table, and / or whether an entry of the TDRA table is selected for uplink (UL) or downlink (DL) transmission of data.

[0155] Since the present disclosure involves scheduling, both entities, a scheduled device (usually a communication device / transceiver device) and a scheduling device (usually a network node), participate. The present invention also provides a system including a scheduled device and a scheduling device, and a corresponding method and program.

[0156] In the following, UE, base station and process will be described for a new radio access technology envisioned for a 5G mobile communication system but can also be used for an LTE mobile communication system. Different implementations and variants will also be explained. The discussions and findings as described above promote the following disclosure and can, for example, be based on at least a portion thereof.

[0157] In general, it should be noted that many assumptions have been made herein in order to be able to explain the basic principles of the present disclosure in a clear and understandable manner. However, these assumptions should be understood as examples made herein for illustrative purposes only and should not limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles disclosed below and as described in the claims can be applied to different scenarios and can be applied in ways not explicitly described herein.

[0158] In addition, some of the terms for processes, entities, layers, etc. used below are closely related to the terms used in LTE / LTE-A systems or in the current 3GPP 5G standardization, even though the specific terms used in the context of new radio access technologies of subsequent 3GPP 5G communication systems have not yet been fully determined or may eventually change. Therefore, the terms may be changed in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art appreciate that the embodiments and their scope of protection should not be limited to the specific terms used exemplarily herein due to the lack of newer or ultimately agreed terms, but should be understood more broadly in accordance with the functions and concepts that underlie the functions and principles of the present disclosure.

[0159] For example, a mobile station or mobile node or user terminal or user equipment (UE) is a physical entity (physical node) within a communication network. A node may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a predetermined set of functions to other functional entities of the same or another node or network. A node may have one or more interfaces that attach the node to a communication facility or medium through which the node can communicate. Similarly, a network entity may have a logical interface that attaches the functional entity to a communication facility or medium through which the network entity can communicate with other functional entities or corresponding nodes.

[0160] The term "base station" or "radio base station" refers to a physical entity within a communication network in this document. Like a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a predetermined set of functions to other functional entities of the same or another node or network. The physical entity performs some control tasks for the communication device, including one or more of scheduling and configuration. Note that the base station functionality and the communication device functionality can also be integrated into a single device. For example, a mobile terminal can also implement the functionality of a base station for other terminals. The term used in LTE is eNB (or eNodeB), while the term currently used in 5GNR is gNB.

[0161] Figure 8 A general, simplified and exemplary block diagram of a user equipment (also referred to as a communication device or transceiver device) 100 and a scheduling device 200 (herein exemplarily assumed to be located in a base station, such as an eLTE eNB (alternatively referred to as ng-eNB) or a gNB in ​​5G NR) is shown. The UE 100 and the eNB / gNB 300 communicate with each other via a (wireless) physical channel using transceivers 110, 210, respectively.

[0162] The communication device 100 may include a transceiver 110 and a processing circuit 120. The transceiver 110 may include and / or act as a receiver and a transmitter. The processing circuit 120 may be one or more hardware, such as one or more processors or any LSI. There is an input / output point (or node, not shown) between the transceiver 110 and the processing circuit 120, through which the processing circuit 120 can control the transceiver 110, that is, control the receiver and / or transmitter and exchange receive / transmit data. As a transmitter and receiver, the transceiver 110 may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit 120 may implement control tasks, such as controlling the transceiver 110 to send user data and control data provided by the processing circuit 120, and / or receiving user data and control data further processed by the processing circuit 120. The processing circuit 120 may also be responsible for performing other processes, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the transmission process and other processes related thereto. The receiver may be responsible for performing the receiving process and other processes related thereto, such as monitoring a channel.

[0163] The scheduling device 200 may include a transceiver 210 and a processing circuit 220. The transceiver 210 may include and / or act as a receiver and a transmitter. The processing circuit 220 may be one or more hardware, such as one or more processors or any LSI. There is an input / output point (or node, not shown) between the transceiver 210 and the processing circuit 220, through which the processing circuit 220 can control the transceiver 210, that is, control the receiver and / or transmitter and exchange receive / transmit data. As a transmitter and receiver, the transceiver 210 may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit 220 may implement control tasks, such as controlling the transceiver 210 to send data and control data provided by the processing circuit 120, and / or receiving user data further processed by the processing circuit 220. The processing circuit 220 may also be responsible for performing other processes, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the transmission process and other processes related thereto. The receiver may be responsible for performing the receiving process and other processes related thereto.

[0164] Example

[0165] For scheduling, four scenarios can be envisaged depending on whether a UE-specific TDRA table is configured, and depending on whether a common TDRA table is configured.

[0166] In the following, the case is described for downlink scheduling. However, for uplink scheduling, a corresponding case can be envisaged, where a corresponding TDRA table is configured for UL scheduling.

[0167] In case a UE-specific TDRA table is configured, i.e., the pdsch-Config includes a pdsch-TimeDomainAllocationList, the UE-specific TDRA table is used for DL ​​scheduling in the user-specific search space (USS) and any common search space (CSS) not associated with CORESET 0.

[0168] In case that no UE-specific TDRA table is configured, the TDRA table used for DL ​​scheduling in the user-specific search space (USS) and any common search space (CSS) not associated with CORESET 0 depends on whether the common TDRA table is configured. In case that a common TDRA table is configured, i.e., pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the configured common TDRA table is used for DL ​​scheduling in the user-specific search space (USS) and any common search space (CSS) not associated with CORESET 0. On the other hand, in case that no common TDRA table is configured, the default TDRA table (Default Table A) is used for DL ​​scheduling in the user-specific search space (USS) and any common search space (CSS) not associated with CORESET 0.

[0169] In case a common TDRA table is configured, the common TDRA table is used for DL ​​scheduling in the CSS associated with CORESET 0. On the other hand, if a common TDRA table is not configured, a default TDRA table is used for DL ​​scheduling.

[0170] Table 1 summarizes the described situations.

[0171]

[0172] Table 1: Usage of TDRA table in DL scheduling

[0173] The present disclosure provides an apparatus and method for determining whether to apply a restriction of a TDRA table for a CSS not associated with CORESET 0 or a TDRA table for a USS and any CSS associated with CORESET 0 in addition to a UE-specific TDRA table according to a minimum scheduling gap.

[0174] Fig. 9 is a schematic diagram showing an exemplary restriction of an exemplary TDRA table according to a minimum scheduling gap. The TDRA table corresponds to Figure 6The TDRA table is shown in FIG. 1 and described in detail above. In addition, the solid-line box and the dashed-line box indicate valid entries of the TDRA table according to the restrictions of the TDRA table according to the minimum scheduling gap of 2 and 3, respectively.

[0175] For example, in the case where the minimum scheduling gap is indicated as 2, rows (entries) 1 to 5 are considered invalid because their corresponding scheduling gaps are smaller than the indicated minimum scheduling gap. In addition, rows (entries) 6 to 16 are determined to be valid because the corresponding scheduling gaps are equal to or larger than the indicated minimum scheduling gap. This is determined by Fig. 9 The solid line box in FIG.

[0176] As another example, in the case where the minimum scheduling gap is indicated as 3, rows (entries) 1 to 8 are considered invalid because their corresponding scheduling gaps are smaller than the indicated minimum scheduling gap. In addition, rows (entries) 9 to 16 are determined to be valid because the corresponding scheduling gaps are equal to or larger than the indicated minimum scheduling gap. This is determined by Fig. 9 The dashed box in FIG.

[0177] In the case where a row (entry) of the configured TDRA table is invalidated, the UE does not need to buffer all symbols after receiving the PDCCH corresponding to the invalid entry of the TDRA table. In addition, for example, the UE can save power by relaxing the PDCCH processing timeline because the UE may not need to decode the PDCCH as fast as in the case of same time slot scheduling.

[0178] In the case where the TDRA table is limited according to the minimum scheduling gap indicated by the DCI, some entries of the TDRA table are invalidated. Specifically, entries with a scheduling gap smaller than the indicated minimum scheduling gap are invalidated. This allows the UE to skip PDSCH buffering in at least the current time slot (e.g., the time slot in which the PDCCH is received) and the next time slot, for example, according to the minimum scheduling gap. In addition, cross-slot scheduling may allow micro-sleep cycles in the time interval, especially when the PDCCH is not monitored until the scheduled resources are received.

[0179] Note that the present disclosure is not limited to the above referenced Fig. 9 The restrictions described. Specifically, a minimum scheduling gap other than 2 or 3 may be indicated. In addition, applying the restrictions to the TDRA table may refer to, for example, skipping all monitoring opportunities in the search space using the TDRA table in the time slot corresponding to the minimum scheduling gap, or switching to another TDRA table to be used for the search space, etc. This is described in the framework of the following embodiments.

[0180] Example 1 - Downlink Case

[0181] In this embodiment, in case of scheduling downlink data transmission, the transceiver device determines whether to apply restriction to the TDRA table according to the minimum scheduling gap, wherein the determination includes determining whether a common TDRA table is configured.

[0182] (A) Public TDRA is not configured

[0183] As described above, in the case where a common TDRA table is not configured for the CSS associated with CORESET 0 in cases 1.2 and 2.2 indicated in Table 1, and in the case where a common TDRA table is not configured for the USS and any CSS not associated with CORESET 0 in case 2.2, the default table A is used. According to the standard, the default TDRA table for DL ​​includes only entries indicating a scheduling gap having a value of zero. Therefore, applying a restriction to the default TDRA table according to the minimum scheduling gap being greater than zero will result in all entries of the default TDRA table being invalidated by the UE, which may result in a loss of scheduling information.

[0184] Therefore, in a case where it is determined that the common TDRA table is not configured, the restriction of the TDRA table for the CSS associated with CORESET 0 (ie, the default TDRA table) according to the minimum scheduling gap is not applied.

[0185] Furthermore, in case the default TDRA table is used for scheduling in a USS and any CSS not associated with CORESET 0 (case 2.2 indicated in Table 1), the restriction according to the minimum scheduling gap also does not apply.

[0186] In other words, when a common TDRA table is not configured and a standard TDRA table is used for scheduling in the CSS and / or USS associated with CORESET 0 and any CSS not associated with CORESET 0, restrictions on the default TDRA table according to the minimum scheduling gap do not apply.

[0187] In a variant, in the case where the default TDRA table is used for scheduling in the CSS associated with CORESET 0 (as in case 1.2 and case 2.2 of Table 1) or is also used for scheduling in the USS and any CSS not associated with CORESET 0 (as in case 2.2 of Table 1), and the minimum scheduling gap indicated by the previous DCI is greater than zero, the UE may not monitor the occasion of the physical control channel (e.g., physical downlink control channel (PDCCH)) in the corresponding search space. By not monitoring the occasion, the UE does not monitor paging and system information. With this approach, if there is no system information indicating a change within the occasion, the gNB may cause the UE to skip the occasion by indicating a minimum scheduling gap greater than zero.

[0188] (B) Public TDRA is configured

[0189] However, in the case where a common TDRA table is configured, as indicated in Case 1.1 and Case 2.1 above and in Table 1, the restrictions of the common TDRA table for scheduling in the CSS associated with CORESET 0 in Case 1.1 and Case 2.1 and for scheduling in the USS and any CSS not associated with CORESET 0 in Case 2.1 cannot be applied either, because in the CSS, the UE will not apply cross-slot scheduling for the group common PDCCH with SI-RNTI, RA-RNTI, TC-RNTI and P-RNTI. However, when the restrictions are not applied to the common TDRA table, the UE will use the fast PDCCH processing timeline and buffer all PDSCHs, which will result in greater power consumption than necessary.

[0190] Therefore, since the gc-PDCCH does not appear in every time slot, the UE does not need to monitor the group-common PDCCH in every possible monitoring opportunity, so power saving is achievable through cross-time slot scheduling adaptation under certain conditions.

[0191] According to this embodiment, depending on a comparison of the indicated minimum scheduling gap and a scheduling gap included in a common TDRA table, the UE determines whether to apply a restriction to the common TDRA table according to the minimum scheduling gap, the common TDRA table comprising a plurality of entries, each entry specifying a time domain resource allocation including a scheduling gap indicator indicating a gap between reception of a scheduling grant and scheduled resources.

[0192] In case the minimum scheduling gap is within the range of scheduling gaps included in the common TDRA table, the UE determines to apply restriction to the common TDRA table according to the minimum scheduling gap by invalidating entries of the TDRA table having scheduling gaps smaller than the indicated minimum scheduling gap.

[0193] In other words, when the minimum scheduling gap is greater than or equal to the minimum scheduling gap in the common TDRA table and less than or equal to the maximum scheduling gap in the common TDRA table, the UE determines to apply the restriction to the common TDRA table according to the minimum scheduling gap.

[0194] In the case where the minimum scheduling gap indicated by the previous DCI is greater than the maximum scheduling gap included in the common TDRA table, the transceiver is controlled not to monitor the PDCCH monitoring opportunity in the search space using the common TDRA table. Therefore, in the case where the minimum gap indicated by the DCI is not greater than the maximum scheduling gap included in the common TDRA, the transceiver can be controlled to monitor the PDCCH monitoring opportunity in the search space using the common TDRA table. For example, when the minimum scheduling gap indicated by the DCI is equal to or less than the maximum scheduling gap value included in the TDRA table, the transceiver can be controlled to start monitoring the monitoring opportunity again.

[0195] Specifically, in the above case 1.1, the PDCCH monitoring opportunities in the CSS associated with CORESET 0 are skipped. In addition, in the above case 2.1, the PDCCH monitoring opportunities in the CSS associated with CORESET 0 and the PDCCH monitoring opportunities in the CSS associated with CORESET 0, as well as the PDCCH monitoring opportunities in the USS and any CSS not associated with CORESET 0 are skipped. This approach allows the monitoring of paging and system information to be skipped if the gNB determines that the UE does not need to monitor the paging and system information. In other words, by indicating a minimum scheduling gap that is larger than the maximum scheduling gap in the common TDRA table, the gNB can cause the UE to not monitor paging and system information.

[0196] Alternatively, in the case where the minimum scheduling gap is greater than the maximum scheduling gap included in the public TDRA table, the UE does not apply the restriction to the public TDRA table. In addition, for example, the UE may determine a second TDRA table different from the public TDRA table and use the second TDRA table for scheduling. In other words, in the case where the minimum scheduling gap is greater than the maximum scheduling gap value included in the public TDRA table, the UE may not apply the restriction to the public TDRA table, but use another TDRA table for scheduling purposes. For example, the second TDRA table may be the default TDRA table described above. With this approach, the loss of scheduling information is prevented because the restriction is not applied to the public TDRA table, which will cause all entries to be considered invalid by the UE.

[0197] Furthermore, alternatively, the UE may not expect to be indicated a minimum scheduling gap that is greater than the maximum scheduling gap included in the common TDRA table. That is, in the case where a minimum scheduling gap greater than the maximum scheduling gap included in the common TDRA is indicated by the DCI, the minimum scheduling gap is ignored when determining whether to apply the restriction to the configured common TDRA table. This approach prevents scheduling losses caused by erroneously applying the restriction of the common TDRA table according to the minimum scheduling gap value, which does not result in a meaningful distinction between valid or invalid TDRA table entries.

[0198] In a variant, in a case where the scheduling gaps according to the entries of the common TDRA table are equal to each other, the UE determines not to apply the restriction to the common TDRA table according to the minimum scheduling gap indicated by the previous DCI. For example, in a case where all scheduling gaps included in the common TDRA table are equal to zero, the UE does not apply the restriction according to the minimum scheduling gap. Specifically, in a case where all scheduling gaps in the common TDRA table are equal, a meaningful distinction between valid and invalid entries using the minimum scheduling gap is impossible, because either all entries are considered valid or no entry is considered valid. The method of this variant allows preventing this situation.

[0199] In a further variation, the UE may determine whether it is configured to monitor a group common physical control channel (i.e., a group common physical downlink control channel gc-PDCCH) in the CSS associated with CORESET 0, and, depending on the result of the determination, determine whether to apply restrictions to the common TDRA table according to the minimum scheduling gap. Specifically, if the UE is not configured to monitor the gc-PDCCH in the CSS associated with CORESET 0, the restrictions are applied to the common TDRA table. That is, in the case where the UE is not configured to monitor the gc-PDCCH, the restrictions are applied, which allows the above-mentioned power saving measures. Note that, for example, the UE may be pre-configured to monitor the gc-PDCCH by broadcast.

[0200] In the above embodiments and variations, the transceiver of the UE receives data after receiving the corresponding scheduling grant. Specifically, the data is received via the PDSCH on the resources indicated in the scheduling grant, wherein the resources are located in a time slot, and the time distance from the time slot to the reception of the scheduling grant is greater than the indicated minimum scheduling gap.

[0201] Example 2 - Uplink Case

[0202] As described above, according to the current 3GPP discussion, the minimum scheduling gaps for downlink and uplink may be jointly configured by RRC signaling and indicated by DCI formats 0_1 and 1_1.

[0203] As for the downlink, if the common TDRA table is not configured, the default TDRA table can be used for scheduling in the CSS associated with CORESET 0. In addition, if the UE-specific TDRA table is also not configured, the default table can also be used for scheduling in the USS and any CSS not associated with CORESET 0.

[0204] However, in contrast to the default downlink TDRA table, the default uplink TDRA table standardly includes entries with scheduling gaps greater than zero.

[0205] Therefore, unlike the downlink, applying restrictions to the default table for the uplink will prevent the power savings that can be achieved through cross-slot scheduling adaptation. Therefore, for uplink scheduling, restrictions can be applied to the TDRA table used for scheduling in the CSS associated with CORESET 0 even if the common TDRA table is not configured. In addition, in the case where the UE-specific TDRA table is also not configured, restrictions can be applied to the TDRA table used for scheduling in the USS and any CSS not associated with CORESET 0 (i.e., the default UL TDRA table).

[0206] Rather, in an embodiment for scheduling uplink transmissions, a transceiver device determines whether to apply restrictions to a time domain resource allocation (TDRA) table based on a minimum scheduling gap, wherein the TDRA table includes a plurality of entries, each entry specifying a time domain resource allocation including a scheduling gap indicator indicating a gap between reception of a scheduling grant and scheduled resources, and the determination includes comparing the minimum scheduling gap and a scheduling gap included in the TDRA.

[0207] In other words, in contrast to the downlink case, the determination of whether to apply restrictions to the TDRA table does not necessarily include a determination of whether a common TDRA table is configured, since restrictions of the TDRA table used for scheduling may or may not be applied in either case. Rather, whether to apply restrictions is determined by comparing the indicated minimum scheduling gap indicated by the DCI with the scheduling gap included in the entry of the TDRA table in use.

[0208] Specifically, the above-mentioned variations for downlink case 1.1 and case 2.1 indicated in Table 1 are applicable to the corresponding cases of uplink scheduling.

[0209] Note that the common TDRA table used for uplink scheduling may be different from the common TDRA table used for downlink scheduling. Therefore, when the above process is applied to uplink scheduling, the corresponding common TDRA table used for uplink scheduling is utilized.

[0210] Furthermore, the above-described variations for downlink case 1.1 and case 2.1 indicated in Table 1 may also be applied to downlink case 1.2 and case 2.2, respectively.

[0211] That is, determining whether to apply restrictions to the common DL TDRA table can be equally applied to determining whether to apply restrictions to the default UL table. Specifically, the comparison of the minimum scheduling gap with the scheduling gap included in the TDRA refers to the comparison of the minimum scheduling gap of the uplink with the scheduling gap included in the default TDRA table of the uplink.

[0212] In other words, the description of the determination of downlink cases 1.1 and 2.1 applies to cases 1.1 and 2.1 of the uplink, where the downlink TDRA table is replaced by the corresponding UL TDRA table. In addition, the description of the determination of downlink cases 1.1 and 2.1 applies to cases 1.2 and 2.2 of the uplink, respectively, where the common DL TDRA table is replaced by the default UL TDRA table.

[0213] In detail:

[0214] According to this embodiment, depending on a comparison of the indicated minimum scheduling gap and the scheduling gap included in the default UL TDRA table, the UE determines whether to apply the restriction to the default UL TDRA table according to the minimum scheduling gap, and the default UL TDRA table includes multiple entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, which scheduling gap indicator indicates a gap between reception of a scheduling grant and scheduled resources.

[0215] In case the minimum scheduling gap is within the range of scheduling gaps included in the default UL TDRA table, the UE determines to apply restriction to the default UL TDRA table according to the minimum scheduling gap by invalidating entries in the TDRA table having scheduling gaps smaller than the indicated minimum scheduling gap.

[0216] In other words, when the minimum scheduling gap is greater than or equal to the minimum scheduling gap in the default UL TDRA table and less than or equal to the maximum scheduling gap in the default UL TDRA table, the UE determines to apply restriction to the default UL TDRA table according to the minimum scheduling gap.

[0217] In the case where the minimum scheduling gap indicated by the previous DCI is greater than the maximum scheduling gap included in the default UL TDRA table, the transceiver is controlled not to use the default UL TDRA table to monitor the PDCCH monitoring opportunity in the search space. Therefore, in the case where the minimum gap indicated by the DCI is not greater than the maximum scheduling gap included in the default UL TDRA, the transceiver can be controlled to use the default UL TDRA table to monitor the PDCCH monitoring opportunity in the search space. For example, when the minimum scheduling gap indicated by the DCI is equal to or less than the maximum scheduling gap value included in the TDRA table, the transceiver can be controlled to start monitoring the monitoring opportunity again.

[0218] Specifically, corresponding to case 1.1 indicated above, the PDCCH monitoring opportunities in the CSS associated with CORESET 0 are skipped. In addition, corresponding to case 2.1 indicated above, the PDCCH monitoring opportunities in the CSS associated with CORESET 0 and the PDCCH monitoring opportunities in the CSS associated with CORESET 0, as well as the PDCCH monitoring opportunities in the USS and any CSS not associated with CORESET 0 are skipped. This approach allows the monitoring of paging and system information to be skipped if the gNB determines that the UE does not need to monitor the paging and system information. In other words, by indicating a minimum scheduling gap that is larger than the maximum scheduling gap in the default UL TDRA table, the gNB can cause the UE to not monitor paging and system information.

[0219] Alternatively, in the case where the minimum scheduling gap is greater than the maximum scheduling gap included in the default UL TDRA table, the UE does not apply the restriction to the default UL TDRA table. With this approach, the loss of scheduling information is prevented because the restriction is not applied to the common TDRA table, which would cause all entries to be considered invalid by the UE.

[0220] Furthermore, alternatively, the UE may not expect to be indicated a minimum scheduling gap that is greater than the maximum scheduling gap included in the default UL TDRA table. That is, in the case where the DCI indicates a minimum scheduling gap that is greater than the maximum scheduling gap included in the default UL TDRA, the minimum scheduling gap is ignored when determining whether to apply the restriction to the configured default UL TDRA table. This approach prevents scheduling losses caused by erroneously applying the restriction of the default UL TDRA table based on the minimum scheduling gap value, which does not cause a meaningful distinction between valid and invalid TDRA table entries.

[0221] In a variant, in the case where the scheduling gaps according to the entries of the default UL TDRA table are equal to each other, the UE determines not to apply the restriction to the default UL TDRA table according to the minimum scheduling gap indicated by the previous DCI. Specifically, in the case where all scheduling gaps in the default UL TDRA table are equal, a meaningful distinction between valid and invalid entries using the minimum scheduling gap is impossible, because either all entries are considered valid or no entry is considered valid. The method of this variant allows preventing this situation.

[0222] In a further variation, the UE may determine whether it is configured to monitor a group common physical control channel (i.e., a group common physical downlink control channel gc-PDCCH) in the CSS associated with CORESET 0, and, depending on the result of the determination, determine whether to apply restrictions to the default UL TDRA table according to the minimum scheduling gap. Specifically, if the UE is not configured to monitor the gc-PDCCH in the CSS associated with CORESET 0, the restrictions are applied to the default UL TDRA table. That is, in the case where the UE is not configured to monitor the gc-PDCCH, the restrictions are applied, which allows the above-mentioned power saving measures. Note that, for example, the UE may be pre-configured to monitor the gc-PDCCH by broadcast.

[0223] In the above embodiments and variations, the transceiver of the UE sends data after receiving the corresponding scheduling grant. Specifically, the data is sent via the PUSCH on the resources indicated in the scheduling grant, wherein the resources are located in a time slot whose time distance to the reception of the scheduling grant is greater than the indicated minimum scheduling gap.

[0224] Hardware and software implementations of the present disclosure

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

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

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

[0228] Communication devices are not limited to portable or transportable, but may also include any kind of non-portable or fixed device, equipment, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in the "Internet of Things (IoT)" network.

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

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

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

[0232] In addition, various embodiments may also be implemented by software modules, which are executed by a processor or directly in hardware. Combinations of software modules and hardware implementations may also be possible. Software modules may be stored on any kind of computer-readable storage medium, such as RAM, EPROM, EEPROM, flash memory, registers, hard disk, CD-ROM, DVD, etc. It should also be noted that individual features of different embodiments may be the subject of another embodiment alone or in any combination.

[0233] Those skilled in the art will appreciate that various changes and / or modifications may be made to the present disclosure as shown in the specific embodiments. Therefore, the present embodiments are considered in all aspects to be illustrative and not restrictive.

[0234] Further aspects

[0235] As described above, a device and method for facilitating UE power saving are provided, including a process involving cross-time slot scheduling. Specifically, a device and method for determining whether to apply restrictions to a time domain resource allocation TDRA table using information about specific conditions are provided. The conditions may include information about whether a common TDRA table is configured, a comparison result between an indicated minimum scheduling gap and a scheduling gap in a TDRA table, and / or whether resources are scheduled for uplink or downlink transmission of data. Aspects of the present disclosure are summarized as follows.

[0236] According to a first aspect, a transceiver device is provided, comprising a transceiver that receives data after receiving a scheduling grant; and a circuit that determines whether to apply restrictions to a time domain resource allocation TDRA table based on a minimum scheduling gap, wherein the determination includes determining whether a common TDRA table is configured.

[0237] For example, the TDRA table to which the restriction may be applied according to the result of the determination may be the common TDRA table itself (if it is configured), or a TDRA table different from the common TDRA table and different from a TDRA table specific to the transceiver device.

[0238] For example, the TDRA table may be a TDRA table for downlink scheduling in a common search space associated with CORESET 0. Also, for example, the TDRA table may be a TDRA table for downlink scheduling in a common search space associated with CORESET 0 and for a user-specific search space and any common search space not associated with CORESET 0.

[0239] For example, the TDRA table may be a public TDRA table or a default TDRA table.

[0240] For example, the TDRA table may be a TDRA table that is not configured to be specific to a transceiver device.

[0241] For example, the TDRA table is a TDRA table used for scheduling resources for data reception.

[0242] For example, the transceiver receives data according to the resources indicated by the scheduling grant.

[0243] For example, the scheduling grant indicates scheduled resources for data reception, wherein after receiving the scheduling grant, the resources are scheduled after a scheduling gap is greater than or equal to a minimum scheduling gap.

[0244] Determining whether to apply restrictions to the TDRA table based on the minimum scheduling gap allows the transceiver device to not buffer symbols after receiving a scheduling grant under certain conditions, which allows, for example, power savings.

[0245] In an embodiment, upon determining that the common TDRA table is not configured, the circuit determines not to apply restrictions to the TDRA table.

[0246] In other words, for example, in the case where a common TDRA table is configured and used for downlink scheduling, the circuit may determine to apply restrictions to the common TDRA table. In addition, in the case where a common TDRA table is not configured and another TDRA table is used for downlink scheduling, restrictions may not be applied.

[0247] For example, in the event that the other TDRA table is not a public TDRA table and is not a TDRA table specifically configured for the transceiver device, the circuitry may determine that no restriction applies.

[0248] Since the restriction is not applied under the defined conditions (ie the common TDRA table is not configured), possible scheduling losses are prevented.

[0249] In an embodiment, the circuit controls the transceiver to not monitor opportunities of the physical control channel in the search space associated with the TDRA table when the minimum scheduling gap is greater than zero.

[0250] For example, in a case where the minimum scheduling gap is greater than zero and the common TDRA table is not configured, the circuit controls the transceiver to not monitor the opportunities of the physical control channel.

[0251] Furthermore, for example, in the case where the minimum scheduling gap is greater than zero, the common TDRA table is not configured, and the default TDRA table is used for scheduling, the circuit controls the transceiver to not monitor the occasions of the physical control channel.

[0252] For example, the physical control channel may be a physical downlink control channel PDCCH.

[0253] In an embodiment, the TDRA table includes multiple entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, which indicates a gap between reception of a scheduling grant and scheduled resources, and in the case of determining that a common TDRA table is configured, the determination also includes comparing the minimum scheduling gap and the scheduling gap included in the TDRA table.

[0254] In other words, determining whether to apply the restriction to the TDRA table may include determining whether the common TDRA table is configured and comparing the minimum scheduling gap and the scheduling gap value included in the TDRA table.

[0255] For example, in the event that it is determined that the common TDRA table is not configured, the circuit may perform a comparison of the minimum scheduling gap with the scheduling gap included in the common TDRA table, and use the result of the comparison to determine whether to apply restrictions to the common TDRA table.

[0256] In an embodiment, the circuit determines to apply the restriction to the TDRA table if the minimum scheduling gap is within the range of scheduling gaps included in the TDRA table.

[0257] For example, if the minimum scheduling gap is greater than or equal to the smallest scheduling gap included in the TDRA table and less than or equal to the largest scheduling gap included in the TDRA table, the circuit determines that the minimum scheduling gap is within the range of scheduling gaps in the TDRA table.

[0258] In an embodiment, in case that the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit controls the transceiver to not monitor the occasion of the physical control channel in the search space associated with the TDRA table.

[0259] For example, the physical control channel may be a physical downlink control channel PDCCH.

[0260] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit determines not to apply the restriction to the TDRA table.

[0261] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit further determines a second TDRA table different from the TDRA table used for resource allocation, and uses the second TDRA table for scheduling.

[0262] In other words, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit determines and utilizes a second TDRA table different from the TDRA table for scheduling of resources. Restrictions are not applied to the second TDRA table.

[0263] For example, the second TDRA table is a default TDRA table.

[0264] In an embodiment, in a case where the scheduling gaps included in the TDRA table are equal to each other, the circuit determines not to apply the restriction to the TDRA table.

[0265] In other words, in the case where the TDRA table includes only scheduling gap values ​​that are all equal to each other, the restriction is not applied to the TDRA table.

[0266] In an embodiment, the determining comprises determining whether the transceiver device is configured to monitor a group common physical control channel; and in the event that the transceiver device is not configured to monitor the group common physical control channel, the circuitry determines to apply the restriction to the TDRA table.

[0267] In an embodiment, the transceiver receives a minimum scheduling gap indicator indicating a minimum scheduling gap.

[0268] For example, the transceiver receives the minimum scheduling gap indicator through downlink control information DCI signaling.

[0269] For example, one or more minimum scheduling gap values ​​are configured by radio resource control RRC signaling.

[0270] In an embodiment, the minimum scheduling gap indicates the minimum value of the gap between the reception of the scheduling grant and the scheduled resources in terms of time slots.

[0271] In other words, the minimum scheduling gap represents the minimum time period between the reception of a scheduling grant and the resources scheduled for the reception of data indicated by the scheduling grant.The time period is indicated in terms of time slots, the duration of which may be pre-set or configured, for example.

[0272] According to a second aspect, a transceiver device is provided, comprising a transceiver that sends data after receiving a scheduling grant; and a circuit that determines whether to apply a restriction to a time domain resource allocation TDRA table based on a minimum scheduling gap, wherein the TDRA table includes multiple entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, the scheduling gap indicator indicating a gap between reception of the scheduling grant and scheduled resources, and the determination includes comparing the minimum scheduling gap and the scheduling gap included in the TDRA table.

[0273] For example, the TDRA table to which the restriction may be applied according to the result of the determination may be the common TDRA table itself (if it is configured), or a TDRA table different from the common TDRA table and different from a TDRA table specific to the transceiver device.

[0274] For example, the TDRA table may be a TDRA table for uplink scheduling in a common search space associated with CORESET 0. Also, for example, the TDRA table may be a TDRA table for uplink scheduling in a common search space associated with CORESET 0 and for a user-specific search space and any common search space not associated with CORESET 0.

[0275] For example, the TDRA table may be a public TDRA table or a default TDRA table.

[0276] For example, the TDRA table may be a TDRA table that is not configured to be specific to a transceiver device.

[0277] For example, the TDRA table is a TDRA table used for scheduling resources for data transmission.

[0278] For example, the transceiver transmits data according to the resources indicated by the scheduling grant.

[0279] For example, the scheduling grant indicates scheduled resources for data transmission, wherein after receiving the scheduling grant, the resources are scheduled after a scheduling gap is greater than or equal to a minimum scheduling gap.

[0280] Determining whether to apply restrictions to the TDRA table based on the minimum scheduling gap allows the transceiver device to not buffer symbols after receiving a scheduling grant under certain conditions, which allows, for example, power savings.

[0281] In an embodiment, the circuit determines to apply the restriction to the TDRA table if the minimum scheduling gap is within the range of scheduling gaps included in the TDRA table.

[0282] For example, if the minimum scheduling gap is greater than or equal to the smallest scheduling gap included in the TDRA table and less than or equal to the largest scheduling gap included in the TDRA table, the circuit determines that the minimum scheduling gap is within the range of scheduling gaps in the TDRA table.

[0283] In an embodiment, in case that the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit controls the transceiver to not monitor the occasion of the physical control channel in the search space associated with the TDRA table.

[0284] For example, the physical control channel may be a physical uplink control channel PUCCH.

[0285] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit determines not to apply the restriction to the TDRA table.

[0286] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit further determines a second TDRA table different from the TDRA table used for resource allocation, and uses the second TDRA table for scheduling.

[0287] In other words, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit determines and utilizes a second TDRA table different from the TDRA table for scheduling of resources. Restrictions are not applied to the second TDRA table.

[0288] For example, the second TDRA table is a default TDRA table.

[0289] In an embodiment, in a case where the scheduling gaps included in the TDRA table are equal to each other, the circuit determines not to apply the restriction to the TDRA table.

[0290] In other words, in the case where the TDRA table includes only scheduling gap values ​​that are all equal to each other, the restriction is not applied to the TDRA table.

[0291] In an embodiment, the determining comprises determining whether the transceiver device is configured to monitor a group common physical control channel; and in the event that the transceiver device is not configured to monitor the group common physical control channel, the circuitry determines to apply the restriction to the TDRA table.

[0292] In an embodiment, the transceiver receives a minimum scheduling gap indicator indicating a minimum scheduling gap.

[0293] For example, the transceiver receives the minimum scheduling gap indicator through downlink control information DCI signaling.

[0294] For example, one or more minimum scheduling gap values ​​are configured by radio resource control RRC signaling.

[0295] In an embodiment, the minimum scheduling gap indicates the minimum value of the gap between the reception of the scheduling grant and the scheduled resources in terms of time slots.

[0296] In other words, the minimum scheduling gap represents the minimum time period between the reception of a scheduling grant and the resources scheduled for the data transmission indicated by the scheduling grant.The time period is indicated in terms of time slots, the duration of which may be pre-set or configured, for example.

[0297] According to a third aspect, a method for receiving data is provided, the method comprising determining whether to apply restriction to a time domain resource allocation TDRA table according to a minimum scheduling gap, wherein the determination comprises determining whether a common TDRA table is configured; and receiving data after receiving a scheduling grant.

[0298] For example, the TDRA table to which the restriction may be applied according to the result of the determination may be the common TDRA table itself (if it is configured), or a TDRA table different from the common TDRA table and different from a TDRA table specific to the transceiver device.

[0299] For example, the TDRA table may be a TDRA table for downlink scheduling in a common search space associated with CORESET 0. Also, for example, the TDRA table may be a TDRA table for downlink scheduling in a common search space associated with CORESET 0 and for a user-specific search space and any common search space not associated with CORESET 0.

[0300] For example, the TDRA table may be a public TDRA table or a default TDRA table.

[0301] For example, the TDRA table may be a TDRA table that is not configured to be specific to a transceiver device.

[0302] For example, the TDRA table is a TDRA table used for scheduling resources for data reception.

[0303] For example, data is received according to the resources indicated by the scheduling grant.

[0304] For example, the scheduling grant indicates scheduled resources for data reception, wherein after receiving the scheduling grant, the resources are scheduled after a scheduling gap is greater than or equal to a minimum scheduling gap.

[0305] Determining whether to apply restrictions to the TDRA table based on the minimum scheduling gap allows the transceiver device to not buffer symbols after receiving a scheduling grant under certain conditions, which allows, for example, power savings.

[0306] In an embodiment, in case it is determined that the common TDRA table is not configured, it is determined not to apply the restriction to the TDRA table.

[0307] In other words, for example, in the case where a common TDRA table is configured and used for downlink scheduling, it may be determined that restrictions are applied to the common TDRA table. In addition, in the case where a common TDRA table is not configured and another TDRA table is used for downlink scheduling, restrictions may not be applied.

[0308] For example, in the case where the other TDRA table is not a public TDRA table and is not a TDRA table specifically configured for the transceiver device, it may be determined that the restriction is not applied.

[0309] Since the restriction is not applied under the defined conditions (ie the common TDRA table is not configured), possible scheduling losses are prevented.

[0310] In an embodiment, when the minimum scheduling gap is greater than zero, the opportunities of the physical control channels in the search space associated with the TDRA table are not monitored.

[0311] For example, when the minimum scheduling gap is greater than zero and the common TDRA table is not configured, the opportunities of the physical control channel are not monitored.

[0312] Furthermore, for example, in the case where the minimum scheduling gap is greater than zero, the common TDRA table is not configured, and the default TDRA table is used for scheduling, the occasions of the physical control channel are not monitored.

[0313] For example, the physical control channel may be a physical downlink control channel PDCCH.

[0314] In an embodiment, the TDRA table includes multiple entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, which indicates a gap between reception of a scheduling grant and scheduled resources, and in the case of determining that a common TDRA table is configured, the determination also includes comparing the minimum scheduling gap and the scheduling gap included in the TDRA table.

[0315] In other words, determining whether to apply the restriction to the TDRA table may include determining whether the common TDRA table is configured and comparing the minimum scheduling gap and the scheduling gap value included in the TDRA table.

[0316] For example, in the case where it is determined that the common TDRA table is not configured, a comparison of the minimum scheduling gap with the scheduling gap included in the common TDRA table may be performed, and a result of the comparison may be used to determine whether to apply restriction to the common TDRA table.

[0317] In an embodiment, in case the minimum scheduling gap is within the range of scheduling gaps included in the TDRA table, it is determined to apply the restriction to the TDRA table.

[0318] For example, if the minimum scheduling gap is greater than or equal to the smallest scheduling gap included in the TDRA table and less than or equal to the largest scheduling gap included in the TDRA table, it is determined that the minimum scheduling gap is within the range of scheduling gaps in the TDRA table.

[0319] In an embodiment, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the occasions of the physical control channel in the search space associated with the TDRA table are not monitored.

[0320] For example, the physical control channel may be a physical downlink control channel PDCCH.

[0321] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, it is determined not to apply the restriction to the TDRA table.

[0322] In an embodiment, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the method further comprises determining a second TDRA table different from the TDRA table used for resource allocation.

[0323] In other words, in the case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, a second TDRA table different from the TDRA table is determined and used for scheduling of resources. Restriction is not applied to the second TDRA table.

[0324] For example, the second TDRA table is a default TDRA table.

[0325] In an embodiment, in a case where the scheduling gaps included in the TDRA table are equal to each other, it is determined not to apply the restriction to the TDRA table.

[0326] In other words, in the case where the TDRA table includes only scheduling gap values ​​that are all equal to each other, the restriction is not applied to the TDRA table.

[0327] In an embodiment, the determining comprises determining whether a monitoring group common physical control channel is configured; and in the event that the monitoring group common physical control channel is not configured, determining to apply restrictions to the TDRA table.

[0328] In an embodiment, the method further comprises receiving a minimum scheduling gap indicator indicating a minimum scheduling gap.

[0329] For example, the minimum scheduling gap indicator is received through downlink control information DCI signaling.

[0330] For example, one or more minimum scheduling gap values ​​are configured by radio resource control RRC signaling.

[0331] In an embodiment, the minimum scheduling gap indicates the minimum value of the gap between the reception of the scheduling grant and the scheduled resources in terms of time slots.

[0332] In other words, the minimum scheduling gap represents the minimum time period between the reception of a scheduling grant and the resources scheduled for the reception of data indicated by the scheduling grant.The time period is indicated in terms of time slots, the duration of which may be pre-set or configured, for example.

[0333] According to a fourth aspect, a method for sending data is provided, the method comprising determining whether to apply restrictions to a time domain resource allocation TDRA table based on a minimum scheduling gap, wherein the TDRA table comprises a plurality of entries, each entry specifies a time domain resource allocation including a scheduling gap indicator, the scheduling gap indicator indicating a gap between reception of a scheduling grant and scheduled resources, and the determination comprises comparing the minimum scheduling gap and a scheduling gap included in the TDRA table; and sending data after receiving the scheduling grant.

[0334] For example, the TDRA table to which the restriction may be applied according to the result of the determination may be the common TDRA table itself (if it is configured), or a TDRA table different from the common TDRA table and different from a TDRA table specific to the transceiver device.

[0335] For example, the TDRA table may be a TDRA table for uplink scheduling in a common search space associated with CORESET 0. Also, for example, the TDRA table may be a TDRA table for uplink scheduling in a common search space associated with CORESET 0 and for a user-specific search space and any common search space not associated with CORESET 0.

[0336] For example, the TDRA table may be a public TDRA table or a default TDRA table.

[0337] For example, the TDRA table may be a TDRA table that is not configured to be specific to a transceiver device.

[0338] For example, the TDRA table is a TDRA table used for scheduling resources for data transmission.

[0339] For example, data is sent according to the resources indicated by the scheduling grant.

[0340] For example, the scheduling grant indicates scheduled resources for data transmission, wherein after receiving the scheduling grant, the resources are scheduled after a scheduling gap is greater than or equal to a minimum scheduling gap.

[0341] Determining whether to apply restrictions to the TDRA table based on the minimum scheduling gap allows the transceiver device to not buffer symbols after receiving a scheduling grant under certain conditions, which allows, for example, power savings.

[0342] In an embodiment, in case the minimum scheduling gap is within the range of scheduling gaps included in the TDRA table, it is determined to apply the restriction to the TDRA table.

[0343] For example, if the minimum scheduling gap is greater than or equal to the smallest scheduling gap included in the TDRA table and less than or equal to the largest scheduling gap included in the TDRA table, it is determined that the minimum scheduling gap is within the range of scheduling gaps in the TDRA table.

[0344] In an embodiment, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the occasions of the physical control channel in the search space associated with the TDRA table are not monitored.

[0345] For example, the physical control channel may be a physical uplink control channel PUCCH.

[0346] In an embodiment, in a case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, it is determined not to apply the restriction to the TDRA table.

[0347] In an embodiment, in case the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the method further comprises determining a second TDRA table different from the TDRA table used for resource allocation.

[0348] In other words, in the case where the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, a second TDRA table different from the TDRA table is determined and used for scheduling of resources. Restriction is not applied to the second TDRA table.

[0349] For example, the second TDRA table is a default TDRA table.

[0350] In an embodiment, in a case where the scheduling gaps included in the TDRA table are equal to each other, it is determined not to apply the restriction to the TDRA table.

[0351] In other words, in the case where the TDRA table includes only scheduling gap values ​​that are all equal to each other, the restriction is not applied to the TDRA table.

[0352] In an embodiment, the determining comprises determining whether a monitoring group common physical control channel is configured; and in the event that the monitoring group common physical control channel is not configured, determining to apply restrictions to the TDRA table.

[0353] In an embodiment, the method further comprises receiving a minimum scheduling gap indicator indicating a minimum scheduling gap.

[0354] For example, the minimum scheduling gap indicator is received through downlink control information DCI signaling.

[0355] For example, one or more minimum scheduling gap values ​​are configured by radio resource control RRC signaling.

[0356] In an embodiment, the minimum scheduling gap indicates the minimum value of the gap between the reception of the scheduling grant and the scheduled resources in terms of time slots.

[0357] In other words, the minimum scheduling gap represents the minimum time period between the reception of a scheduling grant and the resources scheduled for the data transmission indicated by the scheduling grant.The time period is indicated in terms of time slots, the duration of which may be pre-set or configured, for example.

[0358] According to a fifth aspect, a scheduling device is provided, comprising a circuit that determines a minimum scheduling gap, which indicates a minimum value of a gap between transmission of a scheduling grant and scheduled resources; and a transceiver that sends a scheduling grant to a transceiver device, which scheduling grant indicates scheduled resources for data transmission, wherein the resources are scheduled after the transmission of the scheduling grant and after the scheduling gap is greater than or equal to the minimum scheduling gap, and data is sent to or received from the transceiver device on the scheduled resources.

[0359] In an embodiment, the transceiver sends a minimum scheduling gap indicator indicating the minimum scheduling gap to the transceiver device.

[0360] For example, the circuitry does not schedule resources for transmission to or reception from the transceiver device during a time period after the transmission scheduling grant, wherein the time period has a duration according to the minimum scheduling gap.

[0361] For example, the minimum scheduling gap indicator is indicated to the transceiver device through downlink control information DCI.

[0362] In an embodiment, the circuit determines that the minimum scheduling gap is greater than a maximum scheduling gap included in a configured time domain resource allocation TDRA table, the TDRA table including a plurality of entries, each entry specifying a time domain resource allocation including a scheduling gap indicator indicating a gap between reception of a scheduling grant and scheduled resources.

[0363] Using this determination, the scheduling device may cause the transceiver device to skip a monitoring opportunity of the physical control channel.

[0364] In an embodiment, the minimum scheduling gap indicates the minimum value of the gap between the reception of the scheduling grant and the scheduled resources in terms of time slots.

Claims

1. A user equipment, comprising: a transceiver, receiving data after receiving the scheduling information; and The circuit determines not to apply restriction to the TDRA table according to the minimum scheduling gap when using the default time domain resource allocation TDRA.

2. The user equipment according to claim 1, wherein The circuit controls the transceiver to not monitor a physical control channel in a search space associated with the TDRA table when the minimum scheduling gap is greater than zero.

3. The user equipment according to claim 1, wherein The TDRA table includes a plurality of entries, each entry specifying a time domain resource allocation including a scheduling gap indicator indicating a gap between reception of scheduling information and scheduled resources.

4. The user equipment according to claim 1, wherein The determining further includes comparing the minimum scheduling gap with a scheduling gap included in the TDRA table when it is determined that a common TDRA table is configured.

5. The user equipment according to claim 3, wherein The circuit determines to apply a restriction to the TDRA table if the minimum scheduling gap is within a range of scheduling gaps included in the TDRA table.

6. The user equipment according to claim 3, wherein The circuit controls the transceiver to not monitor a physical control channel in a search space associated with the TDRA table when the minimum scheduling gap is greater than a maximum scheduling gap included in the TDRA table.

7. The user equipment according to claim 3, wherein The circuit determines not to apply restriction to the TDRA table if the minimum scheduling gap is greater than a maximum scheduling gap included in the TDRA table.

8. The user equipment according to claim 7, wherein When the minimum scheduling gap is greater than the maximum scheduling gap included in the TDRA table, the circuit further determines a second TDRA table different from the TDRA table for resource allocation, and uses the second TDRA table for scheduling.

9. The user equipment according to claim 3, wherein The circuit determines not to apply restriction to the TDRA table if the scheduling gaps included in the TDRA table are equal to each other.

10. The user equipment according to claim 1, wherein The determining comprises determining whether the user equipment monitors a group common physical control channel; and The circuit determines to apply restrictions to the TDRA table if the user equipment does not monitor the set of common physical control channels.

11. The user equipment according to claim 1, wherein The transceiver receives a minimum scheduling gap indicator indicating a minimum scheduling gap.

12. The user equipment according to claim 1, wherein The minimum scheduling gap indicates the minimum value of the gap between the reception of scheduling information and the scheduled resources in time slots.

13. A method for receiving data, the method comprising: In case of using the default time domain resource allocation TDRA, determining not to apply restrictions to the TDRA table according to the minimum scheduling gap; as well as Data is received after receiving the scheduling information.

Images