WAKE-UP RECEIVER USAGE BY A COMMUNICATION NODE

TECHNICAL FIELD

The present application relates generally to a communication node, and relates more particularly to usage of a wake-up receiver by such a node.

BACKGROUND

A wireless communication network transmits a paging message to a wireless communication device in order to trigger the device to connect to the wireless communication network, e.g., for receiving downlink user data. The paging message may for instance be transmitted over a downlink control channel, e.g., a Physical Downlink Control Channel (PDCCH). A wireless communication device in this case must monitor and decode the downlink control channel in order to determine whether any paging message is intended for the device. Such monitoring and decoding, however, consumes device power and negatively impacts device battery life.

Reduced power consumption can be realized by the use of a so-called wake-up signal (WUS). A wake-up signal is a signal that indicates a wireless communication device is to wake-up one or more receiver components, if needed, and monitor a downlink control channel, e.g., for any paging message intended for the device. A wake-up signal is designed so that it can be detected more quickly and/or without consuming as much power as compared to monitoring and decoding a downlink control channel. Exploiting a wake-up signal affords a wireless communication device more frequent opportunities to operate in a low power mode, e.g., in between occasions in which the device is to monitor for the wake-up signal.

Yet additional power conservation can be realized by using a so-called wake-up receiver (WUR) to monitor for and receive the wake-up signal. A wake-up receiver is a receiver that is capable of receiving a wake-up signal and that is separate from another receiver (referred to as a main receiver) which is woken up upon the wake-up receiver receiving the wake-up signal. The wake-up receiver’s circuitry is less complex and/or more power efficient than the main receiver. This may mean that the main receiver is capable of receiving some signals or channels that the wake-up receiver cannot. For example, the main receiver may be capable of receiving one or more other signals or channels (e.g., PDCCH) needed for connecting to the wireless communication network, but the wake-up receiver may not be capable of receiving such signals or channels. Relieved of the need to receive the other signal(s) or channel(s), the wake-up receiver can be simplified and more power efficient than the main receiver. The wakeup receiver may for instance be dedicated for receiving the wake-up signal, and optionally, a synchronization signal. Or, even if not so dedicated, the wake-up receiver may be dedicated or tailored for receiving one or more signals or channels in a Radio Resource Control (RRC) idle state or an RRC inactive state, i.e., to the exclusion of one or more other signals or channels in an RRC connected state. In these and other cases, a wireless communication device may be equipped with both a wake-up receiver and another receiver (e.g., referred to as a main receiver) capable of receiving the other signal(s) or channel(s) that the wake-up receiver is not capable of receiving. The wireless communication device can then power down one or more components of its main receiver unless and until its wake-up receiver receives a wake-up signal.

Challenges nonetheless still exist in minimizing device power consumption and prolonging battery life. Indeed, even if a wireless communication device can use a wake-up receiver to reduce how often the device has to monitor a downlink control channel, there are still limits on the power conservation benefits achievable with a wake-up receiver.

SUMMARY

Some embodiments herein provide signal(s) and/or channel(s) that are receivable with a wake-up receiver, e.g., for performing signal measurements usable for cell (re)selection and/or for performing idle mode procedure(s) or inactive mode procedure(s). Some embodiments for example avoid a wireless communication device having to use its main receiver and tune to a different frequency than that of a wake-up signal in order to perform signal measurements for cell reselection and in order to perform other idle mode procedures. Some embodiments herein thereby improve power conservation in a wireless communication device equipped with a wakeup receiver.

More particularly, embodiments herein include a method performed by a wireless communication device. The method comprises, while operating a first receiver of the wireless communication device in a sleep state, receiving one or more signals and/or one or more channels with a second receiver of the wireless communication device that is a wake-up receiver. In some embodiments, the method also comprises, still while operating the first receiver in the sleep state, performing cell selection or reselection, and/or checking for an update of System Information, based on the one or more signals and/or one or more channels received.

In some embodiments, receiving one or more signals and/or one or more channels comprises receiving one or more signals with the second receiver. In this case, performing cell selection or reselection comprises performing one or more signal measurements on the one or more signals received, and performing cell selection or reselection based on the one or more signal measurements. In some embodiments, performing cell selection or reselection comprises applying one or more wake-up receiver specific offsets to one or more results of the one or more signal measurements. In some embodiments, performing cell selection or reselection comprises performing cell selection or reselection based on the one or more results as offset by the one or more wake-up receiver specific offsets. In some embodiments, performing cell selection or reselection comprises prioritizing, or limiting selection or reselection to, cells that support reception of the one or more signals with a wake-up receiver. In some embodiments, receiving one or more signals and/or one or more channels comprises receiving, with the second receiver, one or more channels that convey System Information. In some embodiments, the conveyed System Information includes a system frame number, a cell barred flag, and/or an intra-frequency reselection flag, and checking for an update of System Information comprises checking for an update of the system frame number, the cell barred flag, and/or the intra-frequency reselection flag.

In some embodiments, receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels while the wireless communication device is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode, and performing cell selection or reselection, and/or checking for an update of System Information are performed while the wireless communication device is in the RRC idle mode or the RRC inactive mode.

In some embodiments, the wake-up receiver is configured to receive a wake-up signal indicating the wireless communication device is to awaken the first receiver from the sleep state. In some embodiments, receiving one or more signals and/or one or more channels comprises receiving one or more signals that include a cell measurement wake-up signal, CM- WUS. In some embodiments, the CM-WUS has the same modulation, length, and/or coding as a wake-up signal but is transmitted for cell measurement purposes. In some embodiments, a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is received indicates that the CM-WUS is a CM-WUS instead of a wake-up signal for awakening the first receiver from the sleep state.

In some embodiments, receiving one or more signals and/or one or more channels comprises receiving one or more signals. In some embodiments, the one or more signals received include a signal that is based on a concatenation of a pair of Zadoff-Chu sequences with different roots. In other embodiments, the one or more signals received include a signal that is generated from a single binary sequence. In yet other embodiments, the one or more signals received include a signal that is a Primary Synchronization Signal, PSS, or a Secondary Synchronization Signal, SSS. In still yet other embodiments, the one or more signals received include a signal that is part of a synchronization signal block, SSB. In some embodiments, the signal is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences. In some embodiments, the signal is based on a concatenation of a pair of Zadoff-Chu sequences with different roots. In this case, one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair. In some embodiments, the signal is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences. In some embodiments, the signal is part of an SSB. In some embodiments, the SSB lacks a Physical Broadcast Channel and includes a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time. In other embodiments, the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB. In some embodiments, the MIB lacks a synchronization signal block time index field. In other embodiments, the MIB alternatively or additionally lacks a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field.

In yet other embodiments, the MIB alternatively or additionally lacks a System Information Block #1 , SIB1 , numerology field. In still yet other embodiments, the MIB alternatively or additionally lacks a SIB1 configuration field. In still yet other embodiments, the MIB alternatively or additionally lacks a common resource block, CRB, grid offset field. In still yet other embodiments, the MIB alternatively or additionally lacks a half-frame bit field. In some embodiments, the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols. In other embodiments, the SSB alternatively or additionally is received with a subcarrier spacing less than 15 kHz. In yet other embodiments, the SSB alternatively or additionally recurs with a period greater than 160ms.

In some embodiments, a granularity of a synchronization raster for the SSB is greater than 1.2 MHz or frequency locations of the SSB are not on a synchronization raster.

Other embodiments herein include a method performed by a network node. The method comprises transmitting, to a wireless communication device that has a first receiver and a second receiver that is a wake-up receiver, one or more signals and/or one or more channels that are usable by the wireless communication device for cell selection or reselection and/or for checking for an update to System Information while the first receiver is in a sleep state.

In some embodiments, transmitting the one or more signals comprises transmitting one or more channels that convey System Information. In some embodiments, the conveyed System Information includes a system frame number, a cell barred flag, and/or an intrafrequency reselection flag.

In some embodiments, transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels while the wireless communication device is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode. In some embodiments, the one or more signals and/or one or more channels are usable for cell selection or reselection, and/or checking for an update to System Information while the wireless communication device is in the RRC idle mode or the RRC inactive mode.

In some embodiments, the wake-up receiver is configured to receive a wake-up signal indicating the wireless communication device is to awaken another receiver from a sleep state. In some embodiments, transmitting one or more signals and/or one or more channels comprises transmitting one or more signals that include a cell measurement wake-up signal, CM-WUS. In some embodiments, the CM-WUS has the same modulation, length, and/or coding as a wake-up signal but is transmitted for cell measurement purposes. In some embodiments, a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is transmitted indicates that the CM-WUS is a CM-WUS instead of a wake-up signal.

In some embodiments, transmitting one or more signals and/or one or more channels comprises transmitting one or more signals. In some embodiments, the one or more signals transmitted include a signal that is based on a concatenation of a pair of Zadoff-Chu sequences with different roots. In other embodiments, the one or more signals transmitted include a signal that is generated from a single binary sequence. In yet other embodiments, the one or more signals transmitted include a signal that is a Primary Synchronization Signal, PSS, or a Secondary Synchronization Signal, SSS. In still yet other embodiments, the one or more signals transmitted include a signal that is part of a synchronization signal block, SSB. In some embodiments, the signal is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences. In some embodiments, the signal is based on a concatenation of a pair of Zadoff- Chu sequences with different roots. In some embodiments, one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair. In some embodiments, the signal is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences. In some embodiments, the signal is part of an SSB. In some embodiments, the SSB lacks a Physical Broadcast Channel and includes a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time. In other embodiments, the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB. In some embodiments, the MIB lacks at least a synchronization signal block time index field. In other embodiments, the MIB lacks at least a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field. In yet other embodiments, the MIB lacks at least a System Information Block #1 , SIB1 , numerology field. In still yet other embodiments, the MIB lacks a SIB1 configuration field. In still yet other embodiments, the MIB lacks a common resource block, CRB, grid offset field. In still yet other embodiments, the MIB lacks a half-frame bit field. In some embodiments, the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols. In other embodiments, the SSB alternatively or additionally is received with a subcarrier spacing less than 15 kHz. In yet other embodiments, the SSB alternatively or additionally recurs with a period greater than 160ms. In some embodiments, a granularity of a synchronization raster for the SSB is greater than 1.2 MHz or frequency locations of the SSB are not on a synchronization raster.

Other embodiments herein include a wireless communication device. The wireless communication device is configured to, while operating a first receiver of the wireless communication device in a sleep state, receive one or more signals and/or one or more channels with a second receiver of the wireless communication device that is a wake-up receiver. The wireless communication device is also configured to, still while operating the first receiver in the sleep state, perform cell selection or reselection, and/or check for an update of System Information, based on the one or more signals and/or one or more channels received.

In some embodiments, the wireless communication device is configured to perform the steps described above for a wireless communication device.

Other embodiments herein include a network node. The network node is configured to transmit, to a wireless communication device that has a first receiver and a second receiver that is a wake-up receiver, one or more signals and/or one or more channels that are usable by the wireless communication device for cell selection or reselection and/or for checking for an update to System Information while the first receiver is in a sleep state.

In some embodiments, the network node is configured to perform the steps described above for a network node.

