CN113906791A - Transceiver device and scheduling device - Google Patents

Abstract

The invention provides a transceiver device and a scheduling device, and a communication method for the transceiver device and the scheduling device. The transceiver device includes: a transceiver for transmitting a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH); and circuitry to start a monitoring dormancy timer after the transceiver transmits a scheduling request, wherein the transceiver does not monitor a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running, and starts monitoring the PDCCH for resource allocations for scheduling data when the monitoring dormancy timer has expired.

Description

Transceiver device and scheduling device

Technical Field

The present invention relates to the transmission and reception of signals in a communication system. In particular, the present invention relates to methods and apparatus for such transmission and reception.

Background

The third generation partnership project (3GPP) is working on technical specifications for the next generation cellular technology, also referred to as the fifth generation (5G), including the "new radio" (NR) Radio Access Technology (RAT), which operates in the spectrum ranging from sub-1 GHz to millimeter frequency bands. NR is a follower of Long Term Evolution (LTE) and LTE-advanced (LTE-a) technologies.

For systems such as LTE, LTE-a, and NR, further modifications and options may facilitate efficient operation of the communication system and the specific devices associated with the system.

Disclosure of Invention

One non-limiting and exemplary embodiment facilitates providing scheduling requests that are flexible and reduce power consumption.

In one embodiment, the technology disclosed herein features a transceiver device comprising: a transceiver for transmitting a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH); and circuitry to start a monitoring dormancy timer after the transceiver transmits a scheduling request, wherein the transceiver does not monitor a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running, and starts monitoring the PDCCH for resource allocations for scheduling data when the monitoring dormancy timer has expired.

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

Additional benefits and advantages of the disclosed embodiments will become apparent from the description and drawings. The benefits and/or advantages may be realized and attained by the various embodiments and features of the specification and the drawings individually, and not all of these embodiments and features need be present in order to achieve one or more of these benefits and/or advantages.

Drawings

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

Fig. 1 is a schematic diagram illustrating an exemplary architecture of a 3GPP NR system;

fig. 2 is a block diagram illustrating an exemplary user and control plane architecture of an LTE eNB, a gNB, and a UE;

fig. 3 is a diagram illustrating a functional division between NG-RAN and 5 GC;

figure 4 is a sequence diagram of an RRC connection establishment/reconfiguration procedure;

FIG. 5 is a diagram illustrating a usage scenario for enhanced mobile broadband, large-scale machine type communication (mMTC) and ultra-reliable low latency communication (URLLC);

FIG. 6 is a block diagram illustrating an exemplary 5G system architecture;

figure 7 shows the transmission of scheduling requests and active periods when a discontinuous reception DRX cycle is configured according to 3GPP TR 38.321;

figure 8A schematically shows a time sequence of transmission of a scheduling request and reception of an uplink grant and an active period in a DRX configuration of an associated high priority logical channel;

figure 8B schematically shows a time sequence of transmission of a scheduling request and reception of an uplink grant and an active period in a DRX configuration of an associated low priority logical channel;

fig. 9 is a block diagram illustrating functional components of a transceiver device and a scheduling device according to an embodiment;

fig. 10 illustrates a delay of an activity period from a transmission time of a scheduling request according to an embodiment;

FIG. 11 is a flow chart illustrating transmission of a scheduling request and beginning monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

FIG. 12 schematically illustrates a mapping of a single scheduling request configuration per logical channel, wherein a first runtime of a watchdog timer is configured for a first logical channel and a second runtime of the watchdog timer is configured for a second logical channel;

fig. 13 schematically shows the mapping of one scheduling request configuration per two logical channels;

fig. 14 schematically shows a MAC control element CE indicating monitoring of the running of a dormancy timer according to an embodiment;

fig. 15 schematically shows a time sequence of transmission of a scheduling request, monitoring for reception of a sleep indicator and reception of an uplink grant and an active period according to an embodiment;

fig. 16 is a flow diagram illustrating transmission of a scheduling request, monitoring for receipt of a dormancy indicator, and beginning monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

fig. 17 schematically shows a time sequence of transmission of a scheduling request, start of a sleep monitor timer, reception of a monitor sleep indicator, and restart of the monitor sleep timer according to an embodiment.

Fig. 18A shows a short format of the buffer status report BSR.

Fig. 18B shows a long format of the buffer status report BSR.

Figure 19 shows transmission of buffer status reports and active periods when a discontinuous reception DRX cycle is configured;

figure 20A schematically illustrates the transmission of a buffer status report and the reception of an uplink grant and the time sequence of active periods in a DRX configuration of an associated high priority logical channel group;

figure 20B schematically illustrates the transmission of a buffer status report and the reception of an uplink grant and the time sequence of active periods in a DRX configuration of an associated low priority logical channel group;

fig. 21 illustrates a delay of an activity period from a transmission time of a buffer status report according to an embodiment;

fig. 22 is a flowchart illustrating transmission of a buffer status report and starting monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

fig. 23 shows the steps of a scheduling request procedure, wherein a scheduling request and a buffer status report are sent and a corresponding supervision dormancy timer may be started.

Detailed Description

5G NR System architecture and protocol Stack

The 3GPP has been working on the next release of the fifth generation cellular technology (abbreviated 5G) including the development of a new radio access technology (NR) operating at frequencies up to 100 GHz. The first release 5G standard was completed in 2017, which allowed the trial and commercial deployment of smartphones to proceed in compliance with the 5G NR standard.

The overall system architecture assumes, among other things, a NG-RAN (next generation radio access network) including a gNB that provides a NG radio access user plane (SDAP/PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminal to the UE. The gnbs interconnect each other by means of an Xn interface the gnbs are also connected to NGCs (next generation cores) by means of Next Generation (NG) interfaces, more specifically to AMFs (access and mobility management functions) (e.g. the specific core entity performing the AMF) by means of NG-C interfaces and to UPFs (user plane functions) (e.g. the specific core entity performing the UPF) by means of NG-U interfaces. The NG-RAN architecture is shown in fig. 1.

A variety of different deployment scenarios may be supported. For example, a non-centralized deployment scenario is proposed in which base stations supporting 5G NR can be deployed. Fig. 2 illustrates an exemplary non-centralized deployment scenario, while also illustrating an LTE eNB and User Equipment (UE) connected to both the gbb and the LTE eNB. The new eNB of NR 5G may exemplarily be referred to as a gNB. An eLTE eNB is an evolution of an eNB that supports connections to EPC (evolved packet core) and NGC (next generation core).

The user plane protocol stack of NR includes PDCP (packet data convergence protocol), RLC (radio link control) and MAC (medium access control) sublayers, which are terminated in the gNB on the network side. In addition, a new Access Stratum (AS) sublayer (SDAP, service data adaptation protocol) was introduced above the PDCP. A control plane protocol stack is also defined for the NR.

5G between NG-RAN and 5GC NR functional partitioning

Fig. 3 shows the functional division between NG-RAN and 5 GC. The NG-RAN logical node is a gNB or an NG-eNB. The 5GC has the above logical nodes AMF, UPF, and SMF.

Specifically, the gNB and ng-eNB carry the following main functions:

functions for radio resource management such as radio bearer control, radio access control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (scheduling);

-IP header compression, encryption and data integrity protection;

-selecting the AMF at the UE accessory when the route to the AMF cannot be determined from the information provided by the UE;

-routing of user plane data to UPF;

-routing of control plane information to the AMF;

-connection establishment and release;

-scheduling and transmitting paging messages;

scheduling and transmission of system broadcast information (originating from AMF or OAM);

-mobile and scheduled measurement and measurement reporting configurations;

-a transport level packet marking in the uplink;

-session management;

-supporting network slicing;

-QoS flow management and mapping to data radio bearers;

-support for UEs in RRC _ INACTIVE state;

-a function of distribution of NAS messages;

-radio access network sharing;

-dual connectivity;

tight interworking between-NR and E-UTRA.

The access and mobility management function (AMF) carries the following main functions:

-a non access stratum, NAS, signalling terminal;

-NAS signaling security;

-access stratum, AS, security control;

-inter-core network CN node signalling for mobility between 3GPP access networks;

idle mode UE reachability (including control and execution of paging retransmissions);

-registration area management;

-supporting intra-system and inter-system mobility;

-an access authentication;

-access authorization, including roaming permission check;

mobility management control (subscription and policy);

-supporting network slicing;

-session management function, SMF, selection.

Furthermore, the user plane function UPF carries the following main functions:

anchor point for intra/inter RAT mobility (as applicable);

-an external PDU session point connected to the data network;

-packet routing and forwarding;

-a user plane part of packet inspection and policy rule enforcement;

-a service usage report;

-an uplink classifier supporting routing of traffic flows to a data network;

-a branch point supporting a multihomed PDU session;

QoS treatment of the user plane, e.g. packet filtering, gating, UL/DL rate enforcement;

-uplink traffic validation (SDF to QoS flow mapping);

-downlink packet buffering and downlink data notification triggering.

Finally, the session management function SMF carries the following main functions:

-session management;

-UE IP address assignment and management;

-selection and control of UP functions;

-configuring traffic control at a user plane function UPF to route traffic to an appropriate destination;

-control part of policy enforcement and QoS;

-downlink data notification.

RRC connection establishment and reconfiguration procedures

Fig. 4 shows some interactions between the UE, the gNB and the AMF (5GC entities) regarding RRC being the higher layer signaling (protocol) for the UE and the gNB configuration. Specifically, the AMF prepares UE CONTEXT data (including, for example, PDU session CONTEXT, security keys, UE radio capabilities, UE security capabilities, etc.) and sends it to the gNB along with INITIAL CONTEXT SETUP REQUEST. Then, the gNB 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. Subsequently, the gNB performs reconfiguration by means of rrcreeconfiguration and rrcreeconfiguration complete to establish signaling radio bearer 2(SRB2) and data radio bearer DRB. For signaling-only connections, step 8 is skipped because SRBs 2 and DRBs are not established. Finally, the gNB notifies AMF that the SETUP process is complete with INITIAL CONTEXT SETUP RESPONSE.

Accordingly, in the present invention, there is provided an entity (e.g. AMF, SMF, etc.) of a fifth generation core (5GC) comprising control circuitry to establish a Next Generation (NG) connection with a gNodeB, and a transmitter to transmit an initial context setup message to the gNodeB via the NG connection to set up a signalling radio bearer between the gNodeB and a User Equipment (UE). In particular, the gsnodeb sends radio resource control, RRC, signaling containing resource allocation configuration information elements to the UE via a signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

2020 and future IMT usage scenarios

Fig. 5 illustrates some use cases of a 5G NR. In third generation partnership project new radio (3GPP NR), three use cases are being considered which are envisaged to support a variety of services and applications through IMT-2020. The phase 1 specification of enhanced mobile broadband (eMBB) has been completed. In addition to further extending eMBB support, current and future work will also involve standardization of ultra-reliable low-latency communications (URLLC) and large-scale machine-type communications. Fig. 5 illustrates some examples of anticipated usage scenarios for IMT at 2020 and beyond.

URLLC use cases have strict requirements on capabilities such as throughput, latency and availability and are envisaged as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, transportation security, etc. The super-reliability of URLLC is supported by identifying technologies that meet the requirements specified by TR 38.913. For release 15 NR URLCC, the key requirements include a target user plane latency of 0.5ms for UL (uplink) and 0.5ms for DL (downlink). The typical URLLC requirement for one packet transmission is a BLER (block error rate) of 1E-5, a packet size of 32 bytes, and a user plane of 1 ms.

From the perspective of RAN1, reliability may be improved in a number of possible ways. Current ranges for improving the reliability of individual CQI tables defining URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR becomes more stable and advanced (critical requirements for NR URLCC), the range to achieve super-reliability may expand. Therefore, the NR URLCC of rel.15 should be able to transmit a 32 byte packet within a user plane latency of 1ms, with a success probability corresponding to a BLER of 1E-5. Specific use cases of NR URLCC of rel.15 include augmented reality/virtual reality (AR/VR), electronic health, electronic safety, and mission critical applications.

Furthermore, NR URLCC is a technological enhancement for latency improvement and reliability improvement. Technological enhancements for latency improvement include configurable parameter sets, non-slot based scheduling with flexible mapping, unlicensed (configuration-licensed) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means that the transmission of the allocated resources is stopped and the allocated resources are used for another transmission that is requested later but has a lower latency/higher priority requirement. Thus, authorized transmissions are preempted by later transmissions. Preemption applies to transmissions independent of a particular service type. For example, transmissions of service type a (urlcc) may be preempted by transmissions of service type B (such as eMBB). The technique enhancements in reliability improvement include a dedicated CQI/MCS table for the target BLER of 1E-5.

A feature of the use case of mtc is that a large number of connected devices typically transmit relatively low volumes of non-delay sensitive data. The equipment requirements are low cost and long battery life. From the NR perspective, utilizing a very narrow bandwidth portion is one possible solution to achieve power savings from the UE perspective and extend battery life.

As described above, the reliability range of NR is expected to be expanded. One key requirement in all cases, especially required by URLLC and mtc, is high reliability or over-reliability. From a radio perspective and a network perspective, several mechanisms can be considered to improve reliability. In general, there are several potential areas that help improve reliability. These areas include compact control channel information, data/control channel repetition, and diversity in the frequency, time, and/or spatial domains. These areas generally apply to reliability regardless of the particular communication scenario.

For NR URLLC, more use cases have been identified that are more demanding, such as factory automation, transportation and power distribution, including factory automation, transportation and power distribution. More stringent requirements are higher reliability (up to level 10-6), higher availability, packet size up to 256 bytes, time synchronization down to a few μm (where the value may be one or a few μm depending on the frequency range), short latency of 0.5 to 1ms, especially target user plane latency of 0.5ms depending on the use case.

Furthermore, for NR URLCC, several technology enhancements have been determined from the perspective of RAN 1. Including PDCCH (physical downlink control channel) enhancements related to compact DCI, PDCCH repetition, increased PDCCH monitoring. Furthermore, UCI (uplink control information) enhancements are related to enhanced HARQ (hybrid automatic repeat request) and CSI feedback enhancements. In addition, PUSCH enhancements related to small slot level frequency hopping and retransmission/repetition enhancements are also identified. The term "mini-slot" refers to a Transmission Time Interval (TTI) that includes fewer symbols than the number of slots (slots that include 14 symbols).

QoS control

The 5G QoS model is based on QoS flows and supports QoS flows that require a guaranteed flow bit rate (GBR QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, QoS flows are the finest granularity of QoS differentiation in PDU sessions. The QoS flow is identified in the PDU session by the QoS flow id (qfi) carried in the encapsulation header on the NG-U interface.

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) with the PDU session, and may then configure additional DRBs for the QoS flow of the PDU session (depending on when the NG-RAN does), e.g., as shown above with reference to fig. 4. The 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.

Fig. 6 illustrates a 5G NR non-roaming reference architecture. The Application Function (AF) interacts with the 3GPP core network to provide services, such as supporting application impact on traffic routing, accessing Network Exposure Function (NEF), or interacting with a policy framework for policy control (see policy control function PCF). Based on the operator deployment, application functions that the operator deems trustworthy may interact directly with the relevant network functions. The operator does not allow application functions that directly access network functions to interact with the relevant network functions via the NEF using an external public framework.

Fig. 6 shows further functional units of the 5G architecture, namely a Network Slice Selection Function (NSSF), a Network Repository Function (NRF), a Unified Data Management (UDM), an authentication server function (AUSF), an access and mobility management function (AMF), a Session Management Function (SMF) and a Data Network (DN), such as an operator service, an internet access or a third party service.

A terminal is referred to as User Equipment (UE) in LTE and NR. This may be a mobile device such as a wireless phone, a smart phone, a tablet computer or a USB (universal serial bus) stick with user equipment functionality. However, the term mobile device is not limited thereto, and in general, a relay may also have the function of such a mobile device, and the mobile device may also function as a relay.

A base station is a network node, e.g. forming part of a network for providing services to terminals. A base station is a network node that provides wireless access to terminals. The communication between the terminal and the base station is typically standardized. In LTE and NR, the radio interface protocol stack includes a physical layer, a medium access layer (MAC), and a higher layer. In the control plane, a radio resource control protocol of a higher layer is provided. Via RRC, the base station may control the configuration of the terminal, and the terminal may communicate with the base station to perform control tasks such as connection and bearer establishment, modification, measurements and other functions.

The service that transports data provided by a layer to higher layers is commonly referred to as a channel. For example, LTE and NR distinguish between logical channels provided by the MAC layer to higher layers, transport channels provided by the physical layer to the MAC layer, and physical channels that define a mapping on physical resources.

Logical channels are different types of data transmission services provided by the MAC. Each logical channel type is defined by the type of information transmitted. Logical channels are divided into two groups: control channels and traffic channels. The control channel is used only for transmitting control plane information. The traffic channel is used only for transmitting user plane information.

The MAC layer then maps the logical channels onto transport channels. For example, logical traffic channels and some logical control channels may be mapped to transport channels in the downlink, referred to as downlink shared channel, DL-SCH, and in the uplink, referred to as uplink shared channel, UL-SCH.

Scheduling

In 3GPP, scheduling in NR-based operation is described (see, e.g., 3GPP TR 38.321, NR; Medium Access Control (MAC) protocol specification, version 15.4.0).

Scheduling is a core part of communication systems such as NR and/or LTE. For each time instance, the scheduler determines to which UE the shared time-frequency resources should be allocated. Uplink, downlink, and/or sidelink transmissions may be scheduled.

In particular, the uplink scheduler may be responsible for dynamically controlling which terminals will transmit on their uplink shared channel (UL-SCH). Each scheduled terminal is provided with a scheduling grant that includes a set of resources on which the terminal should transmit its UL-SCH.

In other words, the function of uplink scheduling is to dynamically determine which devices to transmit and on which uplink resources. Dynamic scheduling is typically performed by means of a Physical Downlink Control Channel (PDCCH). The physical downlink control channel carries scheduling grants and other control information, which may also be referred to as downlink control information, DCI. Each terminal (UE) monitors the PDCCH. This means that the UE (blindly) decodes a specific resource called the search space. The PDCCH search space is a region in the downlink resource grid that may carry PDCCH. The UE performs blind decoding in these search spaces in an attempt to find PDCCH Data (DCI). To decode the PDCCH, the UE applies its own RNTI (radio network temporary identity) and attempts to decode the PDCCH in a resource called a control channel element, CCE. If the decoding is successful, which may be checked by an error detection code, such as a cyclic redundancy check, DCI is received. The UE may also blindly try various parameter values for some selected transmission parameters. Each terminal may monitor a plurality of PDCCHs. The PDCCH may be common to a group of UEs (in which case the UEs are using a common group RNTI) or dedicated to a particular UE.

The standard (LTE or NR) defines DCI in several different formats. These formats differ in their purpose. For example, the format used to carry the uplink grant (such as format 0 or 4) is different from the format carrying the downlink grant or no grant at all. Further, there are different formats defined according to the utilization of beamforming, broadcast/multicast, and the like.

Accordingly, in the uplink, control information on the physical layer is carried by a physical uplink control channel. The PUCCH carries a set of parameters called UCI (uplink control information). This is similar to the PDCCH carrying the DCI described above. The PUCCH may also adopt different formats depending on the type of information that the UCI carries in the PUCCH. For example:

format 1 carries the scheduling request SR,

format 4 carries SR and Channel State Information (CSI),

format 3 carries SR and CSI with HARQ acknowledgement (positive or negative),

there are other formats defined by LTE and/or NR.

The basis for uplink scheduling is a scheduling grant, containing device information providing information on resources and associated transport formats for transmission of the UL-SCH. In other words, a DCI with a particular format (e.g., defined in a standard) may carry a Resource Allocation (RA) corresponding to a resource grant, as well as some other transmission parameters such as a Modulation and Coding Scheme (MCS), configuration for multiple-input multiple-output (MIMO) transmission, and so on.

If the terminal has a valid grant, it is allowed to map its corresponding UL-SCH onto a Physical Uplink Shared Channel (PUSCH) specified by the resource allocation.

That is, the scheduler needs knowledge about the terminals having data to be transmitted, and thus needs to schedule uplink resources. There is no need to provide uplink resources to devices that have no data to transmit as this will result in the devices performing padding to fill in the granted resources. Thus, the scheduler needs to know whether the device has data to transmit and should be granted.

Scheduling requests

The scheduling request may be for terminals that do not have a valid scheduling grant. The scheduling request may be transmitted on a physical uplink control channel, PUCCH. Each terminal may be assigned dedicated scheduling request resources, occurring every nth sub-frame. The scheduling request may be a simple flag, set by the terminal to request uplink resources from the uplink scheduler. By means of a dedicated scheduling request mechanism, the identity of the requesting terminal does not have to be provided together with the scheduling request, since the identity of the terminal is implicitly known from the resource transmitting the request. These are configured by the scheduling node (such as the gNB), e.g. by a higher layer control protocol.

Upon receiving the scheduling request, the scheduling device may assign a scheduling grant to the terminal. If the terminal receives a scheduling grant, it will transmit its data in the scheduling resources. The data to be transmitted on the PUSCH may include, in a first buffer state, a notification to the scheduling node of the amount of data the UE has to transmit. Based on the buffer status, the scheduling node may then schedule the actual data resources on the PUSCH. However, this is only an option and in general, data resources may also be scheduled directly. In some systems, a scheduling request may also be associated with a particular amount of data that is requested to be scheduled.

The scheduling request may be repeated if the terminal does not receive a scheduling grant until the next possible moment.

Thus, a contention-free scheduling request mechanism is provided on PUCCH, where each terminal in a cell is given a reserved resource on which a request for uplink resources can be transmitted.

The UE MAC entity may be configured with zero, one or more SR configurations. The SR configuration consists of a PUCCH resource set for scheduling requests across different bandwidth parts (BWPs). For Logical Channel (LCH), at most one PUCCH resource is configured for SR per BWP. Each SR configuration corresponds to one or more logical channels. The mapping between logical channels and SR configuration may be configured through Radio Resource Control (RRC) messages.

As described above, when a regular Buffer Status Report (BSR) is triggered in the UE but uplink radio resources for transmitting the BSR are unavailable, an SR procedure may be initiated. During the SR procedure, the UE may perform transmission of the SR through the PUCCH or initiate a Random Access (RA) procedure, depending on whether the UE is configured with PUCCH resources for the SR. The RA procedure is only initiated when PUCCH resources for SR are not configured.

When the UE MAC entity has an SR transmission position on the configured valid PUCCH resource for SR, it instructs a physical layer (PHY) to signal the SR on one valid PUCCH resource for SR. Subsequently, the SR prohibit timer starts (SR _ prohibit timer). At consecutive SR transmission occasions, if the SR prohibit timer is running, the MAC does not instruct the PHY to signal the SR.

In NR, SR resources are configured with a certain periodicity. Once the UE transmits the SR, the SR prohibit timer is started, and the SR is not transmitted on the already configured resources as long as the SR prohibit timer is running.

The scheduling request configuration information element for configuring the scheduling request is defined in 3GPP TS 38.331 ("NR; Radio Resource Control (RRC); Protocol specification", version 15.4.0, section 6.3.2), as follows.

SchedulingRequestConfig information element

Specifically, the scheduling request prohibit timer is configured by the SR-ProhibitTimer and indicates a duration for which the scheduling request is not transmitted after transmission of the SR, even if no scheduling grant is received. The maximum number of scheduling requests is defined by sr-TransMax. For example, sr-ProhibitTimer and sr-TransMax are provided to the UE from the scheduling node via RRC signaling.

When the prohibit timer (SR-prohibit timer) is active, the SR will not be restarted. The SR-ProhibitTimer is configured for each SR and may be set to a value in the range of 1ms to 128 ms.

For example, if the gNB configures the SR-ProhibitTimer as 32ms, the gNB may allocate uplink resources within 32ms after receiving the SR, and the UE needs to monitor the PDCCH for a maximum of 32ms after transmitting the SR.

Discontinuous reception-DRX

Packet data is typically highly bursty and occasionally silences for some time. From a delay perspective, it is beneficial to permanently monitor downlink control signaling to receive uplink grants or downlink data transmissions and react instantaneously to changes in traffic behavior. At the same time, this is also a penalty in terms of power consumption of the device. To reduce device power consumption, LTE includes mechanisms for Discontinuous Reception (DRX).

The basic mechanism of DRX is a configurable DRX cycle in the device. With the DRX cycles configured, the device monitors downlink control signaling only for active periods of each DRX cycle, and sleeps with the receiver circuitry off for the remaining inactive periods. This allows a significant reduction in power consumption. This, of course, implies a limitation on the scheduler, since the device can only be addressed during active periods.

The DRX cycle may be configured in the LTE downlink such that the UE does not have to decode a Physical Downlink Control Channel (PDCCH) or receive a Physical Downlink Shared Channel (PDSCH) transmission in certain periods by periodically turning off the receiver, as defined in 3GPP TS 36.321 "(Evolved Universal Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification", version 15.5.0, section 5.7) for connected modes, and as defined in 3GPP TS 36.304 ("Evolved Universal Radio Access (E-UTRA); User Equipment (UE) protocol in idle", version 15.3.0, section 7.1) for idle modes.

