WO2017054478A1 - 一种l2和l3 vpn中l3维护诊断方法、装置及系统 - Google Patents

一种l2和l3 vpn中l3维护诊断方法、装置及系统 Download PDF

Info

Publication number
WO2017054478A1
WO2017054478A1 PCT/CN2016/083519 CN2016083519W WO2017054478A1 WO 2017054478 A1 WO2017054478 A1 WO 2017054478A1 CN 2016083519 W CN2016083519 W CN 2016083519W WO 2017054478 A1 WO2017054478 A1 WO 2017054478A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
interface
maintenance
vpn
entity
Prior art date
Application number
PCT/CN2016/083519
Other languages
English (en)
French (fr)
Inventor
刘爱华
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP16850103.9A priority Critical patent/EP3358784A4/en
Publication of WO2017054478A1 publication Critical patent/WO2017054478A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L2012/4629—LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present application relates to, but is not limited to, a Packet Transport Network (PTN), especially a Layer 2 (L2, Layer 2) and Layer 3 (L3, Layer 3) virtual private network (VPN, Virtual Private Network) L3. Maintain diagnostic methods, devices, and systems.
  • PTN Packet Transport Network
  • L2, Layer 2 Layer 2
  • L3, Layer 3 Layer 3
  • VPN Virtual Private Network
  • FIG. 1 is a schematic diagram of a typical L2+L3 VPN networking for mobile backhaul in the related art.
  • a typical L2+L3 VPN uses an L2 VPN network at the access layer, an L3 VPN network at the aggregation and core layers, and a bridging technology at the edge of the L2 and L3 VPNs.
  • the L2+L3 VPN networking structure is conducive to network planning and construction, the L2 VPN and the L3 VPN only carry part of the service path because the services carried by the network are divided by the L2 and L3 VPNs. End-to-End maintenance.
  • IP Internet Internet Explorer
  • TWAMP Tin-Way Active Measurement Protocol
  • RFC 5357 provides a rich set of L3 performance measurement capabilities.
  • L2 detection technologies L2 devices are required to support L3 interfaces and addresses. This requirement brings many obstacles to the deployment of IP-based service end-to-end maintenance functions.
  • the end-to-end L3 maintenance diagnostic function of the L2+L3 VPN service path requires additional configuration and occupation of an IP address, and the IP address also needs to be the IP address of the detected service.
  • the IP network segment that is, the network mask is the same
  • this requirement cannot be met in many actual projects.
  • 62 of the network segments with a 64-IP address are typically used for base station services, and only 2 IPs are reserved.
  • the address can be used for maintenance diagnosis, which is far from meeting the requirements of service maintenance diagnosis.
  • the IP address configured on the L2 device is only the same as the service IP segment but not the same (the IP address conflicts with the same IP address).
  • the result of the maintenance of the IP address diagnosis does not fully represent the actual situation of the actual business. Therefore, in the current mobile backhaul L2+L3 VPN network structure, the L3 device L3 address planning and configuration problem affects the end-to-end maintenance diagnosis of the IP service.
  • This document provides an L3 maintenance diagnosis method, device, and system for L2 and L3 VPNs.
  • the L2 device can easily support L3 maintenance diagnosis in the L2+L3 VPN carried by the mobile backhaul service.
  • An L3 maintenance diagnosis method in the L2 and L3 VPNs includes: the L2 device borrows the L3 address of the corresponding L3 interface; the L2 device performs L3 maintenance diagnosis by proxying the L3 interface by borrowing the L3 address of the L3 interface.
  • the L3 device where the L3 interface is located is directly connected to the L2 device.
  • the L3 device borrowing the L3 address of the corresponding L3 interface includes:
  • the L2 device borrows the L3 address of the L3 interface statically configured through the configuration command; or
  • the L2 device borrows the L3 address of the corresponding L3 interface obtained by actively monitoring the L3 address.
  • the method further includes: the L2 device actively monitoring, by using the L3 address, obtaining the L3 interface of the L3 interface that the L2 device can borrow. address.
  • the L3 device that actively monitors the L3 address of the L3 interface that the L2 device can borrow by using the L3 address includes:
  • ARP L3 Address Resolution Protocol
  • An L3 maintenance diagnostic device in an L2 and L3 VPN configured in an L2 device, includes: an L3 maintenance diagnostic sub-entity, configured to: borrow an L3 address of a corresponding L3 interface; and a processing module, configured to: borrow an L3 address proxy of the L3 interface The L3 interface performs L3 maintenance diagnosis.
  • the L3 device where the L3 interface is located is directly connected to the L2 device.
  • the L3 maintains a diagnostic sub-entity, including:
  • the first borrowing address unit is set to: borrow the L3 address of the L3 interface statically configured by the configuration command; or
  • the second borrowing address unit is set to: borrow the L3 address of the corresponding L3 interface obtained by actively monitoring the L3 address.
  • the second borrowing address unit is further configured to: actively monitor the L3 address of the borrowable L3 interface by using the L3 address.
  • the second borrowing address unit is set to:
  • An L3 maintenance and diagnosis system in an L2 and L3 VPN comprising: an L2 device and an L3 device, wherein the L2 device borrows an L3 address of a corresponding L3 interface, and performs L3 maintenance diagnosis by proxying the L3 interface by borrowing an L3 address of the L3 interface. Wherein the L3 interface is located on the L3 device.
  • a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the above method.
  • the L2 device borrows the L3 address of the corresponding L3 interface, and performs L3 maintenance diagnosis by proxying the L3 interface by borrowing the L3 address of the L3 interface.
  • the L2 device conveniently supports the L3 maintenance diagnosis in the L2+L3 VPN carried by the mobile backhaul service.
  • the L2 device borrows the L3 address to simplify or configure the L3 address in the mobile backhaul service carrying the L2+L3 VPN network, so that the L2 device can conveniently support the L3 maintenance diagnosis, thereby supporting the mobile backhaul service.
  • End-to-end L3 maintenance diagnosis solves the problem of service path segmentation caused by L2 and L3 VPN bridge networking.
  • FIG. 1 is a schematic diagram of a typical L2+L3 VPN networking for mobile backhaul in the related art
  • FIG. 2 is a flowchart of an L3 maintenance diagnosis method in an L2 and L3 VPN according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an L3 maintenance diagnostic apparatus in an L2 and L3 VPN according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of deployment of an L3 interface entity and an L3 maintenance diagnostic sub-entity according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of an L3 maintenance diagnosis method in an L2 and L3 VPN according to an embodiment of the present invention. As shown in FIG. 2, the L3 maintenance diagnosis method in the L2 and L3 VPNs provided in this embodiment includes the following steps:
  • Step 11 The L2 device borrows the L3 address of the corresponding L3 interface.
  • the L3 device where the L3 interface is located is directly connected to the L2 device.
  • step 11 includes:
  • the L2 device borrows the L3 address of the L3 interface statically configured through the configuration command; or,
  • the L2 device borrows the L3 address of the corresponding L3 interface obtained by actively monitoring the L3 address.
  • the method further includes: the L2 device actively monitoring the L3 address of the L3 interface that the L2 device can borrow by using the L3 address.
  • the L3 address of the L3 interface that the L2 device can actively use to obtain the L3 interface borrowed by the L2 device includes: monitoring a specific L3 address resolution protocol (ARP) to obtain an L3 address that can be borrowed; or monitoring specific L3 Message to get the L3 address that can be borrowed.
  • ARP L3 address resolution protocol
  • Step 12 The L2 device performs L3 maintenance diagnosis by proxying the L3 interface by borrowing the L3 address of the L3 interface.
  • the embodiment of the present invention further provides an L3 maintenance diagnostic device in the L2 and L3 VPN, which is configured on the L2 device, and includes: an L3 maintenance diagnostic sub-ent.
  • the L3 address is set to: borrow the L3 address of the corresponding L3 interface; and the processing module is set to: The L3 maintenance diagnosis is performed by proxying the L3 interface by borrowing the L3 address of the L3 interface.
  • the L3 device where the L3 interface is located is directly connected to the L2 device.
  • the L3 maintains a diagnostic sub-entity, including:
  • the first borrowing address unit is set to: borrow the L3 address of the L3 interface statically configured by the configuration command; or
  • the second borrowing address unit is set to: borrow the L3 address of the corresponding L3 interface obtained by actively monitoring the L3 address.
  • the second borrowing address unit is further configured to: actively monitor the L3 address of the borrowable L3 interface by using the L3 address.
  • the second borrowing address unit is configured to: monitor a specific L3 address resolution protocol (ARP) to obtain an L3 address that can be borrowed; or monitor a specific L3 address to obtain a borrowable L3 address.
  • ARP L3 address resolution protocol
  • FIG. 3 is a schematic diagram of an L3 maintenance diagnostic apparatus in an L2 and L3 VPN according to an embodiment of the present invention.
  • the L3 maintenance diagnostic apparatus in the L2 and L3 VPNs provided in this embodiment includes at least one L3 maintenance diagnostic sub-entity 31 and a processing module 32.
  • the processing flow of the above module is the same as that described above, and thus will not be described herein.
  • the above modules may be implemented by a processor executing programs/instructions stored in the memory.
  • the embodiment of the present invention further provides an L3 maintenance and diagnosis system in an L2 and L3 VPN, including: an L2 device and an L3 device; the L2 device borrows an L3 address of the corresponding L3 interface, and proxyes the L3 by borrowing an L3 address of the L3 interface.
  • the interface performs L3 maintenance diagnosis, where the L3 interface is located on the L3 device.
  • the L3 address borrowing of the L2 device is implemented by the L3 maintenance diagnostic sub-entity and the L3 interface entity.
  • the L3 maintenance diagnostic sub-entity is logically part of the L3 interface entity, and the physical deployment may be
  • the L3 interface entity can be physically separated from the L3 maintenance diagnostic sub-entity.
  • the number of L3 maintenance diagnostic sub-entities is one or more, and can be deployed on all or part of the L2 device.
  • FIG. 4 is a schematic diagram of deployment of an L3 interface entity and an L3 maintenance diagnostic sub-entity according to an embodiment of the present invention.
  • all or part of the N L3 maintenance diagnostic sub-entries 31 are deployed on the L2 device 41, and the L3 interface address sub-entity 431 of the L3 interface entity 43 is deployed on the L3 device 42, and the L3 maintenance diagnostic sub-entity 31 inherits.
  • the L3 interface address sub-entity 431 attribute of the L3 interface entity 43 ie, the L3 address). In this manner, the L3 maintenance diagnostic sub-ent.
  • the L2 device 41 realizes that the L2 device 41 borrows the L3 address of the L3 interface by inheriting the L3 address of the L3 interface entity 43 and supports the L2 device 41L3 address configuration free. Furthermore, the L3 maintenance diagnostic sub-entity 31 may, for example, also inherit other L3 attributes of the L3 interface entity 43. Wherein, when the L3 interface entity 43 is fully supported on the L2 device 41, the L2 device 42 has a complete L3 interface function.
  • the L3 maintenance diagnostic sub-ent. 31 implements the static configuration of the configuration command or the active monitoring of the L3 address to implement the L3 device 41 borrowing the L3 address of the L3 interface.
  • the L3 address of the L3 interface entity to which the L3 maintenance diagnostic sub-entity 31 belongs is statically configured.
  • the L3 maintenance diagnostic sub-entries 31 enable the L3 address active monitoring function to monitor the L3 address of the L3 interface entity to which the L3 maintenance diagnostic sub-entity 31 belongs. .
  • the L3 maintenance diagnostic sub-entries 31 obtains the L3 address that the L3 maintenance diagnostic sub-entries 31 can borrow by actively monitoring the L3 address; for example, monitoring the specific L3 address resolution protocol (ARP) of the L3 maintenance diagnostic sub-ent. 31; or
  • the specific L3 message (for example, a customized L3 message) that is maintained by the L3 maintenance diagnostic sub-ent. 31 is monitored to obtain the L3 address that the L3 maintenance diagnostic sub-entry 31 can borrow.
  • ARP specific L3 address resolution
  • the L3 address configured by the L3 maintenance diagnostic sub-enticle 31 and the L3 address obtained by the active monitoring are used for address borrowing only, and are not used to configure the L3 interface entity 43 of the L2 device 41, and the L2 device 41 is not implemented.
  • Complete L3 interface entity functions including creating an L3 interface, responding to an L3 address resolution protocol (ARP), etc.
  • the borrowed address can be used for maintenance diagnosis of the L3 interface entity 43, such as proxy L3 interface response Ping detection, proxy response L3 interface TWAMP measurement.
  • the L2 device borrows the L3 address proxy L3 interface to implement the Ping detection response. Bright.
  • the mobile backhaul networking is shown in Figure 5.
  • the access layer is an L2 VPN network.
  • L2 VPN network For the mobile backhaul service from L2 VPN to L3 VPN end-to-end connectivity ping detection, either the base station is pinged from the wireless core network, or The L3 VPN is located at the L3 device Ping base station, so that although the connectivity between the wireless base station and the wireless core network and the L3 VPN drop location can be detected, the connectivity between the L2 VPN access point device and the L3 VPN drop location cannot be detected.
  • the L2 device implements the proxy wireless base station Ping response by using the L3 address of the wireless base station, and provides end-to-end connectivity detection between the L2 VPN access point and the L3 VPN drop location.
  • This embodiment is described as follows:
  • the radio base station provides an L3 interface entity, which can support the function of the L3 maintenance diagnostic sub-enteration Ping.
  • the L2 device of the L2 VPN access point that is connected to the radio base station deploys the function of the L3 maintenance diagnostic sub-enteration Ping.
  • the L2 device itself does not need to create an L3 interface, and directly borrows the L3 address of the wireless base station.
  • the L3 interface entity is deployed on the wireless base station and the L2 VPN access layer L2 device, wherein the L3 interface address sub-entity is deployed on the wireless base station, and
  • the L3 maintenance diagnostic sub-entity ping function is deployed on the L2 VPN access layer L2 device.
  • the L3 maintenance diagnostic sub-entity ping function of the L3 interface entity is configured to inherit the interface address attribute of the L3 interface entity, and the L3 interface address sub-entity of the L3 interface entity is deployed on the radio base station;
  • the L2 device to enable the L3Ping proxy response function and statically configure the L3 interface address (that is, the L3 interface address of the radio base station).
  • the L2 device itself does not create an L3 interface and does not affect the L3 interface of the radio base station. Or any other function; or, the L3 device L3Ping proxy response function is enabled and the L3 address monitoring mode is enabled, and the L3 address of the docking base station of the wireless base station is obtained by monitoring the radio base station L3 Address Resolution Protocol (ARP);
  • ARP Address Resolution Protocol
  • the L2 device After the L3 maintenance diagnostic ping function is enabled, the L2 device immediately listens to the service flow passing through the L2 device access point. After detecting the Ping request message, the proxy L3 interface entity performs a Ping response. Similarly, the L3 interface can also initiate a Ping request. .
  • the L2 device borrows the L3 address proxy L3 interface to implement TWAMP performance measurement.
  • the mobile backhaul networking is shown in Figure 5.
  • the access layer is an L2 VPN network.
  • L2 VPN to L3 VPN end-to-end L3 TWAMP performance measurement either the TWAMP from the wireless core network side to the base station is initiated.
  • Measurement either from the L3 VPN location L3 device initiated to the base station TWAMP measurement, so although it can measure the L3 performance between the wireless base station and the wireless core network and the L3 VPN drop location, but can not measure the L2 VPN access point device and L3 VPN End-to-end L3 performance between drop locations.
  • the L2 device implements the L3 TWAMP response by borrowing the L3 address of the wireless base station, and provides end-to-end L3 performance measurement between the L2 VPN access point and the L3 VPN drop location.
  • This embodiment is described as follows:
  • the wireless base station provides an L3 interface entity, which itself can support the L3 maintenance diagnostic sub-entity TWAMP performance measurement function.
  • the L2 device of the L2 VPN access point that is connected to the wireless base station deploys the L3 maintenance diagnostic sub-entity TWAMP performance measurement function.
  • the L2 device itself does not need to create an L3 interface, and directly borrows the L3 address of the wireless base station.
  • the L3 interface entity is deployed on the wireless base station and the L2 VPN access layer L2 device, wherein the L3 interface address sub-entity is deployed on the wireless base station, and The L3 maintenance diagnostic sub-entity TWAMP performance measurement function is deployed on the L2 VPN access layer L2 device;
  • the L3 maintenance diagnostic sub-ent The TWAMP performance measurement function of the L3 interface entity inherits the interface address attribute of the L3 interface entity, and the L3 interface address sub-entity of the L3 interface entity is deployed on the radio base station;
  • the L2 device Configure the L2 device to enable the L3 TWAMP performance measurement proxy response function and statically configure the L3 interface address of the TWAMP response (that is, the L3 interface address of the radio base station).
  • the L2 device itself does not create an L3 interface and does not affect the radio base station. Any other function of the L3 interface; or, enable the L3 device L3 TWAMP response function and enable the L3 address monitoring mode, and obtain the L3 address of the docking base station of the wireless base station by monitoring the radio base station L3 Address Resolution Protocol (ARP);
  • ARP Address Resolution Protocol
  • the L2 device After the L3 maintenance diagnostic TWAMP function is enabled, the L2 device immediately listens to access through the L2 device. The service flow of the point, after listening to the TWAMP protocol message, the proxy L3 interface entity performs the TWAMP response. Similarly, the L3 interface can also actively initiate the TWAMP measurement.
  • the L2 device borrows the L3 address proxy L3 interface to implement the Y.1564 performance measurement.
  • the mobile backhaul networking is shown in Figure 5.
  • the access layer is an L2 VPN network.
  • the L2 VPN to the L3 VPN end-to-end L3 Y.1564 performance measurement is initiated from the wireless core network side to the base station.
  • the Y.1564 measurement either from the L3 VPN location L3 device to the base station Y.1564 measurement, so that although the L3 performance between the wireless base station and the wireless core network and the L3 VPN drop location can be measured, the L2 VPN connection cannot be measured.
  • End-to-end L3 performance between the inbound device and the L3 VPN drop location is an L2 VPN network.
  • the L2 device implements the L3 Y.1564 response by using the L3 address of the wireless base station, and provides end-to-end L3 performance measurement between the L2 VPN access point and the L3 VPN drop location.
  • This embodiment is described as follows:
  • the radio base station provides an L3 interface entity, which can support the L3 maintenance diagnostic sub-entity Y.1564 performance measurement function.
  • the L2 device of the L2 VPN access point that is connected to the radio base station deploys the L3 maintenance diagnostic sub-ent. 1564 performance measurement function;
  • the L2 device itself does not need to create an L3 interface, and directly borrows the L3 address of the wireless base station.
  • the L3 interface entity is deployed on the wireless base station and the L2 VPN access layer L2 device, wherein the L3 interface address sub-entity is deployed on the wireless base station, and The L3 maintenance diagnostic sub-entity Y.1564 performance measurement function is deployed on the L2 VPN access layer L2 device;
  • the L3 maintenance diagnostic sub-entity Y.1564 performance measurement function deployed on the L2 device inherits the interface address attribute of the L3 interface entity, and the L3 interface address sub-entity of the L3 interface entity is deployed on the radio base station;
  • the L2 device configures the L2 device to enable the L3 Y.1564 performance measurement proxy response function and statically configure the L3 interface address of the Y.1564 response (that is, the L3 interface address of the wireless base station).
  • the L2 device itself does not create an L3 interface. Does not affect any other functions of the L3 interface of the wireless base station; or, turn on the L3 device L3 Y.1564 response function and enable the L3 address monitoring mode, by monitoring
  • the radio base station L3 address resolution protocol (ARP) acquires the L3 address of the docking base station of the radio base station;
  • the L2 device After the L3 maintenance diagnosis Y.1564 function is enabled, the L2 device immediately listens to the service flow passing through the access point of the L2 device. After detecting the Y.1564 protocol packet, the proxy L3 interface entity responds with Y.1564. Similarly, The L3 interface can be actively initiated to initiate Y.1564 measurements.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, which are implemented by the processor to implement the L3 maintenance diagnosis method in the L2 and L3 VPNs.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the L2 device borrows the L3 address to simplify or configure the L3 address in the mobile backhaul service carrying the L2+L3 VPN network, so that the L2 device can conveniently support the L3 maintenance diagnosis, thereby supporting the mobile backhaul service.
  • End-to-end L3 maintenance diagnosis solves the problem of service path segmentation caused by L2 and L3 VPN bridge networking.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布一种二层(L2)和三层(L3)虚拟专用网络(VPN)中L3维护诊断方法、装置及系统，所述方法包括：L2设备借用相应L3接口的L3地址，并通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。

