Transmission trigger using a separate low-power wake-up receiver

Abstract

Various embodiments herein provide techniques related to a main receiver of a user equipment (UE) and a wake-up receiver (WUR) of the UE. In an embodiment, the WUR may receive a low-power wake-up signal (LP-WUS) from a base station. Based on the LP-WUS, the WUR may be configured to wake up the main receiver of the UE. Other embodiments may be described and / or claimed.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority to U.S. Provisional Patent Application No. 63 / 389,275, filed on July 14, 2022; No. 63 / 389,278, filed on July 14, 2022; No. 63 / 389,280, filed on July 14, 2022; No. 63 / 411,465, filed on September 29, 2022; No. 63 / 411,542, filed on September 29, 2022; and U.S. Provisional Patent Application No. 63 / 484,957, filed on February 14, 2023.

[0002] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to techniques associated with low - power wake - up receivers.

Background Art

[0003] Various embodiments may generally relate to the field of wireless communication.

Brief Description of the Drawings

[0004] Embodiments can be readily understood by the following detailed description in conjunction with the accompanying drawings. For the sake of facilitating this description, like structural elements shall be denoted by like reference numerals. Embodiments are shown by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1

[0005]

Figure 2

[0006]

Figure 3

[0007]

Figure 4

[0008]

Figure 5

[0009]

Figure 6

[0010]

Figure 7

[0011]

Figure 8

[0012]

Figure 9

[0013]

Figure 10

[0014]

Figure 11

[0015]

Figure 12

[0016]

Figure 13

[0017]

Figure 14

[0018]

Figure 15

[0019]

Figure 16

[0020]

Figure 17

[0021]

Figure 18

[0022]

Figure 19

[0023]

Figure 20

[0024]

Figure 21

[0025]

Figure 22

[0026]

Figure 23

[0027]

Figure 24

[0028]

Figure 25

[0029]

Figure 26

[0030]

Figure 27

MODE FOR CARRYING OUT THE INVENTION

[0031] The following detailed description refers to multiple accompanying drawings. The same reference numbers may be used to identify the same or similar elements in different drawings. In the following description, for purposes of explanation and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are described to provide a deep understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that the various aspects of the various embodiments can be implemented in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this specification, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0032] The 5th generation (5G) system can be designed and developed targeting one or both of mobile phones and vertical use cases. In addition to latency, reliability, and availability, the energy efficiency of user equipment (UE) can also be considered important for 5G. Existing 5G devices may need to be recharged weekly or daily depending on individual usage times. Generally, 5G devices consume tens of milliwatts in the radio resource control (RRC) idle / inactive state and hundreds of milliwatts in the RRC connected state. Designs for extending battery life may improve energy efficiency and / or provide a better user experience.

[0033] The power consumption depends on the configured length of the wake-up period, for example, the paging cycle. To meet the battery life requirement, it is expected that a long discontinuous reception (DRX) cycle will result in high latency, which may not be appropriate for such services with both long battery life and low latency requirements. For example, in a fire detection and extinguishing use case, a fire shutter may need to be closed, but a fire sprinkler will be turned on by an actuator within 1 to 2 seconds from the time detected by a sensor. With a long DRX cycle, it may not be possible to meet the delay requirement. Therefore, it may be desirable to reduce power consumption with reasonable latency.

[0034] In a legacy implementation, the UE may need to wake up periodically once per DRX cycle, which can be advantageous for power consumption during periods without signaling or data traffic. If the UE can wake up only when triggered (e.g., paging), the power consumption can be dramatically reduced. Such reduction can be achieved by triggering the main radio using a wake-up signal (WUS). The WUS can be received by a separate receiver having the ability to monitor the WUS with ultra-low power consumption. Such a receiver may be referred to herein as a WUR or a low-power WUR (LP-WUR). The main receiver of the UE may function for data transmission and reception and may be turned off or set to deep sleep unless turned on (e.g., via reception of a WUS).

[0035] FIG. 1 shows one example of the use of the main receiver and the WUR. In a power-saving state, if there is no WUS received by the WUR, the main receiver may remain off for deep sleep. On the other hand, if a WUS is received by the WUR, the WUR may trigger the main receiver to turn on. In the latter case, since the main receiver is active, the WUR may be turned off.

[0036] The power consumption for monitoring the WUS may depend on the WUS design used for signal detection and processing and the hardware modules of the WUR. In the present disclosure, an exemplary basic design regarding the wake-up signal / channel transmission procedure is disclosed. In particular, embodiments may relate to discontinuous reception (DRX) in an idle / inactive state (e.g., RRC idle or inactive state); DRX in a connected state (e.g., RRC connected state); and / or continuous LP-WUS monitoring in a connected state and may relate to one or more of the above. [DRX in an idle / inactive state] For DRX operation of a UE in idle / inactive state according to the 3rd Generation Partnership Project (3GPP (registered trademark)) New Radio (NR) Release-17 (Rel-17) specification, a Physical Downlink Control Channel (PDCCH) with a Permanent Equipment Identifier (PEI), for example, a Downlink Control Information (DCI) format 2_7 indicating whether a subgroup within a paging group of the UE is paged in a coming paging opportunity, is introduced. Further, the PEI PDCCH may also indicate a Tracking Reference Signal (TRS) availability indication for the idle / inactive state. However, decoding of the PEI PDCCH requires detecting at least a System Synchronization Block (SSB) or a TRS for the idle / inactive state for at least Automatic Gain Control (AGC) and time / frequency synchronization. The UE may also need to perform Radio Resource Management (RRM) measurements based on the SSB. In summary, in each paging cycle, the UE still needs to detect at least an SSB or a TRS for the idle / inactive state and detect the PEI PDCCH, which still consumes a lot of power. To further reduce power consumption, a separate Low-Power Wake-Up Receiver (LP-WUR) may be used to detect a Low-Power Wake-Up Signal (LP-WUS), and the main receiver is always active when the LP-WUS is detected. Here, it is assumed that a periodic TRS configured in the idle / inactive mode is used by the TRS.

[0037] The LP-WUS can serve the following purposes, namely, The LP-WUS can be used for cell selection, for example, the UE can identify a cell and perform RRM measurements based on the LP-WUS. The LP-WUS can be used to determine paging reception. The LP-WUS can be used to determine System Information Block (SIB) reception. The LP-WUS can be used to acquire synchronization. and can fulfill at least one of the following. To serve corresponding purposes, single or multiple different types of LP-WUS may be supported.

[0038] For example, for all purposes, a single LP-WUS configuration may be applied. In another example, multiple different types of LP-WUS may be configured to serve different purposes, for example, to enable RRM measurements. A first type of LP-WUS that carries information for identifying a cell (e.g., a cell identifier (ID)) may be transmitted periodically, and a second type of LP-WUS that wakes up the UE to receive other DL channels / signals or transmit UL channels / signals may be transmitted aperiodically. The second type of LP-WUS may further be configured using a period, but the gNB only transmits the LP-WUS on demand. To receive the first and second types of LP-WUS, the UE does not need to turn on the main radio, and the UE turns on the main radio only when the UE detects a specific type of LP-WUS that instructs the UE to turn on the main radio, for example, the second type of LP-WUS that instructs paging reception for the UE.

[0039] The UE may receive one type of LP-WUS in response to receiving another type of LP-WUS. For example, the UE receives another type of LP-WUS only if the UE can receive a first type of LP-WUS that includes an RRM result greater than a threshold.

[0040] The UE may receive one type of LP-WUS according to a configuration or condition. For example, if the RRM result based on a legacy procedure (e.g., by Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) or Channel State Information Reference Signal (CSI-RS)) or based on a first type of LP-WUS is greater than a specific threshold, or if the difference between the last and current RRM results is not greater than a specific threshold, the UE can receive a second type of LP-WUS; otherwise, the UE skips receiving the second type of LP-WUS. Instead, the UE may need to turn on the main radio to perform corresponding reception, e.g., legacy paging reception.

[0041] In the following embodiments, the LP-WUS may include one or more parts. For example, the LP-WUS may include two parts. The first part is a sequence for LP-WUS detection, and the second part is a payload, e.g., including UE subgroup information and / or other downlink (DL) channel / signal reception indication. For example, in the case of an LP-WUS including only a single part, the LP-WUS may be generated by a sequence or by encoding payload information. For example, if the first part is detected using an energy or power level higher than a threshold, the UE may further detect the second part. In other words, the first part is an indicator as to whether the second part is transmitted.

[0042] In one example, the first type of LP-WUS may be sequence-based, while the second type of LP-WUS can encode and transmit payload information. The first type of LP-WUS may be used for synchronization and measurement purposes, e.g., for RRM measurement. Next, the second type of LP-WUS may be processed based on the detected first type of LP-WUS. The second type of LP-WUS can carry wake-up information. In some embodiments, the second type of LP-WUS may also be used for measurement purposes.

[0043] In another example, the first type of LP-WUS may be sequence-based, while the second type of LP-WUS may include two parts. The first type of LP-WUS can be used for synchronization and RRM purposes. Next, the second type of LP-WUS can be processed based on the detected first type of LP-WUS. The second type of LP-WUS can carry wake-up information. The second type of LP-WUS can also be used for RRM purposes.

[0044] In one embodiment, if RRM measurements are still valid for the UE (which indicates that the UE is still within the current cell), the UE can monitor the LP-WUS to determine whether the main receiver needs to be woken up by the UE within the paging cycle. Once the main receiver is turned on within the paging cycle, it can be left to the UE implementation to re-perform RRM measurements, for example, based on the detected SSB or CSI-RS. On the other hand, if the RRM measurements become invalid, the UE may not detect the configured LP-WUS. Therefore, the UE can perform RRM measurements, detect the PEI PDCCH, and / or detect the paging PDSCH according to one or more legacy 3GPP procedures.

[0045] In one option, the UE can perform RRM measurements based on legacy NR reference signals. For example, the UE turns on the main radio to receive the SS / PBCH. If cell reselection is triggered by the RRM measurements, the UE can start the initial access process of the new cell according to the legacy process. During cell reselection, the UE can skip one or more LP-WUS opportunities. After the UE has completed cell reselection or if cell reselection is not triggered by the RRM measurements, the UE monitors subsequent LP-WUS within a specific period, for example, within several paging cycles, assuming that the selected cell will not change after the last RRM measurement.

[0046] In another option, the UE may perform RRM measurements based on a first type of LP-WUS for which it may not be necessary to turn on the main radio. If cell reselection is triggered by the RRM measurements, the UE may attempt to perform cell reselection based on the first type of LP-WUS of other cells. During cell reselection, the UE may skip specific LP-WUS opportunities, e.g., LP-WUS opportunities of a second type of LP-WUS. After the UE has completed cell reselection or if cell reselection is not triggered by the RRM measurements, the UE may monitor subsequent LP-WUS within a specific period, e.g., monitor a second type of LP-WUS.

[0047] In another option, the UE can perform RRM measurements based on LP-WUS and legacy NR reference signals. The UE may first perform RRM measurements based on LP-WUS. If cell reselection is triggered by the RRM measurements based on LP-WUS, the UE can turn on the main radio and start the initial access process of the new cell according to the legacy process (e.g., based on SS / PBCH). During cell reselection, the UE can skip LP-WUS opportunities. If cell reselection is not triggered by the RRM measurements based on LP-WUS or after the UE has completed cell reselection by the legacy procedure, the UE may monitor subsequent LP-WUS within a specific period on the assumption that the selected cell will not change after the last RRM measurement.

[0048] In one embodiment, multiple options for performing RRM measurements by LP-WUS may be considered. The UE may derive RRM measurements based on only the first part of LP-WUS. Alternatively, the UE may derive RRM measurements based on only the second part of LP-WUS. Alternatively, the UE may derive RRM measurements based on both the first and second parts of LP-WUS.

[0049] In one option, the UE may perform RRM measurements based only on the LP-WUS sent to the UE. The second part of the LP-WUS may include the UE's group ID, subgroup ID, or unicast ID.

[0050] In another option, the UE may perform RRM measurements based on the LP-WUS regardless of whether the LP-WUS is indicated to the UE or not. For example, if the LP-WUS is for other UEs, the UE can still receive the WUS symbol of the LP-WUS and derive RRM measurements. However, since the LP-WUS is not for the UE, the UE does not wake up the main radio.

[0051] In another option, a special LP-WUS may be sent by a base station such as a gNodeB (gNB). The special LP-WUS may indicate that the UE performs RRM measurements based on the LP-WUS. Specifically, this special LP-WUS may have the same structure as other LP-WUSs, but the second part of the LP-WUS may carry a broadcast ID indicating that this LP-WUS is for RRM measurements. Alternatively, this special LP-WUS may use a specific resource different from other LP-WUSs, for example, a sequence different from other LP-WUSs. Other functions are not excluded for the special LP-WUS. The special LP-WUS may be sent at a predefined, preconfigured, or upper layer-configured period.

[0052] In one embodiment, for RRM measurements by the LP-WUS, the UE may expect that at least one LP-WUS is available for RRM measurements within a certain period.

[0053] In one option, the UE may expect that the above special LP-WUS is periodically sent by the gNB and then used for RRM measurements.

[0054] In another option, assuming that the UE supports RRM based on LP-WUS other than the above-mentioned special LP-WUS, if the gNB transmits LP-WUS to one or more UEs within a certain period, the gNB may not need to transmit the special LP-WUS. In other words, if the gNB does not transmit any other LP-WUS within a certain period, the gNB can transmit the special LP-WUS so that the UE can perform at least one RRM within a certain period.

[0055] In one embodiment, the LP-WUS may be configured for a UE that provides some or all of the functions of the PEI PDCCH defined in Rel-17. In one example, it is not excluded that the LP-WUS may indicate more information than that provided by the PEI PDCCH.

[0056] In one option, an early indication of a subgroup of paging opportunities and / or a TRS availability indication defined for downlink control information (DCI) format 2_7 may be indicated by the LP-WUS. For example, Paging Indication Field -

Number

Number

Number

[0057] Figure 2 shows one example of the use of LP-WUS to indicate paging early indication and TRS availability indication. In part (A) of Figure 2, the UE detects a valid indication of LP-WUS (ON), indicating that the UE's paging subgroup has been triggered. Next, the UE can wake up the main receiver for detection in the associated paging opportunity (PO). Assuming that the TRS for the idle / inactive state is not available, the UE may need to detect one or more (three SSBs are assumed in part (A) of Figure 2) SSBs for the serving cell RRM measurement and / or fine time / frequency synchronization required before receiving the paging PDSCH. In part (B) of Figure 2, one difference from part (A) of Figure 2 is the availability of the TRS for the idle / inactive state. After the main receiver is turned on, the UE may detect one SSB of RRM and one additional TRS for fine time / frequency synchronization for receiving the paging PDSCH. In part (C) of Figure 2, one difference from part (B) of Figure 2 may be based on the assumption that RRM is not required within the current paging cycle. After the main receiver is turned on, the UE may detect only the TRS for fine time / frequency synchronization for receiving the paging PDSCH. In part (D) of FIG. 2, the UE detects an LP-WUS (off) indicating that the paging subgroup for the UE has not been triggered. If the UE does not need to perform RRM measurements within the current paging cycle, the UE does not wake up the main receiver at all. Alternatively, if the LP-WUS can be used for RRM, the UE may determine RRM measurements and does not wake up the main receiver at all.

[0058] In one embodiment, the LP-WUS may be configured for a UE that provides a part of the functionality of the PEI PDCCH defined in Rel-17. It is not excluded that the LP-WUS may indicate more information than that provided by the PEI PDCCH.

[0059] In one option, an early indication for the paged UE and / or a TRS availability indication defined for DCI format 2_7 may be indicated by the LP-WUS. For example, Paging indication field - ID of the paged UE. TRS availability indication - 1, 2, 3, 4, 5 or 6 bits, where if configured, the number of bits is equal to the maximum value of all indBitIDs provided by TRS-ResourceSetConfig plus 1; otherwise, 0 bits.

