Methods, systems, and computer program products for modifying bandwidth and/or quality of service in a core network

• US 7,545,788 B2
• Filed: 08/20/2004
• Issued: 06/09/2009
• Est. Priority Date: 08/20/2004
• Status: Active Grant

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Shrum, Jr., Edgar Vaughan, Anschutz, Thomas Arnold
• Primary Examiner(s): Orgad, Edan
• Assistant Examiner(s): Patel, Jay P
• Application Number:
  US10/922,605
• Publication Number:
  US 20060039381A1
• Time in Patent Office: 1,754 Days
• Field of Search: 370/395.21, 370/340
• US Class Current: 370/340
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/765 triggered by the end-points
• CPC Class Codes: H04L 47/801 Real time traffic
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04M 11/062 using different frequency bands for speech and other data
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

Bandwidth and/or Quality of Service (QoS) may be modified in a Regional/Access Network (RAN) that includes a core network, the RAN facilitating differentiated end-to-end data transport between an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP) and a customer Premises Network (CPN). Application Programming Interface (API) calls are used at the enterprise, NSP, and/or the ASP to communicate with the RAN to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP. API calls are also used at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

Claims

1. A method of modifying bandwidth and/or Quality of Service (QoS) in a Regional/Access Network (RAN) that comprises a core network, the RAN facilitating differentiated end-to-end data transport between an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP) and a customer Premises Network (CPN), comprising:

using Application Programming Interface (API) calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP; and

using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP, wherein using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP comprises,

sending a change network resource request message from the enterprise, NSP, and/or the ASP to the RAN that contains a request for changing the bandwidth and/or traffic priority of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP, and

sending a change network resource response message from the RAN to the enterprise, NSP, and/or the ASP that contains an acknowledgement for the change network resource request message.

2. The method of claim 1, further comprising:

querying the core network directly from the RAN to obtain the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

3. The method of claim 1, further comprising:

querying an Operational Support System (OSS) associated with the core network to obtain the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

4. The method of claim 1, further comprising:

modifying the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP directly from the RAN.

5. The method of claim 1, further comprising:

communicating with an Operational Support System (OSS) to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

6. The method of claim 1, wherein the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP is traffic priority.

7. The method of claim 1, wherein using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query the resource allocation in the core network comprises:

sending a query network resource request message from the enterprise, NSP, and/or the ASP to the RAN that contains a request for information on resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP; and

sending a query network resource response message from the RAN to the enterprise, NSP, and/or the ASP that contains the information on resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

8. The method of claim 1, further comprising:

authenticating the enterprise, NSP, and/or the ASP with the RAN prior to using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query the resource allocation and prior to using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation.

9. The method of claim 8, wherein authenticating the enterprise, NSP, and/or the ASP with the RAN comprises:

sending an establish service session request message from the enterprise, NSP, and/or the ASP to the RAN that contains an identification of the enterprise, NSP, and/or the ASP and authorization credentials; and

sending an establish service session response message from the RAN to the enterprise, NSP, and/or the ASP that contains an authentication result.

10. The method of claim 1, wherein the RAN is coupled to at least one edge network and wherein using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP comprises:

using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the at least one edge network that is assigned to the enterprise, NSP, and/or the ASP.

11. The method of claim 10, wherein the RAN is coupled to a plurality of edge networks of different types and wherein using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the edge network that is assigned to the enterprise, NSP, and/or the ASP comprises:

using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the plurality of edge networks that is assigned to the enterprise, NSP, and/or the ASP.

12. A Regional/Access Network (RAN) node, comprising:

a network resource manager module;

an Application Programming Interface (API) module that is configured to facilitate communication between the network resource manager module and an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP); and

a core network interface module that is configured to facilitate communication between the network resource manager module and a core network;

wherein the network resource manager module is configured to process API calls initiated by the enterprise, NSP, and/or the ASP to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP, and to process API calls initiated by the enterprise, NSP, and/or the ASP to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP;

wherein the core network interface module is configured to facilitate communication between the network resource manager module and an Operational Support System (OSS) associated with the core network.

15. The RAN node of claim 12, wherein the RAN node is a Broadband Remote Access Server (BRAS).

16. The RAN node of claim 12, wherein the RAN node is a policy enabled router.

17. The RAN node of claim 12, wherein the RAN node is a (multiprotocol label switching) MPLS router that supports traffic engineering.

18. The RAN node of claim 12, wherein the core network is coupled to at least one edge network;

