WO2025210237A1 - User equipment, radio network node, system and methods performed therein - Google Patents

Abstract

Embodiments herein may relate to a method performed by a UE (10) for handling communication in a wireless communication network. The UE obtains a configuration comprising one or more time offsets. The UE (10) receives a WUS, from a radio network node (12) at a first reception time instant; and monitors a PDCCH, at a second reception time instant, wherein the second reception time instant is based on a first time offset out of the one or more time offsets relative to the first reception time instant.

Description

USER EQUIPMENT, RADIO NETWORK NODE, SYSTEM AND METHODS PERFORMED THEREIN

TECHNICAL FIELD

Embodiments herein relate to a user equipment (UE), a radio network node, a system and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication, such as handling paging of the UE, in a wireless communication network.

BACKGROUND

In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an architecture comprising radio network nodes connected directly to one or more core networks.

With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), Access Management Function (AMF), Authentication Service Function (ALISF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

A UE may comprise a wake-up receiver (WUR), which is sometimes also referred to as ‘wake-up radio’. Using the WUR is about enabling a low power (LP) receiver in UEs, which, in case of the detection of a wake-up signal (WUS), wakes up a main receiver (MR), also referred to as main radio. The MR may be a baseband receiver, or a radio frequency (RF) receiver and is a less power efficient receiver than the WUR, and is used to detect an incoming message, typically a paging message, e.g., in a physical downlink control channel (PDCCH) in a paging occasion (PO). The paging message may schedule a message on physical downlink shared channel (PDSCH), or schedule DL data on PDCCH. The main benefit of employing WUR at the UE is to lower energy consumption and prolong battery life of the UE, or at a fixed energy consumption the downlink latency can be reduced, whereas the UE may implement shorter discontinuous reception (DRX) and/or duty-cycles and perform more frequent checks for incoming transmissions.

In general, there are two approaches for detecting WUS:

• Using the MR at the UE for detecting the WUS: o This means that there is no need for additional dedicated hardware/receiver for monitoring WUS o A coverage of the main receiver is not typically impacted

• Using the approach implies a limited power saving gain since the MR monitors for the WUS Having a dedicated receiver, such as a WUR at the UE for detecting the WUS: o The WUR has an extremely low power consumption, with a simple and low-cost receiver architecture, and also with relaxed requirements, since it can use a less accurate clock or oscillator o Using the WUR implies that a significant power saving gain can be achieved by maximizing a time in which the MR can be kept in the sleep mode o Using the WUR enables operations for zero energy devices, battery-less devices, and/or devices with energy harvesting operations. o There are coverage considerations given the tradeoff between WUR power consumption and sensitivity to detect WUS.

In release (Rel)-18, there has been rather large interest in introducing WUR for NR, with an ambition to achieve a more significant energy efficiency improvement compared to solutions already specified in earlier releases. As explained above, the only specification support needed to be able to use a WUR in the UE, is the specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO, to allow the UE to start up the MR. Therefore, the main difference to Rel-17 paging early indication (PEI) is that the WUS in Rel-18 should not be PDCCH-based receiver and this allows for a simpler and low power receiver, i.e., a WUR with simple modulation and detection techniques, e.g., using on-off keying (OOK) modulation and noncoherent detection.

In Rel-18, a study item on “low-power wake-up signal and receiver for NR” was approved. The relevant justification and objective sections are copied below:

The benefit of using a WUR is to reduce the energy consumption of the receiver, such that unless there is any paging and data for the UE, the UE may remain in a power saving state. This will prolong the battery life of the UE, or alternatively enable shorter downlink latency, since shorter DRX cycles may be used at the UE, at a fixed battery life.

The Rel-18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical report is provided in: 3GPP TR 38.869, VO.4.0, “Study on low-power Wake-up Signal and Receiver for NR”. Subsequently, there will be a Rel-19 Work Item to specify the various design aspects of WUS and/or WUR. For Rel-19, a work item has been agreed to specify the wake-up signal for both radio resource control (RRC) Idle/lnactive and RRC Connected states: RP-234056, New WID: Low- power wake-up signal and receiver for NR (LP WUS/WUR). The objectives are the following:

WUS functionality in RRC connected mode:

The relevant RAN1 agreements related to this so far are:

Agreement 1

• For RRC connected mode, the following is assumed for a low power (LP)-WUS study in RANI . o Radio link monitoring (RLM)/beam failure detection (BFD)/ channel state information (CSI) are performed by UE MR. o Radio resource management (RRM) measurements are performed by UE MR. o Ultra-deep sleep state is not allowed for MR.

• Study additional support of RRM measurement by LP-WUR for RRC connected mode.

• Study RRC connected mode LP-WUS functionality, purpose, and/or procedures.

• Study RRC connected mode LP-WUS activation and/or deactivation procedures.

• Study RRC connected mode LP-WUS bandwidth (BW), whether same as IDLE/lnactive mode or different.

In RRC connected, study the relationship between LP-WUS and legacy UE power saving techniques.

Agreement

■ In RRC CONNECTED mode, study benefit of LP-WUS over existing Rel-15, Rel-16, and Rel-17 power saving techniques for following functionalities: o The LP-WUS with similar functionality as Rel-16 downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by Power saving (PS)- Radio Network Temporary Identifier (RNTI) denoted as Downlink Control Information of Power Saving (DCP). o LP-WUS activates and/or resumes PDCCH monitoring when LP-WUS is received.

■ interaction with legacy power saving techniques, if any. o other functionalities are not precluded o for evaluation

■ companies to report

• assumption on MR sleep state when LP-WUR is monitoring LP-WUS o deep sleep, o light sleep, o micro sleep.

• how to activate and/or deactivate LP-WUS monitoring and deactivate and/or activate PDCCH monitoring

• LP-WUS waveform

■ In RRC CONNECTED mode, the LP-WUS monitoring can be activated and/or deactivated by at least one or more of: o by gNB RRC signaling, with or without UE assistance. o by gNB layer one (L1) and/or layer two(L2) LP-WUS activation and/or deactivation signaling, with or without UE assistance. o based on pre-configured condition(s), such as using a timer to activate and/or deactivate LP-WLIS monitoring. o LP-WLIS monitoring by UE is known to gNB, study whether it could be transparent to gNB. o other options are not precluded.

SUMMARY

As part of developing embodiments herein one or more issues have been identified. 3GPP is going to introduce the WUS signal monitoring using the WUR in Rel-19 to potentially save the UE receiver power during RRC connected and idle mode. The UE will thus equip an additional WUR to receive the WUS signal. During the connected mode, the UE may monitor the WUS using the WUR and if there is no WUS received, the UE may continue to keep the MR in sleep mode, and thereby, additional power can be saved.

When a WUS targeted to a specific UE is successfully decoded, the UE wakes up its MR to monitor the PDCCH. Such behavior is similar with Rel-16 DCI based wake-up signal but with the notable difference that for using the WUR, the MR maybe kept in a sleep state for the monitoring of the WUS at the WUR, and the MR may only to be woken when there is data for the UE.

Depending on which sleep state the UE is in, the time it takes to wake up the MR may vary. For example, typical numbers, assumed by 3GPP for modelling, are deep sleep: 20ms, light sleep: 6ms and micro sleep 0ms. An ultra-deep sleep state may be associated with, e.g., a 400 ms wakeup time. Depending on UE implementation or UE capability, a specific UE may have shorter, or longer, wake up times from the different sleep states. In order to allow the UE to wake up the MR before the PDCCH is transmitted, an offset between the WUS and the PDCCH is needed. Several aspects may need to be considered for configuration and design of such an offset, for example, the offset will determine the sleep state the UE can use and still be able to wake up the MR. Also latency requirements, i.e., if the UE has data or expects data for communication with high latency requirements, a long offset should not be configured. In addition, from network (NW) perspective, it may be of interest to group UEs with the same WUS offset to avoid having to transmit multiple WUSs to wake up all UEs. Energy efficiency, which is an objective, needs also to be considered as well as an expected data transmission pattern. Furthermore, the design should allow a fast switch of the offset to use and not give a large increase of signaling.

Thus, a solution is needed to find a good and efficient design for the configuration and use of a time offset between the WUS and PDCCH transmission.

An object of embodiments herein is to support communication in a wireless communication network in an energy efficient manner.

According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a UE for handling communication in a wireless communication network. The UE obtains a configuration comprising one or more time offsets, wherein the one or more time offsets comprises a first time offset. The UE further receives a WUS from a radio network node at a first reception time instant, and monitors a PDCCH at a second reception time instant. The second reception time instant is based on the first time offset relative to the first reception time instant.

According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a radio network node for handling communication in a wireless communication network. The radio network node transmits to a UE, a configuration comprising one or more time offsets, wherein the one or more time offsets comprises a first time offset. The radio network node further transmits a WUS to the UE at a first transmission time instant; and a signal in a PDCCH at a second transmission time instant. The second transmission time instant is based on the first time offset relative to the first transmission time instant.

It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE or the radio network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the UE or the radio network node, respectively.

Furthermore, according to another aspect the object is achieved, according to some embodiments herein, by providing a UE and a radio network node configured to perform the methods herein, respectively.

Thus, according to an aspect the object is achieved, according to some embodiments herein, by providing a UE for handling communication in a wireless communication network. The UE is configured to obtain a configuration comprising one or more time offsets, wherein the one or more time offsets comprises a first time offset. The UE is further configured to receive a WUS from a radio network node at a first reception time instant, and to monitor a PDCCH at a second reception time instant. The second reception time instant is based on the first time offset relative to the first reception time instant.

According to another aspect the object is achieved, according to some embodiments herein, by providing a radio network node for handling communication in a wireless communication network. The radio network node is configured to transmit to a UE, a configuration comprising one or more time offsets, wherein the one or more time offsets comprises a first time offset. The radio network node is further configured to transmit a WUS to the UE at a first transmission time instant; and to transmit a signal in a PDCCH at a second transmission time instant. The second transmission time instant is based on the first time offset relative to the first transmission time instant. According to another aspect the object is achieved, according to some embodiments herein, by providing a system comprising a UE and a radio network node configured to perform the methods herein.

It is proposed herein to provide a solution to enable varyingly deep UE power saving states in, for example, RRC Connected state, through the connection of a configured time offset and a sleep state. The sleep state may be a deepest or lowest power consumption sleep that is applicable for the UE. Further, some embodiments herein may include configurational aspects with multiple time offsets, such as at least two time offsets, and how the UE may switch between the multiple time offsets. The UE may switch between the multiple time offsets implicitly, such as switching the time offset to use based on a timer, or explicitly, such as switching the time offset to use according to received DCI.

Embodiments herein enable configurations and application of one or more time offsets between WUS and PDCCH which enhances the WUS operation to give a lower energy consumption while at the same time ensure short latency, for example, when new or additional traffic can be expected. Hence, the embodiments herein provide a mechanism to provide a solution that is energy efficient.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

Fig. 1 shows an overview depicting a wireless communication network according to embodiments herein;

Fig. 2 is a combined flowchart and signaling scheme according to some embodiments herein;

Fig. 3 shows a flowchart illustrating a method performed by a UE according to embodiments herein;

Fig. 4 shows a flowchart illustrating a method performed by a radio network node according to embodiments herein;

Fig. 5 shows an example of a scenario wherein a UE uses more than one time offset according to some embodiments herein;

Fig. 6 shows a block diagram depicting embodiments of a UE according to embodiments herein;

Fig. 7 shows a block diagram depicting embodiments of a radio network node according to embodiments herein;

Fig. 8 schematically illustrates embodiments of a communication system,

Fig. 9 is a generalized block diagram of embodiments of a UE,

Fig. 10 is a generalized block diagram of embodiments of a network node, and Fig. 11 is a generalized block diagram of embodiments of a virtualization environment.

DETAILED DESCRIPTION

Embodiments herein relate to communication networks in general. Fig. 1 is a schematic overview depicting a wireless communication network 1. The wireless communication network 1 comprises one or more RANs and one or more CNs. The wireless communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA) or any applicable future generation standard, e.g., 6G.

