User equipment, scheduling node, method for user equipment, and method for scheduling node

Abstract

The present disclosure relates to a communication device, a base station, and corresponding methods for the communication device and the base station. More specifically, the base station sends (S930) and the communication device receives (S1030) downlink control information DCI signaling. The DCI signaling includes an indication related to the sleep behavior of the secondary cell (Scell). The Scell ​​is configured with multiple bandwidth parts (BWPs), and the multiple BWPs include a sleep BWP and one or more normal BWPs. If the indication indicates a transition from sleep behavior to non-sleep behavior, a target BWP for performing the non-sleep behavior is determined (S1060). Specifically, the determination of the target BWP is performed based on at least one of the following: a priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

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] Currently, 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 "New Radio" (NR) radio access technology (RAT) operating 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 and NR, further improvements and options may facilitate efficient operation of the communication system as well as the specific devices belonging to the system. Summary of the Invention

[0004] One non-limiting and exemplary embodiment facilitates providing efficient determination of a BWP for performing non-sleep-like behavior in a wireless communication system.

[0005] In an embodiment, the technology disclosed herein features an apparatus (e.g., user equipment (UE)). The apparatus includes a transceiver that receives downlink control information (DCI) signaling. The apparatus also includes circuitry that obtains an indication related to sleep behavior of a secondary cell (Scell) from the DCI signaling, wherein the Scell ​​is configured with multiple bandwidth parts (BWPs), the multiple BWPs including a sleep BWP and one or more normal BWPs; and if the indication indicates a transition from sleep behavior to non-sleep behavior, determines a target BWP for performing the non-sleep behavior. Specifically, the determination of the target BWP is performed based on at least one of the following: a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[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 description and drawings. Benefits and / or advantages may be achieved individually by various embodiments and features of the description and drawings, and the various embodiments and features do not need to be fully provided in order to achieve one or more of such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0012] Figure 4 is a schematic diagram illustrating 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 is a block diagram illustrating an exemplary functional structure of a network node and a user equipment;

[0015] Figure 7 It is shown that it can be included in Figure 6 A block diagram of an exemplary functional structure of a PDCCH generation circuit in an exemplary scheduling node;

[0016] Figure 8 It is shown that it can be included in Figure 6 A block diagram of an exemplary functional structure of a PDCCH monitoring circuit in an exemplary user equipment of FIG. 1 ; and

[0017] Figure 9 is a flow chart illustrating exemplary steps performed by a network node and exemplary steps performed by a user equipment.

[0018] Specific implementation method

[0019] 5G NR system architecture and protocol stack

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

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

[0022] The user plane protocol stack for NR (see, for example, 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol, see Section 6.4 of TS 38.300), the RLC (Radio Link Control, see Section 6.3 of TS 38.300), and the MAC (Medium Access Control, see Section 6.2 of TS 38.300) sublayers, which terminate in the gNB on the network side. Furthermore, a new access stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced above PDCP (see, for example, subclause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, for example, subclause 4.4.2 of TS 38.300). An overview of Layer 2 functionality is provided in subclause 6 of TS 38.300. The functions 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.

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

[0024] 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, the physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel), and PUCCH (Physical Uplink Control Channel) for the uplink, and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel), and PBCH (Physical Broadcast Channel) for the downlink.

[0025] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), which have diverse requirements in terms of data rate, latency and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user-experienced data rates that are three times higher than those provided by 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 respectively) and high reliability (1-10 times within 1ms). -5 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 for low-cost devices (15 years).

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

[0027] 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.7.0).

[0028] Compared to the LTE parameter set (subcarrier spacing and symbol length), NR supports multiple different types of subcarrier spacing marked by the parameter μ (in LTE, there is only a subcarrier spacing of 15kHz, corresponding to μ=0 in NR). The types of NR parameter sets are summarized in 3GPP TS38.211v15.7.0.

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

[0030] Figure 2 The diagram shows the functional division between NG-RAN and 5GC. The NG-RAN logical node is the gNB or ng-eNB. The 5GC has the logical nodes AMF, UPF, and SMF.

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

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

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

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

[0035] - Routing of user plane data towards the UPF;

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

[0037] -Connection establishment and release;

[0038] - Scheduling and transmission of paging messages;

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

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

[0041] - Transport level packet marking in uplink;

[0042] -Session management;

[0043] - Network slicing support;

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

[0045] -Support UE in RRC_INACTIVE state;

[0046] -NAS message distribution function;

[0047] - Radio access network sharing;

[0048] -Dual connectivity;

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

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

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

[0052] -NAS signaling security;

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

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

[0055] - 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 for interconnection to data networks;

[0066] -Packet routing & forwarding;

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

[0068] -Business usage report;

[0069] - Uplink classifier that supports routing traffic to the data network;

[0070] -Support branch points for multi-homed PDU sessions;

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

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

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

[0074] Finally, the Session Management Function (SMF) hosts the following key functions:

[0075] -Session management;

[0076] -UE IP address allocation and management;

[0077] -Selection and control of UP function;

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

[0079] -Control some policy enforcement and QoS;

[0080] - Downlink data notification.

[0081] RRC connection establishment and reconfiguration process

[0082] 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).

[0083] RRC is the 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) and sending it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security with the UE by sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. The gNB then performs reconfiguration to establish Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB) by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete message from the UE in response. For signaling-only connections, the steps related to RRCReconfiguration are skipped because SRB2 and DRB are not established. Finally, the gNB notifies the AMF that the setup procedure is complete with the Initial Context Setup Response (INITIALCONTEXT SETUP RESPONSE).

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

[0085] IMT usage scenarios in 2020 and beyond

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

[0087] 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, remote medical surgery, distribution automation in smart grids, transportation safety, etc. The ultra-reliability of URLLC will be supported by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, the key requirements include a target user plane latency of 0.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.

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

[0089] In addition, the technical enhancements targeted by NR URLLC are aimed at latency improvement and reliability improvement. The 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 later transmission. Preemption is applicable independently of the specific service type. For example, a transmission of service type A (URLLC) can be preempted by a transmission of service type B (such as eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table with a target BLER of 1E-5.

[0090] The mMTC (Massive Machine Type Communication) use case is characterized by a very large number of connected devices, often sending relatively small amounts of non-latency-sensitive data. This requires low-cost devices with very long battery life. From an NR perspective, utilizing very narrow bandwidth segments is a possible solution, which, from the UE's perspective, can save power and extend battery life.

[0091] As mentioned above, the scope of reliability in NR is expected to become even broader. High or ultra-reliability is a key requirement for all scenarios, and is particularly necessary for URLLC and mMTC. From both a radio and network perspective, several mechanisms can be considered to improve reliability. Generally, 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 in the frequency, time, and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0092] For NR URLLC, further use cases have been identified with more stringent requirements, such as factory automation, transportation and power distribution. The more stringent requirements are higher reliability (up to 10 -6 level), 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, specifically a target user plane latency of 0.5 ms, depending on the use case.

[0093] In addition, for NR URLLC, several technical enhancements from a physical layer perspective have been identified. Among these are PDCCH enhancements related to compact DCI, PDCCH (Physical Downlink Control Channel) repetition, and 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 slot (a slot including fourteen symbols).

[0094] QoS control

