User equipment and scheduling nodes

Abstract

A user equipment (UE), a scheduling node, and a communication method for the UE and the scheduling node, respectively, are provided. The UE includes a transceiver, which receives a configuration of a PoSS time window for monitoring a power saving signal PoSS and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether the UE is allowed to skip monitoring of the PDCCH in the DRX ON period; and a circuit, which determines the PoSS time window based on the configuration, and controls the transceiver to perform monitoring of the PoSS within the PoSS time window.

Description

Technical Field

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

[0002] 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 frequency range up to 100 GHz. NR is a follower of technologies represented by Long Term Evolution (LTE) and LTE-Advanced (LTE-A).

[0003] For systems like LTE, LTE-A and NR, further modifications and options may facilitate efficient operation of the communication systems and specific devices associated with the systems. Summary of the invention

[0004] One non-limiting and exemplary embodiment facilitates user equipment to save power by going to sleep during most of the DRX OFF period and flexibly allocating power save signals (PoSS) suitable for various scenarios including multi-beam operation and repeated PoSS.

[0005] In an embodiment, the technology disclosed herein features a user equipment (UE) that includes a transceiver that receives a configuration of a PoSS time window for monitoring a power saving signal (PoSS) and before a discontinuous reception (DRX) ON period for monitoring a physical downlink control channel (PDCCH), wherein the PoSS indicates whether the UE is allowed to skip monitoring of the PDCCH in the DRX ON period; and a circuit that determines the PoSS time window based on the configuration and controls the transceiver to perform monitoring of the PoSS within the PoSS time window.

[0006] 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.

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

[0008] In the following exemplary embodiments, it will be described in more detail with reference to the accompanying drawings.

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

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

[0011] Figure 3 is a sequence diagram of the RRC connection establishment / reconfiguration process,

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

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

[0014] Figure 6 An illustration of the configuration of the search space for PDCCH,

[0015] Figure 7 is a block diagram of a scheduling node and a user equipment (UE),

[0016] Figure 8 is a block diagram of a PoSS (power saving signal) processing circuit of a UE,

[0017] Fig. 9 is a block diagram of the PoSS determination circuit of the scheduling node,

[0018] Fig.10 is a flow chart of a communication method performed by a scheduling node and a UE,

[0019] Fig.11 is a flow chart of a communication method for a UE,

[0020] Figures 12 to 15 is a diagram showing a PoSS time window. DETAILED DESCRIPTION

[0021] 5G NR system architecture and protocol stack

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] -Connection establishment and release;

[0039] - Scheduling and transmission of paging messages;

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

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

[0042] -Transport level packet marking in uplink;

[0043] -Session management;

[0044] - Network slicing support;

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

[0046] - Support of UE in RRC_INACTIVE state;

[0047] -NAS message distribution function

[0048] - Radio access network sharing;

[0049] -Dual connection;

[0050] - Close interaction between NR and E-UTRA.

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

[0052] - Non-access stratum NAS signaling termination;

[0053] -NAS signaling security;

[0054] -Access layer AS security control;

[0055] - Inter-Core Network (CN) node signaling for mobility between 3GPP access networks; - Idle mode UE reachability (including control and execution of paging retransmissions);

[0056] -Registration area management;

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

[0058] -Access authentication;

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

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

[0061] - Network slicing support;

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

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

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

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

[0066] -Packet routing & forwarding;

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

[0068] - Traffic usage reports;

[0069] - Uplink classifier that supports routing of traffic flows to data networks;

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

[0071] - QoS handling in the user plane, such as packet filtering, gating, UL / DL rate enforcement; - Uplink traffic verification (SDF to QoS flow mapping);

[0072] - Downlink packet buffering and downlink notification triggering.

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

[0074] -Session management;

[0075] -UE IP address allocation and management;

[0076] -Selection and control of UP function;

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

[0078] -Control some policy enforcement and QoS;

[0079] - Downlink data notification.

[0080] RRC connection establishment and reconfiguration process

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

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

[0083] Therefore, in the present disclosure, an entity (e.g., AMF, SMF, etc.) of a fifth generation core (5GC) is provided, which includes a control circuit for establishing a next generation (NG) connection with a gNodeB, and a transmitter, which sends an initial context establishment message to the gNodeB via the NG connection to cause a signaling radio bearer establishment 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.

[0084] IMT use cases in 2020 and beyond

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

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

[0087] From a physical layer perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability involves defining a separate CQI table for URLLC, a more compact DCI (downlink control information) format, repetition of PDCCH, etc. However, as NR becomes more stable and developed (a key requirement for NR URLLC), the scope for achieving ultra-reliability can be expanded. Specific use cases for NR URLLC in Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

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

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

[0090] As mentioned above, the scope of reliability in NR is expected to become wider. A key requirement for all cases, and especially necessary 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 key potential areas that can help improve reliability. Among these areas are compact control channel information, data / control channel repetition, and diversity with respect to frequency, time and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

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

[0092] In addition, for NR URLLC, several technical enhancements from the physical layer perspective have been identified. Among these are 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. PUSCH enhancements related to mini-slot level hopping and retransmission / repetition enhancements are also identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a time slot (a time slot including fourteen symbols).

