Method and apparatus for low-power wake-up signaling

Abstract

The logic is operable to generate or decode a low-power wake-up signal (LP-WUS) received via the interface, the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols modulated with on-off keying (OOK) modulation or frequency shift keying (FSK) modulation, and the LP-WUS including information for performing at least one low-power wake-up radio (LP-WUR) function by the LP-WUR of the UE while the main radio of the UE is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS. The logic is operable to determine at least one metric or trigger transmission of the LP-WUS based on the measurement.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. from U.S. Provisional Application No. 63 / 485,487, entitled "Measurements Via Low Power Wake-Up Signaling," filed February 16, 2023, the subject matter of which is incorporated herein by reference. [Background technology]

[0002] Fifth-generation (5G) cellular systems are being designed and developed for both mobile telephony and vertical use cases. In addition to latency, reliability, and availability, user equipment (UE) energy efficiency is also important for 5G. Currently, battery-powered 5G devices such as UEs may need to be recharged weekly or daily, depending on the individual's usage duration. Typically, 5G devices consume tens of milliwatts in radio resource control (RRC) idle / inactive states and hundreds of milliwatts in RRC connected states. Designing for extended battery life is necessary not only to improve energy efficiency but also for a good user experience.

[0003] Power consumption depends on the configured length of the wake-up period, e.g., the paging cycle. To meet the above battery life requirement, a long discontinuous reception (DRX) cycle is planned, resulting in a large latency, which is not suitable for such services that require both long battery life and low latency. For example, in a fire detection and fire suppression use case, fire shutters must be closed and fire sprinklers must be turned on by actuators within 1 to 2 seconds after a fire is detected by sensors, and a long DRX cycle cannot meet the latency requirement. It is necessary to reduce power consumption with reasonable latency. [Brief explanation of the drawings]

[0004] [Figure 1] FIG. 1 illustrates an embodiment of a system including base stations, user devices, cloud-based computing and data services interconnected via a communications network. [Figure 2] FIG. 2 illustrates another embodiment of a network according to various embodiments, such as the network of FIG. [Figure 3] FIG. 3 illustrates another embodiment of a network in accordance with various embodiments. [Figure 4A] FIG. 4A illustrates an embodiment of a user device having a main radio in an off or deep sleep state in accordance with various embodiments. [Figure 4B] FIG. 4A illustrates an embodiment of a user device with a main radio in an on or powered state in accordance with various embodiments. [Figure 4C] FIG. 4C illustrates an embodiment of a subframe including a low-power wake-up signal (LP-WUS) in accordance with various embodiments. [Figure 4D] FIG. 4D illustrates an embodiment of a low-power wake-up signal (LP-WUS) and determining a metric such as reference signal received power (RSRP) based on a sequence of on-off keying (OOK) symbols in the LP-WUS. [Figure 5] FIG. 5 illustrates an embodiment of a simplified block diagram of a base station and a user equipment (UE), such as the base station or RAN, user equipment (UE), and communication network illustrated in FIGS. 1-4. [Figure 6] FIG. 6 illustrates a flow chart of an embodiment of a user equipment for measurement-based cell reselection by a low power wake-up radio and a main radio, such as the embodiments described in connection with FIGS. 1-5. [Figure 7] FIG. 7 shows a flow chart of an embodiment for a base station such as the embodiment described in connection with FIGS. 1-5. [Figure 8]FIG. 8 illustrates an embodiment of protocol entities that may be implemented in a wireless communication device. [Figure 9] FIG. 9 illustrates an embodiment of a PHY data unit (PDU) format that may be transmitted by a PHY device via one or more antennas, according to some aspects, and that may be encoded and decoded by a MAC entity, such as the processor in FIG. 5, the baseband circuits in FIGS. 5, 13, and 14. [Figure 10] 10A-B illustrate embodiments of communication circuitry such as the components and modules shown in the user equipment and base station shown in FIG. [Figure 11] FIG. 11 illustrates an embodiment of a storage medium described herein. [Figure 12] FIG. 12 illustrates a system architecture for a network according to some embodiments. [Figure 13] FIG. 13 illustrates example components of devices according to some embodiments, such as the base station and UE illustrated in FIGS. 1-12. [Figure 14] FIG. 14 illustrates an example interface of a baseband circuit according to some embodiments, such as the baseband circuit shown and / or described in connection with FIGS. 1-13. [Figure 15] FIG. 15 shows an embodiment of a block diagram of components for performing the described functions. DETAILED DESCRIPTION OF THE INVENTION

[0005] The following is a detailed description of the embodiments illustrated in the drawings, which covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.

[0006] Currently, user equipment (UE) wakes up periodically, once per discontinuous reception (DRX) cycle, which significantly impacts power consumption during periods when there is no signaling or data traffic. Power consumption could be dramatically reduced if the UE were only able to wake up when triggered, such as for paging. This could be achieved by using the wake-up signal to trigger a low-power wake-up radio (LP-WUR) to wake up the main radio. The LP-WUR could potentially have the ability to monitor the wake-up signal with ultra-low power consumption. The main radio would wake up to perform data transmission and reception and enter deep sleep unless it was turned on by the LP-WUR.

[0007] Embodiments may include a LP-WUR and a main radio unit, and may include low-power wake-up radio (LP-WUR) logic for performing LP-WUR functions such as measurement, paging reception, cell selection / reselection, beam failure detection (BFD), radio link monitoring (RLM), synchronization, and / or the like via low-power wake-up signaling. In some embodiments, the LP-WUR logic may perform LP-WUR functions without waking up the main radio unit. In some embodiments, the LP-WUR logic may perform LP-WUR functions to reduce the required wake-up time of the main radio unit. In some embodiments, the LP-WUR logic may perform LP-WUR functions to reduce the required wake-up time of the main radio unit to perform main radio functions such as measurement, paging reception, cell selection / reselection, beam failure detection (BFD), radio link monitoring (RLM), synchronization, and / or the like. In some embodiments, the LP-WUR logic is capable of performing the functions of the LP-WUR to determine whether to activate the main radio.

[0008] In some embodiments, the LP-WUR is capable of waking up or applying power to the main radio in response to receiving a low power wake-up signal (LP-WUS). In many embodiments, the LP-WUR is capable of performing measurements based on the low power wake-up signal without waking up the main radio, except in predefined, preconfigured, or configured circumstances by higher layer signaling, such as radio resource control (RRC) signaling.

[0009] The LP-WUR is capable of receiving low-power wake-up signaling with amplitude modulated via on-off keying (OOK) or frequency shift keying (FSK) modulation. Furthermore, the LP-WUR may require different metrics for measurement than the main radio, which may be defined in system information blocks (SIBs) and transmitted to the LP-WUR.

[0010] The LP-WUR logic of the base station may trigger the transmission of a SIB via low power wake-up signaling with metrics for LP-WUR measurements. The LP-WUR logic of the UE may receive the SIB with metrics for LP-WUR measurements, determine metrics for measurements based on the SIB, perform measurements based on the metrics for LP-WUR, and perform cell selection / reselection via low power wake-up signaling (LP-WUS) and LP-WUR to wake up the main radio.

[0011] In some embodiments, for cell selection / reselection, the UE's LP-WUR logic may wake up the main radio in response to a decision to change to a new cell, and the main radio may re-perform radio resource management (RRM) measurements, if applicable, based on LP-WUR metrics and / or based on main radio metrics, before registering on the new cell. In some embodiments, the LP-WUR logic may adjust RRM measurements for LP-WUR cell selection / reselection with a scaling factor and / or offset to adjust the measurements to more closely match or align with the RRM measurements made by the main radio. In some embodiments, the LP-WUR logic may adjust RRM measurements for LP-WUR cell selection / reselection via a translation function for the LP-WUR measurements. In some embodiments, the LP-WUR logic may adjust RRM measurements used for cell selection / reselection via a function for RRM measurements made by the main radio and measurements made by the LP-WUR. In some embodiments, the LP-WUR logic can adjust the RRM measurements used for cell selection / reselection with functions of the RRM measurements made by the main radio. In some embodiments, the LP-WUR logic can adjust the measurements via one or more functions to translate the RRM measurements made by the LP-WUR and / or the main radio, where the translation can include a validation level of the RRM measurements made by the LP-WUR and / or the main radio. In many embodiments, higher layer signaling (e.g., a radio resource control (RRC) layer, other protocol layer, or the like) can pre-define, pre-configure, or configure functions for translating RRM measurements.

[0012] In some embodiments, the LP-WUR logic of the UE may select the best measurement from the measurements by the main radio part and the measurements by the LP-WUR for cell selection / reselection or otherwise. In some embodiments, higher layer signaling (e.g., RRC layer, other protocol layer, or the like) may pre-define, pre-configure, or configure selection criteria for the selection of the best measurement.

[0013] In some embodiments, the LP-WUR logic of the UE is capable of performing beam failure detection (BFD) via the LP-WUR. In some embodiments, the LP-WUR logic of the UE is capable of performing radio link monitoring (RLM) via the LP-WUR. In some embodiments, the LP-WUR logic of the UE is capable of determining paging reception via the LP-WUR. In some embodiments, the LP-WUR logic of the UE is capable of receiving, demodulating, decoding, and interpreting SIBs via the LP-WUR. In some embodiments, the LP-WUR logic of the UE is capable of acquiring synchronization via the LP-WUR.

[0014] Various embodiments may be designed to address various technical challenges related to power consumption by the main radio of a UE; short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to perform measurements such as RRM measurements; short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to perform cell selection and / or cell reselection; short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to perform beam failure detection (BFD); short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to perform radio link monitoring (RLM); short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to determine paging reception; short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to receive SIBs; short DRX cycles for the main radio of a UE due to a periodic, sporadic, or occasional requirement to acquire synchronization; and / or the like.

[0015] The various technical challenges discussed above may be addressed by one or more various embodiments. Embodiments may address one or more of these challenges related to power consumption by the main radio of the UE. For example, some embodiments addressing challenges related to power consumption by the main radio of the UE may address the challenges by one or more various technical means, such as encoding, modulating, and transmitting an SIB along with metrics for measurements by the LP-WUR; receiving, decoding, and interpreting an SIB along with metrics for measurements by the LP-WUR; performing measurements such as RRM measurements by the LP-WUR; performing cell selection and / or cell reselection by the LP-WUR and / or the main radio; performing BFD by the LP-WUR; performing RLM by the LP-WUR; determining paging reception by the LP-WUR; acquiring synchronization by the LP-WUR; enabling longer DRX cycles by the main radio of the UE by activating the main radio as needed; and / or the like.

[0016] Some embodiments include systems with multiple processor cores, such as central servers, access points, and / or stations (STAs), including modems, routers, switches, servers, workstations, netbooks, mobile devices (e.g., laptops, smartphones, tablets), sensors, meters, controls, gauges, monitors, home or office appliances, Internet of Things (IoT) gear (e.g., watches, glasses, headphones, cameras), etc. Some embodiments may provide, for example, indoor and / or outdoor "smart" grid and sensor services. In various embodiments, these devices relate to specific applications, such as healthcare, home, commercial office and retail, security, and industrial automation and monitoring applications, as well as vehicle applications (e.g., automobiles, autonomous vehicles, airplanes, drones), and the like.

[0017] The technology disclosed herein may include transmission of data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may include transmission over one or more wireless connections according to one or more technologies and / or standards, including 3rd Generation Partnership Project (3GPP®), 3GPP Long Term Evolution (LTE), 3GPP LTE-Advanced (LTE-A), 4G LTE, 5G New Radio (NR), and / or 6G, including amendments, successors, and variations thereof. Various embodiments may additionally or alternatively include transmission according to one or more Global System for Mobile Communications (GSM) / Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS) / High-Speed ​​Packet Access (HSPA), and / or GSM with General Packet Radio Service (GPRS) systems (GSM / GPRS) technologies and / or standards, including amendments, successors, and variations thereof.

[0018] Examples of wireless mobile broadband technologies and / or standards may include, but are not limited to, the Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standard (e.g., 802.16m and / or 802.16p), International Mobile Telecommunications Advanced (IMT-ADV), Industry Standard for Microwave (WiMAX) and / or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), High Performance Wireless Metropolitan Area Network (HIPERFMAN), wireless broadband (WiBro), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSAPA), High Speed ​​Uplink Packet Access (HSUPA) technologies and / or standards, including amendments, successors, and variations thereof.

[0019] Some embodiments may further perform wireless communications in accordance with other wireless communications technologies and / or standards. Examples of other wireless communication technologies and / or standards that may be used in various embodiments include other IEEE wireless communication standards such as IEEE 802.11-5220, IEEE 802.11ax-5221, IEEE 802.11ay-5221, IEEE 802.11ba-5221, and / or other specifications and standards such as the specifications developed by the Wi-Fi Alliance (WFA) Neighbor Awareness Networking (NAN) Task Group, 3GPP Technical Report (TR) 23.887, 3GPP Technical Specification (TS) 22.368, 3GPP TS 23.682, 3GPP TS 36.133, 3GPP TS 36.306, 3GPP TS 36.321, 3GPP TS.331, 3GPP TS 38.133, 3GPP TS 38.306, 3GPP This may include, but is not limited to, machine type communication (MTC) standards such as those embodied in TS38.321, 38.214, and / or 3GPP TS38.331, and / or near field communication (NFC) standards such as those developed by the NFC Forum, including any revisions, successors, and / or variations of any of the above.

[0020] 1 illustrates a communication network 100 that reduces power consumption by a UE's primary radio by performing low-power wake-up radio signaling to enable LP-WUR functionality and by performing LP-WUR functionality in the UE. Communication network 100 is an orthogonal frequency division multiplexing (OFDM) network that includes a primary base station 101, a secondary base station 102, a cloud-based service 103, a first user device UE-1, a second user device UE-2, and a third user device UE-3. One or more of the UEs may be equipped with LP-WURs that prompt a longer DRX cycle for the UE's corresponding primary radio to reduce the overall power consumption rate by the one or more UEs.

[0021] In 3GPP systems based on Orthogonal Frequency Division Multiple Access (OFDMA) downlink, radio resources are divided into subframes in the time domain, with each subframe containing two slots. Each OFDMA symbol further consists of several OFDMA subcarriers in the frequency domain, depending on the system (or carrier) bandwidth. The basic unit of the resource grid is called a resource element (RE), which spans the OFDMA subcarriers across one OFDMA symbol. A resource block (RB) contains a group of REs, where each RB may contain, for example, 12 consecutive subcarriers within one slot.

[0022] Several physical downlink channels and reference signals use sets of resource elements carrying information originating from higher coding layers. For downlink channels, the Physical Downlink Shared Channel (PDSCH) is the primary data-carrying downlink channel, and the Physical Downlink Control Channel (PDCCH) can carry downlink control information (DCI). The control information may include scheduling decisions, information related to reference signal information, rules for forming the corresponding transport blocks (TBs) to be carried by the PDSCH, and power control commands. UEs can use cell-specific reference signals (CRS) for demodulation of control / data channels in non-precoded or codebook-based precoded transmission modes, radio link monitoring, and channel state information (CSI) feedback measurements. UEs can use UE-specific reference signals (DM-RS) for demodulation of control / data channels in non-codebook-based precoded transmission modes.

[0023] The communication network 100 may include cells, such as a micro cell or a macro cell, and a base station 101 may provide wireless service to UEs within the cell. The base station 102 may provide wireless service to UEs in another cell that is adjacent to or overlaps the cell. In other embodiments, the communication network 100 may include a macro cell, and the base station 102 may operate a smaller cell within the macro cell, such as a micro cell or a pico cell. Other examples of small cells may include, but are not limited to, a micro cell, a femto cell, or another type of smaller sized cell.

[0024] In various embodiments, base station 101 and base station 102 may communicate via a backhaul. In some embodiments, the backhaul may include a wired backhaul. In various other embodiments, the backhaul may include a wireless backhaul. In some embodiments, the backhaul may include an Xn interface or an F1 interface, which are interfaces defined between two RAN nodes or base stations, such as the backhaul between base station 101 and base station 102. If the architecture of communications network 100 is a central unit / distributed unit (CU / DU) architecture, the Xn interface is an interface for gNBs, and the F1 interface is an interface for gNB-distributed units (DUs). For example, in some embodiments, base station 101 may comprise a CU, and base station 102 may comprise a DU. In other embodiments, both base stations 101 and 102 may comprise eNBs or gNBs.

