Communication apparatus, scheduling apparatus, method thereof, and integrated circuit

Abstract

The invention provides a communication apparatus, a scheduling apparatus, a method thereof, and an integrated circuit. In one embodiment, a communication apparatus includes: a transceiver that transmits a scheduling request (SR) over a physical uplink control channel (PUCCH), the SR being suspended until a valid uplink grant is received; and circuitry coupled to the transceiver and initiating an active time to monitor a Physical Downlink Control Channel (PDCCH) after SR transmission and monitoring a sleep time.

Description

[0001] This application is a divisional application of the Chinese invention patent application with application date of May 5, 2020, application number 202080039886.4, and invention name “Transceiver Device and Scheduling Device”. Technical Field

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

[0003] The 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as fifth generation (5G), including the "New Radio" (NR) radio access technology (RAT), which operates in the spectrum range from sub-1 GHz to millimeter bands. NR is a follow-up to Long Term Evolution (LTE) and LTE Advanced (LTE-A) technologies.

[0004] For systems such as LTE, LTE-A and NR, further modifications and options may facilitate efficient operation of the communication systems and specific equipment associated with the systems. Summary of the invention

[0005] One non-limiting and exemplary embodiment facilitates providing flexible and power-saving scheduling requests.

[0006] In one embodiment, the technical features disclosed herein are characterized by a communication device, including: a transceiver, which sends a scheduling request SR through a physical uplink control channel PUCCH, and the SR is suspended until a valid uplink grant is received; and a circuit, which is coupled to the transceiver and starts an active time to monitor a physical downlink control channel PDCCH after the SR is sent and the monitoring sleep time.

[0007] In one embodiment, the technical feature disclosed herein is a scheduling device, comprising: a transceiver, which receives a scheduling request SR from a communication device via a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is sent to the communication device via a physical downlink control channel PDCCH, wherein after the SR is sent and a sleep time is monitored, an active time is started to monitor the PDCCH; and a circuit, which is coupled to the transceiver and allocates resources according to the SR.

[0008] In one embodiment, the technical feature disclosed herein is a method, comprising: sending a scheduling request SR via a physical uplink control channel PUCCH, wherein the SR is suspended until a valid uplink grant is received; and after the SR is sent and the monitoring sleep time, starting an active time to monitor a physical downlink control channel PDCCH.

[0009] In one embodiment, the technical feature disclosed herein is a method, comprising: receiving a scheduling request SR from a communication device via a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is sent to the communication device via a physical downlink control channel PDCCH, wherein after the SR is sent and a sleep time is monitored, an active time is started to monitor the PDCCH; and allocating resources according to the SR.

[0010] In one embodiment, the technical features disclosed herein are in an integrated circuit that controls a process of a communication device, the process comprising: sending a scheduling request SR through a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is received; and after the SR is sent and the sleep time is monitored, an active time is started to monitor the physical downlink control channel PDCCH. 10. An integrated circuit that controls a process of a scheduling device, the process comprising: receiving a scheduling request SR from a communication device through a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is sent to the communication device through a physical downlink control channel PDCCH, wherein after the SR is sent and the sleep time is monitored, an active time is started to monitor the PDCCH; and allocating resources according to the SR.

[0011] In one embodiment, the technical features disclosed herein are characterized by a transceiver device, including: a transceiver, which sends a scheduling request for scheduling data through a physical uplink control channel PUCCH; and a circuit, which starts a monitoring sleep timer after the transceiver sends the scheduling request, wherein the transceiver does not monitor the physical downlink control channel PDCCH when the monitoring sleep timer is running, and starts monitoring the PDCCH for resource allocation for scheduling data when the monitoring sleep timer has expired.

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

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

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

[0015] Figure 1is a schematic diagram showing an exemplary architecture of a 3GPP NR system;

[0016] Figure 2 is a block diagram illustrating an exemplary user and control plane architecture of an LTE eNB, gNB, and UE;

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

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

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

[0020] Figure 6 is a block diagram illustrating an exemplary 5G system architecture;

[0021] Figure 7 shows the transmission of scheduling request and active period when discontinuous reception DRX cycle is configured according to 3GPP TR 38.321;

[0022] Fig. 8A schematically illustrates a time sequence of sending of scheduling requests and receiving of uplink grants and an active period in a DRX configuration of an associated high priority logical channel;

[0023] Figure 8B schematically illustrates a time sequence of transmission of a scheduling request and reception of an uplink grant and an associated active period in a DRX configuration of a low priority logical channel;

[0024] Fig. 9 is a block diagram illustrating functional components of a transceiver device and a scheduling device according to an embodiment;

[0025] Fig.10 shows the delay of the activity period from the sending time of the scheduling request according to an embodiment;

[0026] Fig.11 is a flow chart illustrating transmission of a scheduling request and starting monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

[0027] Fig.12 Schematically illustrating a mapping of a single scheduling request configuration per logical channel, wherein a first runtime of monitoring a dormancy timer is configured for a first logical channel and a second runtime of monitoring a dormancy timer is configured for a second logical channel;

[0028] Fig.13 Schematically shows a mapping of one scheduling request configuration per two logical channels;

[0029] Fig.14 schematically illustrates a MAC control element CE according to an embodiment, which indicates the runtime of the monitoring sleep timer;

[0030] Fig.15 schematically illustrates the time sequence of the sending of a scheduling request, the receiving of a monitoring dormancy indicator and the receiving of an uplink grant and an active period according to an embodiment;

[0031] Fig.16 is a flow chart illustrating the sending of a scheduling request, the receiving of a monitoring dormancy indicator, and the start of monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

[0032] Fig.17 The time sequence of sending a scheduling request, starting a sleep monitoring timer, receiving a monitoring sleep indicator and restarting the monitoring sleep timer according to an embodiment is schematically shown.

[0033] Fig.18A The short format of the buffer status report BSR is shown.

[0034] Fig.18B The long format of the buffer status report BSR is shown.

[0035] Fig.19 shows the transmission and activity period of the buffer status report when a discontinuous reception DRX cycle is configured;

[0036] Fig. 20A schematically illustrates the time sequence of the sending of a buffer status report and the receiving of an uplink grant and an active period in a DRX configuration of an associated high priority logical channel group;

[0037] Fig. 20B schematically illustrates the time sequence of the sending of a buffer status report and the receiving of an uplink grant and an active period in a DRX configuration of an associated low priority logical channel group;

[0038] Fig.21 shows the delay of the activity period starting from the sending time of the buffer status report according to an embodiment;

[0039] Fig. 22 is a flow chart illustrating the sending of a buffer status report and the start of monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer;

[0040] Fig.23The steps of the scheduling request process are shown, where a scheduling request and a buffer status report are sent, and a corresponding monitoring sleep timer may be started. DETAILED DESCRIPTION

[0041] 5G NR system architecture and protocol stack

[0042] 3GPP has been working on the next version of the fifth generation of cellular technology, or 5G for short, including the development of a new radio access technology (NR) that operates at frequencies up to 100GHz. The first version of the 5G standard was completed at the end of 2017, allowing trials and commercial deployment of smartphones compliant with the 5G NR standard to continue.

[0043] The overall system architecture assumes, among other things, a NG-RAN (Next Generation Radio Access Network) comprising gNBs, which provide NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations to the UE. The gNBs are interconnected to each other by means of Xn interfaces. The gNBs are also connected to the NGC (Next Generation Core) by means of Next Generation (NG) interfaces, and more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that implements the AMF) by means of the NG-C interface and to the UPF (User Plane Function) (e.g., a specific core entity that implements the UPF) by means of the NG-U interface. The NG-RAN architecture as Figure 1 shown.

