US8929367B2

Methods and apparatus to dynamically control connectivity within virtual private networks

Summary by NHIP

Dynamic VPN Route Server

The route server stores database indications defining additional connectivity between provider edge routers and modifies received border gateway protocol advertisements. It generates a copy of the advertisement and changes the first border gateway protocol route target attribute to match the stored additional connectivity before broadcasting the modified copy.

Claim Score by NHIP

Read claim 7, the broadest

Abstract

Methods and apparatus to dynamically control connectivity within VPNs are disclosed. A disclosed example route server to control connectivity within a VPN comprises a memory to implement a database, a border gateway protocol (BGP) engine to process BGP advertisements, a network interface to receive a first BGP advertisement, which a first route target (RT) associated with the first PE router, from a first provider edge (PE) router associated with the VPN, and an intra-VPN connectivity controller to, in response to the first BGP advertisement, query the database to determine whether the first PE router is to be communicatively coupled to a second PE router of the VPN and when the first and second PE routers of the VPN are to be communicatively coupled, direct the BGP engine to form a second BGP advertisement that includes a second RT associated with the second PE router based on the first BGP advertisement.

US8929367B2, drawing sheet 1 — Sheet 1 of 6

Term

3.3 yearsleft in the term

Expires 1 January 2030, including 427 days of term adjustment.

17 claims: 3 independent, 14 dependent

1
A route server, comprising:a memory comprising machine readable instructions;and a processor to execute the instructions to perform operations comprising: storing an indication in connection with a first provider edge router in an intra-virtual private network connectivity database, the indication to define an additional connectivity for the first provider edge router beyond connectivity defined in a virtual private network routing and forwarding table associated with the first provider edge router, the additional connectivity defined in the indication including an identification of a second provider edge router to which the first provider edge router is to be communicatively coupled;receiving a border gateway protocol advertisement from the first provider edge router, the border gateway protocol advertisement including a first border gateway protocol route target attribute included in an export policy of the virtual routing and forwarding table associated with the first provider edge router;generating a copy of the border gateway protocol advertisement;and modifying the first border gateway protocol route target attribute of the copy to correspond to the additional connectivity of the indication stored in the database.
7
Broadest claimClaim Score 45, average(NHIP)A method, comprising:storing an indication in connection with a first provider edge router in an intra-virtual private network connectivity database, the indication to define an additional connectivity for the first provider edge router beyond connectivity defined in a virtual private network routing and forwarding table associated with the first provider edge router, the additional connectivity defined in the indication including an identification of a second provider edge router to which the first provider edge router is to be communicatively coupled;receiving a border gateway protocol advertisement from the first provider edge router, the first border gateway protocol advertisement including a first border gateway protocol route target attribute included in an export policy of the virtual routing and forwarding table associated with the first provider edge router;generating a copy of the border gateway protocol advertisement;and modifying the first border gateway protocol route target attribute of the copy to identify the additional connectivity of the indication stored in the database.
13
A tangible machine readable medium not comprising propagating signals and having instructions stored thereon that, when executed, cause a machine to perform operations comprising:storing an indication in connection with a first provider edge router in an intra-virtual private network connectivity database, the indication to define an additional connectivity for the first provider edge router beyond connectivity defined in a virtual private network routing and forwarding table associated with the first provider edge router, the additional connectivity defined in the first indication comprising an identification of a second provider edge router to which the first provider edge router is to be communicatively coupled;receiving a border gateway protocol advertisement from the first provider edge router, the border gateway protocol advertisement including a first border gateway protocol route target attribute included in an export policy of the virtual routing and forwarding table associated with the first provider edge router;generating a copy of the border gateway protocol advertisement;and modifying the first border gateway protocol route target attribute of the copy to correspond to the additional connectivity of the indication stored in the database.

Independent claims3

43 paragraphs in 5 sections, as filed

0001This patent arises from a continuation of U.S. patent application Ser. No. 12/262,675, filed on Oct. 31, 2008, now U.S. Pat. No. 8,121,118, which is hereby incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

0002This disclosure relates generally to virtual private networks (VPNs) and, more particularly, to methods and apparatus to dynamically control connectivity within VPNs.

BACKGROUND

0003Enterprise customers are increasingly adopting multiprotocol label switching (MPLS) based VPN services to implement a communication network among their respective customer sites via a service provider's network. Such MPLS-based VPNs provide direct any-to-any reachability among an enterprise's customer sites.

BRIEF DESCRIPTION OF THE DRAWINGS

0004<figref idref="DRAWINGS">FIG. 1</figref> is a schematic illustration of example communication system constructed in accordance with the teachings of this disclosure.

0005<figref idref="DRAWINGS">FIG. 2</figref> illustrates example default intra-VPN connectivity configurations for the example communication system of <figref idref="DRAWINGS">FIG. 1</figref>.

0006<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example manner of implementing a route server for the example communication system of <figref idref="DRAWINGS">FIG. 1</figref>.

0007<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example data structure that may be used to implement an intra-VPN connectivity database for the example route server of <figref idref="DRAWINGS">FIG. 3</figref>.

