1. ZeroLatency presents TIMEPACK TM INFRASTRUCTURE VISIBILITY
FOR REAL-TIME NEEDS
2. Traditional Network Monitoring Challenges Latency monitoring
is becoming a key aspect to be monitored nowadays, since it impacts
data quality, customer experience and ultimately business. 6:00
9:00 All market solutions are using LAN packet time-stamping or
event correlation which cannot cope with the amount of data
Specific decoder per protocol High computational power Extra
management traffic
3. TimePack, a new monitoring approach Timepack is a
proprietary IP protocol extension designed to carry time/location
in the same information packet. TRACKING 3:00 5:00 6:00 9:00 This
is the most efficient way to measure latency, troubleshoot routing
issues and provide performance metrics on heterogeneous networks.
Timepack can be implemented in hardware but also in software,
creating a new ecosystem of latency aware
application/networks.
4. TimePack Uses a new algorithm to store time and location
information in the IP packet which remains fully RFC complaint.
Allows to trace the IP packet journey in a transparent way across
any network. Provides a method to assure network visibility that
can be integrated in any existing monitoring tool. Provides network
visibility latency and traceability for flow and packages.
5. Technology Implementation TIMEPACK Software Hardware It can
be implemented in the operative system Similar to an inline device
(like a network tap) or network appliance (like a
router/switch)
7. Inline deployment No extra traffic generated, no need of
packet/event correlation, no intensive tasks PTP clock IN OUT Time
and location tracking possible (useful for dynamically routed
network) Can be used in every network (MPLS,VPN, 4G, Satellite) and
for a specific traffic (ie FIX) Linear scalability: one device per
link, not based on traffic to analyze Easy to integrate with any
network monitoring infrastructure Very low infrastructure impact,
transparent for the whole network A software implementation (on
Linux) of the same algorithm can be used at the origin of the data
flow
8. Probe deployment Central collector GPS clock Very small
extra management traffic generated Can simulate any IP traffic to
test every QoS on the network Latency measurement from every point
of the network Remotely configurable (customize test, different
hosts) Multicast available 1.5W power consumption per probe, 30W
central collector
9. Uses cases Latency heatmap Network quality of service (QoS)
latency aware Cloud/carrier SLA monitoring Latency aware video
codec Improved natural disasters real-time monitoring Improved real
power grids time monitoring
