Wake-up Signal Design

Abstract

The present disclosure relates to wake-up signal design. A technique for a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network is disclosed. The UE may be configured to: identify a resource set of the WUS having a repetition level, wherein: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set; and switch from a power saving mode (PSM) to a network access mode (NAM) based on detection of the WUS in the resource set.

Description

[0001] This application is a divisional application of the invention patent application with the application date of October 14, 2019, application number 201980068321.6, and title "Wake-up Signal Design". Background Art

[0002] Wireless systems generally include multiple user equipment (UE) devices communicatively coupled to one or more base stations (BS). The one or more BSs may be Long Term Evolution (LTE) evolved Node Bs (eNBs) or New Radio (NR) Node Bs (gNBs), next generation Node Bs (gNBs) or New Radio Base Stations (NR BSs) that can be communicatively coupled to one or more UEs by a 3rd Generation Partnership Project (3GPP) network.

[0003] Next-generation wireless communication systems are expected to be a unified network / system designed to meet distinct and sometimes conflicting performance dimensions and services. The new radio access technology (RAT) is expected to support a wide range of use cases, including enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable machine type communication (uMTC), and similar service types operating in frequency ranges up to 100 GHz. Brief Description of the Drawings

[0004] The features and advantages of the present disclosure will be apparent from the following detailed description taken in conjunction with the drawings that illustrate, by way of example, the features of the present disclosure; and in which:

[0005] Figure 1 A block diagram of a 3rd Generation Partnership Project (3GPP) New Radio (NR) Release 15 frame structure according to one example is shown;

[0006] Figure 2 Wake-up Signal (WUS)-assisted Discontinuous Reception (DRX) according to one example is shown;

[0007] Figure 3 Wake-up Signal (WUS)-assisted Discontinuous Reception (DRX) according to one example is shown;

[0008] Figure 4 The functionality of a user equipment (UE) operable for wake-up signal (WUS) communication in a 5th Generation (5G) New Radio (NR) network according to one example is depicted;

[0009] Figure 5 The functionality of a new radio Node B (gNB) operable for wake-up signal (WUS) communication in a 5th Generation (5G) New Radio (NR) network according to one example is depicted;

[0010] Figure 6 A flow diagram of a machine-readable storage medium having instructions embodied thereon for a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network is depicted according to an example;

[0011] Figure 7 An exemplary architecture of a system of networks according to one example is shown;

[0012] Figure 8 An example of a platform or device according to one example is shown;

[0013] Figure 9 shows exemplary components of a baseband circuit and a radio front end module (RFEM) according to one example;

[0014] Figure 10 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium according to one example; and

[0015] Figure 11 A diagram of a wireless device (eg, UE) is shown according to an example.

[0016] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same, but it will be understood, however, that no limitation of the scope of the technology is intended thereby. DETAILED DESCRIPTION

[0017] Before disclosing and describing the present technology, it should be understood that the technology is not limited to the specific structures, process operations or materials disclosed herein, but extends to equivalents thereof as will be recognized by those skilled in the relevant art. It should also be understood that the terminology used herein is for the purpose of describing specific examples only and is not intended to be limiting. The same reference numerals in different figures represent the same elements. The numbers provided in the flow charts and processes are for clarity of illustration of the actions and operations and do not necessarily indicate a particular order or sequence.

[0018] Exemplary Embodiment

[0019] The following provides an initial overview of the technical embodiments, and specific technical embodiments will be described in more detail later. This initial summary is intended to help readers understand the technology more quickly, but is not intended to identify the key features or essential features of the technology, nor is it intended to limit the scope of the claimed subject matter.

[0020] The battery life of a user equipment (UE) is an aspect of the user experience, which can affect the adoption of fifth-generation (5G) mobile phones and services. Therefore, the UE power efficiency of 5G new radio (NR) UEs should be enhanced relative to long-term evolution (LTE). The energy efficiency of a device can include: (a) efficient data transmission in high-data scenarios; and (b) low power consumption in low-data scenarios. The efficient data transmission under load can be demonstrated by the average spectral efficiency. The low power consumption in low-data cases can be estimated by the sleep ratio.

[0021] In new radio (NR), user data can be transmitted in bursts and served in short durations. A UE power saving mechanism can include triggering the UE to perform network access from a power-efficient mode. The UE can remain in the power-efficient mode, such as in a micro-sleep or off-cycle in a long discontinuous reception (DRX) cycle, unless the UE is notified of network access through the UE power saving framework. Alternatively, when there is a small amount of traffic to be delivered, the network can assist the UE to switch from the "network access" mode (NAM) to the "power-efficient" mode (PAM) (e.g., based on network-assisted signals for dynamic UE transitions to sleep).

[0022] Since more than half of the power consumption in LTE can occur when the UE is in the network access mode, the power consumption should be reduced during network access in the RRC_CONNECTED mode. Some power consumption factors in the network access mode can include: the processing of the aggregated bandwidth, the number of active RF chains, the active reception time, the transmission time, and the dynamic transition to the power-efficient mode. Since the LTE field transmission time interval (TTI) can include a small amount of data, power saving can be configured for the dynamic adaptation to different data arrivals. In one example, network-assisted wake-up signaling can signal the UE to switch from the UE power saving mode (PSM) to the network access mode (NAM).

[0023] In one example, an apparatus for a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network may include one or more processors. The one or more processors may be configured to: identify, at the UE, a resource set of the WUS having a repetition level, wherein: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set. The one or more processors may be configured to: monitor, at the UE, the resource set of the WUS having a repetition level. The one or more processors may be configured to: decode, at the UE, a transmission received from a new radio node B (gNB) in the resource set of the WUS. The one or more processors may be configured to: switch, at the UE, from a power saving mode (PSM) to a network access mode (NAM) based on a detection of the WUS in the resource set. The apparatus may further include a memory interface configured to store the resource set of the WUS in a memory.

[0024] Figure 1 An example of the frame structure of 3GPP NR Release 15 is provided. Specifically, Figure 1 The downlink radio frame structure is shown. In this example, a radio frame 100 for signals for transmitting data may be configured to have a duration T of 10 milliseconds (ms). f . Each radio frame may be segmented or divided into ten subframes 110i, each subframe having a length of 1 millisecond. Each subframe may be further subdivided into one or more time slots 120a, 120i, and 120x, each time slot having a duration T of 1 / μ ms slot , where μ = 1 for a 15 kHz subcarrier spacing, μ = 2 for 30 kHz, μ = 4 for 60 kHz, μ = 8 for 120 kHz, and μ = 16 for 240 kHz. Each time slot may include a physical downlink control channel (PDCCH) and / or a physical downlink shared channel (PDSCH).

[0025] According to the CC frequency bandwidth, each time slot of a component carrier (CC) used by a node and a wireless device may include a plurality of resource blocks (RBs) 130a, 130b, 130i, 130m, and 130n. A CC may have a carrier frequency including the bandwidth. Each CC time slot may include downlink control information (DCI) present in the PDCCH. The PDCCH is transmitted in a control channel resource set (CORESET), which may include one, two, or three orthogonal frequency division multiplexing (OFDM) symbols and a plurality of RBs.

[0026] Each time slot of each RB (physical RB or PRB) may include 12 subcarriers (on the frequency axis) and 14 orthogonal frequency division multiplexing (OFDM) symbols (on the time axis). If short cyclic or standard cyclic prefix is used, the RB may use 14 OFDM symbols. If extended cyclic prefix is used, the RB may use 12 OFDM symbols. The resource block may be mapped to 168 resource elements (REs) using short cyclic or standard cyclic prefix, or may be mapped to 144 REs (not shown) using extended cyclic prefix. An RE may be a unit that contains one OFDM symbol 142 and one subcarrier (i.e., 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz) 146.

[0027] In the case of using quadrature phase shift keying (QPSK) modulation, each RE 140i may transmit two bits of information 150a and 150b. Other modulation types may be used, such as 16 quadrature amplitude modulation (QAM) or 64QAM, to transmit more bits in each RE, or binary phase shift keying (BPSK) modulation may be used to transmit fewer bits (one bit) in each RE. The RB may be configured for downlink transmission from the NR BS to the UE, or may be configured for uplink transmission from the UE to the NR BS.

[0028] This example of the frame structure of 3GPP NR Release 15 provides an example of a way to transmit data or a transmission mode. This example is not intended to be limiting. In the 5G frame structures included in 3GPP LTE Release 15, MulteFire Release 1.1 and later versions, many Release 15 features will evolve and change. In such systems, due to the coexistence of different network services such as eMBB (enhanced mobile broadband), mMTC (massive machine type communication or massive IoT), and URLLC (ultra-reliable low-latency communication or critical communication), design constraints may coexist with multiple 5G parameter sets in the same carrier. Carriers in 5G systems may be above or below 6 GHz. In one implementation, each network service may have a different parameter set.

[0029] WUS-Assisted DRX Transmission

[0030] In another example, as Figure 2 shown, the wake-up signal (WUS) 202 or 206 may be configured to have discontinuous transmission (DTX) 212. Radio resource control (RRC)-connected mode discontinuous reception (DRX) (CDRX) may be configured for the WUS signal 202 or 206 associated with each drx-onDuration occasion 204 or 208 or for the DTX signal 212 associated with each drx-onDuration occasion 214.

