Signaling for on-demand synchronization signal block

Abstract

According to some embodiments, a method is performed by a wireless device for synchronization signal block (SSB) reception on a secondary cell (SCell). The method comprises: determining one of an activation state or deactivation state of the SCell; receiving a SSB indication for the SCell; determining a SSB configuration for the SCell based on the determined one of the activation state or deactivation state and the SSB indication; and performing one or more SSB operations according to the determined SSB configuration.

Description

SIGNALING FOR ON-DEMAND SYNCHRONIZATION SIGNAL BLOCKTECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to signaling for on-demand synchronization signal block (SSB).BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0003] For a cell in New Radio (NR), typically, a synchronization signal block (SSB) is transmitted periodically, and the SSB may be used to aid a user equipment (UE) with initial cell search, acquire frame / slot timing, initial time / frequency synchronization, measurements, and as a quasi-colocated (QCL) reference for channels / signals, etc. With beamforming, SSBs are transmitted in multiple beams. This can lead to further increased network energy consumption when the SSBs are transmitted in a burst that spans one or multiple slots.

[0004] An NR gNB may be configured with up to 64 SSBs. The configured SSBs in a cell for UEs in Radio Resource Control (RRC) IDLE / INACTIVE states all have the same periodicity and output power. The gNB may provide information to the UEs about how many / which SSBs are active (present) within the serving cell and neighboring cells. The SSB consists of a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and the physical broadcast channel (PBCH).

[0005] The gNB may further provide information about the rate / periodicity at which the SSBs are provided on a cell level. For the serving cell, the parameter ssb-PositionsInBurst indicateswhich of the SSBs are active, and the parameter ssb-PeriodicityServingCell specifies the rate / periodicity of the SSBs. Furthermore, the UEs are informed about the SSBs output power via the common parameter ss-PBCH-BlockPower . For neighbor cells, a gNB may specify the neighboring active (present) SSBs via the parameter ssb-ToMeasure and the associated rate / periodicity via the SSB Measurement Timing Configuration (SMTC), which defines the time window during which the UE measures the SSBs belonging to the neighboring cells.

[0006] The UE makes certain assumptions for a standalone NR cell upon the cell selection procedure. Even though the periodicity of the SSB is configurable, the UE upon initial cell selection expects that the SSB is provided every 20ms in that cell. The master information block (MIB) is part of the SSB. Together with SIB1, they are referred to as minimum system information (Minimum SI).

[0007] UEs are configured with the above SSB / SIB1 / SI presence and timing / rate information either in RRC IDLE / INACTIVE via broadcast system information or in RRC Connected via dedicated RRC messages. In IDLE / INACTIVE, the ssb-PositionsInBurst and ssb- PeriodicityServing for serving cell is configured via SIB1 and the SMTC configurations for neighboring cells are provided in SIB2 / SIB4 contained in SI messages.

[0008] FIGURE 1 illustrates an example of SSB transmission / structure. The horizontal axis represents the time domain in symbols, and the vertical axis represents the frequency domain in subcarriers.

[0009] The MIB is transmitted in the message part of the PBCH, which is a part of the SSB, and it contains the following information:MIB : : = SEQUENCE { systemFrameNumber BIT STRING ( SI ZE ( 6 ) ) , subCarrier SpacingCommon ENUMERATED { s cs l5or60 , s cs 30orl20 } , s sb-SubcarrierOf f set INTEGER ( 0 . . 15 ) , dmrs-TypeA- Position ENUMERATED { pos2 , pos 3 } , pdcch-Conf igSIBl PDCCH-Conf igSIBl , cellBarred ENUMERATED { barred, notBarred } , intraFreqRes election ENUMERATED { allowed, notAllowed } , spare BIT STRING ( SI ZE ( 1 ) )}

[0010] In addition to the MIB content, the SSB also provides the UE with a physical cell ID(derived from the sequence indexes of the PSS and SSS) and an SSB-Index (derived from the sequence index of the demodulation reference signal (DM-RS) transmitted in the PBCH).

[0011] In certain scenarios, a gNB may omit SSB transmissions on a cell and the UE may use SSB of another cell (e.g., another serving cell that is adjacent to the current serving cell in thesame frequency band, or with certain restrictions, another serving cell in in another frequency band).

[0012] A UE may be configured with multiple serving cells via carrier aggregation and / or dual connectivity (e.g., with a master cell group (MCG) and a secondary cell group (SCG)). There may be a primary serving cell (PCell) and one or more secondary serving cells (SCell). SSB(s) may be transmitted on each of the serving cells, including the primary serving cell and secondary serving cell.

[0013] The SCells may be activated / deactivated using an SCell activation command that is typically communicated using a medium access control (MAC) control element (CE), such as SCell Activation / Deactivation MAC CE or an enhanced SCell Activation / Deactivation MAC CE. For an activated SCell, the UE monitors downlink control messages (physical downlink control channel (PDCCH), etc.), measures and report channel state information (CSI), transmits uplink sounding reference signal (SRS), etc. For a deactivated SCell, the UE does not need to monitor PDCCH, etc., measure and report CSI, or transmit uplink SRS, etc. Thus, a UE can save energy when an SCell is deactivated.

[0014] Upon receiving an SCell activation message (e.g., from the gNB), the UE starts acquiring the automatic gain control (AGC), time / frequency synchronization and should be able to activate the SCell within a certain duration as defined by the requirements for different cases (known cell versus unknown cell, etc.). For an enhanced SCell Activation / Deactivation MAC CE, the MAC CE may also be used to trigger tracking reference signals (TRSs) or CSI- RS for tracking on the activated SCells to speed up the activation procedure.

[0015] Examples of legacy SCell activation / deactivation MAC CEs are given below. Some of the MAC CEs were described in prior Release (Rell 5 / 16 / 17 / 18) NR specifications.

[0016] In one example, the legacy SCell Activation / Deactivation MAC CE of one octet is identified by a MAC subheader with logical channel identifier (LCID) as specified in Table 6.2.1-1 of TS 38.321. It has a fixed size and consists of a single octet containing seven C-fields and one R-field (Reserve field). The SCell Activation / Deactivation MAC CE with one octet is defined as follows (Figure 6.1.3.10-1).• Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell with SCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 toindicate that the SCell with SCelllndex i shall be activated. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated;R: Reserved bit, set to 0.

[0017] FIGURE 2 illustrates SCell Activation / Deactivation MAC CE of one octet.

[0018] There is another legacy SCell activation / deactivation MAC CE of four octets that can support up-to 31 SCells. In this MAC CE signaling, the network indicates the wanted activation status for each configured SCell.

[0019] There is another legacy SCell activation / deactivation MAC CE referred to as Enhanced SCell activation / deactivation MAC CE, wherein along with the SCell activation message, the gNB may also indicate to the UE whether TRS for SCell activation is also triggered.• Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell with SCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with SCelllndex i shall be activated and that a TRS IDj field is included for the SCell. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated and that no TRS ID field is included for this SCell;• TRS IDj: If TRS IDj is set to a non-zero value, it indicates the corresponding TRS address by scellActivationRS-Id as specified in TS 38.331 is activated. If TRS IDj is set to zero, it indicates that no TRS is used for the corresponding SCell;• R: Reserved bit, set to 0.

[0020] FIGURE 3 illustrates enhanced SCell Activation / Deactivation MAC CE with one octet for SCell activation / deactivation.

[0021] There currently exist certain challenges. For example, provisioning of SSBs on demand for SCell operation may be done via UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, and / or SCell activation / deactivation signaling. On-demand SSB based on UE request, such as uplink wakeup signaling to enable SSB transmission on SCells, however, may lead to unnecessary overhead and complexity (e.g., define the wake-up request / procedure, etc.).SUMMARY