[0060] In this option, LP-WUS may also indicate the intended behavior for paged UEs. For example, a short message indication, with or without a short message, may be indicated by LP-WUS. As a result, once the UE knows that it has been paged by LP-WUS, if the UE is ready to receive control / data, it may start receiving other control / data regardless of the relevant timing among other control / data POs and timings. For example, even if the system information update is earlier than the PO following the physical random access channel (PRACH) transmission from the main radio or the reception of message 2 or message B, the UE may start monitoring the system information update.

[0061] Figure 3 shows an example of the use of LP-WUS to indicate a specific paged UE and the TRS availability indication. Since the paged UE may already have been indicated by LP-WUS, the UE may not need to monitor the PO again. When the UE is paged, the UE may turn on the main receiver for other control / data reception. In part (A) of Figure 3, if LP-WUS (ON) indicates that the UE is being paged, the UE can wake up the main receiver. Assume that since the TRS for the idle / inactive state is not available, the UE may need to detect three SSBs for the fine time / frequency synchronization RRM required for control / data reception. For example, the control / data may mean the control / data related to the system information update or the reception of message 2 or message B following the PRACH transmission from the main radio. In part (B) of Figure 3, the difference from part (A) of Figure 3 is the availability of the TRS for the idle / inactive state. After the main receiver is turned on, the UE may detect one SSB of the RRM and one additional TRS for the fine time / frequency synchronization for control / data reception. In part (C) of FIG. 3, the difference from part (B) of FIG. 3 can be based on the assumption that RRM is not required within the current paging cycle. After the main receiver is turned on, the UE can detect only the TRS for fine time / frequency synchronization for control / data reception. In part (D) of FIG. 3, the UE detects LP-WUS (off) indicating that the UE is not being paged. If the UE does not need to perform RRM measurements within the current paging cycle, the UE does not wake up the main receiver at all. Alternatively, if LP-WUS can be used for RRM, the UE may determine RRM measurements and does not wake up the main receiver at all.

[0062] In another option, LP-WUS may indicate that the group of UEs of the PO is being paged and / or the TRS availability indication defined for DCI format 2_7. Since LP-WUS can indicate that the group is being paged, the UE can be configured to monitor the PEI PDCCH to know the paged subgroup of the PO when the PEI and paging subgroup are configured. For example, Paging Indication Field -

Number

Number

[0063] In this option, the LP-WUS may include only one bit to indicate whether any of the associated POs are paged and whether the information carried by the LP-WUS is minimized.

[0064] Figure 4 shows an example of the use of LP-WUS to indicate paging early indication and TRS availability indication. In part (A) of Figure 4, the UE detects a valid indication of LP-WUS (ON), indicating that the paging group of the PO has been paged. Next, the UE wakes up the main receiver for the detection of PDCCH PEI to know the paged subgroup. Assuming that the TRS for the idle / inactive state is not available, the UE may need to detect three SSBs for the fine time / frequency synchronization required for RRM, PEI PDCCH detection, and reception of the paging PDSCH. In part (B) of Figure 4, the difference from part (A) of Figure 4 is the availability of the TRS for the idle / inactive state. After the main receiver is turned on, the UE may detect one SSB of RRM and PEI PDCCH detection and one additional TRS for the fine time / frequency synchronization for the reception of the paging PDSCH. In part (C) of Figure 4, the difference from part (B) of Figure 4 may be the assumption that RRM is not required within the current paging cycle. After the main receiver is turned on, the UE may detect only the TRS for the fine time / frequency synchronization for the reception of the PEI PDCCH and the paging PDSCH. In part (D) of Figure 4, the UE may detect LP-WUS (off), indicating that the paging group for the UE is not paged. If the UE does not need to perform RRM measurements within the current paging cycle, the UE does not wake up the main receiver at all. Alternatively, if LP-WUS can be used for RRM, the UE may determine RRM measurements and not wake up the main receiver at all.

[0065] In the above embodiment, LP-WUS may be configured to indicate some or all of the following information. It is not excluded that LP-WUS may indicate more information than that provided by PEI PDCCH. Paging early indication that may indicate a group of UEs of a PO, a subgroup of a group of UEs of a PO, or UEs to be paged. TRS for idle / inactive indication that may be defined in DCI format 2_7 Other control / data reception indication For example, LP WUS may indicate whether to receive paging PDCCH / PDSCH after turning on the main receiver. Similar to the short message indicator and / or short message defined in DCI format 1_0 in Type 2 CSS sets such as Table 7.3.1.2.1-1 in 3GPP TS38.212 and Table 6.5-1 in 3GPP TS38.331, LP WUS may indicate that a control / data channel is received after turning on the main receiver. Tables 1 and 2 provide two examples.

[0066] [Table 7.3.1.2.1-1: Short message indicator]

Table 1

Table 2

Table 3

Table 4

[0067] In one option, if the gNB expects the UE to turn on the main receiver when the UE turns on the main receiver, the gNB sends the LP-WUS to the UE, or a group / subgroup of the UE. If the UE does not detect the LP-WUS targeted at the UE, the UE may not turn on the main receiver. This is the most power-efficient for the UE.

[0068] In another option, the gNB sends the LP-WUS to the UE, or a group / subgroup of the UE, together with information about whether the UE should turn on the main receiver. For example, 1 bit in the LP-WUS indicates whether to turn on the main receiver. If the UE does not detect the LP-WUS instructing the UE to wake up the main receiver, the UE turns on the main receiver to receive the legacy DL signal / channel, for example, to monitor the PEI and / or PO according to the legacy procedure. In this way, if the UE fails to detect the LP-WUS from the gNB, the UE can still receive paging.

[0069] [DRX in the connected state] For the DRX operation of the UE operating in the connected state according to the 3GPP NR Release-16 (Rel-16) specification, a DCI format, for example, DCI format 2_6 indicating that the UE should wake up for PDCCH monitoring within the DRX ON duration, is introduced. Further, DCI format 2_6 may also indicate 5 bits for SCell suspension switching.

[0070] In one embodiment, for a UE in a connected state, the LP-WUS may be configured to indicate to the UE whether to turn on the main receiver within a certain period. For example, LP-WUS opportunities are configured using a period. Within a certain period, the LP-WUS indicates whether to turn on the main receiver.

[0071] In one embodiment, the LP-WUS may be configured to indicate to the UE whether to skip control / data reception within the UE's next DRX ON duration, e.g., PDCCH monitoring in the UE-specific search space within the next DRX ON duration, while the behavior of the UE during the DRX OFF period is the same as the legacy behavior. The LP-WUS may indicate only 1 bit for wake-up indication. The LP-WUS may indicate only 1 or more bits of SCell suspension indication. Alternatively, the LP-WUS may include 1 bit for wake-up indication and 1 or more bits of SCell suspension indication. It is not excluded that the LP-WUS may indicate more information than that provided by DCI format 2_6. There is a delay between the LP-WUS and the time when the UE is ready for reception within the DRX ON duration, which may be predefined and configured by the upper layer or determined by UE capability reporting.

[0072] Parts (A) to (C) of FIG. 5 show examples related to the indication of control / data transmission within the DRX ON duration by the existing DCI format 2_6 in NR or LP-WUS. Part (A) of FIG. 5 shows an example of legacy behavior, and the UE may be configured to monitor the corresponding bit in DCI format 2_6 to know whether the UE has control / data transmission within the DRX ON duration on the PCell or SCell. In part (B) of FIG. 5, the UE may detect a valid indication of LP-WUS (ON) for control / data reception within the next DRX ON duration. The UE may wake up the main receiver for detection of control / data transmission within the DRX ON duration. The power consumption for monitoring LP-WUS is much lower than that of DCI format 2_6. In part (C) of FIG. 5, assume that the UE does not detect LP-WUS (off) for control / data reception within the next DRX ON duration and the UE cannot wake up the main receiver.

[0073] Note: In part (A) or (B) of FIG. 5, the UE may already have valid AGC and time / frequency synchronization, so the UE may directly receive control / data transmission within the DRX ON duration. Alternatively, the LP WUS may also indicate whether some signal / channel is received before the DRX ON duration, such as an aperiodic TRS. Next, the UE should turn on the main receiver before such signal / channel, and then the UE can set up the AGC and / or perform time / frequency synchronization before the DRX ON duration.

[0074] In one embodiment, the LP-WUS may be configured to indicate to the UE whether to receive control / data within the next DRX ON duration of the UE and whether to receive a specific signal during the DRX OFF period.

[0075] In one option, the LP-WUS may indicate that the UE may turn off the main receiver during the DRX ON and / or OFF periods within the LP-WUS period.

[0076] In another option, the LP-WUS may instruct the UE to skip reception of any control / data during the DRX ON and / or OFF periods within the LP-WUS period.

[0077] In another option, LP-WUS may instruct the UE to skip receiving specific control / data during DRX ON and / or OFF periods within the LP-WUS period. This specific control / data may be at least one of DL or UL control / data configured by the UE-specific upper layer, cell-specific DL or UL control / data, cell-specific reference signals, and reference signals other than RSs for specific purposes, e.g., for RRM measurements.

[0078] [LP-WUS Monitoring in Connected State] In one embodiment, LP-WUS may be applicable at least within the DRX ON duration or when the DRX operation is not configured. The UE may continuously monitor LP-WUS or monitor LP-WUS in short cycles. When an LP-WUS indicating that the UE's control / data is scheduled is detected, the UE can turn on the main receiver for receiving the control / data. Note: In the connected state, the UE may already have a valid AGC and time / frequency synchronization. Therefore, the UE can directly receive control / data transmission by the main receiver after waking up. Otherwise, the UE needs to use the main receiver to detect specific DL channels / signals to set up the AGC and / or time / frequency synchronization. There is a delay between LP-WUS and the time when the UE is ready to receive using the main radio, which may be predefined and configured by the upper layer or determined by UE capability reporting.

[0079] LP-WUS may indicate only 1 bit for the wake-up indication. LP-WUS may indicate only 1 or more bits of SCell suspension indication. Alternatively, LP-WUS may include 1 bit for the wake-up indication and 1 or more bits of secondary cell (SCell) suspension indication. It is not excluded that LP-WUS may indicate more information than that provided by DCI format 2_6.

[0080] FIG. 6 shows an example of continuous LP-WUS monitoring. If the UE does not detect an LP-WUS (off) indicating that control / data reception is scheduled, the UE does not have to wake up the main receiver. If the UE detects a valid indication of an LP-WUS (on) indicating that control / data reception is scheduled, the UE may wake up the main receiver for reception.

[0081] LP-WUS may be configured to indicate information for the UE regarding PDCCH skip or search space set group (SSSG) switching. For example, the UE may be configured to detect LP-WUS instead of monitoring DCI formats 0_1, 0_2, 1_1, 1_2 for PDCCH skip or SSSG switching.

[0082] LP-WUS may indicate the same set of information about LP-WUS within the DRX OFF or DRX ON duration. Alternatively, some of the information carried by LP-WUS may be different for LP-WUS configured in the DRX OFF or DRX ON duration.

[0083] [Duty Cycle of LP-WUS] In some embodiments, the power consumption associated with monitoring WUS may depend on the WUS design and the hardware modules of the WUR used for signal detection and processing. This section describes some basic designs regarding the wake-up signal / channel transmission procedure. In particular, the embodiments are the configured duty cycle of LP-WUS LP-WUS determined by DRX of other channels / signals may be related to one or more of these. This separate LP-WUR may have the advantage of extremely low power consumption. On the other hand, it is still beneficial to consider duty cycle-based operation for the LP-WUR. In such cases, the LP-WUR only needs to be active during the period when the LP-WUS can be transmitted to the UE.

[0084] In one embodiment, the parameters of the duty cycle-based operation of the LP-WUS may be configured according to the timing of the main receiver. The duty cycle period shown as wus-Cycle The start offset of LP-WUS detection within the duty cycle, shown as wus-StartOffset The duration during which the UE can detect the LP-WUS, shown as wus-OnDuration One or more of such parameters may be used for this configuration. FIG. 7 shows an example of duty cycle-based LP-WUS detection. The start subframe of LP-WUS detection is [SFN×10 + subframe number] modulo (wus-Cycle) = wus-StartOffset may be defined as. Here, the SFN and the subframe number may be derived from the main receiver.

[0085] In one option, the above start offset indicating the ON duration of LP-WUS detection may be configured in units of subframes (a subframe is fixed at 1 ms in NR). Alternatively, the start offset may be configured in units of slots. The slot may be a slot having the SCS numerology u m determined by the main receiver. u m may be the SCS of the active DL BWP of the main receiver, or the SCS of the initial DL BWP of the main receiver, or the reference SCS of the main receiver. The slot may be a slot having the SCS numerology u of the LP-WUS.

[0086] In one option, the UE may expect that the LP-WUS will start immediately from the above start offset for the UE. Accordingly, the parameter wus-OnDuration is not required if the UE monitors only one LP-WUS within the duty cycle. Alternatively, multiple candidate positions for the LP-WUS for the UE may be permitted. In this case, the UE needs to detect the LP-WUS within wus-OnDuration. The candidate positions within wus-OnDuration may be composed of a list of start points and durations similar to multiple SLIVs, which may support non-contiguous LP-WUS positions. Alternatively, the candidate positions within wus-OnDuration may be determined by the number of candidate positions or the duration of the LP-WUS, which may support contiguous LP-WUS positions.

[0087] In another embodiment, multiple duty cycle configurations may be configured for the UE for LP-WUS detection. Each duty cycle configuration may be configured using a separate wus-Cycle, wus-StartOffset, and wus-OnDuration. In this option, the duty cycle configuration may be configured to enable the LP-WUS for the UE to be transmitted within the most appropriate time considering the wake-up delay between the LP-WUS and the desired channel / signal of the main receiver.

[0088] If the UE has already started turning on the main receiver based on the previous LP-WUS, the UE may skip the LP-WUS opportunity. Alternatively, if the LP-WUS and the previously detected LP-WUS are from different LP-WUS duty cycle configurations, the UE still receives the LP-WUS.

[0089] FIG. 8 shows an exemplary configuration of two duty cycles of LP-WUS detection. The main receiver can be woken up for system information updates or monitoring of paging opportunities. The PDCCH scheduling SI update and the PDCCH scheduling paging PDSCH can be configured at different timings. Assuming a fixed delay for wake-up and SI update or reception of paging PDSCH for the main receiver, the UE may need to monitor LP-WUS at different timings for the two types of transmissions at the main receiver. In FIG. 8, for simplicity, it is assumed that these two configurations have the same duty cycle period. However, different start offsets, e.g., start offset 1 and start offset 2, can be configured for these two configurations considering the timing differences between the time of SI update and the PO respectively.

[0090] In one example, if the UE receives an LP-WUS instructing the UE to receive an SI update within ON duration 1, the UE can skip the LP-WUS reception within ON duration 2. In another example, even if the UE receives an LP-WUS within ON duration 1, the UE still tries to receive the LP-WUS within ON duration 2. This is because these two LP-WUSs may indicate different information.

[0091] Figure 9 shows another example of the configuration of two duty cycles for LP-WUS detection in the connected state. The main receiver may be configured using multiple serving cells for carrier aggregation (CA) operation. The serving cells may include cells within frequency range 1 (FR1) and cells within frequency range 2 (FR2). Due to the large difference in channel conditions of different frequency ranges (FR), NR supports different DRX configurations for different FRs. Based on the same logic, the duty cycle-based LP-WUS detection configurations for these two FRs may be different. Since the power efficiency of frequencies within FR1 is higher, the LP-WUS of these two duty cycle-based configurations may be configured on FR1 cells. In Figure 9, for simplicity, it is assumed that these two configurations have the same duty cycle period. However, different start offsets, e.g., start offset 1 and start offset 2, may be configured for these two configurations considering the transmissions on the cells of these two FRs respectively.