In the wireless communication network 1, a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

The wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as 6G, NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the radio network node 12 depending e.g. on the first radio access technology and terminology used. The radio network node may be referred to as a serving radio network node wherein the service area may be referred to as a serving cell, and the serving network node communicates with the UE 10 in form of DL transmissions to the UE and UL transmissions from the UE. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. The radio network node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks.

According to embodiments herein the UE 10 obtains a configuration comprising one or more time offsets. The one or more time offsets comprises a first time offset. The UE 10 may, for example, receive from the radio network node 12, the configuration comprising one or more WUS offsets, for example, at least two WUS offsets. The UE 10 then receives from the radio network node 12 a WUS at a first reception time instant, and the UE 10 monitors a PDCCH at a second reception time instant. The second reception time instant is based on the first time offset, i.e., first WUS offset, relative to the first reception time instant. A time offset is defined as a time interval between an indication, e.g. the WUS, and a corresponding event that it indicates, e.g. the PDCCH transmission and/or reception.

Embodiments herein describe methods to configure time offsets between WUS and PDCCH time instants. The time offset may be an interval time value, a time value, or similar. This may be based on UE capabilities in RRC Connected state and the UE 10 may autonomously switch between time offsets depending on, for example, a time since a last data transmission.

The UE 10 may select and indicate its preferred one or more time offsets to the radio network node 12, and/or the one or more time offsets that the UE 10 is capable of may be signaled to the radio network node 12 as part of a legacy UE capability reporting framework. The indicated time offsets may correspond to the time offsets the UE 10 needs to be able to start its MR, i.e., the ramp up time, from the different sleep states. That is, a time offset may be a time interval corresponding to a respective ramp-up time of a respective sleep state to allow for the configuration to enable communication to be optimized.

