Inter-cell interference handling for low-power wake-up signals

Abstract

Various embodiments herein provide techniques related to low-power wake-up signals (LP-WUS) used to trigger wake-up of a user equipment (UE). For example, embodiments may include techniques for handling inter-cell interference for wake-up signals / channels. Additionally, embodiments may include techniques for coexistence between low-power wake-up signals / channels and other signals / channels (e.g., channels of a wireless cellular network, such as a New Radio (NR) network). For example, embodiments include systems and methods for configuring and / or receiving an LP-WUS in consideration of other signals / channels and / or for configuring and / or receiving other signals / channels in consideration of the LP-WUS. Other embodiments may be described and claimed.

Description

[Background technology]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to U.S. Provisional Patent Application No. 63 / 485,227, filed February 15, 2023; and to U.S. Provisional Patent Application No. 63 / 485,202, filed February 15, 2023.

[0002] Fifth-generation (5G) cellular systems have been designed and developed for both mobile telephony and vertical use cases. In addition to latency, reliability, and availability, energy efficiency of user equipment (UE) is also important for 5G. Currently, 5G devices may need to be charged at least once per week or per day, depending on the device and associated usage time. Typically, 5G devices may consume tens of milliwatts in a radio resource control (RRC) idle / inactive state and hundreds of milliwatts in an RRC connected state. [Brief explanation of the drawings]

[0003] Embodiments will be readily understood by the following detailed description taken in conjunction with the accompanying drawings, in which: To facilitate this description, like reference numerals refer to like elements, and in which embodiments are shown by way of example, and not by way of limitation.

[0004] [Figure 1] 1 illustrates a schematic diagram of a user equipment (UE) with a main receiver and a wake-up receiver, according to various embodiments.

[0005] [Figure 2] 1 illustrates a low power wakeup signal (LP-WUS) having two parts, according to various embodiments.

[0006] [Figure 3]1 illustrates time division multiplexing (TDM) based multiplexing for LP-WUS and other channels / signals, according to various embodiments.

[0007] [Figure 4] 1 illustrates frequency division multiplexing (FDM) based multiplexing for LP-WUS and other channels / signals, according to various embodiments.

[0008] [Figure 5] 1 illustrates an example of one LP-WUS transmitted in multiple subframes or slots, according to various embodiments.

[0009] [Figure 6] 10 illustrates another example of one LP-WUS transmitted in multiple subframes or slots, according to various embodiments.

[0010] [Figure 7] 1 illustrates rate matching of a physical downlink shared channel (PDSCH) around a LP-WUS according to various embodiments.

[0011] [Figure 8] 1 illustrates a schematic diagram of a wireless network in accordance with various embodiments.

[0012] [Figure 9] 1 illustrates a schematic diagram of components of a wireless network in accordance with various embodiments.

[0013] [Figure 10] FIG. 1 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies described herein, according to some example embodiments.

[0014] [Figure 11]1 illustrates a network in accordance with various embodiments.

[0015] [Figure 12] 1 illustrates an exemplary procedure for carrying out various embodiments described herein. [Figure 13] 1 illustrates an exemplary procedure for carrying out various embodiments described herein. [Figure 14] 1 illustrates an exemplary procedure for carrying out various embodiments described herein. DETAILED DESCRIPTION OF THE INVENTION

[0016] The following detailed description refers to the 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 are set forth, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of this disclosure that various aspects of the various embodiments may be practiced 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 purposes of this document, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0017] Various embodiments herein provide techniques related to low-power wake-up signals (LP-WUS) used to trigger wake-up of user equipment (UE). For example, embodiments may include techniques for handling inter-cell interference for wake-up signals / channels. Additionally, embodiments may include techniques for coexistence between low-power wake-up signals / channels and other signals / channels (e.g., channels of wireless cellular networks, such as New Radio (NR) networks). For example, embodiments include systems and methods for configuring and / or receiving an LP-WUS in consideration of other signals / channels and / or for configuring and / or receiving other signals / channels in consideration of the LP-WUS.

[0018] The power consumption depends on the configured length of the wake-up period, e.g., the paging cycle. To meet the battery life requirement, a long DRX cycle is expected to be used, resulting in high latency, which is not suitable for such services with both long battery life and low latency requirements. For example, in a fire detection and extinguishing use case, fire shutters may be closed and extinguishing sprinklers may be activated by actuators within 1 to 2 seconds from when a fire is detected by a sensor. In that case, a long DRX cycle cannot meet the latency requirement. Therefore, it is necessary to reduce the power consumption with reasonable latency.

[0019] Currently, UEs need to wake up periodically, once per DRX cycle, which accounts for the majority of power consumption during periods without signaling or data traffic. If UEs were allowed to wake up only when they were triggered, e.g., for paging, power consumption could be dramatically reduced. This can be achieved by using the wake-up signal to trigger a main radio and a separate receiver capable of monitoring the wake-up signal with ultra-low power consumption. The main receiver serves for data transmission and reception and can be stopped or set to deep sleep unless it is activated.

[0020] 1 shows an example of a cell UE 100 that includes a main receiver 102 and a wake-up receiver 104. In a power saving state, if a wake-up signal is not received by the wake-up receiver 104, the main receiver 102 remains in an off state (e.g., deep sleep). On the other hand, if a wake-up signal is received by the wake-up receiver 104, the wake-up receiver 104 triggers the main receiver 102 to wake up. In the latter case, since the main receiver 102 is active, the wake-up receiver 104 can be stopped.

[0021] Techniques for inter-cell interference in LP-WUS Inter-cell interference is a key limiting factor for cellular systems, and this problem may be even more severe since advanced interference handling schemes may not be practical for LP-WUS due to the need for extremely low complexity and power consumption.

[0022] Various embodiments herein provide techniques for inter-cell interference handling for wake-up signals / channels.

[0023] In some embodiments, LP-WUS may use on-off keying (OOK) or frequency shift keying (FSK). In OFDM systems, OOK or FSK modulation may be mapped to multiple subcarriers, e.g., multi-carrier OOK (MC-OOK) or MC-FSK. In this disclosure, a WUS symbol is used to represent an OOK symbol, an FSK symbol, an MC-OOK symbol, or an MC-FSK symbol. An OOK / FSK symbol may consist of multiple samples in time. LP-WUS may also use the same waveform as other NR channels / signals.

[0024] The LP-WUS may be mapped to the duration of consecutive OFDM symbols. The start of the LP-WUS may be defined by an offset relative to the start of a slot, subframe, half radio frame, or radio frame. The LP-WUS may consist of a single part or at least two parts. In a single-part LP-WUS, the LP-WUS may be generated based on a sequence or coded payload information. In a two-part LP-WUS, the first part may be generated based on a sequence, and the second part, which carries wake-up information, typically uses channel coding. The channel coding for the second part may be a spreading operation or repetition coding. The first part may also carry one or more information bits. Figure 2 shows an example of two parts of an LP-WUS allocated within a subframe.

[0025] In various embodiments, inter-cell interference may be considered in the design and configuration of LP-WUS in multiple cells. The inter-cell interference handling may be the same or different for the two parts of the LP-WUS. Two types of LP-WUS may be defined. The first type of LP-WUS may be transmitted periodically, which can be used for synchronization and / or RRM measurements. The first type of LP-WUS may be a reference for detecting the second type of LP-WUS. While the resources of the second type of LP-WUS are configured with periodicity, the second type of LP-WUS may be transmitted on demand, for example, when paging arrives. The inter-cell interference handling may be the same or different for the two types of LP-WUS.

[0026] Different cells may be configured with different IDs. The IDs may include a physical cell ID, a tracking area ID, a RAN area ID, or an ID for a system information area (systemInformationAreaID). In one example, the time or frequency of multiple LP-WUSs associated with different IDs may be different. It is not limited that the sequences or scrambling codes of multiple LP-WUSs are the same or different. This option can avoid LP-WUS transmissions in overlapping time / frequency resources from neighboring cells, which is preferable for inter-cell interference mitigation. It should be noted that whether two cells separated by a long distance may use the same time and frequency resources for LP-WUS depends on the network deployment.

[0027] Cooperative LP-WUS transmission in multiple cells In one embodiment, a first gNB may transmit an intended configuration of LP-WUS to a second gNB. It is up to the second gNB to decide whether to mute or transmit LP-WUS or other channels / signals on the time / frequency resources of the intended LP-WUS at the first gNB. The second gNB may transmit feedback information about whether all or part of the intended LP-WUS resources of the first gNB are muted. The intended configuration of LP-WUS to the second gNB may include multiple configurations. Each configuration includes a periodicity, an offset with the period, the number of LP-WUS starting from the offset, a symbol for the LP-WUS in a subframe or slot, and PRBs occupied by the LP-WUS. Note that multiple LP-WUS in a period may occupy consecutive or non-consecutive subframes or slots. The occupied PRBs may include only PRBs for LP-WUS transmission or both PRBs for LP-WUS transmission and guard bands.

[0028] As a further extension, one or more muting patterns for the LP-WUS may be configured by RRC signaling. For a muting pattern, a bitmap of corresponding transmission opportunities for the LP-WUS may be defined. In particular, if a bit "0" is indicated in the bitmap, the corresponding transmission opportunity for the LP-WUS may be muted or not transmitted. If a bit "1" is indicated in the bitmap, the corresponding transmission opportunity for the LP-WUS may be transmitted.

[0029] Furthermore, the first gNB may transmit the configuration of the muting pattern of the LP-WUS to the second gNB via the Xn interface.

[0030] In one embodiment, the second cell may refrain from transmitting any channel / signal in the time / frequency resources of the LP-WUS in the first cell, thus avoiding interference from the second cell to the LP-WUS of the first cell.

[0031] In one option, one or more zero-power (ZP) LP-WUSs can be configured for a UE in a cell. The ZP LP-WUS configuration may include the periodicity, the offset in the periodicity, the number of subframes or slots containing the ZP LP-WUS, or the starting and ending OFDM symbols of the ZP LP-WUS in a slot. Correspondingly, the resources indicated by the ZP LP-WUS are not applicable for DL ​​reception and / or UL transmission for UEs in the cell. With respect to a configured ZP LP-WUS, the gNB may refrain from transmitting or receiving any DL or UL channels / signals in the cell, thereby avoiding interference with LP-WUSs in other cells.

[0032] In one embodiment, in the time / frequency resources of the LP-WUS in the first cell, the second cell may transmit a channel / signal other than the LP-WUS. In this way, interference from the second cell to the LP-WUS in the first cell is a regular OFDM symbol. Furthermore, the interference of the LP-WUS in the first cell can be reduced by reducing the transmit power of the channel / signal in the second cell. The second gNB may indicate the transmit power of the channel / signal in the second cell at the second gNB that overlaps with the LP-WUS in the first cell at the first gNB.

