Title of Invention	"A ROUTER FOR ROUTING IN VIRTUAL PRIVATE NETWORK AND A NETWORK COMPRISING THE SAME"
Abstract	A network comprising a gateway GPRS support node (GGSN) serving at least one virtual private network (VPN), whereby the gateway GPRS support node comprises at least two virtual private network (VPN) routing/forwarding instances per internet protocol (IP) interface has been shown. A router with directional specific properties has moreover been disclosed.

Full Text

Routing in virtual private network Field of the invention The invention relates to the technical field of TCP/IP routing and forwarding and relates especially to concepts within virtual private networks (VPNs). The main applications for the invention are IP routers with high VPN scalability demands, such as the GGSN (Gateway GPRS Switching Node) in GPRS (General Packet Radio Service) networks. The invention relates to WPP 5.0 (Wireless Packet Platform). Background of the invention A Virtual Private Network (VPN) is an extension to a network that is remotely administrated. This network is carried over the local network via tunnelling, either in protocols that either can be IP based or not IP based (for example ATM). When extending these networks into mobile packet data networks, a single node must handle a large number of VPNs. This implicates that the management and configuration of all these extensions to the VPNs has to be managed by the operator managing the mobile packet network. In for example GPRS (General Packet Radio Service), the GGSN (Gateway GPRS Switching Node) connects the mobile network to the remotely administrated network. Figure 1 depicts a schematic overview of such a GPRS network with the GGSN. Figure 2 depicts an example with traffic between two mobile stations. This example shows that the administrator of the GGSN has to manage the packet filtering rules that protects the mobile stations from each other. The traffic between mobile stations cannot be monitored from a remotely administrated network. One known solution is based on an implementation of packet filtering doing packet forwarding. By defining a packet filter that forwards all traffic from one interface or tunnel to another interface or tunnel, the routing information in the forwarding table will not be considered and the traffic can be forced to a remote network. Another known WPP solution to the problem is to directly map traffic from one interface/tunnel into another interface or tunnel, without making a forwarding decision based on the destination IP address. This known solution is called APN (Access Point Name) Routing. The disadvantage with the above solutions is poor redundancy, since the packet filters (or mapping table) are not dynamically updated and the interface or tunnel that the packets are forwarded to might be unavailable due to link or network problems. Fig. 3 shows two nodes A and B and a router R being physically connected to an Ethernet segment ETH S. Two virtual private networks VPN_1 and VPN_2 are implemented over the common Ethernet segment ETH_S. Node A comprises a first and a second IP interface IP_lF1 and IP_lF2. The IP interfaces IP_lF1 and IP_lF2 at the IP layer 3 are mapped to the given unique layer 2 MAC (Media Access Control) Ethernet address ETHJF1 by means of the ARP (automatic Request Protocol) protocol. Likewise interfaces IPIF3 and IP_lF4 are mapped to Ethernet interface ETHJF2 of node B. IP interfaces IP_lF5 and IP_lF6 is mapped to ETHJF2 on router RT. IP_lF1 of node A forms a first virtual private network VPN_1 with IP_IF3 of node B. IP_IF4 of node B forms a second virtual private network VPN_2 with IP_lF6 of router RT. IP Packets may be communicated between the respective IP interfaces over the respective VPN's. To the various IP interfaces of each respective VPN it appears that the Ethernet segment is exclusive. Fig. 4 shows an exemplary IP packet delivered from IP interface IP_lF3 to IP_lF1 on VPN_1 for the network shown in fig. 3. The IP packet is encapsulated in an Ether packet with source address ETHJF2 and destination address ETHJF1. It has an Ethernet type identification of type "VLAN" - Virtual Local Area Network - and carries a corresponding network identifier VPN_1 and a second Ethernet type identifier IPv4 pertaining to the version of the IP protocol being used. In the Ethernet payload ETH_PL there is provided the IP source and destination addresses mentioned above and the IP payload. The packet is ended by an Ethernet cyclical redundancy check value ETH CRC. In fig. 5 an exemplary prior art network has been shown comprising a router RT providing a first virtual private network VPN_1 via forwarding table VRF_1 providing interconnectivity for IP interfaces 1P_lF1,1P_lF2 and IP_lF3. The router moreover provides a second virtual private network VPN_2 via forwarding table VRF_2 providing interconnectivity for IP interfaces IP_IF5 and IP_lF6. Summary of the invention It is first object of the invention to set forth a router that allows for selective routing depending on traffic direction. This object has been accomplished by claim 1. It is a secondary object to set forth a router that allows for communication between various private networks. This object has been accomplished by claim 2. It is a third object to set forth a system allowing for forced traffic over a specific interface. This object has been accomplished by claim 6. It is a fourth object to set forth a system in which packet control is deferred to a corporate network. This object has been accomplished by claim 7. According to a further aspect of the invention, in order to increase the security in a VPN network it is desired that all traffic (i.e. IP packets) from mobile terminals always shall go via the home network. This gives the VPN administrator the possibility to specify the packet filtering rules to be applied both for traffic destined to a mobile terminal, as well as for traffic coming from a mobile terminal. This is independent of whether the packets are destined to the same mobile network extension as the packet originated from, or not. Without forcing traffic to the home network, the packet filtering rules would have to be configured by the operator of the mobile extension to the VPN network instead of the administrator of the home network. Further advantages of the invention will appear from the following detailed description of preferred embodiments of the invention. Brief description of the drawings Fig. 1 shows an overall diagram of the GPRS network architecture, fig. 2 shows a known method of performing routing in a GPRS network, fig. 3 shows a known way of implementing virtual private networks (VPN) on an Ethernet segment, fig. 4 shows a packet used in fig. 3, fig. 5 shows a prior art router providing two VPN networks, fig. 6 shows a first embodiment of a router according to the invention, fig. 7 shows a second embodiment of a VPN network according the invention including a packet flow form a node A to a node B, fig. 8 shows the same VPN network as in fig 7, including a packet flow form a node B to a node A, fig. 9 shows an application of the present invention in a GPRS network, and fig. 10 shows a fourth embodiment according to the invention. Detailed description of preferred embodiments of the invention According to the invention, multiple VRF's (VPN Routing/Forwarding instances) are used per IP interface. An IP interface can for example be a bi-directional lP-in-lP tunnel or an IP-over-Ethernet interface. The forwarding table that is used to route traffic from a given interface may not route traffic to the same IP interface. This distinction makes it possible to let traffic in one direction belong to one VRF and traffic in the other direction belong to another VRF. Furthermore, if the interface has multiple peers, each peer end-point can belong to different VRF's. Fig. 6 shows a first embodiment of the invention, comprising a router RT comprising router tables VRF_1 and VRF_2 and IP interfaces IP_lF1, providing access to a GTP tunnel GTP_A, which connects to a first mobile station MS_A and IP interface 1P_lF2, providing access to a second GTP tunnel GTP_B that connects to mobile station MS_B. The router moreover comprises a third IP interface IP_lF3 that connects to GRE tunnel GRE_RT providing connection to a VPN access net, such as a corporate Intranet. As indicated by the arrows, forwarding table VRF_1 routes packets form IP interface IP_lF3 to IP interface IP_(F1 and IP_lF2 depending on which mobile station the given packet is intended for. Forwarding table VRF_2 route packets from source MS_A and MS_B to IP interface IP_IF3 and further to the VPN access net. Thereby, the traffic between mobile stations MS_A and MS_B can be controlled by the VPN access net. Fig. 7 shows a further embodiment of the invention in which a first router RT connects to an Ethernet segment ETH_S via IP interfaces IP_lF1, 1P_lF2 and IP_lF3, forming respective virtual private networks VLAN1, VLAN2 and VLAN3 and an Ether router interface ETH_IF. The first router comprises a first forwarding table VRF_1 and forwarding table VRF2. A node A connects to the router via virtual local area network VLAN1 and a node B connects to the router via virtual local network VLAN2 over the common Ethernet segment ETH_S. A second router R comprising forwarding table VRF_T connects VLAN3 over the common Ethernet segment ETH_S. The second router also connects to the Internet. Forwarding tables VRF_1 defines for destination A a next hop of IP interface 1P_lF1 and for destination node B IP interface IF2. Forwarding tables VRF_2 defines interface IP_lF3 as default next hop address. Forwarding table VRF_R defines IP interface IPIF_3 for both destinations A and B. A packet sent from mobile station A to B is forwarded along arrow 10 through IP interface IPIF_1 to forwarding table VRF_2 and further on to IP interface IPIF_3 to router R, arrow 20, and back again to IP interface IPIF_3 and to forwarding table VRF_1. Forwarding table VRF_1 defines IP interface !PlF_2 as next hop for destination B, and consequently the packet is transmitted to node B along arrow 30. The router is being configured such that in the event that a mobile station on one interface IP_lF1 is communicating with a mobile station on interface 1P_lF2, the traffic may be routed via the second interface IP_lF3. In fig. 8 the opposite path of transmitting a packet has been shown as indicated by arrows 40, 50 and 60. It should be understood that the many other technologies that Ethernet could be used on the data link layer. As shown above, the forwarding table for a VRF can only have routes to interfaces that in the outbound direction belong to the VRF. The question of which VRF to use for the forwarding decision is selected from the VRF configuration for the inbound direction of the receiving interface. The definition of interfaces in both outbound and inbound direction can be extended to also consider the source and destination peers (can for instance be identified via link level addresses) to allow different VRFs for different remote peers (for example routers) on a multi-access link. The distinction between inbound and outbound direction provides the possibility that an interface can be used by multiple VRFs in the outbound direction. That is, several VRFs can use the same outbound link. In figure 7, it is shown how both VRF_1 and VRF_2 use the same outbound link, for instance IPIF_3. This feature is very useful together with broadcast and multicast based services. One example is that it makes it possible to have a separate multicast VPN that gives multicast services that several other VPNs can use. Traffic from the multicast network can be forwarded into another VPN where the end-users of the service are connected. The benefit of doing this is that the common services between the networks can use one common network architecture that enables more efficient use of the transport links. This is how multicast networks are used to give better performance, but multicast services are currently not possible to share between VPNs and this invention provides a solution to the problem. The main problem in WPP solved by the invention is that it allows GGSN nodes to defer packet filtering to a remote network to decrease the need of packet filtering configurations for the manager of the GGSN node. The present invention provides a scalable routing solution towards the external networks. Figure 9 depicts a third preferred embodiment of the invention in which traffic between two mobile stations MS#1 and MS#2, belonging to the same corporate network as the router holding VRF#23, according to the invention. VRF#37 and VRF#42 are used in the GGSN and VRF#23 is used in the router. The invention is used in the GGSN. For traffic from the mobile stations VRF#42 is used. For traffic from the router VRF#37 is used. VRF#42 has the Router as next hop for all the routes in the forwarding table. This means that all traffic from the mobiles is sent to the router. VRF#37 has the SGSN (Serving GPRS Support Node) as next hop for the two mobile stations. This means traffic from the Router destined to the Mobile Stations are sent to the SGSN. Traffic from the router which is not destined to the Mobile Stations are sent back to the router as the forwarding table for VRF#37 has an default route pointing out the router as next hop for all traffic which is not destined to the mobile stations. The router only has one VRF (VRF#23) for all its interfaces. The router is a normal router. A packet sent from one of the mobile station destined to the other mobile station is sent to the GGSN via the SSGN. The GGSN performs a forwarding lookup (using the forwarding table of VRF#42) and then routes the packet to the router. The router performs a forwarding lookup and routes the traffic back to the GGSN as the forwarding table for VRF#23 points out the GGSN as next hop for the mobile stations. The GGSN once again makes a forwarding lookup (using the forwarding table of VRF#37) and then routes the packet to the SGSN. The SGSN delivers the packet to the receiving mobile station. It should be noted that, a third mobile station not belonging to the corporate network would not use the tunnel shown in fig. 3. Another parallel set of tunnels and forwarding tables would be set up. Figure 9 shows an example of how the Network Management responsibilities can be divided between different administrators. In this figure, the mobile stations MS#1, MS#2 and the router holding VRF#23 belong to the same corporate network, designated "Corporate", and all administration for this network is handled by the corporate network administrator. By way of example, a first operator, Operator 1, controls the SGSN node and a second operator, Operator 2, controls the GGSN node. There is a clear separation between GPRS network administration and the administration of the corporate network. This example also shows, when applicable, the separation between the SGSN and GGSN operators. It is a strong business case for an operator to provide the corporate networks with a service, making it possible for the corporate network administrator to configure the packet filters for the mobile stations and monitor all traffic to and from mobile stations. It is therefore a strong business case for a GGSN vendor to provide an operator with equipment implementing this invention. It should be noted that forwarding tables VRF#37 and VRF#42 are controlled by Operator 2 in accordance with whatever agreement exists between Corporate and Operator 2. The ability to route packets to the VRF in the opposite direction for an interface have been implemented. This is necessary to implement, if ICMP messages shall be supported. The VRF for the opposite direction is easy to find, since ICMP messages are generated for an outbound interface and the packet can then be handled as if it had arrived on that interface. The forwarding table in a VRF can be updated by a routing daemon. Routing daemons receive their routing information from different interfaces and can treat these interfaces as belonging to different routing areas. By separating the inbound and outbound direction of these interfaces, the routing protocol can be configured to filter which information to send to different interfaces. Thereby, the directions of the routing updates can be separated; if the routing protocol used for route announcements supports unidirectional links. The invention can for example be used for IPv4 and IPv6. Both IPv4 and IPv6 interfaces can be bi-directional or unidirectional. The present invention provides the possibility for a router (or host) to treat bi-directional interfaces as two uni-directional interfaces at the same time as the peer routers (or hosts) view the interface on the router (or host) as a bi-directional interface. In other words, the surrounding network environment is not affected by the use of the invention, if it is not deliberately used in such a way. The invention has a high potential to solve many current and future problems in different areas of IP routing, since it is a fundamental change of how interfaces are treated in IP routing and forwarding environments. Abbreviations ATM Asynchronous Transfer Mode APN In the GPRS backbone, an Access Point Name (APN) is a reference to a GGSN. To support inter-PLMN roaming, the internal GPRS DNS functionality is used to translate the APN into the IP address of the GGSN. GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile communication ICMP Internet Control Message Protocol (RFC 792) IP Internet Protocol (RFC 791) IP IF IP interface SGSN Serving GPRS Support Node TCP Transmission Control Protocol (RFC 793) TCP/IP Suite of protocols, including IP, TCP UDP, ICMP and other protocols UDP User Datagram Protocol (RFC 768) UMTS Universal Mobile Telephone System VPN Virtual Private Network. VRF VPN Routing/Forwarding instance WPP Wireless Packet Platform We Claim: 1. A router (RT) for routing in a virtual private network, said router comprising: at least two IP interfaces (IPIF_1 ; IPIF_2 ; IPIF_3), wherein each IP interface is associated with a respective virtual local area network (VLAN1; VLAN2; VLAN3); at least two forwarding tables (VW_1 ; VRF_2), wherein a first of said forwarding tables (VIW_1 ; VW2) is used for routing traffic towards a first of said IP interfaccs ( 11'11:_1 ; IPIF_2 ; IPIF_3), and a sccond of said forwarding tables (VR.F_2 ; VRF_1) is used for routing traffic from the first IP interface (IPIF_I ; IPIF_2 ; IPIF _ 3); wherein thc first IP intcrfacc is coupled to a first tunnel providing bi_directional connectivity to mobile stations and a second IP interface is coupled to a second tunnel providing bi_directional connectivity to a corporate network; and wherein a third interface provides bi_ directional connectivity to mobile stations, and wherein the router routes the traffic via the second interface in the event that a mobile station on the first IP interface is communicating with a mobile station on the third interface. 2. ?'he router as claimed in claim 1, wherein packets received on one IP intcrfacc (IPII;'_.l; IPII; 2 ; IPIF 3 ) and relating to one given virtual local area nctwork (VI,AN 1 ; VLAN2; VLAN3) is forwarded to anothcr IP interface (IPIF_1 ; IPIF_2 ; IPI113) rclating to another virtual local area network (VLAN 1 ; VLAN2; VLAN3). 3. The router as claimcd in claim 1, wherein the packets from one mobile station (MSA) to another mobile station (MSB) are forwarded to a remote router (R), the remote router being adapted for taking a policy decision, such as to discard packets. 4. A Network comprising a router (RT) for routing in a virtual private network, said router comprising: at least two IP interfaces (IPIF _ 1 ; IPIF_2 ; IPIF_3), wherein each IP interface is associated with a respective virtual local area network (VLAN1; VLAN2; VLAN3); and at least two forwarding tables (VRF_1 ; VW_2); wherein a first table (VRF_1 ; VRT; _ 2) of the two forwarding tables is used for routing traffic towards a given interface (IPIF_1 ; IPIF_2 ; IPIF_3 and the second table ( V m 2 ; VW_1) of the two forwarding tables is used for routing traffic appearing from the first IP interface (IPIF_1 ; IPIF _ 2 ; IPIF _ 3), wherein the two tables together allow bidirectional traffic from the same first IP interface; wherein packets received on the first IP interface (IPIF_1 ; IPIF_2 ; IPIF _ 3) and relating to a first virtual local area network (VLAN1; VLAN2; VLAN3) are forwarded to a second IP interface (IPIF _ 1 ; IPIF _ 2 ; IPIF_3) relating to a second virtual local area network (VLAN 1 ; VLAN2; VLAN3); wherein the first IP interface (IP _ IF1) is coupled to a first tunnel (GTP_A) providing bi_dircctional connectivity to mobile stations and the second IP intcrfacc (IPIF_3) is couplcd to a tunncl (GIU? K1') providing bi_dircctional conncctivity to a corporate network; and wherein a third interface (IP IF_2) is provides bi_directional connectivity to mobile stations, and wherein the router routes the traffic via the second IP interface in the event that a mobile station on the first interface (IP I F 1 ) is communicating with a mobile station on the third interface (IPIF_2). 5. The network as claimed in claim 4, wherein the router is communicatively coupled to a remote router, said remote router being configured such that packets fiom one mobile station (MS_A) to another mobile station (MSB) is forwarded to said remote router (K), the remote router selectively taking a policy decision, such as to discard packets. 6. The network as claimed in claim 5, wherein the remote router comprising a firewall. 7. The network as claimed in claim 4, wherein the router (RT) comprises a GGSN node.

Documents:

2280-DELNP-2004-Abstract-(16-09-2011).pdf

2280-delnp-2004-abstract.pdf

2280-DELNP-2004-Claims-(16-09-2011).pdf

2280-delnp-2004-Claims-(21-01-2013).pdf

2280-delnp-2004-claims.pdf

2280-DELNP-2004-Correspondence Others-(09-05-2011).pdf

2280-DELNP-2004-Correspondence Others-(16-09-2011).pdf

2280-delnp-2004-Correspondence-Others-(21-01-2013).pdf

2280-delnp-2004-Correspondence-Others-(31-05-2013).pdf

2280-delnp-2004-correspondence-others.pdf

2280-delnp-2004-description (complete).pdf

2280-DELNP-2004-Drawings-(16-09-2011).pdf

2280-delnp-2004-drawings.pdf

2280-DELNP-2004-Form-1-(16-09-2011).pdf

2280-delnp-2004-form-1.pdf

2280-delnp-2004-form-13 (21-06-2005).pdf

2280-delnp-2004-form-13.pdf

2280-delnp-2004-form-18.pdf

2280-DELNP-2004-Form-2-(16-09-2011).pdf

2280-delnp-2004-form-2.pdf

2280-DELNP-2004-Form-3-(09-05-2011).pdf

2280-DELNP-2004-Form-3-(16-09-2011).pdf

2280-delnp-2004-Form-3-(31-05-2013).pdf

2280-delnp-2004-form-3.pdf

2280-delnp-2004-form-5.pdf

2280-delnp-2004-GPA-(21-01-2013).pdf

2280-delnp-2004-gpa.pdf

2280-delnp-2004-pct-210.pdf

2280-delnp-2004-pct-304.pdf

2280-delnp-2004-pct-409.pdf

2280-DELNP-2004-Petition-137-(16-09-2011).pdf

abstract.jpg