In some embodiments, the radio network node 12 may configure the UE 10 with one or more time offsets to be used, for example, for corresponding sleep states or in certain predefined operating modes and/or states, based on the UE’s reported time offset capabilities, as indicated as a time offset preference, and/or based on a DL latency requirement, such as a Quality-of-service (QoS) requirement.

The UE 10, and also the radio network node 12, may then apply the different time offsets according to the configuration, i.e., at a given time the UE 10 and the radio network node 12 apply the same time offset. The time offset to be used, out of the multiple configured time offsets, may be selected based on a PDCCH monitoring scenario, e.g. the function of type of the PDCCH. Alternatively, the time offset to be used may be indicated by signaling an indication from the radio network node 12, where the indication may refer to one or more preconfigured time offsets, or an overriding value. According to embodiments herein, the radio network node 12 transmits to the UE 10, a WUS at a first transmission time instant and the UE 10 receives the WUS at a first reception time instant. The radio network node 12 further transmits to the UE 10, a signal, such as a paging message, in PDCCH at a second transmission time instant and the UE 10 monitors the PDCCH at a second reception time instant. The second transmission and reception time instants are based on or associated with the first time offset relative to the first transmission or reception time instant, respectively. Thus, the first time offset defines when to transmit from the radio network node 12, and when to monitor at the UE 10, for the signal, such as a paging message in the PDCCH.

In one option, similar to a short DRX and a long DRX in Connected state, the shortest offset, such as an offset_1, may be applied after an inactivity timer has expired and the MR is turned off after finalization of data transmission activity. After a configurable time, e.g. a first timer value such as timer_1 expires, the UE 10 and the radio network node 12 may apply offset_2 until a second configurable time, e.g. a second timer value such as timer_2 expires, after which a third time offset is used such as timer_3. The number of time offsets, and accordingly also the number of MR sleep states, to consider may be configurable.

In another option, the time offsets may be linked to short and long DRX cycles, respectively. That is, the WUR operation may be added on top of a legacy Connected DRX operation. In this case, while the short-DRX cycles are used, a first shorter time offset may be used and while the long DRX is applied, a second longer time offset may be applied. That is, a WUR operation may be reusing legacy Connected DRX configuration parameters with the addition of the time offset.

Embodiments herein enable configurations and application of time offsets between WUS and PDCCH which enhances the WUS operation to give lower energy consumption while at the same time ensure short latency when new traffic can be expected.

Fig. 2 is a combined flow chart and signaling scheme according to some embodiments herein.

Action 201. The radio network node 12 may transmit the configuration to the UE 10. The configuration comprises the one or more time offsets comprising the first time offset.

Action 202. The radio network node 12 transmits the WUS at the first transmission time instant TT 1 , also referred to as a first transmission time instance, a first transmission time occasion, a first transmission time, or similar. The UE 10 receives the WUS at the first reception time instant RT1, also referred to as a first reception time instance, a first reception time occasion, a first reception time, or similar.

Action 203. The radio network node 12 furthermore transmits to the UE 10, a signal such as a paging message in the PDCCH at the second transmission time instant TT2, also referred to as a second transmission time instance, a second transmission time occasion, a second transmission time, or similar. The second transmission time instant is based on the first time offset, such as offset_1, relative to the first transmission time instant. The UE 10 monitors the PDCCH at the second reception time instant RT2, also referred to as a second reception time instance, a second reception time occasion, a second reception time, or similar. The second reception time instant is based on the first time offset, such as offset_1 , relative to the first reception time instant. Thus, the first time offset is used by the radio network node 12 and the UE 10 and thereby synchronizing the radio network node 12 and the UE 10. Thus, TT2-TT1 equals the first time offset, and the first time offset equals RT2-RT 1 in Fig. 2. The TT 1 may be the same as RT 1 and the TT2 may be equal to RT2, but the RT1 may be delayed from TT1 and RT2 may be delayed from TT2 to consider propagation and/or transmission of the signal.

It is further herein disclosed a system comprising a UE and a radio network node configured to perform the methods herein.

The method actions performed by the UE 10 for handling communication in the wireless communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 3. Optional actions are marked as dashed boxes. The UE 10 may be in RRC_CONNECTED state.

Action 301. The UE 10 may transmit to the radio network node 12 one or more UE indications, also referred to as capability indications, indicating one or more preferred or supported time offsets or offset values. The one or more supported and/or preferred time offset values may be associated with a respective UE sleep state or MR sleep state. The one or more supported and/or preferred time offset values may comprise a list of threshold values each associated with an energy level at the UE 10 during operation such as during monitoring.

Action 302. The UE 10 obtains the configuration comprising the one or more time offsets, wherein the one or more time offsets comprises the first time offset. The respective time offset out of the one or more time offsets may be associated with a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc. The respective time offset out of the one or more time offsets may be associated with at least one of a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type. Service type refers to the current device use case requirements or quality of service and/or experience requirements, including reliability, throughput, and latency key performance indicators (KPI) for the UE 10 and radio network node 12 in that use case. Typically, higher requirements lead to stricter WUS-to-PDCCH delay constraints and thus shorter WUS offset times. Reception type may be the modulation used for WUS. Currently either on-off Keying (OOK) or orthogonal frequency-division multiplexing (OFDM). The configuration may be preconfigured or be received from the radio network node 12 or other radio network node in a system information (SI) or a dedicated RRC signalling. The one or more time offsets may comprise multiple time offsets such as at least two time offsets. Action 303. The UE 10 further receives the WUS from the radio network node 12 at the first reception time instant. The UE 10 may receive the WUS using the WUR of the UE 10.

Action 304. The UE 10 may wake up the MR upon reception of the WUS at the WUR. Thus, the UE 10 may move, transit, set or switch the MR into an active state or mode.

Action 305. The UE 10 may request to use the first time offset based on at least one of: a time offset capability of the UE 10, one or more time offset preferences, DL latency requirement, an operating mode, an operating state, a timer value, a service type, a time to start the MR from a sleep state, and/or a reception type. This action may be performed before or after action 302, 303, and/or action 304, or be a part of action 301.

Action 306. The UE 10 may receive a selection indication from the radio network node 12 indicating the first time offset to use. This action may be performed before or after action 302, 303, and/or action 304. This action may be an example of action 302.

Action 307. The UE 10 may determine the first time offset out of the one or more time offsets based on a PDCCH monitoring scenario. This action may be performed before or after action 302, 303 and/or action 304.

