Method and apparatus for triggering low power receiver in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system supporting a higher data transmission rate. The method performed by a terminal (or UE) includes: receiving a physical downlink control channel (PDCCH); determining a downlink control information (DCI) format based on the PDCCH, the DCI format including an indication as to whether to activate an LR to receive a low power wake-up signal (LP-WUS); determining to activate the LR based on the indication in the DCI format; the monitoring opportunity of the LP-WUS is determined; and receiving the LP-WUS based on the monitoring opportunity.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems and, more particularly, to a method and apparatus for triggering a low power receiver (LR). Background Art

[0002] 5G mobile communications technology defines a wide frequency band, enabling high transmission rates and new services. This technology is available not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, to achieve transmission rates 50 times faster than 5G mobile communications technology and ultra-low latency as low as one-tenth that of 5G mobile communications technology, consideration is being given to implementing 6G mobile communications technology in the terahertz (THz) frequency band (e.g., the 95 GHz to 3 THz band) (referred to as "beyond 5G systems").

[0003] In the early stages of 5G mobile communication technology development, in order to support related services and meet the performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC), ongoing standardization includes: beamforming and massive multiple-input multiple-output (MIMO) technologies for mitigating path loss of radio waves and increasing the transmission distance of radio waves in the millimeter wave band, support for parameter sets (for example, operating multiple subcarrier spacings) to effectively utilize millimeter wave resources and dynamic operation of time slot formats, 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-scale data transmission and polar codes for highly reliable control information transmission), L2 preprocessing, and network slicing technology for providing dedicated networks for specific services.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communications technology, taking into account the services it will support. Meanwhile, standardization is underway at the physical layer for technologies such as V2X (Vehicle-to-Everything) technology, designed to assist autonomous vehicles in making decisions and improve user convenience based on the location and status information transmitted by vehicles; NR-U (New Radio in Unlicensed Bands), which aims to operate systems in unlicensed frequency bands that meet various regulatory requirements; NR UE energy-saving technology; Non-Terrestrial Network (NTN) technology, which enables direct communication between UEs and satellites to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning technology.

[0005] In addition, in terms of air interface architecture / protocols, the technologies involved in the ongoing standardization work include: Industrial Internet of Things (IIoT) technologies that support new services through interoperability and integration with other industries, IAB (Integrated Access and Backhaul) technologies that provide nodes for network service area expansion by integrating wireless backhaul links and access links, mobility enhancement technologies including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access technology for simplifying the random access process. In terms of system architecture / services, the technologies involved in the ongoing standardization work include: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) technology for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponentially increasing number of connected devices will be connected to communication networks. Therefore, it is expected that enhancing the functionality and performance of 5G mobile communication systems and enabling the integrated operation of connected devices will become essential. To this end, new research is planned, including: extended reality (XR) for efficient support of AR (augmented reality), VR (virtual reality), and MR (mixed reality); leveraging artificial intelligence (AI) and machine learning (ML) to enhance 5G performance and reduce complexity; supporting AI services, supporting metaverse services, and drone communications.

[0007] In addition, the development of 5G mobile communication systems will not only lay the foundation for the development of the following technologies: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial lenses and antennas for improving the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface) technology; it will also lay the foundation for the development of the following technologies: full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology that uses satellites and AI to achieve system optimization from the design stage and has built-in end-to-end AI support functions, and next-generation distributed computing technology that uses ultra-high-performance communication and computing resources to implement services with complexity that exceeds the operational capabilities of UEs. Summary of the Invention

[0008] Technical issues

[0009] Currently, there is a need to enhance the triggering of low-power receivers in wireless communication systems.

[0010] Solution

[0011] The present disclosure relates to triggering LR.

[0012] In an embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes: a transceiver configured to receive a physical downlink control channel (PDCCH); a wireless LR; and a processor operably connected to the transceiver and the wireless LR. The processor is configured to: determine a downlink control information (DCI) format based on the PDCCH, the DCI format including an indication as to whether to activate the wireless LR to receive a low-power wake-up signal (LP-WUS); determine to activate the wireless LR based on the indication in the DCI format; and determine a monitoring opportunity for the LP-WUS. The wireless LR is configured to receive the LP-WUS based on the monitoring opportunity.

[0013] In another embodiment, a base station (BS) in a wireless communication system is provided. The BS includes: a processor configured to determine a DCI format, the DCI format including an indication of whether to activate a LR and transmit a LP-WUS, and determine a monitoring timing for the LP-WUS; and a transceiver operatively connected to the processor, the transceiver configured to transmit a PDCCH including the DCI format and transmit the LP-WUS based on the monitoring timing for the LP-WUS.

[0014] In yet another embodiment, a method for a UE in a wireless communication system is provided. The method includes: receiving a PDCCH; determining a DCI format based on the PDCCH, the DCI format including an indication of whether to activate a LR to receive an LP-WUS; determining to activate the LR based on the indication in the DCI format; determining a monitoring opportunity for the LP-WUS; and receiving the LP-WUS based on the monitoring opportunity.

[0015] Those skilled in the art can easily understand other technical features from the following drawings, descriptions and claims.

[0016] Before proceeding with the following detailed description, it may be helpful to first define certain words and phrases used throughout this patent document. The term "coupled" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact. The terms "send," "receive," and "communicate" and their derivatives encompass both direct and indirect communication. The terms "include," "comprise," and their derivatives mean including, but not limited to. The term "or" is inclusive, meaning "and / or." The phrase "associated with" and its derivatives mean including, contained within, interconnected, containing, contained within, connected to, coupled with, communicable with, cooperating with, interwoven, juxtaposed, proximate, bound to, bound with, having, having a characteristic of, having a relationship with, and the like. The term "controller" refers to any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The phrase "at least one," when used with a list of items, means that various combinations of one or more of the listed items may be used, and only one item in the list is required. For example, "at least one of A, B, and C" includes any combination of A, B, C, A and B, A and C, B and C, and A, B, and C.

[0017] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed of 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, procedures, functions, objects, classes, instances, associated data, or portions thereof, suitable for implementation in 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 medium capable of being accessed by a computer, such as read-only memory (ROM), random-access memory (RAM), hard drives, compact disks (CDs), digital video disks (DVDs), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored, as well as media in which data can be stored and then rewritten, such as rewritable optical disks or erasable storage devices.

[0018] Definitions for other specific words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that, in many instances, such definitions apply to prior and future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] For a more complete understanding of the present disclosure and its effects, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts: Figure 1 An exemplary wireless network according to an embodiment of the present disclosure is shown; Figure 2 An exemplary base station according to an embodiment of the present disclosure is shown; Figure 3 An exemplary user equipment (UE) according to an embodiment of the present disclosure is shown; Figure 4A shows exemplary wireless transmit and receive paths according to an embodiment of the present disclosure; Figure 4B shows exemplary wireless transmit and receive paths according to an embodiment of the present disclosure; Figure 5 A schematic diagram of explicitly triggering LR according to an embodiment of the present disclosure is shown; Figure 6 A schematic diagram illustrating application delay according to an embodiment of the present disclosure is shown; Figure 7 A flowchart illustrating an exemplary method for UE triggering LR according to an embodiment of the present disclosure is shown; Figure 8 A schematic diagram illustrating DRX of a LR according to an embodiment of the present disclosure is shown; Figure 9 A schematic diagram illustrating reception by a UE within a DRX cycle according to an embodiment of the present disclosure is shown; Figure 10 A schematic diagram illustrating an extended active portion of a DRX cycle according to an embodiment of the present disclosure is shown; Figure 11 A schematic diagram illustrating shortening the active portion of a DRX cycle according to an embodiment of the present disclosure is shown; Figure 12 A flowchart of an exemplary method implemented by a UE based on LR-DRX according to an embodiment of the present disclosure is shown; Figure 13 A structural block diagram of a user equipment (UE or terminal) according to an embodiment of the present disclosure is shown; Figure 14 A structural block diagram of a base station (BS) according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0020] Fifth-generation (5G) or New Radio (NR) mobile communications has been rapidly developing recently, driven by global industry and academic activity on a variety of candidate technologies. Candidate enabling technologies for 5G / NR mobile communications include massive antenna technology (moving from traditional cellular bands to higher frequency bands to provide beamforming gain and support capacity improvements), new waveforms (e.g., new radio access technologies (RATs) to flexibly accommodate diverse services and applications with varying requirements), and new multiple access schemes to support massive connectivity.

[0021] Discussed below Figures 1 to 14 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 understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0022] The following documents and standard descriptions are incorporated by reference into this disclosure as if fully set forth herein: 3GPP TS 38.211 v16.6.0, “NR; Physical Channels and Modulation” (REF1); 3GPP TS 38.212 v16.6.0, “NR; Multiplexing and Channel Coding” (REF2); 3GPP TS 38.213 v16.6.0, “NR; Physical Layer Procedures for Control” (REF3); 3GPP TS 38.214 v16.6.0, “NR; Physical Layer Procedures for Data” (REF4); and 3GPP TS 38.331 v16.6.0, “NR; Radio Resource Control (RRC) Protocol Specification” (REF5).

[0023] To meet the growing demand for wireless data traffic since the deployment of 4G communication systems and enable a variety of vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are expected to be implemented in higher-frequency (millimeter wave) bands (such as the 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower-frequency bands (such as 6 GHz) to provide robust coverage and mobility support. To reduce radio wave propagation losses and increase transmission distances, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are being discussed in 5G / NR communication systems.

[0024] In addition, in 5G / NR communication systems, development work is underway to improve system networks based on technologies such as 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), and receiver-side interference cancellation.

[0025] The discussion of 5G systems and their associated frequency bands is provided for reference only, as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or their associated frequency bands; embodiments of the present disclosure may be applied to any frequency band. For example, aspects of the present disclosure may also be applied to the deployment of 5G communication systems, 6G, and even subsequent versions that may utilize terahertz (THz) frequency bands.

