Cisco Cisco Prime Optical 9.5 テクニカルリファレンス

TM FORUM Implementation Statement (IS) Template and Guidelines  

have similar response time 
characteristics can be 
grouped into a single entry 
in this table (the group of 
SNC establishment 
operations) 

 

A similar table is needed for each notification type. There may be delays in delivering a notification. Once a 
notification has reached a particular age without being delivered to the NMS, it may make no sense for the 
Notification service to deliver the notification. The parties representing the NMS and EMS  need to agree on a 
timeout period for each notification type.  

The following table is needed to specify the heartbeat time constraints for the session supervision from NMS to 
EMS, and vice versa. It should be noted that Table Error! No text 

-8  refers to 

pings that are sent from the NMS to the EMS and vice versa, in order to make sure the connection between the 
NMS and EMS is still up. Table Error! No text of spec

-85, on the other hand, refers to 

NT_HEARTBEAT notifications sent from the notification service to the NMS (this allows the NMS to know that its 
connection to the notification service is up.  

style in document.

Table Error! No text of specified 

-84 Heartbeat Time Constraints 

NMS 

 

 

The NMS may use 
requests/responses for 
supervision instead of 
heartbeats.  

EMS  

 

 

 

 

In Version 3.0, the EMS may send heartbeat notifications (NT_HEARTBEAT) when it has not sent any 
notifications for a period of time. The EMS supplier should indicate how often heartbeat notifications are sent (in 
the absence of other notifications). The EMS supplier should also indicate the number of consecutively missed 
heartbeat notifications after which the NMS should consider its association with the notification service has been 
lost. 

style in document.

 

Table Error! No text of specified 

-85. Heartbeat Notification Time Constraints 

 

 

 

Page 86 of 115 

 TeleManagement Forum 2007 

TMF814Av3.1