According to the 3GPP TS 38.321v15.5.0 specification, when the DRX cycle is configured, the active time includes the time that DRX-onDurationTimer, DRX-inactivytimer, DRX-retransmission timerdl, DRX-retransmission timerrl, or ra-contentresourcestationtimer runs, as described in 3GPP TS 38.321, section 5.1.5.

The DRX-onDurationTimer defines a duration at the beginning of the DRX cycle, and the DRX-inactivity timer specifies a duration after a PDCCH occasion when the PDCCH indicates a new Uplink (UL) or Downlink (DL) transmission by the MAC entity. drx-retransmission timerdl and-UL define the longest duration before receiving a DL retransmission and the longest duration before receiving a UL retransmission grant, respectively.

Further, the active time includes a time when a PDCCH indicating a new transmission of a cell radio network temporary identifier (C-RNTI) addressed to the MAC entity is not received after successfully receiving a random access response for a random access preamble that is not selected by the MAC entity in the contention-based random access preamble, as described in section 5.1.4 of 3GPP TS 38.321 v15.5.0.

As described above, the UE requests radio resources for a new uplink transmission using a scheduling request procedure. In particular, during the time when a scheduling request has been sent and is in a suspended state, the PDCCH is monitored for scheduling assignments as described in 3GPP TS 38.321v15.5.0 section 5.4.4.