In some embodiments, a computer program comprising instructions which, when executed by at least one processor of a wireless communication device, causes the wireless communication device to perform the steps described above for a wireless communication device. In some embodiments, a carrier containing the computer program is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Other embodiments herein include a wireless communication device. The wireless communication device comprises communication circuitry and processing circuitry. The processing circuitry is configured to, while operating a first receiver of the wireless communication device in a sleep state, receive one or more signals and/or one or more channels with a second receiver of the wireless communication device that is a wake-up receiver. The processing circuitry is also configured to, still while operating the first receiver in the sleep state, perform cell selection or reselection, and/or check for an update of System Information, based on the one or more signals and/or one or more channels received.

In some embodiments, the processing circuitry is configured to perform the steps described above for a wireless communication device.

Other embodiments herein include a network node. The network node comprises communication circuitry and processing circuitry. The processing circuitry is configured to transmit, to a wireless communication device that has a first receiver and a second receiver that is a wake-up receiver, one or more signals and/or one or more channels that are usable by the wireless communication device for cell selection or reselection and/or for checking for an update to System Information while the first receiver is in a sleep state.

In some embodiments, the processing circuitry is configured to perform the steps described above for a network node.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram of a wireless communication network according to some embodiments.

Figure 2 is a block diagram of a wake-up signal occasion and paging occasion according to some embodiments.

Figure 3 is a block diagram of a wake-up receiver (WUR) synchronization signal block (SSB) according to some embodiments.

Figure 4A is a block diagram of a WUR SSB in the form of a single-sided frequency truncated SSB according to some embodiments.

Figure 4B is a block diagram of a WUR SSB in the form of a double-sided frequency truncated SSB according to some embodiments.

Figure 4C is a block diagram of a WUR SSB in the form of a frequency and time truncated SSB according to some embodiments.

Figure 4D is a block diagram of a WUR SSB in the form of a frequency truncated but time expanded SSB according to some embodiments.

Figure 5A is a block diagram of an SSB without PBCH according to some embodiments.

Figure 5B is a block diagram of a WUR SSB in the form of a frequency truncated SSB according to other embodiments.

Figure 6 is a block diagram of a legacy SSB for comparison against some embodiments.

Figure 7 is a logic flow diagram of cell selection according to some embodiments.

Figure 8 is a logic flow diagram of a method performed by a first communication node according to some embodiments.

Figure 9 is a logic flow diagram of a method performed by a second communication node according to some embodiments.

Figure 10 is a block diagram of a first communication node according to some embodiments.

Figure 11 is a block diagram of a second communication node according to some embodiments.

Figure 12 is a block diagram of a communication system in accordance with some embodiments

Figure 13 is a block diagram of a user equipment according to some embodiments.

Figure 14 is a block diagram of a network node according to some embodiments.

Figure 15 is a block diagram of a host according to some embodiments.

Figure 16 is a block diagram of a virtualization environment according to some embodiments.

Figure 17 is a block diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION Figure 1 shows a first communication node 12 and second communication node 14 according to some embodiments herein. In one embodiment as exemplified in Figure 1 , the first communication node 12 is a wireless communication device and the second communication node 14 is a network node in a wireless communication network 10. In another embodiment not shown, though, the first communication node 12 is a network node in a wireless communication network 10 and the second communication node 14 is a wireless communication device. In still another embodiment not shown, each of the first and second communication network nodes 12, 14 is a wireless communication device.

Regardless of the particular types of the communication nodes 12, 14, the first communication node 12 is equipped with receive circuitry for receiving one or more signals or channels from the second communication node 14. One or more components of this receive circuitry are configurable to be put to sleep, e.g., in a sleep state. When put to sleep, the sleeping component(s) consume less power than when awake, e.g., such that the sleep state may also be referred to as a low power state. The sleeping component(s) may for instance be powered down so as to be inoperable unless and until the component(s) are awaken, e.g., by control circuitry which may be separate from or a part of the receive circuitry.

As one example, the receive circuitry may include or implement a receiver 12R. The receiver 12R is capable of receiving one or more signals or channels 22 needed for establishing a connection with the second communication node 14, e.g., a Physical Downlink Control Channel (PDCCH), and/or for user data reception. The receiver 12R may for instance be capable of receiving a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH). The receiver 12R may therefore generally be usable for reception in a Radio Resource Control (RRC) connected mode.

In some embodiments, one or more components of the receiver 12R are configurable to be put to sleep. The first communication node 12 may for instance put these component(s) to sleep unless and until those component(s) are needed for receiving a PDCCH, e.g., for checking for a paging message. That is, before the receiver 12R is able to receive certain signal(s) or channel(s), the asleep component(s) must be awaken.

The second communication node 14 in this regard may transmit a wake-up signal (WUS) 20 to the first communication node 12. The wake-up signal 20 triggers the first communication node 12 to wake up one or more components of the receiver 12R from sleep.

In some embodiments, the receiver 12R itself is able to receive the wake-up signal 20, even when one or more components of the receiver 12R are asleep. For example, the component(s) put to sleep may be separate from the component(s) of the receiver 12R usable to receive the wake-up signal 20.

In other embodiments, by contrast, the receive circuitry also includes or implements another receiver, referred to as a wake-up receiver (WUR) 12W, that is capable of receiving the wake-up signal 20. The wake-up receiver 12W may not be capable of receiving the other one or more signals or channels 22. The wake-up receiver 12W may generally be usable for reception in an RRC idle mode or an RRC inactive mode, as compared to the receiver 12R which may be usable for reception in an RRC connected mode. Regardless, in some embodiments, use of the wake-up receiver 12W enables the first communication node 12 to put more components of the receiver 12R to sleep, since the receiver 12R in this case is relieved of the need to detect the wake-up signal 20. Accordingly, in some embodiments, the wake-up receiver 12W is simplified and more power efficient than the main receiver 12R.

In operation in this case, then, when the first communication node 12 does not need to receive the one or more signals or channels 22, such as when the first communication node 12 is in an RRC idle or inactive mode, the first communication node 12 operates the receiver 12R in a power-saving or sleep state, e.g., by powering down one or more components of the receiver 12R. During this time, though, the wake-up receiver 12W monitors for the wake-up signal 20. Reception of the wake-up signal 20 indicates to the first communication node 12 that the receiver 12R needs to be awaken in order to monitor for the one or more signals or channels 22. That is, the wake-up signal 20 indicates to wake-up one or more components of the receiver 12R. Accordingly, responsive to detecting the wake-up signal 20, the wake-up receiver 12W wakes up the one or more components of the receiver 12R, whereupon the receiver 12R monitors for the one or more signals or channels 22.

No matter which receiver 12R, 12W is configured to receive the wake-up signal 20, some embodiments herein provide one or more signals and/or one or more channels 16 shown in Figure 1. Some embodiments design and/or transmit the signal(s) and/or channels 16 in such a way that the signal(s) and/or channel(s) are receivable by the WUR 12W. The signal(s) and/or channel(s) 16 may for example be usable for cell (re)selection and/or for performing idle mode procedure(s) or inactive mode procedure(s). Rather than having to receive the signal(s) and/or channel(s) 16 with the main receiver 12R, then, the first communication node 12 may receive the signal(s) and/or channel(s) 16 with the wake-up receiver 12W and thereby better conserve power. Some embodiments herein thereby improve power conservation in the first communication node 12.

In some embodiments, the signal(s) and/or channel(s) 16 are transmitted/received as part of a synchronization signal block (SSB), e.g., that is specific for reception by the WUR 12W.

Consider an example in a New Radio (NR) context below where the first communication node 12 is a user equipment (UE) and the second communication node 14 is a gNB. In this example, the signal(s) and/or channel(s) 16 are transmitted as part of an SSB, referred to as a WUR-SSB. In order to enable low-power and low-complexity WUR 12W to decode SSB for cell measurements, a new WUR-specific SSB can be generated. The gNB can generate such new WUR-SSB using its Orthogonal Frequency Division Multiplexing -based (OFDM-based) transceiver while the WUR can use a simple a simple modulation such as on-of-keying (OOK) or frequency shift keying (FSK). To this end, the generated WUR-SSB may need a different structure and/or configuration compared to the legacy SSB.

New WUR-SSB structure

In one embodiment, a new SSB is designed for WUR to be suitable for low-complexity and low-power WUR 12W. In particular, on the transmitter side, the WUR-SSB as shown in Figure 3 spans over K subcarriers and N symbols where K and N can be different than the existing NR SSB. For example, the number of physical resource blocks (PRBs) can be smaller than 240 (K < 240) to have a smaller bandwidth. Meanwhile, to increase the number of resource elements (REs), the number of symbols can be increased.

In another embodiment, for a given number of REs (L), the number of subcarriers or PRBs and symbols are jointly adjusted to minimize the WUR power consumption. For example, one embodiment optimizes K and N, such that KN = L, where L is fixed. As another example, one embodiment increases the number of symbols while decreasing the bandwidth (i.e., subcarriers/PRBs). As still another example, one embodiment only reduces the number of symbols, whereas another embodiment only reduces the number of subcarriers or PRBs. Still other embodiments reduce both the number of subcarriers/PRBs and symbols.

In another embodiment, the WUR-SSB uses a smaller subcarrier spacing (SCS) compared to the legacy SSB. For example, the SCS of the WUR-SSB can be 7.5 kHz to reduce the bandwidth by factor of 2 (compared to 15 kHz SCS). As another example, the SCS of the WUR-SSB can be 5 kHz to reduce the bandwidth by factor of 3. As still another example, the SCS of the WUR-SSB can be 1 .25 kHz to reduce the bandwidth by factor of 12.

In another embodiment, the WUR-SSB uses a different structure than the legacy SSB. The new structure can be based on the legacy SSB structure with further bandwidth reduction. For example, different WUR structures according to some embodiments are illustrated in Figures 4A-4D. The WUR structure shown in Figure 4A is truncated in frequency on one side. The WUR structure shown in Figure 4B is truncated in frequency on both sides. The WUR structure shown in Figure 4C is truncated in time and frequency. And the WUR structure shown in Figure 4D is truncated and reduced bandwidth with time domain expansion.

In another embodiment, an SSB used for cell measurements and synchronization only contains PSS and SSS, without Physical Broadcast Channel (PBCH). Figures 5A-5B show two examples of a PBCH-free SSB. Figure 5A in particular shows a PBCH-free SSB that removes the PBCH while still keeping the PSS and SSS spaced apart in time in their legacy positions, as if the PBCH were still there. Figure 5B by contrast shows a PBCH-free SSB that removes the PBCH and condenses the PSS and SSS in time so that they are consecutive in time, with no gap therebetween. In another embodiment, the WUR-SSB is contained in the same REs as those of the legacy SSB, or is multiplexed in time with the legacy SSB (e.g., a certain frequency offset can either be configured or is hard-coded in the 3GPP specification). This allows the gNB to still get the same gains from the ‘micro sleep Tx’ features which enables the base-station to reduce the energy consumption by going to a micro sleep state when there are no “always-on” or broadcast signals.

Reduction of information carried by WUR-SSB