and

wherein the network resource manager module is configured to process API calls initiated by the enterprise, NSP, and/or the ASP to query a resource allocation in the core network and the at least one edge network that is assigned to the enterprise, NSP, and/or the ASP, and to process API calls initiated by the enterprise, NSP, and/or the ASP to modify the bandwidth and/or the QoS of the resource allocation in the core network and the at least one edge network that is assigned to the enterprise, NSP, and/or the ASP.

19. The RAN node of claim 18, wherein the core network is coupled to a plurality of edge networks of different types;

and

wherein the network resource manager module is configured to process API calls initiated by the enterprise, NSP, and/or the ASP to query a resource allocation in the core network and the plurality of edge networks that is assigned to the enterprise, NSP, and/or the ASP, and to process API calls initiated by the enterprise, NSP, and/or the ASP to modify the bandwidth and/or the QoS of the resource allocation in the core network and the plurality of edge networks that is assigned to the enterprise, NSP, and/or the ASP.

13. A Regional/Access Network (RAN) node, comprising:

a network resource manager module;

an Application Programming Interface (API) module that is configured to facilitate communication between the network resource manager module and an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP);

a core network interface module that is configured to facilitate communication between the network resource manager module and a core network; and

a data repository that is communicatively coupled to the network resource manager module and is configured to store a topology of core network resources that are assigned to the enterprise, the NSP, and/or the ASP;

wherein the network resource manager module is configured to process API calls initiated by the enterprise, NSP, and/or the ASP to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP, and to process API calls initiated by the enterprise, NSP, and/or the ASP to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

14. The RAN node of claim 13, wherein the core network interface module is configured to facilitate communication between the network resource manager module and an Operational Support System (OSS) associated with the core network.

20. A system for modifying bandwidth and/or Quality of Service (QoS) in a Regional/Access Network (RAN) that comprises a core network, the RAN facilitating differentiated end-to-end data transport between an enterprise, a Network Service Provider (NSP), and/or an Application Service Provider (ASP) and a customer Premises Network (CPN), comprising:

means for using Application Programming Interface (API) calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query a resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP; and

means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP wherein the means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP comprises,

means for sending a change network resource request message from the enterprise, NSP, and/or the ASP to the RAN that contains a request for changing the bandwidth and/or traffic priority of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP, and

means for sending a change network resource response message from the RAN to the enterprise, NSP, and/or the ASP that contains an acknowledgement for the change network resource request message.

21. The system of claim 20, further comprising:

means for querying the core network directly from the RAN to obtain the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

22. The system of claim 20, further comprising:

means for querying an Operational Support System (OSS) associated with the core network to obtain the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

23. The system of claim 20, further comprising:

means for modifying the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP directly from the RAN.

24. The system of claim 20, further comprising:

means for communicating with an Operational Support System (OSS) to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

25. The system of claim 20, wherein the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP is traffic priority.

26. The system of claim 20 wherein the means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query the resource allocation in the core network comprises:

means for sending a query network resource request message from the enterprise, NSP, and/or the ASP to the RAN that contains a request for information on resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP; and

means for sending a query network resource response message from the RAN to the enterprise, NSP, and/or the ASP that contains the information on resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP.

27. The system of claim 20, further comprising:

means for authenticating the enterprise, NSP, and/or the ASP with the RAN prior to using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to query the resource allocation and prior to using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation.

28. The system of claim 27, wherein the means for authenticating the enterprise, NSP, and/or the ASP with the RAN comprises:

means for sending an establish service session request message from the enterprise, NSP, and/or the ASP to the RAN that contains an identification of the enterprise, NSP, and/or the ASP and authorization credentials; and

means for sending an establish service session response message from the RAN to the enterprise, NSP, and/or the ASP that contains an authentication result.

29. The system of claim 20, wherein the RAN is coupled to at least one edge network and wherein the means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network that is assigned to the enterprise, NSP, and/or the ASP comprises:

means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the at least one edge network that is assigned to the enterprise, NSP, and/or the ASP.

30. The system of claim 29, wherein the RAN is coupled to a plurality of edge networks of different types and wherein the means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the edge network that is assigned to the enterprise, NSP, and/or the ASP comprises:

means for using API calls at the enterprise, NSP, and/or the ASP to communicate with the RAN to modify the bandwidth and/or the QoS of the resource allocation in the core network and the plurality of edge networks that is assigned to the enterprise, NSP, and/or the ASP.