[0092] As used herein, the terms frequency range 1 (which may be abbreviated as "FR-1", "FR1", etc.) and / or frequency range 2 (which may be abbreviated as "FR-2", "FR2", etc.) may refer to the frequency bandwidth defined by the 3rd Generation Partnership Project (3GPP), e.g., Technical Specification (TS) 38.104, whether previously defined, defined at the time of filing of this specification, or may be defined at some future point in time. In some specific embodiments, frequency range 1 may refer to a frequency bandwidth between approximately 410 megahertz (MHz) and approximately 7125 MHz. In other specific embodiments, frequency range 1 may refer to a frequency bandwidth less than or equal to approximately 6000 MHz. Similarly, in specific embodiments, frequency range 2 may refer to a bandwidth between approximately 24250 MHz and approximately 71000 MHz. In some embodiments, the bandwidth between approximately 24250 MHz and approximately 52600 MHz may be referred to as frequency range 2-1 (which may be abbreviated as "FR2-1", "FR2-1", etc.). The bandwidth between approximately 52600 MHz and approximately 71000 MHz may be referred to as frequency range 2-2 (which may be abbreviated as "FR2-2", "FR2-2", etc.).

[0093] In another embodiment, the UE may switch between two or more duty cycle configurations configured for the UE for LP-WUS detection. Each duty cycle configuration may be configured using a separate wus-Cycle, wus-StartOffset, and wus-OnDuration. The active duty cycle configuration of LP-WUS may be explicitly indicated to the UE or implicitly determined by other configurations. For example, when a plurality of search space setting groups (SSSG) are configured for the UE, different duty cycle configurations may be applied when different SSSGs become active.

[0094] In another embodiment, a separate duty cycle configuration for LP-WUS for a UE may be configured differently for LP-WUS within the DRX OFF or DRX ON duration. Each duty cycle configuration may be configured using a separate wus-Cycle, wus-StartOffset, and wus-OnDuration. In one example, the wus-Cycle of the duty cycle configuration within the DRX ON duration may be shorter than the duty cycle configuration at DRX OFF. Specifically, LP-WUS may be configured continuously or in all slots or subframes.

[0095] In another embodiment, when the DRX operation is configured for the main receiver, the duty cycle of LP-WUS and the period of the DRX operation are related for either the idle / inactive state or the connected state. In one option, the UE may expect that the duty cycle of LP-WUS is equal to the period of the DRX operation of the main receiver. In another option, the duty cycle of LP-WUS may be the same as or different from the period of the DRX operation of the main receiver.

[0096] In another embodiment, for a UE configured using LP-WUS-based indication, a second set of paging opportunities (POs), and, if supported, paging early indication (PEI) PDCCHs, e.g., DCI format 2-7 associated with the PO, can be configured for the UE. The second set of PO / PEI can be configured with a shorter period than the first set of PO / PEI known to all UEs with or without LP-WUR. The second set of PO / PEI can be configured by SIB or UE-specific signaling. After the UE detects LP-WUS, if the gap between the PO / PEI and LP-WUS is greater than or equal to period X, the UE may be able to decode the PDCCH / PDSCH within the PO / PEI for the UE. X can be predefined, pre-configured, configured, or reported by the UE as UE capability by upper layer signaling. For example, period X is the transition time for the UE to wake up the main radio.

[0097] In one option, the duty cycle configuration can be configured for the UE for LP-WUS detection separate from the PO / PEI configuration. This configuration can include wus-Cycle, wus-StartOffset, and wus-OnDuration. The timing at which the UE detects LP-WUS is determined according to the duty cycle configuration.

[0098] In another option, the timing at which the UE detects LP-WUS is determined according to the PO / PEI configuration. In one example, the timing of LP-WUS detection is period X before the PO / PEI in the second set. Alternatively, the timing of LP-WUS detection is period X before the PO / PEI in either the first or second set.

[0099] In another option, the potential time resources of LP-WUS are configured by a duty cycle configuration separate from the PO / PEI configuration. This configuration may include wus-Cycle, wus-StartOffset, and wus-OnDuration. The timing at which the UE detects LP-WUS is determined according to the duty cycle configuration and the PO / PEI configuration. For example, the group of LP-WUS based on the duty cycle configuration is monitored only for whether it is the most recent group of LP-WUS that is period X before the PO / PEI in the second set. Alternatively, the group of LP-WUS based on the duty cycle configuration is monitored only for whether it is the most recent group of LP-WUS that is period X before the PO / PEI in either the first or the second set. A group of LP-WUS may include one or more resources for LP-WUS detection. A group of LP-WUS may include LP-WUS during the ON duration within the duty cycle period.

[0100] In one option, after the UE detects LP-WUS, the UE monitors only the PO / PEI in the second set that is period X after at least the detected LP-WUS.

[0101] In another option, after the UE detects LP-WUS, the UE monitors the PO / PEI in the earlier one of the first or the second set. The monitored PO / PEI in the first or the second set must be at least period X after the detected LP-WUS.

[0102] In another embodiment, for a UE configured using an LP-WUS-based indication, after the UE detects LP-WUS, the UE monitors the PO / PEI derived from the LP-WUS. For example, the time and / or frequency resources of the PDCCH for paging or early paging identification are indicated by the LP-WUS.

[0103] [LP-WUS Determined by DRX of Other Channels / Signals]In the case of DRX operation of a UE in the idle / inactive state in Rel-17, the LP-WUS of the UE can be configured at a time position that can be determined with reference to the DRX configuration of the UE.

[0104] In one embodiment, for the main receiver in the idle / inactive state, the time position of detection of the LP-WUS of the UE can be determined with reference to the first paging frame (PF) of the UE.

[0105] In one option, the time position of the LP-WUS of the UE can be determined by a reference point and an offset from the reference point to the start of the first LP-WUS of the UE. The reference point can be the start of a reference frame determined by a frame-level offset from the start of the first PF of the PF associated with the LP-WUS. This offset is the offset from the reference point to the start of the first LP-WUS of the UE. This offset can be in units of sub-frames, slots, or OFDM symbols.

[0106] Figure 10 shows an example for the determination of the time position of the LP-WUS. Note: The UE can monitor one or more LP-WUSs at the determined time position.

[0107] In another option, the possible positions of the LP-WUS can be configured periodically for the UE, and which position is used for LP-WUS detection is determined according to the first PF of the UE. The monitored LP-WUS of the UE can be the last LP-WUS that is at least X frames, sub-frames, slots, or OFDM symbols earlier than the start of the first PF of the UE. X can be predefined, configured by upper layer signaling, or reported as UE capability. Figure 11 shows an example for the determination of the latest time position of the LP-WUS.

[0108] In one embodiment, to indicate whether the UE needs to start PDCCH monitoring before the start of the next DRX ON duration, the time position for the detection of the UE's LP-WUS can be determined in relation to the start of the next DRX ON duration. Such LP-WUS can provide some or all of the functions of DCI format 2_6.

[0109] In one option, the timing of the LP-WUS detection is at least offset 1 before the start of the next DRX ON duration. FIG. 12 shows one example of the determination of the time position of the LP-WUS for the next DRX ON duration. Here, in one example, offset 1 implies the minimum time gap between the last monitoring opportunity of the LP WUS and the start of the next DRX ON. In other words, even if an opportunity is included within this duration, the UE does not need to monitor the LP-WUS during offset 1.

[0110] In another option, the monitoring and detection of LP-WUS starts after the timing which is offset 2 before the start of the next DRX ON duration. FIG. 13 shows an example of the time position of LP-WUS for the next DRX ON duration. Note: Offset 2 can only determine the start of a slot, subframe or radio frame. The exact start of LP-WUS can be later depending on the structure of LP-WUS. After the timing position identified from offset 2, the UE can monitor LP-WUS based on the SS set configuration. In one example, the last valid LP-WUS monitoring opportunity can be before offset 1 shown in FIG. 13. For example, a valid monitoring opportunity of LP-WUS can exist between the time positions indicated by offset 2 and offset 1. In one example, a valid monitoring opportunity of LP-WUS is located within the first full duration after offset 2 of the configured SS set. In other words, if there are multiple periodic opportunities of the SS set, in each periodic opportunity, the monitoring opportunity may span the duration of one or more slots, and only the monitoring opportunity within the first duration is used by the UE for monitoring LP-WUS.

[0111] In another option, LP-WUS detection starts after the timing which is offset 2 before the start of the next DRX ON duration and starts at least at the timing which is offset 1 before the start of the next DRX ON duration. FIG. 14 shows an example related to the window of the time position of LP-WUS for the next DRX ON duration. In this example, the UE would expect there to be at least one LP-WUS monitoring opportunity between the time positions indicated by offset 2 and offset 1.

[0112] In another option, when the duty cycle configuration is configured for the UE for LP-WUS detection, the UE may monitor for LP-WUS within the first full ON duration of the LP-WUS. The ON duration starts after the timing which is offset 2 before the start of the next DRX ON duration and starts at least at the timing which is offset 1 before the start of the next DRX ON duration. FIG. 15 shows an example of a window of the time position of the LP-WUS of the next DRX ON duration. The duty cycle configuration may include wus-Cycle, wus-StartOffset and wus-OnDuration. The timing at which the UE detects the LP-WUS is determined according to the duty cycle configuration. As an extension of FIG. 15, only one or both of the two parameter offsets 1 and 2 may be applicable.

[0113] [LP-WUS Transmission] The various embodiments in this section relate to techniques for wake-up signal / channel transmission. For example, the embodiments relate to systems and methods for changing the states of the main receiver and the LP-WUR.

[0114] A separate Low-Power Wake-Up Receiver (LP-WUR) has the advantage of extremely low power consumption. When a Low-Power Wake-Up Signal (LP-WUS) is detected by the LP-WUR, the UE can turn on the main receiver for control / data transmission. Otherwise, the UE may not turn on the main receiver for power saving. Furthermore, it is still beneficial to have two states of the LP-WUR, shown as the WUR-ON state and the WUR-OFF state. In the WUR-ON state, the LP-WUR can detect the LP-WUS, while in the WUR-OFF state, the LP-WUR does not detect any LP-WUS that enables further power saving. One example of the application of the two states of the LP-WUR is duty cycle-based LP-WUS detection. The LP-WUR detects only the LP-WUS during the ON duration within the duty cycle period corresponding to the WUR-ON state. At other times of the duty cycle, the LP-WUR does not detect the LP-WUS, for example, the WUR-OFF state. Furthermore, there may be other conditions for switching between the two states of the LP-WUR and the states of the main receiver (idle, inactive, connected).

[0115] In one embodiment, the LP-WUS-based wake-up indication may be applicable to all three RRC states (idle, inactive, connected) of the main receiver. In the idle / inactive state, the LP-WUS may instruct the UE to wake up the main receiver to receive paging messages and / or other broadcast information. In the connected state, the LP-WUS may indicate that the UE should be active in the next DRX ON period, or the LP-WUS may indicate that the UE should be active after a delay.

[0116] In one example, the pattern in which the UE monitors the LP-WUS may be different for different states of the main receiver. In another example, the information carried by the LP-WUS may be different for different states of the main receiver.

[0117] FIG. 16 shows one general example of the states of the main receiver and the WUR. The main receiver may switch among three states: idle, inactive, and connected, while the WUR may switch between two states, e.g., WUR-ON and WUR-OFF.

[0118] In one option, the two states of the LP-WUR are applicable to any of the three states of the main receiver. The possible combinations of the states of the main receiver and the WUR are idle-WUR-ON, idle-WUR-OFF, inactive-WUR-ON, inactive-WUR-OFF, connected-WUR-ON, and connected-WUR-OFF.

[0119] In one option, when the main receiver is in the idle / inactive state, the LP-WUR may be in either the WUR-ON or WUR-OFF state. However, when the main receiver is in the connected state, the LP-WUR should always be active, e.g., remain in the WUR-ON state. The possible combinations of the states of the main receiver and the WUR are idle-WUR-ON, idle-WUR-OFF, inactive-WUR-ON, inactive-WUR-OFF, and connected-WUR-ON. FIG. 17 shows one example of the possible states of the main receiver and the WUR.

[0120] In one embodiment, the LP-WUS-based wake-up indication may be applicable only to the idle / inactive state of the main receiver. When the main receiver is in the connected state, the LP-WUR may be turned off. The possible combinations of the states of the main receiver and the WUR are idle-WUR-ON, idle-WUR-OFF, inactive-WUR-ON, inactive-WUR-OFF, connected-N / A. In one example, the pattern by which the UE monitors LP-WUS may be different for the idle or inactive state of the main receiver. In another example, the information carried by LP-WUS may be different for the idle or inactive state of the main receiver. FIG. 18 shows one example of the states of the main receiver and the WUR.

[0121] In one embodiment, the gNB may provide a plurality of configurations of LP-WUS. The UE may select one configuration of LP-WUS of the LP-WUR according to the RRC state of the main receiver. For example, the gNB provides two configurations of LP-WUS, one with a larger duty cycle and the other with a smaller duty cycle. To reduce latency, when the main receiver is in the RRC idle state, the configuration with the larger duty cycle is applied to the LP-WUR, while when the main receiver is in the RRC connected mode, the configuration with the shorter duty cycle is applied to the LP-WUR.

[0122] The switching of the RRC state of the main receiver may be independent of or dependent on the state of the LP-WUR.

[0123] In one embodiment, the UE determines when the main receiver proceeds to sleep according to a predefined rule. In one option, when the UE enters a specific RRC state, for example, the RRC idle state and / or the RRC inactive state, the main receiver can proceed to sleep. In another option, when a timer that starts when the UE enters a specific RRC state (for example, the RRC idle and / or the RRC inactive state) expires, the main receiver proceeds to sleep.

[0124] The sleep mode of the main receiver includes at least one of an off state, a deep sleep state, or a light sleep state.

[0125] For different RRC states, the sleep mode of the main receiver may be different. For example, the sleep mode of the main receiver is the off state for the RRC idle state, while the sleep mode of the main receiver is the deep sleep state for the RRC connected state.

[0126] [System and Implementation] Figures 19 to 22 show various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0127] Figure 19 shows a network 1900 according to various embodiments. The network 1900 may operate in a manner consistent with the 3GPP technical specifications for an LTE or 5G / NR system. However, the exemplary embodiments are not limited in this regard, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0128] Network 1900 may include UE1902, which may include any mobile or non-mobile computing device designed to communicate with RAN1904 via an over-the-air connection. UE1902 may be communicatively coupled to RAN1904 via the Uu interface. UE1902 may be a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-vehicle entertainment device, instrument cluster, head-up display device, on-vehicle diagnostic device, dash-top mobile device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc., but is not limited thereto.

[0129] In some embodiments, network 1900 may include a plurality of UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels, such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0130] In some embodiments, UE1902 may additionally communicate with AP1906 via an over-the-air connection. AP1906 may manage a WLAN connection and may function to offload some / all network traffic from RAN1904. The connection between UE1902 and AP1906 may conform to any IEEE 802.11 protocol, where AP1906 may be a Wireless Fidelity (Wi-Fi (R)) router. In some embodiments, UE1902, RAN1904, and AP1906 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may involve UE1902 being configured by RAN1904 to utilize both cellular radio resources and WLAN resources.

[0131] RAN1904 may include one or more access nodes, e.g., AN1908. AN1908 may terminate the radio interface protocol of UE1902 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. Thus, AN1908 may enable data / voice connectivity between CN1920 and UE1902. In some embodiments, AN1908 may be implemented in a discrete device or as one or more software entities executing on a server computer as part of a virtual network, e.g., referred to as a CRAN or virtual baseband unit pool. AN1908 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN1908 may be a macrocell base station or a low-power base station for providing a femtocell, picocell, or other similar cell having a coverage area smaller than, user capacity smaller than, or bandwidth higher than that of a macrocell.

[0132] In embodiments where RAN1904 includes a plurality of ANs, they may be coupled to each other via an X2 interface (when RAN1904 is an LTE RAN) or an Xn interface (when RAN1904 is a 5G RAN). In some embodiments, the X2 / Xn interface that may be separated into a control / user plane interface may enable the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0133] Each of the ANs of RAN1904 may manage one or more cells, cell groups, component carriers, etc. to provide a radio interface for network access to UE1902. UE1902 may be simultaneously connected to a plurality of cells provided by the same or different ANs of RAN1904. For example, UE1902 and RAN1904 may use carrier aggregation to enable UE1902 to connect to a plurality of component carriers each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNB, gNB, ng-eNB, etc.