[0025] Base stations 101 and 102 may communicate protocol data units (PDUs) over the backhaul. As an example, for an Xn interface, base station 101 may transmit or share control plane PDUs over the Xn-C interface and may transmit or share data PDUs over the Xn-U interface. For an F1 interface, base station 101 may transmit or share control plane PDUs over the F1-C interface and may transmit or share data PDUs over the F1-U interface. Note that references herein to signaling, sharing, receiving, or transmitting over the Xn interface may refer to signaling, sharing, receiving, or transmitting over the Xn-C interface, the Xn-U interface, or a combination thereof. Similarly, references herein to signaling, sharing, receiving, or transmitting over the F1 interface may refer to signaling, sharing, receiving, or transmitting over the F1-C interface, the F1-U interface, or a combination thereof.

[0026] In some embodiments, base stations 101 and 102 may include LP-WUR logic to determine, encode, modulate, and trigger transmission of low power wake-up radio signaling to the UE's LP-WUR to advantageously enable longer DRX cycles for the corresponding main radio of the UE.

[0027] In many embodiments, the LP-WUR logic of base stations 101 and 102 may comprise or have access to memory to store and maintain configurations, descriptions, definitions, or instructions for SIBs and / or information from SIBs, such as metrics for measurements by the LP-WUR of the UE, and to encode, modulate, and trigger transmission of the SIBs with metrics for measurements by the LP-WUR. In some embodiments, the memory may store configurations, descriptions, definitions, or instructions for low power wake-up radio signaling to enable measurements and / or other functions (e.g., RLM, paging, BFD, synchronization, etc.) by the LP-WURs of the UE. In some embodiments, the memory may store descriptions, definitions, configurations, or instructions for low power wake-up radio signaling (e.g., DRX cycle) to determine when to send an LP-WUR to wake up the main radio of the UE.

[0028] In some embodiments, the LP-WUR logic of the UEs (UE-1, UE-2, and UE-3) may store and maintain configurations, descriptions, definitions, or instructions for SIBs and / or information from SIBs, such as metrics for measurements by the LP-WURs of the UEs, to receive, decode, demodulate, and interpret the SIBs along with metrics for measurements by the LP-WURs. In some embodiments, the memory may store configurations, definitions, or instructions for low power wake-up radio signaling to enable measurements and / or other functions (RLM, paging, BFD, synchronization, and / or the like) by the LP-WURs of the UEs. In some embodiments, the memory may store configurations, descriptions, definitions, or instructions for low power wake-up radio signaling to determine when to monitor the LP-WURs to wake up the main radio of the UE.

[0029] For example, the LP-WUR logic of base stations 101 and 102 can transmit SIBs, such as two or more of SIB1 through SIB5, to the LP-WURs of the UEs to convey metrics for RRM measurements to the LP-WURs. The LP-WUR logic of the UEs can determine S-criteria and R-criteria from the SIBs to enable RRM measurements for cell reselection by the LP-WURs. Based on the S-criteria and R-criteria, and on reception and measurement of WUS symbols of the LP-WUR via low-power wake-up radio signaling from base station 101, the LP-WUR logic of UE-1 can determine RRM measurements, such as reference signal received power (RSRP) measurements and / or reference signal received quality (RSRQ) measurements. The LP-WUR logic can determine configurations to be stored in the UE's memory for cell reselection. The configuration may define a conversion function for converting RRM measurements based on LP-WUR metrics, including a scaling factor and / or offset for converting RSRP and / or RSRQ measurements by the LP-WUR logic via the LP-WUR to equivalent RSRP and / or RSRQ measurements by the main radio. After performing the conversion of the RSRP and / or RSRQ measurements, the LP-WUR logic of UE-1 may determine to select a neighbor cell as a better cell for communication with communication network 100. In some embodiments, the LP-WUR logic may further register UE-1 with the neighbor cell by waking up the main radio by sending a wake-up signal from the LP-WUR to the main radio, or by otherwise changing the main radio from an off state or a deep sleep state to an on state. The LP-WUR logic of UE-1 may communicate the selection of the neighbor cell to perform registration with the neighbor cell.

[0030] In another embodiment, after deciding to change to a new cell, such as a neighbor cell, the LP-WUR logic may wake the main radio to redo RRM measurements, such as RSRP and / or RSRQ measurements, based on the LP-WUR measurement metrics. The LP-WUR logic of UE-1 may select the best RRM measurements or determine RRM measurements based on a function of the RRM measurements made by the main radio and / or the RRM measurements made by the LP-WUR to determine cell reselection. Based on measurements of the serving cell (the cell where UE-1 is currently registered, such as base station 101) and a neighbor cell (e.g., base station 102), the LP-WUR logic of UE-1 may select the neighbor cell (base station 102) and register with base station 102 via the main radio.

[0031] Figure 2 illustrates an embodiment of a network 100B according to various embodiments, such as network 100 of Figure 1. Network 100B may operate in a manner consistent with 3GPP technical standards for LTE or 5G / NR systems, as well as O-RAN standards such as O-RAN "Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM), RAN Control." However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems or the like.

[0032] The network 100B may include a UE 102B (such as UE-1, UE-2, or UE-3 in FIG. 1), which may include any mobile or non-mobile computing device designed to communicate with the RAN 104 (such as base station 101 or base station 102 in FIG. 1) via an over-the-air connection. The UE 102B may be communicatively coupled to the RAN 104 by a Uu interface. The UE 102B may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an in-vehicle diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, or the like.

[0033] In some embodiments, the network 100B may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0034] In some embodiments, the UE 102B may further communicate with the AP 106 via an over-the-air connection. The AP 106 may manage a WLAN connection that may function to offload all or some network traffic from the RAN 104. The connection between the UE 102B and the AP 106 may conform to any IEEE 802.11 protocol, where the AP 106 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 102B, the RAN 104, and the AP 106 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 102B being configured by the RAN 104 to utilize both cellular radio resources and WLAN resources.

[0035] The RAN 104 may include one or more access nodes, such as the AN 108. The AN 108 may terminate air interface protocols for the UE 102B by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 108 may enable data / voice connectivity between the CN 120 and the UE 102B. In some embodiments, the AN 108 may be implemented as one or more software entities running on a server computer, either in a separate device or as part of a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 108 may also be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 108 may be a macro cell base station or a low-power base station for providing a femto cell, pico cell, or other similar cell with a smaller coverage area, lower user capacity, or higher bandwidth compared to a macro cell.

[0036] In some embodiments, the UE 102B may further communicate with the AP 106 via a wireless connection. The AP 106 may manage a WLAN connection that may function to offload some / all network traffic from the RAN 104. The connection between the UE 102B and the AP 106 may conform to any IEEE 802.11 protocol, where the AP 106 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 102B, the RAN 104, and the AP 106 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 102B being configured by the RAN 104 to utilize both cellular radio resources and WLAN resources.

[0037] In embodiments in which the RAN 104 includes multiple ANs, they may be coupled to one another via an X2 interface (if the RAN 104 is an LTE RAN) or an Xn interface (if the RAN 104 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into a control / user plane interface, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0038] Each AN of the RAN 104 may manage one or more cells, cell groups, component carriers, etc. to provide the UE 102B with an air interface for network access. The UE 102B may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 104. For example, the UE 102B and the RAN 104 may use carrier aggregation to enable the UE 102B to connect to multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connectivity scenario, a first AN may be a master node providing an MCG, and a second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0039] The RAN 104 may provide the air interface via licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using PCell / SCell. Prior to accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example, based on the Listen Before Talk (LBT) protocol.

[0040] In a V2X scenario, the UE 102B or the AN 108 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.

[0041] An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; An RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; An RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", etc.

[0042] In one example, an RSU is a roadside-located computing device coupled to radio frequency circuits that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high-speed events such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0043] In some embodiments, the RAN 104 may be an LTE RAN 110 with an eNB, such as eNB 112. The LTE RAN 110 may provide an LTE air interface with the following characteristics: a 15 kHz SCS; a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0044] In some embodiments, the RAN 104 may be an NG-RAN 114 with a gNB, e.g., gNB 116, or an ng-eNB, e.g., ng-eNB 118. The gNB 116 may connect to a 5G-capable UE using a 5G NR interface. The gNB 116 may connect to a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 118 may also connect to the 5G core via the NG interface, but may connect to a UE via an LTE air interface. The gNB 116 and the ng-eNB 118 may connect to each other via an Xn interface.

[0045] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface (e.g., N3 interface), which carries traffic data between nodes in the NG-RAN 114 and the UPF 148, and an NG Control Plane (NG-C) interface (e.g., N2 interface), which is the signaling interface between nodes in the NG-RAN 114 and the AMF 144.

[0046] The NG-RAN 114 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetitive, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface may rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0047] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs may be used for dynamic SCS adaptation. For example, a UE 102B may be configured with multiple BWPs, each with a different SCS. When a BWP change is indicated to the UE 102B, the SCS of its transmissions is also changed. Another example use case for BWPs relates to power saving. In particular, multiple BWPs may be configured for the UE 102B with different amounts of frequency resources (e.g., PRBs) to support data transmissions under different traffic load scenarios. A BWP with fewer PRBs may be used for data transmissions with a small traffic load, while enabling power savings at the UE 102B and, in some cases, at the gNB 116. A BWP with a larger number of PRBs may be used for scenarios with a higher traffic load.

[0048] The RAN 104 is communicatively coupled to the CN 120, which includes network elements that provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 102B). The components of the CN 120 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 120 onto physical computing / storage resources, such as servers, switches, etc. A logical instantiation of the CN 120 may be referred to as a network slice, and a partial logical instantiation of the CN 120 may be referred to as a network sub-slice.

[0049] In some embodiments, the CN 120 may be an LTE CN 122, sometimes referred to as an EPC. The LTE CN 122 may include an MME 124, an SGW 126, an SGSN 128, an HSS 130, a PGW 132, and a PCRF 134 coupled together via interfaces (or "reference points") as shown. The following briefly introduces the functionality of the elements of the LTE CN 122.

[0050] The MME 124 may implement mobility management functions that track the current location of the UE 102B to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0051] The SGW 126 terminates the S1 interface towards the RAN and can route data packets between the RAN and the LTE CN 122. The SGW 126 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other duties may include lawful interception, charging, and some policy enforcement.

[0052] The SGSN 128 may track the location of the UE 102B and perform security functions and access control. Additionally, the SGSN 128 may perform EPC inter-node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by the MME 124; MME selection for handover; etc. An S3 reference point between the MME 124 and the SGSN 128 may enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0053] The HSS 130 may include a database for network users, including subscription-related information to support the network entity's handling of communication sessions. The HSS 130 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS 130 and the MME 124 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 120.

[0054] The PGW 132 may terminate an SGi interface toward a data network (DN) 136, which may include an application / content server 138. The PGW 132 may route data packets between the LTE CN 122 and the data network 136. The PGW 132 may be coupled to the SGW 126 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 132 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. Furthermore, the SGi reference point between the PGW 132 and the data network 136 may be an operator-external public or private PDN, or an operator-internal packet data network, for example, for the provision of IMS services. The PGW 132 may be coupled to the PCRF 134 via a Gx reference point.

[0055] The PCRF 134 is the policy and charging control element of the LTE CN 122. The PCRF 134 may be communicatively coupled to an application / content server 138 to determine appropriate QoS and charging parameters for a service flow. The PCRF 132 may provision the PCEF with the appropriate TFT and QCI (via the Gx reference point) and associated rules.

[0056] In some embodiments, CN 120 may be 5GC 140. 5GC 140 may include AUSF 142, AMF 144, SMF 146, UPF 148, NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, and AF 160 coupled together via interfaces (or "reference points") as shown. The following briefly introduces the functionality of the elements of 5GC 140.

[0057] The AUSF 142 may store data for authentication of the UE 102B and process authentication-related functions. The AUSF 142 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 140 via reference points, as shown, the AUSF 142 may exhibit a Nausf service-based interface.

[0058] The AMF 144 may enable other functional units of the 5GC 140 to communicate with the UE 102B and the RAN 104 and subscribe to be notified of mobility events related to the UE 102B. The AMF 144 may be responsible for registration management (e.g., for registering the UE 102B), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 144 may provide transport for SM messages between the UE 102B and the SMF 146 and act as a transparent proxy for routing SM messages. The AMF 144 may also provide transport for SMS messages between the UE 102B and the SMSF. The AMF 144 may interact with the AUSF 142 and the UE 102B to perform various security anchor and context management functions. Additionally, the AMF 144 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 104 and the AMF 144; the AMF 144 is also the termination point of NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 144 may also support NAS signaling with the UE 102B over the N3 IWF interface.