[0093] In slot-based scheduling or allocation, the slot corresponds to the time granularity of the scheduling allocation (TTI—Transmission Time Interval). Typically, the TTI determines the time granularity of the scheduling allocation. One TTI is the time interval during which a given signal is mapped to the physical layer. For example, traditionally, the TTI length can vary between 14 symbols (slot-based scheduling) and 2 symbols (non-slot-based scheduling). Downlink (DL) and uplink (UL) transmissions are specified to be organized into frames (10ms duration) consisting of 10 subframes (1ms duration). In slot-based transmission, the subframes are further divided into slots, and the number of slots is defined by the parameter set / subcarrier spacing. The specified values ​​range between 10 slots per frame (1 slot per subframe) for 15kHz subcarrier spacing to 80 slots per frame (8 slots per subframe) for 120kHz subcarrier spacing. For a normal cyclic prefix, the number of OFDM symbols per time slot is 14, and for an extended cyclic prefix, the number of OFDM symbols per time slot is 12 (see Section 4.1 (General frame structure), Section 4.2 (Parameter sets), Section 4.3.1 (Frames and subframes), and Section 4.3.2 (Time slots) of 3GPP TS 38.211 V15.3.0, Physical Channels and Modulation, 2018-09). However, the allocation of time resources for transmission may also be non-slot based. Specifically, a TTI in a non-slot based allocation may correspond to a mini-slot instead of a time slot. That is, one or more mini-slots may be allocated for the transmission of requested data / control signaling. In a non-slot based allocation, the minimum length of a TTI may be, for example, 1 or 2 OFDM symbols.

[0094] QoS Control

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

[0096] For each UE, the 5GC establishes one or more PDU Sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session, and may subsequently configure additional DRBs for the QoS flows of that PDU Session (when to do so is up to the NG-RAN), e.g. as described above with reference to Figure 3As shown in Figure 1. NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in UE and NG-RAN associate UL and DL QoS flows with DRBs.

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

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

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

[0100] In wireless communication systems such as LTE and NR, discontinuous reception (DRX) is applied to improve the efficiency of power utilization. DRX is a method of shortening the active period in RRC_CONNECTED mode without scheduling authorization. Specifically, through a timer that can be configured by the eNB or gNB, the UE is able to operate in an active mode (or DRX ON state) and a DRX OFF state or mode, in which the UE monitors the PDCCH, and in which the reception is turned off.

[0101] Therefore, the DRX mechanism provides an ON duration (in which the PDCCH is monitored) and an OFF duration (in which the PDCCH is not monitored). The start time and duration of the ON time (and therefore the OFF time) are configured by RRC, which means that it is not dynamic, but at most semi-static. Dynamic change means changing with the scheduling frequency, for example, with the scheduling grant. Semi-static may still mean changing during the communication connection, for example, by RRC, but the RRC configuration is not as frequent as the scheduling grant. Since in DRX, the PDCCH cannot usually be monitored during the OFF duration, the service delay may increase, which may not be effective for some specific, delay-sensitive services. In other words, since in the OFF mode, the UE does not monitor the PDCCH, if traffic arrives, the UE cannot be scheduled until the next ON duration. Therefore, for some services, low latency requirements may not be guaranteed. However, it should be noted that even when DRX is applied, the UE can still monitor certain types of signals or PDCCHs during the DRX OFF period, such as common PDCCH or paging. However, during the DRX OFF period, there is no need to monitor UE-specific PDCCHs.

[0102] If the DRX ON duration period is configured with a short value, power consumption will increase due to the increased monitoring of the PDCCH. Even in the case of no traffic at all, the UE still needs to turn on to monitor the PDCCH, which results in a waste of power. Conversely, when traffic arrives, DRX may result in long waiting times, and when no traffic arrives, DRX may result in unnecessary power waste.

[0103] To improve the power saving capability, Power Saving Signaling (PoSS) can be used in addition to DRX and in combination with DRX. For example, the power saving signal is based on DCI: it can be included in a special DCI that is monitored during the DRX OFF period. Specifically, if the UE receives PoSS before the start of the DRX ON period, the PoSS can indicate to the UE whether it needs to perform monitoring during the next PDCCH, or whether it can remain in the OFF state (or "sleep") during the next DRX ON period.

[0104] For example, the PoSS saving signal is monitored outside of the active time (or DRX ON period), with an offset before DRX ON. Such a configuration is intended to include that PoSS does not need to be monitored during DRX ON. Furthermore, in this example, a single monitoring opportunity is assumed (e.g., PoSS is monitored only in a single time slot).

[0105] However, multiple monitoring occasions are supported to provide better PoSS reception reliability and support for beamforming / scanning operations, and multiple monitoring occasions may be supported by a working assumption that more than one monitoring occasion may be configured within a timeslot or multiple timeslots before DRX ON.

[0106] The following two alternatives can be used to specify the PoSS monitoring timing:

[0107] Alternative 1: Provide a dedicated configuration with an offset relative to the start of DRX ON. This corresponds to a single position of the monitoring occasion with a configured offset relative to the start of DRX ON.

[0108] Alternative 2: Offset based on search space configuration This alternative proposes to use a common search space configuration associated with DRX without other new signaling.

[0109] In the NR specification of the common search space configuration, the PDCCH monitoring timing is controlled by parameters from the IE (Information Element) Search Space and Control Resource Set (ControlResourceSet) in the RRC signaling, such as Figure 6As shown. Basically, the monitoring slot period and offset (monitoringSlotPeriodicityAndOffset) and duration (duration) in the search space (SearchSpace) determine the time slot for monitoring PDCCH. Then, the bitmap monitoring symbols within the time slot (monitoringSymbolsWithinSlot) in the search space (SearchSpace) and the duration (duration) in the control resource set (ControlResourceSet) determine the PDCCH monitoring mode (e.g., the starting symbol and the number of symbols) of the search space within the time slot.