[0134] RAN1904 may provide a radio interface through a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology using PCell / Scell. Before accessing the unlicensed spectrum, the nodes may perform a media / carrier sensing operation based on, for example, a listen before talk (LBT) protocol.

[0135] In a V2X scenario, UE1902 or AN1908 can be, or function as, an RSU that can refer to any transport infrastructure entity used for V2X communication. The RSU can be implemented in, or by, a suitable AN or a static (or relatively static) UE. The RSU implemented in or by a UE can be referred to as a "UE-type RSU"; the RSU implemented in or by an eNB can be referred to as an "eNB-type RSU"; the RSU implemented in or by a gNB can be referred to as a "gNB-type RSU"; and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located roadside that provides connectivity support to passing vehicle UEs. The RSU can also include an internal data storage circuit that stores intersection map geometry, traffic statistics, media, and applications / software for detecting and controlling ongoing vehicle and pedestrian traffic. The RSU can provide very low latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally, or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet®) to a traffic signal controller or a backhaul network.

[0136] In some embodiments, RAN 1904 can be an LTE RAN 1910 that includes an eNB, such as eNB 1912. The LTE RAN 1910 can provide the following characteristics to the LTE radio interface, namely, 15 kHz SCS; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo code for data and TBCC for control; etc. The LTE radio interface relies on CSI-RS for CSI acquisition and beam management; relies on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and can rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection in the UE. The LTE radio interface can operate in the sub-6 GHz band.

[0137] In some embodiments, RAN 1904 can be an NG-RAN 1914 that has a gNB, such as gNB 1916, or an ng-eNB, such as ng-eNB 1918. The gNB 1916 can connect to 5G-capable UEs using the 5G NR interface. The gNB 1916 can connect to the 5G core through an NG interface that can include an N2 interface or an N3 interface. The ng-eNB 1918 can also connect to the 5G core through the NG interface, but can connect to UEs via the LTE radio interface. The gNB 1916 and the ng-eNB 1918 can be connected to each other via the Xn interface.

[0138] In some embodiments, the NG interface can be split into two parts, namely, an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between nodes of the NG-RAN 1914 and the UPF 1948, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between nodes of the NG-RAN 1914 and the AMF 1944.

[0139] NG-RAN1914 may provide the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar codes, iterative codes, simplex codes, and Reed-Muller codes for control, and LDPC for data, to the 5G-NR radio interface. The 5G NR radio interface may rely on CSI-RS, PDSCH / PDCCH DMRS, similar to the LTE radio interface. The 5G NR radio interface may not use CRS, and may use PBCH DMRS for PBCH demodulation; may use PTRS for phase tracking of PDSCH; may use a tracking reference signal for time tracking. The 5G NR radio interface may operate in the FR1 band including the sub-6 GHz band, or in the FR2 band including the band from 24.25 GHz to 52.6 GHz. The 5G NR radio interface may include SSB, which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0140] In some embodiments, the 5G-NR radio interface may utilize BWPs for various purposes. For example, a BWP may be used for dynamic adaptation of the SCS. For example, UE1902 may be composed of multiple BWPs, with each BWP configuration having a different SCS. When a BWP change is indicated to UE1902, the transmission SCS is also changed. Another use case example of a BWP relates to power saving. In particular, multiple BWPs can be configured for UE1902 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs may be used for data transmission with a small traffic load, while enabling power saving in UE1902 and, in some cases, in gNB1916. A BWP containing more PRBs may be used in scenarios with a higher traffic load. RAN1904 is communicatively coupled to CN1920, which includes network elements that provide various functions for supporting data and telecommunications services to customers / subscribers (e.g., users of UE1902). The components of CN1920 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of CN1920 onto physical computing / storage resources in a server, switch, etc. The logical instantiation of CN1920 may be referred to as a network slice, and a partial logical instantiation of CN1920 may be referred to as a network sub-slice.

[0141] In some embodiments, CN1920 may be the LTE CN1922, which may also be referred to as the EPC. As shown, LTE CN1922 may include MME1924, SGW1926, SGSN1928, HSS1930, PGW1932, and PCRF1934, which are coupled to each other via interfaces (or "reference points"). The functions of the elements of LTE CN1922 may be briefly introduced as follows.

[0142] MME 1924 may implement a mobility management function that tracks the current location of UE 1902 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0143] SGW 1926 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 1922. SGW 1926 may be a local mobility anchor point for handovers between RAN nodes and may also provide an anchor for mobility between 3GPPs. Multiple other roles may include lawful interception, charging, and some policy enforcement.

[0144] SGSN 1928 may track the location of UE 1902 and perform security functions and access control. In addition, SGSN 1928 may perform EPC node - to - node signaling for mobility between different RAT networks; PDN and S - GW selection as specified by the MME 1924; MME selection for handover; etc. The S3 reference point between the MME 1924 and the SGSN 1928 may enable the exchange of user and bearer information for mobility between 3GPP access networks in idle / active states.

[0145] HSS 1930 may include a database for network users that contains subscription - related information to support the handling of communication sessions by network entities. HSS 1930 may provide support for routing / roaming, authentication, authorization, name / address resolution, location - dependence, etc. The S6a reference point between the HSS 1930 and the MME 1924 may enable the transfer of subscription and authentication data to authenticate / authorize user access to the LTE CN 1920.

[0146] PGW 1932 may terminate the SGi interface towards a data network (DN) 1936 that may include an application / content server 1938. PGW 1932 may route data packets between the LTE CN 1922 and the data network 1936. PGW 1932 may be coupled to the SGW 1926 via the S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1932 may further include nodes for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point between PGW 1932 and the data network 1936 may be a public, private PDN outside the operator, or an intra-operator packet data network, for example, for the provisioning of IMS services. PGW 1932 may be coupled to the PCRF 1934 via the Gx reference point. PCRF 1934 is a policy and charging control element of the LTE CN 1922. PCRF 1934 may be communicatively coupled to the app / content server 1938 to determine appropriate QoS and charging parameters for the service flow. PCRF 1932 may provision the relevant rules to the PCEF (via the Gx reference point) using appropriate TFT and QCI.

[0147] In some embodiments, CN 1920 may be 5GC 1940. 5GC 1940 may include, as shown, an AUSF 1942, an AMF 1944, an SMF 1946, a UPF 1948, an NSSF 1950, a NEF 1952, an NRF 1954, a PCF 1956, a UDM 1958, and an AF 1960 coupled to each other via interfaces (or "reference points"). The functions of the elements of 5GC 1940 may be briefly introduced as follows. AUSF 1942 may store data for the authentication of the UE 1902 and handle authentication-related functions. AUSF 1942 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 1940 via the reference points as shown, AUSF 1942 may present an Nausf service-based interface.

[0148] AMF1944 may enable other functions of the 5GC1940 for communicating with the UE1902 and the RAN1904 and for subscribing to notifications about mobility events related to the UE1902. AMF1944 may be responsible for registration management (e.g., registration of the UE1902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF1944 may provide the transport of SM messages between the UE1902 and the SMF1946 and may function as a transparent proxy for the routing of SM messages. AMF1944 may also provide the transport of SMS messages between the UE1902 and the SMSF. AMF1944 may interact with the AUSF1942 and the UE1902 to perform various security anchor and context management functions. Further, AMF1944 may be an end point of the RAN CP interface that may include or be the N2 reference point between the RAN1904 and the AMF1944; AMF1944 may be an end point of the NAS (N1) signaling and may perform NAS encryption and integrity protection. AMF1944 may also support NAS signaling with the UE1902 through the N3 IWF interface.

[0149] The SMF 1946 is responsible for SM (e.g., session establishment between the SM, such as the UPF 1948 and the AN 1908, tunnel management); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuration of traffic steering in the UPF 1948 for routing traffic to the appropriate destination; termination of the interface to the policy control function; enforcement of policies, charging, and partial control of QoS, lawful interception (of SM events and the interface to the LI system); termination of the SM part of the NAS message; downlink data notification; initiation of AN-specific SM information sent to the AN 1908 through N2 via the AMF 1944; and may be responsible for determining the SSC mode of the session. SM may refer to the management of the PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1902 and the data network 1936.

[0150] The UPF 1948 may function as an anchor point for RAT-internal and inter-RAT mobility, an external PDU session point for interconnecting to the data network 1936, and a branching point for supporting multi-home PDU sessions. The UPF 1948 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of the policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1948 may include an uplink classifier for supporting the routing of traffic flows to the data network.

[0151] The NSSF 1950 may select a set of network slice instances to provide services to the UE 1902. The NSSF 1950 may also determine the permitted NSSAI and, if required, the mapping to the subscribed S-NSSAI. The NSSF 1950 may determine a set of AMFs, or a list of candidate AMFs, to be used to provide services to the UE 1902, based on the appropriate configuration and, optionally, by querying the NRF 1954. The selection of the set of network slice instances for the UE 1902 may be triggered by the AMF 1944 in which the UE 1902 is registered by interacting with the NSSF 1950, whereby a change of AMF may be brought about. The NSSF 1950 may interact with the AMF 1944 via the N22 reference point; and may communicate with another NSSF within the visited network via an (not shown) N31 reference point. Additionally, the NSSF 1950 may indicate an Nnssf service-based interface.

[0152] NEF1952 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal disclosure / re-disclosure, AF (e.g., AF1960), edge computing, or fog computing systems, etc. In such embodiments, NEF1952 may authenticate, authorize, or throttle the AF. NEF1952 may also transform information exchanged with AF1960 and information exchanged with internal network functions. For example, NEF1952 may transform between AF service identifiers and internal 5GC information. NEF1952 may also receive information from other NFs based on the exposed capabilities of other NFs. This information may be stored as structured data in NEF1952 or stored in a data storage NF using a standardized interface. The stored information may then be re-exposed by NEF1952 to other NFs and AFs or used for other purposes such as analysis. Additionally, NEF1952 may indicate an Nnef service-based interface. NRF1954 may support a service discovery function, receive NF discovery requests from NF instances, and provide information on discovered NF instances to NF instances. NRF1954 may also maintain information on available NF instances and the services they support. As used herein, terms such as "instantiate," "instantiation," etc. may refer to the generation of an instance, and an "instance" may refer to a specific occurrence of an object that may occur, for example, during the execution of program code. Additionally, NRF1954 may indicate an Nnrf service-based interface. PCF1956 may provide policy rules to control plane functions for implementing them and may also support an integrated policy framework for controlling network behavior. PCF1956 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM1958.In addition to communicating with the function through the reference point as shown, PCF1956 indicates an Npcf service-based interface. UDM1958 may handle subscription-related information to support the handling of communication sessions by network entities and may store the subscription data of UE1902. For example, the subscription data may communicate between UDM1958 and AMF1944 via the N8 reference point. UDM1958 may include two parts, namely, an application front end and a UDR. The UDR may store subscription data and policy data for UDM1958 and PCF1956, and / or structured data and application data for publication for NEF1952 (including PFD for application detection, application request information for multiple UEs1902). The Nudr service-based interface may be presented by UDR221 to permit UDM1958, PCF1956, and NEF1952 to access a specific set of stored data, read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE that is responsible for processing such as credentials, location management, and subscription management. Several different front ends may provide services to the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication certificate processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs via the reference point as shown, UDM1958 may present an Nudm service-based interface. AF1960 may provide the impact of the application on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0153] In some embodiments, the 5GC 1940 may enable edge computing by selecting operator / third-party services such that they are geographically closer to the point where the UE 1902 is connected to the network. Thereby, latency and the load on the network may be reduced. To provide an edge computing implementation, the 5GC 1940 may select a UPF 1948 close to the UE 1902 and perform traffic steering from the UPF 1948 to the data network 1936 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 1960. In this way, the AF 1960 may influence UPF (re)selection and traffic routing. Based on the operator's deployment, if the AF 1960 is considered a trusted entity, the network operator may grant the AF 1960 permission to interact directly with the relevant NF. Additionally, the AF 1960 may indicate a Naf service-based interface. The data network 1936 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers including, for example, an application / content server 1938.

[0154] Figure 20 schematically shows a wireless network 2000 according to various embodiments. The wireless network 2000 may include a UE 2002 that wirelessly communicates with an AN 2004. The UE 2002 and the AN 2004 are similar to the components of the same name described elsewhere in this specification and may be substantially interchangeable. The UE 2002 may be communicatively coupled to the AN 2004 via a connection 2006. The connection 2006 is shown as a wireless interface to enable a communication coupling and may conform to a cellular communication protocol such as an LTE protocol or a 5G NR protocol operating at millimeter wave or sub-6 GHz frequencies. The UE 2002 may include a host platform 2008 coupled to a modem platform 2010. The host platform 2008 may include an application processing circuit 2012 that may be coupled to a protocol processing circuit 2014 of the modem platform 2010. The application processing circuit 2012 may execute various applications for the UE 2002 to source / sink application data. The application processing circuit 2012 may further implement one or more layer operations for transmitting / receiving application data to / from a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations. The protocol processing circuit 2014 may implement one or more of the layer operations to facilitate the transmission or reception of data through the connection 2006. The layer operations implemented by the protocol processing circuit 2014 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. Further, the modem platform 2010 may include a digital baseband circuit 2016 that may implement one or more layer operations “below” the layer operations executed by the protocol processing circuit 2014 in a network protocol stack.These operations may include PHY operations that include one or more of, for example, HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding that may include one or more of space-time, spatial frequency, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions. Further, the modem platform 2010 may include or be connected to an RF front end (RFFE) 2024 that may include a transmission circuit 2018, a reception circuit 2020, an RF circuit 2022, and one or more antenna panels 2026. Briefly, the transmission circuit 2018 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the reception circuit 2020 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 2022 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 2024 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the components of the transmission circuit 2018, the reception circuit 2020, the RF circuit 2022, the RFFE 2024, and the antenna panel 2026 (commonly referred to as "transmission / reception components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, whether it is millimeter wave or sub-6 GHz frequency, etc. In some embodiments, the transmission / reception components may be arranged in multiple parallel transmission / reception chains, may be arranged on the same or different chips / modules, etc. In some embodiments, the protocol processing circuit 2014 may include one or more instances (not shown) of a control circuit to provide control functions for the transmission / reception components.UE reception may be established by and through antenna panel 2026, RFFE 2024, RF circuit 2022, reception circuit 2020, digital baseband circuit 2016, and protocol processing circuit 2014. In some embodiments, antenna panel 2026 may receive transmissions from AN2004 by receiving beamforming the signals received by the plurality of antennas / antenna elements of the one or more antenna panels 2026.

[0155] UE transmission can be established by and through protocol processing circuitry 2014, digital baseband circuitry 2016, transmission circuitry 2018, RF circuitry 2022, RFFE 2024, and antenna panel 2026. In some embodiments, the transmission components of UE 2004 can apply a spatial filter to the data being transmitted to form a transmission beam radiated by the antenna elements of antenna panel 2026. Similar to UE 2002, AN 2004 may include a host platform 2028 coupled to a modem platform 2030. Host platform 2028 may include application processing circuitry 2032 coupled to protocol processing circuitry 2034 of modem platform 2030. The modem platform may further include digital baseband circuitry 2036, transmission circuitry 2038, reception circuitry 2040, RF circuitry 2042, RFFE circuitry 2044, and antenna panel 2046. The components of AN 2004 can be similar to and substantially interchangeable with the similarly named components of UE 2002. In addition to performing data transmission / reception as described above, the components of AN 2008 may perform various logical functions including, for example, radio bearer management, uplink and downlink dynamic radio resource management, and RNC functions such as scheduling of data packets. FIG. 21 is a block diagram showing components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., non-transitory machine-readable storage medium) and performing any one or more of the plurality of methods described herein. Specifically, FIG. 21 shows a schematic representation of hardware resources 2100 including one or more processors (or processor cores) 2110, one or more memory / storage devices 2120, and one or more communication resources 2130, each of which may be communicatively coupled via bus 2140 or other interface circuitry. In embodiments where network function virtualization (e.g., NFV) is utilized, a hypervisor 2102 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 2100.

