User equipment and method in a wireless communications network

Abstract

A method performed by a User Equipment, UE, for handling a Wake Up Signal, WUS, in a wireless communications network. The UE receives (501) a WUS message. The UE decodes (502) the WUS message. The decoding comprises determining whether a subgroup identifier, ID, comprised in the WUS message is related to the UE. Interpretation of the subgroup ID is based on whether the UE is operating in a connected mode or in an idle and / or inactive mode. When determined that the subgroup ID is related to the UE, the UE activates (503) a main receiver and performing a first action associated to receiving the WUS message.

Description

[0001] USER EQUIPMENT AND METHOD IN A WIRELESS COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a User Equipment (UE) and method therein. In some aspects, they relate to handling Wake Up Signal (WUS) in a wireless communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] Wake-up receiver (WUR), sometimes also referred to as ‘wake-up radio’, is about enabling a low power receiver in UEs, which, in case of the detection of a wake-up signal (WUS), wakes up the main, e.g., baseband and / or higher power, receiver to detect an incoming message, typically paging, e.g., Physical Downlink Control Channel (PDCCH) in paging occasions (PO), scheduling the paging message on Physical Downlink Shared Channel (PDSCH). The main benefit of employing WUR is lowering energy consumption and longer device battery life, or at a fixed energy consumption the downlink latency can be reduced, e.g., shorter DRX / duty-cycles and more frequent checks for incoming transmissions. Figure 1 shows an illustration of a location of a WUS and the paging occasion to which it is associated.

[0010] WUS for NB-loT and LTE-M

[0011] Release 15 (Rel-15)

[0012] In Rel-15 WUS was specified for Narrowband Internet of Things (NB-loT) and LTE- M. The main motivation was UE energy consumption reduction since with the coverage enhancement PDCCH could be repeated many times and the WUS is relatively much shorter and hence requires less reception time for the UE. The logic is that a UE would check for a WUS a certain time before its PO, and only if a WUS is detected the UE would continue to check for PDCCH in the PO, and if not, which is most of the time, the UE can go back to a sleep state to conserve energy. Due to the coverage enhancements the WUS can be of variable length depending on the UE’s coverage. Figure 2 shows an illustration of WUS for NB-loT and LTE-M.

[0013] A WUS is based on the transmission of a short signal that indicates to the UE that it should continue to decode the DL control channel e.g., full Narrowband PDCCH (NPDCCH) for NB-loT. If such signal is absent, Discontinuous Transmission (DTX) i.e., the UE does not detect it, then the UE can go back to sleep without decoding the DL control channel. The decoding time for a WUS is considerably shorter than that of the full NPDCCH since it essentially only needs to contain one bit of information whereas the NPDCCH may contain up to 35 bits of information. This, in turn, reduces UE power consumption and leads to longer UE battery life. The WUS would be transmitted only when there is a paging for the UE. But if there is no paging for the UE then the WUS will not be transmitted, i.e., implying a DTX, and the UE would go back to deep sleep e.g., upon detecting DTX instead of WUS. This is illustrated in Figure 1 , where white blocks indicate possible WUS and PO positions whereas the black boxes indicate actual WUS and PO positions.

[0014] The specification of Rel-15 WUS is spread out over several parts of the LTE 36- series standard, e.g., 3GPP TS 36.211 V17.4.0, 3GPP TS 36.213 V18.0.0, 3GPP TS 36.304 V17.4.0 and 3GPP TS 36.331 V17.6.0.

[0015] A UE will report its WUS capability to the network, and WUS gap capability, see below. Further WUS information was added to the paging message and / or request from a Mobility and Management Entity (MME) to an eNB, see UE radio paging capabilities, an eNB will use WUS for paging the UE IFF 1) WUS is enabled in the cell, i.e., WUS-Config present in SI, and 2) the UE supports WUS according to the wakeUpSignal-r15 UE capability, see also the description of WUS gap below.

[0016] WUS was introduced for both LTE-M and NB-loT with support for both Discontinuous Reception (DRX) and extended DRX (eDRX), the former with a 1-to-1 mapping between the WUS and the PO, and for the latter in an addition with the possible configuration of 1-to-N, 1-to-many, POs. an eNB may configure one WUS gap for UEs using DRX, and another one for UEs using eDRX:

[0017] The UE capabilities may also indicate the minimum WUS gaps required for the UE be able to decode PDCCH in the associated PO, for DRX and eDRX, respectively:

[0018] At the end of Rel-15, a longer WUS gap of 1 s or 2s was introduced to enable the use of WUR. That is, starting up the main baseband receiver if a WUR is used for the detection of WUS may take longer time. If this is supported in the cell, eNB would include timeOffset-eDRX-Long in the WUS-Config in SI, see above. In 3GPP TS 36.304 V17.4.0 the UE behavior for monitoring paging with WUS is specified, and in Table 7.4-1 it is indicated which WUS time gap the UE, and eNB, should apply depending on the reported UE capability:

[0019] In essence, the UE will only use WUR, or timeOffset-eDRX-Long, if it is capable of starting up the main receiver as quickly as indicated by the value used in SI. If not, it will fall back to using timeOffset-eDRX-Short, without WUR. Figure 3 shows an illustration of the use of eDRX and DRX WUS gaps for NB-loT and LTE-M.

[0020] Since UEs share PO, the eNB may, in the worst case, have to transmit up to 3 WUSs for one PO. I.e. corresponding to timeoffsetDRX, timeoffset-eDRX-Short, and timeoffset-eDRX-Long. WUS UE grouping objective in Rel-16

[0021] In the Rel-16 Work Item Description (WID), it was agreed that WUS should be further developed to also include UE grouping, such that the number of UEs that are triggered by a WUS is further narrowed down to a smaller subset of the UEs that are associated with a specific PO: The objective is to specify the following set of improvements for machine-type communications for Bandwidth reduced Low complexity (BL) and / or Coverage Enhanced (CE) UEs.

[0022] Improved DL transmission efficiency and / or UE power consumption:

[0023] • Specify support for UE-group WUS [RAN1 , RAN2, RAN4]

[0024] The purpose is to reduce the false paging rate, i.e., avoid that a given UE is unnecessarily woken up by a WUS transmission intended for another UE. This feature is referred to as Rel-16 group WUS, or GWUS. However, this is not directly related to WUR and will not further be explained here.

[0025] Rel-17 NR PEI