[0031] In another example, as Figure 3 shown, the WUS signal 302 may be associated with the onDuration occasion 304, or the DTX signals 312 or 322 may be associated with N consecutive onDuration occasions 314 or 324, where N may be an integer greater than or equal to 1. In this example, N = 2. In this example, detecting the WUS may indicate that the UE remains in or switches to the network access mode within the next two DRX cycles. If the UE detects the WUS, the UE may enter the "Network Access Mode" (NAM) (i.e., during the associated drx-onDuration period, the Medium Access Control (MAC) entity switches to the "active time"), where Physical Downlink Control Channel (PDCCH) monitoring may be performed. Alternatively, when the WUS (DTX) is not detected, the UE may remain in the power saving mode in which PDCCH monitoring is not performed (i.e., during the associated drx-onDuration occasion, the MAC entity is in the "inactive time").

[0032] Wake-Up Signal Transmission

[0033] Base WUS Sequence

[0034] In another example, the base WUS may be a sequence of consecutive resource blocks (RBs) mapped to one or more consecutive or non-consecutive OFDM symbols, where the number of consecutive RBs may be X, where X may be an integer greater than or equal to 1. In one example, X may be 6. The starting position in frequency (i.e., the RB index) may be indicated by higher layer signaling that is part of a configuration (such as a WUS configuration). In one example, the sequence may be mapped across the entire active Bandwidth Part (BWP). In another example, the sequence may be mapped to every odd or even RB in the active BWP. The frequency domain occupancy may be indicated by higher layer signaling that is part of a configuration (such as a WUS configuration). In another example, the sequence may be mapped to the frequency domain according to a higher layer parameter, density, where the density may be referred to by ρ (e.g., resource mapping may occur in every ρth RB within the BWP). In one example, the frequency domain position may be indicated by a bitmap.

[0035] In another example, the time domain position can be provided by a higher layer parameter. In one example, before the start of the OnDuration in the DRX cycle, a resource set including a set of RBs and a set of symbols can be configured to include WUS transmissions. In one example, WUS transmissions can be transmitted using a single antenna port. In another example, WUS transmissions can be transmitted in the i-th and j-th symbols in a time slot, where i can be an integer in the range of 1 to 13, and j can be an integer in the range of 1 to 13. In one example, i may not be equal to j. In one example, the WUS transmission pattern can be repeated in every N-th time slot, where N is an integer greater than or equal to 1. In one example, the UE can monitor WUS in every 2 time slots (e.g., N = 2), where, in each time slot, WUS can be transmitted in the 4th symbol and the 11th symbol.

[0036] In another example, a sequence can be generated according to the Long Term Evolution (LTE) NarrowBand Internet of Things (NB-IoT) WUS (i.e., a Zadoff-Chu (ZC) sequence with a coverage code based on a Gold sequence). In one example, the coverage code sequence can be initialized by UE-specific parameters (e.g., the configured UE cell radio network temporary identifier (C-RNTI) and a time component (e.g., the time slot interval between the first time slot containing the WUS transmission and the associated drx-onDuration occasion)).

[0037] In another example, the following can be used to generate the WUS sequence: d wus (n)=c(m)·g(n), where g(n) can represent a cell-specific sequence, and c(m) can represent a UE-specific sequence.

[0038] In another example, the sequence g(n) can be generated by using a ZC sequence, for example where n' = n mod L ZC , L ZC can define the length of the ZC sequence, and u can be predetermined or configured in a cell-specific manner.

[0039] In another example, the sequence g(n) can be generated using a Secondary Synchronization Signal (SSS) sequence: g(n)=[1 - 2x0((n′ + m0) mod 127)][1 - 2x1((n′ + m1) mod 127)], where 0 ≤ n < 127, where n’ = n mod 127, x0(i + 7) = (x0(i + 4) + x0(i)) mod 2, x1(i + 7) = (x1(i + 1) + x1(i)) mod 2, [x0(6) x0(5) x0(4) x0(3) x0(2) x0(1) x0(0)] = [0 0 0 0 0 0 1], [x1(6) x1(5) x1(4) x1(3) x1(2) x1(1) x1(0)] = [0 0 0 0 0 0 1], and is a mini - slot identifier (ID), and is an in - mini - slot identifier ID.

[0040] In another example, the WUS can be generated without using the cell - specific component sequence g(n) such that: d wus (n) = c(n), where c(n) can be generated by a length - 31 Gold sequence such that c(n) = [1 - 2x0(n + m0)][1 - 2x1(n + m0)], where m0 = 1600, x0(i + 31) = (x0(i + 3) + x0(i)) mod 2, x1(i + 31) = (x1(i + 3) + x1(i + 2) + x1(i + 1) + x1(i)) mod 2, x0(0) = 1, x0(n) = 0, n = 1…, 30, shall be initialized in a UE - specific manner and configured via RRC signaling.

[0041] In another example, the sequence can be generated as c(n): where the pseudo - random (PN) sequence r(m) can be defined by a length - 31 Gold sequence and a sequence r(m) of length M r where m = 0, 1, … M r - 1, where r(m) = (y1(m + N c ) + y2(m + N c )) mod 2, y1(m + 31) = (y1(m + 3) + y1(m)) mod 2, y2(m + 31) = (y2(m + 3) + y2(m + 2) + y2(m + 1) + y2(m)) mod 2, where N C = 1600. In another example, the first m - sequence y1(m) can be initialized with y1(0) = 1, y1(m) = 0, m = 1, 2, …, 30, and y2(m) can be another m - sequence.

[0042] In another example, the PN sequence r(m) can be used with Initialization, where at the start of each OFDM symbol, may number the time slots within a radio frame, l may number the OFDM symbols within a time slot, and n ID may be a parameter indicated by a higher layer, such as a scrambling ID or a WUS sequence generation configuration. In another example, n ID may be a cell radio network temporary identifier (C-RNTI) or a UE-specific configurable ID.

[0043] UE-Specific Initialization of c(n)

[0044] In another example, c init_WUS = f(n RNTI ) mod 2 31 , where f(n RNTI ) may be a function of n RNTI which may be the C-RNTI configured for the UE. In another example, the function may be f(n RNTI ) = n RNTI .

[0045] In another example, c init_WUS = f(N RNTI , N ID ) mod 2 31 , where f(n RNTI , N ID ) may be a function of n RNTI and N ID which may correspond to the UE C-RNTI and the physical cell ID.

[0046] In another example, N ID may refer to other virtual cell IDs or bandwidth part IDs. In one example, the function may be f(n RNTI , N ID ) = (n RNTI 2 16 + N ID ) mod 2 31 .

[0047] In another example, c init_WUS = f(n RNTI , n ID , n sl_O ) mod 2 31 , where f(n RNTI , N ID , n sl_O ) may be the number of time slot intervals between the (first) time slot corresponding to the configured WUS / DTX and the start time slot of the associated drx-onDuration occasion, of n RNTI , N IDand n sl_O function. In another example, c init_WUS can be in the range from 1 to where can be pre-determined. In another example, when c init_WUS =(n RNTI 2 18 +(n sl_O -1)2 16 +n ID ) mod 2 31

[0048] Configurable Base WUS Sequence

[0049] In another example, the base WUS sequence can be configured by radio resource control (RRC) signaling. The base WUS sequence length set (e.g., {4, 6, 8}) can be pre-determined. In another example, the RRC signaling parameters for WUS configuration can indicate the base WUS sequence length. In another example, for a UE with high channel quality conditions, a short base WUS sequence can be configured. In another example, for a UE with low channel quality conditions, a larger base WUS sequence length can be configured.

[0050] Link Adaptation for WUS Transmission

[0051] In another example, for a configured base WUS sequence length, different WUS transmission candidates with different repetition levels can be configured for different coverage range targets. In one example, the WUS configuration can include Y WUS candidates, where Y can be an integer greater than or equal to 1 (e.g., Y can be 4 or 5), and each WUS candidate can correspond to a repetition level (e.g., RL1, RL2, RL4, and RL8). The WUS with a low repetition level can be used for UEs in high-quality channel conditions, while the WUS with a high repetition level can be configured for UEs in low-quality channel conditions. In each WUS occasion, the network can select a specific WUS candidate to wake up the UE for the associated upcoming drx-onDuration occasion.

[0052] Another example provides a function 400 of a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth-generation (5G) new radio (NR) network, as Figure 4As shown. The UE may include one or more processors. The one or more processors may be configured to identify, at the UE, a resource set of a WUS having a repetition level, where: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set, as shown in block 410. The one or more processors may be configured to monitor, at the UE, a resource set of a WUS having a repetition level, as in block 420. The one or more processors may be configured to: decode, at the UE, a transmission received from a new radio node B (gNB) in the resource set of the WUS, as in block 430. The one or more processors may be configured to switch, at the UE, from a power saving mode (PSM) to a network access mode (NAM) based on detection of the WUS in the resource set, as in block 440. Additionally, the UE may include a memory interface configured to store the resource set of the WUS in a memory.