[0033] In one embodiment, in the time / frequency resources of the LP-WUS in the first cell, the second cell may transmit the LP-WUS in the same time / frequency resources in the second cell. The transmit power of the LP-WUS may be exchanged between the two gNBs. For example, the first gNB indicates the intended transmit power of the LP-WUS to the second gNB. The second gNB may use a lower transmit power. The LP-WUS transmitted by the first gNB may support cell-edge UEs, and the LP-WUS transmitted by the second gNB at the lower transmit power may only support cell-center UEs.

[0034] Randomization of the sequence of WUS symbols When a WUS symbol in a first cell may overlap with a WUS symbol from a second cell, it is beneficial for interference mitigation if the sequence of WUS symbols can be randomized for different cells.

[0035] In one embodiment, the sequence of samples of a WUS symbol of a cell can be generated based on at least one of the following parameters: a subframe or slot index, an OFDM symbol index, an LP-WUS opportunity index, a physical cell ID (PCID), a virtual cell ID, a tracking area ID, a RAN area ID, a paging group ID, or a UE ID. Accordingly, sequences of samples of a WUS symbol from different cells can have low correlation, which can help reduce inter-cell interference. The same sequence can be generated and applied to samples of different WUS symbols of an LP-WUS. Alternatively, sequences of samples of different WUS symbols of an LP-WUS can be generated separately. Alternatively, sequences of samples of WUS symbols of different LP-WUS within a period can be generated separately. The period can be the periodicity for a frame, a subframe, a slot, or an LP-WUS configuration. The period for a second type of LP-WUS can be the periodicity for a first type of LP-WUS.

[0036] In another embodiment, a common sequence of WUS symbol samples that can be applied to any cell may be defined, and a cell-specific scrambling sequence may be applied beyond the common sequence. The scrambling sequence may be a pseudo-random sequence, such as a Gold sequence. The scrambling sequence may be generated based on at least one of the following parameters: a subframe or slot index, an OFDM symbol index, an LP-WUS opportunity index, and a physical cell ID (PCID), a virtual cell ID, or a UE ID. For example, a scrambling sequence for each WUS symbol may be generated based on the PCID and the OFDM symbol index. As another example, a scrambling sequence may be generated based on the PCID without symbol index dependency and repeatedly applied to each WUS symbol of the LP-WUS. A scrambling sequence may be generated, and different segments of the scrambling sequence may be applied to different WUS symbols of the LP-WUS. Alternatively, a scrambling sequence may be generated, and different segments of the scrambling sequence may be applied to WUS symbols of multiple LP-WUS within a period. The period may be a frame, a subframe, a slot, or a periodicity for the LP-WUS configuration. The period for the second type of LP-WUS may be the periodicity of the first type of LP-WUS.

[0037] In one option, if DFT-s-OFDM based generation for LP-WUS is adopted, a scrambling sequence can be applied to the samples of the WUS symbol before the DFT operation.

[0038] In another option, the LP-WUS can be generated by first generating intermediate samples of the WUS samples of the OFDM symbol, then transforming and mapping the intermediate samples to a set of subcarriers for the LP-WUS, and finally performing an IDFT to generate the transmitted OFDM carrying the WUS symbol. In this scheme, a scrambling sequence can be applied to the intermediate samples of the WUS symbols of the OFDM symbol.

[0039] Randomization in units of WUS symbols The LP-WUS consists of multiple WUS symbols. Therefore, it is beneficial for interference mitigation if the sequence of WUS symbols in the LP-WUS can be randomized for different cells on a WUS symbol basis. In other words, the sequence elements are applied to all samples of the WUS symbol.

[0040] In one embodiment, on a WUS symbol basis, the sequence for the WUS symbols in the first part of the LP-WUS can be different for different cells. The sequences used in different cells can have low correlation, which can help reduce inter-cell interference. The sequence can be determined based on at least one of the following parameters: subframe or slot index, OFDM symbol index, LP-WUS opportunity index, physical cell ID (PCID), virtual cell ID, tracking area ID, RAN area ID, paging group ID, or UE ID.

[0041] In another embodiment, a scrambling sequence may be applied to the WUS symbols for the second part of the LP-WUS on a WUS symbol-by-WUS symbol basis. The scrambling sequence may be different for different cells. The scrambling sequences used in different cells may have low correlation, which may help reduce inter-cell interference. The scrambling sequence may be generated based on at least one of the following parameters: subframe or slot index, OFDM symbol index, LP-WUS opportunity index, and physical cell ID (PCID), virtual cell ID, tracking area ID, RAN area ID, paging group ID, UE ID, or sequence ID for the first part of the LP-WUS.

[0042] In another embodiment, scrambling can be applied to the WUS symbols of multiple LP-WUSs within a period on a WUS symbol basis. The scrambling sequence may be applied to both the first and second parts of the multiple LP-WUSs. The scrambling sequence can be different for different cells. Preferably, the sequences used in different cells can have low correlation. The scrambling sequence can be generated based on at least one of the following parameters: subframe or slot index, OFDM symbol index, LP-WUS opportunity index or physical cell ID (PCID), tracking area ID, RAN area ID, paging group ID, or UE ID.

[0043] Orthogonal spreading codes in different cells In one embodiment, orthogonal spreading codes across multiple WUS symbols can be used in different cells to mitigate inter-cell interference on a WUS symbol basis. In one example, assuming that information bits from a first cell are spread with the code [1 0 1 0] and information bits from a second cell are spread with the code [1 1 0 0], the mutual interference between the two cells can be reduced due to the orthogonality of the spreading codes.

[0044] In one option, the spreading codes for the LP-WUS in a cell can be configured together with other parameters in the LP-WUS configuration. The spreading codes applied to different information bits can be configured or derived separately by the spreading code applied to the first information bit and / or other parameters. Alternatively, the same spreading code is applied to all information bits.

[0045] Alternatively, the spreading code for LP-WUS in a cell can be implicitly determined by other parameters, such as a physical cell ID, a virtual cell ID, a tracking area ID, a RAN area ID, a paging group ID, or a UE ID. The index of the information bit can also be used in spreading code determination. As a result, different spreading codes can be used for different information bits, which helps inter-cell interference randomization.

[0046] As a further enhancement, the spreading code for the second part of the LP-WUS may be determined according to the spreading code ID and / or the time / frequency resource ID for the first part of the LP-WUS.

[0047] CRC Masking If LP-WUS from multiple cells may overlap each other, a scheme is needed to identify the source cell transmitting the LP-WUS.

[0048] In one embodiment, the ID can be masked on the CRC attached to the payload of the LP-WUS, and the ID can be derived by at least one of a physical cell ID (PCID), a virtual cell ID, a tracking area ID, a RAN area ID, a paging group ID, or a UE ID.

[0049] In one embodiment, the scrambling code applied to the LP-WUS may be derived by at least one of a physical cell ID (PCID), a virtual cell ID, a tracking area ID, a RAN area ID, a paging group ID, or a UE ID.

[0050] Techniques for collision handling in LP-WUS The wake-up signal / channel can be transmitted within the same carrier of the main radio, e.g., an in-band wake-up signal / channel, or on a dedicated carrier different from the carrier of the main radio, e.g., an out-of-band wake-up signal / channel.

[0051] Various embodiments herein provide techniques for coexistence between low power wake-up signals / channels and other signals / channels for in-band use cases (e.g., uplink and / or downlink channels of a wireless cellular network, such as a New Radio (NR) network). For example, embodiments include systems and methods for LP-WUS configuration and reception taking into account other signals / channels, and other signal / channel configuration and reception taking into account LP-WUS.

[0052] A UE may be configured with one or more types of low power wake-up signals / channels (LP-WUS). For example, a first type of LP-WUS, also known as LP-SS, may be transmitted periodically, and a second type of LP-WUS may be transmitted on demand, e.g., to trigger paging reception by the main radio.

[0053] For the in-band LP-WUS case, within a carrier, LP-WUS and other NR channels / signals can be multiplexed using TDM as shown in Figure 3, or FDM or CDM or SDM or a combination of at least two of the multiplexing mechanisms as shown in Figure 4.

[0054] The multiplexing mechanism can be predefined or configured by the gNB. The multiplexing mechanism can depend on the frequency band, e.g., FR1 or FR2. The multiplexing mechanism can depend on the duplex mode, e.g., TDD or FDD or half-duplex FDD or full-duplex. The multiplexing mechanism can depend on the type of LP-WUS, e.g., FDM for a first type of LP-WUS and other NR signals / channels, and TDM for a second type of LP-WUS and other NR signals / channels.

[0055] For an FDD system, the NR channels / signals are DL channels / signals, such as SSB, CSI-RS, DMRS, PTRS, DL-PRS, PDSCH, and PDCCH. For a TDD or half-duplex FDD system, the NR channels / signals can be DL channels / signals or both DL and UL channels / signals, such as SRS, PUSCH, PUCCH, and PRACH.

[0056] In embodiments herein, a LP-WUS can be configured for a UE and the UE detects the LP-WUS for one or more functions, such as RRM or wake-up of the main radio, or alternatively, a LP-WUS can be configured for a UE and the UE does not detect the LP-WUS.

[0057] LP-WUS Reception on a TDD Carrier In one embodiment, when LP-WUS and other NR signals / channels are multiplexed on a TDD carrier, the UE may or may not expect the LP-WUS symbols to be indicated as uplink by the TDD configuration when provided to the UE. The LP-WUS symbols may be configured or predefined by the gNB.

[0058] In one option, the UE does not expect the symbols of the LP-WUS to be indicated as uplink by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE, and the UE can receive the LP-WUS in the configured symbols of the LP-WUS.

[0059] In another option, whether the symbols of the LP-WUS can overlap with the uplink symbols depends on the type of the LP-WUS.

[0060] For example, if the LP-WUS is a first type LP-WUS, the UE does not expect the symbols of the LP-WUS to be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE. The UE can receive the LP-WUS in the configured symbols of the LP-WUS. If the LP-WUS is a second type LP-WUS, the symbols of the LP-WUS can be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE. The UE drops reception of the LP-WUS if at least some of the symbols of the LP-WUS overlap with uplink symbols.

[0061] In one option, whether the LP-WUS symbols can overlap with UE-specific or cell-specific uplink symbols depends on the RRC state of the UE.

[0062] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon when provided to the UE when the UE is in RRC idle state.

[0063] In one example, when the UE is in RRC idle state, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE, and tdd-UL-DL-ConfigurationDedicated is provided in RRC release signaling.

[0064] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon when provided to the UE when the UE is in an RRC inactive state.

[0065] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE when the UE is in an RRC inactive state.

[0066] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon when provided to the UE when the UE is in an RRC connected state.

[0067] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE when the UE is in an RRC connected state.

[0068] In one example, the UE does not expect the LP-WUS symbols to be indicated as uplink by the tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, or by the slot format indication (SFI), when provided to the UE, when the UE is in an RRC connected state.