[0022] As described above, certain challenges currently exist with signaling for on-demand synchronization signal block (SSB). Certain aspects of the present disclosure and theirembodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling details for on-demand SSB operation, particularly different options for SSB assumption for an SCell based indications such as SCell activation / deactivation signaling, SCell activated / deactivated status, based on SSB indication bit along with SCell activation / deactivation, or based on SSB indication bit along with SCell activated / deactivated status.

[0023] According to some embodiments, a method is performed by a wireless device for SSB reception on a SCell. The method comprises: determining one of an activation state or deactivation state of the SCell; receiving a SSB indication for the SCell; determining a SSB configuration for the SCell based on the determined one of the activation state or deactivation state and the SSB indication; and performing one or more SSB operations according to the determined SSB configuration.

[0024] In particular embodiments, determining the activation state or deactivation state of the SCell is based on receiving an SCell activation or deactivation command. The SCell activation or deactivation command may be received separately from the SSB indication.

[0025] In particular embodiments, determining the activation state or deactivation state of the SCell is based on a SCell deactivation timer.

[0026] In particular embodiments, determining the SSB configuration comprises determining one or more of: a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

[0027] In particular embodiments, the wireless device monitors for SSB in the SCell according to a determined first SSB configuration when the SCell is determined to be in the activated state; and the wireless device does not monitor for SSB in the SCell when the SCell is determined to be in the deactivated state.

[0028] In particular embodiments, when the SSB indication indicates a first value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined first SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless device does not monitor for SSB in the SCell. When the SSB indication indicates a second value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined second SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless monitors for SSB in the SCell according to a determined third SSB configuration.

[0029] In particular embodiments, after determining the activation state or deactivation state of the SCell and before receiving the SSB indication, when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined fourth SSB configuration.

[0030] In particular embodiments, the third SSB configuration comprises a preconfigured or default configuration. The fourth SSB configuration may also comprise a preconfigured or default configuration.

[0031] In particular embodiments, a periodicity of the fourth SSB configuration is greater than a periodicity of any of the first SSB configuration, second SSB configuration, and third SSB configuration. Aperiodicity of the third SSB configuration may be less than a periodicity of any of the first SSB configuration and second SSB configuration.

[0032] In particular embodiments, the SSB according to the first SSB configuration comprises an on-demand SSB configuration.

[0033] In particular embodiments, the method further comprises determining quasi-colocation information for a physical channel or signal on the SCell based on the determined SSB configuration.

[0034] In particular embodiments, the SSB operation comprises one or more of acquiring frame / slot timing, initial time / frequency synchronization, measurements, and as a quasicolocation reference for channels or signals.

[0035] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless device described above.

[0036] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0037] According to some embodiments, a method is performed by a network node for SSB transmission on a SCell. The method comprises: transmitting to a wireless device a SCell activation or deactivation command and transmitting to the wireless device a SSB indication for the SCell. SSB is transmitted in the SCell based on a determined SSB configuration for the SCell based on a determined one of the activation state or deactivation state and the SSB indication.

[0038] In particular embodiments, the SSB indication is transmitted separately from the SCell activation or deactivation command.

[0039] In particular embodiments, the determined SSB configuration comprises one or more of: a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

[0040] In particular embodiments, when the SSB indication indicates a first value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a first SSB configuration; when the SCell is in the deactivated state, the SSB is not transmitted in the SCell. When the SSB indication indicates a second value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a second SSB configuration; and when the SCell is in the deactivated state, the SSB is transmitted in the SCell according to a third SSB configuration.

[0041] In particular embodiments, after transmitting the SCell activation or deactivation command and before transmitting the SSB indication, when the SCell is in the activated state, the SSB is transmitted in the SCell according to a fourth SSB configuration.

[0042] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0043] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0044] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments are directed towards user equipment (UE) behavior with respect to SSB assumptions based on signaling from a gNB, which improves UE performance while also enabling network energy savings.BRIEF DESCRIPTION OF THE DRAWINGS

[0045] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:FIGURE 1 illustrates an example of synchronization signal block (SSB)transmission / structure;FIGURE 2 illustrates SCell Activation / Deactivation medium access control (MAC) control element (CE) of one octet;FIGURE 3 illustrates enhanced SCell Activation / Deactivation MAC CE with one octet for SCell activation / deactivation;FIGURE 4 is a timing diagram illustrating omission / transmission / stoppage of SSB burst based on activation / deactivation commands, including aligning start / stop to the beginning of a complete SSB burst;FIGURE 5 is a timing diagram illustrating omission / transmission / stoppage of on- demand SSB burst based on activation / deactivation commands, including aligning start / stop to the beginning of a complete SSB burst, and transmission of periodic SSB;FIGURE 6 illustrates enhanced SCell activation / deactivation MAC CE with SSB transmission / absence indication;FIGURE 7 illustrates enhanced SCell activation / deactivation MAC CE with SSB transmission / absence indication and triggering tracking reference signal (TRS) for one or more SCells;FIGURE 8 illustrates an example communication system, according to certain embodiments;FIGURE 9 illustrates an example user equipment (UE), according to certain embodiments;FIGURE 10 illustrates an example network node, according to certain embodiments;FIGURE 11 illustrates a block diagram of a host, according to certain embodiments;FIGURE 12 illustrates a method performed by a wireless device, according to certain embodiments; andFIGURE 13 illustrates a method performed by a source network node, according to certain embodiments.DETAILED DESCRIPTION

[0046] As described above, certain challenges currently exist with signaling for on-demand synchronization signal block (SSB). On-demand SSB based on user equipment (UE) request, such as uplink wakeup signaling to enable SSB transmission on SCells, may lead to unnecessary overhead and complexity (e.g., define the wake-up request / procedure, etc.). Thedetails of how to efficiently communicate the presence / absence / triggering of on-demand SSBs to the UE and associated UE behavior is lacking in existing technology, particularly those based on gNB indication. Thus, it is beneficial to have detailed solutions on enabling on-demand SSBs without explicit UE request, such as UE wakeup signaling.

[0047] Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include signaling details for on-demand SSB operation, particularly different options for SSB assumption for an SCell based indications such as SCell activation / deactivation signaling, SCell activated / deactivated status, based on SSB indication bit along with SCell activation / deactivation, or based on SSB indication bit along with SCell activated / deactivated status.

[0048] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0049] A user equipment (UE) may be configured with at least two cells. One of the cells may be a primary cell or primary serving cell (PCell). One or more of the other cells may be a secondary cell(s) or secondary serving cell(s) (SCell(s)). The UE may assume that the primary cell is always activated. The SCell for the UE may be activated and deactivated on an as needed basis. For example, when there is data to be scheduled to / from a UE, a gNB may activate one or more SCell(s) (e.g., to reduce latency, increase data rate) in addition to the PCell to carry the traffic. When there is no / less data to be transmitted to / received from the UE, the gNB may deactivate one or more SCells to reduce UE energy consumption.

[0050] A UE may receive SCell configuration information via higher layers such as Radio Resource Control (RRC). The UE can receive SCell activation / deactivation message via SCell activation / deactivation medium access control (MAC) command control element (CE) or via layer one (LI) signaling or via higher layer signaling (direct SCell activation). In addition to activation / deactivation message for SCells, the UE may also receive information about one or two tracking reference signal (TRS) bursts that may help for faster SCell activation through an enhanced SCell activation / deactivation MAC command CE.