[0156] Processor 2110 may include, for example, processors 2112 and 2114. Processor 2110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0157] Memory / storage device 2120 may include main memory, disk storage, or any suitable combination thereof. Memory / storage device 2120 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid state storage, etc.

[0158] Communication resource 2130 may include an interconnect or network interface controller, component, or other suitable device for communicating with one or more peripheral devices 2104, or one or more databases 2106, or other network elements via network 2108. For example, communication resource 2130 may include wired communication components (for coupling via, e.g., USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0159] Command 2150 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of processors 2110 to execute any one or more of the methods described herein. Command 2150 may be fully or partially present in at least one of processors 2110 (e.g., within the cache memory of the processor), memory / storage device 2120, or any suitable combination thereof. Additionally, any part of Command 2150 may be transferred from any combination of peripheral devices 2104 or database 2106 to hardware resource 2100. Accordingly, the memory of processor 2110, memory / storage device 2120, peripheral devices 2104, and database 2106 are examples of computer-readable and machine-readable media.

[0160] FIG. 22 shows a network 2200 according to various embodiments. Network 2200 may operate in matters consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, network 2200 may operate concurrently with network 1900. For example, in some embodiments, network 2200 may share one or more frequency or bandwidth resources with network 1900. As one specific example, a UE (e.g., UE 2202) may be configured to operate in both network 2200 and network 1900. Such a configuration may be based on a UE that includes circuitry configured to communicate with the frequency and bandwidth resources of both network 1900 and network 2200. Generally, some elements of network 2200 may share one or more characteristics with elements of network 1900. For the sake of brevity and clarity, such elements may not be repeated in the description of network 2200.

[0161] Network 2200 may include UE 2202, which may include any mobile or non-mobile computing device designed to communicate with RAN 2208 via an over-the-air connection. UE 2202 may be similar to, for example, UE 1902. UE 2202 may be a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-vehicle entertainment device, instrument cluster, head-up display device, on-vehicle diagnostic device, dash-top mobile device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, network-connected appliance, machine-type communication device, M2M or D2D device, IoT device, etc., but is not limited thereto.

[0162] Although not specifically shown in FIG. 22, in some embodiments, network 2200 may include a plurality of UEs directly coupled to each other via a sidelink interface. The UEs may be, for example, but not limited to, M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in FIG. 22, UE 2202 may be communicatively coupled to an AP such as AP 1906 as described with respect to FIG. 19. Additionally, although not specifically shown in FIG. 22, in some embodiments, RAN 2208 may include one or more ANs such as AN 1908 described with respect to FIG. 19. RAN 2208 and / or the ANs of RAN 2208 may be referred to as a base station (BS), a RAN node, or using some other term or name.

[0163] UE2202 and RAN2208 may be configured to communicate via a radio interface that may be referred to as a sixth generation (6G) radio interface. The 6G radio interface may include communication in the terahertz (THz) bandwidth or sub-THz bandwidth, or one or more features such as joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that enables radar-based sensing via wireless communication and various types of multiplexing. As used herein, the THz or sub-THz bandwidth may refer to communication in a frequency range of 80 GHz or higher. Such a frequency range may additionally or alternatively be referred to as the "millimeter wave" or "mmWave" frequency range.

[0164] RAN2208 may enable communication between UE2202 and a 6G core network (CN) 2210. Specifically, RAN2208 may facilitate the transmission and reception of data between UE2202 and 6G CN2210. The 6G CN2210 may include various functions such as NSSF1950, NEF1952, NRF1954, PCF1956, UDM1958, AF1960, SMF1946, and AUSF1942. The 6G CN2210 may additionally include UPF1948 and DN1936 as shown in FIG. 22.

[0165] Additionally, RAN 2208 may include various additional functions in addition to, or instead of, the functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 2224 and a Compute Service Function (Comp SF) 2236. Comp CF 2224 and Comp SF 2236 may be part of or functions of a computing service plane. Comp CF 2224 may be a control plane function that provides functions such as management of Comp SF 2236, generation and management of computing task contexts (e.g., generation, read, modification, deletion), and interaction with the underlying computing infrastructure for computing resource management. Comp SF 2236 may be a user plane function that functions as a gateway for interfacing a computing service user (e.g., UE 2202) and the computing nodes behind the Comp SF instance. Some functions of Comp SF 2236 include parsing computing service data received from a user to calculate tasks executable by a computing node; holding a service mesh ingress gateway or a service API gateway; enforcing service and charging policies; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 2236 instance may function as a user plane gateway for a cluster of computing nodes. A Comp CF 2224 instance may control one or more Comp SF 2236 instances. Two other such functions may include a Communication Control Function (Comm CF) 2228 and a Communication Service Function (Comm SF) 2238, which may be part of a communication service plane. Comm CF 2228 may be a control plane function for management of Comm SF 2238, communication session generation / configuration / release, and management of communication session contexts. Comm SF 2238 may be a user plane function for data transport.Comm CF2228 and Comm SF2238 can be regarded as upgrades of SMF1946 and UPF1948 described with respect to the 5G system in FIG. 19. The upgrades provided by Comm CF2228 and Comm SF2238 may enable service-aware transport. In the case of legacy (e.g., 4G or 5G) data transport, SMF1946 and UPF1948 may still be used.

[0166] Two other such functions may include a Data Control Function (Data CF) 2222, and a Data Service Function (Data SF) 2232 may be part of the data service plane. Data CF 2222 may be a control plane function and may provide functions such as, for example, Data SF 2232 management, data service generation / configuration / release, data service context management, etc. Data SF 2232 may be a user plane function and may function as a gateway between data service users (e.g., UE 2202 and various functions of 6G CN 2210) and data service endpoints behind the gateway. Specific functions may include analysis of data service user data, transfer to the corresponding data service endpoint, generation of charge data, and reporting of data service status. Another such function may be a Service Orchestration and Chaining Function (SOCF) 2220 that can discover, orchestrate, and chain up communication / computing / data services provided by functions within the network. When receiving a service request from a user, SOCF 2220 interacts with one or more of Comp CF 2224, Comm CF 2228, and Data CF 2222 to identify instances of Comp SF 2236, Comm SF 2238, and Data SF 2232, configure service resources, and generate a service chain that may include multiple instances of Comp SF 2236, Comm SF 2238, and Data SF 2232 and their associated computing endpoints. Within the generated service chain, workload processing and data movement may then be performed. SOCF 2220 may also be responsible for the maintenance, update, and release of the generated service chain.

[0167] Another such function may be the Service Registration Function (SRF) 2214, which can serve as a registry for system services provided in the user plane, such as services provided by the service endpoints behind the Comp SF 2236 and Data SF 2232 gateways, and services provided by the UE 2202. SRF 2214 can be regarded as the counterpart of the NRF 1954, which can serve as a registry for network functions.

[0168] Other such functions may include the evolved Service Communication Proxy (eSCP) and the Service Infrastructure Control Function (SICF) 2226, which can provide a service communication infrastructure for control plane services and user plane services. The eSCP may be related to the 5G Service Communication Proxy (SCP) with the addition of the user plane service communication proxy function. Therefore, the eSCP is represented by two parts, namely the eCSP-C 2212 and the eSCP-U 2234, for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 2226 can control and configure the eCSP instance from the perspectives of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0169] Another such function is the AMF 2244. The AMF 2244 may be similar to the 1944 but has additional functions. Specifically, the AMF 2244 may include potential function re-partitioning, such as moving the message transfer function from the AMF 2244 to the RAN 2208.

[0170] Another such function is the Service Orchestration Exposure Function (SOEF) 2218. The SOEF can be configured to expose service orchestration and chaining services to external users such as applications.

[0171] UE2202 may include an additional function called computing client service function (comp CSF) 2204. Comp CSF 2204 may have both control plane functions and user plane functions, and may interact with corresponding network side functions such as SOCF 2220, Comp CF 2224, Comp SF 2236, Data CF 2222 and / or Data SF 2232 for service discovery, request / response, computing task workload exchange, etc. Comp CSF 2204 may also cooperate with network side functions to determine whether computing tasks should be executed on UE 2202, on RAN 2208, and / or on elements of 6G CN 2210.

[0172] UE 2202 and / or comp CSF 2204 may include a service mesh proxy 2206. The service mesh proxy 2206 may function as a proxy for inter-service communication within the user plane. The functions of the service mesh proxy 2206 may include one or more of addressing, security, load balancing, etc.

[0173] [Exemplary Procedure] In some embodiments, an electronic device, network, system, chip, or component, or a part or implementation thereof, from FIGS. 19 to 22 or some other figures of this specification, may be configured to execute one or more processes, techniques or methods, or a part thereof, as described in this specification. One such process is shown in FIG. 23. This process may relate to a method executed by a user equipment (UE), one or more elements of the UE, and / or an electronic device including and / or implementing one or more elements of the UE. This process may include, at 2301, identifying a low power wake-up signal (LP-WUS) by a low power wake-up receiver (LP-WUR); and, at 2302, facilitating the wake-up of another receiver of the UE based on the LP-WUS. Another such process is shown in FIG. 24. This process may be related to a method executed by a base station, one or more elements of the base station, and / or an electronic device including and / or implementing one or more elements of the base station. This process may include, at 2401, identifying that a transmission is to be sent to a user equipment (UE) operating in a discontinuous reception (DRX) mode; at 2402, sending a low power wake-up signal (LP-WUS) to the UE based on the identification; and, at 2403, sending the transmission to the UE after the transmission of the LP-WUS. Another such process is shown in FIG. 25. The process of FIG. 25 may include or relate to a method executed by a user equipment (UE), one or more elements of the UE, and / or an electronic device including and / or implementing one or more elements of the UE. This process may include, at 2501, identifying a low power wake-up signal (LP-WUS) received from a base station, where the LP-WUS is received by a low power wake-up receiver (LP-WUR) of the UE that is different from the main receiver of the UE; and, at 2502, facilitating the wake-up of the main receiver of the UE based on the LP-WUS. Another such process is shown in FIG. 26.The process of FIG. 26 may include, or may be related to, a method performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include, at 2601, receiving configuration information including one or more duty cycle parameters of a low power wake-up signal (LP-WUS), where the one or more duty cycle parameters are based on the timing of a main receiver; at 2602, detecting the LP-WUS based on the configuration information via a wake-up receiver; and, at 2603, activating the main receiver based on the LP-WUS. Another such process is shown in FIG. 27. The process of FIG. 27 may include, or may be related to, a method performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The process may include, at 2701, identifying the radio resource control (RRC) state of a main receiver of the UE; and at 2702, setting the state of a wake-up receiver of the UE based on the RRC state of the main receiver. For one or more embodiments, at least one of the components described in one or more of the above-described drawings may be configured to perform one or more operations, techniques, processes, and / or methods as described in the following exemplary sections. For example, the baseband circuitry described above in connection with one or more of the above-described drawings may be configured to operate in accordance with one or more of the examples described below. For another example, the circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the above-described drawings may be configured to operate in accordance with one or more of the examples described in the exemplary sections below. [Example]

[0174] Example 1A includes a system and method for triggering transmissions using a separate low power wake-up receiver.

[0175] Example 2A includes the system and method of Example 1A and / or any other example herein, and LP-WUS supports one of the following purposes, namely, RRM measurement, triggering of paging reception, triggering of SIB reception, or acquisition of synchronization. Example 3A may include the system and method of Example 2A and / or any other example herein, and the UE performs RRM measurement based on the LP-WUS transmitted to the UE, or the LP-WUS, regardless of whether the LP-WUS is indicated to the UE or not, or only based on a special LP-WUS for the UE to perform RRM measurement based on the LP-WUS. Example 4A may include the system and method of Example 3A and / or any other example herein, and the LP-WUS for RRM is periodically transmitted by the gNB. Example 5A may include the system and method of Example 3A and / or any other example herein, and if the gNB does not transmit any other LP-WUS within a certain period, the gNB transmits the LP-WUS for RRM. Example 6A includes the system and method of Example 1A and / or any other example herein, and if the RRM measurement is still valid for the UE, the UE monitors the LP-WUS to determine whether the UE needs to wake up the main receiver.

[0176] Example 7A includes the system and method of Example 1A and / or any other example herein, and the LP-WUS indicates an early indication of a subgroup of paging opportunities and / or a TRS availability indication. Example 8A includes the system and method of Example 1A and / or any other example herein, and the LP-WUS indicates an early indication of the paged UE and / or a TRS availability indication. Example 9A includes the system and method of Example 1A and / or any other example herein, and the LP-WUS indicates a group of UEs of the PO and / or a TRS availability indication. Example 10A includes the system and method of Example 1A and / or any other example herein, and the LP-WUS includes the following information, namely, Paging early indication TRS for idle / non-active indication, some or all of other control / data reception indications Examples 11A include the systems and methods of Example 1A and / or any other example herein, and LP-WUS is configured for the UE to indicate control / data reception during the next DRX ON duration for the UE. Example 12A includes the systems and methods of Example 1A and / or any other example herein, and LP-WUS is configured for the UE to indicate control / data reception during the next DRX ON duration for the UE and whether to receive a specific signal during the DRX OFF period.

[0177] Example 13A includes the systems and methods of Example 1A and / or any other example herein, and the LP-WUS indicating that control / data for the UE is scheduled is continuously monitored. Example 14A may include the systems and methods of Example 1A and / or any other example herein, and the LP-WUS indicates information regarding PDCCH skip or search space set group (SSSG) switching. Example 15A may include the systems and methods of Example 1A and / or any other example herein, and the LP-WUS indicates the same or different set of information regarding LP-WUS within the DRX OFF or DRX ON duration. Example 16A includes a method performed by a user equipment (UE), one or more elements of the UE, and / or an electronic device including and / or implementing one or more elements of the UE, the method comprising: identifying, by a low power wake-up receiver (LP-WUR), a low power wake-up signal (LP-WUS); and facilitating a wake-up for another receiver of the UE based on the LP-WUS. Example 17A includes the method of Example 16A and / or any other example herein, and this other receiver is in a sleep mode based on the discontinuous reception (DRX) operation of the UE. Example 18A includes any method of Examples 16A to 17A and / or any other example herein, further comprising performing cell selection based on the LP-WUS. Example 19A includes any method of Examples 16A to 18A and / or any other example herein, further comprising determining paging reception based on the LP-WUS. Example 20A includes any method of Examples 16A to 19A and / or any other example herein, further comprising determining system information block (SIB) reception based on the LP-WUS. Example 21A includes any method of Examples 16 to 20A and / or any other example herein, further comprising obtaining synchronization based on the LP-WUS.Example 22A includes a method performed by a base station, one or more elements of the base station, and / or an electronic device including and / or implementing one or more elements of the base station. The method includes identifying that a transmission is to be sent to a user equipment (UE) operating in discontinuous reception (DRX) mode; based on the identification, sending a low power wake-up signal (LP-WUS) to the UE; and after sending the LP-WUS, sending the transmission to the UE. Example 23A includes the method of Example 22A and / or any other example herein, wherein a low power wake-up receiver (LP-WUR) facilitates waking up another receiver of the UE based on the LP-WUS. Example 24A includes the method of any of Examples 22A to 23A and / or any other example herein, wherein the LP-WUS is further related to cell selection. Example 25A includes the method of any of Examples 22A to 24A and / or any other example herein, wherein the LP-WUS is further related to paging reception. Example 26A includes the method of any of Examples 22A to 25A and / or any other example herein, wherein the LP-WUS is further related to system information block (SIB) reception. Example 27A includes the method of any of Examples 22A to 26A and / or any other example herein, wherein the LP-WUS is further related to synchronization. Example 28A includes the method of any of Examples 22A to 27A and / or any other example herein, wherein the LP-WUS includes an indication that it is related to the UE, does not include a related indication that it is related to the UE, or is a special LP-WUS.