[0095] The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows that require a guaranteed stream bit rate (GBR QoS flows) and QoS flows that do not require a guaranteed stream bit rate (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest granularity of QoS differentiation within 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) along with the PDU Session and may subsequently configure additional DRBs for the QoS flows of that PDU Session (when to do so depends on the NG-RAN), e.g. as described above with reference to Figure 3 As shown in Figure 2, NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the 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) (e.g., an external application server hosting 5G services) described in the example interacts with the 3GPP core network to provide services, such as supporting the impact of applications on traffic routing, accessing the network exposure function (NEF), or interacting with the policy framework for policy control (see Policy Control Function (PCF)) for example, QoS control. Based on the operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with relevant network functions. Application functions that are not allowed by the operator to directly access network functions interact with relevant network functions using the external exposure framework via the NEF.

[0098] Figure 5 Other functional units of the 5G architecture are 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 a 5G architecture) is provided, which includes a transmitter that sends a request including QoS requirements for at least one of URLLC, eMMB, and mMTC services to at least one function of a 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements; and a control circuit that uses the established PDU session to perform the service.

[0100] Terminals and base stations

[0101] In LTE and NR, a terminal or user terminal or user equipment is referred to as user equipment (UE). This can be a mobile device or communication device such as a wireless phone, smartphone, tablet computer, or USB (Universal Serial Bus) stick that functions as a user equipment. However, the term mobile device is not limited to this; generally, a relay can also have the functions of such a mobile device, and a mobile device can also function as a relay.

[0102] 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 or scheduling node that provides wireless access to a terminal. The communication between the terminal and the base station is generally standardized. In LTE and NR, the radio interface protocol stack comprises a physical layer, a medium access layer (MAC) and higher layers. In the control plane, a higher layer protocol, the 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, etc., measurements, and other functions. The term used in LTE is eNB (or eNodeB), while the term currently used in 5G NR is gNB.

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

[0104] Logical channels are different types of data transmission services provided by the MAC. Each logical channel type is defined by the type of information it transmits. Logical channels are divided into two groups: control channels and traffic channels. Control channels are used only for the transmission of control plane information. Traffic channels are used only for the transmission of user plane information.

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

[0106] Since the present disclosure involves scheduling, both scheduled devices (typically communication devices / transceiver devices) and scheduling devices (typically network nodes) participate. The present invention also provides a system including scheduled and scheduling devices, and corresponding methods and programs.

[0107] Hereinafter, a UE, a base station, and procedures will be described for a new radio access technology envisioned for 5G mobile communication systems, but which may also be used in LTE mobile communication systems. Various implementations and variations will also be described. The following disclosure is motivated by and may, for example, be based at least in part on the discussions and findings described above.

[0108] Generally, it should be noted that many assumptions have been made herein in order to be able to explain the basic principles of the present disclosure in a clear and understandable manner. However, these assumptions should be understood as examples made herein for illustrative purposes only and should not limit the scope of the present disclosure.

[0109] In addition, some of the terms used below, such as processes, entities, and layers, are closely related to terms used in LTE / LTE-A systems or in the current 3GPP5G standardization, even though the specific terms used in the context of new radio access technologies for the next 3GPP 5G communication system have not yet been fully determined or may ultimately change. Therefore, the terms may change in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art will appreciate that the embodiments and their scope of protection should not be limited to the specific terms used exemplarily herein due to the lack of updated or ultimately agreed terms, but should be understood more broadly based on the functions and concepts that form the basis of the functions and principles of the present disclosure.

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

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

[0112] Downlink control channel monitoring, PDCCH, DCI

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

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

[0115] Paging message monitoring function,

[0116] System information acquisition function,

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

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

[0119] Random access response reception of the random access function,

[0120] Packet Data Convergence Protocol (PDCP) layer reordering function.

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

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

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

[0124] Each of these functions serves a specific purpose for PDCCH monitoring and therefore begins and ends as described. PDCCH monitoring is typically controlled based on at least one timer operated by the UE. The timer has the purpose of controlling PDCCH monitoring, for example, to limit the maximum amount of time a UE monitors PDCCH. For example, a UE may not need to monitor PDCCH indefinitely, but may stop monitoring after a period of time to save power.

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

[0126] Physical Resource Block

[0127] In general, the term "physical resource block" (PRB) refers to the smallest allocatable unit of resources that can be used for (user) data transmission. In LTE and NR, a PRB has a predetermined number of contiguous subcarriers in the frequency domain (e.g., 12) and a predetermined number of symbols in the time domain (e.g., 14 OFDM symbols in LTE).

[0128] Cell type - primary cell, secondary cell, service cell

[0129] The term "cell" refers to a component carrier (CC) on which allocable resources (such as time-frequency-space resources) are located. A terminal can use more carriers, for example, to increase the amount of available resources. These CCs may be referred to as cells.

[0130] A primary cell (Pcell) operates on a primary frequency, which is the frequency on which the UE performs an initial connection establishment procedure and / or initiates a connection re-establishment procedure. The Pcell may be a cell explicitly indicated during a handover procedure.

[0131] A secondary cell (Scell), operating on a secondary frequency, can be configured once an RRC connection is established and can be used to provide additional radio resources.

[0132] For a UE without carrier aggregation (CA) configured in RRC_CONNECTED, there is only one serving cell, the primary cell. For a UE with CA configured in RRC_CONNECTED, the term "serving cell" refers to the primary cell and all secondary cells. In other words, the serving cell is the cell through which the UE is configured to send and / or receive data.

[0133] Bandwidth Part (BWP)

[0134] Typically, for each cell (eg, serving cell), multiple BWPs may be configured (eg, through RRC signaling).

[0135] In NR, a BWP consists of a set of contiguous PRBs. The bandwidth (BW) of a BWP cannot exceed the component carrier (CC) BW configured for the UE and must be at least as large as one synchronization signal (SS) block BW, but a BWP may or may not contain an SS block. Each BWP is associated with a specific parameter set, namely the subcarrier spacing (SCS) and cyclic prefix (CP) type. Therefore, the BWP is also the component that reconfigures the UE with a certain parameter set. For each cell, multiple BWPs can be configured for the UE via radio resource control (RRC) signaling, and these BWPs can overlap in frequency. The granularity of BW configuration is one PRB. For each serving cell, DL and UL BWPs are configured separately and independently for paired spectrum, and up to four BWPs can be configured for each of the DL and UL. For unpaired spectrum, the DL BWP and UL BWP are jointly configured as a pair, and up to four pairs can be configured. Up to four UL BWPs can also be configured for the supplementary UL (SUL). Each configured DL BWP includes at least one control resource set (CORESET) with a UE-specific search space (USS). The USS is a search space for the UE to monitor for possible reception of control information destined for the UE (e.g., a UE-specific PDCCH carrying DCI).

[0136] Similar to LTE, the search space is a set of candidate resources that the UE monitors for PDCCH. Monitoring includes, for example, blind detection and decoding of PDCCH in the candidate resources. The PDCCH addressed to the UE is provided, for example, by a cyclic redundancy check (CRC) mask that depends on the UE identity. For example, in LTE or NR, the UE identity can be a temporary identity assigned to the UE by the network, such as a radio network temporary identifier RNTI. The RNTI can be used to scramble the CRC. If the candidate resource carries a PDCCH addressed to the UE, the UE will be able to identify the PDCCH addressed to the UE and successfully decode the DCI, which means that the CRC has not failed.