[0051] At least the following cases can be considered for enabling on-demand SSB:• Case 1: Cell operation is solely based on on-demand SSB• Case 2: Cell operation based on on-demand SSB along with periodic SSB

[0052] Some embodiments regarding indication of on-demand SSB are described next.

[0053] A UE may be configured with a first SSB burst configuration for an SCell. An SSB burst configuration may include one or more of a bitmap indicating SSB positions within the burst and periodicity of SSB. Each SSB within an SSB burst may have an index. The UE may be configured to receive an SCell activation / deactivation message (e.g., via a MAC CE). If the message indicates activation of an SCell, the UE can start receiving SSBs associated with the first SSB burst configuration for the SCell and / or the UE can assume SSBs associated with the first SSB burst configuration for the SCell are transmitted. In certain embodiments, before receiving an indication / message that the SCell is activated, the UE may not assume transmission of SSBs for the SCell unless previously indicated (e.g., if gNB indicated previously that SSBs are transmitted explicitly or implicitly).

[0054] There are multiple cases for on-demand SSBs (or alternately referred to as triggerable SSBs) for SCell activation / deactivation.

[0055] In an embodiment, the UE may be configured with a higher layer (e.g., RRC) indication that a SCell is operated using on-demand SSB operation. Based on the indication the UE may receive SSBs associated with a first SSB burst configuration (in short ‘first-config-SSBs’) using one or more of the following approaches.

[0056] In an approach (A0), the UE configured with the higher layer indication determines that first-config-SSBs are absent when SCell is deactivated (e.g., via legacy SCell activation / deactivation MAC CE or upon expiration of a SCell deactivation timer) and that first-config-SSBs are present when the SCell is activated (e.g., via legacy SCell activation / deactivation MAC CE or via direct SCell activation indication included during SCell addition).

[0057] In an approach (Al), the UE configured with the higher layer indication determines that first-config-SSBs are present when the SCell is activated / deactivated using a legacy mechanism (e.g., via legacy SCell activation / deactivation MAC CE or upon expiration of a SCell deactivation timer) and first-config-SSBs are absent when an additional indication related to ‘first-config-SSBs’ is received. The additional indication related to ‘first-config- SSBs’ may be a LI or MAC CE based indication.

[0058] For example, the additional indication may be a MAC CE with bits indicating absence of first-config-SSBs for the SCell. In another example, the additional indication may be a MACCE with bits indicating SCell deactivation and also bits indicating absence of first-config-SSBs for the SCell. In another example, the additional indication may be a MAC CE with bits indicating either SCell activation or SCell deactivation and also bits indicating absence of first- config-SSBs for the SCell. In another example, the additional indication may be a physical downlink control channel (PDCCH) with downlink control information (DCI) contents indicating absence of first-config-SSBs for the SCell.

[0059] In an approach (A2), the UE configured with the higher layer indication determines that first-config-SSBs are absent when the SCell is deactivated using legacy mechanisms (e.g., via legacy SCell activation / deactivation MAC CE or upon expiration of a SCell deactivation timer) and that first-config-SSBs are present when an additional indication related to ‘first-config- SSBs’ is received. The additional indication related to ‘first-config-SSBs’ may be a LI or MAC CE based indication.

[0060] For example, the additional indication may be a MAC CE with bits indicating presence of first-config-SSBs for the SCell. In another example, the additional indication may be a MAC CE with bits indicating SCell activation / deactivation and also bits indicating presence of first- config-SSBs for the SCell. In another example, the additional indication may be a PDCCH with DCI contents indicating presence of first-config-SSBs for the SCell.

[0061] In an approach, the UE may be configured (e.g., via RRC) to determine the presence / absence of first-config-SSBs via one of Approach A0, Approach Al or Approach A2 described above.

[0062] In an approach, the UE configured with the higher layer indication determines that first- config-SSBs are present when the SCell is activated via direct SCell activation (direct SCell activation indication included during SCell addition), and for all other cases, the UE may follow the behavior described for one of Approach A0, Al or A2 above.

[0063] In an approach, the UE configured with the higher layer indication determines that first- config-SSBs are absent when the SCell is deactivated using SCell activation / deactivation MAC CE (e.g., legacy SCell activation / deactivation MAC CE, or a MAC CE with bits indicating SCell activation / deactivation and also bits indicating presence of first-config-SSBs for the SCell.) and that first-config-SSBs are present when the SCell is deactivated upon expiration of SCell deactivation timer.

[0064] A variant approach is described next.

[0065] A UE receives configuration for a SCell, where the configuration contains at least one type of SSB burst configuration (e.g., first SSB burst configuration only or first and second SSB burst configuration). The first SSB burst configuration indicates a number of SSB bursts (XI) for an SCell (e.g., for an on-demand SSB, as part of on-demand SSB configuration, etc.).

[0066] In some examples XI may be 1 or 2 or a configurable number by the network. In one example, an SSB burst configuration may include one or more of a bitmap indicating SSB positions within the burst and periodicity of SSB. In another example, an SSB burst configuration may include the number of SSB (e.g., L value as in TS 38.213) within the burst and periodicity of SSB burst. Each SSB within an SSB burst may have an index.

[0067] The second SSB burst configuration indicates one or more of a bitmap indicating SSB positions within the burst and periodicity of SSB. In another example, a second SSB burst configuration may include the number of SSB (e.g., L value as in TS 38.213) within the burst and periodicity of SSB burst. Each SSB within an SSB burst may have an index.

[0068] The UE may receive first SSB burst from the network node from a reference point (e.g., reference time). For example, the UE receives an SCell activation / deactivation command, and if the message indicates activation of the SCell, the UE may start receiving SSBs associated with the first SSB burst configuration for the SCell and / or the UE may assume SSBs associated with the first SSB burst configuration for the SCell are transmitted, for a number of SSB bursts (X) indicated for the SCell. In certain embodiments, before receiving an indication that the SCell is activated, the UE may not assume transmission of SSBs for the SCell unless previously indicated (e.g., if gNB indicated previously that SSBs are transmitted explicitly). The number of SSB bursts (X) may also be indicated via the SCell activation / deactivation CE or another L1 / L2 indication.

[0069] The reference point in one example is a slot / symbol of SCell activation, SCell activation / deactivation command reception or offset from the slot / symbol of the SCell activation / deactivation command reception.

[0070] The reference point in other examples may be based on slot / symbol of reception of a L1 / L2 signaling from the network node or an offset from the reception of L1 / L2 signaling from the network node indicating or triggering first SSB burst.

[0071] The UE may receive second SSB burst configured from a reference point (e.g., reference time). The reference point may be reception of SCell activation message. In certain embodiments, before receiving an SCell activation indication, the UE may not assumetransmission of SSBs for the SCell unless previously indicated (e.g., if gNB indicated previously that SSBs are transmitted explicitly). The reference point may be SCell addition.

[0072] The UE may receive an indication of the ending point (e.g., ending time) or nonavailability of first SSB burst from a from a reference point. The reference point may be after the XI number of SSB burst occasions as indicated in the configuration and / or reception of SCell deactivation command.

[0073] The UE may receive an indication of the ending point or non-availability for second SSB burst from a reference point. The reference point may be reception time of SCell deactivation command and / or reception time of SCell release.

[0074] In some embodiments, the received configuration (e.g., RRC configuration) from the network node further contains information about the SCell operation with first SSB burst only or combination second SSB burst and first SSB burst. In one example, it is explicitly indicated through a parameter in the configuration.

[0075] In another example, lack of second SSB burst configuration is implicitly considered as SCell operating with first SSB burst (e.g., on-demand SSB) alone. Some examples of explicit indication of on-demand SSB transmission are described next.

