New radio wake-up radio components

Abstract

This invention discloses apparatus, systems, and methods for waking up radio components in wireless communication systems, such as in 5G NR systems and later versions. RRC states are introduced to support waking up radio components, including defining a transition mechanism to / from an existing RRC state. Furthermore, signaling is introduced to activate the waking up radio component / activate the RRC low-power state. Additionally, a bandwidth portion framework for the wake-up signal is defined, wherein the base station can configure one or more time / frequency resources or wake-up signals for waking up the radio component. Furthermore, various mechanisms are introduced to turn on and off the waking up radio component. Moreover, mechanisms are introduced for multiplexing multiple wake-up signals in time / frequency resources, configuring wake-up signal bandwidth, and configuring on which beams the wake-up signal can be received.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for waking up radio components in wireless communication systems, such as in 5G NR systems and later versions.

[0002] Related technical descriptions

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0004] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their user base. LTE was first proposed in 2004 and first standardized in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand from wireless network operators has increased to support higher capacity for a higher density of mobile broadband users. Therefore, research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.

[0005] Compared to LTE, 5G-NR (also known as NR) offers higher capacity for higher density mobile broadband users, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling compared to current LTE. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention

[0006] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for waking up radio components in wireless communication systems, such as in 5G NR systems and later versions.

[0007] For example, in some cases, additional Radio Resource Control (RRC) states may be introduced to support wake-up radio components and / or wake-up signals, including defining transition mechanisms between RRC low-power states (e.g., low-power and / or ultra-low-power RRC states where the wake-up radio component is active) and existing RRC states (e.g., idle, connected, and / or inactive where the primary communication radio component, such as the primary cellular radio component, is active). As another example, in some cases, various signaling (e.g., physical layer, MAC CE signaling, and / or RRC signaling) may be introduced to activate the wake-up radio component and / or activate the RRC low-power state. Furthermore, in some cases, a bandwidth portion framework for the wake-up signal may be defined, where the base station can configure one or more time and / or frequency resources or wake-up signals for the wake-up radio component. Still further, in some cases, various mechanisms may be introduced to trigger the UE to turn on the wake-up radio component (and turn off the primary communication radio component) and to trigger the UE to turn off the wake-up radio component (and turn on the primary communication radio component). Other examples include mechanisms for multiplexing multiple wake-up signals in time / frequency resources and configuring wake-up signal bandwidth (e.g., based on the UE's signal-to-noise ratio) and configuring on which beam the wake-up signal can be received (e.g., beam scheduling).

[0008] In some implementations, the UE can operate in a first RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state), in which the UE's primary communication radio component can be powered on and the UE's wake-up radio component can be powered off. Additionally, while operating in the first RRC state, the UE can receive a signal indicating a transition to a second RRC state (e.g., RRC low power state), in which the UE's primary communication radio component can be powered off and the UE's wake-up radio component can be powered on. This signal can be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. Furthermore, the UE can transition to the second RRC state based on the received signal. Therefore, the UE can power on the wake-up radio component and power off the primary communication radio component.

[0009] In some implementations, the UE can operate in a first RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state), in which the UE's primary communication radio component can be powered on and the UE's wake-up radio component can be powered off. Additionally, the UE can receive configurations from the base station for monitoring one or more time and frequency resources for the wake-up radio component. Furthermore, after transitioning to a second RRC state (e.g., RRC low power state), the UE can monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources, in which the UE's primary communication radio component can be powered off and the UE's wake-up radio component can be powered on.

[0010] In some implementations, the UE can operate in a first RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state), in which the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. Additionally, the UE can monitor the format of a first downlink control indicator (DCI) on the group common physical downlink control channel (PDCCH) for a duration. Furthermore, the UE can, for example, transition to a second RRC state based on this monitoring. In other words, the UE can transition to the second RRC state while detecting and decoding the first DCI format. Therefore, the UE can power on the wake-up radio component and power off the primary communication radio component.

[0011] In some implementations, when operating in a low-power RRC state, the UE can monitor a configured bandwidth portion of the wake-up signal. In this low-power RRC state, the UE's primary communication radio component can be powered down, and the UE's wake-up radio component can be powered on. Additionally, the UE can transition to another RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state) upon receiving a wake-up signal. In this other RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered down.

[0012] In some implementations, the UE can operate in a first RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state), in which the UE's primary communication radio component can be powered on and the UE's wake-up radio component can be powered off. Additionally, while operating in the first RRC state, the UE can receive a signal multiplexed with one or more other signals in time and frequency resources and indicating a transition to a second RRC state (e.g., RRC low power state), in which the UE's primary communication radio component can be powered off and the UE's wake-up radio component can be powered on. Furthermore, the UE can transition to the second RRC state based on the received signal. Therefore, the UE can power on the wake-up radio component and power off the primary communication radio component.

[0013] In some implementations, the UE can operate in a first RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state), in which the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. Additionally, the UE can report the signal-to-noise ratio (SNR) to the base station. Furthermore, the UE can receive from the base station a configuration of the bandwidth of the signal indicating a transition to a second RRC state, wherein the signal bandwidth can be based on the SNR reported by the UE. Moreover, when operating in the first RRC state, the UE can monitor the signal bandwidth.

[0014] In some implementations, the UE can receive beamscheduling of the wake-up signal from the base station. Additionally, when operating in a low-power RRC state, the UE can monitor the wake-up signal, for example, based on beamscheduling, in which the UE's primary communication radio component can be powered down and the UE's wake-up radio component can be powered on. Furthermore, the UE can transition to another RRC state (e.g., RRC idle state, RRC inactive state, and / or RRC connected state) upon receiving the wake-up signal, in which the UE's primary communication radio component can be powered on and the UE's wake-up radio component can be powered down.

[0015] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.

[0016] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0017] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0018] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0019] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0020] Figure 2 An exemplary block diagram of a base station according to some implementation schemes is shown.

[0021] Figure 3 An exemplary block diagram of a server according to some implementation schemes is shown.

[0022] Figure 4 An exemplary block diagram of a UE according to some implementation schemes is shown.

[0023] Figure 5 An example block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0024] Figure 6A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN.

[0025] Figure 6B An example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.

[0026] Figure 7 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0027] Figure 8A An example of reducing UE power consumption by monitoring wake-up signals is shown.

[0028] Figure 8B An example of a dedicated search space for wake-up signals is shown.

[0029] Figure 9 An example of an RRC status is shown.

[0030] Figure 10A and Figure 10B An example of an RRC state machine that can be implemented by a UE according to some implementation schemes is shown.

[0031] Figure 11A , Figure 11B and Figure 11C Examples of various bandwidth configurations for wake-up radio component monitoring are shown according to some implementation schemes.

[0032] Figure 12A , Figure 12B and Figure 12C Examples of various schemes for monitoring wake-up radio components are shown, according to some implementation schemes.

[0033] Figure 13A and Figure 13B Examples of various schemes for triggering the transition of a UE from RRC state to wake-up radio component activity state are shown, according to some implementation schemes.

[0034] Figure 14A , Figure 14B and Figure 14C Examples of various schemes for triggering the transition of a UE from the wake-up radio component active state to the RRC state are shown, according to some implementation schemes.

[0035] Figure 15A and Figure 15B Examples of various schemes for multiplexing wake-up signals according to some implementation schemes are shown.

[0036] Figure 16 An example of a UE packet for wake-up signal bandwidth monitoring according to some implementation schemes is shown.

[0037] Figure 17 A block diagram is shown as an example of a method for operating a UE's wake-up radio component according to some implementation schemes.

[0038] Figure 18 A block diagram of another example of a method for operating a UE's wake-up radio component according to some implementation schemes is shown.

[0039] Figure 19 A block diagram illustrating an example of a method for monitoring DCI format as part of a wake-up radio component for operating a UE, according to some implementation schemes.

[0040] Figure 20A block diagram illustrating an example of a method for monitoring a wake-up signal via a wake-up radio component of a UE, according to some embodiments, is shown.

[0041] Figure 21 A block diagram of another example of a method for operating a UE's wake-up radio component according to some implementation schemes is shown.

[0042] Figure 22 A block diagram is shown as yet another example of a method for operating a wake-up radio component of a UE according to some embodiments.

[0043] Figure 23 A block diagram is shown as another example of a method for monitoring wake-up signals via the wake-up radio component of a UE, according to some implementation schemes.

[0044] Figures 16 to 19 An example block diagram of a method for configuring initial access communication according to some implementation schemes is shown.

[0045] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0046] acronym

[0047] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0048] 3GPP: Third Generation Partnership Project

[0049] UE: User Equipment

[0050] RF: Radio Frequency

[0051] ·BS: Base Station

[0052] DL: Downlink

[0053] ·UL: Uplink

[0054] LTE: Long Term Evolution

[0055] NR: New Radio

[0056] ·5GS: 5G system

[0057] ·5GMM: 5GS Mobility Management

[0058] ·5GC / 5GCN: 5G Core Network

[0059] SIM: User Identity Recognition Module

[0060] eSIM: Embedded User Identity Module

[0061] ·IE: Information Elements

[0062] ·CE: Control Element

[0063] MAC: Media Access Control

[0064] •SSB: Synchronization Signal Block

[0065] • PDCCH: Physical Downlink Control Channel

[0066] • PDSCH: Physical Downlink Shared Channel

[0067] •RRC: Radio Resource Control

[0068] the term

[0069] The following is a glossary of terms used in this disclosure:

[0070] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media that may reside in different locations on different computer systems connected via a network, for example. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0071] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0072] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0073] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0074] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by the user and capable of wireless communication.