[0137] In the primary carrier, at least one configured DL BWP includes a CORESET with a Common Search Space (CSS). The CSS is a search space used by the UE to monitor for possible reception of control information common to all UEs or destined for a specific UE. If the CORESET of the active DL BWP is not configured with a CSS, the UE does not need to monitor it. Note that the UE is expected to receive and transmit only within the frequency range configured for the active BWP with the associated parameter set. However, there are exceptions; the UE may perform Radio Resource Management (RRM) measurements or transmit Sounding Reference Signals (SRS) outside of its active BWP via measurement gaps. The BWP also serves as a tool for switching the UE's operating parameter set. The parameter set configured for the DL BWP is at least for the Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), and the corresponding Demodulation RS (DMRS). Similarly, the parameter set configured for the UL BWP is at least for the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), and the corresponding DMRS. On the other hand, it is noted that, at least in early releases of NR, the configuration of parameter sets is restricted. That is, the same parameter set should be used within the same PUCCH group including DL and UL.

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

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

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

[0141] Activation / deactivation of BWP

[0142] At a given time, (only) one configured BWP for a cell can be active, which is also referred to as the (currently) active BWP for the cell. Note that in this disclosure, the term "currently active" BWP refers to the BWP that was active when a DCI including a dormant handover indication (described below) was received. In other words, the currently active BWP can be the BWP that was active when determining the target BWP and / or when determining the priority of the BWP (also described below).

[0143] If a cell has an active BWP, it is also referred to as an active / activated cell. Typically, one or more cells can be active simultaneously. For example, a UE may have an active PCell and one or more active Scells. Typically, a UE is not expected to receive PDSCH, PDCCH, CSI-RS, or TRS outside of an active BWP. Therefore, a UE does not report CSI for inactive BWPs.

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

[0145] In NR, BWP activation / deactivation can be performed via dedicated RRC signaling or DCI signaling. While faster than MAC Control Element (CE)-based activation / deactivation, the DCI-based mechanism requires additional considerations for error handling, i.e., situations where the UE fails to decode the DCI containing the BWP activation / deactivation command. To aid recovery from such DCI loss situations, activation / deactivation of the DL BWP (or activation / deactivation of a DL / UL BWP pair for unpaired spectrum) via a timer is also supported. With this mechanism, if a UE is not scheduled within a certain amount of time, i.e., the timer expires, the UE switches its active DL BWP (or DL / UL BWP pair) to a default BWP. During initial access, there is an initial active BWP for the UE until the UE is explicitly configured with a BWP during or after RRC connection establishment. Unless otherwise configured, the initial active BWP is the default BWP. In Release 15, there is at most one active DL BWP and at most one active UL BWP (per cell) for a UE. When switching the active BWP of the UE, HARQ retransmission across different BWPs is supported. However, the present disclosure is not limited thereto. Typically, for each cell, there may be more than one activated BWP.

[0146] Sleep / non-sleep behavior

[0147] 3GPP RAN1 defines sleep-like and non-sleep-like behaviors to support UE power conservation and efficient and low-latency serving cell configuration / activation / establishment. Note that in this disclosure, the terms "sleep behavior" and "sleep-like behavior" are used interchangeably. Similarly, the terms "non-sleep behavior" and "non-sleep-like behavior" are used interchangeably.

[0148] More specifically, sleep-like behavior means that in an activated Scell, the UE does not monitor the PDCCH and only reports periodic CSI as configured. Non-sleep-like behavior means that in an activated Scell, the UE needs to monitor the PDCCH and also report periodic CSI. Typically, a UE can perform sleep-like behavior in one (activated) Scell ​​and non-sleep-like behavior in another (activated) Scell. The UE can then periodically report CSI for both Scells (for any BWP configured for the Scell), but only monitor the PDCCH in the activated BWP of the Scell ​​for which it performs non-sleep behavior.

[0149] The configured BWPs of a cell may include a normal BWP, which may be a configured BWP other than a sleep BWP and the sleep BWP. In other words, generally, one or more configured BWPs may be sleep BWPs, and one or more BWPs may be normal BWPs. Here, a sleep BWP is a BWP for which the UE can perform sleep-like behavior.

[0150] More specifically, when a UE performs a sleep-like behavior on a cell, only the sleep BWP in the BWP configured for that cell can be active, while the normal BWP cannot be active. Therefore, because the UE performs a sleep-like behavior on the active sleep BWP, the UE does not monitor the PDCCH in the sleep BWP. Because other configured BWPs are inactive, the UE also does not monitor the PDCCH in these other BWPs. In other words, the UE does not monitor the PDCCH in the cell for which it performs a sleep-like behavior. However, the UE can still report CSI for the active sleep BWP of the sleep cell.

[0151] On the other hand, when the UE performs non-dormant class behavior on an (activated) cell, any BWP configured for the cell may be activated and perform non-dormant class behavior on the active BWP. In other words, when performing non-dormant class behavior on a cell, the UE may monitor the PDCCH in the active BWP, which may be any configured BWP (dormant or normal) and report the CSI of the active BWP.

[0152] Typically, a single dormant BWP may be configured for each cell. However, the present disclosure is not limited thereto. Typically, one or more dormant BWPs may also be configured for each cell. Specifically, one cell may have only one (single) configured dormant BWP, while another cell may have more than one configured dormant BWP. Furthermore, there may be cells with zero configured dormant BWPs.

[0153] Switching between hibernation and non-hibernation behavior

[0154] An L1 (physical layer)-based Scell ​​dormancy indication can be sent on the primary cell (e.g., via DCI) during active time. More specifically, an explicit information field in the DCI indicates switching to / from the dormant BWP configured for the Scell. For example, the PDCCH can schedule data for the primary cell (Pcell) and also indicate the dormancy of one or more Scells. However, the PDCCH can also indicate the dormancy of one or more Scells without scheduling data. It is also possible to indicate to the UE (e.g., via DCI) whether the PDCCH with the dormancy indication schedules data for the Pcell. In general, the BWP framework can be used for behavior indication.

[0155] For a particular Scell, the sleep BWP can be a relatively narrower BWP than other configured BWPs, allowing the UE to perform sleep behavior. This allows the UE to save more power. When traffic arrives, the UE can switch to other BWPs as needed for small packet traffic or larger packet traffic to achieve higher throughput. On the other hand, the sleep BWP can also be a relatively wider BWP than other configured BWPs. This can be a trade-off between saving power by only measuring / reporting CSI without monitoring PDCCH and preparing for high-throughput traffic. When traffic with large data packets and high throughput and latency requirements arrives, the UE can quickly switch to another wide BWP to start data transmission by using the previous wideband CSI report.

[0156] For example, for each Scell ​​or Scell ​​group, the sleep indication can be a one-bit field (e.g., a flag) in the DCI. The flag can then be set to "0" and "1" by the network node to indicate sleep and non-sleep behaviors, respectively (or vice versa). In other words, each value of the bit field can be associated with a different one of the sleep and non-sleep behaviors and thus indicate a different one of the sleep and non-sleep behaviors. Alternatively, for example, the flag can also be used as a switching flag. One of its values ​​(e.g., "1") can then indicate switching the sleep behavior, while the other value (e.g., "0") can be used to indicate not switching the sleep behavior.

[0157] Generally, a UE may receive, for example, an indication related to sleep and / or non-sleep behavior via DCI, which is referred to herein as a "sleep indication," a "Scell ​​sleep indication," or the like. The sleep indication related to / associated with the sleep behavior of one or more (active) cells (e.g., a single cell or a corresponding cell group) may indicate a switch / conversion from sleep to non-sleep behavior, or a switch from non-sleep to sleep behavior, in the relevant cell. Generally, the sleep indication may also indicate that the sleep behavior in the activated cell has not been switched / changed. A sleep indication indicating a change / switch in the sleep behavior of one or more cells is also referred to herein as a "sleep switching indication."

