US9813226B2 - Modeling a clock - Google Patents
Modeling a clock Download PDFInfo
- Publication number
- US9813226B2 US9813226B2 US14/819,337 US201514819337A US9813226B2 US 9813226 B2 US9813226 B2 US 9813226B2 US 201514819337 A US201514819337 A US 201514819337A US 9813226 B2 US9813226 B2 US 9813226B2
- Authority
- US
- United States
- Prior art keywords
- clock
- node
- packets
- packet
- generating
- 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.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/06—Synchronising arrangements
- H04J3/0635—Clock or time synchronisation in a network
- H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
- H04J3/0658—Clock or time synchronisation among packet nodes
- H04J3/0661—Clock or time synchronisation among packet nodes using timestamps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L7/00—Arrangements for synchronising receiver with transmitter
- H04L7/0008—Synchronisation information channels, e.g. clock distribution lines
- H04L7/0012—Synchronisation information channels, e.g. clock distribution lines by comparing receiver clock with transmitter clock
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/14—Monitoring arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/0858—One way delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
- H04L43/087—Jitter
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
Definitions
- the subject matter described herein relates to clock related measurements. More specifically, the subject matter relates to methods, systems, and computer readable media for modeling a clock.
- Network operators typically test network nodes for reliability and other characteristics before deploying the network nodes in live (e.g., non-test) networks. While testing a network node before deployment may be beneficial, scenarios exist where testing a network node in a live network is useful and/or necessary, e.g., for detecting and/or resolving previously undetected issues.
- Traffic related measurements are typically dependent on clock synchronization between two endpoints, e.g., a sender node and a receiver node.
- each endpoint may include clocks of varying precision.
- a sender node may use a low precision clock (e.g., a clock that is precise to one millisecond) and a receiver clock may use a higher precision clock (e.g., a clock that is precise to one microsecond) than a receiver node.
- timestamps associated with one or more of the clocks may not provide enough precision and/or accuracy for performing one or more traffic related measurements, such as a one-way latency measurement.
- the method occurs at a monitoring module associated with a first node.
- the method includes receiving packets from a second node, extracting timestamps from at least two of the packets, and generating, using the timestamps, clock related information for generating a local clock model indicative of a precision of a local clock at the first node relative to a clock at the second node.
- the system includes at least one memory and a monitoring module (MM) associated with a first node.
- the MM is implemented using the at least one memory.
- the MM is configured to receive packets from a second node, extract timestamps from at least two of the packets, and generate, using the timestamps, clock related information for generating a local clock model indicative of a precision of a local clock at the first node relative to a clock at the second node.
- the subject matter described herein may be implemented in software in combination with hardware and/or firmware.
- the subject matter described herein may be implemented in software executed by a processor.
- the subject matter described herein may be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps.
- Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory devices, such as disk memory devices, chip memory devices, programmable logic devices, field-programmable gate arrays, and application specific integrated circuits.
- a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
- node refers to a physical computing platform including one or more processors (e.g., hardware-based processors), network interfaces, and memory.
- processors e.g., hardware-based processors
- network interfaces e.g., Ethernet interfaces
- memory e.g., random access memory
- clock refers to any entity (e.g., software, hardware, and/or firmware) for generating an indication of time.
- each of the terms ‘function’, ‘engine’, and ‘module’ refers to hardware, firmware, or software in combination with hardware and/or firmware for implementing features described herein.
- FIG. 1 is a block diagram illustrating an exemplary computing platform for modeling a clock according to an embodiment of the subject matter described herein;
- FIG. 2 is a timing diagram illustrating exemplary packets associated with modeling a clock according to an embodiment of the subject matter described herein;
- FIG. 3 is a message flow diagram illustrating exemplary communications associated with modeling a clock according to an embodiment of the subject matter described herein;
- FIG. 4 is a table illustrating exemplary data associated with modeling a clock according to an embodiment of the subject matter described herein;
- FIG. 5 is a flow chart illustrating an exemplary process for modeling a clock according to an embodiment of the subject matter described herein.
- a receiver node e.g., a device or endpoint
- a receiver node may be responsible for performing various traffic related measurements, such as measuring one-way latency or jitter.
- a receiver node may need to perform clock synchronization with one more sender nodes that send the streaming traffic.
- clocks of varying precisions may generate timestamps and/or other information that yield less than optimal traffic related measurements, such as a one-way latency measurement.
- a sender node may insert a transmit timestamp, based on a clock at the sender node, into each egress packet.
- a monitoring device may monitor egress packets (e.g., packets sent from the sender node) and may periodically or aperiodically (e.g., dynamically or continuously) generate and send clock related information usable for modeling a clock associated with the sender node to a receiver node or another entity for modeling the clock associated with the sender node.
- a receiver node e.g., a test system
- a ‘time-of-receipt’ timestamp associated with a relatively high precision clock of the receiver node may be generated.
- the receiver node may extract the ‘time-of-transmit’ timestamp from the packet and may apply a clock model so as to generate an adjusted ‘time-of-transmit’ timestamp that is correlated with the receiver node's high precision clock.
- a one-way latency measurement or other traffic related measurement may be more precise and/or accurate.
- mechanisms may be provided for implementing a clock model and/or for correlating (e.g., adjusting) timestamps associated with a first clock to a second clock.
- a clock model and/or timestamp correlation precision and/or accuracy of traffic related measurements may be improved over conventional methods.
- a distributed traffic measurement system may be implemented whereby various traffic measurements, including one-way latency, can be performed without requiring that all packets being sent to a single entity.
- FIG. 1 is a block diagram illustrating an exemplary computing platform 100 for modeling a clock according to an embodiment of the subject matter described herein.
- computing platform 100 may represent a node or device that includes functionality for testing various aspects of system under test (SUT) 110 , SUT 112 , and/or other nodes.
- SUT system under test
- computing platform 100 may receive traffic generated by SUT 112 and may perform traffic related measurements, such as jitter and one-way latency, associated with the traffic from SUT 112 .
- traffic related measurements such as jitter and one-way latency
- computing platform 100 may include a base clock 107 .
- Base clock 107 may represent any suitable entity for generating an indication of time.
- base clock 107 may be a high precision clock (e.g., relative to other clocks at SUT 110 and/or 112 ).
- base clock 107 may be synchronized with, shared with, and/or implemented by various modules, nodes, and/or entities associated with computing platform 100 .
- base clock 107 may be implemented by monitoring nodes 106 and 108 .
- computing platform 100 may include functionality for communicating with various entities.
- computing platform 100 may provide a communications interface or console for communicating with a user.
- a user may include an automated system or may be controlled or controllable by a human user.
- a user may select and/or determine traffic related measurements to perform, clock modeling preferences, and/or other configurations via one or more user interfaces associated with computing platform 100 .
- each of SUTs 110 and 112 may represent a network device, a network module, a node, or a system of devices, nodes, and/or modules.
- SUT 110 may be an endpoint located in a network (e.g., a private test network, a public network, or an enterprise network).
- each of SUTs 110 and 112 may be a single node or may include functionality distributed across multiple computing platforms or nodes.
- each of SUTs 110 and 112 may represent one or more virtual machines (VMs) executing at one or more computing platforms.
- SUT 110 may include three VMs, where each VM sends test traffic to computing platform 100 .
- each of SUTs 110 and 112 may include or access a clock, such as clock 114 or clock 116 .
- clocks 114 and 116 may represent any entity (e.g., software, hardware, and/or firmware) for generating an indication of time.
- each of clocks 114 and 116 may include an oscillator that operates at a particular frequency as well as software for generating timestamps based on oscillator clock pulses and a start time or an epoch.
- clock 114 may generate timestamps for packets sent from SUT 110 and clock 116 may generate timestamps for packets sent from SUT 112 .
- each of clocks 114 and 116 may be less precise than one or more other clocks, e.g., a clock at computing platform 100 .
- each VM may include a software-implemented clock that has a precision on the order of 16 milliseconds (ms), while computing platform 100 may have a clock with microsecond ( ⁇ s) precision.
- computing platform 100 may communicate with each other and/or other entities.
- SUTs 110 and 112 may be web servers or other entities that communicate with each other via a network.
- computing platform 100 may be a monitoring device for monitoring traffic between SUTs 110 and 112 .
- each of SUTs 110 and 112 may be web servers or other entities that communicate with computing platform 100 .
- computing platform 100 therein may include functionality for performing various traffic related measurements.
- computing platform 100 may receive a packet from SUT 112 and may perform a one-way latency measurement and/or a jitter measurement.
- timestamps and/or other clock related information may be usable for performing the measurements.
- computing platform 100 may include functionality for correlating timestamps associated with different clocks when performing various measurements. For example, computing platform 100 may receive a packet containing a ‘time-of-transmit’ timestamp based on clock 114 . In this example, at the time of receipt, computing platform 100 may generate a ‘time-of-receipt’ timestamp based on a clock at computing platform 100 . Continuing with this example, computing platform 100 may adjust one or more of these timestamps (e.g., using a correlated clock model) such that traffic measurements performed by computing platform 100 are more precise and/or accurate.
- timestamps e.g., using a correlated clock model
- computing platform 100 may include, utilize, and/or access a clock modeling module (CMM) 102 , also referred to as clock modeling system (CMS) and a clock modeling engine (CME).
- CMM 102 may represent any suitable entity or entities (e.g., a computing platform, software executing on a processor, a logic device, a module, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and/or an application specific integrated circuit (ASIC)) for performing one or more aspects associated with clock modeling.
- CMM clock modeling module
- CMS clock modeling system
- CME clock modeling engine
- CMM 102 may represent any suitable entity or entities (e.g., a computing platform, software executing on a processor, a logic device, a module, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and/or an application specific integrated circuit (ASIC)) for performing one or more aspects associated with clock modeling.
- CPLD complex programmable
- CMM 102 may include one or more communications interfaces for communicating with monitoring modules 106 and 108 .
- Each of monitoring modules 106 and 108 may represent any entity (e.g., software, hardware, and/or firmware) for monitoring and/or copy packets and/or information therein.
- monitoring module 106 may act as a probe or tap device and may copy packet information as packets (e.g., from or to SUT 110 ) traverse monitoring module 106 and monitoring module 108 may act as a probe or tap device and may copy packet information as packets (e.g., from or to SUT 112 ) traverse monitoring module 108 .
- monitoring modules 106 and 108 may monitor VMs associated with SUTs 110 and 112 .
- monitoring module 106 may represent a probe that monitors packets sent from a VM that uses a software implemented clock for packet timestamps.
- monitoring modules 106 and 108 may include or access base clock 107 .
- each base clock 107 associated with monitoring modules 106 and 108 may be periodically or aperiodically (e.g., dynamically) synchronized with a base clock 107 at computing platform 100 or another entity.
- a common time source and a clock synchronization technique may be used to periodically synchronize base clocks 107 associated with various entities in FIG. 1 .
- monitoring modules 106 and 108 may include functionality for performing passive monitoring and/or active monitoring. For example, when performing passive monitoring, monitoring modules 106 and 108 may inspect traversing packets and may copy packets without modifying information therein and/or without affecting the flow of the original traffic. In another example, when performing active monitoring, monitoring modules 106 and 108 may inspect traversing packets and may modify information therein, e.g., adding, replacing or removing timestamps in the packet, and/or may affect the flow of the original traffic.
- monitoring modules 106 and 108 may include functionality for receiving commands or instructions from computing platform 100 , CMM 102 , and/or other entities.
- CMM 102 may instruct monitoring modules 106 and 108 to perform enhanced monitoring actions.
- Exemplary monitoring actions may include monitoring packets associated with a particular VM, a user, a session, a network, and/or based on other criteria.
- base clocks 107 associated with computing platform 100 and monitoring modules 106 and 108 may be more precise than clocks 114 and 116 .
- clock 114 may have a precision on the order of ms
- base clock 107 associated with monitoring module 106 may have a precision on the order of 100 ⁇ s.
- clock 114 has 1/10 th the precision of base clock 107 associated with monitoring module 106
- monitoring modules 106 and 108 may analyze packets or information therein for determining clock related information usable for modeling a clock.
- Exemplary clock related information may include includes a clock period scale factor value and a relative phase offset value for correlating the first clock and the second clock.
- monitoring module 106 may monitor packets sent from SUT 110 and may attempt to correlate timestamps (e.g., based on clock 114 ) in the packets with base clock 107 associated with monitoring module 106 .
- monitoring module 106 may calculate a clock period scale factor value by measuring how many clock periods (e.g., smallest clock increments) of base clock 107 occurred during a single clock period of clock 114 as indicated by an incremental change in timestamps of monitored packets from the SUT 110 . Additional exemplary correlation details are disclosed below with regard to FIG. 2 .
- monitoring modules 106 and 108 may send the clock related information to CMM 102 and/or computing platform 100 .
- CMM 102 and/or computing platform 100 may use the clock related information for implementing and/or recalibrating a clock model.
- CMM 102 may receive clock related information about clock 114 (e.g., from monitoring module 106 ) and may implement a corresponding clock model 118 .
- CMM 102 may receive clock related information about clock 116 (e.g., from monitoring module 108 ) and may implement a corresponding clock model 120 .
- each of clock models 118 and 120 may represent any suitable entity for implementing or providing a linear model or a piecewise linear model of a remote clock (e.g., a clock not at the implementing node).
- clock model 118 may be periodically or aperiodically adjusted and/or reconfigured to resemble clock 114 .
- clock model 118 may provide a substantially linear approximation of the time at clock 114 .
- clock model 118 may represent a higher precision version of clock 114 and/or clock model 120 may represent a higher precision version of clock 116 .
- computing platform 100 and/or a related entity may use clock model 118 to add additional precision to a timestamp associated with clock 114 .
- computing platform 100 and/or a related entity may use clock models 118 and 120 for performing more precise and/or accurate traffic related measurements.
- clock model 120 may be used to generate, adjust, or recreate timestamps associated with clock 116 .
- computing platform 100 may use clock model 120 to increase the precision of the ‘time-of-transmit’ timestamp and may adjust the timestamp from ‘3453’ to ‘3452.978’.
- computing platform 100 and/or a related entity may use this adjusted timestamp along with one or more other timestamps from more precise clocks when performing various traffic related measurements.
- computing platform 100 may compute confidence values for indicating how likely a clock model is to be accurate.
- computing platform 100 , CMM 102 , and/or a related entity may initiate actions for enhance or additional monitoring. For example, computing platform 100 , CMM 102 , and/or a related entity may compare measurements to predetermined threshold values. In this example, if measurements meet or exceed the threshold values, computing platform 100 , CMM 102 , and/or a related entity may trigger one or more monitoring performance actions.
- a monitoring performance action may include instructing a monitoring module 106 to identify particular packets as they traverse monitoring module 106 and to send packet identifying information (e.g., a packet hash, a timestamp value, a sequence ID, and/or other unique identifiers) to computing platform 100 , CMM 102 , and/or a related entity for identifying (e.g., disambiguating) the particular packets at computing platform 100 and for generating more precise clock models and/or timestamps.
- packet identifying information e.g., a packet hash, a timestamp value, a sequence ID, and/or other unique identifiers
- packet identifying information e.g., a packet hash, a timestamp value, a sequence ID, and/or other unique identifiers
- packet identifying information e.g., a packet hash, a timestamp value, a sequence ID, and/or other unique identifiers
- monitoring module 106 may identify a packet for
- monitoring module 106 may generate a virtual tag (e.g., packet identifying information based on unique information in the packet) and may send the virtual tag, e.g., via a management network, from monitoring module 106 to computing platform 100 , CMM 102 , and/or a related entity.
- computing platform 100 , CMM 102 , and/or a related entity may use the received virtual tag for identifying (e.g., disambiguating) the particular packets and extracting or deriving relevant information usable for generating more precise clock models and/or timestamps.
- monitoring module 106 may generate a virtual tag and may incorporate the virtual tag into the packet before sending the packet from monitoring module 106 to computing platform 100 , CMM 102 , and/or a related entity.
- a monitoring performance action may include instructing a monitoring module 106 to modify particular packets as they traverse monitoring module 106 .
- monitoring module 106 may use modify layer 4-7 timestamp values and/or other parameters.
- monitoring module 106 may add additional information (e.g., a hardware implemented layer 4 timestamp parameter value) to the packet for improving precision and/or other purposes.
- a monitoring performance action may include instructing a monitoring module 106 to monitor and/or modify particular packets associated with a particular user, VM, or session.
- a user may experience various latency issues and may report these issues to a network operator.
- the network operator may instruct, via computing platform 100 or CMM 102 , monitoring module 106 and 108 to generate high precision timestamps as the packets traverse monitoring module 106 and 108 and provide these high precision timestamps to CMM 102 .
- CMM 102 may compare these high precision timestamps with timestamps that were stored in these packets (e.g., a less precise clock) and may perform adjustments to a relevant clock model at computing platform 100 .
- computing platform 100 and/or CMM 102 may include functionality for storing and/or maintaining clock related information (e.g., clock identifiers (IDs), clock period scale factor values, relative phase offset values, confidence values, packet IDs, and/or update flags) for one or more clocks.
- clock related information e.g., clock identifiers (IDs), clock period scale factor values, relative phase offset values, confidence values, packet IDs, and/or update flags
- CMM 102 at computing platform 100 may maintain clock related information, such as a clock period scale factor value and a relative phase offset value, for each of a plurality of clock models, such as clock models 118 and 120 .
- CMM 102 may store clock related information and/or other information at CMM storage 104 .
- CMM storage 104 may represent any suitable entity (e.g., a non-transitory computer readable medium or a memory device) for storing clock related information and/or other information.
- Exemplary data stored at CMM storage 104 may include traffic related information, traffic related measurements, timers related to clock leases, clock related information (e.g., clocks associated with one or more nodes), clock synchronization preferences or settings, clock drift algorithms, and/or other information.
- CMM storage 104 may be integrated with or accessible by CMM 102 , computing platform 100 , or modules therein. In some embodiments, CMM storage 104 may be located at a node distinct from CMM 102 or computing platform 100 .
- FIG. 1 is for illustrative purposes and that various nodes, their locations, and/or their functions described above in relation to FIG. 1 may be changed, altered, added, or removed. For example, some nodes (e.g., CMM 102 and monitoring module 106 ) and/or functions described herein may be combined into a single entity.
- some nodes e.g., CMM 102 and monitoring module 106
- functions described herein may be combined into a single entity.
- FIG. 2 is a timing diagram illustrating exemplary packets associated with modeling a clock according to an embodiment of the subject matter described herein.
- monitoring modules 106 and 108 may monitor packets sent from SUTs 110 and 112 .
- packets may be monitored for obtaining and/or deriving clock related information usable to implement a clock model associated with clock 114 and/or clock 116 .
- each base clock 107 associated with monitoring modules 106 and 108 may represent a high precision clock, e.g., a clock having a higher precision than clock 114 or clock 116 .
- monitoring modules 106 and 108 may use base clocks 107 when determining a clock period scale factor value and/or a relative phase offset value associated with clock models 118 and 120 .
- base clocks 107 associated with monitoring modules 106 and 108 may be synchronized using a central time server or other mechanisms and may also be synchronized with a clock (e.g., at a receive port) at computing platform 100 .
- monitoring module 106 may be configured to compute a clock period scale factor value by comparing timestamp values in packets 200 - 206 from SUT 110 to a high precision clock time values (e.g., clock ticks associated with base clock 107 ).
- Each of packets 200 - 206 may include a timestamp parameter value (e.g., a transmission control protocol (TCP) timestamp value) indicating a number of ms that have elapsed since a particular reference time.
- TCP transmission control protocol
- Clock related timestamp interval 208 may represent an amount of time between a change or increment in a timestamp parameter value in monitored packets. Clock related timestamp interval 208 may be usable in computing or determining a clock period scale factor value and/or other related information. In some embodiments, monitoring module 106 may attempt to identify two packets that most accurately represent one or more intervals or increments in time by detecting a change in timestamp parameter values among packets 200 - 206 . For example, monitoring module 106 may select packet 202 by identifying, in a stream of packets, the first packet to include a timestamp that has incremented by one from an immediately preceding packet.
- monitoring module 106 may identify packet 206 by identifying, in a stream of subsequent packets after packet 200 , the first packet to include a timestamp that has incremented by 1 from packet 200 .
- High precision clock time interval 210 may represent an amount of time that has occurred during timestamp interval 208 .
- monitoring module 106 may use base clock 107 (e.g., a high precision clock) to determine that an amount of time between packet 202 and packet 206 .
- base clock 107 e.g., a high precision clock
- high precision clock time interval 210 may be 500, e.g., the absolute difference between when packet 202 traversed (e.g., 400 ⁇ s) monitoring module 106 and when packet 206 arrived (e.g., 900 ⁇ s) monitoring module 106 .
- a relative phase offset value may be computed.
- monitoring module 106 may provide this information and/or other clock related information to CMM 102 for implementing a clock model. For example, after determining a clock period scale factor value and a relative phase offset value related to clock 114 , monitoring module 106 may send the information to CMM 102 for implementing clock model 118 .
- various techniques for averaging or smoothing out jitter and/or other anomalies in clock related information may be utilized.
- a digital filter may be used to smooth out the ticks of clock 114 and/or a high precision clock associated with monitoring module 106
- FIG. 2 is for illustrative purposes and that additional and/or different information may use for determining or deriving clock related information.
- a clock period scale factor value may be determined using packets 202 and 206
- a clock period scale factor value and/or a relative phase offset value may be determined using other packets, such as packets 200 and 204 , packets 204 and 206 , or packets 200 and 206 .
- FIG. 3 is a message flow diagram illustrating exemplary communications associated with modeling a clock according to an embodiment of the subject matter described herein.
- SUT 110 may include a traffic generator or any functionality for generating and sending traffic to computing platform 100 .
- packets may be generated at SUT 110 .
- Each of the packets may include a timestamp added by and/or associated with clock 114 .
- each packet may be a TCP packet and may include a timestamp parameter value representing a number of ms since the start of a reference time.
- the packets may be sent from SUT 110 towards computing platform 100 .
- packets may be sent from SUT 110 via a port or path associated with computing platform 100 .
- the packets may be monitored as the packets traverse monitoring module 106 and clock related information for implementing a clock model associated with SUT 110 may be generated, obtained, and/or derived using the packets. For example, a clock period scale factor value and a relative phase offset value associated with clock 114 may be determined by monitoring module 106 using base clock 107 .
- clock related information may be sent from monitoring module 106 to computing platform 100 .
- clock related information may be sent to CMM 102 .
- communications between monitoring module 106 and computing platform 100 may occur via a network (e.g., a management network) and/or path separate from a network or path use to send packets from SUT 110 to computing platform 100 .
- a network e.g., a management network
- the clock model may be implemented at computing platform 100 using the clock related information.
- CMM 102 may implement clock model 118 based on clock related information associated with clock 114 .
- the packets may be sent to computing platform 100 via monitoring module 106 .
- packets generated by SUT 110 may be sent to computing platform 100 .
- traffic related measurements may be performed using the clock model.
- the clock model may be usable to generate a higher precision timestamp from a timestamp received in a packet.
- computing platform 100 and/or a related entity may generate an adjusted timestamp using a ‘time-of-transmit’ timestamp from a received packet and the clock model.
- computing platform 100 and/or a related entity may compute one-way latency by subtracting the adjusted timestamp from a ‘time-of-receipt’ timestamp generated by a high precision clock at computing platform 100 .
- steps 3003 - 3005 may be omitted in some instance and/or may occur periodically. It will also be appreciated that various actions described herein may occur in a different order or sequence. For example, steps 3003 , 3004 , and/or 3005 may occur before or concurrently with step 3006 .
- FIG. 4 is a table illustrating exemplary data associated with modeling a clock according to an embodiment of the subject matter described herein.
- Data 400 may include any suitable clock related information, such as clock identifiers (IDs), clock period scale factor values, relative phase offset values, confidence values, packet IDs, and/or update flags, for generating a clock model and/or correlating two clocks.
- IDs clock identifiers
- data 400 may be obtained or derived from CMM 102 , monitoring module 106 , monitoring module 108 , and/or other sources.
- data 400 may be accessed by computing platform 100 , CMM 102 , and/or another entity and may be stored using various data structures (e.g., in CMM storage 104 ).
- data 400 may be depicted using one or more data structures representing associations between clock IDs and various types of clock related information, including clock period scale factor values, relative phase offset values, confidence values, packet IDs, and/or update flags.
- data 400 may include information that identifies or represents clock models associated with particular SUTs.
- each clock ID may be represented by a SUT or related node identifier and/or other identifying information.
- data 400 may include information that identifies or represents clock period scale factor values associated with particular clock models.
- each clock period scale factor value may be an integer value, such as ‘500’, ‘400’, ‘100’, or ‘1000’.
- data 400 may include information that identifies or represents relative phase offset values associated with particular clock models.
- each relative phase offset value may be an integer value, such as ‘ ⁇ 2200’, ‘4598’, ‘200’, or ‘ ⁇ 200’.
- data 400 may include information that identifies or represents a confidence value indicating how likely particular clock models are to be accurate.
- each confidence value may be an integer value ranging from 0 to 100, such as ‘95’, ‘80’, ‘40’, or ‘25’.
- data 400 may include information that identifies or represents one or more packet IDs for identifying particular packets for obtaining additional clock related information.
- each packet IDs value may indicate one or more portions of a packet for uniquely identifier the packet, such as ‘a sequence number and a hash value of packet’, ‘a sequence number and a timestamp parameter value’, or ‘a sequence number and a timestamp parameter value’.
- data 400 may include information that indicates whether a clock model is becoming inaccurate and/or should be updated or recalibrated.
- ‘UPDATE FLAG’ data may be represented as a Boolean value in FIG. 4
- information in various forms may be stored for determining whether to update particular clock models and/or to retrieve additional clock related information.
- another indicator in data 400 may indicate whether to perform a special packet-based clock model (re)calibration, e.g., by tracking and/or correlating clock related information associated with one or more particular packets (e.g., as indicated by packet IDs).
- a special packet-based clock model (re)calibration e.g., by tracking and/or correlating clock related information associated with one or more particular packets (e.g., as indicated by packet IDs).
- data 400 is for illustrative purposes and that different and/or additional information may be used for performing aspects associated with clock modeling.
- FIG. 5 is a flow chart illustrating an exemplary process 500 for modeling a clock according to an embodiment of the subject matter described herein.
- exemplary process 500 may be performed by or at computing platform 100 , CMM 102 , monitoring module 106 , monitoring module 108 , SUT 110 , SUT 112 , and/or another node or module.
- exemplary process 500 may include steps 502 , 504 , and 506 .
- steps 502 , 504 , and 506 may occur at or be performed by a monitoring module (e.g., monitoring module 106 ) associated with a first node (e.g., computing platform 100 ).
- a monitoring module e.g., monitoring module 106
- first node e.g., computing platform 100
- step 502 packets from a second node may be received.
- step 504 timestamps from at least two of the packets may be extracted.
- clock related information for generating a local clock model may be generated using the timestamps.
- the local clock model may be indicative of a precision of a local clock at the first node relative to a clock at the second node.
- an entity for implementing and/or using a clock model may be configured to receive a first packet containing a transmit timestamp associated with a second node (e.g., SUT 110 ), to generate a receipt timestamp indicating when the first packet is received at the first node, to generate, using the clock model and the transmit timestamp, a time representation associated with the transmit timestamp that is more precise than the transmit timestamp, and to perform a traffic related measurement using the time representation or the clock model.
- performing a traffic related measurement may include computing one-way latency, jitter, and/or another traffic related measurement.
- computing one-way latency may include computing the difference between the receipt timestamp and the time representation.
- a node may be configured to perform a monitoring enhancement action in response to meeting or exceeding one or more threshold values associated with a traffic related measurement or a confidence value associated with a clock model.
- performing a monitoring enhancement action may include initiating modification of a first packet, initiating modification of a transmit timestamp in the first packet with timestamp information associated with a first node or a clock model, initiating copying of the first packet, initiating timestamped copying of at least a portion of the first packet, initiating utilization of one or more test packets for testing a second node, the first node, or a communications path, or initiating monitoring of subsequent packets sent from the second node to the first node using packet identifiers.
- an implemented clock model may be adjusted aperiodically or periodically.
- clock related information may include a clock period scale factor value for indicating a number of clock periods associated with a first clock (e.g., a high precision clock or base clock 107 ) that occurs during a clock period associated with a second clock (e.g., a low precision clock or clock 114 ) and a relative phase offset value for correlating the first clock and the second clock.
- a clock period scale factor value for indicating a number of clock periods associated with a first clock (e.g., a high precision clock or base clock 107 ) that occurs during a clock period associated with a second clock (e.g., a low precision clock or clock 114 ) and a relative phase offset value for correlating the first clock and the second clock.
- a first node e.g., computing platform 100
- a second node e.g., SUT 110 or SUT 112
- implementing a clock model may include implementing a linear model or a piecewise linear model of a high precision clock based on a low precision clock.
- exemplary process 500 is for illustrative purposes and that different and/or additional actions may be used. It will also be appreciated that various actions described herein may occur in a different order or sequence.
- computing platform 100 , CMM 102 , monitoring module 106 , monitoring module 108 , and/or functionality described herein may constitute a special purpose computing device. Further, computing platform 100 , CMM 102 , monitoring module 106 , monitoring module 108 , and/or functionality described herein can improve the technological field of passive monitoring of network nodes and/or related measurement systems (e.g., testing platforms) by providing mechanisms for modeling a clock and/or for using the clock model or related information to increase or improve precision and/or accuracy of traffic related measurements.
- network nodes and/or related measurement systems e.g., testing platforms
Abstract
Description
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/819,337 US9813226B2 (en) | 2015-08-05 | 2015-08-05 | Modeling a clock |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/819,337 US9813226B2 (en) | 2015-08-05 | 2015-08-05 | Modeling a clock |
Publications (2)
Publication Number | Publication Date |
---|---|
US20170041126A1 US20170041126A1 (en) | 2017-02-09 |
US9813226B2 true US9813226B2 (en) | 2017-11-07 |
Family
ID=58052746
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/819,337 Active 2035-12-18 US9813226B2 (en) | 2015-08-05 | 2015-08-05 | Modeling a clock |
Country Status (1)
Country | Link |
---|---|
US (1) | US9813226B2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10019333B2 (en) | 2015-04-16 | 2018-07-10 | Keysight Technologies Singapore (Holdings) Pte. Ltd. | Methods, systems, and computer readable media for emulating network devices with different clocks |
US10409321B2 (en) * | 2017-02-03 | 2019-09-10 | Raytheon Company | Simulation system with clock and messaging synchronization |
US10425321B2 (en) | 2017-04-25 | 2019-09-24 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Methods, systems, and computer readable media for testing time sensitive network (TSN) elements |
US10609054B2 (en) | 2017-04-07 | 2020-03-31 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Methods, systems, and computer readable media for monitoring, adjusting, and utilizing latency associated with accessing distributed computing resources |
US10965392B2 (en) | 2019-01-25 | 2021-03-30 | Keysight Technologies, Inc. | Active network tap supporting time sensitive network (TSN) standards |
US11563768B2 (en) | 2019-01-31 | 2023-01-24 | Keysight Technologies, Inc. | Methods, systems, and computer readable media for detecting and mitigating effects of timing attacks in time sensitive networks |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9736804B2 (en) | 2015-04-16 | 2017-08-15 | Ixia | Methods, systems, and computer readable media for synchronizing timing among network interface cards (NICS) in a network equipment test device |
RO131471A2 (en) | 2015-04-21 | 2016-10-28 | Ixia, A California Corporation | Methods, systems and computer-readable media for testing quality of recovered clock |
US9800595B2 (en) | 2015-09-21 | 2017-10-24 | Ixia | Methods, systems, and computer readable media for detecting physical link intrusions |
WO2018186876A1 (en) | 2017-04-07 | 2018-10-11 | Intel Corporation | Technologies for high-precision timestamping of packets |
JP6528807B2 (en) * | 2017-06-28 | 2019-06-12 | オムロン株式会社 | Control system, control device, coupling method and program |
US11153191B2 (en) | 2018-01-19 | 2021-10-19 | Intel Corporation | Technologies for timestamping with error correction |
US11503005B2 (en) * | 2018-11-09 | 2022-11-15 | Ge Aviation Systems Limited | Tool verification system and method of verifying an unqualified component |
US11265096B2 (en) | 2019-05-13 | 2022-03-01 | Intel Corporation | High accuracy time stamping for multi-lane ports |
GB201911378D0 (en) * | 2019-08-08 | 2019-09-25 | Hoptroff Richard George | System for timestamping events on edge devices |
US11271851B2 (en) * | 2020-02-10 | 2022-03-08 | Syntropy Network Limited | System and method for autonomous selection of routing paths in a computer network |
Citations (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030105976A1 (en) | 2000-11-30 | 2003-06-05 | Copeland John A. | Flow-based detection of network intrusions |
US20030200483A1 (en) | 2002-04-23 | 2003-10-23 | Sutton Christopher K. | Electronic test program that can distinguish results |
US20040190547A1 (en) | 2003-03-31 | 2004-09-30 | Gordy Stephen C. | Network tap with integrated circuitry |
US6868069B2 (en) | 2001-01-16 | 2005-03-15 | Networks Associates Technology, Inc. | Method and apparatus for passively calculating latency for a network appliance |
US7092586B2 (en) | 2003-07-18 | 2006-08-15 | Network Integrity Systems Inc. | Intrusion detection system for use on an optical fiber using a translator of transmitted data for optimum monitoring conditions |
US20070268938A1 (en) | 2006-05-19 | 2007-11-22 | Dowd Gregory Louis | Network time protocol precision timestamping service |
US20090231191A1 (en) | 2008-03-17 | 2009-09-17 | Wi-Lan, Inc. | Systems and methods for distributing GPS clock to communications devices |
US7881209B2 (en) | 2006-07-27 | 2011-02-01 | Cisco Technology, Inc. | Method and system for protecting communication networks from physically compromised communications |
US20110170534A1 (en) | 2010-01-11 | 2011-07-14 | Faro Technologies, Inc. | Method and apparatus for synchronizing measurements taken by multiple metrology devices |
US20110199133A1 (en) | 2008-09-05 | 2011-08-18 | Advantest Corporation | Test apparatus and test method |
US20110211473A1 (en) | 2010-02-28 | 2011-09-01 | Eldad Matityahu | Time machine device and methods thereof |
US20110268097A1 (en) * | 2010-03-12 | 2011-11-03 | University Of Maryland | Method and system for adaptive synchronization of timing information generated by independently clocked communication nodes |
WO2011144263A1 (en) | 2010-05-17 | 2011-11-24 | Telefonaktiebolaget L M Ericsson (Publ) | Optimizing timing packet transport |
US20120166327A1 (en) | 2010-12-22 | 2012-06-28 | HyannisPort Research | Data capture and real time risk controls for electronic markets |
US20120275317A1 (en) | 2011-04-29 | 2012-11-01 | Rad Data Communications Ltd. | Timing over packet demarcation entity |
US20130080817A1 (en) | 2011-07-20 | 2013-03-28 | Janez Mihelic | Systems and Methods of Network Synchronization |
US20130094515A1 (en) | 2011-08-31 | 2013-04-18 | Nils Gura | Systems, apparatus, and methods for removing duplicate data packets from a traffic flow of captured data packets transmitted via a communication network |
US20130173778A1 (en) | 2011-12-30 | 2013-07-04 | Bmc Software, Inc. | Monitoring network performance remotely |
US20130212439A1 (en) | 2012-02-15 | 2013-08-15 | Michael Stevens | Method and system for network monitoring using signature packets |
US20130259049A1 (en) | 2012-02-09 | 2013-10-03 | Marvell Israel (M.I.S.L) Ltd. | Clock synchronization using multiple network paths |
US20130265886A1 (en) | 2011-09-30 | 2013-10-10 | Gigamon Llc | Systems and methods for implementing a traffic visibility network |
US20130278312A1 (en) | 2012-04-23 | 2013-10-24 | Analog Devices, Inc. | Synchronization of multiple signal converters |
US20130329595A1 (en) | 2011-02-22 | 2013-12-12 | Voipfuture Gmbh | Voip quality measurement enhancements using the internet control message protocol |
US20130347103A1 (en) | 2012-06-21 | 2013-12-26 | Mark Veteikis | Packet capture for error tracking |
US20130343207A1 (en) | 2012-06-21 | 2013-12-26 | Brent Aaron Cook | Dynamic latency analysis system |
US20140006610A1 (en) | 2012-07-02 | 2014-01-02 | Datacom Systems, Inc. | Real-time highly accurate network latency measurement with low generated traffic or data requirements |
US8718482B1 (en) | 2009-11-10 | 2014-05-06 | Calix, Inc. | Transparent clock for precision timing distribution |
US8767565B2 (en) | 2008-10-17 | 2014-07-01 | Ixia | Flexible network test apparatus |
US20140185632A1 (en) | 2011-05-06 | 2014-07-03 | Fts Computertechnik Gmbh | Network and Method for Implementing a High-Availability Grand Master Clock |
US20140297852A1 (en) | 2011-12-21 | 2014-10-02 | Fujitsu Limited | Information processing apparatus and method therefor |
US20140317288A1 (en) | 2012-01-05 | 2014-10-23 | VolP Future GmbH | Determination of a quality induced termination rate of communication sessions |
US20140321285A1 (en) | 2013-04-25 | 2014-10-30 | Ixia | Distributed network test system |
US20140344930A1 (en) | 2013-05-17 | 2014-11-20 | Cisco Technology, Inc. | Network Eavesdropping Detection |
US20150016274A1 (en) | 2013-07-09 | 2015-01-15 | Cellco Partnership D/B/A Verizon Wireless | Monitoring of the packet-based communication performance of ip address pools |
US20150023168A1 (en) | 2013-07-18 | 2015-01-22 | Verizon Patent And Licensing Inc. | Dynamic network traffic analysis and traffic flow configuration for radio networks |
US20150023170A1 (en) | 2013-07-19 | 2015-01-22 | Cellco Partnership D/B/A Verizon Wireless | Traffic measurement system for wireless service providers |
US9130945B2 (en) | 2012-10-12 | 2015-09-08 | Schweitzer Engineering Laboratories, Inc. | Detection and response to unauthorized access to a communication device |
US20150281025A1 (en) | 2012-11-02 | 2015-10-01 | Voipfuture Gmbh | Detection of periodic impairments in media streams |
US20160065434A1 (en) | 2014-09-02 | 2016-03-03 | Tektronix, Inc. | Methods and devices to efficiently determine node delay in a communication network |
US20160110211A1 (en) | 2014-10-15 | 2016-04-21 | Anue Systems, Inc. | Methods And Systems For Forwarding Network Packets Within Virtual Machine Host Systems |
US9380070B1 (en) | 2015-01-20 | 2016-06-28 | Cisco Technology, Inc. | Intrusion detection mechanism |
US20160285575A1 (en) | 2015-03-25 | 2016-09-29 | Ontime Networks As | Time-stamping data packets in a network tap element |
US20160301589A1 (en) | 2015-04-10 | 2016-10-13 | Ixia | Methods, systems, and computer readable media for one-way link delay measurement |
US20160301599A1 (en) | 2013-11-19 | 2016-10-13 | Telefonaktiebolaget L M Ericsson (Publ) | Method and first network node for managing a first ip path used by a connection |
US20160306726A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for emulating network devices with different clocks |
US20160309434A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for synchronizing timing among network interface cards (nics) in a network equipment test device |
US20160315756A1 (en) | 2015-04-21 | 2016-10-27 | Ixia | Methods, systems, and computer readable media for testing recovered clock quality |
US20170085581A1 (en) | 2015-09-21 | 2017-03-23 | Ixia | Methods, systems, and computer readable media for detecting physical link intrusions |
-
2015
- 2015-08-05 US US14/819,337 patent/US9813226B2/en active Active
Patent Citations (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030105976A1 (en) | 2000-11-30 | 2003-06-05 | Copeland John A. | Flow-based detection of network intrusions |
US6868069B2 (en) | 2001-01-16 | 2005-03-15 | Networks Associates Technology, Inc. | Method and apparatus for passively calculating latency for a network appliance |
US20030200483A1 (en) | 2002-04-23 | 2003-10-23 | Sutton Christopher K. | Electronic test program that can distinguish results |
US20040190547A1 (en) | 2003-03-31 | 2004-09-30 | Gordy Stephen C. | Network tap with integrated circuitry |
US7092586B2 (en) | 2003-07-18 | 2006-08-15 | Network Integrity Systems Inc. | Intrusion detection system for use on an optical fiber using a translator of transmitted data for optimum monitoring conditions |
US20070268938A1 (en) | 2006-05-19 | 2007-11-22 | Dowd Gregory Louis | Network time protocol precision timestamping service |
US7881209B2 (en) | 2006-07-27 | 2011-02-01 | Cisco Technology, Inc. | Method and system for protecting communication networks from physically compromised communications |
US20090231191A1 (en) | 2008-03-17 | 2009-09-17 | Wi-Lan, Inc. | Systems and methods for distributing GPS clock to communications devices |
US20110199133A1 (en) | 2008-09-05 | 2011-08-18 | Advantest Corporation | Test apparatus and test method |
US8767565B2 (en) | 2008-10-17 | 2014-07-01 | Ixia | Flexible network test apparatus |
US8718482B1 (en) | 2009-11-10 | 2014-05-06 | Calix, Inc. | Transparent clock for precision timing distribution |
US20110170534A1 (en) | 2010-01-11 | 2011-07-14 | Faro Technologies, Inc. | Method and apparatus for synchronizing measurements taken by multiple metrology devices |
US20110211473A1 (en) | 2010-02-28 | 2011-09-01 | Eldad Matityahu | Time machine device and methods thereof |
US20110268097A1 (en) * | 2010-03-12 | 2011-11-03 | University Of Maryland | Method and system for adaptive synchronization of timing information generated by independently clocked communication nodes |
WO2011144263A1 (en) | 2010-05-17 | 2011-11-24 | Telefonaktiebolaget L M Ericsson (Publ) | Optimizing timing packet transport |
US20120166327A1 (en) | 2010-12-22 | 2012-06-28 | HyannisPort Research | Data capture and real time risk controls for electronic markets |
US20130329595A1 (en) | 2011-02-22 | 2013-12-12 | Voipfuture Gmbh | Voip quality measurement enhancements using the internet control message protocol |
US20120275317A1 (en) | 2011-04-29 | 2012-11-01 | Rad Data Communications Ltd. | Timing over packet demarcation entity |
US20140185632A1 (en) | 2011-05-06 | 2014-07-03 | Fts Computertechnik Gmbh | Network and Method for Implementing a High-Availability Grand Master Clock |
US20130080817A1 (en) | 2011-07-20 | 2013-03-28 | Janez Mihelic | Systems and Methods of Network Synchronization |
US20130094515A1 (en) | 2011-08-31 | 2013-04-18 | Nils Gura | Systems, apparatus, and methods for removing duplicate data packets from a traffic flow of captured data packets transmitted via a communication network |
US20130265886A1 (en) | 2011-09-30 | 2013-10-10 | Gigamon Llc | Systems and methods for implementing a traffic visibility network |
US20140297852A1 (en) | 2011-12-21 | 2014-10-02 | Fujitsu Limited | Information processing apparatus and method therefor |
US20130173778A1 (en) | 2011-12-30 | 2013-07-04 | Bmc Software, Inc. | Monitoring network performance remotely |
US20140317288A1 (en) | 2012-01-05 | 2014-10-23 | VolP Future GmbH | Determination of a quality induced termination rate of communication sessions |
US20130259049A1 (en) | 2012-02-09 | 2013-10-03 | Marvell Israel (M.I.S.L) Ltd. | Clock synchronization using multiple network paths |
US20130212439A1 (en) | 2012-02-15 | 2013-08-15 | Michael Stevens | Method and system for network monitoring using signature packets |
US20130278312A1 (en) | 2012-04-23 | 2013-10-24 | Analog Devices, Inc. | Synchronization of multiple signal converters |
US20130343207A1 (en) | 2012-06-21 | 2013-12-26 | Brent Aaron Cook | Dynamic latency analysis system |
US20130347103A1 (en) | 2012-06-21 | 2013-12-26 | Mark Veteikis | Packet capture for error tracking |
US20140006610A1 (en) | 2012-07-02 | 2014-01-02 | Datacom Systems, Inc. | Real-time highly accurate network latency measurement with low generated traffic or data requirements |
US9130945B2 (en) | 2012-10-12 | 2015-09-08 | Schweitzer Engineering Laboratories, Inc. | Detection and response to unauthorized access to a communication device |
US20150281025A1 (en) | 2012-11-02 | 2015-10-01 | Voipfuture Gmbh | Detection of periodic impairments in media streams |
US20140321285A1 (en) | 2013-04-25 | 2014-10-30 | Ixia | Distributed network test system |
US20140344930A1 (en) | 2013-05-17 | 2014-11-20 | Cisco Technology, Inc. | Network Eavesdropping Detection |
US20150016274A1 (en) | 2013-07-09 | 2015-01-15 | Cellco Partnership D/B/A Verizon Wireless | Monitoring of the packet-based communication performance of ip address pools |
US20150023168A1 (en) | 2013-07-18 | 2015-01-22 | Verizon Patent And Licensing Inc. | Dynamic network traffic analysis and traffic flow configuration for radio networks |
US20150023170A1 (en) | 2013-07-19 | 2015-01-22 | Cellco Partnership D/B/A Verizon Wireless | Traffic measurement system for wireless service providers |
US20160301599A1 (en) | 2013-11-19 | 2016-10-13 | Telefonaktiebolaget L M Ericsson (Publ) | Method and first network node for managing a first ip path used by a connection |
US20160065434A1 (en) | 2014-09-02 | 2016-03-03 | Tektronix, Inc. | Methods and devices to efficiently determine node delay in a communication network |
US20160110211A1 (en) | 2014-10-15 | 2016-04-21 | Anue Systems, Inc. | Methods And Systems For Forwarding Network Packets Within Virtual Machine Host Systems |
US9380070B1 (en) | 2015-01-20 | 2016-06-28 | Cisco Technology, Inc. | Intrusion detection mechanism |
US20160285575A1 (en) | 2015-03-25 | 2016-09-29 | Ontime Networks As | Time-stamping data packets in a network tap element |
US20160301589A1 (en) | 2015-04-10 | 2016-10-13 | Ixia | Methods, systems, and computer readable media for one-way link delay measurement |
US20160306726A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for emulating network devices with different clocks |
US20160309434A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for synchronizing timing among network interface cards (nics) in a network equipment test device |
WO2016168064A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for emulating network devices with different clocks |
WO2016168063A1 (en) | 2015-04-16 | 2016-10-20 | Ixia | Methods, systems, and computer readable media for synchronizing timing among network interface cards (nics) in a network equipment test device |
US20160315756A1 (en) | 2015-04-21 | 2016-10-27 | Ixia | Methods, systems, and computer readable media for testing recovered clock quality |
US20170085581A1 (en) | 2015-09-21 | 2017-03-23 | Ixia | Methods, systems, and computer readable media for detecting physical link intrusions |
WO2017052714A1 (en) | 2015-09-21 | 2017-03-30 | Ixia | Methods, systems, and computer readable media for detecting physical link intrusions |
Non-Patent Citations (32)
Title |
---|
"AN-1838 IEEE 1588 Boundary Clock and Transparent Clock Implementation Using the DP83640," Application Report, Texas Instruments, pp. 1-9 (Apr. 2013). |
"External Bypass Switches," Ixia, White Paper, 915-6688-01 Rev. B, pp. 1-5 (Dec. 2015). |
"High Density Modular Fiber Tap," Ixia, http://www.ixiacom.com/products/net-optics-flex-tap, pp. 1-4 (Jul. 2014). |
"Ixia Anue 3500-Mobile Backhaul Testing Solution," Ixia Data Sheet, pp. 1-5 (Dec. 2013). |
"Network Time Protocol," Wikipedia, https://en.wikipedia.org/wiki/Network-Time-Protocol, pp. 1-7 (Jul. 3, 2015). |
"Ixia Anue 3500—Mobile Backhaul Testing Solution," Ixia Data Sheet, pp. 1-5 (Dec. 2013). |
"Network Time Protocol," Wikipedia, https://en.wikipedia.org/wiki/Network—Time—Protocol, pp. 1-7 (Jul. 3, 2015). |
Arnold, "What Are All of These IEEE 1588 Clock Types," http://blog.meinbergglobal.com/2013/10/21/ieee1588clocktypes/, News and Tutorials from Meinberg, pp. 1-6 (Oct. 21, 2013). |
Commonly-assigned, co-pending International Application No. PCT/US16/40532 for "Methods, Systems, and Computer Readable Media for Detecting Physical Link Intrusions," (Unpublished, filed Jun. 30, 2016). |
Commonly-assigned, co-pending U.S. Appl. No. 14/685,552 for "Methods Systems, and Computer Readable Media for One-Way Link Delay Measurement," (Unpublished, filed Apr. 13, 2015). |
Commonly-assigned, co-pending U.S. Appl. No. 14/688,630 for "Methods, Systems, and Computer Readable Media for Synchronizing Timing Among Network Interface Cards (NICs) in a Network Equipment Test Device," (Unpublished, filed Apr. 16, 2015). |
Commonly-assigned, co-pending U.S. Appl. No. 14/688,644 for "Methods, Systems, and Computer Readable Media for Emulating Network Devices with Different Clocks," (Unpublished, filed Apr. 16, 2015). |
Commonly-assigned, co-pending U.S. Appl. No. 14/860,630 for "Methods, Systems, and Computer Readable Media for Detecting Physical Link Intrusions," (Unpublished, filed Sep. 21, 2015). |
Commonly-assigned, co-pending, U.S. Appl. No. 15/482,672 for "Methods, Systems, and Computer Readable Media for Monitoring, Adjusting, and Utilizing Latency Associated With Accessing Distributed Computing Resources," (Unpublished, filed Apr. 7, 2017). |
Eidson, "IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems-A Tutorial," Agilent Technologies, pp. 1-94 (Oct. 2005). |
Eidson, "IEEE-1588 Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems—A Tutorial," Agilent Technologies, pp. 1-94 (Oct. 2005). |
Final Office Action for U.S. Appl. No. 13/933,661 (Apr. 12, 2016). |
Non-Final Office Action for U.S. Appl. No. 13/933,661 (Dec. 14, 2015). |
Non-Final Office Action for U.S. Appl. No. 13/933,661 (Sep. 27, 2016). |
Non-Final Office Action for U.S. Appl. No. 14/685,552 (Oct. 20, 2016). |
Non-Final Office Action for U.S. Appl. No. 14/688,630 (Oct. 17, 2016). |
Non-Final Office Action for U.S. Appl. No. 14/809,513 (May 30, 2017). |
Non-Final Office Action for U.S. Appl. No. 14/860,360 (Dec. 19, 2016). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/933,661 (Feb. 17, 2017). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/685,552 (Mar. 1, 2017). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/688,630 (Apr. 12, 2017). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2016/026534 (Jul. 8, 2016). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2016/040523 (Sep. 12, 2016). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2016/040532 (Sep. 12, 2016). |
Notification of Transmittal of the International Searh report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2016/026533 (Jul. 8, 2016). |
Spirent, "Precision Time Protocol (PTP) IEEE 1588," YouTube "alantalkstech", https://www.youtube.com/watch?v=yw-gd01aOYg, pp. 1-11 (Dec. 7, 2011). |
Watt et al., "Understanding and Applying Precision Time Protocol," 14th Annual Clemson Univeristy Power Systems Conference, pp. 1-7 (Mar. 2015). |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10019333B2 (en) | 2015-04-16 | 2018-07-10 | Keysight Technologies Singapore (Holdings) Pte. Ltd. | Methods, systems, and computer readable media for emulating network devices with different clocks |
US10409321B2 (en) * | 2017-02-03 | 2019-09-10 | Raytheon Company | Simulation system with clock and messaging synchronization |
US10609054B2 (en) | 2017-04-07 | 2020-03-31 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Methods, systems, and computer readable media for monitoring, adjusting, and utilizing latency associated with accessing distributed computing resources |
US10425321B2 (en) | 2017-04-25 | 2019-09-24 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Methods, systems, and computer readable media for testing time sensitive network (TSN) elements |
US10623297B2 (en) | 2017-04-25 | 2020-04-14 | Keysight Technologies Singapore (Sales) Pte. Ltd. | Methods, systems, and computer readable media for testing scheduling fidelity in a time sensitive network |
US10965392B2 (en) | 2019-01-25 | 2021-03-30 | Keysight Technologies, Inc. | Active network tap supporting time sensitive network (TSN) standards |
US11563768B2 (en) | 2019-01-31 | 2023-01-24 | Keysight Technologies, Inc. | Methods, systems, and computer readable media for detecting and mitigating effects of timing attacks in time sensitive networks |
Also Published As
Publication number | Publication date |
---|---|
US20170041126A1 (en) | 2017-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9813226B2 (en) | Modeling a clock | |
US9923656B2 (en) | Methods, systems, and computer readable media for testing recovered clock quality | |
US11838110B2 (en) | Method of remotely monitoring the timing performance of a PTP slave | |
US9306692B2 (en) | Method and device for assessing the performance of one or more packet synchronization services in a packet data transmission network | |
US9814008B2 (en) | Methods, systems, and computer readable media for receiving a clock synchronization message | |
US9736804B2 (en) | Methods, systems, and computer readable media for synchronizing timing among network interface cards (NICS) in a network equipment test device | |
Mani et al. | An architecture for IoT clock synchronization | |
US9401856B2 (en) | Latency monitoring function | |
Ferrari et al. | Experimental characterization of uncertainty sources in a software-only synchronization system | |
US20210328698A1 (en) | Clock synchronization method and apparatus, and storage medium | |
WO2016054884A1 (en) | Frequency deviation monitoring method, device and computer storage medium | |
WO2020135279A1 (en) | Clock synchronization method and apparatus and storage medium | |
CN102523263A (en) | Sharing access host quantity monitoring method, device thereof and system thereof | |
Li et al. | A security management architecture for time synchronization towards high precision networks | |
WO2017012337A1 (en) | Uplink time adjustment method and apparatus | |
EP2627040B1 (en) | Method for eliminating systematical error components in a set of one-way delay measurement results for communications between two or more computing systems in a communication network, apparatus for performing the method and computer program product | |
KR20190094499A (en) | apparatus for testing load capacity of ptp/ntp server | |
CN105530139B (en) | Self-checking method and device for 1588 equipment | |
Naik et al. | Methodology and Implementation for Monitoring Precise Time Synchronisation in TSN | |
JP2018157462A (en) | Log storage method | |
Ronen | Synchronization monitoring in IEEE1588 synchronization networks | |
Lin et al. | A fuzzy-based approach to remove clock skew and reset from one-way delay measurement | |
US20240056346A1 (en) | Mobile network synchronization domain anomaly identification and correlation | |
Novick et al. | Improving packet synchronization in an NTP server | |
Smith et al. | ARTT: A scalable approach for monitoring the quality of time in distributed systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: IXIA, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BERGERON, MATTHEW R.;REEL/FRAME:036777/0001 Effective date: 20150930 |
|
AS | Assignment |
Owner name: KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IXIA;REEL/FRAME:044222/0695 Effective date: 20170930 Owner name: KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:IXIA;REEL/FRAME:044222/0695 Effective date: 20170930 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: KEYSIGHT TECHNOLOGIES SINGAPORE (SALES) PTE. LTD., Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LTD.;REEL/FRAME:048225/0065 Effective date: 20181001 Owner name: KEYSIGHT TECHNOLOGIES SINGAPORE (SALES) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KEYSIGHT TECHNOLOGIES SINGAPORE (HOLDINGS) PTE. LTD.;REEL/FRAME:048225/0065 Effective date: 20181001 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |