WO2015027405A1 - A residential gateway device and a network-side control device - Google Patents

A residential gateway device and a network-side control device Download PDF

Info

Publication number
WO2015027405A1
WO2015027405A1 PCT/CN2013/082441 CN2013082441W WO2015027405A1 WO 2015027405 A1 WO2015027405 A1 WO 2015027405A1 CN 2013082441 W CN2013082441 W CN 2013082441W WO 2015027405 A1 WO2015027405 A1 WO 2015027405A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
openflow
control device
side control
residential
Prior art date
Application number
PCT/CN2013/082441
Other languages
French (fr)
Inventor
Sven Ooghe
Riza Cetin
Qin Yin
Original Assignee
Alcatel Lucent
Alcatel-Lucent Shanghai Bell Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alcatel Lucent, Alcatel-Lucent Shanghai Bell Co., Ltd. filed Critical Alcatel Lucent
Priority to CN201380078483.0A priority Critical patent/CN105409184B/en
Priority to PCT/CN2013/082441 priority patent/WO2015027405A1/en
Publication of WO2015027405A1 publication Critical patent/WO2015027405A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803Home automation networks
    • H04L12/283Processing of data at an internetworking point of a home automation network
    • H04L12/2836Protocol conversion between an external network and a home network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0895Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses
    • H04L61/5014Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1301Optical transmission, optical switches
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13196Connection circuit/link/trunk/junction, bridge, router, gateway