[0069] In one option, whether the symbols of the LP-WUS can overlap with UE-specific or cell-specific uplink symbols depends on the RRC state of the UE and the type of LP-WUS.

[0070] In one embodiment, the UE does not expect the PRBs of the LP-WUS to overlap with the SS / PBCH blocks. Alternatively, the PRBs of the LP-WUS may overlap with the SS / PBCH blocks, and the UE drops the LP-WUS reception if at least one PRB of the LP-WUS overlaps with the SS / PBCH. In one option, the SS / PBCH block can be a cell-defining SSB (CD-SSB), e.g., an SS / PBCH block indicated by ssb-PositionsInBurst in SIB1 or by ssb-PositionsInBurst in ServingCellConfigCommon. In another option, the SS / PBCH block can be an NCD-SSB. Note that this embodiment is also applicable to FDD carriers.

[0071] In one embodiment, if the LP-WUS symbols can be indicated as uplink when provided to the UE, and if the LP-WUS resources can occupy multiple subframes or slots, the UE can determine whether the LP-WUS is dropped or postponed in a slot if the LP-WUS symbols in the slot overlap with the indicated uplink symbols.

[0072] In one option, an LP-WUS in a slot is dropped if the symbols of the LP-WUS in the slot overlap with uplink symbols according to tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, or according to SFI, when provided to the UE.

[0073] Figure 5 provides an example. The LP-WUS consists of multiple transmission opportunities in both slot n and slot n+1, for example, with a repetition factor = 2. If slot n+1 is a UL slot, the LP-WUS in slot n+1 is dropped.

[0074] In another option, an LP-WUS in a slot is postponed until the next available slot if the symbols of the LP-WUS in the slot overlap with uplink symbols according to tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE.

[0075] Figure 6 provides an example. The LP-WUS consists of multiple transmission opportunities in both slot n and slot n+1, for example, with a repetition factor = 2. If slot n+1 is a UL slot and slot n+2 is a DL slot, the LP-WUS in slot n+1 is postponed until slot n+2.

[0076] In one embodiment, if PRBs of the LP-WUS may overlap with SS / PBCH blocks according to ssb-PositionsInBurst in SIB1 or according to ssb-PositionsInBurst in ServingCellConfigCommon, and if the LP-WUS resources may occupy multiple subframes or slots, the UE may postpone the LP-WUS in a slot if at least one PRB of the LP-WUS in the slot overlaps with the SS / PBCH. Note that this embodiment is also applicable to FDD carriers.

[0077] In one embodiment, the PRB of the LP-WUS may overlap with the PDSCH. The UE may drop the LP-WUS reception, or the UE may receive the LP-WUS. The UE behavior may depend on the PDSCH type and / or the LP-WUS type. For example, if the PDSCH is a PDSCH carrying an SIB, the LP-WUS is dropped. As another example, if the LP-WUS is a first type of LP-WUS, the UE receives the LP-WUS. Alternatively, the UE does not expect a PDSCH of a specific type to overlap with an LP-WUS of a specific type. Note that this embodiment is also applicable to FDD carriers.

[0078] In one embodiment, the PRB of the LP-WUS may overlap with a CORESET or a PDCCH. In one option, the UE drops the LP-WUS. The UE can drop the LP-WUS reception, or the UE can receive the LP-WUS. The UE behavior can depend on the PDCCH / CORESET type and / or the LP-WUS type. For example, if the CORESET is CORESET0 with search space ID=0, the LP-WUS is dropped. As another example, if the LP-WUS is a first type of LP-WUS, the UE receives the LP-WUS. Alternatively, the UE does not expect a PDCCH / CORESET with a specific type to overlap with an LP-WUS with a specific type. Note that this embodiment is also applicable to FDD carriers.

[0079] In one embodiment, when LP-WUS and other NR signals / channels are multiplexed on a TDD carrier, the UE may or may not expect the LP-WUS symbols to overlap with valid PRACH opportunities or Msg A PUSCH opportunities. Note that this embodiment is also applicable to half-duplex FDD operation. In some aspects, the PRACH transmission opportunities may include PRACH transmission opportunities for both 4-step and 2-step RACH.

[0080] In one option, the UE does not expect the LP-WUS symbols to overlap with valid PRACH or MsgA PUSCH opportunities.

[0081] In one option, the symbols of the LP-WUS may overlap with a valid PRACH opportunity or MsgA PUSCH opportunity. In one example, the UE does not receive the LP-WUS if the LP-WUS overlaps with a valid PRACH opportunity or MsgA PUSCH opportunity.

[0082] In another example, whether the LP-WUS overlaps with a valid PRACH opportunity or MsgA PUSCH opportunity depends on whether the UE implementation receives the LP-WUS or not.

[0083] In another example, the UE can receive LP-WUS regardless of whether it overlaps with a valid PRACH opportunity or MsgA PUSCH opportunity.

[0084] In another example, the UE may receive the LP-WUS regardless of whether it overlaps with a valid PRACH opportunity or a MsgA PUSCH opportunity if the LP-WUS is a first type LP-WUS.

[0085] NR DL reception on carriers with LP-WUS For DL ​​reception of NR DL signals / channels, the DL reception can depend on the resources of the LP-WUS. NR DL signals / channels can be divided into two types: a first type of DL signal / channel includes at least cell-specific SSBs, and a second type of DL signal / channel includes at least unicast PDSCH.

[0086] In one embodiment, DL reception of at least the second type of DL signal / channel depends on the LP-WUS resource. Alternatively, DL reception of at least the second type of DL signal / channel depends on the LP-WUS resource if the LP-WUS is a first type of LP-WUS. Alternatively, DL reception of at least the second type of DL signal / channel does not depend on the LP-WUS resource. For example, if the PDSCH overlaps with the LP-WUS resource, the PDSCH is received as a legacy method that is not rate-matched around the LP-WUS resource.

[0087] In one option, DL reception of DL signals / channels is rate-matched around LP-WUS symbols, e.g., when LP-WUS and NR DL signals / channels overlap in time, the unicast PDSCH is rate-matched around the first type of LP-WUS symbols.

[0088] In another option, DL reception of DL signals / channels is rate-matched around PRBs of the LP-WUS, e.g., when the LP-WUS and NR DL signals / channels overlap in frequency, the unicast PDSCH is rate-matched around PRBs of the first type of LP-WUS.

[0089] For the above options, in one example, the gNB relies on the existing rate matching pattern to cover the PRBs and symbols of the LP-WUS. In another example, in addition to the existing RB symbol level rate matching pattern and CORESET rate matching pattern, a new rate matching pattern for the LP-WUS symbols or PRBs that need to be rate matched is introduced. The new rate matching pattern can be configured as one of semi-static or dynamic rate matching patterns. In another example, the LP-WUS symbols or PRBs that need to be rate matched are not included in the semi-static or dynamic rate matching pattern, but the UE can still perform rate matching based on the configured LP-WUS symbols or PRBs.

[0090] The symbols or PRBs of the LP-WUS can be derived from the resource configuration for the LP-WUS provided in the system information or from UE-specific signaling. For example, for a UE configured with LP-WUS reception, the UE may not know the LP-WUS resources for other UEs, but the UE can perform rate matching based on the configured LP-WUS. Alternatively, the symbols or PRBs of the LP-WUS can be derived from the resource configuration for rate matching.

[0091] To enable dynamic rate matching, the UE can be configured with a dedicated DCI, or a DL assignment / UL grant without DL-SCH / UL-SCH, or a DL assignment / UL with DL-SCH / UL-SCH, to indicate the presence of LP-WUS resources, and the UE can determine rate matching accordingly. The dedicated DCI can be UE-specific or UE group-specific. The dedicated DCI can be a new DCI or an existing DCI that adds a bit field, for example, in adding a state within the SFI. For example, the UE can be configured with one or more sets of LP-WUS resources by RRC signaling, and the dedicated DCI can indicate the presence of a portion of the LP-WUS within a slot or time window, for example, within the current or next cycle of the DCI, or within the current or next LP-WUS cycle. As another example, the UE may be configured with LP-WUS resources that may be rate-matched around by RRC signaling, and the DL allocation DCI scheduling the PDSCH may indicate the presence of LP-WUS that is to be rate-matched around by the PDSCH, e.g., by one bit in the DCI to indicate the presence of LP-WUS.

[0092] Different rate-matching mechanisms can be applied for different types of LP-WUS. For example, semi-static rate matching is performed for a first type of LP-WUS, and dynamic rate matching is performed for a second type of LP-WUS. Figure 7 provides an example. In slot n, there is a first type of LP-WUS resource, which is transmitted with periodicity, and in slot n+1, there is a second type of LP-WUS resource, which may or may not be transmitted on demand. In slot n, the unicast PDSCH (PDSCH1) always rate-matches around the first type of LP-WUS. However, in slot n+1, the gNB does not dynamically indicate rate matching for the second type of LP-WUS, and therefore PDSCH2 does not rate-match around the LP-WUS.

[0093] For this embodiment, in one option, the first type of DL signal / channel includes at least SS / PBCH blocks according to ssb-PositionsInBurst in SIB1 or according to ssb-PositionsInBurst in ServingCellConfigCommon. For example, in case of DL reception, for at least SS / PBCH blocks according to ssb-PositionsInBurst in SIB1 or according to ssb-PositionsInBurst in ServingCellConfigCommon, the UE can receive SS / PBCH without considering LP-WUS.

[0094] In another option, the first type of DL signal / channel includes a PDCCH in CORESET0 with search space ID = 0. The UE may receive the PDCCH in CORESET without considering the LP-WUS.

[0095] In another option, the first type of DL signal / channel includes at least a PDCCH in one of a Type0A-PDCCH CSS set, a Type0B-PDCCH CSS set, and a Type1-PDCCH CSS set, and the UE can receive the PDCCH in the CSS set without considering the LP-WUS.

[0096] In another option, the first type of DL signal / channel includes a PDCCH in a Type 3 CSS set.

[0097] In another option, the first type of DL signal / channel includes a PDCCH in any SS set.

[0098] In another option, the first type of DL signal / channel includes at least a non-unicast PDSCH scheduled by a PDCCH in one of the Type0-PDCCH CSS set, the Type0A-PDCCH CSS set, the Type0B-PDCCH CSS set, and the Type1-PDCCH CSS set.

[0099] In another option, the first type of DL signal / channel includes CSI-RS.

[0100] In another option, the first type of DL signal / channel includes CSI-RS for a specific function, for example, for mobility.

[0101] In another option, the first type of DL signal / channel includes a DMRS.

[0102] NR UL transmission on TDD carrier with LP-WUS For UL transmission of NR UL signals / channels in semi-static flexible symbols, UL reception can depend on the resources of the LP-WUS. NR UL signals / channels can be divided into two types: the first type of UL signals / channels includes at least a cell-specific PRACH, and the second type of UL signals / channels includes at least a unicast PUSCH.

