Downlink control information for joint resource control

Abstract

A method (400) performed by a user equipment, UE, (612) for configuration switching includes receiving (402) two or more configurations for at least a first signal. A DCI is received (404), from a network node (610), for resource control. The DCI includes at least a first configuration indicator for the first signal. The UE receives or transmits (406) the first signal based on the first configuration indicator, and the first signal is from a signal set including a Synchronization Signal Block, SSB, a paging DCI for paging occasion, PO, and a PRACH preamble for Random Access, RA.

Description

[0001] DOWNLINK CONTROL INFORMATION FOR JOINT RESOURCE CONTROL

[0002] TECHNICAL FIELD

[0003] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for Downlink Control Information (DCI) for Joint Resource Control.

[0004] BACKGROUND

[0005] In Release 15 (Rel-15) New Radio (NR), Synchronization Signal Block (SSB) configuration for a cell is cell-specific, static, and configuration parameters are provided in System Information Block- 1 (SIB1). The parameters include SSB period, actual number of SSBs transmitted per burst, etc.

[0006] Any changes to SSB configuration are signaled via System Information (SI) update short message in a paging DCI, whereby camping User Equipments (UEs) re-read the SIB1. Connected mode UEs may obtain the updated SSB configuration information via dedicated Radio Resource Control (RRC) signaling.

[0007] Paging Occasion (PO) Configuration

[0008] In Rel-15 NR, PO configuration for a UE in a cell is provided in the SIB1, in the PCCH- Config field. Any changes to PCCH-Config are signaled via SI update short message in a paging DCI, whereby camping UEs re-read the SIB1 for the cell. In addition to the Cell-specific paging configuration, some UE-specific paging configuration parameters such as Discontinuous Reception (DRX) period may be provided via dedicated RRC signaling prior to releasing the connected UE to idle / inactive state. Such configuration may be changed via RRC signaling when the UE returns to connected mode.

[0009] UEs that have moved outside their last connected cell or related paging / tracking area will use the PCCH-Config for paging monitoring.

[0010] RA Configuration In Rel-15 NR, cell access-related Random Access (RA) configuration is cell-specific, static, and configuration parameters are provided in the SIB1. The parameters include at least the Physical Random Access Channel (PRACH) occasion period, offset, and PRACH format, Random Access Response (RAR) Synchronization Signal (SS), etc. Any changes to SSB configuration are signaled via SI update short message in a paging DCI, whereby camping UEs re-read the SIB1.

[0011] Rel-15 PRACH occasions can only be configured periodically, with a single-level period value.

[0012] For non-access functionality in connected mode, e.g. Scheduling Request (SR) transmission or target cell connection in handover (HO), a UE may be configured with additional PRACH occasions that are not visible to other UEs in the Network (NW).

[0013] Signal Configuration Switching Using DCI Signaling

[0014] In NR, signaling mechanisms exist for indicating dynamic modification of configuration of some transmitted signals. For example, the UE may be provided multiple possible configurations, including all preconfigured parameter values, via one-time RRC signaling. To dynamically apply a specific configuration upon one or more UEs, the NW may transmit a DCI carrying an index value specifying one of the previously provided configurations. Configurations can, thus, be rapidly adapted, without undue signaling overhead and delay. The switching commands may be dedicated or group commands. Some examples of such adaptation are Physical Downlink Control Channel (PDCCH) search space switching in Release 17 (Rel-17), or Channel State Information-Reference Signal (CSI-RS) reporting configuration switching in Release 18 (Rel-18).

[0015] NR Enhancements for Common Signal Adaptation

[0016] In Release 19 (Rel-19), a need for introducing more flexible adaptation of SSB, PO, and RA configurations has been identified and, as a result, the following Work Item (WI) objectives have been defined as per 3 GPP RAN#102 meeting:

[0017] 1. Specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with Carrier Aggregation (CA), for both intra- / inter-band CA. [RAN1 / 2 / 3 / 4] • Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Secondary Cell (SCell) activation / deactivation signaling)

[0018] • Notel : On-demand SSB transmission can be used by UE for at least SCell time / frequency synchronization, Layer 1 (Ll) / Layer 3 (L3) measurements and SCell activation and is supported for Frequency Range 1 (FR1) and Frequency Range 2 (FR2) in non-shared spectrum.

[0019] 2. Study procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0020] • Triggering method by uplink wake-up-signal using an existing signal / channel.

[0021] • Wake-up-signal configuration provisioning to UE

[0022] Note: No modification of SSB will be discussed under this objective

[0023] • Information exchange between gNodeBs (gNBs) at least for the configuration of wake-up signal, if necessary.

[0024] • Checkpoint for normative work in RAN#105

[0025] 3. Specify adaptation of common signal / channel transmissions. [RAN1 / 2 / 3 / 4]

[0026] • Adaptation of SSB in time domain, e.g., adapting periodicity

[0027] • Adaptation of PRACH in time domain

[0028] • Study adaptation of PRACH in spatial domain, e.g., non-uniform PRACH resources per SSB, and specify if found beneficial.

[0029] This study is to be done in 2Q’2O24 only.

[0030] • Adaptation of paging occasions including confining the paging occasions in the time domain

[0031] Note: there shall be no paging latency increase

[0032] • Note: there shall be no negative impact to legacy UEs, unless significant benefits are shown

[0033] 4. Specify the corresponding core requirements, for the above features [RAN4], See, RP -234065, 3GPP TSG RAN Meeting #102, Edinburgh, Scotland, December 1 lth-15th, 2023; New WID: Enhancements of network energy savings for NR. There currently exist certain challenge(s), however. For example, the SSB, PO, and RA configurations and transmission are three individual frameworks established in Rel-15 that are generally independent of each other. Each are configurable without affecting configurations of the other components. DCI-based switching between multiple provided configurations has been specified such as, for example, for PDCCH search space configurations, but necessary details have not been developed for each of the above frameworks, to achieve dynamic adaptation.

[0034] In several of the above-described scenarios, additionally, switching between higher-load and lower-load-optimized operation, or between capacity-optimized and Network Energy Savings (NES)-optimized operation, preferably includes mode switching in two, or all three, of the mentioned frameworks. However, DCI signaling according to each framework to switch multiple mechanisms simultaneously may cause large additional PDCCH transmissions, blocking PDCCH resources for other functions like data transmissions or paging.

[0035] SUMMARY

[0036] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are provided for using a joint source control DCI for carrying configuration indications for two or more of the SSB, PO, and RA frameworks. According to certain embodiments, when a UE receives the joint source control DCI, the UE obtains multiple configurations in a single reception operation, whereby all frameworks that are relevant for a given operating scenario can be switched to their respective required states for a coordinated overall configuration.

[0037] According to certain embodiments, a method by a UE for configuration switching includes receiving two or more configurations for at least a first signal. The UE receives, from a network node, a DCI for resource control, and the DCI includes at least a first configuration indicator for the first signal. The UE receives or transmits the first signal based on the first configuration indicator. The first signal is from a signal set that includes an SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0038] According to certain embodiments, a UE for configuration switching is configured to receive two or more configurations for at least a first signal. The UE is configured to receive, from a network node, a DCI for resource control, and the DCI includes at least a first configuration indicator for the first signal. The UE is configured to receive or transmit the first signal based on the first configuration indicator. The first signal is from a signal set that includes an SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0039] According to certain embodiments, a method by a network node for configuration switching includes transmitting, to a UE, two or more configurations for at least a first signal. The network node transmits, to the UE, a DCI for resource control, and the DCI includes at least a first configuration indicator for the first signal. The network node receives or transmits the first signal based on the first configuration indicator, and the first signal is from a signal set that includes an SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0040] According to certain embodiments, a network node for configuration switching is configured to transmit, to a UE, two or more configurations for at least a first signal. The network node is configured to transmit, to the UE, a DCI for resource control, and the DCI includes at least a first configuration indicator for the first signal. The network node is configured to receive or transmit the first signal based on the first configuration indicator, and the first signal is from a signal set that includes an SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0041] Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enabling all frameworks (e.g., SSB, paging, and / or RA) that are relevant for a given operating scenario to be switched to their respective required states using a single DCI transmission. This minimizes PDCCH resource overhead and PDCCH blocking probability for the NW, improving capacity and reducing user scheduling latency.

[0042] As another example, certain embodiments may provide a technical advantage on the UE side of reducing the receiver processing effort and the overall switching latency for the UE. Thus, energy efficiency and upload speed (UPT) may be improved.

[0043] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

[0044] 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:

[0046] FIGURE 1 illustrates two configurations that a UE may switch between for optimization of energy savings and capacity, according to certain embodiments.

[0047] FIGURE 3 illustrates an example method by a network node for configuration switching, according to certain embodiments.

[0048] FIGURE 4 illustrates another example method by a UE for configuration switching, according to certain embodiments.

[0049] FIGURE 5 illustrates a method performed by a network node for configuration switching, according to certain embodiments.

[0050] FIGURE 6 illustrates an example communication system, according to certain embodiments.

[0051] FIGURE 7 illustrates an example UE, according to certain embodiments.

[0052] FIGURE 8 illustrates an example network node, according to certain embodiments; and

[0053] FIGURE 9 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments.

[0054] DETAILED DESCRIPTION

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

