UE sleep state management with WUR operation

Abstract

Systems and methods are disclosed that relate to Wake-Up Radio / Receiver (WUR) operation. In one embodiment, a method performed by a User Equipment (UE) comprises selecting, from among a set of time offsets, a time offset to use for Wake-Up Signal (WUS) triggered Physical Downlink Control Channel (PDCCH) monitoring. The method further comprises receiving a WUS from a network node and, responsive thereto, performing PDCCH monitoring during a time occasion that is based on the selected time offset. In this manner, a time offset can be selected that provides the optimal trade-off between energy cost and guaranteed latency.

Description

[0001] UE SLEEP STATE MANAGEMENT WITH WUR OPERATION

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of provisional patent application serial number 63 / 605,846, filed December 4, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0004] TECHNICAL FIELD

[0005] The present disclosure relates to a wireless communication system and, more specifically, to Wake-Up Radi o / Recei ver (WUR) operation in a wireless communication system.

[0006] BACKGROUND

[0007] In the 3rdGeneration Partnership Project (3GPP), Wake-Up Receiver / Radio (WUR), alternatively referred to as ‘wake-up radio’, is an ultra-low power and low-complexity receiver which, in case of the detection of a Wake-Up Signal (WUS), wakes up the main receiver (e.g., baseband, Radio Frequency (RF), control processor, external memory, system clock, etc.) to trigger Physical Downlink Control Channel (PDCCH) monitoring. The main receiver / radio can go to sleep mode and save power until it is triggered by WUR. One example is to use WUR for the User Equipment (UE) in Radio Resource Control (RRC) connected (RRC CONNECTED) mode to allow the network to dynamically indicate to the UE to start monitoring PDCCH for incoming downlink (DL) traffic. This is an alternative solution to configuring the UE to apply Discontinuous Reception (DRX) with periodic on-duration time, which cannot cater for aperiodic traffic with varying inter-arrival time and which is thus either energy inefficient or introduces additional delay. Another example is to use WUR for the UE in RRC idle or inactive (RRC IDLE / RRC INACTIVE) mode for paging (i.e., indicating to the UE to start monitoring PDCCH in paging occasions (PO), which schedules the paging message on Physical Downlink Shared Channel (PDSCH)). The main benefit of employing WUR is lowering energy consumption and prolonging 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).

[0008] As an example, Figure 1 shows a dedicated WUR that is used for monitoring a WUS. Having a dedicated WUR means:

[0009] • Extremely low-power, simple, and low-cost receiver architecture, relaxed requirements, noisier (i.e., less accurate) clock or oscillator;

[0010] • Significant power saving gain can be achieved by maximizing the time in which the main receiver can be in the sleep mode; and • There are coverage considerations given the tradeoff between WUR power consumption and sensitivity.

[0011] For RRC CONNECTED mode UEs, the WUS / WUR solution has the potential to replace or complement DRX in RRC CONNECTED (also referred to as C-DRX) in 6thGeneration (6G) for a broad range of traffic assumptions. The essence of the traffic assumption is that the traffic arrival moments cannot be known in advance by the network, such as for aperiodic traffic (e.g., enhanced Mobile Broadband (eMBB)), quasi -periodic traffic with jitter (e.g., Augmented or Virtual Reality (XR) video), or multiple periodic traffic flows (e.g., XR video and audio). If the network does not have any traffic information or knows only the traffic delay budget, it is sufficient to restrict the main receiver (MR) ramp-up time and thus limit the traffic delay down to the minimum, if needed or uncertain, while still saving significant UE power. In contrast, deciding how to configure DRX parameters is not trivial to obtain a good power / delay tradeoff. Specifically, for optimally configuring DRX to achieve low energy consumption while limiting the delay to a minimum, additional traffic knowledge is needed in the network (e.g., periodicity, alignment, and jitter statistics), which may be difficult in practice.

[0012] A UE’s MR can be in different sleep states depending on the number and the duration of hardware circuits that can be configured into power-off or low power mode. More energy can be saved by turning-off more circuits longer but consequently with a longer time to wake the MR up. As shown in Table 1 below, 3GPP Technical Report (TR) 38.840 has listed out three sleep states. Each state offers a trade-off between transition time / energy and power consumption in that state.

[0013] Table 1

[0014] SUMMARY