[0059] The SMF 146 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 148 and the AN 108); UE IP address allocation and management (optionally including authorization); UP function selection and control; configuring traffic steering in the UPF 148 to route traffic to the appropriate destination; terminating the interface towards the policy control function; controlling policy enforcement, charging, and parts of QoS; lawful intercept (for SM events and the interface to the L1 system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent by the AMF 144 to the AN 108 via N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to the PDU connectivity service that provides or enables the exchange of PDUs between the UE 102B and the data network 136.

[0060] The UPF 148 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 136, and a branch point to support multi-homed PDU sessions. The UPF 148 may also perform packet routing and forwarding, packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking in the uplink and downlink, downlink packet buffering, and downlink data notification triggering. The UPF 148 may include an uplink classifier to support routing traffic flows to the data network.

[0061] The NSSF 150 may select a set of network slice instances to serve the UE 102B. The NSSF 150 may also determine the allowed NSSAIs and their mapping to subscribed S-NSSAIs, if necessary. The NSSF 150 may also determine the AMF set or list of candidate AMFs to be used to serve the UE 102B based on appropriate configuration and possibly by querying the NRF 154. The selection of a set of network slice instances for the UE 102B may be triggered by the AMF 144 to which the UE 102B is registered by interacting with the NSSF 150, which may result in an AMF change. The NSSF 150 may interact with the AMF 144 via the N22 reference point; it may also communicate with another NSSF in a visited network via the N31 reference point (not shown). Furthermore, the NSSF 150 may expose an NNSSF service-based interface.

[0062] The NEF 152 can securely expose services and capabilities provided by 3GPP network functions for third-party internal exposure / re-exposure, AFs (e.g., AF 160), edge computing systems, or fog computing systems. In such embodiments, the NEF 152 can authenticate, authorize, or throttle AFs. The NEF 152 can also translate information exchanged with the AF 160 and information exchanged with internal network functions. For example, the NEF 152 can translate between AF service identifiers and internal 5GC information. The NEF 152 can also receive information from other NFs based on the other NFs' exposed capabilities. This information can be stored in the NEF 152 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-published by the NEF 152 to other NFs and AFs or used for other purposes, such as analysis. Furthermore, the NEF 152 can exhibit NEF service-based interfaces.

[0063] The NRF 154 supports service discovery functionality and is capable of receiving NF discovery requests from NF instances and providing information about discovered NF instances to the NF instances. The NRF 154 also maintains information about available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, the NRF 154 may refer to an Nnrf service-based interface.

[0064] The PCF 156 can provide policy rules to control plane functions for enforcement and can support a unified policy framework to manage network behavior. The PCF 156 can also provide a front end for accessing subscription information related to policy decisions in the UDRs of the UDM 158. In addition to communicating with functions through reference points as shown, the PCF 156 also exhibits an NPCF service-based interface.

[0065] The UDM 158 may process subscription-related information to support network entity communication session processing and may store subscription data for the UE 102B. For example, the subscription data may be communicated via the N8 reference point between the UDM 158 and the AMF 144. The UDM 158 may include two parts: an application front end (Application Front End) and a UDR. The UDR may store subscription data and policy data for the UDM 158 and PCF 156, and / or structured data for exposure and application data (including PFDs for application discovery and application requirement information for multiple UEs 102B) for the NEF 152. The Nudr service-based interface, represented by the UDR 546, may enable the UDM 158, PCF 156, and NEF 152 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of associated data changes in the UDR. The UDM may include a UDM-FE responsible for credential handling, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential handling, user identification, access authorization, registration / mobility management, and subscription management. As shown, in addition to communicating with other NFs via reference points, the UDM 158 may expose a Nudm service-based interface.

[0066] The AF 160 allows applications to influence traffic routing, provides access to the NEF, and interfaces with the policy framework for policy control.

[0067] In some embodiments, the 5GC 140 may enable edge computing by selecting an operator / third-party service to be geographically close to the point where the UE 102B attaches to the network. This may reduce latency and load on the network. To support edge computing implementations, the 5GC 140 may select a UPF 148 close to the UE 102B and perform traffic steering from the UPF 148 to the data network 136 over the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 160. In this way, the AF 160 may influence UPF (re)selection and traffic routing. If the AF 160 is considered a trusted entity based on operator deployment, the network operator may allow the AF 160 to interact directly with associated NFs. Additionally, the AF 160 may exhibit a NAF service-based interface.

[0068] Data network 136 may represent various network operator services, internet access, or third party services that may be provided by one or more servers, including, for example, application / content server 138 .

[0069] In some embodiments, the RAN 104 or one or more ANs 108 may include LP-WUR logic for configuring, defining, determining, and generating low-power wake-up signaling for communication with the LP-WUR of the UE 102B. The LP-WUR logic of the RAN 104 may cause transmission of an OOK or FSK signal to the UE 102B to wake up the main radio of the UE 102B and provide for measurements, such as RRM measurements, by the LP-WUR of the UE 102B, paging by the LP-WUR of the UE 102B, synchronization by the LP-WUR of the UE 102B, and / or the like.

[0070] FIG. 3 illustrates an embodiment of a network 3000, such as the communications network 100 shown in FIG. 1, in accordance with various embodiments. The network 3000 may operate in a manner consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 3000 may operate concurrently with the network 100B. For example, in some embodiments, the network 3000 may share one or more frequency or bandwidth resources with the network 100B. As one particular example, a UE (e.g., the UE 3002) may be configured to operate in both the network 3000 and the network 100B. Such a configuration may be based on the UE including circuitry configured for communication using the frequency and bandwidth resources of both the networks 100B and 3000. In general, some elements of the network 3000 may share one or more features with elements of the network 100B. For purposes of brevity and clarity, such elements may not be repeated in the description of the network 3000.

[0071] The network 3000 may include a UE 3002, which may include any mobile or non-mobile computing device designed to communicate with the RAN 3008 via an over-the-air connection. The UE 3002 may be similar to, for example, the UE 102B. The UE 3002 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, an instrument cluster, a head-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0072] Although not specifically shown in FIG. 3 , in some embodiments, the network 3000 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in FIG. 3 , the UE 3002 may be communicatively coupled to an AP, such as the AP 106, as described with respect to FIG. 2 . Furthermore, although not specifically shown in FIG. 3 , in some embodiments, the RAN 3008 may include one or more ANs, such as the AN 108, as described with respect to FIG. 2 . The RAN 3008 and / or the ANs of the RAN 3008 may be referred to as base stations (BSs), RAN nodes, or using some other terminology or designation.

[0073] The UE 3002 and the RAN 3008 may be configured to communicate over an air interface that may be referred to as a sixth-generation (6G) air interface. The 6G air interface may include one or more features such as communications in terahertz (THz) or sub-THz bandwidths, or joint communications and sensing. As used herein, the term "joint communications and sensing" may refer to a system that enables wireless communications and radar-based sensing through various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communications in frequency ranges above 80 GHz. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mmWave" frequency ranges.

[0074] The RAN 3008 may enable communication between the UE 3002 and a 6G Core Network (CN) 3010. Specifically, the RAN 3008 may facilitate transmission and reception of data between the UE 3002 and the 6G CN 3010. The 6G CN 3010 may include various functions such as the NSSF 150, the NEF 152, the NRF 154, the PCF 156, the UDM 158, the AF 160, the SMF 146, and the AUSF 142. The 6G CN 3010 may further include the UPF 148 and the DN 136, as shown in FIG. 3 .

[0075] Additionally, the RAN 3008 may include various additional functions that are in addition to or alternative to the functions of legacy cellular networks, such as 4G or 5G networks. Two such functions may include a Compute Control Function (Comp CF) 3024 and a Compute Services Function (Comp SF) 3036. The Comp CF 3024 and Comp SF 3036 may be part of or functionally part of a Compute Services Plane. The Comp CF 3024 may be a control plane function that provides functions such as Comp SF 3036 management, compute task context creation and management (e.g., create, read, modify, delete), and interaction with the underlying compute infrastructure for compute resource management. The Comp SF 3036 may be a user plane function that acts as a gateway interfacing with compute service users (such as UE 3002) and the compute nodes behind the Comp SF instance. Some functions of the Comp SF 3036 may include: analyzing compute service data received from users to compute tasks that can be performed by compute nodes; maintaining a service mesh ingress gateway or service API gateway; enforcing service and billing policies; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 3036 instance may act as a user plane gateway for a cluster of compute nodes. A Comp CF 3024 instance may control one or more Comp SF 3036 instances.

[0076] Two other such functions may include a communications control function (Comm CF) 3028 and a communications services function (Comm SF) 3038, which may be part of the communications services plane. The Comm CF 3028 may be a control plane function for managing communications session creation / configuration / release and managing communications session contexts, and the Comm SF 3038 may be a user plane function for data transport. The Comm CF 3028 and Comm SF 3038 may be considered upgrades to the SMF 146 and UPF 148 described with respect to the 5G system in FIG. 1B. The upgrades provided by the Comm CF 3028 and Comm SF 3038 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, the SMF 146 and UPF 148 may continue to be used.

[0077] Two other such functions may include a data control function (data CF) 3022 and a data service function (data SF) 3032, which may be part of the data service plane. The data CF 3022 may be a control plane function and may provide functions such as data SF 3032 management, data service creation / configuration / release, data service context management, etc. The data SF 3032 may be a user plane function and may act as a gateway between data service users (such as various functions in the UE 3002 and the 6G CN 3010) and data service endpoints behind the gateway. Specific functions may include parsing and forwarding data service user data to the corresponding data service endpoints, generating charging data, and reporting data service status.

[0078] Another such function may be a service coordination and chaining function (SOCF) 3020, which may discover, coordinate, and chain communication, compute, and data services provided by functions in the network. Upon receiving a service request from a user, the SOCF 3020 may interact with one or more of the Comp CF 3024, Comm CF 3028, and Data CF 3022 to identify instances of the Comp SF 3036, Comm SF 3038, and Data SF 3032, configure service resources, and generate a service chain, which may include multiple instances of the Comp SF 3036, Comm SF 3038, and Data SF 3032 and their associated compute endpoints. Workload processing and data movement may then occur within the generated service chain. The SOCF 3020 may be responsible for maintaining, updating, and releasing the created service chain.

[0079] Another such function may be the Service Registration Function (SRF) 3014, which may act as a registry for system services offered in the user plane, such as services offered by service endpoints behind the Comp SF 3036 and Data SF 3032 gateways, and services offered by the UE 3002. The SRF 3014 may be considered the counterpart of the NRF 154, which may act as a registry for network functions.

[0080] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 3026, which may provide a service communication infrastructure for control plane services and user plane services. The eSCP may relate to a 5G service communication proxy (SCP) with added user plane service communication proxy capabilities. Thus, the eSCP is represented by two parts: eSCP-C 3012 and eSCP-U 3034 for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 3026 may control and configure eCSP instances with respect to service traffic routing policies, access rules, load balancing configuration, performance monitoring, etc.

[0081] Another such function is the AMF 3044. The AMF 3044 may be similar to 144, but has additional functions. In particular, the AMF 3044 may include a possible repartition of functions, such as moving message transfer functions from the AMF 3044 to the RAN 3008.

[0082] Another such function is the Service Orchestration Exposure Function (SOEF) 3018. The SOEF can be configured to expose service orchestration and chaining services to external users, such as applications.

[0083] The UE 3002 may include an additional function called a Compute Client Service Function (comp CSF) 3004. The Comp CSF 3004 may have both control plane and user plane functions and may interact with corresponding network-side functions such as the SOCF 3020, Comp CF 3024, Comp SF 3036, Data CF 3022, and / or Data SF 3032 for service discovery, request / response, computational task workload exchange, etc. The Comp CSF 3004 may also work with the network-side functions to determine whether a computational task should be performed in elements of the UE 3002, the RAN 3008, and / or the 6G CN 3010.

[0084] The UE 3002 and / or the Comp CSF 3004 may include a service mesh proxy 3006. The service mesh proxy 3006 may act as a proxy for service-to-service communications in the user plane. Capabilities of the service mesh proxy 3006 may include one or more of addressing, security, load balancing, etc.

[0085] 4A-4B illustrate embodiments of a UE that changes state to a power-saving state and from a power-saving mode to a powered state based on signaling via a wake-up signal. FIG. 4A illustrates an embodiment of a UE 410 (such as UE-1, UE-2, or UE-1 in FIG. 1) with a low-power wake-up (LP-WUR) 414 that transitions a main receiver 412 from a powered state, such as "on," to a power-saving state, such as "off" or deep sleep. In the power-saving state, if a low-power wake-up (LP-WUR) 418 is not received by the LP-WUR 414 from a base station, such as base station 101 or 102 in FIG. 1, the main receiver 412 remains in the "off" state for deep sleep. On the other hand, as shown in FIG. 4B , when the LP-WUS 418 is received by the LP-WUR 414 from the base station, the LP-WUR 414 may trigger the main receiver 412 to turn on or transition the main receiver 412 to an “on” state via a wake-up signal 419 from the LP-WUR 414 to the main receiver 412. In the latter case, since the main receiver 412 is active, the wake-up receiver 414 may be turned off or transitioned to an off state. Note that the main receiver 412 may include a receiver portion of a main radio, such as the main radio described in connection with FIG. 1 , and waking up the main receiver 412 may, in some embodiments, include waking up the main radio.

[0086] It should be noted that in other embodiments, the LP-WUR 414 may be integrated with or include portions of the circuitry of the main receiver 412. In other words, one or more components of the circuitry of the LP-WUR 414 may be components of the main receiver 412. In such embodiments, powering down the LP-WUR 414 may include powering down circuitry dedicated to the LP-WUR 414 and not shared with the main receiver 412. Furthermore, in such embodiments, powering up the main radio 412 may include powering additional components of the circuitry associated with the functionality of the main receiver 412, such as a main transmitter. For example, in some embodiments, the baseband processor may include circuitry common to both the LP-WUR 414 and the main receiver 412 and may coordinate and / or perform the functions of the LP-WUR 414 and the main receiver 412. In other embodiments, the LP-WUR 414 and the main receiver 412 may comprise separate or dedicated baseband processors, processor cores, or processing circuits of one or more baseband processors.

[0087] A wake-up signal 419 may be transmitted over the wake-up signal channel 413 to trigger reception and / or transmission of signals by the main receiver 412. The circuitry of the LP-WUR 414 and the circuitry of the main receiver 412 may also communicate (transmit and / or receive) over the wake-up signal channel 413 for purposes of serving cell or neighbor cell radio resource management (RRM) measurements, radio link monitoring (RLM) measurements, beam failure detection (BFD), synchronization, and the like. Using measurements over the wake-up signal channel 413, the main receiver 412 may be turned off with greater periodicity to further reduce power consumption at the UE 410.

[0088] Many embodiments may use mechanisms for measurements based on one or more LP-WUS. For example, some embodiments may define metrics for measurements by the LP-WUS, processes for cell selection / reselection, processes for joint operation for RRM by the LP-WUS and by the main radio, and processes for BFD, RLM, paging reception, and synchronization.

[0089] Metrics for measurements with LP-WUS An LP-WUS includes multiple WUS symbols. In some embodiments, an LP-WUS may include at least a first part, a first part and a second part, or more than two parts. In some embodiments, more than one type of LP-WUS is established and configured to perform different functions. In some embodiments, some types of LP-WUS may include only the first part, some types may include at least two parts, all types of LP-WUS may include only the first part, or some types of LP-WUS may include at least two parts.

[0090] For example, metrics for RSRP or RSRQ measurements may be defined based on reception of WUS symbols of the LP-WUS by the LP-WUR. The UE's LP-WUR logic may derive measurements based on only the first type of LP-WUS, only the second type of LP-WUS, or both the first and second types of LP-WUS. The UE's LP-WUR logic may derive measurements based on only the first part of the LP-WUS, only the second part of the LP-WUS, or both the first and second parts of the LP-WUS.

[0091] Cell Selection Cell selection / reselection refers to the process of finding a better cell based on criteria and changing cells while in an idle mode, such as the off state or deep sleep state. The process for cell selection / reselection includes performing one or more measurements of signals from neighbor cells; selecting a new cell based on criteria; and performing registration to register the UE on the new cell. Cell reselection may occur after the UE has performed cell selection and entered idle mode. Cell reselection may include measurements of the serving cell (the cell where the UE is currently registered) and one or more neighbor (or nearby) cells.

[0092] Generally, cell selection may involve scanning energy levels from one or more neighbor cells; and decoding system information blocks (SIBs), such as SIB1 and SIB2, that carry cell reselection parameters to determine the SIB schedule. Cell selection may involve estimating one or more cell selection parameters and cell selection criteria calculated by a predefined algorithm; selecting a new cell with the best criteria; and performing a registration process to register with the new cell. SIB1 defines scheduling and other system information, including periodicity. SIB2 contains cell reselection information common to intra-frequency, inter-frequency, and / or inter-RAT cell reselection. SIB3 contains information related to RSRQ cell reselection. SIB4 contains information related only to inter-frequency cell reselection. And SIB5 contains information related only to inter-RAT cell reselection.

[0093] In the procedure for cell reselection of an idle UE, the S and R criteria are checked. In all cases, the UE shall reselect to a new cell only if the following conditions are met: - Time interval Treselection according to the cell reselection criteria specified above RAT the new cell is better than the serving cell; and A time period longer than, say, 1 second has elapsed since the UE camped on the current serving cell.

[0094] The S criterion may be met if: ●Srxlev > 0 AND Squal > 0 where: ●Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset) - Pcompensation - Qoffsettemp ●Squal = Qqualmeas - (Qqualmin + Qqualminoffset) - Qoffsettemp where: ● Srxlev is the cell reselection reception (RX) level value (dB).

[0095] ● Squal is the cell selection quality value (dB).

[0096] ●Qrxlevmeas is the measured cell RX level value (RSRP).

[0097] ● Qrxlevmin is the required minimum RX level (dBm) in the cell. If the UE supports the supplementary uplink (SUL) frequencies of this cell, Qrxlevmin is obtained from RxLevMinSUL in SIB1, SIB2, and SIB4, if present, and if QrxlevminoffsetcellSUL is present in SIB3 and SIB4 of the considered cell, this cell-specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the considered cell; otherwise, Qrxlevmin is obtained from q-RxLevMin in SIB1, SIB2, and SIB4, and if Qrxlevminoffsetcell is present in SIB3 and SIB4 of the considered cell, this cell-specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the considered cell.

[0098] ● Qrxlevminoffset is the offset to the signaled Qrxlevmin that is taken into account in the Srxlev evaluation as a result of periodic searches for higher priority PLMNs while successfully camped on a VPLMN, as specified in TS 23.122.

[0099] Pcompensation If the UE supports additionalPmax in SIB1, SIB2, and SIB4, if present, in the NR-NS-PmaxList: ○max(PEMAX1 - PpowerClass, 0) - (min(PEMAX2, PPowerClass) - min(PEMAX1, PPowerClass)) (dB); else: ○max(PEMAX1 - PPowerClass, 0) (dB) Qqualmeas is the measured cell quality value (RSRQ).

[0100] Qqualmin is the required minimum quality level (dB) in the cell. Additionally, if Qqualminoffsetcell is signaled for the considered cell, this cell-specific offset is added to achieve the required minimum quality level in the considered cell.

[0101] ●Qqualminoffset is the offset to the signaled Qqualmin that is taken into account in the Squal evaluation as a result of periodic searches for higher priority PLMNs while successfully camped on a VPLMN, as specified in TS23.122.

[0102] PEMAX1, PEMAX2 are the maximum transmit (TX) power levels (dBm) that a UE may use when transmitting in the uplink within the cell, defined as PEMAX in TS38.101. If the UE supports the SUL frequency for this cell, PEMAX1 and PEMAX2 are obtained from the p-Max for SUL in SIB1 and the NR-NS-PmaxList for SUL in SIB1, SIB2, and SIB4, respectively, as specified in TS38.331; otherwise, PEMAX1 and PEMAX2 are obtained from the p-Max and NR-NS-PmaxList in SIB1, SIB2, and SIB4 for the regular UL, respectively, as specified in TS38.331.

[0103] The R criteria may include Rs and Rn: ●Rs = Rs = Qmeas,s + Qhyst ●Rn = Qmeas,n - Qoffset where s is the serving cell and n is the neighbor cell. Qmeas is the measurement used in cell reselection, Qoffset is the Qoffset,n between the serving cell and the neighbor cell for intra-frequency and Qoffset,n+Qoffsetfrequency for inter-frequency, Qoffsetfrequency is the frequency-specific offset for equal priority frequencies, and Qhyst specifies the hysteresis value for the ranking criteria. RAT specifies cell reselection timer values ​​that are applicable when evaluating reselection within a 5G NR system or for another radio access technology (RAT).

[0104] In many embodiments, the LP-WUR logic of the UE may perform cell selection / reselection in two phases. The first phase may include primary cell (PCell) selection / reselection, and the second phase may include secondary cell (SCell) selection / reselection. The selection / reselection criteria for the SCell may differ from the selection / reselection criteria for the PCell and, in some embodiments, may be set by the selected PCell or by higher layer signaling.

[0105] During the cell reselection procedure, the UE's LP-WUR logic receives neighbor cell SIB1 and other necessary SIBs (e.g., one or more of SIB2 to SIB5) to determine the neighbor cell configuration. In essence, cell selection results in downlink (DL) reception using the main radio.

[0106] LP-WUS-based RRM measurements may be configured for both the serving cell and neighbor cell(s). The neighbor cells may be on the same frequency or on different frequencies. Predetermined criteria for cell reselection, such as S and R criteria, may be defined for the UE's LP-WUS-based RRM measurements. The UE's LP-WUR logic may use parameters in computing S and R criteria that may be configured separately for the LP-WUR-based and main radio-based RRM measurements. In another embodiment, the UE's LP-WUR logic may use parameters in computing S and R criteria that are configured by the LP-WUR and main radio and that apply commonly to the RRM measurements.

[0107] The LP-WUR logic of the UE may configure a set of neighbor cells for the RRM measurements by the LP-WUR separately from a set of neighbor cells for the RRM measurements by the main radio unit. In a further embodiment, the LP-WUR logic of the UE may configure a set of neighbor cells for the RRM measurements by the LP-WUR to be the same as a set of neighbor cells for the RRM measurements by the main radio unit.

[0108] In some embodiments, the LP-WUR logic of the UE may perform cell reselection and turn on the main radio if the neighbor cell has been reselected by the LP-WUR according to the S and R criteria. In such embodiments, the LP-WUR logic of the UE may reselect the neighbor cell based solely on the S and R criteria by the LP-WUR. The LP-WUR logic of the UE may receive the neighbor cell's SIB1 and other required SIBs (e.g., one or more of SIB2 through SIB5) to determine the neighbor cell's configuration. The neighbor cell's new configuration may include at least one of system information, paging configuration, and LP-WUS configuration.

[0109] In some embodiments, the LP-WUR logic of the UE may perform cell reselection and reselect a neighbor cell according to the LP-WUR S and R criteria. In such embodiments, the LP-WUR logic of the UE may reselect a neighbor cell based solely on the LP-WUR S and R criteria. In such embodiments, if the UE receives an indication to receive system information on a neighbor cell, e.g., a system information update indicated by the LP-WUS from the serving cell and / or neighbor cell, the LP-WUR logic of the UE may receive the neighbor cell's SIB1 and other required SIBs immediately or shortly thereafter to determine the neighbor cell's configuration; otherwise, the LP-WUR logic of the UE may not turn on the main radio for reception. In such an embodiment, the UE's LP-WUR logic may prepare (determine or configure) in advance to receive an LP-WUS for the neighbor cell and activate the main radio while the UE is camped on the neighbor cell, but may only monitor for and act upon an LP-WUS (with a wake-up indication) from the neighbor cell after the neighbor cell is reselected. In other embodiments, the UE's LP-WUR logic may configure the LP-WUS for the neighbor cell to activate the main radio after the neighbor cell is reselected.

[0110] In some embodiments, when the UE reselects a neighbor cell according to the S and R criteria from the LP-WUR, the LP-WUR logic of the UE can turn on the main radio, and the main radio can redo RRM measurements of one or more neighbor cells that have potentially better metrics than the LP-WUR S and R criteria. The LP-WUR logic of the UE can then perform cell reselection according to the S and R criteria from the LP-WUR. The number of neighbor cells for which RRM measurements may be performed by the main radio can be predefined, preconfigured, or configured by higher layer signaling. In further embodiments, the minimum number of neighbor cells for which RRM measurements may be performed by the main radio can be predefined, preconfigured, or configured by higher layer signaling.

[0111] In some embodiments, the S and R criteria may be the same as those defined in the NR specification. In other embodiments, the S and R criteria may differ from those defined in the NR specification. For example, the S and R criteria may define thresholds for, for example, RSRP and / or RSRQ measurements.

[0112] Joint operation for RRM by LP-WUS and main radio section If the LP-WUR based RRM measurements are configured to mitigate RRM by the main radio, the UE's LP-WUR logic may have both valid RRM measurements by the LP-WUR and valid RRM measurements by the main radio, and the UE's LP-WUR logic can jointly consider the two types of RRM measurements when checking the S and R criteria for potential cell reselection.

[0113] In some embodiments, if both valid RRM measurements by the LP-WUR and valid RRM measurements by the main radio are available for a cell at a given time, the UE's LP-WUR logic may only check criteria for potential cell reselection based on one type of RRM measurement for that cell. For example, the UE's LP-WUR logic may prioritize the RRM measurements by the main radio for cell selection. In other words, the UE's LP-WUR logic may assume that the RRM measurements by the main radio are better than the RRM measurements by the LP-WUR due to additional resources available to the main radio, or may determine that the RRM measurements by the main radio are better based on predefined or preconfigured criteria.

[0114] In some embodiments, the UE's LP-WUR logic may maintain separate or different metrics for validation of RRM measurements by the LP-WUR and separate or different metrics for validation of RRM measurements by the main radio. In some embodiments, the UE's LP-WUR logic may select an RRM measurement with a larger validation metric to check potential cell reselection criteria. The validation metric may be defined by the amount of time elapsed since the RRM measurement was taken. For example, the validation metric may be set to a maximum value immediately after the RRM measurement was taken by the LP-WUR or the main radio. The validation metric is decremented as time passes. The maximum values ​​for the validation metrics for RRM by the LP-WUR and the main radio may be set separately by higher layer signaling, and the UE's LP-WUR logic may select the RRM measurement with the largest validation metric after both RRM measurements are completed.

[0115] In a further embodiment, the same maximum value for the verification metric is applied to both the RRM measurements by the LP-WUR and the RRM measurements by the main radio. The step size for reducing the verification metric for the RRM measurements by the LP-WUR and the main radio may be configured separately by higher layer signaling. In another embodiment, the same step size for reducing the verification metric is applied to the RRM measurements by the LP-WUR and the main radio.

[0116] In some embodiments, the UE's LP-WUR logic can convert the LP-WUR RRM measurements into intermediate values. The UE's LP-WUR logic can compare the LP-WUR RRM measurements with the main radio RRM measurements for the same or different cells, or combine the LP-WUR RRM measurements with the main radio RRM measurements for the same cell. The UE's LP-WUR logic can then use the converted values ​​and the main radio RRM measurements to perform cell reselection according to the S and R criteria.

[0117] In some embodiments, the LP-WUR logic of the UE may add an offset to the RRM measurements (M LR ) is converted into RRM measurements (M LR ) may be assumed to be equivalent to the RRM measurements by the main radio unit: M MR =M LR +Δ, where Δ is an offset that can be predefined, preconfigured, or configured by higher layer signaling. The offset Δ may be common for both the serving cell measurements and the neighbor cell measurements. In further embodiments, the offset Δ may be configured / determined separately for the serving cell measurements or the neighbor cell measurements.

[0118] In some embodiments, the LP-WUR logic of the UE may perform RRM measurements (M LR ) is multiplied by a scaling factor and / or added an offset, and then the RRM measurement by LP-WUR (M LR ) may be assumed to be equivalent to the RRM measurements by the main radio unit: M MR =c·M LR +Δ. C is a scaling factor and Δ is an offset. C and Δ can be predefined, preconfigured, or configured by higher layer signaling.

[0119] In some embodiments, other functions may be predefined, preconfigured, or configured by higher layer signaling to convert the RRM measurements made by the LP-WUR to be equivalent to the RRM measurements made by the main radio. In such embodiments, the LP-WUR logic of the UE may convert the RRM measurements made by the LP-WUR (M LR ) is converted by the function, and then the RRM measurement by LP-WUR (M LR ) may be assumed to be equivalent to the RRM measurements by the main radio unit: M MR =f(M LR ), where f() is a function for conversion. For example, the verification level of the RRM measurements by the LP-WUR and / or by the main radio unit may be included in the function.

[0120] In some embodiments, the LP-WUR logic of the UE may derive joint RRM measurements based on the RRM measurements by the LP-WUR and the RRM measurements by the main radio, and the LP-WUR logic of the UE may then use the joint RRM measurements to perform cell reselection according to the S and R criteria.

[0121] In some embodiments, the LP-WUR logic of the UE may be configured to calculate MJ=aM MR +bM LRThe joint RRM measurement M is defined as J It is possible to derive where M LR ,M MR are the RRM measurements by the LP-WUR and the RRM measurements by the main radio, respectively, and a and b are scaling factors for the RRM measurements by the LP-WUR and the RRM measurements by the main radio, respectively. Note that these may be predefined, preconfigured, or configured by higher layer signaling.

[0122] In some embodiments, the LP-WUR logic of the UE may be configured to calculate MJ=aM MR +b(M LR +Δ) J It is possible to derive where M LR ,M MR are the RRM measurements by the LP-WUR and the main radio, respectively, a and b are scaling factors for the RRM measurements by the LP-WUR and the main radio, respectively, and Δ is an offset. a, b, and Δ may be predefined, preconfigured, or configured by higher layer signaling.

[0123] In some embodiments, the LP-WUR logic of the UE may be configured to receive RRM measurements M by the LP-WUS. LR and RRM measurement M by the main radio section MR In such an embodiment, the LP-WUR logic of the UE may derive the joint RRM measurements by combining the LP-WUR RRM measurements (M LR ) and the RRM measurements (MMR) by the main radio unit can be combined by the function: M J =g(M LR ,M MR), where g() is a function for combining. For example, the verification level of the RRM measurements by the LP-WUR and / or by the main radio part may be included in the function.

[0124] Processes for BFD, RLM, paging reception, and synchronization In some embodiments, the LP-WUR logic of the UE is capable of monitoring low power wake-up radio signaling, measuring the low power wake-up radio signaling, and determining or calculating a metric of low power wake-up radio signaling quality (e.g., RSRQ) over a predetermined or pre-configured time period to detect a predetermined medium access control layer count number of times the low power wake-up radio signaling does not meet a signal quality threshold. If the count reaches or exceeds that count, the LP-WUR logic of the UE is capable of determining a BFD event, and in some embodiments, the LP-WUR logic of the UE is capable of waking up the main radio to indicate BFD using a wake-up signal or otherwise.

[0125] In some embodiments, the LP-WUR logic of the UE may monitor low power wake-up radio signaling, measure the low power wake-up radio signaling, and determine or calculate low power wake-up radio signaling quality (e.g., RSRQ) and performance (e.g., RSRP) metrics for RLM. In some embodiments, the LP-WUR logic of the UE may compare the quality and performance to one or more thresholds, e.g., according to a predefined, preconfigured, or configured process, e.g., by higher layer signaling and / or one or more SIBs. In some embodiments, the LP-WUR logic of the UE may wake up the main radio to indicate the outcome of RLM using a wake-up signal or otherwise.

[0126] In some embodiments, the LP-WUR logic of the UE is capable of monitoring low power wake-up radio signaling for paging. In some embodiments, the LP-WUR logic of the UE is capable of receiving paging information via the LP-WUS. In further embodiments, the LP-WUR logic of the UE is capable of waking up the main radio to receive paging information via the LP-WUS or via the main radio. In some embodiments, the LP-WUR logic of the UE is capable of determining whether to wake up the main radio based on one or more criteria, such as a priority associated with the paging information.

[0127] In some embodiments, the LP-WUR logic of the UE is capable of monitoring low power wake-up radio signaling for a synchronization signal, measuring the low power wake-up radio signaling, and determining or calculating a timing and frequency offset based on the synchronization signal. In some embodiments, the LP-WUR logic of the UE is capable of waking the main radio in response to the synchronization signal and / or the timing and frequency offset based on the synchronization signal, e.g., according to a predefined, preconfigured, or configured process by higher layer signaling and / or one or more SIBs.

[0128] FIG. 4C illustrates an embodiment of two parts of a low-power wake-up signal (LP-WUS) 420 allocated within a subframe 422. The LP-WUS 420 may use on-off keying (OOK) or frequency-shift keying (FSK). In an OFDM system, the OOK or FSK modulation may be mapped onto multiple subcarriers, i.e., multi-carrier OOK (MC-OOK) or MC-FSK. The wake-up signal (WUS) symbols may represent OOK symbols, FSK symbols, MC-OOK symbols, or MC-FSK symbols. In some embodiments, the LP-WUS 420 may also use the same waveform as other New Radio (NR) channels / signals.

[0129] The LP-WUS 420 may consist of a single part, two parts, or more than two parts. For an LP-WUS 420 that includes a single part (Part 1 424), the base station's LP-WUS logic may generate the LP-WUS 420 based on sequence or coded payload information and trigger transmission of the LP-WUS 420 to the UE's LP-WUS. For an LP-WUS 420 that includes two parts, the base station's LP-WUS logic may generate the first part (Part 1 424) based on the sequence and use channel coding to generate the second part (Part 2 426) containing wake-up information and trigger transmission of the LP-WUS 420 to the UE's LP-WUS. The first part (Part 1 424) may also carry one or more information bits, such as WUS symbols 428.

[0130] The LP-WUS 420 may serve at least one of the following purposes: · Cell selection, e.g., the UE is able to identify cells and perform RRM measurements based on the LP-WUS 420. Radio link monitoring (RLM) Beam management, e.g., beam failure detection (BFD) Paging reception determination System information block (SIB) reception determination ·Synchronized acquisition.

[0131] A single type or multiple different types of LP-WUS 420 may be supported to address corresponding purposes. For example, the base station's LP-WUR logic may generate and trigger transmission of a single LP-WUS 420 configuration for all purposes. As another example, the base station's LP-WUR logic may generate and transmit multiple different types of LP-WUS 420 configured to serve different purposes. For example, the base station's LP-WUR logic may periodically generate and trigger transmission of a first type of LP-WUS 420 that can be used by the UE's LP-WUR for synchronization and / or measurement.