[0075] Base station—The term “base station” has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0076] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0077] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0078] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.

[0079] Wi-Fi—The term “Wi-Fi” (or WiFi) has the full range of its usual meaning and includes at least wireless communication networks or RATs that are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are different from cellular networks.

[0080] 3GPP access refers to access technologies (e.g., radio access technologies) specified by 3GPP standards. These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.

[0081] Non-3GPP access refers to any access technology (e.g., radio access technologies) not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be categorized into two types: "trusted" and "untrusted." Trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.

[0082] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0083] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0084] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0085] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0086] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC §112(f) for that component.

[0087] Figure 1A and 1B Communication system

[0088] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0089] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0090] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0091] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".

[0092] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0093] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0094] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-N as shown in Figure 1, each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base station), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. Such cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, base stations 102A to 102B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0095] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0096] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0097] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

[0098] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.

[0099] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0100] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0101] Figure 2 Block diagram of a base station

[0102] Figure 2 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 204 capable of executing program instructions specific to base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0103] Base station 102 may include at least one network port 270. Network port 270 may be configured to be coupled to a telephone network and provide access rights as described above in Figure 1 and... Figure 2 The telephone network as described herein includes multiple devices (such as UE device 106).

[0104] Network port 270 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 270 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0105] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0106] Base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0107] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0108] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 204 of base station 102 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of base station 102 may be configured to implement or support some or all of the features described herein.

[0109] Furthermore, as described herein, processor 204 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 204. Therefore, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.

[0110] Additionally, as described herein, the radio component 230 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 230. Therefore, the radio component 230 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 230. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 230.

[0111] Figure 3 Server block diagram

[0112] Figure 3 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 3 The server described is merely one example of a possible server. As shown, server 104 may include processor 344 capable of executing program instructions specific to server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuitry or devices.

[0113] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.

[0114] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.

[0115] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

[0116] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0117] Figure 4 : UE block diagram

[0118] Figure 4An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 4 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 400 may be implemented as individual components or groups of components for various purposes. This set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0119] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 460 that may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). TM The communication device 106 may include wired communication circuitry (not shown), such as a network interface card for Ethernet, for example. (Including WLAN circuitry) and wake-up radio component circuitry 431. In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as a network interface card for Ethernet, for example.

[0120] Cellular communication circuitry 430 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, short-to-medium-range wireless communication circuitry 429 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 437 and 438, or as an alternative, to antennas 435 and 436. Wake-up radio component circuitry 431 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 439a and 439b as shown. Alternatively, wake-up radio component circuitry 431 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 435 and 436, or as an alternative, to antennas 439a and 439b, or as an alternative, to antennas 439a and 439b. The short-to-medium-range wireless communication circuit 429 and / or the cellular communication circuit 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration. The wake-up radio component circuit 431 may include a wake-up receiver; for example, the wake-up radio component circuit 431 may be a wake-up receiver. In some cases, the wake-up radio component circuit 431 may be a low-power and / or ultra-low-power wake-up receiver. In some cases, the wake-up radio component circuit may be powered on / activated only when the cellular communication circuit 430 and / or the short-to-medium-range wireless communication circuit 429 are in a sleep / unpowered / inactive state. In some cases, the wake-up radio component circuit 431 may (e.g., periodically) monitor a specific frequency / channel for a wake-up signal. Receiving a wake-up signal may trigger the wake-up radio component circuit 431 (e.g., directly and / or indirectly) to notify the cellular communication circuit 430 to enter a powered-on / active state.

[0121] In some embodiments, as further described below, the cellular communication circuit 430 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 430 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.

[0122] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.

[0123] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0124] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

[0125] As shown in the figure, the SOC 400 may include a processor 402 and a display circuit 404. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or coupled to other circuitry or devices (such as the display circuit 404, short-to-medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.

[0126] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for revoking and / or modifying user consent in the MEC, for example, in 5G NR systems and later, as further described herein. For example, communication device 106 can be configured to perform methods for CORESET#0 configuration, SSB / CORESET#0 multiplexing mode 1 of hybrid SCS, time-domain RO determination of 480kHz SCS / 960kHz SCS, and RA-RNTI determination of 480kHz SCS / 960kHz SCS.

[0127] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 402 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, processor 402 of communication device 106 may be configured to implement some or all of the features described herein.

[0128] Furthermore, as described in this invention, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0129] Furthermore, as described herein, the cellular communication circuit 430 and the short-to-medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-to-medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 429.

[0130] Figure 5 Block diagram of cellular communication circuit

[0131] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.

[0132] Cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a-435b and 436 are shown in the diagram. In some embodiments, the cellular communication circuitry 530 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0133] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0134] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0135] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0136] In some implementations, the cellular communication circuit 530 may be configured to perform, for example, methods for waking up radio components in wireless communication systems in 5G NR systems and later versions, as further described herein. For example, the cellular communication circuit 530 may support additional RRC states introduced to support wake-up radio components and / or wake-up signals; various signaling (e.g., physical layer, MAC CE signaling, and / or RRC signaling) for activating wake-up radio components and / or activating RRC low-power states; and various mechanisms for triggering the UE to turn on the wake-up radio component (and turn off the cellular communication circuit 530) and triggering the UE to turn off the wake-up radio component (and turn on the cellular communication circuit 530).

[0137] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0138] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0139] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0140] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0141] Figure 6A , Figure 6B and Figure 7 5G Core Network Architecture—Interoperability with Wi-Fi

[0142] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). Figure 6AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP Interoperability Function (N3IWF) 603 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 605 of the 5G CN. AMF 605 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register for access simultaneously via gNB 604 and AP 612. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 620, Short Message Service Function (SMSF) 622, Application Function (AF) 624, Unified Data Management (UDM) 626, Policy Control Function (PCF) 628, and / or Authentication Server Function (AUSF) 630). It should be noted that these functional entities can also be supported via the 5G CN's Session Management Functions (SMF) 606a and SMF 606b. AMF 605 can connect to (or communicate with) SMF 606a. Furthermore, gNB 604 can communicate with (or connect to) User Plane Function (UPF) 608a, which can also communicate with SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.

[0143] Figure 6BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., such as UE106) can access the 5G CN via both a radio access network (RAN, such as gNB 604 or eNB 602, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to the AMF 605 of the 5G CN. AMF 605 may include an instance of 5G MM functionality associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 612. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). As shown, eNB 602 may have connections to both Mobility Management Entity (MME) 642 and Service Gateway (SGW) 644. MME 642 may have connections to both SGW 644 and AMF 605. Furthermore, SGW 644 may have connections to both SMF 606a and UPF 608a. As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that UDM 626 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 606a and SMF 606b. The AMF 606 can connect to (or communicate with) the SMF 606a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 608a, which in turn can communicate with the SMF 606a. Similarly, the N3IWF 603 can communicate with the UPF 608b, which in turn can communicate with the SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the IMS core network 610.

[0144] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, such as those used in 5G NR systems and later, including mechanisms for waking up radio components in wireless communication systems, such as those further described herein.

[0145] Figure 7 An example of a baseband processor architecture for a UE (e.g., such as UE 106) according to some implementation schemes is shown. Figure 7 The baseband processor architecture 700 described herein may be implemented on one or more radio components (e.g., radio components 429 and / or 430) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include a communication connection with a traditional access stratum (AS) 770. The 5G NAS 720 may include communication connections with a 5G AS 740 and a non-3GPP AS 730, as well as a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as Short Message Service (SMS) entity 752, Evolved Packet System (EPS) Session Management (ESM) entity 754, Session Management (SM) entity 756, EPS Mobility Management (EMM) entity 758, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 760. Furthermore, the traditional AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.

[0146] Therefore, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0147] It should be noted that, in various implementations, one or more of the functional entities described above in the 5G NAS and / or 5G AS may be configured to perform methods for waking up radio components in wireless communication systems, such as those described further herein.

[0148] Wake-up radio components

[0149] In current implementations, UE battery life is a crucial aspect of user experience. Furthermore, compared to 4G systems (e.g., LTE), cellular systems (e.g., 5G NR systems) offer increased complexity, flexibility, wider bandwidth, and higher data rate support. These aspects of 5G NR systems can lead to increased power consumption and the potential for overheating. However, by optimizing the time, frequency, spatial, and device domain characteristics of 5G NR, for example, it achieves a higher target energy efficiency than LTE.

[0150] To further conserve power, 5G NR Release 16 introduces a Wake-Up Signal (WUS) in Radio Resource Control (RRC) connected mode to indicate whether the UE should wake up during the upcoming Connected Mode Discontinuous Receive Cycle (CDRX) on-duration. Therefore, when the UE receives the Wake-Up Signal, it can monitor the Physical Downlink Control Channel (PDCCH) for the subsequent CDRX on-duration. However, if the UE does not receive the Wake-Up Signal, it can skip PDCCH monitoring for the subsequent CDRX on-duration. Therefore, as... Figure 8A As shown, the UE can reduce power consumption by monitoring the wake-up signal instead of monitoring the PDCCH during the CDRX on-time. As illustrated, monitoring the PDCCH during the CDRX on-time consumes more power than monitoring the PDCCH itself, because monitoring the wake-up signal requires less power and has a shorter duration compared to monitoring the PDCCH during the CDRX on-time. Furthermore, as... Figure 8B As shown, 5G NR Release 16 introduces a dedicated search space (window) for the wake-up signal and a minimum gap between the end of the dedicated search space and the start of the CDRX on-time duration. Furthermore, as shown, 5G NR Release 16 introduces an offset from the start of the CDRX on-time duration to define the start of the dedicated search space. Additionally, the wake-up signal is defined as a DCI format 2_6 that can be configured by the primary or secondary cell. DCI format 2_6 is further defined as power-saving information containing UE-specific configurations for one or more UEs. Therefore, the UE is configured to begin monitoring DCI format 2_6 at an offset before the start of the CDRX on-time duration until the end of the configured monitoring window. It should be noted that this mechanism only applies to long CDRXs and not short CDRXs.