[0103] In one embodiment, the UL transmission of at least the second type of UL signal / channel depends on the LP-WUS resource. For example, if the PUSCH overlaps with a symbol of the LP-WUS, the unicast PUSCH can be dropped, but the PRACH transmission can be transmitted regardless of the presence of the LP-WUS symbol. Alternatively, the UL transmission of at least the second type of UL signal / channel depends on the LP-WUS resource if the LP-WUS is a first type of LP-WUS. For example, whether to transmit the unicast PUSCH depends on whether the PUSCH overlaps with a symbol of the first type of LP-WUS, but the PUSCH transmission may not depend on a symbol of the second type of LP-WUS. The gNB can avoid overlap between the PUSCH and the second type of LP-WUS by appropriate implementation, for example, not configuring / scheduling overlapping resources or canceling the upper layer PUSCH in the symbol of the second type of LP-WUS via an SFI.

[0104] In one option, the UE does not expect to be scheduled for an UL transmission that overlaps with a symbol of the first type of LP-WUS. In another option, the UE does not expect to be scheduled for an UL transmission in a single transmission opportunity that overlaps with a symbol of the first type of LP-WUS, but the UE may be scheduled for an UL transmission that overlaps with a symbol of the first type of LP-WUS if the UL transmission has multiple transmission opportunities, e.g., in the case of PUSCH with repetition, or multi-PUSCH scheduling, or TBoMS. In another option, higher layer configured UL transmissions may overlap with symbols of the first type of LP-WUS.

[0105] If an UL transmission opportunity overlaps with an LP-WUS, the UE may drop the UL transmission or postpone the UL transmission until the next available slot. For example, if a PUSCH without available slot counting configuration overlaps with a first type of LP-WUS in a flexible symbol, the PUSCH is dropped. As another example, if a PUSCH configured with available slot counting overlaps with a first type of LP-WUS in a flexible symbol, the slot of the PUSCH is not counted as an available slot, and the PUSCH is postponed until the next available slot.

[0106] In one option, the UE may be indicated to drop symbols or rate-match around symbols for LP-WUS. For example, in an UL grant scheduling a PUSCH, a bit field in the UL grant may indicate the presence of LP-WUS so that the UE may drop symbols of the PUSCH or perform rate-matching of the PUSCH around symbols that overlap with the LP-WUS. As another example, the presence of LP-WUS may be indicated in a dedicated DCI similar to DCI2_4 for the UL CI.

[0107] For all the above embodiments, the UE may be configured with LP-WUS resources and guard bands for the LP-WUS. In one option, the LP-WUS resources include the guard bands for the LP-WUS. The above mechanism for LP-WUS resource handling includes handling for the guard bands. Alternatively, the above mechanism for LP-WUS resource handling does not consider the guard bands.

[0108] System and Implementation 8-11 illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments.

[0109] 8 illustrates a network 800 according to various embodiments. Network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited in this respect, and the described embodiments may be applied to other networks, future 3GPP systems, or the like, that would benefit from the principles described herein.

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

[0111] In some embodiments, the network 800 may include multiple UEs directly coupled to each other via a sidelink interface. The UEs may be M2M / D2D devices communicating using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0112] In some embodiments, the UE 802 may further communicate with an AP 806 via an over-the-air connection. The AP 806 may manage a WLAN connection, which may function to offload some / all network traffic from the RAN 804. The connection between the UE 802 and the AP 806 may be consistent with any IEEE 802.11 protocol, where the AP 806 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 802, the RAN 804, and the AP 806 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). The cellular WLAN aggregation may utilize both cellular radio resources and WLAN resources by including the UE 802 configured by the RAN 804.

[0113] The RAN 804 may include one or more access nodes, such as, for example, an AN 808. The AN 808 may terminate air-interface protocols for the UE 802 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 808 may enable data / voice connectivity between the CN 820 and the UE 802. In some embodiments, the AN 808 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as, for example, a CRAN or a virtual baseband unit pool. The AN 808 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 808 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0114] In embodiments where the RAN 804 includes multiple ANs, they may be coupled to one another via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into control / user plane interfaces, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference control, etc.

[0115] The ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc., to provide the UE 802 with network access over the air interface. The UE 802 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and the RAN 804 may use carrier aggregation, allowing the UE 802 to be connected to multiple component carriers, each corresponding to a Pcell or an 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 eNBs, gNBs, ng-eNBs, etc.

[0116] The RAN 804 may provide an air interface via licensed or unlicensed spectrum. To operate in the unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA techniques using a PCell / Scell. Before accessing the unlicensed spectrum, the node may perform medium / carrier sensing operations, for example, based on a Listen-Before-Talk (LBT) protocol.

[0117] In a V2X scenario, the UE 802 or AN 808 may be or operate as an RSU, which may refer to any carrier infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a static (or relatively static) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU," an eNB may be referred to as an "eNB-type RSU," a gNB may be referred to as a "gNB-type RSU," etc. In one example, an RSU is a computing device coupled to radio frequency circuits located on the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuits that store intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low-latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof 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 backhaul network.

[0118] In some embodiments, the RAN 804 may be an LTE RAN 810 having an eNB, such as eNB 812. The LTE RAN 810 may provide an LTE air interface with the following characteristics: a 15 kHz SCS; a CP-OFDM waveform for DL ​​and an SC-FDMA waveform for UL; turbo coding for data and TBCC for control; etc. The LTE air interface may rely on the CSI-RS for CSI acquisition and beam management; the PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and the CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate in sub-6 GHz bands.

[0119] In some embodiments, the RAN 804 may be an NG-RAN 814 having a gNB, such as a gNB 816, or an ng-eNB, such as an ng-eNB 818. The gNB 816 may be connected to a 5G-capable UE using a 5G NR interface. The gNB 816 may be connected to a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 may also be connected to the 5G core via an NG interface, but may be connected to a UE via an LTE air interface. The gNB 816 and the ng-eNB 818 may be connected to each other via an Xn interface.

[0120] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface, which carries traffic data between nodes in the NG-RAN 814 and the UPF 848 (e.g., the N3 interface), and an NG Control Plane (NG-C) interface, which is the signaling interface between nodes in the NG-RAN 814 and the AMF 844 (e.g., the N2 interface).

[0121] The NG-RAN 814 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL; CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control; and LDPC for data. The 5G-NR air interface, like the LTE air interface, may rely on CSI-RS and PDSCH / PDCCH DMRS. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signals for time tracking. The 5G-NR air interface may operate in the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes the bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0122] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic SCS adaptation. For example, a UE 802 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is also changed. Another example use case of BWPs relates to power saving. In particular, multiple BWPs can be configured to support data transmissions for the UE 802 under different traffic load scenarios using different amounts of frequency resources (e.g., PRBs). A BWP with a smaller number of PRBs can be used for data transmissions with low traffic loads while enabling power savings at the UE 802 and, in some cases, at the gNB 816. A BWP with a larger number of PRBs can be used in scenarios with higher traffic loads. The RAN 804 is communicatively coupled to the CN 820, which includes network elements, to provide various functions and support data and telecommunication services to customers / subscribers (e.g., users of the UE 802). The components of CN 820 may be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functionality provided by the network elements of CN 820 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of CN 820 may be referred to as a network slice, and a logical instantiation of a portion of CN 820 may be referred to as a network sub-slice.

[0123] In some embodiments, the CN 820 may be an LTE CN 822, which may also be referred to as an EPC. The LTE CN 822 may include an MME 824, an SGW 826, an SGSN 828, an HSS 830, a PGW 832, and a PCRF 834 coupled to each other via interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 822 may be briefly introduced as follows.

[0124] The MME 824 may implement mobility management functions, track the current location of the UE 802, and facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0125] The SGW 826 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 822. The SGW 826 may be a local mobility anchor point for inter-RAN node handovers and may provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0126] The SGSN 828 may track the location of the UE 802 and perform security functions and access control. In addition, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; selection of PDN and S-GW designated by the MME 824; MME selection for handover, etc. The S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0127] The HSS 830 may include a database for network users containing subscription-related information to support communication session handling of the network entities. The HSS 830 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authentication / authorization of user access to the LTE CN 820.

[0128] The PGW 832 may terminate an SGi interface toward a data network (DN) 836, which may include an application / content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled to the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may further include nodes for policy enforcement and charging data collection (e.g., PCEF). In addition, the SGi reference point between the PGW 832 and the data network 836 may be a public, private PDN, or intra-operator packet data network external to the operator, for example, for provisioning of IMS services. The PGW 832 may be coupled to a PCRF 834 via a Gx reference point. The PCRF 834 is the policy and charging control element of the LTE CN 822. The PCRF 834 is communicatively coupled to the app / content server 838 and may determine appropriate QoS and charging parameters for service flows. The PCRF 832 may provision the associated rules to the PCEF (over the Gx reference point) using the appropriate TFT and QCI.

[0129] In some embodiments, the CN 820 may be a 5GC 840. The 5GC 840 may include an AUSF 842, an AMF 844, an SMF 846, a UPF 848, an NSSF 850, an NEF 852, an NRF 854, a PCF 856, a UDM 858, and an AF 860 coupled to each other via interfaces (or "reference points") as shown. The functionality of the elements of the 5GC 840 may be briefly introduced as follows: The AUSF 842 may store data for authentication of the UE 802 and handle authentication-related functions. The AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 840 via reference points as shown, the AUSF 842 may exhibit a Nausf service-based interface.

[0130] The AMF 844 may allow other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and subscribe to notifications about mobility events related to the UE 802. The AMF 844 may be responsible for registration management (e.g., for registering the UE 802), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 844 provides transport for SM messages between the UE 802 and the SMF 846 and may act as a transparent proxy for routing SM messages. The AMF 844 may also provide transport for SMS messages between the UE 802 and the SMSF. The AMF 844 may interact with the AUSF 842 and the UE 802 to perform various security anchor and context management functions. Furthermore, the AMF 844 may be the termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 804 and the AMF 844; the AMF 844 is the termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 844 may also support NAS signaling with the UE 802 over the N3 IWF interface.