[0158] As just mentioned, the sleep indication relates to the sleep behavior of one or more cells. The cell or cell group may be configured / indicated by RRC, for example. In other words, before receiving the DCI including the sleep indication, the UE may receive an indication via RRC indicating the cell or cell group to which one or more sleep indications are applied. For example, there may be a cell group of one or more cells that can be configured and reconfigured by RRC, and each sleep indication may be associated with the cell group configured when the DCI including the corresponding sleep indication is received. Alternatively, the sleep indication may be defined or configured for all cells configured with sleep and non-sleep class behavior switching.

[0159] Typically, the Scell ​​sleep indication may be received in the DCI of the Pcell. However, the present disclosure is not limited thereto, and the sleep indication may be received, for example, in the DCI of the Scell. In other words, the sleep indication may typically be received in the DCI of any cell in the UE's serving cell.

[0160] Typically, if a UE receives an indication to switch its sleep behavior in a cell, it can change its active BWP for that cell, also referred to herein as the target BWP. In other words, the target BWP is the BWP of the cell that becomes active after the UE has performed the transition indicated by the sleep indication. In other words, after receiving an indication to change its sleep behavior, the UE will perform the indicated sleep behavior in the target BWP. In other words, when performing the transition to the sleep behavior indicated by the sleep indication, the target BWP becomes the active BWP. Typically, the target BWP can be different from the currently active BWP (e.g., the BWP that was active when the sleep indication was received) or can be the currently active BWP. Note that if the sleep indication is associated with more than one cell, there may be a corresponding target BWP for each of those cells. Specifically, if the UE receives an indication to switch from sleep to non-sleep, then after switching to the target BWP, the UE should perform non-sleep-like behavior (PDCCH monitoring and CSI reporting) in the target BWP.

[0161] For example, assume that a dormant BWP and multiple normal BWPs are configured for a Scell. If, for each cell or cell group, L1 signaling (dormancy indication) indicates a transition from non-dormant to dormant, the UE behavior is clear: the active BWP should be switched to the dormant BWP. In other words, the dormant BWP becomes the target BWP, the dormant BWP becomes the active BWP, and the UE performs dormant-like behavior in the dormant BWP.

[0162] However, if L1 signaling indicates a transition from dormant to non-dormant behavior, the dormant BWP or any one of multiple normal BWPs may be the target BWP for performing non-dormant-like behavior. In other words, the UE behavior of switching to which target BWP may have to be defined.

[0163] However, specifically, when the DCI including the L1 signaling also schedules data, the number of L1 sleep indication bits may be limited. For example, in NR, the upper limit (also expressed as X2) of the number of sleep indication bits during the active time may be 5 (X2=5).

[0164] To address these issues, the present disclosure provides various embodiments that facilitate determining a target BWP without requiring explicit signaling via DCI.

[0165] An exemplary user equipment UE according to an embodiment Figure 6 is shown on the right side of . According to this embodiment, a UE 660 is provided. The UE includes a transceiver 670 that receives downlink control information DCI signaling (e.g., on a primary cell (Pcell)). The UE also includes a circuit 680 that obtains an indication related to the sleep behavior of a secondary cell (Scell) from the DCI signaling, wherein the Scell ​​is configured with multiple bandwidth parts (BWPs) (e.g., configured with four BWPs), the multiple BWPs including a sleep BWP and one or more normal BWPs. If the indication indicates a transition from sleep behavior to non-sleep behavior, the circuit 680 determines a target BWP for performing the non-sleep behavior based on at least one of the following: a priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0166] Circuit 680 can implement more functions than the above-mentioned obtaining sleep indication and determining target BWP. Therefore, circuit 680 is considered to include PDCCH monitoring circuit 685, which is configured to perform the obtaining and determining. This configuration can be provided by hardware adaptation and / or software.

[0167] Figure 8 FIG3 illustrates an exemplary functional structure of the PDCCH monitoring circuit 685. Specifically, the PDCCH monitoring circuit 685 may include a sleep monitoring circuit 836 and a target BWP determination circuit 837. The sleep monitoring circuit 836 may obtain a sleep indication from the DCI / PDCCH and accordingly set the sleep behavior in the cell. The sleep monitoring circuit 836 may thus activate / deactivate PDCCH monitoring by the PDCCH monitoring circuit 685 in cells where the DCI indicates non-sleep / sleep behavior. The BWP determination circuit 837 is configured to determine the corresponding target BWP when the sleep indication obtained by the sleep monitoring circuit 836 indicates a transition from sleep behavior to non-sleep behavior for one or more Scells.

[0168] Note that the PDCCH monitoring circuit 685 can implement more functions, as it can, for example, determine the resources for sending / receiving data. The processing circuit 680 can, for example, further control the transceiver 670 to receive the PDDCH / DCI and receive or transmit data on the resources indicated in the PDCCH / DCI.

[0169] Specifically, if the sleep indication indicates a switch from sleep behavior to non-sleep behavior, the circuit 680 (specifically, the sleep monitoring circuit 836) may switch from sleep behavior to non-sleep behavior for the Scell ​​and perform the non-sleep behavior in the determined target BWP. Specifically, if an indication is received to switch the sleep behavior to non-sleep behavior for the Scell, the circuit may control the transceiver 670 to monitor the PDCCH in the Scell.

[0170] According to another exemplary embodiment, a network node 610 ( Figure 7 ). The network node includes a transceiver 620 that transmits downlink control information (DCI) signaling addressed to a user equipment. The DCI signaling includes an indication related to the sleep behavior of a secondary cell (Scell) of the UE. The Scell ​​is configured with multiple bandwidth parts, the bandwidth parts including a sleep BWP and one or more normal BWPs. The network also includes a circuit 630. If the indication indicates a transition from sleep behavior to non-sleep behavior, the circuit 630 determines a target BWP for performing the non-sleep behavior. The circuit 630 may determine the target BWP based on at least one of the following: a priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0171] Scheduling device 610 may further include allocation circuitry as part of circuitry 630 that performs scheduling of one or more UEs. As a result of the scheduling, circuitry 630 may generate a time domain resource allocation and corresponding DCI signaling indicating the resource allocation. Processing circuitry 630 may then control transceiver 620 to transmit DCI and receive or transmit data on the resources indicated in the generated PDCCH / DCI.

[0172] Figure 9 FIG2 shows an exemplary functional structure of the PDCCH generation circuit 635. Specifically, the PDCCH generation circuit 635 may include a sleep determination circuit 736 and a target BWP determination circuit 737. The PDCCH generation circuit 635 may further perform scheduling, such as collecting measurements from one or more UEs and allocating resources to the corresponding UEs based on these measurements, requests from the UEs, and / or availability of their resources. The PDCCH generation circuit 635 may then generate DCI including the resource allocation and the associated DCI based on the scheduling results for the corresponding one or more UEs.

[0173] The dormancy determination circuit 736 may determine the dormancy behavior that the UE should perform for one or more of its cells. The PDCCH generation circuit 635 may then include a corresponding dormancy indication in a DCI addressed to the UE, indicating the result of the dormancy determination performed by the dormancy determination circuit 736.

[0174] The target BWP determination circuit 737 is configured to determine the corresponding target BWP when the sleep determination circuit 736 determines that the UE will transition from sleep behavior to non-sleep behavior for one or more Scells. Note that the target BWP determination circuit 737 may determine the target BWP for a cell before the sleep determination circuit 736 determines the sleep behavior for the cell. In practice, the sleep determination circuit 736 may consider the target BWP of a cell or cell group to determine the sleep behavior for that cell or cell group.

