Patent US4499491A successfully refreshed from Google Patents.
US5809286A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus for emulating a dynamically configured digital cross-connect switch network
Assignee: Verizon Patent and Licensing Inc
•
Filing: 1996-05-01
•
Granted: 1998-09-15
•
Expires: 2016-05-01
Abstract
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.
Inventors
- 👤 John V. McLain, Jr.
- 👤 James D. Dellinger
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 22:50
CPC Classifications
H; H04; H04M; H04M3/00; H04M3/22; H04M3/2254; H04M3/26; H04M3/28; H04M3/32; H04M3/323
Claims Analysis
Total Claims: 45
Claim 1
Independent Claim
168 words
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.
Claim 2
Dependent Claim
168 words
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.
Claim 3
Dependent Claim
28 words
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.
Claim 4
Dependent Claim
26 words
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.
Claim 5
Dependent Claim
63 words
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.
Claim 6
Dependent Claim
23 words
The emulator apparatus of claim 4, wherein said processor updates said port provision data in response to said MCS connect and disconnect commands.
Claim 7
Dependent Claim
16 words
The emulator apparatus of claim 1, wherein said digital cross-connect network comprises a DXC 1/0 network.
Claim 8
Dependent Claim
130 words
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.
Claim 9
Dependent Claim
43 words
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.
Claim 10
Dependent Claim
33 words
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.
Claim 11
Dependent Claim
36 words
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.
Claim 12
Dependent Claim
120 words
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.
Claim 13
Dependent Claim
44 words
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.
Claim 14
Dependent Claim
49 words
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.
Claim 15
Dependent Claim
42 words
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.
Claim 16
Dependent Claim
37 words
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.
Claim 17
Dependent Claim
167 words
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.
Claim 18
Dependent Claim
18 words
The emulator apparatus of claim 1, wherein said processor provides sub-second responses to the MCS and a user-interface.
Claim 19
Dependent Claim
21 words
The emulator apparatus of claim 1, wherein the emulator apparatus is run on a stand-alone personal computer connected to the MCS.
Claim 20
Dependent Claim
18 words
The emulator apparatus of claim 1, wherein user-inputs are entered through a user-interface for controlling the emulator apparatus.
Claim 21
Dependent Claim
44 words
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.
Claim 22
Dependent Claim
25 words
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.
Claim 23
Dependent Claim
26 words
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.
Claim 24
Dependent Claim
49 words
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.
Claim 25
Dependent Claim
58 words
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.
Claim 26
Dependent Claim
58 words
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.
Claim 27
Dependent Claim
29 words
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.
Claim 28
Dependent Claim
41 words
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.
Claim 29
Dependent Claim
28 words
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.
Claim 30
Dependent Claim
24 words
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.
Claim 31
Dependent Claim
39 words
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.
Claim 32
Dependent Claim
28 words
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.
Claim 33
Dependent Claim
162 words
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.
Claim 34
Dependent Claim
162 words
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.
Claim 35
Dependent Claim
27 words
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.
Claim 36
Dependent Claim
57 words
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.
Claim 37
Dependent Claim
76 words
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.
Claim 38
Dependent Claim
32 words
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.
Claim 39
Dependent Claim
15 words
The method of claim 32, wherein the digital cross-connect network comprises a DXC I/O network.
Claim 40
Dependent Claim
66 words
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.
Claim 41
Dependent Claim
49 words
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.
Claim 42
Dependent Claim
55 words
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.
Claim 43
Dependent Claim
58 words
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.
Claim 44
Dependent Claim
40 words
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.
Claim 45
Dependent Claim
26 words
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.
References Cited (Backward Citations)
US4575797A
Cited
US4555602A
Cited
US4552297A
Cited
US4636948A
Cited
US4737985A
Cited
US4799251A
Cited
US5008812A
Cited
US4924493A
Cited
US5276440A
Cited
US5027343A
Cited
US5005197A
Cited
US5095505A
Cited
US5222120A
Cited
US5157665A
Cited
US5241584A
Cited
US5197127A
Cited
US5170362A
Cited
US5224108A
Cited
US5226041A
Cited
US5375126B1
Cited
US5375126A
Cited
US5343461A
Cited
US5337306A
Cited
US5323388A
Cited
US5280481A
Cited
US5187740A
Cited
US5410586A
Cited
US5444693A
Cited
US5355405A
Cited
US5384822A
Cited
US5373501A
Cited
US5285494A
Cited
US5394540A
Cited
US5375159A
Cited
US5335268A
Cited
US5438528A
Cited
US5414858A
Cited
US5563930A
Cited
US5557795A
Cited
US5396616A
Cited
US5488648A
Cited
US5435003A
Cited
US5490272A
Cited
US5594792A
Cited
US5513345A
Cited
US5600632A
Cited
US5636345A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-09-14 | 2002-03-16 | 2002-09-15 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-09-14 | 2006-03-16 | 2006-09-15 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-09-14 | 2010-03-16 | 2010-09-15 | $7700.00 | Window Closed / Lapsed |