[0053] Another example provides a function 500 of a new radio node B (gNB) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network, as Figure 5 shown. The gNB may include one or more processors. The one or more processors may be configured to determine, at the gNB, a resource set of a WUS having a repetition level, where: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set, as shown in block 510. The one or more processors may be configured to encode, at the gNB for transmission to a user equipment (UE), a resource set of a WUS having a repetition level, where the WUS signals the UE to switch from a power saving mode (PSM) to a network access mode (NAM), as in block 520. Additionally, the gNB may include a memory interface configured to store the resource set of the WUS in a memory.

[0054] Another example provides at least one machine-readable storage medium having instructions 600 embodied thereon for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network, as Figure 6As shown. These instructions can be executed on a machine, where these instructions are included on at least one computer-readable medium or a non-transitory machine-readable storage medium. When the instructions are executed, they perform the following operations: Identify, at the UE, a resource set of the Wake-Up Signal (WUS) with a repetition level, where: The resource set of the WUS includes a mapping of the WUS that associates the WUS with one or more physical resource blocks and one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the repetition level identifies multiple base sequences of the WUS in the resource set, as in block 610. When the instructions are executed, they perform the following operations: Monitor, at the UE, a resource set of the WUS with a repetition level, as in block 620. When the instructions are executed, they perform the following operations: Decode, at the UE, a transmission received from a New Radio Node B (gNB) in the resource set of the WUS, as in block 630. When the instructions are executed, they perform the following operations: Switch, at the UE, from a Power Saving Mode (PSM) to a Network Access Mode (NAM) based on the detection of the WUS in the resource set, as in block 640.

[0055] Although examples have been provided that have specified a gNB, these examples are not intended to be limiting. An evolved Node B (eNB), a Next Generation Node B (gNB), a New Radio Node B (gNB), or a New Radio Base Station (NR BS) can be used in place of the gNB. Thus, unless otherwise stated, any example of a gNB that has been disclosed herein can similarly disclose the use of an eNB, a gNB, or a New Radio Base Station (NR BS).

[0056] Figure 7 An exemplary architecture of a system 700 of a network according to various embodiments is shown. The following description is provided for an example system 700 that operates in conjunction with the LTE system standard and the 5G or NR system standard provided in the 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G) systems), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0057] As Figure 7As shown, system 700 includes UE 701a and UE 701b (collectively referred to as "multiple UEs 701" or "UE 701"). In this example, the multiple UEs 701 are shown as smart phones (e.g., handheld touchscreen mobile computing devices that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument clusters (IC), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDT), electronic engine management systems (EEMS), electronic / engine electronic control units (ECU), electronic / engine electronic control modules (ECM), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" home appliances, MTC devices, M2M, IoT devices, etc.

[0058] In some embodiments, any one of the multiple UEs 701 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe, or D2D communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connection to the IoT network.

[0059] The multiple UEs 701 may be configured to be communicatively coupled to, for example, the RAN 710. In an embodiment, the RAN 710 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN", etc. may refer to the RAN 710 operating in an NR or 5G system 700, while the term "E-UTRAN", etc. may refer to the RAN 710 operating in an LTE or 4G system 700. The multiple UEs 701 respectively utilize connections (or channels) 703 and 704, each connection including a physical communication interface or layer (discussed in further detail below).

[0060] In this example, the connections 703 and 704 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, an NR protocol, and / or any other communication protocol discussed herein. In an embodiment, multiple UEs 701 may directly exchange communication data via the ProSe interface 705. The ProSe interface 705 may alternatively be referred to as the SL interface 705 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0061] UE 701b is shown as being configured to access an AP 706 (also referred to as a "WLAN node 706", "WLAN 706", "WLAN terminal 706", "WT 706", etc.) via a connection 707. The connection 707 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where the AP 706 will include a wireless fidelity router. In this example, the AP 706 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, the UE 701b, the RAN 710, and the AP 706 may be configured to utilize LWA operations and / or LWIP operations. LWA operations may involve a UE 701b in the RRC_CONNECTED state that is configured by RAN nodes 711a-b to utilize the radio resources of LTE and WLAN. LWIP operations may involve the UE 701b using the WLAN radio resources (e.g., connection 707) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through the connection 707. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0062] RAN 710 may include one or more AN nodes or RAN nodes 711a and 711b (collectively referred to as "multiple RAN nodes 711" or "RAN nodes 711") that enable connections 703 and 704. As used herein, terms such as "access node," "access point," etc. may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include a terrestrial station (e.g., a land access point) or a satellite station that provides coverage within a geographical area (e.g., a cell). As used herein, terms such as "NG RAN node" etc. may refer to a RAN node 711 (e.g., gNB) operating in an NR or 5G system 700, while terms such as "E-UTRAN node" etc. may refer to a RAN node 711 (e.g., eNB) operating in an LTE or 4G system 700. According to various embodiments, multiple RAN nodes 711 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing femto cells, pico cells, or other similar cells with a smaller coverage area, smaller user capacity, or higher bandwidth compared to macro cells.

[0063] In some embodiments, all or part of multiple RAN nodes 711 may be implemented as one or more software entities running on a server computer, as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 711; MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, while the PHY layer is operated by individual RAN nodes 711; or "lower PHY" partitioning, where the RRC, PDCP, RLC, MAC layers, and the upper part of the PHY layer are operated by the CRAN / vBBUP, while the lower part of the PHY layer is operated by individual RAN nodes 711. This virtualization framework allows the idle processor cores of multiple RAN nodes 711 to execute other virtualization applications. In some specific implementations, an individual RAN node 711 may represent a connection via a separate F1 interface ( Figure 7A separate gNB-DU (not shown) connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server (not shown) located in the RAN 710 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the plurality of RAN nodes 711 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations to a plurality of UEs 701 and is connected to the 5GC via the NG interface (discussed below).

[0064] In a V2X scenario, one or more of the plurality of RAN nodes 711 may be or act as an RSU. The term "road side unit" or "RSU" may refer to any traffic infrastructure entity for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where the RSU implemented in or by a UE may be referred to as a "UE-type RSU", the RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", the RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side, which provides connectivity support to passing vehicle UEs 701 (vUE 701). The RSU may also include an internal data storage circuit for storing intersection map geometries, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz direct short range communication (DSRC) frequency band to provide extremely low latency communication required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on a cellular V2X frequency band to provide the aforementioned low latency communication and other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz frequency band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communication. Some or all of the computing device and the radio frequency circuit of the RSU may be encapsulated in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or a backhaul network.

[0065] Any one of the plurality of RAN nodes 711 can be the termination point of the air interface protocol and can be the first point of contact for a plurality of UEs 701. In some embodiments, any one of the plurality of RAN nodes 711 can perform various logical functions of the RAN 710, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0066] In an embodiment, the plurality of UEs 701 can be configured to communicate with each other or with any one of the plurality of RAN nodes 711 over a multi-carrier communication channel using OFDM communication signals according to various communication technologies, such as but not limited to OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this regard. The OFDM signal can include a plurality of orthogonal sub-carriers.

[0067] In some embodiments, a downlink resource grid can be used for downlink transmission from any one of the plurality of RAN nodes 711 to the plurality of UEs 701, and uplink transmission can utilize a similar technique. The grid can be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is the physical resources in the downlink in each time slot. For an OFDM system, such a time-frequency plane representation is a common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid correspond to an OFDM symbol and an OFDM sub-carrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in the radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this can represent the smallest amount of resources that can be currently allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0068] According to various embodiments, the plurality of UEs 701 and the plurality of RAN nodes 711 transmit data (e.g., send data and receive data) over a licensed medium (also referred to as "licensed spectrum" and / or "licensed band") and an unlicensed shared medium (also referred to as "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum can include channels operating in a frequency range of approximately from 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum can include the 5 GHz band.

[0069] To operate in unlicensed spectrum, multiple UEs 701 and multiple RAN nodes 711 may operate using LAA, eLAA, and / or feLAA mechanisms. In these embodiments, multiple UEs 701 and multiple RAN nodes 711 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to the listen-before-talk (LBT) protocol.

[0070] LBT is a mechanism by which devices (e.g., multiple UEs 701, multiple RAN nodes 711, etc.) sense the medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which uses at least ED to determine whether there are other signals on the channel to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy on the expected transmission band for a period of time and comparing the sensed RF energy with a predefined or configured threshold.

[0071] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as a UE 701, an AP 706, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, in the case where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS, which increases exponentially in the event of a collision and is reset to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLANs. In some embodiments, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmissions) may have a variable-length LAA contention window between X and Y ECCA slots, where X and Y are the minimum and maximum values of the LAA's CWS. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and the MCOT (e.g., the transmission burst) may be based on government regulatory requirements.

[0072] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, for DL and UL, the number of aggregated carriers can be different, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC can have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are usually the same for DL and UL.

