Validation of call processing network performance

• US 6,618,389 B2
• Filed: 06/08/2001
• Issued: 09/09/2003
• Est. Priority Date: 11/22/1999
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: WorldCom, Inc. (Verizon Communications Inc.)
• Inventors: Hoefelmeyer, Ralph L., Hutchinson, Michael L.
• Primary Examiner(s): Yao, Kwang Bin
• Assistant Examiner(s): JONES, PRENELL P
• Application Number:
  US09/877,890
• Publication Number:
  US 20020172158A1
• Time in Patent Office: 823 Days
• Field of Search: 370/401-404, 370/352-356, 370/233, 370/254, 370/469, 370/475, 370/389-395, 379/220, 379/230, 379/114.01, 379/114.09, 379/221.01, 709/222, 709/250, 709/244
• US Class Current: 370/401
• CPC Class Codes: H04L 12/4604 LAN interconnection over a backbone network, e.g. Internet, Frame Relay
• CPC Class Codes: H04L 2012/5667 IP over ATM
• CPC Class Codes: H04L 2012/5684 Characteristics of traffic flows
• CPC Class Codes: H04L 49/20 Support for services
• CPC Class Codes: H04L 49/253 using establishment or release of connections between ports
• CPC Class Codes: H04L 49/352 Gigabit ethernet switching [GBPS]
• CPC Class Codes: H04L 49/555 Error detection
• CPC Class Codes: H04L 49/602 Multilayer or multiprotocol switching, e.g. IP switching

Abstract

A call processing network performance verification and validation system and test methodology. The call processing network implements Internet Protocol (IP) subnet topology, ATM WAN configuration, equipment placement, and device configuration to provide partitioning of a call processing application across multiple sites. The partitioning reduces latency for mission critical messages, while providing for necessary provisioning traffic needs. Further, the overall topology provides the redundancy and resiliency necessary for mission critical call processing application, utilizing the IP subnets, ATM permanent virtual circuits, network device configuration, and server segregation to achieve Quality of Service (QoS). The validation testing method and system proves out the various segregated routes, verifies subnet integrity and measures total latency and data path traversal in a verifiable manner.

Claims

1. A system for validating a telecommunications call processing network comprising:

a call processing network including a variety of application servers and network devices for simulating handling of call processing traffic along first segregated routes comprising one or more subnets between associated network devices, and handling of call provisioning traffic along second segregated routes comprising one or more subnets;

said first and second segregated routes segregated according to call traffic latency requirements,

and test tool capable of communicating test information packets along selected segregated routes in said call processing network; and

mechanism for measuring round trip latencies of communicated packets along said selected segregated routes, whereby internetwork and intranetwork latency and subnet integrity for simulated packet traffic is verified.

2. The system according to claim 1, wherein said test tool is capable of communicating test packets at traffic load levels of varying severity across said segregated routes, said test tool generating test scripts for generating and communicating packets along selected segregated routes.

3. The system according to claim 1, wherein said mechanism for measuring round trip latencies includes mechanism for applying time stamp information for packets entering a call processing network path during validation test and for comparing timestamps of returned packets to determine the length of a round trip path.

4. The system according to claim 1, further comprising interface for enabling packets to enter said call processing network, said interface including an IP socket interface.

5. The system according to claim 4, wherein said test information packets include TCP and UDP packets.

6. The system according to claim 2, wherein said call processing network comprises:

a first local area network (LAN) including one or more network devices including a first redundant high-speed network device dedicated for handling call traffic processing packets;

second LAN including one or more network devices including a second redundant high-speed network device dedicated for handling call provisioning traffic packets; and

a wide area network (WAN) including one or more network devices for handling traffic destined to a second call processing network from said call processing network, said WAN including a router device and a permanent virtual connection (PVC) established for communicating packets to a receiving device at said second call processing network, said segregated routes including one or more of;

call processing routes between one or more subnets, call processing routes between said first and second LAN, and call processing routes across said WAN via a selected PVC.

