Method and apparatus for supporting ATM services in an intelligent network

• US 6,788,649 B1
• Filed: 10/19/1999
• Issued: 09/07/2004
• Est. Priority Date: 08/03/1998
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Incorporated (Verizon Communications Inc.)
• Inventors: Syed, Sami, McDyson, David, Dugan, Andrew
• Primary Examiner(s): HSU, ALPUS
• Application Number:
  US09/420,657
• Time in Patent Office: 1,785 Days
• Field of Search: 370/230, 370/231, 370/235, 370/236, 370/252, 370/254, 370/389, 370/392, 370/395.1, 370/396, 370/397, 370/395.3, 370/395.31, 370/400, 370/401, 370/409, 370/465, 370/466, 370/467, 370/477, 379/88.17, 379/93.01, 379/93.07, 379/93.08, 379/93.15, 379/201.01, 379/201.02, 379/201.03, 379/220.01, 379/221.07, 379/221.08, 379/221.14, 379/221.15, 379/269, 709/200, 709/201, 709/202, 709/203, 709/217, 709/218, 709/219, 709/223, 709/224, 709/238, 709/249
• US Class Current: 370/254
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 2012/5621 Virtual private network [VPN]; Private-network - network-interface (P-NNI)
• CPC Class Codes: H04L 2012/563 Signalling, e.g. protocols, reference model
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/90 using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: H04M 2201/54 Object oriented software
• CPC Class Codes: H04M 2203/052 software update
• CPC Class Codes: H04M 2215/016 Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: H04M 3/42136 Administration or customisation of services
• CPC Class Codes: H04Q 11/0478 Provisions for broadband connections
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking
• CPC Class Codes: H04Q 3/0037 involving call modelling techniques, e.g. modifications to the basic call state model [BCSM]

Abstract

An intelligent network implementing processes and apparatus for supporting ATM/Vnet services. The intelligent network comprises the ability to receive an ATM VNET call at an ATM switch associated with a service node of the intelligent network, translate the dialed VNET number and then extend the call to a correct termination. Prior to the outdial, source address and subscription validation, destination address screening, source address screening and VNET number translation are performed. In one embodiment, assuming that the VNET call is an ATM to ATM call, no number translation is required. In placing Vnet/ATM calls, the network does all resource allocation, e.g., bandwidth reservation and allocation. The resource specification in the ATM setup message (e.g., bandwidth) is validated against the customer'"'"'s subscription versus the current network utilization.

Claims

1. A method for performing virtual network (Vnet) service relating to a Vnet request event received at a network resource complex associated with a service node provided in an intelligent communications network, said method comprising:

a) receiving a Vnet service request at a resource complex associated with a service node;

b) communicating information relating to each Vnet service request to a Vnet service agent object instance executing with an execution environment provided within a service node of said intelligent network;

c) instantiating a Vnet service object thread via said Vnet service agent object instance for each Vnet service request and associating a unique transaction identifier with each Vnet service instance, a Vnet service object processing thread encapsulating logic for performing a Vnet service;

d) for each Vnet service request, transferring said information from said resource complex indicating an originator of said Vnet service request and a destination number for said request to an executing Vnet service instance according to said unique identifier;

e) determining a route plan for said Vnet call based upon said transferred information and on one or more factors as determined by said Vnet service thread instance; and

,

f) routing said Vnet call from said resource complex to said destination number based on said determined routing plan.

2. The method as claimed in claim 1, wherein prior to said step e) of determining a route plan, the step of utilizing said information transferred to said executing Vnet service thread to perform a database look-up to verify that a calling party is entitled to request said Vnet service according to a Vnet subscription;

and, terminating said Vnet service request if said calling party is not entitled to perform said request.

3. The method as claimed in claim 2, wherein prior to said step e) of determining a route plan, the step of performing a database lookup to verify that said called party may receive a Vnet service call according to a Vnet subscription;

and, terminating said Vnet service request if said called party is not entitled to receive said call.

4. The method as claimed in claim 1, wherein prior to said step e) of determining a route plan, the step of performing a database lookup to verify that said calling party and said called party belong to a closed-user group permitting said Vnet call to be routed.

5. The method as claimed in claim 1, wherein prior to said step e) of determining a route plan for said Vnet call, the step of determining a current time for the received Vnet service request.

6. The method as claimed in claim 5, wherein said one or more factors includes the current time of year, said routing plan based on the time of year of said Vnet service request.

7. The method as claimed in claim 5, wherein said one or more factors includes the current time of day, said routing plan based on the time of day of said Vnet service request.

8. The method as claimed in claim 5, wherein prior to step h) of routing said Vnet call, the step of performing a database lookup to determine a switch to enable routing of said Vnet call from said resource complex to said destination number based on said routing plan.

9. The method as claimed in claim 5, wherein prior to step h) of routing said Vnet call, the step of performing a database lookup to determine an outdial path for routing said Vnet call from said resource complex to said destination number based on said routing plan.

10. The method as claimed in claim 5, wherein prior to step h) of routing said Vnet call, the step of determining available credit associated with said calling party and routing said call if enough credit is available, or terminating said Vnet call if not enough credit is available.

11. The method as claimed in claim 10, wherein after step h) of routing said Vnet call, the step of updating said credit associated with said calling party.