[0056] As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (I AB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self-Organizing Network (SON), positioning node (e.g. E- SMLC), etc. The terms network node and radio network node are used interchangeably herein.

[0057] Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

[0058] The term radio access technology (RAT) may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs.

[0059] The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0060] Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New RadioSecondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR- PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.

[0061] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, sub-slot, minislot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc.

[0062] As described above, in certain scenarios, switching between higher-load and lower-load- optimized operation, or between capacity-optimized and NES -optimized operation, preferably includes mode switching in two, or all three, of the SSB, PO, and RA frameworks. DCI signaling according to each framework to switch multiple mechanisms simultaneously may cause large additional PDCCH transmissions, blocking PDCCH resources for other functions like data transmissions or paging.

[0063] In Release 19 (Rel-19), a need has been identified for introducing more flexible adaptation of SSB, PO, and RA configurations, which resulted in certain Work Item (WI) objectives defined as per 3GPP RAN#102 meeting. See, RP-234065, 3GPP TSG RAN Meeting #102, Edinburgh, Scotland, December 1 lth-15th, 2023; New WID: Enhancements of network energy savings for NR. As part of the objectives defined there, to reduce gNB energy consumption at low-to medium load, several improvements can be proposed such as, for example:

[0064] • Consolidating SSB, POs, and RA transmission / reception operations into condensed time intervals and creating gNB sleep opportunities between these intervals.

[0065] • Avoiding always-on frequent SSB transmissions in all cells and allowing ON-demand provision of SSBs instead for reception preparation and measurements.

[0066] • Flexible adaptation of PO patterns between paging capacity-prioritized and NES- prioritized configuration.,

[0067] • Flexible adaptation of PRACH occasion between patterns supporting traditional access and paging and patterns suitable with NES -prioritized PO configurations.

[0068] Some scenarios where such adaptations are expected to be useful include: • Secondary Cell (Scell) quality measurements upon Scell configuration

[0069] • Synchronization to an Scell upon Scell activation

[0070] • Faster or improved-quality Radio Resource Management (RRM) measurements on serving or neighbor cells

[0071] • Adaptation of PO configurations based on paging load and gNB sleep opportunities

[0072] • Adaptation of PRACH occasions based on RA load and / or PO locations

[0073] • Etc.

[0074] Thus, there is a need for a signaling solution to dynamically switch the SSB, PO, and RA patterns, including two or more of them simultaneously, to provide sufficient adaptation flexibility without losing robustness or incurring undue PDCCH resource overhead.

[0075] Accordingly, methods and systems are disclosed herein for using a joint source control DCI for carrying configuration indications for two or more of the SSB, PO, and RA frameworks. When a UE receives the joint source control DCI, the UE obtains multiple configurations in a single reception operation, whereby all frameworks that are relevant for a given operating scenario can be switched to their respective required states for a coordinated overall configuration.

[0076] According to certain embodiments, for example, a method in a UE for configuration switching includes receiving, via RRC or SI broadcast, two or more configurations for at least a first signal. The UE receives a DCI for resource control, which includes at least a first configuration indicator for the first signal. The UE receives or transmits the first signal based on the first configuration indicator. The first signal is from a signal set comprising SSB, paging DCI [PO], and PRACH preamble [RA],

[0077] Joint Control for Two or More Signals

[0078] In a particular embodiment, the UE receives two or more configurations for a second signal from the signal set. The DCI is for joint resource control and comprises a second configuration indicator for the second signal, and the UE receives or transmits the second signal based on the second configuration indicator.

[0079] In another particular embodiment, the UE receives two or more configurations for a third signal from the signal set. The DCI comprises a third configuration indicator for the third signal, and the UE receives or transmits the third signal based on the third configuration indicator. DCI bit fields for individual signal ’s config indicators

[0080] In a particular embodiment, the size of the DCI is optionally configurable via, for example, SI broadcast or dedicated RRC signaling.

[0081] In a particular embodiment, the DCI comprises a first control bit field for the first configuration indicator, and a second control bit field for the second configuration indicator (and optionally a third control bit field for the third configuration indicator). In a further particular embodiment, the first and second (and third) control bit fields may be of different lengths, nl and n2 (and n3). In another particular embodiment, the position of the controlling bitfields within the DCI may be configurable. For example, the position of the controlling bitfields may be cellspecific (e.g., configured via broadcast system information) or UE-specific (e.g., configured via RRC signaling per UE or group of UEs).

[0082] In another particular embodiment, there may be control bits shared between indicators to save indicator overhead because there may be fixed patterns of joint configuration between signals. For example, a part of control bits is shared between indicators. In another example, two or more indicators have same control bits.

[0083] In a particular embodiment, the first configuration indicator indicates which of the up to 2nlfirst signal configurations should be used for first signal reception [same for 2nd, 3rdsignal].

[0084] In a particular embodiment, one of the first configuration indicator values [e.g., the value 2nl-l] is reserved to indicate that there is no change to the first signal configuration and the previously indicated configuration should be used for first signal reception [same for 2nd, 3rdsignal].

[0085] Dedicated or Group DCI

[0086] In a particular embodiment, the DCI is detected in a common search space or a UE-specific search space and the PDCCH is scrambled with a C-RNTI and / or a new RNTI.

[0087] In a particular embodiment, the DCI is detected in a common search space the PDCCH is scrambled with a group RNTI. In various particular embodiments:

[0088] • the group RNTI is a P-RNTI or a PEI -RNTI

[0089] • the group RNTI is a new resource control RNTI such as, for example, G-RNTI defined in the specifications • the group RNTI may be configured per UE, e.g. via RRC signaling. Note however that multiple UEs may be configured with the same configurable RNTI

[0090] Contains Serving Cell(s) Identifier

[0091] In a particular embodiment, the DCI contains field for identifying one or more serving cell(s) where the indicated configurations for the two or more signals are used.

[0092] DCI Indicates Configurations in a Subset of Configurations

[0093] In a particular embodiment, the DCI indicates configurations for the one or more signals from a subset of configurations. In a further particular embodiment, the subset of configurations is indicated to the UE via Medium Access Control Control Element (MAC CE). In another particular embodiment, the subset of configurations depends on the serving cell in which the DCI was transmitted, or the serving cell indicated in the DCI.

[0094] PDCCH Search Space

[0095] In a particular embodiment, the SS configured for monitoring the PDCCH carrying the DCI is a default common SS [SSO, same as paging etc.].

[0096] In a particular embodiment, the SS configured for monitoring the PDCCH carrying the DCI is a separate common SS [for resource control DCI only].

[0097] In a particular embodiment, the SS configured for monitoring the PDCCH carrying the DCI is a dedicated SS [for this UE only].

[0098] In a particular embodiment, the SS configured for monitoring the PDCCH carrying the DCI defines monitoring occasions “nearby” to the Pos.

[0099] Configuration Applicability Delay

[0100] In a particular embodiment, the application delay may be different for the different indicated resource configurations (e.g., SSB vs PRACH) in the DCI, even though the DCI for controlling said resources is received by the UE at same occasion.

[0101] Configuration Switching Delay In a particular embodiment, the UE need not monitor for PDCCH or parts thereof within a predetermined or configured delay from the reception of the DCI.

[0102] Relation to Legacy Configurations

[0103] In a particular embodiment, one of the possible first configuration indicator values [e.g., the value 0] indicates a configuration used by legacy UEs for the first signal reception [same for 2nd, 3rdsignal].

[0104] In a particular embodiment, the RRC configuration or the DCI comprises a bit field to indicate that the first signal occasions the UE must receive / monitor is a union of legacy occasions and occasions in the configuration indicated by the DCI [same for 2nd, 3rdsignal].

[0105] Duplication of Indications in SIBn (to enable robust mobility in idle)

[0106] In a particular embodiment, the most recently signaled state of at least one of the first, second, and third configuration indicators is broadcasted in a SIBn [to provide current config info when UE enters / camps in new cell].

[0107] In a further particular embodiment, the configuration info in SIBn may be changed without SI update signaling.

[0108] In a particular embodiment, the one or more configurations in a cell for at least one of the first, second, and third signals is provided in SIBn, allowing different cells to have different configuration options for a signal, although the same number of them.

[0109] Invalidity of G-DCI Outside the Releasing Cell (To Enable Robust Mobility in Idle)

[0110] In a particular embodiment, one or more configuration indicators in the G-DCI are not valid [i.e., are ignored by the UE] in cells or paging areas other than where the UE was most recently connected, potentially based on NW configuration.

[0111] Configuration Contents for the Three Signals (At Least New / Additional Items Compared to Legacy)

[0112] In a particular embodiment, the two or more configurations for SSB comprise one or more parameters from a legacy SSB configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling. In a further particular embodiment, the configurations are separately specified per serving cell (e.g., per Scell in case of carrier aggregation).

[0113] In a particular embodiment, the two or more configurations for paging DCI / PDCCH / PDSCH comprise one or more parameters from a legacy paging DCI / PDCCH / PDSCH configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0114] In a particular embodiment, the two or more configurations for PRACH / RA comprise one or more parameters from a legacy PRACH / RA configuration and additionally point to configurations in the specifications, or preconfigured by RRC via either broadcast or dedicated signaling

[0115] Joint Configuration and Update Procedure for Idle / inactive UEs

[0116] According to certain embodiments, the joint resource control mechanism may be used for UEs in idle / inactive mode.