Action 308. The UE 10 monitors the PDCCH at the second reception time instant, where the second reception time instant is based on the first time offset relative to the first reception time instant. Thus, the UE 10 may monitor the PDCCH at the second reception time instant, where the offset between the first reception time instant and the second time instants is based on the first time offset. The UE 10 may then proceed subsequently to receive and decode the PDSCH message that the PDCCH points to. The one or more time offsets may further comprise a second time offset, and the UE 10 may monitor, after a timer related to expected additional data arrival window has expired, the PDCCH at a third reception time instant. The third reception time may be based on the second time offset relative to the first reception time instant, which allows the UE 10 to go into a second sleep state.

The method actions performed by the radio network node 12 for handling communication in the wireless communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 4. Optional actions are marked as dashed boxes.

Action 401. The radio network node 12 may receive from the UE 10, the one or more UE indications indicating the one or more preferred and/or supported time offsets or offset values. The one or more supported and/or preferred time offset values may be associated with a respective UE sleep state or MR sleep state. The one or more supported and/or preferred time offset values may comprise a list of threshold values each associated with an energy level at the UE 10.

Action 402. The radio network node 12 transmits to the UE 10, the configuration comprising the one or more time offsets, wherein the one or more time offsets comprises the first time offset. The respective time offset of the one or more time offsets may be associated with at least one of: a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc. The respective time offset of the one or more time offsets may be associated with at least one of a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type. The configuration may be transmitted in a SI or a dedicated RRC signalling. The one or more time offsets may in some embodiments comprise at least two time offsets.

Action 403. The radio network node 12 further transmits the WUS to the UE 10 at the first transmission time instant.

Action 404. The radio network node 12 may receive a request from the UE 10, requesting to use the first time offset. This action may be performed before or after action 402, and/or action 403, or be a part of action 401.

Action 405. The radio network node 12 may determine to use the first time offset based on at least one of: a time offset capability of the UE 10, one or more time offset preferences, DL latency requirement, an operating mode, an operating state, a timer value, a service type, and/or a reception type. The radio network node 12 may determine the first time offset out of the one or more time offsets based on a PDCCH monitoring scenario. This action may be performed before or after action 402, and/or action 403.

Action 406. The radio network node 12 may transmit the selection indication to the UE 10 indicating the first time offset to use. This action may be performed before or after action 402, and/or action 403.

Action 407. The radio network node 12 transmits to the UE 10, a signal such as a paging message in the PDCCH at the second transmission time instant, where the second transmission time instant is based on the first time offset relative to the first transmission time instant.

A high level view of some embodiments herein, wherein the UE 10 is in RRC Connected state, is depicted in Fig. 5. The UE 10 is configured with a set of time offsets. Further, the UE 10 may be configured with timer values which dictate when the different time offsets in the set applies. Fig. 5 shows an example wherein the UE 10 first uses a first time offset allowing it to go into one sleep state. After some time, e.g. after a timer related to expected additional data arrival window has expired, the UE 10 uses a second time offset which allows the UE to go into a second sleep state.

According to embodiments herein, the UE 10 may be configured with the configuration, also referred to as a Connected WUR configuration, including the one or more time offsets, also referred to as WUS-PDCCH offsets, and rules for when they should be applied. This may be configured for example in an RRC configuration message such as the RRC re-configuration received upon RRC connection establishment or RRC connection resume message when the UE 10 comes from RRC Idle or RRC Inactive, in the same as the legacy Connected DRX configuration.

The radio network node 12 may determine the time offsets in the set of time offsets based on a UE indication from the UE 10 which indicates which time offsets the UE 10 is capable of and/or prefers to apply. The time offsets which the UE 10 is capable of can be indicated in UE capability signaling messages. The time offsets which the UE prefers could for example be indicated in a UE assistance information message.

The radio network node 12 may indicate whether the UE 10 is allowed to indicate its one or more preferred and/or capable time offsets. The radio network node 12 may further indicate how often the UE 10 is allowed to indicate the one or more UE capable and/or preferred time offsets. This may be indicated from radio network node 12 by means of a timer value which indicates how long time a new UE indication can be sent after a previous UE indication. Alternatively, the UE 10 may only be allowed to indicate a new UE indication if the time offsets have changed, e.g. more than a change threshold. Another approach is that the UE 10 cannot change its UE (time offset) indications unless the UE 10 has initiated new (type of) traffic or traffic bearer. This has the benefit that the UE 10 will not send unnecessary UE indications to the radio network node 12 and hence the UE 10 may save signaling overhead.

The one or more time offsets which is allowable and/or possible for the radio network node 12 to configure for the UE 10 may be a subset of all possible time offset values. For example, the radio network node 12 may only support time offsets of 1 , 5 and 20 ms, while the particular UE 10 may support 1 , 5 and 10 ms. In one embodiment the radio network node 12 indicates to the UE 10 the set of allowable and/or possible time offsets for the radio network node 12. The UE 10 may in this case only indicate to the radio network node 12 those time offsets which are allowable and/or possible for the radio network node 12 and which the UE 10 also is capable of, or prefers. In the above example, the UE 10 may indicate 1 and 5 ms but not 10 ms since the radio network node 12 didn’t indicate that 10 ms is allowable and/or possible for the radio network node 12 to configure. This can be seen as a means to filter and/or reduce the size of the UE indications to the radio network node 12 and may reduce signaling overhead. The network’s allowable and/or possible time offsets may be indicated to the UE 10 in a dedicated message or in a broadcast message such as system information.

The allowable and/or possible time offsets for the radio network node 12, and the time offsets that the UE 10 is capable of and/or prefers may be expressed as set of time offsets per different sleep states, e.g. 0,1 , 2, 3 ms for micro sleep, 4, 5, 6, 7, 8 ms for light sleep etc. Further, these indications can be indicated by means of enumerated list(s) of typical or standardized sleep states. The UE 10 may report preferred one or more time offsets or sleep states which are different from the one or more time offsets which the UE 10 is capable of. For example, the UE 10 may prefer to remain in a deeper sleep state in order to save energy.

The one or more time offsets indicated by the UE 10 may be expressed as thresholds where making the delay longer than a particular time offset provides no additional power saving benefits to the UE 10, until the next value. E.g. the UE 10 may indicate thresholds 20 and 150 ms, which means that setting a time offset to 21-149 ms does not benefit UE power saving (PS) compared to setting it to 20 ms.

The time offset, also referred to as time offset value, indicated by the UE 10 may include the sum of the turn-on and turn-off times. In another embodiment, the one or more time offsets include the turn-off time of the MR or WUR, and the turn-off time may be indicated separately and treated as a prohibition time between when the previous UE activity ends and the next WUS reception.

The UE 10 may indicate one or more preferred time offsets based on hardware (HW) design choices and capabilities. Such UE indication may be provided once per network (NW) connection or once per RRC_CON NESTED session. The UE 10 may indicate one or more preferred time offsets based on maximum latency permitted in an ongoing application, use case, or traffic pattern. Such UE indication may be changed during an RRC_CONNECTED session.