[0073] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells can be different. For example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell can provide PCC for both UL and DL and can handle activities related to RRC and NAS. Other serving cells are called SCell, and each SCell can provide individual SCCs for both UL and DL. SCCs can be added and removed as needed, while changing the PCC may require the UE 701 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCell can operate in the unlicensed spectrum (referred to as "LAA SCell"), and the LAA SCell is assisted by the PCell operating in the licensed spectrum. When the UE is configured with more than one LAA SCell, the UE can receive UL authorization on the configured LAA SCell, indicating different PUSCH start positions within the same subframe.

[0074] The PDSCH carries user data and higher layer signaling to multiple UEs 701. Among other information, the PDCCH carries information about the transport format and resource allocation related to the PDSCH channel. It can also notify multiple UEs 701 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Generally, downlink scheduling (allocating control and shared channel resource blocks to the UEs 701b within the cell) can be performed on any of the multiple RAN nodes 711 based on the channel quality information fed back from any of the multiple UEs 701. Downlink resource allocation information can be sent on the PDCCH for each of the multiple UEs 701 (e.g., allocated to).

[0075] The PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quads, and then a sub-block interleaver can be used to permute them for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets each having four physical resource elements, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and the channel conditions, one or more CCEs can be used to transmit the PDCCH. There can 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).

[0076] Some embodiments can use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments can utilize the EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs can be used to transmit the EPDCCH. Similar to the above, each ECCE can correspond to nine sets including four physical resource elements, called EREGs. In some cases, the ECCE can have other numbers of EREGs.

[0077] Multiple RAN nodes 711 can be configured to communicate with each other via an interface 712. In an embodiment where the system 700 is an LTE system, the interface 712 can be the X2 interface 712. The X2 interface can be defined between two or more RAN nodes 711 (e.g., two or more eNBs, etc.) connected to the EPC 720, and / or between two eNBs connected to the EPC 720. In some specific implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide a flow control mechanism for user packets transmitted through the X2 interface, and can be used to convey information about the delivery of user data between eNBs. For example, the X2-U can provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-order delivery of PDCP PDUs from the SeNB to the UE 701 for user data; information about PDCP PDUs not delivered to the UE 701; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. The X2-C can provide access mobility functions within LTE, including context transfer from the source eNB to the target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0078] In an implementation where the system 700 is a 5G or NR system, the interface 712 can be the Xn interface 712. The Xn interface is defined between two or more RAN nodes 711 (e.g., two or more gNBs, etc.) connected to the 5GC 720, between a RAN node 711 (e.g., gNB) connected to the 5GC 720 and an eNB, and / or between two eNBs connected to the 5GC 720. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U can provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and traffic control functions. The Xn-C can provide management and error handling functions for managing the functions of the Xn-C interface; the mobility support for the UE 701 in the connected mode (e.g., CM connection) includes functions for managing the UE mobility in the connected mode between one or more RAN nodes 711. This mobility support can include the context transfer from the old (source) serving RAN node 711 to the new (target) serving RAN node 711; and the control of the user plane tunnel between the old (source) serving RAN node 711 and the new (target) serving RAN node 711. The protocol stack of the Xn-U can include a transport network layer built on the Internet Protocol (IP) transport layer, and a GTP-U layer for carrying user plane PDUs on top of the UDP and / or IP layer. The Xn-C protocol stack can include an application layer signaling protocol (called the Xn application protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP can be on top of the IP layer and can provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack can be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0079] RAN 710 is shown as communicatively coupled to a core network - in this embodiment, communicatively coupled to core network (CN) 720. CN 720 may include a plurality of network elements 722 configured to provide various data and telecommunication services to customers / users (e.g., users of a plurality of UEs 701) connected to CN 720 via RAN 710. Components of CN 720 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 720 may be referred to as a network slice, and a logical instance of a portion of CN 720 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources that include a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0080] Generally, application server 730 may be an element that provides an application that uses IP bearer resources in conjunction with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). Application server 730 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.) for a plurality of UEs 701 via EPC 720.

[0081] In an embodiment, CN 720 may be a 5GC (referred to as "5GC 720", etc.), and RAN 710 may be connected to CN 720 via NG interface 713. In an embodiment, NG interface 713 may be divided into two parts: an NG user plane (NG-U) interface 714 that carries traffic data between RAN node 711 and UPF; and an S1 control plane (NG-C) interface 715 that is a signaling interface between a plurality of RAN nodes 711 and a plurality of AMFs.

[0082] In an embodiment, the CN 720 can be a 5G CN (referred to as "5GC 720" etc.), while in other embodiments, the CN 720 can be an EPC. In the case where the CN 720 is an EPC (referred to as "EPC 720" etc.), the RAN 710 can be connected to the CN 720 via the S1 interface 713. In an embodiment, the S1 interface 713 can be divided into two parts: the S1 user plane (S1-U) interface 714, which carries traffic data between the RAN node 711 and the S-GW; and the S1-MME interface 715, which is a signaling interface between multiple RAN nodes 711 and multiple MMEs.

[0083] Figure 8 An example of a platform 800 (or "device 800") according to various embodiments is shown. In an embodiment, the computer platform 800 can be adapted to be used as multiple UEs 701, an application server 730, and / or any other element / device discussed herein. The platform 800 can include any combination of the components shown in the example. The components of the platform 800 can be implemented as integrated circuits (ICs), parts of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within the computer platform 800, or as components otherwise incorporated within the chassis of a larger system. Figure 8 The block diagram is intended to show a high-level view of the components of the computer platform 800. However, some of the components shown may be omitted, additional components may exist, and different arrangements of the shown components may occur in other specific implementations.

[0084] The application circuit 805 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and an LDO, an interrupt controller, a serial interface (such as SPI), 2 I2C or a general-purpose programmable serial interface module, an RTC, timers (including interval timers and watchdog timers), general-purpose I / O, a memory card controller (such as an SD MMC or a similar controller), a USB interface, an MIPI interface, and a JTAG test access port, among others. The processor (or core) of the application circuit 805 can be coupled to the memory / storage element or can include the memory / storage element, and can be configured to execute instructions stored in the memory / storage element to enable various application programs or operating systems to run on the platform 800. In some embodiments, the memory / storage element can be an on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0085] The processor of the application circuit may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit may include or may be a dedicated processor / controller for operating according to the various embodiments herein.

[0086] As an example, the processor of application circuit 805 may include a processor based on Architecture Core TM , such as Quark TM , Atom TM , i3, i5, i7, or an MCU-class processor, or another such processor available from Corporation in Santa Clara, California. The processor of application circuit 805 may also be one or more of the following: an Advanced Micro Devices (AMD) processor or an accelerated processing unit (APU); an A5-A9 processor from Inc., a Snapdragon processor from TM Technologies, Inc., a Texas Instruments, Open Multimedia Applications Platform (OMAP) TM processor; MIPS-based designs from MIPS Technologies, Inc., such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as ARM Cortex-A, Cortex-R, and Cortex-M series processors; and so on. In some specific implementations, application circuit 805 may be part of a system-on-chip (SoC), where application circuit 805 and other components are formed as a single integrated circuit or a single package, such as the Edison or Galileo TM SoC board available from TM Corporation.

[0087] In addition or alternatively, application circuitry 805 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs; programmable system on chips (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 805 may include logic blocks or logic architectures, as well as other interconnect resources that may be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 805 may include memory elements (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuse, etc.)) for storing logic blocks, logic architectures, data, etc. in look-up tables (LUTs) and the like.

[0088] Baseband circuitry 810 may be implemented as, for example, a soldered-in substrate that includes one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module that includes two or more integrated circuits. Various hardware electronic components of baseband circuitry 810 are discussed below with reference to Figure 9 discussion.

[0089] RFEM 815 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some embodiments, the one or more sub-millimeter wave RFICs may be physically separated from the millimeter wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, for example, antenna array 911 below Figure 9 ), and the RFEM may be connected to multiple antennas. In alternative embodiments, the radio functions of both millimeter wave and sub-millimeter wave may be implemented in the same physical RFEM 815 that incorporates both millimeter wave antennas and sub-millimeter wave.

[0090] Memory circuit 820 may include any number and type of memory devices for providing a given amount of system memory. For example, memory circuit 820 may include one or more of the following: volatile memory, which includes random access memory (RAM), dynamic RAM (DRAM), and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), which includes high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. Memory circuit 820 may be developed according to Joint Electron Device Engineering Council (JEDEC) low-power double data rate (LPDDR)-based designs such as LPDDR2, LPDDR3, LPDDR4, etc. Memory circuit 820 may be implemented as one or more of the following: a soldered-in package integrated circuit, a single-die package (SDP), a dual-die package (DDP), or a quad-die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, memory circuit 820 may be an on-chip memory or register associated with application circuit 805. To provide persistent storage of information such as data, applications, operating systems, etc., memory circuit 820 may include one or more mass storage devices, which may particularly include solid state disk drives (SSDDs), hard disk drives (HDDs), micro HDDs, resistive change memories, phase change memories, holographic memories, or chemical memories, etc. For example, computer platform 800 may incorporate 3D cross-point (XPOINT) memory obtained from and .

[0091] Removable memory circuit 823 may include a device, circuit, housing / case, port, or socket, etc. for coupling a portable data storage device to platform 800. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD Picture Cards, etc.), as well as USB flash drives, optical discs, external HDDs, etc.

[0092] Platform 800 may also include interface circuitry (not shown) for connecting external devices to platform 800. External devices connected to platform 800 via this interface circuitry include sensor circuit 821 and electromechanical components (EMC) 822, as well as removable memory devices coupled to removable memory circuit 823.

[0093] The sensor circuit 821 includes a device, module, or subsystem aimed at detecting an event or change in its environment and sending information (sensor data) about the detected event to some other device, module, subsystem, etc. Examples of such sensors include, in particular: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0094] The EMC 822 includes a device, module, or subsystem aimed at enabling the platform 800 to change its state, position, and / or orientation or move or control a mechanism or (sub)system. Additionally, the EMC 822 can be configured to generate messages / signaling and send messages / signaling to other components of the platform 800 to indicate the current state of the EMC 822. The EMC 822 includes one or more power switches, relays (including an electromechanical relay (EMR) and / or a solid-state relay (SSR)), actuators (e.g., a valve actuator, etc.), an audible sound generator, a visual warning device, a motor (e.g., a DC motor, a stepper motor, etc.), a wheel, a thruster, a propeller, a claw, a clamp, a hook, and / or other similar electromechanical components. In an embodiment, the platform 800 is configured to operate one or more EMCs 822 based on one or more captured events and / or instructions or control signals received from a service provider and / or various clients.

[0095] In some embodiments, the interface circuit may couple platform 800 to positioning circuit 845. Positioning circuit 845 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of GNSS. Examples of navigation satellite constellations (or GNSS) may include GPS of the United States, GLONASS of Russia, Galileo system of the European Union, Beidou Navigation Satellite System of China, regional navigation systems, or GNSS augmentation systems (e.g., NAVIC, QZSS of Japan, DORIS of France, etc.). Positioning circuit 845 may include various hardware elements (e.g., including hardware devices for facilitating OTA communication such as switches, filters, amplifiers, antenna elements, etc.) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, positioning circuit 845 may include a micro PNT IC that uses a primary timing clock to perform position tracking / estimation without GNSS assistance. Positioning circuit 845 may also be part of and / or interact with baseband circuitry and / or RFEM 815 to communicate with nodes and components of the positioning network. Positioning circuit 845 may also provide position data and / or time data to application circuit 805, which may use this data to synchronize operations with various infrastructure (e.g., radio base stations) for turn-by-turn navigation applications and the like.

[0096] In some embodiments, the interface circuit may couple platform 800 to near field communication (NFC) circuit 840. NFC circuit 840 is configured to provide contactless short-range communication based on radio frequency identification (RFID) standards, where magnetic field sensing is used to enable communication between NFC circuit 840 and NFC-enabled devices external to platform 800 (e.g., "NFC contact points"). NFC circuit 840 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to NFC circuit 840 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to NFC circuit 840, or initiate data transfer between NFC circuit 840 and another active NFC device (e.g., a smart phone or NFC-enabled POS terminal) in the vicinity of platform 800.

[0097] The drive circuit 846 may include software elements and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled with the platform 800. The drive circuit 846 may include individual drivers that allow other components of the platform 800 to interact with or control various input / output (I / O) devices that may be present within or connected to the platform 800. For example, the drive circuit 846 may include: a display driver for controlling and allowing access to a display device, a touchscreen driver for controlling and allowing access to the touchscreen interface of the platform 800, a sensor driver for obtaining sensor readings from the sensor circuit 821 and controlling and allowing access to the sensor circuit 821, an EMC driver for obtaining the actuator position of the EMC 822 and / or controlling and allowing access to the EMC 822, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0098] A power management integrated circuit (PMIC) 825 (also referred to as “power management circuit 825”) may manage the power provided to the various components of the platform 800. Specifically, with respect to the baseband circuit 810, the PMIC 825 may control power selection, voltage regulation, battery charging, or DC-DC conversion. When the platform 800 is capable of being powered by a battery 830, e.g., when the device is included in the UE 701, the PMIC 825 is typically included.

[0099] In some embodiments, the PMIC 825 may control or otherwise be part of various power saving mechanisms of the platform 800. For example, if the platform 800 is in the RRC_Connected state, in which the platform remains connected to the RAN node because it expects to receive traffic soon, after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 800 may power down for short intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 800 may transition to the RRC_Idle state, in which the platform is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The platform 800 enters a very low power state and performs paging, in which the platform wakes up periodically to listen for the network and then powers down again. The platform 800 may not receive data in this state; to receive data, the device may transition back to the RRC_Connected state. Additional power saving modes may make the device unavailable to the network for longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and may be completely powered down. Any data sent during this time will incur a significant delay, and it is assumed that the delay is acceptable.

[0100] The battery 830 can power the platform 800. However, in some examples, the platform 800 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 830 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in V2X applications, the battery 830 can be a typical lead-acid automotive battery.

[0101] In some specific implementations, the battery 830 can be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS can be included in the platform 800 to track the state of charge (SoCh) of the battery 830. The BMS can be used to monitor other parameters of the battery 830, such as the state of health (SoH) and the state of function (SoF) of the battery 830, to provide fault prediction. The BMS can transmit information about the battery 830 to the application circuit 805 or other components of the platform 800. The BMS can also include an analog-to-digital (ADC) converter that allows the application circuit 805 to directly monitor the voltage of the battery 830 or the current from the battery 830. Battery parameters can be used to determine actions that the platform 800 can perform, such as transmission frequency, network operation, sensing frequency, etc.

[0102] A power block or other power source coupled to the power grid can be coupled to the BMS to charge the battery 830. In some examples, the power block can be replaced with a wireless power receiver to wirelessly obtain power, for example, through a loop antenna in the computer platform 800. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 830 and thus on the current required. Charging can be performed using the aviation fuel standards published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Consortium, or the Rezence charging standard published by the Wireless Power Consortium.

[0103] The user interface circuit 850 includes various input / output (I / O) devices present within or connected to the platform 800 and includes one or more user interfaces designed to enable user interaction with the platform 800 and / or a peripheral component interface designed to enable interaction with peripheral components of the platform 800. The user interface circuit 850 includes input device circuitry and output device circuitry. The input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. The output device circuitry includes any physical or virtual means for displaying information or otherwise communicating information such as sensor readings, actuator positions, or other similar information. The output device circuitry may include any number and / or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary state indicators (e.g., light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as a display device or a touchscreen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the platform 800. The output device circuitry may also include a speaker or other audio emitting device, a printer, etc. In some embodiments, the sensor circuit 821 may be used as input device circuitry (e.g., an image capture device, a motion capture device, etc.), and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing haptic feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuit including an NFC controller and a processing device coupled to an antenna element. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, etc.

[0104] Although not shown, the components of the platform 800 may communicate with each other using suitable bus or interconnect (IX) technologies, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, Time-Triggered Protocol (TTP) systems, FlexRay systems, or any number of other technologies. The bus / IX may be a proprietary bus / IX, e.g., used in a system-on-chip (SoC)-based system. Other bus / IX systems may be included, such as 2 I

[0105] Figure 9 Exemplary components of a baseband circuit 910 and a radio frequency front-end module (RFEM) 915 are shown in accordance with various embodiments. The baseband circuit 910 correspondingly corresponds to Figure 8The baseband circuit 810. The RFEM 915 correspondingly corresponds to Figure 8 the RFEM 815. As shown, the RFEM 915 may include a radio frequency (RF) circuit 906, a front-end module (FEM) circuit 908, and an antenna array 911 coupled together at least as shown.

[0106] The baseband circuit 910 includes circuits and / or control logic components configured to perform various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 906. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 910 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 910 may include convolutional, tail-biting convolutional, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments. The baseband circuit 910 is configured to process baseband signals received from the receive signal path of the RF circuit 906 and generate baseband signals for the transmit signal path of the RF circuit 906. The baseband circuit 910 is configured to connect to the application circuit 805 (see Figure 8 ) to generate and process baseband signals and control the operation of the RF circuit 906. The baseband circuit 910 may process various radio control functions.

[0107] The foregoing circuits and / or control logic components of the baseband circuit 910 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 904A, a 4G / LTE baseband processor 904B, a 5G / NR baseband processor 904C, or some other baseband processor 904D for other existing generations, generations under development, or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 904A-D may be included in modules stored in the memory 904G and executed via a central processing unit (CPU) 904E. In other embodiments, some or all of the functions of the baseband processors 904A-D may be provided as hardware accelerators (e.g., FPGA, ASIC, etc.) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In various embodiments, the memory 904G may store program code of a real-time OS (RTOS) that, when executed by the CPU 904E (or other baseband processor), will cause the CPU 904E (or other baseband processor) to manage the resources of the baseband circuit 910, schedule tasks, etc. Examples of RTOS may include those provided by the provided Operating System Embedded (OSE) TM by Mentor the provided Nucleus RTOS TM by Mentor the provided Versatile Real - Time Executive (VRTX), by Express the provided ThreadX TM , by the provided FreeRTOS, REX OS, by OpenKernel (OK) the provided OKL4, or any other suitable RTOS, such as those discussed herein. Additionally, the baseband circuit 910 includes one or more audio digital signal processors (DSPs) 904F. The audio DSP 904F includes elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments.

[0108] In some embodiments, each of the processors 904A - 904E includes a corresponding memory interface to send data to / from the memory 904G. The baseband circuit 910 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to the baseband circuit 910; an application circuit interface for sending data to / receiving data from the application circuit 805 of Figure 9 ; an RF circuit interface for sending data to / receiving data from the RF circuit 906 of Figure 9 ; a wireless hardware connection interface for sending data to / receiving data from one or more wireless hardware elements (e.g., near - field communication (NFC) components, low - power components, components, etc.); and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 825.

[0109] In an alternative embodiment (which may be combined with the above embodiments), the baseband circuit 910 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, the audio subsystem, and the interface subsystem via an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connectors, a network-on-chip (NOC) architecture, and / or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memories, program memories, voice processing accelerator circuitry, data converter circuitry such as analog-to-digital converter circuitry and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 910 may include protocol processing circuitry having one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., radio front-end module 915).