[0151] In addition, such as Figure 9 As shown, an RRC inactive state is introduced, in which the RRC context and core network connectivity are maintained. The RRC inactive state preserves all the information needed for rapid connection recovery, including security, and allows for a faster transition to the RRC connected state, while allowing the UE to remain in a lower power state than required by the RRC connected state. In comparison, in the RRC connected state, the UE can transmit data, maintain and / or establish the RRC context, and maintain the core network connectivity, while in the RRC inactive state, the UE cannot transmit data, but does maintain and / or establish the RRC context and maintain the core network connectivity. In the RRC idle state, the UE cannot transmit data, does not maintain and / or establish the RRC context, and does not maintain the core network connectivity.

[0152] Further power-saving enhancements are under discussion, including potential support for ultra-low power UE wake-up signals via wake-up radio components / receivers. However, many considerations exist associated with the introduction of such wake-up radio components / receivers (e.g., WUR) and ultra-low power UE wake-up signals (WUS). For example, there are concerns about WURs, how they will fit into existing NR frameworks, and / or how to turn WURs on / off. Also, there are concerns about WUSs, their bandwidth and multiplexing structure, and / or how WUSs will be transmitted in beam-based systems.

[0153] The embodiments described herein provide systems, methods, and mechanisms for wake-up signals in cellular communication systems. For example, in some cases, additional Radio Resource Control (RRC) states may be introduced to support WUR / WUS, including defining transition mechanisms between RRC WUR states (e.g., low-power and / or ultra-low-power RRC states) and existing RRC states (e.g., idle, connected, and / or inactive). As another example, in some examples, various signaling (e.g., physical layer, MAC CE signaling, and / or RRC signaling) may be introduced to activate the WUR and / or activate the RRC WUR state. Furthermore, in some cases, a bandwidth portion (BWP) framework for the wake-up signal may be defined, where the base station can configure one or more time and / or frequency resources of the WUR or the wake-up signal. Still further, in some cases, various mechanisms may be introduced to trigger the UE to turn on the WUR (and turn off the primary cellular radio component and / or primary communication radio component (PCR)) and to trigger the UE to turn off the WUR (and turn on the PCR). Other examples include mechanisms for multiplexing multiple WUS in time / frequency resources and configuring WUS bandwidth (e.g., based on the signal-to-noise ratio (SNR) of a UE such as UE 106) and configuring on which beams WUS can be received (e.g., beam scheduling).

[0154] Figure 10A An example of an RRC state machine that can be implemented by a UE such as UE 106 according to some embodiments is shown. As shown, the UE can move from a power-on state 1010 to an RRC idle state 1020 via a power-on action 1012, in which at least the primary cellular radio component of the UE is powered on. From the RRC idle state 1020, the UE can transition to the RRC connected state 1030 via an RRC connection procedure 1024, or to the RRC inactive state 1040 via an RRC connection failure 1026. Additionally, the UE can move from the RRC idle state 1020 to the RRC low-power state 1050 via a WUR turn-on action 1022. Note that in the RRC low-power state 1050, the primary cellular radio component can be powered off, and the UE's wake-up radio component / receiver can be powered on. In some examples, the WUR turn-on action 1022 may include receiving any of a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. Physical layer signals may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified in 3GPP Release 17. The DCI may be DCI format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be a wake-up signal as specified in 3GPP Release 16. Alternatively and / or in addition, the DCI may be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, and / or any other DCI format X_Y). It should be noted that such a DCI format (e.g., DCI format X_Y) may be UE-specific. It should also be noted that the UE-specific DCI format can indicate a bandwidth portion switching. Once in low-power RRC state 1050, the UE can transition back to RRC idle state 1020 via WUR shutdown action 1052. In some cases, WUR shutdown action 1052 may include transmitting evidence of receiving a wake-up signal to the base station.

[0155] Continuing to RRC Connected State 1030, once the UE is in RRC Connected State 1030, the UE can transition to RRC Idle State 1030 via RRC Departure Procedure 1034, or to RRC Inactive State 1040 via RRC Suspension Procedure 1034. Additionally, the UE can move from RRC Connected State 1030 to RRC Low Power State 1050 via WUR Action 1032. In some examples, WUR Turn-On Action 1032 may include receiving any of the following: physical layer signals, Media Access Control (MAC) control elements (CE), and / or RRC messages. Physical layer signals may include at least one of the following: Downlink Control Indicator (DCI) received via the Physical Downlink Control Channel (PDDCH) and / or signals including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The DCI may be DCI format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be a wake-up signal as specified by 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth portion handover. Once in low-power RRC state 1050, the UE can transition back to RRC connected state 1030 via WUR shutdown action 1054. In some cases, WUR shutdown action 1054 may include transmitting evidence of a received wake-up signal to the base station.

[0156] Continuing to RRC Inactive State 1040, once the UE is in RRC Inactive State 1040, the UR can transition to RRC Connected State 1030 via RRC Recovery Procedure 1044. Alternatively, the UE can move from RRC Inactive State 1040 to RRC Low Power State 1050 via WUR Turn-On Action 1042. In some examples, WUR Turn-On Action 1042 may include receiving any of the following: physical layer signals, Media Access Control (MAC) Control Element (CE), and / or RRC messages. Physical layer signals may include at least one of the following: Downlink Control Indicator (DCI) received via Physical Downlink Control Channel (PDDCH) and / or signals including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The DCI may be DCI Format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be a wake-up signal as specified by 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format may indicate a bandwidth portion switching. Once in the low-power RRC state 1050, the UE can transition back to the RRC inactive state 1040 via WUR shutdown action 1056. In some cases, WUR shutdown action 1056 may include transmitting evidence of a received wake-up signal to the base station.

[0157] It should be noted that the UE can enter the RRC low power state 1050 from any of the RRC idle state 1020, RRC connected state 1030, and / or RRC inactive state 1040, and can then return from the RRC low power state 1050 to any of these states. In other words, the UE can transition from any RRC state to the RRC low power state 1050, and then return to the same RRC state or a different RRC state.

[0158] Figure 10BAnother example of an RRC state machine that can be implemented by a UE such as UE 106 according to some implementation schemes is shown. As shown, the UE can move from a power-on state 1010 to a PCR RRC state 1060 via a power-on action 1012, in which at least the primary cellular / communication radio component of the UE is powered on. Note that the PCR RRC state can be any of an RRC idle state, an RRC connected state, or an RRC inactive state, as well as any other RRC state in which at least the primary cellular / communication radio component of the UE is powered on. The UE can transition from the PCR RRC state 106 to an RRC low-power state 1050 via a WUR turn-on action 1062. Note that in the RRC low-power state 1050, the primary cellular radio component can be powered off, and the UE's wake-up radio component / receiver can be powered on. In some examples, the WUR turn-on action 1062 may include receiving any of a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. Physical layer signals may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified in 3GPP Release 17. The DCI may be DCI format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be a wake-up signal as specified in 3GPP Release 16. Alternatively and / or in addition, the DCI may be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, and / or any other DCI format X_Y). It should be noted that such a DCI format (e.g., DCI format X_Y) may be UE-specific. It should also be noted that the UE-specific DCI format can indicate a bandwidth portion switching. Once in low-power RRC state 1050, the UE can transition back to PCR RRC state 1060 via WUR shutdown action 1064. In some cases, WUR shutdown action 1064 may include transmitting evidence of receiving a wake-up signal to the base station.

[0159] In some implementations, a base station such as base station 102 may configure one or more time and / or frequency resources and / or wake-up signals for the wake-up radio component of a UE such as UE 106. It should be noted that this may be a subset of the channel bandwidth configured for the primary cellular radio component of the UE, rather than the entire channel bandwidth configured for the primary cellular radio component. In some cases, the base station may configure 4+X bandwidth portions, where four bandwidth portions are used for normal transmission (e.g., for the primary cellular radio component), and X bandwidth portions are defined for wake-up radio component operation. For example, in some cases, the base station may configure only one bandwidth portion for wake-up radio component operation, such as... Figure 11A As shown in the figure, the first bandwidth portion (BWP) can be configured for primary cellular radio component (PCR) communication, such as the BWP for PCR 1120, and the second BWP can be configured for wake-up radio component operation, such as the BWP for wake-up signal (WUS) and RRM procedure 1110. In other cases, the base station can configure more than one bandwidth portion for wake-up radio component operation and radio resource management procedures, such as for signal / channel discovery (e.g., for neighboring cell discovery), for example... Figure 11B and Figure 11C As shown. Figure 11B As shown, in some cases, the BWP for WUS (e.g., the BWP for WUS 1130) and the BWP for the RRM process (e.g., the BWP for RRM process 1132) can be configured to have the same bandwidth. Figure 11CAs shown, in some cases, the BWP for WUS (e.g., the BWP for WUS 1140) and the BWP for the RRM procedure (e.g., the BWP for RRM procedure 1142) can be configured on different bandwidths. It should be noted that the configured bandwidth portion can be narrowband to accommodate narrowband wake-up signals (e.g., signaling such as on-off key signaling). In some cases, the bandwidth portion size can be fixed as a multiple of a fixed bandwidth, where all wake-up signals are configured at the same bandwidth. It should be noted that the bandwidth portion size can be fixed as a multiple because multi-carrier on-off key (OOK) signals can be transmitted with the same guard band between each OOK signal. In some cases, the bandwidth portion size can be configurable (semi-static and / or dynamic) to accommodate UE-specific (and / or UE group) wake-up signal bandwidth and UE-specific (and / or UE group) guard band. Additional bandwidth subcarrier spacing can be fixed and / or configurable, for example, based on frequency bands. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. Similarly, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. And again, when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. In some cases, the bandwidth portion subcarrier spacing can be configured as part of the bandwidth portion configuration. However, it may not be necessary to define parameters such as pdcch-ConfigCommon, pdsch-ConfigCommon, sps-Config, and / or radioLinkMonitoringConfig, because wake-up signal / wake-up radio component configuration parameters, such as discovery channel parameters, wake-up signal data rate, etc., may already be defined. It should be noted that in some cases, all symbols may be defined as downlink symbols. In other words, uplink and / or flexible symbols may not be defined.