12. The method as claimed in claim 1, wherein said Vnet service event is communicated as an ATM message, said information including quality of service parameters associated with a Vnet subscription.

13. The method as claimed in claim 12, wherein said step h) of routing said Vnet call from said resource complex to said destination number based on said determined routing plan includes validating said quality of service parameters against the calling party'"'"'s subscription and against a current network utilization to determine if said Vnet call can be routed.

14. The method as claimed in claim 1, wherein said step b) of communicating further includes the step of enabling a platform independent operating system to communicate information relating to each Vnet service request to said Vnet service agent object instance, said message communicated from said resource complex includes a port ID number and a Terminal ID number corresponding to an originating location of said Vnet service request.

15. The method as claimed in claim 1, wherein said platform-independent operating system further provides a mapping of a logical name associated with a Vnet service request to a physical address associated with an executing Vnet service agent object instance in said service execution environment prior to communicating said information to said Vnet service agent object instance.

16. A system for performing virtual network (Vnet) se vices relating to a Vnet request event received at a network resource complex associated with a service node provided in an intelligent communications network, said system comprising:

a) service execution environment for executing one or more service objects associated with performing a Vnet service;

b) Vnet service agent object executing within a service execution environment and responsible for instantiating a Vnet service object thread instance for each Vnet request received and associating a unique transaction identifier therewith;

c) platform-independent communication system for transferring information relating to each Vnet service request to said Vnet service agent object instance, said information including an originator of said Vnet service request and a destination number for said request, said Vnet service agent object instance forwarding said information to an executing Vnet service thread instance according to said unique identifier;

d) mechanism for determining a route plan for each received Vnet call based upon said transferred information and on one or more factors as determined by said Vnet service thread instance; and

,

h) mechanism for routing said Vnet call from said resource complex to a destination number based on said determined route plan.

17. The system as claimed in claim 16, wherein said Vnet service thread instance includes mechanism for performing a database look-up to verify that a calling party is entitled to request said Vnet service according to a Vnet subscription.

18. The system as claimed in claim 16, wherein said Vnet wherein said information includes a port ID number and a Terminal ID number, said mechanism for performing a database lookup including querying a source address screening database utilizing said port ID number and a Terminal ID number as keys to determine that a calling party is entitled to make said Vnet service request;

said executing Vnet service thread terminating said Vnet service request if said calling party is not entitled to perform said request.

19. The system as claimed in claim 16, wherein said Vnet service thread instance includes mechanism for performing a database look-up verify that said called party may receive a Vnet service call according to a Vnet subscription;

and, terminating said Vnet service request if said called party is not entitled to receive said call.

20. The system as claimed in claim 16, wherein said Vnet service thread instance includes mechanism for performing a closed user group database query to determine if said and calling party is entitled to call said called party according to a Vnet service subscription.

21. The system as claimed in claim 16, wherein said Vnet service thread instance further determines a current time for the received Vnet service request.

22. The system as claimed in claim 21, wherein said one or more factors includes the current time of year, said mechanism for determining a route plan including performing a time of year database query to find a routing choice based on a time of year of said received request.

23. The system as claimed in claim 21, wherein said one or more factors includes the current time of day, said mechanism for determining a route plan including performing a time of day database query to find a routing choice based on a time of day of said received request.

24. The system as claimed in claim 23, wherein said mechanism for determining a route plan includes mechanism for performing a database lookup to determine a switch to enable routing of said Vnet call from said resource complex to said destination number based on said routing choice.

25. The system as claimed in claim 24, wherein said mechanism for determining a route plan includes mechanism for performing a database lookup to determine an outdial path for routing said Vnet call from said resource complex to said destination number based on said routing plan.

26. The system as claimed in claim 25, wherein said Vnet service object thread instance further includes mechanism for querying a user profile database query to determine if said calling party has enough available credit to route said received call, and routing said call if enough credit is available, or terminating said Vnet call if not enough credit is available.

27. The system as claimed in claim 26, wherein said Vnet service object thread instance further includes mechanism updating said credit associated with said calling party after routing said Vnet call.

28. The system method as claimed in claim 16, wherein said Vnet service event comprises an asynchronous transfer mode (ATM) message, said information including quality of service parameters associated with a Vnet subscription.

29. The system as claimed in claim 28, wherein said Vnet service object thread instance further includes mechanism for validating said quality of service parameters against the calling party'"'"'s subscription and against a current network utilization to determine if said Vnet call can be routed according to said routing plan.

30. The system as claimed in claim 16, further including a feature discriminator object instance for receiving said message associated with a received call from said resource complex and determining from said message which Vnet service agent object to execute based on said handed-off message.

31. The system as claimed in claim 16, further including a line logic program object instance for maintaining a current state of a network access line at said resource complex, said line logic program maintaining a state of both an originating and terminating network access line.

32. The system as claimed in claim 16, further including an event logic program object functioning as a repository for all Vnet service processing event data associated with each received call.

33. The system as claimed in claim 16, further including call logic program for maintaining the current state of a Vnet service call by associating all service logic programs, line logic programs and event logic programs executed with respect to a received call.

34. The system as claimed in claim 16, wherein said Vnet service logic object is based on combinations of indivisible functional building blocks each for performing a function independent of a said Vnet service.