[0110] Although Figure 9 not shown, in some embodiments, the baseband circuit 910 includes respective processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and respective processing devices for implementing PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 910 and / or the RF circuit 906 is part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuitry may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuitry will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 910 and / or the RF circuit 906 is part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In the second example, the protocol processing circuitry will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 904G) for storing program code and data for operating the protocol functions, and one or more processing cores for executing the program code and performing various operations using the data. The baseband circuit 910 may also support radio communication for more than one wireless protocol.

[0111] The various hardware components of the baseband circuit 910 discussed herein may be implemented as, for example, a soldered-in substrate that includes one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module that includes two or more ICs. In one example, the components of the baseband circuit 910 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the constituent components of the baseband circuit 910 and the RF circuit 906 may be implemented together, such as, for example, a system-on-a-chip (SOC) or a system-in-package (SiP). In another example, some or all of the constituent components of the baseband circuit 910 may be implemented as a separate SoC that is communicatively coupled to the RF circuit 906 (or multiple instances of the RF circuit 906). In yet another example, some or all of the constituent components of the baseband circuit 910 and the application circuit 805 may be implemented together as separate SoCs (e.g., "multi-chip packages") mounted on the same circuit board.

[0112] In some embodiments, the baseband circuit 910 may provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 910 may support communication with E-UTRAN or other WMAN, WLAN, WPAN. Embodiments in which the baseband circuit 910 is configured to support radio communication for more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0113] The RF circuit 906 may implement communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit 906 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. The RF circuit 906 may include a receive signal path that may include circuitry for down-converting an RF signal received from the FEM circuit 908 and providing a baseband signal to the baseband circuit 910. The RF circuit 906 may also include a transmit signal path that may include circuitry for up-converting a baseband signal provided by the baseband circuit 910 and providing an RF output signal for transmission to the FEM circuit 908.

[0114] In some embodiments, the receive signal path of RF circuit 906 may include mixer circuit 906a, amplifier circuit 906b, and filter circuit 906c. In some embodiments, the transmit signal path of RF circuit 906 may include filter circuit 906c and mixer circuit 906a. RF circuit 906 may also include synthesizer circuit 906d for synthesizing the frequencies used by mixer circuit 906a of the receive and transmit signal paths. In some embodiments, mixer circuit 906a of the receive signal path may be configured to down-convert the RF signal received from FEM circuit 908 based on the synthesized frequency provided by synthesizer circuit 906d. Amplifier circuit 906b may be configured to amplify the down-converted signal, and filter circuit 906c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 910 for further processing. In some embodiments, although not required, the output baseband signal may be a zero-frequency baseband signal. In some embodiments, mixer circuit 906a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0115] In some embodiments, mixer circuit 906a of the transmit signal path may be configured to up-convert the input baseband signal based on the synthesized frequency provided by synthesizer circuit 906d to generate an RF output signal for FEM circuit 908. The baseband signal may be provided by baseband circuit 910 and filtered by filter circuit 906c.

[0116] In some embodiments, mixer circuit 906a of the receive signal path and mixer circuit 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, mixer circuit 906a of the receive signal path and mixer circuit 906a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, mixer circuit 906a of the receive signal path and mixer circuit 906a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, mixer circuit 906a of the receive signal path and mixer circuit 906a of the transmit signal path may be configured for superheterodyne operation.

[0117] 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 regard. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 906 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 910 may include a digital baseband interface for communicating with the RF circuit 906.

[0118] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, but the scope of the embodiments is not limited in this regard.

[0119] In some embodiments, the synthesizer circuit 906d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this regard, as other types of frequency synthesizers may also be suitable. For example, the synthesizer circuit 906d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0120] The synthesizer circuit 906d may be configured to synthesize an output frequency based on a frequency input and a frequency divider control input for use by the mixer circuit 906a of the RF circuit 906. In some embodiments, the synthesizer circuit 906d may be a fractional-N / N+1 synthesizer.

[0121] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), although this is not required. The frequency divider control input may be provided by the baseband circuit 910 or the application circuit 805 according to the desired output frequency. In some embodiments, the frequency divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application circuit 805.

[0122] The synthesizer circuit 906d of the RF circuit 906 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 an input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO period into Nd equal phase bins, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

[0123] In some embodiments, the synthesizer circuit 906d may be configured to generate a carrier frequency 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 an orthogonal generator and a divider circuit to generate multiple signals having multiple different phases relative to each other at that carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 906 may include an IQ / polarity converter.

[0124] The FEM circuit 908 may include a receive signal path that may include circuitry configured to operate on an RF signal received from the antenna array 911, amplify the received signal, and provide an amplified version of the received signal to the RF circuit 906 for further processing. The FEM circuit 908 may also include a transmit signal path that may include circuitry configured to amplify a transmit signal provided by the RF circuit 906 for transmission by one or more antenna elements in the antenna array 911. In various embodiments, amplification through the transmit or receive signal path may be accomplished only in the RF circuit 906, only in the FEM circuit 908, or in both the RF circuit 906 and the FEM circuit 908.

[0125] In some embodiments, the FEM circuit 908 may include a TX / RX switch to switch between transmit mode and receive mode of operation. The FEM circuit 908 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 908 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 906). The transmit signal path of the FEM circuit 908 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuit 906), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 911.

[0126] The antenna array 911 includes one or more antenna elements, each antenna element being configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, the digital baseband signal provided by the baseband circuit 910 is converted into an analog RF signal (e.g., a modulated waveform), which will be amplified and transmitted via the antenna elements of the antenna array 911 that includes one or more antenna elements (not shown). The antenna elements can be omnidirectional, directional, or a combination thereof. The antenna elements can form various arrangements as known and / or discussed herein. The antenna array 911 can include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 911 can be formed as a patch of metal foil in various shapes (e.g., a patch antenna), and can be coupled to the RF circuit 906 and / or the FEM circuit 908 using metal transmission lines, etc.

[0127] The processor of the application circuit 805 and the processor of the baseband circuit 910 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 910 can be used, either alone or in combination, to execute layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 805 can utilize the data received from these layers (e.g., packet data) and further execute layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 can include the RRC layer, which will be described in further detail below. As mentioned herein, layer 2 can include the MAC layer, the RLC layer, and the PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 can include the PHY layer of the UE / RAN node, which will be described in further detail below.

[0128] Figure 10 is a block diagram showing components capable of reading instructions from a machine-readable medium or a computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein. Specifically, Figure 10 shows a schematic diagram of hardware resources 1000, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which can be communicatively coupled via a bus 1040. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1000.

[0129] The processor 1010 may include, for example, processor 1012 and processor 1014. The processor 1010 may be, for example, 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0130] The memory / storage device 1020 may include a main memory, a disk memory, or any suitable combination thereof. The memory / storage device 1020 may include, but is not limited to, any type of volatile or non-volatile memory, such as 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 devices, and the like.

[0131] The communication resources 1030 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1004 or one or more databases 1006 via the network 1008. For example, the communication resources 1030 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or low power) component, components, and other communication components.

[0132] The instructions 1050 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 1010 to execute any one or more of the method sets discussed herein. The instructions 1050 may reside wholly or partially within at least one of the processors 1010 (e.g., within the cache memory of the processor), the memory / storage device 1020, or any suitable combination thereof. Additionally, any portion of the instructions 1050 may be transferred from any combination of the peripheral devices 1004 or the database 1006 to the hardware resources 1000. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral devices 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0133] Figure 11An exemplary illustration of a wireless device is provided, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet computer, a handheld terminal, or other types of wireless devices. The wireless device may include one or more antennas configured to communicate with a node, a macro node, a low-power node (LPN), or a transmission station such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other types of wireless wide area network (WWAN) access points. The wireless device may be configured to communicate using at least one wireless communication standard, such as but not limited to 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device may communicate using a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. The wireless device may communicate in a wireless local area network (WAN), a wireless personal area network (WPAN), and / or a WWAN. The wireless device may also include a wireless modem. The wireless modem may include, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). In one example, the wireless modem may modulate signals transmitted by the wireless device via one or more antennas and demodulate signals received by the wireless device via one or more antennas.