That is, when the SR is transmitted on the PUCCH and suspended, the PDCCH is monitored. Fig. 7 schematically shows active and inactive times (on period and off period) according to a configured DRX cycle (solid line) and active times due to a pending scheduling request (dotted line). In fig. 7, time is shown on the horizontal axis. Once the SR is transmitted on the PUCCH, the UE starts monitoring the PDCCH for an uplink grant of scheduling data to be transmitted, as indicated by the arrow labeled "SR" in fig. 7.

However, the UE may not be scheduled immediately after the scheduling request is transmitted. Fig. 8A and 8B schematically show active and inactive times according to a configured DRX cycle and active times due to a pending scheduling request. In the figure, the point in time when an uplink grant (UL grant) is received is indicated by an arrow labeled "UL grant". The PDCCH is monitored for UL grants as long as the SR is in a suspended state.

In the case shown in fig. 8B, the UL grant is received at a longer point in time after the SR transmission than in the case shown in fig. 8A. This may be the case when the scheduling device prioritizes the scheduling of UL grants based on the priority and traffic load of the associated logical channels.

As a result, the UE consumes power in monitoring the PDCCH during periods when the gNB does not intend to schedule UL grants to the UE. This period is shown as a shaded area in fig. 8A and 8B. During periods when no UL grant is transmitted, the UE monitors the PDCCH and thus consumes power.

Techniques are provided to facilitate adjusting monitoring duration within the framework of an SR process. In particular, the present invention provides an SR procedure for reducing power consumption of a UE in a configured DRX cycle.

The present invention provides a transceiver apparatus and a scheduling apparatus as shown in fig. 9.

The transceiver apparatus 100 comprises a transceiver 110 (transmitter and/or receiver, comprising hardware components such as one or more antennas and control circuitry controlling the operation of the hardware components) for transmitting scheduling requests for scheduling data over a physical uplink control channel, PUCCH. In addition, the transceiver device 100 includes circuitry 120 (or processing circuitry) to start a watchdog timer after the transceiver 110 transmits a scheduling request. Further, the transceiver 110 does not monitor the physical downlink control channel PDCCH while the monitoring dormancy timer is running, and starts monitoring the PDCCH for resource allocation for scheduling data when the monitoring dormancy timer expires.

For example, the transceiver apparatus 100 is a UE in an NR network. Accordingly, transceiver 110 and circuitry 120 are also referred to as "UE transceiver" and "UE circuitry". However, these terms are only used to distinguish the transceiver 110 and the circuitry 120 from circuitry and transceivers comprised by other devices, such as a scheduling device or a base station. The transceiver device 100 may be a terminal service, a relay device or a communication device like a communication system. The UE circuitry may be considered or include "monitor sleep control circuitry".

A scheduling apparatus 200 (or scheduling node) as shown in fig. 9 is also provided.

The scheduling apparatus 200 comprises a circuit 220 which allocates resources according to a scheduling request for scheduling data and starts a transmission timer. The scheduling apparatus 200 further comprises a transceiver 210 which receives a scheduling request over a physical uplink control channel, PUCCH, and after expiration of a transmission timer, transmits a resource allocation indicator indicating the allocated resource over a physical downlink control channel, PDCCH.

The scheduling apparatus 200 is, for example, a network node (base station) in an NR network system (gNB) or similar communication system. The circuitry 220 is also referred to as "scheduling request control circuitry" or "scheduling apparatus circuitry" to distinguish it from circuitry such as the UE circuitry 120.

A method is also provided that includes transmitting a scheduling request for scheduling data over a physical uplink control channel, PUCCH, and starting a watchdog dormancy timer after transmitting the scheduling request. Further, the method includes preventing monitoring of a physical downlink control channel, PDCCH, while monitoring the dormancy timer is running, and starting monitoring of the PDCCH for resource allocations for scheduling data when the monitoring dormancy timer expires.

A method is also provided that includes receiving a scheduling request for scheduling data over a physical uplink control channel, PUCCH, and starting a transmission timer. The method also includes allocating resources according to the scheduling request and transmitting a resource allocation indicator indicating the allocated resources through a physical downlink control channel, PDCCH, after a transmission timer expires.

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

The transceiver apparatus 100 transmits a scheduling request for transmitting scheduling data through the PUCCH using the transceiver 110 and starts a monitoring sleep timer using the UE circuit 120 after the SR has been transmitted. When the monitoring sleep timer is running, the transceiver 110 does not monitor the PDCCH for receiving a UL grant corresponding to the transmitted SR. After the monitoring sleep timer expires, the transceiver 110 starts monitoring the PDCCH for receiving a UL grant according to the transmitted SR, wherein the UL grant indicates allocated resources for transmitting scheduling data.

A time sequence is schematically shown in fig. 10, in which, when the DRX cycle is configured, the UE (or specifically, the transceiver) monitors the PDCCH during an active period and does not monitor the PDCCH during an inactive period.

According to one embodiment, once the SR is transmitted, a monitoring dormancy timer is started, and when the monitoring dormancy timer has expired, the transceiver 110 starts monitoring the PDCCH for the UL grant from the scheduling apparatus 200. That is, according to the present embodiment, when the transceiver 110 transmits a scheduling request, the monitoring sleep timer is started.

With this procedure, the power consumption of the UE is reduced because the active time monitoring PDCCH of the UE is reduced by running the monitoring dormancy timer in a period in which the SR is suspended but the scheduling device does not intend to transmit the UL grant.

Fig. 11 is a flow diagram illustrating transmission of a scheduling request and starting monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer, according to an embodiment.

After the process starts, in step S100, it is determined whether the DRX mode is configured, i.e., whether the UE is in the DRX mode. In case it is determined that the UE is not in DRX mode (no in step S100), the procedure is repeated at the beginning. In the case where it is determined that the UE is in the DRX mode (yes in step S100), the procedure proceeds to step S110.

In step S110, it is determined whether an SR is transmitted. For example, as shown in fig. 9, it is determined whether the transceiver 110 has transmitted a scheduling request for scheduling data to be transmitted to the scheduling device 200 through the PUCCH. In the case where the scheduling request is not transmitted (no in step S110), the process repeats step S110. In the case where it is determined that the SR has been transmitted (yes in step S110), the process proceeds to step S120.

In step S120, a monitor sleep timer is started. For example, as shown in fig. 9, the circuitry 120 of the transceiver device 100 starts a watchdog sleep timer. For example, the operation of the monitoring sleep timer may be defined by a duration or an offset of a specific symbol or slot of the PDCCH. This is described below. Further, monitoring the operation of the dormancy timer may be configured according to a scheduling request configuration, as described below. While the monitoring dormancy timer is running (i.e., not expired), the PDCCH is not monitored for UL grants of scheduling data.

In step S130, it is determined whether the monitor sleep timer has expired. In the case where the monitoring sleep timer has not expired (no in step S130), the procedure remains at step S130, and determination is repeatedly made as to whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has expired (yes in step S130), the process proceeds to step S140.

In step S140, monitoring of the PDCCH for receiving resource allocation (UL grant) of scheduling data corresponding to the scheduling request transmitted in step S110 is started.

As described above, the operation of the monitoring sleep timer may be separately configured according to the priority of the service, i.e., the value of the monitoring sleep timer may be separately configured in each SR configuration. That is, the operation of the sleep timer is monitored according to the priority level configuration of the scheduling request configuration.

For example, for an SR configuration of a first priority level, the operation of the watchdog timer may be set to a smaller value than an SR configuration of a second priority level lower than the first priority level.

In other words, an SR having a higher priority and a smaller latency may be configured with an operation of a relatively smaller watchdog timer, and an SR having a lower priority and a larger latency may be configured with an operation of a relatively larger watchdog timer. In this case, the power saving effect of the higher priority and lower latency services is small compared to the lower priority and higher latency services.

As described above, after the transceiver 110 transmits the SR, the UE circuitry 120 applies the run of the watchdog timer corresponding to the SR configuration.

As shown in fig. 12, a first run of the monitoring dormancy timer may be configured for a first logical channel, and a second run of the monitoring dormancy timer may be configured for a second logical channel. Thus, the operation of monitoring the sleep timer may differ depending on the logical channel. In particular, a lower priority logical channel may be configured with a larger runtime supervision sleep timer than a higher priority logical channel, and vice versa. As shown in fig. 12, LCH1 and LCH2 are mapped to different SR configurations because LCH1 and LCH2 have different priorities.