[0160] In some implementations, a group common PDCCH such as DCI (e.g., modified DCI format 2_6) can be used to switch a UE, such as UE 106, from a mode in which the UE's primary cellular radio components are active (e.g., RRC states such as RRC connected, RRC idle, and / or RRC inactive) to a mode in which the primary cellular radio components are inactive and the UE's wake-up radio components are active. For example, the UE may monitor DCI at a configured offset (e.g., ps_offset) before the start of the CDRX on duration until the end of the configured monitoring range (e.g., for a configured duration). In some cases, such as... Figure 12AAs shown, the UE can monitor DCIs, and when a threshold number of DCIs have been received without a wake-up indication, the UE can switch to a mode in which the primary cellular radio component is inactive and the UE's wake-up radio component is active. It should be noted that in at least some cases, the threshold number can be configurable. It should also be noted that the threshold number can be based at least in part on UE capabilities and / or UE channel conditions. The UE can send a wake-up radio component indication (e.g., the wake-up radio component will be activated) and / or acknowledgment to a base station, such as base station 102, to notify the base station of the mode switch. The wake-up radio component indication and / or acknowledgment can be transmitted using a scheduling request and / or via the Physical Uplink Control Channel (PUCCH). In some cases, this scheme can be used for both long CDRXs and short CDRXs. In some cases, for example, as... Figure 12B As shown, the UE can monitor the DCI, and when the DCI includes an indication to activate the wake-up radio component, the UE can switch to a mode in which the primary cellular radio component is inactive and the UE's wake-up radio component is active. Alternatively, when the DCI includes an indication to remain awake during the DCRX on cycle, the UE can remain in its current mode (e.g., where the primary cellular radio component is active). The UE can send a wake-up radio component indication (e.g., the wake-up radio component will be activated) and / or acknowledgment to a base station, such as base station 102, to notify the base station of the mode switch. The wake-up radio component indication and / or acknowledgment can be transmitted using a scheduling request and / or via PUCCH. It should be noted that in either case, switching to a mode in which the wake-up radio component is active can trigger a bandwidth portion switch to the wake-up radio component time and frequency resources as described herein.

[0161] In some implementations, UE-specific signaling such as a specific DCI format X_Y (e.g., any of DCI formats 0_0, 0_1, 0_2, 0_x, 1_0, 1_1, 1_2, 1_x, etc.) can be used to switch a UE, such as UE 106, from a mode in which the UE's primary cellular radio components are active (e.g., an RRC state such as RRC connected, RRC idle, and / or RRC inactive) to a mode in which the primary cellular radio components are inactive and the UE's wake-up radio components are active. For example, the UE can monitor a specific DCI format X_Y to indicate that the bandwidth portion is switched to the configured wake-up radio component bandwidth portion. Then, as... Figure 12C As shown, when the UE detects an indication to switch to a specific DCI format X_Y of a configured wake-up radio component bandwidth portion, the UE can switch from a mode in which the UE's primary cellular radio component is active to a mode in which the primary cellular radio component is inactive and the UE's wake-up radio component is active. In some cases, the UE may transmit feedback to a base station, such as base station 102, before the bandwidth portion switch. For example, as... Figure 13AAs shown, the UE can delay (e.g., modify its timing) the bandwidth portion handover until after transmission feedback (e.g., acknowledgment (ACK)). This scheme could include not scheduling any data and transmitting ACK / NACK (positive acknowledgment / negative acknowledgment) and then switching the DCI format of the bandwidth portion. Alternatively, the UE could not send any feedback regarding the bandwidth portion handover. In some cases, the base station can transmit a PDCCH carrying DCI format X_Y at a higher level than normal aggregation to ensure the UE receives DCI format X_Y. In some cases, for example, as... Figure 13B As shown, the base station can transmit DCI format X_Y multiple times to ensure that the UE receives DCI format X_Y.

[0162] In some implementations, a base station, such as base station 102, may transmit a wake-up signal on a configured wake-up radio component bandwidth portion to trigger a UE, such as UE 106, to transition from a mode in which the UE's wake-up radio component is active and the UE's primary cellular radio component is inactive to a mode in which the wake-up radio component is inactive and the primary cellular radio component is active (e.g., RRC states such as RRC active, RRC idle, and / or RRC inactive). In some cases, such as... Figure 14A As shown, this handover can occur during the configured wake-up radio component bandwidth portion of the duration, and additional buffer time can be allocated to allow the UE to transmit an acknowledgment (ACK) to the base station. This acknowledgment can be a scheduling request and / or other PUCCH. Note that, as... Figure 14B As shown, if and / or when the base station does not receive an acknowledgment, the base station may retransmit the wake-up signal. In some cases, the base station may retransmit the wake-up signal with a different set of parameters (e.g., a lower data rate) and / or with higher power. In some cases, the base station may retransmit the wake-up signal from multiple transmission points. In other cases, the base station may assume that the wake-up signal is always received. In such cases, the base station may begin transmitting to the primary cellular radio unit at a specified and / or configured time after the wake-up signal transmission. The base station can then anticipate an acknowledgment from the primary cellular radio unit. Furthermore, if and / or when the base station does not receive an acknowledgment within a specified time period, the base station may retransmit the wake-up signal, for example, as... Figure 14C As shown. In some cases, the base station may retransmit the wake-up signal using different sets of parameters (e.g., lower data rates) and / or with higher power. In some cases, the base station may retransmit the wake-up signal from multiple transmission points.

[0163] In some implementations, multiple wake-up signals can be multiplexed in time and frequency resources (e.g., bandwidth portions). For example, such as Figure 15AAs shown, the wake-up signal can be multiplexed as a multi-carrier on-off key (MC-OOK), where there is a fixed or configured gap between each "carrier" and time-domain multiplexing with different groups within the bandwidth. Therefore, as shown, UE groups 1, 2, and 3 can be time-division multiplexed in the first bandwidth, UE groups 4, 5, and 6 can be time-division multiplexed in the second bandwidth, and UE groups 7, 8, and 9 can be time-division multiplexed in the third bandwidth. Additionally, as shown, guard bands may exist between the time-division multiplexed UE groups. It should be noted that high-capacity UEs may be able to decode multiple multi-carrier OOK signals simultaneously, and this can be used to increase coverage (diversity) and / or data rate (capacity). Furthermore, this scheme may be useful if and / or when there are limited time resources available to transmit OOK signals. In some cases, the guard band between individual WUS "carriers" can be based on a configuration where a base station (such as base station 102) assigns a UE (such as UE 106) to a wake-up signal channel based on the UE's capabilities (e.g., whether the UE can simultaneously decode multiple multi-carrier OOK signals), and / or can be pre-configured / pre-specified. It should be noted that within the licensed frequency band, the wake-up signal can be multiplexed in both time and frequency, which allows for a non-uniform duration of the wake-up signal (e.g., no padding) because there is no need to prevent other UEs from transmitting on time and frequency resources. In some cases, this scheme can be implemented by setting a wake-up signal with an "on duty cycle" that implicitly enables time-domain multiplexing of different UE groups. For example, as... Figure 15B As shown, wake-up signals can be multiplexed into nested wake-up signal groups. Furthermore, to allow for decoding with smaller bandwidths, the guard band between nested wake-up signals can be based on the configuration where the base station assigns the UE to the wake-up signal channel based on the UE's capabilities, and / or can be pre-configured / pre-specified. Therefore, as shown, UE groups 1, 2, 3, 4, 5, 6, and 7 can be multiplexed in both time and frequency. It should be noted that using this bandwidth-partition framework allows each UE in the group to detect only its own wake-up signal bandwidth portion. It should also be noted that in a nested group structure, even within the permitted frequency band, the duration of different wake-up signals must be equal.