0008<figref idref="DRAWINGS">FIG. 5</figref> is a flowchart representative of an example process that may be carried out to implement the example route servers of <figref idref="DRAWINGS">FIGS. 1</figref> and/or 3.

0009<figref idref="DRAWINGS">FIG. 6</figref> is a schematic illustration of an example processor platform that may be used and/or programmed to carry out the example process of <figref idref="DRAWINGS">FIG. 5</figref> and/or to implement any of all of the methods and apparatus disclosed herein.

DETAILED DESCRIPTION

0010Example methods and apparatus to dynamically control connectivity within virtual private networks (VPNs) are disclosed. A disclosed example route server to control connectivity within a VPN includes a memory to implement an intra-VPN connectivity database, a border gateway protocol (BGP) engine to process BGP advertisements, a network interface to receive a first BGP advertisement from a first provider edge (PE) router associated with the VPN, the first BGP advertisement including a first route target (RT) associated with the first PE router, and an intra-VPN connectivity controller to, in response to the first BGP advertisement, query the database to determine whether the first PE router is to be communicatively coupled to a second PE router of the VPN and when the first and second PE routers of the VPN are to be communicatively coupled, direct the BGP engine to form a second BGP advertisement based on the first BGP advertisement, the second BGP advertisement including a second RT associated with the second PE router.

0011A disclosed example method includes receiving a first BGP advertisement from a first PE router associated with a VPN, the first BGP advertisement including a first RT associated with the first PE router, automatically querying an intra-VPN connectivity database to determine whether the first PE router is to be communicatively coupled to a second PE router of the VPN, forming a second BGP advertisement based on the first BGP advertisement when the first and second PE routers of the VPN are to be communicatively coupled, the second BGP advertisement including a second RT associated with the second PE router, and broadcasting the second BGP advertisement.

0012In the interest of brevity and clarity, throughout the following disclosure references will be made to an example multiprotocol label switching (MPLS) based communication system 100 of <figref idref="DRAWINGS">FIG. 1</figref>. However, the methods and apparatus described herein to dynamically control connectivity within VPNs are applicable to other types of networks constructed using other technologies, topologies and/or protocols.

0013<figref idref="DRAWINGS">FIG. 1</figref> illustrates the example MPLS-based communication system 100. To facilitate communication services between a plurality of customer edge (CE) routers, eight of which are designated at reference numerals 105-112, the example communication system 100 of <figref idref="DRAWINGS">FIG. 1</figref> includes a service-provider network 115. While for ease of illustration and discussion, all of the example CE routers 105-112 are associated with a single VPN, the example communication system 100 of <figref idref="DRAWINGS">FIG. 1</figref> may facilitate communication services for a plurality of VPNs. Moreover, not all of the VPNs implemented by the example communication system 100 need include and/or implement the methods and apparatus to dynamically control intra-VPN connectivity.

0014To route and/or transport data between and/or among the example CE routers 105-112, the example service-provider network 115 of <figref idref="DRAWINGS">FIG. 1</figref> includes a plurality of PE routers, four of which are designated at reference numerals 120, 121, 122 and 123. The example PE routers 120-123 of <figref idref="DRAWINGS">FIG. 1</figref> are communicatively coupled to each other via any number and/or type(s) of communication paths (not shown) that allow any particular PE router 120-123 to communicate with at least some, but not necessarily all of, the other PE routers 120-123.

0015For each VPN implemented by the service-provider network 115, each of the example PE routers 120-123 of <figref idref="DRAWINGS">FIG. 1</figref> has a corresponding VPN routing and forwarding (VRF) table. In the illustrated example of <figref idref="DRAWINGS">FIG. 1</figref>, the PE router 120 has a VRF table 130, the PE router 121 has a VRF table 131, the PE router 122 has a VRF table 132, and the PE router 123 has a VRF table 133. The example VRF tables 130-133 of <figref idref="DRAWINGS">FIG. 1</figref> are associated with the VPN communicatively coupling the example CE routers 105-112. The example VRF tables 130-133 are used by the PE routers 120-123 to route and/or forward a packet received at a particular PE router 120-123 to and/or toward its final destination. In general, when a packet is received at a PE router 120-123 from a CE router 105-112 associated with a particular VPN, the PE router 120-123 uses the final destination specified and/or identified in the packet to perform a query of the VRF table 130-133 associated with that VPN. Based on a result of the query, the PE router 120-123 determines how the packet is to be routed or forwarded within the service provider network 110, and/or delivered to a particular CE router 105-112.

0016By sending, for example, BGP route advertisements, each of the example PE routers 120-123 of <figref idref="DRAWINGS">FIG. 1</figref> publishes and/or exports information concerning the CE router(s) 105-112 that are communicatively coupled to the PE router 120-123. Isolation between different VPNs and/or between different devices of a VPN is achieved via RTs, import policies and/or export policies. Specifically, BGP advertisements and/or routes within a BGP advertisement are tagged with an RT value. The RT that is included in a BGP advertisement is defined by the export policy of the PE router 120-123 that is sending the BGP advertisement. For instance, when the example PE router 120 of <figref idref="DRAWINGS">FIG. 1</figref> sends a BGP advertisement containing information regarding any of the CE routers 105-107, the BGP advertisement includes an RT B, as defined by an export policy 135 associated with the VRF table 130.