[0044] A variety of different deployment scenarios can be supported. For example, a decentralized deployment scenario is proposed, in which base stations supporting 5G NR can be deployed. Figure 2 An exemplary non-centralized deployment scenario is shown, along with an LTE eNB and a user equipment (UE) connected to both the gNB and the LTE eNB. The new eNB for NR 5G may be exemplarily referred to as a gNB. The eLTE eNB is an evolution of the eNB that supports connections to both the EPC (Evolved Packet Core) and the NGC (Next Generation Core).

[0045] 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) is introduced on top of PDCP. A control plane protocol stack is also defined for NR.

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

[0047] Figure 3The functional division between NG-RAN and 5GC is shown. The NG-RAN logical node is gNB or ng-eNB. 5GC has the above-mentioned logical nodes AMF, UPF and SMF.

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

[0049] - 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);

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

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

[0052] - Routing of user plane data to UPF;

[0053] - Routing of control plane information to AMF;

[0054] -Connection establishment and release;

[0055] -Scheduling and transmitting paging messages;

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

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

[0058] -Transport level packet marking in uplink;

[0059] -Session management;

[0060] -Support network slicing;

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

[0062] -Support UE in RRC_INACTIVE state;

[0063] -NAS message distribution function;

[0064] - Radio access network sharing;

[0065] - Dual connectivity;

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

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

[0068] - Non-access layer NAS signaling terminal;

[0069] -NAS signaling security;

[0070] -Access layer AS security control;

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

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

[0073] -Registration area management;

[0074] -Support mobility within and between systems;

[0075] -Access authentication;

[0076] - Access authorization, including roaming permission check;

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

[0078] -Support network slicing;

[0079] -Session management function SMF selection.

[0080] In addition, the user plane function UPF carries the following main functions:

[0081] - Anchor point for intra / inter-RAT mobility (if applicable);

[0082] - External PDU session point connected to the data network;

[0083] -Packet routing and forwarding;

[0084] - User plane part of packet inspection and policy rule enforcement;

[0085] -Business usage reports;

[0086] - Uplink classifier, supporting routing of traffic flows to the data network;

[0087] -Support branching points for multi-homed PDU sessions;

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

[0089] - Uplink service verification (SDF to QoS flow mapping);

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

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

[0092] -Session management;

[0093] -UE IP address allocation and management;

[0094] -Selection and control of UP function;

[0095] -Configure traffic control at the User Plane Function (UPF) to route traffic to the appropriate destination; -Control part of policy enforcement and QoS;

[0096] - Downlink data notification.

[0097] RRC connection establishment and reconfiguration process

[0098] Figure 4 Some interactions between the UE, gNB and AMF (5GC entity) are shown regarding RRC which is the high-layer signaling (protocol) used for UE and gNB configuration. Specifically, the AMF prepares the UE context data (including, for example, PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and sends it to the gNB along with the INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. Subsequently, the gNB performs reconfiguration by way of RRCReconfiguration and RRCReconfigurationComplete to establish signaling radio bearer 2 (SRB2) and data radio bearer DRB. For a signaling-only connection, step 8 is skipped because SRB2 and DRB are not established. Finally, the gNB notifies the AMF with the INITIALCONTEXT SETUP RESPONSE that the establishment process is complete.

[0099] Therefore, in the present invention, an entity (such as AMF, SMF, etc.) of a fifth generation core (5GC) is provided, including a control circuit that establishes a next generation (NG) connection with a gNodeB, and a transmitter that sends an initial context establishment message to the gNodeB via the NG connection to establish a signaling radio bearer between the gNodeB and a user equipment (UE). Specifically, the gNodeB sends a radio resource control RRC signaling containing a resource allocation configuration information element to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation configuration.

[0100] IMT usage scenarios in 2020 and beyond

[0101] Figure 5 Some use cases for 5G NR are shown. In the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are being considered that are envisioned to support multiple services and applications through IMT-2020. The specifications for Phase 1 of enhanced mobile broadband (eMBB) have 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 massive machine type communications. Figure 5 Some examples of expected usage scenarios of IMT in 2020 and beyond are shown.

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

[0103] From a RAN1 perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability defines separate CQI tables for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR becomes more stable and advanced (a key requirement for NR URLCC), the scope for achieving ultra-reliability is likely to expand. Therefore, a NR URLCC at Rel.15 should be able to transmit a 32-byte packet within a user plane latency of 1ms, with a probability of success corresponding to a BLER of 1E-5. Specific use cases for NR URLCC at Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0104] In addition, NR URLCC has technical enhancements for latency improvement and reliability improvement. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, ungranted (configured grant) uplink, slot-level repetition of data channels, and downlink preemption. Preemption means stopping the transmission of allocated resources, and the allocated resources are used for another transmission that is requested later but has lower latency / higher priority requirements. Therefore, the authorized transmission is preempted by the later transmission. Preemption applies to transmissions independent of a specific service type. For example, a transmission of service type A (URLCC) may be preempted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table with a target BLER of 1E-5.

[0105] The use case of mMTC is characterized by a large number of connected devices that typically transmit relatively low volumes of non-delay-sensitive data. The devices require low cost and long battery life. From the NR perspective, utilizing very narrow bandwidth sections is a possible solution to achieve energy savings from the UE perspective and extend battery life.

[0106] As mentioned above, the reliability range of NR is expected to expand. A key requirement in all cases, especially one required for URLLC and mMTC is high reliability or ultra-reliability. Several mechanisms can be considered to improve reliability from both a radio perspective and a network perspective. In general, there are several potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in frequency, time and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0107] For NRURLLC, more use cases with more stringent requirements have been identified, such as factory automation, transportation, and power distribution. The more stringent requirements are higher reliability (up to 10-6), higher availability, packet size up to 256 bytes, time synchronization down to a few μm (where the value can be one or a few μm, depending on the frequency range), short latency of 0.5 to 1 ms, and in particular a target user plane latency of 0.5 milliseconds, depending on the use case.

[0108] In addition, for NR URLCC, several technical enhancements have been identified from the RAN1 perspective. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. In addition, PUSCH enhancements related to mini-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 a timeslot (a timeslot including 14 symbols).

[0109] QoS Control

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

[0111] For each UE, the 5GC establishes one or more PDU Sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session and may subsequently configure additional DRBs for the QoS flows of that PDU Session (depending on when the NG-RAN does so), e.g. as described above with reference to Figure 4 As shown in Figure 2. 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.

[0112] Figure 6 The 5G NR non-roaming reference architecture is shown. The application function (AF) interacts with the 3GPP core network to provide services, such as supporting application impact on service routing, accessing the network exposure function (NEF), or interacting with the policy framework for policy control (see Policy Control Function PCF). Based on operator deployment, the application function that the operator considers trustworthy can interact directly with the relevant network function. The application function that the operator does not allow direct access to the network function interacts with the relevant network function using an external exposure framework via the NEF.

[0113] Figure 6Other functional units of the 5G architecture are shown, namely the Network Slice Selection Function (NSSF), the Network Repository Function (NRF), the Unified Data Management (UDM), the Authentication Server Function (AUSF), the Access and Mobility Management Function (AMF), the Session Management Function (SMF) and the Data Network (DN), such as operator services, Internet access or third-party services.

[0114] The terminal is called user equipment (UE) in LTE and NR. This may be a mobile device such as a wireless phone, a smartphone, a tablet, or a USB (Universal Serial Bus) stick with the functionality of a user device. However, the term mobile device is not limited to this, and in general, a relay may also have the functionality of such a mobile device, and a mobile device may also be used as a relay.

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

[0116] The service that transmits data provided by the layer to the higher layer is generally called a channel. For example, LTE and NR distinguish between logical channels provided by the MAC layer to the higher layer, transport channels provided by the physical layer to the MAC layer, and physical channels that define the mapping on physical resources.