[0026] In Rel-17 discussions started on introducing a WUS for NR, then called ‘Paging Early Indication’ (PEI). However, since at the time no coverage enhancement was specified for NR, the only gain for Rel-17 PEI was for scenarios where a small fraction of UEs are in bad coverage and with large synchronization error due to the use of longer DRX cycles. The gain for such UEs were that with the use of PEI they would typically only have to acquire one Synchronization Signal Block (SSB) before decoding PEI, instead of up to 3 SSBs if PEI is not used. So, for most UEs, Rel-17 PEI will result in gains or increased performance.

[0027] Rel-17 PEI will also support UE grouping for false paging reduction, similar to the Rel-16 GWUS above, which will have some gains at higher paging load.

[0028] In RAN#93e it was agreed that PEI will be PDCCH-based, as seen below, making it much less interesting for WUR, i.e., the main baseband receiver is required for decoding PEI.

[0029] Rel-18 NR WUR

[0030] In Rel-18, there has been rather large interest to introduce WUR for NR. 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 main receiver. Therefore, the main difference to Rel-17 PEI is that the WUS in Rel-18 should not be PDCCH-based and allow for a simpler and low power receiver, i.e., WUR with simple modulation and detection techniques, e.g., using on-off keying (OOK) modulation and non-coherent 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 (RP-213645):

[0031]

[0032] For more details on e.g. suggestions on WUR architecture and design, receiver power vs. sensitivity trade-off see e.g., RP-212005, RP-212254, RP-212367, and RP- 212427 which were submitted to RAN3#93-e.

[0033] The benefit of WUR is to reduce the energy consumption of the receiver, such that unless there is any paging and data for the UE it can remain in a power saving state. This will extent the battery life of the device, or alternatively enable shorter downlink latency, e.g., shorter DRX, at a fixed battery life. For short-range communication, the WUR power can be low enough, e.g., ~3 uW, that this can even, in combination with energy harvesting, enable that the WUR is continuously on, i.e., DRX or duty-cycling is not used without the need for a battery. This can be considered as a key enabler of battery-less devices towards 6G.

[0034] 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, V1.0.0, “Study on low-power Wake-up Signal and Receiver for NR”. According to the outcome of this study, one important aspect of designing WUR / WUS is synchronization, called low power sync signal (LP-SS), as highlighted below:

[0035] IEEE WUR

[0036] In Institute of Electrical and Electronics Engineering (IEEE), the support for WUR has been specified to a greater extent than in 3GPP. That is, the focus was on low power WUR from start and the design uses WUR not only for receiving the WUS but also other control signals and signalling, such as synchronization and mobility information. This allows the stations, corresponding to UEs in 3GPP, to only use the WUR when there is no user-plane data transmission ongoing.

[0037] Similar to the 3GPP solution, the use of WUR is only enabled in stations and not in access points (APs), that is for downlink communication only. The AP advertises that it has WUR operation capability, along with WUR configuration parameters, among other info, in which band / channel WUR is operational, which can be different from the band / channel used for data transmission using the main receiver, e.g. WUR in 2.4 GHz band but data communication in 5 GHz band. Also note that he WUR operating channel is advertised in the beacon, and that the WUR discovery operating channel may be different from the WUR operating channel. Stations can then request to be configured with WUR mode of operation. This request has to be granted by the AP, and in case it is granted, the station is further configured / setup for WUR mode of operation. The configuration is only valid for the connection to the associated AP, and further the configuration must be torn down / de-configured if WUR is not be used anymore. Both continuous WUR, receiver open all the time, and duty-cycled WUR, receiver only open during preconfigured time slots, mode of operations are supported. For the latter the length of the duty-cycles and on-time during wake up is part of the WUR configuration.

[0038] Unlike the 3GPP solution, the WUR operation mode is a “sub-state” of the regular operation and upon the detection of a WUS transmission from the AP, the station will resume the power saving mechanism it was configured with before entering the WUR operation mode. That is, IEEE has specified a number of different power saving mechanisms, and for example if duty-cycled monitoring of the downlink has been configured for the station it will switch to that upon detection of the WUS, i.e., unlike the specified 3GPP mechanism which only covers paging, and the UE will continue to monitor PDCCH if WUS is detected.

[0039] A station receiving the IEEE WUS must synchronize to the wireless medium prior to performing any transmissions, i.e. using sync info in the beacon from the AP, typically transmitted every 100ms, or from the transmission to another station. Synchronization to the wireless medium refers to the following in IEEE 802.11 ; a station changing from sleep to awake in order to transmit must perform channel clear assessment until it receives one or more frames that allow it to correctly set the virtual carrier sensing. This is to prevent collisions with transmissions from hidden nodes. Essentially the virtual carrier sensing tells a station to defer for a time period even if the wireless medium appears to be idle, and can be set by receiving frames that indicate the duration of an ongoing frame exchange. Note that in WiFi typically one beacon transmission is enough to sync for the station, i.e., no need to acquire several transmissions due to poor coverage. Unlike operation in licensed bands, the station also has to apply carrier sensing, and also possibly re-acquire channel sensing parameters, before uplink transmission.