[0134] Figure 11 An illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device is also provided. The display screen may be a liquid crystal display (LCD) screen or other types of display screens such as an organic light emitting diode (OLED) display. The display screen may be configured as a touch screen. The touch screen may use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor may be coupled to an internal memory to provide processing and display capabilities. A non-volatile memory port may also be used to provide data input / output options to the user. The non-volatile memory port may also be used to expand the memory capabilities of the wireless device. A keyboard may be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard may also be provided using the touch screen.

[0135] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more of the operations, techniques, processes, and / or methods described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the following embodiments. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures may be configured to operate in accordance with one or more of the embodiments shown in the embodiments section below.

[0136] Example

[0137] The following embodiments relate to specific technical implementations and point out specific features, elements, or actions that may be used or otherwise combined in implementing such implementations.

[0138] Embodiment 1 includes an apparatus for a user equipment (UE) operable for wake-up signal (WUS) communication in a fifth generation (5G) new radio (NR) network, the apparatus including: one or more processors configured to: identify, at the UE, a resource set of WUS having a repetition level, wherein: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set; monitor, at the UE, the resource set of WUS having a repetition level; decode, at the UE, a transmission received from a new radio node B (gNB) in the resource set of the WUS; and switch, at the UE, from a power saving mode (PSM) to a network access mode (NAM) based on detection of the WUS in the resource set; and a memory interface configured to store the resource set of the WUS in a memory.

[0139] Embodiment 2 includes the apparatus according to Embodiment 1, wherein the one or more processors are further configured to: detect, at the UE, the repetition level of the resource set of the WUS.

[0140] Embodiment 3 includes the apparatus according to Embodiment 1, wherein the one or more processors are further configured to: identify, at the UE, the resource set of the WUS, wherein the WUS includes a cell-specific sequence and a UE-specific sequence.

[0141] Embodiment 4 includes the apparatus according to Embodiment 3, wherein the one or more processors are further configured to: identify, at the UE, the resource set of the WUS, wherein the cell-specific sequence is generated from a Zadoff-Chu (ZC) sequence having a Gold covering code sequence initialized by UE-specific parameters as follows: where: g(n) is a cell-specific sequence, μ is predetermined or configured via cell-specific signaling, and n' is n mod L zc , and L zc is the length of the ZC sequence; or identify a resource set for WUS at the UE, where the cell-specific sequence is generated from the secondary synchronization signal (SSS).

[0142] Example 5 includes the apparatus according to Example 1, wherein one or more processors are further configured to: identify a resource set for WUS at the UE, where WUS includes a UE-specific sequence generated from a length-31 Gold sequence.

[0143] Example 6 includes the apparatus according to Example 1, wherein one or more processors are further configured to: identify a resource set for WUS at the UE, where WUS includes a UE-specific initialization of the UE-specific sequence, where the UE-specific initialization is based on one or more of the following: cell radio network temporary identifier (C-RNTI), physical cell identifier (ID), virtual cell ID, bandwidth part ID (BWP ID), or slot offset.

[0144] Example 7 includes the apparatus according to Example 1, wherein one or more processors are further configured to: identify the length of a base sequence among a plurality of base sequences at the UE, where the length of the base sequence is based on a target level of coverage of the UE and is configured via radio resource control (RRC) signaling.

[0145] Example 8 includes the apparatus according to Example 1, wherein one or more processors are further configured to: identify a resource set for WUS at the UE from one or more of the following: a starting position in the frequency of the resource set, a bandwidth part (BWP) of the resource set, a density of the resource set, a bitmap of the frequency-domain position of the resource set, a higher-layer parameter of the time-domain position, one or more antenna ports for transmission of WUS, one or more slot indices of the resource set, or one or more symbol indices of the resource set.

[0146] Example 9 includes the apparatus according to any one of Examples 1 to 8, wherein the resource set for WUS is configured via radio resource control (RRC) signaling.

[0147] Embodiment 10 includes an apparatus for a new radio node B (gNB) operable for wake-up signal (WUS) communication in a fifth-generation (5G) new radio (NR) network. The apparatus includes: one or more processors configured to: determine, at the gNB, a resource set of the WUS having a repetition level, where: the resource set of the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set; encode, at the gNB for transmission to a user equipment (UE), the resource set of the WUS having the repetition level, where the WUS signals the UE to switch from a power saving mode (PSM) to a network access mode (NAM); and a memory interface configured to store the resource set of the WUS in a memory.

[0148] Embodiment 11 includes the apparatus according to Embodiment 10, where the one or more processors are further configured to: select, at the gNB, the repetition level of the resource set of the WUS based on the UE's channel conditions.

[0149] Embodiment 12 includes the apparatus according to Embodiment 10, where the one or more processors are further configured to: determine, at the gNB, the resource set of the WUS, where the WUS includes a cell-specific sequence and a UE-specific sequence.

[0150] Embodiment 13 includes the apparatus according to Embodiment 12, where the one or more processors are further configured to: determine, at the gNB, the resource set of the WUS, where the cell-specific sequence is generated from a Zadoff-Chu (ZC) sequence having a Gold overlay code sequence initialized by UE-specific parameters as follows: where: g(n) is the cell-specific sequence, μ is predetermined or configured via cell-specific signaling, and n' is n mod L zc , and L zc is the length of the ZC sequence; or determine, at the gNB, the resource set of the WUS, where the cell-specific sequence is generated from a secondary synchronization signal (SSS).

[0151] Embodiment 14 includes the apparatus according to Embodiment 10, where the one or more processors are further configured to: determine, at the gNB, the resource set of the WUS, where the WUS includes a UE-specific sequence generated from a length-31 Gold sequence.

[0152] Example 15 includes the apparatus according to Example 10, wherein one or more processors are further configured to: determine, at a gNB, a resource set for a wake-up signal (WUS), where the WUS includes UE-specific initialization of a UE-specific sequence, and where the UE-specific initialization is based on one or more of: a cell radio network temporary identifier (C-RNTI), a physical cell identifier (ID), a virtual cell ID, a bandwidth part ID (BWP ID), or a slot offset.

[0153] Example 16 includes the apparatus according to Example 10, wherein one or more processors are further configured to: determine, at a gNB, a length of a base sequence among a plurality of base sequences, where the length of the base sequence is based on a coverage level of a UE and is configured via radio resource control (RRC) signaling.

[0154] Example 17 includes the apparatus according to any one of Examples 10 to 16, wherein the resource set for the WUS is configured via radio resource control (RRC) signaling, and the resource set for the WUS is identifiable from one or more of: a starting position in the frequency of the resource set, a bandwidth part (BWP) of the resource set, a density of the resource set, a bitmap of a frequency-domain position of the resource set, a higher-layer parameter of a time-domain position, one or more antenna ports for transmission of the WUS, one or more slot indices of the resource set, or one or more symbol indices of the resource set.

[0155] Example 18 includes at least one machine-readable storage medium having instructions embodied thereon for wake-up signal (WUS) communication in a fifth-generation (5G) new radio (NR) network, the instructions performing the following operations when executed by one or more processors at a user equipment (UE): identify, at the UE, a resource set for the WUS having a repetition level, where: the resource set for the WUS includes a mapping of the WUS associating the WUS with one or more physical resource blocks and one or more orthogonal frequency-division multiplexing (OFDM) symbols, and the repetition level identifies a plurality of base sequences of the WUS in the resource set; monitor, at the UE, the resource set for the WUS having the repetition level; decode, at the UE, a transmission received from a new radio node B (gNB) in the resource set for the WUS; and switch, at the UE, from a power saving mode (PSM) to a network access mode (NAM) based on detection of the WUS in the resource set.

[0156] Example 19 includes the at least one machine-readable storage medium according to Example 18, further including instructions that perform the following operations when executed: select, at the UE, a repetition level of the resource set for the WUS based on a channel condition of the UE.

[0157] Example 20 includes at least one machine-readable storage medium according to Example 18 and further includes instructions that, when executed, perform the following operations: identify, at the UE, a resource set for a WUS from one or more of the following: a starting position in the frequency of the resource set, a bandwidth part (BWP) of the resource set, a density of the resource set, a bitmap of the frequency-domain position of the resource set, a higher-layer parameter of the time-domain position, one or more antenna ports for transmission of the WUS, one or more slot indices of the resource set, or one or more symbol indices of the resource set.

[0158] Various techniques or certain aspects or portions thereof may take the form of program code (i.e., instructions) embodied in a tangible medium such as a floppy disk, a compact disc read-only memory (CD-ROM), a hard disk drive, a non-transitory computer-readable storage medium, or any other machine-readable storage medium, where, when the program code is loaded into a machine such as a computer and executed by the machine, the machine becomes an apparatus for practicing the various techniques. In the case of executing program code on a programmable computer, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and / or storage elements may be random access memory (RAM), erasable programmable read-only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. Nodes and wireless devices may also include a transceiver module (i.e., transceiver), a counting module (i.e., counter), a processing module (i.e., processor), and / or a clock module (i.e., clock) or timing module (i.e., timer). In one example, selected components of the transceiver module may be located in a cloud radio access network (C-RAN). One or more programs that implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, etc. Such programs may be implemented in a high-level procedural or object-oriented programming language to communicate with a computer system. However, if desired, one or more programs may be implemented in assembly language or machine language. In any case, the language may be a compiled or interpreted language and combined with hardware specific implementations.