[0015] Systems and methods are disclosed that relate to Wake-Up Radio / Receiver (WUR) operation. In one embodiment, a method performed by a User Equipment (UE) comprises selecting, from among a set of time offsets, a time offset to use for Wake-Up Signal (WUS) triggered Physical Downlink Control Channel (PDCCH) monitoring. The method further comprises receiving a WUS (e.g., via a WUR of the UE) from a network node and, responsive thereto, performing PDCCH monitoring (e.g., using a main receiver of the UE) during a time occasion that is based on the selected time offset. In this manner, a time offset can be selected that provides the optimal trade-off between energy cost and guaranteed latency.

[0016] In one embodiment, the set of time offsets comprises two or more time offsets.

[0017] In one embodiment, the method further comprises receiving, from the network node, information that configures the UE with the set of time offsets.

[0018] In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication from the network node.

[0019] In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via dynamic signaling.

[0020] In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI).

[0021] In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring is based on an implicit indication from the network node. In one embodiment, the implicit indication comprises one or more conditions or parameters configured by the network, and selecting the time offset to use for WUS triggered PDCCH monitoring comprises selecting the time offset to use for WUS triggered PDCCH monitoring based on the one or more conditions or parameters configured by the network. In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring is based on one or more predefined or configured rules.

[0022] In one embodiment, selecting the time offset to use for WUS triggered PDCCH monitoring comprises selecting a first time offset if a timer has not expired and selecting a second time offset if the timer has expired, the second time offset being greater than the first time offset. In one embodiment, the timer is started or re-started by the UE each time the UE transmits uplink data or receives downlink data.

[0023] In one embodiment, the selected time offset is a time offset between a time at which the UE receives the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0024] In one embodiment, the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., Synchronization Signal Block (SSB) or Tracking Reference Signal (TRS)) after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0025] In one embodiment, the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., SSB or TRS) that occurs a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0026] In one embodiment, the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., SSB or TRS) that occurs at least a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0027] In one embodiment, the UE is configured with two or more sets of time offsets for two or more respective WUS sets, and the set of time offsets from which the selected time offset is selected is one of the two or more sets of time offsets for one of the two or more respective WUS sets monitored by the UE when receiving the WUS from the network node.

[0028] In one embodiment, the method further comprises performing PDCCH monitoring (e.g., using a main receiver of the UE) during one or more additional time occasions that are based on one or more additional time offsets, from among the set of time offsets, that are greater than the selected time offset.

[0029] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE is adapted to select, from among a set of time offsets, a time offset to use for WUS triggered PDCCH monitoring, receive a WUS from a network node, and, responsive to receiving the WUS, perform PDCCH monitoring during a time occasion that is based on the selected time offset. In one embodiment, a UE comprises a communication interface comprising one or more receivers, and processing circuitry associated with the communication interface. The processing circuitry is configured to cause the UE to select, from among a set of time offsets, a time offset to use for WUS triggered PDCCH monitoring, receive a WUS from a network node, and, responsive to receiving the WUS, perform PDCCH monitoring during a time occasion that is based on the selected time offset.

[0030] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node comprises sending, to a UE, an explicit or implicit indication of a time offset from the set of time offsets to be used by the UE for WUS triggered PDCCH monitoring.

[0031] In one embodiment, the method further comprises configuring the UE with the set of time offsets for WUS triggered PDCCH monitoring.

[0032] In one embodiment, the set of time offsets comprises two or more time offsets.

[0033] In one embodiment, sending the explicit or implicit indication comprises sending, to the UE via dynamic signaling, an explicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring. In one embodiment, the dynamic signaling is a MAC CE or DCI.

[0034] In one embodiment, sending the explicit or implicit indication comprises sending, to the UE, an implicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring. In one embodiment, the implicit indication comprises one or more conditions or parameters.

[0035] In one embodiment, the method further comprises configuring the UE with two or more different sets of WUSs having different sets of time offsets.

[0036] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for a cellular communications network is adapted to sending, to a UE, an explicit or implicit indication of a time offset from the set of time offsets to be used by the UE for WUS triggered PDCCH monitoring.