[0132] Additionally, the base station's LP-WUR logic may generate and trigger transmission of the second type LP-WUS 420 on demand, for example, by waking up the UE's main radio to receive paging or by periodically configuring resources for the second type LP-WUS for periodicity. The second type LP-WUS 420 may further support synchronization and / or measurements. At least for UEs in RRC idle state, the UE does not need to turn on its main radio to receive the first and second types of LP-WUS 420. In such an embodiment, the UE's LP-WUR logic may turn on or wake up its main radio only if it detects a particular type of LP-WUS 420 that instructs the UE to turn on its main radio. For example, the second type LP-WUS 420 may indicate a paging request for the UE rather than waking up the main radio to receive the paging, which advantageously reduces the power consumption of the UE.

[0133] 4D shows an embodiment of an LP-WUS 430 for RSRP measurement by a UE's LP-WUR. The LP-WUS 430 may include eight OOK symbols (WUS symbols). Other embodiments may include more or less than eight WUS symbols. The LP-WUS 430 may include multiple WUS symbols.

[0134] A reference signal received power (RSRP) metric and / or a reference signal received quality (RSRQ) measurement may be defined by the UE's LP-WUR logic based on reception of WUS symbols of the LP-WUS 430 by the UE's LP-WUR. The UE's LP-WUR logic may derive the measurement based only on the first type LP-WUS 430, only on the second type LP-WUS 430, and / or based on both the first type LP-WUS 430 and the second type LP-WUS 430. The UE's LP-WUR logic may derive the measurement based only on the first part of the LP-WUS, only on the second part of the LP-WUS, or based on both the first part of the LP-WUS and the second part of the LP-WUS.

[0135] In some embodiments, a part of the LP-WUS 430 includes N WUS symbols, such as FSK symbols, and the sequence of information for the N FSK symbols is represented by b k = 0 or 1, k = 0, 1, ..., N-1, and RSRP based on this part may be defined as follows: First, the intermediate metric P k1 -P k2 is determined for FSK symbol k, where P k1 is the average received power at the first frequency of the FSK symbol representing the value '1', while P k2 is the average received power at the first frequency of the FSK symbol representing the value '0'; RSRP based on N FSK symbols is a sequence b k Considering this, it can be defined as follows:

number

[0136] Referring again to Figure 4D, the average received power of the eight OOK symbols is P0 to P7, respectively. The transmitted ON / OFF sequence is '1,0,1,0,1,0,1,0'. The RSRP measurement is:

number

[0137] In some embodiments, a part of the LP-WUS 430 includes N OOK symbols. The RSRP may be defined as the average transmit power of all ON symbols within the N OOK symbols.

[0138] In some embodiments, a part of the LP-WUS contains N WUS symbols. The sequence of ON or OFF information for this part is denoted by b k = 0 or 1, k = 0, 1, ..., N-1. The received signal strength indicator (RSSI) may be based on this part and may be defined as follows: First, the average received power P for OOK symbol k k can be determined using all samples of WUS symbol k; The RSSI based on N OOK symbols is calculated as the average received power P k It can be determined by:

number

[0139] For example, for a received OOK symbol as shown in FIG. 4D, the RSSI measurement is:

number

[0140] In some embodiments, a part of the LP-WUS 430 includes N FSK symbols. The sequence of information for the N FSK symbols is denoted by b k = 0 or 1, k = 0, 1, ..., N-1. RSRP can be based on this part and may be defined as follows: First, the intermediate metric P k1 -P k2 is determined for FSK symbol k, where P k1 is the average received power at the first frequency of the FSK symbol representing the value '1', while P k2 is the average received power at the first frequency of the FSK symbol representing the value '0'; RSRP based on N FSK symbols is calculated by dividing the N average received power P k The average of

number

[0141] Based on the above definition, a part of the LP-WUS 430 may include N WUS symbols, and the RSRQ may be defined by the RSRP divided by the corresponding RSSI.

[0142] In some embodiments, if multiple sequences of WUS symbols are transmitted in a part of the LP-WUS 430, the LP-WUR logic of the UE may first detect the transmitted sequence. After the sequence of WUS symbols is detected, the LP-WUR logic of the UE may further derive measurements based on the detected sequence. If a payload is encoded and transmitted for a part of the LP-WUS 430, the LP-WUR logic of the UE may first decode the payload. After the payload is decoded, the LP-WUR logic of the UE may regenerate the transmitted sequence of WUS symbols for the LP-WUS 430. Finally, the LP-WUR logic of the UE may further derive measurements based on the regenerated sequence.

[0143] FIG. 5 illustrates an embodiment of a simplified block diagram 500 of a base station 501 and a user equipment (UE) 511, in which certain embodiments may be implemented in a communication network such as a base station or RAN, a UE, and the communication networks shown in FIGS. 1-4. For the base station 510, an antenna 546 transmits and receives wireless signals. RF circuitry 544, coupled to the antenna 546, which is the physical layer of the base station 510, receives the RF signals from the antenna 546 and performs operations on the signals, such as amplifying the signals and splitting the signals into quadrature-phase and in-phase signals. Receiver circuitry 590 converts the signals to digital baseband signals or uplink data, and the digital in-phase and quadrature-phase signals may be passed to a processor 520 of the baseband circuitry 514, also referred to as processing circuitry or baseband processing circuitry, via an interface 525 of the baseband circuitry 514 (such as RF interface 1416 shown in FIG. 14). In another embodiment, an analog-to-digital converter in the processor 520 may convert the in-phase and quadrature-phase signals to digital baseband signals.

[0144] The transmitter circuitry 592 can convert the digital baseband signals or downlink data received from the processor 520 to analog signals. The RF circuitry 544 processes and amplifies the analog signals, converts the analog signals to RF signals, and sends the amplified analog RF signals to the antenna 546.

[0145] The processor 520 decodes and processes digital baseband signals or uplink data and invokes various functional modules to perform functions in the base station 510. The memory 522 stores program instructions or code and data 524 to control the operation of the base station 510. The host circuitry 512 is capable of executing code, such as RRC layer code, from the code and data 524 to perform the RRC layer functions and codes.

[0146] A similar configuration exists in the UE 560, where an antenna 596 transmits and receives RF signals. RF circuitry 594, coupled to the antenna 596, receives the RF signals from the antenna 596, amplifies the RF signals, and processes the signals to generate analog in-phase and quadrature-phase signals. The receiver circuitry 590 processes and converts the analog in-phase and quadrature-phase signals to digital baseband signals via an analog-to-digital converter or to downlink data, and passes the in-phase and quadrature-phase signals to a processor 570 in the baseband circuitry 564 via an interface 575 (such as the RF interface 1416 shown in FIG. 14 ) of the baseband circuitry 564. In other embodiments, the processor 570 can include an analog-to-digital converter and convert the analog in-phase and quadrature-phase signals to digital in-phase and digital quadrature-phase signals.

[0147] The transmitter circuitry 592 can convert the digital baseband signals or downlink data received from the processor 570 to analog signals. The RF circuitry 594 processes and amplifies the analog signals, converts the analog signals to RF signals, and sends the amplified analog RF signals to the antenna 596.

[0148] The RF circuitry 594 illustrates multiple RF chains. While the RF circuitry 594 illustrates five RF chains, each UE may have a different number of RF chains, and each RF chain in the figure may represent multiple time-domain receive (RX) and transmit (TX) chains. The RX and TX chains include circuitry that can process or modify time-domain signals transmitted through the time-domain chain, such as circuitry for inserting guard intervals in the TX chain and circuitry for removing guard intervals in the RX chain. For example, the RF circuitry 594 may include transmitter and receiver circuitry, often referred to as transceiver circuitry. The transmitter circuitry can prepare digital data from the processor 570 for transmission via the antenna 596. In preparation for transmission, the transmitter can encode data, modulate the encoded data, and form the modulated and encoded data into orthogonal frequency division multiplexing (OFDM) and / or orthogonal frequency division multiple access (OFDMA) symbols. The transmitter can then convert the symbols from the frequency domain to the time domain for input to the TX chain, which can include a chain for each subcarrier of the RF chain's bandwidth, where the TX chain processes the time-domain signals and prepares them for transmission on the RF chain's component subcarriers. For wide-bandwidth communications, two or more of the RF chains may simultaneously process symbols representing data from the baseband processor.

[0149] The processor 570 decodes and processes digital baseband signals, or downlink data, and invokes various functional modules to perform functions in the UE 560. The memory 572 stores program instructions or code and data 574 for controlling the operation of the UE 560. The processor 570 may also execute medium access control (MAC) layer code for the UE 560. For example, the MAC layer code may execute on the processor 570 to cause UL communications to be transmitted to the base station 510 via one or more RF chains of a physical layer (PHY). The PHY is the RF circuitry 594 and associated logic, such as all or some of the functional modules.

[0150] The host circuitry 562 is capable of executing code, such as RRC layer code, to perform RRC layer functions and codes.

[0151] The base station 510 and the UE 560 may include several functional modules and circuits to perform some embodiments. Different functional modules may include circuits or circuitry that may be constructed and implemented by code, hardware, or any combination thereof. Each functional module that may implement a function as code and processing circuitry or as circuitry configured to perform a function may be referred to as a functional block. For example, the processor 520 (e.g., by executing program code 524) is a functional block that configures and implements the circuitry of the functional module, enabling the base station 510 to schedule (via scheduler 526), ​​encode or decode (via codec 528), modulate or demodulate (via modulator 530), and transmit data to or receive data from the UE 560 via RF circuitry 544 and antenna 546.

[0152] Processor 570 is a functional block for configuring and implementing the circuitry of functional modules (e.g., by executing program code in Code and Data 574) to enable UE 560 to receive or transmit, demodulate or modulate (via Demodulator 578), and decode or encode (via Codec 576) data via RF circuitry 594 and antenna 596.

[0153] In many embodiments, the UE 560 may include LP-WUR circuitry 513. The LP-WUR circuitry 513 may comprise a low-power receiver for receiving, demodulating, and decoding a LP-WUS, such as the LP-WUS described in connection with FIGS.

[0154] In some embodiments, the LP-WUR circuitry 563 of the UE 560 may include separate circuitry (RF circuitry 594, receiver circuitry 590, and transmitter circuitry 592) from the main radio. In some embodiments, the LP-WUR circuitry 563 may use the same antenna 596 as the RF circuitry 594, while in other embodiments, the LP-WUR circuitry 563 may have a separate antenna such as antenna 596. In further embodiments, the LP-WUR circuitry 563 may share some components of the RF circuitry 594, receiver circuitry 590, and transmitter circuitry 592. In other embodiments, the LP-WUR circuitry 563 may be part of the RF circuitry 594, receiver circuitry 590, and transmitter circuitry 592 and may not have separate components used exclusively for the LP-WUR circuitry 563. In many embodiments, the LP-WUR circuitry 563 may be powered on while the main radio of the UE 560 is in an off state, such as a deep sleep state during a DRX cycle.

[0155] The base station 510 may also include a functional module, LP-WUR logic 535. The LP-WUR logic 535 of the base station 510 may cause the processor 520 and / or the host circuitry 512 to perform operations to generate and cause transmission of an LP-WUS. For example, the LP-WUS may include an OFDM symbol, where transmission of a symbol or a portion of a symbol may represent transmission of a WUS symbol having a logical bit value of 1, and absence of transmission of a symbol or a portion of a symbol may represent transmission of a WUS symbol having a logical bit value of 0.

[0156] The LP-WUR logic 535 of the base station 510 may include or access configurations, definitions, and / or the like stored in memory 522 to define one or more types of LP-WUS. The LP-WUR logic 535 may maintain in memory 522 the status of the main radio and LP-WUR circuitry 563 for the UE 560 while the UE 560 is registered with the base station 510 to determine when to transmit one or more types of LP-WUS and when to communicate to the main radio to facilitate reduced power consumption by the UE 560. For example, the LP-WUR logic 535 of the base station 510 may encode, modulate, and transmit the LP-WUS along with the SIB to: communicating metrics for measurements by the LP-WUR circuit 563 of the UE 560; Facilitating performance of measurements, such as RRM measurements, by the UE 560; Facilitating cell selection / reselection performance by the UE 560; Facilitating BFD performance by the UE 560; Facilitating RLM performance by the UE 560; Facilitating performance of paging reception by the UE 560; It is possible to facilitate synchronization by the UE 560, or a combination thereof.

[0157] The UE 560 may also include a functional module, LP-WUR logic 580. The LP-WUR logic 580 of the UE 560 may cause the processor 520 and / or the host circuitry 512 to perform actions to advantageously offload functionality from the main radio (RF circuitry 594, receiver circuitry 590, and transmitter circuitry 592). The LP-WUR logic 580 of the UE 560 may receive, demodulate, decode, and interpret the LP-WUR signal by one or more processors of the LP-WUR circuitry 563 and the baseband circuitry 514. In other embodiments, the LP-WUR circuitry 563 may comprise or be coupled to a separate processor or processor core for implementation of the LP-WUR logic 580. The LP-WUR logic 580 is capable of interpreting the LP-WUS to determine metrics for measurements such as RRM measurements, perform cell selection / reselection, perform BFD, perform RLM, perform paging reception, obtain synchronization information, and in some embodiments, perform synchronization.

[0158] 6 shows a flowchart 6000 of an embodiment for cell reselection according to the S and R criteria, first by the LP-WUR of a UE via the LP-WUS and then by the main radio of the UE, such as some embodiments described in connection with FIGS. 1 through 5. Flowchart 6000 begins with the LP-WUR logic of the UE receiving, demodulating, decoding, and interpreting the LP-WUS by the LP-WUR to perform measurements, such as RRM measurements, and determine metrics, such as RSRP, RSSI, RSRQ, or a combination thereof, based on the LP-WUS (element 605). The LP-WUR logic can then calculate or determine S and R criteria for the serving cell and one or more neighbor cells and compare the S and R criteria of various cells to determine whether to select a new cell or remain camped on the serving cell.

[0159] If the UE reselects a neighbor cell according to the S-criterion and the R-criterion by the LP-WUR (element 610), the LP-WUR logic of the UE may turn on the main radio, and the LP-WUR logic may cause the main radio to re-perform RRM measurements on the serving cell and one or more neighbor cells using the S-criterion and R-criterion metrics configured for the LP-WUR (element 615), which may be predefined, preconfigured, or configured by higher layer signaling. In some embodiments, the set of neighbor cells may have a predefined, preconfigured, or configured number of neighbor cells, or a predefined, preconfigured, or configured minimum number of neighbor cells. In some embodiments, the main radio may perform RRM measurements according to a configuration for determining the S-criterion and the R-criterion metrics by the main radio, which may be predefined, preconfigured, or configured by higher layer signaling.

[0160] After determining the S-criterion and R-criterion metrics for the serving cell and one or more neighbor cells, the UE's main radio logic may perform cell reselection, which may include ranking and comparing parameters related to the S-criterion and R-criterion to select a new cell (one of the neighbor cells) or to select the serving cell (element 620).

[0161] In some embodiments, when the UE reselects a neighbor cell via the LP-WUS using the LP-WUR according to the S and R criteria, the LP-WUR logic of the UE may turn on the main radio and re-perform RRM measurements using the main radio for the serving cell and all neighbor cells configured for RRM measurements by the main radio (which may be a set of neighbor cells different from and / or overlapping with the set of neighbor cells configured for the LP-WUR). The LP-WUR logic of the UE then performs cell reselection according to the S and R criteria determined by the main radio.

[0162] In some embodiments, the S and R criteria may be the same as those defined in the current NR standard. In further embodiments, the S and R criteria may differ from those defined in the current NR standard. For example, the S and R criteria may include one or more thresholds defined for RSRP and / or RSRQ measurements.

[0163] FIG. 7 shows a flowchart 700 of an embodiment of a UE such as the embodiments described in connection with FIGS. 1 through 6. Flowchart 700 begins with LP-WUR logic of a base station of a cellular network determining that the UE is in a DRX cycle (element 705). For example, the LP-WUR logic of the base station can determine the status of the UE to be in a DRX cycle based on a DRX cycle configuration that may reside in a memory of the base station. The configuration for the DRX cycle may be determined, for example, in negotiation between the UE and the base station, and may or may not be based on a configuration, a pre-configuration, a definition, and / or the like provided by higher layer signaling.