[0076] In some cases, the UE may determine that the UE may receive SSBs associated with a second SSB burst configuration (in short ‘second-config-SSBs’) instead of determining absence of first-config-SSBs in the approaches described above. The ‘second-config-SSBs’ may have a more infrequent periodicity compared to ‘first-config-SSBs’.

[0077] The approaches described above provide different trade-offs between additional signaling overhead and gNB / UE energy efficiency. Consider an example where there are two UEs, UE1 and UE2, communicating with a gNB. With approach Al the gNB may configure both UE1 and UE2 for on-demand SSB SCell operation. If the SCell for UE2 has to be deactivated, and if on-demand SSBs are required for UE1 but not UE2, the gNB can deactivate UE2 using legacy SCell deactivation MAC CE. If on-demand SSBs are not required for both UE1 and UE2, the gNB can deactivate UE2 using the additional indication. Such flexibility is not available with Approach A0. However, A0 avoids extra signaling associated with additional indication.

[0078] A UE may be configured with a first SSB burst configuration for an SCell. In an embodiment, the UE may assume that the SSBs associated with the first SSB burst configuration are transmitted based on an explicit indication via the SCellactivation / deactivation MAC CE (e.g., along with indication of activation of the SCell). In another embodiment, the UE may assume that the SSBs associated with the first SSB burst configuration are not transmitted based on an explicit indication via the SCell activation / deactivation MAC CE (e.g., along with indication of deactivation of the SCell). This may, for example, be supported using the MAC CE structure in FIGURE 6.

[0079] A UE may be configured with a first SSB burst configuration for an SCell. In an embodiment, the UE may assume that the SSBs associated with the first SSB burst configuration are transmitted upon activation of the SCell via SCell activation / deactivation MAC CE (e.g., along with indication of activation of the SCell). The UE may assume that the SSBs associated with the first SSB burst configuration are not transmitted based on an explicit indication via the SCell activation / deactivation MAC CE (e.g., along with indication of deactivation of the SCell). This enables preconfigured SSBs that are always present upon SCell activation, while they may be turned off or kept on upon SCell deactivation.

[0080] Some embodiments include preconfigured SSBs for an SCell with explicit indication of the SSBs transmission along with activation of the SCell, and explicit transmission / omission (or no transmission) of SSBs along with deactivation of the SCell. In certain embodiments, the legacy deactivation message may be sent to deactivate an SCell but still keep the SSB transmission ongoing. This may be helpful if there are several UEs (e.g., other legacy UEs). This may also help reactivate the SCell without needing new enhanced activation / deactivation MAC command CE to indicate transmission of SSBs again.

[0081] The UE may receive an SCell activation / deactivation command. The command includes at least one bitmap that indicates an activation / deactivation information for one or more SCells.

[0082] The activation / deactivation command may be received in a first slot (slot n) of a serving cell (e.g., a PCell or another already activated SCell). The UE may send an acknowledgement corresponding to reception of the activation / deactivation command in a second slot on another serving cell (e.g., of the PCell or another SCell), which may be in a reference slot n+k. The UE may assume that triggerable or on-demand SSB(s) for the SCell are transmitted starting from the first occasion of SSB that is no earlier than a third slot (n + k + Km), wherein Km is an offset value greater than 0. Km may typically be set to provide MAC CE processing time of about 3ms. The slot numbers may be with reference to the slots used for physical uplink controlchannel (PUCCH) transmissions (e.g., based on subcarrier spacing (SCS) of the cell on which the PUCCH corresponding to the acknowledgment is transmitted).

[0083] In an embodiment, upon reception of an activation command in slot n indicating activation of the SCell, the UE assumes that SSB burst(s) for the SCell are transmitted starting from the first occasion of an SSB with the lowest index within the burst that starts no earlier than an offset relative to the slot / symbol in which the activation command is received. This enables the UE to start receiving SSBs within full bursts instead of receiving partial SSB bursts. This also enables the gNB to flexibly schedule the activation / deactivation messages without having to unnecessarily transmit partial SSB bursts.

[0084] In yet another embodiment, upon reception of an activation / deactivation command in slot / symbol n indicating deactivation of the SCell, the UE may assume no transmission of the SSB burst for the SCell starting from the first occasion of an SSB within the burst the lowest index that occurs no earlier than an offset relative to the slot / symbol in which the command is received. An example is shown in FIGURE 4.

[0085] FIGURE 4 is a timing diagram illustrating omission / transmission / stoppage of SSB burst based on activation / deactivation commands, including aligning start / stop to the beginning of a complete SSB burst. The illustrated example shows an example where there are three SSBs in a SSB burst on an SCell (indexed 0, 1, 2). Before activation command is received for the SCell, the UE may assume no transmission of the SSBs on the SCell. Upon reception of an activation command, the UE applies a minimum offset, and finds the first occasion of SSB with the lowest index (e.g., index 0) within the SSB burst that starts no earlier than an offset (offsetl) relative to the slot / symbol in which the activation command is received. FIGURE 4 shows the shaded occasions where SSB bursts are transmitted on the cell and the UE may assume SSB presence in such bursts. Subsequently, the UE may receive a deactivation command and the UE may assume that SSBs are turned off starting the next burst that starts after an offset (offset2) relative to the slot / symbol in which the deactivation command is received.

[0086] Some further examples of SSB configurations are described next.

[0087] In certain embodiments, the SCell may be operated using an on-demand SSB and a periodic SSB transmissions.

[0088] In an embodiment, the UE is configured with a first SSB configuration for an SCell. The SSB configuration may include at least one or more of a bitmap indicating SSB positions in a burst and SSB periodicity. The UE may further be configured with second SSBconfiguration for the SCell. The SSB configuration may include at least one or more of a bitmap indicating SSB position in a burst and SSB periodicity. The SSBs associated with the first SSB configuration may be transmitted or omitted based on signaling such as MAC command / Ll signaling. The SSBs associated with the second SSB configuration may be always transmitted (e.g., assumed to be present upon SCell configuration, etc.).

[0089] In an embodiment, the first SSB configuration may be defined as an extension of the second SSB configuration (e.g., with a second periodicity, etc.).

[0090] In an embodiment, the bitmap indicating SSB positions in a burst is identical for both the first and second SSB configuration.

[0091] In an embodiment, the periodicity used for the first and second SSB configuration are distinct. The second periodicity (e.g., 160ms) may be a multiple of the first periodicity (20ms).

[0092] In an embodiment, the UE uses the first SSB configuration for determining SSB resources for PDSCH rate-matching when SSBs associated with the first SSB configurations indicated as transmitted. An example is shown in FIGURE 5.

[0093] FIGURE 5 is a timing diagram illustrating omission / transmission / stoppage of on- demand SSB burst based on activation / deactivation commands, including aligning start / stop to the beginning of a complete SSB burst, and transmission of periodic SSB. The illustrated example shows an example where there are three SSBs in a SSB burst(s) on an SCell. There are two SSB configurations for the SCell - a second SSB configuration with three SSBs in a SSB burst and a (second) periodicity. A first SSB configuration with three SSBs in a SSB burst and a (first) periodicity. Before activation command is received for the SCell, the UE may assume transmission of the SSBs on the SCell only according to the second SSB configuration. Upon reception of an activation command, the UE applies a minimum offset, and finds the first occasion of an SSB associated with the first SSB configuration with the lowest index within the SSB burst (e.g., index 0) that starts no earlier than an offset (offsetl) relative to the slot / symbol in which the activation command is received. FIGURE 5 shows the shaded occasions where SSB bursts according to the first SSB configuration are transmitted on the cell. Subsequently, the UE may receive a deactivation command and the UE may assume that SSBs according to the first SSB configuration are turned off starting at the next burst that starts after an offset (offset2) relative to the slot / symbol in which the deactivation command is received. The UE may use SSBs transmitted according to one or both of the first and second SSB configurations.

