On-demand bandwidth provisioning in a network environment

Patent metadata

Field	Value
Publication number	US-2016013985-A1
Application number	US-201414328421-A
Country	US
Kind code	A1
Filing date	Jul 10, 2014
Priority date	Jul 10, 2014
Publication date	Jan 14, 2016
Grant date	—

Abstract

An example method for facilitating on-demand bandwidth provisioning in a network environment is provided and includes receiving a request from a client at a first network for accommodating flow characteristics at a second network that is associated with executing an application at the first network, determining that the request cannot be fulfilled with available network resources allocated to the client by the second network, advising the client of additional cost for accommodating the flow characteristics, and authorizing additional network resources in the second network to accommodate the flow characteristics after receiving notification from the client of payment of the additional cost.

First claim

1 . A method executed at a server in a network, comprising:
receiving a request from a client at a first network for accommodating flow characteristics at a second network to which the first network subscribes according to a subscriber level agreement (SLA), the flow characteristics being associated with executing an application in the first network, wherein the SLA prescribes allocation of certain network resources of the second network to flows associated with the first network; determining that the request cannot be fulfilled with available network resources allocated to the client by the second network according to the SLA; advising the client of additional cost for accommodating the flow characteristics; receiving an access token from the client, wherein the access token is issued by an authorization server; verifying the access token with the authorization server, wherein the authorization server verifies the access token with payment covering the additional cost for the requested flow characteristics and validates the access token against flow characteristics for which payment has been made; accepting the access token as notification of payment if the authorization server validates the access token; and authorizing additional network resources in the second network to accommodate the flow characteristics after receiving notification of payment of the additional cost.

2 . (canceled)

3 . The method of claim 1 , wherein the access token points to information about the flow characteristics and the additional cost at the authorization server.

4 . The method of claim 1 , wherein a proxy acts as an intermediary for communication between the client and the server.

5 . The method of claim 1 , wherein the first network comprises a customer premises network, and the second network comprises an access network.

6 . The method of claim 1 , wherein the authorization server is located in the access network.

7 . The method of claim 1 , wherein the flow characteristics, additional cost, and the notification are provided in packet metadata communicated between the client and the server.

8 . The method of claim 7 , wherein communication between the server and the client is according to port control protocol (PCP), wherein the packet metadata comprises options in a PCP message.

9 . The method of claim 8 , wherein the PCP message comprises a PCP response message from the server to the client, wherein the options in the PCP response message comprises the additional cost information.

10 . The method of claim 8 , wherein the PCP message comprises a PCP request message from the client to the server, wherein the options in the PCP request message comprises an access token indicating notification of payment of the additional cost.

11 . Non-transitory computer readable storage media that includes instructions for execution, which when executed by a processor, is operable to perform operations comprising:
receiving a request from a client at a first network for accommodating flow characteristics at a second network to which the first network subscribes according to an SLA, the flow characteristics being associated with executing an application in the first network, wherein the SLA prescribes allocation of certain network resources of the second network to flows associated with the first network; determining that the request cannot be fulfilled with available network resources allocated to the client by the second network according to the SLA; advising the client of additional cost for accommodating the flow characteristics; receiving an access token from the client, wherein the access token is issued by an authorization server; verifying the access token with the authorization server, wherein the authorization server verifies the access token with payment covering the additional cost for the requested flow characteristics and validates the access token against flow characteristics for which payment has been made; accepting the access token as notification of payment if the authorization server validates the access token; and authorizing additional network resources in the second network to accommodate the flow characteristics after receiving notification of payment of the additional cost.

12 . (canceled)

13 . The media of claim 11 , wherein the first network comprises a customer premises network, and the second network comprises an access network.

14 . The media of claim 11 , wherein the flow characteristics, additional cost, and the notification are provided in packet metadata communicated between the client and the server.

15 . The media of claim 14 , wherein communication between the server and the client is according to PCP, wherein the packet metadata comprises options in a PCP message.

16 . An apparatus, comprising:
a memory element for storing data; and a processor, wherein the processor executes instructions associated with the data, wherein the processor and the memory element cooperate, such that the apparatus is configured for:
receiving a request from a client at a first network for accommodating flow characteristics at a second network to which the first network subscribes according to an SLA, the flow characteristics being associated with executing an application in the first network, wherein the SLA prescribes allocation of certain network resources of the second network to flows associated with the first network;
determining that the request cannot be fulfilled with available network resources allocated to the client by the second network according to the SLA;
advising the client of additional cost for accommodating the flow characteristics;
receiving an access token from the client, wherein the access token is issued by an authorization server;
verifying the access token with the authorization server, wherein the authorization server verifies the access token with payment covering the additional cost for the requested flow characteristics and validates the access token against flow characteristics for which payment has been made;
accepting the access token as notification of payment if the authorization server validates the access token; and
authorizing additional network resources in the second network to accommodate the flow characteristics after receiving notification of payment of the additional cost.

17 . (canceled)

18 . The apparatus of claim 16 , wherein the first network comprises a customer premises network, and the second network comprises an access network.

19 . The apparatus of claim 16 , the flow characteristics, additional cost, and notification are provided in packet metadata communicated between the client and the server.

20 . The apparatus of claim 19 , wherein communication between the server and the client is according to PCP, wherein the packet metadata comprises options in a PCP message.

Assignees

• Cisco Tech Inc

Inventors

• Reddy K Tirumaleswar
• Patil Prashanth
• Wing Daniel G
• Versteeg William C
• Wild Christopher

Classifications

• H04L43/10

  Active monitoring, e.g. heartbeat, ping or trace-route · CPC title

• H04L41/18

  Delegation of network management function, e.g. customer network management [CNM] · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• H04L41/5003

  Managing SLA; Interaction between SLA and QoS · CPC title

• H04L47/25

  with rate being modified by the source upon detecting a change of network conditions · CPC title