Description

一种L2和L3 VPN中L3维护诊断方法、装置及系统 技术领域
本申请涉及但不限于包传送网络(PTN，Packet Transport Network)，尤其是一种二层(L2，Layer 2)和三层(L3，Layer 3)虚拟专用网络(VPN，Virtual Private Network)中L3维护诊断方法、装置及系统。
背景技术
随着移动业务网络协议(IP，Internet Protocol)化的发展以及长期演进(LTE，Long Term Evolution)业务承载的需求，移动回传(Mobile Backhaul)对承载网的要求越来越高，要求在承载网络的核心层引入三层(L3，Layer 3)调度，而接入网仍采用简单的二层(L2，Layer 2)组网，形成了独特的L2+L3虚拟专用网络(VPN，Virtual Private Network)的承载结构，其中，L3为开放式系统互联(OSI，Open System Interconnection)网络模型的网络层，L2为OSI网络模型的链路层。图1为相关技术中移动回传典型的L2+L3 VPN组网示意图。如图1所示，典型的L2+L3 VPN在接入层采用L2 VPN组网，在汇聚和核心层采用L3 VPN组网，在L2和L3 VPN的边缘通过桥接技术进行连接。
虽然L2+L3 VPN组网结构有利于网络规划和建设，但是由于该网络承载的业务被L2和L3 VPN进行了网络分割，L2 VPN和L3 VPN都只承载业务路径的一部分，不便于业务端到端(End-to-End)的维护。
针对IP化的业务端到端维护诊断的需求，相关技术例如通过下述技术实现：IP互联网包探索器(Ping，Packet Internet Groper)作为最简单的维护工具，提供IP路径的连通性检测；双向主动测量协议(TWAMP，Two-Way Active Measurement Protocol)RFC 5357提供丰富的L3性能测量功能。但是这些技术无一例外都是L3检测技术，对于L2+L3 VPN承载网络均要求L2设备端支持L3接口和地址，这个要求对于IP化的业务端到端维护功能部署带来了诸多障碍。首先，完成L2+L3 VPN业务路径端到端L3维护诊断功能需要额外配置和占用IP地址，而且该IP地址还需要与被检测业务的IP地址 处于相同IP网段(即网络掩码相同)，这个要求在很多实际工程中无法满足，比如中移典型规划一个64个IP地址的网段中有62个用于基站业务，仅仅保留2个IP地址可以用于维护诊断，远远无法满足业务维护诊断的要求；其次，L2设备端配置的IP地址只是和业务IP相同网段而不是相同(配置相同IP地址会有IP地址冲突问题)，基于该IP地址维护诊断的结果并不能完全代表实际业务的真实情况。因此，在当前移动回传L2+L3 VPN组网结构下，L2设备端L3地址的规划和配置问题影响了IP化业务端到端的维护诊断。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种L2和L3 VPN中L3维护诊断方法、装置及系统，能够实现在移动回传业务承载的L2+L3 VPN中L2设备方便地支持L3维护诊断。
一种L2和L3 VPN中L3维护诊断方法，包括：L2设备借用相应L3接口的L3地址；L2设备通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
可选地，所述L3接口所在的L3设备与所述L2设备直连。
可选地，所述L2设备借用相应L3接口的L3地址包括：
所述L2设备借用通过配置命令静态配置的L3接口的L3地址；或者，
所述L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址。
可选地，所述L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址之前，该方法还包括：所述L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址。
可选地，所述L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址包括：
监视特定L3地址解析协议(ARP)，以获得能借用的L3地址；或者，
监视特定L3报文，以获得能借用的L3地址。
一种L2和L3 VPN中L3维护诊断装置，设置于L2设备，包括：L3维护诊断子实体，设置为：借用相应L3接口的L3地址；处理模块，设置为：通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
可选地，所述L3接口所在的L3设备与所述L2设备直连。
可选地，所述L3维护诊断子实体，包括：
第一借用地址单元，设置为：借用通过配置命令静态配置的L3接口的L3地址；或者，
第二借用地址单元，设置为：借用通过L3地址主动监视获得的相应L3接口的L3地址。
可选地，所述第二借用地址单元，还设置为：通过L3地址主动监视获得能借用的L3接口的L3地址。
可选地，所述第二借用地址单元，设置为：
监视特定L3地址解析协议，以获得能借用的L3地址；或者，
监视特定L3地址，以获得能借用的L3地址。
一种L2和L3 VPN中L3维护诊断系统，包括：L2设备以及L3设备，所述L2设备借用相应的L3接口的L3地址，并通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断，其中，所述L3接口位于L3设备上。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述方法。
在本发明实施例中，L2设备借用相应L3接口的L3地址，并通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。如此，本发明实施例实现了在移动回传业务承载的L2+L3 VPN中L2设备方便地支持L3维护诊断。
通过本发明实施例，在移动回传业务承载L2+L3 VPN网络中L2设备端借用L3地址实现L3地址简化配置或者免配置，使得L2设备可以方便地支持L3维护诊断，从而支持移动回传业务路径端到端的L3维护诊断，解决了L2和L3 VPN桥接组网带来的业务路径分割问题。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为相关技术中移动回传典型的L2+L3 VPN组网示意图；
图2为本发明实施例提供的L2和L3 VPN中L3维护诊断方法的流程图；
图3为本发明一实施例提供的L2和L3 VPN中L3维护诊断装置的示意图；
图4为本发明一实施例提供的L3接口实体及L3维护诊断子实体的部署示意图；
图5为本发明实施例的应用场景示意图。
本发明的实施方式
以下结合附图对本发明的实施方式进行说明，应当理解，以下所说明的实施例仅用于说明和解释本申请，并不用于限定本申请。
图2为本发明实施例提供的L2和L3 VPN中L3维护诊断方法的流程图。如图2所示，本实施例提供的L2和L3 VPN中L3维护诊断方法包括以下步骤：
步骤11：L2设备借用相应L3接口的L3地址。
可选地，L3接口所在的L3设备与L2设备直连。
可选地，步骤11包括：
L2设备借用通过配置命令静态配置的L3接口的L3地址；或者，
L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址。
可选地，L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址之前，该方法还包括：L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址。其中，L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址包括：监视特定L3地址解析协议(ARP，Address Resolution Protocol)，以获得能借用的L3地址；或者，监视特定L3 报文，以获得能借用的L3地址。
步骤12：L2设备通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
此外，本发明实施例还提供一种L2和L3 VPN中L3维护诊断装置，设置于L2设备，包括：L3维护诊断子实体，设置为：借用相应L3接口的L3地址；处理模块，设置为：通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
可选地，L3接口所在的L3设备与所述L2设备直连。
可选地，所述L3维护诊断子实体，包括：
第一借用地址单元，设置为：借用通过配置命令静态配置的L3接口的L3地址；或者，
第二借用地址单元，设置为：借用通过L3地址主动监视获得的相应L3接口的L3地址。
可选地，所述第二借用地址单元，还设置为：通过L3地址主动监视获得能借用的L3接口的L3地址。可选地，所述第二借用地址单元，设置为：监视特定L3地址解析协议(ARP)，以获得能借用的L3地址；或者，监视特定L3地址，以获得能借用的L3地址。
图3为本发明一实施例提供的L2和L3 VPN中L3维护诊断装置的示意图。如图3所示，本实施例提供的L2和L3 VPN中L3维护诊断装置包括至少一个L3维护诊断子实体31以及处理模块32。关于上述模块的处理流程同上所述，故于此不再赘述。于实际应用中，上述模块可以通过处理器执行存储在存储器中的程序/指令实现。
此外，本发明实施例还提供一种L2和L3 VPN中L3维护诊断系统，包括：L2设备以及L3设备；L2设备借用相应L3接口的L3地址，并通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断，其中，所述L3接口位于L3设备上。
L2设备的L3地址借用通过L3维护诊断子实体及L3接口实体实现。其中，L3维护诊断子实体逻辑上为L3接口实体的一部分，物理部署上可以在 不同设备上，即L3接口实体可以和L3维护诊断子实体物理上分离，L3维护诊断子实体的数目为一个或多个，可以全部或部分部署在L2设备上。
图4为本发明一实施例提供的L3接口实体及L3维护诊断子实体的部署示意图。如图4所示，N个L3维护诊断子实体31的全部或部分部署在L2设备41上，L3接口实体43的L3接口地址子实体431部署在L3设备42上，L3维护诊断子实体31继承L3接口实体43的L3接口地址子实体431属性(即L3地址)。如此，L2设备41上配置的L3维护诊断子实体31通过继承L3接口实体43的L3地址实现L2设备41借用L3接口的L3地址，支持L2设备41L3地址免配置。此外，L3维护诊断子实体31例如还可继承L3接口实体43的其他L3属性。其中，当L3接口实体43在L2设备41上完整支持时，L2设备42具备完整的L3接口功能。
其中，L3维护诊断子实体31通过配置命令静态配置或者L3地址主动监视实现L2设备41借用L3接口的L3地址。其中，通过配置命令静态配置L3维护诊断子实体31所属L3接口实体的L3地址；或者，L3维护诊断子实体31开启L3地址主动监视功能，监视L3维护诊断子实体31所属L3接口实体的L3地址。其中，L3维护诊断子实体31通过L3地址主动监视获得本L3维护诊断子实体31能借用的L3地址；例如，监视经过本L3维护诊断子实体31的特定L3地址解析协议(ARP)；或者，监视经过本L3维护诊断子实体31的特定L3报文(如，自定义的L3报文)，以获得本L3维护诊断子实体31能借用的L3地址。
其中，L3维护诊断子实体31通过静态配置方式配置的L3地址和通过主动监视获得的L3地址只用于地址借用，并不是用来配置L2设备41的L3接口实体43，并不实现L2设备41完整的L3接口实体功能，包括创建L3接口、响应L3地址的解析协议(ARP)等，该借用的地址可以用于L3接口实体43的维护诊断，比如代理L3接口响应Ping检测、代理响应L3接口的TWAMP测量。
以下通过多个实施例进行说明。
实施例一
本实施例对L2设备借用L3地址代理L3接口实现Ping检测响应进行说 明。
移动回传组网如图5所示，接入层为L2 VPN组网，对于移动回传业务从L2 VPN到L3 VPN端到端连通性Ping检测，要么从无线核心网侧Ping基站，要么从L3 VPN落地点L3设备Ping基站，这样虽然能检测无线基站与无线核心网和L3 VPN落地点之间的连通性，但是不能检测L2 VPN接入点设备与L3 VPN落地点之间的连通性。
本实施例实现L2设备借用无线基站的L3地址实现代理无线基站Ping响应，提供L2 VPN接入点到L3 VPN落地点之间的端到端连通性检测。本实施例说明如下：
无线基站提供L3接口实体，其本身可以支持L3维护诊断子实体Ping的功能，于此，与所述无线基站对接的L2 VPN接入点的L2设备部署L3维护诊断子实体Ping的功能；
L2设备本身不用创建L3接口，直接借用无线基站的L3地址，于此，L3接口实体部署在无线基站和L2 VPN接入层L2设备上，其中，L3接口地址子实体部署在无线基站上，而L3维护诊断子实体Ping功能部署在L2 VPN接入层L2设备上；
L2设备上部署的L3维护诊断子实体Ping功能继承L3接口实体的接口地址属性，L3接口实体的L3接口地址子实体部署于无线基站上；
通过静态命令配置L2设备开启L3Ping代理响应功能并静态配置Ping代理响应的L3接口地址(即无线基站的L3接口地址)，其中，L2设备本身并不创建L3接口，且并不影响无线基站L3接口的其他任何功能；或者，开启L2设备L3Ping代理响应功能并开启L3地址监视模式，通过监视无线基站L3地址解析协议(ARP，Address Resolution Protocol)，获取无线基站的对接基站的L3地址；
开启L3维护诊断Ping功能后，L2设备立即侦听经过该L2设备接入点的业务流，侦听到Ping请求消息后代理L3接口实体进行Ping响应，同理，也可以代理L3接口发起Ping请求。
实施例二
本实施例对L2设备借用L3地址代理L3接口实现TWAMP性能测量进行说明。
移动回传组网如图5所示，接入层为L2 VPN组网，对于移动回传业务从L2 VPN到L3 VPN端到端L3 TWAMP性能测量，要么从无线核心网侧发起到基站的TWAMP测量，要么从L3 VPN落地点L3设备发起到基站的TWAMP测量，这样虽然能测量无线基站与无线核心网和L3 VPN落地点之间的L3性能，但是不能测量L2 VPN接入点设备与L3 VPN落地点之间端到端的L3性能。
本实施例实现L2设备借用无线基站的L3地址实现L3 TWAMP响应，提供L2 VPN接入点到L3 VPN落地点之间的端到端L3性能测量。本实施例说明如下：
无线基站提供L3接口实体，其本身可以支持L3维护诊断子实体TWAMP性能测量的功能，于此，与所述无线基站对接的L2 VPN接入点的L2设备部署L3维护诊断子实体TWAMP性能测量功能；
L2设备本身不用创建L3接口，直接借用无线基站的L3地址，于此，L3接口实体部署在无线基站和L2 VPN接入层L2设备上，其中，L3接口地址子实体部署在无线基站上，而L3维护诊断子实体TWAMP性能测量功能部署在L2 VPN接入层L2设备上；
L2设备上部署的L3维护诊断子实体TWAMP性能测量功能继承L3接口实体的接口地址属性，L3接口实体的L3接口地址子实体部署于无线基站上；
通过静态命令配置L2设备开启L3 TWAMP性能测量代理响应功能并静态配置TWAMP响应的L3接口地址(即无线基站的L3接口地址)，其中，L2设备本身并不创建L3接口，且并不影响无线基站L3接口的其他任何功能；或者，开启L2设备L3 TWAMP响应功能并开启L3地址监视模式，通过监视无线基站L3地址解析协议(ARP)，获取无线基站的对接基站的L3地址；
开启L3维护诊断TWAMP功能后，L2设备立即侦听经过该L2设备接入 点的业务流，侦听到TWAMP协议报文后代理L3接口实体进行TWAMP响应，同理，也可以代理L3接口主动发起TWAMP测量。
实施例三
本实施例对L2设备借用L3地址代理L3接口实现Y.1564性能测量进行说明。
移动回传组网如图5所示，接入层为L2 VPN组网，对于移动回传业务从L2 VPN到L3 VPN端到端L3 Y.1564性能测量，要么从无线核心网侧发起到基站的Y.1564测量，要么从L3 VPN落地点L3设备发起到基站的Y.1564测量，这样虽然能测量无线基站与无线核心网和L3 VPN落地点之间的L3性能，但是不能测量L2 VPN接入点设备与L3 VPN落地点之间端到端的L3性能。
本实施例实现L2设备借用无线基站的L3地址实现L3 Y.1564响应，提供L2 VPN接入点到L3 VPN落地点之间的端到端L3性能测量。本实施例说明如下：
无线基站提供L3接口实体，其本身可以支持L3维护诊断子实体Y.1564性能测量的功能，于此，与所述无线基站对接的L2 VPN接入点的L2设备部署L3维护诊断子实体Y.1564性能测量功能；
L2设备本身不用创建L3接口，直接借用无线基站的L3地址，于此，L3接口实体部署在无线基站和L2 VPN接入层L2设备上，其中，L3接口地址子实体部署在无线基站上，而L3维护诊断子实体Y.1564性能测量功能部署在L2 VPN接入层L2设备上；
L2设备上部署的L3维护诊断子实体Y.1564性能测量功能继承L3接口实体的接口地址属性，L3接口实体的L3接口地址子实体部署于无线基站上；
通过静态命令配置L2设备开启L3 Y.1564性能测量代理响应功能并静态配置Y.1564响应的L3接口地址(即无线基站的L3接口地址)，其中，L2设备本身并不创建L3接口，且并不影响无线基站L3接口的其他任何功能；或者，开启L2设备L3 Y.1564响应功能并开启L3地址监视模式，通过监视 无线基站L3地址解析协议(ARP)，获取无线基站的对接基站的L3地址；
开启L3维护诊断Y.1564功能后，L2设备立即侦听经过该L2设备接入点的业务流，侦听到Y.1564协议报文后代理L3接口实体进行Y.1564响应，同理，也可以代理L3接口主动发起Y.1564测量。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现上述L2和L3 VPN中L3维护诊断方法。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
以上显示和描述了本申请的基本原理和主要特征和本申请的优点。本申请不受上述实施例的限制，上述实施例和说明书中描述的只是说明本申请的原理，在不脱离本申请精神和范围的前提下，本申请还会有多种变化和改进，这些变化和改进都落入要求保护的本申请范围内。
工业实用性
通过本发明实施例，在移动回传业务承载L2+L3 VPN网络中L2设备端借用L3地址实现L3地址简化配置或者免配置，使得L2设备可以方便地支持L3维护诊断，从而支持移动回传业务路径端到端的L3维护诊断，解决了L2和L3 VPN桥接组网带来的业务路径分割问题。