[0110] Typically, a monitoring opportunity corresponds to the configured time and frequency domain resources in several consecutive symbols within a time slot. TS38.213 V15.6.0 Section 10.1 defines the monitoring opportunity:

[0111] The UE determines the PDCCH monitoring timing on the active DLBWP based on the PDCCH monitoring period, PDCCH monitoring offset and PDCCH monitoring mode in the time slot. For the search space set s, if Then the UE determines that the f The frame number is There is a PDCCH monitoring opportunity in the time slot of Start monitoring T s The PDCCH candidates of the search space set s of consecutive time slots are not monitored. s -T s The search space set s of consecutive time slots contains PDCCH candidates.

[0112] This definition of monitoring occasion is applicable to monitoring PDCCH for DCI. It is particularly applicable to PoSS monitoring occasion for monitoring DCI-based PoSS included in a specific DCI and monitored outside the DRX ON period.

[0113] As mentioned above, PoSS monitoring opportunities are configured before the DRX ON period. DRX configuration also utilizes Figure 6 The period and offset forms shown.

[0114] Then, when looking at the RRC configuration for drx-LongCycleStartOffset as shown below, the supported period and offset options do not align with the monitoringSlotPerodicityAndOffset options in the SearchSpace further shown below:

[0115] RRC configuration for drx-LongCycleStartOffset:

[0116]

[0117] RRC configuration for monitoring slot period and offset (monitoringSlotPerodicityAndOffset):

[0118]

[0119]

[0120] Therefore, if the PoSS search space is directly associated with the DRX configuration when following the above search space configuration, the misaligned period of the above configuration may cause the PoSS monitoring opportunities to be widely spread during the DRX OFF period. This may make it more difficult for the UE to save power by going to sleep for most of the DRX OFF duration and start monitoring PoSS a few time slots before DRX ON. This may be an obstacle for the PoSS search space configuration to directly reuse the above search space IE and associate it with the DRX configuration.

[0121] In addition, DRX configuration is more UE-specific because it takes into account UE traffic patterns, base station scheduling strategies, and time domain load expansion due to control / data physical resource shortages. Although PoSS monitoring occasions are also UE-specifically configured, group-based operation supports wake-up triggers. Therefore, one monitoring occasion with a fixed offset value before DRX ON is limited for wake-up triggers.

[0122] Furthermore, the above description may not be sufficient to support enhancement by configuring multiple monitoring opportunities for repetition or beamforming operations.

[0123] The present disclosure provides a technology for power saving signal monitoring. Specifically, it specifies accurate, well-positioned and sufficient monitoring opportunities for PoSS based on DCI, clarifies the behavior of UE in the standard, recommends configuring the monitoring window or duration, and defines the corresponding UE behavior for monitoring PoSS.

[0124] In the present disclosure, a UE and a scheduling node such as a base station and corresponding methods are described for a new radio access technology envisioned for a 5G mobile communication system such as 3GPP NR but which may also be used for an LTE mobile communication system.

[0125] Therefore, the communication device (or user terminal or communication terminal) is referred to as UE (User Equipment), and the scheduling node such as the base station may correspond to gNodeB (gnN).

[0126] In addition, some of the terms for processes, entities, layers, etc. used below are closely related to the terms used in LTE / LTE-A systems or in the current 3GPP 5G standardization, even though the specific terms used in the context of the new radio (NR) access technology of the next 3GPP 5G communication system have not yet been fully decided or may eventually change. Therefore, the terms may be changed in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art realize that the embodiments and their scope of protection should not be limited to the specific terms used exemplarily herein due to the lack of updated or finally agreed terms.

[0127] Communication devices or equipment such as UE and scheduling nodes may include transceivers and circuits such as processing circuits. The transceiver may include and / or be used as a receiver and a transmitter. The processing circuit may be one or more pieces of hardware, such as one or more processors or any LSI (large scale integration). There are input / output points (or nodes) between the transceiver and the processing circuit, and the processing circuit may control the transceiver through the input / output points (or nodes), that is, control the receiver and / or transmitter and exchange receive / transmit data. The transceiver as a transmitter and receiver may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit may implement control tasks, such as controlling the transceiver to send user data and control data provided by the processing circuit and / or receiving user data and control data further processed by the processing circuit. The processing circuit may also be responsible for performing other processes, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the transmission process and other processes related thereto. The receiver may be responsible for performing the reception process and other processes related thereto, such as monitoring channels.

[0128] Provided Figure 7 A user equipment (UE) 760 and a scheduling node 710 are shown. The UE 760 and the scheduling node, which may be a gNB in ​​3GPP NR, communicate via a wireless channel in a wireless communication system.

[0129] The UE includes a transceiver 770 (or "UE transceiver") and circuitry 780 ("UE circuitry"), such as processing circuitry.

[0130] The transceiver receives the configuration of the PoSS (Power Save Signal) time window. The PoSS time window is a time interval for monitoring PoSS and precedes the DRX ON interval for monitoring PDCCH. PoSS indicates whether the UE is allowed to skip monitoring of PDCCH in the DRX ON period.

