Methods and systems of verifying EMS compliance via NMS interface

• US 7,451,452 B2
• Filed: 12/21/2006
• Issued: 11/11/2008
• Est. Priority Date: 07/08/2002
• Status: Expired due to Fees

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Yasrebi, Mehrad, Yampanis, Mark, Garbanati, Linda Jean Freede
• Primary Examiner(s): Ho; Andy
• Application Number:
  US11/643,134
• Publication Number:
  US 20070157215A1
• Time in Patent Office: 691 Days
• Field of Search: 719/313, 719/328, 719/330, 709/223
• US Class Current: 719/313
• CPC Class Codes: H04L 41/02 Standardisation; Integration
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: H04Q 3/0087 Network testing or monitoring arrangements

Abstract

A test harness tests an element management system (EMS) via a network management system (NMS) interface for compliance with a particular interface standard. The test harness may be used by a party other than a vendor of the EMS to verify compliance of the EMS to the particular interface standard, such as Q.834.4.

Claims

1. A method executing within a computer having a processor, comprising:

translating test scripts defining one or more tests in an interface standard into sequences of Common Object Request Broker Architecture (CORBA) messages; and

determining whether an element management system (EMS) is compliant with the interface standard based on responses to at least one of the sequences of CORBA messages, the responses received from the EMS via a network management service (NMS) interface.

2. The method of claim 1, further comprising:

executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface for compliance with the interface standard.

3. The method of claim 2, wherein the interface standard is based on Q.834.4.

4. The method of claim 2, wherein a party other than a vendor of the EMS executes the at least one of the sequences of CORBA messages and determines whether the EMS is compliant with the interface standard.

5. The method of claim 4, wherein a customer of the EMS executes the at least one of the sequences of CORBA messages and determines whether the EMS is compliant with the interface standard.

6. The method of claim 4, wherein a carrier network executes the at least one of the sequences of CORBA messages and determines whether the EMS is compliant with the interface standard.

7. The method of claim 4, wherein a service provider executes the at least one of the sequences of CORBA messages and determines whether the EMS is compliant with the interface standard.

8. The method. of claim 2 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes acts of:

creating a naming hierarchy structure in a naming service;

creating at least one event channel and registering the at least one event channel with the naming service;

starting the EMS;

determining whether at least one NMS interface object associated with the at least one event channel has been properly registered using the naming service; and

determining whether the EMS has registered as an event supplier for the at least one event channel using a notification service.

9. The method of claim 2 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes an act of:

testing whether one or more valid method invocations cause expected results.

10. The method of claim 9 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes an act of:

testing whether one or more invalid method invocations raises a proper exception.

11. The method of claim 2 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes an act of:

performing every operation defined by an EMS-NMS interface definition language (IDL) interface specification of the interface standard.

12. The method of claim 2 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes an act of:

determining whether the EMS responds appropriately to at least one external stimulus from a network element.

13. The method of claim 2 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface causes an act of:

providing a simulated network error condition to the EMS;

receiving an alarm event sent by the EMS in response to the simulated network error condition;

determining whether the alarm event is appropriate for the simulated network error condition.

14. The method of claim 2 wherein executing at least one least one of the sequences of CORBA messages to test the EMS via the NMS interface comprises:

performing at least one of an initialization test, an interface test, a NMS action, and a EMS action.

15. A computer-readable storage medium comprising a set of instructions to direct a processor to perform acts of:

translating test scripts defining one or more tests in an interface standard into sequences of Common Object Request Broker Architecture (CORBA) messages; and

determining whether an element management system (EMS) is compliant with the interface standard based on responses to at least one of the sequences of CORBA messages, the responses received from the EMS via a network management service (NMS) interface.

16. An apparatus comprising:

a processor;

a test harness which interfaces with a network management service (NMS) interface of an element management system (EMS), the test harness having an NMS client to test the EMS via the NMS interface for compliance with an interface standard;

wherein the test harness is operative to translate test scripts defining one or more tests in an interface standard into sequences of Common Object Request Broker Architecture (CORBA) messages and to determine whether the EMS is compliant with the interface standard based on responses to at least one of the sequences of CORBA messages, the responses received from the EMS via the NMS interface.

17. The apparatus of claim 16 wherein the interface standard is based on Q.834.4.

18. The apparatus of claim 16 wherein the test harness is further operative to execute at least one of the sequences of CORBA messages to test the EMS via the NMS interface for compliance with the interface standard.

19. The apparatus of claim 18 wherein executing at least one of the sequences of CORBA messages to test the EMS via the NMS interface comprises performing at least one of an initialization test, an interface test, a NMS action, and a EMS action.