Within legacy SSB, PBCH carries basic system information such as master information block (MIB) and determines essential parameters for initial access of the cell including the downlink system bandwidth and the system frame number. SSB can be used for different purposes such as initial access, time-frequency synchronization, and radio resource management (RRM) measurements. Depending on the case, for WUR-SSB it may not be necessary to always transmit all the information carried by MIB. A PBCH that excludes some information in this way, for WUR purposes, is referred to as a WUR-PBCH.

Accordingly, in one embodiment, one or more of the MIB fields are not transmitted for an WUR-SSB used for synchronization and RRM measurements. Table 1 below shows different possible candidates for exclusion from the MIB. For example, information about System Information Block #1 (SIB1) may not be needed, since legacy SIB1 is not needed for synchronization or RRM measurements and can instead be acquired when the UE has the intention to access the cell and set up a connection. Therefore, MIB size can be reduced which is beneficial in terms of coverage or the lower data rate as supported by the WUR. Reducing the MIB size for WUR-PBCH can enable employing simple modulation schemes for WUR.

Table 1

* All these are required only when the UE continues to acquire SIB1 and other information, i.e., upon cell access and connection setup, therefore no need to have in ‘WUR-MIB’.

In summary, then, a WUR-MIB may contain just the following fields shown in Table 2 (example with 8 bit CRC) in some embodiments:

Table 2

New WUR-SSB configuration

In another embodiment, a new configuration is introduced for WUR-SSB. Specifically, new values are considered for the monitoring periodicity and frequency locations of WUR-SSB to minimize the WUR energy consumption for cell search.

In a sub-embodiment, the periodicities of WUR-SSB increase by a factor of a compared to legacy SSB. In another embodiment, new values are added to the set of existing SSB periodicity for WUR-SSB. In particular, the WUR-SSB periodicity can be more than 160 ms (the maximum legacy SSB periodicity) which can be for example 320 ms, 640 ms, or 1280 ms.

In one embodiment, the granularity of synchronization raster for WUR-SSB is larger than legacy SSB. For example, the existing granularity increases a factor of q to reduce the acquisition time and thus receiver energy consumption (i.e., fewer candidates for the WUR UE to check). For example, the granularity of SSB can be larger than 1 .2 MHz (legacy value for below 3 GHz).

In another sub-embodiment, the frequency locations of WUR-SSB are off-raster (i.e., are not on the synchronization raster) in order to provide further deployment flexibility. In this case, there will be less constraints on the positions of SSB within a frequency range which is particularly beneficial for WUR operation in coexistence scenarios (e.g., considering out of band emissions).

In some embodiments where the WUR-SSB is specific for reception in RRC IDLE or RRC INACTIVE mode, the first communication node 12 may be configured to receive multiple types of SSB, including the WUR-SSB which is specific for IDLE or INACTIVE mode and the legacy SSB which is specific for RRC CONNECTED mode.

Using NR as an example, then, the legacy SSB is described below so as to highlight the distinction of the WUR-SSB described above. In some embodiments, the legacy synchronization signal block (SS block or SSB) consists of primary and secondary synchronization signals (PSS and SSS) and physical broadcast channel (PBCH). During the initial cell search, the UE first aims at detecting PSS and then SSS. Time and frequency synchronization as well as cell ID detection are done using PSS and SSS. Proper detection of PSS and SSS is an essential step for PBCH demodulation. PBCH carries basic system information such as master information block (MIB) and determines essential parameters for initial access of the cell including the downlink system bandwidth, where to locate the remaining SI, and the system frame number. The legacy SSB periodicity can be {5, 10, 20, 40, 80, 160} ms, configured via RRC parameters. However, a default periodicity of 20 ms is assumed during initial cell search. To support initial access and beam management, NR supports SS burst set which consists of multiple SS blocks confined within a 5 ms window. Depending on the carrier frequency, up to 64 SS blocks can be transmitted within a SS burst set.

In the frequency domain, one legacy SSB block occupies 20 contiguous resource blocks which is equivalent to 240 subcarriers, as illustrated in Figure 6. In the time domain, one legacy SSB block spans over 4 OFDM symbols. Among the four symbols, one symbol is for PSS, one symbol is for SSS, and 2 symbols are for PBCH. Specifically, PSS occupies the first OFDM symbol of SSB and spans over 127 subcarriers. SSS is located in the third OFDM symbol of legacy SSB and spans over 127 subcarriers. The total number of resource elements (REs) used for PBCH transmission per legacy SSB is 576. There are, however, 113 unused subcarriers in the first symbol, and 17 unused subcarriers in the thirds symbol, as shown in Figure 6. Therefore, there are 130 unused resource elements (REs) within a legacy SSB. In the current NR design, the complex-valued symbols corresponding to these unused REs are set to zero.

The legacy SSB bandwidth depends on the subcarrier spacing (SCS) as provided in Table 3.

Table 3: Legacy SSB bandwidth for different SCSs. WUS-based signaling for cell measurements

Consider now another example where the signal(s) and/or channel(s) 16 in Figure 1 include a so-called cell measurement (CM) wake-up signal (WUS), referred to as CM-WUS.

In some embodiments in this regard, a simple signaling based on WUS design can be used for cell measurements (CM-WUS), i.e., this new cell measurement signaling can be received by WUR 12W as it has the same modulation, length, and/or coding as WUS.

In one embodiment, the CM-WUS is WUR-SSB without PBCH, e.g., CM-WUS can be derived from one of the existing synchronization signals i.e., the PSS or the SSS.

In another embodiment, the CM-WUS is formed from a Zadoff Chu sequence, e.g., which has a flexible length and good auto-correlation and cross-correlations properties. In particular, in some embodiments, a Zadoff Chu sequence is orthogonal to a time-shifted version of the sequence. Also, a Zadoff Chu sequence defined by a first root has low cross-correlation with a second Zadoff Chu sequence defined by a second root. These properties allow a device to synchronize to the sequence in time, and also to distinguish a specific Zadoff Chu sequence transmitted from a specific access point from a set of possible Zadoff Chu sequences transmitted from other access points. The length of the sequence can be said to correspond to the power with which the sequence is transmitted and can be selected sufficiently long to facilitate detection at a desired signal-to-interference-plus-noise-ratio (SINR). A Zadoff Chu sequences also supports frequency synchronization and detection of frequency offsets in the local frequency reference hosted by the communication node in comparison to the carrier frequency of a received Zadoff Chu sequence. A Doppler shift in frequency of the received Zadoff Chu sequence will however distort its excellent auto correlation properties.

According to some embodiments herein, the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots, e.g., one Zadoff-Chu sequence in the pair is tacked onto the end of the other Zadoff-Chu sequence in the pair. For example, in some embodiments, the CM-WUS is based on a pair of concatenated Zadoff Chu (ZC) sequences using unique and different roots and // ₂ . Sets of distinct ZC sequences can be generated by means of using multiple unique root pairs. Although the ZC sequences with different roots are not orthogonal, they do exhibit a low cross-correlation. The ZC sequences obtained via cyclic shifts of a ZC root sequence, however, are orthogonal. Therefore, orthogonal ZC sequences can be generated by cyclic shifts of the concatenated sequences. With this design, a large set of orthogonal WUS can be generated based on the concatenated ZC sequences. This design can also be exploited for the CM-WUS thanks to the excellent frequency error resilience it offers even towards high Doppler shifts which may deteriorate the performance of a single Zadoff Chu sequence based CM-WUS.

In one embodiment, the CM-WUS is designed by using a pair of ZC sequences of lengths n _x and n ₂ and roots and // ₂ , respectively. In a sub-embodiment, n _x = n ₂ = n and = _n - // ₂ mod. n such that one sequence is the complex conjugate of the other. This simplification enables a lower-complexity processing for detecting the delay and the carrier frequency offset (CFO) at the wake-up receiver 12W.

More particularly, for ease of exposition, assume n = n _x = n ₂ in the following. There are n - 1 unique root sequences possible for a sequence of length n when n is a prime number. When each CM-WUS is based on a pair of ZC sequences using two unique roots, there are U unique root CM-WUSs possible where each CM-WUS is generated using a unique root pair, and floor(.) is the integer floor function.

Note that there are up to ⁽ⁿ ~ ¹ ^ ⁿ ~ ² ^ unique root CM-WUSs possible such that no two root CM-WUSs have the same root pairs. In some embodiments, for each root CM-WUS with roots and // ₂ , one may also consider its “mirror image” CM-WUS (i.e., the CM-WUS with roots // ₂ and as a distinct CM-WUS even though both have the same root pairs. If mirror images are considered, then there can be up to (n - 1) x (n - 2) unique root CM-WUSs possible.

In another embodiment, the second sequence can be obtained by taking a complex conjugate of the first sequence. In this special case, the root of the second sequence is given by // ₂ = n - mod n, where n is the sequence length and modulo arithmetic is assumed. As a result, each CM-WUS can be uniquely identified by specifying only a single root since the second root is a known function of the first root.

There are unique root CM-WUSs possible where each CM-WUS is generated using a unique root pair. Note that if considering the mirror image of each root CM-WUS as a distinct CM-WUS, then there can be up to (n - 1) unique root CM-WUSs possible.

For each unique root CM-WUS, it is possible to further generate up to V orthogonal CM- WUSs (including the root CM-WUS) by cyclically shifting the root CM-WUS. All such sequences will correspond to the same root pair. In particular, cyclically shifting a root CM-WUS means that each constituent ZC sequence of the root CM-WUS is cyclically shifted by a certain amount, i.e., sequence 1 shifted by c_1 samples while sequence 2 shifted by c_2 samples, where c_1 and c_2 may or may not be the same.

Note that for a length n ZC sequence, the cyclic shifts from 0, ..., n-1 yield n orthogonal ZC sequences where a cyclic shift of 0 corresponds to the root ZC sequence. Further note that a root CM-WUS is constructed from 2 length n ZC sequences. If the same cyclic shift value is applied to both sequences, a root CM-WUS can be used to generate up to n orthogonal CM- WUS including the root CM-WUS. If cyclic shift values for both sequences are not restricted to be the same and can be chosen independently of each other, a root CM-WUS can be used to generate up to n ² orthogonal CM-WUS including the root CM-WUS. In total, there can be up to W=UxV unique CM-WUS where all the CM-WUSs generated from the same root CM-WUS are orthogonal. The CM-WUS generated from different root CM-WUS will not typically be orthogonal but are expected to have a low cross-correlation.

In another embodiment, the CM-WUS can be generated by concatenating two ZC sequences in the time domain, by concatenating two ZC sequences in the frequency domain, or by jointly transmitting two ZC sequences using the same time/frequency resources. For efficient processing, the first communication node 12 needs to know the time-domain and/or frequency domain structure of the CM-WUS generated in this way. This can be either fixed in a governing communications specification or signaled by the network 10, e.g., using System Information.

In another embodiment, the CM-WUS is fixed in a governing communications specification (i.e., roots and cyclic shift values are specified) and the same CM-WUS is used in all cells. In yet another embodiment, more than one possible value for the roots and cyclic shifts are specified in the governing communications specification, i.e., different CM-WUSs are specified and the network 10 configures one such CM-WUS in a cell. The network 10 can indicate this information explicitly in the System Information (SI). Alternatively, the CM-WUS configured in the cell can be tied to a cell characteristic such as Physical Cell Identity (PCID), and the first communication node 12 learns it implicitly during initial synchronization.