[0131] The UE circuit 780 determines the PoSS time window based on the received configuration, and controls the transceiver to perform monitoring of the PoSS within the PoSS time window.

[0132] The UE transceiver 770 performs monitoring of the PoSS according to the control of the UE circuit 770 , and may be further controlled by the UE circuit 780 to perform monitoring of the PDCCH in the next DRX ON period after the PoSS time window according to an indication included in the PoSS.

[0133] For example, if the PoSS indication allows the UE 760 to skip (or omit) monitoring of the PDCCH during the DRX ON period, the UE circuit 780 controls the UE transceiver 770 to skip monitoring of the PDCCH during the DRX ON period. Therefore, the UE does not monitor the PDCCH during the DRX ON period. On the other hand, if the PoSS indication does not allow the UE 760 to skip monitoring of the PDCCH during the DRX ON period, the UE circuit 780 controls the UE transceiver 770 to monitor the PDCCH during the DRX ON period.

[0134] As from Figure 7 It can be seen that the UE circuit 780 may include Figure 8 The PoSS processing circuit 785 shown. For example, the PoSS processing circuit includes a PoSS time window determination circuit 886 and a PoSS monitoring circuit 887.

[0135] The scheduling node includes circuitry 730 or "scheduling node circuitry," and transceiver 720 or "scheduling node transceiver."

[0136] The scheduling node circuit 730 determines the configuration of the PoSS time window for the UE to monitor the PoSS. The PoSS time window precedes the DRX ON period for monitoring the PDCCH, and the PoSS indicates whether the UE is allowed to skip monitoring the PDCCH in DRX.

[0137] The scheduling node transceiver 720 sends the configuration of the PoSS time window and sends the PoSS within the time window.

[0138] For example, the scheduling node 710 performs transmission of the PDCCH in the DRX ON period according to the instruction of the PoSS. Therefore, if the PoSS does not indicate to skip monitoring, the scheduling node transceiver 720 transmits the PDCCH, and if the PoSS indicates that the UE can skip monitoring of the PDCCH in the DRX ON period, the scheduling node transceiver 720 skips (or omits) the transmission of the PDCCH.

[0139] like Figure 7As shown, the scheduling node circuit 730 may include a PoSS determination circuit 735. Fig. 9 As further shown, the PoSS determination circuit 735 may include a PoSS time window configuration circuit 936 and a PoSS generation circuit 937 .

[0140] Corresponding to the above-mentioned apparatus, the present application provides a communication method to be executed by UE 760 and a communication method to be executed by scheduling node 710. The steps of the communication method executed by UE 760 and scheduling node 710 are as follows: Fig.10 Shown in.

[0141] In step S1010, the scheduling node 710 determines the configuration of the PoSS time window in which the UE 760 will perform monitoring of the PoSS. The PoSS time window is before the DRX ON period, and the PoSS indicates whether the monitoring of the PDCCH will be performed by the UE in the DRX ON period. In step S1020, the scheduling node 710 sends the configuration of the PoSS time window to the UE 760, and the UE 760 receives the configuration from the scheduling node in step S1030. In step S1040, the UE 760 determines the PoSS time window based on the configuration. In addition, the scheduling node 710 sends the PoSS to the UE 760 in step S1050, and the UE 760 monitors the PoSS time window within the configured time window in step S1060.

[0142] In addition, in the DRX ON window, the scheduling node may perform transmission of the PDCCH, for example, transmit the PDCCH or skip transmission of the PDCCH according to the PoSS signal, and the UE thus monitors or skips monitoring of the PDCCH.

[0143] Regarding the UE, exemplary steps and decisions for monitoring the PoSS are described in Fig.11 As shown in FIG. 11 . In step S1110, PoSS monitoring is started, including determining or deciding whether monitoring is to be performed. In step S1120, the UE checks or determines whether it is in a DRX OFF state or whether the current time instance is within a DRX OFF period. If not, such as in a DRX ON period, the PoSS may not be monitored, S1150. If yes, the UE checks whether the current time instance is within a configured PoSS monitoring window, S1130. If the current time instance is not within the PoSS monitoring window, the PoSS is not monitored (S1150). If the current time instance is within the configured monitoring window, the PoSS is monitored, S1140.

[0144] For example, PoSS is located according to Figure 6The monitoring opportunities within the search space configured as described above. Therefore, the periodicity and duration of the time slot and the symbol within the time slot can be determined by the search space configuration. However, according to the present disclosure, if the PoSS monitoring window is configured, it is only necessary to monitor the monitoring opportunities of the search space within the window. Therefore, the UE can sleep or does not need to perform any monitoring on the PoSS outside the PoSS monitoring window.

[0145] There may be one or more configured search spaces. For example, the UE may be configured with one or more search spaces, including monitoring opportunities for monitoring the PoSS. For example, in multi-beam operation, each search space may be associated with one of the multiple beams. The UE transceiver 770 is controlled by the UE circuit 780 to monitor and perform monitoring of the PoSS at a monitoring opportunity that falls within a PoSS time window.

[0146] Therefore, the PoSS time window may be included in a plurality of PoSS time windows. Each time window is configured for a search space in a plurality of search spaces, and each of the plurality of search spaces is associated with one of a plurality of beams. The scheduling node transceiver 720 transmits each of the plurality of PoSSs including the PoSS on a corresponding one of the plurality of beams within the PoSS time windows respectively configured according to the associated search spaces.