[0117] In certain embodiments, the UE may receive two or more configurations for multiple common signal features: SSB, POs, and RACH (e.g., PRACH occasions). These may be provided via RRC signaling before the UE is released to idle / inactive, or via SI broadcast such as, for example, in SIB1 or in another SIBn. One of the two or more configurations per common signal feature may be an “off’ configuration, i.e., the common signal is not transmitted.

[0118] In certain embodiments, the two or more configurations for SSB may comprise one or more parameters from a legacy SSB configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling. The configurations may be separately specified per serving cell (e.g., per Scell in case of carrier aggregation).

[0119] In certain embodiments, the two or more configurations for paging DCI / PDCCH / PDSCH may comprise one or more parameters from a legacy paging DCI / PDCCH / PDSCH configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0120] In certain embodiments, the two or more configurations for PRACH / RA may comprise one or more parameters from a legacy PRACH / RA configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0121] In certain embodiments, the configurations are later activated / s witched using a joint resource control DCI (named, for example, G-DCI) that may contain separate configuration indicators for the different features. The UE may then receive / transmit signals corresponding to the different features using the configurations indicated respectively in the DCI.

[0122] In certain embodiments, the size and the field structure of the DCI may be configurable via, for example, SI broadcast or dedicated RRC signaling or fixed in the spec. The DCI may contain multiple fields, possibly of different sizes, one for each configuration indication for a feature. For example, two fields may be used to indicate that feature A has configuration 1 and feature B also has configuration 1, or that that feature A has configuration 1 but feature B has configuration 2. Alternatively, the DCI may contain one or more aggregate fields whose contents carry indication applying to multiple signals / features. For example, it may indicate that features A and B has configuration 1.

[0123] In certain embodiments, there may be control bits shared between indicators to save overhead because there may be fixed patterns of joint configuration between signals (e.g., both 1stand 2ndindicators are 1 bit and overlapped). Apparently, there are two configurations for 1st signal and 2nd signal. However, if 1st signal is set to config No.1, then 2nd signal has to be set as config No.l. Otherwise, NW doesn't benefit from this configuration. One example is if PO condensation is No.l config for the 1st signal, then PRACH which is the second signal should become denser or be provided more frequent, which is the No.1 config for the 2nd signal. Otherwise, there may be more PRACH failure. Apparently, sparse PRACH, which is No.2 config for the 2ndsignal, is unwise.

[0124] In certain embodiments, positions within the DCI for respective control of SSB / PRACH / PO may be defined or configured (e.g., via a parameter “positionlnDCI”). Some configurations such as, for example, SSB configurations may be controlled per Scell. The position of the controlling bitfields may be cell-specific (e.g., configured via broadcast system information) or UE-specific (e.g., configured via RRC signaling per UE or group of UEs).

[0125] In certain embodiments, one of the configuration indicator values (e.g., the value 2n-l, where n is the number of indicator bits) may be reserved to indicate that there is no change to the feature configuration and the previously indicated configuration should be used for first signal reception. One of the possible configuration indicator values (e.g., the value 0) may indicate a configuration used by legacy UEs for a signal reception or transmission. One of the possible indicator values may indicate that none of the configurations are used (i.e., that the common signal is not transmitted).

[0126] In certain embodiments, the RRC configuration or the DCI may also contain a bit field to indicate that signal occasions the UE must receive / monitor or that it can use for transmission is a union of legacy occasions and occasions in the configuration indicated by the DCI.

[0127] In certain embodiments, the RNTI may be configurable such as, for example, the UE may be provided with one or more RNTIs to monitor. The joint resource control DCI may be transmitted to a group of two or more idle / inactive UEs and the PDCCH is scrambled with a group RNTI. The group RNTI may be a P-RNTI or a PEI-RNTI, or a new resource control RNTI such as, for example, group RNTI (G-RNTI) defined in the specifications. The G-RNTI may also be configured per UE, e.g. via RRC signaling. Note however that multiple UEs may be configured with the same configurable G-RNTI. The search space for monitoring the PDCCH carrying the DCI may be a default common SS (SSO, same as paging etc.), or a separate common SS, reserved for the resource control DCI only. The SS may define monitoring occasions that are temporally close to the POs.

[0128] In certain embodiments, the joint resource control DCI may contain a carrier(s) indicator for identifying one or more serving cell(s) for which the indicated common signal configurations are applied. For example, PDCCH inPCell can adapt common signal transmissions in one or more configured Scells. In this way, the DCI may be sent in a serving cell other than serving cell for which the common signal configurations is updated.

[0129] Alternatively, each of the one or more configurations includes a serving cell identifier such that they can be indicated in a serving cell other than the serving cell in which the joint resource control DCI is received.

[0130] In certain embodiments, there may be a configuration applicability delay after DCI transmission. The delay may be different for the different indicated resource configurations (e.g., SSB vs PRACH) in the DCI, even though the DCI for controlling said resources is received by the UE at same occasion. In certain embodiments, there may also be a configuration switching delay during which the UE need not monitor for PDCCH or parts thereof within a predetermined or configured delay from the reception of the DCI.

[0131] In certain embodiments, the DCI may use a legacy DCI format (e.g., DCI Format 2 6) with additional fields and / or scrambled with new G-RNTI for indicating common signal features.

[0132] Joint Configuration and Update Procedure for Connected UEs

[0133] In certain embodiments, the joint resource control mechanism may also be used for UEs in connected mode. The usage is similar to idle / inactive mode UEs with some additions or differences.

[0134] In certain embodiments, the two or more configurations may be provided via RRC signaling.

[0135] In certain embodiments, a subset of the two or more configurations may be indicated (activated) using MAC CE signaling and / or different subsets are configured / activated per serving cell. The DCI can indicate only configurations in the activated subset. In this way, UE(s) can be configured with a larger set of configurations while limiting the DCI overhead by allowing NW to indicate only a subset of said larger set of configurations per PDCCH occasion.

[0136] In certain embodiments, the DCI may be transmitted only to the given UE, and the PDCCH may be scrambled with a C-RNTI.

[0137] In certain embodiments, the DCI may use a legacy DCI format (e.g., DCI Format 1 0 and / or DCI Format 1 3) with additional fields and / or scrambled with new G-RNTI for indicating common signal features.

[0138] In a particular embodiment, cell DTX-like signaling may be used. As an example, DCI 2 9, used for Rel-18 cell DTRX may be complemented with a resource control function.

[0139] As agreed in Rel-18, DCI format 2 9 is used for activating or de-activating the cell DTX and / or DRX configuration of one or multiple serving cells for one or more UEs, and / or for providing NES-mode indication of the primary cell for one or more UEs. The following information is transmitted by means of the DCI format 2 9 with CRC scrambled by cellDTRX- RNTI:

[0140] -block number 1 , block number 2, ... , block number N where the starting position of a block associated with a serving cell is determined by the parameter positionlnDCI-cellDTRX provided by higher layers for the UE.

[0141] If the UE is configured to monitor DCI 2 9 with CRC scrambled by cellDTRX-RNTI, one or more blocks are configured for the UE by higher layers, with the following fields defined for each block:

[0142] -Cell DTX / DRX indication - number of bits determined by the following:

[0143] -If higher layer parameter cellDTXDRX-Ll activation is configured

[0144] -2 bits as defined in Clause 11.5 of [5, TS38.213] if cellDTXDRXconfigType is configured to dtxdrx for the associated serving cell of the block, with the MSB corresponding to cell DTX configuration and the LSB corresponding to cell DRX configuration;

[0145] -1 bit as defined in Clause 11.5 of [5, TS38.213] if cellDTXDRXconfigType is configured to either dtx or drx for the associated serving cell of the block;

[0146] -0 bit otherwise.

[0147] -NES-mode indication - 1 bit indicating NES-specific CHO execution condition as defined in Clause 11.5 of [5, TS38.213], if the higher layer parameter nesEvent is configured and the associated serving cell of the block is primary cell; 0 bit otherwise.

[0148] According to certain embodiments, for resource control, one or more additional fields may be added in DCI 2 9:

[0149] -SSB Resource configuration indication - number of bits determined by the following:

[0150] -If higher layer parameter SSB-L1 activation (e.g. can be configured per Cell, including PCell, SCell) is configured

[0151] -X bits if at least two SSB configurations / periodicity (e.g. first SSB configuration with a first periodicity or burst structure, and a second SSB configuration with second periodicity or burst structure, or SSB with a first periodicity and second periodicity) for the associated serving cell of the block, -PO Resource configuration indication - number of bits determined by the following:

[0152] -If higher layer parameter PO- / . / activation (e.g. can be configured per Cell, including PCell, SCell) is configured

[0153] -X bits if at least two PO configurations / periodicity (e.g. first PO configuration with a first periodicity or burst structure, and a second PO configuration with second periodicity or burst structure, or PO with a first periodicity and second periodicity) for the associated serving cell, -RACH Resource configuration indication - number of bits determined by the following:

[0154] -If higher layer parameter activation (e.g. can be configured per

[0155] Cell, including PCell, SCell) is configured

[0156] -X bits if at least two RACH configurations / periodicity (e.g. first RACH configuration with a first periodicity or burst structure, and a second RACH configuration with second periodicity or burst structure, or RACH with a first periodicity and second periodicity) for the associated serving cell,