[0026] The following Figure 1-3 Various embodiments are described as being implemented in a wireless communication system and utilizing Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figure 1-3 The description is not meant to impose physical or architectural limitations on the implementation of the various embodiments. The various embodiments of the present disclosure may be implemented in any suitably arranged communication system.

[0027] Figure 1 An exemplary wireless network according to an embodiment of the present disclosure is shown. Figure 1 The wireless network embodiment shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0028] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0029] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UEs) within gNB 102's coverage area 120. The first plurality of UEs includes UE 111 (which may be located in a small business), UE 112 (which may be located in an enterprise), UE 113 (which may be a WiFi hotspot), UE 114 (which may be located in a first residence), UE 115 (which may be located in a second residence), and UE 116 (which may be a mobile device, such as a cell phone, wireless laptop, wireless PDA, etc.). gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within gNB 103's coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), Long Term Evolution-Advanced (LTE-A), WiMAX, WiFi, or other wireless communication technologies.

[0030] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmit receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wireless-enabled devices. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR Third Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE-Advanced (LTE-A), High-Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, in this patent document, the terms "BS" and "TRP" are used interchangeably to refer to a network infrastructure component that provides wireless access to remote terminals. Similarly, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "reception point," or "user device." For convenience, in this patent document, the terms "user equipment" and "UE" are used to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or a device that is generally considered to be fixed (such as a desktop computer or vending machine).

[0031] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as generally circular for purposes of illustration and explanation. It should be clearly understood that coverage areas associated with a gNB (e.g., coverage areas 120 and 125) may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstructions.

[0032] As described in more detail below, one or more of the UEs 111-116 include circuitry, programming, or a combination thereof to support triggering LR. In some embodiments, one or more of the BSs 101-103 include circuitry, programming, or a combination thereof to trigger LR.

[0033] although Figure 1 An example of a wireless network is shown, but Figure 1Various modifications are possible. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 may communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 may communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Furthermore, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0034] Figure 2 An exemplary gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustration only. Figure 1 The gNBs 101 and 103 in FIG can have the same or similar configurations. However, gNBs have various configurations, Figure 2 The scope of this disclosure is not limited to any particular implementation of a gNB.

[0035] like Figure 2 As shown, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235. According to various embodiments of the present disclosure, the gNB 102 can support triggered LR and DRX of LR through the controller or processor 225.

[0036] Transceivers 210a-210n receive incoming radio frequency (RF) signals from antennas 205a-205n, such as signals transmitted by UEs in network 100. Transceivers 210a-210n downconvert the incoming RF signals to generate IF signals or baseband signals. The IF signals or baseband signals are processed by receive (RX) processing circuitry within transceivers 210a-210n and / or controller / processor 225, which filters, decodes, and / or digitizes the baseband signals or IF signals to generate processed baseband signals. Controller / processor 225 may further process the baseband signals.

[0037] Transmit (TX) processing circuitry within transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (e.g., voice data, web page data, email, or interactive video game data) from controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the output baseband data to generate processed baseband or IF signals. Transceivers 210a-210n upconvert the baseband or IF signals into RF signals, which are then transmitted via antennas 205a-205n.

[0038] The controller / processor 225 may include one or more processors or other processing devices for controlling the overall operation of the gNB 102. For example, the controller / processor 225 may control the transceivers 210a-210n to receive uplink (UL) channel signals and transmit downlink (DL) channel signals in accordance with well-known principles. The controller / processor 225 may also support other functions, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations by differentially weighting the output / input signals from / to the multiple antennas 205a-205n to effectively direct the output signals in a desired direction. The controller / processor 225 may also support a variety of other functions within the gNB 102.

[0039] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as the process that triggers the LR discussed in more detail below. The controller / processor 225 can move data into or out of the memory 230 as required by the process being executed.

[0040] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. The interface 235 can support communication over any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a system supporting 5G / NR, LTE, or LTE-A), the interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 can allow the gNB 102 to communicate over a wired or wireless local area network, or over a wired or wireless connection to a larger network (e.g., the Internet). The interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as Ethernet or a transceiver.

[0041] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM and another portion may include flash memory or other ROM.

[0042] although Figure 2 An example of a gNB 102 is shown, but Figure 2 Various modifications may be made. For example, gNB 102 may include Figure 2 Any number of each component shown. In addition, Figure 2 The various components in can be combined, further subdivided, omitted, or have additional components added according to specific needs.

[0043] Figure 3An exemplary UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only. Figure 1 UEs 111-115 in the embodiment may have the same or similar configurations. However, UEs have various configurations. Figure 3 The scope of this disclosure is not limited to any particular implementation of a UE.

[0044] like Figure 3 As shown, UE 116 includes an antenna 305, a transceiver 310, and a microphone 320. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362. In embodiments of the present disclosure, gNB 102 may support methods and apparatus for triggering LR via antenna 305, transceiver 310, and processor 340.

[0045] Transceiver 310 receives an incoming RF signal from antenna 305, transmitted by a gNB in ​​network 100. Transceiver 310 downconverts the incoming RF signal to generate an intermediate frequency (IF) signal or a baseband signal. The IF signal or baseband signal is processed by RX processing circuitry and / or processor 340 within transceiver 310, which filters, decodes, and / or digitizes the baseband signal or IF signal to generate a processed baseband signal. The RX processing circuitry transmits the processed baseband signal to speaker 330 (e.g., for voice data) or is processed by processor 340 (e.g., for web browsing data).

[0046] The TX processing circuitry within transceiver 310 and / or processor 340 receives analog or digital voice data from microphone 320 or other outgoing baseband data (e.g., web page data, email, or interactive video game data) from processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband signal or IF signal. Transceiver 310 up-converts the baseband signal or IF signal into an RF signal, which is transmitted via antenna 305.

[0047] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the transceiver 310 to receive downlink channel signals and transmit uplink channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0048] Processor 340 is also capable of executing other processes and programs residing in memory 360. For example, as discussed in greater detail below, processor 340 can execute processes that support triggering LR. Processor 340 can move data into or out of memory 360 as required by the executing process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which enables UE 116 to connect to other devices, such as laptops and handheld computers. I / O interface 345 provides a communication path between these accessories and processor 340.

[0049] The processor 340 is also coupled to an input 350 (e.g., comprising a touch screen, a keyboard, etc.) and a display 355. An operator of the UE 116 can use the input 350 to input data into the UE 116. The display 355 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics (e.g., graphics from a website).

[0050] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion may include flash memory or other read-only memory (ROM).

[0051] In various embodiments, transceiver 310 includes or is at least one LR 312 and at least one main receiver (MR) 314. For example, as discussed in greater detail below, when UE 116 is in a sleep state (e.g., an ultra-deep sleep state, discussed in greater detail below), LR 312 may be configured or used to receive low-power signals (e.g., LP-WUS) while MR 314 is powered off or in a low-power state. For example, in some embodiments, LR 312 may be a component of transceiver 310 that is used or enabled when UE 116 is in the sleep state, while MR 314 is the transceiver 310 used when UE 116 is not in the sleep state. In another example, in other embodiments, LR 312 may be a separate or independent receiver from transceiver 310, while transceiver 310 is the MR 314 used for normal receive operations when UE 116 is not in the sleep state.

[0052] Similarly, in such embodiments, processor 340 includes at least one of a low-power processor (LP) 342 and a main processor (MP) 344, or is one of them. For example, in some embodiments, LR 312 and MR 314 may be connected to and / or controlled by LP 342 and MP 344, respectively, with LP 342 and MP 344 being separate and / or independent processors. In these embodiments, LP 342 may operate in a lower power state than MP 344, such that when the UE is in a sleep state, MP 344 may be powered off or in a low-power state while LP 342 processes any signals received by LR 312 (e.g., LP-WUS). In these embodiments, the operation of LP 342 may consume less power than the normal operation of MP 344, thereby conserving power while UE 116 is in the sleep state while maintaining the UE 116's ability to receive and process signals. In other embodiments, the LP 342 and the MP 344 may be components of the processor 340, and the LR 312 and the MR 314 may be connected to and / or controlled by the LP 342 and the MP 344, respectively. In these embodiments, when the UE 116 is in the sleep state, the MP 344 component of the processor 340 is powered off or in a low-power state, and the LP 342 component operates to process signals (e.g., LP-WUS) received by the LR 312. In these embodiments, the operation of the LP 342 component of the processor 340 may consume less power than the normal operation of the processor 340 including the operation of the MP 344 component, thereby conserving power while the UE 116 is in the sleep state while maintaining the UE 116's ability to receive and process signals.

[0053] although Figure 3 An example of a UE 116 is shown, but for Figure 3 Various changes can be made. For example, Figure 3 The various components in the can be combined, further subdivided, omitted, or have additional components added according to specific needs. As a specific example, the processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, the transceiver 310 can include any number of transceivers and signal processing chains and can be connected to any number of antennas. In addition, although Figure 3 The UE 116 is configured as a mobile phone or smartphone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0054] Figure 4A and Figure 4BExample wireless transmit and receive paths according to the present disclosure are shown. In the following description, transmit path 400 may be described as being implemented in a gNB (e.g., gNB 104), while receive path 450 may be described as being implemented in a UE (e.g., UE 116). However, it should be understood that receive path 450 may also be implemented in a gNB, and transmit path 400 may also be implemented in a UE.

[0055] Transmit path 400 includes channel coding and modulation block 405, serial-to-parallel conversion (S-to-P) block 410, N-point inverse fast Fourier transform (IFFT) block 415, parallel-to-serial conversion (P-to-S) block 440, cyclic prefix addition block 445, and upconverter (UC) 430. Receive path 450 includes downconverter (DC) 455, cyclic prefix removal block 460, serial-to-parallel conversion block (S-to-P) 465, N-point fast Fourier transform (FFT) block 470, parallel-to-serial conversion (P-to-S) block 475, and channel decoding and demodulation block 480. In an embodiment, both transmit path 400 and receive path 450 are configured to support triggered LR.