[0164] After determining that the UE is in a DRX cycle (meaning that the UE's main radio is in deep sleep or off mode and the UE's LP-WUR is powered on), the base station's LP-WUR logic may determine and generate an LP-WUS to send to the UE to perform LP-WUR functions such as measurements, cell reselection, beam failure detection, radio link monitoring, paging reception, synchronization, a combination thereof, or the like (element 710). For example, based on services established for the UE with the base station, the base station's LP-WUR logic may determine, for example, to send an LP-WUS to the UE's LP-WUR so that the UE's LP-WUR logic can perform RRM measurements via the UE's LP-WUR. If a specific type of LP-WUS exists for that LP-WUR function (RRM measurement), the base station's LP-WUR logic may select the LP-WUS for that LP-WUR function. If there is no LP-WUS of a specific type for that function, or if there is only one type of LP-WUS, the LP-WUR logic of the base station may configure one or more parts of the LP-WUR (such as the first part and / or the second part) to perform the LP-WUS function, e.g., RRM measurements.

[0165] In some embodiments, generating the LP-WUS may include generating WUS symbols for the LP-WUS by encoding and modulating information for each of the parts of the LP-WUS to form OOK symbols, MC-OOK symbols, FSK symbols, MC-FSK symbols, and / or the like, as described in connection with other figures herein (element 715).

[0166] 8 illustrates an embodiment of a protocol entity 8000 that may be implemented in a wireless communication device as described with reference to other figures herein, including one or more of a user equipment (UE) 8060, a base station that may be referred to as an evolved Node B (eNB) or new radio, next generation Node B (gNB) 8080, and a network function that may be referred to as a mobility management entity (MME) or access and mobility management function (AMF) 8094, according to some aspects. In further embodiments, the Node B may comprise an xNode B for a 6th generation or later Node B.

[0167] According to some aspects, the gNB 8080 may be implemented as one or more dedicated physical devices such as a macro cell, a femto cell, or other suitable device, or in alternative aspects, as one or more software entities running on a server computer as part of a virtualized network referred to as a Cloud Radio Access Network (CRAN).

[0168] According to some aspects, one or more protocol entities that may be embodied in one or more of the UE 8060, the gNB 8080, and the AMF 8094 may be described as implementing all or a portion of a protocol stack, where the layers are assumed to be ordered from lowest to highest in the following order: physical layer (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and non-access stratum (NAS). According to some aspects, one or more protocol entities that may be embodied in one or more of the UE 8060, the gNB 8080, and the AMF 8094 may communicate with a respective peer protocol entity that may be implemented on another device, using the services of the respective lower layer protocol entity to perform such communication.

[0169] According to some aspects, the UE PHY layer 8072 and the peer entity gNB PHY layer 8090 can communicate using signals transmitted and received over a wireless medium. According to some aspects, the UE MAC layer 8070 and the peer entity gNB MAC layer 8088 can communicate using services provided by the UE PHY layer 872 and the gNB PHY layer 8090, respectively. According to some aspects, the UE RLC layer 8068 and the peer entity gNB RLC layer 8086 can communicate using services provided by the UE MAC layer 8070 and the gNB MAC layer 8088, respectively. According to some aspects, the UE PDCP layer 8066 and the peer entity gNB PDCP layer 8084 can communicate using services provided by the UE RLC layer 8068 and the gNB RLC layer 8086, respectively. According to some aspects, the UE RRC layer 8064 and the gNB RRC layer 8082 can communicate using services provided by the UE PDCP layer 8066 and the gNB PDCP layer 8084, respectively. According to some aspects, the UE NAS 8062 and the AMF NAS 8092 can communicate using services provided by the UE RRC layer 8064 and the gNB RRC layer 8082, respectively.

[0170] The PHY layers 8072 and 8090 may transmit or receive information used by the MAC layers 8070 and 8088 over one or more air interfaces. The PHY layers 8072 and 8090 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers such as the RRC layers 8064 and 8082. The PHY layers 8072 and 8090 may further perform error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and multiple-input multiple-output (MIMO) antenna processing.

[0171] The MAC layers 8070 and 8088 may perform mapping between logical channels and transport channels, multiplexing MAC service data units (SDUs) from one or more logical channels into transport blocks (TBs) to be delivered to the PHY via the transport channels, demultiplexing MAC SDUs from transport blocks (TBs) delivered from the PHY via the transport channels into one or more logical channels, multiplexing MAC SDUs into TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0172] The RLC layers 8068 and 8086 may operate in multiple modes of operation, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layers 8068 and 8086 may perform upper layer protocol data unit (PDU) transfer, automatic repeat request (ARQ) error correction for AM data transfer, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transfer. The RLC layers 8068 and 8086 may also perform resegmentation of RLC data PDUs for AM data transfer, reordering RLC data PDUs for UM and AM data transfer, detecting duplicate data for UM and AM data transfer, discarding RLC SDUs for UM and AM data transfer, detecting protocol errors for AM data transfer, and performing RLC re-establishment.

[0173] The PDCP layers 8066 and 8084 may perform header compression and decompression of Internet Protocol (IP) data, maintain PDCP sequence numbers (SN), perform in-sequence delivery of upper layer PDUs upon lower layer re-establishment, de-duplicate lower layer SDUs upon lower layer re-establishment for RLC AM mapped radio bearers, cipher and decrypt control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, decryption, integrity protection, integrity verification, etc.).

[0174] The main services and functions of the RRC layers 8064 and 8082 may include broadcasting of system information (e.g., contained in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the Non-Access Stratum (NAS)), broadcasting of system information related to the Access Stratum (AS), paging, establishment, maintenance, and release of RRC connections between the UE and the E-UTRAN (e.g., RRC Connection Paging, RRC Connection Establishment, RRC Connection Modification, and RRC Connection Release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, mobility between Radio Access Technologies (RATs), and measurement configuration for UE measurement reporting. The MIBs and SIBs may contain one or more information elements (IEs), each of which may contain individual data fields or data structures.

[0175] The UE 8060 and the RAN node, gNB 8080, can use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising PHY layers 8072 and 8090, MAC layers 8070 and 8088, RLC layers 8068 and 8086, PDCP layers 8066 and 8084, and RRC layers 8064 and 8082.

[0176] The Non-Access Stratum (NAS) protocol 8092 forms the highest stratum of the control plane between the UE 8060 and the AMF 8005. The NAS protocol 8092 supports the mobility of the UE 8060 and session management procedures to establish and maintain IP connectivity between the UE 8060 and a Packet Data Network (PDN) Gateway (P-GW).

[0177] 9 illustrates an embodiment of a format of a PHY data unit (PDU) that may be transmitted by a PHY device via one or more antennas and encoded and decoded by a MAC entity, such as processors 520 and 570 described in connection with FIG. 5, baseband circuitry 1304 described in connection with FIG. 13 and FIG. 14, and / or described in connection with other figures herein. In some embodiments, an upper layer frame, such as a frame comprising RRC layer information elements, may be transmitted from a base station to a UE, or vice versa, as one or more MAC service data units (MSDUs) in the payload of one or more PDUs in one or more subframes of a radio frame.

[0178] According to some aspects, the MAC PDU 9100 can be comprised of a MAC header 9105 and a MAC payload 9110, which can be comprised of zero or more MAC control elements 9130, zero or more MAC service data unit (SDU) portions 9135, and zero or one padding portion 9140. According to some aspects, the MAC header 8105 can be comprised of one or more MAC sub-headers, each of which corresponds to a MAC payload portion and can appear in a corresponding order. According to some aspects, each of the zero or more MAC control elements 9130 included in the MAC payload 9110 can correspond to a fixed-length sub-header 9115 included in the MAC header 9105. According to some aspects, each of the zero or more MAC SDU portions 9135 included in the MAC payload 9110 can correspond to a variable-length sub-header 9120 included in the MAC header 8105. According to some aspects, the padding portion 9140 included in the MAC payload 9110 may correspond to the padding sub-header 9125 included in the MAC header 9105.

[0179] 10A illustrates an embodiment of communications circuitry 1000, such as the circuitry within base station 510 and user equipment 560 shown and described in connection with FIG. 5 or other figures herein. Communications circuitry 1000 may alternatively be grouped according to function. Components such as those shown in communications circuitry 1000 are shown here for illustrative purposes and may include other components not shown in FIG. 10A.

[0180] The communications circuitry 1000 may include a protocol processing circuitry 1005, which may implement one or more of Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and Non-Access Stratum (NAS) functions. The protocol processing circuitry 1005 may include one or more processing cores (not shown) for executing instructions and one or more memory structures (not shown) for storing program (code) and data information.

[0181] The communications circuitry 1000 may further include digital baseband circuitry 1010 capable of implementing physical layer (PHY) functions including one or more of hybrid automatic repeat request (HARQ) functions, scrambling and / or descrambling, coding and / or decoding, layer mapping and / or demapping, modulation symbol mapping, received symbol and / or bit metric determination, multi-antenna port precoding and / or decoding which may include one or more of space-time, space-frequency, or spatial coding, reference signal generation and / or detection, preamble sequence generation and / or decoding, synchronization sequence generation and / or detection, control channel signal blind decoding, and other related functions.

[0182] The communications circuit 1000 may further include transmit circuitry 1015, receive circuitry 1020, and / or antenna array 1030 circuitry.

[0183] The communications circuitry 1000 may further include radio frequency (RF) circuitry 1025, such as RF circuitry 544 and 594 of Figure 2. In one aspect of the embodiment, the RF circuitry 1025 may include multiple parallel RF chains for one or more of the transmit or receive functions, each connected to one or more antennas of the antenna array 1030.

[0184] In one aspect of the present disclosure, the protocol processing circuitry 1005 may include one or more instances of control circuitry (not shown) that provides control functions for one or more of the digital baseband circuitry 1010, the transmit circuitry 1015, the receive circuitry 1020, and / or the radio frequency circuitry 1025.

[0185] 10B illustrates an embodiment of the radio frequency circuit 1025 of FIG. 10A in some aspects such as the RF circuits 544 and 594 shown and described in connection with FIG. 5 or other figures herein. The radio frequency circuit 1025 may include one or more instances of radio chain circuitry 1072, which in some aspects may include one or more filters, power amplifiers, low noise amplifiers, programmable phase shifters, and power supplies (not shown).

[0186] The radio frequency circuitry 1025 may include a power combining and distribution circuitry 1074. In some aspects, the power combining and distribution circuitry 1074 may be capable of operating bidirectionally, such that the same physical circuitry may be configured to operate as a power divider when the device is transmitting and as a power combiner when the device is receiving. In some aspects, the power combining and distribution circuitry 1074 may include one or more fully or partially separate circuits to perform power distribution when the device is transmitting and power combining when the device is receiving. In some aspects, the power combining and distribution circuitry 1074 may include passive circuitry comprising one or more bidirectional power dividers / combiners arranged in a tree configuration. In some aspects, the power combining and distribution circuitry 1074 may include active circuitry comprising amplifier circuitry.

[0187] In some aspects, the radio frequency circuitry 1025 can be connected to the transmit circuitry 1015 and receive circuitry 1020 of Figure 10A via one or more radio chain interfaces 1076 or a combined radio chain interface 1078. The combined radio chain interface 1078 can provide a wide or very wide bandwidth.

[0188] In some aspects, one or more radio chain interfaces 1076 may provide one or more interfaces for one or more receive or transmit signals, each associated with a single antenna structure that may include one or more antennas.

[0189] In some aspects, the multiple radio chain interface 1078 may provide a single interface for one or more receive or transmit signals, each of which is associated with a group of antenna structures comprising one or more antennas.

[0190] FIG. 11 illustrates an example of a storage medium 1100 that stores code and data for execution by any one or more of the processors and / or processing circuits to perform the functions of the logic circuits described herein in connection with FIGS. 1 through 10 and 12 through 15. The storage medium 1100 may include an article of manufacture. In some examples, the storage medium 1100 may include any non-transitory computer-readable or device-readable medium, such as optical, magnetic, or semiconductor storage devices. The storage medium 1100 may store various types of computer-executable instructions, such as instructions for implementing the logic flows and / or techniques described herein. Examples of computer-readable or device-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or rewritable memory, etc. Examples of computer-executable instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like.

[0191] Figure 12 illustrates the architecture of a system 1200 of a network according to some embodiments. System 1200 is shown to include user equipment (UE) 1510, such as the UEs described in connection with Figures 1 through 11, and UE 1522. UEs 1510 and 1522 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may comprise any mobile or non-mobile computing device, such as a personal digital assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, or any computing device that includes a wireless communications interface.

[0192] In some embodiments, either UE 1510 or 1522 may comprise an Internet of Things (IoT) UE, which may have a network access layer designed for low-power IoT applications that utilize short-lived UE connections. IoT UEs may use technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with MTC servers or devices via public land mobile networks (PLMNs), proximity-based services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be device-initiated data exchanges. IoT networks interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. IoT UEs may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate IoT network connectivity.

[0193] The UEs 1510 and 1522 may connect to, e.g., be communicatively coupled to, a radio access network (RAN), in this embodiment, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 1210, such as the base stations shown in Figures 1 through 11. UEs 1510 and 1522 utilize connections 1520 and 1204, respectively, each of which comprises a physical communication interface or layer (described in more detail below); in this example, connections 1520 and 1204 are shown as air interfaces for enabling communication coupling and may conform to cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, and the like.

[0194] In this embodiment, the UEs 1510 and 1522 may further directly transmit and receive communication data via the ProSe interface 1205. The ProSe interface 1205 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0195] UE 1522 is shown configured to access access point (AP) 1206 via connection 1207. Connection 1207 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, and AP 1206 comprises a Wireless Fidelity (WiFi) router. In this example, AP 1206 is shown connected to the Internet without connecting to a wireless system core network (described in further detail below). E-UTRAN 1210 may include one or more access nodes that enable connections 1520 and 1204. These access nodes (ANs) may be referred to as base stations (BSs), Node Bs, evolved Node Bs (eNBs), next generation Node Bs (gNBs), RAN nodes, etc., and may comprise earth stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). The E-UTRAN 1210 may include one or more RAN nodes for providing macro cells, such as a macro RAN node 1560, and one or more RAN nodes for providing femto cells or pico cells (e.g., cells having a smaller coverage area, lower user capacity, or higher bandwidth compared to a macro cell), such as a low power (LP) RAN node 1572.

[0196] Either of the RAN nodes 1560 and 1572 may terminate air interface protocols and may be the first point of contact for the UEs 1510 and 1522. In some embodiments, either of the RAN nodes 1560 and 1572 may perform various logical functions for the E-UTRAN 1210, including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0197] According to some embodiments, the UEs 1510 and 1522 may be configured to communicate with each other or with the RAN nodes 1560 and 1572 over multi-carrier communication channels using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques (e.g., but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communication) or a single-carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communication)), although the scope of the embodiments is not limited in this respect. The OFDM signals may comprise multiple orthogonal subcarriers.

[0198] In some embodiments, a downlink resource grid may be used for downlink transmissions from either RAN node 1560 or 1572 to UEs 1510 and 1522, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, also referred to as a resource grid or time-frequency resource grid, that represents the physical resources in the downlink in each slot. This time-frequency plane representation is common practice for OFDM systems and provides an intuitive representation of radio resource allocation. Each column and row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid contains several resource blocks, which describe the mapping of a particular physical channel to resource elements. Each resource block contains a collection of resource elements; in the frequency domain, this may represent the smallest amount of resources currently available for allocation. There are several different physical downlink (DL) channels that are carried using such resource blocks.

[0199] The physical downlink shared channel (PDSCH) may carry user data and higher layer signaling to the UEs 1510 and 1522. The physical downlink control channel (PDCCH) may carry, among other things, information about the transport format and resource allocation associated with the PDSCH channel. It may also inform the UEs 1510 and 1522 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to the UEs 102 within a cell) may be performed in either of the RAN nodes 1560 and 1572 based on channel quality information fed back from either of the UEs 1510 and 1522. Downlink resource allocation information may be transmitted on the PDCCH used for (e.g., assigned to) each of the UEs 1510 and 1522.

