Abstract:
A method of allowing a nomadic terminal to access a home network on the Layer 2 level. The method comprises connecting said terminal to a remote access network via an access point, the remote access network being connected to an operator&#39;s backbone network via a remote access router. Signalling is exchanged between the access point and an authentication server within the backbone network in order to authenticate the terminal to the authentication server and, following successful authentication, a Layer 2 tunnel extending across the backbone network is established for the purpose of connecting said nomadic terminal to the home network.

Description:
TECHNICAL FIELD 
       [0001]    The present invention relates to a method and apparatus for facilitating network interconnectivity. In particular, though not necessarily, the invention relates to the interconnection of LANs. 
       BACKGROUND 
       [0002]    It is desirable to allow users of a “home” LAN to access that LAN even when they are away from the home LAN environment. In many cases, this means allowing the user to connect to a LAN in his current location, e.g. a WLAN hotspot or a public Ethernet access, and through that connection to the home LAN. 
         [0003]    The inter-connection of private, e.g. house and office, networks across intervening broadband networks is possible using already standardised solutions (or solutions under standardisation). For example, work carried out by the Internet Engineering Task Force (IETF) deals with providing so-called “pseudo wires” between access points to an IP or Multiprotocol Label Switching (MPLS) network and which emulate Ethernet services over the IP or MPLS network. Work carried out by the IEEE deals with LAN interconnection solutions, where the intermediate operator-provided network is also itself an Ethernet network. 
         [0004]    Ethernet is an example of a Layer 2 (L2) networking protocol. In order to enable the inter-connection of different Ethernet networks, L2 tunnels and L2VPN solutions are required. One such solution is that known as “EtherIP” [IETF RFC3378], which encapsulates Ethernet packet at a sending side LAN with an IP header, and sends the packets to an access router (AR) of the receiving side LAN which decapsulates the packets and bridges the Ethernet frame as if it was a L2 node (switch, bridge). Another currently standardised solution is to use L2TPv3 [RFC4719, “Transport of Ethernet Frames over Layer 2 Tunnelling Protocol Version 3 (L2TPv3)”] to transport Ethernet frames in an IP/UDP packet. An extension of L2TP for L2VPN usage also exists and which enables L2 tunnels to be connected to virtual bridges, so that standard Ethernet MAC forwarding can be used along with MAC learning to forward the Ethernet frames received by the virtual switch [RFC4667, “Layer 2 virtual private network (L2VPN) extensions for layer 2 tunnelling protocol (L2TP)”]. 
         [0005]    Different solutions exist for LAN inter-connect over MPLS provider networks. One solution is a pseudo-wire over MPLS as described in RFC4448, “Encapsulation Methods for Transport of Ethernet over MPLS Networks”. Also, The L2VPN working group of the IETF is standardising a Virtual Private LAN Service (VPLS) to transport L2 protocol data units over IP/MPLS networks [IETF WG Layer 2 Virtual Private Networks (l2vpn), http://ietforg/html.charters/l2vpn-charter.html]. VPLS is also referred to as Transparent LAN Service and Virtual Private Switched Network service. It incorporates MAC address learning, flooding, and forwarding functions in the context of pseudo-wires that connect individual LANs across a packet switched network. Implementations of VPLS in an IP/MPLS router often refer to the virtual bridge functionality as VSI (Virtual Switch Instance). 
         [0006]    There exist solutions to inter-connect two (or more) LANs using an intervening L2 operator (provider) networks. If the provider&#39;s network is Ethernet, then the 802.1ad Q-in-Q method or the 802.1ah Mac-in-Mac method could be used. In the case of 802.1ad, the original 802.1Q header has been extended with an additional virtual LAN (VLAN) tag called “S-VLAN” (Service VLAN), which makes it possible to build up a virtual network structure. Whilst the original VLAN tag defined in the 802.1Q standard is transmitted transparently by 802.1ad capable switches, a virtual topology can be defined between 802.1ad capable switches by configuring VLANs appropriately on the switch interfaces, and switching and forwarding based on the S-VLAN tag. The switches on the border of an 802.1ad and 802.1Q segment are responsible for generating and stripping the S-VLAN tag. 
         [0007]    One possible application of 802.1ad is to use the S-VLAN tag for identification of a service. It is important to note that, in the case of 802.1ad, the customer and provider network are not separate, so both networks appear as a large domain, causing for example an STP action in a customer network to impact on the provider network. 
         [0008]    802.1ah MAC-in-MAC provides for the encapsulation of an entire Ethernet frame and a new MAC header is generated by the edge switch on the border of an 802.1ah domain. Within the domain the original Ethernet frame is transmitted transparently, with all switching and forwarding decisions in the intermediate switches being based upon the destination MAC address and VLAN tag(s) in the outer MAC header. The main benefit of 802.1ah is its scalability to large Ethernet networks, and in addition the clear separation that it provides between the provider and customer Ethernet networks. 
         [0009]    Existing L2VPN solutions rely on static configuration and assume fixed locations for customer sites. Mobile users are therefore restricted to using only pre-configured customer sites. On the other hand, while L3 mobility solutions such as MobileIP (MIP) potentially offer unrestricted access, they do not offer L2 transparency. This means that if a terminal uses L2 specific protocols (e.g. protocols relying on broadcast L2 frames), the L3 solution will not work. Moreover, L3 mobility solutions do not allow overlapping addresses for mobile hosts. Although a terminal may reside in a remote subnet with its home IP address, this home IP address must be unique. Thus for example two mobile terminals cannot have the same home IP address in the same access network. Unfortunately, home users often use private address spaces which may very easily be overlapping. 
         [0010]    Some L3 mobility solutions require the implementation of dedicated protocols in terminals, and which are often not available (e.g., MIP is not available in Windows™). L3 solutions are to some extent dependent on the version of IP. However, if mobility is transparent at layer 2, then the terminal may use either IPv4 or IPv6 in its home LAN. 
       SUMMARY 
       [0011]    According to a first aspect of the present invention there is provided a method of allowing a nomadic terminal to access a home network on the Layer 2 level, the method comprising:
       connecting said terminal to a remote access network via an access point, the remote access network being connected to an operator&#39;s backbone network via a remote access router;   exchanging signalling between the access point and an authentication server within the backbone network in order to authenticate the terminal to the authentication server; and   following successful authentication, establishing a Layer 2 tunnel extending across the backbone network for the purpose of connecting said nomadic terminal to the home network.       
 
         [0015]    The invention thus provides for triggering of the Layer 2 tunnel establishment upon successful authentication of the nomadic terminal to the backbone network. As far as the terminal is concerned, the process of establishing the tunnel is transparent, and no modifications to the terminal are necessary. A key aspect to the implementation of the invention is the introduction of functionality into the backbone network which detects authentication and triggers tunnel establishment by configuring access routers and/or access points as appropriate. 
         [0016]    The invention is applicable in particular to networks which implement the Layer 2 using Ethernet, in which case said step of establishing an Ethernet Layer 2 tunnel may use one of: EtherIP, Ethernet over Point-to-Point Protocol (PPP), L2TPv3, and VPLS. 
         [0017]    The invention encompasses embodiments where the access router is an endpoint of the Layer 2 tunnel, as well as embodiments where the access point is the tunnel endpoint. 
         [0018]    The key functionality of the invention may be implemented as a new node within the backbone network referred to here as a Mobility Manager function. The method comprises informing the Mobility Manager function within the operator&#39;s backbone network of a successful authentication, the Mobility Manager function configuring one or both of said remote access router and said remote access point to establish said Layer 2 tunnel. The Mobility Manager function may further configure said home access router to establish said Layer 2 tunnel. In some cases, the Mobility Manager function may cooperate with a peer Mobility Manager function associated with the home network in order to establish said Layer 2 tunnel. This arrangement allows nomadic terminals to access their home networks even when their network operator has an agreement with an own backbone network operator which is different from the backbone network to which the remote access network is attached, providing that an agreement exists between the two backbone network operators. 
         [0019]    According to a second aspect of the present invention there is provided apparatus for providing mobility management within a communication system, the apparatus being arranged in use to:
       receive authentication related signalling in respect of a nomadic terminal connected to an access point of a remote access network and as a result to establish a Layer 2 tunnel extending across a backbone network for the purpose of connecting said nomadic terminal to the home network.       
 
         [0021]    In future networks this apparatus may be implemented as a Mobility Manager function. The apparatus may be standalone, or may be collocated with an authentication server. 
         [0022]    According to a third aspect of the present invention there is provided apparatus for providing an access point for a nomadic terminal to a remote access network, the apparatus having an interface for connection to a mobility manager within an operator&#39;s backbone network, the apparatus being configurable via said interface to establish a Layer 2 tunnel between itself and home network of the nomadic terminal. 
         [0023]    According to a fourth aspect of the present invention there is provided apparatus for providing an access router to interconnect an access network to an operator&#39;s backbone network, the apparatus being configured to provide Layer 2 switching and having an interface towards a mobility manager within the operator&#39;s backbone network, the apparatus being further configurable via said interface to establish a Layer 2 tunnel towards a nomadic terminal or towards a home network of a nomadic terminal. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0024]      FIG. 1  illustrates schematically two L2 access networks interconnected via a L3 operator network using a L2 tunnel extending from home access router to remote access point; 
           [0025]      FIG. 2  illustrates the creation of a virtual bridge within the access point of  FIG. 1 ; 
           [0026]      FIG. 3  illustrates the creation of a pseudo-wire within the access point of  FIG. 1 ; 
           [0027]      FIG. 4  illustrates schematically two L2 access networks interconnected via a L3 operator network using a L2 tunnel extending from home access router to remote access router; 
           [0028]      FIG. 5  illustrates the establishment of multiple bridged L2 tunnels extending from a remote access network to respective home networks; 
           [0029]      FIG. 6  illustrates the mapping of VLAN tags to home networks used by a remote access network; 
           [0030]      FIG. 7  illustrates the bridging of VLAN virtual interfaces with the corresponding L2 tunnels leading to the home networks associated with VLAN tags; 
           [0031]      FIG. 8  illustrates the connection of VLAN virtual interfaces with the corresponding L2 tunnels leading to the home networks associated with VLAN tags via pseudo-wires; 
           [0032]      FIG. 9  is a flow diagram illustrating a procedure for establishing a L2 tunnel between a remote access network and a home network; 
           [0033]      FIG. 10  is a flow diagram illustrating a procedure for tearing down a L2 tunnel established between a remote access network and a home network; 
           [0034]      FIG. 11  illustrates a bridging and Mac-in-Mac tunnelling structure; 
           [0035]      FIG. 12  illustrates schematically a system architecture which provides a pre-established L2 tunnel between PoIs in respective operator networks; 
           [0036]      FIG. 13  illustrates schematically a system architecture which provides for the establishment of a L2 tunnel between PoIs in respective operator networks, following a negotiation between the provider networks; 
           [0037]      FIG. 14  illustrates a system architecture adapted to the case where a home LAN accesses the operator network through a wholesale service; 
           [0038]      FIG. 15  illustrates a system architecture where a home LAN is behind an xDSL home router; 
           [0039]      FIG. 16  illustrates schematically the configuring of an xDSL router as a home access router to directly tunnel Ethernet frames to a remote access router; 
           [0040]      FIG. 17  illustrates schematically a system architecture in which a home DSL router has a statically configured L2 interface towards a BRAS; 
           [0041]      FIG. 18  illustrates schematically the binding of Mac-in-Mac or Q-in-Q capable interfaces along with the VPLS pseudo-wires to VPLS Virtual Switch Instances; and 
           [0042]      FIG. 19  illustrates a hub and spoke layout in which Ethernet services are provided though a central node. 
       
    
    
     DETAILED DESCRIPTION 
       [0043]      FIG. 1  illustrates schematically an operator network  1  comprising a Layer 3 (L3) backbone, e.g. IP or MPLS. A corporate LAN  2 , the “home” LAN, is connected to the operator network via an Access Router (AR)  3 . The home LAN is assumed to be an Ethernet network.  FIG. 1  illustrates further a remote access network  4 , which is an Ethernet network connecting WLAN hotspots or public Ethernet “jacks”. It is assumed here that the operator network and the remote access network are owned by the same operator, or at least have established a trust relationship. A user connects to the remote access network  4  via an access point  5 . The remote access network is connected to the operator network via an AR  6 . In order to allow the user to seamlessly attach to the home LAN via the remote access network, a Layer 2 (L2) tunnel  7  is established between the home AR  3  and the remote access point AP  5  as described below. 
         [0044]    When a mobile terminal or “host”  8  presents itself to the remote access point  5 , it must authenticate itself to obtain L2 access. This is usually done via the IEEE 802.1x procedure. The specific application of 802.1x for WLANs is described in the 802.1i standard. The access point  5  uses an authentication or AAA server  9  within the operator network  1  to authenticate the terminal  8 , using for example the RADIUS or DIAMETER protocol. The AAA server is standard functionality, and the address of the AAA server  9  is preconfigured in the remote access point. A new Mobility Manager (MM)  10  implements functions to use the AAA trigger for remote setup of connectivity to the home network. The MM may reside in the same physical node as the AAA server or at any other location suitable for receiving authentication messages sent to the AAA server. One possible implementation of the MM is as a proxy to the AAA server. In this case, AAA messages are forwarded from the access point  5  to the MM  10 , which forwards them to the real AAA server  9 . 
         [0045]    If the MM  10  determines that the terminal  8  is allowed to access the remote access network  4 , it will determine the home network and the corresponding access router, for example by mapping a MAC address of the terminal or a username/password combination to a home network address. It must also identify the serving access point, for example by examining the source address of the authentication message (e.g. from the header&#39;s source field). The MM will then remotely configure the home network AR  3  and the remote access point  5  to establish a L2 tunnel between them. L2 tunnels may be built using, for example, EtherIP, Ethernet over Point-to-Point Protocol (PPP), L2TPv3 or any similar present or future protocol supporting L2 tunnelling. The remote AR  6  in this case functions in a standard manner, forwarding packets based upon L3, i.e. IP addresses. In this way, frames from the terminal are transported undisturbed to the home access router, which in turn will forward (bridge) the frame into the home network. 
         [0046]    The next task is to configure the home AR  3  to bridge the interface leading to the home network with the newly established virtual interface, so that Ethernet frames are bridged between the two interfaces. This way, the home AR  3  is able to bridge between multiple remote hosts. The MM  10  then sets up the remote serving access point  5  to create a similar virtual bridge as illustrated in  FIG. 2 . Alternatively, it may directly bind the L2 tunnel as a pseudo-wire to the interface leading to the terminal as illustrated in  FIG. 3 . If the remote access point is a wired Ethernet switch, the terminal&#39;s interface can be learnt from, for example, the CallingStationID in the AAA request. On the other hand, the wireless interface of a WiFi access point is a medium shared among multiple terminals. Nonetheless, by applying 802.1i, the access point is capable of differentiating hosts (allow, not allow), and may even setup an encrypted connection to the host, so it would be relatively straightforward to achieve a logical interface for a specific terminal. Specifically, this could be implemented via firmware or a software update in the wireless access points. 
         [0047]    The embodiment illustrated in  FIG. 1  assumes that the remote access point  5  contains the required L2 tunnelling functionality, e.g. EtherIP or a suitable alternative. If this is not the case, according to an alternative embodiment, the remote AR  6  may terminate the L2 tunnel. This is illustrated in  FIG. 4 . In this case, the MM  10  must remotely configure the home and the remote ARs  3 , 6  to establish the L2 tunnel, and the MM will assign a specific VLAN tag to the terminal  8  in the access point  5 . This way, frames from the terminal  8  are transported undisturbed to the remote network AR  6 , which will in turn forward (bridge) the frames through the L2 tunnel. 
         [0048]    Regardless of whether the approach of  FIG. 1  or of  FIG. 4  is employed, it is the authentication procedure which is used to trigger the remote configuration which in turn establishes the transparent access to the home LAN. If this triggering and the remote configuration are reasonably fast, then session continuity can be provided when changing the access (e.g. during handovers). 
         [0049]    Considering now an alternative lightweight but possibly less secure mechanism, after processing the authentication, the MM could configure the remote access network access router and the home access router to establish a L2 tunnel between each other, without tunnelling below the routers. The L2 tunnel may again be built using EtherIP, L2TPv3, VPLS etc. The next task would be to configure the access router to bridge the interface leading to the access network with the newly established virtual interface, so that Ethernet frames are bridged between the two interfaces. This is illustrated in  FIG. 5 . 
         [0050]    This solution establishes connectivity to the home network, although it has an unfortunate side-effect. If the remote access network handles multiple terminals from multiple home networks (A and B), then these different home networks will be connected on L2 due to multiple bridged L2 tunnels, as shown in  FIG. 5 . Therefore, broadcast messages will be received by different home networks raising scalability and privacy issues. 
         [0051]    To ensure the separation of traffic belonging to different home networks, an advantageous embodiment should map terminals in the remote network to home network VLAN tags as illustrated in  FIG. 6 . This should be done in such a way that terminals from the same home network are mapped to the same VLAN tag to enable local communication and to decrease the number of required VLAN identifiers. To do this, the MM should configure the access point of the terminal to assign the selected VLAN tag to every frame it receives from the terminal. If the access point is an Ethernet switch, this can be done on a per-interface basis as described in the proposed 802.1ad standard—the so called Q-in-Q encapsulation method. Proper VLAN tagging in the access point requires the assignment of the appropriate VLAN tag to that port where the terminal is connected. The port can be identified on the basis of the terminal MAC address, which can be obtained from the frame sent to the AAA server (e.g., CallingStationID in the AAA request). In the case of a wireless interface however, application of 802.1i allows the access point to differentiate hosts as already described. 
         [0052]    The MM should also configure VLAN encapsulation/decapsulation in the access router. VLANs appear in the access router as virtual interfaces, which should be connected to the home access router&#39;s virtual bridge. Depending on the L2 tunnel type, it may be possible to implement this in two ways. Firstly, the VLAN virtual interfaces can be bridged with the corresponding L2 tunnels leading to the home network which the VLAN tag (or VLAN virtual interface) is assigned to. This is illustrated in  FIG. 7 . Secondly, the virtual interface may be connected via a pseudo-wire directly with the home network&#39;s virtual bridge. This is illustrated in  FIG. 8 . 
         [0053]    The interior switches of the remote access network can be configured in such a way that they can transport the frames of different VLANs, so these interior switches need not be configured each time a new VLAN is assigned to a newly arriving terminal. Only the edges, i.e. the access nodes and the access router, need on-the-fly configuration to bind them to VLAN tags. 
         [0054]      FIG. 9  is a flow diagram illustrating the process carried out by the MM, i.e. on-the-fly connection of a nomadic or mobile terminal to its home network. In order to reduce complexity and reduce scalability issues, the reverse process of tearing down connectivity for superfluous remote networks (i.e., remote accesses where there are no longer terminals belonging to a certain home network) is also required. This is illustrated in the flow diagram of  FIG. 10 . 
         [0055]    The solutions presented above may result in scalability issues, as broadcast frames, or frames for which the direction of the destination is not yet learnt via MAC learning, are broadcast in the remote L2 network. Although the edge access nodes will filter packets based on VLAN tags, the MAC forwarding tables of the interior switches may become overloaded. To address this issue, the currently standardized 802.1ah Mac-in-Mac Encapsulation can be used. Instead of configuring Q-in-Q encapsulation in the access node, the MM should configure Mac-in-Mac encapsulation from the access node up to the access router. 
         [0056]    The bridging and Mac-in-Mac tunnelling structure is depicted in  FIG. 11 . This structure allows the encapsulated frames to be transported by Provider Backbone Bridges (PBBs) without their having to know the addresses of other access networks. The access node (AN 1  or AN 2  in  FIG. 11 ) has to encapsulate the L2 frame coming from a host within an external L2 MAC header. This external header contains the access router&#39;s local MAC address as the destination. As a result, the provider&#39;s Ethernet switches inside the access network need to know the Ethernet routes only for themselves, the access nodes and the access router, and they do not need to maintain forwarding information for each possible home network. Before the virtual bridge in the access router bridges the received frames, it must strip the outer MAC header from the frame. 
         [0057]    According to this structure, it is also possible to avoid virtual bridging in the remote access router. In this case, the Mac-in-Mac tunnels should be connected via a pseudo-wire to the home network. Note, however, that if there are multiple hosts in the remote access network at different access nodes, then each Mac-in-Mac tunnel will be connected to the home access router&#39;s bridge, leading to suboptimal network usage if the remote terminals communicate with each other. 
         [0058]    It is possible or even likely that the home network will be administered by an operator other than the operator of the remote access network (and the provider network). In this case, the MM located within the provider network may not be able to reconfigure the access router of the home network, and in some cases it may not even be able to authenticate the newly appeared terminal. Of course, any MM associated with the home network has no right to reconfigure the remote access router. 
         [0059]    To address this issue, a fixed access operator may pre-establish L2 tunnels with partner operator networks (based on appropriate contracts) in order to provide a connectivity service even from these other operator access networks. In this case, the two (home and serving) operators have pre-established points of interconnect (PoI) between which the L2 tunnels are established. IPSec may be used for security reasons. 
         [0060]    The task of the serving MM associated with the remote access network is to obtain the authentication messages from the terminal, to identify its home network, and to relay the authentication messages through the appropriate L2 tunnel to the home MM. To this end, the “serving” MM is provided with a database that maps the authentication data to the PoI address and home MM address. The MM in the home network reacts to receipt of a tunnelled authentication request by configuring the L2 tunnelling between the home AR and the PoI within the home operator network. The authentication reply messages from the home MM are sent through (or caught by) the serving MM. When the serving MM infers from the authentication messages that authentication is successful, it configures the L2 tunnel between the PoI and the serving AR in its network or between the PoI and the serving access point. The former configuration is illustrated in  FIG. 12 , where the home MM is identified by reference numeral  11 , the serving MM by reference numeral  12 , the respecting PoIs by  13  and  14 , and the respecting ARs by  15  and  16 . The home network is indicated by reference numeral  17 , the remote access network by  18 , the remote access network access point by  19 , and the nomadic terminal by  20 . 
         [0061]    If there is no pre-established tunnel between operators, the two MMs must inter-work. The MM of the new network may communicate and authenticate the terminal with its home MM, and each MM can configure the access router (or access point) in its own administrative area. This is illustrated in  FIG. 13 , where the tunnel is deployed between the access routers. [In an alternative approach, the tunnel is established between the home AR and the serving AP.] Such inter-working requires the use of a standardized and secure protocol between the two MMs. The MM of the new network must provide the authentication data of the terminal and the new access router&#39;s IP address. If the home MM properly authenticates the terminal, it has to acknowledge authentication and must provide the IP address of the corresponding home access router. 
         [0062]    The mechanisms described here are applicable to the case where the home LAN accesses the operator network through a wholesale service. The home LAN connects to the service through an infrastructure provider. The infrastructure provider sets up a L2 tunnel to the operator network. This is shown in  FIG. 14 . In this case, the AR sees a virtual interface connecting it to the home LAN. However, the procedures performed in the MM are unchanged: it must setup a bridging between this (virtual) interface and the newly established L2 tunnel interface (also virtual) between the two ARs. 
         [0063]    In the traditional xDSL service, the home LAN is behind an xDSL home router, which has a single IP address from the operator but which provides internal addressing via DHCP, firewall and NAT to the internal LAN. In this case, being the first IP hop, the xDSL router must be modified with the L2 tunnelling capabilities to support transparent access of the home LAN from remote locations. Enhanced xDSL routers may be provided for this purpose. In the case of traditional xDSL with PPP, the xDSL router sends the “de-NATted” IP packets over PPP to the Broadband Remote Access Server (BRAS), which removes the PPP header and forwards the IP packet. [PPP itself may be transport over a combination of PPPoE or L2TP protocols.] This is illustrated in  FIG. 15 , where LAC indicates a L2TP Access Concentrator. 
         [0064]    Considering further xDSL with PPP, one implementation involves configuring the xDSL router as a home AR to directly tunnel Ethernet frames to the remote location&#39;s access router. This is illustrated in  FIG. 16  (assuming implementation of xDSL as ADSL). In this case, the xDSL home router must also implement the virtual bridge functions so that it is capable of bridging Ethernet frames into the L2 tunnel. The MM in this case has to configure the home ADSL router (as a home access router) and the remote AR/AP remotely. 
         [0065]    An alternative implementation, illustrated in  FIG. 17 , involves statically configuring the home xDSL router to provide a virtual L2 interface towards the BRAS, where it can tunnel L2 frames. At each mobility event or whenever a local device shows up at a remote access, the MM has to configure the BRAS, not the home xDSL router. As such, the BRAS takes the role of the AR having virtual bridges (or VSIs if it supports VPLS). 
         [0066]    The home xDSL router may have direct Ethernet connectivity over PPP to the BRAS. In contrast to traditional DSL solutions (where the PPP session from the customer equipment to the BRAS delivers IP packets), the PPP would have to transmit Ethernet frames. This makes use of the teachings in RFC3518, “Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)”. 
         [0067]    The MM in this case has to remotely configure the BRAS (as a home access router) and the remote access router to dynamically establish a L2 tunnel using any L2 tunnelling technique that supports the binding of the virtual interface into virtual bridges. This virtual bridge has to switch Ethernet frames decapsulated from the tunnel from the xDSL router (e.g. from the PPP session) and switch the frames to another L2 tunnel leading to the remote location. 
         [0068]    Remotely configuring the above described mechanisms in the access routers and access points is possible by remotely accessing the command line interface via, for example, Telnet. Alternatively, for improved performance, a proprietary interface may be used. 
         [0069]    If the backbone provides Virtual Private LAN Service (VPLS) service, the MM has to configure VPLS pseudo-wires between the edge routers. Instead of binding to generic virtual bridges, the MM has to bind Mac-in-Mac or Q-in-Q capable interfaces along with the VPLS pseudo-wires to VPLS Virtual Switch Instances. This is illustrated in  FIG. 18 . 
         [0070]    In some cases, the transparent Ethernet service may be provided through a central node working as the AR of multiple home networks, i.e. a hub and spoke layout. This central node is denoted here as the Connectivity Services Node (CSN). An intervening network may be present between the CSN and the home LAN, in which case it must be ensured that the CSN is connected via a L2 tunnel to the home network. This tunnel can be setup on demand by the MM when a terminal appears at a remote location, or may be pre-configured to speed up the process. Furthermore, the CSN must implement a virtual bridge per home network. 
         [0071]    The MM should configure this CSN and connect it via another L2 tunnel when a home terminal shows up at a remote location. If the CSN has no pre-configured tunnel to the home network, the MM has to setup this tunnel. 
         [0072]    The hub and spoke layout is illustrated in  FIG. 19 . Note that logically this scenario is not different from the previously described context if we substitute the home AR with the CSN. 
         [0073]    The embodiments presented above allow a network operator to provide a value added connectivity service to its customers, i.e. a nomadic terminal can be transparently connected to its home LAN from any access (e.g. any hot spot) of a fixed network operator. Moreover, if proper contracts are established with partner networks, the connectivity service can be used even from these partners&#39; access networks. 
         [0074]    As connectivity to the home network is established on layer 2, the internal IP addressing structure or the IP version used in the home network is not relevant: any combination will work. Furthermore, the moving terminal in the visited network is connected transparently to the home network (here transparency means that the terminal does not recognize that it is not in the home network). This transparent layer 2 connection makes it possible to reach the home network without any dedicated client software in the terminal, as well as supporting those future applications which require Ethernet level connection. 
         [0075]    It will be appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the present invention.