[0037] In one embodiment, a network node for a cellular communications network comprises processing circuitry configured to cause the network node to send, to a UE, an explicit or implicit indication of a time offset from the set of time offsets to be used by the UE for WUS triggered PDCCH monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0039] Figure 1 illustrates a User Equipment (UE) including a dedicated wake-up radio accompanying the main receiver;

[0040] Figure 2 is a flow chart that illustrates the operation of a UE in accordance with embodiments of the present disclosure;

[0041] Figure 3 is a flow chart that illustrates the operation of a network node in accordance with embodiments of the present disclosure;

[0042] Figure 4 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0043] Figure 5 shows a UE in accordance with some embodiments of the present disclosure;

[0044] Figure 6 shows a network node in accordance with some embodiments of the present disclosure; and

[0045] Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

[0046] DETAILED DESCRIPTION

[0047] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0048] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0049] There currently exist certain challenge(s) with respect to Wake-Up Receiver / Radio (WUR) / Wake-Up Signal (WUS) in a 3rdGeneration Partnership Project (3GPP) network, e.g., a New Radio (NR) or 6thGeneration (6G) network. If the User Equipment (UE) knows in advance when it must wake up the Main Receiver / Radio (MR), then the UE can choose on its own what sleep states to enter with the objective, e.g., to minimize the total energy cost. For example, • if the next time to wake up is far ahead in the future, then the UE can choose to enter deep sleep state with lower power consumption and longer wake up time;

[0050] • if the next time to wake up is very close in time, then the UE can choose to enter micro sleep instead.

[0051] With Discontinuous Reception (DRX) configured, the UE knows precisely when the next on-duration starts and so the UE also knows when the UE’s MR shall be up. In the case of a UE equipped with WUS / WUR, the moment to wake up the MR and start monitoring Physical Downlink Control Channel (PDCCH) is upon the reception of WUS from the network and so is unknown beforehand.

[0052] One solution is to configure a time offset and the MR must be woken up to monitor PDCCH within this time offset after receiving the WUS. But this solution of a single time offset cannot adapt well to the heterogenous nature of traffic for the UE. The issue is that:

[0053] • If the time offset is set to be too long, then it may take long time for UE to wake up, which leads to either the latency guarantee not being met or UE’s MR rarely going to sleep state;

[0054] • If the time offset is set to be too short, then the energy saving gain may be small.

[0055] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The network indicates to a UE one or more time offsets, out of which one time offset is selected at a time, to determine the start of PDCCH monitoring (using MR), after receiving the WUS. This enables the UE to go to different sleep states. The indication can be implicit in which the network configures conditions related with configurable timers / counters. The indication can be explicit but, e.g., more dynamic than Radio Resource Control (RRC) configuration, e.g., Medium Access Control (MAC) Control Element (CE) or Downlink Control Information (DCI).

[0056] Certain embodiments may provide one or more of the following technical advantage(s). Using embodiments of the present disclosure, an optimal trade-off between energy cost and latency guaranteed can be obtained, e.g., the energy cost is minimized while the delay of the packets meets the requirement.

[0057] Now, a more detailed description of embodiments of the present disclosure will be provided. In one embodiment, at least two different time offsets are configured at the UE. The time offset is a duration of time starting at a time at which a WUS is received by the UE and ending at time at which the UE starts to monitor PDCCH. For each configured and actively used time offset at the UE, the UE monitors PDCCH starting at the time offset after receiving the WUS. In other words, the time offset is the maximum ramp-up time for UE’s MR. The actual sleep state, ramp-up time, etc., are up to UE implementation. In one embodiment, a short time offset is used by the UE as default and an additional timer is used to determine if a long offset time is used instead. More specifically, in one example embodiment, a first time offset is used by the UE as a default. The UE starts or re-starts the timer whenever there is an uplink (UL) and / or downlink (DL) data transmission from / to the UE. Upon expiry of the timer, the UE uses a second time offset, wherein the second time offset is greater than the first time offset.

[0058] In another embodiment, if the UE has entered a state in which synchronization between the UE and the network node (e.g., a base station such as, e.g., a gNodeB (gNB)) is lost, the time offset is counted from the first occasion of Synchronization Signal Block (SSB) / Tracking Reference Signal (TRS) reception after the reception of the WUS. In one related embodiment, SSB / TRS are additional reference signals transmitted from the network node for the UE to perform synchronization for waking up the MR. For example, the network configures the UE such that the UE knows that, whenever there is a WUS transmitted from the network, there is a TRS transmitted from the network node to the UE x time slots later in a frequency position y to enable the UE to perform synchronization.