[0131] The SMF 846 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 848 and the AN 808); UE IP address allocation and management (including optional authorization); selection and control of the UP function; configuring traffic steering in the UPF 848 to route traffic to the appropriate destination; terminating the interface towards the policy control function; controlling the policy enforcement, charging, and QoS portions; lawful interception (for SM events and the interface towards the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent through the N2 to the AN 808 via the AMF 844; and determining the SSC mode of the session. SM may refer to the management of a 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 802 and the data network 836.

[0132] The UPF 848 may operate as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 836, and a branching point for supporting multi-homed PDU sessions. The UPF 848 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of 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 validation (e.g., SDF to QoS flow mapping), perform transport-level packet marking in the uplink and downlink, downlink packet buffering, and downlink data notification triggering. The UPF 848 may include an uplink classifier to support routing traffic flows to the data network.

[0133] The NSSF 850 ​​may select a set of network slice instances to serve the UE 802. The NSSF 850 ​​may also determine, if necessary, the allowed NSSAIs and their mapping to subscribed S-NSSAIs. The NSSF 850 ​​may also determine the AMF set to be used to serve the UE 802, or a list of candidate AMFs based on a preferred configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 with which the UE 802 is registered by interacting with the NSSF 850, which may result in an AMF change. The NSSF 850 ​​may interact with the AMF 844 via the N22 reference point; it may communicate with another NSSF in the visited network via the N31 reference point (not shown). Additionally, the NSSF 850 ​​may exhibit an Nnssf service-based interface.

[0134] The NEF 852 may securely expose services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, AFs (e.g., AFs 860), edge computing or fog computing systems, etc. In such embodiments, the NEF 852 may authenticate, authorize, or throttle AFs. The NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between AF service identifiers and internal 5GC information. The NEF 852 may also receive information from other NFs based on the exposed capabilities of the other NFs. This information may be stored in the NEF 852 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs, or used for other purposes, such as analysis. Additionally, the NEF 852 may present an NEF service-based interface. The NRF 854 may support service discovery functions, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. The NRF 854 also maintains information about available NF instances and their supported services. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object, such as may occur during the execution of program code. Additionally, the NRF 854 may exhibit an Nnrf service-based interface. The PCF 856 may provide policy rules to control plane functions for their enforcement and may support a unified policy framework for governing network behavior. The PCF 856 may also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 858. In addition to communicating with functions through reference points as shown, the PCF 856 exhibits an Npcf service-based interface.The UDM 858 may handle subscription-related information to support handling of communication sessions by network entities and may store subscription data for the UE 802. For example, the subscription data may be communicated via the N8 reference point between the UDM 858 and the AMF 844. The UDM 858 may include two parts: an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and / or structured data for exposure and application data for the NEF 852 (including PFD for application discovery, application request information for multiple UEs 802). A Nudr service-based interface may be exposed by the UDR 221 to allow the UDM 858, PCF 856, and NEF 852 to access specific sets of stored data and to read, update (e.g., add, modify), delete, and subscribe to notifications of associated data changes in the UDR. The UDM may include a UDM-FE responsible for handling certificates, location management, subscription management, etc. Multiple different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identity handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 858 may present a Nudm service-based interface. The AF 860 may provide application influence over traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0135] In some embodiments, the 5GC 840 may enable edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 802 attaches to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5GC 840 may select a UPF 848 that is close to the UE 802 and perform traffic steering from the UPF 848 to the data network 836 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing. Based on operator deployment, when the AF 860 is deemed a trusted entity, the network operator may allow the AF 860 to interact directly with associated NFs. Additionally, the AF 860 may exhibit a NAF service-based interface. The data network 836 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, the application / content server 838.

[0136] FIG. 9 schematically illustrates a wireless network 900 in accordance with various embodiments. The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and the AN 904 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein. The UE 902 may be communicatively coupled to the AN 904 via a connection 906. The connection 906 is depicted as an air interface enabling the communicative coupling and may be consistent with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating in mmWave or sub-6 GHz frequencies. The UE 902 may include a host platform 908 coupled to a modem platform 910. The host platform 908 may include an application processing circuit 912, which may be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 may execute various applications for the UE 902 to source / sink application data. The application processing circuit 912 may further implement one or more layer operations to transmit / receive 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 914 may implement one or more of the layer operations to facilitate transmitting or receiving data over the connection 906. The layer operations implemented by the protocol processing circuit 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations. Additionally, the modem platform 910 may include a digital baseband circuit 916 that may implement one or more layer operations "below" the layer operations performed by the protocol processing circuit 914 in the network protocol stack.These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding which may include one or more of space-time, space-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. Additionally, modem platform 910 may include an RF front end (RFFE) 924, which may include or be connected to transmit circuits 918, receive circuits 920, RF circuits 922, and one or more antenna panels 926. Briefly, the transmit circuitry 918 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 920 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 922 may include low-noise amplifiers, power amplifiers, power tracking components, etc.; and the RFFE 924 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 components in the transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panel 926 (collectively referred to as "transmit / receive components") may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM, at mmWave or sub-6 GHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc. In some embodiments, the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.UE reception may be established by and through antenna panel 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. In some embodiments, antenna panel 926 may receive transmissions from AN 904 by receive beamforming signals that are received by multiple antennas / antenna elements of one or more antenna panels 926.

[0137] UE transmissions may be established by and through protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some embodiments, the transmit components of the UE 904 may apply spatial filtering to the transmitted data to form transmit beams that are radiated by the antenna elements of the antenna panel 926. Similar to the UE 902, the AN 904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit 932 coupled to the protocol processing circuitry 934 of the modem platform 930. The modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panel 946. The components of the AN 904 may be similar to and substantially interchangeable with similarly named components of the UE 902. In addition to performing data transmission / reception as described above, the components of the AN 908 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. FIG. 10 is a block diagram illustrating components that, according to some example embodiments, are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methodologies described herein. Specifically, FIG. 10 shows a diagrammatic representation of hardware resources 1000, including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may execute and provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1000.

[0138] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 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 DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those described herein), or any suitable combination thereof.

[0139] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 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.

[0140] Communications resources 1030 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1004 or one or more databases 1006 or other network elements over network 1008. For example, communications resources 1030 may include wired communications components (e.g., for coupling via USB, Ethernet, etc.), cellular communications components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communications components.

[0141] The instructions 1050 may include software, a program, an application, an applet, an app, or other executable code for causing at least one of the processors 1010 to perform any one or more of the methodologies discussed herein. The instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., in a processor's cache memory), the memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0142] FIG. 11 illustrates a network 1100 according to various embodiments. The network 1100 may operate in a manner consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1100 may operate simultaneously with the network 800. For example, in some embodiments, the network 1100 may share one or more frequency or bandwidth resources with the network 800. As a specific example, a UE (e.g., the UE 1102) may be configured to operate in both the network 1100 and the network 800. Such a configuration may be based on the UE including circuitry configured to communicate with the frequency and bandwidth resources of both the networks 800 and 1100. In general, elements of the network 1100 may share one or more characteristics with elements of the network 800. For the sake of brevity and clarity, such elements may not be repeated in the description of the network 1100.

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

[0144] Although not specifically shown in FIG. 11 , in some embodiments, the network 1100 may include multiple 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, a PSBCH, a PSDCH, a PSSCH, a PSCCH, a PSFCH, etc. Similarly, although not specifically shown in FIG. 11 , the UE 1102 may be communicatively coupled to an AP, such as the AP 806, as described with respect to FIG. 8 . Additionally, although not specifically shown in FIG. 11 , in some embodiments, the RAN 1108 may include one or more ANs, such as the AN 808, as described with respect to FIG. 8 . The RAN 1108 and / or the ANs of the RAN 1108 may be referred to as base stations (BSs), RAN nodes, or using some other terminology or designation.

[0145] The UE 1102 and the RAN 1108 may be configured to communicate over an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features, such as communication in terahertz (THz) or sub-THz bandwidths, or cooperative communication and sensing. As used herein, the term "cooperative communication and sensing" may refer to a system that enables wireless communication and radar-based sensing through various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communication in a frequency range above 80 GHz. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mm-wave" frequency ranges.

[0146] The RAN 1108 may enable communication between the UE 1102 and a 6G core network (CN) 1110. Specifically, the RAN 1108 may facilitate the transmission and reception of data between the UE 1102 and the 6G CN 1110. The 6G CN 1110 may include various functions, such as an NSSF 850, an NEF 852, an NRF 854, a PCF 856, a UDM 858, an AF 860, an SMF 846, and an AUSF 842. The 6G CN 1110 may additionally include a UPF 848 and a DN 836, as shown in FIG. 11 .

[0147] Additionally, the RAN 1108 may include various additional functions in addition to or instead of the functions of a traditional cellular network, such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1124 and a Compute Service Function (Comp SF) 1136. The Comp CF 1124 and the Comp SF 1136 may be part of or functions of a computing service plane. The Comp CF 1124 may be a control plane function that provides functions such as management of the Comp SF 1136, computing task context creation and management (e.g., creation, reading, modification, deletion), interaction with the underlying computing infrastructure for computing resource management, etc. The Comp SF 1136 may be a user plane function that acts as a gateway for interfacing computing service users (e.g., UE 1102) and computing nodes behind the Comp SF instance. Some functions of the Comp SF 1136 may include: analyzing computing service data received from users to compute tasks that can be performed by the computing nodes; maintaining a service mesh ingress gateway or service API gateway; service and billing policy enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1136 instance may act as a user plane gateway for a cluster of computing nodes. A Comp CF 1124 instance may control one or more Comp SF 1136 instances. Two other such functions may include a Communication Control Function (Comm CF) 1128 and a Communication Service Function (Comm SF) 1138, which may be part of the communication service plane.The Comm CF 1128 may be a control plane function for management of the Comm SF 1138, communication session creation / configuration / release, and communication session context management. The Comm SF 1138 may be a user plane function for data transport. The Comm CF 1128 and Comm SF 1138 may be considered upgrades to the SMF 846 and UPF 848 described with respect to the 5G system in FIG. 8. The upgrades provided by the Comm CF 1128 and Comm SF 1138 may enable service-aware transport. For conventional (e.g., 4G or 5G) data transport, the SMF 846 and UPF 848 may still be used.

[0148] Two other such functions may include a Data Control Function (Data CF) 1122 and a Data Service Function (Data SF) 1132, which may be part of the data service plane. The Data CF 1122 may be a control plane function, providing functions such as Data SF 1132 management, data service creation / configuration / release, data service context management, etc. The Data SF 1132 may be a user plane function, acting as a gateway between data service users (such as the UE 1102 and various functions of the 6G CN 1110) and data service endpoints behind the gateway. Specific functions may include parsing and forwarding data service user data to corresponding data service endpoints, generating charging data, and reporting data service status. Another such function may be a Service Orchestration and Chaining Function (SOCF) 1120, which may discover, orchestrate, and chain up communication / computing / data services provided by functions in the network. Upon receiving a service request from a user, SOCF 1120 may interact with one or more of Comp CF 1124, Comm CF 1128, and Data CF 1122 to identify instances of Comp SF 1136, Comm SF 1138, and Data SF 1132, configure service resources, and generate a service chain that may include multiple Comp SF 1136, Comm SF 1138, and Data SF 1132 instances and their associated computing endpoints. Workload processing and data movement may then occur within the generated service chain. SOCF 1120 may also be responsible for maintaining, updating, and releasing the created service chain.

[0149] Another such function may be a service registration function (SRF) 1114, which may act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 1136 and Data SF 1132 gateways and services provided by the UE 1102. The SRF 1114 may be considered a counterpart to the NRF 854, which may act as a registry for network functions.