[0157] -0 bit otherwise.

[0158] Other formats or contents for the additional fields may be used, to indicate SSB, PO, and / or RACH resource control info.

[0159] In one embodiment, the DCI 2 9 may contain a field allowing joint indication of two or more of the resources to be activated.

[0160] The size of DCI format 2 9 may be indicated by the higher layer parameter sizeDCI-2-9.

[0161] The extensions described for DCI 2 9 may also be specified and transmitted in a DCI format other than 2 9.

[0162] The SS configured for monitoring the PDCCH carrying the DCI may be a common SS, or it may be a dedicated SS, configured only for the given UE.

[0163] Scenario Example: Switching Between Consolidated and Spread (Legacy) Paging Configurations Certain embodiments may be used, for example, for switching between energy savings- optimized and capacity-optimized. According to certain embodiments, the UE may be provided with two or more configurations. FIGURE 1 illustrates two configurations that a UE may switch between for optimization of energy savings and capacity, according to certain embodiments.

[0164] The upper portion of FIGURE 1 depicts first SSB, paging, and PRACH configurations that is possible to configure in legacy solutions, targeting energy-efficient operation. The SSB, PO, and PRACH occasions are condensed together to minimize the gNB awake time in the absence of other traffic activity. If no connected UEs are present, the gNB may be in deep sleep most of the 160 ms SSB period.

[0165] However, the paging and PRACH capacity may be low, and related NW access latency may be high, in case the paging and access needs increase such as, for example, due to a paging and / or PRACH storm when more UEs are present in the coverage area. To address the need for more paging resources, PRACH resources, and UE receiver preparation, UEs may be provided second configurations for SSB, paging, and PRACH occasions, as shown in the bottom portion of FIGURE 1. As described above, the first and second configurations may be provided, for example, via SIBn signaling or via RRC signaling.

[0166] Here, the second paging configuration provides additional Paging Frames (PFs), or Pos compared to the baseline first configuration to accommodate paging messages to more Ues, the second PRACH configuration provides additional access opportunities to paged Ues, and the second SSB configuration provides additional SSB transmissions before PRACH occasions.

[0167] According to certain embodiments, the UE may efficiently and dynamically switch between the two configuration sets. With a single DCI transmission, indicating the second configurations, the SSB, paging and PRACH configuration may be switched, for example, from the energy-efficient mode to increased capacity mode when paging and UE access needs increase. Similarly, another single DCI transmission indicating return to first configurations suffices to resume energy-efficient operation.

[0168] In some scenarios, not all of the three features are switched, or not all are switched from the respective first to respective second configurations, but different configuration combinations may be used. Also, more than two configurations per feature may be provided, and third, fourth, etc. configurations may be invoked.

[0169] Scenario Example: Idle / Inactive UEs Moving Between Cells Or Tracking Areas According to certain embodiments, the joint resource control may be applied also to UEs that moving between cells or paging areas in the network, outside the area where they were last connected and released to idle. Here, we assume that all cells in a paging area have configured functionally similar configuration sets (i.e., first configurations for energy saving, second configurations for capacity), although the configuration specifics may differ, and the granularity of rules for applying the second configuration is at the paging area level. Alternatively, the configuration may also be considered per cell and the rules apply at cell granularity.

[0170] In a particular embodiment, if the UE has obtained the second configurations and a DCI indication indicating the second configurations in its originating paging area, it continues to apply the second configuration while in this paging area. If the UE moves to a new paging area, it connects to the NW to inform about its paging area change. The NW may then provide a new set of configurations and / or configuration indications and the new paging area becomes the originating area.

[0171] In certain embodiments, the second configurations may differ from the first embodiments in that some occasions present in the first embodiments are not present in the second embodiments. It is then important to maintain UE / NW alignment regarding which occasions may be used at a given time.

[0172] In a particular embodiment, the indicating DCIs are transmitted simultaneously in all cells in a paging area and indicate the same (first / second) configurations so regardless of which cell the UE is in it will receive the current configuration status and alignment is maintained.

[0173] In a particular embodiment, the most recent DCI indication state for one or more features (SSB, PO, RACH configuration) is reflected in a field in SIBn (e.g., SIB1) of the cell. A UE entering a cell may check the indication state in SIBn and apply the appropriate configurations. This removes the indeterminism whether the UE has seen the most recent DCI signaling in the cell.

[0174] In a particular embodiment, any DCI signaling outside the originating cell, or the originating paging area is not considered by the UE, and the UE always uses SSB, PO, and / or PRACH occasions according to the first configurations.

[0175] In certain embodiments, the second configurations only add SSB, paging, or PRACH occasions compared to the first configurations. No occasions are removed. In that case, the switching signaling does not incur alignment robustness issues, and the UE may always use the first configurations and use the second configurations only when it has explicitly received DCI signaling indicating the second configurations.

[0176] FIGURE 2 illustrates an example method 200 by a UE for configuration switching, according to certain embodiments. In the illustrated embodiment, the method includes at least one of a first receiving step at 202, a second receiving step at 204, and a third receiving step or a first transmitting step at 206. For example, at step 202, the UE may receive two or more configurations for at least a first signal. At step 204, for example, the UE may receive, from a network node, a DCI for resource control. The DCI includes at least a first configuration indicator for the first signal. At step 206, the UE may receive or transmit the first signal based on the first configuration indicator. The first signal is from a signal set comprising: a SSB, a paging DCI for PO, and a PRACH preamble for RA. Thus, the first signal may comprise at least one of a SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0177] FIGURE 3 illustrates an example method 300 by a network node for configuration switching, according to certain embodiments. In the illustrated embodiment, the method includes at least one of a first transmitting step at 302, a second transmitting step at 304, and a third transmitting step or a first receiving step at 306. For example, at step 302, the network node may transmit, to a UE, two or more configurations for at least a first signal. At step 304, for example, the network node may transmit, to the UE, a DCI for resource control. The DCI includes at least a first configuration indicator for the first signal. At step 306, the network node may transmit or receive the first signal based on the first configuration indicator. The first signal is from a signal set comprising: a SSB, a paging DCI for PO, and a PRACH preamble for RA. Thus, the first signal may comprise at least one of a SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0178] FIGURE 4 illustrates another example method 400 by a UE for configuration switching, according to certain embodiments. In the illustrated embodiment, the method begins at step 402 when the UE receives two or more configurations for at least a first signal. At step 404, the UE receives, from a network node, a DCI for resource control, and the DCI includes at least a first configuration indicator for the first signal. At step 406, the UE receives or transmits the first signal based on the first configuration indicator, and the first signal is from a signal set including a SSB, a paging DCI for PO and a PRACH preamble for RA.

[0179] In a particular embodiment, the two or more configurations are received via RRC or SI broadcast from the network node. In a particular embodiment, the DCI is for joint resource control and includes a second configuration indicator for a second signal from the signal set. The UE receives two or more configurations for the second signal from the signal set and then receives or transmits the second signal based on the second configuration indicator.

[0180] In a particular embodiment, the DCI includes a third configuration indicator for a third signal from the signal set, and the UE receives two or more configurations for the third signal from the signal set and then receives or transmits the third signal based on the third configuration indicator.

[0181] In a particular embodiment, the DCI includes a first control bit field for the first configuration indicator and at least one of a second control bit field for the second configuration indicator and a third control bit field for the third configuration indicator.

[0182] In a particular embodiment, the first and second control bit fields are of different lengths, nl and n2, respectively, and / or the first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

[0183] In a particular embodiment, a position and / or length of at least one of the first, second, and third bitfields are cell-specific and configured via broadcast system information, and / or the position and / or length of at least one of the first, second, and third bitfields are UE-specific and configured via Radio Resource Control, RRC, signaling per UE or group of UEs.

[0184] In a particular embodiment, the DCI includes a shared control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

[0185] In a particular embodiment, the first configuration indicator indicates which of the up to 2n-l first signal configurations to use for a first signal reception, and / or the second configuration indicator indicates which of the up to 2n-l first signal configurations to use for a second signal reception, and / or the third configuration indicator indicates which of the up to 2n-l first signal configurations to use for a third signal reception.

[0186] In a particular embodiment, the DCI is detected in a common search space or a UE-specific search space and a PDCCH is scrambled with a C-RNTI, or the DCI is detected in a common search space and the PDCCH is scrambled with a group RNTI.

[0187] In a particular embodiment, a SS configured for monitoring a PDCCH carrying the DCI is at least one of: a default common SS, a separate common SS, and a dedicated SS for the UE. FIGURE 5 illustrates a method 500 performed by a network node for configuration switching, according to certain embodiments. As illustrated the method begins at step 502 when the network node transmits, to a UE, two or more configurations for at least a first signal. At step 504, the network node transmits, to the UE, a DCI, for resource control, and the DCI includes at least a first configuration indicator for the first signal. At step 506, the network node receives or transmits the first signal based on the first configuration indicator. The first signal is from a signal set including a SSB, a paging DCI for PO, and a PRACH preamble for RA.

[0188] In a particular embodiment, the two or more configurations are received via RRC or SI broadcast from the network node.

[0189] In a particular embodiment, the DCI is for joint resource control and comprises a second configuration indicator for a second signal from the signal set. The network node transmits two or more configurations for the second signal from the signal set and then receives or transmits the second signal based on the second configuration indicator.