[0178] Example 29A includes the method of any of Examples 22A to 28A and / or any other example herein, wherein the LP-WUS is transmitted periodically.

[0179] Example 30A includes the method of any of Examples 22A to 29A and / or any other example herein, wherein the LP-WUS includes an indication related to PDCCH skip or SSSG switching.

[0180] Example 31A includes any of the methods of Examples 22A through 30A and / or any other examples herein, and the LP-WUS information is based on whether the UE is operating in either the DRX OFF or DRX ON mode.

[0181] Example 1B may include a method for duty cycle-based low power wake-up signal transmission.

[0182] Example 2B may include the method of Example 1B and / or any other example herein, and the parameters of the duty cycle-based operation of LP-WUS are configured according to the timing of the main receiver.

[0183] Example 3B may include the method of Example 2B and / or any other example herein, and one or more of the following parameters, namely, the duty cycle period the start offset of LP-WUS detection within the duty cycle the duration for which the UE detects LP-WUS are used. Example 4B may include the method of Example 3B and / or any other example herein, and multiple duty cycle configurations are configured for the UE for LP-WUS detection.

[0184] Example 5B may include the method of Example 3B and / or any other example herein, and the UE expects that the duty cycle of the LP-WUS is equal to the period of the DRX operation of the main receiver. Example 6B may include the method of Example 3B and / or any other example herein, and the UE switches between two or more duty cycle configurations configured for LP-WUS detection. Example 7B may include the method of Example 1B and / or any other example herein, and the UE is configured using a second set of paging opportunities (POs) and, if supported, a paging early indication (PEI) PDCCH associated with the PO. Example 8B may include the method of Example 7B and / or any other example herein, after the UE detects the LP-WUS, the UE monitors only the PO / PEI within a second set that is at least period X after the detected LP-WUS. Example 9B may include the method of Example 7B and / or any other example herein, after the UE detects the LP-WUS, the UE monitors the PO / PEI that is earlier of either the first or second set, and the monitored PO / PEI within the first or second set is at least period X after the detected LP-WUS.

[0185] Example 10B may include the method of Example 1B and / or any other example herein. For the case of the main receiver in the idle / inactive state, the time position for detecting the UE's LP-WUS is determined with reference to the UE's first paging frame (PF). Example 11B may include the method of Example 1B and / or any other example herein. To indicate whether the UE needs to start PDCCH monitoring from the start of the next DRX ON duration, the time position for detecting the UE's LP-WUS is determined with reference to the start of the next DRX ON duration. Example 12B may include a method of the UE, the method comprising receiving configuration information including one or more duty cycle parameters of a low power wake-up signal (LP-WUS), wherein the one or more duty cycle parameters are based on the timing of the main receiver; detecting the LP-WUS based on the configuration information via a wake-up receiver; and activating the main receiver based on the LP-WUS.

[0186] Example 13B may include the method of Example 12B and / or any other example herein, and the one or more duty cycle parameters include a duty cycle period; a start offset of LP-WUS detection within the duty cycle; and / or a duration for which the UE detects the LP-WUS and includes one or more of them.

[0187] Example 14B may include the method of Examples 12B to 13B and / or any other example herein, and the configuration information includes a plurality of duty cycle configurations for LP-WUS detection.

[0188] Example 15B may include the method of Examples 12B to 14B and / or any other example herein, and the duty cycle of the LP-WUS is equal to the period of the DRX operation of the main receiver.

[0189] Example 16B may include the method of Examples 12B to 15B and / or any other example herein. When the main receiver is in an idle and / or inactive state, the time position for the detection of LP-WUS is determined based on the first paging frame (PF) of the UE.

[0190] Example 17B may further include a step of switching between multiple duty cycle configurations for LP-WUS detection and may include the method of Example 14B and / or any other example herein. Example 18B may include the method of Examples 12B to 17B and / or any other example herein. The configuration information includes the first and second sets of paging opportunities (POs) and the indication of the paging early indication (PEI) PDCCH associated with the first or second set of POs. Example 19B may further include a step of monitoring, at least, the PO / PEI within the second set of POs that is the period X after the detected LP-WUS, based on the detection of LP-WUS, and may include the method of Example 18B and / or any other example herein. Example 20B may further include a step of monitoring, at least, the PO / PEI in the earlier of the first or second set of POs that is the period X after the detected LP-WUS, based on the detection of LP-WUS, and may include the method of Examples 18B to 19B and / or any other example herein.

[0191] Example 1C may include a method for a state machine of low power wake-up signal transmission.

[0192] Example 2C may include the method of Example 1C and / or any other example herein. The LP-WUS based wake-up indication is applicable to all three RRC states (idle, inactive, connected) of the main receiver.

[0193] Example 3C may include the method of Example 2C and / or any other example herein. The two states of LP-WUR are applicable to any of the three states of the main receiver.

[0194] Example 4C may include the method of Example 2C and / or any other example herein. When the main receiver is in a connected state, the LP-WUR is always active.

[0195] Example 5C may include the method of Example 1C and / or any other example herein. The LP-WUS-based wake-up indication is applicable only to the idle / inactive state of the main receiver.

[0196] Example 6C may include the method of Example 1C and / or any other example herein. The UE selects one configuration of LP-WUS for the LP-WUR according to the RRC state of the main receiver.

[0197] Example 7C may include the method of Example 1C and / or any other example herein. When the timer that starts when the UE enters a specific RRC state expires, the main receiver proceeds to sleep.

[0198] Example 8C may include a method of a user equipment (UE). The method includes identifying the radio resource control (RRC) state of the main receiver of the UE; and setting the state of the wake-up receiver of the UE based on the RRC state of the main receiver.

[0199] Example 9C may include the method of Example 8C and / or any other example herein. When the main receiver is in an idle state, an inactive state, and a connected state, the wake-up receiver monitors for a low power wake-up signal (LP-WUS).

[0200] Example 10C may include the method of Examples 8C to 9C and / or any other example herein. The monitoring pattern of LP-WUS is different for different RRC states of the main receiver.

[0201] Example 11C may include the methods of Examples 8C through 10C and / or any other example herein, and the content of the LP-WUS may vary for different RRC states of the main receiver.

[0202] Example 12C may include the methods of Examples 8C through 11C and / or any other example herein. When the main receiver is in the connected state, the wake-up receiver is always in the active state. When the main receiver is in the idle state or the non-active state, the wake-up receiver switches between the active state and the non-active state.

[0203] Example 13C may include the methods of Example 8C and / or any other example herein. When the RRC state of the main receiver is connected, the wake-up receiver is non-active.

[0204] Example 14C may include the methods of Examples 8C through 13C and / or any other example herein, further comprising determining the configuration of the LP-WUS based on the RRC state of the main receiver.

[0205] Example 15C may include the methods of Examples 8C through 14C and / or any other example herein, further comprising starting a timer when the UE enters the RRC state; and moving the main receiver to sleep when the timer expires.

[0206] Example 1D includes a method performed by a user equipment (UE), one or more elements of the UE, and / or an electronic device including and / or implementing one or more elements of the UE. The method includes identifying a low-power wake-up signal (LP-WUS) received from a base station, where the LP-WUS is received by a low-power wake-up receiver (LP-WUR) of the UE, which is different from the main receiver of the UE; and facilitating wake-up of the main receiver of the UE based on the LP-WUS. Example 2D includes the method of Example 1D and / or any other example herein, where the main receiver is in a sleep mode based on the discontinuous reception (DRX) operation of the UE. Example 3D includes the method of any of Examples 1D to 2D and / or any other example herein, further comprising, by the UE, performing cell selection via the main receiver after wake-up of the main receiver based on the LP-WUS. Example 4D includes the method of any of Examples 1D to 3D and / or any other example herein, further comprising, by the UE, performing paging reception via the main receiver after wake-up of the main receiver based on the LP-WUS. Example 5D includes the method of any of Examples 1D to 4D and / or any other example herein, further comprising, by the UE, performing system information block (SIB) reception via the main receiver after wake-up of the main receiver based on the LP-WUS. Example 6D includes the method of any of Examples 1D to 5D and / or any other example herein, further comprising, by the UE, obtaining downlink (DL) synchronization via the main receiver after wake-up of the main receiver based on the LP-WUS. Example 7D includes the method of any of Examples 1D-6D and / or any other example herein, where the LP-WUS includes an indication that it is related to the UE. Example 8D includes the method of any of Examples 1D-7D and / or any other example herein, where the LP-WUS is transmitted periodically by the base station. Example 9D includes the method of any of Examples 1D-8D and / or any other example herein, where the LP-WUR does not have a data transmission function, and the main receiver has a data transmission function.Example 1E includes a method performed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The method includes receiving configuration information including one or more duty cycle parameters of a low power wake-up signal (LP-WUS), where the one or more duty cycle parameters are based on the timing of a main receiver; detecting the LP-WUS based on the configuration information via a wake-up receiver; and activating the main receiver based on the LP-WUS. Example 2E includes the method of Example 1E and / or any one or more other examples herein, and the duty cycle parameter includes a duty cycle period, a start offset for LP-WUS detection within the duty cycle, or a duration for which the UE detects the LP-WUS. Example 3E includes the method of any one of Examples 1E-2E and / or any other example herein, and the configuration information includes a plurality of duty cycle configurations for LP-WUS detection. Example 4E includes the method of Example 3E and / or any other example herein, further comprising switching between each of the plurality of duty cycle configurations for LP-WUS detection. Example 5E includes the method of any one of Examples 1E-4E and / or any other example herein, and the duty cycle of the LP-WUS is equal to the period of the DRX operation of the main receiver. Example 6E includes the method of any one of Examples 1E-5E and / or any other example herein, and when the main receiver is in a radio resource control (RRC) idle state or an RRC inactive state, the time position for LP-WUS detection is based on the first paging frame (PF) of the UE. Example 7E includes the method of any one of Examples 1E-6E and / or any other example herein, and the configuration information includes an indication of a first set of paging opportunities (POs); an indication of a second set of POs; and an indication of a physical downlink control channel (PDCCH) of a paging early indication (PEI) associated with the first set of POs or the second set of POs.Example 8E further includes, based on the detection of LP-WUS, at least the step of monitoring the POs within the second set of POs that are in the period X after the detected LP-WUS, where the value of X is determined based on pre-configuration, configuration by upper layer signaling, or reporting by the UE as UE capabilities, and includes the method of Example 7E and / or any other example herein. Example 9E further includes, based on the detection of LP-WUS, at least the step of monitoring the POs in the earlier one of the first set of POs or the second set of POs that are in the period X after the detected LP-WUS, where the value of X is determined based on pre-configuration, configuration by upper layer signaling, or reporting by the UE as UE capabilities, and includes the method of Example 7E and / or any other example herein. Example 1F includes a method executed by a user equipment (UE), one or more elements of the UE, and / or one or more electronic devices including and / or implementing the UE. The method includes the steps of identifying the radio resource control (RRC) state of the main receiver of the UE; and setting the state of the wake-up receiver of the UE based on the RRC state of the main receiver. Example 2F includes the method of Example 1F and / or any other example herein. When the main receiver is in the radio resource control (RRC) idle state, RRC inactive state, or RRC connected state, the wake-up receiver monitors for a low power wake-up signal (LP-WUS). Example 3F includes the method of Example 2F and / or any other example herein. The monitoring pattern of LP-WUS when the main receiver is in one of the RRC idle state, RRC inactive state, and RRC connected state is different from the monitoring pattern of LP-WUS when the main receiver is in another one of the RRC idle state, RRC inactive state, and RRC connected state.Example 4F includes the method of Example 2F and / or any other example herein, and when the main receiver is in one of the RRC idle state, RRC inactive state, and RRC connected state, the content of the LP-WUS is different from the content of the LP-WUS when the main receiver is in another one of the RRC idle state, RRC inactive state, and RRC connected state. Example 5F includes the method of Example 2F and / or any other example herein. When the main receiver is in the RRC connected state, the wake-up receiver is always in the active state. When the main receiver is in the RRC idle state or RRC inactive state, the wake-up receiver switches between the active state and the inactive state. Example 6F includes the method of Example 2F and / or any other example herein. When the main receiver is in the RRC connected state, the wake-up receiver is inactive. Example 7F further includes the step of determining the configuration of the LP-WUS based on the radio resource control (RRC) state of the main receiver, and includes any one of the methods of Examples 1F to 6F and / or any other example herein. Example Z01 may include an apparatus comprising means for performing one or more elements of any one of the methods described in Examples 1A to 7F, or in connection with, or any other method or process described herein.

[0207] Example Z02 may include one or more non-transitory computer-readable media comprising instructions for causing an electronic device to perform one or more elements of any one of the methods described in Examples 1A to 7F, or in connection with, or any other method or process described herein when executed by one or more processors of the electronic device.

[0208] Example Z03 may include an apparatus comprising logic, module, or circuitry for performing one or more elements of any one of the methods described in Examples 1A to 7F, or in connection with, or any other method or process described herein.

[0209] Example Z04 is a method described in any of Examples 1A through 7F, or portions or parts thereof, or in relation thereto. It may include a technique or process.

[0210] Example Z05 may include an apparatus comprising one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to execute a method, technique, or process described in any of Examples 1A through 7F, or portions thereof.

[0211] Example Z06 may include a signal described in any of Examples 1A through 7F, or portions or parts thereof, or in relation thereto.

[0212] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described in any of Examples 1A through 7F, or portions or parts thereof, or in relation thereto, or otherwise described in this disclosure.

[0213] Example Z08 may include a signal encoded using data described in any of Examples 1A through 7F, or portions or parts thereof, or in relation thereto, or otherwise described in this disclosure.

[0214] Example Z09 may include a signal encoded using a datagram, packet, frame, segment, protocol data unit (PDU), or message described in any of Examples 1A through 7F, or portions or parts thereof, or in relation thereto, or otherwise described in this disclosure.

[0215] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, and the execution of the computer-readable instructions by one or more processors is for causing the one or more processors to execute the methods, techniques, or processes described in any of Examples 1A through 7F or portions thereof, or related thereto.

[0216] Example Z11 may include a computer program comprising instructions, and the execution of the program by a processing element is for causing the processing element to execute the methods, techniques, or processes described in any of Examples 1A through 7F or portions thereof, or related thereto.

[0217] Example Z12 may include signals in a wireless network as shown and described herein.

[0218] Example Z13 may include a communication method in a wireless network as shown and described herein.

[0219] Example Z14 may include a system for providing wireless communication as shown and described herein.

[0220] Example Z15 may include a device for providing wireless communication as shown and described herein.