[0040] The physical WUS in IEEE contains complete frames which much be processed by the station. The drawback with this design is that is requires more processing and handling and processing in the station, i.e., compared to a simple WUR design which trigger one pre-defined activity in case WUS is detected. The benefit is that it contains more information, and the solution is more general. The IEEE WUS contains information to indicate if the WUS is a WUR sync beacon), a WUR discovery beacon, or a regular WUS intended to wake the station up. The WUS can also contain proprietary frames, which could e.g., be used to directly turn actuators on / off. The transmission uses OOK modulation, using Manchester coding, but is using multi-carrier OOK which can be generated by an (Orthogonal Frequency Division Multiplexing (OFDM) transmitter, i.e., WUR can be enabled as a software upgrade in APs. The WUS is 4 MHz wide, but a whole 20 MHz channel is reserved. The WUS starts with a 20 MHz legacy preamble (to allows other stations to perform carrier sense) followed by 4 MHz Manchester coded OOK. Two data rates are supported: 62.5 kbps and 250 kbps, and link adaptation is up to the AP. Each packet is self-contained and includes the data rate, i.e., in the WUR there are two possible sync words used to signal the data rate.

[0041] The WUS can contain the following information:

[0042] • Station ID, or group ID, grouping of stations is supported.

[0043] • Payload up to 22 bytes.

[0044] • Short frames contain only basic info; which WUR frame type + addressing.

[0045] • Ordinary frames contain control info, and in addition proprietary info. WUR beacons contain basic service set (BSS) ID, sync information, time counter.

[0046] • Similar structure for WUS and WUR beacons,. Sync words indicate the data rate, the station can then detect the header, from this the station can tell if it is WUS or beacon, then check body.

[0047] • WUR discovery frames contain mobility related information to allow for lower power scan.

[0048] Regarding mobility, both WUR sync beacons and WUR discovery beacons has been specified, which only requires the WUR to be used for reception, such that stations can stay in the WUR operation mode unless there is data transmission for the station. I.e., stations only need to switch back to legacy PSM upon WUS detection, or when moving to a new AP. WUR sync beacons are used by stations to obtain rough synchronization, for data transmission the legacy beacon must still be acquired, and WUR discovery beacons are used to carry, e.g., legacy, mobility information to enable quick and / or low energy scanning, allowing stations, only using the WUR, to get information related to local and roaming scans for nearby APs, e.g. Service Set ID (SSID) and main radio operating channels, if the channel quality should deteriorate.

[0049] That is, in the WUR discovery beacon the AP can indicate one or more BSS, and the BSS-ID has a one-to-one mapping with the assigned SSID name, in which WUR is supported such that stations do not have to scan all frequencies and / or channels. Since the WUR discovery beacon contains the legacy mobility information, which means there is some duplication and / or redundancy in the broadcasted information. This allows for low power scanning, using only the WUR. Note however that mobility in IEEE is restricted to the same AP, and that hand-over between APs etc. is not supported in the same way as in 3GPP. If a station in WUR operation mode moves to a new AP, it would have to move out of WUR operation mode and use the main receiver to obtain the beacon, sync, configuration, and associate to the new AP.

[0050] Energy consumption vs. latency trade-off

[0051] An important trade-off in WUR design and operation is energy consumption versus latency. For example, to achieve a minimum latency, WUR may need to be always on to continuously monitor for downlink transmissions, e.g., WUS. The average power consumption can be reduced by relaxing latency and allowing the WUR to go to sleep modes. SUMMARY

[0052] An object of embodiments herein is to improve the performance of a UE operating in a wireless communications network by reducing false paging.

[0053] According to a first aspect of embodiments herein, the object is achieved by a method performed by a UE for handling a WUS in a wireless communications network.

[0054] The UE receives a WUS message.

[0055] The UE decodes the WUS message. The decoding comprises determining whether a subgroup identifier (ID) comprised in the WUS message is related to the UE. The interpretation of the subgroup ID is based on whether the UE is operating in a connected mode or in an idle and / or inactive mode.

[0056] When determined that the subgroup ID is related to the UE, the UE activates a main receiver and performs a first action associated to receiving the WUS message.

[0057] According to a second aspect of embodiments herein, the object is achieved by a UE configured to handle a WUS in a wireless communications network.

[0058] The UE is configured to receive a WUS message.

[0059] The UE is configured to decode the WUS message. The UE is further configured to decode the WUS message by determining whether a subgroup ID adapted to be comprised in the WUS message is related to the UE. The UE is further configured to interpretate the subgroup ID based on whether the UE is operating in a connected mode or in an idle and / or inactive mode.

[0060] When determined that the subgroup ID is related to the UE, the UE is configured to activate a main receiver and perform a first action associated to receiving the WUS message.

[0061] Embodiments herein target to handle UE actions when receiving a WUS message, upon receiving the WUS message, the UE decodes the WUS message, interprets the subgroup ID, and determines whether a subgroup ID in the WUS message corresponds to a subgroup ID is related to the UE, and performs an action.

[0062] Embodiments herein bring the advantage of an efficient mechanism for handling WUS, the same WUS design may be used for UEs operating in both connected mode and idle / inactive mode. This is achieved by applying an interpretation of the subgroup ID the is based on whether the UE operates in connected mode or idle / inactive mode. This leads to reducing the risk of false paging, resulting in an improved performance of UEs operating in the wireless communication network. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Examples of embodiments herein are described in more detail with reference to the accompanying drawings, according to the following description.

[0064] Figure 1 is a schematic diagram illustrating WUS and paging occasion according to prior art.

[0065] Figure 2 is a schematic diagram illustrating WUS for NB-loT and LTE-M according to prior art.

[0066] Figure 3 is a schematic diagram illustrating eDRX and DRX WUS gaps for NB-loT and LTE-M according to prior art.

[0067] Figure 4 is a schematic block diagram illustrating embodiments of a wireless communications network.

[0068] Figure 5 is a flowchart depicting embodiments of a method in a UE.

[0069] Figure 6 is a schematic block diagram illustrating a non-limiting example of a UE according to embodiments herein.

[0070] Figure 7 shows an example of a communication system QQ100 in accordance with some embodiments.

[0071] Figure 8 shows a UE QQ200 in accordance with some embodiments.

[0072] Figure 9 shows a network node QQ300 in accordance with some embodiments.

[0073] Figure 10 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 8, in accordance with various aspects described herein.

[0074] Figure 11 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.

[0075] Figure 12 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

[0076] DETAILED DESCRIPTION

[0077] As a part of developing embodiments herein the inventors identified a problem which first will be discussed.

[0078] The Rel-18 study item on Low Power (LP) WUS and WUR is coming to an end and the scope of the subsequent Rel-19 work item (Wl) has been started to be discussed. For the Rel-19 Wl, there is a split view if LP-WUS / WUR should be supported only in RRC Idle / lnactive, or if also support in RRC Connected should be supported. The proponents of supporting both Idle / lnactive and Connected are claiming a common / joint LP-WUS design applicable to both Idle / lnactive and Connected mode and mean the Rel-19 scope wouldn’t necessarily become that much larger. However, there are several aspects for such a joint design that requires solutions.

[0079] It has been concluded that it may be beneficial for the LP-WUS to contain UE subgroup information, similar to Rel-15 WUS for NB-loT / LTE-M and Rel-17 PEI. That is, a UE would only be woken up to start the main receiver for monitoring PDCCH if not only the LP-WUS is detected but also the UE subgroup therein matches the UE’s subgroup. This may have the advantage that it minimizes the false paging, i.e., that UE is unnecessarily woken up by paging for another UE, which improves the UE power saving by employing LP-WUS. According to embodiments herein, a method performed by a UE is provided. The UE applies different interpretations or use of the UE subgrouping in LP- WUS, depending on if the UE is in RRC Idle / lnactive or in RRC Connected.

[0080] Figure 4 is a schematic overview depicting a wireless communications network 100, wherein embodiments herein may be implemented. The wireless communications network 100 comprises one or more RANs and one or more CNs. The wireless communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0081] Network nodes, such as a network node 110, operate in the wireless communications network 100. Each of the network nodes e.g. provides a number of cells and may use these cells for communicating with other network nodes. Each of the network nodes may be a transmission and reception point e.g. a network node, a radio access network node such as a base station, a radio base station, a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR / g Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE served by the network node depending e.g. on the radio access technology and terminology used. UEs, such as a UE 121 , operate in the wireless communications network 100. The UE 121 may e.g. be an NR device, a mobile station, a wireless terminal, an internet of things (loT) device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to-everything (V2X) device, Vehicle-to- Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to-lnfrastructure (V2I) device, a Vehicle-to-Network (V2N) device, a Wi-Fi device, an LTE device, a non- access point (non-AP) STA, a STA, that communicates via a base station, and one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that the term UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0082] Methods herein may in one aspect be performed by the UE 121. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Figure 1 , may be used for performing or partly performing the methods of embodiments herein.