The radio network node 12 may configure one or more time offsets and timer values or other parameters needed for the UE 10 to determine which of the configured time offsets to apply. Or in other words, the timer values and/or parameters may dictate which time offset the UE 10 applies and when.

The different time offset values may be configured for different predefined operating modes. For example, a first time offset may apply while monitoring for a first actual data transmission in an onDuration or a traffic burst, while a second time offset may apply for a subsequent monitoring occasion after the first transmission is received, until the end of the monitoring interval or a DRX inactivity timer (IAT). Alternatively, different time offsets may be configured for short and long DRX cycle phases, etc.

In one option of this embodiment, some of these configurations may be given in system information.

The radio network node 12 may configure the UE 10 with a specific time offset to apply. This signaling can override any previous configuration. The radio network node 12 may signal to the UE 10 a WUS offset that will be applied to its subsequent transmissions, also referred to as selection indication. The signaling could either indicate which of multiple previously defined configurations to apply, or it could explicitly indicate and/or update the time offset. The signaling may include an application delay after which the time offset becomes valid, up to which point a previously indicated, or default, time offset may apply.

The radio network node 12 may select and signal, for the UE 10, the largest time offset previously provided by the UE 10 that does not exceed a current data latency requirement for the UE 10, where the data latency requirement may be based on the UE use case, or on NW performance key performance indicators (KPI) or other criteria.

According to some embodiments herein, the UE 10 may start a first timer when the MR is turned off. While this timer is running, the UE 10 applies a first configured time offset. When the first timer expires, the UE 10 starts a second timer and while the second timer is running the UE 10 applies a second time offset. This may be repeated for all configured time offsets. When the last configured time offset is used, i.e. the largest time offset, no timer is started, and the largest time offset is applied until the MR is started upon which the UE 10 starts the first timer again.

The application of the different time offsets may be based on which DRX cycle is used. In this case a first time offset may be used when a short-DRX cycle is applied. When a long DRX cycle is applied, a second time offset may be applied. This may be combined with the previous features so that also one or more timers are used. For example, a timer may be started when the UE 10 enters long DRX cycle and the UE 10 uses a first time offset, and when the timer expires, the UE 10 applies a second time offset. In another option, a time offset is applied for a configurable number of DRX cycles.

UE behavior on offset configurations.

Based on the configuration of different time offsets from the network side, the UE 10 may choose different sleep states. In one embodiment, the UE 10 follows the configured time offset and chooses a sleep state accordingly. In one example of the table below, a=6, b=20, c=30 to map time offsets to a corresponding sleep state.

More generally, the UE 10 may choose the deepest sleep state whose associated wakeup time does not exceed the configured time offset.

In another embodiment, if the battery condition is below a certain battery threshold, the UE 10 may report the situation and always choose deep sleep or light sleep until the battery condition is above the certain battery level. Further examples of embodiments:

Embodiments herein may relate to a method in a UE for signal reception in RRC_CONNECTED, comprising

- receiving from a gNB a WUS configuration comprising a WUS offset,

- receiving from the gNB a WUS at a first time instant,

- monitoring a PDCCH at a second time instant, where the offset between the first and second time instants is based on the WUS offset.

In some embodiments, the WUS configuration comprises multiple WUS offset, each associated with a respective PDCCH monitoring context/scenario, timer status, short/long DRX mode, etc.

In some embodiments, the WUS configuration comprises a single WUS offset to be used for scheduling PDCCH monitoring.

In some embodiments, the WUS configuration is provided via SI broadcast signaling.

In some embodiments, the WUS configuration is provided via dedicated RRC signaling. a. Multiple configurations are provided via RRC and DCI/MAC CE signalling is used to indicate the currently applied configuration.

In some embodiments, at least the WUS offset part of the WUS configuration is provided via dedicated DCI or MAC CE signalling, or via group DCI signaling.

In some embodiments signaling to the gNB one or more preferred or supported WUS offset values. a. + the preferred values are associated with respective UE/MR sleep states. b. + the preferred values comprise a list of threshold values without an explicit association to specific UE/MR sleep states. c. + the preferred WUS offset values are associated with a signalled UE capability.

In some embodiments the preferred WUS offset values comprise offset values based on wake-up times from one or more UE sleep states.

In some embodiments upon receiving the WUS configuration to an operating scenario, the

UE configures, for the scenario, the deepest available MR sleep state for which the wakeup time does not exceed the configured WUS offset.

In some embodiments the UE monitors the WUS using the WUR, upon detecting the WUS indicating a PDCCH occasion, initiates a MR wakeup and monitors the PDCCH occasion using the MR. Fig. 6 is a block diagram depicting the UE 10 for handling communication in the wireless communication network 1 according to embodiments herein.

The UE 10 may comprise processing circuitry 601 , e.g. one or more processors, configured to perform the methods herein.

The UE 10 and/or the processing circuitry 601 is configured to obtain the configuration comprising the one or more time offsets, wherein the one or more time offsets comprises the first time offset. The UE 10 and/or the processing circuitry 601 is configured to receive the WUS from the radio network node 12 at the first reception time instant. The one or more time offsets may in some embodiments comprise at least two time offsets.

The UE 10 and/or the processing circuitry 601 is configured to monitor the PDCCH at the second reception time instant, wherein the second reception time instant is based on the first time offset relative to the first reception time instant.

The UE 10 and/or the processing circuitry 601 may be configured to transmit to the radio network node 12 one or more UE indications indicating the one or more preferred or supported time offsets (or offset values).

The respective time offset out of the one or more time offsets may be associated with, or correspond to, at least one of: a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc.

The respective time offset out of the one or more time offsets may be associated with, or correspond to, at least one of a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type.

The UE 10 and/or the processing circuitry 601 may be configured to request to use the first time offset based on at least one of: a time offset capability of the UE 10, one or more time offset preferences, a DL latency requirement, an operating mode, an operating state, a timer value, a service type, a time to start main receiver from a sleep state, and/or a reception type.

The UE 10 and/or the processing circuitry 601 may be configured to receive the selection indication from the radio network node 12 indicating the first time offset to use.

The UE 10 and/or the processing circuitry 601 may be configured to determine the first time offset out of the one or more time offsets based on the PDCCH monitoring scenario. The one or more time offsets may further comprise the second time offset. The UE 10 and/or the processing circuitry 601 may be configured to monitor, after a timer related to expected additional data arrival window has expired, the PDCCH at the third reception time instant that is based on the second time offset relative to the first reception time instant, which allows the UE 10 to go into a second sleep state.

The UE 10 may comprise a memory 605. The memory 605 comprises one or more units to be used to store data on, such as data packets, indications, WUS information, time offsets, configurations, resource information, support information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the UE 10 may comprise a communication interface 606 such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.