[0190] In a particular embodiment, the DCI comprises a third configuration indicator for a third signal from the signal set, and the network node transmits two or more configurations for the third signal from the signal set. The network node receives or transmits the third signal based on the third configuration indicator.

[0191] In a particular embodiment, the DCI includes a first control bit field for the first configuration indicator and at least one of a second control bit field for the second configuration indicator and a third control bit field for the third configuration indicator.

[0192] In a particular embodiment, the first and second control bit fields are of different lengths, nl and n2, respectively, and / or the first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

[0193] In a particular embodiment, a position and / or length of at least one of the first, second, and third bitfields are cell-specific and configured via broadcast system information, and / or the position and / or length of at least one of the first, second, and third bitfields are UE-specific and configured via RRC signaling per UE or group of UEs.

[0194] In a particular embodiment, the DCI comprises a shared control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

[0195] In a particular embodiment, the first configuration indicator indicates which of the up to 2n-l first signal configurations to use for a first signal reception, the second configuration indicator indicates which of the up to 2n-l first signal configurations to use for a second signal reception, and / or the third configuration indicator indicates which of the up to 2n-l first signal configurations to use for a third signal reception.

[0196] In a particular embodiment, the DCI is detected in a common search space or a UE-specific search space and a PDCCH is scrambled with a C-RNTI, or the DCI is detected in a common search space and the PDCCH is scrambled with a group RNTI.

[0197] In a particular embodiment, a SS configured for monitoring a PDCCH carrying the DCI is at least one of: a default common SS, a separate common SS, and a dedicated SS for the UE.

[0198] In a particular embodiment, the network node ceases to monitor for PDCCH or parts of a PDCCH within a predetermined delay from reception of the DCI.

[0199] In a particular embodiment, a most recently signaled configuration of the first, second, and third configuration indicators is broadcasted in a SIB.

[0200] FIGURE 6 shows an example of a communication system 600 in accordance with some embodiments. In the example, the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a radio access network (RAN), and a core network 606, which includes one or more core network nodes 608. The access network 604 includes one or more access network nodes, such as network nodes 610a and 610b (one or more of which may be generally referred to as network nodes 610), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. The network nodes 610 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 612a, 612b, 612c, and 612d (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.

[0201] 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 600 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 600 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. The UEs 612 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 610 and other communication devices. Similarly, the network nodes 610 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 612 and / or with other network nodes or equipment in the telecommunication network 602 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 602.

[0202] In the depicted example, the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. 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 606 includes one more core network nodes (e.g., core network node 608) 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 608. 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).

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

[0204] As a whole, the communication system 600 of FIGURE 6 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.

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

[0206] In some examples, the UEs 612 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 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604. 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).

[0207] In the example, the hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612c and / or 612d) and network nodes (e.g., network node 610b). In some examples, the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 614 may be a broadband router enabling access to the core network 606 for the UEs. As another example, the hub 614 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 610, or by executable code, script, process, or other instructions in the hub 614. As another example, the hub 614 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 614 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 614 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.

[0208] The hub 614 may have a constant / persistent or intermittent connection to the network node 610b. The hub 614 may also allow for a different communication scheme and / or schedule between the hub 614 and UEs (e.g., UE 612c and / or 612d), and between the hub 614 and the core network 606. In other examples, the hub 614 is connected to the core network 606 and / or one or more UEs via a wired connection. Moreover, the hub 614 may be configured to connect to an M2M service provider over the access network 604 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection. In some embodiments, the hub 614 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 610b. In other embodiments, the hub 614 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 610b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0209] FIGURE 7 shows a UE 700, which may be an embodiment of the UE 112 of FIGURE 6, 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 (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0211] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 7. 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.

[0212] The processing circuitry 702 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 710. The processing circuitry 702 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 702 may include multiple central processing units (CPUs).

[0213] In the example, the input / output interface 706 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 700. 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.

[0214] In some embodiments, the power source 708 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 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.

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

[0216] The memory 710 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 710 may allow the UE 700 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 710, which may be or comprise a device-readable storage medium.

[0217] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 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 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

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

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

[0220] 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 itemtracking 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 700 shown in FIGURE 7.

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

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

[0223] FIGURE 8 shows a network node 800, which may be an embodiment of the network node 110 of FIGURE 5, 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)).

[0224] 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). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSRBSs, 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).

[0225] The network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. The network node 800 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 800 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 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, 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 800.

[0226] The processing circuitry 802 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 800 components, such as the memory 804, to provide network node 800 functionality. In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the radio frequency (RF) transceiver circuitry 812 and the baseband processing circuitry 814 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 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

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

[0228] The communication interface 806 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 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. The communication interface 806 also includes radio frontend circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810. Radio front-end circuitry 818 comprises filters 820 and amplifiers 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio frontend circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 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 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0229] In certain alternative embodiments, the network node 800 does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

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

[0231] The antenna 810, communication interface 806, and / or the processing circuitry 802 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 810, the communication interface 806, and / or the processing circuitry 802 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.

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

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

[0234] FIGURE 9 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized.

[0235] In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0236] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0237] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 908a and 908b (one or more of which may be generally referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.

[0238] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0239] In the context of NFV, a VM 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.

[0240] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.

[0241] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0242] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionalities may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0243] EXAMPLE EMBODIMENTS

[0244] Group A Example Embodiments

[0245] Example Embodiment Al . A method performed by a user equipment for configuration switching, the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0246] Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.

[0247] Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.

[0248] Group B Example Embodiments

[0249] Example Embodiment Bl. A method performed by a network node for configuration switching, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

[0250] Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.

[0251] Example Embodiment B3. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0252] Group C Example Embodiments

[0253] Example Embodiment Cl. A method performed by a user equipment (UE) for configuration switching, the method comprising: receiving two or more configurations for at least a first signal; receiving, from a network node, a Downlink Control Information (DCI) for resource control, the DCI comprising at least a first configuration indicator for the first signal; receiving or transmitting the first signal based on the first configuration indicator; where the first signal is from a signal set comprising: a Synchronization Signal Block (SSB), a paging DCI for paging occasion (PO), and a PRACH preamble for Random Access (RA).

[0254] Example Embodiment C2. The method of Example Embodiment Cl, wherein the two or more configurations are received via RRC or SI broadcast from the network node.

[0255] Example Embodiment C3. The method of any one of Example Embodiments Cl to C2, wherein the DCI is for joint resource control and comprises a second configuration indicator for a second signal from the signal set, and the method comprises: receiving two or more configurations for the second signal from the signal set and receiving or transmitting the second signal based on the second configuration indicator.

[0256] Example Embodiment C4. The method of any one of Example Embodiments Cl to C3, wherein the DCI comprises a third configuration indicator for a third signal from the signal set, and the method comprises: receiving two or more configurations for the third signal from the signal set and receiving or transmitting the third signal based on the third configuration indicator.

[0257] Example Embodiment C5. The method of any one of Example Embodiments Cl to C4, wherein the size of the DCI is configurable via SI broadcast or dedicated RRC signaling.

[0258] Example Embodiment C6. The method of any one of Example Embodiments Cl to C5, wherein the DCI comprises a first control bit field for the first configuration indicator and a second control bit field for the second configuration indicator.

[0259] Example Embodiment C7. The method of any one of Example Embodiments Cl to C6, wherein the first and second control bit fields are of different lengths, nl and n2, respectively.

[0260] Example Embodiment C8. The method of any one of Example Embodiments C6 to C7, wherein the DCI comprises a third control bit field for the third configuration indicator.

[0261] Example Embodiment C9. The method of Example Embodiment C8, wherein the first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

[0262] Example Embodiment CIO. The method of any one of Example Embodiment C6 to C9, wherein a position of at least one of the first, second, and third bitfields within the DCI are configurable.

[0263] Example Embodiment Cl 1. The method of Example Embodiment CIO, wherein the position of at least one of the first, second, and third bitfields are cell-specific and configured via broadcast system information. Example Embodiment Cl 1. The method of Example Embodiment CIO, wherein the position of at least one of the first, second, and third bitfields are UE-specific and configured via RRC signaling per UE or group of UEs.

[0264] Example Embodiment Cl 2. The method of any one of Example Embodiments Cl to C5, wherein the DCI comprises a control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

[0265] Example Embodiment C13. The method of any one of Example Embodiments Cl to C5, wherein at least two of the first and second and third indicators have same control bits.

[0266] Example Embodiment Cl 4. The method of any one of Example Embodiment Cl to Cl 3, wherein at least one of: the first configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a first signal reception, the second configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a second signal reception, and the third configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a third signal reception.

[0267] Example Embodiment Cl 5. The method of Example Embodiment Cl 4, wherein at least one of: one of the first configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the first signal configuration and a previously indicated configuration is to be used for first signal reception, one of the second configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the second signal configuration and a previously indicated configuration is to be used for second signal reception, and one of the third configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the third signal configuration and a previously indicated configuration is to be used for third signal reception.

[0268] Example Embodiment Cl 6. The method of any one of Example Embodiments Cl to Cl 5, wherein the DCI is detected in a common search space or a UE-specific search space and the PDCCH is scrambled with a C-RNU and / or a new RNTI.