[0159] As used herein, the term "circuit" may refer to, be part of, or include: an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) that executes one or more software or firmware programs, combinational logic circuits, and / or other suitable hardware components that provide the recited functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic components that are capable of operating at least partially in hardware.

[0160] It should be understood that many of the functional units described in this specification have been labeled as modules to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit that includes a custom very large scale integration (VLSI) circuit or gate array, off-the-shelf semiconductors (such as logic chips, transistors), or other discrete components. A module may also be implemented in a programmable hardware device (such as a field programmable gate array, programmable array logic, programmable logic device, etc.).

[0161] A module may also be implemented in software for execution by various types of processors. The identified executable code modules may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, procedures, or functions. However, the executable files of the identified modules may not be physically located together, but may include different instructions stored in different locations, which, when logically connected together, include the module and implement the intended purpose of the module.

[0162] In fact, the executable code modules may be a single instruction or many instructions, and may even be distributed over several different code segments, between different programs, and across several memory devices. Similarly, the operational data may be identified and shown within a module herein, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations, including distributed over different storage devices, and the operational data may exist at least partially only as electronic signals on a system or network. A module may be passive or active, including an agent operable to perform the desired function.

[0163] The phrase "an example" or "exemplary" as used throughout this specification means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, the appearances of the phrase "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0164] As used herein, for convenience, a plurality of items, structural elements, constituent elements, and / or materials may be presented in a common list. However, these lists should be understood to be such that each member of the list is separately identified as a separate and unique member. Thus, no member of such a list should be understood to be in fact equivalent to any other member of the same list solely based on being presented in a common group in the absence of contrary indication. Additionally, various embodiments and examples of the present technology may be referenced herein along with alternatives for its various components. It should be understood that such embodiments, examples, and alternatives should not be understood to be in fact equivalents of one another, but rather should be considered separate and autonomous representations of the present technology.

[0165] Furthermore, the features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, to provide a thorough understanding of the embodiments of the present technology. However, those skilled in the relevant art will recognize that the present technology may be practiced without one or more of the specific details or in conjunction with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the present technology.

[0166] While the foregoing examples illustrate the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that many modifications may be made to the specific forms of implementation, use, and details without the exercise of creative faculty and without departing from the principles and concepts of the present technology. Accordingly, this technology is not intended to be limited herein except as set forth in the following claims.

Claims

1. A user equipment (UE) operable for wake-up signal (WUS) communication in a wireless network, the UE comprising: One or more processors configured to: Identify, at the UE, a resource set of the WUS, wherein the WUS includes a cell-specific sequence that is generated from a Zadoff-Chu (ZC) sequence having a Gold coverage code sequence initialized by UE-specific parameters using the following formula: where: g(n) is the cell-specific sequence, μ is predetermined or configured via cell-specific signaling, and n' is n mod L zc , And L zc is the length of the ZC sequence; Monitor, at the UE, the resource set of the WUS; Decode, at the UE, a transmission received from a base station in the resource set of the WUS; and Switch, at the UE, from a power saving mode (PSM) to a network access mode (NAM) based on a detection of the WUS in the resource set; and A memory interface configured to store the resource set of the WUS in a memory.

2. The UE according to claim 1, wherein the one or more processors are further configured to: Detect, at the UE, a repetition level of the resource set of the WUS.

3. The UE according to claim 1, wherein the WUS further includes a UE-specific sequence generated from a length-31 Gold sequence.

4. The UE according to claim 1, wherein the WUS includes a UE-specific initialization of the UE-specific sequence, wherein the UE-specific initialization is based on one or more of the following: a cell radio network temporary identifier (C-RNTI), a physical cell identifier (ID), a virtual cell ID, a bandwidth part ID (BWP ID), or a time slot interval.

5. The UE according to claim 1, wherein the one or more processors are further configured to: Identify, at the UE, a length of a base sequence among a plurality of base sequences, wherein the length of the base sequence is based on a target level of coverage of the UE and is configured via radio resource control (RRC) signaling.

6. The UE according to claim 1, wherein the one or more processors are further configured to: Identify, at the UE, the resource set of the WUS from one or more of the following: A starting position in a frequency of the resource set, A bandwidth part (BWP) of the resource set, A density of the resource set, A bitmap of a frequency domain position of the resource set, Higher layer parameters of a time domain position, One or more antenna ports for transmission of the WUS, One or more time slot indices of the resource set, or One or more symbol indices of the resource set.

7. The UE according to claim 1, wherein the resource set of the WUS is configured via radio resource control (RRC) signaling.

8. A base station operable for wake-up signal (WUS) communication in a wireless network, the base station comprising: One or more processors configured to: Determine, at the base station, a resource set of the WUS, wherein the WUS includes a cell-specific sequence that is generated from a Zadoff-Chu (ZC) sequence having a Gold coverage code sequence initialized by UE-specific parameters using the following formula: where: g(n) is the cell-specific sequence, μ is predetermined or configured via cell-specific signaling, and n' is n mod L zc , and L zc is the length of the ZC sequence: Encoding, at the base station for transmission to a user equipment UE, a resource set of the WUS, wherein the WUS signals the UE to switch from a power saving mode PSM to a network access mode NAM; and A memory interface configured to store the resource set of the WUS in a memory.

9. The base station according to claim 8, wherein the one or more processors are further configured to: At the base station, select a repetition level of the resource set of the WUS based on a channel condition of the UE.

10. The base station according to claim 8, wherein the WUS further includes a UE-specific sequence generated from a length-31 Gold sequence.

11. The base station according to claim 8, wherein the WUS includes UE-specific initialization of the UE-specific sequence, wherein the UE-specific initialization is based on one or more of: a cell radio network temporary identifier (C-RNTI), a physical cell identifier (ID), a virtual cell ID, a bandwidth part ID (BWP ID), or a slot offset.

12. The base station according to claim 8, wherein the one or more processors are further configured to: at the base station, determine a length of a base sequence among a plurality of base sequences, wherein the length of the base sequence is based on a coverage level of the UE and is configured via radio resource control RRC signaling.

13. The base station according to claim 8, wherein the resource set of the WUS is configured via radio resource control RRC signaling, and the resource set of the WUS is identifiable from one or more of: A starting position in a frequency of the resource set, A bandwidth part BWP of the resource set, A density of the resource set, A bitmap of a frequency domain position of the resource set, Higher layer parameters of a time domain position, One or more antenna ports for transmission of the WUS, One or more slot indices of the resource set, or One or more symbol indices of the resource set.

14. At least one machine-readable storage medium having instructions embodied thereon for Wake-Up Signal WUS communication in a wireless network, the instructions when executed by one or more processors at a user equipment UE perform the following operations: Identify a resource set of WUS at the UE, where the WUS includes a cell-specific sequence, and the cell-specific sequence is generated from a Zadoff-Chu (ZC) sequence having a Gold covering code sequence initialized by UE-specific parameters using the following formula: Wherein: g(n) is the cell-specific sequence, μ is predetermined or configured via cell-specific signaling, and n' is n mod L zc , and L zc is the length of the ZC sequence; At the UE, monitor the resource set of the WUS; At the UE, decode a transmission received from a base station in the resource set of the WUS; And At the UE, switch from a power saving mode PSM to a network access mode NAM based on detection of the WUS in the resource set.

15. The at least one machine-readable storage medium according to claim 14, further comprising instructions that when executed perform the following operations: At the UE, select a repetition level of the resource set of the WUS based on a channel condition of the UE.

16. The at least one machine-readable storage medium according to claim 14, wherein the WUS further includes a UE-specific sequence generated from a length-31 Gold sequence.

17. The at least one machine-readable storage medium according to claim 14, wherein the WUS includes UE-specific initialization of a UE-specific sequence, and the UE-specific initialization is based on one or more of the following: a cell radio network temporary identifier (C-RNTI), a physical cell identifier (ID), a virtual cell ID, a bandwidth part ID (BWP ID), or a slot offset.

18. The at least one machine-readable storage medium according to claim 14, further comprising instructions that, when executed, perform the following operations: Identify, at the UE, the length of a base sequence among a plurality of base sequences, wherein the length of the base sequence is based on a target level of coverage of the UE and is configured via radio resource control (RRC) signaling.

19. The at least one machine-readable storage medium according to claim 14, further comprising instructions that, when executed, perform the following operations: Identify, at the UE, the resource set of the WUS from one or more of the following: A starting position in the frequency of the resource set, A bandwidth part (BWP) of the resource set, The density of the resource set, A bitmap of the frequency-domain position of the resource set, Higher-layer parameters of the time-domain position, One or more antenna ports for transmission of the WUS, One or more slot indices of the resource set, or One or more symbol indices of the resource set.

20. The at least one machine-readable storage medium according to claim 14, wherein the resource set of the WUS is configured via radio resource control (RRC) signaling.

Images