[0164] In some implementations, the wake-up signal bandwidth can be configured at least in part based on the signal-to-noise ratio (SNR) of a UE, such as UE 106. For example, multiple bandwidths can be specified and / or configured to represent different SNRs among UEs. It should be noted that the number of subcarriers used can be a function of the configured subcarrier spacing. Additionally, a base station, such as base station 102, can group UEs with common bandwidths (and the same and / or different subcarrier spacings) within a common time and frequency range (e.g., in a common wake-up signal) or at a common frequency at different times, for example... Figure 16As shown. It should be noted that different subcarrier intervals are possible for the OOK wake-up signal. Furthermore, this scheme allows modification of the wake-up signal bandwidth based on the desired coverage. For example, the coverage can be modified by selecting one or more of the bandwidth, repetition, and / or the number of bits transmitted per OOK symbol. It should be noted that the resources used for the wake-up signal can be located on the UE's center resource / carrier frequency and / or on any frequency resource offset from the UE's center resource / carrier frequency. It should also be noted that the resources used for the wake-up signal can be predetermined and / or pre-specified, such as physical resource blocks 0 and 1 only. Alternatively and / or in addition, the resources used for the wake-up signal can be signaled and / or configured based on bandwidth portion configuration. For example, the physical resource blocks to be used can be signaled, and the size of the guard band within the physical resource block can also be signaled, for example, as the number of resource elements to be avoided. The wake-up signal can also be multiplexed within the same time-frequency resources, for example, using orthogonal sequences or partially / non-orthogonal sequences such as orthogonal coverage codes.

[0165] In some implementations, such as for FR2 and / or FR2-x operation, the transmission beam can be learned by the wake-up radio component. For example, beam scheduling can be passed from the primary cellular radio component to the wake-up radio component. Alternatively, beam scheduling can be signaled in the wake-up radio component discovery channel of each base station. Furthermore, when decoding the wake-up signal, the UE, such as UE106, can be instructed, for example, on the next beam timing, the configured number of beams, or the entire beam scheduling. In some cases, the UE can decode the wake-up signal at a specified and / or desired time, but the wake-up signal may not include a wake-up indication. Instead, the wake-up signal includes the next beam timing.

[0166] In some implementations, for beam-based wake-up signals, the length of the wake-up signal can be constrained (e.g., using a short wake-up signal) to enable the wake-up signal to be completed in the shortest possible time. In some implementations, for beam-based wake-up signals, a UE such as UE 106 can anticipate changes in the wake-up signal receiving beam at specific times, for example, using multiple beams to transmit the wake-up signal over time. In some implementations, due to time constraints, the wake-up signal can be transmitted on a wider frequency range, and different data can be used on each frequency, for example, using MC-OOK.

[0167] Figure 17 A block diagram illustrating an example of a method for operating a wake-up radio component of a UE according to some embodiments is shown. Among other devices, Figure 17The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0168] At 1702, a UE such as UE 106 can operate in a first Radio Resource Control (RRC) state. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered on, and the UE's wake-up radio components can be powered off. It should be noted that the first RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. Additionally, the second RRC state can be a low-power RRC state, such as an RRC wake-up radio component (WUR) state or an RRC wake-up signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0169] At 1704, when operating in the first RRC state, the UE may receive a signal indicating a transition to the second RRC state. This signal may be received from a base station, such as base station 102. In the second RRC state, the UE's primary communication radio component may be powered off, and the UE's wake-up radio component may be powered on. This signal may be a physical layer signal, a media access control (MAC) control element (CE), and / or an RRC message. The physical layer signal may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified by 3GPP Release 17. The DCI may be DCI format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be as specified by 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth portion switching. Furthermore, the type of physical layer signal can be at least partially based on the first RRC state.

[0170] At 1706, the UE can transition to the second RRC state based on the received signal. Therefore, the UE can power on the wake-up radio and power off the main communication radio.

[0171] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a second RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0172] In some implementations, when operating in a first RRC state, receiving a signal indicating a transition to a second RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) activation period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. This indication of a transition to a second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a second RRC state. Based on this determination, the UE may then transmit the indication of a transition to a second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the second RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0173] In some implementations, when operating in the first RRC state, the UE receiving a signal indicating a transition to the second RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the second RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the second RRC state to the base station. It should be noted that this transmission may occur before the transition to the second RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0174] In some implementations, when operating in the second RRC state, the UE can monitor a configured bandwidth portion. Then, upon receiving a wake-up signal, the UE can transition to a third RRC state. It should be noted that in the third RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the third RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the third RRC state can be equivalent to the first RRC state. However, in at least some other cases, the third RRC state can differ from the first RRC state. The transition to the third RRC state can occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE can transmit an indication of the transition to the third RRC state to the base station. This indication of the transition to the third RRC state can be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the third RRC state. It should be noted that if the UE does not transition to the third RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for a specified time), the base station may retransmit the wake-up signal. The base station may retransmit the wake-up signal at one or more of a lower data rate or higher power compared to the previous wake-up signal. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0175] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0176] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0177] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0178] Figure 18 A block diagram of another example of a method for operating a wake-up radio component of a UE, according to some embodiments, is shown. Among other devices, Figure 18 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0179] At 1802, a UE such as UE 106 can operate in a first Radio Resource Control (RRC) state. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered on, and the UE's wake-up radio components can be powered off. It should be noted that the first RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. Additionally, the second RRC state can be a low-power RRC state, such as an RRC wake-up radio component (WUR) state or an RRC wake-up signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0180] At 1804, the UE may receive configuration of one or more time and frequency resources for wake-up radio component monitoring from a base station such as base station 102.

[0181] At 1806, after transitioning to the second RRC state, the UE can monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station can configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighbor cell discovery). Additionally, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size may be configurable to accommodate UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size may be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions may be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing may be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing may be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing may be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​may be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions may be configurable. For example, the configuration of the subcarrier spacing may be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for waking up radio component monitoring may include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0182] In some implementations, when operating in the first RRC state, the UE may receive a signal indicating a transition to the second RRC state. This signal may be received from a base station, such as base station 102. In the second RRC state, the UE's primary communication radio component may be powered down, and the UE's wake-up radio component may be powered on. This signal may be a physical layer signal, a media access control (MAC) control element (CE), and / or an RRC message. The physical layer signal may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified by 3GPP Release 17. The DCI may be DCI format 2_6, for example, it may be a UE group common DCI. Therefore, the wake-up signal may be as specified by 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth partial switching. Furthermore, the type of physical layer signal can be based at least in part on a first RRC state. Additionally, the UE can transition to a second RRC state based on received signals. Therefore, the UE can power on the wake-up radio and power off the main communication radio.

[0183] In some implementations, when operating in a first RRC state, receiving a signal indicating a transition to a second RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) activation period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. This indication of a transition to a second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a second RRC state. Based on this determination, the UE may then transmit the indication of a transition to a second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the second RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0184] In some implementations, when operating in the first RRC state, the UE receiving a signal indicating a transition to the second RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the second RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the second RRC state to the base station. It should be noted that this transmission may occur before the transition to the second RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0185] In some implementations, when operating in the second RRC state, the UE can monitor a configured bandwidth portion. Then, upon receiving a wake-up signal, the UE can transition to a third RRC state. It should be noted that in the third RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the third RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the third RRC state can be equivalent to the first RRC state. However, in at least some other cases, the third RRC state can differ from the first RRC state. The transition to the third RRC state can occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE can transmit an indication of the transition to the third RRC state to the base station. This indication of the transition to the third RRC state can be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the third RRC state. It should be noted that if the UE does not transition to the third RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for a specified time), the base station may retransmit the wake-up signal. The base station may retransmit the wake-up signal at one or more of a lower data rate or higher power compared to the previous wake-up signal. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0186] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0187] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0188] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0189] Figure 19 A block diagram illustrating an example of a method for monitoring DCI formats as part of a wake-up radio component for operating a UE, according to some embodiments, is shown. Among other things, Figure 19 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0190] At 1902, a UE such as UE 106 can operate in a first Radio Resource Control (RRC) state. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered on, and the UE's wake-up radio components can be powered off. It should be noted that the first RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. Additionally, the second RRC state can be a low-power RRC state, such as an RRC wake-up radio component (WUR) state or an RRC wake-up signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0191] At position 1904, the UE can monitor the first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration can be defined as a configured offset from the start of the discontinuous reception (DRX) activation period until the end of the configured monitoring range. In some cases, the UE can determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE can, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. This indication of a transition to the second RRC state can be sent via a scheduling request, the physical uplink control channel (PUCCH), and / or via another signaling and / or signaling type. In some cases, the UE can receive the first DCI format and determine that the first DCI format includes an indication of a transition to the second RRC state. Based on this determination, the UE can then transmit the indication of a transition to the second RRC state to the base station, for example, as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the second RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0192] At point 1906, the UE can, for example, transition to the second RRC state based on this monitoring. In other words, the UE can transition to the second RRC state while detecting and decoding the first DCI format. Therefore, the UE can power on the wake-up radio and power off the main communication radio.

[0193] In some implementations, monitoring the first DCI format may include the UE receiving a signal indicating a transition to a second RRC state when operating in a first RRC state. This signal may be received from a base station, such as base station 102. In the second RRC state, the UE's primary communication radio component may be powered down, and the UE's wake-up radio component may be powered on. This signal may be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. The physical layer signal may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified in 3GPP Release 17. The DCI may be DCI format 2-6, for example, a UE group common DCI. Therefore, the wake-up signal may be as specified in 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth portion switching. Furthermore, the type of physical layer signal can be at least partially based on the first RRC state.

[0194] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a second RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0195] In some implementations, when operating in the first RRC state, the UE receiving a signal indicating a transition to the second RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the second RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the second RRC state to the base station. It should be noted that this transmission may occur before the transition to the second RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0196] In some implementations, when operating in the second RRC state, the UE can monitor a configured bandwidth portion. Then, upon receiving a wake-up signal, the UE can transition to a third RRC state. It should be noted that in the third RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the third RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the third RRC state can be equivalent to the first RRC state. However, in at least some other cases, the third RRC state can differ from the first RRC state. The transition to the third RRC state can occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE can transmit an indication of the transition to the third RRC state to the base station. This indication of the transition to the third RRC state can be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the third RRC state. It should be noted that if the UE does not transition to the third RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for a specified time), the base station may retransmit the wake-up signal. The base station may retransmit the wake-up signal at one or more of a lower data rate or higher power compared to the previous wake-up signal. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0197] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0198] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0199] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0200] Figure 20 A block diagram illustrating an example of a method for monitoring a wake-up signal via a wake-up radio component of a UE, according to some embodiments, is shown. Figure 20 The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0201] At 2002, when operating in a first Radio Resource Control (RRC) state, a UE such as UE 106 can monitor a configured bandwidth portion of the wake-up signal. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered down, and the UE's wake-up radio components can be powered on. It should be noted that the first RRC state can be a low-power RRC state, such as an RRC wake-up radio component (WUR) state or an RRC wake-up signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0202] At 2004, the UE can transition to a second RRC state upon receiving a wake-up signal. It should be noted that in the second RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the second RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the second RRC state may be equivalent to the RRC state the UE operated in before transitioning to the first RRC state. However, in at least some other cases, the second RRC state may differ from the RRC state the UE operated in before transitioning to the first RRC state. The transition to the second RRC state may occur before the bandwidth portion is switched from the configured bandwidth portion. In such cases, the UE may transmit an indication of the transition to the second RRC state to the base station. This indication of the transition to the second RRC state may be transmitted via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to a third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the second RRC state. It should be noted that if the UE does not transition to the second RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for the specified time), the base station may retransmit the wake-up signal. Compared to the previous wake-up signal, the base station may retransmit the wake-up signal at one or more of the following rates: a lower data rate or higher power. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0203] In some implementations, prior to operation in the first RRC state, when operating in a previous RRC state, the UE may receive a signal indicating a transition to the first RRC state. This signal may be received from a base station, such as base station 102. In the previous RRC state, the UE's primary communication radio component may be powered on, and the UE's wake-up radio component may be powered off. Note that the previous RRC state may be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. This signal may be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. The physical layer signal may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified by 3GPP Release 17. The DCI can be DCI format 2_6, for example, it can be a UE group common DCI. Therefore, the wake-up signal can be a wake-up signal as specified by 3GPP Release 16. Alternatively and / or in addition, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that such a DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth partial switch. Furthermore, the type of physical layer signal can be at least partially based on a first RRC state. Furthermore, the UE can transition to the first RRC state based on received signals. Therefore, the UE can power on the wake-up radio component and power off the main communication radio component.

[0204] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a first RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0205] In some implementations, when operating in a previous RRC state, receiving a signal indicating a transition to a first RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) enable period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. The indication of a transition to the second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a first RRC state. Based on this determination, the UE may then transmit an indication of a transition to the second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the first RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0206] In some implementations, when operating in a previous RRC state, the UE receiving a signal indicating a transition to a first RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the first RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the first RRC state to the base station. It should be noted that this transmission may occur before the transition to the first RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0207] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0208] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0209] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0210] Figure 21 A block diagram of another example of a method for operating a UE's wake-up radio component according to some implementation schemes is shown. Figure 21 The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0211] At 2102, a UE such as UE 106 can operate in a first Radio Resource Control (RRC) state. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered on, and the UE's wake-up radio components can be powered off. It should be noted that the first RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. Additionally, the second RRC state can be a low-power RRC state, such as an RRC wake-up radio component (WUR) state or an RRC wake-up signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0212] At 2104, when operating in the first RRC state, the UE may receive a signal multiplexed with one or more other signals in time and frequency resources and indicating a transition to the second RRC state. For example, the signal may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. Note that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, the signal may be multiplexed as nested signal groups. Note that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0213] It should be noted that the signal can be received from a base station such as base station 102. In the second RRC state, the UE's primary communication radio component can be powered off, and the UE's wake-up radio component can be powered on. This signal can be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. The physical layer signal can include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI can indicate an idle state. Furthermore, the PEI can be as specified by 3GPP Release 17. The DCI can be DCI format 2_6, for example, it can be a UE group common DCI. Therefore, the wake-up signal can be as specified by 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth portion switching. Furthermore, the type of physical layer signal can be at least partially based on the first RRC state.

[0214] At point 2106, the UE can transition to the second RRC state based on the received signal. Therefore, the UE can power on the wake-up radio component and power off the main communication radio component.

[0215] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a second RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0216] In some implementations, when operating in a first RRC state, receiving a signal indicating a transition to a second RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) activation period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. This indication of a transition to a second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a second RRC state. Based on this determination, the UE may then transmit the indication of a transition to a second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the second RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0217] In some implementations, when operating in the first RRC state, the UE receiving a signal indicating a transition to the second RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the second RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the second RRC state to the base station. It should be noted that this transmission may occur before the transition to the second RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0218] In some implementations, when operating in the second RRC state, the UE can monitor a configured bandwidth portion. Then, upon receiving a wake-up signal, the UE can transition to a third RRC state. It should be noted that in the third RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the third RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the third RRC state can be equivalent to the first RRC state. However, in at least some other cases, the third RRC state can differ from the first RRC state. The transition to the third RRC state can occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE can transmit an indication of the transition to the third RRC state to the base station. This indication of the transition to the third RRC state can be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the third RRC state. It should be noted that if the UE does not transition to the third RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for a specified time), the base station may retransmit the wake-up signal. The base station may retransmit the wake-up signal at one or more of a lower data rate or higher power compared to the previous wake-up signal. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0219] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0220] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0221] Figure 22 A block diagram is shown as yet another example of a method for operating a wake-up radio component of a UE according to some embodiments. Among other devices, Figure 22 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown, the method operates as follows.

[0222] At 2202, a UE such as UE 106 can operate in a first Radio Resource Control (RRC) state. In the first RRC state, the UE's primary communication radio components (e.g., primary cellular radio components and / or primary short-to-medium range radio components) can be powered on, and the UE's wake-up radio components can be powered off. It should be noted that the first RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state.

[0223] At 2204, the UE can report the signal-to-noise ratio (SNR) to a base station such as base station 102.

[0224] At 2206, the UE can receive from the base station the configuration of the bandwidth of the signal used to indicate the transition to the second RRC state. The bandwidth of the signal can be based on the SNR reported by the UE. For example, the bandwidth of the signal can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs in the bandwidth within a common time and frequency range. It should be noted that in the second RRC state, the UE's primary communication radio component can be powered down, and the UE's wake-up radio component can be powered on. It should also be noted that the second RRC state can be a low-power RRC state, such as the RRC Wake-up Radio Component (WUR) state or the RRC Wake-up Signal (WUS) state. In at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component can include only a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0225] At 2208, when operating in the first RRC state, the UE can monitor the bandwidth of a signal. This signal can be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. The physical layer signal can include at least one of the following: a Paging Advance Indicator (PEI), a Downlink Control Indicator (DCI) received via the Physical Downlink Control Channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI can indicate an idle state. Furthermore, the PEI can be as specified in 3GPP Release 17. The DCI can be DCI format 2_6, for example, it can be a UE group common DCI. Therefore, the wake-up signal can be as specified in 3GPP Release 16. Alternatively and / or otherwise, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that this DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth portion switching. Furthermore, the type of physical layer signal can be at least partially based on the first RRC state.

[0226] In some implementations, the UE can transition to a second RRC state based on a received signal. Therefore, the UE can power on the wake-up radio and power off the main communication radio.

[0227] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a second RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0228] In some implementations, when operating in a first RRC state, receiving a signal indicating a transition to a second RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) activation period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. This indication of a transition to a second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a second RRC state. Based on this determination, the UE may then transmit the indication of a transition to a second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the second RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0229] In some implementations, when operating in the first RRC state, the UE receiving a signal indicating a transition to the second RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the second RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the second RRC state to the base station. It should be noted that this transmission may occur before the transition to the second RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0230] In some implementations, when operating in the second RRC state, the UE can monitor a configured bandwidth portion. Then, upon receiving a wake-up signal, the UE can transition to a third RRC state. It should be noted that in the third RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the third RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the third RRC state can be equivalent to the first RRC state. However, in at least some other cases, the third RRC state can differ from the first RRC state. The transition to the third RRC state can occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE can transmit an indication of the transition to the third RRC state to the base station. This indication of the transition to the third RRC state can be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified amount of time after transmitting the wake-up signal. In some cases, the UE may transmit an acknowledgment to the base station after transitioning to the third RRC state. It should be noted that if the UE does not transition to the third RRC state within a specified time (e.g., when the base station does not receive an acknowledgment for a specified time), the base station may retransmit the wake-up signal. The base station may retransmit the wake-up signal at one or more of a lower data rate or higher power compared to the previous wake-up signal. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0231] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0232] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0233] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0234] Figure 23 A block diagram is shown as another example of a method for monitoring wake-up signals via the wake-up radio component of a UE, according to some implementation schemes. Figure 23 The method shown can be used in conjunction with any system, method, or device shown in the figure, as well as other devices. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. As shown in the figure, the method operates as follows.