[0269] Example Embodiment Cl 7. The method of any one of Example Embodiments Cl to Cl 6, wherein the DCI is detected in a common search space and the PDCCH is scrambled with a group RNTI. Example Embodiment C18. The method of Example Embodiment C17, wherein at least one of: the group RNTI is a P-RNTI or a PEI-RNTI, the group RNTI is a new resource control RNTI (e.g. G-RNTI), and the group RNTI is configured per UE via RRC signaling.

[0270] Example Embodiment Cl 9. The method of any one of Example Embodiments Cl to Cl 8, wherein the DCI comprises a field for identifying one or more serving cell(s) where the indicated configurations for the first signal, second signal, and / or third signal are used.

[0271] Example Embodiment C20. The method of any one of Example Embodiments Cl to Cl 9, wherein the DCI indicates configurations for the first signal, second signal, and / or third signal from a subset of configurations.

[0272] Example Embodiment C21. The method of Example Embodiment C20, comprising receiving the subset of configurations via MAC CE.

[0273] Example Embodiment C22. The method of Example Embodiment C20, wherein the subset of configurations depends on a serving cell in which the DCI was transmitted, or a serving cell indicated in the DCI.

[0274] Example Embodiment C23. The method of any one of Example Embodiments Cl to C22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a default common SS.

[0275] Example Embodiment C24. The method of any one of Example Embodiments Cl to C22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a separate common SS.

[0276] Example Embodiment C25. The method of any one of Example Embodiments Cl to C22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a dedicated SS for the UE.

[0277] Example Embodiment C26. The method of any one of Example Embodiments Cl to C22, wherein a SS configured for monitoring a PDCCH carrying the DCI defines monitoring occasions.

[0278] Example Embodiment C27. The method of any one of Example Embodiments Cl to C26, wherein an application delay is different for different indicated resource configurations in the DCI, even though the DCI for controlling said resources is received by the UE at same occasion.

[0279] Example Embodiment C28. The method of any one ofExample Embodiments Cl to C27, wherein the UE ceases monitoring for PDCCH or parts thereof within a predetermined or configured delay from reception of the DCI.

[0280] Example Embodiment C29. The method of any one ofExample Embodiments Cl to C28, wherein a first configuration indicator value indicates a configuration used by legacy UEs for first signal reception. Example Embodiment C30. The method of any one of Example Embodiments Cl to C29, wherein a most recently signaled state of at least one of the first, second, and third configuration indicators is broadcasted in a SIBn.

[0281] Example Embodiment C31. The method of any one of Example Embodiments Cl to C30, wherein configuration info in SIBn may be changed without SI update signaling.

[0282] Example Embodiment C32. The method of any one of Example Embodiments Cl to C31 , wherein one or more configurations in a cell for at least one of the first, second, and third signals is provided in SIBn.

[0283] Example Embodiment C33. The method of any one ofExample Embodiments Cl to C32, wherein one or more configuration indicators in the G-DCI are not valid in cells or paging areas other than where the UE was most recently connected.

[0284] Example Embodiment C34. The method of any one ofExample Embodiments Cl to C33, wherein two or more configurations for SSB comprise one or more parameters from a legacy SSB configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0285] Example Embodiment C35. The method of Example Embodiment C34, wherein the configurations are separately specified per serving cell.

[0286] Example Embodiment C36. The method of any one ofExample Embodiments Cl to C33, wherein two or more configurations for paging DCI / PDCCH / PDSCH comprise one or more parameters from a legacy paging DCI / PDCCH / PDSCH configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0287] Example Embodiment C37. The method of any one ofExample Embodiments Cl to C33, wherein two or more configurations for PRACH / RA comprise one or more parameters from a legacy PRACH / RA configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0288] Example Embodiment C38. The method of Example Embodiments Cl to C37, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0289] Example Embodiment C39. A user equipment comprising processing circuitry configured to perform any of the methods ofExample Embodiments Cl to C38. Example Embodiment C40. A user equipment configured to perform any of the methods of Example Embodiments Cl to C38.

[0290] Example Embodiment C41. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C38.

[0291] Example Embodiment C42. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C38.

[0292] Example Embodiment C43. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C38.

[0293] Example Embodiment C44. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C38.

[0294] Group D Example Embodiments

[0295] Example Embodiment DI. A method performed by a network node for configuration switching, the method comprising: transmitting, to a UE, two or more configurations for at least a first signal; transmitting, to the UE, a Downlink Control Information (DCI) for resource control, the DCI comprising at least a first configuration indicator for the first signal; receiving or transmitting the first signal based on the first configuration indicator; where the first signal is from a signal set comprising: a Synchronization Signal Block (SSB), a paging DCI for paging occasion (PO), and a PRACH preamble for Random Access (RA).

[0296] Example Embodiment D2. The method of Example Embodiment DI, wherein the two or more configurations are transmitted to the UE via RRC or SI broadcast.

[0297] Example Embodiment D3. The method of any one of Example Embodiments DI to D2, wherein the DCI is for joint resource control and comprises a second configuration indicator for a second signal from the signal set, and the method comprises: transmitting, to the UE, two or more configurations for the second signal from the signal set and receiving or transmitting the second signal based on the second configuration indicator.

[0298] Example Embodiment D4. The method of any one of Example Embodiments DI to D3, wherein the DCI comprises a third configuration indicator for a third signal from the signal set, and the method comprises: transmitting, to the UE, two or more configurations for the third signal from the signal set and receiving or transmitting the third signal based on the third configuration indicator.

[0299] Example Embodiment D5. The method of any one of Example Embodiments DI to D4, wherein the size of the DCI is configurable via SI broadcast or dedicated RRC signaling.

[0300] Example Embodiment D6. The method of any one of Example Embodiments DI to D5, wherein the DCI comprises a first control bit field for the first configuration indicator and a second control bit field for the second configuration indicator.

[0301] Example Embodiment D7. The method of any one of Example Embodiments DI to D6, wherein the first and second control bit fields are of different lengths, nl and n2, respectively.

[0302] Example Embodiment D8. The method of any one of Example Embodiments D6 to D7, wherein the DCI comprises a third control bit field for the third configuration indicator.

[0303] Example Embodiment D9. The method of Example Embodiment D8, wherein the first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

[0304] Example Embodiment DIO. The method of any one of Example Embodiment D6 to D9, wherein a position of at least one of the first, second, and third bitfields within the DCI are configurable.

[0305] Example Embodiment D 11. The method of Example Embodiment DIO, wherein the position of at least one of the first, second, and third bitfields are cell-specific and configured via broadcast system information.

[0306] Example Embodiment D 11. The method of Example Embodiment DIO, wherein the position of at least one of the first, second, and third bitfields are UE-specific and configured via RRC signaling per UE or group of UEs.

[0307] Example Embodiment DI 2. The method of any one of Example Embodiments DI to D5, wherein the DCI comprises a control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

[0308] Example Embodiment D13. The method of any one of Example Embodiments DI to D5, wherein at least two of the first and second and third indicators have same control bits.

[0309] Example Embodiment DI 4. The method of any one of Example Embodiment DI to DI 3, wherein at least one of: the first configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a first signal reception, the second configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a second signal reception, and the third configuration indicator indicates which of the up to 2nlfirst signal configurations to use for a third signal reception.

[0310] Example Embodiment DI 5. The method of Example Embodiment DI 4, wherein at least one of: one of the first configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the first signal configuration and a previously indicated configuration is to be used for first signal reception, one of the second configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the second signal configuration and a previously indicated configuration is to be used for second signal reception, and one of the third configuration indicator values [e.g. the value 2nl-l] is reserved to indicate that there is no change to the third signal configuration and a previously indicated configuration is to be used for third signal reception.

[0311] Example Embodiment D 16. The method of any one of Example Embodiments DI to DI 5, wherein the DCI is transmitted in a common search space or a UE-specific search space and the PDCCH is scrambled with a C-RNU and / or a new RNTI.

[0312] Example Embodiment D 17. The method of any one of Example Embodiments DI to DI 6, wherein the DCI is transmitted in a common search space and the PDCCH is scrambled with a group RNTI.

[0313] Example Embodiment D8. The method of Example Embodiment DI 7, wherein at least one of: the group RNTI is a P-RNTI or a PEI-RNTI, the group RNTI is a new resource control RNTI (e.g. G-RNTI), and the group RNTI is configured per UE via RRC signaling.

[0314] Example Embodiment D 19. The method of any one of Example Embodiments DI to DI 8, wherein the DCI comprises a field for identifying one or more serving cell(s) where the indicated configurations for the first signal, second signal, and / or third signal are used.

[0315] Example Embodiment D20. The method of any one of Example Embodiments DI to DI 9, wherein the DCI indicates configurations for the first signal, second signal, and / or third signal from a subset of configurations.

[0316] Example Embodiment D21. The method of Example Embodiment D20, comprising transmitting, to the UE, the subset of configurations via MAC CE.

[0317] Example Embodiment D22. The method of Example Embodiment D20, wherein the subset of configurations depends on a serving cell in which the DCI was transmitted, or a serving cell indicated in the DCI. Example Embodiment D23. The method of any one of Example Embodiments DI to D22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a default common SS.

[0318] Example Embodiment D24. The method of any one of Example Embodiments DI to D22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a separate common SS.

[0319] Example Embodiment D25. The method of any one of Example Embodiments DI to D22, wherein a SS configured for monitoring a PDCCH carrying the DCI is a dedicated SS for the UE.