[0117] Logical channels are different types of data transmission services provided by 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. Control channels are used only to transmit control plane information. Traffic channels are used only to transmit user plane information.

[0118] The MAC layer then maps the logical channels to transport channels. For example, logical traffic channels and some logical control channels can be mapped to a transport channel called the downlink shared channel DL-SCH in the downlink and a transport channel called the uplink shared channel UL-SCH in the uplink.

[0119] Scheduling

[0120] In 3GPP, scheduling in NR based operation is described (see, for example, 3GPP TR 38.321, NR; Medium Access Control (MAC) protocol specification, Version 15.4.0).

[0121] 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 can be scheduled.

[0122] Specifically, 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 the set of resources on which the terminal should transmit its UL-SCH.

[0123] In other words, the function of uplink scheduling is to dynamically determine which devices are to transmit and on which uplink resources. Dynamic scheduling is usually performed by means of a physical downlink control channel (PDCCH). The physical downlink control channel carries scheduling authorization and other control information, which can also be referred to as downlink control information DCI. Each terminal (UE) monitors the PDCCH. This means that the UE (blindly) decodes specific resources called search spaces. The PDCCH search space is an area in the downlink resource grid that can carry the PDCCH. The UE performs blind decoding in these search spaces, trying to find PDCCH data (DCI). In order to decode the PDCCH, the UE applies its own RNTI (radio network temporary identifier) ​​and attempts to decode the PDCCH in a resource called a control channel element CCE. If the decoding is successful (which can be checked by an error detection code (such as a cyclic redundancy check)), the DCI is received. The UE can also blindly try various parameter values ​​for some selected transmission parameters. Each terminal can monitor multiple PDCCHs. The PDCCH can be shared by a group of UEs (in this case, the UE is using a common group RNTI) or dedicated to a specific UE.

[0124] The standard (LTE or NR) defines several different formats of DCI. These formats differ because of their purpose. For example, the format used to carry uplink grants (such as format 0 or 4) is different from the format that carries downlink grants or no grants at all. In addition, there are different formats defined depending on the utilization of beamforming, broadcast / multicast, etc.

[0125] Correspondingly, in the uplink, the control information on the physical layer is carried by the physical uplink control channel. PUCCH carries a set of parameters called UCI (uplink control information). This is similar to the PDCCH that carries the above-mentioned DCI. Depending on the type of information that UCI carries in PUCCH, PUCCH can also use different formats. For example:

[0126] -Format 1 carries a scheduling request SR,

[0127] -Format 4 carries SR and channel state information (CSI),

[0128] - Format 3 carries SR and CSI with HARQ acknowledgment (positive or negative),

[0129] There are other formats defined by LTE and / or NR.

[0130] The basis of uplink scheduling is the scheduling grant, which contains device information about resources and the associated transmission format for the transmission of UL-SCH. In other words, a DCI with a specific format (e.g., defined in the standard) can carry the resource allocation (RA) corresponding to the resource grant, as well as some other transmission parameters such as the modulation and coding scheme (MCS), the configuration for multiple-input multiple-output (MIMO) transmission, etc.

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

[0132] That is, the scheduler needs knowledge about the terminals that have data to transmit and therefore needs to schedule uplink resources. It is not necessary to provide uplink resources to devices that have no data to transmit, as this will cause the device to perform padding to fill the granted resources. Therefore, the scheduler needs to know whether a device has data to transmit and should obtain a grant.

[0133] Scheduling Request

[0134] Scheduling requests may be used for terminals that do not have a valid scheduling grant. Scheduling requests may be transmitted on the Physical Uplink Control Channel (PUCCH). Each terminal may be assigned a dedicated scheduling request resource, occurring every nth subframe. A scheduling request may be a simple flag, raised (set) by a terminal to request uplink resources from the uplink scheduler. With a dedicated scheduling request mechanism, the identity of the requesting terminal does not have to be provided with the scheduling request, as the identity of the terminal is implicitly known from the resources requested for transmission. These are configured by the scheduling node (such as a gNB), for example, through a higher layer control protocol.

[0135] Upon receiving a 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 scheduled resources. The data to be transmitted on the PUSCH may include, in a first buffer state, the amount of data that the UE must transmit, which informs the scheduling node. Based on the buffer state, the scheduling node may then schedule the actual data resources on the PUSCH. However, this is only an option, and typically, the data resources may also be scheduled directly. In some systems, the scheduling request may also be associated with a specific amount of data requested for scheduling.

[0136] If the terminal does not receive the scheduling grant until the next possible time, the scheduling request may be repeated.

[0137] Thus, a contention-free scheduling request mechanism is provided on the PUCCH, where each terminal in the cell is given reserved resources on which it can transmit requests for uplink resources.

[0138] The UE MAC entity can be configured with zero, one or more SR configurations. An SR configuration consists of a set of PUCCH resources for scheduling requests across different bandwidth parts (BWPs). For a 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 configurations can be configured via Radio Resource Control (RRC) messages.

[0139] As mentioned above, when a regular buffer status report (BSR) is triggered in the UE but the uplink radio resources for sending the BSR are not available, the SR procedure can be initiated. During the SR procedure, the UE can perform the transmission of the SR via the PUCCH or initiate a random access (RA) procedure, depending on whether the UE is configured with PUCCH resources for SR. The RA procedure is initiated only when the PUCCH resources for SR are not configured.

[0140] When the UE MAC entity has an SR transmission position on a valid PUCCH resource configured for SR, it instructs the physical layer (PHY) to signal the SR on a valid PUCCH resource for SR. Subsequently, the SR prohibit timer starts (sr_prohibitTimer). During consecutive SR transmission opportunities, if the SR prohibit timer is running, the MAC does not instruct the PHY to signal the SR.

[0141] In NR, SR resources are configured with a specific periodicity. Once the UE sends an SR, the SR prohibit timer is started, and as long as the SR prohibit timer is running, no SR will be sent on the configured resources.

[0142] The scheduling request configuration information element used to configure 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 shown below.

[0143] SchedulingRequestConfig Information Element

[0144]

[0145] Specifically, the scheduling request prohibit timer is configured by sr-ProhibitTimer and indicates the duration for which no scheduling request is sent after the 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 from the scheduling node to the UE via RRC signaling.

[0146] When the prohibit timer (sr-ProhibitTimer) is active, no further SRs will be started. sr-ProhibitTimer is configured for each SR and can be set to a value in the range of 1ms to 128ms.

[0147] For example, if the gNB configures sr-ProhibitTimer to 32ms, the gNB can allocate uplink resources within 32ms after receiving the SR, and the UE needs to monitor the PDCCH for a maximum of 32ms after sending the SR.

[0148] Discontinuous Reception – DRX

[0149] Packet data is typically highly bursty, with occasional periods of silence. From a latency perspective, it is beneficial to permanently monitor downlink control signaling to receive uplink grants or downlink data transmissions and react instantly to changes in traffic behavior. At the same time, this also comes at a cost in terms of device power consumption. To reduce device power consumption, LTE includes mechanisms for discontinuous reception (DRX).

[0150] The basic mechanism of DRX is the DRX cycle configurable in the device. With the DRX cycle configured, the device monitors downlink control signaling only during the active period of each DRX cycle and sleeps during the remaining inactive periods with the receiver circuitry turned off. This allows for significant reductions in power consumption. Of course, this implies a restriction on the scheduler, since the device can only be addressed during the active period.

