Method of connecting VLAN systems to other networks via a router

Information

  • Patent Grant
  • 8437357
  • Patent Number
    8,437,357
  • Date Filed
    Wednesday, May 28, 2008
    16 years ago
  • Date Issued
    Tuesday, May 7, 2013
    11 years ago
Abstract
A local system including at least two VLANs may be connected to a local layer 2 switch to a wider network by providing a connection between the local switch and a router port and a single logical layer 3 interface may be assigned to the VLANs. A VLAN tag may be assigned to each connected VLAN. Outgoing data including the user's address, the intended recipient of the data and the VLAN tag assigned to the VLAN may be communicated to the router. The address of the user and the VLAN tag may be copied to a forwarding table, and the outgoing data may be forwarded to the wider network for delivery to the intended recipient. Incoming date intended for delivery to the user may be received at the assigned layer 3 interface and forwarded to the local switch for delivery to the user.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a national phase application of PCT/EP2008/056563, filed pursuant to 35 U.S.C. §371, which claims priority to EP 07109108.6, filed May 29, 2007. Both applications are incorporated herein by reference in their entirety.


TECHNICAL FIELD

This invention relates to techniques for connecting systems comprising multiple virtual local area networks (VLANs) to a wider network via a router.


BACKGROUND ART


FIG. 1 shows a generic description of a broadband network for providing telephone, internet and TV/video services to subscribers in a number of locations. A series of service providers provide the various services (SP1, SP2, SP3) to the network 10 via conventional access points 12. The network 10 provides connects these to subscribers via routers 14 located close to the subscribers. These can include business locations that can include routers in commercial property 16, and domestic subscribers with routers located in a central office 18 for a neighbourhood of separate dwellings (houses 17), or in a single building 19 such as an apartment building. The network operator manages the network function by the use of a control and provisioning system 20.


Certain users, particularly business users, like to be able to operate local area networks (LANs). To support this while still having connectivity to a wider network, a series of products and solutions are currently available to allow Layer 2 LANs and virtual LANs (VLANs) to be provided. VLANs allow an effectively separate LAN to be established within a single physical infrastructure. A simple VLAN system is shown in FIG. 2 and comprises a local (layer 2) switch 2 that has a number of connections 4 to the various users connected to the VLAN and a physical connection 6 to a port on the router 14. The router will have a fixed number of ports available for such connections. One example, the ASR4K of Packetfront has 32 ports available. The router 14 provides layer 3 interfaces 8 for the connected VLANS and is connected to the wider network 10. The local switch 2, user connections 4 and connection 6 to interface 8 define a Layer 2 segment VLAN.