Claims (11)

  1. 一种二层L2和三层L3虚拟专用网络VPN中L3维护诊断方法，包括：
    L2设备借用相应L3接口的L3地址；
    所述L2设备通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
  2. 如权利要求1所述的方法，其中，所述L3接口所在的L3设备与所述L2设备直连。
  3. 如权利要求1所述的方法，其中，所述L2设备借用相应L3接口的L3地址包括：
    所述L2设备借用通过配置命令静态配置的L3接口的L3地址；或者，
    所述L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址。
  4. 如权利要求3所述的方法，其中，所述L2设备借用通过L3地址主动监视获得的相应L3接口的L3地址之前，还包括：所述L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址。
  5. 如权利要求4所述的方法，其中，所述L2设备通过L3地址主动监视获得所述L2设备能借用的L3接口的L3地址包括：
    监视特定L3地址解析协议ARP，以获得能借用的L3地址；或者，
    监视特定L3报文，以获得能借用的L3地址。
  6. 一种L2和L3VPN中L3维护诊断装置，设置于L2设备，包括：
    L3维护诊断子实体，设置为：借用相应L3接口的L3地址；
    处理模块，设置为：通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断。
  7. 如权利要求6所述的装置，其中，所述L3接口所在的L3设备与所述L2设备直连。
  8. 如权利要求6所述的装置，其中，所述L3维护诊断子实体，包括：
    第一借用地址单元，设置为：借用通过配置命令静态配置的L3接口的L3地址；或者，
    第二借用地址单元，设置为：借用通过L3地址主动监视获得的相应L3接口的L3地址。
  9. 如权利要求8所述的装置，其中，所述第二借用地址单元，，还设置为：通过L3地址主动监视获得能借用的L3接口的L3地址。
  10. 如权利要求9所述的装置，其中，所述第二借用地址单元，设置为：
    监视特定L3地址解析协议ARP，以获得能借用的L3地址；或者，
    监视特定L3地址，以获得能借用的L3地址。
  11. 一种L2和L3VPN中L3维护诊断系统，包括：如权利要求6-10任一项所述的L2设备以及L3设备，所述L2设备借用相应的L3接口的L3地址，并通过借用L3接口的L3地址代理所述L3接口进行L3维护诊断，其中，所述L3接口位于L3设备上。