[0059] Suppose there are two types of waking up actions at the UE, one that can only start after the presence of a sync signal, and another that is not. Denote the needed time of the first action as t_a, and the needed time of the second action as t_b. Suppose that the UE can only wake up one component at a time.

[0060] In one follow-up embodiment, the time offset is counted from the first occasion of SSB / TRS reception that occurs a fixed time (e.g., t_b) after the reception of the WUS. In one alternative embodiment, after reception of the WUS if the sync signal is transmitted within t_a, the UE shall wake up the MR t_a+t_b time offset after reception of the WUS; after reception of the WUS if the sync signal is transmitted after t_a, the UE shall wake up the MR t_b time offset after reception of the sync signal.

[0061] In another embodiment, the UE may be configured with different sets of WUS signals to monitor, with different time offsets to PDCCH monitoring. The UE may then explicitly or implicitly switch between which sets to monitor. As an example, an additional temporary set of WUS signals may be assigned for a restricted period of time using a MAC control element.

[0062] In one embodiment, the UE is configured with multiple time offsets, and the UE determines which of the multiple time offsets to use based on an explicit or implicit indication (e.g., from the network node). The time offset to be used by the UE may change over time based on new explicit or implicit indications received from the network. In one embodiment, the UE monitors PDCCH after the determined time offset and also at time occasions related to all of the configured time offsets that are longer than the determined time offset. This protects the system from state errors since the transmitter may always fall back to the longest offset. In an extension to this embodiment, the UE may only have to monitor PDCCH in a later occasion if no Downlink Control Information (DCI) was received in any of the earlier occasions.

[0063] In one embodiment, the time offset for the next time when the MR is on is indicated in the WUS payload based on learning or traffic pattern summary. Therefore, the network node (e.g., base station such as, e.g., gNB) can send PDCCH according to the pre-configured time offset between WUS reception and PDCCH monitoring.

[0064] In one embodiment, the network indicates to the UE explicitly (e.g., in a DCI or MAC CE) a time offset to be applied temporarily, or semi -persistently, after the next WUS or set of next WUSs. This is useful in case the network expects that the next traffic for the UE has a longer / shorter delay requirement, e.g. in case there are multiple traffic flows for the UE that are interleaved in time and have different delay requirements.

[0065] In one embodiment, the network pre-configures the UE with multiple time offsets, and there are (e.g., predefined or configured) rules for the UE to implicitly select a time offset (from among the pre-configured time offsets) depending on UE activity and / or configuration for uplink traffic. In one example, if the UE is configured with periodic configured grant (CG) for uplink traffic, the UE implicitly selects a short offset before / after every CG occasion. This can be meaningful since the MR has to wake up for sending uplink traffic anyway, so it can also start monitoring PDCCH for the downlink faster after a WUS. The time before / after the CG occasion may be configurable and indicated by the network as another type of offset before / after the CG occasion, or as a timer duration after the CG occasion.

[0066] Figure 2 is a flow chart that illustrates the operation of a UE in accordance with at least some of the embodiments described above. Optional steps are represented by dashed boxes. Note that while not all details from the description above are repeated here in the description of Figure 2, it is to be understood that the details above are applicable to the corresponding steps of Figure 2. As illustrated, the UE optionally (i.e., in some embodiments) receives, from a network node (e.g., a base station such as, e.g., a gNB), information that configures the UE with a set of time offsets for WUS triggered PDCCH monitoring (step 200). The set of time offsets preferably includes two or more time offsets. The UE selects a time offset from the set of time offsets (e.g., the configured set of time offsets from step 200 or a predefined or otherwise configured set of time offsets) to be used by the UE for WUS triggered PDCCH monitoring (step 202). Details regarding various embodiments of the selection of the time offset are described above and are equally applicable here. In one embodiment, the UE selects the time offset based on an explicit indication received from the network (e.g., from the network node), e.g., via dynamic signaling such as, for example, MAC CE or DCI. In another embodiment, the UE selects the time offset based on an implicit indication received from the network (e.g., from the network node) such as, e.g., one or more conditions or one or more parameters that implicit indicate which time offset from the set of time offsets is to be selected by the UE. In one embodiment, the UE selects the time offset based on one or more rules and / or one or more timers. For example, as described above, in one embodiment, the UE selects a first time offset if a timer has not expired and selects a second time offset if the timer has expired, where the second time offset is greater than the first time offset. The timer is started or re-started by the UE each time of the transmits UL data and / or receives DL data. The initial value of the timer may be predefined or configured (e.g., configured by the network node).