[0147] In addition to beamforming operations, the provision of a PoSS time window also allows repetitions of sending power saving signals. Monitoring and reception of PoSS and its repetitions can provide power saving gains for UE 660. Therefore, in some embodiments, the scheduling node transceiver 720 sends repetitions of PoSS within the PoSS time window.

[0148] In a configuration, a PoSS time window (eg, a start, end, or length of the time window) may be indicated in units of time slots, for example as a number of time slots.

[0149] On the other hand, the PoSS monitoring window may also be indicated as a number of monitoring opportunities, such as the configured monitoring opportunities included in the configured search space. Figure 6For the search space configuration shown, the number of monitoring opportunities may correspond to the number of monitoring symbols (such as the "1" bits in the bitmap monitoring symbols within the time slot (monitoringSymbolsWithinSlot) multiplied by the duration in the symbol, which duration corresponds to the duration (duration) in the search space IE (SeachSpace IE)) multiplied by the number of monitoring time slots included in the window, as indicated by the monitoring time slot periodicity (monitoringSlotPeriodicity) and offset (Offset) and duration (duration) in the control resource set (ControlResourceSet). Alternatively, with respect to the number of monitoring symbols, only the "1" bits in the monitoring symbols (monitoringSymbolsWithinSlot) within the time slot corresponding to the start symbol for monitoring may be counted without multiplying them by the duration in the symbol.

[0150] The configuration of PoSS can be sent and received via RRC signaling.

[0151] In the present disclosure, any embodiment will be understood to describe and be applicable to each of the UE 760, the scheduling node 710, and the corresponding communication method.

[0152] For example, the configuration of the PoSS time window may include an offset indicating the start of the PoSS time window. The offset is an offset relative to the start of the DRX ON period.

[0153] For example, the offset may indicate the number of time slots, or the time distance in time slots, or the number of monitoring opportunities between the start of the PoSS monitoring window and the start of the DRX ON period, or the number of time slots or configured monitoring opportunities before the DRX ON period at which the PoSS monitoring window starts.

[0154] Regarding the end of the PoSS time window, in some embodiments, the PoSS time window ends at the beginning of the DRX ON period. Therefore, the last time slot of the PoSS monitoring window or the PoSS time window is the last time slot before the start of the DRX ON period, which is temporally adjacent to the first time slot included in the DRX ON period. Similarly, the last monitoring opportunity may be the last monitoring opportunity included in the search space before the start of the DRX ON period.

[0155] However, in some embodiments, the configuration of the PoSS time window may include a first offset (e.g., in units of time slots or monitoring opportunities) indicating the start of the PoSS time window and a second offset (e.g., in units of time slots or monitoring opportunities) indicating the end of the PoSS time window relative to the start of the DRX ON period (or with respect to the start of the DRX ON period). Alternatively, the second offset may indicate the duration of the PoSS time window (the number of time slots or the number of monitoring opportunities) starting from the start of the PoSS time window.

[0156] Therefore, according to the present disclosure, the monitoring opportunity of the PoSS is determined by a window or a duration. As will be further described, in some embodiments, the PoSS time window may be, for example, specific to a search space. Therefore, the PoSS time window or monitoring duration may be determined by the search space configuration and one offset Xstart or two offsets (a first offset Xstart and a second offset Xend) configured for each search space.

[0157] However, in some embodiments, the configuration of the PoSS time window is specific to the DRX configuration. Thus, the window or duration for monitoring PoSS may be determined by one offset Ystart, or a first offset Ystart and a second offset Yend associated with the DRX configuration.

[0158] Search space specific PoSS time window configuration

[0159] exist Fig.12 In FIG. 1 , an example of a search space specific PoSS time window configuration is shown for two search spaces (search space 1 and search space 2). The PoSS time window or PoSS monitoring window is defined for each search space by a corresponding parameter Xstart, which indicates the starting offset if it is a PoSS time window. The parameter Xstart is configured for each search space set for PoSS monitoring. Fig.12 and continuous Figure 13 to Figure 15 In , an array of time slots is shown, and the search space is shown as shaded time slots. In addition, "X" marks indicate time slots in the search space within the PoSS monitoring window.

[0160] If the UE 760 is in the DRX OFF state, the UE will monitor the PoSS in all configured or valid search space monitoring occasions falling within the PoSS time window, which spans the corresponding time slot indicated by the Xstart parameter before the next nearest subsequent DRX ON period or duration until the start of the DRX ON duration. As described above, the parameter (s) Xstart can be indicated by the number of time slots or the number of monitoring opportunities.

[0161] In some embodiments, monitoring opportunities of the PoSS that fall within the DRX ON period may be skipped by the UE since they do not fall within the PoSS monitoring window.

[0162] The parameter Xstart (or multiple parameters Xstart) can be added in the IE search space (IE Search Space), which is configured with a PS-RNTI (Power Saving RNTI (Radio Network Temporary Identifier)). For example, the PS-RNTI is a UE-specific RNTI. Alternatively, each parameter Xstart (or Xoffset) can also be separately configured with a corresponding search space, where the search space is configured with multiple RNTIs, such as an RNTI for each search space.

[0163] The search space specific PoSS time window configuration changes in Fig.13 Specifically, two values ​​may be configured for each search space instead of using one value to define the monitoring window or duration.