Although in fig. 12, the mapping of monitoring the runtime of the dormancy timer is shown for two logical channels, the present embodiment is not limited thereto, and different runtimes of the dormancy timer may be monitored for multiple logical channel/SR configuration configurations.

For example, as shown in fig. 13, two logical channels of the same priority level (LCH1 and LCH2) are mapped to a single SR configuration, and a single runtime monitoring the dormancy timer is mapped to the SR configuration.

Although in fig. 12 and 13, one-to-one mapping of runtime, SR configuration, and logical channel or mapping of multiple logical channels to a single SR configuration is illustrated, the present embodiment is not limited thereto, and a combination of mapping of a single SR configuration to multiple logical channels and mapping of a single SR configuration to a single logical channel may be applied.

According to one embodiment, the runtime of the watchdog timer is fixed, wherein the network/scheduling device 200 and the transceiver device 100 map each SR configuration with a predefined runtime of the watchdog timer. In particular, the mapping may depend on the logical channel (SR) priority, such that it is defined which logical channel corresponds to which run of the monitoring dormancy timer. With this approach, no additional signaling is required.

For example, table 1 shows fixed values in the specification. As shown in table 1, the operation of the supervision sleep timer is indicated for the scheduling request identifiers 0 to 7 according to the symbol (sym) or slot (sl) offset. For example, for scheduling request identifier 5, transceiver 110 does not monitor PDCCH for an UL grant of 8 slots. Alternatively, the operation of the monitoring sleep timer may be configured according to a duration (e.g., a duration from 0 to 256 ms).

schedulingRequestID	Timer/offset
		0	sym2
1	sym6
		2	sl1
3	sl2
		4	sl4
5	sl8
		6	sl10
7	sl16

Table 1: a fixed value of sleep timer run/offset is monitored.

For example, when the logical channel LCH1 maps to SR configuration 1 and a scheduling request is triggered due to LCH1, the MAC passes schedulingRequestID information to the PHY to transmit the scheduling request. If the SR configuration of LCH1 is associated with schedulingRequestID 5, the UE runs with 8ms supervision dormancy timer.

The transceiver device 100 may receive the scheduling request configuration by a scheduling request configuration indicator indicating at least one scheduling request configuration having at least an associated priority level.

For example, the transceiver 110 may receive the scheduling request configuration indicator via a radio resource control, RRC, message.

According to one embodiment, the network signals the runtime of the watchdog dormancy timer for each SR configuration, such that the watchdog dormancy timer runtime may be dynamically configured. For example, the monitoring sleep timer running may be signaled via an RRC message (system information message or dedicated RRC message). In this way, the network can take into account the current traffic load and change the run time via RRC messages.

For example, a scheduling request configuration information element for RRC signaling that can be used for configuration of a scheduling request is as follows.

SchedulinRequestResourceConfig information element

Specifically, the monitoring sleep timer is configured by a timer/offset, and the operation of the monitoring sleep timer is indicated according to a symbol of a slot of the PDCCH.

According to one embodiment, if network/gNB 200 does not intend to schedule UL resources after receiving a scheduling request for scheduling data, network/gNB 200 may determine a runtime to monitor the dormancy timer and transmit the determined runtime to UE 100.

For example, a MAC control element indicating the monitoring of the runtime of the dormancy timer may be sent in a bitmap format carrying timing related information.

For example, in LTE, the MAC layer may insert a so-called MAC control element (MAC CE) into a transport block for transmission over a transport channel. The MAC CE is used for in-band control signaling, e.g., timing advance commands or random access responses.

However, in accordance with the present invention, the MAC CE may carry information about monitoring the operation of the dormancy timer, where the MAC CE may indicate a duration in the range of 0 to 256, for example. The time unit of the length may be a duration (ms) or a number of symbols or a number of slots.

Fig. 14 schematically shows a MAC control element CE indicating the operation of monitoring a dormancy timer according to an embodiment. For example, if the UE100 receives a MAC CE command indicating "000010000", the UE does not monitor the PDCCH for a resource scheduled for 8ms or 8 slots.

Fig. 15 schematically shows a time sequence of transmission of a scheduling request, monitoring for reception of a sleep indicator and reception of an uplink grant and an active period according to an embodiment. Specifically, the transceiver 110 transmits a scheduling request for scheduling data and monitors the PDCCH for a UL grant. When a MAC CE is received indicating a runtime to monitor the dormancy timer (as indicated by the arrow indicated with "MAC CE"), circuitry 120 starts the monitoring dormancy timer with the associated runtime according to the received runtime indicated by the MAC CE. As long as the monitoring dormancy timer is running, the transceiver 110 does not monitor the PDCCH for a scheduling assignment of scheduling data corresponding to the transmitted scheduling request. When the monitoring dormancy timer has expired, the transceiver 110 starts monitoring the PDCCH for UL grants.

That is, transceiver 110 receives a monitor sleep indicator (e.g., MAC CE) indicating the operation of a monitor sleep timer, and when transceiver receives the monitor sleep indicator, circuitry 120 starts the monitor sleep timer

By this method, the transceiver 110 of the transceiver apparatus 100 does not monitor the PDCCH for the time period of the duration indicated by the received MAC CE. Thus, by considering both traffic load and SR priority, UE power saving can be achieved in a more dynamic manner

Fig. 16 is a flow diagram illustrating transmission of a scheduling request, monitoring for receipt of a dormancy indicator, and beginning monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer.

After the process starts, in step S200, it is determined whether the DRX mode is configured, i.e., whether the UE is in the DRX mode. In case it is determined that the UE is not in DRX mode (no in step S200), the process repeats at the beginning. In the case where it is determined that the UE is in the DRX mode (yes in step S200), the procedure proceeds to step S210.

In step S210, it is determined whether an SR has been transmitted. For example, it is determined whether the transceiver 110 has transmitted a scheduling request for scheduling data to be transmitted to the scheduling device 200 through the PUCCH. In the case where the scheduling request is not transmitted (no in step S210), the process repeats step S210. In the case where it is determined that the SR has been transmitted (yes in step S210), the process proceeds to step S220.

In step S220, monitoring of the PDCCH is started. In step S230, it is determined whether a MAC CE indicating the operation of monitoring the sleep timer is received. In the case where the MAC CE indicating the operation is not received (no in step S230), the procedure repeats monitoring of the PDCCH. In the case where the MAC CE indicating the monitoring of the operation of the sleep timer is received (yes in step S240), the procedure proceeds to step S240.

In step S240, a monitoring sleep timer is started with a runtime corresponding to the runtime indicated by the MAC CE. In addition, monitoring of the PDCCH is terminated. That is, while the monitoring dormancy timer is running, i.e., has not expired, for example, the PDCCH is not monitored by the transceiver 110.

In step S250, it is determined whether the watchdog sleep timer has expired. In the case where the monitoring sleep timer has not expired (no in step S250), the procedure remains at step S250, and determination is repeatedly made as to whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has expired (yes in step S250), the process proceeds to step S260.

In step S260, monitoring of the PDCCH for receiving resource allocation (UL grant) of scheduling data corresponding to the transmitted scheduling request is started.

According to this embodiment, monitoring the run time of the sleep timer is signaled by the scheduling apparatus 200 using a MAC control element. However, the present invention is not limited to transmission using MAC CEs, and monitoring the operation of the dormancy timer may be another transmission method. In particular, the scheduling apparatus 200 may transmit a monitor sleep indicator indicating the operation of the monitor sleep timer, and the UE circuitry 120 may start the monitor sleep timer upon receiving the monitor sleep indicator.

Needless to say, in the case where the UL grant can be received through the PDCCH without receiving the monitoring indicator. In this case, it is no longer necessary to monitor the PDCCH due to the pending scheduling request.

Further, according to the above-described embodiments, the monitoring sleep timer may be started, for example, by the MAC CE when a scheduling request is transmitted or a monitoring sleep indicator is received.

In a first example, monitoring of the PDCCH is not started immediately after the scheduling request is transmitted, but rather a monitoring sleep timer is started and monitoring is started after expiration.

In a second example, monitoring of the PDCCH starts when a scheduling request is transmitted, and when a monitoring sleep indicator is received, monitoring of the PDCCH is interrupted for a duration corresponding to operation of monitoring the sleep indicator indication.

However, the present invention is not limited to any of the embodiments. In particular, monitoring of the PDCCH may not be performed between transmission of the SR and expiration of the monitoring sleep timer and between reception of the monitoring sleep indicator and expiration of the corresponding monitoring sleep timer. In other words, the methods of the above examples may be combined.

This is shown in fig. 17, in which a shaded region indicates a period in which the PDCCH is not monitored due to a monitoring sleep timer started when the SR is transmitted. Further, when a MAC CE indicating a run-time of the monitoring sleep timer is received, the monitoring sleep timer may be restarted using the received run-time, or a second monitoring sleep timer may be started such that the PDCCH is not monitored for a duration period indicated by the MAC CE.