The system of FIG. 2 has one VLAN connected via the local switch 2. However, it can often be desirable to operate more than one VLAN from a local switch. Details of the general approach for such solutions can be found in the white paper ‘Layer 2 Virtual Private Networks’, December 2005 from World Wide Packets Inc of Spokane Valley Wash. USA (see http://www.wwp.com/technology/white-papers/L2-VPN-WhitePaper.pdf). Local switch devices, such as the LightningEdge devices from World Wide Packets, allow several VLANs to be connected to a router for access to a wider network. In accordance with the appropriate standards (IEEE 802.1Q), tags are associated with each VLAN as identifiers. Up to 4094 tags/VLANs are available for each device. When these devices are connected to routers (e.g. router 14 of FIG. 1), the routers typically assign a logical layer 3 interface for each VLAN. Therefore, including the tag in the addressing for data allows it to be directed to the appropriate VLAN.


Various proposals have been made for connecting to VLANs. In US2007/058638, a routing mechanism provides network segmentation preservation by route distribution with segment identification, policy distribution for a given VPN segment, and encapsulation/decapsulation for each segment using an Ethernet VLAN_ID, indicative of the VPN segment (subnetwork). Encapsulated segmentation information in a message packet identifies which routing and forwarding table is employed for the next hop. A common routing instance receives the message packets from the common interface, and indexes a corresponding VRF table from the VLAN ID, or segment identifier, indicative of the subnetwork (e.g. segment). In this manner, the routing instance receives the incoming message packet, decapsulates the VLAN ID in the incoming message packet, and indexes the corresponding VRF and policy ID from the VLAN ID, therefore employing a common routing instance over a common subinterface for a plurality of segments (subnetworks) coupled to a particular forwarding device (e.g. VPN router). The system described in U.S. Pat. No. 7,200,145 uses a layer 2 switch (L2 switch), or bridge, to separate user's message traffic by use of Virtual Local Area Networks (VLANs) defined within the switch. Three new types of ports are defined, “promiscuous” ports “isolated” ports, and “community” ports. Three types of VLANs internal to the switch are defined, “primary” VLANs, “isolated” VLANs and “community” VLANs. The promiscuous ports are connected to layer 3 or layer 4 devices. Isolated ports and community ports are connected to individual user's servers, etc., and maintain traffic for each user separate from other users. The primary VLAN connects to all promiscuous ports, to all isolated ports, and to all community ports. The primary VLAN is a one way connection from promiscuous ports to isolated or community ports. An isolated VLAN connects to all promiscuous ports and to all isolated ports. The isolated VLAN is a one way connection from an isolated port to the promiscuous ports. A community VLAN is defined as connecting to a group of community ports, and also connecting to all of the promiscuous ports. The group of community ports is referred to as a “community” of community ports. A community VLAN is a one way connection from a community of ports to the promiscuous ports, but allows a packet received by one community port to be transmitted out of the switch, through the other community ports connected to that community VLAN.


A number of problems exist with current approaches for connecting multiple VLAN systems. One is that assigning a separate logical layer 3 interfaces to each VLAN can quickly use up memory in the router, especially for lower end routers with limited memory. Another is that VLAN to VLAN communication can require the use of a Layer 2 switch which sits between the local switch and the router. As such a communication path avoids the router; it can also avoid router functions such as filters and firewalls which can be undesirable.


It is an object of the invention to provide a technique which allows direct access for all VLANs to the router without these problems.


DISCLOSURE OF THE INVENTION

One aspect of this invention provides a method for connecting a local system comprising at least two VLANs connected to a local layer 2 switch to a wider network via a router, the method comprising:

    • providing a connection between the local switch and a port on the router;
    • assigning a single logical layer 3 interface to the two VLANs connected via the local switch;
    • assigning a VLAN tag to each connected VLAN;
    • communicating outgoing data from a user connected to one of the two connected VLANs to the router via the local switch, the outgoing data including the address of the user in the VLAN, the intended recipient of the data and the VLAN tag assigned to the VLAN to which the user is connected;
    • on receipt of the outgoing data at the router, copying the address of the user and the VLAN tag to a forwarding table;
    • forwarding the outgoing data from the assigned layer 3 interface to the wider network for delivery to the intended recipient;
    • receiving at the layer 3 interface incoming data intended for delivery to the user, the data including the address of the user;
    • consulting the lookup table to obtain the VLAN tag associated with the address of the user;
    • applying the VLAN tag to the incoming data; and
    • forwarding the incoming data and VLAN tag to the local switch for delivery to the user.


Another aspect of this invention provides a system for connecting a user in a local system comprising a VLAN to a wider network, comprising:

    • a local layer 2 switch to which the VLAN is connected, the local switch having at least two VLANs connected thereto and being configured to assign a VLAN tag to each connected VLAN; and
    • a router for receiving outgoing data from a user connected to one of the VLANs via the local switch, the outgoing data including the address of the user in the VLAN, the intended recipient of the data and the VLAN tag assigned to the VLAN to which the user is connected, the local switch being connected to a port on the router;


      wherein the router assigns a single layer 3 interface to the connected VLANs and, on receipt of the outgoing data, copies the address of the user and the VLAN tag to a forwarding table and forwards the outgoing data to the wider network via the layer 3 interface for delivery to the intended recipient; and on receipt of incoming data at the assigned layer 3 interface intended for delivery to the user which includes the address of the user, consults the lookup table to obtain the VLAN tag associated with the address of the user, applies the VLAN tag to the incoming data, and forwards the incoming data and VLAN tag to the local switch for delivery to the user.


In preferred embodiments, multiple local switches are provided, each of which has multiple VLANs connected thereto. Similarly, multiple routers can be provided.


Each local switch is preferably connected to a single logical port on the router.


The wider network is typically a broadband network that can provide internet, TV and phone connectivity for users.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a generic network system in which the invention can be used;



FIG. 2 shows a prior art configuration for a VLAN connected to a router; and



FIG. 3 shows a schematic of a system according to an embodiment of the invention.





MODE(S) FOR CARRYING OUT THE INVENTION

A network system in which the invention operates is shown in FIG. 1. Operation of the network 10 is controlled by a control and provisioning system 20 that configures the various elements of the network to operate in the desired manner.


For the function of the control and provisioning system 20, the network can be considered in an abstract way as comprising a core 22 having one or more cells 24, each cell having one or more network elements 26 as is shown in FIG. 3. Subscribers 28 connect to the network elements 26. This structure is not to be confused with the physical elements making up the network. The functional blocks 22, 24, 26 may be wholly or partly resident in the same or different physical elements, depending on the exact size and makeup of the network in question, although typically, each network element 26 will comprise a router.


In one embodiment of the invention, the subscribers 28 comprise local (layer 2) switches having a number of VLANs 30 connected thereto. Each VLAN will typically have a number of individual users in the conventional manner.


In use, the local switches 28 are provided with a single physical connection to the router 26 with one or more logical layer 3 interfaces being assigned to this connection. Typically one layer 3 interface is assigned to all of the connected VLANs but it is also possible to sub-divide the connected VLANs into groups, each with an assigned layer 3 interface. By assigning single layer 3 addresses to multiple VLANs, it is possible to connect a larger number of VLANs to the router without excedding its memory capacity. A user connected to one of the VLANs communicates with the network by sending data over the VLAN that includes its logical address in the normal manner. The local switch provides the VLAN tag for that data to identify in which VLAN the user is connected.


The outgoing data, including the VLAN tag is sent to the assigned layer 3 interface on the router 26. On reception of the outgoing data, the router 26 reads the addressing and loads the user address and associated VLAN tag into a forwarding table 32. The data is then forwarded to the wider network using the recipient address in the usual manner.


Incoming data will be addressed to the user with the usual logical address, i.e. not including the VLAN tag. On receipt of the incoming data, the router 26 consults to lookup table 32 to determine the VLAN tag associated with the logical destination address of the user and appends it to the data. This is then communicated to the local switch which in turn directs the data to the appropriate VLAN on which the user is located.


Because the router 26 can assign a single layer 3 interface to multiple VLANs, a relatively lower specification router can be used to provide connectivity for a large number of users. Since the router 26 is also typically under the control of the network operator, it is also possible to control interface assignment for the VLANs. From the user point of view, it is possible to communicate with other VLANs via the router and so get the benefit of all of the router functions (firewall, filtering, etc.).


Various changes to the system described above can be made while staying within the scope of the invention. Two or more local switches 28 can be connected to a router 26. Likewise, more than one router can have multiple VLANS attached via local switches in this way. Other such changes will also be apparent.

Claims
  • 1. A method for connecting a local system comprising at least two VLANs connected to a local layer 2 switch to a wider network via a router, the method comprising: providing a connection between the local layer 2 switch and a port on the router;assigning, at the layer 2 switch, a VLAN tag to each connected VLAN;communicating outgoing data from a user connected to one of the at least two connected VLANs to the router via the local layer 2 switch, the outgoing data including an address of the user in the VLAN, the intended recipient of the data and the VLAN tag assigned to the VLAN to which the user is connected;assigning, at the router, a single logical layer 3 address of a layer 3 interface to the at least two VLANs connected via the local layer 2 switch;copying the address of the user and the VLAN tag to a forwarding table upon receipt of the outgoing data at the router;forwarding the outgoing data including the single layer 3 address from the assigned layer 3 interface to the wider network for delivery to the intended recipient;receiving at the layer 3 interface incoming data intended for delivery to the user, the data including the single logical layer 3 address without the VLAN tag;consulting the lookup table to obtain the VLAN tag associated with the address of the user;applying the VLAN tag to the incoming data; andforwarding the incoming data and VLAN tag to the local layer 2 switch for delivery to the user.
  • 2. A method as claimed in claim 1, wherein multiple local layer 2 switches are provided, each having multiple VLANs connected thereto.
  • 3. A method as claimed in claim 1, comprising assigning a single layer 3 interface to all VLANs connected to the local layer 2 switch.
  • 4. A method as claimed in claim 1, comprising assigning multiple layer 3 interfaces, at least one of which is assigned to multiple VLANs.
  • 5. A system for connecting a user in a local system comprising a VLAN to a wider network, comprising: a local layer 2 switch to which the VLAN is connected, the local layer 2 switch having at least two VLANs connected thereto and being configured to assign a VLAN tag to each connected VLAN; anda router for receiving outgoing data from a user connected to one of the VLANs via the local layer 2 switch, the outgoing data including the address of the user in the VLAN, the intended recipient of the data and the VLAN tag assigned to the VLAN to which the user is connected, the local layer 2 switch being connected to a port on the router;wherein the router assigns a single logical layer 3 address of a layer 3 interface to the connected VLANs and, on receipt of the outgoing data, copies the address of the user and the VLAN tag to a forwarding table and forwards the outgoing data including the single logical layer 3 address to the wider network via the layer 3 interface for delivery to the intended recipient; and on receipt of incoming data at the assigned layer 3 interface intended for delivery to the user which includes the single logical layer 3 address without the VLAN tag, consults the lookup table to obtain the VLAN tag associated with the address of the user, applies the VLAN tag to the incoming data, and forwards the incoming data and VLAN tag to the local layer 2 switch for delivery to the user.
  • 6. A system as claimed in claim 5, further comprising multiple local layer 2 switches connected to the router, each local layer 2 switch having a number of VLANs connected thereto.
  • 7. A system as claimed in claim 5, comprising a number of routers, each with one or more local layer 2 switches connected thereto.
  • 8. A system as claimed in claim 5, wherein each local layer 2 switch is connected to a respective single logical layer 3 interface on the router.
Priority Claims (1)
Number Date Country Kind
07109108 May 2007 EP regional
PCT Information
Filing Document Filing Date Country Kind 371c Date
PCT/EP2008/056563 5/28/2008 WO 00 6/9/2010
Publishing Document Publishing Date Country Kind
WO2008/145677 12/4/2008 WO A
US Referenced Citations (83)
Number Name Date Kind
5586255 Tanaka et al. Dec 1996 A
5659736 Hasegawa et al. Aug 1997 A
5684988 Pitchaikani et al. Nov 1997 A
5689598 Dean, Jr. et al. Nov 1997 A
5802042 Natarajan et al. Sep 1998 A
5832503 Malik et al. Nov 1998 A
5913037 Spofford et al. Jun 1999 A
6028769 Zurek Feb 2000 A
6059614 Shelby et al. May 2000 A
6122639 Babu et al. Sep 2000 A
6222852 Gandy Apr 2001 B1
6233616 Reid May 2001 B1
6286038 Reichmeyer et al. Sep 2001 B1
6393472 Anerousis et al. May 2002 B1
6430621 Srikanth et al. Aug 2002 B1
6560236 Varghese et al. May 2003 B1
6680945 Merchant et al. Jan 2004 B1
6769124 Schoening et al. Jul 2004 B1
6839749 Bera Jan 2005 B1
6876667 Synnestvedt et al. Apr 2005 B1
6885657 Rabenko et al. Apr 2005 B1
6954436 Yip et al. Oct 2005 B1
6958996 Xiong Oct 2005 B2
7054309 Hoot et al. May 2006 B1
7082463 Bradley et al. Jul 2006 B1
7099158 Bjorklund Aug 2006 B1
7139818 Kinnear, Jr. et al. Nov 2006 B1
7200145 Edsall et al. Apr 2007 B1
7218827 Vongseng et al. May 2007 B2
7386629 Rover et al. Jun 2008 B2
7581024 Yip et al. Aug 2009 B1
7760984 Solheid et al. Jul 2010 B2
7801133 Siegel Sep 2010 B2
7826463 Patel et al. Nov 2010 B2
7945164 Theodoras, II May 2011 B2
7948993 Kini et al. May 2011 B2
7969880 Yano et al. Jun 2011 B2
7983190 Hirota Jul 2011 B2
7990994 Yeh et al. Aug 2011 B1
20020023174 Garrett et al. Feb 2002 A1
20020075844 Hagen Jun 2002 A1
20020161801 Hind et al. Oct 2002 A1
20030039249 Basso et al. Feb 2003 A1
20030056225 Bione Mar 2003 A1
20030131107 Godse et al. Jul 2003 A1
20030165140 Tang et al. Sep 2003 A1
20030200285 Hansen et al. Oct 2003 A1
20030206548 Bannai et al. Nov 2003 A1
20040013126 Yun Jan 2004 A1
20040017829 Gray et al. Jan 2004 A1
20040047353 Umayabashi et al. Mar 2004 A1
20040049568 Nguyen et al. Mar 2004 A1
20040052216 Roh Mar 2004 A1
20040090965 Lin May 2004 A1
20040128367 Piercy et al. Jul 2004 A1
20040160464 Reyna Aug 2004 A1
20040172412 Files et al. Sep 2004 A1
20040213152 Matuoka et al. Oct 2004 A1
20040258074 Williams et al. Dec 2004 A1
20040267949 Rover et al. Dec 2004 A1
20050044265 Vinel et al. Feb 2005 A1
20050049886 Grannan et al. Mar 2005 A1
20050129379 Reagan et al. Jun 2005 A1
20050216584 Chisholm Sep 2005 A1
20050281526 Vongseng et al. Dec 2005 A1
20050286517 Babbar et al. Dec 2005 A1
20060002324 Babbar et al. Jan 2006 A1
20060026228 Kim Feb 2006 A1
20060047791 Bahl Mar 2006 A1
20060085532 Chu et al. Apr 2006 A1
20060261116 Brandeis Nov 2006 A1
20060277603 Kelso et al. Dec 2006 A1
20070058538 Chiang et al. Mar 2007 A1
20070058638 Guichard et al. Mar 2007 A1
20070061458 Lum Mar 2007 A1
20070168547 Krywaniuk Jul 2007 A1
20070174522 Lee Jul 2007 A1
20070203999 Townsley et al. Aug 2007 A1
20070286198 Muirhead et al. Dec 2007 A1
20080162609 Bigian et al. Jul 2008 A1
20080219281 Akin et al. Sep 2008 A1
20080285569 Stademann et al. Nov 2008 A1
20110161360 Lundstrom Jun 2011 A1
Foreign Referenced Citations (15)
Number Date Country
1 039 698 Sep 2000 EP
1780941 May 2007 EP
2 069 767 Jan 1981 GB
20010038481 May 2001 KR
WO9534975 Dec 1995 WO
WO 0060864 Oct 2000 WO
WO 0235797 May 2002 WO
WO 2008068316 Jun 2008 WO
WO 2008113852 Sep 2008 WO
WO 2008113854 Sep 2008 WO
WO 2009019300 Feb 2009 WO
WO 2009027513 Mar 2009 WO
WO 2009047215 Apr 2009 WO
WO 2009047334 Apr 2009 WO
WO 2009047345 Apr 2009 WO
Non-Patent Literature Citations (13)
Entry
Bodzinga, Anne, et al., “Interworking IPTV Services with IMS”, Telecommunications Network Strategy and Planning Symposium 2006 pp. 1-5.
European Search Report issued in EP Application 06125497, Publication 1931085, mailed Jan. 9, 2009, 8 pages.
International Search Report and Written Opinion for PCT/EP2008/053369, mailed Jul. 2, 2008, 10 pages.
International Search Report and Written Opinion for PCT/EP2008/060384, mailed Nov. 11, 2008, 10 pages.
International Search Report and Written Opinion for PCT/EP2008/061403, mailed Dec. 18, 2008, 12 pages.
International Search Report and Written Opinion for PCT/EP2007/063467, mailed Mar. 4, 2008, 7 pages.
International Search Report for PCT/EP2008/053374, mailed Sep. 25, 2009, 3 pages.
International Search Report and Written Opinion for PCT/EP2008/056563, mailed Aug. 21, 2008, 11 pages.
International Search Report for PCT/EP2008/063667, mailed Jul. 30, 2009, 3 pages.
International Search Report for PCT/EP2008/063639, mailed Oct. 1, 2009, 2 pages.
International Search Report for PCT/EP2008/063270, mailed Jan. 21, 2009, 3 pages.
International Search Report and Written Opinion for PCT/EP2008/056565, mailed Jan. 19, 2009.
European Search Report issued in EP Application 07104707, Publication 1973269, dated Aug. 27, 2007, 7 pages.
Related Publications (1)
Number Date Country
20100254396 A1 Oct 2010 US