0017Based on received BGP route advertisements, the example PE routers 120-123 of <figref idref="DRAWINGS">FIG. 1</figref> build, compile, update, maintain and/or construct their respective VRF tables 130-133. The example PE routers 120-123 import routes in accordance with their associated import policy. In the illustrated example of <figref idref="DRAWINGS">FIG. 1</figref>, when the example PE router 123 receives a BGP advertisement tagged with an RT, the PE router 123 compares the RT contained in the BGP advertisement with its import policy 136. If the import policy 136 specifies that routes associated with that RT are to be imported, the PE router 123 updates its VRF table 133. For example, if the BGP advertisement includes an RT G, the PE router 123 would import the routes listed in the BGP advertisement. However, BGP advertisements including other RTs would be ignored.

0018By configuring the import and export policies of the example VRF tables 130-133, nominal and/or default routes between the example PE routers 120-123 for the example VPN of <figref idref="DRAWINGS">FIG. 1</figref> can be controlled, as shown in <figref idref="DRAWINGS">FIG. 2</figref>. For example, if the values A, B, C, D, E, F and G of <figref idref="DRAWINGS">FIG. 1</figref> are configured to have the same value, then the example VPN of <figref idref="DRAWINGS">FIG. 1</figref> is configured in the any-to-any topology traditionally utilized within VPNs. If the values A, B, C, D, E, F and G are all different, then no routes between any of PE routers 120-123 for the example VPN of <figref idref="DRAWINGS">FIG. 1</figref> have been configured and/or enabled. If the values A, C, E, and H have a first value, and the values B, D, F and G have a second value, then the example VPN of <figref idref="DRAWINGS">FIG. 1</figref> is configured in a hub and spoke topology. In particular, the example PE router 123 would operate as a hub router for the VPN with the other PE routers 120-122 operating as spoke routers.

0019Returning to <figref idref="DRAWINGS">FIG. 1</figref>, to facilitate sharing of routing information among the example PE routers 120-123, the example service provider network 110 of <figref idref="DRAWINGS">FIG. 1</figref> includes any number of route servers, route reflectors, intelligent route reflectors and/or intelligent route service control points, one of which is designated at reference numeral 140. Because not all of the example PE routers 120-123 are necessarily communicatively coupled in a full mesh topology (for example, when at least one PE router 120-123 does not have a direct communication path to another PE router 120-123), the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> forwards BGP advertisements among and/or to the PE routers 120-123. By forwarding each received BGP advertisement, the example route server 140 enables each of the PE routers 120-123 to build, compile and/or construct a VRF table 130-133 that can be used by the PE router 120-123 to route data from any of its communicatively coupled CE routers 105-112 to none, some or all of the CE routers 105-112 communicatively coupled to other PE routers 120-123, even if such routing of data requires use of one or more intervening PE routers 120-123.

0020To dynamically control communication within the example VPN of <figref idref="DRAWINGS">FIG. 1</figref> without having to reconfigure and/or change import and/or export policies of a VRF table 130-133, the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> forms a copy of each BGP advertisement that it receives, modifies the copy of the received BGP advertisement, and sends and/or broadcasts the modified BGP advertisement. For example, when the example PE router 120 is to be communicatively coupled to the example PE router 122 for a particular VPN and the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> receives a BGP advertisement 150 that includes the RT B associated with the export policy 135 of the VRF table 130, the example route server 140 broadcasts a version 151 of the BGP advertisement 150 that includes an RT E associated with an import policy 155 of the VRF table 132. Likewise, when the example route server 140 receives a BGP advertisement 152 that includes an RT F associated with an export policy 156 of the VRF table 132, the example route server 140 broadcasts a version 153 of the BGP advertisement 152 that includes an RT A associated an import policy 157 of the VRF table 130. When a particular PE router 120-123 is not to have additional connectivity within a VPN beyond that defined by the import and/or export policy of the PE router 120-123, the route server 140 forwards the originally received BGP advertisements 150 and 152 without making, modifying and/or sending a copy of the received BGP advertisements 150 and/or 152.

0021Intra-VPN connectivity enabled by the example route server 140 is in addition to any intra-VPN connectivity defined by the import and/or export policies of the VRF tables 130-132. For example, if the values A, B, C, D, E, F and G are all different, the route server 140 is the sole enabler for connectivity within the example VPN of <figref idref="DRAWINGS">FIG. 1</figref>. However, if the values A, C, E, and H have a first value, and the values B, D, F and G have a second value thereby enabling a hub and spoke topology with the PE router 123 operating as a hub router, the example route server 140 can be used to dynamically enable additional connectivity between the spoke PE routers 120-122.