[0056] In the transmit path 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding), and modulates the input bits (e.g., using quadrature phase-shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel conversion block 410 converts (e.g., demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 104 and UE 116. The N-point IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. The parallel-to-serial conversion block 440 converts (e.g., multiplexes) the parallel time-domain output symbols from the N-point IFFT block 415 into a serial time-domain signal. The cyclic prefix add block 445 inserts a cyclic prefix into the time-domain signal. The upconverter 430 modulates (e.g., downconverts) the output of the cyclic prefix add block 445 to RF frequency for transmission over a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0057] The RF signal transmitted from gNB 104 arrives at UE 116 after traversing the wireless channel. UE 116 performs the reverse operations of gNB 104. Downconverter 455 downconverts the received signal to baseband frequency, and cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel conversion block 465 converts the time-domain baseband signal into parallel time-domain signals. N-point FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial conversion block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0058] Each of gNBs 101-103 may implement a transmit path similar to 400 for downlink transmissions to UEs 111-116 and may implement a receive path similar to 450 for uplink reception from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path similar to 400 for uplink transmissions to gNBs 101-103 and may implement a receive path similar to 450 for downlink reception from gNBs 101-103.

[0059] Figure 4A and Figure 4B Each component in can be implemented using hardware only, or a combination of hardware and software / firmware. As a specific example, Figure 4A and Figure 4B At least some components in the algorithm may be implemented in software, while other components may be implemented in configurable hardware, or a mixture of software and configurable hardware. For example, FFT block 470 and IFFT block 415 may be implemented as configurable software algorithms, where the value of N may be modified according to the implementation.