Definitions

  • the invention relates to access networks.
  • virtualized residential gateway vRG is designed to handle both user control plane and user data plane in a virtualized way:
  • vRG both LAN side and WAN side control plane protocols need to be handled by vRG, protocols being e.g. IP Forwarding (DHCP server, DHCP client, ARP, ICMP, PPPoE Client, ...), NAPT (PCP, IGD, DMZ, UPnP, ...), TR-69, VoIP, .... NAPT is mainly required for IPv4, and may be required for IPv6 to provide means for simple-security.
  • IP Forwarding DHCP server, DHCP client, ARP, ICMP, PPPoE Client, ...), NAPT (PCP, IGD, DMZ, UPnP, ...), TR-69, VoIP, .... NAPT is mainly required for IPv4, and may be required for IPv6 to provide means for simple-security.
  • IPv4/v6 forwarding of user data packets, NAPT forIPv4, QoS, VoIP, etc..
  • vRG requires moving all the intelligence present in the home network gateway outside of the home network and virtualizing these intelligence in the network side. This kind of virtualization is mainly driven by:
  • this service/policy can be embodied in the vRG instead of in the residential home gateway device. Deploying this service/policy in the vRG is relatively quicker and has lower cost than updating all of the residential home gateways, therefore the service/policy can hit the market within a shortest deployment time.
  • vRG is implemented as a centralized server functionality (outside of the home gateway device) which handles both user control and user data packet processing.
  • the data plane functionalities consume a lot of processing capability. Since it is centralized, it may become a bottle-neck mainly for user data traffic handling.
  • Layer 3/4 packet processing functionalities such as network address translation, packet inspection, firewalling and etc. are implemented in the vRG. Therefore, the vRG must have very powerful processing capability to support these functions. In case that the size of the access network increases, the processing capability needs also be increased.
  • vRG control protocol handling is centralized in network-side control device, and the user data plane handling is distributed over user home gateway devices. Since the data plane handling is distributed, it provides much better scalable solution.
  • a first aspect of the invention proposes a residential gateway device with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises: - Layer 3/4 packet processing functionalities of residential gateways;
  • the residential gateway device further comprises:
  • a controller for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device.
  • Layer 3/4 packet processing functionalities are provided in the residential gateway device.
  • Layer 3/4 packet processing in the data plane are implemented in residential gateway devices instead of in the vRG, thus the vRG would not become a bottleneck for data plane functionalities, and therefore the whole access network is more scalable.
  • the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities: IP routing based on IP address lookup; Network Address Translation; Packet inspection; and Fire walling.
  • This embodiment proposes several specific Layer 3/4 packet processing functionalities that can be distributed in the residential gateway devices to alleviate the processing burden of vRG and increases the scalability.
  • the residential gateway device is taken as an OpenFlow switch defined in Software Defined Networking architecture, and the first interface is for exchanging the control information in the form of OpenFlow/Config protocol with the network-side control device.
  • SDN Software Defined Networks
  • the home residential gateway acts as OpenFlow switch and the network-side control device as the vRG acts as OpenFlow/Config control point, and uses OpenFlow/Config to configure the data plane at home devices.
  • the residential gateway device is for an access network of any one of the following types: EPON; GPON; XGPON; 10GEPON; and DSL.
  • the residential gateway device comprises an optical network unit of GPON
  • the optical network unit as the residential gateway device comprises:
  • GPON domain for establishing and maintaining GPON transmission tunnels with the network-side control device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
  • This embodiment proposes a specific architecture for implementing the layer 3/4 processing in optical network units (ONU) of GPON.
  • One GPON domain is provided in the ONU to establish and maintain a necessary GPON communication path to carry the control information of layer 3/4 processing, and one OpenFlow domain is provided to implement the layer 3/4 processing according to the control information.
  • This embodiment provides a hierarchy architecture for the ONU.
  • the GPON domain uses an ONT management and control interface (OMCI) to establish and maintain the GPON transmission tunnels with the network-side control device, and the GPON domain has a virtual Ethernet interface point (VEIP), for interfacing with the OpenFlow domain and exchanging the OpenFlow/Config data between the transmission tunnels and the OpenFlow domain.
  • ONT management and control interface ONT management and control interface
  • VEIP virtual Ethernet interface point
  • This embodiment adapts the OMCI interface to maintain the GPON transmission tunnels and adapts the VEIP interface to exchange the control information for the layer 3/4 processing functionalities.
  • the OMCI and VEIP interfaces themselves are current interfaces, however the embodiment adapts these interfaces to support the exchange of control information for the layer 3/4 processing functionalities. Therefore this embodiment can be incorporated into the ONU very conveniently.
  • the optical network unit receives OpenFlow/Config control information using an ONT Management and Control Interface (OMCI) Managed Entity, and the Managed Entity comprises any one of the following:
  • OMCI ONT Management and Control Interface
  • This embodiment proposes a new OMCI Managed Entity for carrying the OpenFlow/Config data.
  • a network-side control device said network-side control device being provided with control plane functionalities of residential gateways, wherein, the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising Layer 3/4 packet processing functionalities of residential gateways.
  • the network-side control device is considered as the vRG and is provided with control plane functionalities but without Layer 3/4 packet processing functionalities of residential gateways.
  • the vRG is no longer a bottle neck for user data handling and the access network is more scalable.
  • the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities: IP routing based on IP address lookup; Network Address Translation; Packet inspection; and Firewalling.
  • control plane functionalities of residential gateways comprises at least any one of the following: NAT binding control; Firewall Access Control List management; PPPoE control signaling; DHCP client; DHCP server; Universal Plug and Play server or Digital Living Network Alliance server; and Configuration management.
  • This embodiment proposes some specific control plane functionalities to control the residential gateway to process the Layer 3/4 packet.
  • the network-side control device comprises: a second interface, for exchanging control information about the data plane functionalities of residential gateways, with a residential gateway device provided with the data plane functionalities of residential gateways.
  • the network-side control device has an interface to send the control information to the residential gateway for processing the Layer 3/4 packet.
  • the network-side control device is taken as an OpenFlow/Config control point defined in software defined network architecture, and the second interface is for exchanging the control information in the form of OpenFlow/Config protocol with the residential gateway device.
  • SDN Software Defined Networks
  • the network-side control device is implemented in any one of: a digital subscriber line access multiplexer; an optical line terminal; a broadband network gateway; and an equipment in a cloud.
  • the network-side control device as the vRG can locate in various network elements in different kind of access network such as DSL or PON.
  • the concept of the invention is to centralize the control plane of the RG in a vRG located in the operator network, and the vRG can be embodied in various network element and is not limited.
  • the network-side control device is implemented in the optical line terminal, and the network-side control device uses ONT management and control interface (OMCI) to establish and maintain GPON transmission tunnels with the residential gateway device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
  • OMCI ONT management and control interface
  • This embodiment adapts the OMCI interface to maintain the GPON transmission tunnels.
  • the OMCI interfaces itself is a current interface, and the embodiment adapts this interface to support the exchange of control information. Therefore this embodiment can be incorporated into the GPON very conveniently.
  • the network-side control device is for transmitting the OpenFlow/Config control information in a Managed Entity
  • the Managed Entity comprises any one of the following:
  • This embodiment proposes a new managed entity for carrying the OpenFlow/Config data.
  • Fig. 1 schematically shows the transition from traditional residential gateway device in the home network to virtualized residential gateway in the network side;
  • Fig. 2 schematically shows the function separation of data plane and control plane between the residential gateway and the virtualized residential gateway, according to embodiments of the invention
  • Fig. 3 schematically shows the implementation of embodiments of fig. 2 based on software defined network
  • Fig. 4 schematically shows the implementation of embodiments of fig. 3 in the GPON access network according to one embodiment of the invention
  • Fig. 5 schematically shows the implementation of the ONU in fig. 4 according to one embodiment of the invention
  • Fig. 6 schematically shows the OMCI model to transmit OpenFlow/Config data according to one embodiment of the invention.
  • the present application proposes a residential gateway device with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises:
  • the residential gateway device further comprises:
  • a controller for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device.
  • the present application proposes a network-side control device, said network-side control device being provided with control plane functionalities of residential gateways.
  • the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising: Layer 3/4 packet processing functionalities of residential gateways.
  • the network-side control device is also referred as vRG (virtualized residential gateway).
  • the network-side control device vRG further comprises: a second interface, for exchanging control information about the data plane functionalities of residential gateways, with the residential gateway device provided with the data plane functionalities of residential gateways.
  • the vRG and the residential gateway RG communicate with each other via a dedicated control path between the second interface of the vRG and the first interface of the RG.
  • the control path is denoted by the dash line in fig. 2. What is to be noted is that this control path is a logic communication tunnel. And there is a physical communication path that carries the control path between the operator network and the residential gateway RG: the access device in the operator network establishes a communication path with the residential gateway RG. This communication path is denoted by the solid line in fig. 2. More detailed implementations of the communication path will be elucidated in the following description.
  • the network side control device vRG is shown as a block separate from the access device, however, this is just for showing the functional separation between the access function in the operator network and the control plane function for the residential gateway RG.
  • the network side control device vRG can be embodied within the access device, such as an OLT as described below, or in a digital subscriber line access multiplexer (DSLAM) or in a broadband network gateway (BNG); alternatively, the network side control device vRG can also be a standalone network element that is connected to the residential gateway RG via the access device, such as an equipment in a cloud.
  • DSLAM digital subscriber line access multiplexer
  • BNG broadband network gateway
  • the network side control device vRG can also be a standalone network element that is connected to the residential gateway RG via the access device, such as an equipment in a cloud.
  • the network side control device vRG can be embodied in any network element in the operator network so as to centralize the control plane functionalities for the Layer 3/4 packet processing of the residential gateways
  • the Layer 3/4 packet processing functionalities of residential gateways implemented by the residential gateway device comprises at least any one of the following functionalities:
  • control plane functionalities of residential gateways implemented by network-side control device vRG comprise at least any one of the following:
  • - DHCP server for to allocating IP addresses to the IP hosts that are connected to the residential gateway; - Universal Plug and Play (UPnP) server or Digital Living Network Alliance (DLNA) server; and
  • UPF Universal Plug and Play
  • DLNA Digital Living Network Alliance
  • SDN Software Defined Networks
  • the residential gateway device RG is taken as an OpenFlow switch defined in software defined network architecture
  • the network-side control device vRG is taken as an OpenFlow/Config control point defined in software defined network architecture.
  • the second interface of the network-side control device vRG and the first interface of the residential gateway device RG use OpenFlow/Config protocol to exchange the control information of the data plane.
  • OpenFlow/Config protocol to exchange the control information of the data plane.
  • SDN is a widely discussed technology, and those skilled in the art understand how to adapt or extend the OpenFlow switch, OpenFlow/Config control point and OpenFlow protocol as generally defined in the SDN, to realize the functions of the residential gateway device and the network-side control device, and the present specification will not give further unnecessary details.
  • Fig. 3 gives a schematic illustration of the above implementation based on SDN, as described above, wherein, the access device is embodied as a DSLAM.
  • the access network is a DSL network.
  • the concept of embodiments of the invention namely the separation of data plane and control plane between the RG and the operator network, is independent from the access technology.
  • the residential gateway device and the corresponding access device are for EPON, GPON, XGPON, or 10GEPON.
  • I I Fig. 4 gives a schematic illustration of one implementation based on GPON.
  • the residential gateway device RG is embodied as an optical network unit (ONU)
  • the access device is embodied as an optical line terminal (OLT).
  • the communication path for carrying the OpenFlow/Config protocol needs to be pre-provisioned between the residential gateway device RG as the OpenFlow Switch and the network-side control device as the OpenFlow controller.
  • the communication path comprises GPON physical layer and L2 (including OF-VLAN, QoS, ...) which be provisioned from OLT through ONT Management and Control Interface (OMCI).
  • OMCI is a general interface defined in GPON standard. However, the embodiment of the invention adapts OMCI to exchange the OpenFlow Config data.
  • embodiments of the invention also create a new management domain in the ONU, i.e. openFlow domain, in G.988 and suggests to reuse the dual management ONU model defined in II.2 of G.988 in order to provision OpenFlow communication path L3 and application layer parameters (including OF-IP addresses, TCP, UDP, ...) from OLT through OMCI.
  • the OMCI architecture model sets up the open flow communication path and GPON data path.
  • the whole OMCI model would use the standard VEIP concept to have two separate management domains: open flow domain and OMCI domain.
  • the optical network unit ONU as the residential gateway device comprises:
  • GPON domain for establishing and maintaining GPON transmission tunnels with the network-side control device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
  • the GPON domain uses the ONT management and control interface (OMCI) to establish and maintain the GPON transmission tunnels with the network-side control device.
  • OMCI ONT management and control interface
  • GEM GPON Encapsulation Method
  • VEIP Virtual Ethernet interface point
  • Fig. 6 schematically shows the OMCI model to transmit OpenFlow/Config data according to one embodiment of the invention.
  • One improvement proposed by the embodiment of the invention is that the OpenFlow Config data is inserted into the VEIP.
  • the rest of the OMCI model is similar as the present standard.
  • the model for VEIP would keep same as specified in II.2 of G.988.
  • the network-side control device in the OLT is for transmitting the OpenFlow/Config control information in a Managed Entity, and the optical network unit as the residential gateway device receives OpenFlow/Config control information using the ONT Management and Control Interface (OMCI) Managed Entity.
  • OMCI ONT Management and Control Interface
  • the Managed Entity comprises any one of the following:
  • processors may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software.
  • the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared.
  • explicit use of the term "processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • ROM read only memory
  • RAM random access memory
  • any switches shown in the FIGS are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.