0022To determine whether PE routers 120-123 are to have additional connectivity within a VPN beyond that defined by their respective import and export policies, the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> queries an intra-VPN connectivity database 305 (<figref idref="DRAWINGS">FIG. 3</figref>). As described below in connection with <figref idref="DRAWINGS">FIGS. 3 and 4</figref>, a user and/or computer 310 can dynamically and/or selectively configure connectivity within a VPN by configuring the intra-VPN connectivity database 305. An example manner of implementing the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> is described below in connection with <figref idref="DRAWINGS">FIG. 3</figref>.

0023While an example communication system has been illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, one or more of the interfaces, data structures, elements, processes and/or devices illustrated in <figref idref="DRAWINGS">FIG. 1</figref> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example PE routers 120-123 and/or the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example PE routers 120-123 and/or the example route server 140 may be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. Further still, a communication system may include interfaces, data structures, elements, processes and/or devices instead of, or in addition to, those illustrated in <figref idref="DRAWINGS">FIG. 1</figref> and/or may include more than one of any or all of the illustrated interfaces, data structures, elements, processes and/or devices.

0024<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example manner of implementing the example route server 140 of <figref idref="DRAWINGS">FIG. 1</figref>. To implement one or more interfaces to the example PE routers 120-123, the example route server 140 of <figref idref="DRAWINGS">FIG. 3</figref> includes any number and/or type(s) of network interfaces, one of which is designated at reference numeral 315.

0025To send, receive and process BGP route advertisements, the example route server 140 of <figref idref="DRAWINGS">FIG. 3</figref> includes a multi-protocol BGP engine 320. When a BGP route advertisement is received from a PE router 120-123 via the example network interface 315, the example multi-protocol BGP engine 320 of <figref idref="DRAWINGS">FIG. 3</figref> forwards the received BGP route advertisement to the other PE routers 120-123. The example multi-protocol BGP engine 320 also queries an intra-VPN connectivity controller 325 to determine whether one or more modified copies of the received BGP router advertisement are to be broadcast.

0026To control connectivity within a VPN, the example route server 140 of <figref idref="DRAWINGS">FIG. 3</figref> includes the example intra-VPN connectivity controller 325. When queried by the example multi-protocol BGP engine 320, the example intra-VPN connectivity controller 325 of <figref idref="DRAWINGS">FIG. 3</figref> queries the example intra-VPN connectivity database 305 to determine whether BGP advertisements associated with a first RT are to be re-broadcast with one or more additional RT. When intra-VPN connectivity beyond that defined by import and/or export policies is to be enabled for a particular RT, the example intra-VPN connectivity controller 325 returns to the multi-protocol BGP engine 320 the one or more additional RTs with which the received BGP route advertisement is to be re-broadcast.

0027In response to the one more additional RTs, the example multi-protocol BGP engine 320 of <figref idref="DRAWINGS">FIG. 3</figref> creates one or more corresponding copies of the received BGP advertisement, modifies the original RT to correspond with a respective one of the one or more additional RTs, and broadcasts the modified copy(-ies) of the received BGP advertisement.

0028Intra-VPN connectivity configuration information may be stored in the example intra-VPN connectivity database 305 using any number and/or type(s) of data structures. An example data structure that may be used to implement the example shared resource control access database 305 of <figref idref="DRAWINGS">FIG. 3</figref> is described below in connection with <figref idref="DRAWINGS">FIG. 4</figref>. The example intra-VPN connectivity database 305 may be stored using any number and/or type(s) of memory(-ies), memory device(s) and/or storage device(s).

0029To allow the user and/or computer 310 to configure intra-VPN connectivity for a VPN, the example route server 140 of <figref idref="DRAWINGS">FIG. 3</figref> includes any number and/or type(s) of user interface modules, one of which is designated at reference numeral 330. The example user 310 of <figref idref="DRAWINGS">FIG. 3</figref> may be associated with a particular VPN, and/or be associated with an operator of the service-provider network 115. The example user interface module 330 of <figref idref="DRAWINGS">FIG. 3</figref> enables the user 310 to interact with the example intra-VPN connectivity controller 325 to update the database 305 to configure connectivity within a VPN. In some examples, intra-VPN connectivity can be configured differently for different periods of time, temporarily configured with an expiration time, and/or automatically re-configured in response to a triggering event. For instance, during business hours there may be full connectivity within a VPN, with the VPN reverting to a nominal hub-and-spoke topology during non-business hours. Additionally or alternatively, if a virus and/or security anomaly is detected, connectivity within a VPN may be restricted and/or blocked to reduce the likelihood of damage. Example user interface modules 330 include, but are not limited to, a web-based interface, a voice activated response system and/or an application programming interface accessible to another computer system 310.

0030While an example route server 140 has been illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, one or more of the interfaces, data structures, elements, processes and/or devices illustrated in <figref idref="DRAWINGS">FIG. 3</figref> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example intra-VPN connectivity database 305, the example network interface 315, the example multi-protocol BGP engine 320, the example intra-VPN connectivity controller 325, the example user interface module 330, and/or, more generally, the example route server 140 of <figref idref="DRAWINGS">FIG. 3</figref> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any or the example intra-VPN connectivity database 305, the example network interface 315, the example multi-protocol BGP engine 320, the example intra-VPN connectivity controller 325, the example user interface module 330, and/or, more generally, the example route server 140 may be implemented by one or more circuit(s), programmable processor(s), ASIC(s), PLD(s) and/or FPLD(s), etc. Further still, a route server may include interfaces, data structures, elements, processes and/or devices instead of, or in addition to, those illustrated in <figref idref="DRAWINGS">FIG. 3</figref> and/or may include more than one of any or all of the illustrated interfaces, data structures, elements, processes and/or devices.