[0067] Optionally, the UE selects a sleep state (e.g., from a predefined set of different sleep states) based on the selected time offset and causes the main receiver of the UE to enter or operate in the selected sleep state (step 204).

[0068] The UE receives a WUS (e.g., from the network node) (step 206). Responsive to receiving the WUS, the UE performs PDCCH monitoring (e.g., using the main receiver of the UE) during a time occasion that is based on the selected time offset (step 208). For example, in one embodiment, the time occasion in which the UE performs PDCCH monitoring starts at a time equal to a predefined or configured reference time plus the selected time offset. The reference time is related to the time at which the UE received the WUS in step 206. For example, in one embodiment, the reference time is the time at which the UE received the WUS in step 206. In another embodiment, the reference time is a time of a first sync signal (e.g., SSB or TRS) reception occasion after reception of the WUS in step 206. In another embodiment, the reference time is a time of a first sync signal (e.g., SSB or TRS) reception occasion after a fixed amount of time after reception of the WUS in step 206.

[0069] Note that, in some embodiments, the UE may further perform PDCCH monitoring (e.g., using a main receiver of the UE) during one or more additional time occasions that are based on one or more additional time offsets, from among the set of time offsets that are greater than the selected time offset, as described above.

[0070] In one embodiment, the UE is configured (e.g., in step 200) with two or more sets of time offsets for two or more different sets of WUSs for which the UE is to monitor. The UE may perform the process of Figure 2 for each set of WUSs using the corresponding configured set of time offsets. Figure 3 is a flow chart that illustrates the operation of a network node (e.g., a base station such as, e.g., a gNB) in accordance with at least some of the embodiments described above. Optional steps are represented by dashed boxes. Note that while not all details from the description above are repeated here in the description of Figure 3, it is to be understood that the details above are applicable to the corresponding steps of Figure 3. As illustrated, the network node optionally (i.e., in some embodiments) sends, to a UE, information that configures the UE with a set of time offsets for WUS triggered PDCCH monitoring (step 300). The set of time offsets preferably includes two or more time offsets. The network node sends, to the UE, an explicit or implicit indication that indicates a time offset(s) from the set of time offsets (e.g., the configured set of time offsets from step 300 or a predefined or otherwise configured set of time offsets) to be used by the UE for WUS triggered PDCCH monitoring (step 302). Details regarding various embodiments of the implicit or explicit indication are described above and such details are equally applicable here.

[0071] Figure 4 shows an example of a communication system 400 in accordance with some embodiments.

[0072] In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a Radio Access Network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410A and 410B (one or more of which may be generally referred to as network nodes 410), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 402 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 402 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 402, including one or more network nodes 410 and / or core network nodes 408.

[0073] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 410 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 412A, 412B, 412C, and 412D (one or more of which may be generally referred to as UEs 412) to the core network 406 over one or more wireless connections.

[0074] 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 400 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 400 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0075] The UEs 412 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 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 412 and / or with other network nodes or equipment in the telecommunication network 402 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 402.

[0076] In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408. 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).

[0077] The host 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and / or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 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.

[0078] As a whole, the communication system 400 of Figure 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 400 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 Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0079] In some examples, the telecommunication network 402 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunication network 402 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) / massive Internet of Things (loT) services to yet further UEs.

[0080] In some examples, the UEs 412 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 404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 404. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi -standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0081] In the example, a hub 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412C and / or 412D) and network nodes (e.g., network node 410B). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 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 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 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 414 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 414 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0082] The hub 414 may have a constant / persistent or intermittent connection to the network node 410B. The hub 414 may also allow for a different communication scheme and / or schedule between the hub 414 and UEs (e.g., UE 412C and / or 412D), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and / or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 404 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 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 410B. In other embodiments, the hub 414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 41 OB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0083] Figure 5 shows a UE 500 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0084] 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).