[0151] The DRX cycle can be configured in the LTE downlink so that the UE does not have to decode the Physical Downlink Control Channel (PDCCH) or receive Physical Downlink Shared Channel (PDSCH) transmissions during certain periods by periodically turning off the receiver as defined in 3GPP TS 36.321 (“Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification”, Release 15.5.0, Section 5.7) for connected mode and in 3GPP TS 36.304 (“Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode”, Release 15.3.0, Section 7.1) for idle mode.

[0152] According to the 3GPP TS 38.321v15.5.0 specification, when the DRX cycle is configured, the active time includes the time that the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or ra-ContentionResolutionTimer runs, as described in Section 5.1.5 of 3GPP TS38.321.

[0153] drx-onDurationTimer defines the duration when the DRX cycle starts, while drx-InactivityTimer specifies the duration after the PDCCH opportunity when the PDCCH indicates a new uplink (UL) or downlink (DL) transmission of the MAC entity. drx-RetransmissionTimerDL and -UL define the maximum duration before receiving a DL retransmission and the maximum duration before receiving a UL retransmission grant, respectively.

[0154] In addition, the active time includes the 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 to a random access preamble that was not selected by the MAC entity in a contention-based random access preamble, as described in section 5.1.4 of 3GPP TS 38.321v15.5.0.

[0155] As described above, the UE uses the Scheduling Request procedure to request radio resources for a new uplink transmission. In particular, during the time that a Scheduling Request has been sent and is pending, the PDCCH is monitored for scheduling assignments as described in 3GPP TS 38.321 v15.5.0 Section 5.4.4.

[0156] That is, when SR is sent on PUCCH and is suspended, PDCCH is monitored. Figure 7 Schematically illustrates the active and inactive times (on periods and off periods) according to the configured DRX cycle (solid line) and the active times due to pending scheduling requests (dashed line). Figure 7 In the example, time is shown on the horizontal axis. Once the SR is sent on the PUCCH, Figure 7 As shown by the arrow marked “SR” in FIG. 1 , the UE starts monitoring the PDCCH for uplink grants of scheduled data to be transmitted.

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

[0158] exist Figure 8B In the case shown, after SR transmission, Fig. 8A In the case shown, the UL grant is received at a longer point in time. This may be the case where the scheduling device prioritizes the scheduling of the UL grant based on the priority and traffic load of the associated logical channel.

[0159] As a result, the UE consumes power in monitoring the PDCCH during the period when the gNB does not intend to schedule an UL grant to the UE. Fig. 8A and 8B During the period when no UL grant is transmitted, the UE monitors the PDCCH and thus consumes power.

[0160] The present invention provides a technique that helps to adjust the monitoring duration in the framework of the SR procedure. In particular, the present invention provides a SR procedure for reducing the power consumption of a UE in a configured DRX cycle.

[0161] The present invention provides Fig. 9 The transceiver equipment and scheduling equipment are shown.

[0162] The transceiver device 100 includes a transceiver 110 (a transmitter and / or a receiver, including hardware components such as one or more antennas and a control circuit that controls the operation of the hardware components), and transmits a scheduling request for scheduling data through a physical uplink control channel PUCCH. In addition, the transceiver device 100 includes a circuit 120 (or a processing circuit) that starts a monitoring sleep timer after the transceiver 110 sends the scheduling request. In addition, the transceiver 110 does not monitor the physical downlink control channel PDCCH when the monitoring sleep timer is running, and starts monitoring the PDCCH for resource allocation for scheduling data when the monitoring sleep timer expires.

[0163] For example, the transceiver device 100 is a UE in an NR network. Therefore, the transceiver 110 and the circuit 120 are also referred to as a "UE transceiver" and a "UE circuit". However, these terms are only used to distinguish the transceiver 110 and the circuit 120 from circuits and transceivers included in 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 of a similar communication system. The UE circuit may be regarded as or include a "monitoring sleep control circuit".

[0164] Also provided such as Fig. 9 The scheduling device 200 (or scheduling node) is shown.

[0165] The scheduling device 200 comprises a circuit 220, which allocates resources according to a scheduling request of scheduling data and starts a transmission timer. The scheduling device 200 also comprises a transceiver 210, which receives the scheduling request via a physical uplink control channel PUCCH and sends a resource allocation indicator indicating the allocated resources via a physical downlink control channel PDCCH after the transmission timer expires.

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

[0167] A method is also provided, comprising transmitting a scheduling request for scheduling data via a physical uplink control channel PUCCH, and starting a monitoring sleep timer after sending the scheduling request. In addition, the method comprises preventing monitoring of a physical downlink control channel PDCCH while the monitoring sleep timer is running, and starting monitoring the PDCCH for resource allocation for scheduling data when the monitoring sleep timer expires.

[0168] A method is also provided, comprising receiving a scheduling request for scheduling data via a physical uplink control channel (PUCCH), and starting a transmission timer. The method also comprises allocating resources according to the scheduling request, and sending a resource allocation indicator indicating the allocated resources via a physical downlink control channel (PDCCH) after the transmission timer expires.

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

[0170] The transceiver device 100 uses the transceiver 110 to send a scheduling request for sending scheduled data through the PUCCH, and starts a monitoring sleep timer using the UE circuit 120 after the SR has been sent. When the monitoring sleep timer is running, the transceiver 110 does not monitor the PDCCH for receiving a UL grant corresponding to the sent SR. After the monitoring sleep timer expires, the transceiver 110 starts monitoring the PDCCH for receiving a UL grant according to the sent SR, wherein the UL grant indicates allocated resources for sending the scheduled data.

[0171] exist Fig.10 The time sequence is schematically shown in , where, when the DRX cycle is configured, the UE (or specifically, the transceiver) monitors the PDCCH during the active period, and does not monitor the PDCCH during the inactive period.

[0172] According to one embodiment, once the SR is sent, the monitoring sleep timer is started, and when the monitoring sleep timer has expired, the transceiver 110 starts monitoring the PDCCH for the UL grant from the scheduling device 200. That is, according to this embodiment, when the transceiver 110 sends a scheduling request, the monitoring sleep timer is started.

[0173] With this procedure, the power consumption of the UE is reduced because the UE's active time monitoring the PDCCH is reduced due to running the monitoring dormancy timer during the period when the SR is pending but the scheduling device does not intend to send an UL grant.

[0174] Fig.11 is a flow chart 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.

[0175] After the process starts, in step S100, it is determined whether the DRX mode is configured, that is, whether the UE is in the DRX mode. In the case of determining that the UE is not in the DRX mode (No in step S100), the process is repeated at the beginning. In the case of determining that the UE is in the DRX mode (Yes in step S100), the process continues to step S110.

[0176] In step S110, it is determined whether an SR has been sent. Fig. 9 As shown, it is determined whether the transceiver 110 has sent a scheduling request for scheduling data to be sent to the scheduling device 200 through the PUCCH. In the case where the scheduling request has not been sent (No in step S110), the process repeats step S110. In the case where it is determined that the SR has been sent (Yes in step S110), the process continues to step S120.

[0177] In step S120, a monitoring sleep timer is started. Fig. 9 As shown, the circuit 120 of the transceiver device 100 starts the monitoring sleep timer. For example, the runtime of the monitoring sleep timer can be defined by a duration or an offset of a specific symbol or time slot of the PDCCH. This is described below. In addition, the runtime of the monitoring sleep timer can be configured according to the scheduling request configuration, as described below. When the monitoring sleep timer is running (i.e., not expired), the PDCCH is not monitored for UL grants for scheduled data.

[0178] In step S130, it is determined whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has not expired (No in step S130), the process remains in step S130 and repeatedly determines whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has expired (Yes in step S130), the process continues to step S140.

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

[0180] As described above, the runtime of the monitoring sleep timer can be configured separately according to the priority of the service, that is, the value of the monitoring sleep timer can be configured separately in each SR configuration. In other words, the runtime of the monitoring sleep timer is configured according to the priority level of the scheduling request configuration.