Note that for this case, the watchdog sleep timer in accordance with one or more embodiments may be restarted or restarted by circuitry 120. In other words, where the sleep timer is monitored as running, the timer may be restarted or its remaining or total run time may be adjusted until expiration. Alternatively or additionally, an additional watchdog dormancy timer may be started.

The scheduling apparatus 200 according to an embodiment may determine to monitor the operation of the sleep timer and transmit a monitor sleep indicator indicating the operation of the sleep timer using the transceiver 210. In particular, the running of the transmission timer may correspond to monitoring the running of the dormancy timer.

Further, in the above-described embodiment, it is determined whether the DRX cycle is configured for the transceiver apparatus 100. However, the present invention is not limited to determining whether a DRX cycle is configured. In particular, the configured DRX cycle is not a mandatory requirement to start monitoring the dormancy timer and not monitor the PDCCH as long as the monitoring dormancy timer is running.

The present invention also provides an SR procedure for reducing power consumption of a UE in a configured DRX cycle.

As shown in fig. 9, the transceiver device 100 includes a transceiver 110 (a transmitter and/or receiver including hardware components such as one or more antennas and control circuitry that controls operation of the hardware components) that transmits a buffer status report indicating a scheduled data amount. In addition, the transceiver device 100 includes circuitry 120 (or processing circuitry) to start a monitor sleep timer after the transceiver 110 transmits the buffer status report. Further, the transceiver 110 does not monitor the physical downlink control channel PDCCH when the monitoring dormancy timer is running, and starts monitoring the PDCCH for resource allocation of scheduling data when the monitoring dormancy timer expires.

A scheduling apparatus 200 (or scheduling node) as shown in fig. 9 is also provided.

The scheduling apparatus 200 comprises a circuit 220 for allocating resources according to a buffer status report indicating a scheduled data amount and starting a transmission timer; the scheduling apparatus 200 further comprises a transceiver 210 which receives the buffer status report and transmits a resource allocation indicator indicating the allocated resource through a physical downlink control channel, PDCCH, after the transmission timer expires.

A method is also provided that includes transmitting a buffer status report indicating an amount of scheduled data, and starting a watch sleep timer after transmitting the buffer status report. Further, the method includes preventing monitoring of a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running, and starting monitoring of the PDCCH for resource allocation of scheduling data when the monitoring dormancy timer has expired.

A method is also provided that includes receiving a buffer status report indicating an amount of scheduled data, and starting a transmission timer. The method also includes allocating resources according to the buffer status report, and transmitting a resource allocation indicator indicating the allocated resources through a physical downlink control channel, PDCCH, after expiration of a transmission timer.