[0094] In an example, the first and second SSB configuration may be associated with the same SSB configuration, each one may be associated with a different periodicity (e.g., 160 ms and 20 ms, respectively).

[0095] In the above examples, instead of lowest index within the SSB burst, a reference index may also be used, wherein the reference index is fixed or indicated by higher layers.

[0096] An example enhanced SCell activation / deactivation MAC CE is shown in the below example. A bitmap is included in the MAC CE for SCell activation / deactivation and a bit of the bitmap to indicate the activation / deactivation of an SCell. A bitmap is included in the MAC CE and a bit of the bitmap to indicate the transmission / absence of SSB / SSB burst associated with an SCell. Below has further description of the MAC CE contents.• Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell with SCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with SCelllndex i shall be activated and that a Sj field is included for the SCell. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated and that a Sj field is included for this SCell;• Sj: If Sj is set to a first (e.g. non-zero) value, it indicates the SSB / SSB burst associated with cell j is activated. If TRS IDj is set to second (zero), it indicates that SSB / SSB burst is not activated for the corresponding SCell;• R: Reserved bit, set to 0.

[0097] FIGURE 6 illustrates enhanced SCell activation / deactivation MAC CE with SSB transmission / absence indication.

[0098] In some embodiments, the MAC CE may include an indicator to indicate which particular SSBs within an SSB burst of a SCell are transmitted.

[0099] In an embodiment, MAC CE may trigger on-demand SSB and also TRS that may be used for fast SCell activation (e.g., one or two bursts of TRS).

[0100] In certain embodiments, the command includes at least one bitmap that indicates an activation / deactivation information for one or more SCells as well as indication of additional reference signals such a TRS for an activated SCell, as well as presence / absence of SSB / SSB burst associated with an SCell. An example is shown below.• Ci: If there is an SCell configured for the MAC entity with SCelllndex i as specified in TS 38.331, this field indicates the activation / deactivation status of the SCell withSCelllndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to 1 to indicate that the SCell with SCelllndex i shall be activated and that a TRS IDj field is included for the SCell. The Ci field is set to 0 to indicate that the SCell with SCelllndex i shall be deactivated and that no TRS ID field is included for this SCell;• TRS IDj: If TRS IDj is set to a non-zero value, it indicates the corresponding TRS address by scellActivationRS-Id as specified in TS 38.331 is activated. If TRS IDj is set to zero, it indicates that no TRS is used for the corresponding SCell;• R: Reserved bit, set to 0.• Sj: If Sj is set to a first (e.g. non-zero) value, it indicates the SSB / SSB burst associated with cell j is activated. If TRS IDj is set to second (zero), it indicates that SSB / SSB burst is not activated for the corresponding SCell;

[0101] FIGURE 7 illustrates enhanced SCell activation / deactivation MAC CE with SSB transmission / absence indication and triggering TRS for one or more SCells.

[0102] While the MAC CEs in the examples above are shown using a single octet (up to 7 SCells), the same principles apply also to MAC CEs with additional octets (such as four octets, or up to 32 SCells).

[0103] Some embodiments include activation / deactivation and explicit bitmap of SSB presence / absence. In an embodiment, the UE receives an SCell activation / deactivation command. The command includes at least one bitmap that indicates an activation / deactivation information for one or more SCells and an explicit indication of the transmission / no transmission of triggerable or on-demand SSBs for one or more SCells.

[0104] In an embodiment, the UE receives an SCell activation / deactivation command. The command includes at least one bitmap and at least a bit of the bitmap indicates that an SCell is deactivated, and the command further includes at least a second field and the second field indicates omission / transmission of triggerable or on-demand SSBs for that SCell. This enables a gNB to deactivate an SCell using legacy MAC command CE without having to turn off the triggerable or on-demand SSBs that are being transmitted (e.g., if there are legacy UEs, SSBs may be kept on). Later, the gNB may send explicit MAC CE to turn off transmission of triggerable or on-demand SSBs.

[0105] In an embodiment, the UE receives an SCell activation / deactivation command. The command includes at least one bitmap and at least a bit of the bitmap indicates that an SCell is activated, and the command further includes at least a second field and the second fieldindicates transmission of triggerable or on-demand SSBs for that SCell. The UE subsequently receives a second SCell activation / deactivation command that indicates the SCell is deactivated. The second command can be a legacy SCell activation / deactivation MAC command.

[0106] Regarding TRS assumption, the SSBs are quasi-colocated (QCL) source for TRS. Thus, unless SSBs are received, a UE may not be able to receive or process TRS signaling from the gNB. Thus, a gNB may be able to turn off TRS to save energy and start transmitting TRS upon transmission of on-demand SSBs from the SCells. In an embodiment, the UE may assume presence of TRS in a TRS occasion only when at least one SSB occasion associated with the TRS occasion has SSB present.

[0107] Some embodiments include further signaling details for on-demand SSB indication. Some further details of on-demand SSB indication are disclosed herein. The tables in the various options below show the example UE behavior for an SCell with respective SSB assumption based on one or more of SSB bit(s) (e.g., within a MAC CE), SCell activation / deactivation bit / field (e.g., within a MAC CE) and SCell activated / deactivated state. In the description below, while SSB is used, it is understood that the same principle applies to SSB burst(s) where one or more SSBs may be transmitted, e.g., in different beams.Option 1

[0108] In this example, the UE behavior with respect to the assumption on SSB on an SCell is determined based on a joint indication of SCell activation / deactivation bit and SSB bit / field.

[0109] The UE may be configured with an SSB with a first configuration and an SSB with a second configuration. In another example, the UE may be configured with an SSB with a first periodicity and an SSB with a second periodicity. For example, the two periodicities Pl, P2 may be chosen from existing periodicity values {5, 10, 20, 40, 60, 80, 160}ms for SSB.

[0110] When the UE determines that an SCell activation / deactivation bit / field associated with an SCell is set to a first value (e.g., 0) and an SSB bit / field associated with the SCell is set to another first value (e.g., 0), the UE may assume that the SCell is deactivated and that SSB may not be present / is not present.[OHl] When the UE determines that an SCell activation / deactivation bit / field is set to a first value (e.g., 0) and an SSB bit / field associated with an SCell is set to another second value (e.g., 1), the UE may assume that the SCell is deactivated and that SSB is present with a predetermined SSB configuration (e.g., with first periodicity, existing periodicity). For example,the pre-determined SSB configuration may be configured by RRC, or may be determined as the current SSB configuration that UE is assuming (e.g., based on prior indication).

[0112] When the UE determines that an SCell activation / deactivation bit / field is set to a second value (e.g., 1) and an SSB bit / field associated with an SCell is set to another first value (e.g., 0), the UE may assume that the SCell is activated and SSB with a first configuration is present.

[0113] When the UE determines that an SCell activation / deactivation bit / field is set to a second value (e.g., 1) and an SSB bit / field associated with an SCell is set to another second value (e.g., 1), the UE may assume that the SCell is activated and SSB with a second configuration is present.