[0085] The UE 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 5. 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.

[0086] The processing circuitry 502 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 510. The processing circuitry 502 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 502 may include multiple Central Processing Units (CPUs).

[0087] In the example, the input / output interface 506 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 500. 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.

[0088] In some embodiments, the power source 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied.

[0089] The memory 510 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems.

[0090] The memory 510 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium.

[0091] The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 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 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., the antenna 522) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0092] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0093] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 512, 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).

[0094] 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.

[0095] A UE, when in the form of an 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 television, 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 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 500 shown in Figure 5. 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 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0096] 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.

[0097] Figure 6 shows a network node 600 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR. Node Bs (gNBs)), and 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).

[0098] 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, distributed units (e.g., in an 0-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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).

[0099] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSRBSs, network controllers such as Radio Network Controllers (RNCs) or BS 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).

[0100] The network node 600 includes processing circuitry 602, memory 604, a communication interface 606, and a power source 608. The network node 600 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 600 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 600 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (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 the network node 600.

[0101] The processing circuitry 602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 600 components, such as the memory 604, to provide network node 600 functionality.

[0102] In some embodiments, the processing circuitry 602 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of Radio Frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 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 the RF transceiver circuitry 612 and the baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units. The memory 604 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, RAM, 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 602. The memory 604 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 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and the memory 604 are integrated.

[0103] The communication interface 606 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 606 comprises port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. The radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 may be configured to condition signals communicated between the antenna 610 and the processing circuitry 602. The radio front-end circuitry 618 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 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 620 and / or the amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface 606 may comprise different components and / or different combinations of components.

[0104] In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618; instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes the one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612 as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

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

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

[0107] The power source 608 provides power to the various components of the network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 608. As a further example, the power source 608 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.

[0108] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0109] Figure 7 is a block diagram illustrating a virtualization environment 700 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 700 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. In some embodiments, the virtualization environment 700 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

[0111] Hardware 704 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 706 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 708A and 708B (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

[0112] The VMs 708 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of the VMs 708, 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.

[0113] In the context of NFV, a VM 708 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 708, and that part of the hardware 704 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 708, 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 708 on top of the hardware 704 and corresponds to the application 702.

[0114] The hardware 704 may be implemented in a standalone network node with generic or specific components. The hardware 704 may implement some functions via virtualization. Alternatively, the hardware 704 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 710, which, among others, oversees lifecycle management of the applications 702. In some embodiments, the hardware 704 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 RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

[0115] 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.

[0116] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired 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.

[0117] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0118] Some example embodiments of the present disclosure are as follows:

[0119] Group A Embodiments

[0120] Embodiment 1 : A method performed by a User Equipment, UE, the method comprising: selecting (202), from among a set of time offsets, a time offset to use for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring; receiving (206) a WUS (e.g., via a WUR of the UE) from a network node; and, responsive to receiving (206) the WUS, performing (208) PDCCH monitoring (e.g., using a main receiver of the UE) during a time occasion that is based on the selected time offset.

[0121] Embodiment 2: The method of embodiment 1, wherein the set of time offsets comprises two or more time offsets.

[0122] Embodiment 3: The method of embodiment 1 or 2, further comprising receiving (200), from the network node, information that configures the UE with the set of time offsets. Embodiment 4: the method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication from the network node.

[0123] Embodiment 5: The method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via dynamic signaling.

[0124] Embodiment 6: The method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via MAC CE or DCI.

[0125] Embodiment 7: The method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an implicit indication from the network node.

[0126] Embodiment 8: The method of embodiment 7, wherein the implicit indication comprises one or more conditions or parameters configured by the network, and selecting (202) the time offset to use for WUS triggered PDCCH monitoring comprises selecting (202) the time offset to use for WUS triggered PDCCH monitoring based on the one or more conditions or parameters configured by the network.

[0127] Embodiment 9: The method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on one or more predefined or configured rules.

[0128] Embodiment 10: The method of any of embodiments 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring comprises: selecting a first time offset if a timer has not expired; and selecting a second time offset if the timer has expired, the second time offset being greater than the first time offset.

[0129] Embodiment 11 : The method of embodiment 10, wherein the timer is started or re-started by the UE each time the UE transmits uplink data or receives downlink data.