[0083] The cloud 190 may comprise a cloud network infrastructure. A cloud network infrastructure may e.g. be a collection of hardware and software elements such as computing power, networking, storage, and virtualization resources needed to enable cloud computing in a wireless communications network such as e.g. a communications network.

[0084] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0085] A method according to embodiments will now be described from the view of the UE 121 together with Figure 5. Figure 2 depicts example embodiments of a method performed by the UE 121 for handling a WUS in the wireless communications network 100. The UE 121 may e.g., comprise a WUR and a main receiver. The WUR may e.g., be used for monitoring for, and receiving, WUS, such as WUS messages. When operating in a connected mode, the UE 121 may be configured with an OFDM-based WUR and / or an envelope detection based WUR, e.g., a on OOK-based WUR. The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0086] Action 501 The UE 121 receives a WUS message. The WUS message may e.g., be received from the network node 110. The WUS message may e.g., be received using the WUR.

[0087] Action 502

[0088] The UE 121 decodes the WUS message. The decoding comprises determining whether a subgroup ID comprised in the WUS message is related to the UE. The interpretation of the subgroup ID is based on whether the UE 121 is operating in a connected mode or in an idle and / or inactive mode. In other words, by decoding the WUS message, the UE 121 may be able to obtain the subgroup ID comprised in the WUS message. The UE 121 uses the subgroup ID comprised in the WUS message to determine if the subgroup ID, and consequently the WUS message, is related to the UE 121. Depending on whether the UE 121 operates in a connected mode or an idle and / or inactive mode, the UE 121 may interpret the obtained subgroup ID differently.

[0089] In some embodiments, the subgroup ID comprised in the WUS message is used both when the UE 121 is operating in a connected mode and when the UE 121 is operating in an idle and / or inactive mode. The subgroup ID may be interpreted according to any one out of:

[0090] - When the UE 121 operates in a connected mode, the subgroup ID is interpreted in relation to a dedicated Radio Access Network, RAN, subgroup ID explicitly assigned to the UE 121 . This may e.g., mean that the subgroup ID is interpreted in relation to a subgroup ID explicitly assigned to the UE 121 by the RAN, such as e.g., the network node 110.

[0091] - When the UE 121 operates in an idle and / or inactive mode, the subgroup ID may be interpreted in relation to a subgroup ID implicitly assigned to the UE 121 and / or a Core Network, CN, configured explicitly assigned subgroup ID. This may e.g., mean that the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE 121 by the RAN, such as e.g., the network node 110. Alternatively, it may e.g., mean that the subgroup ID is interpreted in relation to a subgroup ID explicitly configured to the UE 121 by the CN, or a CN node.

[0092] Thus, the some WUS, and subgroup ID comprised in the WUS message, may be used for both UEs operating in connected mode and UEs operating in an idle and / or connected mode. This since the interpretation of the subgroup ID depends on the mode the UE is operating in.

[0093] In some embodiments, the UE 121 determines whether the decoded subgroup ID is related to the UE 121 by comparing the decoded subgroup ID with a subgroup ID assigned to UE 121 . It is determined that the decoded subgroup ID is related to the UE 121 when the decoded subgroup ID matches the subgroup ID assigned to the UE 121 . As mentioned above, the UE 121 may be assigned a subgroup in different ways, depending on whether the UE 121 operates in a connected mode or an idle and / or inactive mode.

[0094] In some embodiments, the subgroup ID comprised in the WUS message is scrambled with a Radio Network Temporary Identifier (RNTI), such as a Power Saving RNTI (PS-RNTI) and / or a Cell RNTI (C-RNTI). The UE 121 is configured with an RNTI for WUS reception. The subgroup ID may e.g., be scrambled with the RNTI by the network node 110 transmitting the WUS message. Whether the UE 121 is able to decode the WUS message correctly, may depend on if the RNTI the subgroup ID is scrambled with is the same RNTI as the RNTI the UE 121 is configured with. Thus, if the subgroup ID is scrambled with the same RNTI as the RNTI the UE 121 is configured with, the UE 121 will be able to decode the WUS message correctly.

[0095] In some embodiments, the WUS message further comprises a Cyclic Redundancy Check (CRC). At least one out of the subgroup ID and the CRC is scrambled with an RNTI. The UE 121 is configured with an RNTI for WUS reception. As mentioned above, the RNTI may e.g., comprise a PS-RNTI and / or a C-RNTI. And whether the UE 121 is able to decode the WUS message correctly, may depend on if the RNTI the subgroup ID and / or the CRC is scrambled with is the same RNTI as the RNTI the UE 121 is configured with. Thus, if the subgroup ID and / or the CRC is scrambled with the same RNTI as the RNTI the UE 121 is configured with, the UE 121 will be able to decode the WUS message correctly.

[0096] In some embodiments, the UE 121 decodes the WUS message by decoding the WUS message using the configured RNTI. The subgroup ID in the WUS message is related to the UE 121 when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE 121 . As mentioned above, the subgroup ID may e.g., be scrambled with the RNTI by the network node 110 transmitting the WUS message. Whether the UE 121 is able to decode the WUS message successfully, may depend on if the RNTI the subgroup ID is scrambled with is the same RNTI as the RNTI the UE 121 is configured with. If the subgroup ID is scrambled with the same RNTI as the RNTI the UE 121 is configured with, the UE 121 will be able to decode the WUS message correctly. If the UE 121 is unable to successfully decode the WUS message, this may be because the RNTI used to scramble subgroup ID is not the RNTI that the UE 121 is configured with. In that case, the UE 121 may determine that the subgroup ID comprised in the WUS message is not related to the UE 121 . When the UE 121 successfully decodes the WUS message, i.e., the RNTI used to scramble the subgroup ID is the same RNTI the UE 121 is configured with, the UE 121 may determine that the subgroup ID comprised in the WUS message is related to the UE 121 when it matches the subgroup ID assigned to the UE 121. If the subgroup ID comprised in the WUS message does not match the subgroup ID assigned to the UE 121 , the UE 121 may determine that the subgroup ID comprised in the WUS message is not related to the UE 121 .