Abstract

The invention makes a clean separation between data plane and control plane for residential gateway, and proposes a residential gateway device and a network-side control device. The residential gateway device is provided with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises: Layer 3/4 packet processing functionalities of residential gateways; and the residential gateway device further comprises: a first interface, for exchanging control information about data plane functionalities of residential gateways, with a network-side control device provided with the control plane functionalities of residential gateways; and a controller, for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device. And the network-side control device is provided with control plane functionalities of residential gateways, wherein, the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising: Layer 3/4 packet processing functionalities of residential gateways.

Description

A RESIDENTIAL GATEWAY DEVICE
AND A NETWORK-SIDE CONTROL DEVICE
TECHNICAL FIELD
The invention relates to access networks.
BACKGROUND OF THE ART
Access network operators are more and more going into the direction of virtualizing residential home network gateway functionality. As shown in fig. 1, virtualized residential gateway vRG is designed to handle both user control plane and user data plane in a virtualized way:
- Control plane: both LAN side and WAN side control plane protocols need to be handled by vRG, protocols being e.g. IP Forwarding (DHCP server, DHCP client, ARP, ICMP, PPPoE Client, ...), NAPT (PCP, IGD, DMZ, UPnP, ...), TR-69, VoIP, .... NAPT is mainly required for IPv4, and may be required for IPv6 to provide means for simple-security.
- Data plane: IPv4/v6 forwarding of user data packets, NAPT forIPv4, QoS, VoIP, etc..
vRG requires moving all the intelligence present in the home network gateway outside of the home network and virtualizing these intelligence in the network side. This kind of virtualization is mainly driven by:
- OPEX (Operational Expenditure) savings. Because each residential home gateway is provided with only simple functionalities such as Ethernet switching, the cost of the gateway device is quite cheap, thereby decreasing the total cost of the access network which includes hundreds of the gateway devices.
- Agility on deploying new services - Time to Market advantages. If a new service/ policy needs to be deployed, this service/policy can be embodied in the vRG instead of in the residential home gateway device. Deploying this service/policy in the vRG is relatively quicker and has lower cost than updating all of the residential home gateways, therefore the service/policy can hit the market within a shortest deployment time.
- Less constraints on technology evolutions (e.g. protocols, ...) - Time to Efficiency. Usually the vRG has powerful computing/processing capability therefore it can be easily upgraded to support new protocols. The traditional residential home gateway device does not have such expandability thus is hard to be upgraded to support new protocols.
SUMMARY OF THE INVENTION
In the existing solutions of virtualizing residential gateway, vRG is implemented as a centralized server functionality (outside of the home gateway device) which handles both user control and user data packet processing. However, the data plane functionalities consume a lot of processing capability. Since it is centralized, it may become a bottle-neck mainly for user data traffic handling. For example, Layer 3/4 packet processing functionalities, such as network address translation, packet inspection, firewalling and etc. are implemented in the vRG. Therefore, the vRG must have very powerful processing capability to support these functions. In case that the size of the access network increases, the processing capability needs also be increased. This can be done by distributing the date plane handling over a multiple server cards in the vRG and adding more server cards, but in essence these functions still locate in the vRG and the complexity and cost of vRG is still increasing. Therefore, the centralized vRG is not scalable.
The basic idea of embodiment of the present invention is to make a clean separation between data plane and control plane: vRG control protocol handling is centralized in network-side control device, and the user data plane handling is distributed over user home gateway devices. Since the data plane handling is distributed, it provides much better scalable solution.
Based on this basic idea, a first aspect of the invention proposes a residential gateway device with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises: - Layer 3/4 packet processing functionalities of residential gateways;
and the residential gateway device further comprises:
- a first interface, for exchanging control information about the data plane functionalities of residential gateways, with a network-side control device provided with control plane functionalities of residential gateways;
- a controller, for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device.
In this aspect, Layer 3/4 packet processing functionalities are provided in the residential gateway device. As the size of the network increases, Layer 3/4 packet processing in the data plane are implemented in residential gateway devices instead of in the vRG, thus the vRG would not become a bottleneck for data plane functionalities, and therefore the whole access network is more scalable.
In a preferred embodiment, the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities: IP routing based on IP address lookup; Network Address Translation; Packet inspection; and Fire walling.
This embodiment proposes several specific Layer 3/4 packet processing functionalities that can be distributed in the residential gateway devices to alleviate the processing burden of vRG and increases the scalability.
In a preferred embodiment, the residential gateway device is taken as an OpenFlow switch defined in Software Defined Networking architecture, and the first interface is for exchanging the control information in the form of OpenFlow/Config protocol with the network-side control device.
In this embodiment, SDN (Software Defined Networks) architecture is one of the examples which can be used for data and control plane separation, wherein: the home residential gateway acts as OpenFlow switch and the network-side control device as the vRG acts as OpenFlow/Config control point, and uses OpenFlow/Config to configure the data plane at home devices.
In a preferred embodiment, the residential gateway device is for an access network of any one of the following types: EPON; GPON; XGPON; 10GEPON; and DSL.
In this preferred embodiment, various access technologies can be supported. It should be noted that, the concept of embodiments of invention is to place the layer 3/4 packet processing into any kind of residential gateway device and the control plane into a network element in the operator network, and therefore the invention is independent from the specific access technology, and any access technology can be used.
In a preferred embodiment, wherein the residential gateway device comprises an optical network unit of GPON,
the optical network unit as the residential gateway device comprises:
- an OpenFlow domain including the OpenFlow switch together with an OpenFlow protocol stack; and
- a GPON domain, for establishing and maintaining GPON transmission tunnels with the network-side control device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
This embodiment proposes a specific architecture for implementing the layer 3/4 processing in optical network units (ONU) of GPON. One GPON domain is provided in the ONU to establish and maintain a necessary GPON communication path to carry the control information of layer 3/4 processing, and one OpenFlow domain is provided to implement the layer 3/4 processing according to the control information. This embodiment provides a hierarchy architecture for the ONU.
In a preferred embodiment, the GPON domain uses an ONT management and control interface (OMCI) to establish and maintain the GPON transmission tunnels with the network-side control device, and the GPON domain has a virtual Ethernet interface point (VEIP), for interfacing with the OpenFlow domain and exchanging the OpenFlow/Config data between the transmission tunnels and the OpenFlow domain.
This embodiment adapts the OMCI interface to maintain the GPON transmission tunnels and adapts the VEIP interface to exchange the control information for the layer 3/4 processing functionalities. The OMCI and VEIP interfaces themselves are current interfaces, however the embodiment adapts these interfaces to support the exchange of control information for the layer 3/4 processing functionalities. Therefore this embodiment can be incorporated into the ONU very conveniently.
In a preferred embodiment, the optical network unit receives OpenFlow/Config control information using an ONT Management and Control Interface (OMCI) Managed Entity, and the Managed Entity comprises any one of the following:
- a Managed Entity identification for referring to OpenFlow control;
- a version of OpenFlow;
- a location of the network-side control device;
- TCP/UDP config data ME pointer;
- parameters for setting up the tunnels for OpenFlow/Config protocol.
This embodiment proposes a new OMCI Managed Entity for carrying the OpenFlow/Config data.
According to a second aspect of the invention, it is provided a network-side control device, said network-side control device being provided with control plane functionalities of residential gateways, wherein, the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising Layer 3/4 packet processing functionalities of residential gateways.
In the second aspect, the network-side control device is considered as the vRG and is provided with control plane functionalities but without Layer 3/4 packet processing functionalities of residential gateways. The vRG is no longer a bottle neck for user data handling and the access network is more scalable.
In a preferred embodiment, the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities: IP routing based on IP address lookup; Network Address Translation; Packet inspection; and Firewalling.
In a preferred embodiment, the control plane functionalities of residential gateways comprises at least any one of the following: NAT binding control; Firewall Access Control List management; PPPoE control signaling; DHCP client; DHCP server; Universal Plug and Play server or Digital Living Network Alliance server; and Configuration management.
This embodiment proposes some specific control plane functionalities to control the residential gateway to process the Layer 3/4 packet.
In a preferred embodiment, the network-side control device comprises: a second interface, for exchanging control information about the data plane functionalities of residential gateways, with a residential gateway device provided with the data plane functionalities of residential gateways.
In this embodiment, the network-side control device has an interface to send the control information to the residential gateway for processing the Layer 3/4 packet.
In a preferred embodiment, the network-side control device is taken as an OpenFlow/Config control point defined in software defined network architecture, and the second interface is for exchanging the control information in the form of OpenFlow/Config protocol with the residential gateway device.
In this embodiment, SDN (Software Defined Networks) architecture is used for data and control plane separation. In a preferred embodiment, the network-side control device is implemented in any one of: a digital subscriber line access multiplexer; an optical line terminal; a broadband network gateway; and an equipment in a cloud.
This embodiment proposes that the network-side control device as the vRG can locate in various network elements in different kind of access network such as DSL or PON. In essence, the concept of the invention is to centralize the control plane of the RG in a vRG located in the operator network, and the vRG can be embodied in various network element and is not limited.
In a preferred embodiment, the network-side control device is implemented in the optical line terminal, and the network-side control device uses ONT management and control interface (OMCI) to establish and maintain GPON transmission tunnels with the residential gateway device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
This embodiment adapts the OMCI interface to maintain the GPON transmission tunnels. The OMCI interfaces itself is a current interface, and the embodiment adapts this interface to support the exchange of control information. Therefore this embodiment can be incorporated into the GPON very conveniently.
In a preferred embodiment, wherein the network-side control device is for transmitting the OpenFlow/Config control information in a Managed Entity, and the Managed Entity comprises any one of the following:
- a Managed Entity identification for referring to OpenFlow control;
- a version of OpenFlow;
- a location of the network-side control device;
- TCP/UDP config data ME pointer;
- parameters for set up the tunnels for OpenFlow/Config protocol.
This embodiment proposes a new managed entity for carrying the OpenFlow/Config data.
These and other features of the embodiment of the invention will be described in the following detailed embodiment part, or are known by ordinary skilled in the field based on the following detailed embodiment.
BRIEF DESCRIPTION OF THE DRAWINGS
Features, aspects and advantages of the present invention will become clear by reading the following description of non-limiting embodiments with the aid of appended drawings.
Fig. 1 schematically shows the transition from traditional residential gateway device in the home network to virtualized residential gateway in the network side;
Fig. 2 schematically shows the function separation of data plane and control plane between the residential gateway and the virtualized residential gateway, according to embodiments of the invention;
Fig. 3 schematically shows the implementation of embodiments of fig. 2 based on software defined network;
Fig. 4 schematically shows the implementation of embodiments of fig. 3 in the GPON access network according to one embodiment of the invention;
Fig. 5 schematically shows the implementation of the ONU in fig. 4 according to one embodiment of the invention;
Fig. 6 schematically shows the OMCI model to transmit OpenFlow/Config data according to one embodiment of the invention. DETAILED DESCRIPTION
Referring to fig. 2, in the customer premises, the present application proposes a residential gateway device with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises:
- Layer 3/4 packet processing functionalities of residential gateways;
and the residential gateway device further comprises:
- a first interface, for exchanging control information about data plane functionalities of residential gateways, with a network-side control device provided with the control plane functionalities of residential gateways;
- a controller, for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device.
In the network side, namely in the operator network, the present application proposes a network-side control device, said network-side control device being provided with control plane functionalities of residential gateways. Wherein, the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising: Layer 3/4 packet processing functionalities of residential gateways. As shown in fig. 2, in the present application, the network-side control device is also referred as vRG (virtualized residential gateway). As shown in fig. 2, the network-side control device vRG further comprises: a second interface, for exchanging control information about the data plane functionalities of residential gateways, with the residential gateway device provided with the data plane functionalities of residential gateways.
As shown in fig. 2, the vRG and the residential gateway RG communicate with each other via a dedicated control path between the second interface of the vRG and the first interface of the RG. The control path is denoted by the dash line in fig. 2. What is to be noted is that this control path is a logic communication tunnel. And there is a physical communication path that carries the control path between the operator network and the residential gateway RG: the access device in the operator network establishes a communication path with the residential gateway RG. This communication path is denoted by the solid line in fig. 2. More detailed implementations of the communication path will be elucidated in the following description.
In fig. 2, the network side control device vRG is shown as a block separate from the access device, however, this is just for showing the functional separation between the access function in the operator network and the control plane function for the residential gateway RG. In practical implementations, the network side control device vRG can be embodied within the access device, such as an OLT as described below, or in a digital subscriber line access multiplexer (DSLAM) or in a broadband network gateway (BNG); alternatively, the network side control device vRG can also be a standalone network element that is connected to the residential gateway RG via the access device, such as an equipment in a cloud. Those skilled in the art may understand that the network side control device vRG can be embodied in any network element in the operator network so as to centralize the control plane functionalities for the Layer 3/4 packet processing of the residential gateways.
More specifically, the Layer 3/4 packet processing functionalities of residential gateways implemented by the residential gateway device comprises at least any one of the following functionalities:
- IP routing based on IP address lookup;
- Network Address Translation;
- Packet inspection; and
- Firewalling.
It should be noted that the above functionalities are just examples, and any functionality that handles Layer 3/4 packet processing should be construed as the Layer 3/4 packet processing functionalities and thus fall into the scope of the invention.
Correspondingly, the control plane functionalities of residential gateways implemented by network-side control device vRG comprise at least any one of the following:
- NAT binding control
- Firewall Access Control List management
- PPPoE control signaling, for setting up the PPP connection, keeping the session alive and removing it;
- DHCP client, for obtaining an IP address;
- DHCP server, for to allocating IP addresses to the IP hosts that are connected to the residential gateway; - Universal Plug and Play (UPnP) server or Digital Living Network Alliance (DLNA) server; and
- Configuration management (Wifi / Voice / Internet settings).
The above description introduces the separation of data plane and control plane between the residential gateway device RG and the network-side control device vRG, as proposed by the invention. The following will propose detailed ways of implementing the RG and the vRG.
The present invention proposes one implementation based on Software Defined Networks (SDN). Specifically, SDN architecture could be one of the examples which can be used for data and control plane separation, wherein:
- the residential gateway device RG is taken as an OpenFlow switch defined in software defined network architecture; and
- the network-side control device vRG is taken as an OpenFlow/Config control point defined in software defined network architecture.
More specifically, the second interface of the network-side control device vRG and the first interface of the residential gateway device RG use OpenFlow/Config protocol to exchange the control information of the data plane. What is to be noted is that SDN is a widely discussed technology, and those skilled in the art understand how to adapt or extend the OpenFlow switch, OpenFlow/Config control point and OpenFlow protocol as generally defined in the SDN, to realize the functions of the residential gateway device and the network-side control device, and the present specification will not give further unnecessary details.
Fig. 3 gives a schematic illustration of the above implementation based on SDN, as described above, wherein, the access device is embodied as a DSLAM. In this embodiment, the access network is a DSL network. What is to be noted is that the concept of embodiments of the invention, namely the separation of data plane and control plane between the RG and the operator network, is independent from the access technology. In other embodiments, the residential gateway device and the corresponding access device are for EPON, GPON, XGPON, or 10GEPON.
I I Fig. 4 gives a schematic illustration of one implementation based on GPON. In this embodiment, the residential gateway device RG is embodied as an optical network unit (ONU), and the access device is embodied as an optical line terminal (OLT).
In case of GPON access networks, as well as XGPON or NGPON access networks, the communication path for carrying the OpenFlow/Config protocol needs to be pre-provisioned between the residential gateway device RG as the OpenFlow Switch and the network-side control device as the OpenFlow controller. In GPON, the communication path comprises GPON physical layer and L2 (including OF-VLAN, QoS, ...) which be provisioned from OLT through ONT Management and Control Interface (OMCI). OMCI is a general interface defined in GPON standard. However, the embodiment of the invention adapts OMCI to exchange the OpenFlow Config data.
More specifically, embodiments of the invention also create a new management domain in the ONU, i.e. openFlow domain, in G.988 and suggests to reuse the dual management ONU model defined in II.2 of G.988 in order to provision OpenFlow communication path L3 and application layer parameters (including OF-IP addresses, TCP, UDP, ...) from OLT through OMCI. The OMCI architecture model sets up the open flow communication path and GPON data path. The whole OMCI model would use the standard VEIP concept to have two separate management domains: open flow domain and OMCI domain.
As shown in fig. 5, the optical network unit ONU as the residential gateway device comprises:
- an OpenFlow domain including the OpenFlow switch together with an OpenFlow protocol stack; and
- a GPON domain, for establishing and maintaining GPON transmission tunnels with the network-side control device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
As shown in fig. 5, the GPON domain uses the ONT management and control interface (OMCI) to establish and maintain the GPON transmission tunnels with the network-side control device. GEM (GPON Encapsulation Method) is used as the transmission tunnel with the OLT for carrying OpenFlow Config data. Virtual Ethernet interface point (VEIP) is used for interfacing with the OpenFlow domain and exchanging the OpenFlow/Config data between the transmission tunnels and the OpenFlow domain.
Fig. 6 schematically shows the OMCI model to transmit OpenFlow/Config data according to one embodiment of the invention. One improvement proposed by the embodiment of the invention is that the OpenFlow Config data is inserted into the VEIP. The rest of the OMCI model is similar as the present standard. The model for VEIP would keep same as specified in II.2 of G.988.
The network-side control device in the OLT is for transmitting the OpenFlow/Config control information in a Managed Entity, and the optical network unit as the residential gateway device receives OpenFlow/Config control information using the ONT Management and Control Interface (OMCI) Managed Entity. The Managed Entity comprises any one of the following:
- a Managed Entity identification for referring to OpenFlow control;
- a version of OpenFlow;
- a location of the network-side control device;
- TCP/UDP config data ME pointer;
- parameters for set up the tunnels for OpenFlow/Config protocol.
The description and drawings merely illustrate the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the invention and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventor(s) to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
The functions of the various elements shown in the Figs., including any functional blocks labeled as "processors", may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term "processor" or "controller" should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage. Other hardware, conventional and/or custom, may also be included. Similarly, any switches shown in the FIGS, are conceptual only. Their function may be carried out through the operation of program logic, through dedicated logic, through the interaction of program control and dedicated logic, or even manually, the particular technique being selectable by the implementer as more specifically understood from the context.