In some embodiments, to distinguish between a wake-up signal 20 for waking up the receiver 12R, a synchronization signal, and/or the CM-WUS, dedicated sets of ZC roots and/or ZC cyclic shifts can be assigned to each. The network 10 can then configure the first communication node 12 to monitor for a CM-WUS that is based on a first unique root pair and cyclic shift combination, and to monitor for a wake-up signal 20 that is based on a second unique root pair and cyclic shift combination.

Define the cell measurement signaling

The CM-WUS/WUR-SSB can be distinguished from the normal WUS in different ways.

In one embodiment, CM-WUS/WUR-SSB can be defined as a WUS in which the first n bits or a header determine if the WUS has been sent for cell measurement purpose.

In another embodiment CM-WUS can be considered as a WUS which has been transmitted in pre-determined downlink (DL) resources. These DL resources can be defined in the time domain, frequency domain, code domain, or a combination of time, code, and frequency domains. That is, from a governing communications specification or from configuration, the UE would know beforehand in which DL resources regular WUS, WUR-SSB, or CM-WUS can be transmitted. In this way, the logic and UE action (i.e., wake-up, sync, etc.) could be determined either on information in the signal itself or in which DL resource the signal is received.

In a related embodiment, the considered resource elements for CM-WUS/WUR-SSB can be considered as a function of the resource elements used for WUS.

Some embodiments herein are usable for cell search and cell (re)selection as described below. In NR, cell search and cell (re-)selection are based on ‘synchronization signal block’ (SSB). Some embodiments perform cell search and/or cell (re)selection as described in 3GPP TS 38.304 v16.6.0, section 5.2. Figure 7 shows the states, state transitions and procedures in RRCJDLE and RRCJNACTIVE.

As shown in Figure 7, some embodiments herein perform the cell selection process and cell selection criteria as follows, consistent with 3GPP TS 38.304 v16.6.0:

Cell Selection process

Cell selection is performed either by initial cell selection (no prior knowledge of which RF channels are NR frequencies) or by cell selection which leverages stored information.

For initial cell selection, the UE shall scan all radio frequency (RF) channels in the NR bands according to its capabilities to find a suitable cell. On each frequency, the UE need only search for the strongest cell, except for operation with shared spectrum channel access where the UE may search for the next strongest cell(s). Once a suitable cell is found, this cell shall be selected.

For cell selection by leveraging stored information, this procedure requires stored information of frequencies and optionally also information on cell parameters from previously received measurement control information elements or from previously detected cells. Once the UE has found a suitable cell, the UE shall select it. If no suitable cell is found, the initial cell selection procedure shall be started.

Priorities between different frequencies or radio access technologies (RATs) provided to the UE by system information or dedicated signalling are not used in the cell selection process.

In some embodiments, the cell selection criterion S is fulfilled when:

Srxlev > 0 AND Squat > 0 where

Srxlev = Qrxlevmeas - (Qrxlevmin + Qrxlevminoffset ) - Pcompensation - Qoffsettemp Squal = Qqualmeas - (Qqualmin + Qqualminoffset) - Qoffsettemp

Srxlev is the Cell selection RX level value (dB).

Squal is the Cell selection quality value (dB).

Qoffsettemp is the offset temporarily applied to a cell as specified in TS 38.331 v16.6.0 (dB).

Qrxlevmeas is the Measured cell RX level value (RSRP).

Qqualmeas is the Measured cell quality value (RSRQ).

Qrxlevmin is the minimum required RX level in the cell (dBm). If the UE supports supplementary uplink (SUL) frequency for this cell, Qrxlevmin is obtained from q-RxLevMinSUL, if present, in SIB1 , SIB2 and SIB4, additionally, if QrxlevminoffsetcellSUL is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum receive (RX) level in the concerned cell. Else, Qrxlevmin is obtained from q-RxLevMin in SIB1 , SIB2 and SIB4, additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell.

Qqualmin is the minimum required quality level in the cell (dB). Additionally, if Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell.

Qrxlevminoffset is the offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN, as specified in TS 23.122 17.4.0.

Qqualminoffset is the offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority Public Land Mobile Network (PLMN) while camped normally in a visited PLMN (VPLMN), as specified in TS 23.122 17.4.0.

Pcompensation is calculated as follows. For FR2, Pcompensation is set to 0. For FR1 , if the UE supports the additionalPmax in the NR-NS-PmaxList, if present, in SIB1 , SIB2 and SIB4: max(PEMAX1 -PPowerClass, 0) - (min(PEMAX2, PPowerClass) - min(PEMAX1 , PPowerClass)) (dB); else: max(PEMAX1 -PPowerClass, 0) (dB).

PEMAX1 , PEMAX2 is the maximum TX power level a UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in TS 38.101 16.9.0. If UE supports SUL frequency for this cell, PEMAXI and PEMAX2 are obtained from the p-Max for SUL in SIB1 and NR-NS- PmaxList for SUL respectively in SIB1, SIB2 and SIB4 as specified in TS 38.331 , else PEMAXI and PEMAX2 are obtained from the p-Max and NR-NS-PmaxList respectively in SIB1, SIB2 and SIB4 for normal UL as specified in TS 38.331 .

Ppowerciass is the maximum RF output power of the UE (dBm) according to the UE power class as defined in TS 38.101-1.

The signalled values Qrxlevminoffset and Qqualminoffset are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN (TS 23.122). During this periodic search for higher priority PLMN, the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN.

New cell selection criterion

Other embodiments herein, by contrast, define new cell selection criterion based on the proposed cell-measurement signaling including CM-WUS/WUR-SSB.

In one embodiment, WUS-RSRP (WUR-RSRP) can be defined as the linear function of the average power of CM-WUS (WUR-SSB).

In the related embodiment, WUS-RSRQ (WUR-RSRQ) can be defined as the ratio of NxWUS-RSRP(WUR-RSRP) /NR carrier RSSI, where N is the number of resource blocks in the NR carrier RSSI measurement bandwidth.

In one embodiment, cell selection is performed by the UE based on reference signal received power (RSRP) and reference signal received quality (RSRQ) which is measured by the UE using the WUR on e.g., CM-WUS or WUR-SSB. The legacy equations as outlined above could be re-used with RSRP an RSRQ values measured by WUR instead. Possibly some modification can be required, or the legacy equations are reused as-is but applying new WUR specific values for some parameters, e.g., Qrxievmin and Q _qU aimin .

In one embodiment, a UE configured to monitor paging with WUR (e.g., by the Access and Mobility Function (AMF) over non-access stratum, NAS, signaling) only considers, or prioritizes, cells which support WUR for the cell selection. That a cell supports WUR could be determined from the broadcast of CM-WUS/WUR-SSB (or WUR-sync) in the cell, i.e., a WUR UE would only consider a cell supporting WUR as a ‘suitable cell’. Further, the prioritization mentioned above could be implemented by the UE first performing the cell selection procedure considering only cells that support WUR, and if that fails fallback to legacy cell selection and camping without using the WUR to monitor for paging. Alternatively, a configurable offset for RSRP or RSRQ could be introduced for cells supporting WUR such that they are prioritized by WUR enables UEs. For example, if the UE supports WUR, the UE performs cell selection with PoffsetwuR. If the selected cell supports WUR, the UE uses WUR for monitoring paging and other Idle mode procedures. Else, the UE monitors paging and other Idle mode procedures with its main receiver.

The offset could for example be used in the legacy equation for cell selection in the following way:

SrxleV — Qrxlevmeas ^— (Qrxlevmin + Qrxlevminoffset ) ^— P compensation - QoffSettem + P offsetWUR

Squal — Qqualmeas ^— (Qqualmin + Qqualminoffset) - QoffSettemp + P offsetWUR

Note that although some embodiments herein have been described in a context where the first communication node 12 uses a wake-up receiver 12W for receiving the signal(s) and/or channel(s) 16, embodiments herein are not limited to that case. In other embodiments, for example, the first communication node 12 may use any receiver for receiving the signal(s) and/or channel(s) 16, e.g., the first communication node 12 may use receiver 12R for receiving both the signal(s) and/or channel(s) 16 and the wake-up signal 20. In these and other embodiments, the signal(s) and/or channel(s) 16 and the wake-up signal 20 may be transmitted on the same frequency, or in the same frequency range, to avoid or minimize frequency re-tuning. Note also that although embodiments may be applied for a New Radio (NR) network, embodiments herein may be equally applicable to Long Term Evolution (LTE) (e.g. Narrowband Internet of Things, NB-loT, or LTE for Machines, LTE-M), or any 6G network.

Some embodiments herein are applicable in the following context. In some embodiments, receiver 12R is a baseband receiver and/or a receiver that consumes higher power than wake-up receiver 12W. The wake-up receiver 12W wakes up receiver 12R to detect an incoming message, e.g., a paging message such as a message on PDCCH in paging occasions or a message scheduling the paging message on the Physical Downlink Shared Channel (PDSCH). One benefit of this is lower energy consumption and longer device battery life, or at a fixed energy consumption the downlink latency can be reduced (shorter DRX/duty-cycles and more frequent checks for incoming transmissions).

Some embodiments for example are applicable to or based on a Rel-15 WUS, e.g., as specified for Narrowband Internet of Things (NB-loT) and LTE-M. One motivation is energy consumption reduction since with coverage enhancement PDCCH may be repeated many times and the WUS is relatively shorter and hence requires less reception time. In this case, the wake-up receiver 12W checks for a WUS a certain time before the first communication node’s paging occasion (PO). Only if a WUS is detected, the first communication node 12 continues to check for PDCCH in the PO. And if not, which is most of the time, the first communication node 12 can go back to a sleep state to conserve energy. Due to the coverage enhancements, the WUS can be of variable length depending on the first communication node’s coverage. Figure 2 shows one example in this regard. In such a case, a wake-up signal occasion 30 as used herein may span the configured maximum wake-up signal duration 32. In one such embodiment shown, there may be a gap 36 in time between the end of the maximum WUS duration 32 and the next PO 34.

In these and other embodiments the wake-up signal 20 may be based on the transmission of a short signal that indicates to the first communication node 12 that it should continue to decode a downlink control channel, e.g., full Narrowband PDCCH, NPDCCH, for NB-loT. If such signal is absent (discontinuous transmission, DTX, i.e., the first communication node 12 does not detect it) then the first communication node 12 can go back to sleep without decoding the downlink control channel. The decoding time for the wake-up signal 20 may be considerably shorter than that of the full Narrowband PDCCH (NPDCCH) since it essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces power consumption and leads to longer battery life. The wake-up signal 20 in some embodiments is transmitted only when there is paging for the first communication node 12. But if there is no paging for the first communication node 12 then the wake-up signal 20 will not be transmitted (i.e., implying a discontinuous transmission, DTX) and the first communication node 12 would go back to sleep, e.g., upon detecting DTX instead of the wake-up signal 20.

In some embodiments, though, the wake-up signal 20 is not PDCCH-based. Rather, the wake-up signal 20 is designed for reception by a simpler and low power receiver, i.e., wake-up receiver 12W. The wake-up signal 20 may for example be based on on-off keying (OOK) modulation and non-coherent detection. Similarly, the signal(s) and/or channel(s) 16 may be based on on-off keying (OOK) modulation and non-coherent detection.