[0200] The PDCCH may use control channel elements (CCEs) to carry control information. Before being mapped to resource elements, PDCCH complex-valued symbols may first be organized into quadruplets, which may then be reordered using a subblock interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel conditions. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8).

[0201] Some embodiments may use a concept of resource allocation for control channel information that is an extension of the concept described above. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced control channel elements (ECCEs). As above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[0202] The RAN nodes 1560 and 1572 may communicate with each other and / or with other access nodes in other RANs and / or in the E-UTRAN 1210 via the X2 interface, which is a signaling interface for communicating data packets between ANs. Any other suitable interface for directly communicating data packets between ANs may also be used.

[0203] The E-UTRAN 1210 is shown communicatively coupled to a core network, in this embodiment, an Evolved Packet Core (EPC) network 1220, via an SI interface. In this embodiment, the SI interface 1570 is divided into two parts: an SI-U interface 1214, which carries traffic data between the RAN nodes 1560 and 1572 and a Serving Gateway (S-GW) 1222, and an SI-Mobility Management Entity (MME) interface 1215, which is a signaling interface between the RAN nodes 1560 and 1572 and the MME 1546.

[0204] In this embodiment, the EPC network 1220 includes an MME 1546, an S-GW 1222, a packet data network (PDN) gateway (P-GW) 1223, and a home subscriber server (HSS) 1224. The MME 1546 may be functionally similar to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 1546 may manage mobility aspects of access, such as gateway selection and tracking area list management. The HSS 1224 may include a database for network users, including subscription-related information to support network entity processing of communication sessions. The EPC network 1220 may include one or more HSSs 1224, depending on the number of mobile subscribers, device capabilities, network organization, etc. For example, the HSS 1224 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0205] The S-GW 1222 terminates the SI interface 1570 towards the E-UTRAN 1210 and can route data packets between the E-UTRAN 1210 and the EPC network 1220. Additionally, the S-GW 1222 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0206] The P-GW 1223 may terminate the SGi interface toward the PDN. The P-GW 1223 may route data packets between the EPC network 1220 and an external network, such as a network including an application server 1230 (alternatively referred to as an application function (AF)), via an Internet Protocol (IP) interface 1225. In general, the application server 1230 may be an element that provides applications (e.g., a UMTS packet service (PS) domain, an LTE PS data service, etc.) that use IP bearer resources in conjunction with the core network. In this embodiment, the P-GW 1223 is shown communicatively coupled to the application server 1230 via the IP interface 1225. The application server 1230 may also be configured to support one or more communication services (e.g., a voice over Internet Protocol (VoIP) session, a PTT session, a group communication session, a social networking service, etc.) for the UEs 1510 and 1522 via the EPC network 1220.

[0207] The P-GW 1223 may also be a node for policy enforcement and charging data collection. The Policy and Charging Enforcement Function (PCRF) 1226 is the policy and charging control element of the EPC network 1220. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with localized traffic disruption, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). The PCRF 1226 may be communicatively coupled to the application server 1230 via the P-GW 1223. The application server 1230 may signal the PCRF 1226 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. The PCRF 1226 can prepare this rule with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI) to the Policy and Charging Enforcement Function (PCEF) (not shown), which initiates QoS and charging as specified by the application server 1230.

[0208] FIG. 13 illustrates example components of a device 1300 according to some embodiments, such as the base station and UE described in connection with FIGS. 1-12 . In some embodiments, the device 1300 may include an application circuit 1302, a baseband circuit 1304, a radio frequency (RF) circuit 1306, a front-end module (FEM) circuit 1308, one or more antennas 1310, and a power management circuit (PMC) 1312, coupled together at least as shown. The illustrated components of the device 1300 may be included in a UE or a RAN node, such as a base station or gNB. In some embodiments, the device 1300 may include fewer elements (e.g., a RAN node may not utilize the application circuit 1302 and instead may include a processor / controller for processing IP data received from an EPC). In some embodiments, the device 1300 may include additional elements, such as memory / storage, a display, a camera, sensors, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the aforementioned circuits may be included separately in more than one device for a Cloud RAN (C-RAN) implementation).

[0209] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include, but is not limited to, one or more single-core or multi-core processor-like circuitry. The processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 1300. In some embodiments, the processor of the application circuit 1302 is capable of processing IP data packets received from the EPC.

[0210] The baseband circuitry 1304 may include, but is not limited to, one or more single-core or multi-core processor-like circuitry. The baseband circuitry 1304 may include one or more baseband processors or control logic for processing baseband signals received from the receive signal path of the RF circuitry 1306 and generating baseband signals for the transmit signal path of the RF circuitry 1306. The baseband circuitry 1304 may interface with the application circuitry 1302 for generating and processing the baseband signals and for controlling the operation of the RF circuitry 1306. For example, in some embodiments, the baseband circuitry 1304 may include a third-generation (3G) baseband processor 1304A, a fourth-generation (4G) baseband processor 1304B, a fifth-generation (5G) baseband processor 1304C, or other baseband processors 1304D for other existing, developing, or future generations (e.g., second generation (2G), sixth generation (6G), etc.). In many embodiments, the fourth generation (4G) baseband processor 1304B may include baseband signal generation and processing capabilities for LTE radios, and the fifth generation (5G) baseband processor 1304C may include baseband signal generation and processing capabilities for NR.

[0211] The baseband circuitry 1304 (e.g., one or more of the baseband processors 1304A-D) may process various radio control functions that enable communication with one or more wireless networks via the RF circuitry 1306. In other embodiments, all or part of the functionality of the baseband processors 1304A-D may be contained in modules stored in memory 1304G and executed via a central processing unit (CPU) 1304E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc.

[0212] In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 1304 may include Fast Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 1304 may include convolution, tail-biting convolution, Turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Embodiments of the modulation / demodulation and encoder / decoder functionality are not limited to these examples, and other embodiments may include other functionality as appropriate.

[0213] In some embodiments, the baseband circuitry 1304 may include one or more audio digital signal processors (DSPs) 1304F. The audio DSPs 1304F may include elements for compression / decompression and echo cancellation, and in other embodiments, may include other suitable processing elements. The components of the baseband circuitry may be suitably combined on a single chip, a single chipset, or, in some embodiments, may be located on the same circuit board. In some embodiments, some or all of the components of the baseband circuitry 1304 and the application circuitry 1302 may be implemented together, such as in a system-on-chip (SOC). In some embodiments, the baseband circuitry 1304 may provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry 1304 may support communication with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), or wireless personal area networks (WPANs). An embodiment in which the baseband circuitry 1304 is configured to support wireless communication of more than one wireless protocol may be referred to as a multi-mode baseband circuitry.

[0214] The RF circuitry 1306 can enable communication with a wireless network using modulated electromagnetic radiation via a non-solid medium. In various embodiments, the RF circuitry 1306 can include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuitry 1306 can include a receive signal path, which can include circuitry to downconvert RF signals received from the FEM circuitry 1308 and provide baseband signals to the baseband circuitry 1304. The RF circuitry 1306 can also include a transmit signal path, which can include circuitry to upconvert baseband signals provided by the baseband circuitry 1304 and provide an RF output signal to the FEM circuitry 1308 for transmission.

[0215] In some embodiments, the receive signal path of the RF circuitry 1306 may include a mixer circuit 1306a, an amplifier circuit 1306b, and a filter circuit 1306c. In some embodiments, the transmit signal path of the RF circuitry 1306 may include a filter circuit 1306c and a mixer circuit 1306a. The RF circuitry 1306 may also include a synthesizer circuit 1306d for synthesizing frequencies or component carriers for use by the mixer circuit 1306a of the receive and transmit signal paths. In some embodiments, the mixer circuit 1306a of the receive signal path may downconvert the RF signal received from the FEM circuitry 1308 based on the synthesized frequency provided by the synthesizer circuit 1306d. The amplifier circuit 1306b may amplify the downconverted signal, and the filter circuit 1306c may be a low-pass filter (LPF) or a band-pass filter (BPF) for removing unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1304 for further processing.

[0216] In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required. In some embodiments, the mixer circuit 1306a in the receive signal path may comprise a passive mixer, although the scope of embodiments is not limited in this respect.

[0217] In some embodiments, the mixer circuit 1306a in the transmit signal path may be configured to upconvert an input baseband signal based on a synthesis frequency provided by the synthesizer circuit 1306d to generate an RF output signal for the FEM circuit 1308. The baseband signal may be provided by the baseband circuit 1304 and may be filtered by the filter circuit 1306c.

[0218] In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may include two or more mixers and may be configured for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may include two or more mixers and may be configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may be configured for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 1306a in the receive signal path and the mixer circuit 1306a in the transmit signal path may be configured for superheterodyne operation.

[0219] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuitry 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 1304 may include a digital baseband interface for communicating with the RF circuitry 1306.

[0220] In some dual-mode embodiments, separate radio IC circuitry may be provided to process signals in each spectrum, although the scope of the embodiments is not limited in this respect.

[0221] In some embodiments, synthesizer circuit 1306d may be a fractional-N synthesizer or a fractional NIN+I synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 1306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0222] The synthesizer circuit 1306d is capable of synthesizing an output frequency used by the mixer circuit 1306a of the RF circuit 1306 based on the frequency input and the divider control input. In some embodiments, the synthesizer circuit 1306d may be a fractional N+I synthesizer.

[0223] In some embodiments, the frequency input may be the output of a voltage-controlled oscillator (VCO), although this is not required. The divider control input may be the output of either the baseband circuitry 1304 or the application processor of the application circuitry 1302, depending on the desired output frequency. Some embodiments may determine the divider control input (e.g., N) from a look-up table based on the channel indicated by the application circuitry 1302.

[0224] The synthesizer circuit 1306d of the RF circuit 1306 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry-out) to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a set of cascaded adjustable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may divide the VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0225] In some embodiments, the synthesizer circuit 1306d may generate the carrier frequency (or component carrier) as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with different phases relative to each other. In some embodiments, the output frequency may be the local oscillator (LO) frequency (fLO). In some embodiments, the RF circuit 1306 may include an IQ-to-polar converter.

[0226] The FEM circuitry 1308 may include a receive signal path that may include circuitry for operating on RF signals received from one or more antennas 1310, amplifying the received signals, and providing an amplified version of the received signals to the RF circuitry 1306 for further processing. The FEM circuitry 1308 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1306 for transmission by one or more of the one or more antennas 1310. In various embodiments, amplification through the transmit or receive signal path may occur solely in the RF circuitry 1306, solely in the FEM circuitry 1308, or in both the RF circuitry 1306 and the FEM circuitry 1308.

[0227] In some embodiments, the FEM circuitry 1308 may include a TX / RX switch for switching between transmit and receive modes of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low noise amplifier (LNA) for amplifying a received RF signal and providing the amplified received RF signal as an output (e.g., to the RF circuitry 1306). The transmit signal path of the FEM circuitry 1308 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuitry 1306) and one or more filters for generating an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1310).

[0228] In this embodiment, the radio section refers to the combination of the RF circuitry 1306 and the FEM circuitry 1308. The radio section refers to the portion of the circuitry that generates, transmits, receives, and processes radio signals. The RF circuitry 1306 includes a transmitter section for generating a time-domain radio signal using data from a baseband signal and applying the radio signal to subcarriers of a carrier frequency that form the channel bandwidth. A PA in the FEM circuitry 1308 amplifies tones for transmission and amplifies received tones from one or more antennas 1310 via an LNA to increase the signal-to-noise ratio (SNR) for interpretation. In wireless communications, the FEM circuitry 1308 can also search for detectable patterns that appear to be wireless communications. The receiver section in the RF circuitry 1306 then converts the time-domain radio signal to a baseband signal using one or more functional modules, such as those shown in the base station 510 and user device 560 shown in FIG. 2.

[0229] In some embodiments, the PMC 1312 may manage the power provided to the baseband circuitry 1304. In particular, the PMC 1312 may control power source selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1312 may often be included when the device 1300 may be battery powered, for example, when the device is included within a UE. The PMC 1312 may increase power conversion efficiency while providing desirable packaging size and heat dissipation characteristics.

[0230] 13 shows the PMC 1312 coupled only to the baseband circuitry 1304. However, in other embodiments, the PMC 1312 may additionally or alternatively be coupled to and perform similar power management operations for other components, such as, but not limited to, the application circuitry 1302, the RF circuitry 1306, or the FEM circuitry 1308.

[0231] In some embodiments, the PMC 1312 may control or otherwise be a part of various power saving mechanisms of the device 1300. For example, if the device 1300 is in the RRC_Connected state (still connected to a RAN node with the expectation of receiving traffic soon), after a period of inactivity, it may enter a state known as Discontinuous Reception Mode (DRX). During this state, the device 1300 may power down for a short interval of time, thus conserving power.

[0232] If there is no data traffic activity for an extended period of time, the device 1300 can transition to an RRC idle state, in which case the device disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 102 goes into a very low power state, performs paging, then wakes up periodically to listen to the network again, and then powers down again. The device 1300 may not receive data in this state and must transition back to the RRC connected state to receive data.

[0233] Additional power saving modes may allow a device to be unavailable to the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unreachable by the network and may even power down completely. Any data transmitted during this time will incur a large delay, and it is assumed that this delay is acceptable.

[0234] The processor of the application circuit 1302 and the processor of the baseband circuit 1304 may be used to execute elements of one or more instances of a protocol stack. For example, the processor of the baseband circuit 1304 may be used, alone or in combination, to execute Layer 3, Layer 2, or Layer 1 functions, while the processor of the application circuit 1302 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functions (e.g., Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) layers). As referred to herein, Layer 3 may comprise a Radio Resource Control (RRC) layer, which is described in further detail below. As referred to herein, Layer 2 may comprise a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which are described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE / RAN node, which is described in further detail below.

[0235] FIG. 14 illustrates an example interface for a baseband circuit according to some embodiments, such as the baseband circuitry shown and / or described in connection with FIGS. 1-13. As discussed above, the baseband circuitry 1304 of FIG. 13 may include processors 1304A-1304E and memory 1304G used by the processors. Each of the processors 1304A-1304E may include a memory interface 1404A-1404E, respectively, for transmitting / receiving data to / from the memory 1304G.

[0236] The baseband circuit 1304 may further include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 1412 (e.g., an interface for sending / receiving data to / from memory external to the baseband circuit 1304), an application circuit interface 1414 (e.g., an interface for sending / receiving data to / from the application circuit 1302 of FIG. 13), an RF circuit interface 1416 (e.g., an interface for sending / receiving data to / from the RF circuit 1306 of FIG. 13), a wireless hardware connection interface 1418 (e.g., an interface for sending / receiving data to / from near field communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1420 (e.g., an interface for sending / receiving power or control signals to / from the PMC 1312).

[0237] 15 is a block diagram illustrating components, according to some example embodiments, capable of reading instructions from a device-readable or computer-readable medium (e.g., a non-transitory device-readable storage medium) and performing any one or more of the methodologies described herein in connection with FIGS. 1-14. Specifically, FIG. 15 illustrates a diagrammatic representation of hardware resources 1500, including one or more processors (or processor cores) 1510, one or more memory / storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1502 may execute to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1500.

[0238] Processor 1510 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1512 and processor 1514.

[0239] The memory / storage device 1520 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1520 may include any type of volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0240] Communications resources 1530 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1504 or one or more databases 1506 over network 1508. For example, communications resources 1530 may include wired communications components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communications components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communications components.