Claims

What is claimed is:
1. A residential gateway device with data plane functionalities of residential gateways, wherein, the data plane functionalities of residential gateways comprises:
- Layer 3/4 packet processing functionalities of residential gateways;
and the residential gateway device further comprises:
- a first interface, for exchanging control information about the data plane functionalities of residential gateways, with a network-side control device provided with control plane functionalities of residential gateways; and
- a controller, for configuring the data plane functionalities of residential gateways according to the control information from the network-side control device.
2. A residential gateway device according to claim 1, wherein the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities:
- IP routing based on IP address lookup;
- Network Address Translation;
- Packet inspection; and
- Firewalling.
3. A residential gateway device according to claim 1 , wherein the residential gateway device is taken as an OpenFlow switch defined in software defined network architecture, and
the first interface is for exchanging the control information in the form of OpenFIow/Config protocol with the network-side control device.
4. A residential gateway device according to claim 3, wherein the residential gateway device is for an access network of any one of the following types:
- EPON;
- GPON; - XGPON;
- 10GEPON; and
- DSL.
5. A residential gateway device according to claim 4, wherein the residential gateway device comprises an optical network unit of GPON,
the optical network unit as the residential gateway device comprises:
- an OpenFlow domain including the OpenFlow switch together with an OpenFlow protocol stack; and
- a GPON domain, for establishing and maintaining GPON transmission tunnels with the network-side control device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
6. A residential gateway device according to claim 5, wherein the GPON domain uses an ONT management and control interface (OMCI) to establish and maintain the GPON transmission tunnels with the network-side control device, and
the GPON domain has a virtual Ethernet interface point, for interfacing with the OpenFlow domain and exchanging the OpenFlow/Config data between the transmission tunnels and the OpenFlow domain.
7. A residential gateway device according to claim 5, wherein the optical network unit receives OpenFlow/Config control information using an ONT Management and Control Interface (OMCI) Managed Entity, and the Managed Entity comprises any one of the following:
- a Managed Entity identification for referring to OpenFlow control;
- a version of OpenFlow;
- a location of the network-side control device;
- TCP/UDP config data ME pointer;
- parameters for setting up the tunnels for OpenFlow/Config protocol.
8. A network-side control device, said network-side control device being provided with control plane functionalities of residential gateways, wherein,
the network-side control device is without data plane functionalities of residential gateways, said data plane functionalities of residential gateways comprising:
- Layer 3/4 packet processing functionalities of residential gateways.
9. A network-side control device according to claim 8, wherein the Layer 3/4 packet processing functionalities of residential gateways comprises at least any one of the following functionalities:
- IP routing based on IP address lookup;
- Network Address Translation;
- Packet inspection; and
- Firewalling.
10. A network-side control device according to claim 8, wherein the control plane functionalities of residential gateways comprises at least any one of the following:
NAT binding control
Firewall Access Control List management
PPPoE control signaling;
DHCP client;
- DHCP server;
Universal Plug and Play server or Digital Living Network Alliance server; and
Configuration management.
11. A network-side control device according to claim 9, wherein the network-side control device comprises:
a second interface, for exchanging control information about the data plane functionalities of residential gateways, with a residential gateway device provided with the data plane functionalities of residential gateways.
12. A network-side control device according to claim 11, wherein the network-side control device is taken as an OpenFlow/Config control point defined in software defined network architecture, and
the second interface is for exchanging the control information in the form of OpenFlow/Config protocol with the residential gateway device.
13. A network-side control device according to claim 12, wherein the network-side control device is implemented in any one of:
- a digital subscriber line access multiplexer;
- an optical line terminal;
- a broadband network gateway;
- an equipment in a cloud.
14. A network-side control device according to claim 12, wherein the network-side control device is implemented the optical line terminal, and
the network-side control device uses ONT management and control interface (OMCI) to establish and maintain GPON transmission tunnels with the residential gateway device, said tunnels for carrying the control information in the form of OpenFlow/Config protocol.
15. A network-side control device according to claim 12, wherein the network-side control device is for transmitting the OpenFlow/Config control information in a Managed Entity, and the Managed Entity comprises any one of the following: - a Managed Entity identification for referring to OpenFlow control;
- a version of OpenFlow;
- a location of the network-side control device;
- TCP/UDP config data ME pointer;
- parameters for set up the tunnels for OpenFlow/Config protocol.
PCT/CN2013/082441 2013-08-28 2013-08-28 A residential gateway device and a network-side control device WO2015027405A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201380078483.0A CN105409184B (en) 2013-08-28 2013-08-28 Residential gateway device and network controls equipment
PCT/CN2013/082441 WO2015027405A1 (en) 2013-08-28 2013-08-28 A residential gateway device and a network-side control device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/082441 WO2015027405A1 (en) 2013-08-28 2013-08-28 A residential gateway device and a network-side control device