The buffer status report BSR may be a Medium Access Control (MAC) -level message transmitted by the UE100 to the serving gbb as the scheduling device 200 in order to provide the gbb with information about the amount of data in the uplink buffer of the UE100 (see 3GPP TS 36.321 ("Evolved Universal Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification", version 15.5.0, section 5.4.5).

Reporting the BSR in the uplink informs the gNB 200 about the amount of buffered data at the UE100 and allows the gNB 200 to distinguish between data having different scheduling priorities, since BSR reporting is performed for each Logical Channel Group (LCG), where each LCG may be associated with a respective priority level.

The LCG is a set of uplink logical channels, or a single joint buffer fill level is reported in the BSR by the UE 100. The mapping of the LCG may be defined by gNB 200 (see 3GPP TS 36.321 ("Evolved Universal Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification," version 15.5.1, section 6.3.2.) the LCG may be defined as a set of logical channels with similar QoS (quality of service) requirements.

Buffer status reporting may be performed by using either the long BSR format or the short BSR format, respectively (as shown in fig. 18A and 18B, respectively), per LCG. Fig. 18A is an illustration of a short BSR format in which the logical channel group whose buffer status is being reported is indicated by a logical channel group ID field of three bits in length. Further, the buffer size field indicates the total amount of data. According to the long BSR format as shown in fig. 18B, the BSR contains a plurality of buffer size fields, each of which represents one LCG. In other words, the short BSR format is used to report the data amount of one indicated logical channel group, and the long BSR format is used to report the data amount of all logical channel groups. For example, the network may configure up to eight logical channel groups per UE, depending on quality of service (QoS) requirements.

When transmitting a BSR during a DRX off period, the UE may switch to a DRX active time during which the PDCCH is monitored for receiving uplink grants. This is shown in FIG. 19

However, monitoring the PDCCH by inputting the DRX activity time due to transmission of the BSR may cause unnecessary power consumption because the UE100 may not be scheduled immediately after transmitting the BSR. In other words, in case the gNB 200 does not intend to schedule resources to the UE100, e.g. when the scheduling of UL grants is based on the BSR's priority level and traffic load, the UE100 may not have to monitor the PUCCH for uplink grants. For example, as shown in fig. 20A and 20B, a higher priority of BSR transmission may result in a shorter PDCCH monitoring period than a lower priority of BSR transmission (resulting in a longer PDCCH monitoring period).

Accordingly, the transceiver device 100 transmits a BSR indicating the amount of scheduled data using the transceiver 110, and starts a monitor sleep timer using the UE circuit 120 after transmission of the BSR. While the monitoring sleep timer is running, transceiver 110 does not monitor the PDCCH for receiving UL grants corresponding to the transmitted SR. After the monitoring sleep timer expires, transceiver 110 starts monitoring the PDCCH according to the transmitted BSR for receiving an UL grant indicating allocated resources for transmitting scheduling data.

Fig. 21 schematically shows a time sequence in which a UE (or specifically, a transceiver) monitors a PDCCH during an active period and does not monitor the PDCCH during an inactive period. Specifically, after the BSR has been transmitted, a monitoring dormancy timer is started, and when the timer expires, the UE100 switches to an active time, in which the PDCCH is monitored for an uplink grant. In other words, switching from not monitoring to monitoring the PDCCH is delayed by a time offset from the transmission of the BSR.

Fig. 22 shows a method performed by the UE 100. Steps S300, S310, S330 and S340 correspond to the method shown in fig. 11, wherein a buffer status report is sent instead of a scheduling request SR. In step S320, a monitoring sleep timer is started with runtime according to the logical channel group LCG.

For example, a runtime may be configured for each LCG. For example, an LCG with a higher priority may be associated with a shorter watchdog dormancy timer running than an LCG with a lower priority.

The mapping of LCGs and the monitoring of the sleep timers may be predefined (e.g., according to definitions given in the specification documentation) or dynamically configured (e.g., via RRC).

Table 2 illustrates fixed values for monitoring sleep timer operation. As shown, the operation of the watch sleep timer is represented by X1 through X10, associated with LCGs having identifier IDs 0 through 7, respectively. For example, in the case where the priority is decreased from LGC ID 0 to LCG ID 7, the operation of the monitoring sleep timer may be increased from X1 to X10. In other words, the lower the level of the associated LCG, the greater the runtime of the watchdog timer may be. The predefined runtime/offset does not require additional signaling.

Table 2: a fixed value of the watchdog timer run/offset for each LCG ID.

Alternatively or additionally, monitoring the operation of the dormancy timer may be dynamically configured, e.g., by RRC. With the mapping between dynamically configured LCG IDs and offset/timer runtimes, the network can take into account traffic load and traffic priority and change the timer runtimes/offsets as needed via RRC (e.g., via system information messages or dedicated RRC messages).

For example, the logical channel configuration information element of the RRC signaling that can be used is as follows.

LogicalChannelConfig information element

Specifically, the "locatalcannel group offset" of each logical channel group indicates that the supervision sleeping timer is running.

In the case where the BSR indicates a plurality of scheduled data amounts associated with different LCGs, the runtime of the monitoring timer may be set to the runtime associated with the highest priority logical channel group for which the scheduled data amount is indicated in the BSR. Alternatively, the runtime monitoring the dormancy timer may be set to the runtime associated with the LCG with the lowest LCG ID. Alternatively, the runtime monitoring the dormancy timer may be set to the shortest runtime associated with the LCG for which the amount of scheduled data is indicated in the BSR.

In summary, according to embodiments of the present disclosure, a transceiver device, such as UE100, sends a scheduling request or buffer status report and then starts a dedicated timer, i.e., a supervision dormancy timer. As long as the timer has not expired, the UE100 does not monitor the PDCCH for receiving uplink grants. When the timer expires, the UE starts monitoring the PDCCH. This may allow for a reduction in energy consumption, since the UE100 does not monitor the PDCCH when scheduling authorization is not desired.

The supervision dormancy timer may be started only after sending a scheduling request, or only after sending a buffer status report, or both after sending a scheduling request and after sending a buffer status report. In the last case, the running of the timer started after the SR is transmitted may be equal to the running of the timer started by runti after the BSR is transmitted. However, the present invention is not limited thereto, and the operation of the timer started after the SR is transmitted may be different from the operation of the timer started after the BSR is transmitted.

An example of a scheduling request procedure is shown in fig. 23A, where SR and BSR are transmitted from the UE100 to the gNB 200. In step 1, a scheduling request is sent by UE100 to the gNB 200 over PUCCH. Further, in step 2, the UE100 receives a scheduling grant indicating resources for transmitting scheduling data from the gNB. In step 3, the UE100 transmits a buffer status report to the gNB 200 using the indicated resources of the PUSCH. In step 4, the UE100 receives a scheduling grant for transmitting scheduling data from the gNB 200. In step 5, the UE100 transmits scheduling data using the resources indicated by the received uplink grant.

As shown in fig. 23B, according to the present invention, the UE100 starts a monitoring sleep timer after having transmitted an SR through the PUCCH, and does not monitor the PDCCH for receiving an uplink grant when the timer has not expired, i.e., for a period indicated as an offset/sleep period. After the expiration of the monitoring dormancy timer, the UE100 monitors the PDCCH for receiving an uplink grant for a period indicated as a UE awake period.

Further, as shown in fig. 23C, the UE starts a monitoring sleep timer after transmitting the BSR (i.e., after step 3), and does not monitor the PDCCH when the monitoring sleep timer has not expired (i.e., during a period indicated as an offset/sleep period). When the timer has expired, the UE 1200 starts monitoring the PDCCH for receiving data uplink grants.

The UE100 may start the monitoring sleep timer after transmission of the SR, after transmission of the BSR, or after transmission of each. The operation of the monitoring sleep timer started after the transmission of the SR may be equal to or different from the operation of the monitoring sleep timer started after the transmission of the BSR.

The present invention can be realized in software, hardware, or software in combination with hardware. Each of the functional blocks used in the description of each of the embodiments described above may be partially or entirely realized by an LSI (large scale integration) such as an Integrated Circuit (IC), and each of the processes described in each of the embodiments may be partially or entirely controlled by the same LSI or a combination of LSIs. The LSI may be formed solely as a chip, or may be formed as one chip to include a part or all of the functional blocks. The LSI may include data inputs and outputs coupled thereto. Here, the LSI may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI, depending on the degree of integration. However, the technique of implementing an integrated circuit is not limited to the LSI, and may be implemented using a dedicated circuit, a general-purpose processor, or a dedicated processor. In addition, an FPGA (field programmable gate array) may be programmed after manufacturing an LSI or a reconfigurable processor, in which connection and setting of circuit cells configured inside the LSI may be used. The invention may be implemented as digital processing or analog processing. If future integrated circuit technologies are developed as semiconductor technologies or other derivative technologies to replace LSIs as reconfigurable processors, the functional blocks can be integrated using the future integrated circuit technologies. Biotechnology may also be applied.

The invention may be implemented by any type of apparatus, device or system having communication capabilities, referred to as a communication device.

Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablets, Personal Computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still/video cameras), digital players (digital audio/video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, remote health/telemedicine (telehealth and medical) devices, and vehicles that provide communication functionality (e.g., automobiles, airplanes, boats), and various combinations thereof.

The communication devices are not limited to being portable or mobile, and may also include any type of device, apparatus, or system that is not portable or stationary, such as smart home equipment (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "thing" in an internet of things (IoT) "network.

The communication may include exchanging data via, for example, a cellular system, a wireless LAN system, a satellite system, and the like, as well as various combinations thereof.

The communication means may comprise a device, such as a controller or sensor, coupled to a communication device that performs the communication functions described in this disclosure. For example, the communication device may include a controller or sensor that generates control signals or data signals for use by a communication apparatus that performs the communication function of the communication device.

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

As described above, an apparatus and method capable of providing a scheduling request and a resource allocation indication that are flexible and reduce power consumption are provided.

There is provided a transceiver device comprising: a transceiver for transmitting a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH); and circuitry to start a monitoring dormancy timer after the transceiver transmits a scheduling request, wherein the transceiver does not monitor a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running, and starts monitoring the PDCCH for resource allocations for scheduling data when the monitoring dormancy timer expires.

In some embodiments, the circuit starts a watchdog sleep timer when a scheduling request is sent by the transceiver.

In some embodiments, the transceiver receives a monitor sleep indicator indicating the operation of a monitor sleep timer; and when the transceiver receives the monitor sleep indicator, the circuit starts a monitor sleep timer.

For example, the monitor sleep indicator indicates the operation of the monitor sleep timer according to the duration or symbol of the PDCCH and/or the number of slots.

In some embodiments, monitoring the operation of the dormancy timer is configured according to a priority level configured by the scheduling request.

For example, configuring a first runtime to monitor a dormancy timer for a first scheduling request having a first priority level; configuring a second runtime, different from the first runtime monitoring the dormancy timer, for a second scheduling request configuration having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, a transceiver receives a scheduling request configuration indicator indicating at least one scheduling request configuration having at least one associated priority level.

For example, the transceiver receives a scheduling request configuration indicator via a radio resource control, RRC, message.

In some embodiments, a discontinuous reception DRX cycle is configured in which the transceiver monitors the PDCCH in active periods and does not monitor the PDCCH in inactive periods.

There is also provided a transceiver device comprising: a transceiver to transmit a buffer status report indicating at least a scheduled data amount; and circuitry to start a monitoring dormancy timer after the transceiver transmits the buffer status report, wherein the transceiver does not monitor a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running and starts monitoring the PDCCH for resource allocations for scheduling data when the monitoring dormancy timer expires.

In some embodiments, the buffer status report is sent over a physical uplink shared channel, PUSCH.

In some embodiments, the circuit starts a watchdog sleep timer when a buffer status report is sent by the transceiver.

In some embodiments, the transceiver receives a monitor sleep indicator indicating the operation of a monitor sleep timer; and when the transceiver receives the monitor sleep indicator, the circuit starts a monitor sleep timer.

In some embodiments, the monitoring sleep indicator indicates the operation of the monitoring sleep timer in accordance with the duration or symbol of the PDCCH and/or the number of slots.

In some embodiments, the operation of the dormancy timer is monitored according to a logical channel group configuration.

For example, the buffer status report also indicates the logical channel group associated with the amount of scheduled data.

In some embodiments, the buffer status report indicates a plurality of logical channel groups, each logical channel group being associated with a respective amount of scheduling data.

For example, each logical channel group is associated with a respective runtime that monitors a dormancy timer.

For example, the runtime monitoring the dormancy timer may be set to the runtime associated with the LCG having the highest priority.

In some embodiments, a first runtime monitoring the dormancy timer is configured for a first logical channel group having a first priority level, and a second runtime different from the first runtime monitoring the dormancy timer is configured for a second logical channel group having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, the transceiver receives a logical channel group runtime indicator indicating an associated runtime of at least one logical channel group with the monitoring dormancy timer.

For example, the transceiver receives the logical channel group run time indicator via a radio resource control, RRC, message.

In some embodiments, a discontinuous reception DRX cycle is configured in which the transceiver monitors the PDCCH in active periods and does not monitor the PDCCH in inactive periods.

There is also provided a scheduling apparatus comprising: the circuit allocates resources according to the scheduling request of the scheduling data and starts a transmission timer; and a transceiver which receives the scheduling request through a physical uplink control channel, PUCCH, and transmits a resource allocation indicator indicating the allocated resource through a physical downlink control channel, PDCCH, after the transmission timer expires.

In some embodiments, the circuit determines to monitor the operation of the sleep timer; and the transceiver transmits a monitor sleep indicator indicating the operation of the monitor sleep timer.

For example, the running of the transmission timer is equal to the running of the monitoring dormancy timer.

There is also provided a scheduling apparatus comprising: a circuit for allocating resources according to a buffer status report indicating a scheduled data amount, and starting a transmission timer; and a transceiver receiving the buffer status report and transmitting a resource allocation indicator indicating the allocated resource through a physical downlink control channel, PDCCH, after the transmission timer expires.

For example, the transceiver receives the buffer status report over a physical uplink shared channel, PUSCH.

In some embodiments, the circuit determines to monitor the operation of the sleep timer; and the transceiver transmits a monitor sleep indicator indicating the operation of the monitor sleep timer.

For example, the running of the transmission timer is equal to the running of the monitoring dormancy timer.

In some embodiments, the circuitry determines to monitor operation of the dormancy timer based on the set of logical channels.

For example, the buffer status report also indicates the logical channel group associated with the amount of scheduled data.

In some embodiments, the buffer status report indicates a plurality of logical channel groups, each logical channel group being associated with a respective amount of scheduling data.

For example, each logical channel group is associated with a respective runtime that monitors a dormancy timer.

In some embodiments, a first runtime monitoring the dormancy timer is configured for a first logical channel group having a first priority level, and a second runtime different from the first runtime monitoring the dormancy timer is configured for a second logical channel group having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, the transceiver transmits a logical channel group runtime indicator indicating an associated runtime of at least one logical channel group with the monitoring dormancy timer.

For example, the transceiver transmits the logical channel group run time indicator via a radio resource control, RRC, message.

There is also provided a method comprising: transmitting a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH), starting a monitoring sleep timer after transmitting the scheduling request; preventing monitoring of a physical downlink control channel, PDCCH, while monitoring the dormancy timer is running; and starting to monitor the PDCCH for a resource allocation for scheduling data when the monitoring dormancy timer has expired.

In some embodiments, the monitoring sleep timer is started when a scheduling request is sent.

In some embodiments, a monitor sleep indicator is received indicating the operation of a monitor sleep timer; starting a monitor sleep timer when a monitor sleep indicator is received;

for example, the monitor sleep indicator indicates the operation of the monitor sleep timer according to the duration or symbol of the PDCCH and/or the number of slots.

In some embodiments, monitoring the operation of the dormancy timer is configured according to a priority level configured by the scheduling request.

For example, a first runtime monitoring a dormancy timer is configured as a first scheduling request configuration having a first priority level; and a second runtime different from the first runtime monitoring the dormancy timer is configured for a second scheduling request configuration having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, a scheduling request configuration indicator is received, the indicator indicating at least one scheduling request configuration having at least one associated priority level,

for example, the scheduling request configuration indicator is received via a radio resource control, RRC, message.

In some embodiments, a Discontinuous Reception (DRX) cycle is configured in which a PDCCH is monitored during an active period and the PDCCH is not monitored during an inactive period.

There is also provided a method comprising transmitting a buffer status report indicating an amount of scheduled data; starting a monitor sleep timer after sending the buffer status report; preventing monitoring of a physical downlink control channel, PDCCH, while monitoring the dormancy timer is running; and starting to monitor the PDCCH for a resource allocation for scheduling data when the monitoring dormancy timer has expired.

In some embodiments, the buffer status report is sent over a physical uplink shared channel, PUSCH.

In some embodiments, a monitor sleep timer is started when a buffer status report is sent.

In some embodiments, the method includes receiving a monitor sleep indicator indicating a runtime to monitor a sleep timer; and starting a monitor sleep timer when the monitor sleep indicator is received.

In some embodiments, the monitoring sleep indicator indicates the operation of the monitoring sleep timer in accordance with the duration or symbol of the PDCCH and/or the number of slots.

In some embodiments, the operation of the dormancy timer is monitored according to a logical channel group configuration.

For example, the buffer status report also indicates the logical channel group associated with the amount of scheduled data.

In some embodiments, the buffer status report indicates a plurality of logical channel groups, each logical channel group being associated with a respective amount of scheduling data.

For example, each logical channel group is associated with a respective runtime that monitors a dormancy timer.

For example, the runtime monitoring the dormancy timer may be set to the runtime associated with the LCG having the highest priority.

In some embodiments, a first runtime monitoring the dormancy timer is configured for a first logical channel group having a first priority level, and a second runtime different from the first runtime monitoring the dormancy timer is configured for a second logical channel group having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, the method includes receiving a logical channel group runtime indicator indicating an associated runtime of at least one logical channel group with a monitoring dormancy timer.

For example, the logical channel group runtime indicator is received via a radio resource control, RRC, message.

In some embodiments, a Discontinuous Reception (DRX) cycle is configured in which a PDCCH is monitored during an active period and the PDCCH is not monitored during an inactive period.

A method is also provided, comprising receiving a scheduling request for scheduling data over a physical uplink control channel, PUCCH; starting a transmission timer; allocating resources according to the scheduling request; and transmitting a resource allocation indicator indicating the allocated resource through a physical downlink control channel, PDCCH, after the transmission timer expires.

In some embodiments, determining to monitor the operation of the dormancy timer; and transmitting a monitor sleep indicator indicating the operation of the monitor sleep timer.

For example, the running of the transmission timer is equal to the running of the monitoring dormancy timer.

A method is also provided that includes receiving a buffer status report indicating an amount of scheduled data; starting a transmission timer; allocating resources according to the buffer status report; and transmitting a resource allocation indicator indicating the allocated resource through a physical downlink control channel, PDCCH, after the transmission timer expires.

For example, the transceiver receives the buffer status report over a physical uplink shared channel, PUSCH.

In some embodiments, the method includes determining to monitor the operation of a dormancy timer; and transmitting a monitor sleep indicator indicating the operation of the monitor sleep timer.

For example, the running of the transmission timer is equal to the running of the monitoring dormancy timer.

In some embodiments, the method includes determining to monitor the operation of the dormancy timer based on the logical channel group.

For example, the buffer status report also indicates the logical channel group associated with the amount of scheduled data.

In some embodiments, the buffer status report indicates a plurality of logical channel groups, each logical channel group being associated with a respective amount of scheduling data.

For example, each logical channel group is associated with a respective runtime that monitors a dormancy timer.

In some embodiments, a first runtime monitoring the dormancy timer is configured for a first logical channel group having a first priority level, and a second runtime different from the first runtime monitoring the dormancy timer is configured for a second logical channel group having a second priority level different from the first priority level.

For example, where the first priority level is lower than the second priority level, the first runtime is larger than the second runtime, and where the first priority level is higher than the second priority level, the first runtime is smaller than the second runtime.

In some embodiments, the method includes transmitting a logical channel group runtime indicator indicating an associated runtime of at least one logical channel group with the monitoring dormancy timer.

For example, the logical channel group runtime indicator is transmitted via a radio resource control, RRC, message.

Claims (15)

1. A transceiver device, comprising:

a transceiver for transmitting a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH); and

