Maintaining consistent measurement intervals of MEF 35.1 performance monitoring (PM) sessions in a history database

A non-transitory computer-readable medium configured to store computer logic having instructions that, when executed, cause one or more processing devices to:

• obtain Performance Monitoring (PM) data during a current Measurement Interval of an ongoing PM session in accordance with the Metro Ethernet Forum (MEF) 35.1 standard, wherein the PM data is configured to be locally stored as a current dataset to be reported at the end of the current Measurement Interval for storage in a history database,
• following an interruption event that interrupts at least the current Measurement Interval, detect a recommencement event that clears the interruption event and allows a PM session to resume,
• determine a number of Measurement Intervals affected by the interruption event based on an end time of a last-reported Measurement Interval, and
• insert the number of affected Measurement Intervals into the history database after the last-reported Measurement Interval,
• wherein each of the Measurement Intervals includes PM data obtained during a predetermined time period, and wherein an end time of one of a particular Measurement Interval aligns with a start time of a subsequent Measurement Interval to eliminate gaps in the history database, and wherein the instructions further cause the one or more processing devices to set a suspect flag associated with each of the affected Measurement Intervals.

A method comprising the steps of:

• obtaining Performance Monitoring (PM) data during a current Measurement Interval of an ongoing PM session in accordance with the Metro Ethernet Forum (MEF) 35.1 standard, wherein the PM data is configured to be locally stored as a current dataset to be reported at the end of the current Measurement Interval for storage in a history database;
• following an interruption event that interrupts at least the current Measurement Interval, detecting a recommencement event that clears the interruption event and allows a PM session to resume;
• determining a number of Measurement Intervals affected by the interruption event based on an end time of a last-reported Measurement Interval, and
• inserting the number of affected Measurement Intervals into the history database after the last-reported Measurement Interval,
• wherein each of the Measurement Intervals includes PM data obtained during a predetermined time period, wherein an end time of one of a particular Measurement Interval aligns with a start time of a subsequent Measurement Interval to eliminate gaps in the history database, and wherein the step of inserting the number of affected Measurement Intervals into the history database is performed in lieu of resetting the PM session, further comprising the step of setting a suspect flag associated with each of the affected Measurement Intervals.