[0241] The instructions 1550 may include software, programs, applications, applets, apps, or other executable code that cause at least one of the processors 1510 to perform any one or more of the methods described herein. The instructions 1550 may reside, completely or partially, within at least one of the processors 1510 (e.g., in a processor's cache memory), within the memory / storage device 1520, or any suitable combination thereof. Furthermore, any portion of the instructions 1550 may be transferred to the hardware resources 1500 from within any combination of the peripheral device 1504 or the database 1506. Thus, the memory of the processor 1510, the memory / storage device 1520, the peripheral device 1504, and the database 1506 are examples of computer-readable and device-readable media.

[0242] In embodiments, one or more elements of Figures 12, 13, 14, and / or 15 may be configured to perform one or more processes, techniques, or methods, or portions thereof, described herein. In embodiments, one or more elements of Figures 12, 13, 14, and / or 15 may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described in the following examples.

[0243] As used herein, the term "circuitry" may refer to, be part of, or include application-specific integrated circuits (ASICs), electronic circuits, processors (shared, dedicated, or groups), and / or memories (shared, dedicated, or groups), combinatorial logic circuits, and / or other suitable hardware components that provide the described functionality, executing one or more software or firmware programs.

[0244] Various examples may be implemented using hardware elements, software elements, or a combination of both. In some examples, hardware elements may include devices, components, processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory units, logic gates, registers, semiconductor devices, chips, microchips, chip sets, etc. In some examples, software elements may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (APIs), instruction sets, opcodes, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. The decision of whether an embodiment is implemented using hardware and / or software elements may vary according to any number of factors, such as desired computing speed, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints, as desired for a given implementation.

[0245] Some embodiments may be described using the phrase "in one example" or "example," along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with that example is included in at least one example. The appearances of the phrase "in one example" in various places in the specification do not necessarily all refer to the same example.

[0246] Some embodiments may be described using the terms "coupled" and "connected," along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, a description using the terms "connected" and / or "coupled" can indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" can also mean that two or more elements are not in direct contact with each other, but yet still cooperate or interact with each other.

[0247] Furthermore, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single example for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in fewer than all features of a single disclosed example. Accordingly, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate example. In the appended claims, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Furthermore, the terms "first," "second," "third," etc. are used merely as labels and are not intended to impose numerical requirements on their subject matter.

[0248] Although the subject matter has been described in language specific to structural features and / or method acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0249] A data processing system suitable for storing and / or executing program code will include at least one processor coupled directly or indirectly to memory elements via a system bus. The memory elements may include local memory, mass storage, and cache memory used during the actual execution of the program code, providing temporary storage of at least some of the program code to reduce the number of times the code must be retrieved from mass storage during execution. The term "code" covers a broad range of software components and configurations, including applications, drivers, processes, routines, methods, modules, firmware, microcode, and subprograms. Accordingly, the term "code" may be used to refer to any collection of instructions that, when executed by a processing system, perform a desired action or operation.

[0250] The processing circuits, logic circuits, devices, and interfaces described herein may be implemented in hardware and / or perform functions implemented in conjunction with code running on one or more processors. A processing circuit or logic circuit refers to hardware or hardware and code that performs one or more logical functions. A circuit is hardware and may refer to one or more circuits. Each circuit may perform a specific function. The circuitry may include discrete electrical components interconnected with one or more conductors, integrated circuits, chip packages, chip sets, memory, or the like. Integrated circuits include circuits formed on substrates such as silicon wafers and may include components. Additionally, integrated circuits, processor packages, chip packages, and chip sets may include one or more processors.

[0251] A processor can receive signals, such as instructions and / or data, at inputs and process the signals to generate at least one output. During execution of the code, the code changes the physical state and characteristics of the transistors that make up the processor pipeline. The physical states of the transistors are converted into logical bits of 1 and 0 that are stored in registers within the processor. The processor can transfer the physical states of the transistors to the registers and transfer the physical states of the transistors to another storage medium.

[0252] A processor may comprise a circuit or circuit configuration for performing one or more sub-functions implemented to perform the overall function of the "processor." Note that a "processor" may comprise one or more processors, each of which may comprise one or more processor cores that process code and / or data independently or interdependently. Each of the processor cores is also a "processor" and is only distinguishable from a processor to describe the physical arrangement or architecture of a processor having multiple processor cores on one or more dies and / or in one or more chip packages. A processor core may comprise a general-purpose processing core or a processor core configured to perform a specific task, depending on the processor design. A processor core may be a processor having one or more processor cores. When describing functions performed by a processor, processing circuit, or the like as described and claimed herein, the processor, processing circuit, or the like may comprise one or more processors, each having one or more processor cores, and any one or more of the processors and / or processor cores may reside on one or more dies in one or more chip packages and may perform some or all of the processing required to perform the function.

[0253] An example of a processor is a state machine or application specific integrated circuit (ASIC) that includes at least one input and at least one output, and is capable of manipulating the at least one input to generate at least one output by performing a predetermined series of serial and / or parallel operations or transformations on the at least one input.

[0254] Some Advantages of the Embodiments While not an exhaustive list, some embodiments have one or more potential advantageous effects. Improvements may advantageously include: Encoding, modulating, and transmitting SIBs with metrics for measurements by LP-WUR; Receive, decode, and interpret SIBs with metrics for measurements by the LP-WUR; Performing measurements such as RRM measurements with LP-WUR; performing cell selection and / or cell reselection by the LP-WUR and / or by the main radio part; To perform beam fault detection (BFD) by LP-WUR; Performing Radio Link Monitoring (RLM) via LP-WUR; Determining paging reception by LP-WUR; Obtaining synchronization through LP-WUR; Enabling longer DRX cycles by the main radio of the UE by waking up the main radio as needed; and / or the like, advantageously reduces power consumption by the main radio of the UE.

[0255] Further embodiment examples The following examples relate to further embodiments, and particulars in the examples may be used anywhere in one or more of the embodiments.

[0256] Example 1 is an apparatus for a user equipment (UE) supporting low power wake-up wireless signaling, comprising: an interface; and a processing circuit coupled to the interface; wherein the processing circuit operates to decode a low power wake-up signal (LP-WUS) received via the interface, the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols being modulated with on-off keying (OOK) modulation or frequency shift keying (FSK) modulation, and the LP-WUS including information for performing at least one low power wake-up wireless unit (LP-WUR) function by the LP-WUR of the UE while a main wireless unit of the UE is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and wherein the processing circuit operates to determine at least one metric based on the measurement.

[0257] In Example 2, in the device of Example 1, the processing circuit includes a processor and a memory coupled to the processor, and the device further includes a main radio unit and a LP-WUR coupled to the processing circuit, and one or more antennas coupled to radio frequency circuits of the main radio unit and the LP-WUR.

[0258] In Example 3, in the apparatus of Example 1, the at least one metric includes a reference signal received power (RSRP), a reference signal received quality (RSRQ), a reference signal strength indicator (RSSI), or a combination thereof.

[0259] In Example 4, in the apparatus of Example 3, determining the at least one metric is based on an average received power P for OOK symbol k. k Determination of and the following formula:

number

[0260] In Example 5, in the apparatus of Example 4, determining the at least one metric is based on an average received power P for OOK symbol k. k Determination of and the following formula:

number

[0261] In Example 6, in the apparatus of Example 1, the S criterion and the R criterion for cell selection are defined using radio resource management (RRM) measurements for LP-WUS.

[0262] In Example 7, in the device of any one of Examples 1 to 6, the processor further performs an operation of performing cell reselection, waking up the main radio unit, and performing joint RRM measurement based on the RRM measurement by the LP-WUR and the RRM measurement by the main radio unit.

[0263] In Example 8, in the device of any one of Examples 1 to 6, the processor performs cell reselection and wakes up the main radio unit when the neighbor cell is selected.

[0264] Example 9 is a device-readable medium containing instructions that, when executed by a processor, cause a processor of a base station to perform an operation; The operations include decoding a low power wake-up signal (LP-WUS) received over the interface, the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols being modulated with on-off keying (OOK) modulation or frequency shift keying (FSK) modulation, the LP-WUS including information for performing at least one low power wake-up radio (LP-WUR) function by the LP-WUR of the UE while the main radio of the UE is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and The operations include determining at least one metric based on the measurements.

[0265] In Example 10, in the device-readable medium of Example 9, the at least one metric includes a reference signal received power (RSRP), a reference signal received quality (RSRQ), a reference signal strength indicator (RSSI), or a combination thereof.

[0266] In Example 11, the device-readable medium of Example 10, wherein determining the at least one metric is based on an average received power P for OOK symbol k. k Determination of and the following formula:

number

[0267] In Example 12, the device-readable medium of Example 11, wherein determining the at least one metric is based on an average received power P for OOK symbol k. k Determination of and the following formula:

number

[0268] In Example 13, in the device-readable medium of Example 9, the processor performs cell reselection, and when a neighbor cell is selected according to the S criteria and R criteria for the LP-WUR, wakes up the main radio unit and redoes radio resource management (RRM) measurements for the LP-WUS for one or more neighbor cells using metrics of the S criteria and R criteria for the LP-WUR.

[0269] In Example 14, in the device-readable medium of any of Examples 9 to 12, the processor performs cell reselection, and if a neighbor cell is selected according to the S criteria and R criteria for the LP-WUR, wakes up the main radio unit and redoes radio resource management (RRM) measurements for the serving cell and one or more neighbor cells using metrics of the S criteria and R criteria for the main radio unit.

[0270] Example 15 is an apparatus for a base station supporting low-power wake-up wireless signaling, comprising: an interface; and a processing circuit coupled to the interface; The processing circuitry is operative to generate a low power wake-up signal (LP-WUS) for a user equipment (UE), the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols being modulated with on-off keying (OOK) modulation or frequency shift keying (FSK) modulation, the LP-WUS including information for performing at least one low power wake-up radio (LP-WUR) function by the LP-WUR of the UE while the main radio of the UE is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and The processing circuitry operates to cause transmission of said LP-WUS over the interface.

[0271] In Example 16, in the device of Example 15, the processing circuit includes a processor and a memory coupled to the processor, and the device further includes a main radio unit and a LP-WUR coupled to the processing circuit, and one or more antennas coupled to radio frequency circuits of the main radio unit and the LP-WUR.

[0272] In Example 17, in the apparatus of Example 16, the processing circuitry further performs the operation of generating a second LP-WUS configured for the LP-WUR to perform paging reception.

[0273] In Example 18, the apparatus of Example 15, wherein the LP-WUS comprises a first type of LP-WUS of the more than one type of LP-WUS.

[0274] In Example 19, in the apparatus of Example 15, the LP-WUS includes a first part and a second part, the first part includes a sequence, and the second part includes information.

[0275] In Example 20, in the device of any of Examples 16 to 19, the LP-WUS is configured to cause the LP-WUR to perform cell reselection, beam failure detection (BFD), radio link monitoring (RLM), synchronization, or a combination thereof.

[0276] Example 21 is a method including any of the operations recited in any one of Examples 1-20.

[0277] Example 22 is an apparatus including means for any of the methods in Example 21.

[0278] Example 23 is a device-readable medium containing instructions that, when executed by a processor, cause the processor to perform operations, the operations including any of the methods in example 21.

Claims

1. 1. An apparatus for a user equipment (UE) supporting low power wake-up wireless signaling, comprising: interface; and a processing circuit coupled to the interface; the processing circuitry is operable to decode a low power wake-up signal (LP-WUS) received via the interface, the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols being modulated with On-Off Keying (OOK) modulation or Frequency Shift Keying (FSK) modulation, the LP-WUS including information for performing at least one low power wake-up radio (LP-WUR) function by the UE's LP-WUR while the UE's main radio is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and The processing circuitry is operable to determine at least one metric based on the measurements.

2. 2. The device of claim 1, wherein the processing circuitry includes a processor and a memory coupled to the processor, and the device further includes the main radio unit and the LP-WUR coupled to the processing circuitry, and one or more antennas coupled to radio frequency circuits of the main radio unit and the LP-WUR.

3. 10. The apparatus of claim 1, wherein the at least one metric comprises a Reference Signal Received Power (RSRP), a Reference Signal Received Quality (RSRQ), a Reference Signal Strength Indicator (RSSI), or a combination thereof.

4. 4. The apparatus of claim 3, wherein the determination of the at least one metric is based on an average received power P for OOK symbol k. k and the following formula: [Equation 10] b) determining the RSRP by k are the bits of a sequence of N OOK symbols, and b k = 0 or 1, and c is a scaling factor.

5. 5. The apparatus of claim 4, wherein the determination of the at least one metric is based on an average received power P for OOK symbol k. k and the following formula: [0011] P of N OOK symbols by k and determining the RSSI by averaging k=0 to N−1, where k=0 to N−1 and c is a scaling factor.

6. 10. The apparatus of claim 1, wherein S and R criteria for cell selection are defined using radio resource management (RRM) measurements for the LP-WUS.

7. 7. The apparatus according to claim 1, wherein the processor further performs an operation of performing cell reselection, waking up the main radio unit, and performing joint RRM measurements based on RRM measurements by a LP-WUR and RRM measurements by the main radio unit.

8. 7. The apparatus of claim 1, wherein the processor performs cell reselection and wakes up the main radio unit when a neighbor cell is selected.

9. A computer program product causing a processor of a base station to perform operations comprising: The operations include decoding a low power wake-up signal (LP-WUS) received over an interface, the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols modulated with On-Off Keying (OOK) modulation or Frequency Shift Keying (FSK) modulation, the LP-WUS including information for performing at least one low power wake-up radio (LP-WUR) function by the UE's LP-WUR while the UE's main radio is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and The computer program product, wherein the operations include determining at least one metric based on the measurements.

10. 10. The computer program of claim 9, wherein the at least one metric comprises Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Strength Indicator (RSSI), or a combination thereof.

11. 11. The computer program of claim 10, wherein the determination of the at least one metric is based on an average received power P for OOK symbol k. k and the following formula: [0012] b) determining the RSRP by k are the bits of a sequence of N OOK symbols, and b k = 0 or 1, and c is a scaling factor.

12. 12. The computer program of claim 11, wherein the determination of the at least one metric is based on an average received power P for OOK symbol k. k and the following formula: [0013] P of N OOK symbols by k and determining the RSSI by averaging k=0 to N−1, where k=0 to N−1 and c is a scaling factor.

13. 10. The computer program of claim 9, wherein the processor performs cell reselection, and when a neighbor cell is selected according to the S criteria and R criteria for the LP-WUR, wakes up the main radio unit and redoes radio resource management (RRM) measurements for the LP-WUS for one or more neighbor cells using metrics of the S criteria and R criteria for the LP-WUR.

14. 13. The computer program of claim 9, wherein the processor performs cell reselection and, if a neighbor cell is selected according to the S-criterion and the R-criterion for the LP-WUR, wakes up the main radio unit and redoes radio resource management (RRM) measurements for a serving cell and one or more neighbor cells using metrics of the S-criterion and the R-criterion for the main radio unit.

15. 1. An apparatus for a base station supporting low power wake-up wireless signaling, comprising: interface; and a processing circuit coupled to the interface; the processing circuitry is operable to generate a low power wake-up signal (LP-WUS) for a user equipment (UE), the LP-WUS including wake-up signal (WUS) symbols, the WUS symbols being modulated with on-off keying (OOK) modulation or frequency shift keying (FSK) modulation, the LP-WUS including information for performing at least one low power wake-up radio (LP-WUR) function by the UE's LP-WUR while a main radio of the UE is powered off, the LP-WUR function including measuring at least a portion of the LP-WUS; and The processing circuitry performs operations to cause transmission of the LP-WUS by the interface.

16. 16. The apparatus of claim 15, wherein the processing circuitry includes a processor and a memory coupled to the processor, and the apparatus further includes a radio frequency circuitry coupled to the processing circuitry, and one or more antennas coupled to the radio frequency circuitry.

17. 16. The apparatus of claim 15, wherein the processing circuitry is further operable to generate a second LP-WUS configured for the LP-WUR to perform paging reception.

18. 16. The apparatus of claim 15, wherein the LP-WUS comprises a first type of LP-WUS of more than one type of LP-WUS.

19. 16. The apparatus of claim 15, wherein the LP-WUS includes a first part and a second part, the first part including a sequence and the second part including the information.

20. 20. The apparatus of any one of claims 16 to 19, wherein the LP-WUS is configured to enable the LP-WUR to perform cell reselection, beam failure detection (BFD), radio link monitoring (RLM), synchronization, or a combination thereof.

Images