[0114] The table below shows an example illustration of how the UE behavior may be determined. In UE behavior 1, the SSB periodicities are switched. In UE behavior 2, the SSB configurations are switched. In the table, the ‘SCell act / deact bit’ may be a bit corresponding to an SCell in SCell activation / deactivation MAC CE. The ‘SSB bit’ may be a bit corresponding to that SCell indication SSB assumption (e.g., one of S1-S7 shown in FIGURE 6 or FIGURE 7). The UE generally should assume that SSBs on the SCell are present when the SCell is activated. When the SCell act / deact bit indicates 1, the interpretation of SSB bit may be SSB presence according first / second config as opposed to on / off of SSB because the off state for SSB is not needed in this case. This approach provides flexible SSB adaptation during SCell activation / deactivation with low overhead (i.e., only one extra bit for SSB indication).Option 2

[0115] In this example, the UE behavior with respect to the assumption on SSB on an SCell, and SCell activation / deactivation indication is determined based on a joint indication of SCell activation / deactivation bit / field and SSB bit / field. In an example, the SSB field may have more than one bit, for example as shown in the table below, there may be two bits for SSB. In the table, the ‘SCell act / deact bit’ may be a bit corresponding to an SCell in SCell activation / deactivation MAC CE. The ‘SSB bitO’ and ‘SSB bitl ’, may be bits corresponding to that SCell indicating SSB assumption. Having two SSB bits provides more flexibility while slightly increasing overhead.

[0116] The UE may determine the assumption on SSB on the SCell based on the content of the SSB bit / field and based on the content of the SCell activation / deactivation bit / field.

[0117] The UE may be configured with an SSB with a first configuration and one or more SSB configurations (e.g., a second configuration, a second and third configurations). The UE may be configured with an SSB with a first periodicity, an SSB with a second periodicity and an SSB with a third periodicity. For example, the periodicities Pl, P2,P3 may be chosen from existing periodicity values {5, 10, 20, 40, 60, 80, 160}ms for SSB. In some examples, the SSBs may also have an associated offset (e.g., in terms of slots / subframes / ms) in reference to a time boundary (e.g., slot / subframe / system frame number (SFN)).

[0118] When the UE determines that an SCell activation / deactivation bit / field associated with an SCell is set to a first value (e.g., 0) and an SSB bit / field associated with the SCell is set to another first value (e.g., 10, i.e. bitO = 1, bitl = 0), the UE may assume that the SCell is deactivated and that SSB with a first pre-determined configuration is present. In such cases, a UE may detect legacy SCell activation / deactivation message which may simply activate / deactivate an SCell without updating the SSB assumption at the UE.

[0119] When the UE determines that an SCell activation / deactivation bit / field associated with an SCell is set to a second value (e.g., 1) and an SSB bit / field associated with the SCell is set to another first value (e.g., 10, i.e. bitO = 1, bitl = 0), the UE may assume that the SCell is activated and that SSB with a first pre-determined configuration is present.

[0120] Offset xl and offset x2 may be preconfigured or provided by higher layers.Option 3

[0121] In some embodiments, the UE receives a new indication such as a SSB bit / field via LI signaling or MAC CE. The MAC CE with SSB bit / field may be separate from the MAC CE used to indicate SCell activation signaling. Example UE behavior for such cases is described below.

[0122] The UE determines if the SCell is activated or not activated (e.g., based on SCell activation / deactivation MAC CE or SCell deactivation timer). Depending on the SCell state (i.e., SCell is activated or not activated), the UE may determine SSB reception as follows.

[0123] When the UE determines that an SSB bit / field associated with an SCell is set to a first value (e.g., 0 ), when the SCell is activated, the UE may assume that the SSB is present with a first configuration or first periodicity. When the SCell is deactivated, the UE may assume that the SSB is not present.

[0124] When the UE determines that an SSB bit / field associated with an SCell is set to a second value (e.g., 1), when the SCell is activated, the UE may assume that the SSB is present with a second configuration or second periodicity. When the SCell is deactivated, the UE may assume that SSB is present with a pre-determined configuration or periodicity.Option 3 a

[0125] In another example, the SCell activation / deactivation MAC CE may be used to indicate SSB assumption. Additionally, the UE may also receive a new indication such as a SSB bit / field via LI signaling or MAC CE. The MAC CE with SSB bit field may be separate from the MAC CE used to indicate SCell activation signaling.

[0126] When the UE determines that an SCell activation / deactivation bit / field associated with an SCell is set to a first value (e.g., 0 or indicating deactivation), the UE may assume that the SCell is deactivated. The UE assumption on SSB can be kept unchanged in this case (e.g., and SSB may / is not present).

[0127] When the UE determines that an SCell activation / deactivation bit / field associated with an SCell is set to a first value (e.g., 1 or indicating activation), the UE may assume that SSB with a first pre-determined configuration and / or a pre-determined periodicity is present. The pre-determined periodicity may be different than the periodicities associated with the new indication.

[0128] Additionally, depending on the SCell state the UE may determine SSB reception as follows. When the UE determines that an SSB bit / field associated with an SCell is set to a first value (e.g., 0 ), when the SCell is activated, the UE may assume that the SSB is present with a first configuration or first periodicity. When the SCell is deactivated, the UE may assume that the SSB is not present.

[0129] When the UE determines that an SSB bit / field associated with an SCell is set to a second value (e.g., 1), when the SCell is activated, the UE may assume that the SSB is present with a second configuration or second periodicity. When the SCell is deactivated, the UE may assume that SSB is present with a pre-determined configuration or periodicity.

[0130] An example is shown in the tables below. In the tables, the ‘SCell act / deact bit’ may be a bit corresponding to an SCell in SCell activation / deactivation MAC CE. ‘SSB bit’ may be a bit corresponding to an SCell in the new indication (i.e., SSB bit / field via LI signaling or MAC CE).5

[0131] In this example, P3 may be configured to be a more frequent periodicity compared to P1 / P2. So, when SCell is activated via SCell activation / deactivation MAC CE the more frequent P3 is assumed by the UE. The new indication (i.e., SSB bit / field via LI signaling or MAC CE) may then be used modify the SSB periodicity to one of Pl or P2 or turned off. In one specific example, P3=20ms, P2=20ms, Pl=160ms may be configured. In another example, P3=5ms, P 1=160ms and P2=20ms may be configured.

[0132] More generally, the UE may be configured with an SSB with a first configuration and one or more SSB configurations (e.g., a second configuration, a second and third configurations). The UE may be configured with an SSB with a first periodicity, an SSB with a second periodicity and an SSB with athird periodicity. For example, the periodicities Pl, P2, P3 may be chosen from existing periodicity values {5, 10, 20, 40, 60, 80, 160}ms for SSB. In some examples, the SSBs may also have an associated offset (e.g., in terms of slots / subframes / ms) in reference to a time boundary (e.g., slot / subframe / SFN).Option 4:

[0133] In one option, the UE behavior with respect to the assumption on SSB on an SCell is determined based on a first existing information element in the RRC configuration for deactivated state and a second information element for the activated state. In one example, the first information element is measCycleSCell in the MeasObjectNR. The second information element is ssb-periodicityServingCell. In some examples, values that the first information element and second information element take are legacy values or may be extended values (e.g., different than the legacy).

[0134] In one option, the UE behavior with respect to the assumption on SSB on an SCell is determined based on a first existing information element in the RRC configuration for deactivated state and a second information element for the activated state. In one example, the first information element is measCycleSCell in the MeasObjectNR. The second information element is ssb-periodicityServingCell. In some examples, values that a first information element and second information element take may be legacy values. In another example, thevalues may be new values that are different than the legacy values (e.g., 320ms, etc.). The trigger for change of assumption on SSB periodicity is SCell activation / deactivation command.

[0135] FIGURE 8 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0136] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0137] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0138] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0139] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

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

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

[0142] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0143] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0144] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and thecore network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0145] FIGURE 9 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0147] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 9. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0148] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0149] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

[0151] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

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

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

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

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

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

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

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

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