[0175] from Figure 6 It can also be seen in FIG6 that UE 660 and scheduling node 610 can form a communication system, that is, they can communicate through channel 650.

[0176] Typically, for an activated Scell, a UE that is instructed to transition from a sleep-like behavior to a non-sleep-like behavior may determine a target BWP based on one or a combination of: a priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0177] Note that since the UE and the network node are part of the communication system, and in order to use the activated BWP for which the UE will perform non-dormant behavior, the UE and the network node must know / determine the (same) target BWP. Therefore, generally, the UE and the network node can independently determine the target BWP using methods that at least produce the same results (e.g., target BWP determination circuit 737 and target BWP determination circuit 837 can operate substantially similarly or even identically). In other words, the determination methods according to the present disclosure can generally be performed on the UE and / or base station (network node) side. Alternatively, one of the two communicating entities can determine the target BWP and send a corresponding indication to the other. For example, the network node (e.g., target BWP determination circuit 737) can determine the target BWP for a Scell ​​and send a corresponding indication to the UE, which then determines the target BWP for the Scell ​​based on / in accordance with the indication (e.g., BWP determination circuit 837). In other words, in the present disclosure, when the UE determines the target BWP using a specific method, the base station can determine the target BWP in the same or similar manner. Of course, this may not apply in cases where the UE determines the target BWP based on DCI and / or RRC indications received from the base station. In this case, the base station may determine the target BWP and generate a corresponding indication taking into account other UEs, available resources, quality of service, requests from the UE, received channel state information, traffic load, battery status of the UE, etc.

[0178] Typically, the target BWP may be a predefined or preconfigured BWP. Therefore, typically, for an active Scell, a UE instructed to transfer / switch to a non-dormant behavior may switch to a predefined / configured BWP to perform the non-dormant behavior, and / or may select a predefined / configured BWP as the target BWP to support the non-dormant behavior.

[0179] In some embodiments, the predefined / configured BWP is a normal BWP. That is, in some embodiments, the target BWP is a normal BWP, or, if more than one normal BWP is configured for a Scell, the target is one of the normal BWPs. For example, the predefined BWP (i.e., the target BWP) may be defined by a standard. The standard may directly define the target BWP (e.g., the index of the target BWP). Alternatively, the standard may define a method for determining the BWP. For example, each BWP is associated with a corresponding index, and the BWP with the lowest or highest index may be defined as the target BWP (the lowest or highest of the configured BWP indices).

[0180] The pre-configured BWP can be configured by radio resource control (RRC) signaling. RRC signaling is semi-static signaling. Alternatively, to increase configurability, the target BWP can be explicitly indicated or configured by the base station, for example, via DCI.

[0181] Advantageously, in this embodiment, the UE does not have to perform calculations to determine the target BWP, and the base station (gNB) can configure the target normal BWP through implementation.

[0182] However, the present disclosure is not limited thereto. Typically, the predefined or preconfigured BWP may be the default BWP. Typically, the default may be configured as either a dormant or normal BWP. However, in some embodiments, the dormant BWP can only be configured and selected from BWPs other than the default BWP. That is, the default BWP in current NR specifications can only be configured as a normal BWP, not a dormant BWP. Therefore, for an active Scell, a UE instructed to transition to a non-dormant behavior may switch to the default BWP, which is the target BWP, to implement the non-dormant behavior.

[0183] Advantageously, the UE behavior is clearly defined, with only small regulatory impact, and no additional RRC parameters, thus preventing additional overhead.

[0184] Typically, the target BWP can be determined according to (or based on) the legacy BWP indicator field in the DCI. In other words, the UE can determine the target BWP for the Scell ​​by using the legacy BWP indicator field in the DCI that carries a sleep behavior indication, where the sleep behavior indication indicates a transition of the Scell ​​to a non-sleep-like behavior. Correspondingly, the base station can determine the target BWP and, when generating a DCI indicating a transition to a non-sleep-like behavior, set the legacy BWP indicator field in the DCI to indicate the determined target BWP. For example, the target BWP can be determined based on an index indicated by the legacy BWP indicator field.

[0185] Note that the Legacy BWP Indicator field is a field in a cell's DCI that the base station uses to indicate the BWP of the cell to the UE. For example, the Legacy BWP Indicator field can be used to indicate the BWP in which the resources scheduled in the DCI (or subsequent DCI for the cell) are located. The Legacy BWP Indicator field can be used to activate the indicated BWP and, therefore, can be used to deactivate the currently active BWP. The Legacy BWP Indicator field can indicate or correspond to an index. More specifically, the Legacy BWP Indicator field is a field present in DCI formats 0_1 and 1_1 in NR for BWP switching operations, such as defined in 3GPP TS 38.212.

[0186] Note that the legacy BWP indicator is not used in NR Release 15 for sleep indication or for indicating the target BWP when switching to non-sleep behavior. It is used to change the active BWP in a serving cell scheduled with data. More specifically, in NR Release 15, the legacy BWP indicator is a field included in the DCI (format 0_1 / 1_1) of a Pcell or Scell ​​that also schedules data for that Pcell / Scell, where it is used to indicate that the BWP is activated in that Pcell / Scell ​​and is receiving / transmitting the scheduled data therein.

[0187] However, in some implementations of the present invention, for a dormancy indication during active time, for each active Scell ​​configured to support dormancy behavior switching, the target BWP index for non-dormant behavior is determined based on the BWP indicator of the Pcell. More specifically, a dormancy switching indication may be received in the DCI of a cell (this may be a Pcell or Scell ​​for which the UE is performing non-dormant behavior) that also schedules data and includes a legacy BWP indicator field. The legacy BWP indicator field may then be used to determine the target BWP for one or more Scells associated with the dormancy switching indication.

[0188] However, the present disclosure is not limited thereto, as the sleep transition indication may also be received in the DCI of a non-sleep Scell ​​(referring to an Scell ​​in which the UE does not perform sleep-like behavior when receiving DCI). In this case, for example, the conventional BWP indicator field in the Scell ​​DCI may be used to determine the target BWP.

[0189] Typically, each configured BWP of a Scell ​​may be associated with or correspond to an index (eg, one-to-one correspondence). This association may be used to determine a target BWP using the index indicated by the legacy BWP indicator field.

[0190] For example, in an exemplary implementation, it is always determined that the target BWP is a BWP among the configured BWPs corresponding to the index indicated by the legacy BWP indicator field.

[0191] In another exemplary implementation, the target BWP may be determined to be a BWP in the configured BWP corresponding to the index indicated by the legacy BWP indicator field (only) if the index corresponds to a normal BWP, and if the index corresponds to a dormant BWP, the target BWP may be determined according to a predetermined or predefined method. In other words, the UE determines the target BWP based on the legacy BWP indicator only when the index in the received legacy BWP indicator does not refer to the current dormant BWP of the Scell. On the other hand, if the index in the received legacy BWP indicator refers to the current dormant BWP of the Scell, the UE determines the target BWP based on a predefined or preconfigured BWP, the most recently active normal BWP, the priority order of the configured BWPs, the priority order of the normal BWPs, and / or the dormant BWP, as described elsewhere in this disclosure.

[0192] Using the legacy BWP indicator field (or the index indicated by the legacy BWP indicator field to indicate the target BWP) has a small specification impact and prevents an increase in overhead when signaling the target BWP to the UE.