[0097] When operating in a connected mode, the interpretation of the subgroup ID may further depend whether the UE 121 is configured with an OFDM-based WUR and / or an envelope detection based WUR, e.g., a on OOK-based WUR. Some examples of this is described further below.

[0098] E.g., one bit in the WUS message, such as one bit on the subgroup ID, may indicate whether the WUS message is intended for UEs configured with an OOK-based WUR or an OFDM-based WUR. This may e.g., mean that the UE 121 should ignore the WUS message if it is intended for a type of WUR the UE 121 is not configured with. That is, when the UE 121 is configured with OFDM-based WUR, the UE 121 should ignore the WUS message if it is intended for UEs configured with OOK-based WUR. Correspondingly, when the UE 121 is configured with OOK-based WUR, the UE 121 should ignore the WUS message if it is intended for UEs configured with OFDM-based WUR.

[0099] Action 503

[0100] When determined that the subgroup ID is related to the UE 121 , the UE 121 activates a main receiver and performs a first action associated to receiving the WUS message. The first action may e.g., comprise monitor a PDCCH and / or PDSCH in a subsequent paging occasion and / or a subsequent DRX-on duration.

[0101] When determined that the subgroup ID is not related to the UE 121 , the UE 121 may refrain from activating the main receiver. The UE 121 may further continue to monitor for receiving a further WUS, e.g., continuously, in the same WUS occasion and / or in a subsequent WUS occasion.

[0102] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above, such as any of the Actions 501-503.

[0103] For Rel-16 GWUS for NB-loT / LTE-M and for Rel-17 PEI for NR, UE subgrouping information is indicated in the WUS for UEs in Idle mode, and also Inactive mode for PEI, using multiple WUS-sequences or subgrouping bits in downlink control information (DCI) format 2_7, respectively. For Rel-16 DCP, DCI format 2_6, UE subgrouping is dealt with differently since the UE is in Connected mode, and it is configured with a PS-RNTI for monitoring the PDCCH-based WUS, DCI format 2_6. How to configure the PS-RNTI is up to gNB implementation; if multiple UEs are configured with a PS-RNTI, all these UEs will belong to the same WUS subgroup. However, if only a single UE is configured with a PS- RNTI, the UE has a dedicated WUS resource and there will be no false paging, i.e., the UE is alone in its subgroup.

[0104] Reusing the same LP-WUS design for both ldle / 1 nactive mode and connected mode for Rel-18 / 19 LP-WUS / WUR puts new requirements on how the WUS UE subgrouping is carried out.

[0105] According to some examples of embodiments herein, for a UE, such as the UE 121 , operating in Idle / lnactive mode, the subgrouping indication in LP-WUS, such as the subgroup ID comprised in the WUS message, is matched against an implicit and / or CN configured explicit assigned UE subgroup, e.g., a RAN assigned implicit UE_ID group and / or a CN assigned explicit subgroup for Rel-15 GWUS for NB-loT / LTE-M or Rel-17 PEI. For the UE 121 , when operating in connected mode, however, this subgrouping indication, e.g., the subgroup ID comprised in the WUS message, is reinterpreted to instead be matched against a dedicated RAN subgroup identifier explicitly configured for the UE.

[0106] For example, if 2 bits are used for subgrouping indication in the LP-WUS, there will be 4 subgroups in total. If an implicit UE_ID based subgroup assignment is used in Idle / lnactive mode, in a simple example the UE 121 with UE_ID=5974903 would then be in subgroup 3, UE_ID modulo 4. The subgrouping indication in LP-WUS can indicate {0, 1 , 2, 3} and only in case it indicates 3 the UE in the example will wake up the main receiver and continue to monitor PDCCH and / or PDSCH in the paging occasion, such as performing the first action. When the UE 121 moves to Connected mode, the UE is instead configured explicitly with a subgroup as part of the Connected LP-WUS / WUR configuration. In this example, a gNB, such as the network node 110, assigns the UE 121 to subgroup=2 since this is at the time the subgroup containing the fewest UEs. When the UE then monitors the Connected LP-WUS monitoring occasion before a DRX on-duration. The UE 121 will only start up the main receiver to monitor PDCCH during the on-duration (drx-onDurationTimer), such as performing the first action, if the received LP-WUS indicates subgroup 2.

[0107] According to some examples of embodiments herein, for a WUR operation in Connected mode, the subgrouping indication in LP-WUS is considered or interpreted with respect to a dedicated RAN subgroup identifier explicitly configured for the UE 121 , i.e., the UE 121 will wake up the main receiver to monitor PDCCH, such as performing the first action, if the subgrouping indication matches with the dedicated RAN subgroup identifier explicitly configured for the UE 121.

[0108] According to some examples of embodiments herein, when the UE 121 operates in Idle / lnactive, the subgrouping indication in LP-WUS replaces an implicit and / or CN configured explicit assigned UE subgroup. When the UE 121 operates in Connected mode, however, this subgrouping indication replaces a dedicated RAN subgroup identifier explicitly configured for the UE.

[0109] According to some examples of embodiments herein, for WUR operation in Connected mode, a WUS payload, such as a payload of the WUS message, comprises the subgrouping indication and / or a CRC. The subgrouping indication and / or the CRC is scrambled by a specific RNTI. The UE 121 operating with WUR in Connected mode is configured with an RNTI for the WUS reception. The UE 121 WUR when monitoring WUS uses the configured RNTI, and it wakes up, such as activates, the main receiver only if the received subgrouping indication after decoding using the configured RNTI matches with the dedicated RAN subgroup identifier explicitly configured for the UE 121 . In this way, the check is a 2-step check: Both the used RNTI and the subgroup indicated in the payload must match if the UE is to wake up, such as activate, the main receiver and continue to decode PDCCH, such as perform the first action. This may be applicable where an RNTI is configured to more than one UE, e.g., as for PS-RNTI in Rel-16 DCP.

[0110] According to some examples of embodiments herein, a UE, such as the UE 121 , configured with an envelope detection based WUR, e.g., OOK-based, may reinterpret the subgrouping bits in Connected mode according to the previous indication, whereas a UE, such as the UE 121 , configured with an OFDM-based WUR may be configured with an RNTI for the monitoring of LP-WUS in Connected mode, e.g., similar to PS-RNTI, or the dedicated C-RNTI already configured to the UE could be reused, and the subgrouping indication in LP-WUS is reinterpreted and used for any or more out of the following:

[0111] • Additional subgrouping information. E.g., the OFDM-based WUR UE 121 is assigned both an RNTI and a subgroup, and only if it receives LP-WUS scrambled with the assigned RNTI which comprises the UEs assigned subgroup it will start up the main receiver. This may be relevant if the RNTI is not UE-specific, e.g. a shared PS-RNTI rather than dedicated C-RNTI. • Increased detection performance. I.e., the OFDM-based WUR UE 121 reinterprets the subgrouping bits as bits encoded to increase LP-WUS detection performance, e.g., using time repetition coding and a different redundancy version of the LP- WUS.

[0112] • Synchronization sequence.

[0113] • Cell ID.

[0114] • WUS time offset indication. E.g., the time offset from the WUS monitoring occasion to when the UE 121 should start monitoring PDCCH may be indicated dynamically pointing to a table of preconfigured values. E.g.:

[0115] • WUR PDCCH monitoring window. E.g., the length of the PDCCH monitoring window, similar to drx-onDurationTimer, may be indicated dynamically to the UE 121 using a pre-configured table. E.g.:

[0116] • Common WUS. E.g., an indication to wake up all UEs receiving the WUS message.

[0117] • Secondary Cell (SCell) dormancy indication, see e.g., DCI format 2_6.

[0118] • Subgrouping indication in LP-WUS may be reinterpreted as additional information for WUR operation. E.g., information related to WUR duty cycle configurations, WUR ON duration, or WUR deactivation can be conveyed. This may be useful to e.g., disable WUR monitoring for a UE in case LP-WUS has reduced coverage compared to legacy PDCCH, and the UE is moving out of LP-WUS coverage. For instance, in the following table different WUR operation modes are indicated:

[0119] The Subgrouping indication in LP-WUS may be reinterpreted for any combinations of the aforementioned usages. For example, a joint indication of the WUR time offset and PDCCH monitoring window may be considered.

[0120] Note that in at least some of the examples of embodiments above, if OOK-based WUR UEs and OFDM-based WUR UEs share the same WUS monitoring occasions, the gNB, such as the network node 110 may have to consider the wake-up of OOK-based WUR UEs, and the possible misinterpretation for OFDM-based WUR UEs. This may however be left to network implementation.

[0121] According to some examples of embodiments herein, one bit in the LP-WUS indicates whether the LP-WUS is intended for OOK-based WUR UEs or OFDM-based WUR UEs, and LP-WUS should be ignored by the UE with the type of WUR it is not intended for. In one example, e.g., the first bit in the OOK-modulated LP-WUS indicates if the LP-WUS is intended for OOK-based WUR or not. OFDM-based WUR UEs may either check the same bit, implementing OOK reception for this part, or a separate bit may be introduced in the OFDM-modulated payload.

[0122] Note that for the examples of embodiments herein, the WUS monitoring occasions must not be shared between Idle / I nactive WUR UEs and Connected WUR UEs.

[0123] In the examples of embodiments below, the following is assumed: the UE uses the same or a different subgroup for an indication to wake up the main receiver regardless of whether it is in idle / inactive or connected mode. The subgroup(s) may be assigned implicitly and / or explicitly via CN configuration or dedicated signaling if the UE is in connected mode.

[0124] According to some examples of embodiments herein, the network, e.g., the network node 110 or an CN node, configures time offset value(s) with respect to the paging occasions in the serving cell, e.g., via system information broadcast (SIB) signaling, to indicate when a UE, such as the UE 121 , should monitor for WUS in idle / inactive mode. This is assuming duty-cycle WUS is adopted for UEs in idle / inactive mode. Once the offset value prior to UE’s PO is applied, the network may configure a single or multiple subframes, e.g., consecutively, for the UE 121 to monitor for WUS, such as the WUS message. In connected mode the UE 121 , regardless of whether it is assigned to the same subgroup, or a different subgroup implicitly, e.g., derived from an identifier such as C-RNTI, or explicitly, monitors for WUS if it should wake up to monitor PDCCH. This is assuming that there is continuous WUS in connected mode. If it happens that this monitoring for WUS in connected mode happens to coincide with the subframe(s) where any other UE in idle / inactive camping in the serving cell is supposed to monitor for WUS, starting with an offset prior to its PO in the serving cell, UEs in connected mode skips monitoring for WUS during those subframe(s).

[0125] According to some examples of embodiments herein, for the example above UEs in connected mode may also be configured with an offset prior to a search space based on “no” or “a” DRX cycle configured by the network, to monitor for PDCCH where network configures an offset value prior to UE’s PO in idle / inactive mode. Similar to the example above, then UEs in connected mode skips monitoring for WUS during those subframe(s) that coincide.

[0126] According to some examples of embodiments herein, it is only the UEs in connected mode that are configured with such offset prior to a search space to monitor for WUS to wake for monitoring PDCCH and UEs in idle / inactive mode, regardless of whether there is continuous or duty-cycled WUS, skip monitoring for WUS during those subframe(s) that coincide with the occasions for UEs in connected mode.

[0127] Figure 6 shows an example of arrangement in the UE 121 .

[0128] The UE 121 may comprise an input and output interface 600 configured to communicate with each other. The input and output interface 600 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0129] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 610 of a processing circuitry in the UE 121 depicted in Figure 6, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE 121 . One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE 121.

[0130] The UE 121 and / or the processor 610 is e.g., configured to handle a WUS in the wireless communications network 100. The UE 121 and / or the processor 410 is further configured to any one or more out of:

[0131] The UE 121 and / or the processor 610 receives a WUS message.

[0132] The UE 121 and / or the processor 610 decodes the WUS message. The UE 121 and / or the processor 610 is further configured to decode the WUS message by determining whether the subgroup ID adapted to be comprised in the WUS message is related to the UE 121. The UE 121 and / or the processor 610 is further configured to interpretate the subgroup ID based on whether the UE 121 is operating in a connected mode or in an idle and / or inactive mode.

[0133] When determined that the subgroup ID is related to the UE 121 , the UE and / or the processor 610 activates the main receiver and performs a first action associated to receiving the WUS message.

[0134] The UE 121 and / or the processor 610 may further be configured to use the subgroup ID adapted to be comprised in the WUS message both when the UE 121 operates in a connected mode and when the UE 121 operates in an idle and / or inactive mode. The UE 121 and / or the processor 610 may further be configured to interpret the subgroup ID is according to any one out of:

[0135] - When the UE 121 operates in a connected mode, the subgroup ID may be interpreted in relation to a dedicated RAN subgroup ID explicitly assigned to the UE 121 , or

[0136] - when the UE 121 operates in an idle and / or inactive mode, the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE 121 and / or a CN configured explicitly assigned subgroup ID.