[0060] Furthermore, although FFT and IFFT are used in the description, this is for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. Other types of transforms, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions, may be used. It should be understood that for DFT and IDFT functions, the value of the variable N can be any integer (e.g., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N can be any integer power of 2 (e.g., 1, 4, 4, 8, 16, etc.).

[0061] although Figure 4A and Figure 4B Examples of wireless transmit and receive paths are shown, but Figure 4A and Figure 4B Various changes can be made. For example, Figure 4A and Figure 4BThe various components in can be combined, further subdivided, omitted, or have other components added according to specific needs. Figure 4A and Figure 4B It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

[0062] NR supports discontinuous reception (DRX) of UEs in RRC_IDLE / RRC_INACTIVE mode or RRC_CONNECTED mode, allowing the UE to stop receiving signals or channels during the inactive period of the DRX cycle, thereby saving power consumption. In Rel-16, enhancements to DRX in RRC_CONNECTED mode (such as C-DRX) were introduced, in which a new DCI format was used to help the UE skip the ON duration within the C-DRX cycle, thereby achieving further energy saving gains. In Rel-17, enhancements to DRX in RRC_IDLE / RRC_INACTIVE mode (such as I-DRX) were introduced, in which a paging advance indication (PEI) was used to allow the UE to skip monitoring paging opportunities, thereby achieving additional energy saving gains.

[0063] However, as recognized in the present disclosure, the UE still needs to wake up frequently to monitor new DCI formats or PEIs, so that the UE's radio cannot be completely turned off for a long time. To avoid this and obtain further energy savings, it is considered to use an additional receive radio, where the additional receive radio can be used to monitor a specific set of signals with very low power consumption, while the main receive radio can be turned off for a long time or run at very low power.

[0064] The present disclosure provides a triggering mechanism for switching from using a primary receiver to using an additional receiver with low power, where the UE expects a low-power signal to be available. For example, a low-power wake-up signal and / or a low-power synchronization signal. The UE may also expect to receive the low-power signal. The present disclosure further provides a method and apparatus for a UE to trigger LR or DRX of LR in RRC_IDLE and / or RRC_INACTIVE and / or RRC_CONNECTED mode.

[0065] The present disclosure also provides a triggering mechanism for a receiver to receive a low-power signal. As will be described in more detail below, the present disclosure provides: (1) a triggering mechanism that is (a) an explicit trigger using a signal or channel, or (b) an implicit trigger without using an explicit signal or channel; an application delay (a) for a primary receiver, (b) for a LR, (c) RRM measurement relaxation based on the application delay, and (d) an extension of the application delay; and an exemplary UE process for triggering the LR.

[0066] The present disclosure also provides DRX configuration for LR, reception based on the DRX configuration, active portion extension based on UE's reception using LR, active portion truncation based on UE's reception using LR, and exemplary UE procedures for DRX operation of LR.

[0067] Figure 5 A schematic diagram 500 of explicitly triggering LR is shown. Figure 5 The embodiment of schematic diagram 500 shown is for illustration only. Figure 5 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 5 The scope of the present disclosure is not limited to any particular implementation of the diagram 500 of explicitly triggering LR.

[0068] In one embodiment, an explicit signal or channel may trigger a transition from using the MR (e.g., MR 314) to using the LR (e.g., LR 312), or trigger use of the LR, or trigger the MR to operate in a low power state (e.g., ultra-deep sleep), or trigger activation and / or deactivation of a low power signal (e.g., a low power wake-up signal and / or a low power synchronization signal) that may be received by the LR.

[0069] In one example, an explicit signal or channel may be received by the MR.

[0070] In some examples, if the UE is in RRC_CONNECTED mode, upon receiving an explicit signal or channel, the UE may transition to RRC_IDLE or RRC_INACTIVE mode.

[0071] In further examples, if the UE is in RRC_INACTIVE mode, upon receiving an explicit signal or channel, the UE may transition to RRC_IDLE mode.

[0072] In other examples, an explicit signal or channel may be sent by the gNB.

[0073] In a further example, the explicit signal or channel may be a response to a request to use LR, where the request may be sent from the UE. The request may be included in one or more of a variety of ways. The request may be included in Msg1 of a four-step RACH procedure (e.g., PRACH). The request may be included in Msg3 of a four-step RACH procedure. The request may be included in MsgA of a two-step RACH procedure. The request may be included in a scheduling request (SR). The request may be included in a PUCCH. The request may be included in a PUSCH (e.g., CG-PUSCH). The request may be included in higher-layer parameters, such as UE assistance information.

[0074] In one example, the explicit signal or channel may be cell-specific.

[0075] In another example, the explicit signal or channel may be UE group specific.

[0076] In yet another example, the explicit signal or channel may be UE-specific.

[0077] In one example, the explicit signal or channel may be a PDCCH carrying a DCI format. The explicit signal or channel may also be one or more of the following. It may be a PDCCH carrying DCI format 1_0, wherein the PDCCH is monitored in the CSS and the CRC of DCI format 1_0 is scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI. It may be a PDCCH carrying DCI format 1_0, wherein the PDCCH is monitored in the CSS and the CRC of DCI format 1_0 is scrambled by P-RNTI. For example, the information carried by the PDCCH may be a paging short message. It may be a PDCCH carrying DCI format 1_0, wherein the PDCCH is monitored in the CSS and the CRC of DCI format 1_0 is scrambled by SI-RNTI. It may be a PDCCH carrying DCI format 1_0, wherein the PDCCH is monitored in the CSS and the CRC of DCI format 1_0 is scrambled by RA-RNTI or MsgB-RNTI. It can be a PDCCH carrying DCI format 1_0, where the PDCCH is monitored in the CSS and the CRC of DCI format 1_0 is scrambled by the TC-RNTI. It can be a PDCCH carrying DCI format 2_0, where the PDCCH is monitored in the CSS and the CRC of DCI format 2_0 is scrambled by the SFI-RNTI. It can be a PDCCH carrying DCI format 2_7, where the PDCCH is monitored in the CSS and the CRC of DCI format 2_7 is scrambled by the PEI-RNTI. It can be a PDCCH carrying a DCI format and monitored in the USS, such as DCI formats 1_1 and / or 1_2. It can be a PDCCH carrying a DCI format (such as a new DCI format) where the PDCCH is monitored in the CSS and / or the CRC of the DCI format is scrambled by at least one new RNTI.

[0078] In another example, the explicit signal or channel can be based on: SS / PBCH blocks, PSS in SS / PBCH blocks, SSS in SS / PBCH blocks, DM-RS of PBCH in SS / PBCH blocks, and PBCH content carried by PBCH in SS / PBCH blocks. The PBCH content can contain an explicit indication as to whether the use of LR should be triggered.

[0079] In another example, the explicit signal or channel can be a PDSCH; a PDSCH for paging, for example, a PDSCH scheduled by a PDCCH monitored in a paging occasion and carrying paging-related information; a PDSCH carrying SIB1, for example, a PDSCH scheduled by a type0-PDCCH; a PDSCH carrying SIBx (where x>1), for example, a PDSCH scheduled by a type0A-PDCCH; a PDSCH for RAR, for example, a PDSCH carrying Msg2 in a four-step RACH; a PDSCH carrying Msg4 in a four-step RACH; a PDSCH carrying MsgB in a two-step RACH; a PDSCH scheduled by a PDCCH carrying DCI formats 1_1 and / or 1_2, for example, where the PDCCH is monitored in a USS; and a PDSCH carrying RRC parameters.

[0080] In another example, the explicit signal or channel can be: a dedicated signal for triggering LR usage and / or triggering activation / deactivation of a low power signal; a signal generated based on an M sequence; a signal generated based on a Gold sequence; a signal generated based on a ZC sequence; and a signal generated based on a PN sequence.

[0081] In yet another example, the explicit signal or channel may be a MAC CE.

[0082] In yet another example, the explicit signal or channel may be an RRC release message.

[0083] In one example, after receiving an explicit signal or channel, the UE may send an acknowledgment of successful reception of the explicit signal or channel to the gNB. This acknowledgment may be included in: Msg1 of a four-step RACH procedure (e.g., PRACH); Msg3 of a four-step RACH procedure; MsgA of a two-step RACH procedure; PUCCH (e.g., PUCCH carrying UCI); PUSCH (e.g., PUSCH carrying UCI); higher layer parameters (e.g., UE assistance information); and an RRC release request. In embodiments, this example may be applicable to RRC_CONNECTED mode.

[0084] In one example, the explicit signal or channel may also include duration information related to the use of LR and / or activation / deactivation of the low-power signal. For example, the unit of the duration may be a symbol, a time slot, a millisecond, a frame, or a DRX cycle. For another example, the reference time as the starting point of the duration may be the start or end time of the symbol or time slot in which the UE receives the signal or channel. For another example, the reference time as the starting point of the duration may be the start or end time of the symbol or time slot in which the UE sends an acknowledgment of successful reception of the signal or channel. For another example, the reference time as the starting point of the duration may be the delay after the UE receives the symbol or time slot of the signal or channel, wherein the delay may be provided by a higher-layer parameter, or fixed in the specification (for example, according to the subcarrier spacing value), or determined based on the UE capability. For another example, the reference time as the starting point of the duration may be explicitly provided by an explicit signal or channel.

[0085] In another example, the explicit signal or channel may also include information about the time when the LR is started and / or the low power signal is activated / deactivated. For example, the unit of the time may be a symbol, a time slot, a millisecond, a frame, or a DRX cycle.

[0086] In yet another example, the explicit signal or channel may also include information regarding the type of energy conservation class in which the UE can operate when using LR. For example, at least two different energy conservation classes may be predefined in the specification or configured by higher layers, and the explicit signal or channel may include an indication of the energy conservation class index in which the UE operates when using LR. For another example, the explicit signal or channel may include an indication of the energy conservation class configuration in which the UE operates when using LR.

[0087] In one example, if the UE does not receive an explicit signal or channel at a certain reception opportunity, the UE may continue to receive and / or transmit using the MR and / or assume that the low power signal is not being transmitted / activated.

[0088] In another example, if the gNB does not receive confirmation of successful reception of an explicit signal or channel, the gNB may assume that the UE's use of LR or activation of low-power signaling was not triggered. Furthermore, the gNB may resend the explicit signal or channel.

[0089] In yet another example, the gNB may send an explicit signal or channel at one or more occasions prior to sending the low power wake-up signal to trigger the use of LR or trigger activation / deactivation of the low power signal.

[0090] In one embodiment, the transition from using MR to using LR, or starting to use LR, or operating MR in a low power state (e.g., ultra-deep sleep), or the activation / deactivation of a low power signal, may be triggered implicitly, e.g., by an implicit trigger.

[0091] In one example, an implicit trigger may be used when no explicit trigger or configuration for an explicit trigger is provided, or when no explicit trigger is received.

[0092] In one example, if the UE is in RRC_CONNECTED mode, then upon implicit triggering, the UE may transition to RRC_IDLE or RRC_INACTIVE mode.

[0093] In another example, if the UE is in RRC_INACTIVE mode, then upon implicit triggering, the UE may transition to RRC_IDLE mode.

[0094] In one example, implicit triggering can be based on timing. When a specific timing moment arrives, it can trigger a transition from using MR to using LR, trigger the start of using LR, trigger MR to operate in a low-power state (e.g., ultra-deep sleep), or trigger the activation / deactivation of a low-power signal. In various examples, the timing can be an OFDM symbol boundary. In other examples, the timing can be a slot boundary. In yet further examples, the timing can be a frame boundary. In some examples, the timing can be a DRX cycle boundary.

[0095] In another example, the implicit trigger may be based on the DRX cycle configuration in RRC_IDLE and / or RRC_INACTIVE mode.In various examples, the implicit trigger may be aligned with a paging occasion or a PEI monitoring occasion.

[0096] In yet another example, the implicit trigger may be based on the DRX cycle configuration in RRC_CONNECTED mode.In various examples, the implicit trigger may be aligned with the ON duration in the DRX cycle or a time period boundary of the DRX cycle.

[0097] In yet another example, an implicit trigger can be based on signal or channel reception conditions, such as reception conditions using MR. In some further examples, if a UE (e.g., using MR) misses reception of a DL signal or channel K times in a row, the UE can assume a transition from using MR to using LR, or assume the UE starts using LR, or assumes the UE operates in a low-power state (e.g., ultra-deep sleep), or assumes the UE activates a low-power signal. In such examples, the DL signal or channel can be an SS / PBCH block, a PDCCH (e.g., a PDCCH for paging, a PDCCH for SIB1, or a PDCCH for SIBx with x>1), a PDSCH (e.g., a PDSCH for paging, a PDSCH for SIB1, or a PDSCH for SIBx with x>1), a DL RS (e.g., a TRS or PRS), or at least one of the explicit triggers described in this disclosure. In such examples, K can be fixed in the specification, provided by a higher-layer parameter, or provided by the DCI format.

[0098] In other examples, if the UE (e.g., using MR) receives an LP-WUS or LP-WUS related signal (e.g., a synchronization signal of the LR), the UE may assume a transition from using the MR to using the LR, or assume starting to use the LR, or assume operating the MR in a low power state (e.g., ultra-deep sleep), or assume deactivation / activation of the low power signal.

[0099] In yet another example, if a UE (e.g., using MR) does not receive a downlink signal or channel for a period of time, the UE may assume that it has transitioned from using MR to using LR, started using LR, or operated MR in a low-power state (e.g., ultra-deep sleep), or activated a low-power signal. In such an example, the downlink signal or channel may be at least one of an SS / PBCH block, a PDCCH (e.g., a PDCCH for paging, a PDCCH for SIB1, or a PDCCH for SIBx with x>1), a PDSCH (e.g., a PDSCH for paging, a PDSCH for SIB1, or a PDSCH for SIBx with x>1), or a downlink RS (e.g., a TRS or PRS). In such an example, the period of time may be fixed in the specification, provided by a higher-layer parameter, or provided by a DCI format. In such an example, the period of time may be determined based on a timing instant, such as the reception instant of SIB1, SIBx, an SS / PBCH block, or a downlink RS, or any downlink reception instant.

[0100] In one example, the implicit trigger may be a response to a request to use LR, which may be sent from the UE. The request may be included in: Msg1 of a four-step RACH procedure (e.g., PRACH); Msg3 of a four-step RACH procedure; MsgA of a two-step RACH procedure; a scheduling request (SR); a PUCCH; a PUSCH (e.g., CG-PUSCH); and higher layer parameters (e.g., UE assistance information).

[0101] In one example, after an implicit trigger, the UE (e.g., 116) can send a confirmation of the use of LR to the gNB (e.g., 102). The confirmation can be included in: Msg1 of a four-step RACH procedure (e.g., PRACH), Msg3 of a four-step RACH procedure, MsgA of a two-step RACH procedure, PUCCH (e.g., PUCCH carrying UCI), PUSCH (e.g., PUSCH carrying UCI), higher layer parameters (e.g., UE assistance information), or an RRC release request. This example can be applicable to RRC_CONNECTED mode.

[0102] In another example, if the gNB does not receive confirmation about the use of LR, the gNB may assume that the UE's use of LR is not triggered or the activation of low power signaling is not triggered.

[0103] Figure 6 A schematic diagram 600 illustrating application delays is shown. Figure 6 The embodiment of schematic diagram 600 shown in FIGURE 6 is for illustration only. Figure 6 One or more of the components shown in the drawings may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 6 The scope of the present disclosure is not limited to any particular implementation of the application delay example diagram 600 .

[0104] In one embodiment, there may be an application delay when a MR (e.g., MR 314) transitions to or is enabled to operate in a low power state (e.g., ultra-deep sleep) or prepares to stop receiving signals / channels other than low power signals (e.g., low power signals may be received by a LR (e.g., LR 312)).

[0105] In one example, the application delay of the MR may be zero.

[0106] In one example, the application delay is determined using a reference timing that triggers reception (eg, a start or end time of an explicit signal or channel).

[0107] In another example, the application delay is determined using a reference timing of a transmission that is an acknowledgement of successful receipt of a trigger (eg, an explicit signal or channel).

[0108] In yet another example, the application delay is determined using a reference timing that is an implicit trigger.

[0109] In one example, a delay may be applied for the UE to prepare for transitioning to or being enabled to operate in a low power state (eg, ultra deep sleep) such that the UE does not need to receive signals or channels other than low power signals, eg, preparation time.

[0110] In another example, application delay may be used for the UE to process signals and / or channels in order to transition to or be enabled to operate in a low power state (e.g., ultra-deep sleep) such that the UE does not need to receive signals or channels other than low power signals, such as processing time.

[0111] In one example, the maximum value, the minimum value, or the value of the applied delay may be determined by a specification, such as based on the subcarrier spacing.

[0112] In another example, the maximum value, the minimum value, or the value of the application delay may be determined based on UE capabilities.

[0113] In yet another example, the maximum value, the minimum value, or the value of the application delay may be provided by a high-level parameter.

[0114] In one example, within a maximum value, a minimum value, or a range of values ​​for an applied delay, the UE is expected to receive and / or transmit signals and / or channels other than low-power signals (e.g., using MR). The signal and / or channel may be an SS / PBCH block or a PDCCH. The PDCCH may be a specific type of PDCCH, such as Type 0 PDCCH, Type 0A PDCCH, Type 1 PDCCH, or Type 2 PDCCH. Alternatively, the PDCCH may be any PDCCH monitored in the CSS or USS, or any PDCCH. The signal and / or channel may also be a PDSCH. For example, the PDSCH may be scheduled by a specific type of PDCCH (e.g., Type 0 PDCCH, Type 0A PDCCH, Type 1 PDCCH, or Type 2 PDCCH), any PDCCH monitored in the CSS, any PDCCH monitored in the USS, or any PDCCH. The signal and / or channel may be a DL RS, which may be a TRS or CSI-RS, PUCCH, PUSCH, PRACH, or UL RS.

[0115] In another example, after a maximum value, a minimum value, or a value of the applied delay (e.g., before the next triggering of an MR, before the low-power signal is deactivated, or before the expiration of a related timer), the UE is expected to refrain from receiving and / or transmitting signals and / or channels other than low-power signals (e.g., using an MR). The signal and / or channel may be an SS / PBCH block or a PDCCH. The PDCCH may be of a specific type, such as Type 0-PDCCH, Type 0A-PDCCH, Type 1-PDCCH, or Type 2-PDCCH, or any PDCCH monitored in the CSS, any PDCCH monitored in the USS, or any other PDCCH. The signal and / or channel may be a PDSCH. For example, the PDSCH may be scheduled by a specific type of PDCCH (e.g., Type 0-PDCCH, Type 0A-PDCCH, Type 1-PDCCH, or Type 2-PDCCH). For another example, the PDSCH may be scheduled by any PDCCH monitored in the CSS. For another example, the PDSCH may be scheduled by any PDCCH monitored in the USS. For example, a PDSCH can be scheduled by any PDCCH. In another sub-example, the signal and / or channel can be a DL RS, where the DL RS can be a TRS or a CSI-RS. The signal and / or channel can be: PUCCH, PUSCH, PRACH, and UL RS.

[0116] In one embodiment, after activation, there may be an application delay while the LR is started or the UE is ready to receive low power signals. Figure 5 An example is shown, and the application delay of LR is denoted as D1_LR.

[0117] In one example, the application delay of the LR may be 0.

[0118] In another example, the application delay of MR (eg, D1_MR) may be the same as the application delay of LR (eg, D1_LR).

[0119] In yet another example, the end time instant of the MR application delay may be aligned with the end time instant of the LR application delay.

[0120] In another example, the end time instant of the MR application delay may be no earlier than (or later than) the end time instant of the LR application delay.

[0121] In yet another example, the end time instant of the MR application delay may be no later than (or earlier than) the end time instant of the LR application delay.

[0122] In one example, the application delay is determined using a reference timing that triggers reception (eg, a start or end time of an explicit signal or channel).

[0123] In another example, the application delay is determined using a reference timing that is sent as an acknowledgement of successful receipt of a trigger (eg, an explicit signal or channel).

[0124] In yet another example, the application delay is determined using a reference timing that is an implicit trigger.

[0125] In one example, the application delay may be used for the UE to prepare to start the LR so that the UE can receive the low power signal, eg, a preparation time.

[0126] In another example, a delay may be applied for the UE to process the signal and / or channel to enable LR so that the UE can receive the low power signal, eg, processing time.

[0127] In one example, the maximum value, the minimum value, or the value of the applied delay may be determined by a specification, such as based on the subcarrier spacing.

[0128] In another example, the maximum value, the minimum value, or the value of the application delay may be determined based on UE capabilities.

[0129] In yet another example, the maximum value, the minimum value, or the value of the application delay may be provided by a high-level parameter.

[0130] In one example, after a maximum value, a minimum value, or a value of an application delay (e.g., before the next triggering of a MR, before low power signal deactivation, or before expiration of a related timer), the UE is expected to receive and / or transmit a signal and / or channel (e.g., a low power signal), for example, using a LR. The signal and / or channel may be a low power wake-up signal (LP-WUS) or a portion of an LP-WUS, or the signal and / or channel may be a synchronization signal (LP-SS) received by the LR, for example, for synchronization between the gNB and the LR.

[0131] In another example, within a maximum value, a minimum value, or a range of values ​​of the applied delay, the UE is expected not to receive and / or transmit a signal and / or channel (e.g., a low power signal), for example, using the LR. The signal and / or channel may be a LP-WUS or a portion of the LP-WUS, or the signal and / or channel may be a synchronization signal (LP-SS) received by the LR, for example, for synchronization between the gNB and the LR.

[0132] In one embodiment, the measurement process may be determined based on the application delay, and the measurement process includes at least one of RRM, RLM, BM, and BFR.

[0133] In one example, the measurement procedure is applicable to RRC_IDLE and / or RRC_CONNECTED states.

[0134] In one example, within a maximum, minimum, or range of values ​​for the MR application delay, the UE is expected to perform measurements based on signals other than low-power signals, such as using MR. In a further example, the measurements may be based on SS / PBCH blocks or on channel CSI-RS.

[0135] In another example, after a maximum value, a minimum value, or a value of the application delay of the MR (e.g., before the next triggering of the MR, before the low power signal is deactivated, or before the expiration of a related timer), the UE is not expected to perform measurements based on signals other than the low power signal, such as using the MR. In a further example, the measurement can be based on SS / PBCH blocks or based on CSI-RS.

[0136] In yet another example, within a maximum value, a minimum value, or a range of values ​​of the LR application delay, it is not desirable for the UE to perform measurements based on low power signals, e.g., using the LR. In other examples, the measurements may be based on the LP-WUS or a portion of the LP-WUS, or may be based on a synchronization signal (LP-SS) received by the LR, e.g., for synchronization between the gNB and the LR.

[0137] In yet another example, after a maximum value, a minimum value, or a value of a delay applied by the LR (e.g., before the next triggering of the MR, before low power signal deactivation, or before expiration of a related timer), the UE is expected to perform a measurement based on a low power signal, e.g., using the LR. In some examples, the measurement can be based on the LP-WUS or a portion of the LP-WUS, or based on a synchronization signal (LP-SS) received by the LR, e.g., for synchronization between the gNB and the LR.

[0138] In one example, if a time period is included in the LR application delay and not included in the MR application delay (e.g., when D1_LR > D1_MR), the UE is not expected to perform measurements based on the RS within the time period. For example, the measurement requirement may be relaxed based on the time period.

[0139] In another example, if the MR application delay includes a time period that is not included in the LR application delay (e.g., when D1_LR < D1_MR), the UE may perform measurements based on at least one RS from the MR or based on one RS from the LR. In further examples, the measurement may use one RS from the MR (e.g., SS / PBCH block and / or CSI-RS) or one RS from the LR (e.g., LP-WUS or LP-SS), for example, and any instance of the measurement may be used to calculate the L1RSRP or L3 RSRP. In other examples, the measurement may be performed using both an RS from the MR (e.g., SS / PBCH block and / or CSI-RS) and an RS from the LR (e.g., LP-WUS or LP-SS), for example, and both instances of the measurement may be used to calculate the L1RSRP or L3 RSRP.

[0140] In one embodiment, the application delay may be extended based on the UE's reception of the signal and / or channel. For example, if the UE receives a PDCCH, the MR's application delay and / or the LR's application delay may be extended.

[0141] In further examples, the application delay may be: recounted / reset upon receiving a PDCCH (e.g., a timer for the application delay may be restarted); extended to a predefined value upon receiving a PDCCH; extended to a value upon receiving a PDCCH, where the value may be provided by a higher layer; and extended to a value upon receiving a PDCCH, where the value may be provided by a DCI format. For example, the DCI format may be carried by the received PDCCH. In another example, the PDCCH may be a PDCCH used to schedule a PDSCH containing user data. For example, the PDCCH may carry DCI format 1_1 and / or DCI format 1_2. In other examples, the PDCCH may be a PDCCH used to schedule a PUSCH containing user data. For example, the PDCCH may carry DCI format 0_1 ​​and / or DCI format 0_2.

[0142] Figure 7 A flow chart of a method 700 for UE to trigger LR is shown. Figure 7 The illustrated embodiment of method 700 is for illustration only. Figure 7 One or more of the steps shown may be implemented in dedicated circuits configured to perform the functions described, or one or more of the steps may be implemented by one or more processors executing instructions to perform the functions described. Figure 7 The scope of the present disclosure is not limited to any particular implementation of method 700 .

[0143] At step 710, a UE (e.g., 116) receives an explicit signal / channel as a trigger. At step 720, the UE determines a time to perform a transition. At step 730, the UE stops using the MR after a first application delay after receiving the trigger. At step 740, the UE starts using the LR after a second application delay after receiving the trigger.

[0144] Figure 8 A DRX diagram 800 of a LR is shown. Figure 8 The embodiment of schematic diagram 800 shown is for illustration only. Figure 8 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 8 The scope of the present disclosure is not limited to any particular implementation of diagram 800 .

[0145] In one embodiment, a LR (e.g., LR 312) may support DRX, which may be denoted as LR-DRX. For example, the LR may receive signals or channels that are discontinuously received, such as LP-WUS and / or LP-SS. In another example, throughout the remainder of this disclosure, DRX refers to LR-DRX unless explicitly stated otherwise.

[0146] In one example, a set of configurations for DRX may be provided to the UE.

[0147] In one example, the set of DRX configurations can be received by a MR (eg, MR 314).

[0148] In one example, the set of DRX configurations or a portion thereof may be provided to the UE by System Information Block 1 (SIB1).

[0149] In another example, the set of DRX configurations or a portion thereof may be provided to the UE by a system information block x (SIBx), where x>1.

[0150] In yet another example, the set of DRX configurations or a portion thereof may be provided to the UE by a paging message (eg, carried by a paging PDSCH).

[0151] In a further example, the set of DRX configurations or a part thereof may be provided to the UE by a paging short message (eg, carried by a paging PDCCH).

[0152] In other examples, the set of DRX configurations or a portion thereof may be provided to the UE by dedicated RRC signaling (eg, UE-specific RRC signaling).

[0153] In some examples, this set of configurations for DRX may be fixed in the specification.

[0154] In some examples, the set of configurations may include a period such that the active portion and / or the inactive portion of the DRX cycle occur periodically in the time domain with respect to the period. For example, the start of a period may be aligned with a system frame, and may be further aligned with its numbering condition.

[0155] In other examples, the set of configurations may include an offset, for example, defined based on a reference timing. For example, the offset may be an offset between the start of the active portion of the DRX cycle and the start of the cycle. For another example, the offset may be an offset between the active portion of the DRX cycle and a paging occasion. For another example, the offset may be an offset between the active portion of the DRX cycle and a PEI monitoring occasion. For another example, the offset may be an offset between the active portion of the DRX cycle and the ON duration of the DRX cycle. For another example, the offset may be an offset between the active portion of the LR-DRX cycle and the active portion of the MR-DRX cycle.

[0156] In yet another example, the set of configurations may include a duration, such as a duration of an active portion of a DRX cycle or a duration of an inactive portion. For example, the term "active portion of a DRX cycle" may be referred to by other equivalent terms, such as an "ON duration" of a DRX cycle. For another example, the term "inactive portion of a DRX cycle" may be referred to by other equivalent terms, such as an "OFF duration" or an "inactive portion" of a DRX cycle.

[0157] In one example, the LR-DRX configuration can match the configuration of the synchronization signal (e.g., LP-SS) that the LR is to receive. For example, the LP-SS transmission timing can be within the active portion of the DRX cycle. For another example, the LP-SS cycle can be an integer multiple of the DRX cycle. For another example, the duration of the active portion of the DRX cycle can be equal to or greater than the duration of the LP-SS.

[0158] In one example, the LR-DRX configuration can match the configuration of a wake-up signal (e.g., LP-WUS) or a portion of the LP-WUS to be received by the LR. For example, the transmission timing of the LP-WUS or a portion thereof can be within the active portion of the DRX cycle. For another example, the period of the LP-WUS or a portion thereof can be an integer multiple of the DRX cycle. For another example, the duration of the active portion of the DRX cycle can be equal to or greater than the duration of the LP-WUS or a portion thereof.

[0159] In one example, the set of configurations for LR-DRX can match the configuration of DRX on MR (MR-DRX). For example, the active portion of the DRX cycle in LR-DRX can be within the active portion of the DRX cycle in MR-DRX (e.g., the ON duration of MR-DRX in RRC_CONNECTED mode and / or the active duration of MR-DRX in RRC_IDLE / INACTIVE mode). For another example, the cycle of LP-DRX can be an integer multiple of the MR-DRX cycle (e.g., MR-DRX in CONNECTED mode and / or MR-DRX in RRC_IDLE / INACTIVE mode). For another example, the duration of the active portion of the DRX cycle in LP-DRX can be equal to or less than the duration of the active portion of the DRX cycle in MR-DRX (e.g., the ON duration of MR-DRX in RRC_CONNECTED mode and / or the active duration of MR-DRX in RRC_IDLE / INACTIVE mode).

[0160] In one example, there may be at least two LR-DRXs, each associated with a set of LR-DRX configurations. For example, a first LR-DRX may be associated with an LP-SS, and a second LR-DRX may be associated with an LP-WUS (or a portion thereof). For another example, the first LR-DRX may be associated with a first portion of an LP-WUS, and the second LR-DRX may be associated with a second portion of the LP-WUS. For another example, the first LR-DRX may be associated with a first LP-WUS, and the second LR-DRX may be associated with a second LP-WUS. For another example, the at least two sets of configurations for the two LR-DRXs may include common configurations, such as a period, an offset, and / or a duration, which may be common to the at least two LR-DRXs.

[0161] In one embodiment, the UE may attempt to receive at least one of the LP-SS, LP-WUS, or a portion of the LP-WUS based on LR-DRX. In the present disclosure, a reception timing of a signal or channel refers to a time and / or frequency resource allocated to the signal or channel for one reception.

[0162] In one example, LR-DRX may be applicable to both LP-SS and LP-WUS (or a portion thereof). For example, the reception timings of LP-SS and LP-WUS (or a portion thereof) are within the active portion of the LR-DRX DRX cycle. In another example, LR-DRX may be applicable to both the first and second portions of LP-WUS. For example, the reception timings of the first and second portions of LP-WUS are within the active portion of the LR-DRX DRX cycle. In yet another example, LR-DRX may be applicable only to LR-SS, while the reception of LP-WUS (or a portion thereof) may not be based on LR-DRX. For example, the reception timings of LP-WUS (or a portion thereof) may be within the inactive portion of the LR-DRX DRX cycle. In yet another example, LR-DRX may be applicable only to LP-WUS (or a portion thereof), while the reception of LP-SS may not be based on LR-DRX. For example, the reception timings of LP-SS may be within the inactive portion of the LR-DRX DRX cycle. In yet another example, LR-DRX may be applied only to the first portion of the LP-WUS, while the reception of the second portion of the LP-WUS may not be based on LR-DRX. For example, the reception timing of the second portion of the LP-WUS may be within the inactive portion of the DRX cycle of the LR-DRX.

[0163] Figure 9 A schematic diagram 900 is shown showing reception by a UE during a DRX cycle. Figure 9 The embodiment of schematic diagram 900 shown is for illustration only. Figure 9 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 9 The scope of the present disclosure is not limited to any particular implementation of diagram 900 of UE reception during a DRX cycle.

[0164] In example reception 910, within the active portion of each DRX cycle of LR-DRX, there may be a single time-domain reception opportunity for at least one of an LP-SS, an LP-WUS, or a portion of an LP-WUS based on the LR-DRX. This time-domain reception opportunity may be aligned with the active portion of the DRX cycle. For example, the start time of the time-domain reception opportunity may be aligned with the start time of the active portion of the DRX cycle. For another example, the duration of the time-domain reception opportunity may be aligned with the duration of the active portion of the DRX cycle. For another example, the period of the time-domain reception opportunity may be equal to the period of the DRX cycle. The time-domain reception opportunity may be the same as the active portion of the DRX cycle, and there may not be an explicit definition of the DRX cycle.

[0165] In the example reception 920, within the active portion of each DRX cycle of LR-DRX, there may be one or more time domain reception opportunities for at least one of LP-SS, LP-WUS, or a portion of LP-WUS based on LR-DRX.

[0166] In one example, one or more time domain reception opportunities may be continuous in the time domain (e.g., there are no gaps between adjacent reception opportunities). For example, the start time of the first time domain reception opportunity may be aligned with the start time of the active portion of the DRX cycle. For example, the end time of the last time domain reception opportunity may be aligned with the end time of the active portion of the DRX cycle. For another example, the duration of all time domain reception opportunities may be aligned with the duration of the active portion of the DRX cycle. For another example, the period of the time domain reception opportunities may be equal to the period of the DRX cycle.

[0167] In another example, there may be uniform gaps between one or more time-domain reception opportunities. For example, the duration of the gaps may be predetermined in the specification. For another example, the duration of the gaps may be provided by a higher-layer parameter.

[0168] In yet another example, the location of one or more time-domain reception opportunities can be provided based on higher-layer parameters. For example, the location can be determined based on at least an offset between a first reception opportunity and the start of the active portion, where, for example, the offset can be provided by a higher layer. For another example, the location can be determined based on at least an interval between adjacent reception opportunities, where, for example, the interval can be provided by a higher layer. For another example, the location can be determined based on at least a number of reception opportunities, where, for example, the number can be provided by a higher layer or determined based on a number of SS / PBCH blocks (e.g., the number of SS / PBCH blocks actually transmitted in a half-frame).

[0169] In one example, the reception timing of the LP-SS may differ from the reception timing of the LP-WUS (or a portion thereof). In this example, the first example or sub-example of this embodiment may apply to the reception timing of the LP-SS, and the second example or sub-example may apply to the reception timing of the LP-WUS (or a portion thereof).

[0170] In another example, the reception timing of the first portion of the LP-WUS may be different from the reception timing of the second portion of the LP-WUS. In this example, the first example or sub-example of this embodiment may apply to the reception timing of the first portion of the LP-WUS, and the second example or sub-example may apply to the reception timing of the second portion of the LP-WUS.

[0171] In one example, the UE does not expect the reception timing of the LP-SS to overlap (or partially overlap) with the reception timing of the LP-WUS (or a portion of the LP-WUS).

[0172] In another example, if a reception timing of the LP-SS overlaps (or partially overlaps) with a reception timing of the LP-WUS (or a portion of the LP-WUS), the UE may abandon reception of the LP-SS and attempt to receive the LP-WUS (or a portion of the LP-WUS).

[0173] In yet another example, if a reception timing of the LP-SS overlaps (or partially overlaps) with a reception timing of the LP-WUS (or a portion of the LP-WUS), the UE may abandon reception of the LP-WUS (or a portion of the LP-WUS) and attempt to receive the LP-SS.

[0174] In yet another example, if the reception timing of the LP-SS overlaps (or partially overlaps) with the reception timing of the LP-WUS (or a portion of the LP-WUS), the UE may abandon reception of the signal with the later reception timing and attempt to receive the signal with the earlier reception timing.

[0175] In one example, the UE does not expect the reception timing of the first part of the LP-WUS and the reception timing of the second part of the LP-WUS to overlap (or partially overlap).

[0176] In another example, if the reception timing of the LP-WUS first part and the reception timing of the LP-WUS second part overlap (or partially overlap), the UE may abandon reception of the LP-WUS first part and attempt to receive the LP-WUS second part.

[0177] In yet another example, if the reception timing of the LP-WUS first part and the reception timing of the LP-WUS second part overlap (or partially overlap), the UE may abandon reception of the LP-WUS second part and attempt to receive the LP-WUS first part.

[0178] In another example, if the reception timing of the first part of the LP-WUS overlaps (or partially overlaps) with the reception timing of the second part of the LP-WUS, the UE may abandon reception of the signal with the later reception timing and attempt to receive the signal with the earlier reception timing.

[0179] In one example, for RRC_IDLE and / or RRC_INACTIVE mode, the reception opportunity of LP-SS and / or LP-WUS can be associated with the MR-DRX cycle, so that the reception opportunity can be associated with a set of paging opportunities and / or PEI monitoring opportunities in the MR-DRX cycle.

[0180] In another example, for the RRC_CONNECTED mode, the reception opportunity of the LP-SS and / or LP-WUS may be associated with the MR-DRX cycle, such that the reception opportunity may be associated with the ON duration within the MR-DRX cycle.

[0181] Figure 10 A schematic diagram 1000 is shown illustrating an extended active portion of a DRX cycle. Figure 10 The embodiment of schematic diagram 1000 shown is for illustration only. Figure 10 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 10 The scope of the present disclosure is not limited to any particular implementation of the diagram 1000 of extending the active portion of a DRX cycle.

[0182] In one embodiment, the active portion of the DRX cycle of LR-DRX may be extended based on the reception status of the UE using LR.

[0183] In one example, for example, if the UE receives LP-SS during an LP-SS reception opportunity within the active part of the DRX cycle, an extension of the active part of the DRX cycle may be triggered.

[0184] In another example, for example, if the UE receives an LP-WUS at an LP-WUS reception opportunity within the active portion of the DRX cycle, extension of the active portion of the DRX cycle may be triggered. In yet another example, for example, if the UE receives the first part of the LP-WUS at a reception opportunity of the first part of the LP-WUS within the active portion of the DRX cycle, extension of the active portion of the DRX cycle may be triggered.

[0185] In one example, the duration of the extended active portion of the DRX cycle may be predefined in the specification. In another example, the duration of the extended active portion of the DRX cycle may be provided by a higher-layer parameter. In yet another example, the duration of the extended active portion of the DRX cycle may be determined based on the configuration of reception opportunities. For example, the duration may be determined as one or more intervals of reception opportunities. In another example, the duration may be determined as the time difference between the trigger of the extension and the next reception opportunity of an LP-SS, LP-WUS, or a portion of an LP-WUS. The duration may be the time difference between the trigger of the extension and the next reception opportunity of an LP-WUS, where the trigger is reception of an LP-SS. In other examples, the duration may be the time difference between the trigger of the extension and the next reception opportunity of the second portion of an LP-WUS, where the trigger is reception of the first portion of an LP-WUS.

[0186] In yet another example, the duration of the active portion of the DRX cycle extension may be provided in an extension trigger (as described in this disclosure).

[0187] In one example, the reference time instance for starting the extension may be determined as the start time of the reception opportunity at which the extension trigger is received.

[0188] In another example, the reference time instance for initiating the extension may be determined as the end time of the reception opportunity at which the extension trigger is received.

[0189] In another example, the reference time instance for starting extension can be determined as the start time of the time slot containing the reception opportunity for receiving the extension trigger or the time slot overlapping with the reception opportunity for receiving the extension trigger (if the reception opportunity is included in multiple time slots, the first time slot).

[0190] In a further example, the reference time instance for starting the extension can be determined as the end time of the time slot containing the reception opportunity for receiving the extension trigger or the time slot overlapping with the reception opportunity for receiving the extension trigger (if the reception opportunity is included in multiple time slots, the last time slot).

[0191] In another example, the reference time instance for starting the extension can be determined as the starting moment of the OFDM symbol that includes the reception opportunity for receiving the extension trigger or the OFDM symbol that overlaps with the reception opportunity for receiving the extension trigger (or the first OFDM symbol if the reception opportunity is included in multiple OFDM symbols).

[0192] In other examples, the reference time instance for starting the extension can be determined as the end time of the OFDM symbol that includes the reception opportunity for receiving the extension trigger or the OFDM symbol that overlaps with the reception opportunity for receiving the extension trigger (or, if the reception opportunity is included in multiple OFDM symbols, the last OFDM symbol).

[0193] In some examples, the reference time instance for starting the extension may be determined as the end time of the active portion of the DRX cycle (eg, the active portion before the extension).

[0194] In one example, the UE assumes that the end time of the active part of the DRX cycle after extension is the later of the end time of the active part of the DRX cycle before extension and the time after extension (according to the examples of the present disclosure).

[0195] In another example, the UE assumes that the end time of the extended active part of the DRX cycle does not exceed the end time of the corresponding DRX cycle. If the determined end time of the extended active part of the DRX cycle exceeds the end time of the corresponding DRX cycle, the UE truncates the active part so that the end time of the active part is aligned with the end time of the corresponding DRX cycle.

[0196] Figure 11 A schematic diagram 1100 is shown for shortening the active portion of a DRX cycle. Figure 11 The embodiment of schematic diagram 1100 shown is for illustration only. Figure 11 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 11 The scope of the present disclosure is not limited to any particular implementation of diagram 1100 for shortening the active portion of a DRX cycle.

[0197] In one example, for example, if the UE receives LP-SS during an LP-SS reception opportunity within the active part of the DRX cycle, a shortening of the active part of the DRX cycle may be triggered.

[0198] In another example, for example, if the UE receives an LP-WUS at an LP-WUS reception opportunity within the active part of the DRX cycle, a shortening of the active part of the DRX cycle may be triggered.

[0199] In yet another example, if the UE receives the first part of the LP-WUS at a reception opportunity of the first part of the LP-WUS within the active part of the DRX cycle, shortening of the active part of the DRX cycle may be triggered.

[0200] In one example, the duration of the shortened active portion of the DRX cycle may be predefined in the specification.

[0201] In another example, the duration of the shortened active portion of the DRX cycle may be provided by a higher layer parameter.

[0202] In yet another example, the duration of the shortened active portion of the DRX cycle may be determined based on the configuration of the reception opportunities. For example, the duration may be determined as one or more intervals of the reception opportunities.

[0203] In yet another example, the shortened duration of the active portion of the DRX cycle may be provided in a shortening trigger (as described in this disclosure).

[0204] In yet another example, the duration of the shortened active portion of the DRX cycle may be the remaining duration of the active portion of the DRX cycle after receiving the shortening trigger.

[0205] In one example, the reference time instance for initiating shortening may be determined as the start time of a receiving opportunity at which a shortening trigger is received.

[0206] In another example, the reference time instance for initiating the shortening may be determined as the end time of the receiving opportunity at which the shortening trigger is received.

[0207] In another example, the reference time instance for starting shortening can be determined as the start time of the time slot that includes the reception opportunity for receiving the shortened trigger or the time slot that overlaps with the reception opportunity for receiving the shortened trigger (or the first time slot if the reception opportunity is included in multiple time slots).

[0208] In another example, the reference time instance for initiating shortening can be determined as the end time of the time slot containing the reception opportunity for receiving the shortened trigger or the time slot overlapping with the reception opportunity for receiving the shortened trigger (or the last time slot if the reception opportunity is included in multiple time slots).

[0209] In another example, the reference time instance for starting the shortening can be determined as the starting time of the OFDM symbol that includes the reception opportunity for receiving the shortened trigger or the OFDM symbol that overlaps with the reception opportunity for receiving the shortened trigger (or the first OFDM symbol if the reception opportunity is included in multiple OFDM symbols).

[0210] In another example, the reference time instance for initiating shortening can be determined as the end time of the OFDM symbol that includes the reception opportunity for receiving the shortened trigger or the OFDM symbol that overlaps with the reception opportunity for receiving the shortened trigger (or, if the reception opportunity is included in multiple OFDM symbols, the last OFDM symbol).

[0211] In yet another example, the reference time instance for initiating the shortening may be determined as the end time of the active portion of the DRX cycle (eg, the active portion before the shortening).

[0212] Figure 12 A flow chart of a method 1200 of UE procedures based on LR-DRX is shown. Figure 12 The embodiment of schematic diagram 1200 shown is for illustration only. Figure 12 One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described. Figure 12 The scope of the present disclosure is not limited to any particular implementation of the example method 1200 .

[0213] At 1210, a UE (e.g., 116) receives a set of LR-DRX configurations. At 1220, the UE determines the active and inactive portions of the LR-DRX cycle based on the set of configurations. At 1230, the UE determines a reception timing for an LP-SS / LP-WUS based on the LR-DRX. At 1240, the UE receives the LP-SS / LP-WUS based on the reception timings. At 1250, the UE may extend or shorten the active portion of the DRX cycle based on the reception of the LP-SS / LP-WUS.

[0214] Figure 13 is a block diagram of a UE structure according to an embodiment of the present disclosure.

[0215] like Figure 13 As shown, the UE according to one embodiment may include a transceiver 1310, a memory 1320, and a processor 1330. The transceiver 1310, the memory 1320, and the processor 1330 of the UE may operate according to the communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 1330, the transceiver 1310, and the memory 1320 may be implemented as a single chip. And, the processor 1330 may include at least one processor. In addition, Figure 13 UE and Figure 1 Corresponding to the UE in.

[0216] The transceiver 1310, collectively referred to as the UE receiver and UE transmitter, can transmit and receive signals to and from a base station or network entity. Signals transmitted to and received from the base station or network entity may include control information and data. The transceiver 1310 may include an RF transmitter for up-converting and amplifying the frequency of transmitted signals, and an RF receiver for low-noise amplification and down-converting the frequency of received signals. However, this is only one example of the transceiver 1310, and the components of the transceiver 1310 are not limited to RF transmitters and RF receivers.

[0217] In addition, the transceiver 1310 may receive a signal through a wireless channel and output it to the processor 1330 , and may also transmit the signal output by the processor 1330 through a wireless channel.

[0218] The memory 1320 can store programs and data required for UE operation. In addition, the memory 1320 can store control information or data contained in signals obtained by the UE. The memory 1320 can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0219] The processor 1330 may control a series of processes so that the UE operates in the manner described above. For example, the transceiver 1310 may receive a data signal including a control signal sent by a base station or a network entity, and the processor 1330 may determine a result of receiving the control signal and the data signal sent by the base station or the network entity.