0031<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example data structure that may be used to implement the example intra-VPN connectivity database 305 of <figref idref="DRAWINGS">FIG. 3</figref>. The example data structure of <figref idref="DRAWINGS">FIG. 4</figref> includes a plurality of entries for respective ones of pairs of RTs, one of which is designated at reference numeral 410. Each of the example entries 410 is associated with a particular combination of RTs. For instance, the example entry 410 is associated with a combination of RT F and RT G.

0032To identify whether communication between the VRFs 130-133 associated with a particular combination of RTs is currently enabled, each of the example entries 410 contains one or more values, flags, rules, criteria and/or strings that represent whether the example route server 140 is to cross-communicate BGP advertisements between the RTs associated with the entry 410. Example entries 410 include, but are not limited to, a flag that indicates that connectivity between the RTs is unconditionally enabled, a time of day range that specifies when connectivity is enabled, a condition when connectivity is enabled, and/or a condition when connectivity is disabled. In some examples, the example entries 410 of <figref idref="DRAWINGS">FIG. 4</figref> each contain a simple flag to indicate whether the example route server 140 is to cross-communicate BGP advertisements between the RTs associated with the entry 410. In such examples, the example user and/or computer 310 (<figref idref="DRAWINGS">FIG. 3</figref>) is responsible for configuring the example intra-VPN connectivity database 305 in response to one or more of conditions, time of day, day of week and/or triggering events.

0033While an example data structure that may be used to implement the example intra-VPN connectivity database 305 of <figref idref="DRAWINGS">FIG. 3</figref> is illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the example data structure of <figref idref="DRAWINGS">FIG. 4</figref> may be implemented using any number and/or type(s) of other and/or additional entries, fields and/or data. Further, the entries, fields and/or data illustrated in <figref idref="DRAWINGS">FIG. 4</figref> may be combined, divided, re-arranged, eliminated and/or implemented in any way. Further still, the example data structures may include entries, fields and/or data in addition to, or instead of, those illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, and/or may include more than one of any or all of the illustrated entries, fields and/or data. Moreover, the example data structure 305 of <figref idref="DRAWINGS">FIG. 4</figref> may be queried using any additional and/or alternative methods.

0034<figref idref="DRAWINGS">FIG. 5</figref> illustrates a flowchart representative of an example process that may be carried out to implement any of the example route servers 140 of <figref idref="DRAWINGS">FIGS. 1</figref> and/or 3. The example process of <figref idref="DRAWINGS">FIG. 5</figref> may be carried out by a processor, a controller and/or any other suitable processing device. For example, the example process of <figref idref="DRAWINGS">FIG. 5</figref> may be embodied in coded instructions stored on any tangible computer-readable medium such as a flash memory, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a read-only memory (ROM), a random-access memory (RAM), a programmable ROM (PROM), an electronically-programmable ROM (EPROM), and/or an electronically-erasable PROM (EEPROM), an optical storage disk, an optical storage device, magnetic storage disk, a magnetic storage device, and/or any other medium which can be used to carry or store program code and/or instructions in the form of machine-accessible instructions or data structures, and which can be accessed by a processor, a general-purpose or special-purpose computer, or other machine with a processor (e.g., the example processor platform P100 discussed below in connection with <figref idref="DRAWINGS">FIG. 6</figref>). Combinations of the above are also included within the scope of computer-readable media. Machine-accessible instructions comprise, for example, instructions and/or data that cause a processor, a general-purpose computer, special-purpose computer, or a special-purpose processing machine to implement one or more particular processes. Alternatively, some or all of the example process of <figref idref="DRAWINGS">FIG. 5</figref> may be implemented using any combination(s) of ASIC(s), PLD(s), FPLD(s), discrete logic, hardware, firmware, etc. Also, some or all of the example process of <figref idref="DRAWINGS">FIG. 5</figref> may instead be implemented manually or as any combination of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, many other methods of implementing the example operations of <figref idref="DRAWINGS">FIG. 5</figref> may be employed. For example, the order of execution of the blocks may be changed, and/or one or more of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, any or all of the example process of <figref idref="DRAWINGS">FIG. 5</figref> may be carried out sequentially and/or carried out in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc.

0035The example process of <figref idref="DRAWINGS">FIG. 5</figref> begins with the example user interface module 330 of <figref idref="DRAWINGS">FIG. 3</figref> determining whether updated intra-VPN connectivity configuration information has been received (block 505). If updated intra-VPN connectivity configuration information has been received (block 505), the example intra-VPN connectivity controller 325 makes corresponding updates to the example intra-VPN connectivity database 305 (block 510). Control then returns to block 505.