[0164] Therefore, the configuration of the PoSS time window of the search space can be a parameter pair {Xstart, Xend} or a parameter pair {Xstart, duration (duration) or Xduration (Xduration)}. For both options of the parameter pair, the two parameters can be indicated in units of the number of time slots or the number of monitoring opportunities. As a further alternative, the parameter pair {Xend, duration (duration)} can be configured.

[0165] and Fig.12 Similarly, also in the case of two parameters per search space, monitoring occasions will apply and will be monitored by the UE 660, which fall within the monitoring window relative to the next consecutive DRX ON duration or period.

[0166] The provision of a second parameter or a second offset Yend indicating the end of the PoSS window or an indicator of the window length or duration allows providing a gap between the end of the PoSS time window and the DRX ON period. Providing some gap through Xend or the duration between the PoSS monitoring window and the DRX ON period can help provide some time budget for the UE 660 to handle PoSS, determine whether to wake up, and ramp up from the start of DRX ON to start monitoring PDCCH.

[0167] As in the case of one parameter, the parameter pair can be added to the IE search space configured with the PS-RNTI. In addition, each parameter pair of one of the multiple search spaces can be configured separately using multiple RNTIs.

[0168] DRX configuration specific PoSS time window configuration

[0169] An example of the configuration of a PoSS time window specific to a DRX configuration is given in Fig.14 The start of the PoSS monitoring window defines an offset, which may be referred to as Ystart, and which is configured by RRC with DRX configuration.

[0170] If the UE 660 is in DRX OFF state, it shall monitor PoSS in all its configured valid search spaces that fall within the PoSS time window, which spans from the time slot indicated by Ystart before the next subsequent DRX ON duration until the start of the DRX ON duration. Fig.14 It can be seen that the PoSS time window has the same number of slots for all search spaces.

[0171] The parameter / offset Xstart may be indicated by the number of time slots or the number of monitoring opportunities. For example, if the offset is indicated as the number of monitoring opportunities, the number of opportunities may be calculated as the total number of monitoring opportunities counted across the configured search space.

[0172] Alternatively, it may be indicated as the number of monitoring opportunities per search space. In this case, the number of indicated opportunities is counted in each search space, and the indicated number multiplied by the number of search spaces is the total number of opportunities.

[0173] As a variation, also when configuring the PoSS time window specific to a DRX configuration, two values ​​may be configured to define the monitoring window, such as a start and an end or its duration, instead of using a single value. An example of such a configuration is given in Fig.15 Shown in.

[0174] For example, the configuration of the PoSS time window may include a parameter pair {Ystart, Yend} corresponding to the first and second offsets relative to the start of the DRX ON period, or a parameter pair {Ystart, duration or Yduration} corresponding to the offset and duration. As a further alternative, a parameter pair {Yend, duration} may be configured. Similar to the above embodiment. In addition, also in this example, the monitoring opportunities falling within the monitoring window relative to the next consecutive DRX ON duration or period will be applied and monitored by the UE 660.

[0175] for Fig.13 The benefit of providing some gap between PoSS monitoring and DRX ON through the second parameter Yend or duration as shown in the search space specific configuration is that it provides some time budget for the UE to handle PoSS, decide whether to wake up and push to start monitoring PDCCH from the start of DRX ON.

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

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

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

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

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

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

[0182] 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 used by the communication device that performs the communication functions of the communication device.

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

[0184] The present disclosure provides a user equipment (UE), including a transceiver, which receives a configuration of a PoSS time window for monitoring PoSS (power saving signal) and before a DRX (discontinuous reception) ON period for monitoring PDCCH (physical downlink control channel), wherein the PoSS indicates whether the UE is allowed to skip monitoring of the PDCCH in the DRX ON period; and a circuit, which determines the PoSS time window based on the configuration, and controls the transceiver to perform monitoring of the PoSS within the PoSS time window.

[0185] For example, if the PoSS indicates that the UE is allowed to skip monitoring of the PDCCH in the DRX ON period, the circuit controls the transceiver to skip monitoring of the PDCCH in the DRX ON period.

[0186] For example, the configuration of the PoSS time window includes indicating an offset of the start of the PoSS time window relative to the start of the DRX ON period.

[0187] In some embodiments, the PoSS time window ends at the beginning of the DRX ON period.

[0188] In some embodiments, the first offset indicates the start of a PoSS time window, and the configuration of the PoSS time window includes a second offset indicating the end of the PoSS time window relative to the start of the DRX ON period or the duration of the PoSS time window.

[0189] In some embodiments, the configuration of the PoSS time window is specific to the search space.

[0190] For example, the configuration of the PoSS time window is search space specific.

[0191] For example, the UE is configured with one or more search spaces including monitoring opportunities for monitoring the PoSS, and the transceiver performs monitoring of the PoSS at monitoring opportunities falling within a PoSS time window.

[0192] For example, the one or more search spaces include the search space of the above embodiment, in which the configuration of the PoSS time window is specific to the search space.

[0193] In some embodiments, the configuration of the PoSS time window is specific to the DRX configuration.

[0194] In some embodiments, the PoSS time window is indicated as a number of time slots.

[0195] In some embodiments, the PoSS time window is indicated as a number of monitoring opportunities.

[0196] In some embodiments, the circuit controls the transceiver to monitor the repetition of PoSS within the PoSS time window.