[0320] Example Embodiment D26. The method of any one of Example Embodiments DI to D22, wherein a SS configured for monitoring a PDCCH carrying the DCI defines monitoring occasions.

[0321] Example Embodiment D27. The method of any one of Example Embodiments DI to D26, wherein an application delay is different for different indicated resource configurations in the DCI, even though the DCI for controlling said resources is received by the UE at same occasion.

[0322] Example Embodiment D28. The method of any one of Example Embodiments DI to D27, comprising configuring the UE to cease monitoring for PDCCH or parts thereof within a predetermined or configured delay from reception of the DCI.

[0323] Example Embodiment D29. The method of any one of Example Embodiments DI to D28, wherein a first configuration indicator value indicates a configuration used by legacy UEs for first signal reception.

[0324] Example Embodiment D30. The method of any one of Example Embodiments DI to D29, comprising broadcasting, in a SIBn, a most recently signaled state of at least one of the first, second, and third configuration indicators.

[0325] Example Embodiment D31. The method of any one of Example Embodiments DI to C30, wherein configuration info in SIBn may be changed without SI update signaling.

[0326] Example Embodiment D32. The method of any one of Example Embodiments DI to D31, comprising providing, in SIBn, one or more configurations in a cell for at least one of the first, second, and third signals. Example Embodiment D33. The method of any one of Example Embodiments DI to D32, wherein one or more configuration indicators in the G-DCI are not valid in cells or paging areas other than where the UE was most recently connected.

[0327] Example Embodiment D34. The method of any one of Example Embodiments DI to D33, wherein two or more configurations for SSB comprise one or more parameters from a legacy SSB configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0328] Example Embodiment D35. The method of Example Embodiment D34, wherein the configurations are separately specified per serving cell.

[0329] Example Embodiment D36. The method of any one of Example Embodiments DI to D33, wherein two or more configurations for paging DCI / PDCCH / PDSCH comprise one or more parameters from a legacy paging DCI / PDCCH / PDSCH configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0330] Example Embodiment D37. The method of any one of Example Embodiments DI to D33, wherein two or more configurations for PRACH / RA comprise one or more parameters from a legacy PRACH / RA configuration and additionally point to configurations in the specifications or preconfigured by RRC via either broadcast or dedicated signaling.

[0331] Example Embodiment D38. The method of any one of Example Embodiments DI to D37, wherein the network node comprises a gNodeB (gNB).

[0332] Example Embodiment D39. The method of any of the previous Example Embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0333] Example Embodiment D40. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D39.

[0334] Example Embodiment D41. A network node configured to perform any of the methods of Example Embodiments DI to D39.

[0335] Example Embodiment D42. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D39.

[0336] Example Embodiment D43. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D39. Example Embodiment D44. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments DI to D39.

[0337] Group E Example Embodiments

[0338] Example Embodiment El. A user equipment for configuration switching, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group A and C Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0339] Example Embodiment E2. A network node for configuration switching, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B and D Example Embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0340] Example Embodiment E3. A user equipment (UE) for configuration switching, the 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 and C Example 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.

[0341] Example Embodiment E4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A and C Example Embodiments to receive the user data from the host. Example Embodiment E5. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0342] Example Embodiment E6. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0343] Example Embodiment E7. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

[0344] Example Embodiment E8. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0345] Example Embodiment E9. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0346] Example Embodiment E10. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A and C Example Embodiments to transmit the user data to the host.

[0347] Example Embodiment El 1. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0348] Example Embodiment El 2. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0349] Example Embodiment El 3. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A and C Example Embodiments to transmit the user data to the host.

[0350] Example Embodiment El 4. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0351] Example Embodiment El 5. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0352] Example Embodiment El 6. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B and D Example Embodiments to transmit the user data from the host to the UE.

[0353] Example Embodiment El 7. The host of the previous Example Embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0354] Example Embodiment El 8. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment El 9. The method of the previous Example Embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0355] Example Embodiment E20. The method of any of the previous 2 Example Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0356] Example Embodiment E21. A communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B and D Example Embodiments to transmit the user data from the host to the UE.

[0357] Example Embodiment E22. The communication system of the previous Example Embodiment, further comprising: the network node; and / or the user equipment.

[0358] Example Embodiment E23. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B and D Example Embodiments to receive the user data from a user equipment (UE) for the host.

[0359] Example Embodiment E24. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0360] Example Embodiment E25. The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

[0361] Example Embodiment E26. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B and D Example Embodiments to receive the user data from the UE for the host.

[0362] Example Embodiment E27. The method of the previous Example Embodiment, further comprising at the network node, transmitting the received user data to the host.

[0363] ADDITIONAL INFORMATION

[0364] Network energy saving is of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g. XR), networks are being denser, use more antennas, larger bandwidths and more frequency bands. The environmental impact of 5G needs to stay under control, and novel solutions to improve network energy savings need to be developed.

[0365] Energy consumption has become a key part of the operators’ OPEX. According to the report from GSMA, the energy cost on mobile networks accounts for -23% of the total operator cost. See, GSMA, 5G energy efficiencies: Green is the new black, https: / / data.gsmaintelligence.com / api-web / v2 / research-file- download?id=54165956&file=241120-5G-energy.pdf. Most of the energy consumption comes from the radio access network and in particular from the Active Antenna Unit (AAU), with data centres and fibre transport accounting for a smaller share. The power consumption of a radio access can be split into two parts: the dynamic part which is only consumed when data transmission / reception is ongoing, and the static part which is consumed all the time to maintain the necessary operation of the radio access devices, even when the data transmission / reception is not on-going.

[0366] During the study in the SI phase, the network energy consumption model for the base station (BS) was defined including the reference configurations for FR1 TDD / FDD and FR2, the deep / light / micro sleep power states with corresponding relative power, transition time and energy consumption among different power states based on two types of BS categories, and the scaling rules for the active DL / UL power states considering BS power split by a static part of power and a dynamic part of power with the latter part reflecting the dynamic power consumption with respect to transmission / reception resource configurations in time, frequency, spatial and power domains. See, 3GPP TR 38.864 V18.1.0, Study on network energy savings for NR.

[0367] In addition, evaluation methodology and assumptions were achieved to study and evaluate the network energy saving gains for potential techniques with respect to other KPI including UPT, access delay, UE power consumption, etc.

[0368] Based on the agreed BS energy consumption model, and the evaluation methodology and assumptions, potential network energy saving techniques in various domains were evaluated with respect to the energy saving gains and the corresponding performance impact considering the above KPIs. The studied techniques are classified into time, frequency, spatial and power domains, and the technical descriptions as well as the legacy UE and specification impacts are summarized in the technical report. See, 3GPP TR 38.864 V18.1.0, Study on network energy savings for NR. The techniques in time and frequency domains mainly aim to reduce the power consumption for dynamic part by trying to shut down more symbols on one or more carriers to achieve BS micro sleep, and even the static power part by enlarging the interval between the contiguous active transmission / reception occasions to achieve BS light / deep sleep. The techniques in spatial and power domains mainly aim to reduce the power consumption of the TRX chains and PAs by trying to shut down more spatial elements and / or reduce transmission power / power spectrum density or increase the PA efficiency. As shown in Section 7 in TR 38.864, some of the studied techniques are beneficial for network energy savings. See, 3GPP TR 38.864 V18.1.0, Study on network energy savings for NR.

[0369] The Rel-18 work item on network energy savings for NR led to the specification of some of the techniques that were found beneficial in the study, primarily for RRC Connected, user specific signals and channels, and low load scenarios. The techniques specified in Rel-18 include SSB-less SCell operation for inter-band CA for FR1 and co-located cells, enhancement on cell DTX / DRX mechanism including the alignment of cell DTX / DRX and UE DRX in RRC CONNECTED mode, inter-node information exchange on cell DTX / DRX, techniques in spatial and power domains to enable efficient adaptation of spatial elements as well as efficient adaptation of power offset values between PDSCH and CSI-RS, as well as mechanisms to prevent legacy UEs camping on cells adopting the Rel-18 NES techniques, CHO procedure enhancement(s), and inter-node beam activation and enhancements on restricting paging in a limited area, and the corresponding RRM / RF core requirements. Some other techniques also found to be beneficial in the study were not yet specified in Rel-18. This Rel-19 work item aims to specify further network energy savings targeting the beneficial techniques studied in Rel-18, but yet unspecified, including on-demand SSB and on- demand SIB1 transmissions, as well as adaptation of common signal / channel transmissions.

[0370] Objective of SI or Core part WI or Testing part WI

[0371] The objectives of the work item are the following:

[0372] 5. Specify procedures and signaling method(s) to support on-demand SSB SCell operation for UEs in connected mode configured with CA, for both intra- / inter- band CA. [RAN1 / 2 / 3 / 4]

[0373] • activation, and is supported for FR1 and FR2 in non-shared spectrum. Specify triggering method(s) (select from UE uplink wake-up-signal using an existing signal / channel, cell on / off indication via backhaul, Scell activation / deactivation signaling)

[0374] • Notel : On-demand SSB transmission can be used by UE for at least SCell time / frequency synchronization, L1 / L3 measurements and SCell

[0375] 6. Study procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, including: [RAN1 / 2 / 3]