[0150] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 1126, which may provide a service communication infrastructure for control plane services and user plane services. The eSCP may refer to a 5G service communication proxy (SCP) with the addition of user plane service communication proxy functionality. The eSCP is therefore expressed in two parts: eCSP-C 1112 and eSCP-U 1134 for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 1126 may control and configure the eCSP instances in terms of service traffic routing policies, access rules, load balancing configuration, performance monitoring, etc.

[0151] Another such function is the AMF 1144. The AMF 1144 may be similar to 844, but with additional functionality. Specifically, the AMF 1144 may include potential functional subdivisions, such as moving message forwarding functionality from the AMF 1144 to the RAN 1108.

[0152] Another such function is the service orchestration exposure function (SOEF) 1118. The SOEF can be configured to expose service orchestration and chaining services to external users, such as applications.

[0153] The UE 1102 may include an additional function referred to as a computing client service function (comp CSF) 1104. The comp CSF 1104 may have both control plane and user plane functions and may interact with corresponding network-side functions such as the SOCF 1120, Comp CF 1124, Comp SF 1136, Data CF 1122, and / or Data SF 1132 for service discovery, request / response, computational task workload exchange, etc. The Comp CSF 1104 may also coordinate with the network-side functions to determine whether a computing task should be performed on the UE 1102, on the RAN 1108, and / or on elements of the 6G CN 1110.

[0154] The UE 1102 and / or Comp CSF 1104 may include a service mesh proxy 1106. The service mesh proxy 1106 may act as a proxy for service-to-service communications within the user plane. The capabilities of the service mesh proxy 1106 may include one or more of addressing, security, load balancing, etc.

[0155] Exemplary Procedure In some embodiments, an electronic device, network, system, chip, or component of FIGS. 8-11 or some other figures herein, or a portion or implementation thereof, may be configured to perform one or more processes, techniques, or methods, or portions thereof, as described herein. One such process 1200 is shown in FIG. 12. Process 1200 may be performed by a gNB or a portion thereof. At 1202, process 1200 may include generating a sequence for symbols of a low-power wake-up signal (LP-WUS) based on one or more parameters associated with the LP-WUS. At 1204, process 1200 may further include transmitting the LP-WUS to a user equipment (UE) according to the generated sequence.

[0156] 13 shows another exemplary process 1300 according to various embodiments. Process 1300 may be performed by a first gNB or a portion thereof. At 1302, process 1300 may include receiving, from a second gNB, a first configuration of a first low-power wake-up signal (LP-WUS) to be transmitted by the second gNB. At 1304, process 1300 may further include determining, based on the first configuration, a second configuration for a second LP-WUS or another channel to be transmitted by the first gNB. At 1306, process 1300 may further include encoding the second LP-WUS or other channel for transmission based on the second configuration.

[0157] FIG. 14 shows another example process 1400 according to various embodiments. Process 1400 may be performed by a UE or a portion thereof. At 1402, process 1400 may include receiving a configuration to identify low-power wake-up signal (LP-WUS) opportunities at which the UE will monitor for LP-WUS. At 1404, process 1400 may further include identifying that a first one of the LP-WUS opportunities overlaps with a UL symbol of the UL / DL configuration. At 1406, process 1400 may further include dropping or postponing reception of the LP-WUS in the first LP-WUS opportunity based on the identification. For one or more embodiments, at least one of the components described in one or more of the drawings above may be configured to perform one or more operations, techniques, processes, and / or methods as described in the example sections below. For example, the baseband circuitry described above in connection with one or more of the drawings above may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, a base station, a network element, etc., described above in connection with one or more of the preceding drawings may be configured to operate according to one or more of the examples described in the exemplary section below. example

[0158] Some non-limiting examples of various embodiments are provided below.

[0159] Example A1 may include one or more computer-readable media (CRM) storing instructions that, when executed by one or more processors, generate a sequence for symbols of a low-power wake-up signal (LP-WUS) based on one or more parameters associated with the LP-WUS; and configure a next generation NodeB (gNB) to transmit the LP-WUS to a user equipment (UE) according to the generated sequence.

[0160] Example A2 may include one or more CRMs of Example A1 or some other example herein, where the one or more parameters include one or more of a subframe index, a slot index, a symbol index, an LP-WUS opportunity index, a physical cell ID (PCID), a virtual cell ID, a tracking area ID, a radio access network (RAN) area ID, a paging group ID, or a UE ID associated with the LP-WUS.

[0161] Example A3 may include one or more CRMs of Example A1 or some other example herein, where generating the sequence includes applying a scrambling sequence to a common sequence, the common sequence to be used by multiple cells, the scrambling sequence being cell-specific and generated based on the one or more parameters.

[0162] Example A4 may include one or more CRMs of Example A1 or some other example herein, where the sequence is used for multiple symbols of the LP-WUS.

[0163] Example A5 may include one or more CRMs of Example A1 or some other example herein, where the sequence is a first sequence, where the symbol is a first symbol, and where the instructions, when executed, further configure the gNB to generate a second sequence for a second symbol, where the second sequence is different from the first sequence.

[0164] Example A6 may include one or more CRMs of Example A1 or some other example herein, where the instructions, when executed, further configure the gNB to apply the sequence to samples of the symbols; and perform a discrete Fourier transform (DFT) operation or an inverse DFT (IDFT) operation on the symbols after application of the sequence.

[0165] Example A7 may include one or more CRMs of Example A1 or some other example herein, where the instructions, when executed, further configure the gNB to apply an orthogonal spreading code across multiple symbols of the LP-WUS prior to the transmission, the orthogonal spreading code being cell-specific.

[0166] Example A8 may include one or more CRMs of any one of Examples A1-A7 or some other example herein, where the instructions, when executed, further configure the gNB to mask an ID on a cyclic redundancy code (CRC) of the LP-WUS, the ID indicating a cell from which the LP-WUS is transmitted.

[0167] Example A9 may include one or more computer-readable media (CRM) having stored thereon instructions, when executed by one or more processors, to: receive, from a second gNB, a first configuration of a first low-power wake-up signal (LP-WUS) to be transmitted by the second gNB; determine, based on the first configuration, a second configuration for a second LP-WUS or another channel to be transmitted by the first gNB; and configure a first Next Generation NodeB (gNB) to encode the second LP-WUS or the other channel for transmission based on the second configuration.

[0168] Example A10 may include one or more CRMs of example A9 or some other example herein, where the first configuration indicates a resource over which the first LP-WUS is to be transmitted.

[0169] Example A11 may include one or more CRMs of Example A9 or some other example herein, where the first configuration includes a periodicity, an offset with a period, a number of repetitions of the first LP-WUS starting from the offset, a symbol for the first LP-WUS in a subframe or slot, or a physical resource block (PRB) occupied by the first LP-WUS.

[0170] Example A12 may include one or more CRMs of Example A9 or some other example herein, where the instructions, when executed, further configure the gNB to send feedback information to the second gNB based on the first configuration.

[0171] Example A13 may include one or more CRMs of any one of Examples A9-A12 or some other example herein, where determining the second configuration includes determining to mute or reduce transmit power of the second LP-WUS or the other channel in one or more resources on which the first LP-WUS is to be transmitted.

[0172] Example A14 may include a user equipment (UE) apparatus comprising: a memory configured to store an uplink (UL) / downlink (DL) configuration; and a processor circuit coupled to the memory, wherein the processor circuit is configured to receive a configuration to identify low power wake-up signal (LP-WUS) opportunities at which the UE will monitor for LP-WUS; identify that a first one of the LP-WUS opportunities overlaps with a UL symbol of the UL / DL configuration; and drop or postpone reception of the LP-WUS in the first LP-WUS opportunity based on the identification.

[0173] Example A15 may include the apparatus of example A14 or any other example herein, where the reception of the LP-WUS is dropped or postponed further based on a radio resource control (RRC) state of the UE.

[0174] Example A16 may include the apparatus of Example A14 or any other example herein, wherein the repetitions of the LP-WUS are transmitted in multiple LP-WUS opportunities, including the first LP-WUS opportunity and a second LP-WUS opportunity, in multiple slots, and the processor circuitry is to decode the LP-WUS in the second LP-WUS opportunity.

[0175] Example A17 may include the apparatus of Example A16 or any other example herein, wherein the processor circuitry is to postpone reception of the LP-WUS associated with the first LP-WUS opportunity until a subsequent subframe or slot that is a DL subframe or slot based on the UL / DL configuration.

[0176] Example A18 may include the apparatus of example A14 or any other example herein, where the UL / DL configuration is a common time division duplex (TDD) configuration or a dedicated TDD configuration.

[0177] Example A19 may include the apparatus of Example A14 or some other example herein, wherein the LP-WUS is dropped or postponed further based on whether the LP-WUS is a first type LP-WUS that is periodic or a second type LP-WUS that is aperiodic.

[0178] Example A20 may include the apparatus of any one of Examples A14-A19 or some other example herein, where the LP-WUS is a first LP-WUS, and the processor circuitry further receives a second LP-WUS in downlink resources; and receives another downlink channel rate-matched around the downlink resources, where a rate-matching mechanism of the another downlink channel is based on a type of the downlink channel or a type of the second LP-WUS.

[0179] Example B1 may include a method for inter-cell interference handling for low power wake-up signal transmission.

[0180] Example B2 may include the method of Example B1 or some other example herein, where the first gNB transmits the intended configuration of the LP-WUS to the second gNB.

[0181] Example B3 may include the method of Example B1 or some other example herein, wherein in the LP-WUS time / frequency resources in the first cell, the second cell refrains from transmitting any channel / signal.

[0182] Example B4 may include the method of Example B3 or some other example herein, where one or more zero power (ZP) LP-WUS are configured for UEs in the cell.

[0183] Example B5 may include the method of Example B1 or some other example herein, where in the time / frequency resources of LP-WUS in the first cell, the second cell transmits a channel / signal other than LP-WUS.

[0184] Example B6 may include the method of example B1 or some other example herein, where the sequence of samples of the WUS symbol is randomized for different cells.

[0185] Example B7 may include the method of Example B1 or some other example herein, where a cell-specific scrambling sequence is applied over a common sequence of samples of a WUS symbol.

[0186] Example B8 may include the method of Example B1 or some other example herein, where, on a WUS symbol basis, the sequence for the WUS symbols in the first part of the LP-WUS is different for different cells.

[0187] Example B9 may include the method of Example B1 or some other example herein, where the scrambling sequence is applied to the WUS symbols for the second part of the LP-WUS on a WUS symbol basis.

[0188] Example B10 may include the method of Example B1 or some other example herein, where orthogonal spreading codes across multiple WUS symbols are used in different cells on a WUS symbol basis.

[0189] Example B11 may include the method of Example B1 or some other example herein, where the ID is masked for the CRC appended to the payload of the LP-WUS.