[0197] For example, the PoSS time window is included in a plurality of PoSS time windows, each PoSS time window is configured for a search space of a plurality of search spaces, each search space being associated with one of the plurality of beams.

[0198] A scheduling node is also provided, comprising: a circuit that determines a configuration of a PoSS time window for monitoring PoSS (Power Save Signal) by a user equipment and before a DRX (Discontinuous Reception) ON period for monitoring PDCCH (Physical Downlink Control Channel), wherein the PoSS indicates whether it is allowed to skip monitoring of the PDCCH in the DRX ON period; and a transceiver that sends the configuration of the PoSS time window, and sends the PoSS within the PoSS time window.

[0199] For example, if the PoSS indicates that skipping monitoring of the PDCCH in the DRX ON period is allowed, the transceiver skips sending the PDCCH in the DRX ON period.

[0200] For example, the configuration of the PoSS time window includes indicating an offset of the start of the PoSS time window relative to the start of the DRX ON period.

[0201] In some embodiments, the PoSS time window ends at the beginning of the DRX ON period.

[0202] In some embodiments, the first offset indicates the start of a PoSS time window, and the configuration of the PoSS time window includes a second offset indicating the end of the PoSS time window relative to the start of the DRX ON period or the duration of the PoSS time window.

[0203] In some embodiments, the configuration of the PoSS time window is specific to the search space.

[0204] For example, the configuration of the PoSS time window is search space specific.

[0205] For example, a circuit that determines and generates a configuration of one or more search spaces including monitoring opportunities for monitoring PoSS; and a transceiver that transmits PoSS on at least one of the monitoring opportunities that falls within a PoSS time window.

[0206] For example, the one or more search spaces include the search space of the above embodiment, in which the configuration of the PoSS time window is specific to the search space.

[0207] In some embodiments, the configuration of the PoSS time window is specific to the DRX configuration.

[0208] In some embodiments, the PoSS time window is indicated as a number of time slots.

[0209] In some embodiments, the PoSS time window is indicated as a number of monitoring opportunities.

[0210] For example, the transceiver sends repetitions of the PoSS within the PoSS time window.

[0211] In some embodiments, the PoSS time window is included in a plurality of PoSS time windows, each PoSS time window is configured for a search space in a plurality of search spaces, each search space is associated with one of a plurality of beams, and the transceiver transmits each of the plurality of PoSSs including the PoSS on a corresponding one of the plurality of beams within the PoSS time windows respectively configured according to the associated search space.

[0212] A communication method for a UE is also provided, comprising receiving a configuration of a PoSS time window for monitoring a PoSS (power saving signal) and before a DRX (discontinuous reception) ON period for monitoring a PDCCH (physical downlink control channel), wherein the PoSS indicates whether the UE is allowed to skip monitoring of the PDCCH in the DRX ON period; and determining the PoSS time window based on the configuration, and monitoring the PoSS within the PoSS time window.

[0213] In some embodiments, the method includes, if the PoSS indicates that the UE is allowed to skip monitoring of the PDCCH during the DRX ON period, skipping monitoring of the PDCCH during the DRX ON period.

[0214] For example, the configuration of the PoSS time window includes indicating an offset of the start of the PoSS time window relative to the start of the DRX ON period.

[0215] For example, where the PoSS time window ends at the beginning of the DRX ON period.

[0216] For example, the first offset indicates the start of a PoSS time window, and the configuration of the PoSS time window includes a second offset indicating the end of the PoSS time window relative to the start of the DRX ON period or the duration of the PoSS time window.

[0217] In some embodiments, the configuration of the PoSS time window is specific to the search space.

[0218] For example, the configuration of the PoSS time window is search space specific.

[0219] In some embodiments for a UE configured with one or more search spaces, including monitoring opportunities for monitoring PoSS, the method includes monitoring the PoSS at a monitoring opportunity falling within a PoSS time window.

[0220] For example, the one or more search spaces include the search space of the above embodiment, in which the configuration of the PoSS time window is specific to the search space.

[0221] For example, the configuration of the PoSS time window is specific to the DRX configuration.

[0222] In some embodiments, the PoSS time window is indicated as a number of time slots.

[0223] In some embodiments, the PoSS time window is indicated as a number of monitoring opportunities.

[0224] For example, the method includes monitoring the repetition of the PoSS within the PoSS time window.

[0225] For example, the PoSS time window is included in a plurality of PoSS time windows, each PoSS time window is configured for a search space of a plurality of search spaces, each search space being associated with one of the plurality of beams.

[0226] A communication method for a scheduling node is also provided, comprising: determining a configuration of a PoSS time window for monitoring PoSS (power saving signal) by a user equipment and before a DRX (discontinuous reception) ON period for monitoring PDCCH (physical downlink control channel), wherein the PoSS indicates whether it is allowed to skip monitoring of the PDCCH in the DRX ON period; sending the configuration of the PoSS time window; and sending the PoSS within the PoSS time window.

[0227] For example, the method includes, if the PoSS indicates that the UE is allowed to skip monitoring of the PDCCH in the DRX ON period, skipping transmission of the PDCCH in the DRX ON period.

[0228] For example, the configuration of the PoSS time window includes indicating an offset of the start of the PoSS time window relative to the start of the DRX ON period.

[0229] In some embodiments, the PoSS time window ends at the beginning of the DRX ON period.

[0230] In some embodiments, the first offset indicates the start of a PoSS time window, and the configuration of the PoSS time window includes a second offset indicating the end of the PoSS time window relative to the start of the DRX ON period or the duration of the PoSS time window.

