Method and apparatus for emulating a dynamically configured digital cross-connect switch network

• US 5,809,286 A
• Filed: 05/01/1996
• Issued: 09/15/1998
• Est. Priority Date: 05/01/1996
• Status: Expired due to Term

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Inventors: Dellinger, James D., McLain, John V. Jr.
• Primary Examiner(s): Teska, Kein J.
• Assistant Examiner(s): Fiul, Dan
• Application Number:
  US08/641,458
• Time in Patent Office: 867 Days
• Field of Search: 370/241, 370/242, 370/244, 370/250, 370/251, 370/252, 370/248, 370/249, 340/825.03, 340/826, 340/827, 364/550, 364/578, 395/500, 395/183.04, 395/183.05, 395/183.08, 395/183.09
• US Class Current: 703/23
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: H04M 3/323 for the arrangements providing the connection (test connection, test call, call simulation)

Abstract

A method and apparatus for emulating a digital cross-connect switching (DXC) network, such as a DXC 1/0 network, fully tests a telecommunication network monitoring and control system (MCS). The communication and behavior of a DXC network at the channel level are emulated in the presence and absence of selected network node and trunk configurations, failures, and/or normalizations. A communication module communicates with the MCS through emulator control links using a communications protocol substantially identical to a communications protocol used in the emulated digital cross-connect network. Configuration data representing the current behavior of the DXC nodes. Topology data traces logical trunks or channels through adjacent DXC nodes. The topology data further includes port provision data identifying the allocation of channels for cross-connected ports at DXC nodes. Additional DXC nodes and/or trunks can be added or deleted from the topology data during pre-processing or emulator operation to test different postulated network designs. The topology data can be updated in response to MCS channel level commands (i.e. grow/de-grow, connect/dis-connect, and cross-connect commands) to set up paths through provisioned ports in the emulated DXC network. Detailed knowledge of intermediate site and equipment within the emulated DXC network is not necessary to emulate different dynamic link connections and DXC topologies. Partial or total logical trunk outages can still be emulated by generating appropriate near-side port alarms. Simulated multi-tasking and dynamic user-interface control options are included.

Claims

1. An emulator apparatus for emulating a dynamically-configured digital cross-connect switch network to allow testing of a communication network monitor and control system (MCS), the emulator apparatus comprising:

a communication module which communicates with the MCS over at least one emulator control link using a communications protocol substantially identical to a communications protocol used in the digital cross-connect switch network to communicate to the MCS;

a memory unit for storing emulated network data representative of the behavior and topology of the emulated digital cross-connect switch network, wherein said emulated network data includes configuration data identifying the transmission behavior of DXC nodes in the digital cross-connect network and topology data identifying logical trunks extending through corresponding ports in the said DXC nodes; and

a processor coupled to said communication module and said memory unit, said processor sending emulator messages for the MCS to said communication module based on said emulated network data, said emulator messages emulating messages which would be sent from the digital cross-connect switch network to the MCS.

2. The emulator apparatus of claim 1, wherein said topology data further comprises port provision data which identifies an allocation of channels between cross-connected ports for each DXC node.

3. The emulator apparatus of claim 2, wherein said processor dynamically configures at least one path through said topology data in response to MCS channel level commands.

4. The emulator apparatus of claim 3, wherein:

each dynamically-configured path comprises at least one logical inter DXC trunk between adjacent DXC nodes, and

said MCS channel level commands include connect and disconnect commands for switching cross-connected channels between cross-connected ports in each of said adjacent DXC nodes to dynamically establish and break down said at least one logical inter-DXC trunk forming said path.

5. The emulator apparatus of claim 4, wherein said processor updates said port provision data in response to said MCS connect and disconnect commands.

6. The emulator apparatus of claim 1, wherein said digital cross-connect network comprises a DXC 1/0 network.

7. The emulator apparatus of claim 1, wherein said processor further comprises:

a control link servicer which detects incoming MCS messages sent to the emulator apparatus by the MCS;

a user-interface servicer which detects user inputs received through a user-interface, said processor updates at least one of said configuration data and said topology data to emulate the presence and absence of selected network failures identified by user-inputs; and

an emulator message generator, wherein said emulator message generator generates emulator messages in response to said incoming MCS messages detected by said control-link servicer based on at least one of said configuration data and said topology data, said emulator messages matching messages which would be sent from DXC nodes in the emulated digital cross-connect network in response to the detected incoming MCS messages.