[0193] Typically, the target BWP can be determined by taking into account the activity of the configured normal and / or dormant BWPs. For example, according to another embodiment, the target BWP is the most recently active normal BWP among the normal BWPs configured for the corresponding cell of the UE. In other words, the UE (and the base station) can determine the target BWP as the most recently active BWP, which is a normal BWP, that is, not a dormant / sleeping BWP. More specifically, for an active Scell, a UE instructed to transition to non-dormant-type behavior can determine the target BWP as the most recently active BWP in which the UE performed non-dormant-type behavior. Determining the target BWP based on the most recent activity offers the advantage of minimal regulatory impact. In addition, no additional signaling is required from the base station to the UE to indicate the target BWP. This reduces overhead, thereby improving communication efficiency.

[0194] In some embodiments, the target BWP is determined to be a dormant BWP. In other words, the UE (and the base station) determines the target BWP from the dormant BWP. If more than one dormant BWP is configured for the Scell, the target BWP can be determined from all dormant BWPs, or, for example, from the currently active dormant BWP, which is the BWP for which the UE performs dormant-like behavior upon receiving a DCI with a dormant handover indication to determine the target BWP. For example, the target BWP can be a dormant BWP, in which case the UE will not switch to a different BWP, but instead will perform non-dormant-like behavior in the currently active dormant BWP.

[0195] As described above, in some embodiments, a target BWP is determined according to (or based on) a priority order. For a UE instructed to transition to a non-sleep-like behavior on an active Scell, the UE (e.g., processing circuit 680) determines the target BWP by calculating a priority order of BWPs (e.g., normal BWPs). Based on the priority order calculated by the UE, the UE selects a target BWP to support the non-sleep-like behavior.

[0196] Typically, this priority order may be the priority order of (all) configured BWPs, the priority order of normal BWPs, or the priority order of configured BWPs, e.g., except for the currently active dormant BWP. Without affecting the present invention, for the sake of clarity, only the priority order of normal BWPs is explicitly mentioned.

[0197] Typically, a priority order for BWPs can be a ranking of BWPs, a ranking of BWPs, or a sequence of BWPs, where each associated BWP appears exactly once. Within a priority order, each BWP can have or be associated with a priority, either explicitly or implicitly. Priority can be a value, and within a priority order, BWPs can be sorted based on the magnitude of the priority value. Therefore, a priority order can be constructed from rules that assign / associate (priority) values ​​to each BWP. Then, for each BWP, the corresponding priority order can be determined / calculated by calculating the priority of each BWP and sorting the BWPs based on the calculated priority.

[0198] In general, if two BWPs are associated with the same priority, the two BWPs may be ordered arbitrarily, or additional criteria or criteria may be defined to distinguish which BWP has a higher priority.

[0199] Note that in order to determine the target BWP according to the priority order, it may not be necessary to explicitly determine the priority order. For example, only the priorities of the BWPs may be determined, and the BWP with the highest priority may be selected.

[0200] Typically, the BWP with the highest priority (value) may be determined to be the target BWP. However, in some embodiments, other criteria are considered, and the BWP with the highest priority that meets these criteria is selected as the target BWP.

[0201] For example, in some implementations where a target BWP is determined based on a priority order, for each normal BWP, the priority of the normal BWP increases as the bandwidth overlap between the normal BWP and the sleep BWP increases. More specifically, if a BWP has more overlapping bandwidth with the currently active sleep BWP (than another BWP), it has a higher priority (than the other BWP). Thus, the target BWP is the normal BWP that has the highest bandwidth overlap (among the normal BWPs) with the currently active sleep BWP.

[0202] For example, if BWP#1 has a 10 MHz overlapping bandwidth with the currently dormant BWP, and BWP#2 has a 5 MHz overlapping bandwidth with the currently dormant BWP, the UE may, for example, determine that the priority of BWP#1 is 10, while the priority of BWP#2 is 5. Therefore, the UE selects BWP#1 as the target BWP for non-dormant class behavior. In general, the UE may therefore determine / calculate the overlap of a normal BWP with the currently active dormant BWP for each normal BWP, and select the normal BWP for which it has calculated the highest overlap as the target BWP.

[0203] Advantageously, this implementation enables the gNB to leverage previous CSI reports received from the UE for the currently active dormant BWP (when the UE performs dormant-like behavior in said BWP).

[0204] In another implementation of determining the target BWP based on a priority order, for each normal BWP, the priority of the normal BWP increases as the difference between the center frequency of the normal BWP and the center frequency of the dormant BWP decreases. More specifically, a BWP has a higher priority if its center frequency is closer to the center frequency of the currently dormant BWP. Generally, the UE may therefore determine / calculate the difference between the center frequency of the normal BWP and the center frequency of the currently active dormant BWP for each normal BWP and select the normal BWP for which it has calculated the smallest difference as the target BWP.

[0205] Advantageously, this implementation enables the gNB to leverage previous CSI reports received from the UE for the currently active dormant BWP (when the UE performs dormant-like behavior in said BWP).

[0206] According to another embodiment, a method for a UE is provided. The method includes the steps of receiving DCI signaling and obtaining an indication related to the sleep behavior of a Scell ​​from the DCI signaling. The Scell ​​is configured with multiple BWPs, and the multiple BWPs include a sleep BWP and one or more normal BWPs. If the indication indicates a transition from sleep behavior to non-sleep behavior, the method further includes the step of determining a target BWP for performing the non-sleep behavior. The target BWP is determined based on at least one of a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0207] According to another embodiment, a method for a network node is provided. The method includes the step of sending DCI signaling. The DCI signaling is addressed to a UE and includes an indication related to the sleep behavior of a Scell ​​of the UE. The Scell ​​is configured with multiple BWPs, including a sleep BWP and one or more normal BWPs. If the indication indicates a transition from sleep behavior to non-sleep behavior, the method also includes the step of determining a target BWP for performing the non-sleep behavior based on a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0208] Figure 9 The left side and the right side of respectively show exemplary methods for a base station and a UE according to the present disclosure.

[0209] In step S910, the base station determines the sleep behavior of the Scell ​​of the S910 UE. This determination may take into account other UEs, available resources, quality of service, requests from the UE, received channel state information, traffic load, battery status of the UE, etc. In the case where the UE is currently performing a sleep-type behavior on the Scell, the determination may further take into account an available target BWP (for example, in an implementation, the base station may select a target BWP and indicate the selected target BWP together with a sleep handover indication to the UE in the DCI) or a BWP that will become the target BWP (for example, in an implementation, the base station cannot indicate the sleep handover indication to the UE in the DCI).

[0210] In other words, if the UE is currently performing a sleep-like behavior on a Scell, the base station determines whether the UE should i) continue to perform the sleep-like behavior on the Scell ​​or ii) switch to a non-sleep behavior in the Scell. As part of this step, the base station may also determine a target BWP. On the other hand, if the UE is currently performing a non-sleep-like behavior on the Scell, the base station determines whether the UE should i) continue to perform the non-sleep-like behavior on the Scell ​​or ii) switch to a sleep-like behavior in the Scell. In other words, the base station determines whether to instruct the UE to switch the Scell's sleep behavior.

[0211] It should be noted that if more than one cell of the UE supports sleep-like behavior, the sleep behavior of more than one cell may be determined in this step. Specifically, advantageously, the determination is performed jointly for more than one cell.