0036If updated intra-VPN connectivity configuration information was not received (block 505), the example multi-protocol BGP engine 320 of <figref idref="DRAWINGS">FIG. 3</figref> determines whether a BGP advertisement was received via the example network interface 315 (block 515). If a BGP advertisement was not received (block 515), control returns to block 505.

0037If a BGP advertisement was received (block 515), the multi-protocol BGP engine 320 broadcasts the received BGP advertisement (block 520). The multi-protocol BGP engine 320 queries the intra-VPN connectivity controller 325 to determine whether modified copies of the received BGP advertisement are to be broadcast (block 525). If the intra-VPN connectivity controller 325 determines that no modified copies of the received BGP advertisement are to be broadcast (block 525), control returns to block 505.

0038If based on a query of the example intra-VPN connectivity database 305, the intra-VPN connectivity controller 325 returns one or more RTs (block 525), the multi-protocol BGP engine 320 creates one or more corresponding copies of the received BGP advertisement (block 530), modifies the RT of the copy(-ies) with respective ones of the returned RT(s) (block 535), and broadcasts the modified BGP advertisement(s) (block 540). Control then returns to block 505.

0039<figref idref="DRAWINGS">FIG. 6</figref> is a schematic diagram of an example processor platform P100 that may be used and/or programmed to implement any of the example route servers 140 of <figref idref="DRAWINGS">FIGS. 1</figref> and/or 2. For example, the processor platform P100 can be implemented by one or more general-purpose processors, processor cores, microcontrollers, etc.

0040The processor platform P100 of the example of <figref idref="DRAWINGS">FIG. 6</figref> includes at least one general purpose programmable processor P105. The processor P105 executes coded instructions P110 and/or P112 present in main memory of the processor P105 (e.g., within a RAM P115 and/or a ROM P120). The processor P105 may be any type of processing unit, such as a processor core, a processor and/or a microcontroller. The processor P105 may execute, among other things, the example process of <figref idref="DRAWINGS">FIG. 5</figref> to implement the example methods and apparatus described herein.

0041The processor P105 is in communication with the main memory (including a ROM P120 and/or the RAM P115) via a bus P125. The RAM P115 may be implemented by DRAM, SDRAM, and/or any other type of RAM device, and ROM may be implemented by flash memory and/or any other desired type of memory device. Access to the memory P115 and the memory P120 may be controlled by a memory controller (not shown). One or both of the example memories P115 and P120 may be used to implement the example intra-VPN connectivity database 305 of <figref idref="DRAWINGS">FIG. 3</figref>.

0042The processor platform P100 also includes an interface circuit P130. The interface circuit P130 may be implemented by any type of interface standard, such as an external memory interface, serial port, general-purpose input/output, etc. One or more input devices P135 and one or more output devices P140 are connected to the interface circuit P130. The input devices P135 and/or output devices P140 may be used to, for example, implement the network interface 315 of <figref idref="DRAWINGS">FIG. 3</figref>.

0043Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.