[0235] At 2302, a UE such as UE 106 may receive beam scheduling of a wake-up signal from a base station such as base station 102. Beam scheduling may be indicated to the UE's wake-up radio component. For example, an indication of beam scheduling for the wake-up signal may be received from a primary communication radio component (e.g., a primary cellular radio component and / or a primary short-to-medium range radio component) and transmitted to the wake-up radio component. Alternatively and / or in addition, the indication of beam scheduling for the wake-up signal may be signaled in the wake-up radio component discovery channel and received by the wake-up radio component. As a further option, the indication of beam scheduling for the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at a specific time. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0236] At 2304, when operating in the first Radio Resource Control (RRC) state, the UE may monitor the wake-up signal, for example, based on beam scheduling. In the first RRC state, the UE's primary communication radio component can be powered down, and the UE's wake-up radio component can be powered on. It should be noted that the first RRC state can be a low-power RRC state, such as the RRC Wake-up Radio Component (WUR) state or the RRC Wake-up Signal (WUS) state. It should be noted that in at least some cases, the wake-up radio component can be a wake-up receiver. In other words, the wake-up radio component may only include a receiver and / or a receive chain, and may not include a transmitter and / or a transmit chain. It should also be noted that the wake-up receiver can be a low-power and / or ultra-low-power wake-up receiver.

[0237] At point 2306, the UE can transition to a second RRC state upon receiving a wake-up signal. It should be noted that in the second RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the second RRC state can be any of the following: RRC idle state, RRC inactive state, and / or RRC connected state. In at least some cases, the second RRC state may be equivalent to the RRC state the UE operated in before transitioning to the first RRC state. However, in at least some other cases, the second RRC state may differ from the RRC state the UE operated in before transitioning to the first RRC state.

[0238] In some implementations, prior to operation in the first RRC state, when operating in a previous RRC state, the UE may receive a signal indicating a transition to the first RRC state. This signal may be received from a base station, such as base station 102. In the previous RRC state, the UE's primary communication radio component may be powered on, and the UE's wake-up radio component may be powered off. Note that the previous RRC state may be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. This signal may be a physical layer signal, a Media Access Control (MAC) control element (CE), and / or an RRC message. The physical layer signal may include at least one of the following: a paging advance indicator (PEI), a downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), a wake-up signal received via the PDDCH, and / or a signal including one or more bit indicators (e.g., any one of them, any combination of them, and / or all of them). The PEI may indicate an idle state. Furthermore, the PEI may be as specified by 3GPP Release 17. The DCI can be DCI format 2_6, for example, it can be a UE group common DCI. Therefore, the wake-up signal can be a wake-up signal as specified by 3GPP Release 16. Alternatively and / or in addition, the DCI can be a UE-specific DCI, such as DCI format X_Y (e.g., such as DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2 and / or any other DCI format X_Y). It should be noted that such a DCI format (e.g., DCI format X_Y) can be UE-specific. It should also be noted that a UE-specific DCI format can indicate a bandwidth partial switch. Furthermore, the type of physical layer signal can be at least partially based on a first RRC state. Furthermore, the UE can transition to the first RRC state based on received signals. Therefore, the UE can power on the wake-up radio component and power off the main communication radio component.

[0239] In some implementations, the UE may receive configurations from a base station, such as base station 102, for one or more time and frequency resources for wake-up radio component monitoring. Additionally, after transitioning to a first RRC state, the UE may monitor one or more bandwidth portions included in and / or specified by one or more time and frequency resources. It should be noted that the base station may configure one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication. Furthermore, the one or more bandwidth portions for wake-up radio component monitoring may include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for radio resource management procedures (e.g., neighboring cell discovery). Furthermore, the one or more bandwidth portions may be narrowband. In such cases, the signal may be a wake-up signal including on-off key signaling. The bandwidth portion size may be fixed as a multiple of a fixed bandwidth portion and / or may be configurable to accommodate UE-specific wake-up signal bandwidth and / or UE-specific guard band. It should be noted that if and / or when the bandwidth portion size is configurable, the bandwidth portion size may be semi-static or / or dynamically configurable. In some cases, the bandwidth portion size can be configurable to accommodate the UE group wake-up signal bandwidth and / or UE group guard band. In such cases, the bandwidth portion size can be semi-static and / or dynamically configurable. In some cases, the subcarrier spacing of one or more bandwidth portions can be fixed based on the frequency band. For example, when the frequency band is Frequency Range (FR) 1 (FR1), the subcarrier spacing can be 30 kHz. As another example, when the frequency band is FR2, the subcarrier spacing can be 60 kHz. Yet another example is when the frequency band is FR2-x, the subcarrier spacing can be 120 kHz. It should be noted that these subcarrier spacing values ​​are merely exemplary, and other fixed values ​​can be used and / or considered. In other cases, the subcarrier spacing of one or more bandwidth portions can be configurable. For example, the configuration of the subcarrier spacing can be included in this configuration. In some cases, the configuration of one or more time and frequency resources used for wake-up radio component monitoring can include only downlink symbols, e.g., excluding any uplink symbols and / or any special symbols.

[0240] In some implementations, when operating in a previous RRC state, receiving a signal indicating a transition to a first RRC state may include the UE monitoring a first downlink control indicator (DCI) format in the group common physical downlink control channel (PDCCH) for a duration. The duration may be defined as a configured offset from the start of a discontinuous reception (DRX) enable period until the end of a configured monitoring range. In some cases, the UE may determine that a threshold number of first DCI formats have been received from the base station without a wake-up indication. In such cases, the UE may, for example, transmit an indication of a transition to a second RRC state to the base station based on the determination that a threshold number of first DCI formats have been received. The indication of a transition to the second RRC state may be sent via a scheduling request, a physical uplink control channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the UE may receive a first DCI format and determine that the first DCI format includes an indication of a transition to a first RRC state. Based on this determination, the UE may then transmit an indication of a transition to the second RRC state to the base station, for example as an acknowledgment of the receipt of the first DCI format. In some cases, an indication of transition to the first RRC state may be sent via a scheduling request, the Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, transition to the second RRC state based on a received signal may include the UE performing a bandwidth portion handover to time and frequency resources configured for wake-up radio component monitoring.

[0241] In some implementations, monitoring the wake-up signal may include a configured bandwidth portion of the UE's wake-up signal. Furthermore, upon receiving the wake-up signal, the UE transitions to a second RRC state. It should be noted that in the second RRC state, the UE's primary communication radio component can be powered on, and the UE's wake-up radio component can be powered off. It should also be noted that the second RRC state can be any of an RRC idle state, an RRC inactive state, and / or an RRC connected state. In at least some cases, the second RRC state may be equivalent to the RRC state the UE operated in before transitioning to the first RRC state. However, in at least some other cases, the second RRC state may differ from the RRC state the UE operated in before transitioning to the first RRC state. The transition to the second RRC state may occur before the bandwidth portion switches from the configured bandwidth portion. In such cases, the UE may transmit an indication of the transition to the second RRC state to the base station. This indication of the transition to the second RRC state may be sent via a scheduling request, a Physical Uplink Control Channel (PUCCH), and / or via another signal and / or signaling type. In some cases, the base station may require the UE to transition to the third RRC state within a specified time after transmitting the wake-up signal. In other cases, the UE may transmit an acknowledgment to the base station after transitioning to the second RRC state. It should be noted that if the UE does not transition to the second RRC state within the specified time (e.g., when the base station does not receive an acknowledgment for the specified time), the base station may retransmit the wake-up signal. Compared to the previous wake-up signal, the base station may retransmit the wake-up signal at one or more of the following rates: a lower data rate or higher power. Furthermore, the base station may retransmit the wake-up signal from another transmit / receive point.

[0242] In some implementations, when operating in a previous RRC state, the UE receiving a signal indicating a transition to a first RRC state may include the UE monitoring a UE-specific downlink control indicator (DCI) format for bandwidth portion handover on the group common physical downlink control channel (PDCCH). In such cases, the UE transitioning to the first RRC state based on the received signal may include the UE switching to a pre-configured bandwidth portion for wake-up radio component monitoring based on the received UE-specific DCI format. It should be noted that the UE-specific DCI format may include at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x. In some cases, the UE may transmit an indication of the transition to the first RRC state to the base station. It should be noted that this transmission may occur before the transition to the first RRC state. In some cases, the PDCCH may be received at a higher level than the normal aggregation level to ensure that the UE-specific DCI format is received. In some cases, the UE-specific DCI format can be transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

[0243] In some implementations, signals may be multiplexed with one or more other signals in time and frequency resources. For example, signals may be multiplexed as a multi-carrier on-off key (MC-OOC), where there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth. It should be noted that the gaps may be fixed gaps and / or configured gaps. It should also be noted that the guard band between the individual carriers may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between the individual carriers may be pre-configured and / or pre-specified. As another example, signals may be multiplexed as nested signal groups. It should be noted that in such cases, the guard band between nested signal groups may be based on a configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capabilities. Alternatively and / or in addition, the guard band between nested signal groups may be pre-configured and / or pre-specified.

[0244] In some implementations, the signal bandwidth can be configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station. For example, the signal bandwidth can be selected from multiple bandwidths based on the SNR. Furthermore, the number of subcarriers used for the signal can be a function of the configured subcarrier spacing. Additionally, the UE can group with other UEs within the same bandwidth over a common time and frequency range.

[0245] In some implementations, beam scheduling of the wake-up signal may be indicated to the wake-up radio component. The indication of beam scheduling of the wake-up signal may be received from the main communication radio component. Alternatively and / or in addition, the indication of beam scheduling of the wake-up signal may be signaled in the wake-up radio component discovery channel. As a further alternative, the indication of beam scheduling of the wake-up signal may be signaled as part of the wake-up signal. In some cases, the length of the wake-up signal may be limited, for example, to further conserve UE power and / or further reduce UE power requirements. In some cases, beam scheduling may include changes in the receive beam at specific times. In some cases, beam scheduling may include a wake-up signal transmitting different data on each of a plurality of frequencies.