[0220] Figure 14 is a block diagram of a base station structure according to an embodiment of the present disclosure.

[0221] like Figure 14 As shown, a base station according to one embodiment may include a transceiver 1410, a memory 1420, and a processor 1430. The transceiver 1410, the memory 1420, and the processor 1430 of the base station may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 1430, the transceiver 1410, and the memory 1420 may be implemented as a single chip. And, the processor 1430 may include at least one processor. In addition, Figure 14 The base station and Figure 1 Corresponding to the BS in.

[0222] Transceiver 1410, collectively referred to as a base station receiver or transmitter, can transmit and receive signals to and from a terminal (UE) or network entity. Signals transmitted to and received from a terminal or network entity may include control information and data. Transceiver 1410 may include an RF transmitter for up-converting and amplifying the frequency of transmitted signals, and an RF receiver for low-noise amplification and down-converting the frequency of received signals. However, this is only one example of transceiver 1410, and the components of transceiver 1410 are not limited to RF transmitters and RF receivers.

[0223] In addition, the transceiver 1410 may receive a signal through a wireless channel and output it to the processor 1430 , and may also transmit the signal output by the processor 1430 through a wireless channel.

[0224] The memory 1420 can store programs and data required for base station operation. In addition, the memory 1420 can store control information or data contained in signals obtained by the base station. The memory 1420 can be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0225] The processor 1430 may control a series of processes so that the base station operates as described above. For example, the transceiver 1410 may receive a data signal including a control signal sent by a terminal, and the processor 1430 may determine the result of receiving the control signal and the data signal sent by the terminal.