The methods according to the embodiments described herein for the UE 10 are respectively implemented by means of e.g. a computer program product 607 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. The computer program product 607 may be stored on a computer- readable storage medium 608, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 608, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the UE for handling communication in a communication network, wherein the UE comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE is operative to perform any of the methods herein.

Fig. 7 is a block diagram depicting the radio network node 12 for handling communication in the wireless communication network 1 according to embodiments herein.

The radio network node 12 may comprise processing circuitry 701 , e.g. one or more processors, configured to perform the methods herein.

The radio network node 12 and/or the processing circuitry 701 is configured to transmit to the UE, the configuration comprising the one or more time offsets, wherein the one or more time offsets comprises the first time offset. The one or more time offsets may comprise at least two time offsets.

The radio network node 12 and/or the processing circuitry 701 is configured to transmit the WUS to the UE at the first transmission time instant.

The radio network node 12 and/or the processing circuitry 701 is configured to transmit to the UE, the signal, such as a paging signal, in the PDCCH at the second transmission time instant. The second transmission time instant is based on the first time offset relative to the first transmission time instant.

The radio network node 12 and/or the processing circuitry 701 may be configured to receive from the UE 10 one or more UE indications indicating one or more preferred or supported time offsets or offset values. The respective time offset out of the one or more time offsets may correspond to at least one of: a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc.

The respective time offset out of the one or more time offsets may correspond to at least one of a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type.

The radio network node 12 and/or the processing circuitry 701 may be configured to determine to use the first time offset based on: a time offset capability of the UE 10, one or more time offset preferences, DL latency requirement, an operating mode, an operating state, a timer value, a service type, and/or a reception type.

The radio network node 12 and/or the processing circuitry 701 may be configured to transmit the selection indication to the UE 10 indicating the first time offset to use.

The radio network node 12 and/or the processing circuitry 701 may be configured to determine the first time offset out of the one or more time offsets based on a PDCCH monitoring scenario.

The radio network node 12 may comprise a memory 705. The memory 705 comprises one or more units to be used to store data on, such as data packets, indications, WUS information, time offsets, configurations, resource information, support information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the radio network node 12 may comprise a communication interface 706 such as comprising a transmitter, a receiver, a transceiver and/or one or more antennas.

The methods according to the embodiments described herein for the radio network node 12 are respectively implemented by means of e.g. a computer program product 707 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. The computer program product 707 may be stored on a computer-readable storage medium 708, e g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 708, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 12. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the radio network node for handling communication in a communication network, wherein the radio network node comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio network node is operative to perform any of the methods herein. In some embodiments a more general term “network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and/or with another network node.

In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and/or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

Fig. 8 shows an example of a communication system 15100 in accordance with some embodiments.

In the example, the communication system 15100 includes a telecommunications network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108. The access network 15104 includes one or more access network nodes or base stations of various types, access network nodes 15110A and 15110B are depicted (which may be collectively referred to as network nodes 15110 or radio network node 12), or any other similar 3^rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 15104 may include more than one access network technology. The network nodes 15110 of access network 15104 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (one or more of which may be generally referred to as UEs 15112 or UE 10) to the core network 15106 over one or more wireless connections.

Moreover, 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 telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and/or core network nodes 15108 such as first/second network node.

Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), 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). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network 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 O-2 interface defined by the O- RAN Alliance or comparable technologies.

The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112 to the core network 15106 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 15100 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 15100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 15112 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 15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged, capable, configured, and/or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 15102) with the UEs 15112 and/or with other network nodes or equipment in the telecommunications network 15102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunications network 15102. More specifically, UEs 15112 may send messages, data, and/or other signals to network nodes 15108, 15110 or other elements of the telecommunications network 15102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data, and other signals to UEs 151122, other network nodes 15108, 15110, and other devices in telecommunications network 15102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 15112 by transmitting the message to an access network node 15110 that will then transmit the message to the intended UE 15112. Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.

In the depicted example, the core network 15106 connects elements of the access network 15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems, such as host 15116. 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 15106 includes one or more core network nodes (e.g., core network node 15108) of various types, one or more of which may be generally referred to as network nodes 15108. Network nodes 15108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 15108. Example core network nodes provide 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 Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and/or the telecommunications network 15102. The host 15116 may be operated by the service provider or on behalf of the service provider. The host 15116 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 15100 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 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 (Wi-Fi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.

As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards, e.g., 4G and 5G 3GPP communication standards, and, as a result, may include an access network 104 and/or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and/or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

Telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 15102. For example, the telecommunications network 15102 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 loT services to yet further UEs.

In some examples, one or more of the UEs 15112 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 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. 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 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and/or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 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 15110, or by executable code, script, process, or other instructions in the hub 15114.

As another example, the hub 15114 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 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

Figure 9 shows a wireless device 15300, which may be configured to operate in communication system 15100 of Figure 8. The wireless device 15300 may be alternatively referred to as a UE 15300, like a UE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Examples of a wireless device 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, vehicle-mounted or vehicle embedded/integrated wireless device, and wireless terminal. Other examples include any type of 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 wireless device 15300 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, wireless device 15300 may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, wireless device 15300 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, wireless device 15300 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).

In particular embodiments, wireless device 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input/output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and/or any other component, or any combination thereof. Certain embodiments of wireless device 15300 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 15300 to another. In general, in a particular embodiment of wireless device 15300, processing circuitry 15302, input/output interface 15306, power source 15308, memory 15310, and communication interface 15312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 15300. Further, certain embodiments of wireless devices 15300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 15302 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 15310. The processing circuitry 15302 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 15302 may include multiple central processing units (CPUs).

In the example, the input/output interface 15306 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 wireless device 15300. 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 15308 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 to supply power to circuitry or to charge an associated battery. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and/or an external power source, to the various parts of wireless device 15300 via input circuitry or an interface such as an electrical power cable. Power source 15308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 15300 to which power is supplied.

The memory 15310 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 15310 includes one or more programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by wireless device 15300, any of a variety of various operating systems or combinations of operating systems.

The memory 15310 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 (IIICC) including one or more subscriber identity modules (SIMs), such as a IISIM and/or ISIM, other memory, or any combination thereof. The IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory 15310 may allow wireless device 15300 to access instructions, 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 15310, which may be or comprise a device-readable storage medium.

The processing circuitry 15302 may be configured to communicate with an access network or other network via or using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 15318 and/or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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.

In particular embodiments, wireless device 15300 may provide an output of data captured via a sensor, through its communication interface 15312, via a wireless connection to a network node, and/or in any appropriate manner. Data captured by sensors of a wireless device 15300 can be communicated through a wireless connection to a network node via another wireless device 15300. In particular embodiments, such 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, wireless device 15300 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, wireless device 15300 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.

Wireless device 15300, 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, 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 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. In particular embodiments, wireless device 15300 represents an loT device that 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 example embodiment of wireless device 15300 shown in Figure 9.