8. The emulator apparatus of claim 7, wherein said processor further determines whether said generated emulator messages correspond to DXC nodes which are transmitting based on said configuration data, said processor sending emulator messages generated by the emulator message generator only for transmitting nodes.

9. The emulator apparatus of claim 8, wherein said configuration data includes a node transmission field representing whether each DXC node in the digital cross-connect network is emulated as a transmitting or non-transmitting node.

10. The emulator apparatus of claim 7, wherein said at least one emulator control link emulates respective at least one network node control links used to couple DXC nodes in the digital cross-connect network to the MCS.

11. The emulator apparatus of claim 10, wherein said at least one emulator link includes a first emulator control link and a second emulator control link, said first and second emulator control links emulating corresponding first and second network control links between DXC nodes in the digital cross-connect switch network and the MCS;

and wherein said processor further comprises;

an emulator link selector which selects at least one of said first and second emulator control links depending upon whether corresponding first and second network control links are enabled at a DXC node based on said configuration data, said communication module sending emulator messages generated by the emulator message generator over said at least one selected emulator primary and secondary control link.

12. The emulator apparatus of claim 11, wherein said configuration data includes first and second link active fields which identify whether respective first and second network node control links are emulated as transmitting or non-transmitting links for each DXC node in the digital cross-connect network.

13. The emulator apparatus of claim 1, wherein said communication module comprises at least one logical router, each logical router being connected between said processor and a respective emulator control link, and wherein each logical router multiplexes messages for a respective group of DXC nodes in the digital cross-connect network.

14. The emulator apparatus of claim 1, wherein said communication protocol comprises a standard data communication protocol including at least one selected from the following group of standard data communications protocols:

X.25, IP, TCP, Frame-Relay, ATM, SMDS, Ethernet, FDDI, ISDN, SDLC, and BISDN.

15. The emulator apparatus of claim 7, wherein said processor switches control transparently between said control-link servicer and said user-interface servicer to service said at least one emulator control link and user-inputs in a pseudo-parallel sequence simulating multi-tasking.

16. The emulator apparatus of claim 15, wherein:

said user-link servicer comprises a first program module for executing a first task to service said user-interface, said first program module having a control switch call after each partial logic unit of work in said first task;

said control link servicer comprises a second program module for executing a second task to service incoming MCS messages received over said at least one emulator control link; and

said processor further comprises a simulated multi-task controller for transparently switching control between said user-link servicer and said control link servicer;

wherein said simulated multi-tasking controller switches control from said user-link servicer to said control link servicer when said control switch call is read during execution of said first program module and an incoming MCS message is detected, and switches control from said control link-servicer back to said user-interface servicer to resume said first task after a partial logical unit of work in the second task has been executed by said control link servicer.

17. The emulator apparatus of claim 1, wherein said processor provides sub-second responses to the MCS and a user-interface.

18. The emulator apparatus of claim 1, wherein the emulator apparatus is run on a stand-alone personal computer connected to the MCS.

19. The emulator apparatus of claim 1, wherein user-inputs are entered through a user-interface for controlling the emulator apparatus.

20. The emulator apparatus of claim 19, wherein said user inputs include dynamic configuration inputs identifying changes in DXC node behavior or the topology of the emulated digital cross-connect network, and said processor updates said emulated network data in accordance with said dynamic configuration inputs.

21. The emulator apparatus of claim 1, wherein said processor detects user inputs identifying a selected network failure and generates an outage script file representative thereof.

22. The emulator apparatus of claim 21, wherein said selected network failure represents at least one of a partial trunk failure, total trunk failure, and node failure.

23. The emulator apparatus of claim 1, wherein said processor executes a user-selected outage script file, corresponding to a selected network failure, and sends emulator alarm messages to the MCS which emulate the behavior of DXC nodes in the digital cross-connect network in the presence of the selected network failure.

24. The emulator apparatus of claim 1, wherein said processor detects a user input selecting an outage script file for normalization, said outage script file corresponding to a selected network failure, and sends emulator clear alarm messages to the MCS which emulate the behavior of DXC nodes in the digital cross-connect network during normalization of the selected network failure.

25. The emulator apparatus of claim 1, further comprising a user-interface module for displaying emulator control options at the user-interface including at least one of outage selection, normalization/clear alarms, view communication log, view trace log, and view real-time message display;

wherein said processor responds to a user-input identifying an emulator control option and executes a corresponding emulator control routine.