[0221] [Abbreviations] Unless otherwise used differently herein, the terms, definitions, and abbreviations may conform to those defined in 3GPP TR21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments described herein. 3GPP: 3rd Generation Partnership Project 4G: 4th Generation 5G: 5th Generation 5GC: 5G Core Network AC: Application Client ACR: Application Context Relocation ACK: Acknowledgment ACID: Application Client Identification AF: Application Function AM: Acknowledgment Mode AMBR: Aggregate Maximum Bit Rate AMF: Access and Mobility Management Function AN: Access Network ANR: Automatic Neighbor Relation AOA: Angle of Arrival AP: Application Protocol, Antenna Port, Access Point API: Application Programming Interface APN: Access Point Name ARP: Allocation and Retention Priority ARQ: Automatic Repeat reQuest AS: Access Stratum ASP: Application Service Provider ASN.1: Abstract Syntax Notation AUSF: Authentication Server Function AWGN: Additive White Gaussian Noise BAP: Backhaul Adaptation Protocol BCH: Broadcast Channel BER: Bit Error Rate BFD: Beam Failure Detection BLER: Block Error Rate BPSK: Binary Phase Shift Keying BRAS: Broadband Remote Access Server BSS: Business Support System BS: Base Station BSR: Buffer Status Report BW: Bandwidth BWP: Bandwidth Part C-RNTI: Cell Radio Network Temporary Identity CA: Carrier Aggregation, Certification Authority CAPEX: Capital Expenditure CBD: Candidate Beam Detection CBRA: Competitive Base Random Access CC: Component Carrier, Country Code, Cyclic Redundancy Check CCA: Clear Channel Assessment CCE: Control Channel Element CCCH: Common Control Channel CE: Coverage Extension CDM: Content Delivery Network CDMA: Code Division Multiple Access CDR: Charging Data Request CDR: Charging Data Response CFRA: Collision-Free Random Access CG: Cell Group CGF: Charging Gateway Function CHF: Charging Function CI: Cell Identity CID: Cell ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier-to-Interference Ratio CK: Cipher Key CM: Connection Management, Conditional Obligation CMAS: Commercial Mobile Alert Service CMD: Command CMS: Cloud Management System CO: Conditional Optional CoMP: Coordinated Multipoint CORESET: Control Resource Set COTS: Commercial Off-the-Shelf CP: Control Plane, Cyclic Prefix, Connection Point CPD: Connection Point Descriptor CPE: Customer Premises Equipment CPICH: Common Pilot Channel CQI: Channel Quality Indicator CPU: CSI Processing Unit, Central Processing Unit C / R: Command / Response Field Bit CRAN: Cloud Radio Access Network, Cloud RAN CRB: Common Resource Block CRC: Cyclic Redundancy Check CRI: Channel State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI: Cell RNTI CS: Circuit Switching CSCF: Call Session Control Function CSAR: Cloud Service Archive CSI: Channel State Information CSI-IM: CSI Interference Measurement CSI-RS: CSI Reference Signal CSI-RSRP: CSI Reference Signal Received Power CSI-RSRQ: CSI Reference Signal Received Quality CSI-SINR: CSI Signal-to-Noise and Interference Ratio CSMA: Carrier Sense Multiple Access CSMA / CA: CSMA with Collision Avoidance CSS: Common Search Space, Cell-Specific Search Space CTF: Charging Trigger Function CTS: Clear to Send CW: Code Word CWS: Contention Window Size D2D: Device-to-Device DC: Dual Connectivity, Direct Current DCI: Downlink Control Information DF: Deployment Flavor DL: Downlink DMTF: Distributed Management Task Force DPDK: Data Plane Development Kit DM-RS, DMRS: Demodulation Reference Signal DN: Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Radio Bearer DRS: Discovery Reference Signal DRX: Discontinuous Reception DSL: Domain-Specific Language. Digital Subscriber Line DSLAM: DSL Access Multiplexer DwPTS: Downlink Pilot Time Slot E-LAN: Ethernet Local Area Network E2E: End-to-End EAS: Edge Application Server ECCA: Extended Clear Channel Assessment, Extended CCA ECCE: Extended Control Channel Element, Extended CCE ED: Energy Detection EDGE: Enhanced Data Rate for GSM (Registered Trademark) Evolution EAS: Edge Application Server EASID: Edge Application Server Identification ECS: Edge Configuration Server ECSP: Edge Computing Service Provider EDN: Edge Data Network EEC: Edge Enable Client EECID: Edge Enable Client Identification EES: Edge Enable Server EESID: Edge Enable Server Identification EHE: Edge Host Environment EGMF: Exposure Governance Management Function EGPRS: Enhanced GPRS EIR: Equipment Identity Register eLAA: Enhanced Licensed Assisted Access, Enhanced LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB: evolved NodeB, E-UTRAN NodeB EN-DC: E-UTRA-NR Dual Connectivity EPC: evolved Packet Core EPDCCH: Enhanced PDCCH, Enhanced Physical Downlink Control Channel EPRE: Energy per Resource Element EPS: Enhanced Packet System EREG: Extended REG, Extended Resource Element Group ETSI: European Telecommunications Standards Institute ETWS: Earthquake and Tsunami Warning System eUICC: Embedded UICC, Embedded Universal Integrated Circuit Card E-UTRA: Evolved UTRA E-UTRAN: Evolved UTRAN EV2X: Extended V2X F1AP: F1 Application Protocol F1-C: F1 Control Plane Interface F1-U: F1 User Plane Interface FACCH: Fast Associated Control Channel FACCH / F: Fast Associated Control Channel / Full Rate FACCH / H: Fast Associated Control Channel / Half Rate FACH: Forward Access Channel FAUSCH: Fast Uplink Signaling Channel FB: Functional Block FBI: Feedback Information FCC: Federal Communications Commission FCCH: Frequency Correction Channel FDD: Frequency Division Duplex FDM: Frequency Division Multiplexing FDMA: Frequency Division Multiple Access FE: Front End FEC: Forward Error Correction FFS: For Further Study FFT: Fast Fourier Transform feLAA: Further Enhanced Licensed Access, Further Enhanced LAA FN: Frame Number FPGA: Field Programmable Gate Array FR: Frequency Range FQDN: Fully Qualified Domain Name G-RNTI: GERAN Radio Network Temporary Identity GERAN: GSM Edge RAN, GSM Edge Radio Access Network GGSN: Gateway GPRS Support Node GLONASS: GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB: Next-generation NodeB gNB-CU: gNB Centralized Unit, Next-generation NodeB Centralized Unit gNB-DU: gNB Distributed Unit, Next-generation NodeB Distributed Unit GNSS: Global Navigation Satellite System GPRS: General Packet Radio Service GPSI: General Public Subscription Identifier GSM: Global System for Mobile Communications, Groupe Special Mobile GTP: GPRS Tunneling Protocol GTP-U: GPRS Tunneling Protocol for the User Plane GTS: Go-to-Sleep Signal (associated with WUS) GUMMEI: Global Unique MME Identifier GUTI: Global Unique Temporary UE Identity HARQ: Hybrid ARQ, Hybrid Automatic Repeat Request HANDO: Handover HFN: Hyperframe Number HHO: Hard Handover HLR: Home Location Register HN: Home Network HO: Handover HPLMN: Home Public Land Mobile Network HSDPA: High-Speed Downlink Packet Access HSN: Hopping Sequence Number HSPA: High-Speed Packet Access HSS: Home Subscriber Server HSUPA: High-Speed Uplink Packet Access HTTP: Hypertext Transfer Protocol HTTPS: Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443) I-Block: Information Block ICCID: Integrated Circuit Card Identification IAB: Integrated Access and Backhaul ICIC: Inter-Cell Interference Coordination ID: Identity, Identifier IDFT: Inverse Discrete Fourier Transform IE: Information Element IBE: In-Band Emission IEEE: Institute of Electrical and Electronics Engineers IEI: Information Element Identifier IEIDL: Information Element Identifier Data Length IETF: Internet Engineering Task Force IF: Infrastructure IIOT: Industrial Internet of Things IM: Interference Measurement, Intermodulation, IP Multimedia IMC: IMS Credential IMEI: International Mobile Equipment Identity IMGI: International Mobile Group Identity IMPI: IP Multimedia Private Identity IMPU: IP Multimedia Public Identity IMS: IP Multimedia Subsystem IMSI: International Mobile Subscriber Identity IoT: Internet of Things IP: Internet Protocol Ipsec: IP Security, Internet Protocol Security IP-CAN: IP Connectivity Access Network IP-M: IP Multicast IPv4: Internet Protocol Version IPv6: Internet Protocol Version IR: Infrared IS: Synchronization IRP: Integrated Reference Point ISDN (Registered Trademark): Integrated Services Digital Network ISIM: IM Service Identification Module ISO: International Organization for Standardization ISP: Internet Service Provider IWF: Interworking Function I-WLAN: Interworking WLAN Constraint Length of Superimposed Code, USIM: Individual Key kB: Kilobyte (1000 bytes) kbps: Kilobits per Second Kc: Cipher Key Ki: Individual Subscriber Authentication Key KPI: Key Performance Indicator KQI: Key Quality Indicator KSI: Key Set Identifier ksps: Kilosymbols per Second KVM: Kernel Virtual Machine L1: Layer 1 (Physical Layer) L1-RSRP: Layer 1 Reference Signal Received Power L2: Layer 2 (Data Link Layer) L3: Layer 3 (Network Layer) LAA: Licensed-Assisted Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Life Cycle Management LCR: Low Chip Rate LCS: Location Service LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Lower Layer Compatibility LMF: Location Management Function LOS: Line of Sight LPLMN: Local PLMN LPP: LTE Positioning Protocol LSB: Least Significant Bit LTE: Long Term Evolution LWA: LTE-WLAN Aggregation LWIP: LTE / WLAN Radio Level Integration with IPsec Tunnel LTE: Long Term Evolution M2M: Machine-to-Machine MAC: Media Access Control (Context of Protocol Layer Ring) MAC: Message Authentication Code (Context of Security / Encryption) MAC-A: MAC for Authentication and Key Sharing (Context of TSG T WG3) MAC-I: MAC Used for Data Integrity of Signaling Messages (Context of TSG T WG3) MANO: Management and Orchestration MBMS: Multimedia Broadcast and Multicast Service MBSFN: Multimedia Broadcast Multicast Service Single Frequency Network MCC: Mobile Country Code MCG: Master Cell Group MCOT: Maximum Channel Occupancy Time MCS: Modulation and Coding Scheme MDAF: Management Data Analytics Function MDAS: Management Data Analytics Service MDT: Minimization of Drive Tests ME: Mobile Equipment MeNB: Master eNB MER: Message Error Ratio MGL: Measurement Gap Length MGRP: Measurement Gap Repetition Period MIB: Master Information Block, Management Information Base MIMO: Multiple Input Multiple Output MLC: Mobile Location Center MM: Mobility Management MME: Mobility Management Entity MN: Master Node MNO: Mobile Network Operator MO: Measurement Object, Mobile Originating MPBCH: MTC Physical Broadcast Channel MPDCCH: MTC Physical Downlink Control Channel MPDSCH: MTC Physical Downlink Shared Channel MPRACH: MTC Physical Random Access Channel MPUSCH: MTC Physical Uplink Shared Channel MPLS: Multi-Protocol Label Switching MS: Mobile Station MSB: Most Significant Bit MSC: Mobile Switching Center MSI: Minimum System Information, MCH Scheduling Information MSID: Mobile Station Identifier MSIN: Mobile Station Identification Number MSISDN: Mobile Subscriber ISDN Number MT: Mobile Terminated, Mobile Termination MTC: Machine Type Communication mMTC: Massive MTC, Massive Machine Type Communication MU-MIMO: Multi-User MIMO MWUS: MTC Wake-up Signal, MTC WUS NACK: Negative Acknowledgment NAI: Network Access Identifier NAS: Non-Access Stratum, Non-Access Stratum layer NCT: Network Connectivity Topology NC-JT: Non-Coherent Joint Transmission NEC: Network Function Exposure NE-DC: NR-E-UTRA Dual Connectivity NEF: Network Exposure Function NF: Network Function NFP: Network Transfer Path NFPD: Network Transfer Path Descriptor NFV: Network Function Virtualization NFVI: NFV Infrastructure NFVO: NFV Orchestrator NG: Next Generation, Next Gen NGEN-DC: NG-RAN E-UTRA-NR Dual Connectivity NM: Network Manager NMS: Network Management System N-PoP: Network Point of Presence NMIB, N-MIB: Narrowband MIB NPBCH: Narrowband Physical Broadcast Channel NPDCCH: Narrowband Physical Downlink Control Channel NPDSCH: Narrowband Physical Downlink Shared Channel NPRACH: Narrowband Physical Random Access Channel NPUSCH: Narrowband Physical Uplink Shared Channel NPSS: Narrowband Primary Synchronization Signal NSSS: Narrowband Secondary Synchronization Signal NR: New Radio, Nearby Relationship NRF: NF Repository Function NRS: Narrowband Reference Signal NS: Network Service NSA: Non-Standalone Operation Mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Assistance Information S-NNSAI Single NSSAI NSSF: Network Slice Selection Function NW: Network NWUS: Narrowband Wakeup Signal, Narrowband WUS NZP: Non-Zero Power O&M: Operation and Maintenance ODU2: Optical Channel Data Unit Type OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access OOB: Out-of-Band OOS: Out-of-Synchronization OPEX: Operating Expenses OSI: Other System Information OSS: Operation Support System OTA: Over-the-Air PAPR: Peak-to-Average Power Ratio PAR: Peak-to-Average Ratio PBCH: Physical Broadcast Channel PC: Power Control, Personal Computer PCC: Primary Component Carrier, Primary CC P-CSCF: Proxy CSCF PCell: Primary Cell PCI: Physical Cell ID, Physical Cell Identity PCEF: Policy and Charging Enforcement Function PCF: Policy Control Function PCRF: Policy Control and Charging Rules Function PDCP: Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer PDCCH: Physical Downlink Control Channel PDCP: Packet Data Convergence Protocol PDN: Packet Data Network, Public Data Network PDSCH: Physical Downlink Shared Channel PDU: Protocol Data Unit PEI: Permanent Equipment Identifier PFD: Packet Flow Description P-GW: PDN Gateway PHICH: Physical Hybrid ARQ Indicator Channel PHY: Physical Layer PLMN: Public Land Mobile Network PIN: Personal Identification Number PM: Performance Measurement PMI: Precoding Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: Push-to-Talk over Cellular PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH: Physical Random Access Channel PRB: Physical Resource Block PRG: Physical Resource Block Group ProSe: Proximity Service, Proximity-Based Service PRS: Positioning Reference Signal PRR: Packet Reception Radio PS: Packet Service PSBCH: Physical Sidelink Broadcast Channel PSDCH: Physical Sidelink Downlink Channel PSCCH: Physical Sidelink Control Channel PSSCH: Physical Sidelink Shared Channel PSFCH: Physical Sidelink Feedback Channel PSCell: Primary SCell PSS: Primary Synchronization Signal PSTN: Public Switched Telephone Network PT-RS: Phase Tracking Reference Signal PTT: Push-to-Talk PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel QAM: Quadrature Amplitude Modulation QCI: QoS Class Identifier QCL: Quasi-Co-Location QFI: QoS Flow ID, QoS Flow Identifier QoS: Quality of Service QPSK: Quadrature (4-Phase) Phase Shift Keying QZSS: Quasi-Zenith Satellite System RA-RNTI: Random Access RNTI RAB: Radio Access Bearer, Random Access Burst RACH: Random Access Channel RADIUS: Remote Authentication Dial In User Service RAN: Radio Access Network RAND: Random Number (used for authentication) RAR: Random Access Response RAT: Radio Access Technology RAU: Routing Area Update RB: Resource Block, Radio Bearer RBG: Resource Block Group REG: Resource Element Group Rel: Release REQ: Request RF: Radio Frequency RI: Rank Indicator RIV: Resource Indicator Value RL: Radio Link RLC: Radio Link Control, Radio Link Control Layer RLC AM: RLC Acknowledged Mode RLC UM: RLC Unacknowledged Mode RLF: Radio Link Failure RLM: Radio Link Monitoring RLM-RS: Reference Signal for RLM RM: Registration Management RMC: Reference Measurement Channel RMSI Residual MSI, Residual Minimum System Information RN: Relay Node RNC: Radio Network Controller RNL: Radio Network Layer RNTI: Radio Network Temporary Identifier ROHC: Robust Header Compression RRC: Radio Resource Control, Radio Resource Control Layer RRM: Radio Resource Management RS: Reference Signal RSRP: Reference Signal Received Power RSRQ: Reference Signal Received Quality RSSI: Received Signal Strength Indicator RSU: Road Side Unit RSTD: Reference Signal Time Difference RTP: Real - Time Protocol RTS: Request To Send RTT: Round - Trip Time Rx: Reception, Receiving, Receiver S1AP: S1 Application Protocol S1 - MME: S for Control Plane S1 - U: S for User Plane S - CSCF: Serving CSCF S - GW: Serving Gateway S - RNTI: SRNC Radio Network Temporary Identity S - TMSI: SAE Temporary Mobile Station Identifier SA: Standalone Operation Mode SAE: System Architecture Evolution SAP: Service Access Point SAPD: Service Access Point Descriptor SAPI: Service Access Point Identifier SCC: Secondary Component Carrier, Secondary CC SCell: Secondary Cell SCEF: Service Capability Exposure Function SC - FDMA: Single - Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management SCS: Sub - Carrier Spacing SCTP: Stream Control Transmission Protocol SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL: Supplementary Downlink SDNF: Structured Data Storage Network Function SDP: Session Description Protocol SDSF: Structured Data Storage Function SDT: Small Data Transmission SDU: Service Data Unit SEAF: Security Anchor Function SeNB: Secondary eNB SEPP: Security Edge Protection Proxy SFI: Slot Format Indication SFTD: Spatial-Frequency Time Diversity, SFN and Frame Timing Difference SFN: System Frame Number SgNB: Secondary gNB SGSN: Serving GPRS Support Node S-GW: Serving Gateway SI: System Information SI-RNTI: System Information RNTI SIB: System Information Block SIM: Subscriber Identity Module SIP: Session Initiation Protocol SiP: System in Package SL: SideLink SLA: Service Level Agreement SM: Session Management SMF: Session Management Function SMS: Short Message Service SMSF: SMS Function SMTC: SSB-Based Measurement Timing Configuration SN: Secondary Node, Sequence Number SoC: System on Chip SON: Self-Organizing Network SpCell: Special Cell SP-CSI-RNTI: Semi-Persistent CSI RNTI SPS: Semi-Persistent Scheduling SQN: Sequence Number SR: Scheduling Request SRB: Signaling Radio Bearer SRS: Sounding Reference Signal SS: Synchronization Signal SSB: Synchronization Signal Block SSID: Service Set Identifier SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator SSC: Session and Service Continuity SS-RSRP: Synchronization Signal Based Reference Signal Received Power SS-RSRQ: Synchronization Signal Based Reference Signal Received Quality SS-SINR: Synchronization Signal Based Signal to Noise and Interference Ratio SSS: Secondary Synchronization Signal SSSG: Search Space Set Group SSSIF: Search Space Set Indicator SST: Slice / Service Type SU-MIMO: Single User MIMO SUL: Supplementary Uplink TA: Timing Advance, Tracking Area TAC: Tracking Area Code TAG: Timing Advance Group TAI: Tracking Area Identity TAU: Tracking Area Update TB: Transport Block TBS: Transport Block Size TBD: To Be Determined TCI: Transmission Configuration Indicator TCP: Transmission Control Protocol TDD: Time Division Duplexing TDM: Time Division Multiplexing TDMA: Time Division Multiple Access TE: Terminal Equipment TEID: Tunnel Endpoint Identifier TFT: Traffic Flow Template TMSI: Temporary Mobile Subscriber Identity TNL: Transport Network Layer TPC: Transmission Power Control TPMI: Transmission Precoding Matrix Indicator TR: Technical Report TRP, TRxP: Transmission / Reception Point TRS: Tracking Reference Signal TRx: Transceiver TS: Technical Specification TTI: Transmission Time Interval Tx: Transmission, Transmitting, Transmitter U-RNTI: UTRAN Radio Network Temporary Identity UART: Universal Asynchronous Receiver and Transmitter UCI: Uplink Control Information UE: User Equipment UDM: Unified Data Management UDP: User Datagram Protocol UDSF: Unstructured Data Storage Network Function UICC: Universal Integrated Circuit Card UL: Uplink UM: Unauthorized Mode UML: Unified Modeling Language UMTS: Universal Mobile Telecommunications System UP: User Plane UPF: User Plane Function URI: Uniform Resource Identifier URL: Uniform Resource Locator URLLC: Ultra-Reliable and Low-Latency USB: Universal Serial Bus USIM: Universal Subscriber Identity Module USS: UE-Specific Search Space UTRA: UMTS Terrestrial Radio Access UTRAN: Universal Terrestrial Radio Access Network UwPTS: Uplink Pilot Time Slot V2I: Vehicle-to-Infrastructure V2P: Vehicle-to-Pedestrian V2V: Vehicle-to-Vehicle V2X: Vehicle-to-Everything VIM: Virtual Infrastructure Manager VL: Virtual Link VLAN: Virtual LAN, Virtual Local Area Network VM: Virtual Machine VNF: Virtualized Network Function VNFFG: VNF Forwarding Graph VNFFGD: VNF Forwarding Graph Descriptor VNFM: VNF Manager VoIP: Voice over IP, Voice over Internet Protocol VPLMN: Visited Public Land Mobile Network VPN: Virtual Private Network VRB: Virtual Resource Block WiMAX (registered trademark): Worldwide Interoperability for Microwave Access WLAN: Wireless Local Area Network WMAN: Wireless Metropolitan Area Network WPAN: Wireless Personal Area Network X2-C: X2-Control Plane X2-U: X2-User Plane XML: Extensible Markup Language XRES: Expected User Response XOR: Exclusive OR ZC: Zadoff-Chu ZP: Zero Power [Terms] For the purposes of this specification, the following terms and definitions are applicable to the examples and embodiments described in this specification.