[0181] For example, for a SR configuration of a first priority level, the runtime of the monitoring sleep timer may be set to a smaller value than that of a SR configuration of a second priority level lower than the first priority level.

[0182] In other words, a SR with a higher priority and a smaller wait time can be configured with a relatively smaller runtime of the monitor sleep timer, and a SR with a lower priority and a larger wait time can be configured with a relatively larger runtime of the monitor sleep timer. In this case, the energy saving effect of the higher priority and lower wait time service is smaller than that of the lower priority and larger wait time service.

[0183] As described above, after the transceiver 110 sends the SR, the UE circuit 120 applies the runtime of the monitoring sleep timer corresponding to the SR configuration.

[0184] like Fig.12 As shown, a first runtime of a monitoring sleep timer may be configured for a first logical channel, and a second runtime of a monitoring sleep timer may be configured for a second logical channel. Thus, the runtime of the monitoring sleep timer may be different depending on the logical channel. Specifically, a lower priority logical channel may be configured with a larger runtime of a monitoring sleep timer than a higher priority logical channel, and vice versa. Fig.12 As shown, LCH1 and LCH2 are mapped to different SR configurations because LCH1 and LCH2 have different priorities.

[0185] Despite Fig.12 In FIG. 1 , the mapping of the runtime of monitoring the sleep timer is shown for two logical channels, but the present embodiment is not limited thereto, and different runtimes of monitoring the sleep timer can be configured for multiple logical channels / SR configurations.

[0186] For example, Fig.13 As shown, two logical channels (LCH1 and LCH2) of the same priority level are mapped to a single SR configuration, and a single runtime monitoring dormancy timer is mapped to the SR configuration.

[0187] Although in Fig.12 and 13 In the figure, a one-to-one mapping of runtime, SR configuration and logical channels or a mapping of multiple logical channels to a single SR configuration is shown, but the present embodiment is not limited to this, 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.

[0188] According to one embodiment, the runtime of the monitoring sleep timer is fixed, wherein the network / scheduling device 200 and the transceiver device 100 map each SR configuration with a predefined runtime of the monitoring sleep timer. Specifically, the mapping may depend on the logical channel (SR) priority, so that it is defined which logical channel corresponds to which runtime of the monitoring sleep timer. Using this approach, no additional signaling is required.

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

[0190] schedulingRequestID Timer / Offset 0 sym2 1 sym6 2 sl1 3 sl2 4 sl4 5 sl8 6 sl10 7 sl16

[0191] Table 1: Fixed values ​​for monitoring sleep timer runtime / offset.

[0192] For example, when logical channel LCH1 is mapped to SR configuration 1 and a scheduling request is triggered due to LCH1, MAC passes the schedulingRequestID information to PHY to send the scheduling request. If the SR configuration of LCH1 is associated with schedulingRequestID 5, the UE shall run the monitoring dormancy timer of 8ms.

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

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

[0195] According to one embodiment, the network signals the runtime of the monitoring dormancy timer for each SR configuration so that the monitoring dormancy timer runtime can be dynamically configured. For example, the monitoring dormancy timer runtime can 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 runtime via RRC messages.

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

[0197] SchedulingRequestResourceConfig Information Element

[0198]

[0199] Specifically, the monitoring sleep timer is configured by a timer / offset, and the running time of the monitoring sleep timer is indicated according to the sign of the time slot of the PDCCH.

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

[0201] For example, a MAC control element indicating the running of a monitoring dormancy timer may be transmitted carrying timing related information in a bitmap format.

[0202] For example, in LTE, the MAC layer may insert so-called MAC Control Elements (MAC CEs) into transport blocks for transmission over transport channels. MAC CEs are used for in-band control signaling, such as timing advance commands or random access responses.

[0203] However, according to the present invention, the MAC CE may carry information on the runtime of the monitoring sleep timer, wherein the MAC CE may indicate, for example, a duration in the range of 0 to 256. The time unit of the length may be a duration (ms) or a number of symbols or a number of time slots.

[0204] Fig.14 The MAC control element CE indicating the operation of monitoring the dormancy timer according to an embodiment is schematically shown. For example, if the UE 100 receives a MAC CE command indicating "0 0 0 0 1 0 0 0 0", the UE does not monitor the PDCCH for resources scheduling 8 ms or 8 time slots.

[0205] Fig.15 The time sequence of sending a scheduling request, receiving a monitoring sleep indicator, receiving an uplink grant, and an active period according to an embodiment is schematically shown. Specifically, the transceiver 110 sends a scheduling request for scheduling data and monitors the PDCCH for UL grants. When a MAC CE indicating the runtime of the monitoring sleep timer is received (as shown by the arrow indicated by "MAC CE"), the circuit 120 starts the monitoring sleep timer with the associated runtime according to the runtime indicated by the received MAC CE. As long as the monitoring sleep timer is running, the transceiver 110 does not monitor the PDCCH for the scheduling allocation of the scheduling data corresponding to the sent scheduling request. When the monitoring sleep timer has expired, the transceiver 110 starts monitoring the PDCCH for UL grants.

[0206] That is, the transceiver 110 receives a monitoring sleep indicator (eg, MAC CE) indicating the operation of the monitoring sleep timer, and when the transceiver receives the monitoring sleep indicator, the circuit 120 starts the monitoring sleep timer.

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

[0208] Fig.16 is a flow chart illustrating the sending of a scheduling request, the reception of a monitoring dormancy indicator, and the start of monitoring of a physical downlink control channel after expiration of a monitoring dormancy timer.

[0209] After the process starts, in step S200, it is determined whether the DRX mode is configured, that is, whether the UE is in the DRX mode. In the case of determining that the UE is not in the DRX mode (No in step S200), the process is repeated at the beginning. In the case of determining that the UE is in the DRX mode (Yes in step S200), the process continues to step S210.

[0210] In step S210, it is determined whether an SR has been sent. For example, it is determined whether the transceiver 110 has sent a scheduling request for scheduling data to be sent to the scheduling device 200 through the PUCCH. In the case where a scheduling request has not been sent (No in step S210), the process repeats step S210. In the case where it is determined that an SR has been sent (Yes in step S210), the process continues to step S220.

[0211] 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 a MAC CE indicating the operation is not received (No in step S230), the process repeats the monitoring of the PDCCH. In the case where a MAC CE indicating the operation of monitoring the sleep timer is received (Yes in step S240), the process continues to step S240.

[0212] In step S240, the monitoring sleep timer is started with the runtime corresponding to the runtime indicated by the MAC CE. In addition, the monitoring of the PDCCH is terminated. That is, when the monitoring sleep timer is running, that is, it has not expired, for example, the PDCCH is not monitored by the transceiver 110.

[0213] In step S250, it is determined whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has not expired (No in step S250), the process remains in step S250 and repeatedly determines whether the monitoring sleep timer has expired. In the case where the monitoring sleep timer has expired (Yes in step S250), the process continues to step S260.

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

[0215] According to this embodiment, the operation of the monitoring sleep timer is signaled by the scheduling device 200 using a MAC control element. However, the present invention is not limited to the transmission using the MAC CE, and the operation of the monitoring sleep timer may be another transmission method. Specifically, the scheduling device 200 may send a monitoring sleep indicator indicating the operation of the monitoring sleep timer, and the UE circuit 120 may start the monitoring sleep timer upon receiving the monitoring sleep indicator.

[0216] Needless to say, in the case where a UL grant can be received via the PDCCH without receiving a monitoring indicator, in this case, it is no longer necessary not to monitor the PDCCH due to a pending scheduling request.