7. The system according to claim 6, wherein said test tool executes scripts for providing worst-case traffic loading for said router and PVC by providing simultaneous real-time, provisioning and statistics packet traffic across said PVC and monitoring packet latency.

8. The system according to claim 6, wherein said test tool includes mechanism for monitoring effect of two redundant high-speed network device interface connections receiving packets from a single application server resource in said call processing network, said monitoring mechanism including measuring CPU utilization of said server resource.

9. The system according to claim 6, wherein said test tool includes mechanism for monitoring failover times for a single component failure in said call processing network, said measuring mechanism including measuring response time before during and after failover under constant traffic loading conditions.

10. The system according to claim 9, wherein said test tool includes mechanism for measuring failback times when a failed component is recovered.

11. The system according to claim 10, wherein said failover monitor mechanism monitors failover times when power is removed from a redundant high-speed network device linked to an application server.

12. The system according to claim 10, wherein said failover monitor mechanism monitors failover times when an application server interface to a redundant high-speed network device is disconnected.

13. The system according to claim 11, wherein said failover monitor mechanism monitors failback times when power is restored to a redundant high-speed network device linked to an application server.

14. The system according to claim 12, wherein said failover monitor mechanism monitors failback times when an application server interface to a redundant high-speed network device is reconnected.

15. A method for validating a telecommunications call processing network comprising the steps of:

interconnecting a variety of application servers and network devices for simulating a call processing network capable of handling call processing traffic along first segregated routes comprising one or more subnets between associated network devices, and handling of call provisioning traffic along second segregated routes comprising one or more subnets;

said first and second segregated routes segregated according to call traffic latency requirements,

communicating test information packets along selected segregated routes in said call processing network; and

measuring round trip latencies of communicated packets along said selected segregated routes, whereby internetwork and intranetwork latency and subnet integrity for simulated packet traffic is verified.

16. The method according to claim 15, wherein said communicating of test packets includes implementing test scripts for generating and communicating packets along selected segregated routes, said generating step including generating packet traffic load levels of varying severity across said segregated routes.

17. The method according to claim 16, wherein said step of measuring round trip latencies includes:

applying time stamp information for packets entering a call processing network path during validation test; and

,

comparing timestamps of returned packets to determine the length of a round trip path.

18. The method according to claim 15, further comprising providing an interface for enabling packets to enter said call processing network, said interface including an IP socket interface.

19. The method according to claim 16, wherein said interconnecting includes:

providing a first local area network (LAN) including one or more network devices including a first redundant high-speed network device dedicated for handling call traffic processing packets;

providing a second LAN including one or more network devices including a second redundant high-speed network device dedicated for handling call provisioning traffic packets;

providing a wide area network (WAN) including one or more network devices for handling traffic destined to a second call processing network from said call processing network via a router device; and

,

establishing and a permanent virtual connection (PVC) for communicating packets to a receiving device at said second call processing network, wherein said segregated routes includes one or more of;

call processing routes between one or more subnets, call processing routes between said first and second LAN, and call processing routes across said WAN via a selected PVC.

20. The method according to claim 19, further including the step of executing scripts for providing worst-case traffic loading for said router and PVC by providing simultaneous real-time, provisioning and statistics packet traffic across said PVC and monitoring packet latency.

21. The method according to claim 19, further including the step of monitoring effect of two redundant high-speed network device interface connections for receiving packets from a single application server resource in said call processing network, said monitoring mechanism including measuring CPU utilization of said server resource.

22. The method according to claim 19, further including the step of monitoring failover times for a single component failure in said call processing network, said monitoring step including measuring response time before during and after failover under constant traffic loading conditions.

23. The method according to claim 22, further including the step of measuring failback times when a failed component is recovered.

24. The method according to claim 23, further including monitoring failover times when power is removed from a redundant high-speed network device linked to an application server.

25. The method according to claim 23, further including monitoring failover times when an application server interface to a redundant high-speed network device is disconnected.

26. The method according to claim 24, further including monitoring failback times when power is restored to a redundant high-speed network device linked to an application server.

27. The method according to claim 25, further including monitoring failback times when an application server interface to a redundant high-speed network device is reconnected.