[0222] The term "application" can refer to a complete and deployable package, environment for realizing a specific function in an operating environment. Terms such as "AI / ML application" can be an application that includes some AI / ML models and application-level descriptions.

[0223] As used herein, the term "circuit" refers to, for example, an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group), an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc., a hardware component configured to provide the described functionality, a part of them, or including them. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code used to execute the functions of that program code. In these embodiments, the combination of the hardware element and the program code may be referred to as a particular type of circuit.

[0224] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit that can perform a series of arithmetic or logical operations continuously and automatically, or record, store, and / or transfer digital data. The processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes. The processing circuit may be a microprocessor, a programmable processing device, etc., and may include more hardware accelerators. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms "application circuit" and / or "baseband circuit" may be considered synonymous with and may be referred to as "processor circuit". As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and / or a network interface card, etc.

[0225] As used herein, the term "user equipment" or "UE" refers to a device having wireless communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be regarded as synonymous with and may be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, wireless device, reconfigurable wireless device, reconfigurable mobile device, etc. Further, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device including a wireless communication interface.

[0226] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be regarded as synonymous with and may be referred to as a networked computer, networked hardware, network device, network node, router, switch, hub, bridge, wireless network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0227] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer coupled to communicate with each other. Further, the terms "computer system" and / or "system" may refer to a plurality of computer devices and / or a plurality of computing systems configured to communicate with each other and share computing and / or networking resources.

[0228] As used herein, terms such as "appliance" or "computer appliance" refer to a computer device or computer system that includes program code (e.g., software or firmware) specially designed to provide certain computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing certain computing resources.

[0229] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as, for example, computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, and / or workload units, etc. "Hardware resources" may refer to computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, and / or network resources provided to applications, devices, systems, etc. by a virtualized infrastructure. The terms "network resources" or "communication resources" may refer to resources that are accessible by computer devices / systems via a communication network. The term "system resources" may refer to any kind of shared entity for providing services, and may include computing and / or network resources. System resources may be regarded as a set of coherent functions, network data objects, or services that are accessible through a server where such system resources exist on a single host or multiple hosts and are clearly identifiable.

[0230] As used herein, the term "channel" refers to any transmission medium, either tangible or intangible, used to communicate data or a data stream. The term "channel" may be synonymous with, and / or equivalent to, terms such as "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", and / or any other similar terms that mean a path or medium through which data is communicated, and / or may be used interchangeably therewith. Additionally, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0231] As used herein, terms such as "instantiate" and "instantiation" refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

[0232] The terms "coupled" and "communicatively coupled", along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements can contact each other through communication, including through a wired or other interconnect connection and / or through a wireless communication channel or link.

[0233] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or a data element that contains the content.

[0234] The term "SMTC" refers to the SSB-based measurement timing configuration constituted by SSB-Measurement Timing Configuration.

[0235] The term "SSB" refers to the SS / PBCH block.

[0236] The term "primary cell" refers to the MCG cell operating on the primary frequency, where the UE either executes the initial connection establishment procedure or starts the connection re-establishment procedure.

[0237] The term "primary SCG cell" refers to the SCG cell where the UE performs random access when executing the Reconfiguration with Sync procedure for DC operation.

[0238] The term "secondary cell" refers to the cell that provides additional radio resources on a special cell for a UE configured with CA.

[0239] The term "secondary cell group" refers to a subset of the serving cell including the PSCell and zero or more secondary cells for a UE configured with DC.

[0240] The term "serving cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, and there is only one serving cell including the primary cell.

[0241] The term "serving cell" or "serving cells" refers to a set of cells that includes a special cell and all secondary cells for a UE in RRC_CONNECTED configured with CA.

[0242] The term "special cell" refers to the MCG's PCell or the SCG's PSCell in the case of DC operation; otherwise, the term "special cell" refers to the Pcell.

[0243] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models for performing a specific task by relying on patterns and inferences without using explicit instructions. ML algorithms build or estimate a mathematical model (referred to as an "ML model", etc.) based on sample data (referred to as "training data", or "model training information", etc.) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to a certain task and a certain performance metric, and an ML model can be any object or data structure generated after an ML algorithm has been trained on one or more training data sets. After training, the ML model can be used to make predictions or generate new data sets. The term "ML algorithm" refers to a concept different from the term "ML model", but as described in this specification, these terms can be used synonymously for the purposes of this disclosure.

[0244] Terms such as "machine learning model", "ML model", or the like may also refer to ML methods and concepts used by the ML-assisted solution means. An "ML-assisted solution means" is a solution means that uses an ML algorithm during operation to handle a specific use case. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithm, support vector machine, Bayesian algorithm, ensemble algorithm, etc.), unsupervised learning (e.g., k-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), and neural networks, etc. Depending on the implementation, a specific ML model may have many sub-models as components, and the ML model may train all the sub-models together. Separately trained ML models can also be joined together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, functions, or functional entities specific to the ML-assisted solution means; an ML pipeline may include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or more data sources in an actor. An "actor" is an entity that hosts the ML-assisted solution means using the output of the ML model inference. The term "ML training host" refers to an entity such as a network function that hosts the training of the model. The term "ML inference host" refers to an entity such as a network function that hosts the model during the inference mode (including both model execution and any online learning, if applicable). The ML host notifies the actor about the output of the ML algorithm, and the actor makes a decision about an action (an "action" is executed by the actor as a result of the output of the ML-assisted solution means). The term "model inference information" refers to the information used as input to the ML model to determine the inference; the data used to train the ML model and the data used to determine the inference may overlap, but "training data" and "inference data" refer to different concepts.

Claims

1. An apparatus for use in a user equipment (UE), comprising: a memory for storing a low power wake-up signal (LP-WUS) received from a base station, wherein the LP-WUS is received by a low power wake-up receiver (LP-WUR) of the UE, which is different from a main receiver of the UE; and one or more processors for waking up the main receiver of the UE based on the LP-WUS The apparatus.

2. The apparatus according to claim 1, wherein the main receiver is in a sleep mode based on an intermittent reception (DRX) operation of the UE.

3. The apparatus according to claim 1, wherein the one or more processors further facilitate cell selection via the main receiver after waking up the main receiver based on the LP-WUS.

4. The apparatus according to claim 1, wherein the one or more processors further facilitate paging reception via the main receiver after waking up the main receiver based on the LP-WUS.

5. The apparatus according to claim 1, wherein the one or more processors further facilitate system information block (SIB) reception via the main receiver after waking up the main receiver based on the LP-WUS.

6. The apparatus according to claim 1, wherein the one or more processors further facilitate downlink (DL) synchronization via the main receiver after waking up the main receiver based on the LP-WUS.

7. The apparatus according to any one of claims 1 to 6, wherein the LP-WUS includes an indication related to the UE.

8. The apparatus according to any one of claims 1 to 6, wherein the LP-WUS is periodically transmitted by the base station.

9. The apparatus according to any one of claims 1 to 6, wherein the LP-WUR does not have a radio data transmission function, and the main receiver has a radio data transmission function.

10. One or more non-transitory computer-readable media (NTCRM) comprising instructions, which when executed by one or more processors of a user equipment (UE), A procedure for identifying received configuration information including one or more duty cycle parameters of a low power wake-up signal (LP-WUS), wherein the one or more duty cycle parameters are based on the timing of a main receiver; A procedure for detecting the LP-WUS based on the configuration information via a wake-up receiver; and A procedure for activating the main receiver based on the LP-WUS to be executed by the UE, NTCRM.

11. The one or more duty cycle parameters include a duty cycle period, a start offset of LP-WUS detection within a duty cycle, or a duration for which the UE detects the LP-WUS, the one or more NTCRMs according to claim 10.

12. The configuration information includes a plurality of duty cycle configurations for LP-WUS detection, the one or more NTCRMs according to claim 10.

13. The instructions further cause the UE to execute a procedure for switching between each of the plurality of duty cycle configurations for LP-WUS detection, the one or more NTCRMs according to claim 12.

14. The duty cycle of the LP-WUS is equal to the period of the DRX operation of the main receiver, the one or more NTCRMs according to claim 10.

15. When the main receiver is in a radio resource control (RRC) idle state or an RRC inactive state, the time position of the detection of the LP-WUS is based on a first paging frame (PF) of the UE, the one or more NTCRMs according to claim 10.

16. The configuration information is An indication of a first set of paging opportunities (POs); An indication of a second set of POs; and An indication of a paging early indication (PEI) physical downlink control channel (PDCCH) associated with the first set of POs or the second set of POs including, The one or more NTCRMs according to any one of claims 10 to 15.

17. The command further causes the UE to execute a procedure of monitoring, based on the detection of the LP-WUS, for the POs in the second set of the POs that are at least a period X after the detected LP-WUS, where the value of X is determined based on pre-configuration, configuration by upper layer signaling, or reporting by the UE as UE capabilities, one or more NTCMs according to claim 16.

18. The command further causes the UE to execute a procedure of monitoring, based on the detection of the LP-WUS, for the POs in the earlier one of the first set of the POs or the second set of the POs that are at least a period X after the detected LP-WUS, where the value of X is determined based on pre-configuration specifications, configuration by upper layer signaling, or reporting by the UE as UE capabilities, one or more NTCMs according to claim 16.

19. A user equipment (UE) comprising: A main receiver configured for wireless data transmission and reception functions; A wake-up receiver configured for wireless data reception functions, where the wake-up receiver does not have a wireless data transmission function; and One or more processors coupled to the main receiver and the wake-up receiver, where the one or more processors are configured to identify the radio resource control (RRC) state of the main receiver of the UE; and configured to set the state of the wake-up receiver of the UE based on the RRC state of the main receiver as described above. A UE comprising the above.

20. The UE according to claim 19, wherein when the main receiver is in a radio resource control (RRC) idle state, an RRC inactive state, or an RRC connected state, the wake-up receiver monitors for a low power wake-up signal (LP-WUS).

21. The UE according to claim 20, wherein the monitoring pattern of the LP-WUS when the main receiver is in one of the RRC idle state, the RRC inactive state, and the RRC connected state is different from the monitoring pattern of the LP-WUS when the main receiver is in another one of the RRC idle state, the RRC inactive state, and the RRC connected state.

22. The UE according to claim 20, wherein the content of the LP-WUS when the main receiver is in one of the RRC idle state, the RRC inactive state, and the RRC connected state is different from the content of the LP-WUS when the main receiver is in another one of the RRC idle state, the RRC inactive state, and the RRC connected state.

23. The UE according to claim 20, wherein when the main receiver is in the RRC connected state, the wake-up receiver is always in the active state, and when the main receiver is in the RRC idle state or the RRC inactive state, the wake-up receiver switches between the active state and the inactive state.

24. The UE according to claim 20, wherein when the main receiver is in the RRC connected state, the wake-up receiver is inactive.

25. The UE according to any one of claims 19 to 20, wherein the one or more processors are further configured to determine the configuration of the LP-WUS based on a radio resource control (RRC) state of the main receiver.

Images