Generally, some embodiments herein enable a UE to avoid using its main baseband receiver for cell measurements and/or other idle/inactive mode procedures. Some embodiments may thereby enable a UE to use only the WUR (not its main receiver) unless and until there is any data activity (i.e., uplink transmission triggered, or the UE is paged). This would ensure that for use cases with infrequent traffic, which is the case for many loT applications, the UE only needs to use the WUR for the majority of the time, and only turn on the main receiver in the relatively rare/infrequent events of user-plane data transmission. Some embodiments enable this by enabling a UE to perform cell measurements for cell selection, cell-reselection, etc. using only WUR.

Some embodiments for example describe a new signal (e.g., WUR-SSB or CM-WUS), which enables the UE to perform Idle/inactive mode procedures such as monitoring of paging, checking for System Information (SI) update, cell measurements cell (re-)selection, etc., using only the UE’s WUR.

Certain embodiments may provide one or more of the following technical advantage(s). WUR is about reducing the UE energy consumption, but if the main receiver is still needed for all other Idle mode procedures than synchronization, then a large part of the gain is lost. Some embodiments enable the UE to always only use the low power WUR unless there is user-plane data transmission (i.e., an access attempt and connection establishment). By enabling the UE to avoid starting up its main receiver for doing cell measurements, some embodiments improve the UE energy reduction gain from using WUR.

In view of the modifications and variations herein, Figure 8 depicts a method performed by a communication node, such as the first communication node 12 in Figure 1 , in accordance with particular embodiments. The method includes receiving one or more signals and/or one or more channels 16, e.g., with a wake-up receiver 12W (Block 800).

In some embodiments, the method further comprises performing one or more signal measurements on the one or more signals 16 received (Block 810). In this case, the method may also comprise performing cell selection or cell reselection based on the one or more signal measurements (Block 820). In some embodiments, receiving the one or more signals and/or one or more channels 16 comprises receiving the one or more signals and/or one or more channels 16 with a wake-up receiver 12W.

In some embodiments, receiving the one or more signals and/or one or more channels 16 comprises receiving the one or more signals and/or one or more channels 16 while the communication node 12 is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

In some embodiments, the method also comprises performing one or more actions based on the one or more signals and/or one or more channels 16 received. In some embodiments, receiving one or more signals and/or one or more channels 16 comprises receiving one or more signals 16. In some embodiments, performing one or more actions comprises performing one or more signal measurements on the one or more signals 16 received. In some embodiments, performing one or more actions comprises performing cell selection or cell reselection based on the one or more signal measurements. In some embodiments, receiving the one or more signals 16 comprises receiving the one or more signals 16 with a wake-up receiver 12W, and performing cell selection or cell reselection comprises, based on receiving the one or more signals 16 with the wake-up receiver 12W, applying one or more wake-up receiver 12W specific offsets to one or more results of the one or more signal measurements and performing cell selection or cell reselection based on the one or more results as offset by the one or more wake-up receiver 12W specific offsets. In some embodiments, receiving the one or more signals 16 comprises receiving the one or more signals 16 with a wake-up receiver 12W, and performing cell selection or cell reselection comprises prioritizing, or limiting selection or reselection to, cells that support reception of the one or more signals 16 with a wake-up receiver 12W. In some embodiments, performing one or more actions comprises monitoring for a paging message, and/or checking for an update of System Information, based on the one or more signals and/or one or more channels 16 received.

In some embodiments, the one or more signals and/or one or more channels 16 are specific for an RRC idle mode or an RRC inactive mode.

In some embodiments, the one or more signals and/or one or more channels 16 are specific for reception by a wake-up receiver 12W.

In some embodiments, receiving one or more signals and/or one or more channels 16 comprises receiving the one or more signals 16. In some embodiments, the one or more signals 16 include a cell measurement wake-up signal, CM-WUS. In some embodiments, the CM-WUS is a wake-up signal 20 transmitted for cell measurement purposes. In some embodiments, the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots. In some embodiments, the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences. In some embodiments, one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair. In some embodiments, the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and a wake-up signal 20 is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences. In some embodiments, the CM-WUS is generated from a single binary sequence. In some embodiments, the CM-WUS is a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS). In some embodiments, a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is received indicates that the CM-WUS is a CM-WUS.

In some embodiments, receiving one or more signals and/or one or more channels 16 comprises receiving the one or more signals and/or the one or more channels 16 as part of a synchronization signal block, SSB. In some embodiments, the one or more signals 16 include a Primary Synchronization Signal and/or a Secondary Synchronization Signal. In some embodiments, the SSB lacks a Physical Broadcast Channel. In some embodiments, the one or more signals 16 include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time. In some embodiments, the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB. In some embodiments, the MIB lacks a synchronization signal block time index field. In other embodiments, the MIB alternatively or additionally lacks a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field. In yet other embodiments, the MIB alternatively or additionally lacks a System Information Block #1 , SIB1 , numerology field. In still yet other embodiments, the MIB alternatively or additionally lacks a SIB1 configuration field. In still yet other embodiments, the MIB alternatively or additionally lacks a common resource block, CRB, grid offset field. In still yet other embodiments, the MIB alternatively or additionally lacks a half-frame bit field. In some embodiments, the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check. In some embodiments, the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols. In some embodiments, the SSB is received with a subcarrier spacing less than 15 kHz. In some embodiments, the SSB recurs with a period greater than 160ms. In some embodiments, a granularity of a synchronization raster for the SSB is greater than 1.2 MHz. In some embodiments, frequency locations of the SSB are not on a synchronization raster.

In some embodiments, receiving the one or more signals and/or one or more channels 16 comprises receiving the one or more signals and/or one or more channels 16 with a wake-up receiver 12W. In some embodiments, the method further comprises receiving a wake-up signal 20 with the wake-up receiver 12W, and based on receiving the wake-up signal 20, waking up one or more components of another receiver 12R of the communication node 12. In some embodiments, the communication node 12 is a wireless communication device configured for use in a wireless communication network 10.

In some embodiments, the communication node 12 is a network node in a wireless communication network 10.

In some embodiments, the one or more channels 16 include a Physical Broadcast Channel.

In some embodiments, receiving the one or more signals and/or the one or more channels 16 as part of the SSB comprises receiving the one or more signals and/or the one or more channels 16 as part of a first SSB specific to an RRC idle mode or an RRC inactive mode. In some embodiments, the first SSB is different than, and/or is received in different radio resources than, a second SSB that is specific to an RRC connected mode. In some embodiments, the first SSB conveys less System Information than the second SSB, or the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

In some embodiments, the method further comprises providing user data, and forwarding the user data to a host computer via the transmission to a base station.

Figure 9 depicts a method performed by a communication node, such as the second communication node 14 in Figure 1 , in accordance with other particular embodiments. The method includes transmitting one or more signals and/or one or more channels 16, e.g., to a communication node 12 equipped with a wake-up receiver 12W (Block 900).

In some embodiments, the method also comprises transmitting a wake-up signal 20, e.g., to the first communication node 12 (Block 910).

In some embodiments, transmitting the one or more signals and/or one or more channels 16 comprises transmitting the one or more signals and/or one or more channels 16 to another communication node 12 equipped with a wake-up receiver 12W.

In some embodiments, transmitting the one or more signals and/or one or more channels 16 comprises transmitting the one or more signals and/or one or more channels 16 to another communication node 12 that is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

In some embodiments, the one or more signals and/or one or more channels 16 are specific for an RRC idle mode or an RRC inactive mode.

In some embodiments, the one or more signals and/or one or more channels 16 are specific for reception by a wake-up receiver 12W.

In some embodiments, transmitting one or more signals and/or one or more channels 16 comprises transmitting the one or more signals 16. In some embodiments, the one or more signals 16 include a cell measurement wake-up signal, CM-WUS. In some embodiments, the CM-WUS is a wake-up signal 20 transmitted for cell measurement purposes. In some embodiments, the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots. In some embodiments, the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences. In some embodiments, one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair. In some embodiments, the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and a wake-up signal 20 is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences. In some embodiments, the CM-WUS is generated from a single binary sequence. In some embodiments, the CM-WUS is a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS). In some embodiments, a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is transmitted indicates that the CM-WUS is a CM-WUS.

In some embodiments, transmitting one or more signals and/or one or more channels 16 comprises transmitting the one or more signals and/or the one or more channels 16 as part of a synchronization signal block, SSB. In some embodiments, the one or more signals 16 include a Primary Synchronization Signal and/or a Secondary Synchronization Signal. In some embodiments, the SSB lacks a Physical Broadcast Channel. In some embodiments, the one or more signals 16 include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time. In some embodiments, the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB. In some embodiments, the MIB lacks a synchronization signal block time index field. In other embodiments, the MIB alternatively or additionally lacks a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field. In yet other embodiments, the MIB alternatively or additionally lacks a System Information Block #1 , SIB1 , numerology field. In still yet other embodiments, the MIB alternatively or additionally lacks a SIB1 configuration field. In still yet other embodiments, the MIB alternatively or additionally lacks a common resource block, CRB, grid offset field. In still yet other embodiments, the MIB alternatively or additionally lacks a half-frame bit field. In some embodiments, the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check. In some embodiments, the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols. In some embodiments, the SSB is transmitting with a subcarrier spacing less than 15 kHz. In some embodiments, the SSB recurs with a period greater than 160ms. In some embodiments, a granularity of a synchronization raster for the SSB is greater than 1.2 MHz. In some embodiments, frequency locations of the SSB are not on a synchronization raster.

In some embodiments, the communication node 14 is a wireless communication device configured for use in a wireless communication network 10. In some embodiments, the communication node 14 is a network node in a wireless communication network 10.

In some embodiments, the one or more channels 16 include a Physical Broadcast Channel.

In some embodiments, transmitting the one or more signals and/or the one or more channels 16 as part of the SSB comprises transmitting the one or more signals and/or the one or more channels 16 as part of a first SSB specific to an RRC idle mode or an RRC inactive mode. In some embodiments, the first SSB is different than, and/or is transmitted in different radio resources than, a second SSB that is specific to an RRC connected mode. In some embodiments, the first SSB conveys less System Information than the second SSB, or the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

In some embodiments, the method further comprises obtaining user data, and forwarding the user data to a host computer or a wireless communication device.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a first communication node 12 configured to perform any of the steps of any of the embodiments described above for the first communication node 12.

Embodiments also include a first communication node 12 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the first communication node 12. The power supply circuitry is configured to supply power to the first communication node 12.

Embodiments further include a first communication node 12 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the first communication node 12. In some embodiments, the first communication node 12 further comprises communication circuitry.

Embodiments further include a first communication node 12 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the first communication node 12 is configured to perform any of the steps of any of the embodiments described above for the first communication node 12.

Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the first communication node 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiments herein also include a second communication node 14 configured to perform any of the steps of any of the embodiments described above for the second communication node 14.

Embodiments also include a second communication node 14 comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the second communication node 14. The power supply circuitry is configured to supply power to the second communication node 14.

Embodiments further include a second communication node 14 comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the second communication node 14. In some embodiments, the second communication node 14 further comprises communication circuitry.

