Client-Server Time Synchronization Using Shared Clock Source Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems, particularly in 5G NR, lack effective methods for end-to-end time synchronization between clients and servers, which is crucial for low-latency cloud-based services like split XR, leading to inefficiencies in resource allocation and user experience.

Innovation Solution

Clients synchronize their clocks with a clock source, such as a cellular clock from the RAN, and transmit information about the clock source, cell identifier, and timestamped data to servers, enabling the servers to synchronize actions and allocate resources efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If clients and servers use independent clock sources, then device autonomy and flexibility are improved, but time synchronization accuracy deteriorates

Engineering Contradiction:
Improvedevice autonomyVSAvoidtime synchronization accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent introduces a clock source indication mechanism as an intermediary that allows clients and servers to identify and reference a common clock source. By transmitting clock source indication information (such as cell ID, frequency offset, timing advance) between devices, the system enables time synchronization without requiring direct coupling of clock sources, thus maintaining device autonomy while achieving synchronization accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback by having clients transmit clock source indication information to servers, which then use this information to align their timing. This feedback loop allows the server to adjust its resource allocation and data transmission timing based on the client's reference to a common clock source, achieving synchronized operation while preserving independent clock hardware.

Inventive Principle:
Principle #23Feedback

2Device complexity

If time synchronization is not implemented, then system complexity is reduced, but resource allocation efficiency deteriorates

Engineering Contradiction:
Improvesystem complexityVSAvoidresource allocation efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies preliminary action by having clients transmit clock source indication information before actual data transmission occurs. This advance notification allows the server to pre-configure resource allocation, buffer management, and scheduling decisions based on expected timing, thereby improving resource allocation efficiency without requiring complex real-time synchronization mechanisms.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If timestamp precision is increased, then event timing accuracy is improved, but data transmission overhead increases

Engineering Contradiction:
Improveevent timing accuracyVSAvoiddata transmission overhead
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent extracts the essential timing reference information (clock source indication) from the complete timestamp data. Instead of transmitting full high-precision timestamps, the system transmits only the critical clock source identification parameters (cell ID, frequency offset, timing advance), which allow the receiving end to reconstruct timing information with sufficient precision while minimizing data overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12477488B2End-to-end time synchronization for cloud-based services
Publication Date: 2025.11.18 QUALCOMM INC
  • US12477488B2 patent drawing
  • US12477488B2 patent drawing
  • US12477488B2 patent drawing

AI summary

Certain aspects of the present disclosure provide techniques for communicating time synchronized data between a client and a server. An example method generally includes synchronizing, by a client, a clock of the client with a clock source. The method also includes transmitting, from the client to a server, at an application level, information indicating the clock source, a cell identifier of a serving cell of the client, and accuracy of the clock source as a time value. The method further includes transmitting, from the client to the server, a message including data and a timestamp correlated to an event associated with the data based on the clock. The method also includes in response to the message, receiving, by the client from the server, generated data.