[0137] The UE 121 and / or the processor 610 may be configured to determine whether the decoded subgroup ID is related to the UE 121 by comparing the decoded subgroup ID with a subgroup ID assigned to UE 121 . It may be determined that the decoded subgroup ID is related to the UE 121 when the decoded subgroup ID matches the subgroup ID assigned to the UE 121 .

[0138] The subgroup ID comprised in the WUS message may be adapted to be scrambled with a RNTI. The UE 121 may be configured with an RNTI for WUS reception.

[0139] The WUS message may further be adapted to comprise a CRC. At least one out of the subgroup ID and the CRC may be adapted to be scrambled with an RNTI. The UE 121 may be configured with an RNTI for WUS reception. The UE 121 and / or the processor 610 may further be configured to decode the WUS message by decoding the WUS message using the configured RNTI. The subgroup ID in the WUS message is related to the UE 121 when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE 121 .

[0140] The UE 121 may further comprise respective a memory 620 comprising one or more memory units. The memory 620 comprises instructions executable by the processor 610 in the UE 121.

[0141] The memory 620 is arranged to be used to store instructions, data, configurations, indications, subgroups, subgroup IDs, identifiers, WUS messages, parameters, and applications to perform the methods herein when being executed in the UE 121.

[0142] In some embodiments, a computer program 630 comprises instructions, which when executed by the at least one processor 610, cause the at least one processor 610 of the UE 121 to perform the actions above.

[0143] In some embodiments, a respective carrier 640 comprises the respective computer program 630, wherein the carrier 640 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0144] Thus, embodiments herein may disclose the UE 121 configured to handle a WUS in the wireless communications network 100. The UE 121 comprises the processor 610 and the memory 620, said memory 620 comprising instructions executable by said processor 610 whereby said UE 121 is operative to perform any of the methods herein.

[0145] Those skilled in the art will also appreciate that the functional modules in the UE 121 , described below may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the UE 121 , that when executed by the respective one or more processors such as the at least one processor 410 described above cause the respective at least one processor 410 to perform actions according to any of the actions above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0146] Embodiments

[0147] Below, some example Embodiments 1-14 are shortly described. See e.g., Figures

[0148] 4-6. Embodiment 1. A method performed by a User Equipment, UE, 121 for handling a Wake Up Signal, WUS, in a wireless communications network 100, the method comprising: receiving 501 a WUS message, decoding 502 the WUS message, which decoding comprises determining whether a subgroup identifier, ID, comprised in the WUS message is related to the UE 121 , wherein interpretation of the subgroup ID is based on whether the UE 121 is operating in a connected mode or in an idle and / or inactive mode, and when determined that the subgroup ID is related to the UE 121 , activating 503 a main receiver and performing a first action associated to receiving the WUS message.

[0149] Embodiment 2. The method according to embodiment 1 , wherein the subgroup ID comprised in the WUS message is used both when the UE 121 is operating in a connected mode and when the UE 121 is operating in an idle and / or inactive mode, and wherein the subgroup ID is interpreted according to any one out of:

[0150] - when the UE 121 operates in a connected mode, the subgroup ID is interpreted in relation to a dedicated Radio Access Network, RAN, subgroup ID explicitly assigned to the UE 121 , or

[0151] - when the UE 121 operates in an idle and / or inactive mode, the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE 121 and / or a Core Network, CN, configured explicitly assigned subgroup ID.

[0152] Embodiment 3. The method according to any of embodiments 1-2, wherein determining whether the decoded subgroup ID is related to the UE 121 comprises comparing the decoded subgroup ID with a subgroup ID assigned to UE 121 , and wherein it is determined that the decoded subgroup ID is related to the UE 121 when the decoded subgroup ID matches the subgroup ID assigned to the UE 121 .

[0153] Embodiment 4. The method according to any of clams 1-3, wherein the subgroup ID comprised in the WUS message is scrambled with a Radio Network Temporary Identifier, RNTI, and wherein the UE 121 is configured with an RNTI for WUS reception.

[0154] Embodiment 5. The method according to any of embodiments 1-3, wherein the

[0155] WUS message further comprises a Cyclic Redundancy Check, CRC, and wherein at least one out of the subgroup ID and the CRC is scrambled with an RNTI, and wherein the UE 121 is configured with an RNTI for WUS reception.

[0156] Embodiment 6. The method according to any of embodiments 4-5, wherein decoding 503 the WUS message comprises decoding the WUS message using the configured RNTI, and wherein the subgroup ID in the WUS message is related to the UE 121 when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE 121 .

[0157] Embodiment 7. A computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the embodiments 1-6.

[0158] Embodiment 8. A carrier comprising the computer program of embodiment 7, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0159] Embodiment 9. A User Equipment, UE, 121 configured to handle a Wake Up Signal, WUS, in a wireless communications network 100, the UE 121 further being configured to: receive a WUS message, decode the WUS message, wherein the UE 121 is further configured to decode the WUS message by determining whether a subgroup identifier, ID, adapted to be comprised in the WUS message is related to the UE 121 , wherein the UE 121 is further configured to interpretate the subgroup ID based on whether the UE 121 is operating in a connected mode or in an idle and / or inactive mode, and when determined that the subgroup ID is related to the UE 121 , activate a main receiver and perform a first action associated to receiving the WUS message.

[0160] Embodiment 10. The UE 121 according to embodiment 9, wherein the UE 121 is further configured to use the subgroup ID adapted to be comprised in the WUS message both when the UE 121 operates in a connected mode and when the UE 121 operates in an idle and / or inactive mode, and wherein the UE 121 is further configured to interpret the subgroup ID is according to any one out of: - when the UE 121 operates in a connected mode, the subgroup ID is interpreted in relation to a dedicated Radio Access Network, RAN, subgroup ID explicitly assigned to the UE 121 , or

[0161] - when the UE 121 operates in an idle and / or inactive mode, the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE 121 and / or a Core Network, CN, configured explicitly assigned subgroup ID.

[0162] Embodiment 11. The UE 121 according to any of embodiments 9-10, wherein the UE 121 is configured to determine whether the decoded subgroup ID is related to the UE 121 by comparing the decoded subgroup ID with a subgroup ID assigned to UE 121 , and wherein it is determined that the decoded subgroup ID is related to the UE 121 when the decoded subgroup ID matches the subgroup ID assigned to the UE 121 .

[0163] Embodiment 12. The UE 121 according to any of embodiments 9-11 , wherein the subgroup ID comprised in the WUS message is adapted to be scrambled with a Radio Network Temporary Identifier, RNTI, and wherein the UE 121 is configured with an RNTI for WUS reception.