As yet another specific example, in an loT scenario, wireless device 15300 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 wireless device and/or a network node. Wireless device 15300 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, wireless device 15300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 15300 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 wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 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 wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 10 shows a network node 15400 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 telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Figure 8, like network nodes 15108 or 15110. 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)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, O-DU, O-CU).

Network nodes 15400 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. Network node 15400 may be a relay node or a relay donor node controlling a relay. Network nodes 15400 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 O-RAN access node) 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 15400 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-cel l/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

In particular embodiments, network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. In general, in a particular embodiment of network node 15400, processing circuitry 15402, memory 15404, communication interface 15406, and power source 15408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 15400.

The network node 15400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 15404 or portions of memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may be shared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 15400.

The processing circuitry 15402 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 components, such as the memory 15404, to provide network node 15400 functionality.

In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 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 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.

The memory 15404 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 nonvolatile, 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 15402. The memory 15404 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 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and/or any data received via the communication interface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.

The communication interface 15406 is used in wired or wireless communication of signaling and/or data with UEs, other network nodes, and/or any other network equipment. In the illustrated embodiment, communication interface 15406 comprises port(s)/terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 15300 may be capable of wireless communication and communication interface 15406 may also include radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments of radio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio front-end circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 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 15418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 15420 and/or amplifiers 15422. The radio signal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 15400 may be capable of wireless communication but does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).

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

The antenna 15410, communication interface 15406, and/or the processing circuitry 15402 may be configured to perform some or all of the receiving operations and/or obtaining operations described herein as being performed by the network node 15400. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and/or the processing circuitry 15402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 15400. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 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 15408. As a further example, the power source 15408 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 15400 may include additional components beyond those shown in Figure 10 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 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400.

Figure 11 is a block diagram illustrating a virtualization environment 15500 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 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a 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 15500 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.

Applications 15502 (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 15504 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 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508.

The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, 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, each of the VMs 15508 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 15508, and that part of hardware 15504 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 of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502.

Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization. Alternatively, hardware 15504 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 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 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 15512 which may alternatively be used for communication between hardware nodes and radio units.

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.

In some embodiments a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and/or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node e.g. Mobility Switching Centre (MSC), Mobile Management Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System (OSS), Self-Organizing Network (SON), positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT), etc.

In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

The embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and/or transmit signals (e.g. data) e.g. LTE, LTE FDD/TDD, WCDMA/HSPA, GSM/GERAN, Wi Fi, WLAN, CDMA2000 etc.

As will be readily understood by those familiar with communications design, functions means or modules may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and non-volatile memory. Other hardware, conventional and/or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Some embodiments herein:

A1. A method performed by a UE for handling communication in a wireless communication network, the method comprising

- obtaining a configuration comprising at least two time offsets; receiving a WUS from a radio network node at a first reception time instant; and monitoring a PDCCH at a second reception time instant, wherein the second reception time instant is based on a first time offset out of the at least two time offsets.

A2. The method according to embodiment A1, further comprising

- transmitting to the radio network node one or more capability indications indicating one or more preferred or supported time offsets or offset values.

A3. The method according to any of the embodiments A1-A2, wherein the at least two time offsets are associated with at least one of: a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc.

A4. The method according to any of the embodiments A1-A3, wherein the at least two time offsets are associated with at least one of a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type.

A5. The method according to any of the embodiments A1-A4, further comprising requesting to use the first time offset based on at least one of: a time offset capability of the UE (10), one or more time offset preferences, a DL latency requirement, an operating mode, an operating state, a timer value, a service type, and/or a reception type.

A6. The method according to any of the embodiments A1-A5, further comprising receiving a selection indication from the radio network node indicating the first time offset to use. A7. The method according to any of the embodiments A1-A6, further comprising

- determining the first time offset out of the at least two time offsets based on a PDCCH monitoring scenario.

B1. A method performed by a radio network node for handling communication in a wireless communication network, the method comprising

- transmitting to a UE, a configuration comprising at least two time offsets;

- transmitting a WUS to the UE at a first transmission time instant; and

- transmitting to the UE, a signal in a PDCCH at a second transmission time instant, wherein the second transmission time instant is based on a first time offset out of the at least two time offsets.

B2. The method according to embodiment B1, further comprising receiving from the UE one or more capability indications indicating one or more preferred or supported time offsets or offset values.

B3. The method according to any of the embodiments B1-B2, wherein the at least two time offsets are associated with a respective PDCCH monitoring context or scenario, a respective timer status, a short DRX mode or a long DRX mode, etc.

B4. The method according to any of the embodiments B1-B3, wherein the at least two time offsets are associated with a respective: DL latency requirement, operating mode, operating state, timer value, service type, and/or reception type.

B5. The method according to any of the embodiments B1-B4, further comprising

- determining to use the first time offset based on: a time offset capability of the UE 10, one or more time offset preferences, DL latency requirement, an operating mode, an operating state, a timer value, a service type, and/or a reception type.

B6. The method according to any of the embodiments B1-B5, further comprising

- transmitting a selection indication to the UE 10 indicating the first time offset to use.

B7. The method according to any of the embodiments B1-B6, further comprising - determining the first time offset out of the at least two time offsets based on a PDCCH monitoring scenario.

C1. A UE for handling communication in a wireless communication network, wherein the UE is configured to: obtain a configuration comprising at least two time offsets; receive a WUS from a radio network node at a first reception time instant; and monitor a PDCCH at a second reception time instant, wherein the second reception time instant is based on a first time offset out of the at least two time offsets.

D1. A radio network node for handling communication in a wireless communication network, wherein the radio network node is configured to: transmit to a UE, a configuration comprising at least two time offsets; transmit a WUS to the UE at a first transmission time instant; and transmit to the UE, a signal in a PDCCH at a second transmission time instant, wherein the second transmission time instant is based on a first time offset out of the at least two time offsets.

E1. A system comprising a UE according embodiment C1 and a radio network node according to embodiment D1.

References:

1. 3GPP TR 38.869, VO.4.0, “Study on low-power Wake-up Signal and Receiver for NR”, Aug. 2023.

2. RP-234056, New WID: Low-power wake-up signal and receiver for NR (LP WUS/WUR)

Claims

1. A method performed by a user equipment, UE, (10) for handling communication in a wireless communication network, the method comprising obtaining (302) a configuration comprising one or more time offsets, the one or more time offsets comprising a first time offset; receiving (303) a wake up signal, WUS, from a radio network node (12) at a first reception time instant; and monitoring (308) a physical downlink control channel, PDCCH, at a second reception time instant, wherein the second reception time instant is based on the first time offset relative to the first reception time instant.

2. The method according to claim 1 , further comprising transmitting (301) to the radio network node one or more UE indications indicating one or more preferred or supported time offsets.