[0217] In addition, according to the above embodiment, for example, the monitoring sleep timer may be started by the MAC CE when sending a scheduling request or receiving a monitoring sleep indicator.

[0218] In the first example, monitoring of the PDCCH does not start immediately after sending a scheduling request, but a monitoring dormancy timer is started and monitoring starts after expiration.

[0219] In a second example, monitoring of the PDCCH starts when a scheduling request is sent, and when a monitoring dormancy indicator is received, monitoring of the PDCCH is interrupted for a duration corresponding to the runtime indicated by the monitoring dormancy indicator.

[0220] However, the present invention is not limited to any one of the embodiments. Specifically, between the transmission of the SR and the expiration of the monitoring sleep timer and between the reception of the monitoring sleep indicator and the expiration of the corresponding monitoring sleep timer, the monitoring of the PDCCH may not be performed. In other words, the above-mentioned example methods can be combined.

[0221] This is Fig.17 , where the shaded area indicates the time period during which the PDCCH is not monitored due to the monitoring sleep timer started when the SR is sent. In addition, when a MAC CE indicating the runtime of the monitoring sleep timer is received, the monitoring sleep timer can be restarted using the received runtime, or a second monitoring sleep timer can be started so that the PDCCH is not monitored during the duration indicated by the MAC CE.

[0222] Note that for this situation, the monitoring sleep timer according to one or more embodiments may be restarted or restarted by the circuit 120. In other words, in the case where the monitoring sleep timer is running, the timer may be restarted, or its remaining or total runtime may be adjusted until it expires. Alternatively or additionally, an additional monitoring sleep timer may be started.

[0223] The scheduling device 200 according to the embodiment may determine the runtime of the monitoring sleep timer and transmit a monitoring sleep indicator indicating the runtime of the monitoring sleep timer using the transceiver 210. Specifically, the runtime of the transmission timer may correspond to the runtime of the monitoring sleep timer.

[0224] Furthermore, in the above-described embodiment, it is determined whether a DRX cycle is configured for the transceiver device 100. However, the present invention is not limited to determining whether a DRX cycle is configured. In particular, as long as the monitoring sleep timer is running, the configured DRX cycle is not a mandatory requirement for starting the monitoring sleep timer and not monitoring the PDCCH.

[0225] The present invention also provides an SR process for reducing the power consumption of UE in a configured DRX cycle.

[0226] like Fig. 9 As shown, the transceiver device 100 includes a transceiver 110 (a transmitter and / or a receiver including hardware components such as one or more antennas and control circuits for controlling the operation of the hardware components), which transmits a buffer status report indicating the amount of scheduled data. In addition, the transceiver device 100 includes a circuit 120 (or a processing circuit) that starts a monitoring sleep timer after the transceiver 110 transmits the buffer status report. In addition, the transceiver 110 does not monitor the physical downlink control channel PDCCH when the monitoring sleep timer is running, and starts monitoring the PDCCH for resource allocation of the scheduled data when the monitoring sleep timer expires.

[0227] Also provided such as Fig. 9 The scheduling device 200 (or scheduling node) is shown.

[0228] The scheduling device 200 includes a circuit 220, which allocates resources according to a buffer status report indicating the amount of scheduled data and starts a transmission timer; the scheduling device 200 also includes a transceiver 210, which receives the buffer status report and transmits a resource allocation indicator indicating the allocated resources via a physical downlink control channel PDCCH after the transmission timer expires.

[0229] A method is also provided, comprising transmitting a buffer status report indicating an amount of scheduled data, and starting a monitoring sleep timer after transmitting the buffer status report. In addition, the method comprises preventing monitoring of a physical downlink control channel (PDCCH) while the monitoring sleep timer is running, and starting monitoring the PDCCH for resource allocation of scheduled data when the monitoring sleep timer has expired.

[0230] A method is also provided, comprising receiving a buffer status report indicating an amount of scheduled data, and starting a transmission timer. The method also comprises allocating resources based on the buffer status report, and transmitting a resource allocation indicator indicating the allocated resources via a physical downlink control channel (PDCCH) after the transmission timer expires.