[0226] The methods according to the embodiments described in the claims or detailed description of the present disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0227] When the electrical structures and methods are implemented using software, a computer-readable recording medium may be provided, containing one or more programs (software modules). The one or more programs recorded on the computer-readable recording medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions for executing the methods according to the embodiments described in the claims or detailed description of this disclosure.

[0228] Programs (e.g., software modules or software) may be stored in random access memory (RAM), nonvolatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, compact disk read-only memory (CD-ROM), digital versatile disk (DVD), another type of optical storage device, or magnetic tape. Alternatively, the programs may be stored in a storage system that includes a combination of some or all of the aforementioned storage devices. Furthermore, each storage device may consist of multiple devices.

[0229] The program may also be stored on a connectable storage device accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wireless local area network (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected to an apparatus according to an embodiment of the present disclosure via an external port. Another storage device connected to the communication network may also be connected to an apparatus performing an embodiment of the present disclosure.

[0230] In the above-mentioned embodiment of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form according to the embodiment. However, for the convenience of explanation, the singular or plural form is appropriately selected, and the present disclosure is not limited thereto. Therefore, the element expressed in plural form can also be configured as a single element, and the element expressed in singular form can also be configured as multiple elements.

[0231] Although the figures illustrate various examples of user equipment, various modifications may be made to these figures. For example, the user equipment may include any number of components in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration. Furthermore, although the figures illustrate operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0232] At least some of the example embodiments described herein may be implemented in part or in whole using dedicated, special-purpose hardware. Terms such as "component," "module," or "unit" as used herein may include, but are not limited to, hardware devices, such as discrete or integrated circuits, field-programmable gate arrays (FPGAs), or application-specific integrated circuits (ASICs), that perform certain tasks or provide related functionality. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and configured to execute on one or more processors. In some embodiments, these functional elements may include, for example, components (such as software components, object-oriented software components, class components, and task components), processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Although example embodiments have been described with reference to the components, modules, and units discussed herein, these functional elements may be combined into fewer elements or separated into more elements. Various optional feature combinations have been described herein, and it should be understood that the described features may be combined in any suitable combination. In particular, features of any example embodiment may be combined with features of any other embodiment, as appropriate, unless such combinations are mutually exclusive. Throughout the specification, the term “include” or “comprising” means including specified components but not excluding the existence of other components.