circuitry to start a watchdog sleep timer after the transceiver transmits a scheduling request, wherein

The transceiver is used for receiving and transmitting the data,

not monitoring a physical downlink control channel while the monitor sleep timer is running

PDCCH, and

starting to monitor the PDCCH for resource allocation for scheduling data when the monitoring dormancy timer expires.

2. The transceiver device of claim 1, wherein

The circuit starts the monitor sleep timer when the transceiver transmits the scheduling request.

3. The transceiver device of claim 1 or 2, wherein

Receiving, by the transceiver, a monitor sleep indicator indicating runtime of the monitor sleep timer; and

the circuit starts the monitor sleep timer when the transceiver receives the monitor sleep indicator.

4. The transceiver device of claim 3, wherein

The monitoring dormancy indicator indicates the operation of the monitoring dormancy timer according to a duration or a number of symbols and/or slots of a PDCCH.

5. The transceiver device of any of claims 1 to 4, wherein

The operation of the monitoring dormancy timer is configured according to the priority level configured by the scheduling request.

6. The transceiver device of claim 5,

a first runtime of the watchdog dormancy timer is configured for a first scheduling request configuration having a first priority level; and

a second runtime of the watchdog dormancy timer different from the first runtime is configured for a second scheduling request configuration having a second priority level different from the first priority level.

7. The transceiver device of claim 6, wherein

In the event that the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, an

The first runtime is smaller than the second runtime if the first priority level is higher than the second priority level.

8. The transceiver device of any of claims 5 to 7, wherein

The transceiver receives a scheduling request configuration indicator indicating at least one scheduling request configuration having at least one associated priority level.

9. The transceiver device of claim 8, wherein

The transceiver receives the scheduling request configuration indicator via a radio resource control, RRC, message.

10. The transceiver device of any of claims 1 to 9, wherein

A discontinuous reception DRX cycle is configured in which the transceiver monitors the PDCCH in an active period and does not monitor the PDCCH in an inactive period.

11. A scheduling apparatus, comprising:

a circuit is provided with a plurality of circuits,

resources are allocated according to a scheduling request for scheduling data,

starting a transmission timer, an

A transceiver for receiving and transmitting a signal from the wireless communication device,

receiving the scheduling request over a physical uplink control channel, PUCCH, and

transmitting a resource allocation indicator indicating the allocated resources through a Physical Downlink Control Channel (PDCCH) after the transmission timer expires.

12. The scheduling apparatus of claim 11, wherein

The circuitry determines to monitor operation of a sleep timer; and

the transceiver transmits a monitor sleep indicator indicating the operation of the monitor sleep timer.

13. The scheduling apparatus of claim 12, wherein

The transmit timer running is equal to the monitor sleep timer running.

14. A method comprising

A scheduling request for scheduling data is sent over a physical uplink control channel PUCCH,

starting a monitor sleep timer after transmitting the scheduling request;

preventing monitoring of a physical downlink control channel, PDCCH, while the monitoring dormancy timer is running; and

starting to monitor the PDCCH for resource allocation for scheduling data when the monitoring dormancy timer expires.

15. A method comprising

Receiving a scheduling request for scheduling data through a Physical Uplink Control Channel (PUCCH);

starting a transmission timer;

allocating resources according to the scheduling request; and

transmitting a resource allocation indicator indicating the allocated resources through a Physical Downlink Control Channel (PDCCH) after the transmission timer expires.

Images