[0130] Embodiment 12: The method of any of embodiments 1 to 11, wherein the selected time offset is a time offset between a time at which the UE receives the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0131] Embodiment 13: The method of any of embodiments 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., SSB or TRS) after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring. Embodiment 14: The method of any of embodiments 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., SSB or TRS) that occurs a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0132] Embodiment 15: The method of any of embodiments 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal (e.g., SSB or TRS) that occurs at least a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

[0133] Embodiment 16: The method of any of embodiments 1 to 15, further comprising performing (208) PDCCH monitoring (e.g., using a main receiver of the UE) during one or more additional time occasions that are based on one or more additional time offsets, from among the set of time offsets, that are greater than the selected time offset.

[0134] Embodiment 17: The method of any of embodiments 1 to 16, wherein the UE is configured to monitor for two or more different sets of WUS s having different sets of time offsets.

[0135] Embodiment 18: The method of embodiment 17, further comprising performing the method of any of embodiments 1 to 16 for each of the two or more different sets of WUSs.

[0136] Embodiment 19: The method of any of the previous embodiments, further comprising: providing user data; and Forwarding the user data to a host via the transmission to the network node.

[0137] Group B Embodiments

[0138] Embodiment 20: A method performed by a network node, the method comprising: sending (302) to a User Equipment, UE, an explicit or implicit indication of a time offset from a set of time offsets to be used by the UE for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring.

[0139] Embodiment 21 : The method of embodiment 20, further comprising configuring (300) the UE with the set of time offsets for WUS triggered PDCCH monitoring,

[0140] Embodiment 22: The method of embodiment 20 or 21, wherein the set of time offsets comprises two or more time offsets.

[0141] Embodiment 23: The method of any of embodiments 20 to 22, wherein sending (302) an explicit or implicit indication comprises sending (302), to the UE via dynamic signaling, an explicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring. Embodiment 24: The method of embodiment 23, wherein the dynamic signaling is a MAC CE or DCI.

[0142] Embodiment 25: The method of any of embodiments 20 to 22, wherein sending (302) an explicit or implicit indication comprises sending (302), to the UE, an implicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring.

[0143] Embodiment 26: The method of embodiment 25, wherein the implicit indication comprises one or more conditions or parameters.

[0144] Embodiment 27: The method of any of embodiments 20 to 26, wherein the UE is configured to monitor for two or more different sets of WUSs having different sets of time offsets.

[0145] Embodiment 28: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0146] Group C Embodiments

[0147] Embodiment 29: A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0148] Embodiment 30: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0149] Embodiment 31 : 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 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.

Claims

CLAIMS1. A method performed by a User Equipment, UE, the method comprising: selecting (202), from among a set of time offsets, a time offset to use for Wake-UpSignal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring; receiving (206) a WUS from a network node; responsive to receiving (206) the WUS, performing (208) PDCCH monitoring during a time occasion that is based on the selected time offset.

2. The method of claim 1, wherein the set of time offsets comprises two or more time offsets.

3. The method of claim 1 or 2, further comprising receiving (200), from the network node, information that configures the UE with the set of time offsets.

4. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication from the network node.

5. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via dynamic signaling.

6. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an explicit indication received from the network node via Medium Access Control, MAC, Control Element, CE, or Downlink Control Information, DCI.

7. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on an implicit indication from the network node.

8. The method of claim 7, wherein the implicit indication comprises one or more conditions or parameters configured by the network, and selecting (202) the time offset to use for WUS triggered PDCCH monitoring comprises selecting (202) the time offset to use for WUS triggered PDCCH monitoring based on the one or more conditions or parameters configured by the network.

9. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring is based on one or more predefined or configured rules.

10. The method of any of claims 1 to 3, wherein selecting (202) the time offset to use for WUS triggered PDCCH monitoring comprises: selecting a first time offset if a timer has not expired; and selecting a second time offset if the timer has expired, the second time offset being greater than the first time offset.

11. The method of claim 10, wherein the timer is started or re-started by the UE each time the UE transmits uplink data or receives downlink data.

12. The method of any of claims 1 to 11, wherein the selected time offset is a time offset between a time at which the UE receives the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

13. The method of any of claims 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

14. The method of any of claims 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal that occurs a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