[0233] Attention is directed to all papers and documents related to this application and filed contemporaneously with or prior to this specification, which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0234] All features disclosed in this specification (including any accompanying claims, abstract and drawings), and / or all steps of any disclosed method or process, may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive.

[0235] Each feature disclosed in this specification (including any accompanying claims, abstract, and drawings) may, unless expressly stated otherwise, be replaced by an alternative feature serving the same, equivalent, or similar purpose. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a series of equivalent or similar features.

[0236] The invention is not limited to the details of the foregoing embodiments. The invention extends to any novel feature disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel feature of the steps of any disclosed method or process, or to any novel combination of those steps.

[0237] Any of the above-mentioned variations can be used alone or in combination with at least one other variation.

[0238] The above flowcharts illustrate example methods that can be implemented according to the principles of the present disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each figure can overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0239] Although the present disclosure has been described in conjunction with exemplary embodiments, various changes and modifications may be proposed by those skilled in the art. The present disclosure is intended to cover such changes and modifications as fall within the scope of the appended claims. Nothing in this application should be construed as implying that any particular element, step, or function is essential to the scope of the claims. The scope of patent protection is defined by the claims.

Claims

1. A terminal in a wireless communication system, the terminal comprising: a transceiver configured to receive a physical downlink control channel (PDCCH); Low power receiver LR; as well as A controller connected to the transceiver and the LR, the controller being configured to: Determining a downlink control information (DCI) format based on the PDCCH, where the DCI format includes an indication of whether to activate the LR to receive a low power wake-up signal (LP-WUS); Determining, based on the indication in the DCI format, to activate the LR; as well as Determine the timing of LP-WUS monitoring, The LR is configured to receive the LP-WUS based on the monitoring opportunity.