Contents5

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US10178025B2	Cited by	United States of America	Search report
US9401844B2	Cited by	United States of America	Applicant
US11115323B2	Cited by	United States of America	Applicant
US2017118112A1	Cited by	United States of America	Pre-grant
US2002181477A1	Cites	United States of America	Applicant
US2003016672A1	Cites	United States of America	Search report
US2003188001A1	Cites	United States of America	Applicant
US2004148439A1	Cites	United States of America	Applicant
US2005066053A1	Cites	United States of America	Applicant
US2006165087A1	Cites	United States of America	Applicant
US2006168279A1	Cites	United States of America	Applicant
US2006168321A1	Cites	United States of America	Applicant
US2006251088A1	Cites	United States of America	Applicant
US2007133577A1	Cites	United States of America	Applicant
US2007140250A1	Cites	United States of America	Applicant
US2007140251A1	Cites	United States of America	Applicant
US2007195800A1	Cites	United States of America	Applicant
US2007217419A1	Cites	United States of America	Applicant
US2007280241A1	Cites	United States of America	Applicant
US2008002697A1	Cites	United States of America	Applicant
US2008049752A1	Cites	United States of America	Applicant
US2008080517A1	Cites	United States of America	Applicant
US2008170578A1	Cites	United States of America	Search report
US2010111093A1	Cites	United States of America	Applicant
US2010115604A1	Cites	United States of America	Applicant
US5623601A	Cites	United States of America	Applicant
US6079020A	Cites	United States of America	Applicant
US6205488B1	Cites	United States of America	Applicant
US6636898B1	Cites	United States of America	Applicant
US6781982B1	Cites	United States of America	Applicant
US7072346B2	Cites	United States of America	Applicant
US7075933B2	Cites	United States of America	Applicant
US7131141B1	Cites	United States of America	Applicant
US7185106B1	Cites	United States of America	Applicant
US7221675B2	Cites	United States of America	Applicant
US7225270B2	Cites	United States of America	Applicant
US7340519B1	Cites	United States of America	Applicant
US7366188B2	Cites	United States of America	Applicant
US7388844B1	Cites	United States of America	Applicant
US7400611B2	Cites	United States of America	Applicant
US7564802B2	Cites	United States of America	Search report
US7616574B2	Cites	United States of America	Applicant
US7751405B1	Cites	United States of America	Search report
US7870604B1	Cites	United States of America	Applicant
US7912856B2	Cites	United States of America	Applicant
US7921686B2	Cites	United States of America	Applicant
US8027347B2	Cites	United States of America	Applicant
US8064440B2	Cites	United States of America	Applicant
US8117325B1	Cites	United States of America	Applicant
US8117338B2	Cites	United States of America	Applicant
US8121118B2	Cites	United States of America	Applicant
US8549616B2	Cites	United States of America	Applicant
US20020181477A1	Cites	United States of America	Applicant
US20030016672A1	Cites	United States of America	Search report
US20030188001A1	Cites	United States of America	Applicant
US20040148439A1	Cites	United States of America	Applicant
US20050066053A1	Cites	United States of America	Applicant
US20060165087A1	Cites	United States of America	Applicant
US20060168279A1	Cites	United States of America	Applicant
US20060168321A1	Cites	United States of America	Applicant
US20060251088A1	Cites	United States of America	Applicant
US20070133577A1	Cites	United States of America	Applicant
US20070140250A1	Cites	United States of America	Applicant
US20070140251A1	Cites	United States of America	Applicant
US20070195800A1	Cites	United States of America	Applicant
US20070217419A1	Cites	United States of America	Applicant
US20070280241A1	Cites	United States of America	Applicant
US20080002697A1	Cites	United States of America	Applicant
US20080049752A1	Cites	United States of America	Applicant
US20080080517A1	Cites	United States of America	Applicant
US20080170578A1	Cites	United States of America	Search report
US20100111093A1	Cites	United States of America	Applicant
US20100115604A1	Cites	United States of America	Applicant
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due, issued for U.S. Appl. No. 121262,675, mailed on Oct. 17, 2011, 16 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Non-Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on Apr. 15, 2011, 19 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on Oct. 4, 2010, 21 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Non-Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on May 11, 2010, 12 pages.	Non-patent	–	Applicant
Rosen, et al., “BGP/MPLS IP Virtual Private Networks (VPNs),” Network Working Group, Request for Comments: 4364, The Internet Society, Feb. 2006, 47 pages.	Non-patent	–	Applicant
Van Der Merwe, et al., “Dynamic Connectivity Management with an Intelligent Route Service Control Point,” AT&T Labs, Proceedings of the 2006 SIGCOMM Workshop on Internet Network Management, held on Sep. 11-15, 2006, 6 pages.	Non-patent	–	Applicant
Van Der Merwe, et al., PowerPoint presentation of “Dynamic Connectivity Management with an Intelligent Route Service Control Point,” AT&T Labs, Proceedings of the 2006 SIGCOMM Workshop on Internet Network Management, held on Sep. 11-15, 2006, 14 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Final Rejection, issued for U.S. Appl. No. 12/262,615, mailed on Mar. 13, 2012, 12 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Office action, issued for U.S. Appl. No. 12/262,615, mailed on Oct. 4, 2012, 12 pages.	Non-patent	–	Applicant
Cisco: IPv6 over MPLS Cisco IPv6 Provider Edge Router (6PE) Cisco IPv6 VPN Provider Edge Router (6VPE); 2006.	Non-patent	–	Applicant
The United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 12/262,615 on Jun. 3, 2013.	Non-patent	–	Applicant
The United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 12/262,615 on Feb. 20, 2013.	Non-patent	–	Applicant
The United States Patent and Trademark Office, “Advisory action,” issued in connection with U.S. Appl. No. 12/262,615 on Dec. 14, 2012.	Non-patent	–	Applicant
United States Patent and Trademark Office, Notice of Allowance and Fee(s) Due, issued for U.S. Appl. No. 121262,675, mailed on Oct. 17, 2011, 16 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Non-Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on Apr. 15, 2011, 19 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on Oct. 4, 2010, 21 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Non-Final Rejection, issued for U.S. Appl. No. 12/262,675, mailed on May 11, 2010, 12 pages.	Non-patent	–	Applicant
Rosen, et al., "BGP/MPLS IP Virtual Private Networks (VPNs)," Network Working Group, Request for Comments: 4364, The Internet Society, Feb. 2006, 47 pages.	Non-patent	–	Applicant
Van Der Merwe, et al., "Dynamic Connectivity Management with an Intelligent Route Service Control Point," AT&T Labs, Proceedings of the 2006 SIGCOMM Workshop on Internet Network Management, held on Sep. 11-15, 2006, 6 pages.	Non-patent	–	Applicant
Van Der Merwe, et al., PowerPoint presentation of "Dynamic Connectivity Management with an Intelligent Route Service Control Point," AT&T Labs, Proceedings of the 2006 SIGCOMM Workshop on Internet Network Management, held on Sep. 11-15, 2006, 14 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Final Rejection, issued for U.S. Appl. No. 12/262,615, mailed on Mar. 13, 2012, 12 pages.	Non-patent	–	Applicant
United States Patent and Trademark Office, Office action, issued for U.S. Appl. No. 12/262,615, mailed on Oct. 4, 2012, 12 pages.	Non-patent	–	Applicant
Cisco: IPv6 over MPLS Cisco IPv6 Provider Edge Router (6PE) Cisco IPv6 VPN Provider Edge Router (6VPE); 2006.	Non-patent	–	Applicant
The United States Patent and Trademark Office, "Notice of Allowance," issued in connection with U.S. Appl. No. 12/262,615 on Jun. 3, 2013.	Non-patent	–	Applicant
The United States Patent and Trademark Office, "Notice of Allowance," issued in connection with U.S. Appl. No. 12/262,615 on Feb. 20, 2013.	Non-patent	–	Applicant
The United States Patent and Trademark Office, "Advisory action," issued in connection with U.S. Appl. No. 12/262,615 on Dec. 14, 2012.	Non-patent	–	Applicant