[0231] In some embodiments, the configuration of the PoSS time window is specific to the search space.

[0232] For example, the configuration of the PoSS time window is search space specific.

[0233] For example, the method includes configuring one or more search spaces including monitoring opportunities for monitoring PoSS, and sending PoSS at at least one of the monitoring opportunities falling within a PoSS time window.

[0234] For example, the one or more search spaces include the search space of the above embodiment, in which the configuration of the PoSS time window is specific to the search space.

[0235] In some embodiments, the configuration of the PoSS time window is specific to the DRX configuration.

[0236] For example, the PoSS time window is indicated as the number of time slots.

[0237] For example, the PoSS time window is indicated as the number of monitoring opportunities.

[0238] In some embodiments, the method includes sending a repetition of the PoSS within a PoSS time window.

[0239] For example, the PoSS time window includes a plurality of PoSS time windows, each PoSS time window is configured for a search space in a plurality of search spaces, each search space is associated with one of a plurality of beams, and the method includes transmitting each of a plurality of PoSSs including the PoSS on a corresponding one of the plurality of beams within the PoSS time windows respectively configured according to the associated search space.

[0240] Overview Provided are user equipment (UE), scheduling nodes, and communication methods for the UE and scheduling nodes, respectively. The UE includes a transceiver that receives a configuration of a PoSS time window for monitoring PoSS (power saving signal) and before a DRX (discontinuous reception) ON period for monitoring PDCCH (physical downlink control channel), wherein the PoSS indicates whether the UE is allowed to skip monitoring of the PDCCH in the DRX ON period; and a circuit that determines the PoSS time window based on the configuration and controls the transceiver to perform monitoring of the PoSS within the PoSS time window.

Claims

1. A user equipment UE, include: a transceiver receiving a configuration of a PoSS time window for monitoring a power saving signal PoSS and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether the UE starts monitoring the PDCCH in the DRX ON period; and a circuit that determines the PoSS time window based on the configuration, and controls the transceiver to perform monitoring of the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

2. The UE according to claim 1, in, If the PoSS instructs the UE not to start monitoring the PDCCH in the DRX ON period, the circuit controls the transceiver not to start monitoring the PDCCH in the DRX ON period.

3. The UE according to claim 1, in, The configuration of the PoSS time window includes indicating a first offset of a start of the PoSS time window relative to a start of the DRX ON period.

4. The UE according to claim 3, in, The second offset indicates a gap between an end of the PoSS time window and the DRXON period.

5. The UE according to claim 1, in, The UE is configured with one or more search spaces including monitoring opportunities for monitoring the PoSS, and the transceiver performs monitoring of the PoSS at the monitoring opportunities within the PoSS time window.

6. The UE according to claim 5, in, The single position of the monitoring occasion is configured relative to the start of the DRX ON period.

7. The UE according to claim 1, in, The configuration of the PoSS is received via RRC signaling.

8. The UE according to claim 1, in, The PoSS is monitored outside of active hours.

9. The UE according to claim 1, in, The duration of monitoring of the PoSS in the search space is indicated as the number of time slots.

10. The UE according to claim 1, in, The UE is configured with one or more search spaces including monitoring opportunities, and wherein the number of monitoring opportunities corresponds to the number of monitoring symbols multiplied by the number of monitoring slots.

11. A scheduling node, include: a circuit for determining a configuration of a PoSS time window for monitoring a power saving signal PoSS by a user equipment and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether to start monitoring the PDCCH in the DRX ON period; and a transceiver for transmitting the configuration of the PoSS time window and transmitting the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

12. The scheduling node according to claim 11, in, The transceiver sends a repetition of the PoSS within the PoSS time window.

13. The scheduling node according to claim 11, in, The PoSS time window includes a plurality of PoSS time windows, each PoSS time window is configured for a search space among a plurality of search spaces, each search space is associated with one of a plurality of beams, and the transceiver transmits each of a plurality of PoSSs including the PoSS on a corresponding one of the plurality of beams within the PoSS time windows respectively configured according to the associated search space.

14. A communication method for a user equipment UE, include: receiving a configuration of a PoSS time window for monitoring a power saving signal PoSS and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether the UE starts monitoring the PDCCH in the DRX ON period; and determining the PoSS time window based on the configuration, and monitoring the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

15. A communication method for scheduling nodes, include: determining a configuration of a PoSS time window for monitoring a power saving signal PoSS by a user equipment and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether to start monitoring the PDCCH in the DRX ON period; Sending the configuration of the PoSS time window; and sending the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

16. An integrated circuit for controlling a process of a user equipment UE, the process include: receiving a configuration of a PoSS time window for monitoring a power saving signal PoSS and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether the UE starts monitoring the PDCCH in the DRX ON period; and determining the PoSS time window based on the configuration, and monitoring the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

17. An integrated circuit, controlling a process of scheduling a node, the process include: determining a configuration of a PoSS time window for monitoring a power saving signal PoSS by a user equipment and before a discontinuous reception DRX ON period for monitoring a physical downlink control channel PDCCH, wherein the PoSS indicates whether to start monitoring the PDCCH in the DRX ON period; Sending the configuration of the PoSS time window; and sending the PoSS within the PoSS time window, The PoSS time window ends at the beginning of the DRX ON period.

Images