[0160] FIGURE 10 shows anetwork node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0161] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

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

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

[0164] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0165] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0166] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0167] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0168] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still otherembodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

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

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

[0171] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0172] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may includeuser interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

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

[0174] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 3 and 4, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

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

[0176] FIGURE 12 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 12 may be performed by UE 200 described with respect to FIGURE 9. The wireless device is capable of SSB reception on a SCell.

[0177] The method begins at step 1212, where the wireless device (e.g., UE 200) determines one of an activation state or deactivation state of the SCell. In particular embodiments, determining the activation state or deactivation state of the SCell is based on receiving an SCell activation or deactivation command (e.g., MAC CE). In particular embodiments, determining the activation state or deactivation state of the SCell is based on a SCell deactivation timer.

[0178] In particular embodiments, the wireless device may determine the activation state or deactivation state according to any of the embodiments and examples described herein.

[0179] At step 1214, the wireless device receives a SSB indication for the SCell.

[0180] In particular embodiments, the SSB indication may be received separately from the SCell activation or deactivation command.

[0181] In particular embodiments, the SSB indication may comprise any of the SSB indications / bit / fields described with respect to the embodiments and examples described herein.

[0182] At step 1216, the wireless device determines a SSB configuration for the SCell based on the determined one of the activation state or deactivation state and the SSB indication.

[0183] In particular embodiments, determining the SSB configuration comprises determining one or more of: a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

[0184] In particular embodiments, when the SSB indication indicates a first value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined first SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless device does not monitor for SSB in the SCell. When the SSB indication indicates a second value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined second SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless monitors for SSB in the SCell according to a determined third SSB configuration.

[0185] In particular embodiments, after determining the activation state or deactivation state of the SCell (e.g., step 1412) and before receiving the SSB indication (e.g., step 1414), whenthe SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined fourth SSB configuration.

[0186] In particular embodiments, the third SSB configuration comprises a preconfigured or default configuration. The fourth SSB configuration may also comprise a preconfigured or default configuration.

[0187] In particular embodiments, a periodicity of the fourth SSB configuration is greater than a periodicity of any of the first SSB configuration, second SSB configuration, and third SSB configuration. Aperiodicity of the third SSB configuration may be less than a periodicity of any of the first SSB configuration and second SSB configuration.

[0188] In particular embodiments, the wireless device determines the SSB configurations according to any of the embodiments and examples described herein.

[0189] At step 1218, the wireless device may determine quasi-colocation information for a physical channel on the SCell based on the determined SSB configuration.

[0190] Modifications, additions, or omissions may be made to method 1200 of FIGURE 12. Additionally, one or more steps in the method of FIGURE 12 may be performed in parallel or in any suitable order.

[0191] FIGURE 13 is a flowchart illustrating an example method in anetwork node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by network node 300 described with respect to FIGURE 10. The network node is capable of SSB transmission on an SCell.

[0192] The method begins at step 1312, where the network node (e.g., network node 300) transmits to a wireless device a SCell activation or deactivation command (e.g., MAC CE).

[0193] At step 1314, the network node transmits to the wireless device a SSB indication for the SCell. In particular embodiments, the SSB indication is transmitted separately from the SCell activation or deactivation command.

[0194] SSB is transmitted in the SCell based on a determined SSB configuration for the SCell based on a determined one of the activation state or deactivation state and the SSB indication.

[0195] In particular embodiments, the determined SSB configuration comprises one or more of: a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

[0196] In particular embodiments, when the SSB indication indicates a first value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a first SSBconfiguration; when the SCell is in the deactivated state, the SSB is not transmitted in the SCell. When the SSB indication indicates a second value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a second SSB configuration; and when the SCell is in the deactivated state, the SSB is transmitted in the SCell according to a third SSB configuration.

[0197] In particular embodiments, after transmitting the SCell activation or deactivation command and before transmitting the SSB indication, when the SCell is in the activated state, the SSB is transmitted in the SCell according to a fourth SSB configuration.

[0198] In particular embodiments, SSB is transmitted in the SCell according to any of the embodiments and examples described herein.

[0199] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order.

[0200] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0201] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0202] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0203] Some example embodiments are described below.1. A method performed by a wireless device for on-demand synchronization signal block (SSB) reception, the method comprising:- receiving a first indication of an activation or deactivation command for a secondary cell (SCell) and a second indication of an on-demand SSB configuration for the SCell; and- monitoring for on-demand SSB in the SCell based on the received first and second indications.2. The method of embodiment 1, wherein the first indication and the second indication comprise any of the indications described with respect to option 1 above..3. The method of embodiment 1, wherein the first indication and the second indication comprise any of the indications described with respect to option 2 above..4. The method of embodiment 1, wherein the first indication and the second indication comprise any of the indications described with respect to option 3 above..5. The method of embodiment 1, wherein the first indication and the second indication comprise any of the indications described with respect to option 3a above..6. The method of embodiment 1, wherein the first indication and the second indication comprise any of the indications described with respect to option 4 above..7. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.8. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.9. The method of any of the previous two embodiments, further comprising:providing user data; and forwarding the user data to a host computer via the transmission to the base station.10. A method performed by a base station for on-demand synchronization signal block (SSB) transmission, the method comprising:- transmitting to a wireless device a first indication of an activation or deactivation command for a secondary cell (SCell) and a second indication of an on-demand SSB configuration for the SCell; and- transmitting on-demand SSB in the SCell based on the received first and second indications.11. The method of embodiment 10, wherein the first indication and the second indication comprise any of the indications described with respect to option 1 above..12. The method of embodiment 10, wherein the first indication and the second indication comprise any of the indications described with respect to option 2 above..13. The method of embodiment 10, wherein the first indication and the second indication comprise any of the indications described with respect to option 3 above..14. The method of embodiment 10, wherein the first indication and the second indication comprise any of the indications described with respect to option 3a above..15. The method of embodiment 10, wherein the first indication and the second indication comprise any of the indications described with respect to option 4 above..16. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions described above.17. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.18. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.19. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.20. A base station comprising:- processing circuitry configured to perform any of the steps of any of the Group B embodiments;- power supply circuitry configured to supply power to the wireless device.21. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;- an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE.22. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward the user data to a cellularnetwork for transmission to a user equipment (UE),- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments. The communication system of the pervious embodiment further including the base station. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE comprises processing circuitry configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),- wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE. The communication system of the previous 2 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, providing user data; and- at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. A communication system including a host computer comprising:- communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,- wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.36. The communication system of the previous embodiment, further including the UE.37. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.38. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.39. The communication system of the previous 4 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and- the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.40. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.41. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.42. The method of the previous 2 embodiments, further comprising:- at the UE, executing a client application, thereby providing the user data to be transmitted; and- at the host computer, executing a host application associated with the clientapplication.43. The method of the previous 3 embodiments, further comprising:- at the UE, executing a client application; and- at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,- wherein the user data to be transmitted is provided by the client application in response to the input data.44. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.45. The communication system of the previous embodiment further including the base station.46. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.47. The communication system of the previous 3 embodiments, wherein:- the processing circuitry of the host computer is configured to execute a host application;- the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.48. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:- at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Claims

CLAIMS:

1. A method performed by a wireless device for synchronization signal block, SSB, reception on a secondary cell, SCell, the method comprising: determining (1212) one of an activation state or deactivation state of the SCell; receiving (1214) a SSB indication for the SCell; determining (1216) a SSB configuration for the SCell based on the determined one of the activation state or deactivation state and the SSB indication; and performing (1218) one or more SSB operations according to the determined SSB configuration.