[0190] Example B12 may include a first next generation NodeB (gNB) method, the method including: receiving, from a second gNB, a first configuration of a first low-power wake-up signal (LP-WUS) to be transmitted by the second gNB; and determining a second configuration for a second LP-WUS or another channel to be transmitted by the first gNB based on the first configuration; Equipped with.

[0191] Examples may include the method of B13, example B12, or some other example herein, where the first configuration indicates resources over which the first LP-WUS is to be transmitted.

[0192] Example B14 may include the method of Examples B12-B13 or any other example herein, where the first configuration includes a periodicity, an offset with a period, the number of the first LP-WUS, symbols for the first LP-WUS in a subframe or slot starting from the offset, and / or a PRB occupied by the first LP-WUS.

[0193] Example B15 may include the method of Examples B12-B14 or any other example herein, further comprising transmitting feedback information to the second gNB based on the first configuration.

[0194] Example B16 may include the method of Examples B12-B15 or any other example herein, where determining the second configuration includes determining to mute or reduce transmit power of the second LP-WUS or the other channel in one or more resources on which the first LP-WUS is to be transmitted.

[0195] Example C1 may include a method for low power wake-up signal (LP-WUS) reception and NR signal / channel reception and transmission with the presence of LP-WUS.

[0196] Example C2 may include the method of Example C1 or some other example herein, where the LP-WUS and NR signals / channels are in the same serving cell.

[0197] Example C3 may include the method of Example C2 or some other example herein, where the UE receives a LP-WUS on configured resources, and the UE does not expect the configured resources of the LP-WUS to overlap with UL symbols indicated by the TDD configuration for at least a first type of LP-WUS.

[0198] Example C4 may include the method of Example C2 or some other example herein, wherein the UE receives the LP-WUS in configured resources when the configured resources of the LP-WUS do not overlap with UL symbols indicated by the TDD configuration, and the UE drops or defers reception of the LP-WUS in configured resources when the resources of the LP-WUS overlap with UL symbols indicated by the TDD configuration.

[0199] Example C5 may include the method of Example C2 or some other example herein, wherein the UE receives the LP-WUS on configured resources when the configured resources of the LP-WUS do not overlap with cell-specific SS / PBCH resources, and the UE drops or defers reception of the LP-WUS on configured resources of the LP-WUS when the resources of the LP-WUS overlap with cell-specific SS / PBCH resources.

[0200] Example C6 may include the method of Example C2 or some other example herein, where the UE receives an NR DL signal / channel in response to the presence of an LP-WUS.

[0201] Example C7 may include the method of Example C6 or some other example herein, where the UE receives an NR DL signal / channel with rate matching around the LP-WUS resource.

[0202] Example C8 may include the method of Example C2 or some other example herein, where the UE transmits an NR UL signal / channel in response to the presence of an LP-WUS.

[0203] Example C9 may include the method of Example C8 or some other example herein, wherein the UE drops or defers NR UL signals / channels in symbols with LP-WUS resources.

[0204] Example C10 may include the method of example C6 and the method of example 8 or some other example herein, where the LP-WUS resource is a first type of LP-WUS resource.

[0205] Example C11 is a method of gNB, comprising: identifying a resource on which a low power wake-up signal (LP-WUS) is to be transmitted to a user equipment (UE); determining a UL-DL configuration based on the identified resources; and encoding an indication of UL-DL configuration for transmission to the UE; The method may include the steps of:

[0206] Example C12 may include the method of example C11 or any other example herein, where the UL-DL configuration is a TDD UL-DL configuration.

[0207] Example C13 may include the method of examples C11-C12 or some other example herein, where the UL symbols of the UL-DL configuration do not overlap with the identified resources.

[0208] Example C14 may include the method of Examples C11-C13 or some other example herein, where one or more DL symbols of the UL-DL configuration overlap with the identified resource.

[0209] Example C15 may include the method of Example C14 or some other example herein, further comprising encoding a DL signal (other than LP-WUS) for the UE into one or more DL symbols for transmission to the UE.

[0210] Example C16 may include the method of Examples C11 to C15 or any other example herein, where the LP-WUS is transmitted by the gNB.

[0211] Example D1 may include an apparatus comprising means for performing one or more elements of the method described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any other method or process described herein.

[0212] Example D2 may include one or more non-transitory computer-readable media containing instructions that, when executed by one or more processors of the electronic device, cause the electronic device to perform one or more elements of a method described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any other method or process described herein.

[0213] Example D3 may include an apparatus having logic, modules, or circuitry to perform one or more elements of the methods described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any other method or process described herein.

[0214] Example D4 may include a method, technique, or process as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any part or portion thereof.

[0215] Example D5 may include an apparatus that includes one or more processors and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process such as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or portions thereof.

[0216] Example D6 may include signals as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any part or portions thereof.

[0217] Example D7 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any part or portion thereof, or as otherwise described in this disclosure.

[0218] Example D8 may include a signal encoded with data as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any part or portion thereof, or as otherwise described in this disclosure.

[0219] Example D9 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or any portion or parts thereof, or as otherwise described in this disclosure.

[0220] Example D10 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process such as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or portions thereof.

[0221] Example D11 may include a computer program comprising instructions, where execution of the program by a processing element causes the processing element to perform a method, technique, or process such as described in or in connection with any of Examples A1-A20, B1-B16, C1-C16, or portions thereof.

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

[0223] Example D13 may include a method of communication in a wireless network as shown and described herein.

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

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

[0226] Any of the examples described above may be combined with any other example (or combination of examples) unless expressly stated otherwise. The above description of one or more implementations has been provided for illustration and description, and is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0227] Abbreviation Unless used differently herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0(2019-06). For purposes of this document, the following abbreviations may apply to the examples and embodiments described herein: 3GPP: Third Generation Partnership Project 4G: Fourth Generation 5G: Fifth Generation 5GC: 5G Core Network AC: Application Client ACR: Application Context Relocation ACK: Acknowledgement ACID: Application Client Identification ADRF: Analytical Data Repository Facility AF: Application Features AM: Acknowledgement mode AMBR: Aggregate Maximum Bitrate AMF: Access and Mobility Management Function AN: Access Network AnLF: Analytic Logic Facility ANR: Automatic Neighbor Relations 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 Layer ASP: Application Service Provider ASN.1: Abstract Syntax Notation 1 AUSF: Authentication Server Function AWGN: Additive white Gaussian noise BAP: Backhaul Adaptation Protocol BCH: Broadcast Channel BER: Bit Error Ratio BFD: Beam Fault 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: Contention-Based Random Access CC: Component Carrier, Country Code, Cryptographic Checksum 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: Billing Data Request CDR: Charging Data Response CFRA: Contention-Free Random Access CG: Cell Group CGF: Charging Gateway Function CHF: Billing function CI: Cell Identity CID: Cell ID (e.g., positioning method) CIM: Common Information Model CIR: Carrier-to-Interference Ratio CK: Encryption Key CM: Connection Management, Conditional Obligations CMAS: Commercial Mobile Alarm 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 replacement CSCF: Call Session Control Function CSAR: Cloud Services 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 reception 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: Charge trigger function CTS: Permit to send CW: Codeword CWS: Contention Window Size D2D: Device to Device DC: Dual connectivity, direct current DCI: Downlink Control Information DF: Expanded Flavor DL: Downlink DMTF: Distributed Management Task Force DPDK: Data Plane Development Kit DM-RS, DMRS: Decoded Reference Signal DN: Data Network DNN: Data Network Name DNAI: Data Network Access Identifier DRB: Data Radio Bearer DRS: Discovery Reference Signal DRX: Intermittent 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: Enhanced Clear Channel Assessment, Enhanced CCA ECCE: Extended Control Channel Element, Extended CCE ED: Energy detection EDGE: Enhanced Data Rates for GSM 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 Enabler Client EECID: Edge Enabler Client Identification EES: Edge Enabler Server EESID: Edge Enabler Server Identification EHE: Edge Host Environment EGMF: Exposure Governance Management Function EGPRS: Enhanced GPRS EIR: Equipment Identity Register eLAA: Extended License Assisted Access, extended LAA EM: Element Manager eMBB: Enhanced Mobile Broadband EMS: Element Management System eNB: Evolution NodeB, E-ULTRAN 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: Evolution 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: Enhanced 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: Fast Associated Control Channel / Half Rate FACH: Forward Access Channel FAUSCH: High-Speed ​​Uplink Signaling Channel FB: Function 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 research FFT: Fast Fourier Transform feLAA: Further Extended License Assisted Access, Further Extended 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 Positioning 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 Subscriber 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 (related to WUS) GUMMEI: Globally Unique MME Identifier GUTI: Globally 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 Credentials 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 4 IPv6: Internet Protocol version 6 IR: Infrared IS: Synchronous IRP: Integration Reference Point ISDN (registered trademark): Integrated Services Digital Network ISIM: IM Service Identity 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: kilobytes (1000 bytes) kbps: kilobits per second Kc: encryption 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: License Assisted Access LAN: Local Area Network LADN: Local Area Data Network LBT: Listen Before Talk LCM: Lifecycle Management LCR: Low Chip Rate LCS: Location Services LCID: Logical Channel ID LI: Layer Indicator LLC: Logical Link Control, Low 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 Tunnels LTE: Long Term Evolution M2M: Machine to Machine MAC: Medium Access Control (in the context of protocol layering) MAC: Message Authentication Code (security / encryption context) MAC-A: MAC used for authentication and key agreement (TSG T WG3 context) MAC-I: MAC used for data integrity of signaling messages (TSG T WG3 context) 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: Managed Data Analysis Facility MDAS: Managed Data Analysis Services MDT: Minimizing Drive Test ME: Mobile device 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: Masternode MNO: Mobile Network Operator MO: Measurement Object, Mobile Originated 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: Multiprotocol Label Switching 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 MTC: Machine Type Communications MTLF; Model Training Logical Function mMTC: Large-scale MTC, large-scale 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 Forwarding Path Descriptor NFV: Network Functions Virtualization NFVI: NFV Infrastructure NFVO: NFV Orchestrator NG: 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, Neighborhood Relations NRF:NF Repository Function NRS: Narrowband Reference Signal NS: Network Services NSA: Non-standalone operation mode NSD: Network Service Descriptor NSR: Network Service Record NSSAI: Network Slice Selection Aid Information S-NNSAI Single NSSAI (Single-NSSAI) NSSF: Network Slice Selection Function NW: Network NWDAF: Network Data Analysis Facility NWUS: Narrowband wake-up signal, narrowband WUS NZP: Non-zero power O&M: Operation and Maintenance ODU2: Optical Channel Data Unit Type 2 OFDM: Orthogonal Frequency Division Multiplexing OFDMA: Orthogonal Frequency Division Multiple Access OOB: Out-of-band OOS: Out of sync OPEX: Operating cost OSI:Other Systems 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: Precoded Matrix Indicator PNF: Physical Network Function PNFD: Physical Network Function Descriptor PNFR: Physical Network Function Record POC: PTT over cellular PP, PTP: Point-to-Point PPP: Point-to-Point Protocol PRACH:Physical RACH PRB: Physical Resource Block PRG: Physical Resource Block Group ProSe: Proximity Services, Proximity-Based Services PRS: Positioning Reference Signal PRR: Packet Receive 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 of Identifier QCL: Quasi-collocation QFI: QoS flow ID, QoS flow identifier QoS: Quality of Service QPSK: Quadrature (four-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 Remaining MSI, Minimum Remaining 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 reception quality RSSI: Received Signal Strength Indicator RSU: Roadside Unit RSTD: Reference signal time difference RTP: Real Time Protocol RTS: Ready-To-Send RTT: Round Trip Time Rx: Reception, receiving, receiver S1AP: S1 Application Protocol S1-MME: S1 for control plane S1-U: S1 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 Function Exposure Function SC-FDMA: Single Carrier Frequency Division Multiple Access SCG: Secondary Cell Group SCM: Security Context Management SCS: Subcarrier spacing SCTP: Stream Control Transmission Protocol SDAP: Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL: Auxiliary Downlink SDNF: Structured Data Storage Network Functions SDP: Session Description Protocol SDSF: Structured Data Storage Facility 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: Space-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: Initiating Session Protocol SiP: System in Package SL: Side link SLA: Service Level Agreement SM: Session Management SMF: Session Management Facility 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 Reception 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: Auxiliary 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: undefined TCI:Transmission Configuration Indicator TCP: Transmission communication protocol TDD: Time division duplex 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: Transmit Power Control TPMI: Transmit Precode Matrix Indicator TR: Technical Report TRP, TRxP: Transmit / Receive Point TRS: Tracking Reference Signal TRx: Transmitter / Receiver TS: Technical specifications, technical standards 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 Functions UICC: Universal Integrated Circuit Card UL: Uplink UM: Unacknowledged 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: Virtualization 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(R): 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 [term] For purposes of this document, the following terms and definitions are applicable to the examples and embodiments described herein.

[0228] The term "application" may refer to a complete and deployable package or environment for achieving a specific function in an operating environment. A term such as "AI / ML application" may refer to an application that includes several AI / ML models and application-level descriptions.

[0229] As used herein, the term “circuitry” refers to, is a part of, or includes a hardware component, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or 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., configured to provide a described function. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term “circuitry” may also refer to a combination of one or more hardware elements (or combinations of circuitry used in an electrical or electronic system) and program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0230] As used herein, the term “processor circuitry” refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations, or recording, storing, and / or transferring digital data. A processing circuitry 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 circuitry” may refer to one or more application processors, one or more baseband processors, physical central processing units (CPUs), single-core processors, dual-core processors, triple-core processors, quad-core processors, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous with “processor circuitry” and may be referred to as such. As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" 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.

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