[0231] The buffer status report BSR can be a medium access control (MAC) level message transmitted by the UE 100 to the serving gNB as the scheduling device 200 to provide the gNB with information about the amount of data in the uplink buffer of the UE 100 (see 3GPP TS 36.321 ("Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification", Version 15.5.0, Section 5.4.5).

[0232] The BSR is reported in the uplink to inform the gNB 200 about the amount of buffered data at the UE 100 and to allow the gNB 200 to distinguish data with different scheduling priorities, since the BSR reporting is performed for each logical channel group (LCG), where each LCG can be associated with a respective priority level.

[0233] An LCG is a group of uplink logical channels, or a single joint buffer filling level reported in a BSR by the UE 100. The mapping of LCGs may be defined by the gNB 200 (see 3GPP TS 36.321 ("Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification", Version 15.5.1, Section 6.3.2). An LCG may be defined as a group of logical channels with similar QoS (Quality of Service) requirements.

[0234] This can be done by using the long BSR format or the short BSR format (respectively Fig.18A and 18B As shown) Each LCG performs buffer status reporting. Fig.18A is an illustration of the 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 length three bits. In addition, the buffer size field indicates the total amount of data. Fig.18B As shown in the long BSR format, the BSR contains multiple buffer size fields, each of which represents an LCG. In other words, the short BSR format is used to report the data volume of an indicated logical channel group, while the long BSR format is used to report the data volume of all logical channel groups. For example, depending on the quality of service (QoS) requirements, the network can configure up to eight logical channel groups per UE.

[0235] When a BSR is transmitted during the DRX off period, the UE may switch to the DRX active time, during which the PDCCH is monitored for uplink grants. Fig.19 Shown in

[0236] However, monitoring the PDCCH by entering the DRX active time due to the transmission of the BSR may result in unnecessary power consumption because the UE 100 may not be scheduled immediately after the BSR is transmitted. In other words, in the case where the gNB 200 does not intend to schedule resources to the UE 100, such as when the scheduling of UL grants is based on the priority level of the BSR and the traffic load, the UE 100 may not have to monitor the PUCCH for uplink grants. For example, Fig. 20A and 20B As shown, 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).

[0237] Therefore, the transceiver device 100 transmits a BSR indicating the amount of scheduled data using the transceiver 110, and starts a monitoring sleep timer using the UE circuit 120 after the BSR is transmitted. While 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 BSR, wherein the UL grant indicates allocated resources for transmitting the scheduled data.

[0238] Fig.21A time sequence is schematically shown, wherein the UE (or specifically, the transceiver), monitors the 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 UE 100 switches to an active time, wherein the PDCCH is monitored for uplink grants. In other words, the switch from not monitoring to monitoring the PDCCH is delayed by a time offset from the transmission of the BSR.

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

[0240] For example, a runtime may be configured for each LCG. For example, an LCG with a higher priority may be associated with a shorter monitoring sleep timer runtime than an LCG with a lower priority.

[0241] The mapping of LCGs and the runtime of monitoring dormancy timers may be predefined (eg, according to definitions given in specification documents), or dynamically configured (eg, via RRC).

[0242] Table 2 illustrates fixed values ​​for the runtime of the monitoring sleep timer. As shown in the table, the runtime of the monitoring sleep timer is represented by X1 to X10, which are associated with LCGs with identifiers ID 0 to 7, respectively. For example, in the case where the priority is reduced from LGC ID 0 to LCG ID 7, the runtime of the monitoring sleep timer may increase from X1 to X10. In other words, the lower the level of the associated LCG, the larger the runtime of the monitoring sleep timer may be. Pre-defining the runtime / offset does not require additional signaling.

[0243]

[0244]

[0245] Table 2: Fixed values ​​of watchdog sleep timer runtime / offset for each LCG ID.

[0246] Alternatively or additionally, the runtime of the monitoring dormancy timer may be dynamically configured, for example, via RRC. With the mapping between the dynamically configured LCG ID and the offset / timer runtime, the network may take into account the traffic load and traffic priority and change the timer runtime / offset as needed via RRC (e.g., via a system information message or a dedicated RRC message).

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

[0248] LogicalChannelConfig Information Element

[0249]

[0250] Specifically, "logicalChannelGroupOffset" of each logical channel group indicates when the monitoring sleep timer runs.

[0251] In case the BSR indicates multiple 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 of the monitoring sleep timer may be set to the runtime associated with the LCG with the lowest LCG ID. Alternatively, the runtime of the monitoring sleep timer may be set to the shortest runtime associated with the LCG for which the scheduled data amount is indicated in the BSR.

[0252] In summary, according to an embodiment of the present disclosure, a transceiver device such as UE 100 sends a scheduling request or a buffer status report and then starts a dedicated timer, i.e., a monitoring sleep timer. As long as the timer has not expired, UE 100 does not monitor PDCCH for receiving uplink grants. When the timer expires, the UE starts monitoring PDCCH. This can allow a reduction in energy consumption because UE 100 does not monitor PDCCH when scheduling grants are not expected.

[0253] The monitoring sleep timer may be started only after sending a scheduling request, or only after sending a buffer status report, or after sending a scheduling request and after sending a buffer status report. In the last case, the runtime of the timer started after sending an SR may be equal to the runtime of the timer started after sending a BSR. However, the present invention is not limited thereto, and the runtime of the timer started after sending an SR may be different from the runtime of the timer started after sending a BSR.

[0254] Fig.23An example of a scheduling request procedure is shown in A, where an SR and a BSR are sent from the UE 100 to the gNB 200. In step 1, a scheduling request is sent by the UE 100 to the gNB 200 via the PUCCH. In addition, in step 2, the UE 100 receives a scheduling grant from the gNB indicating resources for sending scheduled data. In step 3, the UE 100 sends a buffer status report to the gNB 200 using the indicated resources of the PUSCH. In step 4, the UE 100 receives a scheduling grant from the gNB 200 for sending scheduled data. In step 5, the UE 100 sends the scheduled data using the resources indicated by the received uplink grant.

[0255] like Fig.23 As shown in FIG. 2B , according to the present invention, the UE 100 starts the monitoring sleep timer after having sent the SR via the PUCCH, and does not monitor the PDCCH for receiving the uplink grant when the timer has not expired, i.e., during the period indicated as the offset / sleep period. After the expiration of the monitoring sleep timer, the UE 100 monitors the PDCCH for receiving the uplink grant during the period indicated as the UE wake-up period.

[0256] In addition, if Fig.23 As shown in FIG. 3 , the UE starts the monitoring sleep timer after sending the BSR (i.e., after step 3), and does not monitor the PDCCH when the monitoring sleep timer has not expired (i.e., during the period indicated as the offset / sleep period). When the timer has expired, the UE 1200 starts monitoring the PDCCH for receiving a data uplink grant.

[0257] UE 100 may start the monitoring sleep timer after transmission of SR, after transmission of BSR, or after transmission of each. The runtime of the monitoring sleep timer started after transmission of SR may be equal to or different from the runtime of the monitoring sleep timer started after transmission of BSR.

[0258] The present invention can be implemented by software, hardware or software in conjunction with hardware. Each functional block used in the description of each of the above embodiments can be implemented in part or in whole by LSI (large scale integration) such as integrated circuit (IC), and each process described in each embodiment can be controlled in part or in whole by the same LSI or a combination of LSI. LSI can be formed as a chip alone, or a chip can be formed to include some or all functional blocks. LSI can include data input and output coupled thereto. Here, LSI can be referred to as IC, system LSI, super LSI or super LSI according to the degree of integration. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented using dedicated circuits, general-purpose processors or dedicated processors. In addition, FPGA (field programmable gate array) can be programmed after manufacturing LSI or reconfigurable processors, wherein the connection and setting of the circuit unit configured inside LSI can be used. The present invention can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI as a reconfigurable processor due to the advancement of semiconductor technology or other derivative technologies, the functional blocks can be integrated using future integrated circuit technology. Biotechnology can also be applied.

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

[0260] Some non-limiting examples of such communication devices include phones (e.g., cellular (mobile) 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, telehealth / telemedicine (remote health and medicine) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.

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

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

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

[0264] 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 above non-limiting examples.

[0265] As described above, an apparatus and method capable of providing flexible and power-saving scheduling requests and resource allocation indications are provided.

[0266] A transceiver device is provided, comprising: a transceiver that sends a scheduling request for scheduling data through a physical uplink control channel PUCCH; and a circuit that starts a monitoring sleep timer after the transceiver sends the scheduling request, wherein the transceiver does not monitor a physical downlink control channel PDCCH when the monitoring sleep timer is running, and starts monitoring the PDCCH for resource allocation for scheduling data when the monitoring sleep timer expires.

[0267] In some embodiments, when a scheduling request is sent by the transceiver, the circuit starts a monitoring sleep timer.

[0268] In some embodiments, the transceiver receives a monitoring sleep indicator indicating the running of the monitoring sleep timer; and when the transceiver receives the monitoring sleep indicator, the circuit starts the monitoring sleep timer.

[0269] For example, the monitoring dormancy indicator indicates the running time of the monitoring dormancy timer according to the duration or the number of symbols and / or slots of the PDCCH.

[0270] In some embodiments, the runtime of the monitoring sleep timer is configured according to a priority level configured by the scheduling request.

[0271] For example, a first scheduling request configuration having a first priority level configures a first runtime for monitoring the sleep timer; and a second scheduling request configuration having a second priority level different from the first priority level configures a second runtime different from the first runtime for monitoring the sleep timer.

[0272] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

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

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

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

[0276] A transceiver device is also provided, comprising: a transceiver that sends a buffer status report indicating at least an amount of scheduled data; and a circuit that starts a monitoring sleep timer after the transceiver sends the buffer status report, wherein the transceiver does not monitor a physical downlink control channel (PDCCH) when the monitoring sleep timer is running, and starts monitoring the PDCCH for resource allocation for scheduled data when the monitoring sleep timer expires.

[0277] In some embodiments, the buffer status report is sent over the Physical Uplink Shared Channel PUSCH.

[0278] In some embodiments, the circuit starts a monitoring sleep timer when a buffer status report is sent by the transceiver.

[0279] In some embodiments, the transceiver receives a monitoring sleep indicator indicating the running of the monitoring sleep timer; and when the transceiver receives the monitoring sleep indicator, the circuit starts the monitoring sleep timer.

[0280] In some embodiments, the monitoring dormancy indicator indicates the runtime of the monitoring dormancy timer according to the duration or number of symbols and / or time slots of the PDCCH.

[0281] In some embodiments, the runtime of the dormancy timer is monitored according to the logical channel group configuration.

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

[0283] 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 scheduled data.

[0284] For example, each logical channel group is associated with a corresponding runtime of a monitoring dormancy timer.

[0285] For example, the runtime of the monitoring sleep timer may be set to the runtime associated with the LCG having the highest priority.

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

[0287] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

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

[0289] For example, the transceiver receives the logical channel group runtime indicator via a radio resource control, RRC, message.

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

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

[0292] In some embodiments, the circuit determines runtime of the monitor sleep timer; and the transceiver transmits a monitor sleep indicator indicating runtime of the monitor sleep timer.

[0293] For example, the runtime of the transmit timer is equal to the runtime of the monitor sleep timer.

[0294] A scheduling device is also provided, comprising: a circuit that allocates resources based on a buffer status report indicating the amount of scheduled data and starts a transmission timer; and a transceiver that receives the buffer status report and, after the transmission timer expires, sends a resource allocation indicator indicating the allocated resources via a physical downlink control channel (PDCCH).

[0295] For example, the transceiver receives the buffer status report via a physical uplink shared channel PUSCH.

[0296] In some embodiments, the circuit determines runtime of the monitor sleep timer; and the transceiver transmits a monitor sleep indicator indicating runtime of the monitor sleep timer.

[0297] For example, the runtime of the transmit timer is equal to the runtime of the monitor sleep timer.

[0298] In some embodiments, the circuitry determines the runtime of the monitoring sleep timer based on the logical channel group.

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

[0300] 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 scheduled data.

[0301] For example, each logical channel group is associated with a corresponding runtime of a monitoring dormancy timer.

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

[0303] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

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

[0305] For example, the transceiver sends the logical channel group runtime indicator via a radio resource control, RRC, message.

[0306] A method is also provided, comprising: sending a scheduling request for scheduling data via a physical uplink control channel PUCCH, starting a monitoring sleep timer after sending the scheduling request; preventing monitoring of a physical downlink control channel PDCCH while the monitoring sleep timer is running; and starting monitoring the PDCCH for resource allocation for scheduling data when the monitoring sleep timer has expired.

[0307] In some embodiments, when a scheduling request is sent, a monitoring sleep timer is started.

[0308] In some embodiments, receiving a monitoring sleep indicator indicating the running of a monitoring sleep timer; when the monitoring sleep indicator is received, starting the monitoring sleep timer;

[0309] For example, the monitoring dormancy indicator indicates the running time of the monitoring dormancy timer according to the duration or the number of symbols and / or slots of the PDCCH.

[0310] In some embodiments, the runtime of the monitoring sleep timer is configured according to a priority level configured by the scheduling request.

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

[0312] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

[0313] In some embodiments, receiving a scheduling request configuration indicator indicating at least one scheduling request configuration having at least one associated priority level,

[0314] For example, the scheduling request configuration indicator is received via a radio resource control, RRC, message.

[0315] In some embodiments, a discontinuous reception (DRX) cycle is configured in which the PDCCH is monitored during active periods and the PDCCH is not monitored during inactive periods.

[0316] A method is also provided, comprising sending a buffer status report indicating an amount of scheduled data; starting a monitoring sleep timer after sending the buffer status report; preventing monitoring of a physical downlink control channel (PDCCH) while the monitoring sleep timer is running; and starting monitoring the PDCCH for resource allocation for scheduled data when the monitoring sleep timer has expired.

[0317] In some embodiments, the buffer status report is sent over the Physical Uplink Shared Channel PUSCH.

[0318] In some embodiments, a monitoring sleep timer is started when a buffer status report is sent.

[0319] In some embodiments, the method includes receiving a monitoring sleep indicator indicating the running of a monitoring sleep timer; and starting the monitoring sleep timer when the monitoring sleep indicator is received.

[0320] In some embodiments, the monitoring dormancy indicator indicates the runtime of the monitoring dormancy timer according to the duration or number of symbols and / or time slots of the PDCCH.

[0321] In some embodiments, the runtime of the dormancy timer is monitored according to the logical channel group configuration.

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

[0323] 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 scheduled data.

[0324] For example, each logical channel group is associated with a corresponding runtime of a monitoring dormancy timer.

[0325] For example, the runtime of the monitoring sleep timer may be set to the runtime associated with the LCG having the highest priority.

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

[0327] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

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

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

[0330] In some embodiments, a discontinuous reception (DRX) cycle is configured in which the PDCCH is monitored during active periods and the PDCCH is not monitored during inactive periods.

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

[0332] In some embodiments, a runtime of a monitor sleep timer is determined; and a monitor sleep indicator is sent indicating the runtime of the monitor sleep timer.

[0333] For example, the runtime of the transmit timer is equal to the runtime of the monitor sleep timer.

[0334] A method is also provided, comprising receiving a buffer status report indicating an amount of scheduled data; starting a transmission timer; allocating resources based on the buffer status report; and after the transmission timer expires, sending a resource allocation indicator indicating the allocated resources via a physical downlink control channel (PDCCH).

[0335] For example, the transceiver receives the buffer status report via a physical uplink shared channel PUSCH.

[0336] In some embodiments, the method includes determining a runtime of a monitor sleep timer; and sending a monitor sleep indicator indicating the runtime of the monitor sleep timer.

[0337] For example, the runtime of the transmit timer is equal to the runtime of the monitor sleep timer.

[0338] In some embodiments, the method includes determining a runtime of a monitoring dormancy timer based on the logical channel group.

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

[0340] 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 scheduled data.

[0341] For example, each logical channel group is associated with a corresponding runtime of a monitoring dormancy timer.

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

[0343] For example, in case the first priority level is lower than the second priority level, the first runtime is greater than the second runtime, and in case the first priority level is higher than the second priority level, the first runtime is less than the second runtime.

[0344] In some embodiments, the method includes sending a logical channel group runtime indicator indicating an associated runtime of at least one logical channel group and a monitoring dormancy timer.

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

Claims

1. A communication device, comprising: a transceiver, sending a scheduling request SR via a physical uplink control channel PUCCH, wherein the SR is suspended until a valid uplink grant is received; and A circuit is coupled to the transceiver and starts an active time to monitor a physical downlink control channel (PDCCH) after the SR transmission and monitoring sleep time. 2 . The communication device according to claim 1 , wherein the duration of the monitoring sleep time is configured by high-layer signaling. 3 . The communication device according to claim 2 , wherein the duration of the monitoring sleep time is indicated in milliseconds (ms) or the number of symbols and / or time slots.

4. The communication device according to claim 1, wherein: The active time includes a time when the SR is sent on the PUCCH and the SR is suspended.

5. The communication device according to claim 1, wherein: In case that a discontinuous reception DRX cycle is configured, the transceiver monitors the PDCCH in an active period and does not monitor the PDCCH in an inactive period.

6. A scheduling device, comprising: a transceiver receiving a scheduling request SR from a communication device via a physical uplink control channel PUCCH, said SR being suspended until a valid uplink grant is sent to said communication device via a physical downlink control channel PDCCH, wherein after the SR sending and the monitoring dormant time, an active time is started to monitor said PDCCH; and A circuit is coupled to the transceiver and allocates resources according to the SR.

7. A method comprising: Sending a scheduling request SR via a physical uplink control channel PUCCH, wherein the SR is pending until a valid uplink grant is received; and After the SR transmission and monitoring sleep time, an active time is started to monitor the physical downlink control channel PDCCH.

8. A method comprising: receiving a scheduling request SR from a communication device via a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is sent to the communication device via a physical downlink control channel PDCCH, wherein an active time is started after the SR sending and a monitoring dormant time to monitor the PDCCH; and Resources are allocated according to the SR.

9. An integrated circuit controlling a process of a communication device, the process comprising: Sending a scheduling request SR via a physical uplink control channel PUCCH, wherein the SR is pending until a valid uplink grant is received; and After the SR transmission and monitoring sleep time, an active time is started to monitor the physical downlink control channel PDCCH.

10. An integrated circuit controlling a process of a scheduling device, the process comprising: receiving a scheduling request SR from a communication device via a physical uplink control channel PUCCH, the SR being suspended until a valid uplink grant is sent to the communication device via a physical downlink control channel PDCCH, wherein an active time is started after the SR sending and a monitoring dormant time to monitor the PDCCH; and Resources are allocated according to the SR.

Images