[0376] • Triggering method by uplink wake-up-signal using an existing signal / channel.

[0377] • Wake-up-signal configuration provisioning to UE

[0378] Note: No modification of SSB will be discussed under this objective

[0379] • Information exchange between gNBs at least for the configuration of wake-up signal, if necessary.

[0380] • Checkpoint for normative work in RAN#105

[0381] 7. Specify adaptation of common signal / channel transmissions. [RAN1 / 2 / 3 / 4]

[0382] • Adaptation of SSB in time domain, e.g. adapting periodicity

[0383] • Adaptation of PRACH in time domain

[0384] • Study adaptation of PRACH in spatial domain, e.g. non-uniform PRACH resources per SSB, and specify if found beneficial

[0385] This study is to be done in 2Q’2O24 only • Adaptation of paging occasions including confining the paging occasions in the time domain

[0386] Note: there shall be no paging latency increase

[0387] • Note: there shall be no negative impact to legacy UEs, unless significant benefits are shown

[0388] 8. Specify the corresponding core requirements, for the above features [RAN4],

[0389] Objective of Performance part WI

[0390] Specify corresponding performance requirements and test cases for the network energy saving techniques [RAN4], RAN time budget request (not applicable to RAN5 WIs / SIs)

[0391] NOTE: For all new RAN related WIs / SIs which are not led by RAN WG5 the WI / SI rapporteur has to fill out the attached Excel table to request time budgets for corresponding RAN WG meetings.

[0392] The Excel table has to be filled out for all affected RAN WGs and up to the target date of the WI / SI.

[0393] One time unit (TU) corresponds to ~ 2 hours in the meeting.

[0394] If no TU is needed, then leave the field empty otherwise enter a number >0 in the field.

[0395] For revisions of already approved WI / SI descriptions: Please remove the Excel table from the WID / SID's zip file. The time budgets are already recorded. If you want to modify them, then this has to be done via the status report and not via a revised WID / SID.

[0396] If this WID is covering Core and Performance part, then please fill out one line for each part in the attached Excel table.

Claims

CLAIMS1. A method (400) performed by a user equipment, UE, (612) for configuration switching, the method comprising: receiving (402) two or more configurations for at least a first signal; receiving (404), from a network node (610), a Downlink Control Information, DCI, for resource control, the DCI comprising at least a first configuration indicator for the first signal; receiving or transmitting (406) the first signal based on the first configuration indicator; wherein the first signal is from a signal set comprising: a Synchronization Signal Block, SSB, a paging DCI for paging occasion, PO, and a PRACH preamble for Random Access, RA.

2. The method of Claim 1, wherein the two or more configurations are received via Radio Resource Control, RRC, or System Information, SI, broadcast from the network node.

3. The method of any one of Claims 1 to 2, wherein the DCI is for joint resource control and comprises a second configuration indicator for a second signal from the signal set, and the method comprises: receiving two or more configurations for the second signal from the signal set, and receiving or transmitting the second signal based on the second configuration indicator.

4. The method of any one of Claims 1 to 3, wherein the DCI comprises a third configuration indicator for a third signal from the signal set, and the method comprises: receiving two or more configurations for the third signal from the signal set, and receiving or transmitting the third signal based on the third configuration indicator.

5. The method of any one of Claims 3 to 4, wherein the DCI comprises: a first control bit field for the first configuration indicator, and at least one of a second control bit field for the second configuration indicator and a third control bit field for the third configuration indicator.

6. The method of Claim 5, wherein at least one of: the first and second control bit fields are of different lengths, nl and n2, respectively, andthe first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

7. The method of any one of Claims 5 to 6, wherein at least one of: a position and / or length of at least one of the first, second, and third bitfields are cellspecific and configured via broadcast system information, and the position and / or length of at least one of the first, second, and third bitfields are UE- specific and configured via Radio Resource Control, RRC, signaling per UE or group of UEs.

8. The method of any one of Claims 3 to 4, wherein the DCI comprises a shared control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

9. The method of any one of Claim 1 to 8, wherein at least one of: the first configuration indicator indicates which of the up to 2n-l first signal configurations to use for a first signal reception, the second configuration indicator indicates which of the up to 2n-l first signal configurations to use for a second signal reception, and the third configuration indicator indicates which of the up to 2n-l first signal configurations to use for a third signal reception.

10. The method of any one of Claims 1 to 9, wherein: the DCI is detected in a common search space or a UE-specific search space and a Physical Downlink Control Channel, PDCCH, is scrambled with a Cell Specific-Radio Network Temporary Identifier, C-RNTI; or the DCI is detected in a common search space and the PDCCH is scrambled with a group Radio Network Temporary Identifier, RNTI.

11. The method of any one of Claims 1 to 10, wherein a search space, SS, configured for monitoring a Physical Downlink Control Channel, PDCCH, carrying the DCI is at least one of: a default common SS, a separate common SS, and a dedicated SS for the UE.

12. A method (500) performed by a network node (610) for configuration switching, the method comprising: transmitting (502), to a User Equipment, UE, (612) two or more configurations for at least a first signal; transmitting (504), to the UE, a Downlink Control Information, DCI, for resource control, the DCI comprising at least a first configuration indicator for the first signal; receiving or transmitting (506) the first signal based on the first configuration indicator; wherein the first signal is from a signal set comprising: a Synchronization Signal Block, SSB, a paging DCI for paging occasion, PO, and a PRACH preamble for Random Access, RA.

13. The method of Claim 12, wherein the two or more configurations are received via Radio Resource Control, RRC, or System Information, SI, broadcast from the network node.

14. The method of any one of Claims 12 to 13, wherein the DCI is for joint resource control and comprises a second configuration indicator for a second signal from the signal set, and the method comprises: transmitting two or more configurations for the second signal from the signal set, and receiving or transmitting the second signal based on the second configuration indicator.

15. The method of any one of Claims 12 to 14, wherein the DCI comprises a third configuration indicator for a third signal from the signal set, and the method comprises: transmitting two or more configurations for the third signal from the signal set, and receiving or transmitting the third signal based on the third configuration indicator.

16. The method of any one of Claims 14 to 15, wherein the DCI comprises: a first control bit field for the first configuration indicator, and at least one of a second control bit field for the second configuration indicator and a third control bit field for the third configuration indicator.

17. The method of Claim 16, wherein at least one of: the first and second control bit fields are of different lengths, nl and n2, respectively, andthe first and second and third control bit fields are of different lengths, nl, n2, and n3, respectively.

18. The method of any one of Claims 16 to 17, wherein at least one of: a position and / or length of at least one of the first, second, and third bitfields are cellspecific and configured via broadcast system information, and the position and / or length of at least one of the first, second, and third bitfields are UE- specific and configured via Radio Resource Control, RRC, signaling per UE or group of UEs.

19. The method of any one of Claims 14 to 15, wherein the DCI comprises a shared control bitfield and a part of control bits is shared between at least two of the first and second and third indicators.

20. The method of any one of Claim 12 to 19, wherein at least one of: the first configuration indicator indicates which of the up to 2n-l first signal configurations to use for a first signal reception, the second configuration indicator indicates which of the up to 2n-l first signal configurations to use for a second signal reception, and the third configuration indicator indicates which of the up to 2n-l first signal configurations to use for a third signal reception.

21. The method of any one of Claims 12 to 20, wherein: the DCI is detected in a common search space or a UE-specific search space and a Physical Downlink Control Channel, PDCCH, is scrambled with a Cell Specific-Radio Network Temporary Identifier, C-RNTI; or the DCI is detected in a common search space and the PDCCH is scrambled with a group Radio Network Temporary Identifier, RNTI.

22. The method of any one of Claims 12 to 21, wherein a search space, SS, configured for monitoring a Physical Downlink Control Channel, PDCCH, carrying the DCI is at least one of: a default common SS, a separate common SS, and a dedicated SS for the UE.

23. The method of any one of Claims 12 to 22, comprising ceasing to monitor for Physical Downlink Control Channel, PDCCH, or parts of a PDCCH within a predetermined delay from reception of the DCI.

24. The method of any one of Claims 12 to 23, wherein a most recently signaled configuration of the first, second, and third configuration indicators is broadcasted in a System Information Block, SIB.

25. A user equipment, UE, (612) for configuration switching, the UE configured to: receive two or more configurations for at least a first signal; receive, from a network node (610), a Downlink Control Information, DCI, for resource control, the DCI comprising at least a first configuration indicator for the first signal; receive or transmitting the first signal based on the first configuration indicator; wherein the first signal is from a signal set comprising: a Synchronization Signal Block, SSB, a paging DCI for paging occasion, PO, and a PRACH preamble for Random Access, RA.

26. The UE of Claim 25, configured to perform any of the methods of Claims 2 to 11.

27. A network node (610) for configuration switching, the network node configured to: transmit, to a User Equipment, UE, (610) two or more configurations for at least a first signal; transmit, to the UE, a Downlink Control Information, DCI, for resource control, the DCI comprising at least a first configuration indicator for the first signal; and receive or transmitting the first signal based on the first configuration indicator; wherein the first signal is from a signal set comprising: a Synchronization Signal Block, SSB, a paging DCI for paging occasion, PO, and a PRACH preamble for Random Access, RA.

28. The network node of Claim 27, configured to perform any of the methods of Claims 12 to

Images