[0232] 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 considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, and / or NFVI.

[0233] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Additionally, the terms "computer system" and / or "system" may refer to multiple computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

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

[0235] As used herein, the term “resource” refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component in a particular device, such as a computer device, a mechanical device, 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 assignments, throughput, memory usage, storage, networks, databases and applications, and / or workload units. “Hardware resources” may refer to computational, storage, and / or network resources provided by physical hardware elements. “Virtualization resources” may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The terms “network resources” or “communication resources” may refer to resources accessible by a computer device / system 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. A system resource may be viewed as a set of coherent functions, network data objects, or services that reside on a single host or on multiple hosts and are accessible through a clearly identifiable server.

[0236] As used herein, the term "channel" refers to any transmission medium, either tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous with and / or equivalent to "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 term meaning a path or medium over which data is communicated. Furthermore, as used herein, the term "link" refers to a connection between two devices through a RAT for the purpose of sending and receiving information.

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

[0238] The terms "coupled," "communicatively coupled," and 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, that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or that one or more other elements are coupled or connected between the elements that are said to be coupled with 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 may be in communication with each other, including through a wired or other interconnect connection and / or through a wireless communication channel or link.

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

[0240] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0241] The term "SSB" refers to an SS / PBCH block.

[0242] The term "primary cell" refers to an MCG cell operating on a primary frequency on which a UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0243] The term "primary SCG cell" refers to the SCG cell to which the UE performs random access when performing a Reconfiguration with Sync procedure for DC operation.

[0244] The term "secondary cell" refers to a cell that provides additional radio resources over a special cell for UEs configured with CA.

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

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

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

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

[0249] The terms "machine learning" or "ML" refer to the use of computer systems that implement algorithms and / or statistical models to perform specific tasks without explicit instructions, but instead rely on patterns and inference. ML algorithms build or infer mathematical models (e.g., referred to as "ML models") based on sample data (e.g., referred to as "training data," "model training information," etc.) to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, ML algorithms are computer programs that learn from experience with respect to a task and a performance measure, and an ML model can be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, the ML model can be used to make predictions or create new datasets. The term "ML algorithm" refers to a different concept from the term "ML model," but as discussed herein, these terms may be used interchangeably for purposes of this disclosure.

[0250] Terms such as "machine learning model," "ML model," or the like may also refer to ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that uses ML algorithms to address a specific use case during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbors (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (e.g., k-means clustering, principal component analysis (PCA)), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), and neural networks, etc. Depending on the implementation, a particular ML model may have many submodels as components, and the ML model may train all the submodels together. Separately trained ML models can also be chained together in an ML pipeline during inference. An "ML pipeline" is a set of functionality, features, or functional entities specific to an ML-assisted solution; an ML pipeline may include a data pipeline, a model training pipeline, a model evaluation pipeline, and one or more data sources in actors. An "actor" is an entity that hosts an ML-assisted solution with the output of ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during 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 performed by the actor as a result of the output of the ML-assisted solution). The term "model inference information" refers to information used as input to an ML model to determine an inference; although the data used to train an ML model and the data used to determine an inference may overlap, "training data" and "inference data" refer to different concepts.

Claims

1. Next-generation NodeB (gNB) processors generating a sequence for symbols of a low-power wake-up signal (LP-WUS) based on one or more parameters associated with the LP-WUS; and transmitting the LP-WUS to a user equipment (UE) according to the generated sequence; A computer program for executing

2. 2. The computer program product of claim 1, wherein the one or more parameters comprise one or more of a subframe index, a slot index, a symbol index, a LP-WUS occasion index, a physical cell ID (PCID), a virtual cell ID, a tracking area ID, a radio access network (RAN) area ID, a paging group ID, or a UE ID associated with the LP-WUS.

3. 2. The computer program product of claim 1, wherein generating the sequence comprises applying a scrambling sequence to a common sequence, the common sequence to be used by multiple cells, the scrambling sequence being cell-specific and generated based on the one or more parameters.

4. The computer program product of claim 1 , wherein the sequence is used for multiple symbols of the LP-WUS.

5. 2. The computer program of claim 1, wherein the sequence is a first sequence, the symbol is a first symbol, and the computer program further causes the processor to perform a procedure of generating a second sequence for a second symbol, the second sequence being different from the first sequence.

6. the processor, applying said sequence to samples of said symbol; and performing a Discrete Fourier Transform (DFT) or Inverse DFT (IDFT) operation on said symbols after said applying said sequence. The computer program of claim 1 , further comprising:

7. The computer program product of claim 1 , further causing the processor to perform the procedure of applying an orthogonal spreading code across multiple symbols of the LP-WUS prior to the transmission, the orthogonal spreading code being cell-specific.

8. 8. The computer program of claim 1, further comprising causing the processor to perform a procedure of masking an ID on a cyclic redundancy code (CRC) of the LP-WUS, the ID indicating a cell from which the LP-WUS is transmitted.

9. A computer-readable storage medium storing the computer program according to any one of claims 1 to 7.

10. The first next-generation NodeB (gNB) processor will receiving, from a second gNB, a first configuration of a first low-power wake-up signal (LP-WUS) to be transmitted by the second gNB; determining a second configuration for a second LP-WUS or another channel to be transmitted by the first gNB based on the first configuration; and encoding the second LP-WUS or other channel for transmission based on the second configuration. A computer program for executing

11. The computer program product of claim 10 , wherein the first configuration indicates a resource on which the first LP-WUS is to be transmitted.

12. 11. The computer program of claim 10, wherein the first configuration includes a periodicity, an offset with a period, a number of repetitions of the first LP-WUS starting from the offset, a symbol for the first LP-WUS in a subframe or slot, or a physical resource block (PRB) occupied by the first LP-WUS.

13. The computer program product of claim 10 , further causing the processor to perform the procedure of transmitting feedback information to the second gNB based on the first configuration.

14. A computer program according to any one of claims 10 to 13, wherein the procedure for determining the second configuration includes a procedure for determining to mute or reduce the transmission power of the second LP-WUS or the other channel in one or more resources in which the first LP-WUS is to be transmitted.

15. A computer-readable storage medium storing the computer program according to any one of claims 10 to 13.

16. A user equipment (UE) device, comprising: a memory adapted to store an uplink (UL) / downlink (DL) configuration; and a processor circuit coupled to the memory, the processor circuit comprising: receiving a configuration identifying a low power wake-up signal (LP-WUS) opportunity that the UE will monitor for an LP-WUS; Identifying that a first one of the LP-WUS opportunities overlaps with a UL symbol of the UL / DL configuration; and Dropping or postponing reception of the LP-WUS at the first LP-WUS opportunity based on the identification. It has become like this. An apparatus comprising:

17. The apparatus of claim 16 , wherein the reception of the LP-WUS is dropped or postponed further based on a radio resource control (RRC) state of the UE.

18. 17. The apparatus of claim 16, wherein the repetitions of the LP-WUS are transmitted in a plurality of the LP-WUS opportunities, including the first LP-WUS opportunity and a second LP-WUS opportunity, in a plurality of slots, and the processor circuitry is adapted to decode the LP-WUS in the second LP-WUS opportunity.

19. 20. The apparatus of claim 18, wherein the processor circuitry is to defer reception of the LP-WUS associated with the first LP-WUS opportunity until a subsequent subframe or slot that is a DL subframe or slot based on the UL / DL configuration.

20. 17. The apparatus of claim 16, wherein the UL / DL configuration is a common time division duplex (TDD) configuration or a dedicated TDD configuration.

21. 17. The apparatus of claim 16, wherein the LP-WUS is dropped or postponed further based on whether the LP-WUS is a first type of LP-WUS that is periodic or a second type of LP-WUS that is aperiodic.

22. The LP-WUS is a first LP-WUS, and the processor circuit further comprises: receiving a second LP-WUS in the downlink resource; and receiving another downlink channel rate-matched around the downlink resource, where the rate-matching mechanism of the another downlink channel is based on the type of the downlink channel or the type of the second LP-WUS; The device according to any one of claims 16 to 21,

Images