Embodiments further include a second communication node 14 comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the second communication node 14 is configured to perform any of the steps of any of the embodiments described above for the second communication node 14.

More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 10 for example illustrates a first communication node 12 as implemented in accordance with one or more embodiments. As shown, the first communication node 12 includes processing circuitry 1010 and communication circuitry 1020. The communication circuitry 1020 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless communication device 1000. The processing circuitry 1010 is configured to perform processing described above, e.g., in Figure 8, such as by executing instructions stored in memory 1030. The processing circuitry 1010 in this regard may implement certain functional means, units, or modules.

Figure 11 illustrates a second communication node 14 as implemented in accordance with one or more embodiments. As shown, the second communication node 14 includes processing circuitry 1110 and communication circuitry 1120. The communication circuitry 1120 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry 1110 is configured to perform processing described above, e.g., in Figure 9, such as by executing instructions stored in memory 1130. The processing circuitry 1110 in this regard may implement certain functional means, units, or modules.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Figure 12 shows an example of a communication system 1200 in accordance with some embodiments.

In the example, the communication system 1200 includes a telecommunication network 1202 that includes an access network 1204, such as a radio access network (RAN), and a core network 1206, which includes one or more core network nodes 1208. The access network 1204 includes one or more access network nodes, such as network nodes 1210a and 1210b (one or more of which may be generally referred to as network nodes 1210), or any other similar 3 ^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1210 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1212a, 1212b, 1212c, and 1212d (one or more of which may be generally referred to as UEs 1212) to the core network 1206 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1200 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1200 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 1212 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1210 and other communication devices. Similarly, the network nodes 1210 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1212 and/or with other network nodes or equipment in the telecommunication network 1202 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1202.

In the depicted example, the core network 1206 connects the network nodes 1210 to one or more hosts, such as host 1216. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1206 includes one more core network nodes (e.g., core network node 1208) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1208. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). The host 1216 may be under the ownership or control of a service provider other than an operator or provider of the access network 1204 and/or the telecommunication network 1202, and may be operated by the service provider or on behalf of the service provider. The host 1216 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system 1200 of Figure 12 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, the telecommunication network 1202 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1202 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1202. For example, the telecommunications network 1202 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

In some examples, the UEs 1212 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1204 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1204. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub 1214 communicates with the access network 1204 to facilitate indirect communication between one or more UEs (e.g., UE 1212c and/or 1212d) and network nodes (e.g., network node 1210b). In some examples, the hub 1214 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1214 may be a broadband router enabling access to the core network 1206 for the UEs. As another example, the hub 1214 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1210, or by executable code, script, process, or other instructions in the hub 1214. As another example, the hub 1214 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1214 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1214 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1214 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1214 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

The hub 1214 may have a constant/persistent or intermittent connection to the network node 1210b. The hub 1214 may also allow for a different communication scheme and/or schedule between the hub 1214 and UEs (e.g., UE 1212c and/or 1212d) , and between the hub 1214 and the core network 1206. In other examples, the hub 1214 is connected to the core network 1206 and/or one or more UEs via a wired connection. Moreover, the hub 1214 may be configured to connect to an M2M service provider over the access network 1204 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1210 while still connected via the hub 1214 via a wired or wireless connection. In some embodiments, the hub 1214 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1210b. In other embodiments, the hub 1214 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1210b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 13 shows a UE 1300 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

The UE 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a power source 1308, a memory 1310, a communication interface 1312, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 1302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1310. The processing circuitry 1302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1302 may include multiple central processing units (CPUs).

In the example, the input/output interface 1306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 1308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1308 may further include power circuitry for delivering power from the power source 1308 itself, and/or an external power source, to the various parts of the UE 1300 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1308. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1308 to make the power suitable for the respective components of the UE 1300 to which power is supplied.

The memory 1310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1310 includes one or more application programs 1314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1316. The memory 1310 may store, for use by the UE 1300, any of a variety of various operating systems or combinations of operating systems.

The memory 1310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1310 may allow the UE 1300 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1310, which may be or comprise a device-readable storage medium. The processing circuitry 1302 may be configured to communicate with an access network or other network using the communication interface 1312. The communication interface 1312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1322. The communication interface 1312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1318 and/or a receiver 1320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1318 and receiver 1320 may be coupled to one or more antennas (e.g., antenna 1322) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 1312 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1312, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1300 shown in Figure 13.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 14 shows a network node 1400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 1400 includes a processing circuitry 1402, a memory 1404, a communication interface 1406, and a power source 1408. The network node 1400 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1400 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1404 for different RATs) and some components may be reused (e.g., a same antenna 1410 may be shared by different RATs). The network node 1400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1400, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1400.

The processing circuitry 1402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1400 components, such as the memory 1404, to provide network node 1400 functionality.

In some embodiments, the processing circuitry 1402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1402 includes one or more of radio frequency (RF) transceiver circuitry 1412 and baseband processing circuitry 1414. In some embodiments, the radio frequency (RF) transceiver circuitry 1412 and the baseband processing circuitry 1414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1412 and baseband processing circuitry 1414 may be on the same chip or set of chips, boards, or units.

The memory 1404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1402. The memory 1404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1402 and utilized by the network node 1400. The memory 1404 may be used to store any calculations made by the processing circuitry 1402 and/or any data received via the communication interface 1406. In some embodiments, the processing circuitry 1402 and memory 1404 is integrated.

The communication interface 1406 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1406 comprises port(s)/terminal(s) 1416 to send and receive data, for example to and from a network over a wired connection. The communication interface 1406 also includes radio front-end circuitry 1418 that may be coupled to, or in certain embodiments a part of, the antenna 1410. Radio front-end circuitry 1418 comprises filters 1420 and amplifiers 1422. The radio front-end circuitry 1418 may be connected to an antenna 1410 and processing circuitry 1402. The radio front-end circuitry may be configured to condition signals communicated between antenna 1410 and processing circuitry 1402. The radio front-end circuitry 1418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1418 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1420 and/or amplifiers 1422. The radio signal may then be transmitted via the antenna 1410. Similarly, when receiving data, the antenna 1410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1418. The digital data may be passed to the processing circuitry 1402. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 1400 does not include separate radio front-end circuitry 1418, instead, the processing circuitry 1402 includes radio front-end circuitry and is connected to the antenna 1410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1412 is part of the communication interface 1406. In still other embodiments, the communication interface 1406 includes one or more ports or terminals 1416, the radio front-end circuitry 1418, and the RF transceiver circuitry 1412, as part of a radio unit (not shown), and the communication interface 1406 communicates with the baseband processing circuitry 1414, which is part of a digital unit (not shown).

The antenna 1410 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1410 may be coupled to the radio front-end circuitry 1418 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1410 is separate from the network node 1400 and connectable to the network node 1400 through an interface or port.

The antenna 1410, communication interface 1406, and/or the processing circuitry 1402 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1410, the communication interface 1406, and/or the processing circuitry 1402 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 1408 provides power to the various components of network node 1400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1400 with power for performing the functionality described herein. For example, the network node 1400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1408. As a further example, the power source 1408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 1400 may include additional components beyond those shown in Figure 14 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1400 may include user interface equipment to allow input of information into the network node 1400 and to allow output of information from the network node 1400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1400.

Figure 15 is a block diagram of a host 1500, which may be an embodiment of the host 1216 of Figure 12, in accordance with various aspects described herein. As used herein, the host 1500 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1500 may provide one or more services to one or more UEs.

The host 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a network interface 1508, a power source 1510, and a memory 1512. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 13 and 14, such that the descriptions thereof are generally applicable to the corresponding components of host 1500.

The memory 1512 may include one or more computer programs including one or more host application programs 1514 and data 1516, which may include user data, e.g., data generated by a UE for the host 1500 or data generated by the host 1500 for a UE. Embodiments of the host 1500 may utilize only a subset or all of the components shown. The host application programs 1514 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1514 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1500 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1514 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 16 is a block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 1602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1604 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs 1608), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.

The VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1608, and that part of hardware 1604 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1608 on top of the hardware 1604 and corresponds to the application 1602.

Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1612 which may alternatively be used for communication between hardware nodes and radio units.

Figure 17 shows a communication diagram of a host 1702 communicating via a network node 1704 with a UE 1706 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1212a of Figure 12 and/or UE 1300 of Figure 13), network node (such as network node 1210a of Figure 12 and/or network node 1400 of Figure 14), and host (such as host 1216 of Figure 12 and/or host 1500 of Figure 15) discussed in the preceding paragraphs will now be described with reference to Figure 17.

Like host 1500, embodiments of host 1702 include hardware, such as a communication interface, processing circuitry, and memory. The host 1702 also includes software, which is stored in or accessible by the host 1702 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1706 connecting via an over-the-top (OTT) connection 1750 extending between the UE 1706 and host 1702. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1750.

The network node 1704 includes hardware enabling it to communicate with the host 1702 and UE 1706. The connection 1760 may be direct or pass through a core network (like core network 1206 of Figure 12) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE 1706 includes hardware and software, which is stored in or accessible by UE 1706 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1706 with the support of the host 1702. In the host 1702, an executing host application may communicate with the executing client application via the OTT connection 1750 terminating at the UE 1706 and host 1702. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1750 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1750.

The OTT connection 1750 may extend via a connection 1760 between the host 1702 and the network node 1704 and via a wireless connection 1770 between the network node 1704 and the UE 1706 to provide the connection between the host 1702 and the UE 1706. The connection 1760 and wireless connection 1770, over which the OTT connection 1750 may be provided, have been drawn abstractly to illustrate the communication between the host 1702 and the UE 1706 via the network node 1704, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection 1750, in step 1708, the host 1702 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1706. In other embodiments, the user data is associated with a UE 1706 that shares data with the host 1702 without explicit human interaction. In step 1710, the host 1702 initiates a transmission carrying the user data towards the UE 1706. The host 1702 may initiate the transmission responsive to a request transmitted by the UE 1706. The request may be caused by human interaction with the UE 1706 or by operation of the client application executing on the UE 1706. The transmission may pass via the network node 1704, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1712, the network node 1704 transmits to the UE 1706 the user data that was carried in the transmission that the host 1702 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1714, the UE 1706 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1706 associated with the host application executed by the host 1702.

In some examples, the UE 1706 executes a client application which provides user data to the host 1702. The user data may be provided in reaction or response to the data received from the host 1702. Accordingly, in step 1716, the UE 1706 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1706. Regardless of the specific manner in which the user data was provided, the UE 1706 initiates, in step 1718, transmission of the user data towards the host 1702 via the network node 1704. In step 1720, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1704 receives user data from the UE 1706 and initiates transmission of the received user data towards the host 1702. In step 1722, the host 1702 receives the user data carried in the transmission initiated by the UE 1706.

One or more of the various embodiments improve the performance of OTT services provided to the UE 1706 using the OTT connection 1750, in which the wireless connection 1770 forms the last segment.

In an example scenario, factory status information may be collected and analyzed by the host 1702. As another example, the host 1702 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1702 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1702 may store surveillance video uploaded by a UE. As another example, the host 1702 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1702 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1750 between the host 1702 and UE 1706, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1702 and/or UE 1706. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1704. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1702. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1750 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Example embodiments of the techniques and apparatus described herein include, but are not limited to, the following enumerated examples: Group A Embodiments