[0212] like Figure 9 As shown, the base station can re-evaluate the dormancy behavior of the Scell. For example, the base station can periodically (re)determine whether to instruct the UE to switch the dormancy behavior. Alternatively or in addition, the (re)determination of the dormancy behavior of the Scell ​​can be triggered by an event, such as a request from the UE to send data or an increase / decrease in traffic associated with the UE.

[0213] Specifically, in step S920, the base station generates a PDCCH / DCI including a sleep indication based on the sleep behavior determined in step S910. The sleep indication indicates whether to switch or maintain the sleep behavior of the Scell ​​(S920). This DCI may include further control information and may or may not schedule data. The DCI may be generated for the PDCCH of the UE's Pcell or for another Scell ​​of the UE for which the UE is not currently performing sleep-like behavior.

[0214] In step S930, the base station sends the DCI generated in step S920 to the UE (S930). As mentioned above, the DCI can be sent in the Scell ​​or the Pcell.

[0215] In step S980, the base station sends data DCI in the PDCCH of the PCell or Scell. Note that this step can be omitted if there is no data to be sent to / received by the UE. If the Scell ​​has switched from sleep-like behavior to non-sleep-like behavior, the UE now also monitors the PDCCH of the Scell. Therefore, the base station can now also send DCI scheduling data in the PDCCH of the Scell.

[0216] In step S1010, the UE monitors the PDCCH of the Pcell (S1010). Figure 9 On the right side of FIG, it is assumed that the UE is currently performing a sleep-type behavior on the Scell.

[0217] In step S1030 , the UE receives DCI in the PDCCH of the Pcell and monitors the PDCCH of the Pcell at the same time, where the DCI includes a sleep indication related to the Scell.

[0218] In step S1040, the UE obtains a sleep indication from the DCI of the PDCCH of the PCell (S1040). The UE may then determine whether the sleep indication indicates a transition from sleep-like to non-sleep-like behavior for one or more cells. If the sleep indication does not indicate a transition, the UE continues to monitor only the PDCCH of the PCell. On the other hand, if the sleep indication indicates a switch to non-sleep-like behavior, the UE determines a target BWP for each Scell ​​involved in the sleep indication to implement the non-sleep-like behavior, as described elsewhere in this disclosure (S1060).

[0219] If there are one or more cells for which the UE is currently performing non-sleep-like behavior, the UE may also determine, for each of the one or more cells, whether the sleep indication indicates a transition from non-sleep-like to sleep-like behavior. If so, the sleep BWP of these Scells becomes the active BWP, and the UE begins performing sleep-like behavior on these Scells.

[0220] In step S1080 , the UE monitors the PDCCH in the Pcell and the Scell. More specifically, for each Scell, the UE monitors the PDCCH in the target BWP determined in step S1060 .

[0221] Note that all embodiments and implementations described in this disclosure apply not only to active time (C-DRX on duration), but also to outside active time, where the non-sleep indication is included in DCI format 3_0, which is called WUS (wake-up signal) or PoSS (power save signal / channel).

[0222] In other words, in some of the above embodiments, the sleep indication is carried by the DCI in the active time. For example, a DCI format that also schedules data can be used for this purpose. However, the present disclosure is not limited to this, and the sleep indication can also be included in the DCI that does not schedule data. For example, the sleep indication can be included in the DCI, which is a wake-up signal from a certain power-saving operation, such as from the above-mentioned discontinuous reception (DRX). DRX is a cycle of ON period and OFF period, in which the UE monitors the PDCCH for scheduling dispatch, and in the OFF period, the UE does not monitor the PDCCH for scheduling dispatch.

[0223] For example, for the ON duration when waking up from DRX OFF, as described above, the UE may determine the target BWP based on any one or more of the priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in DCI signaling, and a dormant BWP. Although the present invention is not limited to the above determination example, and generally, the target BWP may also be determined as the most recently active normal BWP, such determination may be less effective if the DRX OFF period is long.

[0224] For other situations, i.e., non-DRX operation or transitions during active time, the target BWP can be determined as the most recently active normal BWP. In this case (active time), determining the target BWP as the most recently active normal BWP can provide an effective means of initiating non-dormant behavior. For example, it can reduce the probability of needing to perform an active BWP change too quickly.

[0225] As described above, for sleep indication during active time, any of the above BWP determination methods may be used alone or in combination.

[0226] According to another implementation, a non-transitory computer-readable recording medium is provided, which stores a program that, when executed by one or more processors, causes the one or more processors to perform the steps of the method according to the present disclosure.

[0227] For example, embodiments of UE 660 and base station 610, and the functionality described herein with reference to UE 660 and base station 610, may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored on a computer-readable medium, or transmitted as one or more instructions or codes via a communication medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media such as data storage media, or communication media, including, for example, any medium that facilitates the transfer of a computer program from one place to another according to a communication protocol. In this manner, computer-readable media may generally correspond to (1) a tangible, non-transitory computer-readable storage medium, or (2) a communication medium such as a signal or carrier wave. A data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this disclosure. A computer program product may include a computer-readable medium.

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

[0229] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Thus, the term "processor" as used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Furthermore, in some aspects, the functionality described herein may be provided in dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Similarly, these techniques may be implemented entirely in one or more circuits or logic elements.

[0230] The techniques of this disclosure can be implemented in a wide variety of devices or apparatuses, including wireless handsets, integrated circuits (ICs), or sets of ICs (e.g., chipsets). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but they do not necessarily need to be implemented by different hardware units. Rather, as described above, the various units can be combined in a codec hardware unit in conjunction with appropriate software and / or firmware, or provided by a collection of interoperable hardware units (including one or more processors as described above).

[0231] According to a first embodiment, an apparatus (e.g., user equipment (UE)) is provided. The apparatus includes a transceiver that receives downlink control information (DCI) signaling. The apparatus also includes circuitry that obtains an indication related to sleep behavior of a secondary cell (Scell) from the DCI signaling, wherein the Scell ​​is configured with multiple bandwidth parts (BWPs), the multiple BWPs including a sleep BWP and one or more normal BWPs; and if the indication indicates a transition from sleep behavior to non-sleep behavior, determines a target BWP for performing the non-sleep behavior. Specifically, the determination of the target BWP is performed based on at least one of the following: a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0232] According to the second embodiment, in the apparatus of the first embodiment, the predefined or preconfigured BWP is: a BWP with a lowest index configured by radio resource control RRC signaling, a BWP with a highest index, and / or explicitly indicated by the base station.

[0233] According to a third embodiment, in the apparatus of the first embodiment or the second embodiment, the predefined or preconfigured BWP is a default BWP configured as a normal BWP.

[0234] According to a fourth embodiment, in the apparatus of the first embodiment, the circuit determines the target BWP based on an index indicated by the legacy BWP indicator field.

[0235] According to a fifth embodiment, in the apparatus of the fourth embodiment, if the index corresponds to the index of a normal BWP among one or more normal BWPs, the circuit (in operation) determines that the target BWP is the normal BWP; and, if the index corresponds to the index of a sleep BWP, the circuit determines that: the target BWP is the sleep BWP; or determines the target BWP according to a predetermined or predefined method.

[0236] According to a sixth embodiment, in the apparatus of the first embodiment, the circuit (in operation) determines that the target BWP is the most recently active normal BWP among the one or more normal BWPs.

[0237] According to a seventh embodiment, in the apparatus of the first embodiment, the circuit (in operation) determines that the target BWP is a dormant BWP.

[0238] According to the eighth embodiment, in the apparatus of the first embodiment, in the priority order, for each normal BWP, the priority of the normal BWP increases as the bandwidth overlap of the normal BWP and the sleep BWP increases.