26. The emulator apparatus of claim 1, wherein said topology data includes initial baseline topology data created from at least one of an external database, the MCS, and manual user-input.

27. The emulator apparatus of claim 1, wherein said processor maintains a communication log file which includes all incoming MCS commands sent to the emulator apparatus and all outgoing solicited and unsolicited emulator messages sent from the emulator apparatus to the MCS.

28. The emulator apparatus of claim 1, wherein said processor maintains a trace log file which includes error messages generated by said processor during operation of the emulator apparatus.

29. The emulator apparatus of claim 7, wherein said incoming MCS messages include session connect, keep alive, initialization, alarm audit, configuration status, and cross-connect commands.

30. The emulator apparatus of claim 7, wherein said emulator messages sent to the MCS include session connected, control implementation confirmation, control not implemented with reason code, solicited status of alarm, solicited status of node configuration, and unsolicited alarm messages.

31. The emulator apparatus of claim 1, wherein the digital cross-connect network comprises a DXC 3/3 network, a hybrid DXC 3/3 and 3/1 network, or a DXC 1/0 network.

32. A computer-implemented method for emulating a digital cross-connect network having dynamically-configured paths to test a network monitoring and control system (MCS), comprising the steps of:

storing emulated network data representative of the behavior and topology of the digital cross-connect network being emulated, said emulated network data including configuration data representative of the behavior of each DXC node in the digital cross-connect network being emulated and topology data identifying logical trunks extending between adjacent nodes in the digital cross-connect network, each dynamically-configurable path comprising at least one logical trunk;

establishing connectivity with the MCS over at least one emulator control link;

detecting incoming MCS messages; and

sending emulator messages over said at least one emulator control link to the MCS in response to said incoming MCS messages based on said emulated network data, said emulator messages emulating messages which would be sent from DXC nodes in the digital cross-connect network being emulated to the MCS in response to said detected incoming MCS messages.

33. The method of claim 32, further comprising the step of storing port provision data which identifies an allocation of channels between cross-connected ports for each DXC node.

34. The method of claim 33, further comprising the steps of:

receiving MCS channel level commands including connect and disconnect channels for switching cross-connected channels between cross-connected ports; and

updating said port provision data in response to said connect and disconnect commands to emulate the dynamic establishing and breaking down of paths in the digital cross-connect switch network.

35. The method of claim 32, further comprising the steps of:

detecting user inputs identifying a modification in at least one of the behavior or topology of the emulated digital cross-connect network;

updating said emulated network data to represent said modification; and

sending emulator messages in response to said detected user-inputs, said emulator messages emulating solicited and unsolicited messages which would be sent from DXC nodes when the digital cross-connect network is configured according to said modification.

36. The method of claim 35, wherein said modification comprises a selected network failure, said selected network failure representing at least one of a partial trunk failure, total trunk failure, and node failure.

37. The method of claim 32, wherein the digital cross-connect network comprises a DXC I/O network.

38. The method of claim 32, further comprising the steps of:

selecting an emulator control link corresponding to an enabled network control link based on said configuration data; and

sending each message generated in said generating step to the MCS over the respective emulator control link selected in said selecting step, thereby, emulating messages sent from DXC nodes over corresponding enabled network control links to the MCS.

39. The method of claim 32, further comprising the steps of:

executing an outage script file corresponding to a selected network failure; and

sending emulator alarm messages to the MCS which emulate the behavior of DXC nodes in the digital cross-connect network in the presence of the selected network failure.

40. The method of claim 32, further comprising the steps of:

executing an outage script file corresponding to a selected network failure to normalize the digital cross-connect network; and

sending emulator clear alarm messages to the MCS which emulate the behavior of DXC nodes in the digital cross-connect network during normalization of the selected network failure.

41. The method of claim 32, further comprising the steps of:

displaying emulator control options at a user-interface, said emulator control options including at least one of outage selection, normalization/clear alarms, view communication log, view trace log, and view real-time message display;

detecting a user-input selecting one of said emulator control options; and

executing a corresponding emulator control routine.

42. The method of claim 32, further comprising the steps of:

detecting user inputs identifying a selected network failure; and

generating an outage script file which identifies near-side port alarms for DXC nodes having near-side ports facing said selected network failure.

43. The method of claim 32, wherein the digital cross-connect network comprises a DXC 3/3 network, a DXC 3/3 and 3/1 network, or a DXC 1/0 network.