A1 . A method performed by a communication node, the method comprising: receiving one or more signals and/or one or more channels.

A2. The method of embodiment A1 , wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels with a wake-up receiver. A3. The method of any of embodiments A1-A2, wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels while the communication node is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

A4. The method of any of embodiments A1-A3, further comprising performing one or more actions based on the one or more signals and/or one or more channels received.

A5. The method of embodiment A4, wherein receiving one or more signals and/or one or more channels comprises receiving one or more signals, and wherein performing one or more actions comprises: performing one or more signal measurements on the one or more signals received; and performing cell selection or cell reselection based on the one or more signal measurements.

A6. The method of embodiment A5, wherein receiving the one or more signals comprises receiving the one or more signals with a wake-up receiver, and wherein performing cell selection or cell reselection comprises, based on receiving the one or more signals with the wake-up receiver, applying one or more wake-up receiver specific offsets to one or more results of the one or more signal measurements and performing cell selection or cell reselection based on the one or more results as offset by the one or more wake-up receiver specific offsets.

A7. The method of any of embodiments A5-A6, wherein receiving the one or more signals comprises receiving the one or more signals with a wake-up receiver, and wherein performing cell selection or cell reselection comprises prioritizing, or limiting selection or reselection to, cells that support reception of the one or more signals with a wake-up receiver.

A8. The method of any of embodiments A4-A7, wherein performing one or more actions comprises monitoring for a paging message, and/or checking for an update of System Information, based on the one or more signals and/or one or more channels received.

A9. The method of any of embodiments A1-A8, wherein the one or more signals and/or one or more channels are specific for an RRC idle mode or an RRC inactive mode.

A10. The method of any of embodiments A1 -A9, wherein the one or more signals and/or one or more channels are specific for reception by a wake-up receiver. A11 . The method of any of embodiments A1 -A10, wherein receiving one or more signals and/or one or more channels comprises receiving the one or more signals.

A12. The method of embodiment A11 , wherein the one or more signals include a cell measurement wake-up signal, CM-WUS.

A13. The method of embodiment A12, wherein the CM-WUS is a wake-up signal transmitted for cell measurement purposes.

A14. The method of any of embodiments A12-A13, wherein the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots.

A15. The method of embodiment A14, wherein the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences.

A16. The method of any of embodiments A14-A15, wherein one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair.

A17. The method of any of embodiments A14-A16, wherein the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and wherein a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences.

A18. The method of any of embodiments A12-A13, wherein the CM-WUS is generated from a single binary sequence.

A19. The method of any of embodiments A12-A13, wherein the CM-WUS is a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS).

A20. The method of any of embodiments A12-A19, wherein a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is recieved indicates that the CM-WUS is a CM-WUS.

A21. The method of any of embodiments A1-A10, wherein receiving one or more signals and/or one or more channels comprises receiving the one or more signals and/or the one or more channels as part of a synchronization signal block, SSB. A22. The method of embodiment A21 , wherein the one or more signals include a Primary Synchronization Signal and/or a Secondary Synchronization Signal.

A23. The method of any of embodiments A21-A22, wherein the SSB lacks a Physical Broadcast Channel.

A24. The method of embodiment A23, wherein the one or more signals include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time.

A25. The method of any of embodiments A21-A23, wherein the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB.

A26. The method of embodiment A25, wherein the MIB lacks one or more of: a synchronization signal block time index field; a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field; a System Information Block #1 , SIB1 , numerology field; a SIB1 configuration field; a common resource block, CRB, grid offset field; or a half-frame bit field.

A27. The method of any of embodiments A25-A26, wherein the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check.

A28. The method of any of embodiments A21-A27, wherein the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols.

A29. The method of any of embodiments A21-A28, wherein the SSB is received with a subcarrier spacing less than 15 kHz.

A30. The method of any of embodiments A21-A29, wherein the SSB recurs with a period greater than 160ms.

A31 . The method of any of embodiments A21-A30, wherein a granularity of a synchronization raster for the SSB is greater than 1.2 MHz.

A32. The method of any of embodiments A21-A31 , wherein frequency locations of the SSB are not on a synchronization raster.

A33. The method of any of embodiments A1-A32, wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels with a wake-up receiver, wherein the method further comprises: receiving a wake-up signal with the wake-up receiver; and based on receiving the wake-up signal, waking up one or more components of another receiver of the communication node.

A34. The method of any of embodiments A1-A33, wherein the communication node is a wireless communication device configure for use in a wireless communication network.

A35. The method of any of embodiments A1-A33, wherein the communication node is a network node in a wireless communication network.

A36. The method of any of embodiments A1-A35, wherein the one or more channels include a Physical Broadcast Channel.

A37. The method of any of embodiments A21-A32, wherein receiving the one or more signals and/or the one or more channels as part of the SSB comprises receiving the one or more signals and/or the one or more channels as part of a first SSB specific to an RRC idle mode or an RRC inactive mode, wherein the first SSB is different than, and/or is received in different radio resources than, a second SSB that is specific to an RRC connected mode.

A38. The method of embodiment A37, wherein the first SSB conveys less System Information than the second SSB, or wherein the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

AA1 . A method performed by a wireless communication device, the method comprising: receiving, from a networknode, one or more signals and/or one or more channels, wherein: the one or more signals include a signal that is based on a concatenation of a pair of Zadoff-Chu sequences with different roots or that is generated from a single binary sequence; and/or the one or more signals and/or one or more channels are part of a synchronization signal block, SSB, which: is specific to a radio resource control, RRC, idle mode or an RRC inactive mode; lacks a Physical Broadcast Channel, PBCH; or includes a PBCH that carries a Master Information Block, MIB, which lacks one or more of a synchronization signal block time index field, a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field, a System Information Block #1 , SIB1 , numerology field, a SIB1 configuration field, a common resource block, CRB, grid offset field, or a half-frame bit field

AA2. The method of embodiment AA1 , wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels with a wake-up receiver.

AA3. The method of any of embodiments AA1-AA2, wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels while the wireless communication device is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

AA4. The method of any of embodiments AA1-AA3, further comprising performing one or more idle mode procedures based on the one or more signals and/or one or more channels received.

AA5. The method of embodiment AA4, wherein the one or more idle mode procedures include: performing one or more signal measurements on the one or more signals received; and performing cell selection or cell reselection based on the one or more signal measurements.

AA6. The method of embodiment AA5, wherein receiving the one or more signals comprises receiving the one or more signals with a wake-up receiver, and wherein performing cell selection or cell reselection comprises, based on receiving the one or more signals with the wake-up receiver, applying one or more wake-up receiver specific offsets to one or more results of the one or more signal measurements and performing cell selection or cell reselection based on the one or more results as offset by the one or more wake-up receiver specific offsets.

AA7. The method of any of embodiments AA5-AA6, wherein receiving the one or more signals comprises receiving the one or more signals with a wake-up receiver, and wherein performing cell selection or cell reselection comprises prioritizing, or limiting selection or reselection to, cells that support reception of the one or more signals with a wake-up receiver.

AA8. The method of any of embodiments AA4-AA7, wherein the one or more idle mode procedures include checking for an update of System Information, based on the one or more signals and/or one or more channels received.

AA9. The method of any of embodiments AA1-AA8, wherein the one or more signals and/or one or more channels are specific for an RRC idle mode or an RRC inactive mode.

AA10. The method of any of embodiments AA1 -AA9, wherein the one or more signals and/or one or more channels are specific for reception by a wake-up receiver.

AA11 . The method of any of embodiments AA1 -AA10, wherein receiving one or more signals and/or one or more channels comprises receiving the one or more signals.

AA12. The method of embodiment AA11 , wherein the signal is a cell measurement wake-up signal, CM-WUS.

AA13. The method of embodiment AA12, wherein the CM-WUS is a wake-up signal transmitted for cell measurement purposes.

AA14. The method of any of embodiments AA12-AA13, wherein the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots.

AA15. The method of embodiment AA14, wherein the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences.

AA16. The method of any of embodiments AA14-AA15, wherein one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair.

AA17. The method of any of embodiments AA14-AA16, wherein the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and wherein a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences.

AA18. The method of any of embodiments AA12-AA13, wherein the CM-WUS is generated from a single binary sequence.

AA19. The method of any of embodiments AA12-AA13, wherein the CM-WUS is a Primary

Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS).

AA20. The method of any of embodiments AA12-AA19, wherein a first part of the CM- WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is recieved indicates that the CM-WUS is a CM-WUS.

AA21. The method of any of embodiments AA1-AA10, wherein receiving one or more signals and/or one or more channels comprises receiving the one or more signals and/or the one or more channels as part of the SSB.

AA22. The method of embodiment AA21 , wherein the one or more signals include a Primary Synchronization Signal and/or a Secondary Synchronization Signal.

AA23. The method of any of embodiments AA21-AA22, wherein the SSB lacks a Physical Broadcast Channel.

AA24. The method of embodiment AA23, wherein the one or more signals include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time.

AA25. The method of any of embodiments AA21-AA23, wherein the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB.

AA26. The method of embodiment AA25, wherein the MIB lacks one or more of: a synchronization signal block time index field; a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field; a System Information Block #1 , SIB1 , numerology field; a SIB1 configuration field; a common resource block, CRB, grid offset field; or a half-frame bit field.

AA27. The method of any of embodiments AA25-AA26, wherein the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check.

AA28. The method of any of embodiments AA21-AA27, wherein the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols.

AA29. The method of any of embodiments AA21-AA28, wherein the SSB is received with a subcarrier spacing less than 15 kHz.

AA30. The method of any of embodiments AA21-AA29, wherein the SSB recurs with a period greater than 160ms.

AA31 . The method of any of embodiments AA21-AA30, wherein a granularity of a synchronization raster for the SSB is greater than 1.2 MHz.

AA32. The method of any of embodiments AA21-AA31 , wherein frequency locations of the SSB are not on a synchronization raster.

AA33. The method of any of embodiments AA1-AA32, wherein receiving the one or more signals and/or one or more channels comprises receiving the one or more signals and/or one or more channels with a wake-up receiver, wherein the method further comprises: receiving a wake-up signal with the wake-up receiver; and based on receiving the wake-up signal, waking up one or more components of another receiver of the wireless communication device.

AA34. The method of any of embodiments AA1-AA33, wherein the one or more channels include a Physical Broadcast Channel.

AA35. The method of any of embodiments AA21-AA32, wherein receiving the one or more signals and/or the one or more channels as part of the SSB comprises receiving the one or more signals and/or the one or more channels as part of a first SSB specific to an RRC idle mode or an RRC inactive mode, wherein the first SSB is different than, and/or is received in different radio resources than, a second SSB that is specific to an RRC connected mode. AA36. The method of embodiment AA35, wherein the first SSB conveys less System Information than the second SSB, or wherein the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to a base station.

Group B Embodiments

B1 . A method performed by a communication node, the method comprising: transmitting one or more signals and/or one or more channels.

B2. The method of embodiment B1 , wherein transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels to another communication node equipped with a wake-up receiver.

B3. The method of any of embodiments B1-B2, wherein transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels to another communication node that is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

B4-B8. Reserved.