[0246] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0247] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0248] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0249] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.

[0250] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0251] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A user equipment (UE) in a 5G NR system, comprising: At least one antenna; At least one main communication radio component, wherein the at least one main communication radio component is configured to perform communication using at least one radio access technology (RAT); At least one wake-up radio component; as well as One or more processors, the one or more processors being coupled to the at least one main communication radio component and the at least one wake-up radio component, wherein the one or more processors, the at least one main communication radio component, and the at least one wake-up radio component are configured to perform communication; The one or more processors wherein the UE is configured to: Operating in a first Radio Resource Control (RRC) state, which includes one of an RRC idle state, an RRC inactive state, or an RRC connected state, wherein, in the first RRC state, the UE's main communication radio component is powered on and the UE's wake-up radio component is powered off; When operating in the first RRC state, a signal indicating a transition to the second RRC state is received, wherein in the second RRC state, the UE's main communication radio component is powered off, and the UE's wake-up radio component is powered on; and Based on the received signal, the system transitions to a second RRC state, which includes one of the following: RRC Wake-up Radio Unit (WUR) state, RRC Wake-up Signal (WUS) state, or RRC Low Power state. The bandwidth of the signal is configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station, wherein multiple wake-up signals are multiplexed in time / frequency.

2. The UE according to claim 1, The signal is a physical layer signal, and the physical layer signal includes at least one of the following: Paging advance indicator (PEI) indicating idle status; Such as PEI as specified in 3GPP Release 17; Downlink control indicator (DCI) received via the physical downlink control channel (PDDCH), wherein the DCI is in format 2_6; DCI received via PDDCH, wherein the DCI indicates a bandwidth partial switch; The wake-up signal received via the PDDCH; or A signal that includes one or more bit indicators.

3. The UE according to claim 2, The type of the physical layer signal is at least partially based on the first RRC state.

4. The UE according to claim 1, The signal mentioned therein is a Media Access Control (MAC) Control Element (CE) or an RRC message.

5. The UE according to claim 1, The one or more processors are further configured such that the UE: Receive configuration from the base station for one or more time and frequency resources for waking up radio component monitoring, wherein the one or more time and frequency resources include one or more bandwidth portions; and After transitioning to the second RRC state, monitor the one or more bandwidth portions.

6. The UE according to claim 5, The base station is configured with one or more bandwidth portions for wake-up radio component monitoring and four bandwidth portions for non-wake-up radio component communication.

7. The UE according to claim 5, The one or more bandwidth portions used for wake-up radio component monitoring include at least one bandwidth portion for wake-up radio component monitoring and at least one bandwidth portion for neighbor cell discovery.

8. The UE according to claim 5, The one or more bandwidth portions are narrowband, and the signal is a wake-up signal that includes on-off key signaling.

9. The UE according to claim 5, The size of the bandwidth portion is at least one of the following: A multiple fixed to a fixed bandwidth portion; Configurable to adapt to UE-specific wake-up signal bandwidth and UE-specific guard band, wherein the size of the bandwidth portion is semi-static or dynamically configurable; or It can be configured to adapt to the UE group wake-up signal bandwidth and UE group guard band, wherein the size of the bandwidth portion is semi-static or dynamically configurable.

10. The UE according to claim 9, The subcarrier spacing of one or more bandwidth portions is fixed based on the frequency band, or is configurable and included in the configuration.

11. The UE according to claim 5, The configuration of the one or more time and frequency resources used for monitoring the wake-up radio components includes only downlink symbols.

12. The UE according to claim 1, The signal is multiplexed with one or more other signals in time and frequency resources.

13. The UE according to claim 12, The signal is multiplexed as at least one of the following: Multi-carrier on-off key (MC-OOC), wherein there are gaps between carriers and time-domain multiplexing with different groups within the bandwidth, wherein the gaps are one of fixed gaps or configured gaps; or Nested signal groups, wherein the guard bands between nested signal groups are pre-configured, pre-specified, or based on a configuration in which the base station allocates the UE to specific frequency resources based on the UE's capabilities.

14. The UE according to claim 12, The guard band between each carrier is based on the configuration in which the base station allocates the UE to a specific frequency resource based on the UE's capability.

15. The UE according to claim 1, The bandwidth of the signal is selected from multiple bandwidths based on the SNR.

16. The UE according to claim 15, The number of subcarriers used for the signal is a function of the configured subcarrier spacing.

17. The UE according to claim 15, The UEs mentioned therein are grouped with other UEs in the bandwidth within a common time and frequency range.

18. An apparatus in a 5G NR system, comprising: Memory; as well as At least one processor, which communicates with the memory, wherein the at least one processor is configured to: Operating in a first Radio Resource Control (RRC) state, which includes one of an RRC idle state, an RRC inactive state, or an RRC connected state, wherein, in the first RRC state, the wake-up radio component communicating with the device is powered off; Receive a downlink control indicator (DCI) of a first format in the group common physical downlink control channel (PDCCH), wherein receiving the DCI of the first format includes receiving a signal indicating a transition to a second RRC state when the device is operating in a first RRC state; as well as A transition to a second RRC state is initiated based on the receipt of a DCI in a first format. This second RRC state includes one of an RRC Wake-up Radio Unit (WUR) state, an RRC Wake-up Signal (WUS) state, or an RRC Low Power state, wherein in the second RRC state, the wake-up radio unit communicating with the device is powered on. The bandwidth of the signal is configured based on the signal-to-noise ratio (SNR) reported by the device to the base station, wherein multiple wake-up signals are multiplexed in time / frequency.

19. The apparatus according to claim 18, The at least one processor is further configured to: The DCI is monitored for a duration of time, wherein the duration is a configured offset from the start of the discontinuous reception (DRX) enable period to the end of the configured monitoring range.

20. The apparatus according to claim 18, The at least one processor is further configured to: Determine the threshold number of DCIs in a first format that have been received from the base station without a wake-up indication; and The indication of the transition to the second RRC state is transmitted to the base station, wherein the indication of the transition to the second RRC state is sent via either a scheduling request or a physical uplink control channel (PUCCH).

21. The apparatus according to claim 18, The at least one processor is further configured to: Determine that the DCI with the first format includes an indication of the transition to the second RRC state; and The indication of the transition to the second RRC state is transmitted to the base station, wherein the indication of the transition to the second RRC state is sent via either a scheduling request or a physical uplink control channel (PUCCH).

22. A non-transitory computer-readable storage medium storing program instructions executable by processing circuitry to enable a user equipment (UE) in a 5G NR system: Operating under the first Radio Resource Control (RRC) state, wherein, In the first RRC state, the UE's main communication radio component is powered on, and the UE's wake-up radio component is powered off. The first RRC state includes one of the following: RRC idle state, RRC inactive state, or RRC connected state. Monitoring the UE-specific downlink control indicator (DCI) format for bandwidth partial handover in the group common physical downlink control channel (PDCCH) includes the following operations: the UE receives a signal indicating a transition to a second RRC state while operating in a first RRC state, the second RRC state including one of an RRC wake-up radio component (WUR) state, an RRC wake-up signal (WUS) state, or an RRC low-power state, wherein in the second RRC state, the UE's primary communication radio component is de-energized and the UE's wake-up radio component is energized; and Based on receiving the UE-specific DCI format, the system switches to a pre-configured bandwidth portion used for wake-up radio component monitoring. The bandwidth of the signal is configured based on the signal-to-noise ratio (SNR) reported by the UE to the base station, wherein multiple wake-up signals are multiplexed in time / frequency.

23. The non-transitory computer-readable storage medium according to claim 22, The UE-specific DCI format includes at least one of DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_x, DCI format 1_0, DCI format 1_1, DCI format 1_2, or DCI format 1_x.

24. The non-transitory computer-readable storage medium according to claim 22, The PDCCH is received at a higher aggregation level than normal to ensure that the UE-specific DCI format is received.

25. The non-transitory computer-readable storage medium according to claim 22, The UE-specific DCI format is transmitted multiple times by the base station to ensure that the UE-specific DCI format is received.

26. The non-transitory computer-readable storage medium according to claim 22: The program instructions can also be executed by the processing circuit to cause the UE to: Upon receiving a wake-up signal, it transitions to the third RRC state, where... In the third RRC state, the main communication radio component of the UE is powered on, and the wake-up radio component of the UE is powered off.

27. The non-transitory computer-readable storage medium according to claim 26, The third RRC state is one of the following: RRC idle state, RRC inactive state, or RRC connected state.

28. The non-transitory computer-readable storage medium according to claim 26, The third RRC state is equivalent to the first RRC state.

29. The non-transitory computer-readable storage medium according to claim 26, The transition to the third RRC state occurs before the bandwidth portion switches from the pre-configured bandwidth portion; and The program instructions can also be executed by the processing circuit to cause the UE to: The indication of the transition to the third RRC state is transmitted to the base station, wherein the indication of the transition to the third RRC state is sent via either a scheduling request or a physical uplink control channel (PUCCH).

30. The non-transitory computer-readable storage medium according to claim 24, The wake-up radio component is instructed with beam scheduling of the wake-up signal, wherein the instruction of beam scheduling of the wake-up signal is received from the main communication radio component, signaled in the wake-up radio component discovery channel, or signaled as part of the wake-up signal.

31. The non-transitory computer-readable storage medium according to claim 30, The beam scheduling mentioned above includes changing the received beam at a specific time.

32. The non-transitory computer-readable storage medium according to claim 30, The beam scheduling mentioned therein includes transmitting wake-up signals with different data at each of the multiple frequencies.

Images