Email copied
Patent Pending Multi-Channel Integrity Δ / UΔ Evidence Source Indication Offline Verification

Phase Time Integrity & Event Evidence

Patent-pending technology for creating portable, tamper-evident records of time and phase integrity. Phase Time compares heterogeneous, physically independent timing/phase channels and can add an information layer showing what diverged, when it diverged, how large the discrepancy was, and which source class or region is most consistent with the observed pattern.

Public overview: implementation details, channel selection logic, thresholds and full record schemas are available only under NDA.
The problem

Modern infrastructure depends on trusted time: logs, transactions, telecom, industrial control, cloud systems, distributed systems and forensic timelines. In an incident, a simple “in sync / out of sync” answer is often not enough.

  • Which timing or phase sources diverged?
  • When did the divergence start?
  • How large was the discrepancy?
  • Was it inside or outside stated uncertainty?
  • Which source class or disturbance pattern best explains it?
What Phase Time adds

Phase Time is designed as an integrity and diagnostic evidence layer above existing timing infrastructure. It does not replace NTP, PTP, GNSS or monitoring systems. It adds a richer record of the observed timing/phase state.

  • Integrity result based on independent channels.
  • Discrepancy value Δ with uncertainty .
  • Evidence of affected channels or sensors.
  • Timing and severity of divergence.
  • Support for source-region or cause-class indication.
Public high-level flow
Step 01
Acquire
Receive time/phase-related estimates from heterogeneous, physically independent channels.
Step 02
Normalize
Bring estimates into a comparable reference window or representation.
Step 03
Compare
Produce discrepancy Δ and associated uncertainty .
Step 04
Indicate
Support indication of affected channels, source region or most consistent cause class.
Step 05
Record
Issue a portable, tamper-evident integrity record for later verification.
Information layer

With more than the minimum number of channels or sensors, Phase Time can become more than an integrity check. Distributed observations can form a spatio-temporal pattern: some sensors react earlier, some later, some channels are affected and others remain stable.

  • Pattern of affected and unaffected channels.
  • Arrival-time differences across distributed sensors.
  • Regional or source-direction indication.
  • Distinction between local faults and wider external disturbances.
  • Evidence trail for later audit, incident response or dispute analysis.
Positioning

Existing timing systems are operational layers: they help infrastructure keep, discipline or distribute time. Phase Time is positioned as an evidence layer: it records whether independent time/phase sources remained mutually consistent, and what the observed divergence most likely indicates.

  • Synchronization tells systems what time to use.
  • Monitoring can show that a source is degraded.
  • Phase Time records what changed, when, how much and with what uncertainty.
Where it matters

The technology is most relevant where timing correctness may become part of an audit, incident investigation, compliance review, dispute or critical operational decision.

Finance & tradingSOC / SIEM / forensicsTelecomData centersCloud infrastructureOT / ICS / TSNResilient PNTDefense & spaceCritical infrastructure
Potential use cases
  • Time/phase integrity evidence during cyber or infrastructure incidents.
  • Detection of abnormal timing divergence across distributed sites.
  • Support for identifying whether divergence is local, regional or system-wide.
  • Audit-ready evidence for timestamped operations.
  • Forensic reconstruction of timing-state changes after an event.
IP status
Patent application
P.454410
Filing date
12 Jan 2026
Office
Polish Patent Office (UPRP)
Status
Patent pending
Licensing

Available for structured licensing discussions, technical evaluation and field-of-use partnerships. Non-confidential discussions can cover the general architecture and use cases. Claim-scope details, verification specifications and deployment variants are available under NDA.

Contact: contact@patrykrosa.com