PCT/CN2016/083519 2015-09-28 2016-05-26 一种l2和l3 vpn中l3维护诊断方法、装置及系统 WO2017054478A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16850103.9A EP3358784A4 (en) 2015-09-28 2016-05-26 L3 maintenance and diagnosis method adopted in l2 and l3 vpn, and device and system utilizing same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510629356.6A CN106559279B (zh) 2015-09-28 2015-09-28 一种l2和l3 vpn中l3维护诊断方法、装置及系统
CN201510629356.6 2015-09-28

Publications (1)

Publication Number Publication Date
WO2017054478A1 true WO2017054478A1 (zh) 2017-04-06

Family

ID=58415761

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/083519 WO2017054478A1 (zh) 2015-09-28 2016-05-26 一种l2和l3 vpn中l3维护诊断方法、装置及系统

Country Status (3)

Country Link
EP (1) EP3358784A4 (zh)
CN (1) CN106559279B (zh)
WO (1) WO2017054478A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7881314B2 (en) * 2006-05-01 2011-02-01 Cisco Technology, Inc. Network device providing access to both layer 2 and layer 3 services on a single physical interface
CN102611618A (zh) * 2012-02-23 2012-07-25 中兴通讯股份有限公司 路由保护切换方法及装置
CN103716172A (zh) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 一种基于多协议标签交换的oam方法及装置
CN104683187A (zh) * 2015-03-12 2015-06-03 烽火通信科技股份有限公司 一种实现路由器二层vpn业务物理接口端到端测量的方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008114361A1 (ja) * 2007-03-16 2008-09-25 Fujitsu Limited 経路データ収集方法、レイヤ２装置、キャリア網内装置及び経路データ収集装置
US9137101B2 (en) * 2011-11-23 2015-09-15 Avaya Inc. Multi-layer network diagnostic tracing
CN104378296B (zh) * 2013-08-15 2018-04-10 新华三技术有限公司 一种报文转发方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7881314B2 (en) * 2006-05-01 2011-02-01 Cisco Technology, Inc. Network device providing access to both layer 2 and layer 3 services on a single physical interface
CN102611618A (zh) * 2012-02-23 2012-07-25 中兴通讯股份有限公司 路由保护切换方法及装置
CN103716172A (zh) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 一种基于多协议标签交换的oam方法及装置
CN104683187A (zh) * 2015-03-12 2015-06-03 烽火通信科技股份有限公司 一种实现路由器二层vpn业务物理接口端到端测量的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3358784A4 *