[0164] Embodiment 13. The UE 121 according to any of embodiments 9-11 , wherein the WUS message is further adapted to comprise a Cyclic Redundancy Check, CRC, and wherein at least one out of the subgroup ID and the CRC is adapted to be scrambled with an RNTI, and wherein the UE 121 is configured with an RNTI for WUS reception.

[0165] Embodiment 14. The UE 121 according to any of embodiments 12-13, wherein the UE is further configured to decode the WUS message by decoding the WUS message using the configured RNTI, and wherein the subgroup ID in the WUS message is related to the UE 121 when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE 121 .

[0166] ADDITIONAL EXPLANATION

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

[0168] Figure 7 shows an example of a communication system QQ100 in accordance with some embodiments. In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108 (being examples of the network node 110). The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 being examples of the network node 110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0169] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112 being examples of the UE 121) to the core network QQ106 over one or more wireless connections.

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

[0171] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0172] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

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

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

[0176] In some examples, the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. 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 QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0177] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Figure 8 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0179] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0180] The processing circuitry QQ202 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 QQ210. The processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).

[0181] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. 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.

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

[0183] The memory QQ210 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0184] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0185] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

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

[0188] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0189] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

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

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

[0192] Figure 9 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0193] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 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).

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

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

[0196] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality. In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0197] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 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 QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0198] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0199] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

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

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

[0202] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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.

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

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

[0205] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

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

[0207] Figure 11 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O- Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0208] Applications QQ502 (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.

[0209] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

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

[0211] In the context of NFV, a VM QQ508 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 QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0212] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units. Figure 12 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 7 and / or UE QQ200 of Figure QQ2), network node (such as network node QQ110a of Figure 7 and / or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure 7 and / or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.

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

[0214] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

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

[0216] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0217] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0218] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606. One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

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

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

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

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

[0223] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of'.

[0224] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1 . A method performed by a User Equipment, UE, (121) for handling a Wake Up Signal, WUS, in a wireless communications network (100), the method comprising: receiving (501) a WUS message, decoding (502) the WUS message, which decoding comprises determining whether a subgroup identifier, ID, comprised in the WUS message is related to the UE (121), wherein interpretation of the subgroup ID is based on whether the UE (121) is operating in a connected mode or in an idle and / or inactive mode, and when determined that the subgroup ID is related to the UE (121), activating (503) a main receiver and performing a first action associated to receiving the WUS message.

2. The method according to claim 1 , wherein the subgroup ID comprised in the WUS message is used both when the UE (121) is operating in a connected mode and when the UE (121) is operating in an idle and / or inactive mode, and wherein the subgroup ID is interpreted according to any one out of:- when the UE (121) operates in a connected mode, the subgroup ID is interpreted in relation to a dedicated Radio Access Network, RAN, subgroup ID explicitly assigned to the UE (121), or- when the UE (121) operates in an idle and / or inactive mode, the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE (121) and / or a Core Network, CN, configured explicitly assigned subgroup ID.

3. The method according to any of claims 1-2, wherein determining whether the decoded subgroup ID is related to the UE (121) comprises comparing the decoded subgroup ID with a subgroup ID assigned to UE (121), and wherein it is determined that the decoded subgroup ID is related to the UE (121) when the decoded subgroup ID matches the subgroup ID assigned to the UE (121).

4. The method according to any of clams 1-3, wherein the subgroup ID comprised in the WUS message is scrambled with a Radio Network Temporary Identifier, RNTI, and wherein the UE (121) is configured with an RNTI for WUS reception.

5. The method according to any of claims 1-3, wherein the WUS message further comprises a Cyclic Redundancy Check, CRC, and wherein at least one out thesubgroup ID and the CRC is scrambled with an RNTI, and wherein the UE (121) is configured with an RNTI for WUS reception.

6. The method according to any of claims 4-5, wherein decoding (503) the WUS message comprises decoding the WUS message using the configured RNTI, and wherein the subgroup ID in the WUS message is related to the UE (121) when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE (121).

7. A computer program comprising instructions, which when executed by a processor, causes the processor to perform actions according to any of the claims 1-6.

8. A carrier comprising the computer program of claim 7, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

9. A User Equipment, UE, (121) configured to handle a Wake Up Signal, WUS, in a wireless communications network (100), the UE (121) further being configured to: receive a WUS message, decode the WUS message, wherein the UE (121) is further configured to decode the WUS message by determining whether a subgroup identifier, ID, adapted to be comprised in the WUS message is related to the UE (121), wherein the UE (121) is further configured to interpretate the subgroup ID based on whether the UE (121) is operating in a connected mode or in an idle and / or inactive mode, and when determined that the subgroup ID is related to the UE (121), activate a main receiver and perform a first action associated to receiving the WUS message.

10. The UE (121) according to claim 9, wherein the UE (121) is further configured to use the subgroup ID adapted to be comprised in the WUS message both when the UE (121) operates in a connected mode and when the UE (121) operates in an idle and / or inactive mode, and wherein the UE (121) is further configured to interpret the subgroup ID is according to any one out of:- when the UE (121) operates in a connected mode, the subgroup ID is interpreted in relation to a dedicated Radio Access Network, RAN, subgroup ID explicitly assigned to the UE (121), or- when the UE (121) operates in an idle and / or inactive mode, the subgroup ID is interpreted in relation to a subgroup ID implicitly assigned to the UE (121) and / or a Core Network, CN, configured explicitly assigned subgroup ID.

11. The UE (121) according to any of claims 9-10, wherein the UE (121) is configured to determine whether the decoded subgroup ID is related to the UE (121) by comparing the decoded subgroup ID with a subgroup ID assigned to UE (121), and wherein it is determined that the decoded subgroup ID is related to the UE (121) when the decoded subgroup ID matches the subgroup ID assigned to the UE (121).

12. The UE (121) according to any of clams 9-11 , wherein the subgroup ID comprised in the WUS message is adapted to be scrambled with a Radio Network Temporary Identifier, RNTI, and wherein the UE (121) is configured with an RNTI for WUS reception.

13. The UE (121) according to any of claims 9-11 , wherein the WUS message is further adapted to comprise a Cyclic Redundancy Check, CRC, and wherein at least one out the subgroup ID and the CRC is adapted to be scrambled with an RNTI, and wherein the UE (121) is configured with an RNTI for WUS reception.

14. The UE (121) according to any of claims 12-13, wherein the UE is further configured to decode the WUS message by decoding the WUS message using the configured RNTI, and wherein the subgroup ID in the WUS message is related to the UE (121) when the decoding is successful and when the decoded subgroup ID matches a subgroup ID assigned to the UE (121).

Images