15. The method of any of claims 1 to 11, wherein the selected time offset is a time offset between a time of reception of a first occasion of a sync signal that occurs at least a fixed amount of time after reception of the WUS and a start of the time occasion during which the UE performs the PDCCH monitoring.

16. The method of any of claims 1 to 15, wherein the UE is configured with two or more sets of time offsets for two or more respective WUS sets, and the set of time offsets from which the selected time offset is selected is one of the two or more sets of time offsets for one of the two ormore respective WUS sets monitored by the UE when receiving (206) the WUS from the network node.

17. The method of any of claims 1 to 15, further comprising performing (208) PDCCH monitoring during one or more additional time occasions that are based on one or more additional time offsets, from among the set of time offsets, that are greater than the selected time offset.

18. A User Equipment, UE, adapted to : select (202), from among a set of time offsets, a time offset to use for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring; receive (206) a WUS from a network node; and responsive to receiving (206) the WUS, perform (208) PDCCH monitoring during a time occasion that is based on the selected time offset.

19. The UE of claim 18, further adapted to perform the method of any of claims 2 to 17.

20. A User Equipment, UE, comprising: a communication interface comprising one or more receivers; and processing circuitry associated with the communication interface, the processing circuitry configured to cause the UE to: select (202), from among a set of time offsets, a time offset to use for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring; receive (206) a WUS from a network node; and responsive to receiving (206) the WUS, perform (208) PDCCH monitoring during a time occasion that is based on the selected time offset.

21. The UE of claim 20, wherein the processing circuitry is further configured to cause the UE to perform the method of any of claims 2 to 17.

22. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any of claims 1 to 17.

23. A carrier containing the computer program of claim 22, wherein the carrier is one of anelectronic signal, an optical signal, a radio signal, or a computer readable storage medium.

24. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a User Equipment, UE, whereby the UE is operable to: select (202), from among a set of time offsets, a time offset to use for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring; receive (206) a WUS from a network node; and responsive to receiving (206) the WUS, perform (208) PDCCH monitoring during a time occasion that is based on the selected time offset.

25. A method performed by a network node, the method comprising: sending (302) to a User Equipment, UE, an explicit or implicit indication of a time offset from a set of time offsets to be used by the UE for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring.

26. The method of claim 25, further comprising configuring (300) the UE with the set of time offsets for WUS triggered PDCCH monitoring,27. The method of claim 25 or 26, wherein the set of time offsets comprises two or more time offsets.

28. The method of any of claims 25 to 27, wherein sending (302) an explicit or implicit indication comprises sending (302), to the UE via dynamic signaling, an explicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring.

29. The method of claim 28, wherein the dynamic signaling is a Medium Access Control, MAC, Control Element, CE, or Downlink Control Information, DCI.

30. The method of any of claims 25 to 27, wherein sending (302) the explicit or implicit indication comprises sending (302), to the UE, an implicit indication of the time offset to be used by the UE from WUS triggered PDCCH monitoring.

31. The method of claim 30, wherein the implicit indication comprises one or more conditions or parameters.

32. The method of any of claims 25 to 31, wherein the UE is configured to monitor for two or more different sets of WUSs having different sets of time offsets.

33. A network node for a cellular communications network, the network node adapted to: send (302) to a User Equipment, UE, an explicit or implicit indication of a time offset from a set of time offsets to be used by the UE for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring.

34. The network node of claim 33, further adapted to perform the method of any of claims 26 to 32.

35. A network node for a cellular communications network, the network node comprising processing circuitry configured to cause the network node to: send (302) to a User Equipment, UE, an explicit or implicit indication of a time offset from a set of time offsets to be used by the UE for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring.

36. The network node of claim 35, wherein the processing circuitry is further configured to cause the network node to perform the method of any of claims 26 to 32.

37. A computer program comprising instructions which, when executed on at least one processor, cause the processor to carry out the method according to any of claims 25 to 32.

38. A carrier containing the computer program of claim 37, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

39. A non-transitory computer-readable medium comprising instructions executable by processing circuitry of a network node, whereby the network node is operable to: send (302) to a User Equipment, UE, an explicit or implicit indication of a time offset from a set of time offsets to be used by the UE for Wake-Up Signal, WUS, triggered Physical Downlink Control Channel, PDCCH, monitoring.

Images