US2012044950A1PendingUtilityA1

Allocation of route targets based on service

Assignee: PUSHPARAJ VINODHPriority: Jul 24, 2007Filed: Oct 31, 2011Published: Feb 23, 2012
Est. expiryJul 24, 2027(~1 yrs left)· nominal 20-yr term from priority
H04L 12/4641H04L 45/308
24
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A network controller to allocate route targets for communication services provided on one or more corresponding virtual private networks, the route targets identifying service providers associated with the virtual private networks and the communication services provided by the corresponding virtual private networks.

Claims

exact text as granted — not AI-modified
1 . A device comprising:
 a network controller to allocate route targets for communication services provided on one or more corresponding virtual private networks, the route targets identifying service providers associated with the virtual private networks and the communication services provided by the corresponding virtual private networks.   
     
     
         2 . The device of  claim 1  where the network controller allocates the route targets according to a layer 3 Multi-Protocol Label Switching (MPLS) virtual private network (VPN) protocol, the route targets expressing distinct communication routes for the virtual private networks. 
     
     
         3 . The device of  claim 1  including a service-based map used by the network controller to decode numbers in the route targets identifying the communication services. 
     
     
         4 . The device of  claim 3  including a provider-based map used by the network controller to decode numbers in the route targets identifying the service providers. 
     
     
         5 . The device of  claim 1  where the route targets include a client identification field identifying the service providers associated with the virtual private networks, and a service identification field identifying the communication services provided by the corresponding virtual private networks. 
     
     
         6 . The device of  claim 5  where the route targets include a topology identification field identifying at least one of a hub configuration, spoke configuration, or mesh topology for the virtual private networks. 
     
     
         7 . The device of  claim 1  where each of the route targets includes a common identification field that both uniquely identifies the service provider associated with the virtual private network and the communication service provided by the associated virtual private network. 
     
     
         8 . A method comprising:
 identifying a service provider and at least one communication service provided on one or more corresponding virtual private networks; and   allocating route targets for communication services provided on the corresponding virtual private networks, the route targets identifying service providers associated with the virtual private networks and the communication services provided by the corresponding virtual private networks.   
     
     
         9 . The method of  claim 8  includes allocating the route targets according to a layer 3 Multi-Protocol Label Switching (MPLS) virtual private network (VPN) protocol, the route targets expressing distinct communication routes for the virtual private networks. 
     
     
         10 . The method of  claim 8  includes decoding numbers from the route targets according to a service-based map to identify corresponding communication services indicated by the route targets. 
     
     
         11 . The method of  claim 8  includes provisioning the route targets according to the communication services indicated in the route target. 
     
     
         12 . The method of  claim 8  where the route targets include a client identification field identifying the service providers associated with the virtual private networks, and a service identification field identifying the communication services provided by the corresponding virtual private networks. 
     
     
         13 . The method of  claim 11  where the route targets include a topology identification field identifying at least one of a hub configuration, spoke configuration, or mesh topology for the virtual private networks. 
     
     
         14 . The method of  claim 8  where each of the route targets includes a common identification field that both uniquely identifies the service provider associated with the virtual private network and the communication service provided by the associated virtual private network. 
     
     
         15 . A system comprising:
 a network controller to allocate route targets for communication services provided on one or more corresponding virtual private networks, the route targets identifying service providers associated with the virtual private networks and at least the communication services provided by the corresponding virtual private networks or a network topology associated with the virtual private network; and   a virtual private network provisioning unit to provision multiple route targets according to at least the service supported by the associated virtual private network or the network topology associated with the virtual private network.   
     
     
         16 . The system of  claim 15  where the network controller allocates the route targets according to a layer 3 Multi-Protocol Label Switching (MPLS) virtual private network (VPN) protocol, the route targets expressing distinct communication routes for the virtual private networks. 
     
     
         17 . The system of  claim 15  including a memory having a service-based map associating route targets with communication services provided on the corresponding virtual private networks, where the network controller includes a route target converter to decode numbers in the route targets identifying the communication services according to the service-based map. 
     
     
         18 . The system of  claim 15  where the route targets include a client identification field identifying the service providers associated with the virtual private networks, and a service identification field identifying the communication services provided by the corresponding virtual private networks. 
     
     
         19 . The system of  claim 15  where the route targets include a topology identification field identifying at least one of a hub configuration, spoke configuration, or mesh topology for the virtual private networks. 
     
     
         20 . The system of  claim 15  where each of the route targets includes a common identification field that both uniquely identifies a service provider associated with the virtual private network and a service provided by the associated virtual private network.

Join the waitlist — get patent alerts

Track US2012044950A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.