B9. The method of any of embodiments B1-B8, wherein the one or more signals and/or one or more channels are specific for an RRC idle mode or an RRC inactive mode.

B10. The method of any of embodiments B1-B9, wherein the one or more signals and/or one or more channels are specific for reception by a wake-up receiver.

B11. The method of any of embodiments B1-B10, wherein transmitting one or more signals and/or one or more channels comprises transmitting the one or more signals.

B12. The method of embodiment B11 , wherein the one or more signals include a cell measurement wake-up signal, CM-WUS.

B13. The method of embodiment B12, wherein the CM-WUS is a wake-up signal transmitted for cell measurement purposes. B14. The method of any of embodiments B12-B13, wherein the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots.

B15. The method of embodiment B14, wherein the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences.

B16. The method of any of embodiments B14-B15, wherein one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair.

B17. The method of any of embodiments B14-B16, wherein the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and wherein a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences.

B18. The method of any of embodiments B12-B13, wherein the CM-WUS is generated from a single binary sequence.

B19. The method of any of embodiments B12-B13, wherein the CM-WUS is a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS).

B20. The method of any of embodiments B12-B19, wherein a first part of the CM-WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is transmitted indicates that the CM-WUS is a CM-WUS.

B21 . The method of any of embodiments B1-B10, wherein transmitting one or more signals and/or one or more channels comprises transmitting the one or more signals and/or the one or more channels as part of a synchronization signal block, SSB.

B22. The method of embodiment B21 , wherein the one or more signals include a Primary Synchronization Signal and/or a Secondary Synchronization Signal.

B23. The method of any of embodiments B21-B22, wherein the SSB lacks a Physical Broadcast Channel.

B24. The method of embodiment B23, wherein the one or more signals include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time.

B25. The method of any of embodiments B21-B23, wherein the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB.

B26. The method of embodiment B25, wherein the MIB lacks one or more of: a synchronization signal block time index field; a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field; a System Information Block #1 , SIB1 , numerology field; a SIB1 configuration field; a common resource block, CRB, grid offset field; or a half-frame bit field.

B27. The method of any of embodiments B25-B26, wherein the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check.

B28. The method of any of embodiments B21-B27, wherein the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols.

B29. The method of any of embodiments B21-B28, wherein the SSB is transmitting with a subcarrier spacing less than 15 kHz.

B30. The method of any of embodiments B21-B29, wherein the SSB recurs with a period greater than 160ms.

B31 . The method of any of embodiments B21-B30, wherein a granularity of a synchronization raster for the SSB is greater than 1.2 MHz.

B32. The method of any of embodiments B21-B31 , wherein frequency locations of the SSB are not on a synchronization raster.

B33. Reserved

B34. The method of any of embodiments B1-B33, wherein the communication node is a wireless communication device configure for use in a wireless communication network. B35. The method of any of embodiments B1-B33, wherein the communication node is a network node in a wireless communication network.

B36. The method of any of embodiments B1-B35, wherein the one or more channels include a Physical Broadcast Channel.

B37. The method of any of embodiments B21-B32, wherein transmitting the one or more signals and/or the one or more channels as part of the SSB comprises transmitting the one or more signals and/or the one or more channels as part of a first SSB specific to an RRC idle mode or an RRC inactive mode, wherein the first SSB is different than, and/or is transmitted in different radio resources than, a second SSB that is specific to an RRC connected mode.

B38. The method of embodiment B37, wherein the first SSB conveys less System Information than the second SSB, or wherein the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

BB1 . A method performed by a network node, the method comprising: transmitting, to a wireless communication device, one or more signals and/or one or more channels, wherein: the one or more signals include a signal that is based on a concatenation of a pair of Zadoff-Chu sequences with different roots or that is generated from a single binary sequence; and/or the one or more signals and/or one or more channels are part of a synchronization signal block, SSB, which: is specific to a radio resource control, RRC, idle mode or an RRC inactive mode; lacks a Physical Broadcast Channel, PBCH; or includes a PBCH that carries a Master Information Block, MIB, which lacks one or more of a synchronization signal block time index field, a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field, a System Information Block #1 , SIB1 , numerology field, a SIB1 configuration field, a common resource block, CRB, grid offset field, or a half-frame bit field

BB2. The method of embodiment BB1 , wherein transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels to a wireless communication device that has a wake-up receiver.

BB3. The method of any of embodiments BB1-BB2, wherein transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels while the wireless communication device is in a Radio Resource Control, RRC, idle mode or an RRC inactive mode.

BB4. The method of any of embodiments BB1-BB3, wherein the one or more signals and/or the one or more channels are usable by the wireless communication device for performing one or more idle mode procedures.

BB5. The method of embodiment BB4, wherein the one or more idle mode procedures include: performing one or more signal measurements on the one or more signals received; and performing cell selection or cell reselection based on the one or more signal measurements.

BB6. The method of embodiment BB5, wherein transmitting the one or more signals comprises transmitting the one or more signals to a wireless communication device that has a wake-up receiver, and wherein one or more wake-up receiver specific offsets are to be applied to one or more results of the one or more signal measurements and cell selection or cell reselection is to be performed based on the one or more results as offset by the one or more wake-up receiver specific offsets.

BB7. Reserved

BB8. The method of any of embodiments BB4-BB7, wherein the one or more idle mode procedures include checking for an update of System Information, based on the one or more signals and/or one or more channels.

BB9. The method of any of embodiments BB1-BB8, wherein the one or more signals and/or one or more channels are specific for an RRC idle mode or an RRC inactive mode.

BB10. The method of any of embodiments BB1-BB9, wherein the one or more signals and/or one or more channels are specific for reception by a wake-up receiver. BB11. The method of any of embodiments BB1-BB10, wherein transmitting one or more signals and/or one or more channels comprises transmitting the one or more signals.

BB12. The method of embodiment BB11 , wherein the signal is a cell measurement wake-up signal, CM-WUS.

BB13. The method of embodiment BB12, wherein the CM-WUS is a wake-up signal transmitted for cell measurement purposes.

BB14. The method of any of embodiments BB12-BB13, wherein the CM-WUS is based on a concatenation of a pair of Zadoff-Chu sequences with different roots.

BB15. The method of embodiment BB14, wherein the CM-WUS is based on a pair of cyclic shifts applied to the pair of Zadoff-Chu sequences.

BB16. The method of any of embodiments BB14-BB15, wherein one Zadoff-Chu sequence in the pair is a complex conjugate of the other one of the Zadoff-Chu sequences in the pair.

BB17. The method of any of embodiments BB14-BB16, wherein the CM-WUS is based on a first cyclic shift of each Zadoff-Chu sequence in a first pair of Zadoff-Chu sequences, and wherein a wake-up signal is based on a second cyclic shift of each Zadoff-Chu sequence in a second pair of Zadoff-Chu sequences.

BB18. The method of any of embodiments BB12-BB13, wherein the CM-WUS is generated from a single binary sequence.

BB19. The method of any of embodiments BB12-BB13, wherein the CM-WUS is a Primary Synchronization Signal (PSS) or a Secondary Synchronization Signal (SSS).

BB20. The method of any of embodiments BB12-BB19, wherein a first part of the CM- WUS, a header encapsulating the CM-WUS, or radio resources on which the CM-WUS is transmitted indicates that the CM-WUS is a CM-WUS.

BB21. The method of any of embodiments BB1-BB10, wherein transmitting one or more signals and/or one or more channels comprises transmitting the one or more signals and/or the one or more channels as part of the SSB. BB22. The method of embodiment BB21 , wherein the one or more signals include a Primary Synchronization Signal and/or a Secondary Synchronization Signal.

BB23. The method of any of embodiments BB21-BB22, wherein the SSB lacks a Physical Broadcast Channel.

BB24. The method of embodiment BB23, wherein the one or more signals include a Primary Synchronization Signal and a Secondary Synchronization Signal in radio resources that are consecutive in time.

BB25. The method of any of embodiments BB21-BB23, wherein the SSB includes a Physical Broadcast Channel that carries a Master Information Block, MIB.

BB26. The method of embodiment BB25, wherein the MIB lacks one or more of: a synchronization signal block time index field; a first Physical Downlink Shared Channel, PDSCH, demodulation reference signal position field; a System Information Block #1 , SIB1 , numerology field; a SIB1 configuration field; a common resource block, CRB, grid offset field; or a half-frame bit field.

BB27. The method of any of embodiments BB25-BB26, wherein the MIB includes only a cell barred flag, an intra-frequency reselection flag, a system frame number field, and/or a cyclic redundancy check.

BB28. The method of any of embodiments BB21-BB27, wherein the SSB spans fewer than 240 subcarriers and/or spans more than 4 symbols.

BB29. The method of any of embodiments BB21-BB28, wherein the SSB is transmitted with a subcarrier spacing less than 15 kHz.

BB30. The method of any of embodiments BB21-BB29, wherein the SSB recurs with a period greater than 160ms.

BB31 . The method of any of embodiments BB21-BB30, wherein a granularity of a synchronization raster for the SSB is greater than 1.2 MHz. BB32. The method of any of embodiments BB21-BB31 , wherein frequency locations of the SSB are not on a synchronization raster.

BB33. The method of any of embodiments BB1-BB32, wherein transmitting the one or more signals and/or one or more channels comprises transmitting the one or more signals and/or one or more channels to a wireless communication device that has a wake-up receiver, wherein the method further comprises transmitting a wake-up signal configured to trigger wake up of one or more components of another receiver of the wireless communication device.

BB34. The method of any of embodiments BB1-BB33, wherein the one or more channels include a Physical Broadcast Channel.

BB35. The method of any of embodiments BB21-BB32, wherein transmitting the one or more signals and/or the one or more channels as part of the SSB comprises transmitting the one or more signals and/or the one or more channels as part of a first SSB specific to an RRC idle mode or an RRC inactive mode, wherein the first SSB is different than, and/or is transmitted in different radio resources than, a second SSB that is specific to an RRC connected mode.

BB36. The method of embodiment BB35, wherein the first SSB conveys less System Information than the second SSB, or wherein the second SSB carries a Physical Broadcast Channel but the first SSB lacks a Physical Broadcast Channel.

BB. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless communication device.

Group C Embodiments

C1 . A communication node configured to perform any of the steps of any of the Group A or Group B embodiments.

C2. A communication node comprising processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments.

C3. A communication node comprising: communication circuitry; and processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments.

C4. A communication node comprising: processing circuitry configured to perform any of the steps of any of the Group A or Group B embodiments; and power supply circuitry configured to supply power to the communication node.

C5. A communication node comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the communication node is configured to perform any of the steps of any of the Group A or Group B embodiments.

C6. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A or Group B embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

C7. A computer program comprising instructions which, when executed by at least one processor of a communication node, causes the communication node to carry out the steps of any of the Group A or Group B embodiments.

C8. A carrier containing the computer program of embodiment C7, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Group D Embodiments

D1 . A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D2. The communication system of the previous embodiment further including the base station.

D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D4. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

D7. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.

D9. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.

D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

D11. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

D14. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

D15. The communication system of the previous embodiment, further including the UE.

D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

D17. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

D18. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

D21. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

D22. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

D23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D24. The communication system of the previous embodiment further including the base station.

D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D26. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.