System and method for PDCCH skip and scheduling requests
By canceling/ignoring PDCCH skipping on cell groups when the SR is pending in 5G mobile communication system, the UL license delay problem caused by PDCCH skipping is solved, and the power consumption of the UE is reduced.
Patent Information
- Application Number
- CN202380028749.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-21
- Filing Date
- 2023-03-20
- Publication Date
- 2024-11-12
AI Technical Summary
In a 5G mobile communication system, after receiving the PDCCH skip indication, the UE triggers the schedule request (SR) for a buffer status report (BSR), beam failure recovery (BFR), or a consistent listen first and then talk (LBT) fault. UL grant is delayed due to skip duration and canceling/ignoring PDCCH skip on cell groups results in increased UE power consumption.
When the SR is pending, the UE cancels/ignors PDCCH skipping on all serving cells on the cell group, determines at least one serving cell and cancels it skips PDCCH monitoring by identifying whether the SR is triggered for the BSR.
Cancel/ignore PDCCH skip when the SR is pending, reducing power consumption of the UE and improving the response speed of UL licenses, avoiding delays.
Smart Images

Figure CN118947200A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a wireless communication system. In particular, the present disclosure relates to an apparatus, method and system for physical downlink control channel (PDCCH) monitoring. Background Art
[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave (millimeter wave) including 28 GHz and 39 GHz. In addition, the implementation of the sixth generation (6G) mobile communication technology (called a super 5G system) in the terahertz frequency band (e.g., 95 GHz to 3 THz frequency band) has been considered to achieve a transmission rate fifty times faster than that of the 5G mobile communication technology and an ultra-low latency of one tenth of that of the 5G mobile communication technology.
[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine type communication (mMTC), there has been ongoing standardization on beamforming and massive MIMO for mitigating radio wave path loss in mmWave and increasing radio wave transmission distance in mmWave, parameter sets supporting dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.
[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as V2X (Vehicle to Everything) for assisting driving decisions made by autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation intended to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable), and positioning.
[0005] In addition, there is ongoing standardization of air interface architecture / protocol aspects of technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also ongoing on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / services of mobile edge computing (MEC) for receiving services based on UE location.
[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and the integrated operation of connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., improving 5G performance and reducing complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
[0007] Furthermore, such developments in 5G mobile communication systems will serve as a foundation not only for the development of new waveforms that provide terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but also for the development of full-duplex technology that improves the frequency efficiency of 6G mobile communication technology and improves system networks, AI-based communication technology for achieving system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high-performance communication and computing resources.
[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art with respect to the present disclosure. Summary of the invention
[0009] Technical issues
[0010] If the UE has received a PDCCH skip indication and a scheduling request (SR) is triggered for a buffer status report (beam failure recovery, BSR), beam failure recovery (beam failure recovery, BFR) or consistent listen before talk (LBT) failure, and the SR is sent through PUCCH, the UL grant (scheduled by PDCCH) is delayed due to the skipping duration.
[0011] To overcome this problem, the UE cancels / ignores PDCCH skipping on all serving cells of the cell group where SR is pending, but this results in an increase in UE power consumption.
[0012] Solution to the problem
[0013] Aspects of the present disclosure at least address the above-mentioned problems and / or disadvantages, and at least provide the advantages described below. Therefore, one aspect of the present disclosure is to provide a communication method and system for integrating a fifth generation (5G) communication system to support a higher data rate than the fourth generation (4G).
[0014] According to one aspect of the present disclosure, a method performed by a terminal is provided. The method includes: receiving downlink control information (DCI) from a base station, the DCI including an indication indicating skipping of physical downlink control channel (PDCCH) monitoring for a duration; in the case where a scheduling request (SR) is triggered and not canceled, identifying whether the SR is triggered for a buffer status report (BSR); based on the identified result, determining at least one serving cell; and canceling skipping of PDCCH monitoring on at least one serving cell.
[0015] According to one aspect of the present disclosure, a terminal is provided. The terminal includes: a transceiver; and a controller configured to: control the transceiver to receive downlink control information (DCI) from a base station, the DCI including an indication indicating to skip physical downlink control channel (PDCCH) monitoring for a duration, identify whether a scheduling request (SR) is triggered for a buffer status report (BSR) when the SR is triggered and not canceled, determine at least one serving cell based on the identified result, and cancel the skipping of PDCCH monitoring on at least one serving cell.
[0016] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, be included within, interconnected with, contain, be contained within, connect to or be connected with, couple to or be coupled with, communicate with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have, have the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
[0017] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.
[0018] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
[0019] Advantageous Effects of the Invention
[0020] According to an embodiment of the present disclosure, there is an effect of defining an enhanced method to cancel / ignore PDCCH skipping when SR is pending. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:
[0022] Figure 1 An example of PDCCH skipping applied by a UE for PDCCH monitoring in the RRC_CONNECTED state according to an embodiment of the present disclosure is shown;
[0023] Figure 2 An example of a UL grant PDCCH skip duration according to an embodiment of the present disclosure is shown;
[0024] Figure 3 A flow chart of a PDCCH skipping operation according to an embodiment of the present disclosure is shown;
[0025] Figure 4 A flowchart of a PDCCH skipping operation according to another embodiment of the present disclosure is shown;
[0026] Figure 5 A block diagram of a terminal according to an embodiment of the present disclosure is shown; and
[0027] Figure 6 A block diagram of a base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0028] Discussed below Figures 1 to 6 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0029] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these details should be considered as merely exemplary. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.
[0030] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.
[0031] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
[0032] The term "substantially" means that the characteristic, parameter or value described need not be achieved precisely, but may deviate or vary by an amount that does not eliminate the effect that the characteristic is intended to provide, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art.
[0033] It is known to those skilled in the art that the combination of the blocks of a flowchart (or sequence diagram) and a flowchart can be represented and executed by computer program instructions. These computer program instructions can be loaded on a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by the processor, they create a device for performing the functions described in the flowchart. Because the computer program instructions can be stored in a computer-readable memory available in a special-purpose computer or a programmable data processing device, an article of manufacture that performs the functions described in the flowchart can also be created. Because the computer program instructions can be loaded on a computer or a programmable data processing device, when executed as a process, they can perform the operations of the functions described in the flowchart.
[0034] The blocks of the flowchart may correspond to a module, segment or code containing one or more executable instructions that implement one or more logical functions, or may correspond to a portion thereof. In some cases, the functions described by the blocks may be performed in an order different from the order listed. For example, two blocks listed in order may be executed simultaneously or in reverse order.
[0035] In this specification, the words "unit", "module", etc. may refer to software components or hardware components, such as, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) that can perform a function or operation. However, "unit", etc. are not limited to hardware or software. Units, etc. may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc. may refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be a combination of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.
[0036] Before the detailed description, terms or definitions necessary for understanding the present disclosure are described. However, these terms should be interpreted in a non-limiting manner.
[0037] A “base station (BS)” is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), Node B (NB), evolved NB (eNB), access point (AP), 5G NB (5GNB), or next generation Node B (gNB).
[0038] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.
[0039] In order to meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 60GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc., system network improvements are being developed. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coded modulation (ACM) and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.
[0040] The Internet is a human-centered connected network where humans generate and consume information, and is now evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology connected to a cloud server, has emerged. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. Such an IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0041] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs) as the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.
[0042] CA / Multiple Connections in the Fifth Generation Wireless Communication System: The fifth generation wireless communication system supports independent operation mode as well as dual connection (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) connected via a non-ideal backhaul. One node acts as a master node (MN) and the other node acts as a secondary node (SN). The MN and the SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multi-RAT dual connection (MR-DC) operation, whereby the UE in the radio resource control (RRC)_CONNECTED is configured to utilize radio resources provided by two different schedulers, the two schedulers being located in two different nodes connected via a non-ideal backhaul and providing Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) (ie, if the node is an ng-eNB) or New Radio (NR) access (ie, if the node is a gNB).
[0043] In NR, for an RRC_CONNECTED UE not configured with carrier aggregation (CA) / DC, there is only one serving cell including the primary cell. For an RRC_CONNECTED UE configured with CA / DC, the term "serving cell" is used to refer to the set of cells including the special cell and all secondary cells. In NR, the term Master Cell Group (MCG) refers to a set of serving cells associated with a primary node, including a primary cell (PCell) and optionally one or more secondary cells (SCells). In NR, the term Secondary Cell Group (SCG) refers to a set of serving cells associated with a secondary node, including a primary SCG cell (PSCell) and optionally one or more SCells.
[0044] In NR, PCell refers to a serving cell operating on the primary frequency in an MCG, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In NR for UEs configured with CA, SCell is a cell that provides additional radio resources on a special cell. PSCell refers to a serving cell in an SCG, where the UE performs random access when performing reconfiguration using a sync procedure. For dual connectivity operation, the term SpCell (i.e., special cell) refers to the PCell of an MCG or the PSCell of an SCG, otherwise the term special cell refers to the PCell.
[0045] Random access in the fifth generation wireless communication system: In the 5G wireless communication system, random access (RA) is supported. RA is used to achieve uplink (UL) time synchronization. RA is used during initial access, handover, RRC connection re-establishment process, scheduling request transmission, SCG addition / modification, beam failure recovery, and data or control information transmission in the UL by an unsynchronized UE in the RRC connected state. Several types of random access procedures are supported, such as contention-based random access, contention-free random access, and each of these can be one of 2-step or 4-step random access.
[0046] Bandwidth Part (BWP) operation in fifth generation wireless communication systems: In fifth generation wireless communication systems, bandwidth adaptation (BA) is supported. With BA, the reception and transmission bandwidth of the UE does not need to be as large as the bandwidth of the cell and can be adjusted: the width can be commanded to change (e.g., shrink during low activity periods to save power); the position can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (e.g., to allow different services). A subset of the total cell bandwidth of a cell is called a BWP. BA is implemented by configuring an RRC-connected UE with a BWP and informing the UE which of the configured BWPs is currently the active BWP. When BA is configured, the UE may monitor the Physical Downlink Control Channel (PDCCH) on only one active BWP, i.e., the UE may not monitor the PDCCH on the entire downlink (DL) frequency of the serving cell.
[0047] In the RRC connected state, for each configured serving cell (i.e., PCell or Scell), the UE is configured with one or more DL and UL BWPs. For an activated serving cell, there is always one active UL BWP and DLBWP at any point in time. BWP switching of the serving cell is used to activate the inactive BWP and deactivate the active BWP at one time. When initiating the random access procedure, the BWP switching is controlled by the PDCCH indicating the downlink allocation or uplink grant, the bwp-InactivityTimer (bandwidth part inactivity timer), RRC signaling, or the MAC entity itself. When adding a SpCell or activating a Scell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id (first active downlink BWP Id) and firstActiveUplinkBWP-Id (first active uplink BWP Id), respectively, are active without receiving a PDCCH indicating a downlink allocation or uplink grant. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP and BWP switching is common for both UL and DL. Upon expiration of the BWP inactivity timer, the UE switches to the default DL BWP or the initial DL BWP (if no default DL BWP is configured).
[0048] In a 5G wireless communication system, RRC can be in one of the following states: RRC_IDLE (RRC idle), RRC_INACTIVE (RRC inactive) and RRC_CONNECTED. When an RRC connection has been established, the UE is in the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, that is, no RRC connection is established, the UE is in the RRC_IDLE state. The RRC state can be further characterized as follows:
[0049] In RRC_IDLE, UE-specific discontinuous reception (DRX) can be configured by upper layers. The UE monitors short messages sent along with the paging radio network temporary identity (RNTI) (P-RNTI) via downlink control information (DCI); monitors the paging channel for core network (CN) paging using 5G-S-temporary mobile subscriber identity (5G-S-TMSI); performs neighbor cell measurements and cell (re)selection; acquires system information and can send system information (SI) requests (if configured); performs logging of available measurements and the UE's location and time configured for the logged measurements.
[0050] In RRC_INACTIVE, UE-specific DRX may be configured by upper layers or by the RRC layer; the UE stores UE inactive access stratum (AS) contexts; the radio access network (RAN) based notification area is configured by the RRC layer. The UE monitors short messages sent via DCI using P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI and RAN paging using full I-RNTI; performs neighbor cell measurements and cell (re)selection; performs RAN based notification area updates periodically and when moving outside the configured RAN based notification area; obtains system information and may send SI requests (if configured); performs logging of available measurements and the UE's location and time configured for the logged measurements.
[0051] In RRC_CONNECTED, the UE stores the AS context and the transmission of unicast data to / from the UE occurs. The UE monitors short messages sent via DCI using the P-RNTI (if configured); monitors the control channel associated with the shared data channel to determine whether data is scheduled for it; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; and obtains system information.
[0052] PDCCH in the fifth generation wireless communication system: In the fifth generation wireless communication system, PDCCH is used to schedule DL transmission on the physical downlink shared channel (PDSCH) and UL transmission on the physical uplink shared channel (PUSCH), wherein the DCI on the PDCCH includes: a downlink allocation including at least the modulation and coding format, resource allocation and hybrid automatic repeat request (ARQ) information related to the downlink shared channel (DL-SCH); an uplink scheduling grant including at least the modulation and coding format, resource allocation and hybrid ARQ information related to the uplink shared channel (UL-SCH). In addition to scheduling, the PDCCH can be used for: activation and deactivation of configured PUSCH transmissions with configured grants; activation and deactivation of PDSCH semi-persistent transmissions; notifying one or more UEs of the time slot format; notifying one or more UEs of physical resource blocks (PRBs) and orthogonal frequency division multiplexing (OFDM) symbols where the UE can assume that no transmission is intended for the UE; transmission of transmit power control (TPC) commands for the physical uplink control channel (PUCCH) and PUSCH; transmission of one or more TPC commands for sounding reference signal (SRS) transmissions by one or more UEs; switching the active bandwidth portion of the UE; and initiating a random access procedure.
[0053] The UE monitors a set of PDCCH candidates in the configured monitoring opportunities in one or more configured control resource sets (CORESETs) according to the corresponding search space configuration. A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource unit resource element groups (REGs) and control channel elements (CCEs) are defined within a CORESET, where each CCE comprises a set of REGs. The control channel is formed by aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE to REG mapping are supported in a CORESET. Polarization coding is used for PDCCH. Each resource element group carrying PDCCH carries its own demodulation reference signal (DMRS). Quadrature phase shift keying (QPSK) modulation is used for PDCCH.
[0054] In the fifth generation wireless communication system, a list of search space configurations is signaled by the gNB for each configured BWP of the serving cell, where each search space configuration is uniquely identified by a search space identifier. The search space identifier is unique in the BWP of the serving cell. The gNB explicitly signals the identifier of the search space configuration to be used for a specific purpose (such as paging reception, SI reception, random access response reception) for each configured BWP. In NR, the search space configuration includes the parameters monitoring-periodicity-PDCCH-slot, monitoring-offset-PDCCH-slot, monitoring-symbols-PDCCH-within-slot, and duration. The UE uses the parameters PDCCH monitoring periodicity (monitoring-periodicity-PDCCH-slot), PDCCH monitoring offset (monitoring-offset-PDCCH-slot) and PDCCH monitoring mode (monitoring-symbols-PDCCH-within-slot) to determine the PDCCH monitoring opportunity within the time slot. The PDCCH monitoring opportunity exists in the time slot "x" to x + duration, where the time slot with number "x" in the radio frame with number "y" satisfies the following equation:
[0055] (y*(number of slots in a radio frame)+x-monitoring-offset-PDCCH-slot)mod(monitoring-periodicity-PDCCH-slot)=0;
[0056] The starting symbol of the PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by monitoring-symbols-PDCCH-within-slot. The length of the PDCCH monitoring opportunity (in symbols) is given in the CORESET associated with the search space. The search space configuration includes an identifier of the CORESET configuration associated with it. The gNB signals a list of CORESET configurations for each configured BWP of the serving cell, where each CORESET configuration is uniquely identified by a CORESET identifier. The CORESET identifier is unique within the BWP of the serving cell. Note that each radio frame has a duration of 10ms. A radio frame is identified by a radio frame number or a system frame number. Each radio frame comprises a number of slots, where the number of slots in a radio frame and the duration of the slots depend on the subcarrier spacing (SCS).
[0057] The number of slots in a radio frame and the duration of the slots depend on the radio frames predefined in NR for each supported SCS. Each CORESET configuration is associated with a TCI (Transmission Configuration Indicator) state list. Each Transmission Configuration Indicator (TCI) state configures a DL Reference Signal (RS) Identifier (ID) (Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI RS)). The TCI state list corresponding to the CORESET configuration is signaled by the gNB via RRC signaling. One of the TCI states in the TCI state list is activated by the gNB and indicated to the UE. The TCI state indicates the DL TX beam (the DL TX beam is quasi-co-located (QCLed) with the SSB / CSI RS used by the gNB to transmit the TCI state of the PDCCH in the PDCCH monitoring opportunity of the search space).
[0058] In 5G wireless communication systems, the PDCCH monitoring activity of UEs in RRC connected mode is managed by DRX. When DRX is configured, the UE may monitor PDCCH discontinuously. The characteristics of DRX are as follows:
[0059] - On Duration: The duration that the UE waits to receive PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE remains awake and starts the inactivity timer;
[0060] - inactivity-timer: The duration that the UE waits for a successful decoding of the PDCCH, starting from the last successful decoding of the PDCCH. If this fails, the UE may go back to sleep. The UE may restart the inactivity timer after a single successful decoding of the PDCCH only for the first transmission (i.e. not for retransmissions);
[0061] - Retransmission timer: duration until a retransmission can be expected;
[0062] -cycle: specifies the periodic repetition of the on-time, followed by a possible period of inactivity (see below Figure 5 );as well as
[0063] -active-time: The total duration that the UE monitors the PDCCH. This includes the "on-duration" of the DRX cycle, the time that the UE is performing continuous reception when the inactivity timer has not expired, and the time that the UE is performing continuous reception when waiting for a retransmission opportunity.
[0064] In RRC_CONNECTED, the service cells of the Medium Access Control (MAC) entity can be configured by RRC in two DRX groups with separate DRX parameters. Note that the MAC entity is per cell group (CG). When RRC does not configure a secondary DRX group in a CG, there is only one DRX group in the CG, and all service cells of the CG belong to this DRX group. When two DRX groups are configured in the CG, each service cell of the CG is uniquely assigned to either of the two groups. DRX parameters are classified into group-specific parameters and common parameters. Group-specific parameters include drx-onDurationTimer and drx-InactivityTimer. The common parameters include drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerUL.
[0065] Meanwhile, various studies have been conducted recently on optimizing PDCCH monitoring in 5G communication systems. Figure 1 The PDCCH skipping shown may be applied by the UE for PDCCH monitoring in the RRC_CONNECTED state. Figure 1 (For example, Figure 1 (a)) shows normal PDCCH monitoring, where the UE monitors all configured PDCCH monitoring opportunities. Figure 1 (For example, Figure 1 (B)) shows PDCCH skipping indicated by a scheduling DCI. Scheduling DCI is a DCI indicating scheduled DL or UL resources. The skip duration may be indicated by an RRC message, may be indicated by a DCI, or may be predefined. Upon receiving a PDCCH skip indication, the UE skips PDCCH monitoring during the skip duration.
[0066] Search Space Set Group (SSSG) switching for PDCCH skipping can also be applied by the UE for PDCCH monitoring in RRC_CONNECTED state. The UE can switch to a "null" SSSG, i.e., no search space (SS) set is configured for the SSSG. Therefore, when the UE switches to a "null" SSSG, the UE does not monitor the PDCCH.
[0067] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art with respect to the present disclosure.
[0068] If the UE receives a PDCCH skip indication and triggers a scheduling request (SR) for a buffer status report (BSR), beam failure recovery (BFR), or consistent listen-before-talk (LBT) failure, and sends the SR over the PUCCH, the UL grant (scheduled by the PDCCH) is delayed due to the skip duration, as Figure 2 As shown. One way to overcome this problem is for the UE to cancel / ignore PDCCH skipping on all serving cells of a cell group when an SR is pending for the corresponding cell group. Note that each cell group triggers an SR. Canceling / ignoring PDCCH skipping on all serving cells of a cell group increases UE power consumption. It is beneficial to restrict the cancellation / ignoring of PDCCH skipping only on some serving cells. An enhanced method for cancelling / ignoring PDCCH skipping when an SR is pending is needed.
[0069] Figure 3 A flow chart of a PDCCH skipping operation according to an embodiment of the present disclosure is shown.
[0070] refer to Figure 3 , the UE is in RRC_CONNECTED state. The UE may be configured with one or more serving cells in at least one cell group (S310).
[0071] Furthermore, the UE may be configured with zero, one or more SR configurations ( S320 ) and a list of one or more allowed cells for transmission of zero or more logical channels (LCHs) ( S330 ).
[0072] The UE monitors PDCCH in the active DL BWP of the SpCell and the active DL BWP of the activated secondary cell. The UE monitors PDCCH in the PDCCH monitoring occasions configured by one or more search space configurations of the active DL BWP.
[0073] The UE receives DCI from the serving cell on the PDCCH, and the DCI includes information indicating PDCCH skipping (S340). In an embodiment, in the RRC_CONNECTED state, the UE may indicate to the gNB whether the UE supports PDCCH skipping using a dedicated RRC message. The gNB sends the PDCCH skipping indication in the DCI only if the gNB has received an indication from the UE that the UE supports PDCCH skipping.
[0074] In the RRC_CONNECTED state, SR is used to request UL-SCH resources for new transmissions. The MAC entity (or CG) can be configured with zero, one or more SR configurations, as explained above in S320. The MAC entity is separate for each CG (i.e., MCG and SCG). The SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For logical channels or for SCell beam failure recovery, for beam failure recovery of the beam failure detection (BFD)-RS set (or transmit and receive point (TRP)) of the serving cell, and for consistent LBT failure recovery, each BWP is configured with at most one PUCCH resource for SR. Each SR configuration corresponds to one or more logical channels and / or SCell beam failure recovery and / or consistent LBT failure recovery and / or beam failure recovery of the BFD-RS set (or TRP) of the serving cell. Each logical channel, SCell beam failure recovery, beam failure recovery of the BFD-RS set (or TRP) of the serving cell, and consistent LBT failure recovery can be mapped to zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers the BSR, or the SR configuration of the SCell beam failure recovery, or the SR configuration of the beam failure recovery of the BFD-RS set (or TRP) of the serving cell, or the SR configuration of the consistent LBT failure recovery (if such configuration exists) is considered to be the corresponding SR configuration for the triggered SR.
[0075] Then, one or more SRs may be triggered and pending (S350). When a SR is triggered, the SR may be considered pending until the SR is canceled.
[0076] All pending SRs for a BSR triggered before MAC protocol data unit (PDU) assembly may be canceled and each corresponding sr-ProhibitTimer may be stopped when a MAC PDU is sent and the PDU includes a long or short BSR MAC control element (CE) containing the buffer status up to (and including) the last event that triggered a BSR before MAC PDU assembly. All pending SRs for a BSR triggered according to the BSR procedure may be canceled and each corresponding sr-ProhibitTimer may be stopped when the UL grant can accommodate all pending data available for transmission.
[0077] If the SR is triggered by beam failure recovery of the SCell and a MAC PDU is sent, and the PDU includes a BFRMAC CE, a truncated BFR MAC CE, an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE, which contains the beam failure recovery information of the SCell; or if the SR is triggered by beam failure recovery of the SCell and the SCell is deactivated: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0078] If the SR is triggered by consistent LBT failure recovery of the SCell and the MAC PDU is sent and the MAC PDU includes an LBT failure MAC CE indicating a consistent LBT failure of the SCell; or if the SR is triggered by consistent LBT failure recovery of the SCell and all triggered consistent LBT failures of the SCell are canceled: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0079] If the SR is triggered by beam failure recovery of the BFD-RS set of the serving cell, and a MAC PDU is sent, and the PDU includes an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE, which contains the beam failure recovery information of the BFD-RS set of the serving cell: if running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0080] If the SR is triggered by beam failure recovery of the BFD-RS set of the SCell and the SCell is deactivated: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0081] In the method of the present disclosure, if a scheduling request is sent on a PUCCH and is pending when a PDCCH skip indication is received; or if a scheduling request is sent on a PUCCH and is pending during a PDCCH skip duration (a DCI indicating a PDCCH skip may be received before or after a scheduling request is sent on a PUCCH); or if a scheduling request is sent on a PUCCH and the scheduling request is pending, the UE (i.e., a MAC entity in the UE) performs the following operations:
[0082] If the pending scheduling request is for LBT failure, if the pending scheduling request is for Scell BFR, if the pending scheduling request is for the BFD-RS set of the serving cell in the MAC entity of the CG (the CG can be MCG or SCG), or if the pending scheduling request is for SL BSR;
[0083] ·The UE cancels / ignores the PDCCH skipping on all serving cells corresponding to the CG (S360). In an embodiment, when the SR is pending, the UE cancels / ignores the PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, during the portion of the skipping duration where the SR is pending, the UE cancels / ignores the PDCCH skipping, and during the portion of the skipping duration where the SR is not pending, the UE applies the PDCCH skipping;
[0084] Otherwise, if the pending scheduling request is a BSR in the MAC entity for the CG; and
[0085] ·If the BSR is triggered by LCH, for the LCH configuration (i.e., a list of "one or more allowed cells for transmission" (i.e., allowedServingCells) is received in an RRC message (e.g., an RRCReconfiguration message from the gNB) (S370): the UE cancels / ignores PDCCH skipping on all serving cells that schedule the corresponding CG of the serving cells included in the list allowedServingCells (S380). In an embodiment, the UE cancels / ignores PDCCH skipping on all serving cells that schedule the corresponding CG of the serving cells included in the list allowedServingCells while the SR is pending. In an embodiment, the UE cancels / ignores PDCCH skipping for a portion of the skip duration when the SR is pending, and applies PDCCH skipping for a portion of the skip duration when the SR is not pending.
[0086] In case of cross-carrier scheduling, serving cell X is scheduled by another serving cell Y, i.e., PDCCH for DL / UL transport block (TB) transmission on serving cell X is received / sent by UE / gNB on serving cell Y. In case of self-scheduling, serving cell X is scheduled by serving cell X itself, i.e., PDCCH for DL / UL TB on serving cell X is received / sent by UE / gNB on serving cell X. For a serving cell that is an SCell, whether the serving cell is self-scheduled or cross-carrier scheduled, and in case of cross-carrier scheduling, the serving cell that schedules the serving cell is indicated by the gNB in an RRC message (e.g., RRCReconfiguration message). For a serving cell that is an SpCell, the serving cell is self-scheduled. In addition, the serving cell may be cross-carrier scheduled by another serving cell, as indicated by the gNB in an RRC message (e.g., RRCReconfiguration message).
[0087] Example 1: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Both serving cell 1 and serving cell 2 are self-scheduled, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 1, and receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 2. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 1 and serving cell 2.
[0088] Example 2: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Both serving cell 1 and serving cell 2 are cross-carrier scheduled by serving cell 3 and serving cell 4, respectively, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 3, and the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 4. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 3 and serving cell 4.
[0089] Example 3: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Serving cell 1 is cross-carrier scheduled by serving cell 3, and serving cell 2 is self-scheduled, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 3, and the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 2. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 3 and serving cell 2.
[0090] If the BSR is triggered by an LCH that is not configured with a list of "one or more allowed cells for transmission" (ie, allowedServingCells).
[0091] ·UE cancels / ignores PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, when SR is pending, UE cancels / ignores PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, during the portion of the skip duration where SR is pending, UE cancels / ignores PDCCH skipping, and during the portion of the skip duration where SR is not pending, UE applies PDCCH skipping.
[0092] In an embodiment, in the above description, the PDCCH indicating that the UE switches to an empty SSSG (i.e., an SSSG that is not configured with any search space set) or a default SSSG is also considered to be a PDCCH skip indication. In this case, the skip duration may be defined by a timer, or the skip duration may be the duration until the UE receives a PDCCH indicating that the UE switches to a non-empty SSSG or a non-default SSSG.
[0093] In an embodiment, the above operation may also be applied to RRC_INACTIVE and / or RRC_IDLE, for example, the UE may receive a PDCCH skip indication during a small data transmission process in RRC_INACTIVE, and the SR may be triggered and sent in the RRC_INACTIVE state. The PDCCH skip indication may be indicated in a wake-up signal or an early paging indication, or in a random access response (RAR) or message B (MsgB) in RRC_INACTIVE and / or RRC_IDLE. In an embodiment, for a small data transmission (SDT) process in the RRC_INACTIVE or RRC_IDLE state, if RA is initiated for SDT, the gNB may send a PDCCH skip indication between message 4 (Msg4) (including contention resolution indicator MAC CE) transmission or MsgB (including contention resolution indicator) transmission and RRC release message transmission. In an embodiment, for a small data transmission process in the RRC_INACTIVE or RRC_IDLE state, if RA is initiated for SDT, the gNB may send a PDCCH skip indication after successfully completing the random access process.
[0094] In the embodiments described above, the serving cell refers to an activated serving cell, and the network may configure multiple serving cells, but some serving cells may be activated and other serving cells may be deactivated.
[0095] Figure 4 A flowchart of a PDCCH skipping operation according to another embodiment of the present disclosure is shown.
[0096] refer to Figure 4, the UE is in RRC_CONNECTED state. The UE may be configured with one or more serving cells in at least one cell group (S400).
[0097] Furthermore, the UE may be configured with zero, one or more SR configurations (S410) and a list of "one or more allowed cells for transmission" for zero or more LCHs (S420).
[0098] The UE monitors PDCCH in the active DL BWP of the SpCell and the active DL BWP of the activated secondary cell. The UE monitors PDCCH in the PDCCH monitoring occasions configured by one or more search space configurations of the active DL BWP.
[0099] The UE receives DCI from the serving cell on the PDCCH, the DCI including information indicating PDCCH skipping (S430). In an embodiment, in the RRC_CONNECTED state, the UE may indicate to the gNB whether the UE supports PDCCH skipping using a dedicated RRC message. The gNB sends the PDCCH skipping indication in the DCI only if the gNB has received an indication from the UE that PDCCH skipping is supported.
[0100] In the RRC_CONNECTED state, SR is used to request UL-SCH resources for new transmissions. The MAC entity (or CG) can be configured with zero, one or more SR configurations, as explained above in S410. The MAC entity is separate for each CG (i.e., MCG and SCG). The SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For logical channel or SCell beam failure recovery, for beam failure recovery of the BFD-RS set (or TRP) of the serving cell, and for consistent LBT failure recovery, each BWP is configured with at most one PUCCH resource for SR. Each SR configuration corresponds to one or more logical channels and / or SCell beam failure recovery and / or consistent LBT failure recovery and / or beam failure recovery of the BFD-RS set (or TRP) of the serving cell. Each logical channel, SCell beam failure recovery, beam failure recovery of the BFD-RS set (or TRP) of the serving cell, and consistent LBT failure recovery can be mapped to zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers the BSR, the SR configuration of the SCell beam failure recovery, the SR configuration of the beam failure recovery of the BFD-RS set (or TRP) of the serving cell, or the SR configuration of the consistent LBT failure recovery (if such configuration exists) is considered to be the corresponding SR configuration for the triggered SR.
[0101] Then, one or more SRs may be triggered and pending (S440). When a SR is triggered, the SR may be considered pending until the SR is canceled.
[0102] - All pending SRs for a BSR triggered before MAC PDU assembly may be canceled and each corresponding sr-ProhibitTimer may be stopped when a MAC PDU is sent and the PDU includes a long or short BSR MAC CE containing the buffer status up to and including the last event that triggered a BSR before MAC PDU assembly. All pending SRs for a BSR triggered according to the BSR procedure may be canceled and each corresponding sr-ProhibitTimer may be stopped when the UL grant can accommodate all pending data available for transmission.
[0103] -If the SR is triggered by beam failure recovery of the SCell and a MAC PDU is sent, and the PDU includes a BFRMAC CE, a truncated BFR MAC CE, an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE, which contains beam failure recovery information for the SCell; or if the SR is triggered by beam failure recovery of the SCell and the SCell is deactivated: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0104] -If the SR is triggered by consistent LBT failure recovery of the SCell and the MAC PDU is sent and the MAC PDU includes an LBT failure MAC CE indicating a consistent LBT failure of the SCell; or if the SR is triggered by consistent LBT failure recovery of the SCell and all triggered consistent LBT failures of the SCell are canceled: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0105] -If the SR is triggered by beam failure recovery of the BFD-RS set of the serving cell, and a MAC PDU is sent, and the PDU includes an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE containing the beam failure recovery information of the BFD-RS set of the serving cell: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0106] - If the SR is triggered by beam failure recovery of the BFD-RS set of the SCell and the SCell is deactivated: If running, the MAC entity cancels the pending SR and stops the corresponding sr-ProhibitTimer.
[0107] In the method of the present disclosure, if a scheduling request is sent on the PUCCH and is pending when a PDCCH skip indication is received; or if a scheduling request is sent on the PUCCH and is pending during the PDCCH skip duration (the DCI indicating the PDCCH skip may be received before or after the scheduling request is sent on the PUCCH); or if a scheduling request is sent on the PUCCH and is pending, the UE performs the following operations:
[0108] If the pending scheduling request is for LBT failure, or if the pending scheduling request is for SCell BFR, or if the pending scheduling request is for the BFD-RS set of the serving cell in the MAC entity of the CG (CG can be MCG or SCG), or if the pending scheduling request is for a sidelink (SL) BSR:
[0109] ·The UE cancels / ignores the PDCCH skipping on all serving cells corresponding to the CG (S450). In an embodiment, when the SR is pending, the UE cancels / ignores the PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, during the portion of the skipping duration where the SR is pending, the UE cancels / ignores the PDCCH skipping, and during the portion of the skipping duration where the SR is not pending, the UE applies the PDCCH skipping;
[0110] Otherwise, if the pending scheduling request is for a BSR in the MAC entity of the CG;
[0111] If the BSR is triggered by an LCH, a list of “one or more allowed cells for transmission” (i.e., allowedServingCells) is configured for the LCH (i.e., received in an RRC message (e.g., an RRCReconfiguration message from the gNB)) (S460); and
[0112] If cross-carrier scheduling is enabled (cross-carrier scheduling being enabled or not enabled may be indicated by the gNB in an RRC message (e.g., an RRCReconfiguration message)) (S470): the UE cancels / ignores PDCCH skipping on all serving cells that schedule the corresponding CG of the serving cells included in the list allowedServingCells (S480). In an embodiment, the UE cancels / ignores PDCCH skipping on all serving cells that schedule the corresponding CG of the serving cells included in the list allowedServingCells while the SR is pending. In an embodiment, the UE cancels / ignores PDCCH skipping during a portion of the skip duration for which the SR is pending, and applies PDCCH skipping during a portion of the skip duration for which the SR is not pending.
[0113] In case of cross-carrier scheduling, serving cell X is scheduled by another serving cell Y, i.e., PDCCH for DL / UL TB transmission on serving cell X is received / sent by UE / gNB on serving cell Y. In case of self-scheduling, serving cell X is scheduled by serving cell X itself, i.e., PDCCH for DL / UL TB on serving cell X is received / sent by UE / gNB on serving cell X. For a serving cell that is an SCell, it is identified whether the serving cell is self-scheduled or cross-carrier scheduled, and in case of cross-carrier scheduling, the serving cell that schedules the serving cell is indicated by the gNB in an RRC message (e.g., RRCReconfiguration message). For a serving cell that is an SpCell, the serving cell is self-scheduled. In addition, the serving cell may be cross-carrier scheduled by another serving cell, as indicated by the gNB in an RRC message (e.g., RRCReconfiguration message).
[0114] Example 1: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Both serving cell 1 and serving cell 2 are self-scheduled, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 1, and receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 2. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 1 and serving cell 2.
[0115] Example 2: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Both serving cell 1 and serving cell 2 are cross-carrier scheduled by serving cell 3 and serving cell 4, respectively, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 3, and the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 4. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 3 and serving cell 4.
[0116] Example 3: In the CG, there are four serving cells, including serving cell 1, serving cell 2, serving cell 3, and serving cell 4. The allowedServingCells of LCH A that triggers the BSR of the pending SR includes serving cell 1 and serving cell 2. Serving cell 1 is cross-carrier scheduled by serving cell 3, and serving cell 2 is self-scheduled, that is, the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for TB transmission / reception on serving cell 1 from serving cell 3, and the UE receives a PDCCH indicating UL SCH resources / DL SCH resources for transmission / reception on serving cell 2 from serving cell 2. In this case, while the SR of the BSR triggered by LCH A is pending, the MAC entity cancels / ignores the PDCCH skipping on serving cell 3 and serving cell 2.
[0117] Otherwise, if cross-carrier scheduling is not enabled:
[0118] ·The UE cancels / ignores the PDCCH skipping on all serving cells of the corresponding CG included in the list allowedServingCells of the LCH that triggered the BSR (S490). In an embodiment, while the SR is pending, the UE cancels / ignores the PDCCH skipping on all serving cells of the corresponding CG included in the list allowedServingCells of the LCH that triggered the BSR. In an embodiment, the UE cancels / ignores the PDCCH skipping during the portion of the skipping duration during which the SR is pending, and applies the PDCCH skipping during the portion of the skipping duration during which the SR is not pending.
[0119] Otherwise, if the BSR is triggered by an LCH that is not configured with a list of "one or more allowed cells for transmission" (i.e., allowedServingCells):
[0120] ·UE cancels / ignores PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, when SR is pending, UE cancels / ignores PDCCH skipping on all serving cells corresponding to the CG. In an embodiment, during the portion of the skip duration where SR is pending, UE cancels / ignores PDCCH skipping, and during the portion of the skip duration where SR is not pending, UE applies PDCCH skipping.
[0121] In an embodiment, in the above description, the PDCCH indicating that the UE switches to an empty SSSG (i.e., an SSSG that is not configured with any search space set) or a default SSSG is also considered to be a PDCCH skip indication. In this case, the skip duration may be defined by a timer, or the skip duration may be the duration until the UE receives a PDCCH indicating that the UE switches to a non-empty SSSG or a non-default SSSG.
[0122] In an embodiment, the above operation may also be applied to RRC_INACTIVE and / or RRC_IDLE, for example, the UE may receive a PDCCH skip indication during a small data transmission process in RRC_INACTIVE, and may trigger and send an SR in the RRC_INACTIVE state. The PDCCH skip indication may be indicated in a wake-up signal or an early paging indication, or in a RAR or MsgB in RRC_INACTIVE and / or RRC_IDLE. In an embodiment, for a small data transmission process in the RRC_INACTIVE or RRC_IDLE state, if RA is initiated for SDT, the gNB may send a PDCCH skip indication between Msg4 (including contention resolution indicator MAC CE) transmission or MsgB (including contention resolution indicator) transmission and RRC release message transmission. In an embodiment, for a small data transmission process in the RRC_INACTIVE or RRC_IDLE state, if RA is initiated for SDT, the gNB may send a PDCCH skip indication after successfully completing the random access process.
[0123] In the embodiments described above, the serving cell refers to an activated serving cell, and the network may configure multiple serving cells, but some serving cells may be activated and other serving cells may be deactivated.
[0124] In the methods described in the present disclosure, in the skip duration, upon receiving a PDCCH skip indication, the UE skips PDCCH monitoring addressed to a first set of RNTIs (and the gNB skips PDCCH transmission for the UE), and continues to monitor PDCCH monitoring addressed to a second set of RNTIs. Therefore, in these methods, canceling / suspending skipping or not skipping PDCCH in the PDCCH skip duration means performing PDCCH monitoring addressed to the first set of RNTIs (or sending PDCCH by the gNB) in the PDCCH skip duration.
[0125] • The first set of RNTIs and the second set of RNTIs may be predefined.
[0126] In an embodiment, the second set of RNTIs may include RNTIs other than the RNTI cell (C)-RNTI (e.g., RA-RNTI, P-RNTI, system information (SI)-RNTI, sidelink (SL)-RNTI, MsgB-RNTI), cancel indication (CI)-RNTI, configured scheduling (CS)-RNTI, interruption (INT)-RNTI, slot format indication (SFI)-RNTI, semi-persistent (SP)-CSI-RNTI, transmit power control (TPC)-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and activity indicator (AI)-RNTI. The first set of RNTIs includes C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and AI-RNTI.
[0127] • In an embodiment, the first set of RNTIs includes all RNTIs for monitoring by a UE in RRC_CONNECTED.
[0128] • In an embodiment, the first set of RNTIs includes all RNTIs for monitoring by the UE in RRC_CONNECTED, except for RNTIs related to SL communications.
[0129] In an embodiment, the method described in the present disclosure may be applied in RRC_INACTIVE and / or RRC_IDLE by replacing SR transmission with RRC message transmission (e.g., RRC connection establishment request, RRC recovery request), and replacing SR pending duration with a pending duration (a duration when T300 runs in the case of RRC connection establishment request, a duration when T319 runs in the case of recovery request) to receive a response to the RRC message transmission (e.g., RRC setup, RRC call).
[0130] In the method described in the present disclosure, in an embodiment, if the criteria for canceling / suspending skipping are met (as defined in the method), the UE may not apply skipping cancellation / suspending if the skipping duration is not extended to the end of the active time during DRX operation.
[0131] In the method described in the present disclosure, in an embodiment, if the criteria for canceling / suspending skipping are met (as defined in the method), the UE may apply skip cancellation / suspension only for a portion / part of the skip duration, where the length of the portion / part of the skip duration may be predefined or signaled by the gNB in the RRC / DCI / MAC CE, and the unit of the specified length may be the number of time slots / symbols / subframes / frames / PDCCH monitoring opportunities.
[0132] In the method described in the present disclosure, in an embodiment, if the criteria for cancelling / suspending skipping are met (as defined in the method), the UE may apply skipping cancellation / suspension only to the first / earliest PDCCH monitoring occasion in the skip duration.
[0133] In the method described in the present disclosure, in an embodiment, if the criteria for canceling / suspending skipping are met (as defined in the method), the UE may apply skipping cancellation / suspend to the earliest "N" PDCCH monitoring occasions in the skipping duration, where the parameter "N" may be predefined or signaled by the gNB in an RRC message or system information.
[0134] Figure 5 A block diagram of a terminal according to an embodiment of the present disclosure is shown.
[0135] refer to Figure 5 The terminal includes a transceiver 510, a controller 520, and a memory 530. The controller 520 may refer to a circuit, an application specific integrated circuit (ASIC), or at least one processor. The transceiver 510, the controller 520, and the memory 530 are configured to execute Figures 1 to 4 Although the transceiver 510, the controller 520 and the memory 530 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Alternatively, the transceiver 510, the controller 520 and the memory 530 may be electrically connected or coupled to each other.
[0136] The transceiver 510 may transmit and receive signals to and from other entities, ie, base stations.
[0137] The controller 520 may control the terminal to perform at least one function according to the above embodiments. For example, the controller 520 performs PDCCH monitoring and skips PDCCH monitoring. According to various embodiments of the present disclosure, the controller 520 controls the transceiver 510 and / or the memory 530 to perform PDCCH monitoring or skip PDCCH monitoring operations.
[0138] In an embodiment of the present disclosure, the operation of the terminal can be implemented using a memory 530 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 530 to store program codes for implementing desired operations. In order to perform the desired operation, the controller 520 can read and execute the program codes stored in the memory 530 by using at least one processor or CPU.
[0139] Figure 6 A block diagram of an embodiment of a base station according to the present disclosure is shown.
[0140] refer to Figure 6 The base station includes a transceiver 610, a controller 620, and a memory 630. The controller 620 may refer to a circuit, an ASIC, or at least one processor. The transceiver 610, the controller 620, and the memory 630 are configured to execute Figures 1 to 4 Although the transceiver 610, the controller 620 and the memory 630 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Alternatively, the transceiver 610, the controller 620 and the memory 630 may be electrically connected or coupled to each other.
[0141] The transceiver 610 may transmit and receive signals to and from other network entities (ie, terminals).
[0142] The controller 620 may control the base station to perform at least one function according to the above embodiments. For example, the controller 620 controls the transceiver 610 to send information for PDCCH monitoring or PDCCH monitoring skipping (ie, PDCCH monitoring skipping indication) to the terminal.
[0143] In an embodiment, the operation of the base station can be implemented using a memory 630 storing corresponding program codes. Specifically, the base station can be equipped with a memory 630 to store program codes that implement the desired operations according to various embodiments of the present disclosure. In order to perform the desired operations, the controller 620 can read and execute the program codes stored in the memory 630 by using at least one processor or CPU.
[0144] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.
[0145] As described above, the embodiments disclosed in the specification and the drawings are only used to present specific examples to easily explain the content of the present disclosure and help understanding, but are not intended to limit the scope of the present disclosure. Therefore, in addition to the embodiments disclosed herein, the scope of the present disclosure should be analyzed to include all changes or modifications derived from the technical concept of the present disclosure.
[0146] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.
Claims
1. A method performed by a terminal in a wireless communication system, the method include: receiving downlink control information (DCI) from a base station, the DCI including an indication to skip physical downlink control channel (PDCCH) monitoring for a time duration; In case a scheduling request (SR) is triggered and not cancelled, identifying whether an SR is triggered for a buffer status report (BSR); determining at least one serving cell based on the identifying; and Skipping PDCCH monitoring on the at least one serving cell is cancelled.
2. The method according to claim 1, in, In case that the SR is triggered for the BSR, the at least one serving cell is determined based on a serving cell that performs scheduling for an allowed serving cell, the allowed serving cell being configured with a logical channel for triggering the BSR.
3. The method according to claim 1, in, In the case where cross-carrier scheduling is enabled, the at least one serving cell includes all serving cells of a corresponding cell group, and the corresponding cell group schedules allowed serving cells, and Wherein, when cross-carrier scheduling is not enabled, the at least one serving cell includes all serving cells of a cell group, and the cell group includes allowed serving cells.
4. The method according to claim 1, in, In the case where SR is triggered for listen-before-talk (LBT) failure, for secondary cell (SCell) beam failure recovery (BFR), for beam failure detection (BFD)-BFR of reference signal (RS) set of serving cell, or for side link (SL) BSR, the at least one serving cell is determined based on all serving cells of the corresponding cell group for which SR is pending.
5. The method according to claim 1, in, Cancelling skipping of PDCCH monitoring includes: cancel skipping of PDCCH monitoring for a portion of the duration for which the SR is pending; and Skipping of PDCCH monitoring is applied during another part of the duration when a SR is not pending.
6. The method according to claim 1, in, Information about serving cells configured for a cell group, information about allowed serving cells configured for a logical channel, and information about duration are received through a Radio Resource Control (RRC) message.
7. The method according to claim 1, further comprising: include: Sending information to the base station indicating that the terminal supports skipping PDCCH monitoring, Wherein, based on the information, the indication is included in the DCI.
8. A terminal in a wireless communication system, the terminal include: Transceiver; as well as The controller is configured as: controlling the transceiver to receive downlink control information (DCI) from a base station, the DCI including an indication to skip physical downlink control channel (PDCCH) monitoring for a duration, In case a Scheduling Request (SR) is triggered and not cancelled, identifying whether an SR is triggered for a Buffer Status Report (BSR), determining at least one serving cell based on the identifying, and Skipping PDCCH monitoring on the at least one serving cell is cancelled.
9. The terminal according to claim 8, in, In case that the SR is triggered for the BSR, the at least one serving cell is determined based on a serving cell that performs scheduling for an allowed serving cell, the allowed serving cell being configured with a logical channel for triggering the BSR.
10. The terminal according to claim 8, in, In the case where cross-carrier scheduling is enabled, the at least one serving cell includes all serving cells of a corresponding cell group, and the corresponding cell group schedules allowed serving cells, and Wherein, when cross-carrier scheduling is not enabled, the at least one serving cell includes all serving cells of a cell group, and the cell group includes allowed serving cells.
11. The terminal according to claim 8, in, In the case where SR is triggered for listen-before-talk (LBT) failure, for secondary cell (SCell) beam failure recovery (BFR), for beam failure detection (BFD)-BFR of reference signal (RS) set of serving cell, or for side link (SL) BSR, the at least one serving cell is determined based on all serving cells of the corresponding cell group for which SR is pending.
12. The terminal according to claim 8, in, The controller is also configured to: cancel skipping of PDCCH monitoring for a portion of the duration for which the SR is pending; and Skipping of PDCCH monitoring is applied during another part of the duration when a SR is not pending.
13. The terminal according to claim 8, in, Information about serving cells configured for a cell group, information about allowed serving cells configured for a logical channel, and information about duration are received through a Radio Resource Control (RRC) message.
14. The terminal according to claim 8, in, The controller is further configured to control the transceiver to send information indicating that the terminal supports skipping PDCCH monitoring to the base station, and Wherein, based on the information, the indication is included in the DCI.
