[go: up one dir, main page]

WO2025226192A1 - Amélioration de sdt dans une cellule utilisant nes - Google Patents

Amélioration de sdt dans une cellule utilisant nes

Info

Publication number
WO2025226192A1
WO2025226192A1 PCT/SE2024/050401 SE2024050401W WO2025226192A1 WO 2025226192 A1 WO2025226192 A1 WO 2025226192A1 SE 2024050401 W SE2024050401 W SE 2024050401W WO 2025226192 A1 WO2025226192 A1 WO 2025226192A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
nes
cell
mode
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/SE2024/050401
Other languages
English (en)
Inventor
Min Wang
Ming Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2024/050401 priority Critical patent/WO2025226192A1/fr
Publication of WO2025226192A1 publication Critical patent/WO2025226192A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present disclosure generally relates to systems and methods for performing small data transmission.
  • RAN is typically deployed in a layered fashion.
  • the RAN capabilities are enhanced by adding carriers or spectrum to macro sites and deploying micro and indoor sites to complement the macro layers to boost (indoor) coverage, absorb (hotspot) traffic, and improve user experience, especially during peak traffic hours.
  • These RAN deployments will, however, lead to excess network capacity at times of low traffic (demand), which will thus result in unnecessarily high energy consumption if not counteracted with suitable energy saving techniques.
  • Cell deactivation is a known/conventional energy saving technique in the spatial domain that takes advantage of the opportunity to offload UEs (user equipment) and thus the associated traffic in a layered RAN structure with overlapping coverage areas to reduce the RAN energy consumption.
  • cell deactivation comes at the price of long cell reactivation delays in case the additional network capacity is needed to provide a certain user experience or opportune for other reasons, which significantly limits the opportunities or amount of time for employing this energy saving technique.
  • More granular energy saving techniques in time, frequency, spatial, and power domains are foreseen.
  • An example for UE energy saving techniques in the time domain is Discontinuous Reception (DRX) or Discontinuous Transmission (DTX).
  • DRX Discontinuous Reception
  • DTX Discontinuous Transmission
  • NR comprises techniques supporting DRX for the UE to reduce the UE energy consumption.
  • DRX can be used in both RRC Connected mode (C-DRX) and RRC Idle/Inactive mode (DRX). It resembles an agreement between network and UE that, regardless of downlink traffic, the network will only attempt to contact the UE during on-times of the configured DRX cycle/pattern. Thus, the UE must monitor/decode the downlink channels only as configured and can sleep, i.e., be in a low power/energy state, otherwise, i.e., during off-times. In case of uplink traffic, however, the UE may initiate transmission regardless of the DRX configuration. Simply put, the gNB must be prepared to receive uplink traffic at any time.
  • DTX/DRX for the network, it also is termed as Cell DTX/DRX interchangeably, is a promising approach enabling the network to introduce certain off-times in which transmission and/or reception is suspended/interrupted.
  • Cell DTX/DRX enables the network to operate on a certain duty cycle by which the available network capacity is scaled accordingly (up or down). In such a way, the available network capacity can dynamically be adjusted to the required network capacity, e.g. regards to current traffic demand.
  • the characteristics of Cell DTX/DRX typically include at least the below aspects: a periodic cell DTX/DRX configuration is explicitly signalled to the UEs; a periodic cell DTX/DRX pattern is configured by UE specific RRC (Radio Resource Control) signalling; the Cell DTX/DRX configuration contains at least periodicity, start slot/offset, and/or duration; as a baseline Cell DTX/DRX is activated/deactivated implicitly by RRC signalling, i.e. activated immediately once configured by RRC and deactivated once the RRC configuration is released.
  • RRC Radio Resource Control
  • Small Data Transmission is a procedure allowing data and/or signalling transmission while remaining in RRC INACTIVE state (i.e. without transitioning to RRC CONNECTED state).
  • SDT is enabled on a radio bearer basis and is initiated by the UE only if less than a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled, the DL RSRP (Downlink Reference Signal Received Power) is above a configured threshold, and a valid SDT resource is available as specified in clause 5.27 of TS 38.321.
  • DL RSRP Downlink Reference Signal Received Power
  • SDT procedure is initiated with either a transmission over RACH (Random Access Control) (configured via system information) or over Type 1 CG (Configured Grant) resources (configured via dedicated signalling in RRCRelease).
  • RACH Random Access Control
  • Type 1 CG Configured Grant resources
  • the UE transmits small data on Message A PUSCH (physical uplink shared channel) in a 2-step RACH procedure, or transmits small data on Message 3 PUSCH in a 4-step RACH procedure.
  • CG-based SDT the UE transmits small data over configured grant type-1 PUSCH resources for UEs in RRC inactive state.
  • the SDT resources can be configured on initial BWP for both RACH and CG.
  • RACH and CG resources for SDT can be configured on either or both of NUL and SUL carriers.
  • the CG resources for SDT are valid only within the cell the UE received RRCRelease and transitioned to RRC INACTIVE state.
  • the network can configure 2-step and/or 4-step RA resources for SDT. When both 2-step and 4-step RA resources for SDT are configured, the UE selects the RA type according to clause 9.2.6. CFRA is not supported for SDT over RACH.
  • the SDT procedure is either: a) successfully completed after the UE is directed to RRC IDLE (via RRCRelease) or RRC INACTIVE (via RRCRelease or RRCReject) or to RRC CONNECTED (via RRCResume or RRCSetup); or b) unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC (Radio Link Control) entity reaching a configured maximum retransmission threshold, or expiry of SDT-specific timing alignment timer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission.
  • RRC IDLE via RRCRelease
  • RRC INACTIVE via RRCRelease or RRCReject
  • RRC CONNECTED via RRCResume or RRCSetup
  • Cell DTX/DRX mechanism for time domain • SSB (Synchronization Signal Block)-less SCell operation for inter-band CA (Carrier Aggregation) for FR1 (frequency range 1) and co-located cells for frequency domain
  • SSB Synchronization Signal Block
  • SCell operation for inter-band CA (Carrier Aggregation) for FR1 (frequency range 1) and co-located cells for frequency domain
  • CSI enhancements for spatial and power domains refers to CSI configuration and report
  • cell DTX/DRX mechanism has no impact to IDLE/INACTIVE UEs as noted in the Rel-18 WID
  • SCell Secondary Cell
  • SSB-less refers to CA configuration.
  • signals/channels for IDLE UEs do occupy a certain part of time and frequency resource especially for empty /low load scenarios, including SSB, SIB1 (System Information Block 1), paging, and RACH.
  • control signals/channels have non-negligible time domain occupancy ratio and thus consumes a certain part of dynamic power.
  • transmission/reception for common control signals/channels may prevent the gNB from entering the sleeping modes even if cell DTX/DRX is introduced in Rel-18.
  • One embodiment under the present disclosure comprises a method performed by a UE for determining which SDT configuration to apply.
  • the method comprises receiving one or more SDT configurations from a network; receiving one or more indications from a network node; and applying one of the one or more SDT configurations based at least in part on one or more indications received from a network node.
  • Another embodiment of a method under the present disclosure is a method performed by a UE for performing SDT.
  • the method comprises applying an uplink transmission carrying one or more small data using one or more SDT resources.
  • Another embodiment can comprise a method performed by a UE in a dormant state for performing SDT.
  • the method comprises requesting one or more preferred NES modes or one or more adjusted parameter settings for a current NES configuration to a network.
  • Another possible embodiment under the present disclosure is a method performed by a network node for configuring a UE for SDT.
  • the method comprises transmitting one or more SDT configurations to the UE, wherein at least one of the one or more SDT configurations is for non-network energy savings mode and at least another of the one or more SDT configurations is for NES mode; and transmitting one or more indications to the UE for use in applying at least one of the one or more SDT configurations.
  • a further embodiment comprises a method performed by a network node for configuring a UE in a dormant state for SDT.
  • the method comprises receiving a request from a UE for one or more preferred cell NES configurations or one or more adjusted parameter settings for a current NES configuration; and deciding whether to agree to the request. If the network node agrees to the request, then it updates the current NES configuration accordingly; and if the network node refuses the request, then it indicates the refusal to the UE.
  • FIG. 1 illustrates a flow-chart of a method embodiment under the present disclosure
  • FIG. 2 illustrates a flow-chart of a method embodiment under the present disclosure
  • Fig. 3 illustrates several parameters for SDT for NES mode
  • FIG. 4 illustrates a flow chart of a method embodiment under the present disclosure
  • FIG. 5 illustrates a flow-chart of a method embodiment under the present disclosure
  • FIG. 6 illustrates a flow-chart of a method embodiment under the present disclosure
  • Fig. 7 shows a schematic of a communication system embodiment under the present disclosure
  • FIG. 8 shows a schematic of a user equipment embodiment under the present disclosure
  • FIG. 9 shows a schematic of a network node embodiment under the present disclosure
  • FIG. 10 shows a schematic of a host embodiment under the present disclosure
  • FIG. 11 shows a schematic of a virtualization environment embodiment under the present disclosure.
  • Fig. 12 shows a schematic representation of an embodiment of communication amongst nodes, hosts, and user equipment under the present disclosure.
  • node which can be a network node or a user equipment (UE).
  • network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) 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.
  • MSR multi-standard radio
  • gNB Baseband Unit
  • C-RAN access point
  • AP access point
  • TRP transmission reception point
  • RRU RRU
  • RRH nodes in distributed antenna system
  • core network node e.g. MSC, MME etc
  • O&M core network node
  • OSS e.g. SON
  • positioning node e.g. E-SMLC
  • the non-limiting term UE 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, PDA, tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles etc.
  • D2D device to device
  • V2V vehicular to vehicular
  • MTC UE machine type UE
  • M2M machine to machine
  • PDA tablet
  • mobile terminals smart phone
  • LEE laptop embedded equipment
  • LME laptop mounted equipment
  • USB dongles etc.
  • the term radio access technology, or RAT may refer to any RAT e.g.
  • UTRA E-UTRA
  • narrow band internet of things NB-IoT
  • WiFi Wireless Fidelity
  • Bluetooth next generation RAT
  • New Radio NR
  • 4G 5G
  • 5G 5G
  • NR NTN loT NTN
  • LTE NTN Long Term Evolution
  • Any of the equipment denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.
  • a cell DTX configuration comprises at least one of the following: a) a DTX cycle wherein each cycle comprises an on-duration during which the gNB is expected to perform transmission, and an off-duration during which the gNB is not expected to perform transmission; b) one or multiple timers controlling additional active durations during which the gNB is expected to perform transmission (for example, the gNB is in DTX active when one of those timers is running); c) one or multiple timers controlling additional inactive/sleep durations during which the gNB is not expected to perform transmission (for example, the gNB is in DTX inactive/sleep when one of those timers is running).
  • a cell DRX configuration comprises at least one of the following: a) a DRX cycle wherein each cycle comprises an on-duration where the gNB is expected to perform reception, and an off-duration where the gNB is not expected to perform reception; b) one or multiple timers controlling additional active durations during which the gNB is expected to perform reception (for example, the gNB is in DRX active when one of those timers is running); c) one or multiple timers controlling additional inactive/sleep durations during which the gNB is not expected to perform reception (for example, the gNB is in DRX inactive/sleep when one of those timers is running).
  • Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
  • Certain embodiments include sets of mechanisms for a UE served by a cell (Cell 1), which in turn is served or managed or operated by a network node (NW1), to conditionally or adaptively update SDT based on rules presented in the present disclosure.
  • Cell 1 a cell
  • NW1 network node
  • RSRP threshold for UE to determine whether to perform SDT procedure
  • cg-SDT-RSRP-ThresholdSSB an RSRP threshold configured for SSB selection for CG-SDT.
  • Three possible embodiments include: configuration by a network node; the UE applying UL transmission carrying small data using SDT resources; and dormant state UE embodiments. These are described further below. Other embodiments are possible.
  • Method 200 is a method performed by a UE for determining which SDT configuration to apply.
  • Step 210 is receiving one or more SDT configurations from a network.
  • Step 220 receiving one or more indications from a network node.
  • Step 230 is applying one of the one or more SDT configurations based at least in part on one or more indications received from a network node.
  • Method 200 can comprise a variety of alternative or additional steps and other variations.
  • the UE may determine to apply one of the SDT configurations with respect to an indication indicated by a gNB, e.g., a signaling enabling NES mode in IDLE state.
  • Method 400 is a method performed by a network node for configurating a UE for SDT.
  • Step 410 is transmitting one or more SDT configurations to the UE, wherein at least one of the one or more SDT configurations is for NES mode and at least another of the one or more SDT configurations is for NES mode.
  • Step 420 is transmitting one or more indications to the UE for use in applying at least one of the one or more SDT configurations.
  • Method 400 can comprise a variety of alternative or additional steps and other variations.
  • a gNB may provide two SDT configurations for SDT procedure wherein at least one configuration is for non-NES mode and one SDT configuration is for NES mode.
  • a SDT configurations may include at the least one of the below parameters:
  • • sdt-DataVolumeThreshold data volume threshold for the UE to determine whether to perform SDT procedure; • sdt-RSRP-Threshold: RSRP threshold for UE to determine whether to perform SDT procedure;
  • cg-SDT-RSRP-ThresholdSSB an RSRP threshold configured for SSB selection for CG-SDT.
  • Figure 3 sets forth several parameters for SDT for NES mode.
  • a UE in the dormant state applies the corresponding SDT configuration to perform SDT procedure accordingly.
  • the gNB provides two SDT configurations for different modes to UEs served in the same BWP, channel, frequency segment, carrier of a cell, in other words, the SDT configurations are configured per BWP/channel/frequency segment/carrier.
  • the gNB provides only one SDT configuration to a UE.
  • This SDT configuration is applicable for the UE in one corresponding NES mode, i.e., NES or non-NES.
  • the gNB has changed to the other mode e.g., change from NES to non-NES, or change from non-NES to NES, the UE applies the SDT configuration plus one or multiple offset values.
  • the SDT configuration when the gNB has changed from non-NES to NES, the SDT configuration was provided for non-NES mode, in this case, the UE may have fewer monitoring/receiving occasions to measure/receive data from the gNB.
  • the SDT configuration therefore needs to be adjusted to be applicable for NES mode.
  • negative offset values are added to the parameters, e.g., sdt- DataVolumeThreshold; sdt-RSRP-Threshold; or cg-SDT-RSRP-ThresholdSSB.
  • the UE can determine whether and how to perform SDT procedure based on lower thresholds in NES mode.
  • positive offset values are added to the above parameters, so that the UE can determine whether and how to perform SDT procedure based on higher thresholds in NES mode.
  • the UE may determine to apply one of the SDT configurations with respect to an indication indicated by the gNB, e.g., a signaling enabling NES mode in dormant state or a signaling specifically indicating SDT regarding NES mode, which may be signaled by system information (SI).
  • SI system information
  • the UE may determine to leave a cell which the UE currently camps on and select another cell through cell reselection, if the SDT in the UE is desirable, however the indication explicitly or implicitly indicates no SDT applicability in the cell. After the cell switch, SDT is applicable for the UE.
  • the UE’s SDT procedure/behavior is different in NES mode from non-NES mode.
  • the UE may buffer more data to trigger SDT procedure in NES mode, i.e., M2 is larger than Ml.
  • the UE may initiate SDT with higher RSRP threshold in NES mode, e.g.
  • N2 is higher than N1 and K2 is higher than KI where M2, N2 and K2 are the parameters/thresholds used in NES mode, while Ml, N1 and KI are the parameters/thresholds used in non-NES mode
  • the UE may buffer fewer data to trigger SDT procedure in NES mode, i.e., M2 is lower than Ml .
  • the UE may initiate SDT with lower RSRP threshold in NES mode, e.g. N2 is lower than N1 and K2 is lower than KI where M2, N2 and K2 are the parameters/thresholds used in NES mode, while Ml, N1 and KI are the parameters/thresholds used in non-NES mode.
  • the UE applies SDT procedure with different parameters/thresholds when the gNB changes between different NES configurations (e.g., cell DTX or DRX configurations), e.g. on-duration, off-duration, cycle, settings are different in two configurations.
  • the SDT parameters/thresholds are adjusted to be higher/lowers when the gNB’s active duration or sleep duration becomes higher/lower.
  • the UE applies different SDT configurations when the gNB changes from a NES configuration (e.g., cell DTX or DRX configuration) to another NES configuration (e.g., cell DTX or DRX configuration).
  • a NES configuration e.g., cell DTX or DRX configuration
  • another NES configuration e.g., cell DTX or DRX configuration
  • the solution may additionally rely on QoS requirements of services, e.g., latency requirement, on the small data to be transmitted in NES mode.
  • QoS requirements of services e.g., latency requirement
  • UE shall apply one set of SDT configuration with smaller (or higher) data volume threshold and/or lower (or higher) RSRP threshold in NES mode
  • UE shall apply another set of SDT configuration with larger (or lower) data volume threshold and/or higher (or lower) RSRP threshold in NES mode.
  • the above embodiments may additionally rely on/consider QoS (quality of service) requirements of services on the small data to be transmitted in NES mode.
  • the cell/the gNB active time is adjusted to provide more SDT resources/occasions, while for services associated with critical QoS requirements (e.g., lower priority or higher latency requirement), the cell/the gNB active time is adjusted to provide fewer SDT resources/occasions.
  • Method 800 is a method performed by a UE for performing SDT.
  • Step 810 is applying UL transmission carrying small data using SDT resources (e.g., RACH or CG (PUSCH) resources).
  • SDT resources e.g., RACH or CG (PUSCH) resources.
  • Method 800 can comprise a variety of alternative or additional steps or other variations. For example, in case the cell has enabled cell DRX, the UE may determine RACH or CG resources in relation to the cell DRX configuration according to one of the below options 1-4.
  • Option 1 SDT resources located during on-duration of cell DRX are enabled, and SDT resources located during off-duration of cell DRX are disabled.
  • Option 2 SDT resources are enabled regardless of whether the resources are located in on-duration or off-duration of cell DRX. i.e., SDT resources are not subject to the inactive duration of the gNB. In other words, the gNB will keep active for monitoring SDT resources/occasions regardless of whether the occasions are in on-duration or off-duration of cell DRX.
  • Option 3 SDT resources located in on-duration of cell DRX are enabled, in addition, SDT resources whose location in time is in off-duration but away from the last on- duration cell DRX less than a threshold, are also enabled, otherwise SDT resources in other off- durations locations are disabled.
  • Option 4 SDT resources located in on-duration of cell DRX are enabled, and SDT resources in off-duration of cell DRX (e.g., also referred to as missed resources) are shifted/moved to on-duration according to a pre-defined rule.
  • a missed SDT resource is moved to the closest on-duration of cell DRX.
  • a missed SDT resource is moved to the on-duration which is away in time from the off-duration at least Xms/slots (where X can be configured or preconfigured to the UE). Otherwise SDT resources in other off- duration are disabled.
  • the above embodiments may additionally rely on/consider QoS requirements of services on the small data to be transmitted in NES mode.
  • QoS requirements e.g., higher priority or lower latency requirement
  • the cell/the gNB active time is adjusted to provide more SDT resources/occasions
  • critical QoS requirements e.g., lower priority or higher latency requirement
  • application/choice of the option may further depend on configurations of NES mode, e.g. on-duration, off-duration, periodicity, the ratio between on- duration and off-duration in a cell DTX/DRX configuration.
  • option 3 or option 4 is applied if the periodicity of cell DRX is larger than a threshold e.g., otherwise option 1 or 2 is applied.
  • which option that the UE shall apply depends on a configuration/a signaling provided by the gNB.
  • which option that the UE shall apply may additionally rely on QoS requirements of services, e.g., latency requirement, on the small data to be transmitted in NES mode.
  • QoS requirements of services e.g., latency requirement
  • option 3 or option 4 is applied
  • option 1 or option 2 is applied.
  • the same options are applicable to the DL SDT resources (e.g., paging resource or SPS PDSCH resources) which are subject to the gNB’s TX inactive time (configured by one or multiple cell DTX configurations).
  • the gNB that performs one of the similar options (similar as the above options).
  • the gNB may determine to apply which option based on similar conditions as described in the above.
  • a RAN node e.g., CU (central unit)
  • a CN (core network) node e.g., AMF (Access and Mobility Management Function), SMF (Session Management Function), etc.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • the UE may ignore/skip a cell DTX/DRX configuration (or skipping NES mode) at the least during SDT transmission or SDT reception.
  • the gNB may also ignore/skip a cell DTX/DRX configuration. Ignoring/skipping one or multiple cell DTX/DRX configuration (or NES mode) for SDT may be applied based one of the below options A or B.
  • Option A the RAN node (e.g., CU, DU or the gNB) or the CN node (e.g., AMF, or SMF etc) determines whether cell DTX/DRX or NES mode can be skipped/ignored/disabled for SDT.
  • the RAN node or the CN node needs to send the configuration or a signaling to the UE indicating this, via at least one of the following signaling alternatives: RRC signaling; NAS signaling; SI (System information); MAC CE (Medium Access Control Control Element); LI signaling (signaling carried on physical channels e.g., PDCCH).
  • Option B the UE itself determines whether cell DTX/DRX or NES mode needs to be skipped/ignored/disabled for SDT, from UE preference perspective.
  • the UE may send an indication message to the gNB indicating that cell DTX/DRX or NES mode needs to be skipped/ignored/disabled for SDT, from UE preference perspective by RRC signaling, MAC-CE or LI -signaling.
  • the UE may send an indication message to the gNB indicating a time window, during which cell DTX/DRX or NES mode needs to be skipped/ignored/disabled for SDT from UE preference perspective by RRC signaling, MAC-CE or Ll-signaling.
  • the gNB may accept or reject the UE’s preference. For the former, the gNB would skip/ignore/disable cell DTX/DRX or NES mode for SDT. For the latter, the gNB rejects the UE’s indication. The gNB would keep the current cell DTX/DRX or NES mode regardless if whether the UE operates SDT or not.
  • Whether to ignore/skip cell DTX/DRX or NES mode for SDT can be determined based on the service/traffic type/application associated with the SDT data. For a service with critical QoS requirements (e.g., high priority or low latency requirement), it is beneficial to ignore/skip/disable cell DTX/DRX or NES mode for SDT. In this case, both the UE and the gNB need to be synced for the knowledge on whether cell DTX/DRX or NES mode is ignored/skipped/disabled.
  • critical QoS requirements e.g., high priority or low latency requirement
  • the gNB may apply a cell DTX/DRX or NES configuration specific for SDT.
  • This configuration gives the cell/the gNB with more active time (e.g., a shorter cycle, longer ON- duration, shorter off-duration etc) for transmission or reception, than that of another cell without supporting SDT for UEs in a RRC dormant state.
  • the UE operating SDT in the cell assumes that the cell/the gNB is applying the SDT specific cell DTX/DRX or NES configuration.
  • Additional embodiments may deal with UE(s) in a dormant state.
  • Method 1000 is a method performed by a network for configurating a UE in a dormant state for performing SDT.
  • Step 1010 is receiving a request or recommendation from a UE for one or more recommended/pref erred cell NES configurations (e.g., cell DTX/DRX configurations for SDT), or adjusted parameter settings for the current NES configuration. For example, if the UE has determined that a current cell DTX/DRX configuration cannot fulfill the UE’s need for transmission or reception of SDT data, e.g.
  • the UE may send a UL signaling or a message to the gNB indicating the current NES configuration (e.g., cell DTX/DRX configuration) can’t meet the UE’s requirements.
  • Step 1015 is deciding whether to accept the UE’s request or recommendation.
  • the gNB may update the configuration for NES configuration accordingly.
  • the gNB refuses to update/reconfigure its NES configuration based on the UE’s preference, it may so indicate to the UE.
  • Method 1000 may comprise a variety of alternative or additional steps or other variations. For example, when the UE has moved to a target cell and operates SDT procedure, upon reception of SDT data from the UE, the receiving gNB in the target cell may fetch a cell NES configuration (e.g., cell DTX/DRX) which is preferred/ acceptable for the UE’s SDT procedure from the last/previous serving/camped cell. After fetching the NES configuration, the receiving gNB may update its own NES configuration accordingly (e.g., same or similar as the fetched NES configuration) for the UE.
  • a cell NES configuration e.g., cell DTX/DRX
  • the receiving gNB may update its own NES configuration accordingly (e.g., same or similar as the fetched NES configuration) for the UE.
  • Method 1000 can include defining the rules for the UE in a RRC dormant state operating/adjusting SDT in a cell operating NES.
  • the cell NES configuration can be adjusted for SDT to provide sufficient SDT resources/occasions.
  • Another possible method embodiment 1200 is shown in Figure 6.
  • Method 1200 is a method performed by a UE in a dormant state for performing SDT.
  • Step 1210 is the UE which is in a RRC dormant state and operating SDT in a cell requesting or recommending a preferred NES configuration, e.g., a cell DTX/DRX configuration for SDT.
  • the UE may send a UL signaling or a message to the gNB indicating the current NES configuration (e.g., cell DTX/DRX configuration) can’t meet the UE’s requirements.
  • the UE may further indicate one or more recommended/preferred cell NES configurations (e.g., cell DTX/DRX configurations), or adjusted parameter settings for the current NES configuration.
  • the gNB may update the configuration for NES configuration accordingly if the gNB agrees with the UE’s suggest! on/preferred NES configurations. Step 1215 is agreeing or disagreeing to the request. If the gNB agrees, then at step 1220, the UE may continue with the requested configuration. If the gNB refuses to update/reconfigure its NES configuration based on the UE’s preference, then at step 1230 the UE may conduct cell reselection and camp on another cell instead of the current cell.
  • Method 1200 may comprise a variety of additional or alternative steps or other variations.
  • FIG. 7 shows an example of a communication system 2100 in accordance with some embodiments.
  • the communication system 2100 includes a telecommunication network 2102 that includes an access network 2104, such as a RAN, and a core network 2106, which includes one or more core network nodes 2108.
  • the access network 2104 includes one or more access network nodes, such as network nodes 2110a and 2110b (one or more of which may be generally referred to as network nodes 2110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 2110 facilitate direct or indirect connection of UE, such as by connecting UEs 2112a, 2112b, 2112c, and 2112d (one or more of which may be generally referred to as UEs 2112) to the core network 2106 over one or more wireless connections.
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 1100 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 2100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 2112 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 2110 and other communication devices.
  • the network nodes 2110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 2112 and/or with other network nodes or equipment in the telecommunication network 2102 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 2102.
  • the core network 2106 connects the network nodes 2110 to one or more hosts, such as host 2116. 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 2106 includes one more core network nodes (e.g., core network node 2108) 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 2108.
  • 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).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 2116 may be under the ownership or control of a service provider other than an operator or provider of the access network 2104 and/or the telecommunication network 2102, and may be operated by the service provider or on behalf of the service provider.
  • the host 2116 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.
  • the communication system 2100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts.
  • 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.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 2102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 2102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2102. For example, the telecommunications network 2102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 2112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 2104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2104.
  • a UE may be configured for operating in single- or multi-RAT or multi -standard mode.
  • 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).
  • MR-DC multi-radio dual connectivity
  • the hub 2114 communicates with the access network 2104 to facilitate indirect communication between one or more UEs (e.g., UE 2112c and/or 2112d) and network nodes (e.g., network node 2110b).
  • the hub 2114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 2114 may be a broadband router enabling access to the core network 2106 for the UEs.
  • the hub 2114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 2114 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.
  • the hub 2114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 2114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 2114 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.
  • the hub 2114 may have a constant/persistent or intermittent connection to the network node 2110b.
  • the hub 2114 may also allow for a different communication scheme and/or schedule between the hub 2114 and UEs (e.g., UE 2112c and/or 2112d), and between the hub 2114 and the core network 2106.
  • the hub 2114 is connected to the core network 2106 and/or one or more UEs via a wired connection.
  • the hub 2114 may be configured to connect to an M2M service provider over the access network 1104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 2110 while still connected via the hub 2114 via a wired or wireless connection.
  • the hub 2114 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 2110b.
  • the hub 2114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 2110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 8 shows a UE 2200 in accordance with some embodiments.
  • 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.
  • VoIP voice over IP
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • UEs identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3 GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehi cl e-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • 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).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may
  • the UE 2200 includes processing circuitry 2202 that is operatively coupled via a bus 2204 to an input/output interface 2206, a power source 2208, a memory 2210, a communication interface 2212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 10. 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.
  • the processing circuitry 2202 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 2210.
  • the processing circuitry 2202 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.
  • the processing circuitry 2202 may include multiple central processing units (CPUs).
  • the input/output interface 2206 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 2200.
  • 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 presencesensitive 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.
  • USB Universal Serial Bus
  • the power source 2208 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 2208 may further include power circuitry for delivering power from the power source 2208 itself, and/or an external power source, to the various parts of the UE 2200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2208.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2208 to make the power suitable for the respective components of the UE 2200 to which power is supplied.
  • the memory 2210 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.
  • the memory 2210 includes one or more application programs 2214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2216.
  • the memory 2210 may store, for use by the UE 2200, any of a variety of various operating systems or combinations of operating systems.
  • the memory 2210 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.
  • RAID redundant array of independent disks
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 2210 may allow the UE 2200 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 2210, which may be or comprise a device-readable storage medium.
  • the processing circuitry 2202 may be configured to communicate with an access network or other network using the communication interface 2212.
  • the communication interface 2212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2222.
  • the communication interface 2212 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 2218 and/or a receiver 2220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 2218 and receiver 2220 may be coupled to one or more antennas (e.g., antenna 2222) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 2212 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.
  • GPS global positioning system
  • 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.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 2212, 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).
  • 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.
  • the states of the actuator, the motor, or the switch may change.
  • 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.
  • 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.
  • 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-
  • AR Augmented Reality
  • VR
  • 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.
  • the UE may implement the 3GPP NB-IoT standard.
  • 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.
  • 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.
  • 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.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 9 shows a network node 3300 in accordance with some embodiments.
  • 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.
  • 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)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • 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.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • 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).
  • DAS distributed antenna system
  • network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 3300 includes a processing circuitry 3302, a memory 3304, a communication interface 3306, and a power source 3308.
  • the network node 3300 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.
  • the network node 3300 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 1300 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 3304 for different RATs) and some components may be reused (e.g., a same antenna 3310 may be shared by different RATs).
  • the network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, 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 1300.
  • RFID Radio Frequency Identification
  • the processing circuitry 3302 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 3300 components, such as the memory 3304, to provide network node 3300 functionality.
  • the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 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 3312 and baseband processing circuitry 3314 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314.
  • the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 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
  • the memory 3304 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), readonly 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 3302.
  • 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), readonly 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-vola
  • the memory 3304 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 3302 and utilized by the network node 3300.
  • the memory 3304 may be used to store any calculations made by the processing circuitry 3302 and/or any data received via the communication interface 3306.
  • the processing circuitry 3302 and memory 3304 is integrated.
  • the communication interface 3306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 3306 comprises port(s)/terminal(s) 3316 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 3306 also includes radio front-end circuitry 3318 that may be coupled to, or in certain embodiments a part of, the antenna 3310.
  • Radio front-end circuitry 3318 comprises filters 3320 and amplifiers 3322.
  • the radio front-end circuitry 3318 may be connected to an antenna 3310 and processing circuitry 3302.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 3310 and processing circuitry 3302.
  • the radio front-end circuitry 3318 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 3318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and/or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when receiving data, the antenna 3310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3318. The digital data may be passed to the processing circuitry 3302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.
  • the network node 3300 does not include separate radio front-end circuitry 3318, instead, the processing circuitry 3302 includes radio frontend circuitry and is connected to the antenna 3310.
  • the processing circuitry 3302 includes radio frontend circuitry and is connected to the antenna 3310.
  • all or some of the RF transceiver circuitry 3312 is part of the communication interface 3306.
  • the communication interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312, as part of a radio unit (not shown), and the communication interface 3306 communicates with the baseband processing circuitry 3314, which is part of a digital unit (not shown).
  • the antenna 3310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 3310 may be coupled to the radio front-end circuitry 3318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port.
  • the antenna 3310, communication interface 3306, and/or the processing circuitry 3302 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.
  • the antenna 3310, the communication interface 3306, and/or the processing circuitry 3302 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.
  • the power source 3308 provides power to the various components of network node 3300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 3308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3300 with power for performing the functionality described herein.
  • the network node 3300 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 3308.
  • the power source 3308 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.
  • Embodiments of the network node 3300 may include additional components beyond those shown in Figure 9 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.
  • the network node 3300 may include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300.
  • FIG 10 is a block diagram of a host 4400, which may be an embodiment of the host 2116 of Figure 7, in accordance with various aspects described herein.
  • the host 4400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 4400 may provide one or more services to one or more UEs.
  • the host 4400 includes processing circuitry 4402 that is operatively coupled via a bus 4404 to an input/output interface 4406, a network interface 4408, a power source 4410, and a memory 4412.
  • processing circuitry 4402 that is operatively coupled via a bus 4404 to an input/output interface 4406, a network interface 4408, a power source 4410, and a memory 4412.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 8 and 9, such that the descriptions thereof are generally applicable to the corresponding components of host 4400.
  • the memory 4412 may include one or more computer programs including one or more host application programs 4414 and data 4416, which may include user data, e.g., data generated by a UE for the host 4400 or data generated by the host 4400 for a UE.
  • Embodiments of the host 4400 may utilize only a subset or all of the components shown.
  • the host application programs 4414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 4414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 4400 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 4414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • FIG 11 is a block diagram illustrating a virtualization environment 5500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • 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 5500 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.
  • VMs virtual machines
  • the node may be entirely virtualized.
  • Applications 5502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 5500 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 5504 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 5506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 5508a and 5508b (one or more of which may be generally referred to as VMs 5508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 5506 may present a virtual operating platform that appears like networking hardware to the VMs 5508.
  • the VMs 5508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 5506.
  • a virtualization layer 5506 Different embodiments of the instance of a virtual appliance 5502 may be implemented on one or more of VMs 5508, 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.
  • NFV network function virtualization
  • a VM 5508 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 5508, and that part of hardware 5504 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.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 5508 on top of the hardware 5504 and corresponds to the application 5502.
  • Hardware 5504 may be implemented in a standalone network node with generic or specific components. Hardware 5504 may implement some functions via virtualization. Alternatively, hardware 5504 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 5510, which, among others, oversees lifecycle management of applications 5502. In some embodiments, hardware 5504 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 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.
  • some signaling can be provided with the use of a control system 5512 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 12 shows a communication diagram of a host 6602 communicating via a network node 6604 with a UE 6606 over a partially wireless connection in accordance with some embodiments.
  • host 6602 Like host 4400, embodiments of host 6602 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 6602 also includes software, which is stored in or accessible by the host 6602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 6606 connecting via an over-the-top (OTT) connection 6650 extending between the UE 6606 and host 6602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 6650.
  • the network node 6604 includes hardware enabling it to communicate with the host 6602 and UE 6606.
  • the connection 6660 may be direct or pass through a core network (like core network 2106 of Figure 7) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 2106 of Figure 7
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 6606 includes hardware and software, which is stored in or accessible by UE 6606 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 6606 with the support of the host 6602.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 6606 with the support of the host 6602.
  • an executing host application may communicate with the executing client application via the OTT connection 6650 terminating at the UE 6606 and host 6602.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 6650 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides
  • the OTT connection 6650 may extend via a connection 6660 between the host 6602 and the network node 6604 and via a wireless connection 6670 between the network node 6604 and the UE 6606 to provide the connection between the host 6602 and the UE 6606.
  • the connection 6660 and wireless connection 6670, over which the OTT connection 6650 may be provided, have been drawn abstractly to illustrate the communication between the host 6602 and the UE 1606 via the network node 6604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 6602 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 6606.
  • the user data is associated with a UE 6606 that shares data with the host 6602 without explicit human interaction.
  • the host 6602 initiates a transmission carrying the user data towards the UE 6606.
  • the host 6602 may initiate the transmission responsive to a request transmitted by the UE 6606.
  • the request may be caused by human interaction with the UE 6606 or by operation of the client application executing on the UE 6606.
  • the transmission may pass via the network node 6604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 6612, the network node 6604 transmits to the UE 6606 the user data that was carried in the transmission that the host 6602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 6614, the UE 6606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 6606 associated with the host application executed by the host 6602.
  • the UE 6606 executes a client application which provides user data to the host 6602.
  • the user data may be provided in reaction or response to the data received from the host 6602.
  • the UE 6606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 6606. Regardless of the specific manner in which the user data was provided, the UE 6606 initiates, in step 6618, transmission of the user data towards the host 6602 via the network node 6604.
  • the network node 6604 receives user data from the UE 6606 and initiates transmission of the received user data towards the host 6602.
  • the host 6602 receives the user data carried in the transmission initiated by the UE 6606.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 6606 using the OTT connection 6650, in which the wireless connection 6670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime.
  • factory status information may be collected and analyzed by the host 6602.
  • the host 6602 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 6602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 6602 may store surveillance video uploaded by a UE.
  • the host 6602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 6602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 6602 and/or UE 6606.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 6650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 6650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 6604. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 6602.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 6650 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • 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.
  • 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.
  • 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.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • 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.
  • controller computer system
  • computing system are defined broadly as including any device or system — or combination thereof — that includes at least one physical and tangible processor and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor.
  • the term “computer system” or “computing system,” as used herein is intended to include personal computers, desktop computers, laptop computers, tablets, hand-held devices (e.g., mobile telephones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multi-processor systems, network PCs, distributed computing systems, datacenters, message processors, routers, switches, and even devices that conventionally have not been considered a computing system, such as wearables (e.g., glasses).
  • the computing system also has thereon multiple structures often referred to as an “executable component.”
  • the memory of a computing system can include an executable component.
  • executable component is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof.
  • structure of an executable component may include software objects, routines, methods, and so forth, that may be executed by one or more processors on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media.
  • the structure of the executable component exists on a computer-readable medium in such a form that it is operable, when executed by one or more processors of the computing system, to cause the computing system to perform one or more functions, such as the functions and methods described herein.
  • a structure may be computer-readable directly by a processor — as is the case if the executable component were binary.
  • the structure may be structured to be interpretable and/or compiled — whether in a single stage or in multiple stages — so as to generate such binary that is directly interpretable by a processor.
  • a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably.
  • the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed.
  • the term “processor” or “controller” also refers to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.
  • the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic, or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as nonlimiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • a computing system includes a user interface for use in communicating information from/to a user.
  • the user interface may include output mechanisms as well as input mechanisms.
  • output mechanisms might include, for instance, speakers, displays, tactile output, projections, holograms, and so forth.
  • Examples of input mechanisms might include, for instance, microphones, touchscreens, projections, holograms, cameras, keyboards, stylus, mouse, or other pointer input, sensors of any type, and so forth.
  • the terms “approximately,” “about,” and “substantially,” as used herein, represent an amount or condition close to the specific stated amount or condition that still performs a desired function or achieves a desired result.
  • the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a specifically stated amount or condition.
  • references to referents in the plural form does not necessarily require a plurality of such referents. Instead, it will be appreciated that independent of the inferred number of referents, one or more referents are contemplated herein unless stated otherwise.
  • references in the specification to "one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • systems, devices, products, kits, methods, and/or processes, according to certain embodiments of the present disclosure may include, incorporate, or otherwise comprise properties or features (e.g., components, members, elements, parts, and/or portions) described in other embodiments disclosed and/or described herein. Accordingly, the various features of certain embodiments can be compatible with, combined with, included in, and/or incorporated into other embodiments of the present disclosure. Thus, disclosure of certain features relative to a specific embodiment of the present disclosure should not be construed as limiting application or inclusion of said features to the specific embodiment. Rather, it will be appreciated that other embodiments can also include said features, members, elements, parts, and/or portions without necessarily departing from the scope of the present disclosure.
  • any feature herein may be combined with any other feature of a same or different embodiment disclosed herein.
  • various well-known aspects of illustrative systems, methods, apparatus, and the like are not described herein in particular detail in order to avoid obscuring aspects of the example embodiments. Such aspects are, however, also contemplated herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés de configuration d'un UE pour des configurations de transmission de données de petite taille et des configurations de NES. Certains modes de réalisation comprennent des ensembles de mécanismes pour un UE desservi par une cellule, qui à son tour est desservie ou gérée ou exploitée par un nœud de réseau, pour mettre à jour de manière conditionnelle ou adaptative le SDT sur la base de différentes règles possibles. Par exemple, dans certains modes de réalisation, un RRC peut configurer les au moins deux ensembles de configurations pour une procédure de SDT, un pour un mode non-NES et un autre pour un mode NES.
PCT/SE2024/050401 2024-04-25 2024-04-25 Amélioration de sdt dans une cellule utilisant nes Pending WO2025226192A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050401 WO2025226192A1 (fr) 2024-04-25 2024-04-25 Amélioration de sdt dans une cellule utilisant nes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050401 WO2025226192A1 (fr) 2024-04-25 2024-04-25 Amélioration de sdt dans une cellule utilisant nes

Publications (1)

Publication Number Publication Date
WO2025226192A1 true WO2025226192A1 (fr) 2025-10-30

Family

ID=97490786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2024/050401 Pending WO2025226192A1 (fr) 2024-04-25 2024-04-25 Amélioration de sdt dans une cellule utilisant nes

Country Status (1)

Country Link
WO (1) WO2025226192A1 (fr)

Similar Documents

Publication Publication Date Title
JP7671862B2 (ja) Ｓｃｅｌｌについてのｌ１／ｌ２セントリックモビリティのための方法及びノード
US20250142470A1 (en) Efficient Usage of Receivers for Paging-Early-Indication Reception
WO2024035327A1 (fr) Économies d'énergie de nœud de réseau par l'intermédiaire d'un mécanisme de réponse d'accès aléatoire flexible
US20250119777A1 (en) Reduction of unnecessary radio measurement relaxation reports
US20240334294A1 (en) Indicating Handover-Persistent Release Preference
US20240407042A1 (en) Systems and methods for connected mode discontinuous reception using short cycles
US20250048261A1 (en) Methods for Avoiding Adverse Effects Caused by NES
WO2023207433A1 (fr) Procédés et appareils de communication dans un système de communication sans fil avec une caractéristique d'économie d'énergie de réseau
US20250280423A1 (en) Methods in determining the application delay for search-space set group-switching
EP4566355A1 (fr) Économie d'énergie de réseau dans un ng-ran scindé
WO2025226192A1 (fr) Amélioration de sdt dans une cellule utilisant nes
EP4381780B1 (fr) Rapport de relaxation de mesure radio précoce
US20240413869A1 (en) Temporary reference signal-based secondary cell activation via radio resource control
WO2025170521A1 (fr) Opération de cellule basée sur des ssb à la demande
WO2024209399A1 (fr) Motifs de saut de fréquence de prs et de srs et configuration d'intervalle de mesure et de ppw associée dans le positionnement
WO2024209417A1 (fr) Rapport d'ue d'une dégradation de performances liée à des économies d'énergie de réseau
WO2025170522A1 (fr) Activation de scell basée sur un ssb à la demande
WO2024014996A1 (fr) Signalisation d'informations d'économie d'énergie dans un réseau d'accès radio
WO2025094140A1 (fr) Envoi et réception d'informations indiquant qu'un nœud de réseau peut sélectionner un état actif ou inactif pour une ou plusieurs cellules, faisceaux et/ou blocs de signaux de synchronisation
WO2024095224A1 (fr) Transmission et réception discontinues de cellule
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2024170689A1 (fr) Transfert intercellulaire conditionnel associé à des nes
EP4666680A1 (fr) Transfert intercellulaire conditionnel associé à des nes
WO2025032542A1 (fr) Rapports de mobilité pour économies d'énergie de réseau
WO2024072281A1 (fr) Procédés pour la fabrication d'un équipement utilisateur conscient d'une transmission ou d'une réception discontinue par un réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24937215

Country of ref document: EP

Kind code of ref document: A1