Also Published As

Publication number Publication date
CN106559279A (zh) 2017-04-05
CN106559279B (zh) 2021-02-02
EP3358784A1 (en) 2018-08-08
EP3358784A4 (en) 2018-08-08

Similar Documents

Publication Publication Date Title
CN113169891B (zh) 通过软件定义的操作管理及维护来识别和解决结构网络中的算法问题
EP3586528B1 (en) Methods, systems and computer readable media for providing integrated service capability exposure function (scef), service capability server (scs) and application server (as) services
US11102219B2 (en) Systems and methods for dynamic analysis and resolution of network anomalies
EP3586529B1 (en) Method, system and computer readable medium for providing service capability exposure function (scef) as a cloud service
WO2020063213A1 (zh) 本地局域网通信方法、设备及系统
US10638409B2 (en) Wi-Fi roaming management
WO2017107018A1 (zh) 应用拓扑关系发现的方法、装置和系统
US20180338187A1 (en) Advanced wi-fi performance monitoring
US10819572B2 (en) Switch triggered traffic tracking
EP3586530A1 (en) Methods, systems and computer readable media for providing service capability exposure function (scef) as a diameter routing agent(dra) feature
US20220150154A1 (en) Automatically managing a mesh network based on dynamically self-configuring node devices
US10439920B2 (en) Network performance monitoring
NL2033607B1 (en) Traffic steering and cross-layered and cross-link mobility management techniques for multi-access management services
CN114270907B (zh) 自动接入点布置系统和方法
KR102621982B1 (ko) V2x 통신들을 위한 애플리케이션 서버 및/또는 서비스들의발견을 위한 방법들, 장치 및 컴퓨터 판독가능한 매체
US11165672B2 (en) Application performance management integration with network assurance
US11595254B2 (en) Systems and methods to control operation of virtualized networks
CN112956158B (zh) 结构数据平面监视
CN106201769B (zh) 服务器系统、非临时计算机可读存储介质以及用以增强服务器系统中的存储器容错率的方法
US11653194B2 (en) Techniques to provide resiliency and overload control for access and mobility management functions
US11683228B2 (en) Automatically managing a role of a node device in a mesh network
US10924369B2 (en) Traffic aware operations, administration, and maintenance (OAM) solutions for internet of things (IoT) networks
US11201921B2 (en) Virtual devices in internet of things (IoT) nodes
WO2017054478A1 (zh) 一种l2和l3 vpn中l3维护诊断方法、装置及系统
Labor SDNizing the Wireless LAN-A Practical Approach

Legal Events

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

Ref document number: 16850103

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016850103

Country of ref document: EP