Publications (1)

Publication Number Publication Date
WO2015027405A1 true WO2015027405A1 (en) 2015-03-05

Family

ID=52585386

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/082441 WO2015027405A1 (en) 2013-08-28 2013-08-28 A residential gateway device and a network-side control device

Country Status (2)

Country Link
CN (1) CN105409184B (en)
WO (1) WO2015027405A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2966830B1 (en) * 2014-06-06 2017-08-16 Huawei Technologies Co., Ltd. Method, apparatus and system for interacting information in access network

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107294753B (en) * 2016-04-11 2019-06-25 中兴通讯股份有限公司 A kind of method that SDN/NFV opens access net system and manages ONU/ONT
CN108243080B (en) * 2016-12-23 2020-04-14 中国移动通信有限公司研究院 Intelligent method and device for optical network unit
CN112585915B (en) * 2019-07-30 2023-04-07 阿里巴巴集团控股有限公司 Apparatus and method for controlling data transmission in network system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1988578A (en) * 2006-12-19 2007-06-27 华为技术有限公司 System and method for providing multimedia communication and household gateway
WO2009080398A1 (en) * 2007-12-20 2009-07-02 Telefonaktiebolaget Lm Ericsson (Publ) Ims-based discovery and control of remote devices
CN101521666A (en) * 2008-01-28 2009-09-02 汤姆森许可贸易公司 Method for direct transmission of content, and associated control device and equipment
US20110320323A1 (en) * 2010-06-28 2011-12-29 Alcatel-Lucent Canada Inc. Pcrf-pcef-ocs interaction in wireless-wireline convergence

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047619B (en) * 2006-03-31 2012-09-26 中兴通讯股份有限公司 System for implementing multicast and broadcast service in radio communication system
CN101123549B (en) * 2006-08-11 2010-05-12 华为技术有限公司 Access network system with separated control and carrier and its communication implementation method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1988578A (en) * 2006-12-19 2007-06-27 华为技术有限公司 System and method for providing multimedia communication and household gateway
WO2009080398A1 (en) * 2007-12-20 2009-07-02 Telefonaktiebolaget Lm Ericsson (Publ) Ims-based discovery and control of remote devices
CN101521666A (en) * 2008-01-28 2009-09-02 汤姆森许可贸易公司 Method for direct transmission of content, and associated control device and equipment
US20110320323A1 (en) * 2010-06-28 2011-12-29 Alcatel-Lucent Canada Inc. Pcrf-pcef-ocs interaction in wireless-wireline convergence

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2966830B1 (en) * 2014-06-06 2017-08-16 Huawei Technologies Co., Ltd. Method, apparatus and system for interacting information in access network
US9941966B2 (en) 2014-06-06 2018-04-10 Huawei Technologies Co., Ltd. Method for information exchange in access network, apparatus, and system

