Wake-up signal operation on dual discontinuous reception groups
By configuring LP-WUS on a default DRX group to synchronize PDCCH monitoring across dual DRX groups, the solution addresses inefficiencies in power consumption and scheduling, enabling efficient data transmission in both groups.
Patent Information
- Application Number
- PCT/SE2026/050308
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-05
- Publication Date
- 2026-11-12
AI Technical Summary
Existing low-power wake-up signal (LP-WUS) solutions for New Radio (NR) face challenges in configuring dual discontinuous reception (DRX) groups, particularly in scenarios where one DRX group is active while the other is not, leading to inefficiencies in power consumption and scheduling of PDCCH monitoring across different frequency ranges.
The proposed solution involves configuring LP-WUS on a default DRX group to enable PDCCH monitoring in both DRX groups by altering timer behaviors and using new PDCCH indications to synchronize PDCCH monitoring across DRX groups, allowing data scheduling on secondary groups even when they are not actively monitoring LP-WUS.
This approach enhances power efficiency by allowing PDCCH monitoring in both DRX groups, reducing unnecessary power consumption and improving scheduling flexibility, especially in scenarios where one DRX group is not actively monitoring LP-WUS.
Smart Images

Figure SE2026050308_12112026_PF_FP_ABST
Abstract
Description
WAKE-UP SIGNAL OPERATION ON DUAL DISCONTINUOUS RECEPTION GROUPSBACKGROUND
[0001] New Radio (NR) Wake-up receiver (WUR), sometimes also referred to as wakeup radio, is about enabling a low power receiver in user equipments (UEs), which, in case of the detection of a wake-up signal (WUS), wakes up the main (e.g., baseband / RF / less power efficient) 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)) or PDCCH scheduling downlink (DL) data. A potential 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 (shorter discontinuous reception (DRX) / duty-cycles and more frequent checks for incoming transmissions).
[0002] In general, there are two approaches for detecting WUS:• Using the main receiver:o No need for additional dedicated hardware / receiver for monitoring WUS, o Coverage of the main receiver is not typically impacted,o Limited power saving gain as the main receiver monitors WUS.• Using a dedicated receiver (WUR):o Extremely low power, simple and low-cost receiver architecture, relaxed requirements, noisier (i.e., less accurate) clock or oscillator,o Significant power saving gain can be achieved by maximizing the time in which the main receiver can be in the sleep mode,o Enablers for zero energy / battery -less devices, and energy harvesting operations,o There are coverage considerations given the tradeoff between WUR power consumption and sensitivity.
[0003] In Rel-18, there has been increased interest to introduce WUR for NR, with an ambition for improving energy efficiency compared to solutions specified in earlier releases. As explained above, the only specification support needed to be able to use a WUR in the UE, is the specification of a WUS and a long enough time gap between the WUS and the PDCCH in the PO (to provide the UE with sufficient time to start up the main receiver). Therefore, themain difference to Rel-17 PEI is that the WUS in Rel-18 should not be PDCCH-based and allow for a less complex and lower power receiver (i.e., WUR with less complexity modulation and detection techniques). For example, using on-off keying (OOK) modulation and noncoherent detection.
[0004] 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 described below.
[0005] Some of the justifications are described below.
[0006] 5G systems are designed and developed targeting for both mobile telephony and vertical use cases. Besides latency, reliability, and availability, UE energy efficiency is also critical to 5G. Currently, 5G devices may have to be recharged per week or day, depending on individual’s usage time. In general, 5G devices consume tens of milliwatts in Radio Resource Control (RRC) idle / inactive state and hundreds of milliwatts in RRC connected state. Designs to prolong battery life is a necessity for improving energy efficiency as well as for better user experience.
[0007] Energy efficiency is even more critical for UEs without a continuous energy source, e.g., UEs using small rechargeable and single coin cell batteries. Among vertical use cases, sensors and actuators are deployed extensively for monitoring, measuring, charging, etc. Generally, their batteries are not rechargeable and expected to last at least few years as described in TR 38.875. Wearables include smart watches, rings, eHealth related devices, and medical monitoring devices. With typical battery capacity, it is challenging to sustain up to 1-2 weeks as required.
[0008] The power consumption depends on the configured length of wake-up periods, e.g., paging cycle. To meet the battery life requirements above, extended discontinuous reception (eDRX) cycle with large value is expected to be used, resulting in high latency, which is not suitable for such services with requirements of both long battery life and low latency. For example, in fire detection and extinguishment use case, fire shutters shall be closed and fire sprinklers shall be turned on by the actuators within 1 to 2 seconds from the time the fire is detected by sensors, long eDRX cycle cannot meet the delay requirements. eDRX is apparently not suitable for latency-critical use cases. Thus, the intention is to study ultra-low power mechanism that can support low latency in Rel-18, e.g. lower than eDRX latency.
[0009] Currently, UEs need to periodically wake up once per DRX cycle, which dominates the power consumption in periods with no signalling or data traffic. If UEs are able to wake up only when they are triggered, e.g., paging, power consumption could be dramatically reduced. This can be achieved by using a wake-up signal to trigger the main radio and a separate receiverwhich has the ability to monitor wake-up signal with ultra-low power consumption. Main radio works for data transmission and reception, which can be turned off or set to deep sleep unless it is turned on.
[0010] The power consumption for monitoring wake-up signal depends on the wake-up signal design and the hardware module of the wake-up receiver used for signal detecting and processing.
[0011] The study should primarily target low-power WUS / WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables. Other use cases are not precluded, (e.g., extended reality (XR) / smart glasses, smart phones).
[0012] Some of the objectives are described below.
[0013] As opposed to the work on UE power savings in previous releases, this study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy UEs. Solutions should target substantial gains compared to the existing Rel-15 / 16 / 17 UE power saving mechanisms. Other aspects such as detection performance, coverage, UE complexity, should be covered by the evaluation.
[0014] The study item includes the following objectives:• Identify evaluation methodology (including the use cases) & key performance indicators (KPIs) [RANI]o Primarily target low-power WUS / WUR for power-sensitive, small form-factor devices including loT use cases (such as industrial sensors, controllers) and wearables■ Other use cases are not precluded• Study and evaluate low-power wake-up receiver architectures [RANI, RAN4]• Study and evaluate wake-up signal designs to support wake-up receivers [RANI, RAN4]• Study and evaluate LI procedures and higher layer protocol changes needed to support the wake-up signals [RAN2, RANI]• Study potential UE power saving gains compared to the existing Rel-15 / 16 / 17 UE power saving mechanisms and their coverage availability, as well as latency impact. System impact, such as network power consumption, coexistence with non-low- power- WUR UEs, network coverage / capacity / resource overhead should be included in the study [RANI]oNote: The need for RAN2 evaluation will be triggered by RANI when necessary
[0015] The benefit of WUR is to reduce the energy consumption of the UE (receiver), such that unless there is paging and data for the UE it can remain in a power saving state. This will extend the battery life of the device and / or enable shorter downlink latency (shorter DRX) at a fixed battery life.
[0016] The Rel-18 study item on “low-power wake-up signal and receiver for NR” is completed and the technical report is provided in: TR 38.869, VO.4.0, “Study on low-power Wake-up Signal and Receiver for NR” [1],
[0017] For Rel-19, a work item has been agreed to specify the wake-up signal for both RRC Idle / Inactive and RRC Connected states: RP-234056, New WID: Low-power wake-up signal and receiver for NR (LP WUS / WUR) [2], The objectives are the following:• To specify an LP-WUS design commonly applicable to both IDLE / INACTIVE and CONNECTED modes (RANI, RAN4).• Specify OOK (OOK-1 and / or OOK-4) based low power wake-up signal (LP- WUS) with overlaid Orthogonal Frequency Division Multiplexing (OFDM) sequence(s) over OOK symbol.• The LP-WUS design shall ensure that for IDLE / INACTIVE operation, the same information is delivered irrespective of LP-WUR type. The OFDM sequence can carry information.• Note:• OOK1 is an on-off keying (OOK) waveform with single segment within one OFDM symbol.• OOK4 is an OOK waveform with multiple segments within one OFDM symbols.• At least duty-cycled monitoring of LP-WUS is supported.• For IDLE / INACTIVE modes• Specify procedure and configuration of LP-WUS indicating paging monitoring triggered by LP-WUS, including at least configuration, sub-grouping and entry / exit condition for LP-WUS monitoring (RAN2, RANI, RAN3, RAN4).• Specify low power synchronization signal (LP-SS) with periodicity with Y milliseconds for LP-WUR, for synchronization and / or Radio Resource Management (RRM) for serving cell. (RANI, RAN4).• LP-SS is based on OOK-1 and / or OOK-4 waveform with or without overlaid OFDM sequences. Further down selection between with and without overlaid OFDM sequences is to be done within WI.• Note: For LP-WUR that can receive existing Primary Synchronization Signal (PSS) / Secondary Synchronization Signal (SSS), existing PSS / SSS can be used for synchronization and RRM instead of LP-SS.• Y will be decided within WI. 320ms is the start point.• Specify further RRM relaxation of UE multi -radio (MR) for both serving and neighbor cell measurements, and UE serving cell RRM measurement offloaded from MR to LP-WUR, including the necessary conditions (RAN4, RAN2).• For CONNECTED mode, specify procedures to allow UE MR PDCCH monitoring triggered by LP-WUS including activation and deactivation procedure of LP-WUS monitoring (RAN2, RANI).• Check in RAN 105 for potential time unit (TU) adjustment in RAN2 • Note: In CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / radio link monitoring (RLM) / beam failure detection (BFD) / channel state information (CSI) measurements are performed by MR.• Note: The target coverage of LP-WUS and LP-SS shall be the coverage of Physical Uplink Shared Channel (PUSCH) for message3.• Note: The optimization of LP-WUS signal design for idle / inactive mode is prioritized over the optimization for connected mode.• Specify the necessary RAN4 core requirement s) to support the feature (RAN4).• This objective is to be further refined in RAN 103
[0018] WUS functionality in RRC connected mode is described below.• In RRC CONNECTED mode, RAN2 to further discuss the impacts of LP-WUS operation methods identified in RAN 1.• For Option 1-1 (as described in RANI agreement), the LP-WUS monitoring occasion locates at a configured time offset before the start of drx-onDurationTimer. The range of time offset can be determined by RANI.• For Option 1-1, RAN2 assumes the solutions / operations introduced for DCP mechanism is taken as baseline.• RAN2 assume that legacy DCP and Option 1-1 is not configured simultaneously for a UE.• The LP-WUS related configuration for RRC CONNECTED state UE is provided via dedicated RRC message.
[0019] For option 1-2,• After LP-WUS triggers the UE to perform PDCCH monitoring, the UE starts one timer.When the timer is running, the UE monitors PDCCH. FFS on the timer (e.g., newly defined timer or legacy timer).• The timer is started at a time offset after receiving the LP-WUS indication for PDCCH monitoring. The range of time offset is left for RANI.
[0020] For Option 1-2, LP-WUS monitoring is performed at least outside legacy connected-mode discontinuous reception (C-DRX) Active Time. FFS if the legacy drx-onDurationTimer is started or not if the new timer is configured in Option 1-2. In option 1-2, a new timer triggered by LP-WUS is introduced. When this new timer is running, UE is in C-DRX active time. When UE is not in C-DRX active time, UE goes back to LPWUS monitoring. When UE is in C-DRX active time, UE PDCCH monitoring behaviors related to other legacy DRX timers (except for drx-onDurationTimer) are not affected.
[0021] The drx-onDurationTimer is not started with Option 1-2 LP-WUS. For Option 1-2, network can configure whether UE reports periodic CSI / L1-RSRP during the time given by the configured drx-onDurationTimer, for the case when UE is outside C-DRX active time. For option 1-2, if UE receives DRX command MAC CE or Long DRX command MAC CE, UE stops the new timer triggered by LP-WUS.
[0022] For option 1-1 and 1-2, there is not support for Option 1-1 and Option 1-2 simultaneously configured for the same UE.
[0023] Regarding LP-WUS for carrier aggregation (CA) and dual connectivity (DC), for both option 1-1 and option 1-2, the LP-WUS can also be configured with secondary per DRX group. Additionally, in NR-DC case, LP-WUS can be configured separately in main cell group (MCG) and secondary cell group (SCG), and LP-WUS could trigger the PDCCH monitoring of all activated serving cells within the same cell group.
[0024] Regarding DRX command and short DRX, for Option 1-1, UE monitors LP-WUS outside C-DRX active time at least when long DRX cycle is used. RAN2 confirm the (Long) DRX command Medium Access Control (MAC) control element (CE) can be used with option1-1 to stop drx-onDurationTimer and drx-InactivityTimer. RAN2 confirm the (Long) DRX command MAC CE can be used with option 1-2 to stop the new timer and drx-InactivityTimer.
[0025] LP-WUS and CA is discussed in further detail below.
[0026] The UE can be configured with CA to provide a relatively high throughput and relatively short latency. Based on RRM measurement reporting and load balancing the CA configuration may change using RRCReconfiguration (i.e., carriers can be added or removed). Based on traffic demand and to save power SCells may be deactivated or enter dormant state (i.e., dormant BWP is used).
[0027] The DRX configuration applies to all the cells of the Cell Group (CA / DC) or DRX group (secondary DRX) (i.e., the UE is in the same DRX state (e.g. Active Time) in all the cells in the Cell Group or DRX group.) The same DRX parameter applies to all the cells of the same Cell / DRX Group, e.g. one drx-OnDurationTimer is running for each Cell / DRX Group. The scheduler uses the full capacity provided by the Cell / DRX groups to schedule traffic.
[0028] With DC and secondary DRX the Cell groups and DRX groups can be in different DRX states, e.g. MCG is inside Active Time and SCG is outside Active Time. With DC the timing is not aligned, i.e. the DRX cycles and drx-OnDurationTimer may start / stop at different times.
[0029] With secondary DRX a shorter drx-OnDurationTimer and drx-InactivityTimer for FR2 can be configured to enable the secondary DRX group on a second frequency range (FR2) to go into sleep more quickly and save power. Thus, the DRX groups may be in different DRX states as illustrated in Error! Reference source not found..SUMMARY
[0030] Figure 1 illustrates two DRX groups partly in different DRX states.
[0031] Cross carrier scheduling is not supported with secondary DRX. The trigger for aperiodic CSI and PUSCH reporting is on the same carrier (e.g., in a primary cell (PCell) of the default DRX group, but the cell for which CSI is reported may be in the same or another DRX group (frequency range)). The network does not trigger aperiodic reporting for the other DRX group, when the UE is outside Active Time in the other DRX group (i.e., the UE is only required to measure during Active Time).
[0032] Downlink control information of power saving (DCP) can be configured with CA or DC (i.e., the primary cell in the cell group can be configured with DCP). When DCP is triggered then the drx-OnDurationTimer is started and the UE starts monitoring PDCCH in all the serving cells of the cell group and the cell group enters Active Time. This is not applicablefor cells that are deactivated or in dormant state (i.e., the UE does not monitor PDCCH on those cells). DCP is also not supported with secondary DRX.
[0033] There currently exist certain challenge(s). Regarding LP-WUS on PCell in a first frequency range (FR1) only, it is not possible to wake-up FR2 when FR1 is in Active Time because the UE does not monitor LP-WUS during Active Time. Regarding LP-WUS on PCell in FR1 and an SCell in FR2, there is additional complexity to support two LP-WUS receivers and it requires transmission of two LP-WUS to restart activity on both cells. Regarding LP-WUS on an SCell in FR2 only, there is not an ability to wake-up FR2 when FR1 is in Active Time. When LP-WUS on FR2 is triggered then all the cells in FR2 enter Active Time, and all the cells in FR1 enter Active Time in case FR1 was outside Active Time. FR2 also has worse coverage than FR1, and LP-WUS coverage is expected to have worse coverage than paging PDCCH, so the usefulness of this option is limited.
[0034] Additionally, LP-WUS has worse coverage than other NR channels which means that, especially if LP-WUS is configured on FR2, the coverage is an issue. Therefore, it would be beneficial to find solutions to the problems associated with option 1. Some of these problems are illustrated in Figure 2.
[0035] Figure 2 illustrates when the secondary DRX group stops PDCCH monitoring it can’t be woken up while PDCCH monitoring is ongoing in Default DRX group. As illustrated, the UE can’t be scheduled on cells in the secondary DRX group when the default DRX group is in Active Time.
[0036] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The present disclosure describes methods for scenarios where Dual DRX groups are configured and LP-WUS monitoring is performed on the Default DRX group (FR1). The present disclosure helps to allow data to be scheduled on the secondary DRX group when its Inactivity timer has expired and it is not monitoring PDCCH. Some embodiments are directed to reception of a PDCCH transmission on the Default DRX group, where the PDCCH transmission may be altered, to start (or restart) PDCCH monitoring in the secondary DRX group. Some additional or alternative embodiments are directed to, when WUS is configured for the UE, not stopping (e.g., not ceasing activation of) PDCCH monitoring in the secondary PDCCH group until LP-WUS monitoring is started in the default DRX group (e.g., until both the Inactivity Timers on the secondary DRX group and on the default DRX group have expired).
[0037] Some embodiments of the present disclosure are directed to a method performed by a wireless device for PDCCH monitoring in a plurality of DRX groups. The method including receiving a wake-up signal from a cell of a first DRX group. The method furtherincludes, responsive to receiving the wake-up signal, activating PDCCH monitoring of cells of the first DRX group and PDCCH monitoring of cells of a second DRX group. Where the PDCCH monitoring of cells of the first DRX group includes starting a first timer that includes a time duration for PDCCH monitoring of the cells of the first DRX group, and the PDCCH monitoring of cells of the second DRX group includes starting a second timer that includes another time duration for PDCCH monitoring of the cells of the second DRX group. Additionally, the method includes restarting the second timer responsive to at least one of the time duration of the first timer not expiring and the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group.
[0038] Some other embodiments of the present disclosure are directed to a method performed by a network node for enabling wireless device PDCCH monitoring in a plurality of DRX groups. The method including transmitting a wake-up signal toward a wireless device to trigger activation of PDCCH monitoring of cells of a first DRX group and PDCCH monitoring of cells of a second DRX group.
[0039] Certain embodiments may provide one or more of the following technical advantage(s). Potential technical advantages may include configuration of LP-WUS on the default DRX group while being able to schedule cells in the secondary DRX group. Additionally, embodiments of the present disclosure may enable PDCCH monitoring to be conducted in both DRX groups when LP-WUS is configured in only one of them. This may be performed by a new PDCCH indication in the active DRX group and / or by changing the timer behavior in the DRX group which is not active and does not have LP-WUS monitoring.BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
[0041] FIG. 1 illustrates two DRX groups partly in different DRX states;
[0042] FIG. 2 illustrates when secondary DRX group stops PDCCH monitoring it can’t be woken up while PDCCH monitoring is ongoing in Default DRX group;
[0043] FIG. 3 illustrates a PDCCH transmission on one DRX group to start PDCCH monitoring on the other DRX group, in accordance with some embodiments;
[0044] FIG. 4 illustrates PDCCH monitoring on the second DRX group that continues until both inactivity timers have expired, in accordance with some embodiments;
[0045] FIG. 5 illustrates a flowchart of wireless device performed operations, in accordance with some embodiments;
[0046] FIG. 6 illustrates a flowchart of network node performed operations, in accordance with some embodiments;
[0047] FIG. 7 is a block diagram of a communication system in accordance with some embodiments;
[0048] FIG. 8 is a block diagram of another communication system in accordance with some embodiments;
[0049] FIG. 9 is a block diagram of a user equipment in accordance with some embodiments;
[0050] FIG. 10 is a block diagram of a network node in accordance with some embodiments; and
[0051] FIG. 11 is a block diagram of a virtualization environment in accordance with some embodiments.DETAILED DESCRIPTION
[0052] 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.
[0053] Herein the terms default DRX group may also be referred to as a first DRX group and the secondary DRX group may also be referred to as a second DRX group, or vice versa. Additionally, the UE described herein is configured with at least two DRX groups. While two DRX groups are described throughout, embodiment of the present disclosure may be used for any number of DRX groups.
[0054] Figure 3 illustrates a PDCCH transmission on one DRX group to start PDCCH monitoring on the other DRX group, in accordance with some embodiments.
[0055] Referring to Figure 3, the UE is configured with two DRX groups, a default DRX group and a secondary DRX group. The UE, while in LP-WUS monitoring for the default DRX group, receives a wake-up signal (e.g., a LP-WUS) from a cell of a default DRX group. Responsive to receiving the wake-up signal, the UE activates PDCCH monitoring of cells of the first DRX group and PDCCH monitoring of cells of a second DRX group. DL data forboth cells in the default DRX group and cells in the secondary DRX group may be received while the UE has the PDCCH monitoring active for both groups.
[0056] In this first embodiment of Figure 3, the network signals a PDCCH indicating a new transmission to the UE on a PDCCH of a cell belonging to the default DRX group. As shown in Figure 3, the PDCCH may be received during drx-InactivityTimerl. Upon the reception of the PDCCH with the indication, the UE starts (in this case restarts) PDCCH monitoring on the cells belonging to the secondary DRX group. When doing so, it may also start a PDCCH monitoring timer such as the DRX-OnDurationTimer or DRX-Inactivity Timer as configured on the secondary DRX group.
[0057] In some embodiments, one or more signaling bits in a WUS payload used in RRC Connected could be interpreted by the UE to indicate if the UE should resume PDCCH monitoring on both DRX groups or just the default DRX group. The PDCCH indication may include a DCI scheduling a DL transmission on a cell belonging to the default DRX group.
[0058] The secondary DRX group may be for cells in FR2 which may result in higher UE energy consumption. Thus, a shorter drx-InactivityTimer may be configured for the secondary DRX group than the default DRX group (i.e., drx-InactivityTimer2 < drx-InactivityTimerl). Having a shorter inactivity timer for the secondary DRX group may have increased the problems of previous solutions, but some of the embodiments herein help to reduce these problems introduced by having a shorter inactivity timer for the secondary DRX group.
[0059] In another example, the PDCCH indication may include a new DCI, or a new entry in a legacy DCI (e.g., a new field), which indicates that the UE shall start PDCCH monitoring on the cells belonging to the other (secondary) DRX group. As an alternative this may be indicated dynamically (e.g., the UE may, from an indication in DCI, determine if the UE should resume PDCCH monitoring on both DRX groups or just the default DRX group).
[0060] Figure 4 illustrates PDCCH monitoring on the second DRX group that continues until both inactivity timers have expired, in accordance with some embodiments. Referring to Figure 4, the UE is configured with the default DRX group and the secondary DRX group. The UE, while in LP-WUS monitoring for the default DRX group, receives a wake-up signal (e.g., a LP-WUS) from a cell of a default DRX group. Responsive to receiving the wake-up signal, the UE activates PDCCH monitoring of cells of the first DRX group and PDCCH monitoring of cells of a second DRX group. DL data for both cells in the default DRX group and cells in the secondary DRX group may be received while the UE has the PDCCH monitoring active for both groups.
[0061] In this second embodiment of Figure 4, the UE is configured with one Inactivity timer per DRX group. In the secondary DRX group where the UE does not monitor LP-WUS, the UE does not stop PDCCH monitoring until both Inactivity timers have expired. In the default DRX group where the UE can monitor LP-WUS, the UE follows legacy behavior and stops PDCCH monitoring when its InactivityTimer expires.
[0062] In some of these second embodiments, PDCCH monitoring on the second DRX group may stop when LP-WUS monitoring is started on the default DRX group. This means that PDCCH monitoring on the second DRX group is controlled by the Inactivity timer on the default DRX group when LP-WUS is configured for a UE in RRC Connected.
[0063] Additionally, or alternatively, the UE may start and restart a timer controlling PDCCH monitoring (such as DRX-InactivityTimer or drx-onDurationTimer) on the secondary DRX group as long as the Inactivity timer on the default DRX group is running or as long as the default DRX group is in Active Time. That is, if the timer on the secondary DRX group expires while the Inactivity timer on the default DRX group is running or the group is in Active Time, the timer on the secondary DRX group is (re)started. If the timer on the secondary DRX group is not running but the Inactivity timer on the default DRX group is started, the timer on the secondary DRX group is also started.
[0064] The second embodiment of Figure 4 may be determined by configuration of the UE. For example, specified handling of the timers, may not be configured for the UE if energy consumption is of primary interest while this feature is configured for the UE, or when high bit rate is of primary interest. As an option, this feature of the second embodiment (i.e., the specified handling of the timers) may be activated or deactivated by a new MAC CE or LI signaling. Additionally, or alternatively, this feature of the second embodiment may be activated or deactivated based on a remaining power in a UE battery (e.g. configured as time), where if the UE batter is low the feature is deactivated.
[0065] In one embodiment, the configuration of the individual DRX timers in this second embodiment may be decided, in addition to power consumption, based on the traffic type (e.g., quality of service (QoS)) that is considered. For example, the configuration of the individual DRX timers can be based on a QoS the particular UE is subscribed to.
[0066] Example of specification changes in 38.321 to handle the first embodiment described above is underlined below:1> if a DRX group is in Active Time:2> monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213;2> if LP-WUS is configured on any of the DRX groups and2> if the PDCCH indicates activation of PDCCH monitoring on the other DRX group:3> start the drx-onDurationTimer for the other DRX group and monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38,213;2> if the PDCCH indicates a DL transmission; or2> if the PDCCH indicates a one-shot HARQ feedback as specified in clause 9.1.4 of TS 38.213; or2> if the PDCCH indicates a retransmission of HARQ feedback as specified in clause 9.1.5 ofTS 38.213:3> if this Serving Cell is configured with downlinkHARQ-FeedbackDisabled.
[0067] Example of specification changes in 38.321 to handle the second embodiment described above is underlined below:1> if a DRX group is in Active Time:2> if LP-WUS is configured on any of the DRX groups and2> if the DRX group where LP-WUS is not configured is not in Active Time:3> start the drx-onDurationTimer in this DRX group.2> monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213;2> if the PDCCH indicates a DL transmission; or2> if the PDCCH indicates a one-shot HARQ feedback as specified in clause 9.1.4 of TS 38.213; or2> if the PDCCH indicates a retransmission of HARQ feedback as specified in clause 9.1.5 ofTS 38.213:3> if this Serving Cell is configured with downlinkHARQ-FeedbackDisabled.
[0068] In a third embodiment, cross-carrier scheduling for cells belonging to different DRX cell groups may be enabled. For example, when the network signals a PDCCH indicating a new transmission to the UE on a PDCCH of a cell belonging to the default DRX group (e.g., during drx-Inacti vity Timer 1 in Figure 3), the network may in the DCI indicate if the data is scheduled on cells belonging to the secondary DRX group.
[0069] The CrossCarrierSchedulingConfig is discussed below. The IE CrossCarrierSchedulingConfig is used to specify the configuration when the cross-carrier scheduling is used in a cell. The CrossCarrierSchedulingConfig information element is shown below.- ASN1 START- TAG-CROSSCARRIERSCHEDULINGCONFIG-STARTCrossCarrierSchedulingConfig ::= SEQUENCE {schedulingCelllnfo CHOICE {own SEQUENCE { — Cross carrier scheduling: scheduling cellcif-Presence BOOLEAN},other SEQUENCE { — Cross carrier scheduling: scheduledschedulingCellld ServCelllndex,cif-InSchedulingCell INTEGER (L .7)}},[[carrier!ndicatorSize-rl6 SEQUENCE {carrierlndicatorSizeDCI- 1 -2-r 16 INTEGER (0 .3),carrierIndicatorSizeDCI-0-2-rl6 INTEGER (0 .3)} OPTIONAL, - Cond CIF- PRESENCEenableDefaultBeamForCCS-rl6 ENUMERATED {enabled}OPTIONAL - Need S]],[[ccs-BlindDetectionSplit-rl7 ENUMERATED {oneSeventh, threeFourteenth, twoSeventh, threeSeventh,oneHalf, fourSeventh, fiveSeventh, spare 1} OPTIONAL — Need R]Lwus-CrossCarrierScheduling-rl9 ENUMERATED {true} OPTIONAL — Need R}- TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP - ASN1STOPCrossCarrierSchedulingConfig field descriptions; carrierIndicatorSizeDCI-0-2, carrierIndicatorSizeDCI-1-2Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0 2 / 1 2. The field carrierIndicatorSizeDCI-0-2 refers to DCI format 0 2 and the field carrierIndicatorSizeDCI-1-2 refers to DCI format 1_2, respectively (see TS 38.212
[0017] , clause 7.3.1 and TS 38.213
[0013] , clause 10.1).ccs-BlindDetectionSplitIndicates the share of blind detection candidates and non-overlapping CCEs for PDCCH monitoring on an SpCell and an SCell when cross-carrier scheduling is configured from the SCell for the SpCell (see TS 38.213
[0013] , clause 10.1.1). The network only configures this field when it sets the field other for an SpCell, i.e., when it configures cross-carrier scheduling of the SpCell by a PDCCH on an Scell.cif-PresenceThe field is used to indicate whether carrier indicator field is present (value true) or not (value false) in PDCCH DCI formats, see TS 38.213
[0013] , If cif-Presence is set to true, the CIF value indicating a grant or assignment for this cell is 0.cif-InSchedulingCellThe field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell, see TS 38.213
[0013] , If configured for an SpCell, the non-fallback DCI formats on the SpCell include same number of CIF bits as the corresponding non-fallback DCI formats on the scheduling cell, and the CIF bits are considered reserved.enableDefaultBeamForCCSThis field indicates whether default beam selection for cross-carrier scheduled PDSCH or aperiodic CSI-RS is enabled, see TS 38.214
[0019] , If not present, the default beam selection behaviour is not applied, i.e. Rel-15 behaviour is applied. This field can only be configured in the cross-scheduled SCell or SpCell.otherParameters for cross-carrier scheduling. If configured for an SpCell, the SpCell can be scheduled by the PDCCH on another SCell as well as by the PDCCH on the SpCell. If configured for an SCell, the SCell is scheduled by a PDDCH on another cell.; ownParameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH.CrossCarrierSchedulingConfig field descriptions carrierIndicatorSizeDCI-0-2, carrierIndicatorSizeDCI-1-2Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0 2 / 1 2. The field carrierIndicatorSizeDCI-0-2 refers to DCI format 0 2 and the field carrierIndicatorSizeDCI-1-2 refers to DCI format 1_2, respectively (see TS 38.212
[0017] , clause 7.3.1 and TS 38.213
[0013] , clause 10.1).ccs-BlindDetectionSplitIndicates the share of blind detection candidates and non-overlapping CCEs for PDCCH monitoring on an SpCell and an SCell when cross-carrier scheduling is configured from the SCell for the SpCell (see TS 38.213
[0013] , clause 10.1.1). The network only configures this field when it sets the field other for an SpCell, i.e., when it configures cross-carrier scheduling of the SpCell by a PDCCH on an Scell.schedulingCellldIf configured for an SpCell, this field indicates which SCell, in addition to the SpCell, signals the downlink allocations and uplink grants, if applicable, for the concerned SpCell. If configured for an Scell, this field indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell. In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range, except if the UE is configured with LP-WUS and the cell is configured to support cross-carrier scheduling for LP-WUS / WUR as indicated by the parameter wus-CrossCarrier Scheduling. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a different Frequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time.
[0070] The operations described above may more generally be performed in accordance with the flowchart of wireless device performed operations illustrated in Figure 5. Referring toFigure 5, the operation may include receiving, in operation 500, a wake-up signal from a cell of a first DRX group.
[0071] The wake-up signal may include a low power wake-up signal. Additionally, the low power wake-up signal indicates to the wireless device to restart the second timer responsive to the time duration of the first timer not expiring or the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group.
[0072] The operations can further include, responsive to receiving the wake-up signal, activating, in operation 502, PDCCH monitoring of cells of the first DRX group and PDCCH monitoring of cells of a second DRX group. The PDCCH monitoring of cells of the first DRX group may include starting a first timer that includes a time duration for PDCCH monitoring of the cells of the first DRX group. Additionally, the PDCCH monitoring of cells of the second DRX group may include starting a second timer that includes another time duration for PDCCH monitoring of the cells of the second DRX group.
[0073] In some embodiments, the another time duration for PDCCH monitoring of the cells of the second DRX group is a shorter period of time than the time duration for PDCCH monitoring of the cells of the first DRX group.
[0074] According to some embodiments, the operations further include, in operation 504, restarting the second timer responsive to at least one of the time duration of the first timer not expiring and the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group. Restarting the second timer may include reactivating the monitoring for the second DRX group (e.g., as shown in Figure 3) or maintaining activation of the monitoring for the second DRX group (e.g., as shown in Figure 4).
[0075] The PDCCH signal may indicate to the wireless device to restart the second timer. In some embodiments, the PDCCH signal includes downlink control information, DCI, indicating scheduling of a downlink transmission on one of the cells of the first DRX group. In some other embodiments, the PDCCH signal comprises DCI indicating if data is scheduled on cells of the secondary DRX group.
[0076] The operations may further include, responsive to the time duration of the first timer expiring, ceasing activation of the PDCCH monitoring of cells of the first DRX group and activating wake-up signal monitoring for cells of the first DRX group. Additionally, responsive to activating wake-up signal monitoring for cells of the first DRX group, the operations may include ceasing activation of the PDCCH monitoring of cells of the second DRX group.
[0077] Additionally or alternatively, the operations may further include, responsive to the time duration of the first timer expiring, ceasing activation of the PDCCH monitoring of cells of the first DRX group, and responsive to the time duration of the second timer expiring, activating wake-up signal monitoring for cells of the first DRX group.
[0078] The wake-up signal (e.g., a LP-WUS) may indicate to the UE whether to apply the second embodiment described above (i.e., the specified handling of the timers - keep Inactivity timer 2 running as long as Inactivity timer 1 is running as shown in Figure 4) or if it should use legacy behavior (e.g., Timer 2 times out when the timer expires as shown in Figure 3). For example, the wake-up signal (e.g., low power wake-up signal) indicates to the wireless device whether to restart the second timer responsive to the time duration of the first timer not expiring or the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group.
[0079] The time duration of the first timer and the another time duration of the second timer may be determined, by the UE, based on a configuration of the wireless device that includes at least one of a desired level of power consumption of the wireless device and a quality of service of the wireless device. Alternatively, the time duration of the first timer and the another time duration of the second timer may be determined, by a network node, based on a configuration of the wireless device that includes at least one of a desired level of power consumption of the wireless device and a quality of service of the wireless device, and an indication may be provided to the UE to indicate the network node selected time durations for the first and second timers.
[0080] In some of these embodiments, the operations further include providing user data and forwarding the user data to a host via the transmission to the network node.
[0081] The operations described above may more generally be performed in accordance with the flowchart of network node performed operations illustrated in Figure 6. Referring to Figure 6, the operation may include transmitting, in operation 600, a wake-up signal toward a wireless device to trigger activation of PDCCH monitoring of cells of a first DRX group and PDCCH monitoring of cells of a second DRX group. In some embodiments, the wake-up signal comprises a low power wake-up signal. Additionally, the wake-up signal (e.g., low power wake-up signal) may indicate to the wireless device whether the second timer is to restart responsive to a time duration of a first timer not expiring or the wireless device receiving the PDCCH signal.
[0082] Optionally, the operations further include transmitting, in operation 602, a PDCCH signal to the wireless device to trigger restarting of a second timer comprising a time durationfor PDCCH monitoring of the cells of the second DRX group. The PDCCH signal may indicate to the wireless device to restart the second timer.
[0083] In some embodiments, the PDCCH signal includes downlink control information, DCI, indicating scheduling of a downlink transmission on one of the cells of the first DRX group. In some other embodiments, the PDCCH signal includes DCI indicating if data is scheduled on cells of the secondary DRX group.
[0084] Additionally, the network node operations may further include determining a time duration of a first timer of a first DRX group and another time duration of a second timer of a second DRX group based on a configuration of the wireless device that includes at least one of a desired level of power consumption of the wireless device and a quality of service of the wireless device. The network node may provide an indication to the UE to indicate the network node selected time durations for the first and second timers. The indication may be provided in the wake-up signal or in the PDCCH signal.
[0085] Additionally, the operations may further include obtaining user data and forwarding the user data to a host or a user equipment.
[0086] Figure 7 shows an example of a communication system 100 in accordance with some embodiments.
[0087] In the example, the communication system 100 includes a telecommunications network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes or base stations of various types, access network nodes 110A and HOB are depicted (which may be collectively referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 104 may include more than one access network technology. The network nodes 110 of access network 104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 112A, 112B, 112C, and 112D (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.
[0088] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network nodein the telecommunications network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 102, including one or more access network nodes 110 and / or core network nodes 108.
[0089] 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). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0090] The network nodes 110 facilitate direct or indirect connection of one or more UEs 112 to the core network 106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 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 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0091] The UEs 112 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 110 and other communication devices. Similarly, the network nodes 108, 110are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 102) with the UEs 112 and / or with other network nodes or equipment in the telecommunications network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 102. More specifically, UEs 112 may send messages, data, and / or other signals to network nodes 108, 110 or other elements of the telecommunications network 102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 108, 110 may send messages, data, and other signals to UEs 1122, other network nodes 108, 110, and other devices in telecommunications network 102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 112 by transmitting the message to an access network node 110 that will then transmit the message to the intended UE 112. Similarly, a core network node 108 may receive a particular message from a UE 112 by receiving the message from an access network node 110 that itself received the message from the UE 112.
[0092] In the depicted example, the core network 106 connects elements of the access network 104 (e.g., one or more of the network nodes 110) to one or more host computing systems, such as host 116. 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 106 includes one or more core network nodes (e.g., core network node 108) of various types, one or more of which may be generally referred to as network nodes 108. Network nodes 108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).
[0093] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunications network 102. The host 116 may be operated by the service provider or on behalf of the service provider. The host 116 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.
[0094] As a whole, the communication system 100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 100 supporting different standards, protocols, or rule sets.
[0095] As one example, in certain embodiments, access network 104 may contain some access network nodes 110 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 110 support (or the same access network nodes 110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0096] Telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.
[0097] In some examples, one or more of the UEs 112 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 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. 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).
[0098] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112C and / or 112D) and network nodes (e.g., network node HOB). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 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 110, or by executable code, script, process, or other instructions in the hub 114.
[0099] As another example, the hub 114 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 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0100] The hub 114 may have a constant / persistent or intermittent connection to the network node HOB. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112C and / or 112D), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 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 HOB. In other embodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0101] Figure 8 is another example of a communication system 200 according to some embodiments. As used herein, the communication system 200 includes multiple access points (APs) 210 (with four exemplary APs 210A, 210B, 210C, and 210D being depicted) and multiple wireless devices, referred to in the context of communication system 200 as stations (STAs) 212 (referred to individually as STA 212A, STA 212B, STA 212C, STA 212D, and STA 212E). STA 212A is served by AP 210A in a first basic service set (BSS) 220A. STA 210B and STA 210C are served by AP 210B in a second BSS, BSS 220B. STA 212D is served by AP 210C in a third BSS, BSS 220C. STA 212E is served by AP 210D in a fourth BSS, BSS 220D. Stations 212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0102] Each of STAs 212 may connect through a radio link to one of APs 210. For example, depending on location or channel conditions experienced by a given STA 212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., anunlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0103] Each AP 210 may provide data connectivity to STAs 212 connected to a particular AP 210. As illustrated, APs 210 may be connected to a data network 230. In this way, APs 210 may also provide data connectivity between STAs 212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 212 and its serving AP 210 may be used for providing various kinds of services to STA 212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 212 and / or on a device linked to STA 212. By way of example, Figure 8 illustrates an application service platform 232 provided in data network 230. The application(s) executed on STA 212 and / or on one or more other devices linked to STA 212 may use the radio link for data communication with one or more other STA 212 and / or the application service platform 232, thereby enabling utilization of the corresponding service(s) at STA 212.
[0104] Figure 9 shows a wireless device 300, which may be configured to operate in communication system 100 of Figure 7 or in communication system 200 of Figure 8. The wireless device 300 may be alternatively referred to as a UE 300, like a UE 112 within the context of communication system 100, or as a station (STA) 300 or as a non-access-point station (non-AP STA) 300, like a STA 212 within the context of the communication system 200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.
[0105] A wireless device 300 may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle-to-everything (V2X). In other examples, wireless device 300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 300 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).
[0106] In particular embodiments, wireless device 300 includes processing circuitry 302 that is operatively coupled via a bus 304 to an input / output interface 306, a power source 308, a memory 310, a communication interface 312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 300 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 300 to another. In general, in a particular embodiment of wireless device 300, processing circuitry 302, input / output interface 306, power source 308, memory 310, and communication interface 312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 300. Further, certain embodiments of wireless devices 300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0107] The processing circuitry 302 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 310. The processing circuitry 302 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 302 may include multiple central processing units (CPUs).
[0108] In the example, the input / output interface 306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 300. Examples of an input device include a touch-sensitive or presence-sensitivedisplay, 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.
[0109] In some embodiments, the power source 308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 308 may further include power circuitry for delivering power from the power source 308 itself, and / or an external power source, to the various parts of wireless device 300 via input circuitry or an interface such as an electrical power cable. Power source 308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 300 to which power is supplied.
[0110] The memory 310 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 310 includes one or more programs 314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 316. The memory 310 may store, for use by wireless device 300, any of a variety of various operating systems or combinations of operating systems.[OHl] The memory 310 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), suchas a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 310 may allow wireless device 300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 310, which may be or comprise a device-readable storage medium.
[0112] The processing circuitry 302 may be configured to communicate with an access network or other network via or using the communication interface 312. The communication interface 312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 322. The communication interface 312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 318 and / or a receiver 320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 318 and receiver 320 may be coupled to one or more antennas (e.g., antenna 322) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0113] In the illustrated embodiment, communication functions of the communication interface 312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
[0114] In particular embodiments, wireless device 300 may provide an output of data captured via a sensor, through its communication interface 312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 300 can be communicated through a wireless connection to a network node via another wirelessdevice 300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0115] As another example, wireless device 300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 300 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.
[0116] Wireless device 300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 300 shown in Figure 9.
[0117] As yet another specific example, in an loT scenario, wireless device 300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 300 may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, wireless device 300 mayimplement the 3GPP NB-IoT standard. In other scenarios, wireless device 300 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.
[0118] In practice, any number of wireless devices 300 may be used together with respect to a single use case. For example, a first wireless device 300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 300 can also include more than one of the functionalities described above. For example, wireless device 300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0119] Figure 10 shows a network node 400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 400 may be configured to operate in communication system 100 of Figure 7, like network nodes 108 or 110, or in communication system 200 of Figure 8, like an AP 210 or a station 212. 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)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, O-DU, O-CU).
[0120] Network nodes 400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 400 may be a relay node or a relay donor node controlling a relay. Network nodes 400 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).
[0121] Other examples of network nodes 400 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).
[0122] In particular embodiments, network node 400 includes a processing circuitry 402, a memory 404, a communication interface 406, and a power source 408. In general, in a particular embodiment of network node 400, processing circuitry 402, memory 404, communication interface 406, and power source 408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 400.
[0123] The network node 400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 404 or portions of memory 404 for different RATs) and some components may be reused (e.g., a same antenna 410 may be shared by different RATs). The network node 400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 400.
[0124] The processing circuitry 402 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 logicoperable to provide, either alone or in conjunction with other components, such as the memory 404, to provide network node 400 functionality.
[0125] In some embodiments, the processing circuitry 402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 402 includes one or more of radio frequency (RF) transceiver circuitry 412 and baseband processing circuitry 414. In some embodiments, the RF transceiver circuitry 412 and the baseband processing circuitry 414 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 412 and baseband processing circuitry 414 may be on the same chip or set of chips, boards, or units.
[0126] The memory 404 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 402. The memory 404 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 402 and utilized by the network node 400. The memory 404 may be used to store any calculations made by the processing circuitry 402 and / or any data received via the communication interface 406. In some embodiments, the processing circuitry 402 and memory 404 is integrated.
[0127] The communication interface 406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 406 comprises port(s) / terminal(s) 416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 300 may be capable of wireless communication and communication interface 406 may also include radio front-end circuitry 418 that may be coupled to, or in certain embodiments a part of, an antenna 410. Particular embodiments of radio front-end circuitry 418 include filter(s) 420 and amplifier(s) 422. The radio front-end circuitry 418 may be connected to an antenna 410 and processing circuitry 402. The radio frontend circuitry may be configured to condition signals communicated between antenna 410 and processing circuitry 402. The radio front-end circuitry 418 may receive digital data that is tobe sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 420 and / or amplifiers 422. The radio signal(s) may then be transmitted via the antenna 410. Similarly, when receiving data, the antenna 410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 418. The digital data may be passed to the processing circuitry 402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0128] In certain alternative embodiments, network node 400 may be capable of wireless communication but does not include separate radio front-end circuitry 418, instead, the processing circuitry 402 includes radio front-end circuitry and is connected to the antenna 410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 412 is part of the communication interface 406. In still other embodiments, the communication interface 406 includes one or more ports or terminals 416, the radio front-end circuitry 418, and the RF transceiver circuitry 412, as part of a radio unit (not shown), and the communication interface 406 communicates with the baseband processing circuitry 414, which is part of a digital unit (not shown).
[0129] The antenna 410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 410 may be coupled to the radio front-end circuitry 418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 410 is separate from the network node 400 and connectable to the network node 400 through one or more interfaces or ports.
[0130] The antenna 410, communication interface 406, and / or the processing circuitry 402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 410, the communication interface 406, and / or the processing circuitry 402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.
[0131] The power source 408 provides power to the various components of network node 400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 408 may further comprise, or be coupledto, power management circuitry to supply the components of the network node 400 with power for performing the functionality described herein. For example, the network node 400 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 408. As a further example, the power source 408 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.
[0132] Embodiments of the network node 400 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 400 may include user interface equipment to allow input of information into the network node 400 and to allow output of information from the network node 400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 400.
[0133] Figure 11 is a block diagram illustrating a virtualization environment 500 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 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0134] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0135] Hardware 504 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 508A and VM 508B (which may be collectively referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 508.
[0136] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, 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.
[0137] In the context of NFV, each of the VMs 508 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 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 508 on top of the hardware 504 and corresponds to an application 502.
[0138] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 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 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 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. Insome embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.
[0139] 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.
[0140] 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.ABBREVIATIONS
[0141] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3 GPP 3rd Generation Partnership Project5G 5th Generation6G 6thGenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplex AccessCGI Cell Global IdentityCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCQI Channel Quality InformationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)Ec / No Received energy per chip divided by the power density in the band eDRX Extended Discontinuous ReceptioneMBMS Evolved Multimedia Broadcast Multicast ServicesECGI Evolved CGIeNB E-UTRAN NodeBePDCCH Enhanced Physical Downlink Control ChannelE-SMLC Evolved Serving Mobile Location CenterE-UTRAN Evolved Universal Terrestrial Radio Access NetworkFDD Frequency Division DuplexFFS For Further StudyBase station in NRGNSS Global Navigation Satellite SystemHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMAC Message Authentication CodeMBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDCP Packet Data Convergence ProtocolPDP Power Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoding Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLC Radio Link ControlRLM Radio Link MonitoringRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power OR Reference Signal Received Power RSRQ Reference Signal Received Quality OR Reference Symbol Received QualityRS SI Received Signal Strength Indicator RSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDAP Service Data Adaptation ProtocolSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self-Organizing NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wideband CDMAWLAN Wireless Local Area NetworkREFERENCES
[0142] A listing of documents referenced herein follows:
[0143] [1], 3GPP TR 38.869, VO.4.0, “Study on low-power Wake-up Signal and Receiver for NR”, Aug. 2023.
[0144] [2], RP -234056, New WID: Low-power wake-up signal and receiver for NR (LP WUS / WUR)
Claims
CLAIMS1. A method performed by a wireless device for Physical Downlink Control Channel, PDCCH, monitoring in a plurality of discontinuous reception, DRX, groups, the method comprising:receiving (500) a wake-up signal from a cell of a first DRX group;responsive to receiving the wake-up signal, activating (502) PDCCH monitoring of cells of the first DRX group and PDCCH monitoring of cells of a second DRX group, wherein the PDCCH monitoring of cells of the first DRX group comprises starting a first timer that comprises a time duration for PDCCH monitoring of the cells of the first DRX group, and the PDCCH monitoring of cells of the second DRX group comprises starting a second timer that comprises another time duration for PDCCH monitoring of the cells of the second DRX group; andrestarting (504) the second timer responsive to at least one of the time duration of the first timer not expiring and the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group.
2. The method of claim 1, wherein the another time duration for PDCCH monitoring of the cells of the second DRX group is a shorter period of time than the time duration for PDCCH monitoring of the cells of the first DRX group.
3. The method of any of claims 1 to 2, further comprising:responsive to the time duration of the first timer expiring, ceasing activation of the PDCCH monitoring of cells of the first DRX group and activating wake-up signal monitoring for cells of the first DRX group.
4. The method of claim 3, further comprising:responsive to activating wake-up signal monitoring for cells of the first DRX group, ceasing activation of the PDCCH monitoring of cells of the second DRX group.
5. The method of any of claims 1 to 2, further comprising:responsive to the time duration of the first timer expiring, ceasing activation of the PDCCH monitoring of cells of the first DRX group; andresponsive to the time duration of the second timer expiring, activating wake-up signal monitoring for cells of the first DRX group.
6. The method of any of claims 1 to 5, wherein the wake-up signal comprises a low power wake-up signal.
7. The method of claim 6, wherein the low power wake-up signal indicates to the wireless device whether to restart the second timer responsive to the time duration of the first timer not expiring or the wireless device receiving a PDCCH signal on a PDCCH of one of the cells of the first DRX group.
8. The method of any of claims 1 to 7, wherein the PDCCH signal indicates to the wireless device to restart the second timer.
9. The method of claim 8, wherein the PDCCH signal comprises downlink control information, DCI, indicating scheduling of a downlink transmission on one of the cells of the first DRX group.
10. The method of claim 8, wherein the PDCCH signal comprises downlink control information, DCI, indicating if data is scheduled on cells of the secondary DRX group.
11. The method of claim 1, wherein the time duration of the first timer and the another time duration of the second timer are determined based on a configuration of the wireless device that includes at least one of a desired level of power consumption of the wireless device and a quality of service of the wireless device.
12. The method of any of the claims, further comprising:providing user data; andforwarding the user data to a host via the transmission to the network node.
13. A method performed by a network node for enabling wireless device Physical Downlink Control Channel, PDCCH, monitoring in a plurality of discontinuous reception, DRX, groups, the method comprising:transmitting (600) a wake-up signal toward a wireless device to trigger activation of PDCCH monitoring of cells of a first DRX group and PDCCH monitoring of cells of a second DRX group.
14. The method of claim 13, further comprising:transmitting (602) a PDCCH signal to the wireless device to trigger restarting of a second timer comprising a time duration for PDCCH monitoring of the cells of the second DRX group.
15. The method of claim 14, wherein the PDCCH signal indicates to the wireless device to restart the second timer.
16. The method of claim 15, wherein the PDCCH signal comprises downlink control information, DCI, indicating scheduling of a downlink transmission on one of the cells of the first DRX group.
17. The method of claim 15, wherein the PDCCH signal comprises downlink control information, DCI, indicating if data is scheduled on cells of the secondary DRX group.
18. The method of any of claims 13 to 17, wherein the wake-up signal comprises a low power wake-up signal.
19. The method of claim 18, wherein the low power wake-up signal indicates to the wireless device whether the second timer is to restart responsive to a time duration of a first timer not expiring or the wireless device receiving the PDCCH signal.
20. The method of any of the previous claims, further comprising:obtaining user data; andforwarding the user data to a host or a user equipment.
21. A wireless device for Physical Downlink Control Channel, PDCCH, monitoring in a plurality of discontinuous reception, DRX, groups, comprising:processing circuitry configured to perform any of the operations of any of the claims 1-12; anda power source configured to supply power to the processing circuitry.
22. A network node for enabling wireless device Physical Downlink Control Channel, PDCCH, monitoring in a plurality of discontinuous reception, DRX, groups, the network nodecomprising:processing circuitry configured to perform any of the operations of any of the claims 13-20;a power source circuitry configured to supply power to the processing circuitry.
23. A wireless device for Physical Downlink Control Channel, PDCCH, monitoring in a plurality of discontinuous reception, DRX, groups, the wireless device comprising:one or more antennas;communication interface connected to the one or more antennas and to processing circuitry;the processing circuitry being configured to perform any of the operations of any of the claims 1-12;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda power source connected to the processing circuitry and configured to supply power to the UE.