3. The method according to any of the claims 1-2, wherein respective time offset out of the one or more time offsets is associated with at least one of: a respective PDCCH monitoring context or scenario; a respective timer status; and a short discontinuous reception, DRX, mode or a long DRX mode.

4. The method according to any of the claims 1-3, wherein respective time offset out of the one or more offsets is associated with at least one of a respective: downlink, DL, latency requirement; operating mode; operating state; timer value; service type; and/or reception type.

5. The method according to any of the claims 1-4, further comprising requesting (305) to use the first time offset based on at least one of: a time offset capability of the UE (10); one or more time offset preferences; a DL latency requirement; an operating mode; an operating state; a timer value; a service type, a time to start main receiver from a sleep state; and/or a reception type.

6. The method according to any of the claims 1-5, further comprising receiving (306) a selection indication from the radio network node (12) indicating the first time offset to use.

7. The method according to any of the claims 1-6, further comprising determining (307) the first time offset out of the one or more time offsets based on a PDCCH monitoring scenario.

8. The method according to any of the claims 1-7, wherein the one or more time offsets further comprises a second time offset, and the method further comprises monitoring, after a timer related to expected additional data arrival window has expired, the PDCCH at a third reception time instant that is based on the second time offset relative to the first reception time instant, which allows the UE (10) to go into a second sleep state.

9. The method according to any of the claims 1-8, wherein the one or more time offsets comprise at least two time offsets.

10. A method performed by a radio network node (12) for handling communication in a wireless communication network, the method comprising transmitting (402) to a user equipment, UE, (10) a configuration comprising one or more time offsets, the one or more time offsets comprising a first time offset; transmitting (403) a wake up signal, WUS, to the UE (10) at a first transmission time instant; and transmitting (407) to the UE (10), a signal in a physical downlink control channel, PDCCH, at a second transmission time instant, wherein the second transmission time instant is based on the first time offset relative to the first transmission time instant.

11. The method according to claim 10, further comprising receiving (401) from the UE (10) one or more UE indications indicating one or more preferred or supported time offsets.

12. The method according to any of the claims 10-11 , wherein respective time offset of the one or more time offsets is associated with a respective PDCCH monitoring context or scenario; a respective timer status; or a short DRX mode or a long DRX mode.

13. The method according to any of the claims 10-12, wherein respective time offset of the one or more time offsets is associated with a respective: downlink, DL, latency requirement; operating mode; operating state; timer value; service type, and/or reception type.

14. The method according to any of the claims 10-13, further comprising determining (405) to use the first time offset based on: a PDCCH monitoring scenario; a time offset capability of the UE (10); one or more time offset preferences; DL latency requirement; an operating mode; an operating state; a timer value; a service type; and/or a reception type.

15. The method according to any of the claims 10-14, further comprising transmitting (406) a selection indication to the UE (10) indicating the first time offset to use.

16. The method according to any of the claims 10-15, wherein the one or more time offsets comprise at least two time offsets.

17. A user equipment, UE, (10) for handling communication in a wireless communication network, wherein the UE (10) is configured to: obtain a configuration comprising one or more time offsets, the one or more time offsets comprising a first time offset; receive a WUS from a radio network node (12) at a first reception time instant; and monitor a PDCCH at a second reception time instant, wherein the second reception time instant is based on the first time offset relative to the first reception time instant.

18. The UE (10) according to claim 17, wherein the UE (10) is further configured to: transmit to the radio network node (12) one or more UE indications indicating one or more preferred or supported time offsets.

19. The UE (10) according to any of the claims 17-18, wherein respective time offset out of the one or more time offsets is associated with at least one of: a respective PDCCH monitoring context or scenario; a respective timer status; and a short discontinuous reception, DRX, mode or a long DRX mode.

20. The UE (10) according to any of the claims 17-19, wherein respective time offset out of the one or more time offsets is associated with at least one of a respective: downlink, DL, latency requirement; operating mode; operating state; timer value; service type; and/or reception type.

21. The UE (10) according to any of the claims 17-20, wherein the UE (10) is configured to request to use the first time offset based on at least one of: a time offset capability of the UE (10); one or more time offset preferences; a DL latency requirement; an operating mode; an operating state; a timer value; a service type, a time to start main receiver from a sleep state; and/or a reception type.

22. The UE (10) according to any of the claims 17-21 , wherein the UE (10) is configured to receive a selection indication from the radio network node (12) indicating the first time offset to use.

23. The UE (10) according to any of the claims 17-22, wherein the UE (10) is configured to: determine the first time offset out of the one or more time offsets based on a PDCCH monitoring scenario.

24. The UE (10) according to any of the claims 17-23, wherein the one or more time offsets further comprises a second time offset, and the wherein the UE (10) is configured to monitor, after a timer related to expected additional data arrival window has expired, the PDCCH at a third reception time instant that is based on the second time offset relative to the first reception time instant, which allows the UE (10) to go into a second sleep state.

25. The UE (10) according to any of the claims 17-24, wherein the one or more time offsets comprise at least two time offsets.

26. A radio network node (12) for handling communication in a wireless communication network, wherein the radio network node (12) is configured to: transmit to a user equipment, UE, (10) a configuration comprising one or more time offsets, the one or more time offsets comprising a first time offset; transmit a wake-up signal, WUS, to the UE (10) at a first transmission time instant; and transmit to the UE (10), a signal in a physical downlink control channel, PDCCH, at a second transmission time instant, wherein the second transmission time instant is based on the first time offset relative to the first transmission time instant.

27. The radio network node (12) according to claim 26, wherein the radio network node (12) is configured to receive from the UE (10) one or more UE indications indicating one or more preferred or supported time offsets.

28. The radio network node (12) according to any of the claims 26-27, wherein respective time offset of the one or more time offsets is associated with a respective PDCCH monitoring context or scenario; a respective timer status; or a short DRX mode or a long DRX mode.

29. The radio network node (12) according to any of the claims 26-28, wherein respective time offset of the one or more time offsets is associated with a respective: downlink, DL, latency requirement; operating mode; operating state; timer value; service type, and/or reception type.

30. The radio network node (12) according to any of the claims 26-29, wherein the radio network node (12) is configured to determine to use the first time offset based on: a PDCCH monitoring scenario; a time offset capability of the UE (10); one or more time offset preferences; DL latency requirement; an operating mode; an operating state; a timer value; a service type; and/or a reception type.

31. The radio network node (12) according to any of the claims 26-30, wherein the radio network node (12) is configured to transmit a selection indication to the UE (10) indicating the first time offset to use.

32. The radio network node (12) according to any of the claims 26-31 , wherein the one or more time offsets comprise at least two time offsets.

33. A system comprising a user equipment according to any of the claims 17-25 and a radio network node according to any of the claims 26-32.

34. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-16, as performed by the UE (10) or the radio network node (12), respectively.

35. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-16, as performed by the UE (10) or the radio network node (12), respectively.