8 members in 1 office

This recordMember, by publication datePriority claim

Priority claims1

Priority claims
Document	Office	Kind	Date
26267508	United States of America	A	2008-10-31

Members8

Family members, oldest first
Document	Office	Kind
US2010111093A1	United States of America	A1	2010-05-06
US8121118B2	United States of America	B2	2012-02-21
US2012113991A1	United States of America	A1	2012-05-10
US8929367B2This record	United States of America	B2	2015-01-06
US2015078203A1	United States of America	A1	2015-03-19
US9137109B2	United States of America	B2	2015-09-15
US2015365287A1	United States of America	A1	2015-12-17
US9401844B2	United States of America	B2	2016-07-26

47 transactions on the USPTO file

Allowed after 1 non-final rejection.

Non-final rejections: 1
Final rejections: 0
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2026-08-24	Maintenance Fee Reminder MailedREM.	REM.
2022-06-08	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2018-06-12	Payment of Maintenance Fee, 4th Year, Large EntityM1551	M1551
2015-04-23	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2015-04-22	Correspondence Address ChangeC.AD	C.AD
2015-01-06	Recordation of Patent Grant MailedPGM/	PGM/
2015-01-06	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2014-12-17	Issue Notification MailedAllowedWPIR	WPIR
2014-12-03	Dispatch to FDCD1935	D1935
2014-12-03	Application Is Considered Ready for IssuePILS	PILS
2014-11-28	Issue Fee Payment VerifiedN084	N084
2014-11-28	Issue Fee Payment ReceivedIFEE	IFEE
2014-09-09	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2014-09-07	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2014-09-05	Interview Summary - Examiner Initiated - TelephonicEXET	EXET
2014-09-05	Interview Summary - Examiner InitiatedEXIE	EXIE
2014-09-05	Reasons for AllowanceEX.R	EX.R
2014-09-05	Examiner's Amendment CommunicationEX.A	EX.A
2014-09-05	Information Disclosure Statement consideredIDSC	IDSC
2014-08-16	Date Forwarded to ExaminerFWDX	FWDX
2014-08-14	Mail Interview Summary - Applicant Initiated - TelephonicMEXAT	MEXAT
2014-08-13	Electronic Information Disclosure StatementEIDS.	EIDS.
2014-08-13	Response after Non-Final ActionA...	A...
2014-08-13	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2014-08-07	Interview Summary- Applicant InitiatedEXIA	EXIA
2014-08-07	Interview Summary - Applicant Initiated - TelephonicEXAT	EXAT
2014-05-13	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2014-05-09	Non-Final RejectionNon-final rejectionCTNF	CTNF
2014-05-07	Information Disclosure Statement consideredIDSC	IDSC
2014-05-07	Information Disclosure Statement consideredIDSC	IDSC
2014-04-29	Case Docketed to Examiner in GAUDOCK	DOCK
2014-04-29	Transfer Inquiry to GAUTI1050	TI1050
2013-05-07	Case Docketed to Examiner in GAUDOCK	DOCK
2013-04-19	Case Docketed to Examiner in GAUDOCK	DOCK
2012-10-04	Electronic Information Disclosure StatementEIDS.	EIDS.
2012-10-04	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2012-09-11	Case Docketed to Examiner in GAUDOCK	DOCK
2012-06-05	Electronic Information Disclosure StatementEIDS.	EIDS.
2012-06-05	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2012-05-10	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2012-01-27	Application Is Now CompleteCOMP	COMP
2012-01-27	Application Dispatched from OIPEOIPE	OIPE
2012-01-27	Filing ReceiptFLRCPT.O	FLRCPT.O
2012-01-18	Cleared by OIPE CSRL194	L194
2012-01-13	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2012-01-12	Applicants have given acceptable permission for participating foreignAPPERMS	APPERMS
2012-01-12	Initial Exam Team nnIEXX	IEXX

5 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2021-12-06	Maintenance fee paymentMAFP	MAFP
2018-06-12	Maintenance fee paymentMAFP	MAFP
2014-12-17	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2014-12-04	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2012-10-05	AssignmentAS	AS

Methods and apparatus to dynamically control connectivity within virtual private networks

Summary by NHIP

Claim Score by NHIP

Abstract