2. The method of claim 1, wherein determining the activation state or deactivation state of the SCell is based on receiving an SCell activation or deactivation command.

3. The method of claim 2, wherein the SCell activation or deactivation command is received separately from the SSB indication.

4. The method of claim 1, wherein determining the activation state or deactivation state of the SCell is based on a SCell deactivation timer.

5. The method of any one of claims 1-4, wherein determining the SSB configuration comprises determining one or more of: a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

6. The method of any one of claims 1-5, wherein: the wireless device monitors for SSB in the SCell according to a determined first SSB configuration when the SCell is determined to be in the activated state; and the wireless device does not monitor for SSB in the SCell when the SCell is determined to be in the deactivated state.

7. The method of any one of claims 1-6, wherein: when the SSB indication indicates a first value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined first SSB configuration; when the SCell is determined to be in the deactivated state, the wireless device does not monitor for SSB in the SCell; when the SSB indication indicates a second value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined second SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless monitors for SSB in the SCell according to a determined third SSB configuration.

8. The method of claim 7, wherein after determining the activation state or deactivation state of the SCell and before receiving the SSB indication, when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined fourth SSB configuration.

9. The method of any one of claims 7-8, wherein the third SSB configuration comprises a preconfigured or default configuration.

10. The method of claim 8, wherein the fourth SSB configuration comprises a preconfigured or default configuration.

11. The method of claim 8, wherein a periodicity of the fourth SSB configuration is greater than a periodicity of any of the first SSB configuration, second SSB configuration, and third SSB configuration.

12. The method of any one of claims 7-11, wherein a periodicity of the third SSB configuration is less than a periodicity of any of the first SSB configuration and second SSB configuration.

13. The method of any one of claims 7-12, wherein the SSB according to the firstSSB configuration comprises an on-demand SSB configuration.

14. The method of any one of claims 1-13, further comprising determining (1420) quasi-colocation information for a physical channel or signal on the SCell based on the determined SSB configuration.

15. The method of any one of claims 1-14, , wherein the SSB operation comprises one or more of acquiring frame / slot timing, initial time / frequency synchronization, measurements, and as a quasi-colocation reference for channels or signals.

16. A wireless device (200) capable of synchronization signal block, SSB, reception on a secondary cell, SCell, the wireless device comprising processing circuitry (202) operable to: determine one of an activation state or deactivation state of the SCell; receive a SSB indication for the SCell; determine a SSB configuration for the SCell based on the determined one of the activation state or deactivation state and the SSB indication; and perform one or more SSB operations according to the determined SSB configuration.

17. The wireless device of claim 16, wherein the processing circuitry is operable to determine the activation state or deactivation state of the SCell based on receiving an SCell activation or deactivation command.

18. The wireless device of claim 17, wherein the processing circuitry receives the SCell activation or deactivation command separately from the SSB indication.

19. The wireless device of claim 16, wherein the processing circuitry is operable to determine the activation state or deactivation state of the SCell based on a SCell deactivation timer.

20. The wireless device of any one of claims 16-19, wherein the processing circuitry is operable to determine the SSB configuration by determining one or more of:a presence or absence of an SSB in the SCell; a periodicity of an SSB in the SCell; and a time offset of an SSB in the SCell.

21. The wireless device of any one of claims 1-5, wherein: the wireless device monitors for SSB in the SCell according to a determined first SSB configuration when the SCell is determined to be in the activated state; and the wireless device does not monitor for SSB in the SCell when the SCell is determined to be in the deactivated state.

22. The wireless device of any one of claims 16-21, wherein: when the SSB indication indicates a first value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined first SSB configuration; when the SCell is determined to be in the deactivated state, the wireless device does not monitor for SSB in the SCell; when the SSB indication indicates a second value: when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined second SSB configuration; and when the SCell is determined to be in the deactivated state, the wireless monitors for SSB in the SCell according to a determined third SSB configuration.

23. The wireless device of claim 22, wherein after the processing circuitry determines the activation state or deactivation state of the SCell and before the processing circuitry receives the SSB indication, when the SCell is determined to be in the activated state, the wireless device monitors for SSB in the SCell according to a determined fourth SSB configuration.

24. The wireless device of any one of claims 22-23, wherein the third SSB configuration comprises a preconfigured or default configuration.

25. The wireless device of claim 23, wherein the fourth SSB configurationcomprises a preconfigured or default configuration.

26. The wireless device of claim 23, wherein a periodicity of the fourth SSB configuration is greater than a periodicity of any of the first SSB configuration, second SSB configuration, and third SSB configuration.

27. The wireless device of any one of claims 22-26, wherein a periodicity of the third SSB configuration is less than a periodicity of any of the first SSB configuration and second SSB configuration.

28. The wireless device of any one of claims 22-27, wherein the SSB according to the first SSB configuration comprises an on-demand SSB configuration.

29. The wireless device of any one of claims 16-28, the processing circuitry further operable to determine quasi-colocation information for a physical channel or signal on the SCell based on the determined SSB configuration.

30. The wireless device of any one of claims 1-14, , wherein the SSB operation comprises one or more of acquiring frame / slot timing, initial time / frequency synchronization, measurements, and as a quasi-colocation reference for channels or signals.

31. A method performed by a network node for synchronization signal block, SSB, transmission on a secondary cell, SCell, the method comprising: transmitting (1312) to a wireless device a SCell activation or deactivation command; transmitting (1314) to the wireless device a SSB indication for the SCell; and wherein SSB is transmitted in the SCell based on a determined SSB configuration for the SCell based on a determined one of the activation state or deactivation state and the SSB indication.

32. The method of claim 31, wherein the SSB indication is transmitted separately from the SCell activation or deactivation command.

33. The method of any one of claims 31-32, wherein: when the SSB indication indicates a first value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a first SSB configuration; when the SCell is in the deactivated state, the SSB is not transmitted in the SCell; when the SSB indication indicates a second value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a second SSB configuration; and when the SCell is in the deactivated state, the SSB is transmitted in the SCell according to a third SSB configuration.

34. The method of claim 33, wherein after transmitting the SCell activation or deactivation command and before transmitting the SSB indication, when the SCell is in the activated state, the SSB is transmitted in the SCell according to a fourth SSB configuration.

35. The method of any one of claims 33-34, wherein the SSB according to the first SSB configuration comprises an on-demand SSB configuration.

36. A network node (300) capable of on-demand synchronization signal block, SSB, transmission on a secondary cell, SCell, the network node comprising processing circuitry (302) operable to: transmit to a wireless device (200) a SCell activation or deactivation command; transmit to the wireless device a SSB indication for the SCell; and wherein SSB is transmitted in the SCell based on a determined SSB configuration for the SCell based on a determined one of the activation state or deactivation state and the SSB indication.

37. The network node of claim 36, wherein the processing circuitry is operable to transmit the SSB indication separately from the SCell activation or deactivation command.

38. The network node of any one of claims 36-37, wherein:when the SSB indication indicates a first value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a first SSB configuration; when the SCell is in the deactivated state, the SSB is not transmitted in the SCell; when the SSB indication indicates a second value: when the SCell is in the activated state, the SSB is transmitted in the SCell according to a second SSB configuration; and when the SCell is in the deactivated state, the SSB is transmitted in the SCell according to a third SSB configuration.

39. The network node of claim 38, wherein after the processing circuitry transmits the SCell activation or deactivation command and before the processing circuitry transmits the SSB indication, when the SCell is in the activated state, the SSB is transmitted in the SCell according to a fourth SSB configuration.

40. The method of any one of claims 38-39, wherein the SSB according to the first SSB configuration comprises an on-demand SSB configuration.

Images