2. The terminal according to claim 1, wherein: The PDCCH is received based on a common search space (CSS) set.

3. The terminal according to claim 1, in, The controller is further configured to: determine an application delay associated with reception of the PDCCH, The monitoring timing of the LP-WUS is determined to be after the application delay, The controller is further configured to: determine a set of signals for radio resource management RRM before applying the delay, and The group of signals is not measured by the terminal. The terminal according to claim 1 , wherein: The monitoring opportunity of the LP-WUS is within the active part of the discontinuous reception DRX cycle of the LR, wherein the controller is further configured to determine a configuration of the active portion of the DRX cycle based on higher layer parameters, and The configuration includes: DRX period value, the duration of the active component, and The active portion is offset within the DRX cycle.

5. A base station (BS) in a wireless communication system, the BS comprising: transceiver; A controller connected to the transceiver, the controller being configured to: determining a downlink control information DCI format, the DCI format including an indication of whether to activate a low power receiver and transmit a low power wake-up signal LP-WUS; and Determine the timing of LP-WUS monitoring; Sending a physical downlink control channel PDCCH containing the DCI format; and The LP-WUS is sent based on the monitoring timing of the LP-WUS. The BS according to claim 5 , wherein: The PDCCH is sent based on a common search space (CSS) set.

7. The BS according to claim 5, wherein: The controller is further configured to: determining an application delay associated with the transmission of the PDCCH, determining a set of signals for radio resource management RRM prior to applying said delay, The monitoring timing of the LP-WUS is determined to be after the application delay, and The group of signals is not measured by the terminal.

8. The BS according to claim 5, wherein: The monitoring opportunity of the LP-WUS is within the active part of the discontinuous reception DRX cycle of the LR, Wherein, the controller is further configured as: determining a configuration of the active portion of the DRX cycle; and Including said configuration in high-level parameters; The configuration includes: DRX period value, the duration of the active component, and The active portion is offset within the DRX cycle.

9. A method for a terminal in a wireless communication system, the method comprising: Receiving a physical downlink control channel PDCCH; Determining a downlink control information DCI format based on the PDCCH, wherein the DCI format includes an indication of whether to activate a low power receiver LR to receive a low power wake-up signal LP-WUS; Determining, based on the indication in the DCI format, to activate the LR; Determine the timing of LP-WUS monitoring; as well as An LP-WUS is received based on the monitoring opportunity.

10. The method according to claim 9, wherein: The PDCCH is received based on a common search space (CSS) set.

11. The method according to claim 9, further comprising: determining an application delay associated with reception of the PDCCH, The monitoring timing of the LP-WUS is determined to be after the application delay. determining a set of signals for radio resource management (RRM) prior to applying said delay, and The group of signals is not measured by the terminal.

12. The method according to claim 9, wherein The monitoring opportunity of the LP-WUS is within the active part of the discontinuous reception (DRX) cycle of the LR, and The method further comprises: Determining a configuration of the active part of the DRX cycle based on higher layer parameters, wherein the configuration comprises: DRX period value, the duration of the active component, and an offset of the active portion within the DRX cycle; receiving a duration based on higher layer parameters; receiving a low power synchronization signal LP-SS; and After receiving the LP-SS, determining to extend the active portion of the DRX cycle by the duration.

13. A method for a base station BS in a wireless communication system, the method comprising: Determining a downlink control information (DCI) format, wherein the DCI format includes an indication of whether to activate a low power receiver and transmit a low power wake-up signal (LP-WUS); as well as Determine the timing of LP-WUS monitoring; Sending a physical downlink control channel PDCCH containing the DCI format; and The LP-WUS is sent based on the monitoring timing of the LP-WUS.

14. The method according to claim 13, wherein The PDCCH is sent based on a common search space (CSS) set.

15. The method according to claim 13, further comprising: determining an application delay associated with the transmission of the PDCCH, determining a set of signals for radio resource management RRM prior to applying said delay, The monitoring timing of the LP-WUS is determined to be after the application delay, and The set of signals is not measured by the terminal.

Images