Also Published As

Publication number Publication date
CN105409184A (en) 2016-03-16
CN105409184B (en) 2019-05-17

Similar Documents

Publication Publication Date Title
US20180176177A1 (en) Method for managing service chaining at a network equipment, corresponding network equipment
KR101418351B1 (en) Method and device for identifying and selecting an interface to access a network
US10079897B2 (en) Control of a chain of services
US9215175B2 (en) Computer system including controller and plurality of switches and communication method in computer system
US9374267B2 (en) Cloud based customer premises equipment
EP3219057B1 (en) Optimized inter-vrf (virtual routing and forwarding ) route leaking in network overlay based environments
EP3692685B1 (en) Remotely controlling network slices in a network
EP2506505A1 (en) Load distribution system, load distribution method, and program
US20020141352A1 (en) System and method for configuring an IP telephony device
WO2015024168A1 (en) Method for realizing residential gateway service function and server
WO2018100437A1 (en) Policy based configuration in programmable access networks
WO2012089504A1 (en) Home gateway system for accessing broadband services
WO2013133837A1 (en) Modifying virtual machine communications
EP3823222A1 (en) Implementation of service function chain on basis of software-defined network
US20160173357A1 (en) Probe Routing in a Network
WO2015027405A1 (en) A residential gateway device and a network-side control device
US20090169207A1 (en) Determining transmission port in a gpon network
US20160182370A1 (en) Probe Routing in a Network
WO2019229760A1 (en) Method and apparatus for optimized dissemination of layer 3 forwarding information in software defined networking (sdn) networks
KR102343908B1 (en) service function chaining control method for network services of virtual customer premises equipment
EP2659622B1 (en) Home gateway system for accessing broadband services
Menachi et al. Scalable, hierarchical, Ethernet transport network architecture (HETNA)
EP3301860A1 (en) Method for interconnecting virtual gateways and corresponding virtual gateway
Chalikosa The Potential Benefits and Challenges of Using Layer 3 IPV6 Configuration Commands in Industrial Communication Routers and Multilayer Switches
Boucadair Softwire Working Group Y. Cui Internet-Draft Tsinghua University Intended status: Standards Track Q. Sun Expires: January 14, 2013 China Telecom

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201380078483.0

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13892568

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13892568

Country of ref document: EP

Kind code of ref document: A1