[0239] According to the ninth embodiment, in the apparatus of the first embodiment, in the priority order, for each normal BWP, the priority of the normal BWP increases as the difference between the center frequency of the normal BWP and the center frequency of the sleep BWP decreases.

[0240] According to a tenth embodiment, in the apparatus of any one of the first to ninth embodiments, if the instruction indicates switching from the sleep behavior to the non-sleep behavior, the circuit switches the Scell ​​from the sleep behavior to the non-sleep behavior and performs the non-sleep behavior in the determined target BWP.

[0241] According to an eleventh embodiment, a method (e.g., a method for a user equipment (UE)) is provided. The method includes the following steps: receiving downlink control information (DCI) signaling; and obtaining, from the DCI signaling, an indication related to sleep behavior of a secondary cell (Scell), wherein the Scell ​​is configured with multiple bandwidth parts (BWPs), the multiple BWPs including a sleep BWP and one or more normal BWPs. The method also includes the step of determining a target BWP for performing the non-sleep behavior if the indication indicates a transition from sleep behavior to non-sleep behavior. Specifically, the determination is performed based on at least one of a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

[0242] According to a twelfth embodiment, a network node is provided. The network node includes a transceiver that transmits downlink control information (DCI) signaling addressed to a user equipment (UE), wherein the DCI signaling includes an indication related to a dormant behavior of a secondary cell (Scell) of the UE, wherein the Scell ​​is configured with multiple bandwidth parts (BWPs), the multiple BWPs including a dormant BWP and one or more normal BWPs. The network node includes circuitry that, if the indication indicates a transition from dormant behavior to non-dormant behavior, determines a target BWP for performing the non-dormant behavior based on at least one of the following: a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a dormant BWP.

[0243] According to a thirteenth embodiment, a method for a network node is provided. The method includes the steps of sending downlink control information (DCI) signaling addressed to a user equipment (UE), wherein the DCI signaling includes an indication related to a dormant behavior of a secondary cell (Scell) of the UE, wherein the Scell ​​is configured with multiple bandwidth parts (BWPs), the multiple BWPs including a dormant BWP and one or more normal BWPs. The method includes the steps of: if the indication indicates a transition from dormant behavior to non-dormant behavior, determining a target BWP for performing the non-dormant behavior based on at least one of the following: a priority order of the one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a dormant BWP.

[0244] According to a fourteenth embodiment, there is provided a non-transitory computer-readable recording medium storing a program which, when executed by one or more processors, causes the one or more processors to perform the steps of the method according to any one of the above-described eleventh or thirteenth embodiments.

[0245] Note that the steps executed by the above-mentioned circuits also constitute steps of the corresponding methods. These can also be implemented in a computer program stored on a non-transitory computer-readable recording medium.

[0246] The present disclosure relates to a communication device, a base station, and corresponding methods for the communication device and the base station. More specifically, the base station sends and the communication device receives downlink control information (DCI) signaling. The DCI signaling includes an indication related to the sleep behavior of a secondary cell (Scell). The Scell ​​is configured with multiple bandwidth parts (BWPs), and the multiple BWPs include a sleep BWP and one or more normal BWPs. If the indication indicates a transition from sleep behavior to non-sleep behavior, a target BWP for performing the non-sleep behavior is determined. Specifically, the determination of the target BWP is performed based on at least one of the following: a priority order of one or more normal BWPs, a predefined or preconfigured BWP, a legacy BWP indicator field in the DCI signaling, a most recently active normal BWP, and a sleep BWP.

Claims

1. A communication device, comprising: a transceiver configured to receive downlink control information (DCI) signaling, wherein the DCI signaling includes an indication related to a sleep behavior of a secondary cell (Scell), The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and circuitry, if the indication indicates a non-sleep behavior, the circuitry determining a target BWP for performing the non-sleep behavior based on a preconfigured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

2. The communication device according to claim 1, wherein The pre-configured BWP is configured by radio resource control RRC signaling.

3. The communication device according to claim 1 or 2, wherein: The preconfigured BWP is a default BWP configured as a normal BWP. The communication device according to claim 1 , wherein: If the indication indicates a sleep behavior, the sleep behavior is performed by using the sleep BWP. The communication device according to claim 1 , wherein: The DCI signaling is used for power saving operations outside the DRX active time.

6. A communication method, comprising: receiving downlink control information DCI signaling, wherein the DCI signaling includes an indication related to a sleep behavior of a secondary cell Scell, The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and If the indication indicates a non-sleep behavior, determining a target BWP for performing the non-sleep behavior according to a pre-configured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

7. The communication method according to claim 6, wherein: The pre-configured BWP is configured by radio resource control RRC signaling.

8. The communication method according to claim 6 or 7, wherein: The preconfigured BWP is a default BWP configured as a normal BWP.

9. The communication method according to claim 6, wherein: If the indication indicates a sleep behavior, the sleep behavior is performed by using the sleep BWP.

10. The communication method according to claim 6, wherein: The DCI signaling is used for power saving operations outside the DRX active time.

11. A network node, comprising: a transceiver that sends downlink control information (DCI) signaling in a target BWP, wherein the DCI signaling includes an indication related to a dormant behavior of a secondary cell (Scell), The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and circuitry, wherein if the indication indicates a non-sleep behavior, the circuitry determines a target BWP for performing the non-sleep behavior based on a preconfigured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

12. The network node according to claim 11, wherein: The pre-configured BWP is configured by radio resource control RRC signaling.

13. The network node according to claim 11 or 12, wherein: The preconfigured BWP is a default BWP configured as a normal BWP. The network node according to claim 11 , wherein: If the indication indicates a sleep behavior, the sleep behavior is performed by using the sleep BWP.

15. The network node according to claim 11, wherein: The DCI signaling is used for power saving operations outside the DRX active time.

16. A communication method, comprising: Sending downlink control information DCI signaling, wherein the DCI signaling includes an indication related to the sleep behavior of the secondary cell Scell, The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and If the indication indicates a non-sleep behavior, determining a target BWP for performing the non-sleep behavior according to a pre-configured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

17. The communication method according to claim 16, wherein: The pre-configured BWP is configured by radio resource control RRC signaling.

18. The communication method according to claim 16 or 17, wherein: The preconfigured BWP is a default BWP configured as a normal BWP.

19. The communication method according to claim 16, wherein: If the indication indicates a sleep behavior, the sleep behavior is performed by using the sleep BWP.

20. The communication method according to claim 16, wherein: The DCI signaling is used for power saving operations outside the DRX active time.

21. An integrated circuit comprising: The receiving circuit controls receiving downlink control information DCI signaling, wherein the DCI signaling includes an indication related to a sleep behavior of a secondary cell Scell, The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and Determine the circuit that controls If the indication indicates a non-sleep behavior, determining a target BWP for performing the non-sleep behavior according to a pre-configured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

22. An integrated circuit comprising: Transmitting circuit, which controls Sending downlink control information DCI signaling, wherein the DCI signaling includes an indication related to the sleep behavior of the secondary cell Scell, The Scell ​​is configured with a plurality of bandwidth parts BWP, wherein the plurality of BWPs include a dormant BWP and one or more normal BWPs; and Determine the circuit that controls If the indication indicates a non-sleep behavior, determining a target BWP for performing the non-sleep behavior according to a pre-configured BWP, wherein: If the DCI signaling is the first DCI signaling, the DCI signaling is received within an active time; and If the DCI signaling is second DCI signaling, the DCI signaling is received outside the active time.

Images